[[TracNav(TracNav/ISO15926Primer)]] = 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 [WikiStart#Contactpoints need a login] to post in the forum. ---- [[PageOutline(2-4,Contents,inline)]] == Abstract == The barrier to interoperablitiy between software applicaitons is not technololgy. The barrier is business processes. [Note 2008.10.27. This page has material from two pages. I will clean it us as soon as possible. GPR] ---- == Business Processes == Up till now we have been focusing on technology [TO DO: Robin Benjamin's slide "The Problem Space"] ''' Fig X - Problem Space ''' We have lots of technology Excel Oracle Databases Java Other stuff We need to focus on our Business Processes [TO DO: Robin Benjamin's slide "A New Approach"] ''' Fig Y - A New Approach''' == Doing it the ISO 15926 Way == [TO DO: diagrams on Babel Fish] [To DO: information exchange diagram with yellow dots, representing facades] == A Metaphor: We Need a Babel Fish == Remember our earlier metaphor about how ISO 15926 acts like a Babel Fish? * [wiki:ISO15926Primer_Metaphor_Babelfish ISO 15926 is like a Babel fish] We need a Babel fish to translate from one company's data sheets to those of another. [[Image(Introduction05.JPG)]] '''Figure 5: Everyone Needs a Babel fish''' Fortunately, ISO 15926 acts very much like a Babel fish. * Each company creates what is known as a ''facade'' and makes it publicly available on the Internet. * Each company maps its own database (or at any rate, those portions of its database that it wishes to publish) to the ISO 15926 standard. * Each company creates an application which can access the facades of its business partners. After that, the only question you have to ask of a supplier (or engineer, or constructor) is "What is the URL of your facade?" [[Image(Introduction06.JPG, 600px)]] '''Figure 6: The Same Project Using ISO 15926 Facades''' Using ISO 15926 Facades, these same 18 players would only need 18 facades, one each. But the best thing is that they would not have to create a new set of connections with each project. They would only have to do it once, ever. The colored lines, from each company to its facade, is all most organizations would have to do. The black lines between facades represent functions built into commercial software. ---- == A Metaphor: We Need a Babel Fish == In the Hitchiker's Guide, intergalactic travellers used a Babel fish to translate alien languages. We need a Babel fish to translate from one company's datasheets to those of another. * [wiki:ISO15926Primer_Metaphor_Babelfish ISO 15926 is like a Babelfish] [[Image(Introduction05.JPG)]] '''Figure 5: Everyone Needs a Babel fish''' Fortunatly, ISO 15926 acts very much like a Babel fish. * Each company creates what is known as a ''facade'' and makes it publicaly available on the Internet. * Each company maps its own database (or at any rate, those portions of its database that it wishes to publish) to the ISO 15926 standard. * Each company creates an application which can access the facades of its business partners. After that, the only question you have to ask of a supplier (or engineer, or constructor) is "What is the URL of your facade?" [[Image(Introduction06.JPG)]] '''Figure 6: The Same Project Using ISO 15926 Facades''' Using ISO 15926 Facades, these same 18 players would only need 18 facades, one each. But the best thing is that they would not have to create a new set of connections with each project. They would only have to do it once, ever. The colored lines, from each company to its facade, is all most organizations would have to do. The black lines between facades represents functions built into commercial software. == Next == How ISO makes life easier [wiki:ISO15926Primer_Benefits Benefits of ISO 15926] ---- [[ViewTopic([Enter forum topic])]]