ISO15926 Reference Data Workshop - Joint Operational Reference Data Project - PowerPoint PPT Presentation

Loading...

PPT – ISO15926 Reference Data Workshop - Joint Operational Reference Data Project PowerPoint presentation | free to download - id: 6d7ac0-NzdhZ



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

ISO15926 Reference Data Workshop - Joint Operational Reference Data Project

Description:

Title: PowerPoint Presentation Author: Ruilin Last modified by: glendinning Created Date: 10/16/2003 3:30:25 PM Document presentation format: On-screen Show – PowerPoint PPT presentation

Number of Views:106
Avg rating:3.0/5.0
Slides: 49
Provided by: Rui93
Learn more at: http://iringug.org
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: ISO15926 Reference Data Workshop - Joint Operational Reference Data Project


1
ISO15926 Reference Data Workshop - Joint
Operational Reference Data Project iRING Editor
/ Mapper Demonstrations
  • ISO15926 Reference Data Workshop March 1st,
    Digital Plant 2010
  • Ian Glendinning Information Risk Management Det
    Norsk Veritas, Oslo, Norway ian.glendinning_at_dnv.co
    m

MANAGING RISK
2
Item Start Mins Description Lead
ISO 15926 Reference Data Workshop Ian Glendinning
1 230 PM 10 Workshop Welcome, Objectives and Agenda Review Ian Glendinning
2 240 PM 10 Introductions All
3 250 PM 20 What does ISO 15926 do for you, and how does it do it? (Understanding Reference Data RDL/RDS/WIP templates Latest status.) Ian Glendinning
4 310 PM 20 Joint Operational Reference Data project Outline of agreed 2010 plan Ian Glendinning
5 330 PM 45 Joint Operational Reference Data project Stakeholder clarifications priorities. All
6 415 PM 15 Actions Commitments All
iRING Demonstration Robin Benjamins
1 430 PM 15 iRINGTools Reference Data Editor - searching and extending ISO 15926 Reference Data Lee Colson
2 445 PM 15 iRINGTools Mapping Editor mapping your data source or schema to ISO 15926 Lee Colson Rob DeCarlo
3 500 PM 30 iRING Data Exchanges Live data exchanges performed over the internet between a diverse set of applications from many different companies Robin Benjamins (moderator)
530 PM 0 Workshop Conclusion All
3
ISO15926 Ref Data Agenda
  • What does ISO15926 Reference Data do for you
    ? Recap Status
  • FIATECH PCA Joint Operational Reference
    Data Project Outline
  • Workshop on stakeholder expectations Project
    Priorities

4
  • POSC-Caesar initiated ISO15926 in 1996 and PCAs
    ongoing focus is Development, maintenance
    enhancement of ISO15926
  • Currently 35 members in 9 countries, and
    associations with other member organizations FIATE
    CH, MIMOSA, Energistics, PLCS, and more ...
  • Web site home page www.posccaesar.org
  • 6 / 7 active PCA projects in 2010 including ....
  • PCA RDL / RDS Delivery (Existing / Ongoing)
  • ISO SC4 WG Activities (Existing /
    Ongoing) Publication approval process for
    ISO15926
  • Joint Operational Reference Data (with FIATECH)
    in 2010
  • NOR-HUB (Implementation agreed in
    2010) Pre-approved shared catalogue information
    for standard equipment in the OilGas industry
    supply chain.
  • IOHN (5 year project completes in
    2012) Integrated Operations in the High-North
  • EPIM-RUF (New phase in 2010) Report User Forum
    Standard Reports for OilGas operating permits.
  • RFID RD-Item Integration (ongoing / under
    development) Radio Frequency ID Tags with RDS/WIP
    URI Links

5
6
5
4
1
2
3
7
8
9
Technology Application Independent Foundation
for Interoperability gtgtgt ISO15926
6
Interoperabilty as reducing ambiguity
  • Because we focus on doing business much
    information may be implicit or ambiguous when
    we exchange or integrate information.
  • Ambiguity when exchanging and intergrating
    information represents risk, requiring effort to
    resolve.
  • The higher the ambiguity, the higher the risk
    cost.
  • When new business uses or interfaces arise, new
    ambiguities may be significant, and the costs
    risks may be repeated.
  • Ambiguity Lifecycle Cost Risk

