ECLYPSE The System Engineering Challenges of Implementing an Automatic Wire Analyzer (AWA) System for the Naval Aviation Community 6th Annual Systems Engineering.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Testing Workflow Purpose
CIS 376 Bruce R. Maxim UM-Dearborn
1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Continuous Integration (CI) By Jim Rush Version Control Build Test Report.
PSE&G Condition-Based Maintenance
Organizational & Intermediate Level Wire Tester Acquisitions (FY-07)
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Predictor of Customer Perceived Software Quality By Haroon Malik.
Apache Focused Recapitalization Program National Defense Industrial Association (NDIA) Systems Engineering Conference San Diego, California October 20-23,
LOTUS to SharePoint Migration Services. © 2010 Star Knowledge Technology Team Alliance 2 Key Discussion Points Star Knowledge Value Proposition Microsoft.
Testing Components in the Context of a System CMSC 737 Fall 2006 Sharath Srinivas.
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
QMS, ISO and Six Sigma It’s all related….. QMS Any Quality Management System must satisfy four requirements: Processes must be defined and their procedures.
Wire System Maintenance Reporting Codes Pall B. Arnason Team Leader, Advanced Development Programs Wiring Systems Branch Aging Aircraft IPT / AIR
Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
Software Reliability: The “Physics” of “Failure” SJSU ISE 297 Donald Kerns 7/31/00.
Risk Management of Aircraft Wiring System Oct. 23, 2003 Wayne Boblitt Chuck Singer 6th Annual Systems Engineering Conference.
Group Members: Brad Cox Kevin Burkett Tera Cline Arthur Perkins CS10 Battery Management System.
ATIF MEHMOOD MALIK KASHIF SIDDIQUE Improving dependability of Cloud Computing with Fault Tolerance and High Availability.
An Introduction to AlarmInsight
Motor Management Basics What Needs to be Managed Motor Life Cycle Measuring Motor Reliability Managing Condition Information Data Mining for the big Reliability.
1 CAPACITY BUILDING AND TRAINING ON PROCUREMENT Session 9 – The World Bank Procedures for IT Procurement September 21, 2005 by Arif Hassan.
U. S. Coast Guard Aircraft Repair and Supply Center.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
JVB-STC'97- 1 #*#* Successful Adoption and Use of Object Oriented Technologies STC ‘97 April 30, 1997 Jim Van Buren.
Help Desk System How to Deploy them? Author: Stephen Grabowski.
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Testing Workflow In the Unified Process and Agile/Scrum processes.
How Aircraft Operators Can Benefit from PHM Techniques Big Sky - Montana 2012 IEEE Aerospace Conference Leonardo Ramos Rodrigues EMBRAER S.A., São José.
Overcoming The Challenges Together Fred Brisbois Director, Aviation & Product Safety Sikorsky Aircraft REDUCING THE ACCIDENT RATE.
V&V of COTS RTOS for Space Flight Projects The 1st Annual NASA Office of Safety and Mission Assurance (OSMA) Software Assurance Symposium (SAS) Michael.
Building Dependable Distributed Systems Chapter 1 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Manag ing Software Change CIS 376 Bruce R. Maxim UM-Dearborn.
Reliability & Maintainability Engineering An Introduction Robert Brown Electrical & Computer Engineering Worcester Polytechnic Institute.
Managing Rotorcraft Safety During Frequently Performed Unique Missions September 28, 2005 AHS International Helicopter Safety Symposium 2005 Philip G.
Advisor: Dr. Edwin Jones 1 Client: Paul Jewell ISU Engineering Distance Learning Facility May01-13 Design Team: David DouglasCprE Matt EngelbartEE Hank.
IENG 423 – Designing Decision Support Systems Sample DSS Analysis.
ANKITHA CHOWDARY GARAPATI
1 Improving the Risk Management Capability of the Reliability and Maintainability Program An introduction to the philosophy behind the AIAA S-102 Performance-Based.
Integrating EM QA Performance Metrics with Performance Analysis Processes August 26, 2009 Robert Hinds, Manager, Quality Assurance Engineering & Greg Peterson,
LEADS/EMS DATA VALIDATION IPS MeteoStar December 11, 2006 WHAT IS VALIDATION? From The Dictionary: 1a. To Make Legally Valid 1b. To Grant Official.
Smart Home Technologies
Software Engineering Lecture 8: Quality Assurance.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
ACEC National Energy and Environment Challenges in Asset Management? Brian Long Transmission Line Performance Xcel Energy August 15, 2015.
© SERG Reverse Engineering (Software Maintenance & Reengineering) Software Maintenance Managing the processes of system change.
P15342 Linear RF Measurement System Kate Gunderson Matt Chauncey Will Tourtillotte.
Failure Modes, Effects and Criticality Analysis
Configuration Management
CSCE 548 Secure Software Development Risk-Based Security Testing
System Design, Implementation and Review
Integration Testing.
Summary of Changes to the
The Development Process of Web Applications
Configuration Management
Taming Data Logistics: The Hardest Part of Data Science
Realized Savings to Date: $10M+
IEEE Std 1074: Standard for Software Lifecycle
SALES: HOW TO USE THIS PRESENTATION
Progress in Cockpit-based Dissemination/Display
Software Test Automation and Tools
Quality Measurable characteristic Cyclomatic complexity Cohesion
Exam 1 review CS 360 Lecture 20.
2016 Maintenance Innovation Challenge
M. Kezunovic (P.I.) S. S. Luo D. Ristanovic Texas A&M University
QMS, ISO and Six Sigma It’s all related…..
Presentation transcript:

