Synchronize work on DEXs and reference data between PLCS pilots and OASISPLCS

1

• Synchronize work on DEXs and reference data
  between PLCS pilots and OASIS/PLCS
• - Proposed PLCS TC Organization and Functional
  Responsibilities

2
PLCS TC Organization Membership
ChairSecretariat1 Voting Member per
CompanyTechnical LeadImplementers Forum Lead
1 Secretariat
LeadSoftware Product VendorsImplementersIntegra
tors
Norwegian PilotUK MOD PilotSwedish PilotOthers
Lead (Information Architect)2 Tool Experts2
Business Experts
DEX Development Teams (min) 1 Team Lead1
Modeler1 Business Expert
Infrastructure/Tool Team (min) Information
Architect1 Modeler
3
Organization Functionality OASIS TC

• Issue AP239 as an IS (function of PLCS, Inc. and
  SC4)
• Agree resolution of DIS ballot comments
• Prepare resolution programme
• Implement change programme
• Submit to ISO for publication
• Issue as IS

4
Organization Functionality OASIS TC

• Formalise OASIS Role
• Agreed programme of work
• Agreed allocation of programme tasks
• Rules for approval of methods
• Agreed DEX development processes
• Agreed Reference Data processes
• Establish resource requirement
• Establishment of an Implementation Plan
• Agree process for review / ballot / update /
  maintenance of ref data
• Infrastructure of RDL Server
• Infrastructure of Dexlib publication environment
• Establish API for PLCS

5
Organization Functionality OASIS TC

• Administration, provision of development tool,
  ballot and publishing activities
• Establish and maintain a detailed project plan
• Produce a DEX development programme
• Manage activities described in the project plan
• recommended activities and
• identified actions relevant for the OASIS TC
  scope
• Administration of DEXs,capabilities, reference
  data, documentation tool, publishing
• Procedures for publishing
• Establish how the DEXs are to be published. I.e.
  what format.
• Establish how to publish Reference data
• Publish OWL files
• Set up OWL files on Web server (Coordinate with
  Tech Lead)
• Agree to publish
• Publish DEXs as OASIS standard
• Core PLCS Reference Data
• Identify Business domain extensions that will be
  published standardized extensions to PLCS
  Reference Data

6
Organization Functionality OASIS TC

• Administration, provision of development tool,
  ballot and publishing activities (contd)
• Publishing
• DEX Publication
• Extend DEXlib to allow HTML publications
• Extend DEXlib to allow individual or sets of DEXs
  to be published as a standalone package.
• Agree how DEXs are published XML Schema?
• RDL publication
• Establish PLCS web server
• Publish OWL files on PLCS web server
• Establish PLCS RDL server accessed via APIs from
  translators

7
Organization Functionality OASIS TC

• Administration, provision of development tool,
  ballot and publishing activities (contd)
• Technical publishing
• DEX Publication
• Extend DEXlib to allow HTML publications
• Extend DEXlib to allow individual or sets of DEXs
  to be published as a standalone package.
• RDL publication
• Establish PLCS web server
• Publish OWL files on PLCS web server
• Establish PLCS RDL server accessed via APIs from
  translators
• Reference data specify process for handling
• Review
• Ballot
• Update

8
Organization Functionality OASIS TC

• Administration, provision of development tool,
  ballot and publishing activities (contd)
• Review DEXs submitted for standardization
• Ballot activities
• Responsible for ballot routines, balloting,
  publishing and regular reporting to OASIS members
  (Tool expert with modeling competence)
• Establish and maintain guidelines for
• Reference data
• DEX and capability (DEX Cookbook)
• Testing (Test document)
• Mapping (UK MODs mapping document)

9
Organization Functionality OASIS TC

• Administration, provision of development tool,
  ballot and publishing activities (contd)
• Maintain infrastructure as exploder, home page,
  reference data server, DEXLib tool etc.
• Developing, Publishing and maintain DEXs,
  Capabilities, Reference data, Guidelines
• Communication with Implementers forum, projects
  and pilots (Business expert)
• Meetings and conference calls
• Identify potential future DEXs

10
Organization Functionality Technical

• Establish agreements for documentation of
  capabilities and business concepts
