VH-92A_Future_Communication_System_BAA.pdf

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 1

VH-92A Future Communication System Broad Agency Announcement

28 July 2017

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 2

1.0 Introduction

The Naval Air Systems Command (NAVAIR) is releasing this Future Communication System (FCS) Broad Agency Announcement (BAA) seeking proposals that will identify opportunities to advance the state of the art and develop approaches and concepts for the VH-92A communications system.

2.0 Background

The VH-92A is the helicopter that is replacing the In-Service aircraft (VH-3D and VH-60N) to become the primary Presidential vertical lift platform employed by Marine Helicopter Squadron One (HMX-1). The VH-92A will be a critical, national-level platform that provides a survivable and dependable worldwide transportation capability and enables the strategic information superiority necessary to execute the duties of the President of the United States. The VH-92A will provide a comprehensive and secure communications capability to ensure connectivity between the President and U.S. Government agencies or foreign Governments, throughout the threat spectrum, regardless of location.

Presidential helicopter transportation requirements are executed by HMX-1. The Director, White House Military Office (WHMO) directs and coordinates Squadron tasking for White House support missions. The primary mission of HMX-1 is to provide safe, reliable, and timely transportation for the President, Vice President, Foreign Heads of State (HoS), and other official parties as directed by the WHMO.

The VH-92A has two (2) main types of missions, administrative lift mission tasking one (MT-1) and contingency operations mission tasking two (MT-2). Both missions use the same communications suite architecture.

2.1 BAA Objectives

The objective of this BAA is to gain further knowledge of communications technology and capability available to support the presidential vertical lift mission. This knowledge will be used to help the Government define and refine future requirements for presidential communications system enhancements. Specific areas of interest include, but are not limited to:

a. Exploring a wide range of options for defining the VH-92A FCS, varying from minor modifications of the existing communications suite to a major redesign

b. Defining system concepts associated with the approach

c. Proposing potential key requirements that will define the attributes of these system concepts

The current VH-92A communications system, the Mission Communications System (MCS), may be used as a starting point for modifications, but reuse of the various components and human interface devices of the system should not be viewed as a constraint. The following are key

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 3 capabilities of the MCS system which need to be retained in the development of future capability:

a. Digital and analog capabilities

b. Voice and data services

c. Top Secret (TS)/Sensitive Compartmented Information (SCI) and Sensitive But

Unclassified (SBU) networks

d. TEMPEST certified

e. Federal Aviation Administration (FAA) airworthiness certified

f. Electro Magnetic Pulse (EMP) hardened

FCS concepts should consider characteristics that will affect the viability of successful integration onto a VH-92A. These characteristics include, but are not limited to:

a. Weight efficiency

b. Suitability for a rotary wing aviation environment

c. Supportability

d. Ability to implement and enhance cyber security measures

In addition to the development of system concepts and associated requirements, the Government’s desired output of the BAA is to identify risks associated with the defined approach. The risks should consider:

a. Performance against defined system level capabilities

b. Integration risks

c. Developmental, Production, and Operations & Sustainment (O&S) risks

d. Technological Maturity

e. Schedule

2.2 BAA Proposal Overview and Government Furnished Information (GFI)

Each BAA proposal shall describe, in detail, the Offeror's approach for meeting the objectives of paragraph 2.1. The Offeror shall develop a Statement of Work (SOW) that describes specific activities and associated data deliverables to be conducted during the period of performance.

Section 6.0 identifies the appendices the Offerors may utilize in support of their proposals in response to this BAA. BAA proposals must be developed and submitted as unclassified documents, however, the execution of studies, meetings, and deliverables during the BAA will include work classified as high as SECRET collateral. Due to the sensitive nature of the mission, no classified information will be provided to the Offerors until a contract is awarded. The following sensitive but unclassified (SBU) GFI is available to support proposal development after contacting the Contracting Officer and complying with the security requirements of Section 5.6

a. Capabilities Document for the VH-92A Future Communication System

b. VH-92A FCS Capabilities Document Industry Input

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 4

c. BAA VH-92A MCS Single Line Block Diagram

