1. 1 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014 PROMCODE Service Specification  PROMCODE Version 3.0? service is based on OSLC Core Specification Version 3.0  Resource Operations  Support resource operations via standard HTTP operations  Service Provider Resources  Provide a Service Provider Catalog and provide a Service Provider resource  Creation Factories  Provide creation factories to enable resource creation via HTTP POST  Query Capabilities  Provide query capabilities to enable clients to query for resources  PROMCODE Version 3.0? service is based on OSLC Core Specification Version 3.0  Resource Operations  Support resource operations via standard HTTP operations  Service Provider Resources  Provide a Service Provider Catalog and provide a Service Provider resource  Creation Factories  Provide creation factories to enable resource creation via HTTP POST  Query Capabilities  Provide query capabilities to enable clients to query for resources

2. 2 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014 Use Case “Project Start with PROMCODE” [Nov. 25]  Preconditions  Scenario  An acquirer registers “Project ID”, “Project plan”, and “Mapping Rules” to the PROMCODE Consumer.  The acquirer generates a data in the PROMCODE model with the PROMCODE Consumer and stores it to a DB.  A supplier registers the “Project ID”, “Project Plan”, and “Mapping Rules” to the PROMCODE Provider.  Preconditions  Scenario  An acquirer registers “Project ID”, “Project plan”, and “Mapping Rules” to the PROMCODE Consumer.  The acquirer generates a data in the PROMCODE model with the PROMCODE Consumer and stores it to a DB.  A supplier registers the “Project ID”, “Project Plan”, and “Mapping Rules” to the PROMCODE Provider.

3. 3 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014 Use Case “Project Start with PROMCODE” with Excel Server 1.Send the Excel files to the Excel Server 2.Get the project URL PROMCODE Excel Server Excel 1.Create an Excel file with a project 2.Create an Excel file with mapping rules 1.Add Plan and ScopeItems in the Excel file 2.Send the Excel file to the Excel server again with project URL as a parameter 1.Load Project into an Excel file Excel client executes PROMCODE services HTTP REST calls Excel 1.Load Plan and ScopeItems into the Excel file Excel client executes PROMCODE services HTTP REST calls

4. 4 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014 1.HTTP GET: service provider catalogservice provider catalog 2.Find creation factory for promcode:Project resource in the catalogcreation factory 3.HTTP POST: a promcode:Project resource in RDF form to the Project creation factory URL Location header in the response is the URL of the created Project resource 1.Create a promcode:Plan RDF resource which has the project URL as a belongsTo property 2.Find creation factory for promcode:Plan resourcecreation factory 3.HTTP POST: a Plan resource to the Plan creation factory URL Location header in the response is the URL of the created Plan resource 1.HTTP GET: project URL 1.Find query capability for promcode:Plan resourcequery capability 2.HTTP GET: query capability URL for Plan resource with oslc.where=promcode:belongsTo=[Project URL] The response contains list of preomcode:Plan resources which belong to the project 3.Find the latest plan by using promcode:date property 4.Find promcode:ScopeItem resources by using promcode:collets property Use Case “Project Start with PROMCODE” with PROMCODE services

5. 5 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014 Use Case “Project Execution with PROMCODE” [Nov. 25/Dec. 10]  Preconditions  The acquirer and supplier respectively register “Project ID”, “Project plan”, and each “Mapping Rules” to the PROMCODE.  The supplier agreed to push the Report to the PROMCODE Provider on the Web until the specified date and time.  The acquirer and suppliers agreed to the schema of the “Report” to be reported from suppliers to the acquirer.[ 要補足説明 : 差分，スナップショッ ト ]  Scenario  A supplier registers its “Report” data to the PM tool S1.  The supplier converts the “Report” from the PM tool S1 to the PROMCODE resources.  The supplier pushes the “Report” in the PROMCODE schema to the PROMCODE Provider on the Web.  The Acquirer, a PROMCODE Consumer, pulls the collection of “Reports” from the PROMCODE Providers.  The Acquirer converts the collection of the “Reports” in the PROMCODE resources to the PM tool A.  The Acquirer reviews the “Report” on the PM tool A.  Preconditions  The acquirer and supplier respectively register “Project ID”, “Project plan”, and each “Mapping Rules” to the PROMCODE.  The supplier agreed to push the Report to the PROMCODE Provider on the Web until the specified date and time.  The acquirer and suppliers agreed to the schema of the “Report” to be reported from suppliers to the acquirer.[ 要補足説明 : 差分，スナップショッ ト ]  Scenario  A supplier registers its “Report” data to the PM tool S1.  The supplier converts the “Report” from the PM tool S1 to the PROMCODE resources.  The supplier pushes the “Report” in the PROMCODE schema to the PROMCODE Provider on the Web.  The Acquirer, a PROMCODE Consumer, pulls the collection of “Reports” from the PROMCODE Providers.  The Acquirer converts the collection of the “Reports” in the PROMCODE resources to the PM tool A.  The Acquirer reviews the “Report” on the PM tool A.

