© 2013 OSLC Steering Committee1 Proposal to Create OSLC Affiliated Technical Committees OSLC Steering Committee Meeting: 1 PM EDT, 8 July 2013 Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web

© 2013 OSLC Steering Committee STARTING POINT i.e. what was communicated at the kickoff meeting 3Q 2013 Election of the 7 th Steering Committee member OSLC Core 3 to be contributed to OASIS to launch the OSLC Core TC

© 2013 OSLC Steering Committee3 Roadmap for OSLC at OASIS December 2012 OSLC Steering Committee approves plan to standardize OSLC domain specs at OASIS May 2013 OASIS Board unanimously approves creation of the OSLC Member Section co- founded by 22 organizations June 2013 First OSLC Member Section Steering Committee meeting OSLC Member Section Kickoff meeting 3Q 2013 Election of the 7 th Steering Committee member OSLC Core 3 to be contributed to OASIS to launch the OSLC Core TC 4Q 2013 – 2014 Existing OSLC domain specs are contributed to create affiliated TCs New domain work to start as affiliated TCs OSLC Member Section Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web To be refined with input from the OSLC Member Section participants.

© 2013 OSLC Steering Committee4 Timeline for OSLC Core Transition ActivityTarget End DateComments Submit Core TC Charter to OASIS 2 August 2013Proposed charter submitted to OASIS TC administrator. Officially Launch Technical Committee 15 October 2013 Minimum 5 eligible people from at least 2 OASIS organizational members. Core 3 Spec to be initial TC Working Draft. Phase 1: Producing first Committee Specification Draft 31 March st round Committee Spec Public Review Ends 30 April 2014Collect comments from Member Section. Phase 2: Addressing Public Review feedback 31 July 2014Update Committee Spec, take to 2nd round review. 2nd round Committee Spec Public Review Ends 31 August 2014Address review’s comments. (Assume no further review required.) Finalize Committee Specification 30 September 2014No implementation or test case requirements. Phase 3: OASIS Standard Review period & voting Ends 30 November review period, 14 day vote period. Requires 3 statements of use. OASIS Standard15 December 2014 All dates subject to change.

© 2013 OSLC Steering Committee5 OSLC Member Section Scope Draft Converge Final Core 3.0 Change Management 3.0 Configuration Management Asset Management 3.0 Quality Management 3.0 Architecture Management 3.0 Estimation and Measurement PLM/ALM Automation 3.0 Performance Monitoring 3.0 Resource Reconciliation 3.0 Change and Configuration Management TC Requirements and Quality Management TC Core TC Integrated Service Management TC Automation TC 1 2 A B C D Example Domain TC Content & Creation Phases Requirements Management 3.0 Other TCs based on other OSLC WGs, OSLC UGs, existing external initiatives, Member interest, or a combination of. E OSLC UG Unordered External Initiative Member Interest Subject to Change

© 2013 OSLC Steering Committee PLAN CHALLENGES i.e. concerns and perceived problems with this plan

© 2013 OSLC Steering Committee7 Q&A Based on Our Current Plan  What TC(s) comes after Core? –We’re not really sure. It depends on OSLC 3 specification progress and community interest.  If we knew what was next, when would it happen? –We’re not really sure. Sometime after we’ve learnt from the experience of creating the Core TC … maybe before the end of 2013 …  How are MS members supposed to get value out of their membership? –Election … be a founder for the Core TC … mailing list … open-services.net … ???  Why would new organizations join the MS? –???

© 2013 OSLC Steering Committee PLAN ELABORATION i.e. augment the plan so that we can give better answers

© 2013 OSLC Steering Committee9 TC Creation Pipeline Prioritization & Preparation TC Charter Creation & TC Co-founder Recruiting TC Charter Submission & OASIS Process OASIS Approval & 1 st TC meeting Core TC DoneJul 2013Aug-Sep 2013Oct st Domain TC(s) Jul-Aug 2013Aug-Sep 2013Sep-Nov 2013Nov nd Domain TC Wave Sep-Oct 2013Nov 2013Dec-Jan 2014Feb rd Domain TC Wave Nov Jan 2014 Feb 2014Mar-Apr 2014May 2014 Jul ‘13Jun ‘14Oct ‘13Feb ‘14 Core 1 st Domain TC’s 2 nd Domain TC Wave 3rd Domain TC Wave

© 2013 OSLC Steering Committee10 Pipeline Comments  As Core passes through each phase we can apply the learnings to the 1 st Domain TC(s) –And similarly for the 2 nd and 3 rd waves –To learn the most from our first time through, we should apply those lessons ASAP  Which Domain TC(s) we create after Core should be determined by a number of factors –Interest from the Member Section –Progress of the version 3 specification at open-services.net –Perceived maturity of scenarios and scope (for new domains, or any existing spec that has reason to start at OASIS based on its version 2 documents plus new scenarios)  The 2 nd and 3 rd waves may be more conceptual than actual … at that point, creation of new TCs may be driven by the Members more than regimented by the Steering Committe

© 2013 OSLC Steering Committee11 Q&A Based on the Proposed Plan  What TC(s) comes after Core? –We’re not really sure. It depends on OSLC 3 specification progress and community interest. If there is strong interest in one or two, we can start working on the Charter(s) as early as August  If we knew what was next, when would it happen? –Given sufficient interest and energy from the community, the first domain TC(s) could be up and running as early as November  How are MS members supposed to get value out of their membership? –Express your PoV and contribute your energy to choose and create, and start work in, the Core TC and domain TCs too.  Why would new organizations join the MS? –It is a vibrant and dynamic community working to standardize how tools share data in, and across, a number of domains, including … Member contributions are encouraged.

© 2013 OSLC Steering Committee BACKUP

© 2013 OSLC Steering Committee13 OSLC inside OASIS OSLC Member Section 5+ OASIS Members are the foundersOther OASIS Members can join when they choose OASIS Steering Committee 1 Technical Architecture TC 2 1.The current OSLC Steering Committee becomes the OASIS OSLC Member Section Steering Committee 2.The Core workgroup becomes the Technical Architecture TC (Technical Committee). 3.Domain TCs are created by composing several OSLC domain workgroups. 4.Subcommittees may be created by the Steering Committee for a number of purposes. E.g. scenario development and prioritization or exploration of new domains ahead of creating a new TC. Domain TC Domain TC 3 Subcommittee Subcommittee 4 advises guides oversees