• Develop a data exchange template
• A "data exchange contract" shall require
• Identification of the specific DEX(es) that shall
  exchange the business data to enable
  conformance testing
• Identification of standards used, and the
  resulting usage of reference data
• Involved parties need to agree what is their
  recognized identifier. A text shall be added in
  the exchange agreement to note the preferred
  option as the one to be used for globally unique
  identifiers, e.g. for identifiers that may be
  used for data merge.
• Agree a common development method for DEXs
  (outcome of DEX Synchronisation meetings)
• Agree common content for DEXs (outcome of DEX
  Synchronisation meetings)
• Develop business ontology
• Business ontology in PLCS OWL shall be developed
  from business needs, not on legacy (systems and
  standards)
• Establish and standardize one complete, stable
  ontology for PLCS shall be a long term objective
• For the short term, harmonization of the Def Stan
  00-60 based ontology currently uploaded to PLCS
  OWL is recommended

11
Organization Functionality Technical

• Establish agreements for documentation of
  capabilities and business concepts
• Reference Data Library
• Class of class definitions in PLCS/OASIS RDL may
  be needed for contracting purposes. How to
  define class of class in OWL shall be
  investigated
• Separate OWL project files shall be defined for
  representation of specific projects and their
  local terms
• Assessment of DEXs, capabilities and reference
  data to avoid competitive DEXs to existing ones
  (Business expert)
• Develop and Maintain guidelines
• Develop guidelines for developing capabilities
• Develop mapping guidelines
• Develop guidelines for creating business domain
  extensions to the reference data library
• Develop Translator Guidance
• Translators shall be developed according to
  agreed data exchange architecture
• Translators may claim compliance to a DEX, if
  need be, with exemptions for import or export
• Develop Usage Guidance for business
  implementation
• Modeller / Developer guidance
• Business user guidance
• Software implementer guidance
• Contract managers guidance

12
Organization Functionality Technical

• Technical - Capabilities
• Develop new capabilities as required
• Incorporate new Ref Data
• Enable representation of instantiation
  capabilities
• Set up a review structure for capabilities
• Technical - Ref Data
• Consolidate existing Ref Data files to establish
  baseline core
• Establish a better development environment for
  consolidation and management
• Technical - DEXs
• Develop an exchange agreement (specialisation of
  DEX)
• Enable specialisation pruning of DEXs
• Provide a mechanism for converting existing part
  28 file to part 21 (OASIS TC meeting 11 action
  item 4)
• Technical - Publication
• Continue to maintain Dexlib on Source Forge
• Maintain an HTML mirror of DEXLib for non
  developers
• Allow an XML view facility in browsers (other
  than I Explorer)
• Extend Dexlib to allow TML publications
• Extend Dexlib to allow individual (or sets of)
  DEXs to be published as a standalone package
  electronically and on paper
• Establish a PLCS web server

13
Organization Functionality Technical

• Develop DEX Packages
• Develop Dexlib Documentation
• Develop a documentation infrastructure
• Develop the Dexlib architecture and a framework
  explanation
• Develop Implementation options
• Business concepts
• Capabilities
• Reference data
• DEX Documentation
• Prune of long forms
• Develop Rules
• Rule types that are needed for DEXs and
  capabilities shall be developed
• Establish templates needed for each rule type
• Templates shall be used for scripts as required
• Scripts to be activated and completed with data
• Rules shall be uniquely enumerated (in
  capabilities etc) to allow normative reference to
  them
• Rules shall be placed at the lowest possible
  level, i.e. in capabilities, without mandating
  PLCS global rules. Experience will show where the
  lowest level is.

DEX Development Team
14
Organization Functionality Technical
DEX Development Team

• Develop DEX Packages
• Develop DEXs for business implementation
• Develop a core capability set
• Develop a DEX template (OASIS TC meeting 11
  action item 2)
• Agree a common usage guidance method for DEXs
• Specify a representation of a thesaurus of
  business concepts reflecting business terms
• Specify an indexing mechanism from the Business
  concepts to DEX capabilities
• Re-develop initial set of DEXs i.a.w. common
  agreements
• Incorporate the recommendations from the series
  of DEX Sync Workshops