d. Broad Area Announcement (BAA) VH-92A Mission Communications System (MCS)

Current Component Physical Attributes

e. SCG ID# 02-282.1 - VH-92A Presidential Vertical Lift Platform Security Classification

Guide, 22 Dec 2015 (Classified Annex removed)

If an Offeror is awarded a contract and meets the necessary security requirements, the following GFI will be provided after contract award:

a. Capabilities Document for the VH-92A Future Communication System Classified

Requirements

b. SCG ID# 02-282.1 - VH-92A Presidential Vertical Lift Platform Security Classification

Guide, 22 Dec 2015 (Classified Annex attached)

c. VH-92A Mission Communication System Cyber Risk Assessment

See Appendix C for a flow chart depicting the process to receive the GFI through the proposal and contract award phases. Additional proposal requirements are contained in Section 4.0.

3.0 BAA Areas of Interest

a. Systems Engineering

1) System Concept: The system concept and architecture development should evolve and mature in concert with requirements analysis based on feedback from the Government. It should address both functional considerations and notional physical definition of the FCS. The Offeror may describe multiple system concepts throughout the contract effort to accommodate for varying degrees of risk, requirements baselines, complexity or other factors. This range of concepts can vary from minor modifications that address current gaps to major modifications that radically change and enhance capabilities.

2) Requirements Analysis: The Offeror shall analyze the requirements and provide a feasibility assessment of the requirements. The Offeror shall propose recommendations on additions, deletions, changes, and derivations to the existing requirements set in preparation for a system development phase. (CDRL A001)

3) Size, Weight, and Power- Cooling (SWaP-C): The Offeror shall analyze and provide SWaP-C estimates for their systems concepts. Current SWaP-C data on the existing MCS is provided for reference but should not be considered as a hard constraint. SWaP-C attributes are vital to the performance of the VH-92A air vehicle, and strong consideration should be given to optimization and efficiency in the FCS architecture.

4) Airworthiness: The VH-92A is a FAR Part 29 certified rotorcraft, including the MCS. The Offeror should consider the requirements to achieve FAA certification including, but not limited to, Design Assurance Levels of software, environmental

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 5 qualification, cockpit integration concerns, and certification pedigree for their system concepts. The current MCS has both non-essential/non-required equipment and essential aircraft equipment.

5) Cost and Schedule: The Offeror shall perform an affordability assessment and develop a high level schedule to include a cost analysis that projects R&D, Procurement, and O&S estimates for proposed concepts as well as identifying strategies for minimizing Total Ownership Cost (TOC).

6) Risk: A risk assessment of the system concepts and development of risk mitigation strategies shall be performed. Consideration of mitigation approaches should focus on potential for future risk reduction activities via trade studies and prototyping. In addition to the Cost/Schedule/Performance risk assessment, a separate technological maturity self-assessment shall be performed.

7) Suitability and Supportability: Reliability and Maintainability requirements are defined as allocations of total system requirements and Offerors should give strong consideration to satisfying the existing requirements. The Offeror shall include supportability requirement considerations in all design efforts for an FCS system concept including support infrastructure.

8) Information Assurance: The FCS must be accredited as a TS/SCI system utilizing the National Institute of Standards and Technology (NIST) SP 800-53 Risk Management Framework (RMF) process. The FCS shall implement NIST SP 800-53 security controls as required by the CNSSI 1253 High, High, High security control baseline supplemented by the Classified Information, INT-C, and NC3 overlays, appropriately tailored for the operational environment. The offeror shall identify Information Security features in their system concepts intended to address these requirements.

9) Open Architecture: The Offeror shall develop concepts that incorporate appropriate considerations for reconfigurability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

10) Model Based System Engineering (MBSE): The system concept should be developed as a system model using System Modeling Language (SysML) in accordance with the Section 2.1 objectives generated by the following tool:

Cameo Systems Modeler™ v18.5 sp1, with Cameo Simulation Toolkit Plug-in, UPDM2 Plug-in and Teamwork Cloud Enterprise available from No Magic, Inc.

