AeroWEB: An Information Infrastructure for the Supply Chain
暂无分享,去创建一个
Information flow up and down the supply chain, particularly for complex products such as automobiles, aircraft, and weapons systems is complex, difficult, fraught with errors and time consuming. In the defense business, for example, just the engineering trade-off process in the conceptual design phase can take up to a year before all the information requested is available for the design engineering team to compare alternatives (Schwart97). Some of the problems encountered include the inability of small suppliers far down the chain to access technical data created with CAD systems to which they do not have access, inaccurate or wrong versions of technical data when the supplier eventually obtains it, and difficulty in contacting people to request clarification. EDI and geometric modeling standards (e.g. STEP) and Email have started to address these problems, but they do not address all of them. Email, for instance often results in huge CAD files bogging down a suppliers email system (often using a dial up modem) only to have it discarded because it was not appropriate to their business. EDI/EC and STEP standards focus on standards for the exchange and sharing of data, not on their smooth and efficient movement up and down the chain.
[1] Edward J. Barkmeyer,et al. Manufacturing Systems Integration Initial Architecture Document , 1991 .
[2] Minder Chen,et al. A framework for integrated CASE , 1992, IEEE Software.
[3] J. J. Mills,et al. The system integration architecture: a framework for extended enterprise information systems , 1997 .