Advanced Processing Build (APB)
Abstract
Advanced Processing Builds (APBs) adhere to a four step process: Step 1: Algorithm/technology assessment by peer review panels of Subject Matter Experts (SME) to down-select technologies and assist developers with technical guidance. Step 2: Algorithm/technology testing with open and closed data sets to further down-select and refine capabilities prior to integration and testing. Step 3: Land-based system-level testing stimulated by the Submarine Multi-Mission Team Trainer (SMMTT), in a realistic tactical environment. Step 4: At-sea testing on an operational submarine. APB capability priorities are generated by the Submarine Tactical Requirements Group (STRG), a group of senior post-command officers chaired by a Flag Officer, Commander, Undersea Warfare Development Center (UWDC). Priorities are vetted by COMSUBPAC and COMSUBFOR, then provided as requirement by the Chief of Naval Operations (CNO), OPNAV N97. Program Executive Office Undersea Warfare Systems (PEO UWS) provides Milestone Decision Authority (MDA) oversight and approval. Steps 1 and 2 are conducted in a pipeline style, parallel to system integration and production. This makes Steps 1 and 2 independent of any particular Build (e.g APB-21, APB-23, APB-25, etc.) and allows for development of longer lead technologies. The content of a specific APB build (delivered every two years) is then determined through a series of discussions with the Fleet/STRG aimed at selecting the most relevant and mature technologies available in the APB pipeline. Integration at the string and system level is performed followed by Steps 3 and 4, as applicable, and transitioned to production. Beginning in FY 2019, the Navy has pursued a transformation across Submarine Warfare Federated Tactical Systems (SWFTS) to maximize cyber-resiliency, improve software quality, and improve the speed of capability delivery and software improvements. The transformation is being accomplished through a transition to a process comprised of a continuous series of 12-week software increments in a DevSecOps environment. This process better aligns with industry practice and enables the SWFTS systems to leverage industry capability improvements in software configuration management, quality control, Artificial Intelligence (AI) and Machine Learning (ML) and other emerging technologies, while also being more responsive to cyber needs. As APB delivers via SWFTS, changes are required in the 0223 Project's software development and integration methodologies to remain synchronized with the production programs. Instead of delivering a stand-alone improved APB to the PEO UWS SWFTS production programs at the end of development (which the production program offices then had to integrate, mature, test, and certify), development capabilities are now being integrated into the latest SWFTS production hardware and software baseline as they are ready, on a continuing basis. This speeds release of these capabilities to the Fleet by many months. Step 3 and Step 4 testing regimes will be maintained.
Document Details
- Document Type
- Accomplishment
- Publication Date
- Oct 01, 2024
- Source ID
- a673c58c9c212698a20fb2029f2f3d8e