[[TracNav(TracNav/ISO15926Primer)]] = Getting Started with 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 [wiki:WikiStart#Contactpoints need a login] to post in the forum. ---- [[PageOutline(2-4,Contents,inline)]] == Abstract == Of necessity, this section is a bit sparse. First, as we have noted before, ISO 15926 does not have to be completely implemented at once, so there is more than one path. As well, new tools are being developed to make implementation of the various parts easier. This section gives some guidelines, as well as some specific examples to help you pick a good introductory scope for implementing ISO 15926 at your organization. ---- The purpose of this section is to give you a roadmap for implementing ISO 15926 at your organization. Of necessity, the roadmap will not be a single direct route to a single end-point, like a route map from your travel agent showing the shortest route from your house to the beach where you plan to take your next vacation. '''Figure 1 - Shortest Route to the Beach''' Instead, this section is more like a roadmap of the country you live in showing many roads, many beaches, and in fact many good vacation spots on the way to the beach in case you don't want to go all the way the first year. This means that you can start with limited goals, or a demonstration project, to, say, map two interacting applications together using ISO 15926 part 4 (15926-4). Later on you can work up to a full 15926-7 façade. '''Figure 2 - A More Interesting Route to the Beach''' A direct route gets you there faster, but sometimes the longer route is more interesting. == ISO 15926 Roadmap == '''Figure 3 - ISO 15926 Roadmap''' ... ... ... == Getting Ready == === Read the Primer === Well, actually, you're already reading it. But in case you linked directly to this page, start at the beginning. Poke the "Primer" link in the big green box. It is important to understand that ISO 15926 is a fundamentally different approach to making machines able to talk to each other and convey meaning. In the past we've viewed machine-to-machine communication as a technology problem, building more powerful processors, or writing more artful code. But we ran into the wall of not knowing how to handle the information. ISO 15926 sidesteps the powerful chips and Machiavellian code and focuses on modeling information. === Build a Team === There are a number of roles to be filled. In theory, they can all be filled by one person. Alternatively, if the project is large enough, one role can be split between several people. '''Subject Matter Expert''' This is the person who knows what your business does. * If your organization is a refinery or petro chemical plant, it should be a process engineer, or someone who knows a great deal about all of the chemical and physical processes, and all of the equipment. * If your organization is an EPC, this person should be familiar with all of your work processes, and have an understanding of all engineering disciplines. '''Information Modeler''' This person will learn ISO 15926 methodology in information modeling, and will eventually work with your Subject Matter Expert. '''Application Configuration''' This person will need to know how to set up web services and how to create a database. '''Project Manager''' This is a typical project manager role. It will be helpful to have some prior exposure to computer programming projects. === Training === Information Modeler * ISO 15926 methodology for information modeling Applications Configurator * Set up web services * Storage for triplestores * Configuring I-Ring components Subject Matter Expert * Overview training == Deciding What to Work On == === Make a Map of Your System Landscape === You will need to know all the individual software applications your organization uses, where they get their input from, and where their output goes. Show all of the information exchanges. Your most important applications will probably already be mapped together either with custom programing or commercial middleware. Other information exchanges might be made manually with manual keyin every time, or exchange files in a neutral format, or perhaps ad hoc software. Show all of them, even if they seem to be working properly. === Choose an Information Flow to Automate === Look for an opportunity to improve an information exchange by using ISO 15926. Preferably, the entire information exchange should be within your organization, as opposed to automating an exchange with a business partner. Choose something simple to start with if you have a choice. To help you out, here are three examples of mapping to ISO 15926 Part 4: * [wiki:ISO15926Primer_GettingStarted_Automate Automate a Manual Exchange] * [wiki:ISO15926Primer_GettingStarted_Encapsulate Encapsulate an Application] * [wiki:ISO15926Primer_GettingStarted_Decouple Decouple an Application from a Confederation of Applications] Here is an example of building a complete façade. * [wiki:ISO15926PrImer_GettingStarted_iRING Build a Façade With iRING] === Gather Application Information === Dig into each application Document the schema - catalogue what's there. * Do this for the information that has to move, not necessarily everything Cover any special requirements. For instance, uncover any relationships that have to be maintained. Understand them all. === Build a Business Case === The very first line in this Primer explains why we need ISO 15926: ''So we can exchange complex plant and project information easier and cheaper.'' So if ISO 15926 actually accomplishes this, it shouldn't be too difficult to build a buisness case. Here are some ideas: * Look at your system landscape. * Which applications are linked? * What could you do differently if more of them, or all of them, were able to exchange information easily? * What does it cost your organization to maintain the existing links between applications? * Is your organization forgoing opportunities to upgrade individual applications because doing so may break links to other applications? All of these questions lead to justification to implement ISO 15926. For any pair of applications, it will always be cheaper and easier to directly map them togther using traditional means. But the maintenace and lack of flexibility will limit you. And once your organization is familiar with ISO 15926, using it to connect applications together will get significantly easier. == Getting Your Feet Wet == === Play with RDS/WIP === Understand the purpose of RDS/WIP. Look at the classes that are there Look at the types and subtypes To know how deep to model, match the legacy system. For instance, to move an instrument list you may only need the class of instruments, not every subtype. It depends on how the legacy system at each end holds them. But the legacy system at each end may not be at the same level. While one application may only use the base class, the other may you subclasses. Most of the steps will be the same as they would have been without ISO 15926, you will just be modeling the information to ISO 15926 standards. === See What Existing Models Are Available === ... ... == Execution == === Set up a Sandbox to Test === ... ... === Map Internal Applications to ISO 15926 === ... ... === Use the Ontology Browser === Use the ontology Browser to examine content to see if the mapping is correct. ... Huh? ---- [[ViewTopic(ISO15926Primer_GettingStarted)]]