7
Interoperability, a major business issue.
  • In the US capital facilities industry in 2002
    alone, NIST estimated the annual cost of poor
    interoperability the cost of finding and
    verifying ( the cost risk of not finding)
    correct information for operational decision
    support at USD15.8 billion over and above
    wider health, safety and environmental risks.
  • The McGraw Hill ENR Technology for Construction
    2007 report on interoperability estimates the
    cost to be twice as much as the 2002 NIST report.
  • According to a 2008 Gartner report Legacy data
    issues (accessing and maintaining data in old
    systems and formats) are unarguably the biggest
    problem facing the process industries.
  • Repeated estimates since the mid-90s had already
    suggested that individual asset projects spend
    multi-million-USDs simply handing over
    information into the operations phase, and that
    inadequate interoperability as a whole accounts
    for 1 to 2 of capital costs.

8
Realizing Interoperability with ISO15926
  • Interoperability is a real and very large
    business problem
  • A common neutral-model or lingua-franca is a
    commonly accepted view of the solution, however
    ....
  • The lingua-franca metaphor is simple enough
    but practical execution is more than a common
    data-model a language is more than a
    dictionary ... communication is more than a
    language
  • ISO15926 is more than a dictionary, more than a
    schema . and meets the business issues directly
    and pragmatically
  • So, how does ISO15926 address interoperability ?

9
The Whole ISO15926 Elephant
Its about all of these things
Its about content vocabulary structures
Its about processes procedures
Its about technology tools
Its a wall
Its a tree
Its a spear
Its a snake
10
ISO 15926- History Evolution
1970
STEP
1980
10303-42
1986
AP227
The Web XML
AP221
1995
Usage Patterns ltgt
EPISTLE
Gellish
PCA
EPISTLE
STEPLIB
1998
PIMC / Daratech / OOF
1999
FIATECH
2000
15926-4 RDL
15926-2 Core Model
15926-7 Templates
2001
Datasets
2002
Semantic Web
2003
IDS
ADI
2004
2005
RDF/OWL
WIP (Content Services)
15926-2 Core Model
15926-7 Templates
2006
W3C PM Incubator Group
IDS-ADI
2007
2008
Parts 7....... 8 9
2009
iRING
Joint Operational RD
2010
11
FIATECH ADI (Accelerating Deployment of 15926)
Project PCA IDS (Intelligent Data Sets) Project
(both in 2006) FIATECH workshop created 17
Matrix Projects (in 2007)
12
Matrix 123 gt Proteus Project Results
XML Schema-based Dictionary-level Exchanges
  • On specification
  • On time
  • On (the vendors own) budgets

13
Matrix 8 gt Camelot Project Results
  • To build and deploy an ISO 15926 open source
    infrastructure on the internet and to show the
    following capabilities
  • The use of ISO 15926 in modeling business
    information
  • The setup, configuration, and use of publicly
    available tools to map legacy systems to ISO
    15926
  • The demonstration of several data exchange
    scenarios between several companies using ISO
    15926 over the internet
  • iRING technology delivered in the public
    domain, available for business use on May 29th
    2009.
  • .... AVALON spin off project defined services
    architecture requirements for federated RDS