6. 6 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014

7. 7 Use Case “Project Execution with PROMCODE” Review and Actions for Schedule Problem [Dec. 10]  Schedule Delay 1.PM-A compares previous report and current report and highlights the difference. 2.Reviews the difference and raises a concern if the following is observed. 1.No progress from the previous report 2.Risk of not meeting a schedule emerges with the current pace of progress. May use past data on productivity to project risk. 3.PM-A interacts with PM-S on further update. 1.Reasons for delay 2.Outlook of meeting a schedule. 4.Based on the interaction, PM-A takes one of the following actions. 1.No formal action, but with notice on the situation to monitor. 2.Raise an issue on the situation and create actions 3.Escalate to stakeholders for possible plan change. 5.If it is necessary, plan will be changed [See details in “Plan Change” scenario]

8. 8 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014 Use Case “Project Execution with PROMCODE” Review and Actions for Quality Problems [Dec. 10]  Quality Concern 1.PM-A compares previous report and current report and highlights the difference. 2.Reviews the difference and raises a concern if the progress is not sufficient and there is a risk of not meeting quality goal. 3.PM-A interacts with PM-S on further update. 1.Reasons of the current problem 2.Outlook of meeting a goal 3.Assess the impact to the overall project. 4.Based on the interaction, PM-A takes one of the following actions. 1.Raise an issue on the situation and create actions 2.Escalate to stakeholders for possible plan change. 5.If it is necessary, actions will be taken place [see details in “Quality Action” scenario]

9. 9 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014 Use Case “Project Execution with PROMCODE” Plan Change[Dec. 10]  About Plan Change: “Plan change” may change  ScopeItem including “PlannedSize”, and entities in the ScopeItem  WorkItem including PlannedEndDate, and  Artifact  Scenario of Plan Change [Change of Scopeitem]  The Acquirer determines to change the ScopeItem  The Acquirer notifies the changes of ScopeItem and associated new plan to appropriate Suppliers.  The Supplier reviews the new ScopeItem and associated new plan, and notify its agreement to the sustimer.a  The Acquirer and Supplier get agreed.  The Acquirer set the new plan to the “plan”.  The Acquirer and Supplier review the ScopeItem revised, and associated WorkItem nd WorlItem if necessary  About Plan Change: “Plan change” may change  ScopeItem including “PlannedSize”, and entities in the ScopeItem  WorkItem including PlannedEndDate, and  Artifact  Scenario of Plan Change [Change of Scopeitem]  The Acquirer determines to change the ScopeItem  The Acquirer notifies the changes of ScopeItem and associated new plan to appropriate Suppliers.  The Supplier reviews the new ScopeItem and associated new plan, and notify its agreement to the sustimer.a  The Acquirer and Supplier get agreed.  The Acquirer set the new plan to the “plan”.  The Acquirer and Supplier review the ScopeItem revised, and associated WorkItem nd WorlItem if necessary

10. 10 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014

11. 11 All Rights Reserved, Copyright Next-Generation Project Management Data Exchange Architecture Committee, 2014 Use Case “Publishing Issue(s) with PROMCODE” [Nov. 25]  Precondition  Acquirer creates an instance of “IssueCollection”.  Scenario  A Supplier registers an “Issue(s)” to the PROMCODE Provider.  The PROMCODE provider notifies the registration of the “Issue(s)” to the Acquirer.  The Acquirer, a PROMCODE Consumer, pulls the published “Issue(s)” from the PROMCODE Provider.  The Acquirer reviews the “Issues”.  Precondition  Acquirer creates an instance of “IssueCollection”.  Scenario  A Supplier registers an “Issue(s)” to the PROMCODE Provider.  The PROMCODE provider notifies the registration of the “Issue(s)” to the Acquirer.  The Acquirer, a PROMCODE Consumer, pulls the published “Issue(s)” from the PROMCODE Provider.  The Acquirer reviews the “Issues”.