JORD. Joint Operational Reference Data Project enhancing the PCA Reference Data Service (RDS) Operation in partnership with FIATECH

Transcription

1 JORD Joint Operational Reference Data Project enhancing the PCA Reference Data Service (RDS) Operation in partnership with FIATECH Delivering the authoritative core of iring. Ian Glendinning / Tore Christiansen / Lillian Hella POSC Caesar Association Interoperability Semantic Days Stavanger - 30 th May 2013

2 Agenda + ISO PCA, Fiatech, iring, JORD Context ISO / iring / RDS Basics JORD Objectives and Project Scoping / Phasing Successful deliveries achieved so far Current status and work in progress Conclusions & Engagement with JORD & PCA RDS

3 Primary focus on ISO15926 & Reference Data since 1996 Developing PCA RDL (Library) and Operating PCA RDS (System) throughout this period, with Operational PCA RDS (System & Services) since 2008 Involving many collaborations.

4 PCA & Fiatech Element 9 & Members Collaboration on ISO / Wilmington / 2007 / 2008 / 2009 ADI, IDS-ADI, Matrix Projects, Camelot, Avalon, Proteus, iringtools Created major challenge to PCA RDS (and PCA s own projects), which JORD was created to address: All Reference Data supported as resolvable / queryable web references (EndPoint). Quality manageable and scalable content and services. (inc. reduced dependence on scarce expert resources.) Clarity on compliance and validation of usage. Sustainable value-adding services business model

5 JORD Joint Operational Reference Data Project (since May 2011) enhancing the PCA Reference Data Service (RDS) Operation in partnership with Fiatech delivering scalable, sustainable, authoritative, core, operational ISO15926 Reference Data and Compliance needs. Further agreed (October 2012 press release) All PCA & Fiatech ISO15926 industry interoperability activities Endorse the common iring branding : And the common communication channel : iringtoday.com

6 Interface Interface + ISO ISO15926 at its simplest Internet map Interoperate map Organization, Business Unit, Application A RDL Organization, Business Unit, Application B Using standard shared definitions & sharing references used, reduces business ambiguity & reduces mapping overheads. Makes interoperability easier and reduces risk & cost

7 Reducing ambiguity and reducing mapping overheads Makes interoperability easier and reduces risk & cost Direct-cost-and-time-savings in reducing effort in transferring & mapping data across business interfaces and in simply finding & accessing information necessary to do your business. Risk-and-cost-reductions in the quality and ambiguity of information which otherwise lead to sub-optimal business operations, failure to satisfy regulators or, in the worst case, loss of health, safety & environmental integrity. Agility & flexibility to take advantage of platform-independent, technology-neutral, collaborative business processes, flexible business partnering, and different subcontracting arrangements across your geographically distributed, even remote & inhospitable, evolving business operations and supply-chains. Know your own specific business case & scope priorities

8 ISO15926 Ontology + ISO map Internet Interoperate map RDL PRIVATE RD SHARED RD PCA / JORD ISO RD Architecturally Peer-to-Peer (Internet Federation) ASSET PROJECT JORD enhanced PCA RDS in partnership with FIATECH

9 ISO15926 Ontology + ISO map Interoperate map RDL PRIVATE RD SHARED RD PCA / JORD ISO RD Architecturally Peer-to-Peer (Internet Federation) ASSET PROJECT JORD enhanced PCA RDS in partnership with FIATECH

10 EPC s ISO RDS Suppliers Regulators Job Site Solutions & Services New Mobile Opportunities ISO Operating Facilities Catalogues Owner Operators

11 JORD Project Scoping A - Compliance, Validation & Methodology Tore Christansen B - Services Platform & Publishing Tools Lillian Hella C - Training Resources Ian Glendinning D - Services Organization & Business Resources Ian Glendinning (O Contribution to Operational Support) (P Project Admin) JORD Project Phasing Phase 1 Technical Enhancements & Fixes (May 2011 to July 2012) (Fixes - known issues, known solutions, known resources) Phase 2 Scalable Platform & Organization (Up to June 2014) Phase 3 Sustainable Business Services Operation (Thereafter)

12 The Deliverable Enhanced PCA RDS. Scalable & Sustainable Business Operation Really about credibility, dependability, value & easier business use. Focussing on the authoritative core of the federated whole. Not attempting direct management control of all reference data for every industrial use. (Think very large elephant ) Having a business model and funding for self-sustaining operation. Infrastructure for 24x7x365 operation & growing, federated content, Organization & governance model for long-term viability, Critical paths not dependent on a few specialists, etc. Professional business arrangements on which industrial users can rely for value-adding services:

