LTEC: Enabling Componentized TESS Procurement using a Service Oriented Architecture Presenter: Phil Sowden

1. LTEC: Enabling Componentized TESS Procurement using a Service Oriented Architecture Presenter: Phil Sowden

2. Outline • Traditional System Based Procurement • PM TRADE Vision: Component Based Procurement • Live Training Engagement Composition (LTEC) • Architecture Overview • How LTEC facilitates component based procurement • Use Cases

3. Traditional System Based Procurement • Currently, the complete TESS system is purchased MILES XXI MILES IWS MILES WITS MILES TVS

4. System Based Procurement Consequences • System component interfaces are proprietary • System software is proprietary • Components don’t interoperate Proprietary TESS Master Controller

5. Problems: System Based Procurement • Product Manager for Live Training Systems (PM LTS) purchases a complete TESS kit • Incumbent vendor difficult to unseat due to proprietary interfaces • Each vendor implements TESS master controller functionality • Results • High sustainment cost • Low competition • Low innovation due to no Government R&D dollars • Dependent on contractors' IR&D funding for innovations • Master controller behaviors aren’t consistent between systems

6. Solution: Component Based Procurement • System component interfaces are open standards • System software is Gov’t owned and reusable MCC Standard

7. Component Based Procurement Details • Product Manager for Live Training Systems (PM LTS) purchases components which interoperate through government managed standards • Vendors re-use government developed TESS master controller software • Results • Lower cost due to re-use and ability to acquire only necessary components • More competition because of published interface standards • Consistent master controller behavior

8. Live Training Engagement Composition (LTEC) Vision • Provide common government owned TESS master controller software • Goals • Reduce development and procurement costs • Integrate with various hardware configurations • Enable adapting quickly to new and changing requirements • Mature and promote interface standards • Enable interoperability between components Crew Interface (UI) Laser Detectors Laser Transmitters TESS Master Controller (LTEC) Weapon Interfaces Signature Devices Power Supply / Battery Surrogates Future / Other

9. LTEC Functional Capabilities LaserTransmitter Crew Interface (UI) Laser Detectors TESS Master Controller • Receives MCC data from MILES laser detector • RTCA • Audio / visual cues • Stimulation of a MILES laser • Linkage to the IS radio • BIT • Control functions Weapon Interfaces Signature Devices Power Supply / Battery Legend Future / Other Currently Supported Surrogates Plan to Support

10. Service Oriented Architecture (SOA) Next • Physical Standard/ICD • SOA Loose coupling between services • Service Capability Definition • Service Business Logic Today • ICD Interface Between two systems or subsystems • Physical • Business • Messages • Processing Responsibilities Higher rates of change Use SOA Application Network Process to Application SOA Presentation Data Representation e.g. Full-Duplex, Simplex, … Stable – Low rates of change Use Standards Session Communications e.g. TCP/IP, … Transport End-to-End Connectivity NetworkLogical Addressing e.g. IPv4, IPv5, … Data LinkPhysical Addressing e.g. MAC, WAN, LAN, … PhysicalPhysical Signal Transmission e.g. RS232, USB, IEEE 802.11 …

11. TESS System using LTEC Legend SOA allows integration with various hardware configurations LTEC Service Main Gun Laser Transmitter LTEC Framework LTEC Messages Government Standard Kill Indicators Visual Cues SAT LTEC Instantiation Vehicle Weapons Interface Stimulator Service #1 Stimulator Service #3 Engagement Simulation Service #1 Engagement Simulation Service #2 User Displays Stimulator Service #4 Sensor Service #1 Stimulator Service #2 Sensor Service #2 LTEC Framework Detectors Data Communication Interface Unit TESS Master Controller

