1 / 12

Mission

Mission. inprove transparency and performance of future accelerator projects introduce specialized information systems for each life cycle activity create integrated solution integrate: connect humans, tasks and systems define common processes propagate transactions (eg. update, ...)

anila
Download Presentation

Mission

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mission • inprove transparency and performance of future accelerator projects • introduce specialized information systems for each life cycle activity • create integrated solution • integrate: connect humans, tasks and systems • define common processes • propagate transactions (eg. update, ...) • connect system user interfaces and repositories Concepts for Integrating Information Systems

  2. Installation &Commissioning Manufacturing Design Specification Life Cycle Activitiesand Information Objects Concepts for Integrating Information Systems

  3. Integration Levels conceptual integration COMMON PROCESS common user interface common workflow(shared libraries) common repository conceptual integration COMMON OBJECTS Concepts for Integrating Information Systems

  4. Common Schema • Life cycle objects are defined in a common (integrated) schema ... Concepts for Integrating Information Systems

  5. Disconnected Repository • ... but available information systems concentrate on specific life cycle activities only • general purpose systems aim at several industries, e.g. • RM for mechanical engineering, software engineering, ... • PDM for plant construction, automtotive, transportation, ... • AM for technical infrastructure, IT devices, ... • system boundaries disconnect schema Concepts for Integrating Information Systems

  6. Form Form LIB LIB LIB LIB LIB LIB System A System B User Expectation • Fully Integrated Architecture • expect systems „to melt“ • Common User Interface • single point of access • identical look & feel • Common Work Flow • identical behavior of every component • Common Repository • standardized objects • consistent data Concepts for Integrating Information Systems

  7. System I System II Form Form open () LIB LIB LIB LIB LIB LIB call () refer-to Alternative I„Integrated Integration“ • incorporate integration into system implementation • distributed across systems • stand-alone operability lost • increasing complexity with added features • high change efforts • change in one systems might affect all systems • „open“ behavior • focussed on ad-hoc queries • incremental development and prototyping enabled • tailored to user specification Concepts for Integrating Information Systems

  8. CommonUser Interface System I System II Form Form Portal KnowledgeRepository LIB LIB LIB LIB LIB LIB ProcessDatabase WorkflowEngine Repository Replication Strategy IntegratedSchema Alternative IIExternal Components • separate integration and information systems • information systems can still be operated stand alone • conceptual and technical integration encapsulated • robust wrt changes • information systems largely untouched by integration • relatively static behavior • pre-defined views and processes • high initial cost and effort Concepts for Integrating Information Systems

  9. Req-Comp-Rel Comp-Eq-Rel Requirement describes Component is a Equipment Schema Matching • connect conceptually related but physically distributed databases • implement by queries or by replication • static mapping • extends existing schema by using e.g. mapping tables • relationships usually established manually • dynamic mapping • uses key attributes to relate datasets • requires naming convention for both databases Concepts for Integrating Information Systems

  10. should enable information navigation, retrieval and update optimum: portal as common point of access navigation elements can be hard-coded directly into application or collected on a dedicated external form require the views of the target GUI to be directly accessible from outside frequently not the case problem: authentication when propagating between systems retrieval using common reporting tool for casual users access and render information content at database level system-independent look & feel problem: authentication retrieval using generic forms forms match table definitions accessibility vs. ergonomy update requires the system‘s transaction mechanism no way to be included in external component expert users at native clients Common User Interface Concepts for Integrating Information Systems

  11. AMS-PDMS Pilot for Workflow Integration Documentfrom PDMS AMS-PDMS Integrator AMS Native Client no generic solution known for workflow integration Concepts for Integrating Information Systems

  12. Experience • Integration is ideally performed top down • develop common process and schema definitions first • customize systems accordingly before release • Integration usually happens bottom up • introduce information systems first to deliver use • import legacy data into systems • reorganize and clean legacy data for integration • hope not to encounter contradicting legacy data • Integrated concept is needed nevertheless • Integration has high demand of resources Concepts for Integrating Information Systems

More Related