The requirements analysis and architecture development should be captured in the model showing traceability of the system concept performance to the requirements and interfaces.

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 6

b. Communications

1) Intercommunications System (ICS)

a) System Capacity

i. Provide all aircrew members access to all communication channels on the aircraft including those specifically limited by the FAA to aircrew members.

ii. Provide all VIPs/passengers/aircrew in the MT-1 configuration access to all communication channels on the aircraft except those specifically limited by the FAA to aircrew members.

iii. Provide all VIPs/passengers/aircrew in the MT-2 configuration access to all communication channels on the aircraft except those specifically limited by the FAA to aircrew members.

iv. Provide the Communication System Operator (CSO) the capability to enable and disable access to each communication channel by passenger location.

b) Conferences

i. Provide the capability to configure multiple conferences among any combination of passengers and aircrew members. These conferences should be both internal to the aircraft as well as external to the aircraft.

2) Data Distribution System (DDS)

The Offeror shall define a DDS that will provide access to voice and data services at multiple classification levels for all passengers and aircrew.

a) Virtualization: The offeror will strongly consider virtualizing routing, switching, and any other functionality within the DDS.

b) Cyber Security Hardening: The offeror shall consider enhancing the cyber security posture of the DDS, for example, utilizing Next Generation Firewall (NGFW) technology or other cyber security measures.

Performance considerations related to processing, memory, and throughput need to be considered as a part of any cyber security measure.

3) Narrow Band System (NBS)

The Offeror shall define a NBS to satisfy the FCS requirements. NBS definition should focus on improved efficiency and reduced SWaP-C. Components should focus on mature technologies ranging from existing MCS radios to high Technology Readiness Level (TRL) solutions.

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 7

4) Wide Band System

The Offeror shall define a Wide Band System to satisfy the FCS requirements. Wide Band System definition should focus on improved efficiency, enhanced performance, greater or increased bandwidth, and reduced SWaP-C. Components should focus on mature technologies ranging from existing MCS radios to high TRL solutions. The Government will reuse the existing Wide Band Line of Sight (WBLoS) system as defined in the MCS architecture.

3.1 Technical Coordination Meetings (TCM) and Program Reviews

A kickoff meeting and two formal TCMs (TCM 1 and 2) at the contractor’s or Government location is anticipated after contract award. The first TCM should focus on requirements analysis, risks, system architecture and initial system concept(s), and the second TCM should conclude the remaining tasks with emphasis on maturing system concept(s) definition, developmental schedule, supportability, costs, and updated risks. The Offeror’s may propose additional TCMs as required. More frequent interaction between the Government and the Offeror may be required on the topic of requirements analysis. Phone communications/virtual meetings every two weeks are the preferred medium for this interaction. (CDRL A002)

4.0 Proposals

4.1 General Information

All proposals submitted under the terms and conditions cited herein will be reviewed. Full proposals should be submitted in one (1) volume, containing three (3) Sections: Section I, Technical; Section II, Price; and Section III, Small Business Subcontracting Plan. All sections shall be bound in one (1) three-ring binder to facilitate the removal of individual sections.

Proposals will be evaluated in accordance with the criteria cited in paragraph 4.5 below.

Proposals shall be submitted in original, with the signature of an authorizing official, with five

(5) copies to the address noted below. The Offeror shall submit a copy of the entire proposal on CD-ROM containing file formats compatible with Microsoft Office 2010 applications along with the submission of the paper proposals. Additionally, schedules should be in Microsoft Project 2010 and supporting price information shall be provided in Microsoft Excel 2010 compatible spreadsheets with formulas that are not locked.

In submitting the proposal, Offerors are advised that quality of the information is significantly more important than quantity. Therefore, Offerors are requested to confine their submissions to essential matters, providing sufficient information to define their offer and establish an adequate basis for Government evaluation. Offerors are neither constrained by descriptions of past methodologies nor prohibited from describing innovative ideas.