15
Organization Functionality Technical
DEX Development Team

• Develop Reference Data for DEX implementation
• Agree how Reference Data is to be published as a
  standard and how it will be maintained
• Define reference data architecture
• Develop pilot RDL service
• Agree and standardised RDL services
• Develop industrial strength RDL services
• Define management of RDL services
• Populate RDL services
• Propose reference data from pilot sources
• Instantiate reference data
• Link with other standards
• Develop a standard publication mechanism
• Submit Reference Data for ballot
• Develop a programme to monitor the resolution of
  ballot comments
• Publish Reference Data as standard (OASIS TC
  meeting 11 action item 7)
• Input recommendations from the synchronisation
  workshops

16
Organization Functionality Technical
DEX Development Team

• Harmonisation with SC4 standards
• 10303 STEP APs
• 13584 PLIB
• 15926 Oil Gas
• Harmonisation with other standards
• 00-60
• SCORM (OASIS TC meeting 11 action item 6)
• 1000D
• 2000M
• OAGIS 9
• W3C
• OMG
• MIP
• SIMBASE

17
Organization Functionality Technical
DEX Development Team

• Generic capabilities shall be tailored to
  specific business domains and business concepts
• Documentation of capabilities and business
  concepts shall be documented according to
  agreements

18
Organization Functionality Technical

• DEXLib Infrastructure
• Enhance user friendliness
• Indexing mechanism
• User-friendly interface to reference data library
  from DEXLib
• Graphical representation of reference data
  hierarchy HTML version
• Expand the introduction to DEXLib. Shall include
  information as
• Data exchange architecture
• Reference data
• Global identifiers
• Rules
• Develop templates for main rule types
• Develop scripts for business concepts, using rule
  templates
• Extend existing DEXLib functionality to activate
  and complete scripts with information
• Develop template for exchange agreements as part
  of each specific DEX
• Graphical presentation of information in DEXLib
  shall be considered

19
Organization Functionality Technical

• DEXLib tools
• Develop tool supporting DEX, Capability and
  Reference Data development
• Responsible for maintaining DEXLib tools and
  reference data server (Tool expert with modeling
  competence)
• Developed to encompass the revised DEX
  architecture containing
• business concepts
• specializations of generic capabilities
• specialization of generic DEXs
• rules
• Extend DEXlib tool set
• User friendly front end
• Develop terminology dictionary
• Develop indexing method from terminology
  dictionary to DEXlib
• Interface to reference data
• Allow publication of DEXs
• Allow publication of Reference Data

20
Organization Functionality Technical

• DEXLib content revised according to new
  architecture
• DEX specification template
• Develop an agreed DEX template for acceptance by
  OASIS based on the example DEX Assembly part
  list to DEXLib
• Agreed model interpretations shall be
  incorporated in DEXLib and existing translators

21
Organization Functionality Implementers Forum

• Establish Implementers Forum
• Define test data
• Develop test tools
• Run test rallies
• Define Conformance requirements
• Establish implementers forum
• Establish tools to develop / view the test data
• Establish tools to validate the test results
• Harmonization and reuse of solutions
• Establish guidelines for the implementers
• Harmonization of
• Reference data
• Interpretations / mapping solutions
• Modify / Review
• DEXs
• Capabilities
• Business concepts
• Reference data

22
Organization Functionality Implementers Forum

• Test DEXs
• Test DEXs
• Test interoperability by round robin test
  rallies
• Identify test sets
• Conduct test rallies
• Run Pilot projects for assurance of AP239
• Identify pilot business areas
• Modify DEXs based on pilot input
• Review Framework for quality (OASIS TC meeting 11
  action item 4)
• Develop a method for viewing test data (OASIS TC
  meeting 11 action item 5)
• Submit DEXs, capabilities and reference data to
  OASIS for standardization

23
Organization Functionality Pilots/Projects

• Activities performed by PLCS pilots and projects
• Development and review activities
• DEXs
• Capabilities
• Reference data
• Submit DEXs, capabilities and reference data to
  Implementers forum
• Update of capabilities shall be performed in
  relation to projects/pilots and not as part of
  the OASIS TC work
• Share results of pilots

24
Finally, the END!