14
Actual May 2009 Camelot / iRING Demo Scenario
NRX
Bentley
PlantSpace SmartPlant Material
Excel
RDS/WIP System
OpenPlant Class Editor
Brisbane
Pune
Hatch
Emerson
PID Valve, Line, In-line Instrument, and Vessel
iRING Web Service
SmartPlant Foundation
OpenPlant PowerPID
Huntsville
Intergraph
ISO 15926 Information Model
Frederick
Bechtel
iRING Web Service
Houston
RDS/WIP
Dow
SmartPlant PID
C3D
Oslo
Wilmington
Email
Athens
RDS/WIP Editor
DuPont
CCC
OpenPlant PowerPID
TCS
15
ISO 15926 The Whole Standard
  • ISO 15926 Integration of life-cycle data for
    process plants including oil and gas production
    facilities.
  • ISO - 15926 - 1 Overview and fundamentals
    (Approved IS June 2004)
  • ISO - 15926 - 2 Data model (Approved IS December
    2003)
  • ISO - 15926 - 3 Geometry (Approved TS April
    2009) (ISO - 10303 - 42 Represented in RDS/WIP
    according to Parts 2 4)
  • ISO - 15926 - 4 Initial reference data. (Approved
    TS October 2007) (RDL included in the RDS/WIP and
    extended from there according to Parts 5 6)
  • ISO - 15926 - 5 RDL Maintenance Procedures
    (Superseded by ISO-TC184/SC4 RDL Database
    procedure with 15926-specific annex issued for
    ballot January 2010)
  • ISO - 15926 - 6 Scope and methodology for
    developing additional reference data (NWI/CD
    submitted to ISO Q3 2007, planned complete in
    2010)
  • ISO - 15926 - 7 Template Implementation
    Methodology (Final TS submission December 2009)
  • ISO - 15926 - 8 OWL/RDF (W3C) Representation (TS
    submission December 2009)
  • ISO - 15926 - 9 Façade (Web Interface)
    Implementation (TS planned complete 2010)
  • ISO - 15926 - 10 Abstract Test Methods (in
    progress)
  • ISO - 15926 - (NWI-11) Simplified Industrial
    Usage (New ISO work item under development, based
    on existing industrial usage and compliance
    guidelines.)

16
ISO 15926 - Reference Data Architecture
Data Model
Standardised in ISO 15926-2
Common Terminology
Technologies
Implemented using SPARQL / Facade (Part 9)
Represented using RDF / OWL (Part 8)
Grouping Mechanism (Classes of Class etc.)
Physical Object Classes
This is 99 about Reference Data
Manufactured or Application-Specific Item Classes
R D L
My thing
17
ISO 15926 Parts Analogy
Part 2 (in RDL) Core Data Model
Natural Language Grammar (Basic rules)
Dictionary Thesaurus (Words terms, extensible
TAXONOMY)
Part 4 (RDL/WIP) Reference Data
Phrase, Sentence, Paragraph, Verse, Rhyme,
Lyric (Semantic structures, extensible ONTOLOGY)
Part 7 (in RDL/WIP) Templates
Part 8 RDF/OWL
Paper, File, Website, Stone-tablet (Representation
technology)
Part 9 Façades
Reading (Read, write, query, services
technology)
18
(No Transcript)
19
(No Transcript)
20
(No Transcript)
21
(No Transcript)
22
ISO 15926 - Reference Data Architecture
Data Model
Standardised in ISO 15926-2
Common Terminology
Grouping Mechanism (Classes of Class etc.)
Physical Object Classes
This is 99 about Reference Data
Manufactured or Application-Specific Item Classes
R D L
My thing
23
Industrial ( non-Industrial) Use
Implemented in RDF/OWL
Data Model Base Classes inc Templates
Data Model Base Classes inc Templates
ltlt Parts 2 7 Only gtgt
P3 / P4 RDL/WIP Content
Compliance of valid RDL Items constrained by
needs of industrial standardization. (Content
management hierarchies, Disciplines, SIGs, etc.)
Core Classes inc Templates
Simple technical compliance of any valid RDL
Items.
Standard Classes inc Templates
Application-Specific Classes inc Templates
Manufactured Application-Specific Classes inc
Templates
ltltltlt Unconstrained Evolution
gtgtgtgt (Any new industry / business areas / uses)
Bottom-Up Content Development
Bottom-Up Content Development
24
The Life Cycle According to IEC 61346-4
25
All objects have separate lifecycles
Identifier
18DE911A
Driving at 18DE911A
Electric Motor suitable for 18DE911A
Consolidated performance envelope
Consolidated Requirements
Model SIEMENS 1LA Variant
SIEMENS 1LA6316-4-AA64-
ZA11G50K45N90Y82
Equipment SIEMENS 1LA6316-4-AA64-
ZA11G50K45N90Y82, 123456
26
Summary so far
  • ISO15926 is in several parts.
  • Core Model, Vocabularies Structures (Taxonomy)
    and Templates (Ontology, Relations Usage
    Patterns) are all in technology-independent
    Reference Data (in RDS/WIP Content)
  • That content is available in many formats.
  • That content is structured / partitioned several
    ways.
  • Levels of abstraction from concepts to real
    individuals
  • Levels of industrial standardization
  • Whether classes / taxonomy / vocabulary of names
    (Dictionary) (physical objects, properties,
    activities, etc)
  • Or, whether ontologies / relationships / patterns
    (Templates)
  • Continuing two technical points
  • Federation
  • Templates

