ACTS OME - Industry Day Brief - FINAL (13Dec2021).pptx


Original Source
Contract Opportunity
Related Agency
Dec. 16, 2021



Air Combat Training Systems (ACTS) Operations, Maintenance, and Engineering (OM&E) Industry Day
Introduction to ACTS
ACTS 101
Customers and Locations

PWS Requirements
Major Areas of Performance
Special Interest Areas
Workload assessment (performance-based)
Changing Factors from Previous Contract
Future Look

Acquisition Strategy / Solicitation

ACTS A Critical Component of Live OTI
ACTS is both a distinct set of capabilities and the lynchpin for integrating OTI from an Enterprise viewpoint

GPS Accuracy
ACTS Integrated Operations
Pod Data Link
Aircraft Data Link
(Link 16 or equivalent)

Ground-Based Weapon Scoring

Pod Ground Station

Link Ground Stations

JNTC / DMO Network
Global Information Grid (GIG)

Integrated Live Ops
Threat Systems

Pod Data Link

ACTS has critical primary roles in delivering an effective live OTI environment
Operate & Maintain systems needed to gather training data
Integrate gathered data into a consolidated training picture
Use integrated data to support live execution of the training sortie
Merge live data and offline data to support full re-creation of the training sortie for warfighter debrief

ACTS has supporting roles to enable an effective live OTI environment
Cybersecurity functions for systems, networks, and software
Secure handling of source and aggregate data at appropriate levels
Routine, persistent, interface with warfighters for scheduling, support, and feedback
Program and quality management to ensure reliable and repeatable delivery of ACTS capabilities
Specialized support to aid technical/engineering activities and to provide critical roles (e.g., Range Training Officer)

ACTS 101
ACTS Community
ACTS is used worldwide by multiple services, MAJCOMs, and foreign partners

This Contract
Four MAJCOMs spanning 12 time zones
15 locations
1 Coalition Partner (Mountain Home)
60K Annual Sorties
Daily training, surge events, LFEs, etc.
Operational squadrons and FTUs

Customers and LocationsLangley AFB, VA; Seymour Johnson AFB, NC; Shaw AFB, SC,
Eglin AFB, FL; Tyndall AFB, FL
Mountain Home AFB, ID; Barksdale AFB, LA, Davis-Monthan AFB, AZ (Optional)
AFCENT Air Warfare Center (AAWC), Al Dhafra AB, UAE

Spangdahlem AB, GE; RAF Lakenheath, UK; Aviano AB, IT

Dyess AFB, TX; Ellsworth AFB, SD
JRB Fort Worth, TX (Optional)

Royal Singaporean Air Force (RSAF) at Mountain Home AFB, ID
Customers and Locations by MAJCOM
Different funding sources but one unified set of requirements
Airborne Instrumentation Systems (AIS) - External, Internal, and Portable systems
Pre-Mission - Scheduling, planning, and systems prep/check-out
Mission Execution - Live operations and training execution
Post-Mission - Mission reconstruction, dedicated debrief, and feedback/follow-up
Pod and Ground Stations
Electronic, Computer, and Networking Systems
Radios, Datalink, and Remote Instrumentation Transceivers
Radio and Transceiver Systems - UHF/VHF/SAT, Link-16, microwave, point-to-point
Network - P5 network, TENA, LMON with associated cybersecurity roles/functions
Software - ITAS product support, software integration activities
Program Management - PM, Site Managers, PROJO,
Quality Management - Contractor Quality Control Program
Security Management - Security Clearances, COMSEC, Industrial Security
Major Areas of the PWS
Flight-line Ops (pod loading/unloading)
Range Training Officer / SAM Operator / Tactical Data Link Manager

Locations (on-base, on-range, off-range)
Site appendices - Towers, off-site facilities, central debriefing facility

Software is full lifecycle product support for ITAS
R&T includes on-site implementation activities such as certified tower climbing
Network includes associated cybersecurity roles/functions (ATO/RMF)

Security clearances - Up to TS/SCI, SAP access
OCONUS Operations - Work permits, agreements, foreign disclosures
QCMS follows ISO 9001-2015 standards for continuous improvement

Special Interest Items
Performance-based contract
Government specifies outcomes desired, not method to get there
Main body of PWS has full requirements
Check appendices for site-specific requirements
Information throughout the PWS provides workload estimate basis
Normal Operating Hours and Support Windows
Sorties estimates, number of daily sortie turns, surge operations
Pod loading (required or not at each site)
Debriefing required (shared or not at each site)
Special facilities (supported or not at each site)
General Equipment categories (supported or not at each site)
Detailed account/inventory of all systems, equipment, tools, etc. for each site
Some roles/functions provide support across all sites
PROJO - 40-hrs/week targeted at key projects across all contract sites
Radio Engineer and Network Engineer - 40-hrs/week working engineering efforts across all sites
Software Engineers - Sufficient support for the version releases and software LOCs in App 8M

