| Version 38 (modified by gordonrachar, 15 years ago) |
|---|
TracNav menu
- An Introduction to ISO 15926
-
What is ISO 15926
- How Information Exchange is Supposed to Work
- How Information Exchange Actually Works
- How Information Exchange Works with ISO 15926
- How ISO 15926 Works
- A Bit of History
- Long Tail
-
Areas of Current Work
- Norwegian Continental Shelf
- MIMOSA
- JORD
- iRING
- Development of Standards
- Educational Material
- Getting Started With ISO 15926
- Other ISO 15926 Resources
-
Introduction to ''An Introduction to ISO 15926''
- ISO 15926 is Like a Babel Fish
- ISO 15926 is Like HTML
- ISO 15926 is Like English on Your Cell Phone
- About the Author
- ISO15926Primer_DiagnosticPage
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 need a login to post in the forum.
Contents
Abstract
[Enter abstract]
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, two or three people may do one of them.
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
Map 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. Map 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. Map 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:
Here is an example of building a complete façade.
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
...
...
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.
