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.
Project BackgroundLockheed 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 StatementThe full problem statement can be found by following the link here. Highlights from this document which outline our exact goals are as follows:
- Will be used in avionics labs at Lockheed Martin Rotary and Mission Systems
- Externally mounted mechanical device that simulates key-press and touch screen inputs on Multi-Function Display
- Design will use a control board and Graphical User Interface (GUI) to program and perform user-defined actions
- System will be salable, detachable, and lightweight
- Must not cause damage during hard and soft touch tests
- The main goal for our senior design team is to establish a proof of concept that includes development of a functional prototype
- Lockheed Martin RMS Owego (our sponsor)
- Lockheed test engineers (end user)
- Lockheed group maintaining ATLAS (artifact successor)
- Our MSD team and faculty adviser
- Working prototype
- Source code
- All design documents
- User operating manual
- Project poster
First Scenario - Hardware passes ATLAS testThe 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
Second Scenario - Hardware fails ATLAS testBegins 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.
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.
- The system weight is not to exceed 10 lbs
- Minimum MFD size : 6" x 6"
- Maximum MFD size: 24" x 16"
- The system must be able to vary applied pressure
- The system must function in orientations ranging from 0 to 180 degrees.
- The system must be easily scalable with minimal changes to design (length of rails, longer cables, etc).