Performance-Based Workload Estimates
PWS can help determine type/quantity of contractor-provided items

Example: Vehicle estimates
Site technical exhibit indicates Remote Range Units (RRUs) assigned. RRUs are off-site equipment. The contractor is responsible for RRU maintenance and should plan vehicle(s) to support.
Site technical exhibit indicates pod loading is required. The contractor is responsible for pod loading and should plan vehicle(s) to support.

PWS provides info on type/quantity of equipment to operate/maintain
PWS main body lists major systems to be supported under general categories
Site appendix indicates if those general categories apply to a site
Technical exhibit provides specifics on type/quantity of systems

PWS requirements can help identify special expertise that might not fit into DOL labor categories
OCONUS personnel have additional site-specific personnel requirements
RTO, RTO-Tactics, TDLM, and SAM Operators have specialized experience requirements.

Performance-Based Workload Estimates (cont.)
Typical support windows - 10 hrs, 4 days/week or 8 hrs, 5 days/week
Check appendices for site-specific requirements

Mission support day components (Notional site)
Pods checked out, driven to ramp, and loaded on aircraft before aircrew step
Live monitoring equipment checked out and ready before flying window starts
RTO in-place and ready to support first sortie set
SAM Operator, TDLM, etc. in-place and ready to support first sortie set
Mission replay file prepped immediately after first sortie set ends
Pod cross-loads happen between sorties sets (as needed) before aircrew step
Dedicated debrief of first sortie set happens
RTO in-place and ready to support second sortie set
Mission replay file prepped immediately after second sortie set ends
Pod download/return to maintenance (as needed)
Dedicated debrief of second sortie set happens

Support Windows
Support Windows (cont.)
Changing Factors Regionalization
OTI assets grouped regionally to meet increasing training requirements with limited assets
Increased Integration
Systems previously operated in an enclave now are part of the larger OTI enterprise
Changes to one system create 2nd and 3rd order ripple effects

More Classified Ops
Link-16 and JSF Live Ops at Secret
DMO, Aggregation, MILS Live Ops at SAP

Expanding Project/Engineering Tasks
System complexity will drive need for increased management, professional, and engineering services

Changing Factors Scope
Changing Factors Increasing Cybersecurity Requirements

OTI functions involve every aspect of the risk intrusion wheel

Risk Management Framework (RMF) designed to mitigate/control risks

Site operators and maintainers responsible for a significant number of RMF controls (100s per system)

Changing Factors Technology Turnover
Multiple new systems projected 3-8 years out
Advanced Radar Threat System (ARTS) - 4 versions
P5CTS replacement pod - 3 versions
Live Mission Operations Center (LMOC) - 3 versions
Live Mission Operations Network (LMON)

Increased focus on technical certifications
IT Professional: Security+, Network+, A+
Microsoft: MTA, MCSA
Cisco: CCNA
Air Force: 8570-certified workforce
Link 16: TDLM
Range Training Control/Management: RCO, RTO
P6CTS - Planned replacement for current P5CTS instrumentation
First fielding could be as early as 2024
Likely some minor overlap (1-2 months) where both P5 and P6 are at a siteFuture approach to provide more standardized and adaptable live ops equipment
LMOC features could reduce some maintenance (patches/upgrades) workload
LMOC and precursor capabilities (WarRoom) will roll out during this contract
Future focus area for PROJORegion 1 implementation underway. Other regions will occur during this contract.
Likely some disruption to ops during transition
Key focus area for network engineer
Cybersecurity functions take on additional importance under LMOCInstalled at multiple locations, but installations will still occur during this contract
Key focus area for radio engineer

Future Look
Acquisition Strategy / Solicitation Overview
J.J. Foster
Contract Specialist

Sharon Potter
Contracting Officer

Key Contractual Aspects
Projected Milestones
Commerciality/Small Business Considerations
Evaluation Process
Evaluation Methodology - Overview
Evaluation Methodology - Factor 1 - Technical Factor
Evaluation Methodology - Factor 2 - Past Performance
Evaluation Methodology - Factor 3 - Price
Security Clearance
Bidders Library
Draft Request for Proposal (RFP)
Site Visit
Communications with the Government
Key Contractual Aspects
Solicitation Number: FA489022R0010
Was FA489020R0034
Cross reference will be provided on
Anticipated Contract Type:
Single Award Firm Fixed Price (FFP) with Cost Reimbursable (CR) Line Items
Draft Contract Line Item Number (CLIN) Structure: