1 / 65

Order-to-Pay ( OtP )

Order-to-Pay ( OtP ). System Requirements Review (SRR) Terry Conroy / Jim Walker Pam Wolfe/ Sittra Battle 10:00 – 11:30 am 07/08/14. AGENDA. Project Governance SRR overview Project Overview system overview Requirements overview success criteria Summary. Project Governance.

binh
Télécharger la présentation

Order-to-Pay ( OtP )

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. Order-to-Pay (OtP) System Requirements Review (SRR) Terry Conroy / Jim Walker Pam Wolfe/ Sittra Battle 10:00 – 11:30 am 07/08/14

  2. AGENDA • Project Governance • SRR overview • Project Overview • system overview • Requirements overview • success criteria • Summary OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/2014

  3. Project Governance * These projects are using a hybrid model to facilitate rapid development for on time delivery. Much of the work and decisions will be made by the Project Manager and Scrum team. Monthly reviews will be held to demonstrate progress to the stakeholder community and determine priorities for the next sprint. In the event that the Project Managers do not have consensus with the Scrum team, or there is concern for increase in the scope of the project, the co Decision Authorities will resolve the matter. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  4. Key Dates, Milestones, and Approach Key Milestones Project Approach The two projects (Center Validation Tool [CVT], and EUSO Refreshes [TR] share a common governance with a single review board and a hybrid Agile / 7120 approach. There will be a single SRR and TRR for both projects. Each will have an ORR as they are released. Between SRR and TRR there will be periodic Sprint Review meetings open to all external stakeholders. The expected interval is approximately 30 to 45 days. These reviews will transparent for all stakeholders. KDP-C and E will be brief by the Project Management team to the I3P KDP Review Board. A Project Completion Review (PCR) will be held after the OtP – Tech Refreshes project is released. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  5. SRR Purpose System Engineering Review Team (SERT) Members and Decision Authority SRR Entrance Criteria Review Item Discrepancy (RID) Overview SRR Overview OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  6. SRR Purpose The purpose of the SRR is to: Examine the functional, technical, performance, and security requirements for the system and elements of the preliminary Project Plan. Ensure that the requirements and the selected concept will satisfy the system objectives. NPR 7120.7/NID 7120.99 Appendix G.2 Agile Scrum n 2 4 5 1 3 3 7120 OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  7. System Engineering Review Team (SERT) Members and SRR Decision Authority OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  8. SRR NPR 7120.7/NID 7120.99Entrance Criteria Status OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  9. SRR NPR 7120.7/NID 7120.99Entrance Criteria Status (cont’d) OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  10. Review Item Discrepancy (RID) Overview • RID • A RID is a formal written request submitted to the RID Review Team (below) that describes a problem, provides possible recommendations, and details impact(s) to the project if the recommendation is not implemented. • RID Considerations • RIDS must submitted by 9 am Pacific time, 14 July, 2014. • Only RIDS addressing issues within the scope of this review will be accepted. • All RIDS with their disposition will be available for review via a website (TBD) for interested stakeholders. • RIDs must be submitted via the RID form available in ServiceNow Project Portfolio Management (PPM). • Completed forms must be emailed to Diane Fulton diane.t.fulton@nasa.gov and vicky.essick@nasa.gov. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  11. Executive Summary Project Organizational Structure Key Dates, Milestones, and Approach Top 5 Project Risks and Issues Project Communications Plan and Activities Project Overview OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  12. Executive Summary (1 of 5) OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  13. Executive Summary (2 of 5) OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  14. Executive Summary (3 of 5) OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  15. Executive Summary (4of 5) OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  16. Executive Summary (5 of 5) Y Y G Y G OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14 Current project rating as of SRR: Overall Cost Schedule Technical Programmatic

  17. Projects Organizational Structure Governance Governance Project Project OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/2014

  18. Top 5 Project Risks a 1 5 a 2 4 a 3 a a OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  19. Project Communication Plan • Communication Plan for the Order to Pay (OtP) 1.0. Sec. 3 project provides messages, both operational regarding enhancements, applications and improvements to key stakeholders within the NASA OCIO community and I3P providers, to maximize ESD’s continued use by all NASA users. • Stakeholders identified in the plan are shown on the following two slides. • The communication plan was published 9/1/2012; OtP added 6/30/14 • An additional “mini-communication plan” has been developed specifically for all eight requirements • Execution of the plan is dependent on the receipt of current, accurate information from the Project Managers. • There are no issues that need to be addressed concerning this plan. • Communications are on schedule for deployment. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  20. Communications and Outreach ActivitiesDevelop Center Validation Tool (CVT) OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  21. Communications and Outreach ActivitiesEnd User Services Office Refresh OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  22. Analysis of Alternatives (AoA) Activities System Concept System Description Major System Interfaces System Overview OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  23. Analysis of Alternatives (AoA) Activities • In April 2014 OCIO asked NSSC to develop a technical solution to improve ACES monthly reconciliation and to provide the EUSO Refresh services via ESRS. Three scenarios: • Do Nothing: Not an option. Customer and program impact with current service model was inadequate. • Make Changes in Remedy: Initial thought was to move in this direction, patching what we could in incremental steps. Concerns: • Remedy did not easily support required customization • Remedy was out of both maintenance and BMC support, making any effort more complex and risky • NSSC Business Case supported move to ServiceNow. All Remedy services would need to be rewritten. • Make Changes using ServiceNow: Decision based on combination of factors: • NSSC Business Case approved move to ServiceNow product migration sooner than anticipated. • ServiceNow offered out-of-the-box functionality and features desired by customers and the program with no customization. • Based on the business case the upgrade effort for both SN and Remedy 8.0 were similar with SN having a slight advantage.  • In evaluating the requirements for TR and CVT, the limitations within 7.5 would result in customization, elongated development schedule and eventual rework.  Use of SN would shorten development time for both CVT and TR. • SN enhanced capabilities led to increased likelihood of meeting customer expectations for delivery. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  24. System Concept • The OTP project will leverage capabilities offered with the ServiceNow platform that add value to data lifecycle management and customer use. Components of the ServiceNow product will be implemented at identified project milestones. The result will be a gradual transition from the Remedy to ServiceNow platform, while implementing functionality for the end-user community. • During the CVT phase, Remedy order data will be deposited into the ServiceNow data store. The data store will be a relational model, allowing for the tracking of each service provisioned under the ACES contract as well as changes to any component/asset associated with that service. In addition, the CVT will be implemented such that end-users will be able to assert that their service and asset data is correct prior to invoicing. The result should be a substantial reduction in invoice errors. • Implementation of the Tech/Early Tech Refreshes processes will rely on several ServiceNow components being in production operation: service catalog, ‘my services’ view, and all service definitions eligible for tech/early tech Refreshes. • In order to leverage the service catalog in ServiceNow, all services will transition; not just the 45 associated with Tech/Early Tech Refresh. Testing of all services will be included within the test plan. • To streamline processes and increase data integrity, a web service interface between NASA and HP will allow for order and fulfillment data to be updated in near real-time, eliminating today’s manual processes. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  25. Sprints • Center Validation Tool (FY14 Q3 through FY15 Q1) • Release 1—Eliminate CI Spreadsheets (Requirement 7.0) • Sprint 1—Eliminate CI Spreadsheets • Release 2—OtP Data Store and User Interfaces (Requirements 2.0, 3.0, 4.0) • Sprint 1—Order to Pay Foundation and Web Services • Sprint 2—Center Validation Tool (Requirement 2.0) • Sprint 3—Role Based View/Modify Access (Requirement 4.0) • Sprint 4--Invoice/Order Exception Reports (Requirement 3.0) • Tech Refresh (FY14 Q3 through FY15 Q2) • Release 1—Tech Refresh and Early Tech Refresh (Requirements 5.0, 6.0) • Sprint 1—Show My Services (Requirement 5.0) • Sprint 2—Build Foundation for TR and ETR Services • Sprint 3—Build Tech Refresh and ETR (Requirement 6.0) • Sprint 4—Scripting Integrations/Reporting • Deliverables include time for unit, integration and user acceptance testing OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  26. Major System Interfaces OtP (Center Validation and EUSO Refresh) Project SRR, 07/01/14

  27. Concept of Operations Requirements Elicitation Approach Review Specific Questions Requirements Traceability and Approach to Requirements Management Functional Requirements Non- Functional Requirements Performance Requirements Requirements Overview OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  28. Concept of Operations Web services Any service Order fulfillment CMDB/AM Incidents ESRS User at Tier 0 in ESRS BMC -ICAM CMDB NED WO Asset Mgr Update FcART Access dB AMES ARFC MSFC SSC JSC KSC GRC GSFC NSSC HQ Langley I3P BO OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  29. Requirements Elicitation Approach • The project team includes members from each of the primarily affected groups: EUSO, I3PBO, ESD, CSC, and HP. This group met via telecon/Lync and F2F since February 2014 formulating the Requirements Document. • Each draft of the requirements document has been distributed to the project team for dissemination to their communities of interest, including CILs, SMEs, Resource Analysts, and Service Executives. • F2F meetings included time at the end of each day for a report out to CILs and SMEs at which time questions would be asked/answered or taken as actions. • Stakeholders are defined as all persons involved in the EUSO and I3PBO business work streams as primary, and all those within the realm of I3P and NSSC service delivery as secondary. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  30. Review Specific Questions OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  31. Requirements Traceability and Approachto Requirements Management Requirements Approach • The following process of discovering, analyzing, defining, and documenting the requirements were used: • Identified Key Stakeholders • Captured Stakeholder requirements • Held focus groups and requirements meetings • Categorized and prioritized requirements. • Defined and recorded high level requirements. • Held several Face to Face Meetings to determine lower level requirements. • All parties agreed too and signed off on the requirements. Requirements Management and Control • All requirement updates will need to be approved by the Project Executives and the Project Sponsor. The Project Manager will be responsible for updating the project requirements document and uploading the new version to Sharepoint. Requirements Repository OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  32. OtP Level 1 High-Level Requirements OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  33. NSSC Level 2 Functional Requirements Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  34. NSSC Level 2 Functional Requirements Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  35. NSSC Level 2 Functional Requirements Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  36. NSSC Level 2 Functional Requirements Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  37. NSSC Level 2 Functional Requirements Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  38. HP Functional Requirements • Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  39. HP Functional Requirements • Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  40. HP Functional Requirements • Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  41. HP Functional Requirements • Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  42. HP Functional Requirements • Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  43. HP Functional Requirements • Level 2 functional requirements are identified below. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  44. NPR 7120.7/NID 7120.99 Success Criteria SRR Success Criteria OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  45. SRR NPR 7120.7/NID 7120.99 Success Criteria OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  46. Lessons Learned Stakeholder Concur Conclusion Request for Approval Summary OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  47. Lessons Learned OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  48. Stakeholder Outreach OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  49. Conclusion / Request for Approval Concurrence: • All entrance criteria have been met. • All success criteria for the SRR are satisfied. OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

  50. Key References and Points of Contact OTP Level 3 & 4 Functional Requirements Backup Material OtP (Center Validation and EUSO Refreshes) Project SRR, 07/08/14

More Related