P18319: Lockheed ATLAS
/public/

Problem Definition

Table of Contents

Team Vision for Problem Definition Phase

During the problem definition phase, the team planned to establish a solid foundation of the customers requirements and expectations of the prototype. After gathering these customer requirements from a combination of the Project Readiness Package, the team was able to develop applicable engineering requirements that were evaluated based on importance. In addition, a use scenario and a project schedule were developed.

This phase also lead to the development of team expectations including team values and norms.

public/Photo Gallery/Initial Project PRP.JPG

Project Summary

Project Background

Lockheed Martin Owego designs and produces multi-function displays (MFDs) that provides a variety of information to the pilot. They are looking for a device that can be programmed to test the functionality of the hardware repeatedly. Details of this are explained below.
Lockheed's Current Test Method
Currently, testing of MFDs are done by a person who sits in front of the screen and manually presses buttons and observes results in order to know if a hardware test is successful.
Disadvantage of Current Test Method - Why Automate?
A human who is testing the same hardware repeatedly in exhaustive, long-duration testing will eventually tire and see a reduction in performance.
By automating button pressing for the testing of MFDs, there will be a way to confirm that hardware is fully functional with high accuracy and efficiency.
Proposed Solution - What is ATLAS?
ATLAS will be an automated hardware test fixture that is faster and more accurate than a human, especially for exhaustive, long-term testing.

Problem Statement

The full problem statement can be found by following the link here. Highlights from this document which outline our exact goals are as follows:

Stakeholders

Deliverables

Use Scenarios

First Scenario - Hardware passes ATLAS test

The design team creates the hardware and sends it over to the test team for testing. The test team creates a simulation profile which the test technician uses to run simulations. MFD is secured to the ATLAS and the simulation runs. The simulation was successful and the hardware moves on to the customer. The design team fabricates hardware and the test engineering team works to public/Problem Definition Documents/Use Scenario 1 - Test success2.png

Second Scenario - Hardware fails ATLAS test

Begins the same as scenario 1, except the hardware fails. The test technician verifies that the ATLAS is secured correctly and the correct simulation was run before reporting the issue to Test Engineering. public/Problem Definition Documents/Use Scenario 2 - Test failure2.png

Customer & Engineering Requirements

From a combination of the Project Readiness Package and a customer interview, the following customer requirements and engineering requirements have been developed.

public/Problem Definition Documents/RequirementsTraceabilityMatrix.png

Constraints

Benchmarking

public/Problem Definition Documents/Benchmarking 1-4.PNG

public/Problem Definition Documents/Benchmarking 5-8.PNG

House of Quality


Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation