Table of Contents
Lockheed Martin Owego designs and produces multi-function displays (MFDs). An MFD is a small screen configured with a mixture of soft keys and touchscreen commands. They are used in aviation to display information to the pilot in numerous configurable ways. Presently, the testing of MFDs is an exhaustive manual task, performed by a human who will eventually tire and thus suffer a reduction in performance. The Avionics Testing Laboratory Automation System (ATLAS) is a testing device that will be used for screening and interacting with MFDs at Lockheed Martin Owego. The ATLAS system will automate hardware testing and ensure high accuracy and efficiency as well.
A prototype of the device was created by a previous RIT senior design team. Details for this project can be found here. This team will work to improve the pre-existing design and add additional features such as a camera for image recognition capabilities. We will analyze the current prototype to identify deficiencies and develop solutions to make the system smaller, faster and more durable.
The goal of this project is to design and implement a functional prototype of the ATLAS system that can be used in the MFD testing process to allow for decreased human intervention and a more efficient testing process. Additional expected deliverables include a comprehensive project poster and technical paper, as well as all relevant technical documents.
Project Goals and Key Deliverables
- A working prototype of the ATLAS system
- Detailed process & design flow documentation
- Test data to support proof of concept
- User Operating Manual
- ImagineRIT Presentation
- Project Poster
- Technical Paper
- Relevant design drawings
Team Vision for Problem Definition Phase
The goal for the problem definition phase is to gain a clear understanding of the project scope and develop a distinct project plan.
- Obtain images, models and other design information about the current state of the device
- Create a list of team values and norms
- Conduct initial customer interview to clarify initial questions and establish an unambiguous project scope
- Review customer needs and use these to define engineering requirements
- Create a summary of project deliverables
- Generate use case scenarios for the ATLAS system
- Define benchmarking parameters and processes
- Develop risks and risk management techniques
- Develop draft of project schedule for phases 1-4
- Coordinate with customer and MSD team for project P19123 to establish a set date to travel to Owego
- Travel to Lockheed Martin site in Owego to meet with the customer and procure ATLAS system
- Our team was able to develop a list of team values and norms as well as two use case scenarios.
- We initially contacted the customer via email with a list of primary questions about the project scope and system. Subsequently, we conducted a phone interview with the customer to clarify any remaining questions and uncertainty. The meeting notes from this interview can be found here.
- We organized the customer requirements based on importance and used this information to define a formal set of engineering requirements.
- Project benchmarking parameters and processes were developed. The ATLAS system was compared to 8 other devices that are currently on the market.
- A draft of the project schedule for phases 1-4 was created, with tasks for each team member established throughout the weeks.
Use CasesThe diagram below illustrates the expected scenarios of operation for the device. The design team creates the MFD hardware and sends it to the testing facilities. The test team creates a test scenario and simulation profile and sends that to the testing facilities for the hardware. The ATLAS is secured to the MFD and the simulation is run. Once the simulation is over, the test technician observes the results and removes the ATLAS. If the test was successful, the hardware is approved and sent to the customer. If the test was unsuccessful, the test technician must verify that the ATLAS was correctly secured. If the ATLAS was correctly secured, the test technician must verify that the correct simulation profile was used. If the correct simulation profile was used, the test technician must remove the ATLAS and report the test results to the test engineering and hardware design teams.
Customer Requirements (Needs)From the customer-generated Project Readiness Package, a draft list of Customer Requirements was created, with a description of the requirements and perceived priority rankings. After talking to the customer, this list was added to and refined. Over the course of the project, this list will be updated with the status of each requirement. Document
Engineering Requirements (Metrics & Specifications)From the list of Customer Requirements, a set of Engineering Requirements was created with quantifiable metrics that our project should meet.
- Project must stay under the budget of $7,500
- Must be compatible with MFD's as small as 6"x9"
- Must be compatible with MFD's as large as 30"x30"
- Must be operational in any orientation from 0 to 180 degrees
- Must utilize Lockheed Martin image recognition software
BenchmarkingIn order to gather relevant information for our project, research was done on devices that serve similar functions. Specifications and design concepts for each device were compiled in the following Benchmark Table. This information will be used for brainstorming design ideas, as well as to compare to our eventual prototype.
House of QualityThe House of Quality (HOQ) is a living document and will be updated as needed as the project progresses.
The HOQ relates Customer Requirements (CR) to Engineering Requirements (ER) and Parameters to establish a baseline for the project. The legend found on the HOQ specifies how strong of a relationship each CR has with each ER.
Plans for next phase
- Travel to Owego
- Analyze current device
- Decide on design path: Modify or Redesign?
The Master Schedule shows work breakdown by phase.