1 / 10

OSLC ALM-PLM interoperability

OSLC ALM-PLM interoperability. Discussion. OSLC PLM extensions. Product. isVersionOf. AMG54556_002. Product, Version. affectsPlanItem. hasView. AMG54556/001-View. affectedByPlanItem. Product, View. CR. hasPart. AMG12345/001-View. Product, View. AMG60112/001-View. hasPart.

jared-mason
Download Presentation

OSLC ALM-PLM interoperability

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. OSLC ALM-PLM interoperability Discussion

  2. OSLC PLM extensions Product isVersionOf AMG54556_002 Product, Version affectsPlanItem hasView AMG54556/001-View affectedByPlanItem Product, View CR hasPart AMG12345/001-View Product, View AMG60112/001-View hasPart Resource, View hasPart AMG60112/001-View Requirement, View

  3. SUV example (1) – Create an SuV Configuration Product configuration “as designed” What are the steps ? What are the needed resources ? How “mark” existing resources ? What new resources needed ? How are variants defined ? Un released product (s) New and existing engine (ranges) New and existing engine control units (ECUs) New and existing ECU Software

  4. The basic precursor to the main scenario focuses on the ability to make associations between the 3 key OSLC entities Variant params Variant B Variant A New unreleased product definition PD Spec draft Product PM System or product context Implementation Implementation Requirements Implementation Requirements AM Spec 2.0 Resource AM RM Spec 2.0 Requirement RM SCM Spec 2.0 Baseline AM

  5. In our product sandbox • Create initial product identity • (Postpone getting the formal identity from the master register • Add initial classification • Product families, types, organisational ownership • Add from Catalogs of existing terms may inherit the requirement traceability • Add preliminary lifecycle codes (state indicator) e.g. preliminary, not for sale • Add business rules for state changes • Workflow is assigned • Or Manually controlled • Typically already under version control • Pause button: Resource type = Product, Version, number of properties

  6. In our product sandbox (2) • Define options and combinational/evaluated rules • From a catalog • From a requirement • From selecting a compositional “thing” • Valid combinations • Pause: Added variant parameters and variant expression • Issue: shown examples but not proposed vocabularies

  7. Discussion • Identification of coding and classification • Membership of Families, ownership, functionality …? • Includes variant parameters ? • Pedigree or provenance e.g. supercedes or replaces … • Need for type =version and property isVersionOf • Role of a base resource + variant parameters vs “direct” access of a version resource ? • Both needed ? • What about combinations of variant parameters to be assigned to multiple “designs” as variant configuration “Specs”? • Definition of structure (and containment) ? • Views as specific resource type vs hasPart or isViewOf property • View identifier for multiple domains • Versioning of views • Structure via linkage to views or base or versions with view specifiers • Linktypes for product relationships

  8. SUV example (2) – “Make from”(Make Configuration B from Configuration A by way of a Change Note) Related product configuration “as designed” Product configuration “as designed” Existing product(s) Related product Existing engine (ranges) New low emission engine (ranges) Existing engine control units (ECUs) Engine control unit (ECUs) updates Existing ECU Software ECU Software updates

  9. Our scenario focuses on the ability to make associations between the 4 key OSLC entities and control them during change CM Spec 2.0 ChangeRequest CM Change Request Problem item, Makefrom or impacts released product config (context) State 1 Existing released product definition PM Spec draft Product PM System or product context Implementation Requirements AM Spec 2.0 Resource AM RM Spec 2.0 Requirement RM Solution item: New released product config (context) State 2 New product definition System or product context Implementation Requirements

  10. Overview of the alignment to existing OSLC Specs No direct relationship, existing example CM Spec affectsPlanItem A product resource could be created from the AM Spec, but OSLC lacks a separate product resource Change Request CM CM Spec ChangeRequest No direct relationship, the AM Spec AMLinkType could be applied System or product context Indirectly via trackChangeSets Implementation Requirements RM Spec Requirement AM The AM Spec is flexible enough to allow definition of many resource types and relationships but does not apply existing domain definitions RM isSatisfiedBy or tracksChangeSet No overall product configuration with variation management. The draft SCM Spec supports baselines and versions. However neither CM, AM or RM Specs support versioning or variation handling directly

More Related