OSLC PLM Workgroup Main monthly meeting Sept 6th 11am ET

Chair: Gray Bachelor

OSLC PLM working session topics:
1. Welcome / Roll call

Attendees: Gray, Rainer, Mike, Michael, Carlos, David
Apologies: Jim, Steve
Welcome to Michael Fiedler - QM experience, lead eclipse Lyo, test suites, SDK client and server

2. Clarify roadmap focus for this working session

Rainer has publicised the roadmap.

Today's focus is Scenarios with some discussioin on PLM extensions and Lyo prototyping

http://open-services.net/bin/view/Main/PLM2011Roadmap

3. Update on the scenario, reference model availability and feedback

(Validation and updates to the scenario and reference model here
Scenarios update a1 and a2
ACTION: The Ref model to be updated as V1.2
Q? What PLM entity "point" at

4. Resource prototyping using RIO / eclipse Lyo
Status and availability of the extensions to Lyo
Michael F Lyo project setup on eclipse - initial code contributions and test suites
Mailing list available
Next month: test suites

Mike L: TC repository example - mapping OSLC obj and PLM obj
Plan to contribute to eclipse

Create, review and update Reqs in/from TC

CM and AM come next - e.g. cross linking

Need discussion about managing cross-repository
TC has a multi-site capability (maps the semantic in the TC "world"
Candidate to show with Core WG

Mike's extensions are in a separate class under RM in the Lyo code
Proposal to put in Core

5. Application and extension of the reference model
Show where in the model for Oct 5th

6. Responding to new OSLC Specs and concepts being published
http://open-services.net/bin/view/Main/Plm20SpecExtensions
Q? What relationahipss are item version speciifc e.g. CR to Doc
Q? Ability to link to latest version
Effectivity topics
e.g. use the latest revison
Lot effectivity - e..g manufacturing batch or lot
Variant handling

Precise locks revisions

Imprecise has links to base objects and which in turn provide the latest revision

Example: CR > revision of artefact, then revise the artefact for another purpose
Approach: Store the explicit revison and relationship or use an effectivity expression e..g date of effectivity
Observation: Spec doesnt mandate handling - so guidance is needed in lieu of strong semantics e.g. relationships between objects
(for example DOORS doesnt use a fine grain version model - so use a baxseline for a set of requirements

Oct 5th Core meeting at 11am
How to present ?
Preparation needed ?
6.1 Description for terms
ACTION: David provde some examples - concepts
ACTION: Rainer propose terms
ACTION: Gray to approach Geoff Clemm re SCM
ACTION: Gray to dig into the STEP definitions
Scenario layout - Carlos to propose
Example from Lyo: Mike L/Gray
Issues and challenges: David provide example(s)
Summarise needs: Gray

7. Summary, actions and close
Check open items from Sept 6th
Next meeting 2th Sept
Check Actions
ACTION: New invites for WorkGroup? - Gray
ACTION: Ask Steve to confirm Oct 5th meeting - Gray
ACTION: Sept 20th focus on Oct 5th prep and Lyo prototyping
OPEN Q: is there a PLM concept of stream