HBM_MAFPS_FOE__SIGNED_20180702_for_Synopsis_Release_with_Redactions_FINAL.pdf

PDF 584 KB Posted

Attached to
FOE - MAFPS FOSSE Federal contract opportunity
Solicitation number
FA8730-18-F-0167
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Hanscom Air Force Base

About this file

This Fair Opportunity Exception (FOE) Detennination and Approval is for a new task order (TO) to be issued under BAE Systems, Inc's Mission Planning Enterprise Contract (MPEC) II IDIQ, FA8720-10-D-0004, for MAPPS Functional On-Site Support Element (FOSSE), Aeronautical Advisory Server (AAS) with Digital Notices to Airmen Services (DNOTAMS), and web-based Flight Plan Request Editor (FPRE). The new Task Order number is expected to be FA8730-18-F-0167.

View the file

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Justification for an Exception to Fair Opportunity or to Use Brand-Name Restriction

30 Aug 2017 Page 2 of 5

The MAFPS FOSSE capabilities will be acquired on a Cost Plus Fixed Fee (CPFF) Level of Effort CLIN with an initial period of performance (PoP) of August 2018 - July 2019 with an option CLIN PoP of August 2019 - July 2020. The estimated cost of this effort is $ .

The web-based AAS DNOTAMS and general web-server FPRE tasks will be a Cost Plus Fixed Fee (CPFF) Level of Effort CLIN with an initial base period of performance (PoP) of August 2018 + 12 months from contract award with an option CLIN for an additional 12 months for an advanced web-server FPRE . The total estimated cost of this effort is $ .

To meet AMC and other DoD customer requirements and to increase operational aircrew safety and situational awareness, AAS with DNOTAMS will be developed as a map server, thick client interface with Joint Mission Planning System (JMPS) to maintain compatibility with Global Mobility (GM) Mission Planning Environment (MPE) in the applicable C2-Enclave environments; as well as, achieving web service, thin client independence from JMPS for deployment and operational performance suitability to include a web-based FPRE in the United States Transportation Command (USTRANSCOM)-specified Cloud environment. In order to begin deployment within the overarching USTRANSCOM schedule, development must begin in August 2018.

(3) Description of the supplies/services required to meet the agency's needs:

1. FOSSE: The contractor shall be responsible to assist the users with making and understanding MAFPS flight plan requests/ results, use of tools/widgets to maintain the underlying data which drives the system, client software maintenance, creation/routing/ tracking/analysis of customer requests/trouble tickets (trend analysis), and resulting products to ensure AOC mission requirements are met. The contractor must provide Site Activation Support (FOSSE) on a 24/7/365 basis.

2. Web-based AAS DNOTAMS and FPRE: The contractor shall be responsible for a map server, thick client interface with JMPS to promote compatibility with GM MPE as well as achieve web server, thin client independence from JMPS by development through operational deployment for performance suitability in USTRANSCOM-specified Cloud environment. This includes the full implementation of a web-based AAS DNOTAMS and FPRE. This development, deployment and support effort is critical to the AOC's smooth transition from the legacy to the new system and uninterrupted planning of world-wide airlift, air refueling, and aeromedical evacuation missions.

The Independent Government Cost Estimate (IGCE) total contract value is $ . This is comprised from FOSSE ( ) + (AAS DNOTAMS and FPRE) $ = $ . AMC, the sponsoring MAJCOM, will fund the FOSSE requirements using Transportation Working Capital Fund (TWCF) Operations. AFLCMC/HB will fund the web-based AAS DNOTAMS/FPRE requirements.

The requirements listed within this document fall within the scope of the performance-based MPEC II contract FA8720-10-D-0004 that includes future mission planning software development, test and evaluation, maintenance, integration, training, and fielding through 2020, and within the period of performance and the maximum value of the contract $950M.

FOSSE Period of Performance (PoP) is 12 months (August 2018 - July 2019) from contract award and an optional 12 months, if exercised, (August 2019 - July 2020) with an estimated total value of base and option of $ . The labor cost estimate of one

(1) FTE is between per month. The FOSSE IGCE estimates are based on the requirement to support 24/7/365 for three (3) shifts of users with an approximate breakdown of 45 day shift users, 35 swing shift users, and 25 mid shift users, and the following assumptions: BAE Systems, Inc. sends from San Diego, CA to Scott AFB, IL at a cost between per month; at least one (1) FOSSE representative per shift at the beginning of the contract and ramp up between August 2018 - December 2018 and additional by end of calendar year 2018.

