[[TracNav(TracNav/ISO15926HowTo)]] = Introduction to Implementing ISO 15926 = Status of this document: Working Draft This document is open for feedback, please post questions and comments in the forum at the bottom of this page. You will [WikiStart#Contactpoints need a login] to post in the forum. ---- [[PageOutline(2-4,Contents,inline)]] ---- == Entry Points == * [attachment:IDS-ADI-Resources-Introduction.ppt Introductory Slide Set] * Primer / knowledge of ISO15926 itself * Existing RDL-WIP content / sources. * The iRING Reference Data Architecture * Etc ... * [wiki:ISO15926HowTo_References Other References and Resources] * A comprehensive list of entry points and learning material == Principles of Interoperability == Before you can understand how to implement ISO 15926, you must understand a few principles. For instance, the typical computer programmer approach to interoperabitlity is to learn as much as possible from each system that is a member of the exchange in order to get the code as tight as possible, exploiting any available idiosyncracies. But this is exactly opposite to the approach of ISO 15926. The more you know about partner systems, the more inflexible your information exchange is. Instead, you need to devise an information exchange system that does not require any knowledge at all of any of the partners to the exchange. * [wiki:ISO15926HowTo_Principles Principles of Interoperability] === How to Use ISO15926 Tasks, Procedures, and Resources === * Common - independent of scenario * Specific to each scenario == Building a Business Case == Different usage scenarios, different maturity starting points. What 15926 does for you in those cases, how is 15926 use justified. (References only to background existing principles, history, model standard development projects ...) (The different scenarios are most important, because what you need to do, and what you should expect to achieve are quite different.) === Content === Your business content Your business process use of that content (relevant to the scenario) Prioritizing different kinds of content (doesn't make any sense to try to represent all of it in 15926) == Case Studies == Descriptions of implementations of ISO 15926. * [wiki:ISO15926HowTo_CaseStudy Case Studies] * Owner/Operators, by Project * Engineering, Procurement, Construction Contractors (EPC) * Software Developers * Equipment Manufacturers (OEM) == Using ISO 15926 Tools == * [wiki:ISO15926HowTo_Software_RDLFacade Using the RDL Façade] * POSC/CAESAR File and XML exchange technologies and other API's as well as iRING / OWL / SparQL Are you a developer or a user - you will have quite different needs here ? == Tutorials == * Dictionary Mapping * Practice Files * Creating a Mapping Spreadsheet * Mapping to ISO 15926-4 using the RDS/WIP * Dealing with all the class choices in the RDS/WIP * Resolving Differences with Business Partners === Mapping your content to 15926 content === (According to priorities and the compliance level appropriate to your business situation and the particular scenario) (Modelling & Templates etc only by reference as necessary - these are really under the hood - wrong to attempt to describe these in this document) ---- [[ViewTopic(ISO15926HowTo_Introduction)]]