The Systems Integration Architecture: an Agile Information Infrastructure

  • John J. Mills
  • Ramez Elmasri
  • Kashif Khan
  • Srinivas Miriyala
  • Kalpana Subramanian
Part of the IFIP — The International Federation for Information Processing book series (IFIPAICT)


The Systems Integration Architecture project is taking a fresh approach to integration with special emphasis on supporting Agile, Virtual enterprises and their unique need for reconfigurable, de-centralized information systems. SIA is based on a different conceptual model of integration — called the TAR model — one which allows higher level integration than the traditional common, neutral format, shared database. The basic concept is that all information processing consists of a series of transformations of data sets called “Aspects” into other “Aspects”. The transformations are effected by what are called Functional Transformation Agents which provide a single function and have a well defined interface structure which allows them to be integrated in a variety of ways. The Systems Integration Architecture provides three high level services which allow FTA’s to be defined, combined into diverse networks which provide transformations of aspects in a manner transparent to the user and executed under a variety of control algorithms in a heterogeneous, de-centralized environment. These are: an Executive--to provide business control services; a Librarian--to act as somewhat of a meta data dictionary, keeping track of FTA’s and their input and output Aspects; and a Network--which is based on the Common Object Request Broker Architecture to facilitate communication between objects on a heterogeneous network. An extended entity relationship diagram is provided and each of the objects in the system is described. A simple example of its use is provided.


Business Process Virtual Enterprise Assembly Planning Product Data Management Common Object Request Broker Architecture 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    Mayer, R.J., “IDEFO Function Modeling,” Pub. by Knowledge Based Systems, College Station, TX, 1990.Google Scholar
  2. 2.
    Mettala, E. Private Communication, September, 1994Google Scholar
  3. 3.
    Mills, J.J., “A Basis Model for Agile Computer Integrated Manufacturing,” to be presented at ICCIM `95, Singapore, September, 1995.Google Scholar
  4. 4.
    Fulton, J.A., PDES/STEP Model Unification: SUMM,“ Product Data International, May, pp. 6–7, 1992.Google Scholar
  5. 5.
    Anon, “CIM-OSA Reference Architecture Specification,;’ ESPRIT Project Nr 688, pub. by CIMOSA/AMICE, Brussels, Belgium, 1990.Google Scholar
  6. 6.
    Balzer„ R., Goldman, N., and Wile, D “On the Transformational Implementation Approach to Programming, ” Proc. 2nd International Conference Software Engineering, pp. 337–343, 1976.Google Scholar
  7. 7.
    Mostow, J., “Program Transformations for VLSI; IJCAI-83, 1983.Google Scholar
  8. 8.
    Ullrich, K., and Seering, W, Conceptual Design: Synthesis of Systems of Components,“ in Intelligent and Integrated Manufacturing Analysis and Synthesis, PED Vol. 25, ASME. NY, 1987, PP 57–66.Google Scholar
  9. 9.
    Shah, J.J., and Wilson, P.R. “Analysis of Knowledge Abstraction, Representation and Interactions Requirements for Computer Aided Engineering,” Computers in Engineering, Vol. 1, 1988, Pub. by ASME, New York, pp. 17–24.Google Scholar
  10. 10.
    Talukdar, S.N., and Fenves, S.J., “Towards a Framework for Concurrent Design, in D. Sriram et. al, Computer-Aided Cooperative Product Development, MIT-JSME Workshop, November 1989, Lecture Notes in Computer Science No. 492, Springer-Verlag, 140–151.Google Scholar
  11. 11.
    SIFRAME V6.0 System Overview,“ Siemens Nixdorf, New York, 1992Google Scholar
  12. 12.
    Betz, M., “Interoperable Objects,” Dr Dobbs Journal, pp 18–39, October, 1994.Google Scholar
  13. 13.
    R. Elmasri and S. Navathe, Fundamentals of Database Systems, Second Edition, Benjamin/Cummings, 1994zbMATHGoogle Scholar
  14. 14.
    Davis D.B. “Software that makes your workflow,” Datamation, April 15, 1991.Google Scholar
  15. 15.
    Dyson E. “Workflow,” Forbes November 23, 1992.Google Scholar

Copyright information

© Springer Science+Business Media Dordrecht 1995

Authors and Affiliations

  • John J. Mills
    • 1
  • Ramez Elmasri
    • 1
  • Kashif Khan
    • 1
  • Srinivas Miriyala
    • 1
  • Kalpana Subramanian
    • 1
  1. 1.The Agile Aerospace Manufacturing Research Center, The Automation & Robotics Research InstituteThe University of Texas at ArlingtonFort WorthUSA

Personalised recommendations