27
ISO 15926 At its simplest
Internet
Exchange or Communicate
map
map
use
map
contribute
RDL
Reference Data Library (RDL)
The RDS/WIP
ISO 15926
28
15926 Federated Reference Data
Logical organization of reference data
Data Model Base Classes inc Templates
Core Classes inc Templates
Standard Classes inc Templates
Manufactured Application-Specific Classes inc
Templates
29
IDs Triples / Relationships Mappings
  • IDs (URIs) are fundamental to the Reference
    Data architecture and
  • Fundamentally all mappings and all relationships
    are Triples.

ID1 (URI) Relationship ID (URI) ID2 (URI)
ltMyObjectgt (URI) MyPump101 ltis agt (Classification relationship URI) ltRDL Classgt (RDL Class URI) Centrifugal Pump
ltMy String or Symbolgt (URI) ???????????? ????? (?) ltis a name forgt (Identification relationship URI) ltRDL Classgt (RDL Class URI) Centrifugal Pump
ltMyClassgt (URI) MyCatalogueXYZPumpType ltis a subClass ofgt (Specialization relationship URI) ltRDL Classgt (RDL Class URI) Centrifugal Pump
These are indicative only. In practice these are
proto-templates in Part 7 terms (one for each
Part 2 relationship entity). Everything else is
built from these.
30
A range on the data sheet
31
Model Ambient Temperature Range
3051CG ambient temperature -40C 85C
32
ISO 15926 Property Range Template
Property Type
Input 1
Property Range
Base Property Type
UoM
Something
Input 2
Something has Property Type with Property
Range of Base Property Type defined by Input
1 and Input 2 with UoM
33
Template Signature Mapping Interface / Wizard
Template Class
Something
Property Type
Base Property Type
Property Range
UoM
Input 1
Input 2
Temp. Inst.
nnn 3051CG Ambient Temperature (Created by the system) Temperature C -40 85




A Mapping Guide already exists, to select
templates and populate their signature ...
Without ever seeing Part 2 (or even Part 7). This
is being upgraded to support an initial core set
of Templates in the RDL.
And note that the method can apply to any data
representation.
34
The Power of Templates
  • They provide a flexible and precise tool for
    ontology building for any arbitrary source
    information definition.
  • They make practical the creation of rich semantic
    structures.
  • They standardize modeling by standardizing
    templates and their selection rules.
  • With good templates and mapping guide, its easy
    to speak the language of the ontology from a
    business modelling perspective.
  • The signature is all the business domain expert
    and end user need to know.
  • Signatures and rules have technology-independent
    definitions.
  • Their rigorous defintion enables automated
    validation.
  • Templates hide complexity and guarantee
    correctness

35
Using and complying with ISO15926
  • Technically according to Parts 1 to 7. Thats it.
  • BUT ... Some business maturity aspects.
  • Limited by which reference data exists (including
    Templates) in adequately managed reference data
    libraries.
  • Limited by the gap between your existing
    technologies tools, and newer technologies
    tools that support Triples URIs (Part 8)
    directly in web interfaces (Part 9). (eg iRING)
  • Limited by your own priorities readiness to map
    the semantics of the business information sets
    that already support your existing business
    processes or your intended process improvements.

36
Dont plan to do everything all at once ! Your
expectations will be disappointed.
  • Gartner paper "Introducing the EIM Maturity
    Model" (2009) Includes these warnings for EIM
    (Enterprise Information Management) initiatives
  • The (Gartner) maturity model consists of stages,
    or levels. Organizations cannot skip stages or
    the associated activities without introducing
    weaknesses into their EIM programs, which will
    cause them to fail later on.
  • Organizations cannot implement EIM as a single
    project. Rather, it requires a gradual building
    of skills, awareness and technology. It must
    happen in iterative phases over time.