ECLYPSE The System Engineering Challenges of Implementing an Automatic Wire Analyzer (AWA) System for the Naval Aviation Community 6th Annual Systems Engineering Conference Presented by Brian Cyrier Eclypse International 23 October 2003

ECLYPSE 2 Agenda Background CTTO AWA Program –NAVAIR Goals –Program Objectives System Engineering Challenges –Defining the Requirements –Designing the System –Fielding the System and Support NAVAIR addressing the Challenges AWA System Implementation –Basic AWA System Design –Initial System Hardware –System Software Final Thoughts

ECLYPSE 3 Background Until recently wiring was not considered a maintenance requirement –No periodic maintenance procedures existed that directly addressed wiring –Very little data existed on the failure or repair of wiring –Few tools existed for maintainers to troubleshoot wiring

ECLYPSE 4 Background Why should we care about wiring on U.S. Navy aircraft? –30 months of fleet data shows us 2.5 electrical fires/month 2 aircraft lost due to electrical fires Averaging 1,400 mission aborts/year (540 in-flight aborts/year) 1-2 Million operational man-hours/year spent troubleshooting/repairing wire problems Averaging 120+ Non-Mission Capable aircraft/year –Wiring is the number 2 safety concern of the fleet (Source 2002 Avionics OAG)

ECLYPSE 5 Metrics and Wire Failure Modes Effectively 125 Non Mission Capable Aircraft/Year Due to Wiring Quarterly Metrics Inventory Flight Hours Readiness (NMC) Availability (Aborts) Safety (Mishaps) Reliability (MTBF) Maintainability (MMH) Supportability (MFHBCC) O&S Costs (M&S Costs)

ECLYPSE 6 CTTO AWA Program NAVAIR Goals –Research, Development, Test and Evaluation of technology for the localization of hard faults and degenerative conditions Hard faults: opens and shorts Degenerative conditions: chafing, cracks, material decomposition, corrosion, water intrusion Branching circuits –Commercial technology adaptation for military applications User interface and maintenance database interface Open system architecture Specification development for out-year procurements

ECLYPSE 7 CTTO AWA Program Program Objectives –Improve the Navy’s ability to test and troubleshoot aircraft wiring systems at all maintenance levels. –Reduce operational and logistical costs associated with wiring malfunctions. –Identify and document maintenance requirements necessary to meet the first two objectives. –Evaluate AWA Technology primarily for use at the Depot level, to include IMC applications –Investigate for use at Intermediate maintenance levels.

