Mandate for PCA Industry Information Semantic Architecture Special Interest Group

Purpose

  • Develop architecture
    • At logical level, with examples of possible implementation architectures
    • Including information access and governance
  • Communicate how ISO15926 and other standards are being used and interlinked
  • Ensure industry relevance

Tasks

  • Define a ”work process vs. Information Technology Architecture and Information Management Architecture” matrix
    • Spanning Engineering, Production, Operation and Maintenance.
    • Align relevant semantic technologies, models and standards
  • Design architecture supporting use cases:
    • Initially these two usecases: Handover from EPC to owner /operators. and remove / replace operation
    • Subsequently: Application interfacing, to the execution environment
    • Include relevant standards artifacts as part of architecture,
  • Provide documentation
    • Deliver as an update to OLF Reference Architecture for IO G2
  • Provide demonstrator
    • Architecturally relevant demonstrations
    • Provide a small representative model supporting use cases
    • Focus on what is practical, implementable and result-oriented

Organization

  • Key parties in the industry
    • Owner/Operators (e.g. Statoil, Woodside, NWU, Total)
    • EPC companies (e.g. Bechtel, Aker Solutions)
    • Standards representatives (e.g. PCA/ISO15926, Open O&M/MIMOSA)
    • Software vendors (e.g. IBM, Bentley, Aveva)
    • System Integrators, Analyst, Consultancies (e.g. IBM, Computas, DNV, Assetricity)
    • Educational institutions (e.g University of Oslo, University of South Australia)
    • Industry associations (e.g OLF)
  • Composition across organization categories
  • Composition across geography
  • Organize in
    • Core Team
    • Extended team
  • Align with Open O&M Operation and Maintenance SIG,
    • ref Markus Stumptner, University of South Australia (DISCUSS)
  • PCA’s staff handles administrative tasks.
  • Reporting to the PCA GM

Way of working

  • Work program to be provided
  • Work format
    • Full team (core team and extended team) meet two times per year
      • At least one face to face in conjunction with other major conference
    • Core team meet more frequently
      • and ahead of full team meetings
    • Ad-hoc working groups/projects may be established when needed
    • Collaboration through virtual and appropriate tools,
      • PCA WIKI
  • Governance
    • Comply with PCA and member general policies and practices, including Intellectual Property policies

Duration

The SIG will run until it is terminated as agreed by the Board

Home
About PCA
Reference Data Services (RDS)
RDS Operations Support
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std
Projects
Search