1 / 13

PLCS staging area

PLCS staging area. Support for data exchange. Jochen Haenisch 2004-02-03. What is a staging area?. ... an application (and possibly a repository) to prepare data for import into and export out of a target system; to enable system interoperability.

tareq
Download Presentation

PLCS staging area

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. PLCS staging area Support for data exchange Jochen Haenisch 2004-02-03

  2. What is a staging area? • ... an application (and possibly a repository) • to prepare data for import into and export out of a target system; • to enable system interoperability. • The one for the NDLO frigate programme is called: • Product • Data • Test • Facility

  3. DEX specification defines semantics and format of the exchange data legacy B legacy C legacy D Staging area PDTF data flow may be based on proprietary specifications Staging area and DEXes legacy A Norwegian Defence Information System legacy x

  4. Role of a DEX specification • To apply business context to a generic data model. • To specify a unified data interface among software applications. • To describe formally a valid data population. By: • subsetting a given data model (AP239); • adding population constraints; • defining reference data (to reduce the valid population even more); • specifying exchange formats.

  5. These elements are the baseline of the NDLO staging area implementation. Suggested formal elements of a DEX • EXPRESS SCHEMA • to describe the subset of another schema • LOCAL and GLOBAL RULES added to the original SCHEMA • to constrain the valid population • ISO 15926 compatible reference data library • to constrain the valid population even further • ISO 10303-21 and 10303-28 • to specify file exchange formats.

  6. DEX and data translators • A data translator converts data • from the DEX format and terminology into a proprietary format and terminology (import); • or vice versa (export). • A DEX provides the requirements for what may be input to or output from a translator. • Other requirements are dictated by the legacy system and its use: • strategy for reading an input file; • what to store and where in the legacy system. Translators Translators

  7. Exchange specification - with business context - with instantiation examples - with exchange guidelines results in Rules Data model Ref. data RDL are used by Legacy source Legacy target populated exchange file dataflow Translator Translator Legacy to legacy exchange - generic view

  8. PDB/IZAR in scope out of scope out of scope Norwegian Defence Information System Staging area SAP ++ PDTF dataflow based on vendor specification Translators Translators dataflow based on PLCS DEXes Translators Translators in the NDLO pilots • A pragmatic, but visionary solution to cover today’s needs. • The more standardized components, the better.

  9. PLCS highway native application (EXPRESS based) format 5 7 2 3 4 6 1 Import Validate PLCS/DEX Convert from PLCS Validate import Merge model Validate result rules Rules Mapping Rules Mapping Rules PLCS/DEX DB native DB schema ISO15926 RDL DB reference data Example of an import translator architecture STEP P21 File populated native DB DEX specification

  10. Mapping Schema (EXPRESS-X) describes Source Schema (EXPRESS) Is mapped to Target Schema (EXPRESS) Data Converter describes describes processes Source Model (Instances) Target Model (Instances) Is mapped to Mapping architecture Target Source

  11. PDTF functionality • If DEX based data exchange: Tailoring by user • validation (against rules and reference data) - rules and ref.data • merge (with existing populations) - merge algorithms • select (for export) - • store (for a long time) - • If vendor specific data exchange: • as above - s.a. • map from/to vendor specific exchange specification - map algorithms

  12. Data Browser Reference Data System (RDS) Report layer 3 7 2 4 5 6 1 STEP P21 File Import Validate import Convert to PLCS Validate PLCS/DEX Merge/extract model Validate result Queries Rules Mapping Rules Mapping Rules data export ISO15926 RDL DB Populated PLCS DB Translator PDB DB EXPRESS basert PLCS/DEX DB PDB feedback 8 move verified data to mirror PDTF IZAR/Ferrol SAP DB ... DB STEP P21 File Populated mirror PLCS DB Translator Translator Product Data Test Facility- applied to NDLO frigate programme Product Data Test Facility User access control, system administration Data Exchange Definition Manager (DXManager) DXDeditor (Schema Manager, Process Editor) DXDexecuter

  13. The End

More Related