separate integration and information systems

1

• 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

• 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 and navigation
• incremental development and prototyping
• tailored to user specification

2
Alternative I Incorporate Integration into
System Implementation
3
User Expectation Fully Integrated Architecture

• Common User Interface
• single point of access
• identical look feel
• Common Work Flow
• identical behavior of every component
• Common Repository
• standardized objects
• consistent data

4
Alternative II Create External Integration
Components
5
General Approaches toIntegrating Information
Systems
6
COMMON PROCESS
COMMON OBJECTS
7
Mission

• inprove transparency and performance of future
  accelerator projects
• introduce specialized information systems for
  each life cycle activity
• create integrated solution
• connect systems at UI level
• propagate transactions (eg. update, ...)
• connect repositories

8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11

• Life cycle objects are defined in common
  (integrated) schema ...
• ... but available information systems concentrate
  on specific life cycle activities
• 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

12
conceputal integration common process definition
13
technical integration common user interface
Technical Integrationcommon workflow(shared
libraries)
technical integration common repository
14
conceptual integration common schema definition
15

• Integration top down
• reconstruct object which were disjoint
• integrate connect humans, tasks and systems
  horizontal
• integration disciplines and functions
• integrate business processes, work flow, data
  schemata
• Integration bottom up
• build a whole from parts
• difficulty no generic solution known for
  integration of information systems

16
Accelerator DocumentationIntegrating AMS and PDMS
17
(No Transcript)