1 / 66

Miscellaneous Risk Topic

Miscellaneous Risk Topic. Concurrency* Risk Management. DT&E Completion. Concurrency. Degree of Concurrency. > 67% 33 to 67 < 33 % 0. Low Moderate High Very High. Risk Handling Imperatives for Concurrent Programs Insure Adequate Test Resources Are Available

karl
Télécharger la présentation

Miscellaneous Risk Topic

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. Miscellaneous Risk Topic

  2. Concurrency* Risk Management DT&E Completion Concurrency Degree of Concurrency > 67% 33 to 67 < 33 % 0 Low Moderate High Very High • Risk Handling Imperatives for Concurrent Programs • Insure Adequate Test Resources Are Available • Have Rapid Corrective Action Process Established • Have Effective Transition to Production Process • Phase Production to Allow for Early Testing • Use Modular Designs When Retrofits Are Expected * Overlap between Development Test & Evaluation and Production

  3. Past Problems with DoD Weapons Systems Due to Requirements Development Practices Characterization of Past Practices 1. Vertical Flowdown Has Often Failed to Address All Products and Processes. This Has Resulted in Premature Selection of Design Features That Provided Little Additional Benefits for the Costs Incurred 2. Weapon System Requirements Have Not Been Developed in an Integrated Fashion (i.e., the Definition and Balancing of All Related Items at All Levels) Future Need • All Requirements Should Be Addressed and Subsequent Design Solutions Should Be Integrated and Verified Both Vertically and Horizontally

  4. Objectives of Requirements Analysis • Articulate Customer Needs • Missions • Environments • Identify and Allocate Constraints • Design • Cost • Schedule • Develop and Define Measures of Effectiveness • Functional • Performance

  5. Requirements Analysis Process Supplier “Hows” Design Features/ Performance Measures “Customer Wants” Needs Identification 1. Close Air Support 2. Deck Launched Intercept Prioritization of Customer “Wants” 1. Cost 2. Supportability 3. Mission Effectiveness Utility/Relationship Matrix Measures How Well “Wants” are Met. Key Tasks: 1. Identify Operational and Environmental Needs 2. Identify Customer Preferences 3. Prioritize Importance of Design Features Sensitivity to Design Features Prioritization of Relative Importance of Changes in Design Features

  6. Requirements Analysis Timeflow Customer Requirements Systems & Operational Analysis Analysis Needs & Objectives • Requirement Categories • Defined • - Affordability • - Sortie Generation • - Target Kills • Technologies Identified • by Category • Preliminary Ranking of Technologies by Category • Preliminary RankingAcross Categories Preliminary Assessments - Effectiveness - Force Structure - Cost/Risk Customer Reaction

  7. Preliminary Ranking of Technologies/Configurations Sort Systems in Each Category by Cost Sort Systems in Each Category by Effectiveness Increment Budget Determine Affordable Systems With Given Budget Estimate Configuration Effectiveness Based on Mission Effectiveness Results Cost Effective Technology/Configuration (for given budget) Determine Optimum Configuration at This Budget Level Approach Explores All Combinations of Options and Determines the Most Effective Technology or Configuration at Each Budget Level

  8. Quantifying A/C Requirements Impact on Force Structure Reasonable Requirements Region ATS Unit Eff. Unit Eff Too Small #s Purchased Too Small ATS Radar Detection Range Air Wing Effectiveness ATS Proc. Quan ATS Radar Detection Range Detection Range

  9. Example - Determining TechnicalPerformance Measures for Multirole Aircraft.

  10. Sample Multi-Role Aircraft Requirements Warfare Objectives to Be Achieved Top-Level Multi-Role Aircraft Requirements Identification Massive Firepower In-Theater “At a Pace and in Numbers Sufficient to Field an Over-Whelming Force” 1. In-theatre Sortie Generation 2. Supportable 3. Kill Armored Vehicles 4. Destroy Critical Chokepoints 5. Destroy Enemy Aircraft in Air and on Ground 6. Destroy Enemy Air Defenses 7. Reconstitutable Direct Support of the Ground Campaign “Slow the Enemy’s Offensive Temp until Friendly Ground Forces Can Mass and Counter the Advance” Establish Air Superiority “Denying the Enemy Use of His Airpower and Defenses” Reconstitution “The ability to Reconstitute a Credible Defense Faster Than Any Potential Opponent Can Generate an Over-Whelming Offense”

  11. Technical Performance Measuresthat Impact In-Theater Sortie Generation • Airlift Loads/Squadron • Airlift Lbs/Squadron • Vulnerable Area • 24 Hour Repairability • Lbs of Expendables Per Sortie Aircraft Available In-Theater • Taxi Speed • Shelter Park Time • Alert Time • Integrated Combat Turn Time • Mission Initialization Time • Break Rate • Ground Abort Rate • Fix Rate • Mean Repair Time Sorties Per Day Per Aircraft Available

  12. Technical Performance Measuresthat Impact Supportability Maintenance Personnel • Maintenance Manhours Per Flight Hour • Average Skill Level Required • Number of Special Skills Required • Break Rate • Maintenance Manhours Per Flight Hour • Flyaway Cost • Mean Fuel Consumption Per Flight Hour • System Weights Cost of Consumables • Break Rate • Maintenance Manhours Per Flight Hour • System Weights Depot Maintenance Cost

  13. Technical Performance Measures thatImpact Armored Vehicles Killed • Takeoff Distance • Landing Distance • Takeoff Ground Roll • Landing Ground Roll • Airlift Loads/Squadron • Airlift Lbs/Squadron • 24 Hour Repairability • Lbs of Expendables Per Sortie • Taxi Speed • Shelter Park Time • Alert Time • Integrated Combat Turn Time • Mission Initialization Time • Break Rate • Ground Abort Rate • Fix Rate • Mean Repair Time In-Theater Sortie Generation Targets Acquired Per Sortie • Range • Loiter Time • Max Detection Range • Max Recognition Range • Navigation System Error • Nite/Wx Capability

  14. Technical Performance MeasuresImpact Armored Vehicles Killed • Deliverable Weapon CEP • Max Number of Air-to-Ground Weapons • Type/Mix of Air-to-Ground Weapons • Targeting Azimuth Limits • Targeting Elevation Limits Targets Destroyed Per Attack • Instantaneous Gs At Combat Conditions • Sustained Gs At Combat conditions • Mil Power Penetration Speed • Ps At Combat Conditions • Acceleration Times at Combat Weight • Time to Bank 90 degrees • Instantaneous Turn Rate • RCS • IR Signature • Visual Signature • Vulnerable Area • Standoff • Threat Sort/Identification Time Aircraft Lost Per Sortie

  15. Technical Performance Measures that Impact Vehicle Flow Rate Reduction in Critical Choke Points • Takeoff Distance • Landing Distance • Takeoff Ground Roll • Landing Ground Roll • Airlift Loads/Squadron • Airlift Lbs/Squadron • 24 Hour Repairability • Lbs of Expendables Per Sortie • Taxi Speed • Shelter Park Time • Alert Time • Integrated Combat Turn Time • Mission Initialization Time • Break Rate • Ground Abort Rate • Fix Rate • Mean Repair Time In-Theater Sortie Generation Targets Acquired Per Sortie • Range • Loiter Time • Max Detection Range • Max Recognition Range • Navigation System Error • Nite/Wx Capability

  16. Technical Performance Measures that Impact Vehicle Flow Rate Reduction in Critical Choke Points (cont.) • Deliverable Weapon CEP • Max Number of Air-to-Ground Weapons • Type/Mix of Air-to-Ground Weapons • Targeting Azimuth Limits • Targeting Elevation Limits Targets Destroyed Per Attack • Instantaneous Gs At Combat Conditions • Sustained Gs At Combat conditions • Mil Power Penetration Speed • Ps At Combat Conditions • Acceleration Times at Combat Weight • Time to Bank 90 degrees • Instantaneous Turn Rate • RCS • IR Signature • Visual Signature • Vulnerable Area • Standoff • Threat Sort/Identification Time Aircraft Lost Per Sortie

  17. Technical Performance Measures that Impact Destruction of Enemy Aircraft in the Air • Takeoff Distance • Landing Distance • Takeoff Ground Roll • Landing Ground Roll • Airlift Loads/Squadron • Airlift Lbs/Squadron • 24 Hour Repairability • Lbs of Expendables Per Sortie • Taxi Speed • Shelter Park Time • Alert Time • Integrated Combat Turn Time • Mission Initialization Time • Break Rate • Ground Abort Rate • Fix Rate • Mean Repair Time In-Theater Sortie Generation Destroy Enemy Aircraft in Air and on Ground Targets Acquired Per Sortie • Range • Loiter Time • Max Detection Range • Max Recognition Range • Navigation System Error • Nite/Wx Capability

  18. Technical Performance Measures that Impact Destruction of Enemy Aircraft in the Air (cont.) • Deliverable Weapon CEP • Max Number of Air-to-Ground Weapons • Type/Mix of Air-to-Ground Weapons • Targeting Azimuth Limits • Targeting Elevation Limits Targets Destroyed Per Attack • Instantaneous Gs At Combat Conditions • Sustained Gs At Combat conditions • Mil Power Penetration Speed • Ps At Combat Conditions • Acceleration Times at Combat Weight • Time to Bank 90 degrees • Instantaneous Turn Rate • RCS • IR Signature • Visual Signature • Vulnerable Area • Standoff • Threat Sort/Identification Time Aircraft Lost Per Sortie

  19. Technical Performance Measures that Impact Aircraft Destroyed on the Ground • Takeoff Distance • Landing Distance • Takeoff Ground Roll • Landing Ground Roll • Airlift Loads/Squadron • Airlift Lbs/Squadron • 24 Hour Repairability • Lbs of Expendables Per Sortie • Taxi Speed • Shelter Park Time • Alert Time • Integrated Combat Turn Time • Mission Initialization Time • Break Rate • Ground Abort Rate • Fix Rate • Mean Repair Time In-Theater Sortie Generation Targets Acquired Per Sortie • Range • Loiter Time • Max Detection Range • Max Recognition Range • Navigation System Error • Nite/Wx Capability

  20. Technical Performance Measures that Impact Aircraft Destroyed on the Ground • Deliverable Weapon CEP • Max Number of Air-to-Ground Weapons • Type/Mix of Air-to-Ground Weapons • Targeting Azimuth Limits • Targeting Elevation Limits Targets Destroyed Per Attack • Instantaneous Gs At Combat Conditions • Sustained Gs At Combat conditions • Mil Power Penetration Speed • Ps At Combat Conditions • Acceleration Times at Combat Weight • Time to Bank 90 degrees • Instantaneous Turn Rate • RCS • IR Signature • Visual Signature • Vulnerable Area • Standoff • Threat Sort/Identification Time Aircraft Lost Per Sortie

  21. Technical Performance Measuresthat Impact Air Defenses Operating • Takeoff Distance • Landing Distance • Takeoff Ground Roll • Landing Ground Roll • Airlift Loads/Squadron • Airlift Lbs/Squadron • 24 Hour Repairability • Lbs of Expendables Per Sortie • Taxi Speed • Shelter Park Time • Alert Time • Integrated Combat Turn Time • Mission Initialization Time • Break Rate • Ground Abort Rate • Fix Rate • Mean Repair Time In-Theater Sortie Generation Targets Acquired Per Sortie • Range • Loiter Time • Max Detection Range • Max Recognition Range • Navigation System Error • Nite/Wx Capability

  22. Technical Performance Measures that Impact Air Defenses Operating • Deliverable Weapon CEP • Max Number of Air-to-Ground Weapons • Type/Mix of Air-to-Ground Weapons • Targeting Azimuth Limits • Targeting Elevation Limits Targets Destroyed Per Attack • Instantaneous Gs At Combat Conditions • Sustained Gs At Combat conditions • Mil Power Penetration Speed • Ps At Combat Conditions • Acceleration Times at Combat Weight • Time to Bank 90 degrees • Instantaneous Turn Rate • RCS • IR Signature • Visual Signature • Vulnerable Area • Standoff • Threat Sort/Identification Time Aircraft Lost Per Sortie

  23. Technical Performance MeasuresImpact Time To Reconstitute Force Cost of Reconstitution • Weapon System Unit Cost • Mean Cost to Remanufacture • Long-Lead Time • Time to Manufacture/Assemble • Interchangeability • Mean Time to Remanufacture • Service Life Manufacturing Time

  24. Multi-Role Aircraft System LevelTechnical Performance Measure List • Takeoff Distance • Landing Distance • Takeoff Ground Roll • Landing Ground Roll • Airlift Loads/Squadron • Airlift Lbs/Squadron • 24 Hour Repairability • Lbs of Expendables Per Sortie • Taxi Speed • Shelter Park Time • Alert Time • Integrated Combat Turn Time • Mission Initialization Time • Break Rate • Ground Abort Rate • Fix Rate • Mean Repair Time • Range • Loiter Time • Max Detection Range • Max Recognition Range • Navigation System Error • Nite/Wx Capability • Deliverable Weapon CEP • Max Number of Air-to-Ground Weapons • Type/Mix of Air-to-Ground Weapons • Targeting Azimuth Limits • Targeting Elevation Limits • RCS • IR Signature • Visual Signature • Vulnerable Area • Standoff • Threat Sort/Identification Time

  25. Multi-Role Aircraft System LevelTechnical Performance Measure List • Instantaneous Gs At Combat Conditions • Sustained Gs At Combat conditions • Mil Power Penetration Speed • Ps At Combat Conditions • Acceleration Times at Combat Weight • Time to Bank 90 degrees • Instantaneous Turn Rate • Maintenance Manhours Per Flight Hour • Average Skill Level Required • Number of Special Skills Required • Mean Fuel Consumption Per Flight Hour • Flyaway cost • System Weights • Weapon System Unit Cost • Mean Cost to Remanufacture • Long-Lead Time • Time to Manufacture/Assemble • Interchangeability • Mean Time to Remanufacture • Service Life

  26. Requirements Handoff - Capturing New Business

  27. Requirements Handoff For Contract Work BV41791

  28. Sample TPM Warning and ActionThresholds Action Threshold System Weight Warning Threshold x x x x x x Requirement Milestones TIME Requirement x x x x System Range x x Warning Threshold Action Threshold x - Predicted Value Milestones

  29. Requirements Tracking

  30. Function Decomposition is Taken to aLevel Sufficient to Drive System Synthesis • System Synthesis • System Concept • Architecture • Conf. Item Def. • Phy. Interfaces • Alternative Solutions Functional Decomposition (System Functions {development, operations, etc} to Segments to Individual Functions) F1, F2, F3... • Systems Analysis • & Control • Trade-Offs • Effect Analyses • Life Cycle Cost • Risk Management • TPMs • Technical Reviews • Documentation Data Base • Decision Support Data • System Architecture • System Specification

  31. Example Functional Decomposition Primary Functions Development Manufacturing Verification Deployment Operations Support Training Disposal Cruise/ Ingress Loiter Climb Commit/ Engage Wpn Del Egress Pre-flight Taxi Takeoff Escort RTB CAP Post-Fit Each Individual Function Must Be Assigned An Owner

  32. Functional Requirements are Owned by IPD Teams Operations Functions Avionics IPD Team Pre- Flight Commit/ Engage Post- Flight • Constraints: • Cost Analysis/Allocation • Weight Analysis/ Allocation • Rel. & Main Analysis • Other ... ... F1 - Search F2 - Detect F3 - Identify F4 - Designate F5 - Track

  33. Requirements Should Be BaselinedBut Plan For Change Requirements will Change, but Baselines put You in Control. • Requirements Baselines: • Insure a Common Understanding Within the Development Group of the “Current” Set of Requirements (What’s In, What’s Not) • Provide a Basis for Evaluating the Effects and Impacts of Proposed Changes • Allows Grouping Changes in Blocks to Minimize Rework Always Include Changes in Budget and Schedule Planning.

  34. Requirements Characteristics • Unambiguous - Every Requirement Has Only One Interpretation • Complete - Includes All Significant Requirements, Functions, Behaviors, Performance, Constraints, and Interfaces • Verifiable - Cost-Effective Means Exists for People or Machines to Check Product Against Requirements • Consistent - Requirements Not in Conflict • Modifiable - Requirements Are Easy to Change Completely and Consistently • Correct - No Errors Exist That Will Affect Design • Traceable - Origin of Requirement is Clear • Design Free - Design Is Left to the Designer

  35. Software Requirement Issues Issues Attributes Performance Constraints Usability Interfaces Reliability Supportability Bits Processed, Speed, Response Time Standards, Data Format, Language Ease of Use, Consistency, Ease of Training, Input Preparation, Output Interpretation Software, Hardware, People Frequency of Failure, Severity of Failure, Recovery From Failure Ease of Upgrade, Ease of Repair, Instability, Expandability, Testability, Flexibility, Portability

  36. Example of Design-Dependent andDesign-Free Requirement • Design-Dependent: The Flight Control System Shall Be Quad-Redundant for Safety Problem - Redundancy Was Dictated without Getting to Fundamental Requirement • Design-Free: No Combinations of Failures within the FLCS, with a Probability of Occurrence Greater Than 10 to 7, Shall Result in a Category 1 Hazard. The Redundancy Level Will Be Determined by Analysis and Trades of Different Redundancy Architectures, MTBFs of Hardware and Allocation of Functions to Hardware and Software During the Design Phase

  37. Example of a Verifiable Requirement • Non-Verifiable: A Single Failure (of the FLCS) Shall Result in Minimal Transients • Verifiable: A Single Failure Shall Result in Less Than +/- 1g’s Normal or Lateral Axis

  38. Example of Requirements Allocation,Traceability and Decomposition • Parent Requirement from Weapon System Spec: • WSS102004: The Weapon System Shall Be Designed to Promote Operational Personnel Safety • One Child Requirement to WSS102004 in Air Vehicle Spec: • AVE31550: The Diagnostic Function Shall Provide Built-in Logic to Promote Personnel Safety for all Tests • One Child Requirement to AVE31550 in Vehicle Management System Spec: • VMS01380: Initiated Built-in Test (IBIT) Shall Not Be Enabled Until Multiple Interlocks are Satisfied • One Child Requirement to VMS01380 in Flight Control System SW Spec: • FLC13790: FLCS Software Shall Only Allow IBIT to Be Engaged When Weight is on Wheels and Wheel Gear Tachs < x Knots and Engine Thrust is Below Flight Idle and IBIT Engaged Switch is Selected

  39. The Need for Automated Requirements Management • System Engineers Need It • Large numbers of requirements (along with the availability of computer hardware and software tools) makes computer automation very beneficial • Answering customer requirement queries will be easier and more defendable • Communication within the design team will be enhanced • Some Programs Require It (Customer Mandate) • Benefits of ARM Approach • Technical Performance Measures tracking/management • Rapid response for management and analysis • Standard views, reports, analyses available • Multi-user access with configuration controls • Complete traceability of requirements - Reqts hierarchies - Reqts histories - Open Issues - Allocation to design elemnets - Verification methods - Response organizations

  40. Need and Enabling Technologies Pointto Implementing Automated Requirements Tracking Requirements Automation Changing Requirements Specialization in Workplace Distributed Processing Hardware Requirements Tracking Software Distributed Data Entry With Update Under Configuration Control Will Allow Specialists From Different Disciplines to Work Efficiently as a Team.

  41. Reasons to Use a Requirements Tracking Tool • Customer Requests for Changing Requirements CanBe Fully, Accurately, and Efficiently Addressed (Allow for Reasonable Requirements Evolution) • Enhances Internal Communications within and AcrossManagement, Engineering, Production and Support Functions • Provides “Corporate Memory” for Future Projects • F-22 Customer Required Top-Down and Bottom-UpRequirements Tracking Capability to Better Address Cost Issues

  42. Requirements Data Base Environment

  43. Sample Weapons System RequirementsDatabase (common data) Number Type Statement Owner Development, Manufacturing, Verification, Deployment, Operations, Support, Training, or Disposal Text statement IPT (or name)

  44. Sample Weapons System RequirementsDatabase (common data Cont. 1) WBS Parent Req. Child Req. Element Number Number Identifier

  45. Sample Weapons System RequirementsDatabase (common data Cont. 2) Associated Trade Studies Related TPMs TPM Names Notes Trade Study Identifier Text

  46. Sample Weapons System RequirementsDatabase (unique data by WBS) • Development: Cost, Schedule (Hardware, Software, • Facilities, Data, Materials) • Manufacturing: Primary Technology, Alternate Technology • (Availability, Cost, Risk) • Verification: Method, Description, Date • Operations: Performance Threshold, Performance Objective, • Weight, Space, Power, Cooling • Support: MTBF, Inspection Cycle, Spares Investment $, • Support Equipment Req. • Training: ... • Disposal: ...

  47. Sample Weapons System RequirementsDatabase (unique data by WBS Cont. 1) Software: - Performance (bits processed, speed, response time) - Constraints (standards, data format, language) - Interfaces (software, hardware, people) - Reliability (freq. of failure, severity of failure, recovery of failure) - Supportability (diagnostics, portability)

  48. Requirements Tracking Software Tools&Sample Trade Study

  49. ARM Comparative Ratings (Performance Capabilities Category) SLATE (1Q94) RDD-100 (Ver 4.0) RTM (Ver 2.1) Wt. Decision Criteria 1. Weights used were 1,2, & 3 with 3 being best. 2. Utility scores used varied from 0 to 10 with 10 being the best.

More Related