ISO 18876


Published on

Presentation made to the CTO Council Information domain

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 1980’s Bruce and Matthew were involved with OIL – and continued to work with several divisions such as Marketing
    Resulted in basic methods and standards until present. Very important but may not have time to discuss today.
    1997 Kalido evolves as product and resulted finally in a software patent. We’ll show some examples.
  • <number>
  • Do not forget, data is only a record of a thing, not the thing itself.
  • <number>
    See how the standards fit in.
    There isn’t just one standard. There’s a whole family.
    ISO 10303 defines the life cycle paradigm and modelling method
    ISO 18876 is the integration standard
    ISO 15926 defines the details of things you want to share - It’s a bit like the e-GIF
    In the private sector efficiency increases are well documented - and the systems work.
    It makes integration easier, so why not give it a try?
  • <number>
    Holy Grail?
  • <number>
  • Standard data analysts’ technique
    Has multiple use of entities
    Does not help understanding by child care professionals
  • It took Bruce about 3 days work
  • <number>
  • <number>
  • <number>
  • <number>
  • <number>
    Holy Grail?
  • ISO 18876

    1. 1. Logicterm ISO Integration StandardsISO Integration Standards Private Sector TransferPrivate Sector Transfer 27th November 2008 Dr L P Anderson
    2. 2. 2Dr L P Anderson©2003-200801/29/15 Logicterm 1980s Data Management Research Shell UK Corporate Data Model HistoryHistory Internal Shell projects Kalido Commercial Release Reference data catalogues for Shell and Unilever Transaction systems for HBOS, BP, HP etc MDM UK Patent granted Kalido Flexible Data Modelling Prototypes Oil Management Data Warehouse Developing High Quality Data Models. ISO Standard For Exchange of Product Data (STEP) 2003ISO18876 ISO10303 ISO15926 Standards Work 20 years research & development20 years research & development
    3. 3. 3Dr L P Anderson©2003-200801/29/15 Logicterm Top Down ConceptsTop Down Concepts Model the World Logical Data Models Data Stores Concepts Concepts cross domainsConcepts cross domains
    4. 4. 4Dr L P Anderson©2003-200801/29/15 Logicterm Spatio-temporal paradigmSpatio-temporal paradigm Life-Cycle Events Monitoring ISO 10303 sets life cycle modelling standardsISO 10303 sets life cycle modelling standards  A “thing” exists in space and time dimensions  It has a life cycle associated with events  States are defined by events Space Time ISO 10303
    5. 5. 5Dr L P Anderson©2003-200801/29/15 Logicterm FoundationConcepts General Concepts Discipline-specificConcepts Derivedconcepts Select Relevant ConceptsSelect Relevant Concepts Application Model Application Model Mappingand translation Integration Model Subset Integration Model Subset Subset Selection Time is a non-negotiable dimensionTime is a non-negotiable dimension Thing Mass Identity Service Event Relationship Length Type Parties State Time Time Time Time Time ISO 18876 ISO 15926 ISO 10303
    6. 6. 6Dr L P Anderson©2003-200801/29/15 Logicterm RoadmapRoadmap Requirements Design Implementation Logical Data Models Data Stores Concepts Integration Model Shared Data Agree integration componentsAgree integration components Re-usable components New, map top-down Legacy, map bottom-up
    7. 7. 7Dr L P Anderson©2003-200801/29/15 Logicterm Family of standardsFamily of standards  An integration model and standard reference data can reduce interface cost by 60% - 75% (Prof Matthew West 2003)  E-GIF is like ISO 15926 Principles & Paradigms ISO 10303 Integration Model ISO 18876 Standard Reference Data ISO 15926 (4) Exchange Templates ISO 15926 (2) Templates Using standards achieves benefitsUsing standards achieves benefits
    8. 8. 8Dr L P Anderson©2003-200801/29/15 Logicterm ISO 18876ISO 18876 The International Standard for interoperability between heterogeneous systems It delivers an extensible integration model which helps to:  integrate data from different sources  share data among applications  map data with different coding structures  resolve conflict between models Can test existing integration architecturesCan test existing integration architectures
    9. 9. 9Dr L P Anderson©2003-200801/29/15 Logicterm MethodologyMethodology Modelling paradigm & principles Integration model Application Model 1 Application Model 2 Application A 1 Application A 2 Exchange mapping specifications Inputs Outputs Application A 3 Application Model 3 extension Needs excellent analysts & toolsNeeds excellent analysts & tools ISO 18876 ISO 15926 ISO 10303
    10. 10. 10Dr L P Anderson©2003-200801/29/15 Logicterm Children’s Social ServicesChildren’s Social Services Person Person Person Data Model – 58 Entities (+550 pages of description & process model)Data Model – 58 Entities (+550 pages of description & process model)
    11. 11. 11Dr L P Anderson©2003-200801/29/15 Logicterm Basic ConceptsBasic Concepts Identify “Things” and eventsIdentify “Things” and events Location: Address, school, residence, Grid ref, … Person: Child, parent, officer, doctor, volunteer, teacher, social worker … Organisation: Family, agency, department, council, external, supplier, … Time: Year, month, day, hour … Case: Event types, risk, incidents, referral, tracking, … Transaction Set: Event risk, visit, effort, cost, …
    12. 12. 12Dr L P Anderson©2003-200801/29/15 Logicterm Integration ModelIntegration Model Family Relationship Class of Relationship Type of Class of Relationship Classification by Need Take Action Location Family/Person Family Individual Employee External Person Organisation External Organisation Internal Organisation Group Organisation Document Event (Action) Case Organisation Type Class of Event Type of Event ClassRisk Responsible PartySubject of Concepts, relationships, classes, types and transactionsConcepts, relationships, classes, types and transactions
    13. 13. 13Dr L P Anderson©2003-200801/29/15 Logicterm ResultsResults Organisation (All) Action Action3 (All) Action Case3 (All) Document (All) Year (All) Quarter (All) Month (All) Day (All) Class of Event (All) Type of Class of Event (All) Risk Level Risk3 (All) Transaction Note (All) Sum of Take Action Count Action Risk3 Family / Person Low Risk Medium Risk Bill Bates 6.00 Derek Park 1.00 Fay Weller 2.00 11.00 Hazel Nutt 5.00 James Park 1.00 Lily Shoesmith 2.00 10.00 Mary Shoesmith 2.00 Mel Baxter 1.00 Nora Shoesmith 4.00 Olive Shoesmith 2.00 Park Family 3.00 Paul Wade 1.00 7.00 Peach Bates 4.00 Queenie Bates 2.00 Sally Wade 1.00 1.00 Sharon Shoesmith 2.00 2.00 Trout Family 3.00 Wade Family 4.00 POC with 5 days effortPOC with 5 days effort  Merged social care, police & health model systems  Created star schema  Consolidated risk events
    14. 14. 14Dr L P Anderson©2003-200801/29/15 Logicterm Public Sector OntologyPublic Sector Ontology Doctor Stethoscope Uses Child School Attends Public Sector Health Families Transport Travels to Child School Bus usingTravels to Person Assetuses Organisation Location Need ServiceOutcome has addressed by provided by Works for creates Applies for Patient Assessment Applies for General Practice Provided by Welfare Benefits Applicant Housing Benefit Applies for Evidence Verifies Obtains Eligibility at Applicable if Satisfied by Paul Davidson
    15. 15. 15Dr L P Anderson©2003-200801/29/15 Logicterm Application Model 2 ProcessProcess Integration Model Application Model 1 Map concepts firstMap concepts first
    16. 16. 16Dr L P Anderson©2003-200801/29/15 Logicterm DataData ExchangeExchange • Create master data and exchange templates with domain specific “ISO 15926” (e-GIF) • Move or view data via mapped relationships • Extend Integration Model at any time Application Models AM1 AM2 Integration Model Data Mapping IM AMn IM+ ISO 18876 “ISO 15926” Map data after modelingMap data after modeling
    17. 17. 17Dr L P Anderson©2003-200801/29/15 Logicterm Should it be followed up?Should it be followed up? “It’s a no brainer” - Andrew Pinder, 1st Feb 2007
    18. 18. 18Dr L P Anderson©2003-200801/29/15 Logicterm What Next?What Next? Opinion from Information & Integration Domains Leadership decision to try an ISO standard Working group for Proof of Concept  2 or 3 application domains, integration model  Test integration for MDM or data warehouse Review Pilot  Live systems Business Case Public Sector benefits from planning & efficiencyPublic Sector benefits from planning & efficiency
    19. 19. 19Dr L P Anderson©2003-200801/29/15 Logicterm HBOS Case StudyHBOS Case Study  Annual spend £1.7 billion  Desire to save £300 million from merger  Purchasing seen to have quick-win potential  Simplify supplier relationships – 32,000 of them  Negotiate price reductions  Prepare for incremental changes Transforming business requirementsTransforming business requirements Halifax Bank of Scotland HBOS Plus subsidiaries
    20. 20. 20Dr L P Anderson©2003-200801/29/15 Logicterm Starting PositionStarting Position  Different structured organisations  Different ledger and purchasing systems  Impractical to create single view of suppliers or group consolidations  Estimated many years to replace with single replacement operational system Modelling led solutionModelling led solution + +++ =
    21. 21. 21Dr L P Anderson©2003-200801/29/15 Logicterm Speed of DeliverySpeed of Delivery  Staff in five different locations all see the same information  Group-wide commodity structure, consolidating and re-ordering 17,000 account codes into 27 commodities across 142 categories Incremental integration within one yearIncremental integration within one year Project Start Feb 2002 May 2002 Phase 1 Quick Wins, eg Stationery Jan 2003 Phase 2 Complex requirements eg fleet management, holistic views
    22. 22. 22Dr L P Anderson©2003-200801/29/15 Logicterm BenefitsBenefits  Improved contract negotiation - new and existing  Identified cost savings initiatives  Prioritised time on “influenceable spend”  Reduced the time spent by users and buyers  Increased collaboration across business units  Streamlined efficiency of business processes  Tracked compliance with group contracts All contribute to bottom line performanceAll contribute to bottom line performance
    23. 23. 23Dr L P Anderson©2003-200801/29/15 Logicterm  96% percent of 150 companies polled are running E-supply management systems but only an average 11% of their cost base. The main problem cited was a lack of integration with existing procurement systems. (AT Kearney)  We wanted a safe, lower-cost incremental solution, the system has already cut staff time spent on procurement, reduced wastage by 25 percent at a saving of around €500,000 a year, and clipped purchase costs on stationery and the like by at least 2 percent. (Taylor, HBOS) Some quotesSome quotes Key words are integration and incrementalKey words are integration and incremental