FORGE_SpEC_charts_8_Jan_18.pdf

• What - Requirements

• Who – Industry

• Why – Growing System Capabilities

• When – Schedule

• Where – DevOps

• How - Overall Approach

• One-On-One Information

What - Requirements

• FORGE Mission Data Processing (MDP) modernizes existing system

• MDP must be designed to quickly respond to evolving missions

• MDP must provide modular, scalable, and cyber resilient Open

Architecture solution

• FORGE MDP must fulfill requirements

• SBIRS 1996 Operational Requirements Document (ORD)

• OPIR Capabilities Development Document (CDD)

• Battlespace Awareness (BA) / Technical Intelligence (TI) requirements

• FORGE MDP will consist of two separate efforts

• FORGE Mission Data Processing Application Framework (MAF) must provide foundation for all of the MDP application requirements and lead MDP integration (First OTA)

• FORGE Mission Data Processing Application Provider must provide the applications and software architecture to perform OPIR mission processing and support integration to the framework

MAF Prototype is the ONLY Focus of this OTA 2

Notional Architecture

Who - Industry

• DoD contractors have traditionally provided complete OPIR warfighter capabilities

• Non-traditional contractors have developed new and innovative approaches to solving problems

• Government has determined that a DoD/non-traditional team would most likely provide the best solution

• MAF roles and responsibilities for the entire effort (described in the table) have initially be defined

Notional Roles

Why – Growing System Capabilities

• Current architecture designed to handle specific vehicles/payload for a defined constellation

• Current system developed to meet existing specific requirements

• Further exploitation is desired from current OPIR assets

• Cyber requirements have become more rigorous

• OPIR CDD will drive new system capabilities

When - Schedule

• Award at least 2, no more than 3, prototype contracts based on responses

• Assess prototypes utilizing quarterly delivery acceptance criteria

• Phase 1 prototyping effort is 9 months – funded incrementally

• Phase 2 prototyping effort is 6 months – funded incrementally

• Potentially reopen competition if Phase 1 prototypes are inadequate

• Update Phase 1 prototypes based on MAP contractor feedback

• Incremental quarterly funding is based on previous quarter performance (for both phases)

Notional Schedule5

Where - DevOps

• Government expects contractor to utilize Agile development methodology for final FORGE MDP development effort, not prototype

• MAF prototyping effort should utilize appropriate software methodology

• Factory, TAP Lab, and MCS MCS-B will be key physical sites

• Initial prototype demos will be conducted at contractor facilities

• Final demo at the TAP lab – unless directed by Government

Notional

How - Overall Approach

• Capabilities demonstrated incrementally

• Software artifacts will be held by escrow company

• Includes design, code, test artifacts, etc.

• Provided, at least, quarterly

• Data rights are required

• Government will not require data rights for Commercial-Off-The-Shelf (COTS) and Free or

Open Source Software (FOSS) software technical baseline

• Government will require data rights for developed MAF prototype software

• Contract purchased hardware must be transferred to TAP Lab upon contract completion

One-On-One Information

• Held at TASC facility

• 200 North Sepulveda Blvd – Floor 18

• El Segundo, CA 90245

• SMO code: 66RP1

• POCs

• (Primary) John Lynch - (O) 310.524-4864 – (M) 505.392.0693 – john.lynch@Engility.com

• (Back-up) Kevin Lucas - (O) 310-524-4864 - (M) 626.449.0975 – kevin.lucas.ctr@Engility.com mailto:john.lynch@Engility.com mailto:kevin.lucas.ctr@Engility.com