1 / 17

Changes to ISO 10303-239

Changes to ISO 10303-239. Rob Bodington, Phil Spiby. Objectives of telecon. Inform about project Agree scope of changes to ISO 10303-239 Agree publication strategy Timescales. Objectives. TOG to agreement 2009-01-19. Deliver update edition of ISO 10303-239

talen
Download Presentation

Changes to ISO 10303-239

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Changes to ISO 10303-239 Rob Bodington, Phil Spiby

  2. Objectives of telecon • Inform about project • Agree scope of changes to ISO 10303-239 • Agree publication strategy • Timescales

  3. Objectives TOG to agreement2009-01-19 • Deliver update edition of ISO 10303-239 • Updated ISO 10303-239 ready for taking forward ballot 31st March • Incorporate required changes identified from PLCS deployments • Ensure compatibility with AP233 • Include additional AP203/233 modules as appropriate • Ensure backward compatibility with AP239 • There may be an impact on PLCS templates • E.g. description • Attempt to ensure that seen as minor corrections/extensions – not another reason not to use PLCS

  4. Approach to publication TOG to agreement2009-01-19 • Agree publication strategy & timetable • New edition? • Publish as International Standard 2010 • The process is to raise a new work item for the development of the AP239e2 Committee Draft (CD) • NWI will list modules to be changed and new modules • Submit NWI to SC4 Change management for a 2 week review • Send for initial ballot under ISO process as combined CD and NWI • AP239e2 CD ballot will include TS ballot of all new and changed modules as well as the AP • Action: develop NWI by 30 Jan 2009 • Identify resources • Eurostep funded by UK MoD to March 31st • Invite other resources to participate to take the AP forward • Role of the TOG • Build consensus • PLCS OASIS Core team • Action: email Core team • PLCS OASIS TOG • Completed • PLCS OASIS TC • ISO SC4 • SC SEDS workshop 9-12 March • Action: notify WG3/WG12 conveners • Action: Notify SC4 • Action: Investigate BSI support

  5. 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 • Action: ensure ALL PLCS issues are raised as SEDS • Action: ensure that everyone is aware of the issue raising process • Either SEDS or DEXlib issue • New AP239modules • Some new PLCS modules will be required to address the issues • Aim to avoid scope creep! • Action: Identify the required new modules • SC4 modifications to AP239 modules • Development of AP203e2/AP233/AP236/AP210 has led to some changes to PLCS modules • New editions of “PLCS” modules have been published • Action: Summarize all the changes evaluate the impact • Use of Ap203e2/233 modules by PLCS • Ap203e2/233 have developed a number of new modules • Action: Summarize modules and agree what if any should be incorporated • ISO documentation changes • Ref data can now be documented in modules • Action: Decide if we include ref data. • E.g identification assignment • Propose to keep this in the dexs • Need to check existing modules for reference data • Abstract Test Suite? • We did not have any before …. • Conformance classes? • We did not have any before …. I think that we should keep them as DEXs

  6. PLCS/SC4 (SEDS) modifications to AP239 modules • Collecting all SEDS • Select extensions • New PLCS modules • Extended_observation • Extended_message • Information collection • Configuration management? • Resource item?

  7. SC4 modifications to PLCS modules TOG to agreement2009-01-19 Focus on the ARM However, we will have to list the MIM changes • 35 out of 138 modules changed • Focussing on ARM changes • MIM changes can we ignore? • Types of Changes • Changes to USE FROMS, selects, rules • Changes to entities • New entities • Reordering of attributes • A number of ARM modules have had their attributes reordered • PLCS p21 files no longer compatible • Do we care? how do we get this changed back? • Mandatory attributes now optional • Documentation “pulls” in extraneous ap203 modules TOG to agreement2009-01-19 Ignore changes Raise issues

  8. SC4 modifications to PLCS modules • Geometry • contextual_shape_positioning • Complete rewrite • elemental_geometric_shape • Removed Value_with_unitAddedIdentification_assignment (WHY?) • shape_property_assignment • Documentation “pulls” in extraneous ap203 modules TOG to agreement2009-01-19 geometry is not the focus of PLCS so live with change Raise SEDS to get this addressed

  9. SC4 modifications to PLCS modules • Assembly structure • An Assembly_component_relationship is now a type of Product_occurrence_definition_relationshipProduct_occurrence_definition_relationship is an abstract supertype with no supertypesNo idea why they changed this • It was a type of View_definition_usage. • This may have a major impact • Documentation “pulls” in extraneous ap203 modules

  10. SC4 modifications to PLCS modules • Properties / representation • extended_measure_representation • Changedvalue_limitRemoved value_limit_with_global_unitqualified_property_value_representation • property_assignment • Made Property_representation a subtype of Property_definition_representation • independent_property_representation • Independent_property_representation now a subtype of Property_definition_representation

  11. SC4 modifications to PLCS modules • State • Changed by AP233 • Same content – split modules • Will require minor modifications to ap239_* modules

  12. SC4 modifications to PLCS modules • Task • Changed by A233 • extended_task_element • Will require minor modifications to ap239_* modules

  13. Use of AP203/233 modules by PLCS • Should we incorporate all of 233 modules? • Description • Fixes 239 hack • Analysis • Behaviour • Validation & Verification • Risk? • However, it is not yet at TS level

  14. ISO publication/documentation changes • Ref data can now be documented in modules • Action: Decide if we include ref data. • E.g identification assignment • Propose to keep this in the dexs • Need to check existing modules for reference data • Abstract Test Suite? • We did not have any before …. • Conformance classes? • We did not have any before …. I think that we should keep them as DEXs • XSLT changes to AP • Action: investigate NDLO resourcing work on test rallies Can contribute to the abstract test suite

  15. Plan • PLCS/SC4 (SEDS) modifications to Ap239 modules • Analyze issues • Identify / Agree new modules • Information collection ……. (others) • Address SEDS • Develop new Ap239 modules • Create module • Create template • SC4 modifications to PLCS modules • Analyze changes – impact analysis • Analyze change to State • Analyze change Task • Analyze Assembly • Update ap239* modules • Use of Ap203/233 modules by PLCS • Analyze new modules • Identify those that are useful to PLCS • Add module • Extend selects • Update templates • ISO document preparation • Complete checklists • Generate HTML

  16. Milestones • SC4 modifications to AP239 modules understood (30th Jan) • Agreed / changed • Scope of AP239e2 agreed (30th Jan) • new AP239 modules identified • 203/233 modules to include agreed • AP239 modules SEDS modules addressed (28th Feb) • SC4 SEDS workshop 10-12th March • New AP239 modules developed (20th March) • AP239e2 + modules ready for SC4 process (31st March) • New HTML for AP239e2 delivered

More Related