1. IPLFOR POIF Process Review Eric Melkerson Payload Operations Director Operations Directors’ Office / EO03 Marshall Space Flight Center 256-544-3869 Eric.Melkerson@nasa.gov

2. IPLFOR Process OwnerProduct/OutputsCustomerSchedule TemplateProcess Documentation FD32 (EO03) Matrix with DN Status/Recommended disposition/Actions POIF Management Team~L-5.5 months (Letter to Book Managers + 60 days) SSP 58311, POH, Volume 1, SOP 1.18.2

3. IPLFOR Schedule Letter to Book ManagersBoard - 60 days Notification LetterBoard - 45 days Books due to WebconBoard - 35 days Review Start: Kickoff Review Schedule Explain each area’s roles/responsibilitiesV&V matrix Review goals of IPLFOR, IFOR & FOR Review activity definitions/PODF Board - 30 days DN cutoff dateBoard - 15 days DN screening (Includes: Inc Lead POD & Procedure ITC) Remove all DNs that do not adhere to guidelines Distribute DNs to Implementors for review Board - 14 days Assess Comments Review Approve/Disapprove/Withdraw/ID Issues ID Actions Board - 8 days Joint Ops TL Walkthru (if available) Step thru STP, ensure PODF in place for each activity Ensure GR&C in place, ensure stowage in place Ensure FDF/SODF inputs in place Activity descriptions in PODF Board - 7 days POIF DN Review Meeting CompleteBoard - 5 days IPLFOR Pre-Board MeetingBoard - 3 days IPLFOR Board Meeting Incorporate Approved CommentsBoard + 5d Repost Update to WebBoard + 10d

4. What is IPLFOR? Integrated Payload Flight Operations Review (IPLFOR) is a formal review of the flight operations products by the POIC Cadre and Users (PIs/PDs) Scheduled at approximately I-8.5 to I-7.5 to prepare for IFOR at I-7 Objectives of the review: –Ensure that the integrated payload ops design is compatible with all operational objectives, requirements, and constraints, and conforms with all ISSP requirements and constraints. –Verify that the payload flight operations concept and planning are properly defined and adequate to allow progressing to detailed implementation. –Verify that the cadre staffing and payload crew, cadre, and PD team training plans and schedules are adequate for proper mission preparation. –Define the detailed flight operations schedule and activities to be accomplished between the IPLFOR and Launch. –Stabilize the operation sequence assuring that the payloads’ requirements are satisfied.

5. POH 1.18.2 The increment-specific payload operations products are reviewed by POIF and customers. DNs are generated to address errors in requirements implementation. DNs that correct typos, request information, or introduce new requirements will be requested to be withdrawn. Increment Lead POD reviews the DNs and dispositions each one. The DN originator (or rep) must agree to the disposition. Each Book Manager should have reviewed the DNs against their book and be prepared to make a recommendation on disposition. All DNs are posted to IPLFOR web page. The DN types are: Type I - Programmatic cost/schedule impacts, nonconformances with established program policy/guidelines, significant changes to requirements, design implementation, or project planning. Type II - Requirements, design implementation, or project planning impacts. Do not impact cost nor schedule. Technical in nature; address the generation/definition/ clarification of requirements or minor changes/deletions to established requirements. Type III - All other issues; technical errors; minor clarification of existing requirements. The review organization consists of: –Review teams (discipline teams) who: Evaluate, Combine, Approve, Approve with Changes, or Disapprove Type III DNs. Disapproved DNs will be presented to the Pre-Board with the appropriate rationale. Recommend disposition of Type II DNs to Pre-Board with the supporting rationale. Present team activities and significant issues for the Pre-Board. –Pre-Board (PLOT): May Approve, Approve with Changes, or Disapprove Type II DNs. Disapproved DNs will be presented to Pre-Board with appropriate rationale. Recommend disposition of Type I DNs to Board with the supporting rationale. Review Disapproved Type III DNs and recommend disposition to the Board with the support rationale. Summarize Team/Pre-Board activities to Board. –Board (POIF Mgmt Team): Disposition all Type I DNs. Review and disposition all Disapproved Type II and III DNs. Ensure accomplishment of IPLFOR objectives. Splinter meetings will be set up to work any DNs that require more than 5 minutes of discussion during the Pre-board meeting. The Splinter meeting chairman will report back to the Pre-board chairman with a recommendation for disposition for all DNs assigned. DNs that have an ECR in work should be approved pending the approval of the ECR.

6. IPLFOR Review Documentation All PODF ‘Books’ –Manual Crew Procedures - All Procedures per ODF structure and Hazard Control List –Payload Message Files –TV Ops Book –Ground Command Procedures Book (Volume 3 only) –Integrated Payload Safing Procedure –Daily Status Cue Card Payload Planning Products –Activity Definitions (in iURC) –Increment-Specific Groundrules and Constraints Safety Hazard Control Matrix Increment-Specific Payload Flight Rules Increment-Specific Payload Regulations Annex Payload Systems Manual (Volume 3 only) Cadre Ops Verification Procedures POIC Databases, Payload Science and IP Comm Loop Assignments Remote Site Connectivity Status Crew Training Status Simulation Plan EPAS inputs SODF inputs