The proposal shall include a draft SOW that describes the work to be accomplished and any deliverables. Offerors must keep in mind that the SOW portion of the proposal shall be incorporated by reference into any resultant contract to serve as the basis for work to be accomplished. Therefore, proprietary and/or other restrictive markings shall not be included on the SOW. Offerors shall restrict any proprietary information to the technical portion of the

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 8 proposal. Each task description of the SOW should be written to facilitate evaluation and acceptance without the need for major revisions prior to incorporation into the resultant contract.

4.2 Format and Length

The narrative material in the technical, price, and Small Business Subcontracting Plan volumes shall be single spaced, typed or printed in Times New Roman font with type no smaller than 12-point font. Paper shall be 8-1/2 X 11 inches with a minimum margin of 1 inch around the page (excluding headers and footers). Any typed narrative included on graphics pages may not be smaller than 12-point font. Foldouts are permitted, not to exceed 11”x17”, and count as one (1) page. The footer shall contain the page number of each page of the proposal and shall be continuous (i.e. numbers are not reset to 1 upon entering a new section). The use of double-sided printing is discouraged. All proposals shall identify the following information:

a. Title of Proposal

b. Name, address, and Commercial and Government Entity (CAGE) code of Offeror

c. Statement that this proposal was submitted in response to BAA N00019-17-R-0084.

The proposal’s sections (excluding draft SOW, cover, title page, table of contents, and tabbed dividers) shall be no longer than the page limits stated in the following table. Each proposal will be evaluated only on the pages falling within the stated page limits.

Section Number Section Title Pages I TECHNICAL 40 Pages

II PRICE 5 Pages

III SMALL BUSINESS UTILIZATION STRATEGY

AND SMALL BUSINESS SUBCONTRACTING

PLAN

As Needed

4.3 Proposal Submission

All responsible sources may submit a proposal which will be considered, but must do so on or before 2:00 PM Eastern Daylight Time on 31 August 2017 to be considered. Clearly mark all packages with the solicitation number. Proposals shall be submitted via United States Postal Service or through a commercial carrier using the address provided below. Proposals are not to be submitted by facsimile or electronically via email.

ATTN CHRIS RAWLINGS

SOLICITATION NUMBER N00019-17-R-0084

NAVAL AIR SYSTEMS COMMAND

48202 BRONSON RD BLDG 2805

PATUXENT RIVER MD 20670

Hand carried proposals may be delivered to the address above, attention Mr. Chris Rawlings.

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 9

4.3.1 Proposal Packaging

The Offerors shall package their proposals in the most efficient manner possible and shall stamp or mark on the package itself the following: “For Official Use Only” and “Source Selection Information -- See FAR-2.101 and 3.104”.

4.4 Proposal Content

The paragraphs below are the minimum required content and should be easily identified in the proposal.

4.4.1 Technical Section

The technical section is expected to address all areas of interest in paragraph 3.0 and any optional sections provided by the Offeror. If an Offeror elects not to address any section identified in paragraph 3.0, the Offeror shall provide the reason for its omission(s), the projected effect the omission(s) will have on the VH-92A concept design, and an explanation of how the overall concept design, including omitted items, could potentially benefit the VH-92A program.

The Offeror shall do so for each section omitted, thereby addressing each and every section.

The Technical section shall include:

• A two-page Executive Summary

• The proposed approach for meeting the objectives of paragraph 3.0

• A SOW which addresses specific tasks to be performed and products to be delivered for each of the activities identified in Section 3.0. Draft Contract Data Requirements Lists (CDRLs) shall be included with the SOW. The SOW and CDRLs do not count against the page limitations set forth above.

• A matrix identifying the list of deliverables, applicable SOW paragraphs, CDRL numbers, and delivery dates that align with the objective of this BAA

• Define the Government’s rights to all data developed, delivered and/or used to execute the BAA study efforts

• Identify any subcontracting efforts

• A description of key personnel, their roles and relevant experience, and the infrastructure to support the study activities

4.4.2 Price Section

