Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 1 Payload Planning System (PPS) User Requirements Collection (URC) POIWG Status August 5, 2004 Launch PPS 5.0

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 2 URC Schedule Status Target Increment for first collection of data in URC is Increment 13 Ops Prep. Training and collection process could begin as early as October –iURC and URC will run concurrently to support different increment datasets. PARCs will begin loading data during Phase II of IV&V

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 3 Training and Transition Training Plan is in Work –PARCs and PPS team members will be available for collaboration. PARCs will provide training to their PD counterpart. –Developing a “URC Pocket Guide” available mid October Login and Accounts information Activities, Sequences and Reports building –URC will have online help. Transition from iURC to URC –PARCs will input existing iURC data for Facilities and Multi-Increment Payloads directly into the URC test system. –Test system data will be transferred to the operational system. When PDs with established Payloads log into their new accounts, they will find their data waiting for them. –New Payloads and PDs may build their own activities and sequences. Or, the PARCS may perform this service as well. New POIC accounts or modifications to existing HOSC accounts will be required for PPS services. PPS will be available as a downloadable for remote users from the Payload Operations and Integration Center (POIC) website on:

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 4 Login to PPS PPS Development PPS Re-engineering Desktop icon to launch PPS

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 5 In Desktop Tray PPS Development PPS Re-engineering View as a Window on Desktop PPS Workstation Launchpad As PD

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 6 URC PD Main Window – Activities View A PD will create a new or edit an existing Activity within this URC main window.

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 7 URC PD Create Activity Screen Commonly used fields such as procedure, duration, and description are located at the top of the activity screen All data required for promotion is clearly visible and indicated by an *.

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 8 URC Resources and Conditions More intuitive resource and condition lists for activity building –Complimentary data inputs in one place, i.e., data inputs more organized. URC USOS Screen for Power and Thermal data inputs URC Data Downlink Screen for data requirements

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 9 URC PD Main Window – Sequences View A PD can create a new or edit an existing sequence within this URC main window

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 10 URC PD Create Sequence Screen The PD will graphically model his sequence and fill out three more fields to promote. All data required for promotion is clearly visible and indicated by an *.

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 11 URC Reports Screen A PD can view reports within the Reports option of the PPS Launchpad Window

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 12 Issues Remote users are required to use Virtual Private Network (VPN) to access HOSC tools and applications, e.g., URC. Currently, we are aware of this being a problem for the NASA Glenn campus. If there are others, please let us know. This issue is in work.

Date: August 5, 2004 Originator: Angela Marsh/FD42 Page: 13 Acronyms DTEDevelopment Test Environment GUIGraphical User Interface HOSCHuntsville Operations Support Center iURCInterim User Requirements Collection IV&V Independent Verification & Validation PARCPayload Activity Requirements Coordination PCPersonal Computer PPS Payload Planning System URC User Requirements Collection VPN Virtual Private Network