13 JORD Core Services Read / Export Content Core Content Mgmt & Validation Support for Users, Projects & SIG's Create / Read / Export new ID's Content Write New Content & Standardization Certification of Users, Org's, Tools & Interfaces Training & Related Consulting + ISO Free to anyone. Available to charter Project Subscribers & Sponsors & to Fee-paying service users. Available to charter Project Subscribers & Sponsors & to Fee-paying service users. (who are also Certified) Available as fee-paying value-adding services. (Per project / per scope.) Primary Service. All references resolvable to immutably-unique content, all readable, exportable. Supported formats include Browser UI, MDB, SQL, Excel, HTML, XML and RDF/OWL/SPARQL. Copyright & IPR licensing apply. Maintenance and fixes of core content only and testing of proposed changes, etc. (for new domain content, see below). Service Band Services Support Free & Open Services Basic Read & Query Subscription Services Fee-based Valueadding Services Functioning Uptime Support only - for Registered Users Maintenance of core procedures and support requests concerning use of core content and processes (For new content processing, see below.) Registered users to the management services are free to generate new lifecycleimmutable Global ID's for content in locally or remotely managed WIP Libraries / Sandboxes, etc. General service, Certified users will be able to write content technical directly (with help appropriate & meta-data controls on provenance & quality) Partitions of federated WIP /Sandbox content become effectively hosted and publicly accessible. content usage Q&A Estimated cost per value-added scope - Price list / rates intended. Will arise from both Commercial Projects and Collaborative "SIG's". Extended Read with Valueadding Queries & Views All other update, content management, compliance validation, standardization, training & consulting services Specific SLA s per Estimated cost per value-added scope - Price list / rates intended. Organized around Compliance Checklist with priced scopes service. per BIDG or other transaction sets. (Economic self-certifying components, as well as services.) Estimated cost per scope - Price list / rates development possible. (Note that these are services related only to providing and using the core RDS Operations content and procedures. Additional services are supported by commercial consultants in content creation, interoperation and integration solution planning and implementation.) Plus, operational services, business, marketing and back-office functions supporting core services. (Other than core technical & coordination functions infrastructure and substrate technologies & specialist services are competitively outsourced.)

14 Procedure / Process View Taken from Methodology Note: Targeted at business domain (SME) experts (Pipe-stressing analogy designer / expert / guru division of labour.) Objective is to achieve defined levels of compliant mapping by selection & population of TSP s & TIP s (Template Signature Patterns). Expansion of the decision-tree (20 Questions analogy) & repeating the loop.

15 TSP Usage Patterns to TIP Delivering the scalable Reference Data Services (RDS) JORD Project PCA RDS JORD Mapping Methodology Specification (Courtesy of Robin Benjamins of Bechtel) ISO Usage Patterns Template Signature Pattern Fiatech IIP Project PCA Delivering consensus on RDL usage TSP /tsp TSP /tsp TSP /tsp TSP /tsp TSP /tsp TSP /tsp TSP /tsp TIP /tip TSP /tsp TSP /tsp TSP /tsp TIP /tip TSP /tsp Specializations and Assembly TSP /tsp TSP /tsp TIP /tip Template Information Pattern Business Requirements Business Requirements Business Requirements 16

16 JORD PCA RDS achievements to May 2013 Achieved interim production PCA RDS EndPoint (and being used) Commercially hosted and managed independently by PCA. Interim development & staging (update & change management) - capability. Initial content validation querying and update process. Sandbox hosting service provided (and being used). (Scalable full production management tools spec and activities now in progress) Spec for URI s Namespaces and immutable ID s with RDF implementation. Compliance Specification & Mapping Methodology for business RDL usage with TSP s & TIP s. (With good consensus in MMT SIG, P8WG & IIP Project) (TSP/TIP Pattern documentation and RDL updates now in progress, business interface validation to come in 2013/14) Business development & marketing consultant contracted to PCA. iringtoday channel contracted to PCA for business communication. Refresh of iringtoday content & format ready for ongoing communications. Future service description & pricing framework proposed

17 Ongoing scopes of work. Scope A - Compliance, Validation & Methodology Project Lead Tore Christiansen Scope B Services Platform & Publishing Tools Project Lead Lillian Hella. Scope C Training Resources, & Scope D Services Organization & Business Resources. and round-off / conclusions / engagement suggestions.)