The price section shall include Firm Fixed Price (FFP) for each Contract Line Item Number (CLIN) proposed by the contractor. Data CLINs shall be Not Separately Priced (NSP). The Government is not soliciting any investments (IR&D, Contractor Funded effort, etc.). However, in order to properly assess the proposed price that appears low due to a corporate decision proposed by the Offeror to absorb costs, e.g. lower than usual burdens or rates, the Offeror shall fully identify and explain any such investments.

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 10

4.4.3 Small Business Utilization Strategy and Small Business Subcontracting Plan Section

This section contains two (2) parts: Part I - Small Business Utilization Strategy; and Part II - Small Business Subcontracting Plan. This section shall not be used to convey technical information for evaluation. In the event the Offeror proposes no subcontracting opportunities for this effort, a small business utilization strategy and small business subcontracting plan are not required; however, the Offeror shall provide a detailed explanation within this section as to why no subcontracting opportunities exist for the proposed effort.

• Part I – Small Business Utilization Strategy - The Offeror shall provide a Small Business Utilization Strategy for using Small Business (SB) concerns which consist of Small Business, Small Disadvantaged Business (SDB), Women-Owned Small Business, HUB Zone Small Business, Veteran-Owned Small Business, Service-Disabled Veteran-Owned Small Business concerns as well as Historically Black Colleges and Universities and Minority Institutions (HBCU/MIs). This strategy is separate from, but shall be consistent with, the Small Business Subcontracting Plan. Offerors (unless exempt pursuant to FAR 19.702) shall address their strategies for utilizing SB Concerns and HBCU/MIs in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor. In describing its strategy for the proposed effort, the Offeror shall:

– Describe its approach to identifying SB Concerns, SDB Concerns, and HBCU / MIs.

– Describe the extent of participation of SB Concerns, SDB Concerns, and HBCU / MIs for this effort, especially as principal subcontractors.

– Describe the extent of commitment to use such SB, SDB Concerns, and HBCU / MIs.

– Describe the complexity and variety of the work SB, SDB Concerns, and HBCU / MIs are to perform;

– Identify what processes have been implemented to correct past inabilities to meet proposed goals.

– Demonstrate that its SB strategy is consistent with its SB Subcontracting Plan.

