1 / 38

Integrated Information Management for Future Projects

Integrated Information Management for Future Projects. Lars Hagge Deutsches Elektronen-Synchrotron, Hamburg Presented at CHEP 2000 Padova, 08-02-2000. Overview. Why Do We Need Information Management? What Do We Need? - Visions and Vocabulary Process Analysis and Architecture Design

nirav
Download Presentation

Integrated Information Management for Future Projects

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. Integrated Information Management for Future Projects Lars HaggeDeutsches Elektronen-Synchrotron, Hamburg Presented at CHEP 2000Padova, 08-02-2000

  2. Overview • Why Do We Need Information Management? • What Do We Need? - Visions and Vocabulary • Process Analysis and Architecture Design • Demonstration Systems • Organizing Information Management • Where Are We Now? Lars Hagge: Integarted Information Management

  3. Overview • Why Do We Need Information Management? • What Do We Need? - Visions and Vocabulary • Process Analysis and Architecture Design • Demonstration Systems • Organizing Information Management • Where Are We Now? Lars Hagge: Integarted Information Management

  4. produce need-to-know Documents and Information Lars Hagge: Integarted Information Management

  5. Information Management Yesterday Search Engine Document Types Detector Components Lars Hagge: Integarted Information Management

  6. Search Engine Document Types Detector Components Information Management Yesterday and Today • up-to-date information • at least on daily basis • both content and cross-linking • availability over several decades • world-wide online access • simultaneous multi-user access • location-independent direct access • multi-lingual information and interfaces • search for category and content • information retrieval Lars Hagge: Integarted Information Management

  7. Search Engine Document Types Detector Components Information Management Yesterday and Today • multi-media information • paper documents • correspondence, drawings, photos, ... • electronic or digitized documents • audio, video, models, ... • interactive documents • 3d-animation of e.g. installation procedures • communication with authors (red-lining) • calculations and simulation Lars Hagge: Integarted Information Management

  8. Search Engine Document Types Detektor Components Information Management Today • information is • not known to all project team members • incomplete and / or outdated • difficult to find • not accessible for all project team members • as a consequence • work is delayed • project cost increases • safety problems can be caused ... and tommorow? Lars Hagge: Integarted Information Management

  9. Search Engine Document Types Detector Components Information Management Yesterday and Today archiving is good access is better Lars Hagge: Integarted Information Management

  10. Overview • Why Do We Need Information Management? • What Do We Need? - Visions and Vocabulary • Process Analysis and Architecture Design • Demonstration Systems • Organizing Information Management • Where Are We Now? Lars Hagge: Integarted Information Management

  11. Vision Design Construction Operation Specification Prototyping Installation Upgrade Auto-IdentificationBarcode mobileComputing CAD Asset Management Facility Management Engineering DataManagement (EDM) Accelerator Life Cycle Lars Hagge: Integarted Information Management

  12. Vision Design Prototype Construction Installation Operation Maintenance Administration Information Providers and Consumers End User (Scientist) Construction Workshops Service-Groups Lars Hagge: Integarted Information Management

  13. Maintenance * part machine 1 1 * * 1 1 1 1 history alignment 1 Three Levels of Complexity TEMPLATE INDIVIDUAL(PART) COMPLEX Vision Design Prototype Construction Installation Operation drawing Lars Hagge: Integarted Information Management

  14. Project Documentation TEMPLATE INDIVIDUAL(PART) COMPLEX • Design • drawings • set of documents • Construction • technical data • for each part • Installation • alignment • overall model • Business Information • Manufacturer, Cost, Deadlines, ... • Project Management • Structures, Budgets, Ressources, Schedules, Results, ... • Documentation • Reports, Presentations, Protocols, ... Lars Hagge: Integarted Information Management

  15. Integrated User Interface Lightweight Viewing (Web-) Client for Casual UsersFully Functional CAx-, Office-, SAP- ... (Web-) Clients for Expert Users EDM Asset Mgmt. GIS FM BF (SAP) Project Mgmt. Documt.Mgmt. Workflow Common Data Repository Integrated Information Management Lars Hagge: Integarted Information Management

  16. Overview • Why Do We Need Information Management? • What Do We Need? - Visions and Vocabulary • Process Analysis and Architecture Design • Demonstration Systems • Organizing Information Management • Where Are We Now? Lars Hagge: Integarted Information Management

  17. EDM Asset Mgmt. GIS FM BF (SAP) Project Mgmt. Documt.Mgmt. Documt.Mgmt. Workflow Common Data Repository An ExampleDocument Mgmt. Processes Integrated User Interface Lightweight Viewing (Web-) Client for Casual UsersFully Functional CAx-, Office-, SAP- ... (Web-) Clients for Expert Users Lars Hagge: Integarted Information Management

  18. Dualism of Real World and IT:Business Process and IT Process archiving authoring indexing approval distribution publication expiration revision alarming Lars Hagge: Integarted Information Management

  19. Authoring Editing Editing Reviewing initialize perform Publication Publication initialize perform Distribution Distribution Discussion initialize perform Revising Process Modelling Business Process Workflow IT-Process Lars Hagge: Integarted Information Management

  20. EDM Asset Mgmt. GIS FM BF (SAP) Project Mgmt. Documt.Mgmt. Changes & Repairs Re-Loctaing Capacity Planning Inventory Kernel Database Business Disciplines • systems represent collections of processes • support the business process: “using an EDM system does not replace a designer” Lars Hagge: Integarted Information Management

  21. Asset Mgmt. BF (SAP) EDM GIS FM Project Mgmt. Documt.Mgmt. Integrating Information Systems CAD Workflow Identification(e.g. Bar Code) MobileComputing • design goal: minimize interfaces- combine information systems - use integrated toolsets Every Nodeis an Interface Lars Hagge: Integarted Information Management

  22. Overview • Why Do We Need Information Management? • What Do We Need? - Visions and Vocabulary • Process Analysis and Architecture Design • Demonstration Systems • Organizing Information Management • Where Are We Now? Lars Hagge: Integarted Information Management

  23. Why Do We Need Pilot Systems? • improve acceptance for project • look & feel • agree on a basis for communication • agree on terminology • evaluate the technology • gather experience (feasibility, planning, ...) • review requirements Lars Hagge: Integarted Information Management

  24. Lars Hagge: Integarted Information Management

  25. Lars Hagge: Integarted Information Management

  26. Lars Hagge: Integarted Information Management

  27. Overview • Why Do We Need Information Management? • What Do We Need? - Visions and Vocabulary • Process Analysis and Architecture Design • Demonstration Systems • Organizing Information Management • Where Are We Now? Lars Hagge: Integarted Information Management

  28. Asset Mgmt. BF (SAP) EDM GIS FM Project Mgmt. Documt.Mgmt. CAD Groupware Barcode MobileComputing Integrating Information Systems Every Nodeis a Project Lars Hagge: Integarted Information Management

  29. Asset Mgmt. BF (SAP) EDM GIS FM Project Mgmt. Documt.Mgmt. CAD Groupware ProjectPreparation Analysis Design Production System Transfer Barcode MobileComputing Every Nodeis a Project Integrating Information Systems Lars Hagge: Integarted Information Management

  30. Project RisksTiming and Acceptance • using information management • demand grows with amount of produced information • usually after users start projects • production system required before users start project • procedures (approval, publishing, ...) and conventions (naming, ...) need to be in place in the beginning • introducing information management • user participation needed for system preparation • user acceptance requires high visibility • usually only after system installation Lars Hagge: Integarted Information Management

  31. System Provider information system licensesmaintenance and support (hotline) product development and add-onsintegration modulestools for operation and maintenance SystemDeveloper ServiceGroup configuration and support (on-location)operation and maintenance information management strategysystem specification and designreference environment ScientificStaff Project Roles and Responsibilities Lars Hagge: Integarted Information Management

  32. System Provider System Provider System Provider Licenses Licenses Licenses DESY SteeringCommittee SystemDeveloper ServiceGroup ScientificStaff Project Organization Alternative 1Do-It-Yourself Lars Hagge: Integarted Information Management

  33. Know-How Add-On Products System Provider SystemDeveloper Tools ServiceGroup Services Licenses ScientificStaff References Project Organization Alternative 2Strategic Partnerships EDMSManufacturer Local ServiceProvider SteeringCommittee DESY Lars Hagge: Integarted Information Management

  34. Overview • Why Do We Need Information Management? • What Do We Need? - Visions and Vocabulary • Process Analysis and Architecture Design • Demonstration Systems • Organizing Information Management • Where Are We Now? Lars Hagge: Integarted Information Management

  35. Project Status • Engineering Data Management • Document Management operational • Requirements Specification finished • Benchmarking in March, Pilot in May • Asset Management • Test Environment operational • Facility Management • Project for creating complete digital floor plans • Requirements Specification in Progress Lars Hagge: Integarted Information Management

  36. Next Steps • extend demonstration and pilot systems • Document Management, Asset Management and EDMS benchmarking • find partners for production environment • launch standardization activities • e.g. naming conventions • e.g. workflow and processes • contribute to TESLA TDR Lars Hagge: Integarted Information Management

  37. Integrated User Interface EDM Asset Mgmt. GIS FM BF (SAP) Project Mgmt. Documt.Mgmt. Workflow Common Data Repository The Strategy Lars Hagge: Integarted Information Management

  38. Conclusion • Information Management needs more awareness in HEP • e.g. planning, modeling, visualization, simulation, construction, technical documentation, operation • Information Management imposes regulations • e.g. process definitions, naming conventions, ... • Information Management needs • to be in place before first activities start and to be available throughout entire project life-cycle • manpower and budget • together with external partners? Lars Hagge: Integarted Information Management

More Related