The Need for a Generic Framework for Systems Integration
This paper outlines the need for a widely accepted generic framework for systems integration within manufacturing enterprises. The provisions of this framework would form a basis for the specification of integration projects and sub-components such as software packages in order to permit the interchange, reconfiguration, expansion and transferability of the whole or part solutions so generated. The overall aim is to allow a logical mapping of integration tools, implementations and solutions to physical resources at all phases from manufacturing system inception to operation so enabling rapid and cost-effective response to changes in products, markets, enabling technologies and manufacturing methodologies.
the need to proceed from a position of existing installed bases of manufacturing machines and operations, both automated and manual,
the integration of the activities of contemporary proprietary software packages with specific reference to production planning and control, and
the provision of an environment for the definition and realisation of interaction, synchronisation and organisation between manufacturing entities.
KeywordsData Repository Shop Floor Manufacturing Cell Integration Tool Exception Handling
Unable to display preview. Download preview PDF.
- 1.Day, J D, and Zimmerman, H,: The OSI Reference Model: Proceedings of IEEE, 1983, 71, (12)Google Scholar
- 2.MAP and TOP Version 3.0 Specifications: Obtainable from the Society of Manufacturing Engineers, Detroit, Michigan, USAGoogle Scholar
- 3.Weston, R H, Sumpter, C M, Gascoigne, J D, and Hodgson, A,: MAP and Integration Architectures in the Flexible Manufacture of PCB’s: Proceedings of CIRP Int Conf on Production Research, Cincinnati, Ohio, USA, June 1987Google Scholar
- 4.Manufacturing Message Specification, Part 1: Service Specification, Appendix B: Guidelines for Writing Companion Standards: EIA Project 1393A Draft 6, May 1987Google Scholar
- 5.Personal Communication: Cincinnatti Milacron, Ohio, USA, August 1987Google Scholar
- 6.ANSI American National Standard Database Language SQL: American National Standards Institute Inc, New York, December 1986Google Scholar
- 7.Teorey, T J, and Fry, J P,: Design of Database Structures: Prentice Hall, 1982Google Scholar
- 8.Vernadat, F,: Artificial Intelligence in CIM Databases, IFS Artificial Intelligence: Impliciations for CIM, 1988Google Scholar
- 9.Su, S Y W, Lam, H, Khatib, M, Krishnamurthy, V, Kilmar, A, Malik, S, Mitchell, M, and Barkmayer, E,: The Architecture and Prototype Implementation of an Integrated Manufacturing Database Administration System: Proceedings of Spring COMPCON Conference, San Francisco, CA, USA, Dec 1986Google Scholar
- 10.ICAM Project: Computer Program Development Specification for ICAM Integrated Support Systems (IISS) Configuration Item: Precomputer prepared by Control Data Corporation and D Appleton Company, USA, Dec 1983Google Scholar
- 11.Rui, A, Weston, R H, Gascoigne, J D, Hodgson, A, and Sumpter, C M,: Automating Information Transfer in Manufacturing Systems: Computer Aided Engineering Journal, June 1988Google Scholar
- 12.Hillawi, J I, and Bennett, K R,: EDIF - An Overview: Computer Aided Engineering Journal, March 1987Google Scholar