Production Technology Textbook Pdf

0 views
Skip to first unread message

Vinnie Frevert

unread,
Aug 3, 2024, 12:25:53 PM8/3/24
to blocargramling

This new edition textbook provides comprehensive knowledge and insight into various aspects of manufacturing technology, processes, materials, tooling, and equipment. Its main objective is to introduce the grand spectrum of manufacturing technology to individuals who will be involved in the design and manufacturing of finished products and to provide them with basic information on manufacturing technologies.

Manufacturing Technology: Materials, Processes, and Equipment, Second Edition, is written in a descriptive manner, where the emphasis is on the fundamentals of the process, its capabilities, typical applications, advantages, and limitations. Mathematical modeling and equations are used only when they enhance the basic understanding of the material dealt with. The book is a fundamental textbook that covers all the manufacturing processes, materials, and equipment used to convert the raw materials to a final product. It presents the materials used in manufacturing processes and covers the heat treatment processes, smelting of metals, and other technological processes such as casting, forming, powder metallurgy, joining processes, and surface technology. Manufacturing processes for polymers, ceramics, and composites are also covered.

The book also covers surface technology, fundamentals of traditional and nontraditional machining processes, numerical control of machine tools, industrial robots and hexapods, additive manufacturing, and industry 4.0 technologies.

The book is written specifically for undergraduates in industrial, manufacturing, mechanical, and materials engineering disciplines of the second to fourth levels to cover complete courses of manufacturing technology taught in engineering colleges and institutions all over the world. It also covers the needs of production and manufacturing engineers and technologists participating in related industries where it is expected to be part of their professional library. Additionally, the book can be used by students in other disciplines concerned with design and manufacturing, such as automotive and aerospace engineering.

Professor Helmi A. Youssef - Based on several research and educational laboratories, which he has built, Professor Youssef founded his own scientific school in both Traditional and Non-traditional Machining Technologies. In the early 1970s, he established the first NTM research laboratory in Alexandria University. Since that time, he carried out intensive research in his fields of specialization and supervised many Ph.D. and M. Sc. theses. Professor Youssef has organized and participated in many international conferences. He has published many scientific papers in specialized journals. He authored many books in his fields of specialization, two of which are singly authored. Currently, Professor Youssef is an emeritus Professor in PED, Alexandria University. His work in the time being involves developing courses and conducting research in the areas of metal cutting and nontraditional machining.

Professor M. Hamed Ahmed constructed and taught numerous graduate and undergraduate courses in the general fields of materials and manufacturing, to name a few; Failure Analysis, Material Selection, Finite Element Analysis, Fracture Mechanics, Non-destructive Testing, Advanced Manufacturing Processes, Theory of Plasticity, Solid Mechanics, Die Design, Metal Forming, Metal Cutting, Non-conventional Machining, Welding Technology, Engineering Materials, and Manufacturing Technology. Professor Ahmed took part in establishing and developing laboratories in the same fields including The Material Technology Lab. (Alex. University), Material Testing, Forming Machines, CNC Machining, Metrology, and Electroplating Labs. (UAE University), as well as Non-conventional Machining, and CNC Machining Labs. (King Abdul-Aziz University, KSA). Over the years, Professor Ahmed has supervised numerous M.Sc. and Ph.D. degrees, covering the areas of Electro-Discharge Machining, Failure of Welded Joints, Extrusion of Fluted Sections, Plasma Cutting, Ultrasonic Machining, Pulsed Current MIG Welding, Compression of Tubular Sections, Forward Tube Spinning, Characterization of Engineering Materials Using Nodal Analysis, Selection of Non-Traditional Machining Processes, Thermo-mechanical Rolling, Functionally Graded Metal Matrix Composites, Manufacturing of Porous Metals and AM Assisted Manufacturing. Prof. Ahmed has a good track record of publishing in numerous national/international conferences and reputable journals. He also contributed to the development and improvement of industrial activities within Alexandria through consultations related to solving design and manufacturing problems, material and product inspection, failure analysis, plant layouts, feasibility and opportunity studies, as well as running crash and training courses in the relevant fields of interest.

