Ron.walsh

19,074 views
19,029 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
19,074
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ron.walsh

  1. 1. Track: Process Makes Perfect Requirements Management Ron WalshProject Manager, Range & Mission Management Office NASA Goddard Space Flight Center/ Wallops Flight Facility PM Challenge 2008
  2. 2. TacSat-2 Launch From NASA WFF • Challenge: 6/20/06: USAF requested that NASA Wallops support the launch the TacSat-2 spacecraft on a Minotaur I launch vehicle in November 2006 by providing: – Launch pad at Wallops – Payload processing facilities – Launch vehicle processing facilities – Range safety – Range instrumentation: telemetry, radar, communications – Weather forecasting – Physical securityPM Challenge 2008 2
  3. 3. Primary Spacecraft: TacSat-2PM Challenge 2008 3
  4. 4. TacSat-2 Arrives at NASA WallopsPM Challenge 2008 4
  5. 5. TacSat-2 mated to Minotaur Stage 4 370 kg spacecraftPM Challenge 2008 5
  6. 6. Secondary Spacecraft: ARC GeneSat GeneSat-1 Flight Article (solar panels removed) 10 inches long PPODPM Challenge 2008 6
  7. 7. Launch Vehicle: Minotaur I • Minotaur I on Wallops Pad 0B • Stages 1 & 2: Minuteman II (M55A1 & SR19) • Stage 3 & 4: Orbital Sciences Corp’s Orion 50 XL & Orion 38 Upper Stack Emplacement on 11/28/06PM Challenge 2008 7
  8. 8. Roll Transfer of Stages 1 & 2 11/7/2006PM Challenge 2008 8
  9. 9. Launch Vehicle: Minotaur IPM Challenge 2008 9
  10. 10. NASA Wallops Wallops Island Main Base Mid-Atlantic Regional Spaceport (MARS) Pad 0BPM Challenge 2008 10
  11. 11. Transportable Grd Station at Coquina, NCPM Challenge 2008 11
  12. 12. Orbital Launches per Yea 19 0 1 2 3 4 60 19 62 19PM Challenge 2008 64 19 66 19 68 19 70 19 72 19 74 19 76 19 78 19 80 19 82 19 84 19 86 19 88 19 90 19 92 19 94 19 96 31 orbital launches between 1960 and 1999 19 98 20 00 20 02 20 04 NASA Wallops Orbital Launches 20 06 20 08 Scout 20 Pegasus 10 Minotaur I Conestoga 12
  13. 13. Importance of Requirements Documents • Formally documents customer’s needs – the “what” of the solution – not the “how” to design that solution • Key input into establishing the system technical baseline • Essential when specific requirements are flowed- down (linked) to: – elements of the system – organizational owners • Provides a traceability path to verify that the design solution satisfies all of the customer’s needsPM Challenge 2008 13
  14. 14. TacSat-2 Customer Requirements Minotaur Minotaur Minotaur TacSat-2 SV WFF Facilities Program START TM Facilities Req. Doc (FRD) Req. Doc (PRD) Collection Plan Req. Doc (FRD) •OSC doc • OSC doc • AF SDTW doc • AF AFRL doc •65 pages •190 pages • 31 pages • 24 pages • UDS Format _______________________ 677 Requirements TotalPM Challenge 2008 14
  15. 15. Requirements Management Database Req. Doc. #1 Req. Doc. #2 Requirements Database of “SHALLS” (Single Electronic File) Req. Doc. #3 Req. Doc #4PM Challenge 2008 15
  16. 16. Requirements Management Tools Word Processor Spreadsheet Specialized Tool Capturing Sorting Linking Tracing Analyzing Ownership Cost Universal AccessPM Challenge 2008 16
  17. 17. Requirements Database Format Requirement No. Page Requirement Verification Ref. Doc. Description Status Responsibility Section Verification Final Value Sub-Field MethodPM Challenge 2008 17
  18. 18. Example of Capturing a Requirement USAF PRD Section 2200, Item #5: All launch vehicle telemetry data and video signals will be transmitted in real-time to the Bldg. W-20 LCR and the RCC (Bldg. E-106) for Range Safety processing and to allow video output to project displays in the Bldg. W-20 LCR, RCC, and to TM Readout. Best source data and video are required to monitor the Minotaur during launch and vehicle flight for all links. The predicted transmitter ON/OFF times are listed below: RF Link Transmitter Transmitter Notes ON Time OFF Time Link 88 LV Telemetry T - 4 hours T - 3 hours Pre-Launch Open Loop RF Checks Link 88 LV Telemetry T - 1 hour T - 50 minutes Terminal Count Open Loop RF Checks Link 88 LV Telemetry T - 30 minutes Loss of Signal Launch Operations Link 40 Video Telemetry T - 30 minutes T + (S3 Separation) Launch Operations Resulting Entry in NASA’s Requirements Matrix: Requirement # Ref Doc Section Page Assigned to Area Comments 360 PRD 7/26/06 2200-05 2-9 Scott Schaire Telemetry WFF shall transmit Minotaur telemetry and video in real- time to Blockhouse 3. 361 PRD 7/26/06 2200-05 2-9 Scott Schaire Telemetry WFF shall transmit Minotaur telemetry and video in real- time to the RCC for Range Safety processing. 362 PRD 7/26/06 2200-05 2-9 Scott Schaire Telemetry WFF shall transmit Minotaur video to Blockhouse 3. 363 PRD 7/26/06 2200-05 2-9 Scott Schaire Telemetry WFF shall transmit Minotaur video to the RCC. 364 PRD 7/26/06 2200-05 2-9 Scott Schaire Telemetry WFF shall transmit Minotaur video to the TM Readout. 365 PRD 7/26/06 2200-05 2-9 Scott Schaire Telemetry WFF shall provide best source data during the launch and vehicle flight. 366 PRD 7/26/06 2200-05 2-9 Scott Schaire Telemetry WFF shall provide best source video during the launch and vehicle flight. 367 PRD 7/26/06 2200-05 2-9 Scott Schaire Telemetry WFF shall receive Minotaur telemetry and video at the times listed.PM Challenge 2008 18
  19. 19. Frequent Requirements Problems • Ambiguous – leads to misinterpretations • Incorrect – system probably will not work • Unnecessary repetition – can lead to contradiction • To restrictive – specifies the “HOW” not the “WHAT’ • Unrealistic - the technology just isn’t there • Inconsistent – not possible to do both • Antiquated – referencing superseded document • Unverifiable – no way to determine the requirement is met • Extraneous information included – not useful • Missing requirements – when are they discovered? • Not freezing requirements – shooting at a moving target • Changing requirements – how to manage?PM Challenge 2008 19
  20. 20. Requirements Management Process Requirements Freeze (After Requirements Freeze (After official signed customer and PRD – V.7/26/06 Customer Documents official signed customer and NASA requirements NASA requirements documents are finalized, and documents are finalized, and FRD – Rev.X4 comment period ends) comment period ends) New Initial Database Database Compilation– Release – Under SE CM Under Project CM Customer Response Customer Response Team members assigned requirement Systems Engineering request Systems Engineering request Team members assigned requirement responsibility (by PM) comment, ask for requirement clarification, and requirement clarification, and responsibility (by PM) comment, ask for clarification and provide aastatus during clarification and provide status during provides feedback to Customer. provides feedback to Customer. Systems Requirements Review. (8/15) Systems Requirements Review. (8/15)PM Challenge 2008 20
  21. 21. Requirement Functional Areas 840 Space . Base Access . Furniture . General . • Six major Janitorial Services . n/a . functional areas, Office Equipment . Command Destruct . Fire/Rescue . 1. Administrative Flight Safety . with 51 sub-fields: Frequency Coordination . FTS . Ground Safety . – 7 Hazardous Waste . Launch Constraints . Material Handling . Administrative Medical . Nitrogen . 2. Mission Health & Safety Non-Hazardous Waste . – 18 H&S Other . Range Safety . Security . – 7 Comm. & Security Classification . Security Officers . Systems Test . Logistics Communications . Data Reduction . – 5 Ground & Logistics . Organizational Relationships . PAO . 3. Communications & Logistics Receiving . Pad Ops. Voice Net . Crane Training . Facilities . – 3 Weather Laboratory . MARS . 4. Ground Support & Pad Operations Minotaur on the Pad . related Launch .down . Weather . Weather Balloons . Launch . 5. Weather – 11 Launch & Payload orbit . Photo . Flight Photo/TV . Radar . RCC . RCC/Video . 6. Launch & Flight Spacecraft . Telemetry . Timing . Trajectory .PM Challenge 2008 21
  22. 22. Detailed Requirement Decomposition • Within the 6 major functional areas, there are a total of 559 sub-field entries. These are under review here.PM Challenge 2008 22
  23. 23. Project Organization NASA Wallops PM Deputy PM Finance & 47 Schedule Institutional Systems Range Launch Area Public Services Communications Safety Engineering Instrumentation (MARS) Affairs & Facilities 30 21 10 494 21 4 50 677 Customer Requirements Tracked & AllocatedPM Challenge 2008 23
  24. 24. NASA Project Life CyclePM Challenge 2008 Ref: NPR 7120.5D NASA Space Flight Program and Project Management Requirements 24
  25. 25. Tailored Project Process Systems Implementation Systems Test Requirements Review Plans Review Review, 8/15/06 9/12/06 10/3/06 Range Facilities Range Readiness Green Card Preparedness Review Rehearsal Test, 10/26/06 11/27/06 12/4/06 Dress Rehearsal Launch 12/5/06 12/11/06 12/16/06PM Challenge 2008 25
  26. 26. Guidance to SRR Presenters Highlight “Shalls” that: • Should be reassigned to others • Are accepted as within my area of responsibility • Need clarification • Contain errors or inconsistencies • Are missing and need to be added • Will be difficult to satisfy • Will be difficult to test compliance • Have high risk to achieve (schedule, cost, or technical) Do not describe intended implementation at the SRR reviewPM Challenge 2008 26
  27. 27. Verification Methods (I-A-D-T) • Inspection • Analysis • Demonstration • TestPM Challenge 2008 27
  28. 28. Mission PatchesPM Challenge 2008 28
  29. 29. Launch: 12/16/06 0700 Local TimePM Challenge 2008 29
  30. 30. Launch Video Video length: 3 minutes & 12 secondsPM Challenge 2008 30

×