12. LTEC Architecture CAL ensures standards interoperability OSAL enables platform independence • CAL • Contains implementations of government standards • Abstracts protocol details from services • Ensures interoperability - devices that interface with LTEC must comply with standards • OSAL • Abstracts OS dependent functions • Facilitates LTEC platform independence LTEC Composition LTEC Common Core Services IS-TESS Device Services CAL – Communication Abstraction Layer Instrumentation System IS_TESS Protocol • PAN Devices • User Interface • Strobe / Flash (CVKI) • Laser Detector • TSPI Device PAN Device Services PAN Protocol LTEC Core Framework OSAL – Operating System Abstraction Layer Legend LTEC Services LTEC Framework Connection to external Interface External HW/SW Government Standard

13. LTEC Use Cases SOA and OSAL enable support for multiple use cases Appended Dismount Appended Platform Appended/ Embedded Hybrid Embedded Platform & Dismount MILES Sensor PAN I/F MILES Sensor MGT MILES Sensor MGT Dual Use Laser ABCS I/F LTEC Services GPS Indoor Tracking GPS 1553 Bus GPS Platform Bus VKI Victory Bus LTEC Core LTEC Core LTEC Core LTEC Core LTEC Core Operating System OSAL-Lite Linux Windows VxWorks Hardware Platform IWS HCU TVS VKC VDET Vehicle

14. Demonstrated Use Case: LTEC Appended/Embedded Hybrid on Stryker • Goals • Embed MILES capability on Army vehicle using LTEC • Reduce/remove appended hardware • Show hardware dual-use • Communicate through interface standards • Results • Embedded LTEC on Stryker’s Video Display Electronic Terminal (VDET) (dual-use) • Appended MILES XXI detector belts • Removed MILES XXI vehicle control unit • Dual-used Hazard Flashers to provide kill indication • Used PAN Standard for new message comms

15. Demonstrated Use Case: LTEC Appended/Embedded Hybrid on Stryker VDET 2. Laser Detection LTEC 1. MILES Laser 3. Decode and Adjudicate MILES Shoulder Launched Munition 4b. Display Assessment Command 4a. Flash Command Embedded Training SW External Monitor 5. Display Lethality Assessment 6. Turn on/off hazard flashers

16. Demonstrated Use Case: LTEC on Dismount • Goals • Demonstrate LTEC RTCA for Dismounts • Integrate with Integrated Soldier Power and Data System (ISPDS) TESS Android Apps

17. Demonstrated Use Case: LTEC on Dismount Samsung Note I (Android) ISPDS Android Apps LTEC ANDROID Service Messenger Detector Interface PAN USB Detector LTEC Common Core Services IS-TESS Device Services OSAL – Operating System Abstraction Layer CAL – Communication Abstraction Layer IS_TESS Protocol Android Service Messenger PAN Device Services PAN Protocol GUI PAN LTEC Core Framework PU Radio Interface IS-TESS PU Radio RS-232 Legend • Demonstrates ISPDS integration • LTEC runs in an Android App • LTEC interfaces with ISPDS Android Apps through the Android Service Messenger • OSAL provides Android Service Messenger interface • Specific message delivery mechanism for Android OS LTEC Services LTEC Framework Connection to external Interface External HW External SW Government Standard

18. Conclusion • System based procurement has resulted in high sustainment costs • PM TRADE vision: Component Based Procurement • Government owned standards • Common TESS master controller software (i.e. LTEC) • LTEC enables component based procurement • Ensures interoperability between independently developed TESS components • Allows integration with various hardware configurations and use cases • Platform/OS independence allows deployment on multiple hardware platforms • Other LTEC benefits • Reuse provides common behaviors and lowers cost • Allows quickly adapting to changing requirements • Facilitates technology insertion • Demonstrated LTEC use cases • Stryker embedded/appended hybrid • Dismount Android

19. Questions? Phil Sowden, Applied Research Associates psowden@ara.com Gary Hall, General Dynamics Gary.hall@gdc4s.com Jim Grosse, PEO STRI James.grosse@us.army.mil Kyle Platt, PEO STRI Kyle.platt@us.army.mil