This book will not get you started with shiny, nor talk how to work with shiny once it is sent to production.What we will be discussing in this book is the process of building an application that will later be sent to production.

Why this topic? Lots of blog posts and books talk about getting started with shiny (Chang et al. 2022) or about what to do once your application is ready to be sent to production.Very few (if any) talk about this area in-between: how to confidently work with shiny once you know the basics, and before you send it to production.

If you are starting to read this book, we assume you have a working knowledge of how to build a small application using shiny, and want to know how to go one step further.In other words, you already have some knowledge about how shiny works, are able to build a small working application, and want to know how to build a serious, production-grade application that can be sent to production.

The content of this book oscillates between conceptual discussions (e.g., what is complexity?), exploration of project-management questions (e.g., how do we organize work when building production shiny applications?), and technical topics (e.g. what are shiny modules, or how do I optimize shiny?), with a large portion of the book being dedicated to technical questions.

Team managers who want to help to organize work, and shiny developers who want to learn about project management.This group will find relevant content in the first 1/3 of this book (roughly until Chapter 5).

Developers who want to cover medium to advanced shiny topics that will be relevant to production.This group will be more interested in the rest of the book, which roughly spans from Chapter 6 to the end.Note that the technical elements covered in this book range from intermediate to advanced topics, and we hope that you will find relevant topics for your current goals, whatever your level is.

There have been a lot of definitions of what production is, and even today if you ask around you will get a wide range of different answers.We like to think that a piece of software is in production when it combines the three following properties, not only for the users, but also the engineers working on it:

Indeed, the users rely on the app to work so that they can do their job, and expect it to deliver meaningful results that they can count on.From the engineering point of view, a production-grade software can be relied upon in the sense that developers count on it to run as expected, and they need to rely on the software to be resilient to change, i.e to be modular, documented, and strongly tested so that changes can be integrated with confidence.

A production software also has real-life impact if something goes wrong: users will make wrong decisions, they might be unable to do their day-to-day work, and there are all the things that can happen when the software you use on a daily basis fails to run.From the engineering point of view, a production-grade software has real impact when something goes wrong: someone has to fix the bug, the company selling the software might lose money, data can be lost, and so on.

This is what this book is about: building shiny applications that can be used, on which you and your users can rely, and including all the tools that will help you prevent things from going wrong, and when they eventually do, making sure you are equipped to quickly fix the bugs.

Colin works at ThinkR, a French agency focused on everything R related. During the day, he helps companies to take full advantage of the power of R, by building tools (packages, web apps, etc.) and setting up infrastructure. His main areas of expertise are data and software engineering, infrastructure, web applications (front-end and back-end), and R in production.

Sbastien is a data scientist at ThinkR, where he teaches anything R related from beginner to expert level, guides R developers towards implementation of best practices, and creates tailor-made R solutions for the needs of his customers.

Vincent is the founder of ThinkR. He created the first proof-of-concept framework for shiny applications inside packages; an idea which has led to the creation of golem.If you feel like a GitHub archaeologist, this very first version is still available with a little bit of exploration!

Cervan is a Data Scientist at ThinkR.He is enthusiastic and motivated when it comes to rolling up his sleeves for new challenges, even if it means venturing dangerously into the depths of R, learning new languages, and experimenting outside your comfort zone.

Open source is moving (very) fast, and some of the tools described in this book are still under active development.But good news!A large portion of this book is about the methodology, and not purely the technology, so even if some of the packages and code sections used in this book can (and will) become obsolete, a significant part of what is described in this book will still be relevant.

Package names are in curly brackets in code format (e.g., rmarkdown), and inline code and file names are formatted in a typewriter font (e.g., knitr::knit('doc.Rmd')).Function names are formatted in a typewriter font and followed by parentheses (e.g., render_book()).Larger code blocks are formatted in a typewriter font and have a gray backgroud, e.g.:

c80f0f1006
Reply all
Reply to author
Forward
0 new messages