1 / 16

Systems Approach To Effective Diagnostics & Prognostics

Systems Approach To Effective Diagnostics & Prognostics. 07/23/2003. Our Company. 28 YEARS of TECHNICAL SERVICE. A Systems Engineering Approach to Integrated Diagnostics and Prognostics. Requirements Derivation Requirements Flow down Design Development Design Optimization

liana
Download Presentation

Systems Approach To Effective Diagnostics & Prognostics

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. Systems Approach To Effective Diagnostics & Prognostics 07/23/2003

  2. Our Company 28 YEARS of TECHNICAL SERVICE

  3. A Systems Engineering Approach to Integrated Diagnostics and Prognostics • Requirements Derivation • Requirements Flow down • Design Development • Design Optimization • Embedded Systems • Life Cycle Support

  4. Requirements & Architectural Definition System Integration & Verification (SI&V) Deployment & Fielded System Conceptual / IR&D SE Management Development URD & Stakeholder Requirements Technology Refresh / Operational Analysis / Historical Maintenance Data & Analysis Conceptual Design, Support and IR&D Trade Analyses SEMP SEMS SEDS A/B SPECS C/D/E SPECS Project Mgr SSDD ICD TRS System Integration & Verification RFP Contract Program Plan Cost Objectives Systems Engineering Management Requirements And Architecture Definition SDP External Customer Design, ILS Production & Test SI&V PLAN Project Mgr T&E PLANS External Customer Product MGMT DIRECTION & REPORTING Product Characteristics Integrated and Qualified System Staffing & Resource Requirements Technical Program Progress Reports Deployed System System Design Package ILS INTEGRATED LOGISTICS SUPORT RFP REQUEST FOR PROPOSAL SDP SOFTWARE DEVELOPMENT PLAN SEDS SYSTEMS ENGINEERING DETAILED SCHEDULE SEMP SYSTEMS ENGINEERING MANAGEMENT PLAN SEMS SYSTEMS ENGINEERING MASTER SCHEDULE T&E TEST AND EVALUATION URD USER REQUIERMENTS DOCUMENT A SPEC SYSTEM FUNCTIONAL REQUIREMENTS B SPEC ALLOCATED DEVELOPMENT REQUIREMENTS C SPEC PRODUCT FUNCTION/FABRICATION REQUIREMENTS D SPEC PROCESS REQUIREMENTS E SPEC MATERIAL REQUIRMENTS SSDD SYSTEM SEGMENT DESIGN DOCUMENT ICD INTERFACE CONTROL DOCUMENT TRS TEST REQUIREMENTS SPECIFICATION

  5. Performance Risk Defined Validated Performance Level Specified Performance Level Gap • Performance Risk is • Uncertainty in the ability of a design to meet the specified performance level and the consequences thereof • The gap between the validated and specified performance levels and the consequences of that gap • “Performance” is defined broadly to include • Operability, Functionality, Safety, Testability, Affordability, Reliability, • Availability, Maintainability, etc. • Any dimension of value to the customer

  6. Today’s Technology Provides Process Improvement To Fill the Gap • Enhanced Diagnostics Modeling Provides: • Improved Fault Detection Confidence (FD%) • Improved Fault Isolation to Optimum Repair Level (FI%) • Reduced False Alarms / False Removals (FA%) • Lower Mean Time to Isolate (MTTI) • Improved Operational Availability (Ao) • Improved Safety Through Critical Fault Analysis (FMECA) • Reduced Life Cycle Cost

  7. Development Information Model • Topology (Visualization) • Functions (Objects + Nets) • Failure Modes (FMECA) • Test Definitions (Testing) • Diagnostic Strategy • Failure Effects (FMECA) • FMECA Report • Working on DMECA • (Degraded Mode Effect and Criticality Analysis) Topology Functions Failure Modes Test Definitions Diagnostic Strategy Failure Effects FMECA Report

  8. Global Modeling • Electrical • Electronic • Mechanical • Hydraulic • Optical • Software • Process • Fully Hierarchical • Object-Oriented • Networked

  9. Diagnostic Outputs Light Green - partially proven good - not yet suspected Green- proven good Light Blue Stimuli necessary for test Yellow - suspected, in current suspect set Teal - secondary suspects, not in the current suspects set but could be responsible for a previously performed test that failed Dark Red - contains potentially failed components, in AG Light Red - higher level part for which a lower level part is color dark red Dark Blue -I/O Test Point Diagnostic Fault Tree Provides an interactive interface to “exercise” the diagnostics. Provides means to “check” models for validity. Quickly Identifies problem areas (i.e.. Large fault / ambiguity groups) Can be used for Intelligent troubleshooting

  10. FMECA Output

  11. Process Interoperability Embedded Diagnostics & Prognostics Operation and Support Environment Topological Model Prognostics & Failure Trend analysis Prognostics modeling Functional Allocation System Partitioning Maintenance Planning Maintenance Procedures Part Selection Reliability Predictions FMECA/Safety Analysis FMECA Reports FMECA Validation Functional Modeling Test Definition Diagnostic Development Diagnostic Reports Testability / Diagnosability Testability Updates Reliability / Safety Reliability Updates Maintainability Maintainability Updates

  12. Typical Model Types Developed or Supported • Reliability • Provides Data to Diagnostics Models • Functional • Dependency • Failure Mode • Rule Base • Case Base • Model Based Reasoner (MBR) • AI • Prognostic Design Direction Design Assessment Design Optimization Support to Ground Operations Higher Order Run Time Require Developed System Derive Information from Functional, Dependency and Failure Information Support to Optimization Studies

  13. Systems Process at Work • RAH-66 Comanche Program • Boeing-Sikorsky-US Army Diagnostic Design Requirements Analysis Guide (DDRAG) Note: Document contents are export restricted with distribution limited to US Government agencies For Distribution and questions, please contact: Steve Desantis Boeing 610-591-6558 stephen.f.desantis@boeing.com

  14. Systems Process at Work DDRAG Purpose • Comanche Team Desktop Reference • Ensures Standard Processes and Procedures for All Levels of Diagnostics Design Development • Identifies Processes Needed to Define Diagnostics Design Requirements • Equipment • Subsystems • System / Segment • Air Vehicle • External Diagnostics • Defines Operational Flight Program and Off-Board Diagnostics Requirements

  15. Design Process management • All Levels of Design Data and Tools Need to be Interoperable • Tools Need to Support Open Information Architecture • Process Needs to be Managed Through an Integrated Product Development Environment (IPDE) • A Concept Development System was Developed for NASA on the 2nd Gen RLV / SLI Project to Meet the Interoperability Needs • IVHM Systems Management Environment (ISME) • Data Management • Translation between Tools, Data and ISME • Version / Configuration Control • Audit Trail Management • User Control • Security KEEP EVERYONE ON SAME PAGE

  16. Important Enterprise Features TYX Test Interactive Electronic DSI Requirements Technical Manual eXpress™ Document (IETM) TYX Maintenance ® TestBase Vehicle Ground Ops Depot/Vendor Data Collection Gateway Embedded Factory Field Diagnosis & Test Test Health Mgmt.

More Related