1. ISO 10303-239 edition 2 Publication plan R. Bodington Eurostep Limited ISO 10303-239 edition 2

2. Project Objective  Deliver update edition of ISO 10303-239 Motivation  Incorporate required changes identified from PLCS deployments  Ensure compatibility with ISO 10303 AP233, AP203e2  Include additional AP203/233 modules within the original scope Governance  The project is managed by OASIS PLCS TOG  Consensus via OASIS PLCS TC and SC4 Contributors  UK MoD, Norwegian NDLO sponsored  Eurostep lead  SAAB, DNV, FMV, LSC, EPM, BAE Systems, LK Soft

3. Status Draft International Standard Ballot  Ballot Start date 2010-04-23 End date 2010-09-23  100% positive votes  Comments from: ISO, Japan, France Editorial Minor technical Next stage  Modify modules affected by ballot comments  Publish as a Change request  Address ballot issues that affect AP document  Publish as an International Standard by early 2011

4. AP239 ed2 Summary of changes  Used latest editions of modules  Extended Selects  Added:  System / non abstract Product  Analysis  Validation & verification  Risk  Created:  Collection  Product Environment  Same-as  Conditional effectivity  Identification relations  Modified:  Message  Observation  Resources  Product category – removed from modules  Justification – added assumption

5. AP239 ed2 Summary of deferred issues  AP214 specification based variant  STEP Architecture  Single level ARM based model  Implementation schema Use of UML Clean schema to remove redundancy (/IGNORE)  Deferred to Future STEP architecture  Product structure  Use of product occurrence Deferred until AP242 simplify the model  Task  Make it easier to implement  Units  Use reference data  Breakdowns  Navigation of structure  Identification  Allow a context  Test data  Develop and publish some

6. AP239 e2 IS publication plan Approach  Ensure we publish quickly  Avoid any major technical work Analyse modules that have changed since DIS.  Approx 20  Mainly minor technical  Review risk_definition risk_management shape_property_assignment value_with_unit Address ballot issues

7. AP239 e2 IS publication plan (cont) Analyse open SEDS and bugzilla issues  Mapping issues – can we defer these? Properties  Make sure that all property assignments conform to rules of Activity/Resource/Documents/Product Breakdown  Review breakdown issues – address if can be done quickly Identification  Review identification issues – address if can be done quickly

8. AP239 e2 IS publication plan (cont) Units  Review on going activity in SC4 Test data  Develop a test file Part_occurrence for assembly structures  Document usage / differences  Defer & Make recommendations to AP242

9. Next stages - Process 1. Hold ballot comment resolution workshop  Agree issues to be addressed 2. Address issues against modules  Produce a new Change Request  Ballot change request 3. Produce the AP document 4. Submit to convener for review 5. Submit to ISO for publication

10. Risks AP242  Risk AP242 intend to modify module ARMs Scope of change not clear, but this will directly impact AP239. Similar changes made by Ap203 and AP210 impacted AP239  Mitigation Agree with AP242 to defer changes until AP239 has published. Work to build consensus with AP242 This will require resource Lack of resource  Mitigation Resource available to support the publication process No resource identified for building consensus with AP242 Delays at SC4  Risk Time take to review In a queue of Change requests  Mitigation Build in quality via XSLT publication mechanism Combine AP239 modules with CR already in development Delays at ISO  Mitigation ??

11. Backup

12. Types of change PLCS/SC4 (SEDS) modifications to PLCS modules  Deployment of the standard has identified issues to be addressed  Raised as SEDS against the standard Only SEDS will be considered (all DEXlib issues migrated)  Mainly SELECT extensions − Allow additional assignments  Modules used by AP239 modified by AP239 New modules created for AP239  Some new PLCS modules will be required to address the issues  Aim to avoid scope creep! Modules used by AP239 modified by other APs  Development of AP203e2/AP233/AP236/AP210 has led to some changes to PLCS modules  New editions of “PLCS” modules have been published Use of Ap203e2/233 modules by PLCS  Ap203e2/233 have developed a number of new modules within original PLCS scope

13. Approach to changes Only change if there is a business requirement to be met  Use deployment projects experience  No changes for changes sake AP239 implementations are principally at the ARM level, some MIM level implementations  Focussing on ARM changes  Which we will map to the MIM Ensure backward compatibility with AP239  Where ever possible ….. there will be some changes There may be an impact on PLCS OASIS templates  E.g. description  Fix these as we go