Previous Abstract Return to Session E8

Session E8: PNT Open Systems Architecture 1

Continue to Benefit from your MOSA Tactical PNT Solutions by Pairing with an Open Test Architecture Solution, Operating in a DevSecOps Environment
Phong Bach, Chris Brechtel, Rosalba Puentes, Kevin Jansen, Kyle Miller, Brett Balazs, Sean Kearney, Collins Aerospace
Location: Room 1-3
Date/Time: Wednesday, Jun. 5, 9:35 a.m.

Collins Aerospace (formerly Raytheon Missiles and Defense) is the prime development contractor for the design, development, integration and testing, and current Software Support Authority of the Navy’s GPS-based Positioning, Navigation, and Timing Service (GPNTS) program, a Modular Open Systems Architecture (MOSA) and Netcentric Enterprise Solutions for Interoperability (NESI) compliant solution. GPNTS is a ship-based navigation data fusion system that receives and processes PNT data from a wide variety of navigation-related sensors on its host platform and distributes the best available PNT data solution in accordance with a variety of defined formats to shipboard PNT user systems. The GPNTS Program of Record, sponsored by the Program Executive Office Command, Control, Communications, Computers & Intelligence (PEO C4I) PMW/A 170 Communications and GPS Navigation Program Office, has been undergoing development, modernization, and sustainment over the last 12 years and has significant lessons learned on what Open Architecture and MOSA compliance means and what values it brings for the DoD. GPNTS’s architecture was designed with the following Quality Attributes in mind:
- Security
- Affordability
- Performance
- Availability
- Interoperability
- Extensibility
- Modifiability
- Modularity
- Usability
- Scalability
The value in developing a MOSA Solution with these Quality attributes are to reduce and improve sustainment for our products, maximize reuse, support rapid scaling and expansion of capabilities, pace the threats and expand the needs of our varying platforms. While this is vital to the success of MOSA compliance for tactical systems, there are also equally vital benefits with coupling them with Open Test Architectures and how together, they become tightly integrated into our DevSecOps pipelines. This further increases the rapid development, test, repeatability, corrective actions, and most importantly, delivery high quality solutions, quickly and continuously to our warfighters.
The GPNTS program needed to address several lessons learned experienced on the baseline program and be more efficient in repeated test events for a wide variety of changes due to obsolescence to pacing PNT threats. The program’s solution was to develop advanced testing capabilities that resolved the following key issues present in the legacy automated test environment:
• Lack of test coverage
• Low % of test reuse
• High maintenance
• Lengthy test conduct and analysis effort
• Late defect discovery
• Automation was for software requirements and software level testing only
• Lacked comprehensive operational and functional testing for happy path requirements-based testing
The new automated test was designed with a Modular Open System Architecture (MOSA) in mind. In addition to addressing the lessons learned and improving test automation, it also:
• Increased productivity and effectiveness throughout development and post-delivery
• Allowed for configurability to support a dynamic software and hardware environment
• Increased comprehensive testing with near real time feedback and debugging capabilities
• Orchestrated test execution of simulators, equipment under test, and data collection
• Supported automated, manual, and hybrid testing for both software and system level testing (white box vs black box)
• Integrated DevOps
This presentation aims to share and discuss the following:
• How the Navy has benefit from the GPNTS Open Architecture solution
• Some of the Automated Test Capabilities gained through the GPNTS Program’s Open Architecture Automated Test Solution
• How the combination of MOSA Tactical Solutions and Open Systems Test Architectures are critical enablers for an effective DevSecOps execution pipeline

Previous Abstract Return to Session E8