37
ISO15926 usage - maturity choices
  • Modeling Ambiguity Semantic Precision
    ? (Dictionary gtgt Short-Cut Relationships gtgt Full
    Ontology)
  • Standardization Level ? (Sandbox gtgt Company gtgt
    Community gtgt Stds Org gtgt ISO)
  • Implementation - Schema Type ? (Implicit/Tabular
    gtgt Explicit XML gtgt RDF / Gellish gtgt P8 OWL/RDF)
  • Implementation - Interface Type ? (File exchange
    gtgt API / Query gtgt P9 / SPARQL / Facade)
  • Business - Payload Scope ? (Existing RDL content
    gtgt Develop new mappings gtgt New content needed)
  • Business - Meta-data Scope Stewardship
    Capability (Identity / Version / Status Import
    / Export / Persist / Consolidate / Reconcile)

38
Distinct Compliance Levels.
  • Technical Compliance per ISO15926 Parts 1 to
    7 (Implementation Technology Independent)
  • Technology Compliance per ISO15926 Parts 8
    9 (Implementation Technology Specific - RDF/OWL
    Facades for wide federation.)
  • Business Semantic Compliance per Usage
    Guideline (NWI-11) Dictionary Level gt Short-Cut
    Level(s) gt Full Ontology Level (NWI-11 includes
    alternative implementation methods where
    appropriate including Gellish. The levels are
    working definitions based on existing compliance
    guideline, and subject to further evolution.)
  • Provide stepping stones for gradual uptake of
    skills and awareness, and iteration of success

39
iRING Technology
ISO 15926
RDS/WIP
EPC
Supplier
EPC
The iRING ISO 15926 Realtime Interoperability
Network Grid
Supplier
Job Site
Supplier
ISO 15926
Owner Operator
40
The Significance of iRING
  • iRING User Group iRING Tools (P8 OWL/RDF P9
    Facades) Technology focus, but with content in
    iRING Sandbox.
  • Important because ISO15926 needs P8 P9 for
    fully automated semantic interoperability, and
    ...
  • Because there is an iteration between content
    technologies in the evolution of both
  • Content is technology independent, BUT creating,
    managing, mapping and using existing and new
    content is easier as better tools become
    available.
  • Better tools will be developed IF developers can
    work with better content needed for business use
    and standard RDL management.

41
(No Transcript)
42
Latest News Release
PCA FIATECH Announce Joint Operational
Reference Data FOR IMMEDIATE RELEASE Austin, TX
and Oslo, Norway, February 24, 2010 POSC Caesar
Association (PCA) and FIATECH have agreed on a
single Joint Operational Reference Data project
plan to create in 2010 a stable, scalable and
commercially-viable operation of the ISO15926
reference data system and associated
services Boards of both member organizations
have already agreed funding for the front-end
phase to start in March, with a governance board
and project manager already in place. .... more
...
43
Project Announced Starting March 2010 FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation. FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation. FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation. FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation. FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation.
Project Announced Starting March 2010 Software (Systems, Tools Services) Business (Procedures Processes) Core Content (Classes Templates) New Content Scopes (Classes Templates) Ongoing RDL/RDS Operation (OPEX)
Phase E (Existing Pre-Agreement) Existing PCA RDS / mdb / xls / xml / html Existing IDS-ADI / iRING / p2/7/8/9 triple stores Existing PCA FIATECH membership project activities. Outline planning agreement. Existing PCA RDL 15926 p3/p4 content PCA extensions Existing proposed user content. Existing PCA RDL Existing PCA RDS Operational Support SLA
Phase F (Front-End Establishment) Nil Establishing PM. Planning Ph1/Ph2. Funding model. Business-case(s). Creating EL9/15926 road-map context. Nil (Only as funded by existing projects) Ongoing as existing Ongoing as existing
Phase 1 (Enhancement RFP) Minimum maintenance development of existing mixed systems tools. Agree compliance methodology. Synchronization of mixed systems. Create specification for third-party RFP. Extend Core RDL to Template Signatures Initial set consistent with methodology New Content Projects (AEX Schema) (Proteus Schema) (Budgetted and planned projects, but not part of Operational RDS/WIP project scope) Enhanced PCA SLA to support Ph1 systems, business content.
Phase 2 (New Development) Develop and migrate content to new third-party supported systems services. Place contracts for new third-party systems services. Nil (Separate funded projects) New Content Projects (AEX Schema) (Proteus Schema) (Budgetted and planned projects, but not part of Operational RDS/WIP project scope) New SLAs based on third-party RFP.
44
History of Joint Operational RD Plan
  • Avalon Challenge to PCA (Spring 09) In fact,
    many of the plan components arose from IDS-ADI
    and related project initiatives.
  • PCA Board (June 09) Created Ad-hoc RDL Team to
    recommend a plan. (Active during Aug / Sep 09)
  • Robin (lead), Petter, David, Kåre, Nils, (Ian /
    Neill liaisons)
  • FIATECH Board (Sep 09) Created 15926 / El9
    Governance team, expressed commitment and asked
    EL9 Champions to create a plan.
  • Derek, Frank, Mark, Jerry, Ric Adrian, Bruce
    (lead), Andy (Neill / Ian liasons)
  • Joint Reviews (Oct / Nov 09) plans cross
    reviewed. Agree need for a single plan as a
    2010 plan (NB already late for 2010 funding
    expectations).
  • Joint Plan Created (Dec 09)
  • Both Boards Agree (Dec 09 / Jan 10) - to the
    overall plan and PM agreements to fund Phase F.
    Prioritized deliverables for Phase F
  • Phase F Funding Contracting Governance put in
    place (Jan / Feb 10)
  • Robin, Jann, Nils, Frank, Mark, Ric (Governance)
    Ian (PM)
  • Go ... 1st Mar 2010 ...

