Data Exchange Architecture Legacy concepts EXPRESS: Business tailored sub-set of PLCS schema. RDL: Ensure unambigous interpretation of standard data Contains standard concepts for all legacy data Opens legacy data to selected partners Maps legacy and standard concepts RDL Core (standard) Standard concepts Local ref data P21/P28 Data exchange in an open business environment Legacy 2 Legacy 1 Translator 1 DEX n spec Translator 2 DEX n spec DEX – contains standard ref data only? Exceptions? Codification data Product names Descriptions DEX spesification (DEX schema) enables: Unambiguous interpretation of business concepts and data Automatic data exchange between legacy systems in an open business environment Translator may claim compliance to the business concepts and standards represented in the DEX schemas. Quality rules. PLCS Inc. (c) 2002

Data Exchange Architecture – PLCS Hub Legacy concepts EXPRESS: Business tailored sub-set of PLCS schema. Reference Data Library Maps legacy and standard concepts Core (standard) Standard concepts Local ref data Legacy systems include PLCS implementations Data exchange in an open business environment Legacy 1….N Translator 1 ….. N DEX n spec Translator X……Y P21/P28 P21/P28 Legacy X…Y PLCS Hub DEX n spec Translator functionality: Consolidation (an integrated whole) Merge (unite more than one set of data) Which are the Hub functionalities? Some could be: Passive hub (including distribute/route/switch) Intelligent hub (registration of traffic, configuration for ports). An hub application could have added functionalities: Converting P21 to P28 Merge functionality Data consolidation Receive, manage and distribute DEXs PLCS Inc. (c) 2002