1 / 11

OSLC PLM workgroup

OSLC PLM workgroup. 2012 Kick off meeting For discussion. Topics for discussion. 2011 Achievements 2012 Roadmap. 2011 Achievements. PLM Workgroup sustained a consistent and regular meeting schedule Regular attendance from participating companies Definition and achievement of a roadmap

hija
Download Presentation

OSLC PLM workgroup

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 PLM workgroup 2012 Kick off meeting For discussion OSLC ALM-PLM interoperability Workgroup

  2. Topics for discussion • 2011 Achievements • 2012 Roadmap OSLC ALM-PLM interoperability Workgroup

  3. 2011 Achievements • PLM Workgroup sustained a consistent and regular meeting schedule • Regular attendance from participating companies • Definition and achievement of a roadmap • Regular website updates • Development and releases achieved: • 2 releases of the OSLC PLM Reference Model which shows what support is needed for the selected scenario • Published first draft Preliminary Specs and gained feedback • OSLC Core extensions for PLM • PLM Spec • Significant Lyo Prototyping to support the Spec extensions OSLC ALM-PLM interoperability Workgroup

  4. 2011 retrospective • Significant time is needed to discuss the domain needs, current Spec, RDF, constraints of existing applications • Path to an agreed Spec needs clarification either as an allowable extension or towards OSLC 3.0 • Systems and Product lifecycle concerns continue to arise and be followed up across multiple OSLC workgroups and an overview of these activities could be more readily available • We have continued to concentrate on a single scenario • The term PLM may be over ambitious and misrepresent the needs of the current scenario, consider a narrow focus to support the Product resource, e.g. Product Definition Spec • There isn’t an overarching context which could be useful to engage more participants including domain vocabulary and additional ALM-PLM lifecycle scenarios OSLC ALM-PLM interoperability Workgroup

  5. 2012 Goals • To secure the necessary Core extensions for PLM into an OSLC Core release plan • To achieve a first Final Spec for ALM-PLM interoperability • To grow participation from returning members and new companies • To build up wider ALM-PLM interoperability context and additional scenarios for selected aspects of the system lifecycle OSLC ALM-PLM interoperability Workgroup

  6. 2012 Focus topics for discussion aligned to proposed Goals • To build up wider ALM-PLM interoperability context and additional scenarios for selected aspects of the system lifecycle • Higher level view of the systems lifecycle with proposed vocabulary • Additional systems lifecycle and ALM-PLM interoperability scenarios • E.g. from EC projects MBAT, CESAR, iFEST and others with KTH, EADS etc • Provide an overview of related systems lifecycle initiative, standards and show/promote alignment with respective or corresponding OSLC Workgroups • To grow participation from returning members and new companies • Web meeting walkthrough of the draft proposals • On line demonstrations and self-service • Quarterly / Monthly news letter • Usage and alignment of existing systems lifecycle Industry Standards with OSLC • To achieve a first Final Spec for ALM-PLM interoperability • Feedback on application of existing Final specs - simplification • Updates following feedback towards Proposed Specs for Core and PLM • Approach to using additional existing ind std properties and linktypeshow to apply e.g. SysML?? Trace within existing (e.g. RM) and newly proposed Specs • To secure the necessary Core extensions for PLM into an OSLC Core release plan • Beautiful RDF (minimum and sufficient • Lyo update or extensions needed to support the core extensions proposals10a) SVN integration using SCM Spec then to PLM Spec • Interlock and alignment into the OSLC V3 Spec activities • impacts of new or emerging specs or application experience e.g. JIS, RELM • SCM Spec application and updates • Application of the Specs • high value example of heterogeneous multi-server queries for traceability • Applying the new Lyo SDK OSLC ALM-PLM interoperability Workgroup

  7. Streams • Lead, topic, timetable OSLC ALM-PLM interoperability Workgroup

  8. 2012 roadmap first draft Q1 newsletter Q2 newsletter Webcast Innovate presence Consolidate existing proposals Realign to OSLC 2012 release plan Invite new submissions Select 1 for new analysis Validate alignment to proposals Note: need to understand OSLC Core release plans for 2012 OSLC ALM-PLM interoperability Workgroup

  9. Follow on activities • Business model aligned across OSLC workgroups – Rainer Ersch • Feedback from MBAT – Rainer Ersch • Plan to approach past attendees – Rainer Ersch • Opportunity for a showcase at Innovate – Mike Fiedler • Outline of the Application showcase with Lyo, RTC + TBD – Gray Bachelor • Advice on OSLC Spec roadmap for 3.0 – Kartik Kanakasabesan, Steve Speicher • Meeting time clash for key IBM attendees – Gray Bachelor OSLC ALM-PLM interoperability Workgroup

  10. Backup OSLC ALM-PLM interoperability Workgroup

  11. Topics for discussion in 1) Feedback on application of existing Final specs - simplification 2) Updates following feedback towards Proposed Specs for Core and PLM 2a) approach to adopt additional existing ind std properties and linktypeshow to apply e.g. SysML?? Trace within existing (e.g. RM) and newly proposed Specs 2a) Web meeting walkthrough of the draft proposals 3) Beautiful RDF (minimum and sufficient 4) Interlock and alignment into the OSLC V3 Spec activities 4a) impacts of new or emerging specs or application experience e.g. JIS, RELM 4b) SCM Spec application and updates 9) next scenarios 9a) e.g. for EC projects CESAR, iFEST and others with KTH, EADS etc 9b) high value example of heterogeneous multi-server queries for traceability 10) Lyo update or extensions needed to support the core extensions proposals10a) SVN integration using SCM Spec then to PLM Spec 11) Applying the new Lyo SDK OSLC ALM-PLM interoperability Workgroup

More Related