ECLYPSE 8 Program Objectives –Mature the AWA technology and associated ILS to evolve the AWA into a viable solution for fleet testing, troubleshooting and prognostication of aircraft wiring systems. –Through coordination with all participating commands, formulate an effective acquisition strategy to procure AWA technology equipment CTTO Program

ECLYPSE 9 System Engineering Challenges Defining the Requirements –The Needs of O,I and D level maintenance vary greatly, defining a system that benefits all with minimum compromise is difficult –Process and procedure differences exist between the depots on reporting and data collection –Data on wiring maintenance is often reported at a subsystem level and detailed particulars are often lost

ECLYPSE 10 Designing the System –State of the Technology Technology to Detect Hard faults continues to improve Technology to locate Hard fault is improving Technology to detect degenerative conditions is limited Technology to locate degenerative conditions is in its infancy No one technology or tool is the silver bullet to cure all System Engineering Challenges

ECLYPSE 11 Fielding the System and Support –Maintenance procedures for the inspection of wiring is primarily visual at the various levels of maintenance –At O and I Levels of maintenance; problems are isolated to black boxes (remove and replace); rarely to wiring unless there is visible damage –Approximately $94 Million spent on no-fault found equipment removals due to undiagnosed wiring problems –Wiring is not viewed as the problem until all else fails System Engineering Challenges

ECLYPSE 12 NAVAIR Addressing the Challenges Process improvements being implemented by NAVAIR to change the current maintenance culture as it relates to wiring –Maintenance Manual improvements (505 Manual) –Work Unit Code (WUC) and Malfunction Code (MAL codes) improvements –Training Improvements for the Technicians –AWA System Deployment

ECLYPSE 13 AWA System Implementation Hardware –Existing Commercial Off-the-Shelf Technology Electrical Analyzer Systems for Fault Detection Standing Wave Reflectometry for Fault location and waveform analysis Software –Customized package of programs designed to interface with COTS Hardware, improve wiring maintenance and insure consistent collection of wiring fault and measurement data

ECLYPSE 14 Basic AWA System Design AWA Operating System AWA Database COTS Hardware COTS Hardware COTS Hardware

ECLYPSE 15 Initial System Hardware USES DIRECT CURRENT VOLTAGES AND CURRENTS –MULTIPLE TEST PROTOCOL PER WIRE PATH –NON-DESTRUCTIVE BASIC CHECKS FAST/AUTO –OPENS (ISOLATION) –SHORTS (CONTINUITY) –4-WIRE KELVIN –INSULATION TESTS CONTROL LOADING PROCEDURE/MENU DRIVEN DETERMINE WHICH PATH IS BAD RTS 501 Electrical Analyzer System

ECLYPSE 16 Initial System Hardware USES NASA PATENTED STANDING WAVE REFLECTOMETRY MULTIPLE FREQUENCY TEST PROTOCOL PER WIRE PATH –NON-DESTRUCTIVE BASIC CHECK IS FAST/AUTO –OPENS (ISOLATION) –SHORTS (CONTINUITY) –DISTANCE IN FT/INCHES OR METERS/CM OR ALL INCHES –SOME WAVEFORM ANALYSIS CAPABILITY PROCEDURE/MENU DRIVEN DETERMINE DISTANCE TO FAILURE ALONG PATH ESP Standing Wave Reflectometer

ECLYPSE 17 System Software User friendly operator interfaces –Common windows environment –Presentation designed for an 18 year old age group Automated AWA Test Program Set development utilities to insure consistent protocols and results capture Open system architecture to allow utilization of other measurement Technologies Utilities to interface with existing Navy maintenance databases – NALCOMIS - Maintenance Database –AWIS - Electrical Component and Tool information –MRPII - Depot Resource Planning Development of an Aircraft wire configuration validation tool (Mapping Automation)

ECLYPSE 18 Final Thoughts Maintenance needs to move from a reactive to proactive posture relative to wiring Wiring needs to be treated as an aircraft system versus a “fit and forget” commodity Conclusion The NAVAIR initiative coupled with the AWA system deployment is the first step in providing the means to meet these objectives

ECLYPSE 19 Brian Cyrier Eclypse International Corporation (909) Ext.: 27