• SB Subcontracting Plan - The Offeror shall provide its SB Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program specified in DFARS 219.7, the Offeror shall describe how SB participation for this effort will contribute to its overall Comprehensive Subcontracting goals. Offerors shall describe specific efforts to ensure the resulting contract, if awarded, meets or exceeds proposed goals. These efforts shall include, but are not limited to: sponsoring program specific outreach programs and industry conferences, establishing Mentor-Protégé relationships and using the NAVAIR SUBNet website (http://www.navair.navy.mil/osbp) to locate SB concerns and to post requirements.

(Note: The Offeror’s subcontracting plans will be reviewed and approved by the PCO prior to any contract award. See FAR 19.702 Statutory Requirements (a)(1) regarding failure of the apparently successful Offeror to negotiate and submit a plan acceptable to

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 11 the Contracting Officer.) The Offeror’s subcontracting plan will be incorporated as an attachment to any resultant contract.

4.4.4 Government Furnished Property, Information or Equipment

Any requests for Government furnished property, additional information over and above what is identified in paragraph 2.2, equipment, or facilities must be clearly identified in this section of the proposal. The cost of any Government furnished property, information, equipment, or facilities required to execute the proposed work will be considered a contract cost in the Government’s evaluation of proposals. The Government, however, is under no obligation to comply with such requests. Therefore, Offerors should make provisions for alternate technical approaches in the event the Government is unwilling or unable to provide the requested property.

4.5 Proposal Evaluation

Proposals must fully address each piece of information required under paragraph 4.4 above.

Offerors are encouraged to include any additional information they deem pertinent to a thorough and complete response. Proposals not minimally responsive to all the required information may be rejected on the grounds that the Offeror lacks a basic understanding of the Government’s requirements or lacks resources to meet the requirements.

The Government is under no obligation to award a contract as a result of this BAA. The Government reserves the right to award one or more contracts for any concept design as described in the BAA. Awards are anticipated for those Offerors whose proposals represent the best value to the Government, proposed cost, and other criteria considered. The Government intends to evaluate each proposal independently and award contracts without discussions with Offerors; therefore, each offer should contain the Offeror’s best terms from a cost and technical standpoint. However, the Government reserves the right to conduct discussions if later determined to be in the best interests of the Government.

Proposals for VH-92A FCS concept(s) designs will not be accepted from foreign-owned firms as prime contractors due to security restrictions. However, foreign participation as subcontractors and/or suppliers to prime Offerors is acceptable. Foreign owned firms should be aware that restrictions would apply which may limit participation.

Proposals will be evaluated using the following two (2) criteria: Technical and Price. The technical criteria is substantially more important than price.

4.5.1 Technical

The soundness of the Offeror’s proposed technical solution and approach to providing that solution will be evaluated, to include:

a. Ability to define VH-92A FCS Design Concept(s)

b. Approach and ability to achieve the BAA objectives identified in section 2.1

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 12

c. Key personnel, their BAA roles and relevant experience, and the infrastructure to support BAA activities

4.5.2 Price

The proposals will be evaluated based on the reasonableness of the proposed prices.

5.0 Contracts Planned for Award

The Government intends to award multiple contracts based on proposals submitted in response to this announcement, within a total budget of approximately $6M. The Offeror may submit multiple concepts in one proposal. Each Offeror may submit only one proposal. However, the Government expects that any synergies gained from the use of common staffing resources be reflected in the price section of the Offeror’s proposals. The Government will not award any contract over $1.5M for each award. However, award amounts and number of awards may vary based on budgetary constraints, technical merit and utility to the Government. The Government is not required to award any contracts as a result of this announcement. Under no circumstances will an Offeror be entitled to more than the Firm Fixed Price it proposed for performance of the contract.

5.1 Period of Performance

The Government expects to award contracts under this BAA during the 1st quarter of FY18. The period of performance is anticipated to be between ten (10) and fourteen (14) months from date of award.

5.2 Deliverables

Offerors shall identify within the technical section of their proposals the specific deliverables in accordance with paragraph 4.4.1. CDRLs will be finalized prior to contract award. At a minimum, deliverables include, but are not limited to the following:

a. Comments on existing and VH-92A FCS capabilities/requirements

b. TCM 1 Presentations

c. TCM 2 Presentations

d. Updated comments on existing and VH-92A FCS capabilities/requirements – end of contract

5.3 Contract Type

Any contracts awarded pursuant to this BAA will be Firm Fixed Price (FFP).

5.4 Data Rights

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 13

The Government seeks unlimited rights in all data delivered under any contracts awarded pursuant to this BAA. The Offerors must provide a list of technical data and computer software it will deliver with less than unlimited rights in accordance with DFARS 252.227-7017. Offerors shall identify in the price section of their proposals any Independent Research and Development (IRAD) investments. No proprietary information is to be included in the FCS requirements analysis deliverables.

5.5 Classified Proposals

Classified proposals are not permitted.

5.6 Security Classification

The DD-254 is for solicitation bidding purposes only, and is not valid for the actual contract. At time of award, a new DD-254 will be established reflecting specific contractor requirements based on their proposal security requirements. The Contractor will be required to perform work up to the Secret collateral level during the period of performance.

5.7 VH-92A Program Points of Contact

Questions regarding this announcement should be directed in writing via email to the points of contact identified below. All questions should be provided on company letter and included as .pdf attachments to the email. You may address your letter using the address provided in paragraph 4.3 above.

Name Title Email Phone Chris Rawlings Procuring Contracting Officer christopher.rawlings@navy.mil (301) 757-1255 Anthony Gatlin PMA-274 Contract Specialist anthony.gatlin@navy.mil (301) 995-2826

6.0 Appendices

o Appendix A: Acronyms o Appendix B: Terms and Definitions o Appendix C: Release of GFI mailto:christopher.rawlings@navy.mil mailto:anthony.gatlin@navy.mil

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 14

Appendix A: Acronym List A B BAA Broad Agency Announcement C CAGE Commercial and Government Entity CD-ROM Compact Disc, Read-Only-Memory CDRLs Contract Data Requirements Lists CSO Communications Systems Operator D DDS Data Distribution System DOD Department of Defense DODD Department of Defense Directive DODI Department of Defense Instruction DON Department of the Navy E EMP Electro Magnetic Pulse F FAA Federal Aviation Administration FCS Future Communication System G G&A (contracts section) General and Administrative expense GFI Government Furnished Information H HMX-1 Marine Helicopter Squadron One HoS Head of State I IR&D (Pricing section) Independent Research And Development K L M MCS Mission Communications System MCS DODAF Department of Defense Architecture Framework MT-1 Mission Tasking One (Administrative Lift Operations) MT-2 Mission Tasking Two (Contingency Operations) N NAVAIR Naval Air Systems Command NB Narrowband NBS Narrow Band System NIST National Institute of Standards and Technology NGFW Next Generation Firewall O O&S Operations & Sustainment P POTUS President of the United States R R&D Research and Development RMF Risk Management Framework

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 15

S S Secret SATCOM Satellite Communications SBU Sensitive But Unclassified SCI Sensitive Compartmented Information SECNAV Secretary of Navy SOW Statement of Work SWaP-C Size Weight and Power-Cooling T TCM Technical Coordination Meetings TEMPEST Transient Electromagnetic Pulse Emanation Standard TOC Total Ownership Cost TRL Technology Readiness Level TS/SCI Top Secret/Sensitive Compartmented Information U US United States V VIP Very Important Person VTC Video Tele-Conferencing VH-92A Vertical Lift Aircraft to conduct Presidential Support Missions W X Y Z WBLOS Wideband Line of Sight WB BLOS Wideband Beyond Line of Sight WHCA White House Communications Agency WHMO White House Military Office

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 16

Appendix B: Terms and Definitions Term Definition

Access Provide the capability to control, transmit, and receive on a terminal.

Aircrew members The VH-92A aircrew members are those Marine Corps personnel assigned duties to operate aircraft systems during flight.

Communication Systems Operator CSO

The aircrew member on the VH-92A that manages the Mission Communications for the passengers.

Conferences (context) to configure multiple conferences among all passengers and aircrew members

Monitor Provide communications capability to listen.

Mission Tasking One (Administrative Lift Operations)

MT-1

MT-1 encompasses all administrative transportation requirements for the President, Vice President, members of the Cabinet, Heads of State, and other parties as directed by the WHMO. MT-1 missions are pre-planned and executed in a controlled environment where fuel load, timing, and landing zones can be carefully controlled. MT-1 also requires executive amenities for administrative Presidential travel.

Mission Tasking Two (Contingency Operations)

MT-2

MT-2 includes all contingency support operations in support of the President, Vice President, and other personnel/agencies, as directed by the WHMO. The MT-2 mission is an unscheduled contingency operation.

Many MT-2 mission variables and risks can be controlled or mitigated by proper planning, but increased flexibility is achieved by larger performance margins.

Technology Readiness Level TRL

A technology element is "critical" if the system being acquired depends on this technology element to meet operational requirements (within acceptable cost and schedule limits) and if the technology element or its application is either new or novel or in an area that poses major technological risk during detailed design or demonstration.

VIP/passenger POTUS, VIPs, heads of state, and passengers who are authorized to transport on the VH-92A aircraft.

FOR OFFICIAL USE ONLY / SOURCE SELECTION INFORMATION SEE FAR 3.104 Page 17

Appendix C: Release of GFI

Solicitation Phase Post-Contract Award

FedBizOpps

• Draft BAA/Synopsis

• Solicitation DD254

Contact PCO

• Provide CAGE code

• Request GFI (Draft)

Verify CAGE code Mail CD w/unclassified GFI (Draft)

Final BAA Release

Contact PCO

• Request Final GFI

Mail final information

• CD w/Final

Unclassified GFI

• Company Specific

DD254

Mail CD w/Classified GFI (if applicable)

: Government Action : Contractor Action

Industry Day

Provide Feedback/Ask questions

Mail CD w/unclassified Final GFI