| Version 6 (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
Business Processes
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
The barrier to interoperability between software applications is not technology. The barrier is business processes.
Business Processes
Up till now we have been focusing on technology.
Fig 1 - Problem Space
We have lots of technology
- Excel
- Oracle and SQL Server Databases
- Java
- ...
- Commercial Mapping Software
Fig 2 - A New Approach
We need to focus on Information Modeling.
The sun will shine brighter, and God will smile on us.
[OK, so I need some help here... GPR]
Ideas
- Senior management has to agree to this
- IT folks from the business partners need to get together
Next
There are a number of issues associated with the need for interoperability, or with current attempts at interoperability. This section shows how ISO 15926 will help.
