Copyright, EPM Technology AS Ole Jørgen Anfindsen (COO) EPM Technology Model-based Industrial Data Management (IDM) EXPRESS Data Manager™ Connecting Engineers - Making data last longer and work harder

Copyright, EPM Technology AS The Company  EPM Technology has provided STEP (SC4) database technology since 1992 to the aerospace, automotive and defence industry.  Focus is 100% compliance to emerging industry standards and the semantics defined by product models.  One product line - the EXPRESS Data Manager™: The product is considered to be among the most functional and robust sytem for implementing SC4 standards, and has done very well in several benchmarks.  Part of IAI since permant observer to ITM since Main focus on extensions to make a standard for the entire built environment - especially IFD (taxonomy) and IFG (GIS).  References:  Singapore e-submission and e-plan check: Model server in production  UK Taylor Woodrow: model server under implementation for FM handover  Norway —Norwegian Frigate project: model server for QA and hand-over of logistics information. —BYGGSØK e-submission: model server to be implemented in 2004/2005 —AHUS Hospital - model server implementation ongoing since spring For client briefing and design - take-off for tendering and FM. —Nyttbygg - portal for contract support and document manageement - model server for object-based construction and logistics.

Copyright, EPM Technology AS IFC Model Server Architecture WorkFlow Versioning API Server-side re-usable methods CAD Model Server User Interface (PDM) IFC+IFD+IFG Used for: Resource Data Project Data Formalized Knowledge Spell Check Code Checks Other KBE Library Mgmt Model Server Work Flow Report Wizard Exchange Filters External Library (CAD) HVACElectroEnergyLogistcs Select & Report ConfigureBrowse Upload Download Validate...

Copyright, EPM Technology AS Model Server Features  Providing a single source of information  complete and consistent using a common language (IFC)  ownership and access rights to contractual information  partial data check-out and check-in (merge)  versioning  transparent access from heterogeneous applications and environments —mapping services —online clients communicating via transactions using API —offline clients communicating via web services - upload/download/execute query (methods)  information quality control —semantics defined by the standard —business rules defined by enterprises and projects  several levels of ambition are possible: —Primary version of data is still stored in proprietary file formats while the Model Server holds secondary versions of data. This is the recommended starting point. —Ultimately, data should be stored only in the Model Server and not in files at all. —It is probably necessary to move step by step from the above starting point to the ultimate goal.