18 2011/12 A: Compliance, Validation & Methodology A1 - Compliance Specification Issued Customers using checklist to assess their own compliance, Validation Procedures are in Phase 2 A2 - Mapping Methodology Issued MMT SIG agreement achieved Attention now shifts to implementing actual TSP s

19 2013/14 A: Compliance, Validation & Methodology A3 - Indexing and Documenting the TSP s Deliverable: Agreed Index of Patterns, each with documentation defined by the Methodology A4 - Content Fixes & Enhancements Deliverable: Quality assured enhancements in the published library. A5 - Compliance Validation Procedures A5.1 - Validation Procedures for RDL Content. Deliverable: Agreed enhancements to existing procedure(s). A5.2 - Validation Procedure(s) for Business Interface Compliance. Deliverable: Agreed new procedure(s)

20 Car Example + ISO Classification Specialisation Entity Type class_of_class_of_ individual + class_of_class_of_ relationship + class_of_class_of_ individual + Relationship Class (of class)- Level 2 SAAB car type SAAB car types have SAAB engine types SAAB engine type Class (of individual) - Level 1 SAAB 900 class_of_individual + class_of_relationship + class_of_individual + SAAB 900 have SAAB V Turbo engines SAAB B V Turbo engine possible _individual + relationship + possible _individual + Individual - Level 0 BN #

21 24 + ISO Template Interface Classification Specialisation Entity Type Relationship class_of_class_of_ individual + class_of_class_of_ relationship + class_of_class_of_ individual + Class (of class)- Level 2 SAAB car type SAAB car types have SAAB engine types SAAB engine type Class (of individual) - Level 1 SAAB 900 class_of_individual + class_of_relationship + class_of_individual + SAAB 900 have SAAB V Turbo engines SAAB B V Turbo engine possible _individual + relationship + possible _individual + Individual - Level 0 BN #

22 Template Signature Template Name Role 1 Role 2 Role 3 SAAB Engine Type SAAB ID Engine ID Has Engine Type BN # SAAB 900 Have V Part 7 SAAB 900 have SAAB V Turbo engines BN #

23 How to Model A Pump s Area #Unit2A #P-101 string that represents Unit 2A 29

24 Part 2 Representation: Arrangement Of Individual Part 7 Relationship Template Template Name Role 1 Role 2 Role 3 Arrangement Of Individual Has Whole Has Part Has Arrangement Type 30

25 Part 2 Representation: Classified Identification Of Individual Part 7 Property Template Template Name Role 1 Role 2 Role 3 Classified Identification Of Individual Has Identified Val Identifier Has Identification Type 31

26 Tranche 3 The Rest of P2 and P7 Ontologies Tranche 2 Properties, Composition & Information Short-Cuts Tranche 1 Registration A3: TSP s The Index of Template Pattern Signatures (TSP s) Taken from Mapping Methodology Group Registration Attributes Composition Short-Cut General Short-Cuts (CoRwS) Information Connection Location Containment Business Meta-Data Processes & Activities (More) Pattern Name Registration Identification Designation (Human Name) Classification Specialization PhysicalProperty MaterialOfConstruction NominalProperty Shape / Size as Design Pattern Shape / Size as Geometry & Dimensions Assembly Collection Short-Cut Relation Manufacturer Supplier About Meta-About Description Definition Direct Indirect Location by Position in Context Location by Coordinates Containment (More) (More) Functions & Roles Involvement (non-specific) Fulfilment (of specific roles) Events / Starts / Ends

27 2011/12 B: Services Platform & Publishing Tools B1.1.2 Triple store endpoint V2 Live, being used & supported on commercial ISP/Host B1.2 - ID Specification Issued (and subject to refinement) B1.3 - Sandbox Hosting Capability Live, being used & supported

28 2013/14 B: Services Platform & Publishing Tools B1 Platform infrastructure and substrate B1.4 Production implementation of platform and storage B2 RDL Expert Manager Tool B2.1 Interim Production Enhancements B2.2 Fully Functional and Supportable Capability B3 RDL User Domain Expert Tool B3.1 Requirements Gathering B3.2 Tool Prototype B3.3 Production Tool B4 Other Tools B4.1 RDL Content Validation B4.2 Business Interface Compliance Validation B4.3 Business Substrate Applications

29 JORD Interim Editing Environment ISO Expert Create Modify Delete Semantic Technology Expert RDL Library Responsible Editor RDF.OWL Port 3037 Port 3032 SparQL update: Insert/Change/Delete Data Development Triple store Sandbox2 Triple store EqHub Triple store RDF/OWL (XML.TTL) Fuseki:RDFload Port 3036 RDS System Responsible SparQL update: Insert/Change/ Delete Data Staging Triple store RDF/OWL (XML.TTL) Fuseki:RDFload End User iring Triple store Port 3030 SparQL query: View Data Endpoint Triple store Editing environment Development environment Staging environment Production environment