AAS DNOTAMS and basic web-based FPRE PoP is 12 months (August 2018 - July 2019) from contract award with an estimated total value of $ . The web-based AAS DNOTAMS and FPRE IGCE estimates are based on the requirements for a map server, thick client interface with JMPS to promote compatibility with GM MPE and general web-server, thin client capabilities for AAS DNOTAMS with independence from JMPS. The optional 12-month period, if exercised, is for the advanced web-based FPRE which achieves complete thin client independence from JMPS for the TACC's proficient operational deployment and full utilization of the AOC client. The option is estimated at $ . Total of base AAS DNOTAMS map-server with general web-server, and Option for FPRE advanced web-server is a value of $ .

Justification for an Exception to Fair Opportunity or to Use Brand-Name Restriction

30 Aug 2017 Page 3 of 5

(4) Identification of the exception to fair opportunity and the supporting rationale:

FAR 16.505(b)1(i) requires the Contracting Officer to provide each awardee under a multiple award contract, a fair opportunity to be considered for each order exceeding $3,500 unless a statutory exception applies. The specific exception that precludes the fair opportunity process for this acquisition is FAR 16.505(b)(2)(i)(B).

FAR 16.505(b)(2)(i)(C) provides: "The order must be issued on a sole-source basis in the interest of economy and efficiency because it is a logical follow-on to an order already issued under the contract, provided that all awardees were given a fair opportunity to be considered for the original order. BAE Systems, Inc. has been the MAFPS prime contractor since 24 April 2013.

Competing this effort would require spinning up a new contractor with no MAFPS experience; which will delay AMC requirement to transition flight planning operations from its legacy ACFP system to MAFPS while severely negatively impacting real-world mission planning capability globally.

As the developer since April 2013 of MAFPS, thick client FRPE, and AAS in the MilCloud with legacy Notices to Airmen (NOTAM), BAE Systems, Inc. is uniquely qualified to provide this mission critical support, development and deployments for both legacy interfaces and new independent web server performing architecture. The Government has invested $79 million over 5 years to develop the legacy MAFPS capabilities. Award to a contractor other than BAE would result in the duplication of these investment costs and it is unlikely the investment would be recouped through competition.

1. FOSSE: Historically, new IT systems include post-development support in the original contract award. When a new IT system is fielded, the software developer is naturally the most knowledgeable SME. Despite a 618 AOC requirement for 24/7 on-site user support during the transition from legacy ACFP to MAFPS, AMC did not add any on-sight technical or user support requirement to the MAFPS contract, only software maintenance was included.

Due to the complexity and inter-dependencies of MAFPS, BAE Systems as the MAFPS developer, is best suited to accomplish this work to meet and maintain FOC of mission critical MAFPS. BAE Systems, through the development and initial system fielding, is uniquely qualified to maximize performance/cost savings, maintain the vast volumes of data, and troubleshoot any inherent client/ server issues within the MAFPS environment.

If this requirement was procured through competitive procedures and awarded to another contractor, it is estimated it would take the new contractor 6 months to be able to fully support the Air Force's requirements. During that 6 month period, AMC would be required to continue use of the legacy system. Current support to the users is limited to 8 hours per day whereas FOSSE will provide 24 hours per day / 7 days a week that results in a 66% increase in support. The current fuel costs and efficiencies for using the current system ACFP are costing an additional $ per month plus $ to operate ACFP or estimated at $ total during the initial 6 months until the awardee can fully support the 400+ sorties per day delivered by this requirement in support of the mission. The estimated cost of this task order is $ therefore it would not be possible to save $ through competition for the 2 year contract.

The MAFPS program is unique to the other areas of mission planning. MAFPS is the Only Client Server mission planning product that creates automatically creates flight routes based on business rules, airspace rules, weather, notices to airmen, terminal area forecasts, enroute weather and hazards, special use airspace activation, International Civil Aeronautical Organization (ICAO) Airspace procedures, Taxi-path, CNS/ATM routing rules, Airfield Suitability and more. Other Mission planning programs that the other MPEC IDIQ developers are creating are manual planning for a specific purposes of an aircraft or a manual planning of a route of flight.

2. Web-based AAS DNOTAMS and FPRE: BAE Systems, Inc. is the developer that created the interface to JMPS for AAS with NOTAMS on MilCloud. They have the most expertise to extend AAS for DNOTAMS and create a JMPS-independent web server and map server deployment to USTRANSCOM-specified Cloud.

File details come from the government source that posted it.