1 / 24

Autonomous Remote Routing for Defensive Driving Systems(AR2D2)

This review assesses the AR2D2 system from a customer's perspective, evaluating RFP criteria, scoring, and communication effectiveness. It includes win strategies, approach, appearance, and consistency, focusing on flexible, reliable, and cost-effective solutions. Technical evaluations cover system overview, architecture, traceability, and risk mitigation. Proprietary information aids in the strategic development and evaluation process. Requirements traceability enhances scheduling, risk mitigation, and product development. Contact Thomas DiNetta for further information.

tyra
Download Presentation

Autonomous Remote Routing for Defensive Driving Systems(AR2D2)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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 A-Team Proprietary Information – Mock Competition Sensitive

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

  4. 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 A-Team Proprietary Information – Mock Competition Sensitive

  5. RFP Evaluation Criteria • RFP-Section MThe 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 A-Team Proprietary Information – Mock Competition Sensitive

  6. 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 A-Team Proprietary Information – Mock Competition Sensitive

  7. 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 A-Team Proprietary Information – Mock Competition Sensitive

  8. Systems Overview and Performance A-Team Proprietary Information – Mock Competition Sensitive

  9. 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 A-Team Proprietary Information – Mock Competition Sensitive

  10. Systems Architecture • Hardware Design • COTS • Modular • Redundant • Batteries A-Team Proprietary Information – Mock Competition Sensitive

  11. 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 A-Team Proprietary Information – Mock Competition Sensitive

  12. Systems Architecture Software Design FSP POC A-Team Proprietary Information – Mock Competition Sensitive

  13. 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 A-Team Proprietary Information – Mock Competition Sensitive

  14. Technical Analysis & System Tradeoffs A-Team Proprietary Information – Mock Competition Sensitive

  15. Technical Analysis & System Tradeoffs A-Team Proprietary Information – Mock Competition Sensitive

  16. 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 A-Team Proprietary Information – Mock Competition Sensitive

  17. 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 A-Team Proprietary Information – Mock Competition Sensitive

  18. 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 A-Team Proprietary Information – Mock Competition Sensitive

  19. 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 A-Team Proprietary Information – Mock Competition Sensitive

  20. 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 A-Team Proprietary Information – Mock Competition Sensitive

  21. 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 A-Team Proprietary Information – Mock Competition Sensitive

  22. 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 A-Team Proprietary Information – Mock Competition Sensitive

  23. 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 A-Team Proprietary Information – Mock Competition Sensitive

  24. Summary A-Team Proprietary Information – Mock Competition Sensitive

More Related