45
The JORD Project Phase F
  • F Front-End Establishment
  • Business, Funding Governance model for ongoing
    operation.
  • Road-map for combined PCA FIATECH EL9/15926
    strategies as context for other collaborations
    developments.
  • Planning Estimating for Phases 1 2
  • Resourcing Bidding strategies for Phases 1 2
  • Reviews with Key Stakeholders.
  • Risks Mitigations.

46
Improving the interim situation
Phase 1 Fix manage legacy / hybrid
situation. Phase 2 Migrate to Avalon / iRING
architecture and retire legacy.
Enhanced per PoC / Tools Technologies IDS-ADI /
iRING / Avalon / DNV/ IOHN...
Synchronization, exceptions change management
by PCA MT Services
Maturity Usage Model Dictionary through
Short-Cuts / Gellish to Full Ontology
IDG
PCA Pt2 owl
Part8 RDF/OWL
xml
T
T
T
Minus (mdb)
Endpoint URI Service
Triple Store
tsv
Static html
Triple Store
External Content External ID Schemes
PCA Work Area Brutus DB
owl / xml / html / mdb / xls / doc content
downloads submissions
TOOLS METHODOLOGIES RDL Tools (Browser / RDE /
Mapper) RDL Content Usage Rules
Methodology Supporting Maturity Usage Model
USERS
47
The JORD Project Phase 1
  • Manage the interim endpoint improvements (above).
  • Consolidate agree compliance usage
    methodology enhance Core Template Content
    consistent with this.
  • Develop RFP(s) for enhanced systems services,
    from Avalon proposed service requirements Agreed
    business model for ongoing operational
    needs Agreed packaging per bidding strategy

48
The JORD Project Phase 2
  • IMPLEMENT and provide User Content Business
    Services
  • (Free to All) Read Licensed Use
  • (Free to All ?) New ID-Generate Licensed Use
  • (Subscription-based ?) Content-management
    validation
  • (Subscription-based ?) Support to users SIGs
  • (Fee-based ?) Non-certified proposal uploads /
    standardization proposals
  • (Fee-based ?) Certification of users and user
    tools
  • (Fee-based ?) training related consulting
  • (?) Certified-subscriber-based Write
  • (?) Voluntary tool taxes / royalties
  • IMPLEMENT Infrastructure Substrate Systems
    Services
  • Generally per AVALON requirements gtgt

