1. TEAM Autonomous Remote Routing for Defensive Driving Systems(AR2D2) 1 Contact Information: Thomas DiNetta Lockheed Martin 9500 Godwin Ave Manassas,VA, 22207 thomas.dinetta@lmco.com 703-367-2856 TEAM Red Team Review April 12, 2011

2. TEAM Introduction Evaluate Draft from Customer’s Perspective – RFP Evaluation Criteria – Formal Scoring (Quantitative Assessment) Review Final Draft for Effective Communication – Win Strategies – Approach – Appearance – Readability – Consistency 2 03/15/2011A-Team Proprietary Information – Mock Competition Sensitive

3. TEAM Agenda Win Strategies RFP Evaluation Criteria Technical Volume Summary 3 03/15/2011A-Team Proprietary Information – Mock Competition Sensitive

4. TEAM Win Strategies Flexible – COTS, Open Architecture, Industry Standards, OOP, Modular Reliable – Redundancy, Contingency for failed seekers Proven Components – Use of COTS to reduce development time and budget of new technologies and risk Reduced Footprint – Affordability - Capability packed into a smaller package reducing deployment and storage costs Spiral Development – Ensure transparent progress and minimize complexity of the overall system 4 03/15/2011A-Team Proprietary Information – Mock Competition Sensitive

5. TEAM RFP Evaluation Criteria RFP-Section M The following conditions must be met in order to be eligible for award: – The proposal must comply in all material respects with the requirements of the law, regulation and conditions set forth in this solicitation. – The proposal must meet all solicitation requirements. Ratings (Outstanding, Good, Satisfactory, Marginal, Unacceptable, Deficiency, Strengths, Weaknesses) Weighted Factors (Decreasing Importance) – Systems Overview and Performance – Systems Architecture Requirements Traceability 5 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

6. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 6 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

7. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 7 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

8. TEAM Systems Overview and Performance 8 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

9. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 9 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

10. TEAM Systems Architecture Hardware Design – COTS – Modular – Redundant Batteries 10 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

11. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 11 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

12. TEAM Systems Architecture Software Design FSPPOC 12 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

13. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 13 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

14. TEAM Technical Analysis & System Tradeoffs ComponentEquipment / Design Ultrasonic SensorLEGO NXT Ultrasonic Sensor Color SensorHiTechnic NXT Color Sensor BatteryLiPO Drive TrainTank Drive 14 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive CriteriaMecanumTank Drive4 Wheel2 Wheel Maneuverable+SSS Weight-+-S Acceleration-S++ Size (Small)-+SS SimplicityS+-- Cost (Low)-+-S Flexibility--++ Turn Radius-S+S High Speed Steering --+S +1442 -7231 S1326 ComponentEquipment / Design Ultrasonic SensorSenix TS-21S Distance Sensor Color Sensor Siemens Outdoor Passive Infrared Detector BatteryLi-Ion Drive TrainTank Drive

15. TEAM Technical Analysis & System Tradeoffs AlgorithmDescription Random PathUMV assets take a random direction with each movement opportunity. No BacktrackingUMVs will not backtrack unless no alternative is available Single HistoryUMV assets will take paths that have not been searched previously by itself Preferred DirectionThe UMV assets always move in the direction of the finish if possible UMV Team History The UMV assets will not travel paths searched previously by any vehicle unless no alternative is available 15 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive CriteriaRandom PathNo BacktrackSingle HistoryPreferred Dir Team History Average Seconds Taken / Seconds Required 1846 / 60 30.76 263 / 60 4.38 220 / 60 3.66 90 / 60 1.5

16. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 16 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

17. TEAM Requirements Traceability Iterative Map Building – Provides scheduling Event Driven – Mitigates schedule risk and maximizes field rest benefit Requirements Analysis – Creates technical specifications and quicker product turnaround Requirements Traceability Matrix – Maps requirements to technical specifications, events and software/hardware components to a common area for ease of readability and customer understanding 17 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive REQUIREMENTS TRACEABILITY MATRIX Project Name: Project Manager Name: Project Description: ID Assoc ID Technical Assumption(s) and/or Customer Need(s) Functional RequirementStatus Architectural /Design Document Architectural/Desig n Technical Specification System Component(s) Software Module(s) Test Case Number Tested In Implem ented In Verifica tion Additional Comments

18. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 18 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

19. TEAM Verification and Validation Iterative Testing Plan – Finds problems earlier in development; therefore, faster, affordable fixes Using software simulator to send messages – Validates routing algorithm and message processing early in program 19 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

20. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 20 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

21. TEAM Risks and Opportunities Assessment – Change fundamental design of IED detection – Mitigation – Keep seeker design modular (SW and HW) to allow seamless future enhancements of the system Assessment: Enemy successfully capturing seeker and reverse engineer our solution to gain technology – Mitigation: Utilize data encryption and anti-tamper device which wipes data if not initially disarmed Assessment: Possible to complete other mission types besides safe route finding for HVAs – Capture Plan: Through COTS, open architecture, and modularity, other mission types can include resource scouting and reconnaissance 21 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

22. TEAM Technical Volume Systems Overview and Performance System Architecture – Hardware – Software Technical Analysis & System Tradeoffs Requirements Traceability Verification and Validation Risks and Opportunities Reliability, Maintainability, and Availability 22 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

23. TEAM Reliability, Maintainability, and Availability Creating list of sources of failure COTS and proven performance increases MTBF Modularity, OA, and OOP simplifies maintaining FSP and reducing mean time to support Partnering with component manufacturers increase customer input on component changes 23 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive

24. TEAM Summary 24 03/15/2011 A-Team Proprietary Information – Mock Competition Sensitive