30

31 Work Processes for PCA Reference Data System RDL/RDS procedures RDL/RDS procedures RDL/RDS procedures Cls and Rels Input Files 1. Load new files Cls and Rels from Dev Triplestore TTL file w. CLS and REL from Dev. 2. Insert new items Cls and Rels from Staging Triplestore TTL file w. CLS and REL from Stage 3. Insert new items Cls and Rels from Prod. Triplestore TTL file w. CLS and REL from Prod. Development Endpoint Staging Endpoint Production Endpoint SwiftLoad SwiftInsert Dump File Upload SPARQL Update SPARQL Query SwiftInsert Dump SPARQL Update SPARQL Query SwiftInsert SPARQL Query List of scripts Front page

32 1. Work Process for Inserting Classes in the PCA Reference Data System Local Desktop or Laptop Prepare Excel file.doc Create CSV file.doc Create TTL file.doc Prepare TTL file.doc Input Class.xls 1. Prepare Excel File Insert Class.xls 2. Create CSV file Insert Class.csv 3. Produce TTL file Input Class.ttl 4. Add namespaces to TTL file Insert Class.ttl Excel Template Excel CSV format Export.groovy Name spaces Server with Triplestore endpoint Copy TTL file to Server.doc Load Classes in triplestore.doc Insert Class.ttl 5. Copy TTL file to Server Insert Class.ttl 6. Load Classes in Triplestore Classes in Triplestore To Insert Relations Copy script sh swiftload.sh Development Endpoint Staging Endpoint Production Endpoint Main process

33

34

35

36 Ongoing Operations Exploiting Independent Endpoint & Sandbox Capabilities: Supporting the V2 Endpoint in production ( ) Hosting Customer Sandboxes Establishing Interim platform and tool enhancements using PCA Development & Staging Sandboxes and LinkedData forms Establishing practical implementation consequences of ID Spec & Conventions and actual OWL / RDF / Triple Representations

37 2013/14 Scope to Complete #C Scope C Training Resources C1 - General iring Approach to Achieving Interoperability (Taking existing Primer scope and inventory of existing materials, and aligning with JORD-enhanced terminology, methods, procedures and PCA RDS capabilities.) C2 How to develop iring Interoperability Business Cases C3 Technical Training in Specific Aspects of ISO15926 (Including Part 2 Model, Part 4 Reference Data, Part 7 Templates, Parts 8&9 RDF/OWL and SPARQL technologies, etc.) C4 User Training in use of Specific PCA RDS Operations Tools, Methods & Procedures (Including Mapping Methodology, RDL Domain Expert User Tool(s), Interface Compliance Validation Procedures, RDL Expert Manager Tool(s), Content Validation Procedures, etc.)

38 2013/14 Scope to Complete #D Scope D - Services Organization & Business Resources D1 Marketing and securing JORD Project Funding (Scheduling being based on current committed funding and priorities but full scope estimates still indicate only ~60% funded) D2 Business Strategy incl. Marketing Strategy & Business Plans (Taking pre-project outlines and developing definitive strategy and plans) D3 Service Descriptions, Pricing Plan, SLA s and T s&c s D4 PCA RDS Operations Marketing Materials & Campaigns (The iringtoday.com channel, and specific business use-cases, business case for increasing compliance, etc.) D5 Staff Resourcing & Subcontracting Plan (Both human and procedural / organizational resources.) D6 Service Sales & Delivery Resources (Maximising use of business substrate element of Avalon architecture.)

39 You need the JORD Project You need the benefits of iring - ISO15926 Reference-Data-Based Interoperability. You need the core JORD deliverables and service enhancements. We all need the authoritative & coordinated clarity on the status of all other iring (ISO15926) resources. so the JORD Project also needs you JORD still requires additional funding and resources to deliver the remaining Phase 2 scope (including operational support). With thanks and acknowledgements to Charter Members: Sponsors - EPIM, RosEnergoAtom, Black&Veatch, CCC, Hatch & VNIIAES; - Supplementary Subscribers Woodside, Dow, Bechtel & Emerson More information - Ian Glendinning / Programme Coordinator- ian@glencois.com Nils Sandsmark / PCA nils.sandsmark@posccaesar.org Ray Topping / FIATECH topping@fiatech.com