49
Operational RDL/RDS Service Layers (per Avalon)
Content Realm Management
Content Realm (Common PCA / FIATECH / 15926
Interests) Common Content Management Rules
Business Domain Content Group
Business Domain Content Group
Business Domain Content Group
Content Realm (BIM)
Content Realm (other)
Content Realm (Collaborating Community
Development)
Substrate
Provider Relationships Management
Scalability Management
Service Subset Management
Software Management
Admin Management
Infrastructure
Network Access Provider
Application Hosting Provider
Content Storage Provider
Backups Provider
Operations Charging Provider
50
Avalon RD Service Organization
Organizations that require reference data hosting
(eg PCA)
Other business entities that implement the RD
Service protocols
Content Realm
Content Realm
Content Realm
Content Realms
Scale
Resources
Charges
Payment
Subtrate Operations
Subtrate Operations
Managed Service Entities
Substrate Operations
Charges
Payment
Management
Services
Service Providers
Note A substrate operations and service provider
can be the same business entity
Service Providers
Substrate Providers
Established internet service providers
51
Expectations Brainstom
  • Questions ... Suggestions ... Needs ...
  • How might you be involved user / contributor
  • in Phases 1 2 ?
  • Defining agreeing Core Templates Usage
    Methodology ?
  • Interim fixing ( iRING use) of PCA Endpoint ?
  • ...
  • In the ongoing operation ?
  • Think transition from development projects to
    operating entity
  • ...
  • What does your organization most need from
    Operational RD ?
  • Do you still need a business case - (where to
    start / think maturity) ?
  • Important vs urgent priorities (think maturity)
    ?
  • Support for particular content / schemas
    (separate projects )?
  • Strong views on the business model suggestions
    / doubts ?
  • ...

52
Project Announced Starting March 2010 FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation. FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation. FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation. FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation. FIATECH PCA Joint Operational RDS/WIP Project To establish PCA FIATECH Reference Data resources as a scalabe, and commercially sustaining operation.
Project Announced Starting March 2010 Software (Systems, Tools Services) Business (Procedures Processes) Core Content (Classes Templates) New Content Scopes (Classes Templates) Ongoing RDL/RDS Operation (OPEX)
Phase E (Existing Pre-Agreement) Existing PCA RDS / mdb / xls / xml / html Existing IDS-ADI / iRING / p2/7/8/9 triple stores Existing PCA FIATECH membership project activities. Outline planning agreement. Existing PCA RDL 15926 p3/p4 content PCA extensions Existing proposed user content. Existing PCA RDL Existing PCA RDS Operational Support SLA
Phase F (Front-End Establishment) Nil Establishing PM. Planning Ph1/Ph2. Funding model. Business-case(s). Creating EL9/15926 road-map context. Nil (Only as funded by existing projects) Ongoing as existing Ongoing as existing
Phase 1 (Enhancement RFP) Minimum maintenance development of existing mixed systems tools. Agree compliance methodology. Synchronization of mixed systems. Create specification for third-party RFP. Extend Core RDL to Template Signatures Initial set consistent with methodology New Content Projects (AEX Schema) (Proteus Schema) (Budgetted and planned projects, but not part of Operational RDS/WIP project scope) Enhanced PCA SLA to support Ph1 systems, business content.
Phase 2 (New Development) Develop and migrate content to new third-party supported systems services. Place contracts for new third-party systems services. Nil (Separate funded projects) New Content Projects (AEX Schema) (Proteus Schema) (Budgetted and planned projects, but not part of Operational RDS/WIP project scope) New SLAs based on third-party RFP.
53
Item Start Mins Description Lead
ISO 15926 Reference Data Workshop Ian Glendinning
1 230 PM 10 Workshop Welcome, Objectives and Agenda Review Ian Glendinning
2 240 PM 10 Introductions All
3 250 PM 20 What does ISO 15926 do for you, and how does it do it? (Understanding Reference Data RDL/RDS/WIP templates Latest status.) Ian Glendinning
4 310 PM 20 Joint Operational Reference Data project Outline of agreed 2010 plan Ian Glendinning
5 330 PM 45 Joint Operational Reference Data project Stakeholder clarifications priorities. All
6 415 PM 15 Actions Commitments All
iRING Demonstration Robin Benjamins
1 430 PM 15 iRINGTools Reference Data Editor - searching and extending ISO 15926 Reference Data Lee Colson
2 445 PM 15 iRINGTools Mapping Editor mapping your data source or schema to ISO 15926 Lee Colson Rob DeCarlo
3 500 PM 30 iRING Data Exchanges Live data exchanges performed over the internet between a diverse set of applications from many different companies Robin Benjamins (moderator)
530 PM 0 Workshop Conclusion All
54
(No Transcript)
About PowerShow.com