Ergen, E (2005) Formalization of life-cycle data management of engineered-to-order components using advanced tracking technologies. PhD thesis, Carnegie Mellon University, USA.
Abstract
In construction supply chains, management of engineered-to-order (ETO) components and the related information is challenging. ETO components are highly customized, have long lead times, and usually on the critical path in the construction schedules. Therefore, ETO components and related component information need to be tracked individually in a supply chain, and this information should be easily available for the participants of an ETO supply chain for effective planning, production and maintenance. Current approaches mostly use labor-intensive methods to record and exchange component-related information and result in unreliable or incomplete information. Advanced tracking technologies, such as radio frequency identification, can enable streamlined information flow by storing some component-related information on the component and communicating this information to different parties as the component flows in the supply chain. Using advanced tracking technologies, components will become intelligent knowing their identities, handling, storage and installation instructions, and histories, and communicate this information to different databases on an as needed basis. However, in order to utilize these technologies, information items and their flow patterns need to be formalized so that requirements for data flow can be derived, and appropriate mechanisms and technologies to support such processes can be identified. In this research, to identify information flow patterns for ETO components, I focused on precast concrete supply chains, and formalized flow of information related to precast components through post-design phases in a supply chain. Based on the identified information flow pattern, I selected two types of components, precast concrete components and fire valves, and focused on two different phases; manufacturing phase and operations and maintenance phase. For those two component types, I identified the requirements and corresponding approaches needed for technology deployment and testing under two different settings in a construction supply chain towards the achievement of my grand vision. I validated the information flow patterns by two descriptive case studies. The requirements and reasoning mechanisms identified for locating precast components was validated with a field test, and the requirements identified for tracking fire valves and their histories were validated with a longevity test.
| Item Type: | Thesis (Doctoral) |
|---|---|
| Thesis advisor: | Akinci, B |
| Uncontrolled Keywords: | construction supply chain; engineered-to-order; radio frequency identification; reasoning; case studies; precast concrete; concrete supply; manufacturing |
| Index terms: | information flow, critical path, data management, field test, precast concrete, valve, construction supply chain, case study, lead time, reasoning, history, radio frequency identification, concrete supply, database, engineer-to-order, testing, identity, design phase |
| Subjects: | cognitive psychology, building materials, data management, information systems, architectural and construction history, control systems, operations research, data collection methods, project controls, manufacturing engineering, digital technology, sociology, professional practice, construction logistics |
| Topics: | Time Control, Research Practice, Supply Chain Management, Design Practice, Construction Materials, Digital Applications, Engineering Principles |
| Descriptive scope: | 4 PCTE |
N.B. Descriptive scope is a count of how many of the five facets of empirical research are indicated by the words used in title, abstract and keywords. It is not intended as a judgement on the research; merely a count of the kind of word we would expect to indicate Phenomenon, Concepts, Theoretical framing, Empirical techniques, Analytical techniques. If all five are present, then a code of “5 PCTEA” will indicate this. If you feel the coding for this record is questionable, we welcome discussion around the terms we matched or the way we categorized them. The facet you would expect may not be coded, or a facet may be coded inappropriately. This can also bear on a larger question, of which facets should be treated as defining in construction management research. Please get in touch, and we will look at it. More details here