693KA8-24-DSIR-EPICSII-01.pdf

6932KA8-24-DSIR-EPICSII-01

Federal Aviation Administration

Enterprise Programs, Infrastructure, and Communications Services (EPICS) II Draft Screening Information Request (DSIR)– Sections B – M

June 14, 2024

693KA8-24-DSIR-EPICSII-01

i | P a g e

DRAFT

CONTENTS

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

SECTION C – DESCRIPTION /SPECIFICATIONS /STATEMENT OF WORK

C.1 Introduction

C.1.1 Objective

C.1.2 Background

C.1.3 Scope

C.1.4 Inherently Governmental Functions

C.1.5 Definition of Key Terms

C.2 Applicable Documents

C.2.1 Government Documents

C.2.2 Non-Government Documents

C.2.3 Order of Precedence Between the SOW and Applicable Documents

C.2.4 Availability of Documents

C.3 Government Furnished Items

C.3.1 Site and System Documentation

C.3.2 Facility Access

C.3.3 Workspace, Telephones, and Computers at Governmental Sites

C.3.4 Wireless Internet Access and Remote Access to the FAA Intranet

C.3.5 Government-Furnished Property

C.3.6 Other Government-Furnished Property and Information

C.4 Functional Support Areas

C.4.1 System Engineering

C.4.2 Program Management Support

C.4.3 In-Service Management and Support

C.4.4 Business and Financial-Management Support

C.4.5 Information-Systems Development and Support

C.4.6 Studies, Analyses, and Evaluations

C.4.7 Administrative Support

C.5 EPICS II Program Management and Contract Administration

C.5.1 Program Management

C.5.2 Contract Administration

C.5.3 Staffing, Recruitment, and Workforce Development

C.5.4 Monthly Status Reporting

C.5.5 Program Management Reviews

C.5.6 Participation in Meetings, Reviews, and Working Groups

C.5.7 Management, Oversight, and Tracking of Government-furnished Property ii | P a g e

Section C Appendix A – Acronyms and Abbreviations ..............................................................................................i

SECTION D – PACKAGING AND MARKING

SECTION E – INSPECTION AND ACCEPTANCE

SECTION F – DELIVERIES OR PERFORMANCE

SECTION G – CONTRACT ADMINISTRATION DATA

SECTION H – SPECIAL CONTRACT REQUIREMENTS

SECTION I – CONTRACT CLAUSES

SECTION J – LIST OF ATTACHMENTS

SECTION K – REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS

SECTION L – INSTRUCTIONS AND NOTICES TO OFFERORS

L.1 AMS Provisions

L.1.1 AMS Provisions Incorporated By Reference

L.1.2 AMS Provisions Incorporated in Full Text

L.1.3 (Additional Language) Timeframe for Filing Protests Based on Elimination from Phase II Participation

L.2 Definition of Offeror

L.3 Date, Time, and Method Of Submission

L.3.1 Date and Time (Phases I and II)

L.3.2 FAA Points of Contact

L.3.3 Submission Via Portal (Phases I and II)

L.3.4 Offeror Questions

L.4 Expenses Related to Offeror Submissions

L.5 Notification of Award and Debriefing of Unsuccessful Offerors

L.6 Number of Awards

L.7 Alternate Proposals and Overlapping Participation

L.7.1 Alternate Proposals Prohibited

L.7.2 Participation on Multiple Teams or Within Multiple Competition Categories Prohibited

L.8 Communications With Offerors

L.9 Non-Governmental Evaluators and Advisors

L.10 General Proposal Instructions

L.10.1 Volumes and Page Limits

L.10.2 Other Formatting Instructions

L.11 Volume I – Team Capability (Phase I)

L.11.1 Volume I, Section 1 – Completed Solution Delivery Team Template

L.11.2 Volume I, Section 2 – Completed Team Experience Template

L.12 Volume II – Technical (Phase II)

L.12.1 Volume II, Section 1 – Technical Approach iii | P a g e

L.12.2 Volume II, Section 2 – Scenario Responses

L.13 Volume III – Management (Phase II)

L.13.1 Volume III, Section 1 – Management Processes Narrative

L.13.2 Volume III, Section 2 – Staffing Narrative

L.13.3 Volume III, Section 3 – Key Personnel Resumes

L.14 Volume IV– Past Performance (Phase II)

L.14.1 Volume IV, Section 1 – List and Description of Past Performance References

L.14.2 Volume IV, Section 2 – Past Performance Questionnaires

L.15 Volume V – Price (Phase II)

L.15.1 Volume V, Section 1 – Price Narrative

L.15.2 Volume V, Section 2 – Price Worksheet

L.16 Volume VI – Other Requirements (Phase II)

L.16.1 Volume VI, Section 1 – Contract Documents and Associated Information

L.16.2 Volume VI, Section 2 – Subcontracting

L.16.3 Volume VI, Section 3 – Organizational Conflicts of Interest and oci mitigation plan

L.16.4 Volume VI, Section 4 – Documentation of Offeror Responsibility

SECTION M – EVALUATION FACTORS FOR AWARD

M.1 AMS Clauses and Provisions

M.1.1 AMS Clauses and Provisions Incorporated by Reference

M.1.2 AMS Clauses and Provisions Incorporated in Full Text

M.2 Source Selection Approach

M.2.1 Two-Phase Evaluation

M.2.2 Competition Categories

M.2.3 Basis of Award

M.2.4 Eligibility for Award

M.3 General Evaluation Information

M.3.1 Initial Review

M.3.2 Rejection of Non-Responsive and Unrealistic Proposals

M.3.3 Communications with Offerors

M.4 Relative Importance of Factors and Sub-Factors

M.5 Adjectivally Rated Factors and Sub-Factors

M.5.1 Factor 1 - Team Capability (Phase I)

M.5.2 Factor 2 – Technical Capability (Phase II)

M.5.3 Factor 3 – Management Approach (Phase II)

M.5.4 Adjectival Ratings and Definitions

M.6 Factor 4 - Past Performance (Phase II)

M.6.1. Inputs iv | P a g e

M.6.2 Recency and Relevance

M.6.3 Evaluation Methodology and Ratings Definitions

M.7 Factor 5 - Price (Phase II)

M.7.1 Total Evaluated Price

M.7.2 Price Reasonableness

M.7.3 Price Realism

M.7.4 Balance

M.8 Other Proposal Elements Pertaining to Eligibility (Phase II)

M.8.1 Contract Documents and Associated Information

M.8.2 Subcontracting

M.8.3 Conflict of Interest

M.8.4 Responsibility Determination

PART I – The Schedule

Section B– Supplies or Services and Prices/Costs

B-1 | P a g e

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 GENERAL

This section defines the prices for services to be provided under the Enterprise Programs, Infrastructure, and Communications Services II (EPICS II) contract as described within Section C, Statement of Work (SOW). The Contractor must provide all resources and equipment (except as expressly stated in this contract as furnished by the Government) necessary to support the delivery of the required services.

All terms and conditions contained in this document are applicable to all orders issued unless explicitly stated otherwise.

B.2 CONTRACT TYPE

(a) This is an Indefinite Delivery, Indefinite Quantity (IDIQ) type contract. Services under this contract will be ordered by placing Task Orders (TOs) against the contract using the ordering procedures described in Section G, Contract Administration Data.

(b) TOs issued against this contract may be Time and Materials (T&M), Fixed Price (FP), or hybrid (contain a mix of T&M and FP Contract Line Items [CLINs]).

(c) Task Orders may include options.

B.3 MAXIMUM CONTRACT VALUE

The maximum cumulative dollar ceiling value of all contracts awarded under this SIR is $TBD. As a result, the contracts awarded under this SIR are subject to a joint, pooled ceiling equal to $TBD.

B.4 GUARANTEED MINIMUM QUANTITY OF WORK

The Government will order at least $10,000 of work for each prime awardee during the term of this contract.

The Government will have fully met the guaranteed minimum once the aggregate dollar value of orders placed on each contract equals or exceeds $10,000.

B.5 CONTRACT PRICING

The following section describes pricing requirements for T&M and FP TOs. Hybrid task orders (containing both T&M and FP CLINs) will clearly specify the contract type for each CLIN. The pricing terms in B.5.1 apply to T&M CLINs. The pricing terms in B.5.2 apply to FP CLINs.

B.5.1 TIME-AND-MATERIALS PRICING

(a) T&M Ceiling Rates

Attachment B-1, Labor Rate Tables, specifies the maximum fixed hourly rate for each labor category that the Contractor may charge under this contract. All TOs issued on a T&M basis are subject to the ceiling rates set forth in Attachment B-1, Labor Rate Tables. The maximum labor rates in Attachment B-1, Labor Rate Tables, reflect fully burdened hourly rates for each labor category and apply to all direct labor hours. In accordance with the AMS clause 3.3.1-5 Payments under Time-and-Materials and Labor-Hour Contracts (October 2021), incorporated into Section I, the rates in Attachment B-1, Labor Rate Tables, wages, indirect costs, general and administrative expense, and profit. The Contractor may propose lower hourly rates on a TO-by-TO basis.

(b) No Change to Rates if Subs Are Added or Deleted

The maximum fixed hourly labor rates in Attachment B-1, Labor Rate Tables, represent the maximum hourly rates of the Contractor and all its subcontractors. The maximum fixed hourly labor rates in

B-2 | P a g e

Attachment B-1, Labor Rate Tables, will not change after the contract award regardless of whether a subcontractor is removed by the Contractor or a new subcontractor is added by the Contractor.

(c) Geographic Area

The maximum labor rates set forth in Attachment B-1, Labor Rate Tables, reflect fully burdened rates for performance at Government sites within the Washington, D.C., metropolitan area and outside of the Washington, D.C., metropolitan area (non-D.C.) as well as for performance at Contractor site locations within those two geographic areas.

(d) Government, Contractor Site & Remote Workers

1) Government Site Rates: When performing at Government sites, the Attachment B-1, Labor Rate Tables, fully burdened labor rates must reflect that the Government will provide office space, furniture, office equipment, and supplies necessary for the Contractor personnel to perform the work specified in the individual TOs.

2) Contractor Site Rates: When performing at a Contractor site, the Attachment B-1, Labor Rate Tables, fully burdened labor rates must include applicable indirect costs for office space and all normal supplies and services required to support the work. This includes but is not limited to telephones; copiers; personal computers with Internet access; postage; ordinary business software to support, for example, word processing, spreadsheets, and graphics; and copying and reproduction.

3) Telework Rates: Contractor resources designated for full-time telework must be proposed and invoiced at the non-DC Contractor site rates specified in the Attachment B-1 Labor Rate Tables.

Except for laptops, network access, and peripherals provided as GFP (if any), the fully burdened labor rates must include applicable indirect costs for all normal supplies and services required to support the work as defined in Section (d)(2), above.

(e) T&M TOs and CLINs

1) The Government will acquire services via T&M TOs based on direct labor hours at specified fixed hourly rates as specified in each TO.

2) The TO will specify the estimated cost of materials. Unless otherwise agreed to by the parties, the material cost estimate will reflect the Contractor’s proposed estimate.

3) The cumulative total of all labor hours ordered plus estimated materials costs will define each T&M TO ceiling price.

(f) Materials (T&M TOs and CLINs)

See AMS clause 3.3.1-5 Payments under Time-and-Materials and Labor-Hour Contracts, incorporated into Section I for definitions and information on allowable indirect costs.

In accordance with the clause and with the Contractor’s proposal, the Contractor will apply an indirect rate of TBD to materials.

(g) Travel (T&M TOs and CLINs)

The metropolitan area corresponding to an individual’s labor rate represents the individual’s official station duty for purposes of determining what constitutes official travel and reimbursable expenses.

Section G.8 sets forth additional requirements with respect to travel.

B-3 | P a g e

B.5.2 FIXED-PRICE (FP) TOS

For FP-type TOs, the TO proposal instructions will detail how the FP prices will be established based upon the technical requirements, milestones (if applicable), and deliverables.

B.6 CLIN STRUCTURE

(a) The CLIN structure for this contract is provided in Table B-6. Services will be ordered and must be invoiced in accordance with this CLIN structure and performed in accordance with Section C and individual task orders SOWs.

Table B.6-1 – CLIN Structure

CLIN Labor Category Title Wash, DC, Unit Price

[Contr. Site]

Wash, DC, Unit Price

[Govt. Site]

Non-Wash, DC Unit Price

[Contr. Site]

Non-Wash, DC Unit Price

[Govt. Site]

(b) CLIN Structure Description

1) Labor CLINs

Each labor CLIN is structured as a four-digit number starting at X001, with the first position representing the contract year. The first year of the contract is represented with the number 1, the second year is represented with the number 2, and so forth, e.g. 1001 or 2001. Individual labor categories under each CLIN are established as sub-CLINs with the fourth position representing the specific labor category and the alpha character representing the individual level of the labor category, with “A” representing the lowest rate and “E” representing the highest rate within the labor-category series. For example, the first three sub-CLINs of the first labor category in the first contract year would be 1001A, Acquisition Specialist Level 1;

1001B, Acquisition Specialist Level 2; and 1001C, Acquisition Specialist Level 3.

2) Materials CLINS

Materials charges must be billed using the following CLIN structure: X000M, with the first position representing the year of the contract in which the charge was incurred, e.g. 1000M.

3) Travel CLINS

Travel charges must be billed using the following CLIN structure: X000T, with the first position representing the year of the contract in which the charge was incurred, e.g. 1000T.

B.7 ADDITIONAL LABOR CATEGORIES

At any time during the life of the contract the Contractor may propose additional labor categories to support requirements of the contract or a specific task order. The Government will assess whether they are necessary for the scope of the effort and whether it is in the Government’s interest to add them to labor schedule. If it in the Government’s interest, the parties will negotiate the labor categories, descriptions, and rates. Upon the Contracting Officer’s determination that rates are fair and reasonable, the Government will incorporate them into Attachment B-1, Labor Rate Tables, via a bilateral modification.

(End of Section B)

Section C– Description / Specifications / Statement of Work

C-4 | P a g e

SECTION C – DESCRIPTION /SPECIFICATIONS /STATEMENT OF WORK

C.1 INTRODUCTION

C.1.1 OBJECTIVE

The objective of the Enterprise Programs, Infrastructure, and Communications Services (EPICS) II acquisition is to obtain the support services required to meet the mission objectives of the Telecommunications Integrated Services Organization (TISO/AJM-5), the Communications, Information and Network Programs (CINP) Group (AJM-31), the Data Communications program (AJM-34), and other FAA organizations that support or share those objectives as described in C.1.2. Collectively, these organizations are referred to as the “Customer Organization”.

C.1.2 BACKGROUND

Communications infrastructure and services are vital to operation of the National Airspace System (NAS) as well as the FAA’s administrative and mission support functions as a federal agency. The FAA has multiple organizations that are responsible for providing and managing the communications infrastructure and services and each has a specific mission as described below based on the underlying communications technologies and networks:

• TISO – The mission of the TISO is to address the challenges associated with discontinuing the legacy FAA Telecommunications Infrastructure (FTI) network while implementing the new FAA Enterprise Network Services (FENS) network. The TISO is responsible for leading and managing all functional aspects of the FAA’s telecommunications portfolio, including acquisition, program management, engineering and integration, implementation and transition, operations, and information security.

• CINP – The CINP Group is responsible for the engineering, acquisition, management and implementation of the FAA’s portfolio of communications services and systems including: a) enterprise communications services for NAS operations, b) enterprise administrative and mission support communications services for the FAA, and c) voice communications systems for NAS operations.

• System-Wide Information Management (SWIM) – The SWIM team (AJM-316) within the CINP is responsible for providing enterprise messaging services that facilitate data sharing requirements for the FAA’s Next Generation (NextGen) air traffic control system as well as the data sharing requirements of Mission Support applications. SWIM provides a single point of access for aviation and agency data that is authorized for release, serving as the digital data-sharing backbone and enabling increased common situational awareness and improved operational agility.

• Data Comm – The Data Comm program is responsible for providing data communications services between the pilots and air traffic controllers, as well as enhancing air traffic control (ATC) information available to airline operations centers. Data Comm provides a data interface between ground automation and flight deck avionics for controller and pilot communications. Data Comm allows pilots and controllers to exchange and manage ATC clearances, instructions, traffic flow management notices, and flight crew requests and reports.

In supporting the missions of these organizations, the EPICS II contractor will be required to provide subject matter expertise in a broad range of communications and related technologies, including but not limited to:

Internet Protocol (IP) networking; Time Division Multiplexing (TDM)-to-IP protocol conversion, cybersecurity including encryption, firewalls, virtual private networking, etc.; voice switching, enterprise messaging including Web Services and Publisher/Subscriber models; Cloud computing, wireless communications including satellite, microwave, and Long-term Evolution (LTE)/4G/5G/6G cellular, air/ground radio communications, ground/ground air traffic control voice communications, unified communications, voice and video conferencing, aeronautical communications, and legal voice recording.

C-5 | P a g e

In addition, the EPICS II contractor will be required to possess an understanding of the challenges associated with implementing and operating these communications technologies in the NAS operating environment, which includes both domestic and international deployments.

C.1.3 SCOPE

The scope of the EPICS II acquisition consists of seven distinct functional support areas listed below:

• System Engineering

• Program Management Support

• In-Service Management and Support

• Business and Financial Management

• Information Systems Development and Support

• Studies, Analyses, and Evaluations – and –

• Administrative Support.

Specific support requirements will be ordered via Task Order (TO) and TOs may encompass any combination of the functional support areas identified in this contract-level SOW. Each TO will have an associated TO SOW that identifies specific programs, organizations, initiatives, objectives, and functional areas to be supported, the place of performance, deliverables, and other pertinent information. In addition, the EPICS II contractor is responsible for the management and oversight of all work efforts performed under this contract.

C.1.4 INHERENTLY GOVERNMENTAL FUNCTIONS

In its performance of this contract, the Contractor must not perform any Inherently Governmental Functions, as identified in Acquisition Management System (AMS) Guidance T3.8.2(3)(a). Inherently Governmental Functions are so intimately related to the public interest as to require performance by Federal Government employees. Inherently Governmental Functions include functions that require either the exercise of discretion in applying Federal Government authority or the making of value judgments in making decisions for the Government. This includes, but is not limited to, binding the Government to take or not to take some action by contract, policy, regulation, authorization, order, or otherwise, and exerting ultimate control over the acquisition, use, or disposition of the property of the United States, including the collection, control, or disbursement of appropriations and other Federal funds.

C.1.5 DEFINITION OF KEY TERMS

Within this SOW and associated task orders, references to “the Contractor” apply to the EPICS II Contractor. References to “vendors” and “service providers” apply to other contractors from which the TISO, CINP, and Data Comm obtain systems and services.

C.2 APPLICABLE DOCUMENTS

Applicable documents consist of Government documents as well as non-Government documents, and are incorporated into this SOW. The Contractor is responsible for reviewing all applicable documents, understanding their impact on the delivery of the required services, and complying with the applicable requirements. The most current version of each document at time of contract award will be the applicable version at the beginning of contract performance. When and if updates are made to applicable documents during the contract period of performance, the Contractor will be allowed to assess the update for any effect on contract performance before it is incorporated into the contract.

C-6 | P a g e

The specific standards and orders applicable to particular work efforts will be identified in each TO SOW.

C.2.1 GOVERNMENT DOCUMENTS

Table C.2.1-1 lists applicable Government documents. These documents apply to the extent stated in the order, standard, manual, policy, specification, handbook, or guide. Where a governance document requires the Agency to identify specific requirements or standards (e.g., Section 508 EIT standards), the FAA will specify those elements in the associated task order.

Table C.2.1-1. Applicable Government Documents Document Type Number Title FAA Order 1000.37C Air Traffic Organization Safety Management System FAA Order 1050.1F Environmental Impacts: Policies and Procedures FAA Order 1100.161A Aviation Safety Oversight FAA Order FAA-C-1217G Electrical Work, Interior FAA Order 1370.117 National Airspace System (NAS) Internet Protocol (IP) Addressing Policy FAA Order 1370.121B FAA Information Security and Privacy Program & Policy FAA Order 1600.1F Personnel Security Program FAA Order 1600.69D FAA Facility Security Management Program FAA Order 1800.66A Configuration Management Policy FAA Order 3900.19D FAA Occupational Safety and Health (OSH) Policy FAA Order 3900.57A EOSH Requirements in the Planning and Execution of Construction and

Maintenance Activities at NAS Facilities FAA Order 3900.64A Air Traffic Organization Electrical Safety Program FAA Order 6050.19G Radio Spectrum Planning FAA Order 6050.32B Spectrum Management Regulations and Procedures Manual FAA Order 6950.27B Power System Analyses: Load Flow Calculations, Short Circuit Analysis, Protective Devices Coordination Study, and ARC Flash Risk Assessment FAA Order 8040.4C Safety Risk Management Policy FAA Standard HF-STD-001B Human Factors Design Standard FAA Standard HF-STD-004a Human Factors Engineering Requirements FAA Standard FAA-STD-013D Quality Control Program Requirements FAA Standard FAA-STD-016A Quality Control System Requirements FAA Standard FAA-STD-019F Lighting and Surge Protection Grounding, Bonding, and Shielding

Requirements for Facilities and Electronic Equipment FAA Specification FAA-G-2100H Electronic Equipment, General Requirements FAA Guide PMO-PLN-0002 PMO Risk, Issue, and Opportunity (RIO) Management Plan (RMP) FAA Manual N/A Air Traffic Organization (ATO) Safety Management System (SMS) Manual FAA Guide N/A ATO Safety Risk Management Guide for System Acquisition (SRMGSA) AMS Policy N/A AMS Policy Section 4.4, Test and Evaluation FAA Handbook N/A FAA/WJHTC Test and Evaluation Handbook FAA Handbook N/A FAA Security Authorization Handbook Government Standard Section 508 of the

Rehabilitation Act - 29 U.S.C. § 798

Information Technology Accessibility Standards

Government Standard 29 CFR 1910, Subpart S

Occupational Safety and Health Standards – Electrical

Government Standard 29 CFR Part 1960 Basic Program Elements for Federal Employees Occupational Safety and Health Programs and Related Matters

C-7 | P a g e

Document Type Number Title Government Standard 29 CFR 1910.1001 Occupational Safety and Health Standards – Toxic and Hazardous Substances

– Asbestos Military Standard MIL-STD-1472 Human Engineering Government Standard NIST SP 800-18 Guide for Developing Security Plans for Federal Information Systems Government Standard NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and

Organizations Government Standard NIST SP 800-61 Computer Security Incident Handling Guide OMB Memorandum M-14-04 Reporting Instructions for the Federal Information Security Management Act and Agency Privacy Management

C.2.2 NON-GOVERNMENT DOCUMENTS

The following non-Government documents are applicable to the performance of Contractor work efforts.

Unless specifically identified by version, the latest version of the document applicable is the one that was current at the time of contract award.

Table C.2.2-1. Applicable Non-Government Documents

Document Type Number Title Commercial Standard ANSI Z535.4 Product Safety Signs and Labels Commercial Standard ANSI/EIA-748 Earned Value Management Systems Commercial Standard NFPA70E Standard for Electrical Safety in the Workplace Commercial Standard NFPA 101 Life Safety Code Commercial Standard GEIA-STD-0007 Logistics Product Data (Engineering Drawing Preparation & Support) Commercial Standard ASME Y14.100-

Engineering Drawing Practices

International Standard AS9100 Rev. D (2016)

Quality Management System – Requirements for Aviation, Space and Defense Organizations

International Standard ISO 9001:2015 Quality Management Systems

C.2.3 ORDER OF PRECEDENCE BETWEEN THE SOW AND APPLICABLE DOCUMENTS

(a) If the requirements of this SOW and the Applicable Documents referenced in SOW Paragraph C.2 are in conflict, the SOW has precedence. Requirements stated within TO SOWs also have precedence over requirements stated in Applicable Documents.

(b) If the Contractor identifies a potential conflict between the SOW and the Applicable Documents, the Contractor must advise the FAA Contracting Officer (CO) for resolution of the potential conflict.

C.2.4 AVAILABILITY OF DOCUMENTS

Copies of FAA orders, directives, and policies may be obtained from the FAA Contracting Officer as identified in Section G of this contract. Contractor requests for applicable documents must clearly identify the title and/or number of the document.

Websites where additional supporting information is available are listed below:

• Orders and Notices:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/18

• Forms:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184

C-8 | P a g e http://www.faa.gov/library/forms/

• Acronyms and Abbreviations:

https://www.faa.gov/jobs/abbreviations/

• Contractor & Industrial Security Program:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/document id/15573

The Contractor is responsible for notifying the Contracting Officer if these links are not available.

C.3 GOVERNMENT FURNISHED ITEMS

C.3.1 SITE AND SYSTEM DOCUMENTATION

The Government will provide currently available site and system documentation (e.g., site drawings, building blueprints, system drawings, rack elevation drawings, etc.) when needed by the Contractor to support the delivery of the required services.

C.3.2 FACILITY ACCESS

The Government will provide the Contractor with access to Government facilities and arrange for Contractor access at non-Government facilities as needed.

C.3.3 WORKSPACE, TELEPHONES, AND COMPUTERS AT GOVERNMENTAL SITES

For Contractor personnel working under a Government Site Rate as defined in Section B of this contract, the Government will provide workspace, a computer, software, and access to network printers for the performance of assigned work efforts under this contract. Contractor personnel must comply with the Government’s applicable usage policies for all GFP.

C.3.4 WIRELESS INTERNET ACCESS AND REMOTE ACCESS TO THE FAA INTRANET

When required to perform the specific duties and roles assigned under this contract, the Government may provide, at no expense to the Contractor, mobile broadband modems and remote access to the FAA Intranet to CO-authorized Contractor personnel. Government approvals of mobile broadband modems and FRAC accounts for remote access will be reassessed annually on an individual basis.

C.3.5 GOVERNMENT-FURNISHED PROPERTY

The Government may provide Government-furnished property (GFP) when the Government determines it to be required for the Contractor to perform specific work efforts authorized under this contract and specifies the GFP to be provided in a task order. All GFP is the property of the Government and must not be transferred to any individual or agency, public or private, without the express written approval of the

CO.

C.3.6 OTHER GOVERNMENT-FURNISHED PROPERTY AND INFORMATION

Other GFP not described in Paragraphs C.3.1 through C.3.5, including information, material, and equipment, may be specified within individual task orders as required. Unless otherwise approved, the Contractor will not be provided with Government-furnished laptops or mobile phones.

C.4 FUNCTIONAL SUPPORT AREAS

Task orders issued under the EPICS II contract may include any combination of the following functional support areas:

• System Engineering;

http://www.faa.gov/library/forms/ http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573

C-9 | P a g e

• Program Management Support;

• In-Service Management and Support;

• Business and Financial Management;

• Information Systems Development and Support;

• Studies, Analyses, and Evaluations; and

• Administrative Support.

The Contractor must furnish the necessary personnel, materials, equipment, and facilities required to satisfy the requirements of the individual task orders.

The following sections describe the scope of work included in each functional support area, if ordered by task order. The Contractor must not perform any work described in section C.4 or C.5 unless specifically ordered by the Government via task order.

C.4.1 SYSTEM ENGINEERING

The scope of the required System Engineering support includes the planning and development of new capabilities and improvements to existing capabilities. System Engineering involves, but is not limited to, identifying and analyzing requirements, assessing system designs and architectures, and planning and evaluating test activities to help to ensure that vendor-provided solutions meet the FAA’s operational needs.

To perform the required work efforts in this area, the Contractor must possess, maintain, and apply an in-depth understanding of industry-standard reference architectures, the NAS Enterprise Architecture framework, and NAS subsystem functions and interfaces.

C.4.1.1 REQUIREMENTS DEFINITION AND ANALYSIS

The Contractor must support the definition and analysis of functional and performance requirements, including but not limited to:

• Identifying, collecting, documenting, and configuration managing requirements for Initial Requirements Documents (IRDs), Final Requirements Documents (FRDs), Service Specification Documents, Interface Requirements Documents (IRDs), Interface Control Documents (ICDs), and other system and procurement specifications;

• Performing lifecycle engineering to identify and manage requirements for system lifecycle attributes including but not limited to deployment and transition, integrated logistics support, sustainment and technology evolution, and disposal;

• Performing functional and system analyses to translate stakeholders’ needs into a traceable set of functional and system requirements;

• Identifying and analyzing requirements for NAS-wide information sharing capabilities including but not limited to repositories, registries, Extensible Markup Language (XML) gateways, policy servers, and message-oriented middleware;

• Collecting, analyzing, and tracking service requirements submitted by service users;

• Maintaining near- and long-term projections of service demands to facilitate network and system capacity planning; and

• Assessing and projecting when technology enhancements may be required to satisfy user requirements.

C-10 | P a g e

C.4.1.2 CONCEPT ANALYSIS

The Contractor must provide support associated with identifying and analyzing candidate alternatives and concepts that address system issues, shortfalls, technological defects, end-of-service issues, and other issues. The required support may include, but is not limited to:

• Ensuring compatibility with NAS architecture;

• Supporting lifecycle cost estimation and cost-benefit analysis;

• Performing risk assessments;

• Evaluating the supportability of NAS systems and services;

• Evaluating operational and procedural impacts;

• Evaluating environmental impacts; and

• Evaluating overall NAS schedule impacts.

C.4.1.3 ENTERPRISE ARCHITECTURE PLANNING AND ANALYSIS

The Contractor must support the development of the NAS Enterprise Architecture (EA) by supporting the proper incorporation of supported programs into NextGen planning. The Contractor must support the development and refinement of artifacts that describe the evolution from the current NAS EA to the NextGen EA. The required support may include, but is not limited to:

• Supporting strategic mission analysis, program mission analysis, and investment analysis;

• Developing operational concepts for supported programs and their translation into NextGen capabilities, operational improvements, and performance requirements;

• Developing and assessing alternative architectural frameworks (e.g. service-oriented and component-based) for system interfaces and information exchanges across the NAS enterprise;

• Performing Enterprise Infrastructure Assessment of Customer Organization programs at the various phases of the AMS acquisition lifecycle;

• Supporting the development and assessment of Enterprise Information Management (EIM) plans and enterprise-level and system-level data architectures;

• Supporting the application of the FAA’s selected architectural framework for NextGen and NextGen-enabling systems; develop reference models, address associated security issues and challenges, and possess and maintain a working knowledge of associated development products, technologies, platforms, standards, data formats, and protocols;

• Performing operational and development analyses and studies for the development and management of the NextGen EA;

• Tracking emerging technologies in the commercial marketplace and provide recommendations to the FAA about potential opportunities to improve performance and reduce cost;

• Supporting the development of technology-evolution plans and transition strategies for supported programs as applied to the NextGen EA; and

• Identifying and assessing supported system alternatives and concepts to address IT-architecture gaps, capability shortfalls, technological defects, risks, and other issues.

C-11 | P a g e

C.4.1.4 STANDARDS DEVELOPMENT, VALIDATION, AND COORDINATION

The Contractor must support development of international standards for aviation safety, performance, and interoperability. The required support may include, but is not limited to:

• Supporting standards-development organizations by acting as subcommittee coordinators, providing meeting minutes, collecting and distributing papers and materials, maintaining membership lists, and serving as administrative focal points for working-group activities;

• Supporting the delegation lead, committee, and working-group chair by preparing standards material, editing and integrating contributor submissions, collecting and resolving reviewer comments, and coordinating with other standards bodies and air navigation service providers;

• Providing standards expertise to support other development activities via technical-interchange meetings, teleconferences, and reviews;

• Supporting domestic and international user forums and panels to coordinate implementation plans and activities; and

• Supporting prototype development and validation efforts being conducted at FAA test facilities, vendor sites, and designated field locations.

C.4.1.5 PROGRAM- AND PROJECT-LEVEL ENGINEERING

The Contractor must support Program- and Project-level Engineering activities. Program- and Project-level Engineering consists of activities specific to supported programs and projects with a particular emphasis on satisfying stakeholder requirements. At the beginning of a program or project lifecycle, the conceptual Enterprise Architecture is used as an input to develop a detailed architecture, system design, and implementation plan. All these elements must be developed in coordination and collaboration with stakeholders and other support contractors to achieve organizational goals. After implementation, Program and Project Engineering continues, and the focus shifts toward enhancements and optimization.

The required support may include, but is not limited to:

• Developing, drafting, and maintaining System Engineering Management Plans;

• Collecting and validating requirements, performing architectural trade-offs, developing cost estimates and projecting funding requirements, maintaining configuration management of solutions, support the ordering of telecommunications services, and tracking program and project implementation;

• Developing, drafting, and maintaining technical specification requirements;

• Performing radio frequency (RF) engineering and spectrum-management-related activities to support the development and deployment of air/ground communications systems and components;

• Supporting the definition and conceptualization of design prototypes;

• Applying Service-Oriented Architecture (SOA) design principles to develop SOA-based architectures to facilitate the organization and utilization of distributed capabilities that may be under the control of different ownership domains;

• Performing Enterprise Infrastructure Assessments encompassing all aspects of the infrastructure, e.g.

networking, system, cloud computing, and SOA;

• Possessing, maintaining, and applying expertise in cloud computing and the potential impacts on telecommunications service needs;

C-12 | P a g e

• Developing system architectures and supporting elements including but not limited to conceptual data models, data descriptions, physical schemas, taxonomies, core service definitions, logical data models, XML schemas, and use cases;

• Establishing, maintaining, and updating a repository or registry of system-provided core services;

• Possessing, maintaining, and applying an in-depth understanding of software-engineering practices, software-development standards, and middleware technologies to support oversight of the development and implementation of systems;

• Performing reliability, maintainability, and availability (RMA) analyses;

• Assessing whether proposed designs comply with FAA and other policy, orders, and standards;

• Identifying and assessing the impacts of proposed technology upgrades;

• Performing engineering trade studies;

• Developing and reviewing Program Control Board (PCB) items;

• Reviewing NAS Change Proposals (NCPs) and provide recommendations for approval;

• Reviewing planned contract modifications that have potential technical, performance, or cost impacts;

• Reviewing and assessing vendor requests for requirements deviations and waivers;

• Performing spectrum analyses to support the planning and implementation of satellite, microwave, and wireless-based communications systems;

• Identifying and documenting telecommunications-service requirements (e.g. data rate, latency, and availability); assessing whether telecommunications requirements submitted by customers comply with FAA and other policy, orders, and standards; developing, and maintaining all Customer Agreements in a secure repository;

• Coordinating the provisioning of telecommunications services via telecommunications architecture, requirements change board, and schedule change board reviews, and tracking and providing feedback on telecommunications-service requirements through implementation;

• Possessing, maintaining, and applying an in-depth understanding of the Technical Operations Safety Management System;

• Supporting the development of system-safety plans; review vendor-generated safety documentation;

conduct and document system-safety assessments and hazards analyses;

• Providing technical assistance in identifying and resolving Environmental, Occupational, Safety, and Health (EOSH) issues to ensure compliance with applicable laws, regulations, and policies;

• Supporting the planning for future systems, networks, and services;

• Interfacing with stakeholders that include but may not be limited to FAA programs, aviation-industry partners (domestic and international), aviation-regulatory agencies such as ICAO, and military organizations; and

• Working with stakeholders to understand and document their requirements, system architectures, security requirements, and data flows.

C-13 | P a g e

C.4.1.6 SYSTEM DEVELOPMENT AND INTEGRATION

The Contractor must support system development and integration activities. The required support may include, but is not limited to:

• Supporting the development of requirements, specifications, and requirements traceability;

• Reviewing system documentation for the design, checkout, integration, and testing of systems at factories, test sites, and field sites;

• Monitoring manufacturers’ compliance with specifications;

• Performing technical analyses related to systems-hardware engineering, system interfaces, software engineering, and software maintenance;

• Supporting the design and implementation of interfaces among systems;

• Performing technical evaluations and analyses of Customer Organization systems in the areas of test planning, safety, logistics, and service-life-extension planning;

• Supporting technical-interchange meetings and design reviews on Customer Organization system components, software, and interfaces; this includes reviewing design changes and advising whether the system meets all requirements of specifications and referenced standards as well as required and standard engineering practices;

• Supporting working-group meetings concerning software, interfaces, hardware, and specialty engineering;

• Reviewing upgrades and modifications of any non-developmental items (NDI) and identify any issues or concerns as well as present potential resolutions; and

• Providing technical assistance in documenting system-transition requirements, and assisting in the generation of transition plans and in the actual transition of services.

C.4.1.7 TEST AND EVALUATION SUPPORT

The Contractor must support the test and evaluation of systems. The required support may include, but is not limited to:

• Developing and reviewing test plans and procedures;

• Supporting the planning and coordination of test activities;

• Observing vendor-conducted testing and provide feedback to the FAA;

• Reviewing vendor-developed test reports and provide recommendations to the FAA; and

• Executing test activities for functional, system-level, and operational testing.

C.4.1.8 SYSTEM PRODUCTION

The Contractor must support system production activities. The required support may include, but is not limited to:

• Reviewing system documentation for first-article testing at factories and production testing at one, some, or all test sites and field sites;

• Monitoring manufacturers’ compliance with production specifications;

• Observing first-article and production testing; and

C-14 | P a g e

• Performing technical analyses related to the production of systems, including problem management, hardware maintenance, system interfaces, and software maintenance.

C.4.1.9 SYSTEM PERFORMANCE

The Contractor must support system performance activities. The required support may include, but is not limited to:

• Developing performance specifications;

• Monitoring manufacturers’ compliance with specifications;

• Collecting, analyzing, and evaluating system performance data for new and existing systems;

• Reviewing modifications to systems and analyze their impacts on system performance; and

• Supporting technical-interchange meetings, design reviews, and working groups.

C.4.1.10 INTERFACE MANAGEMENT

The Contractor must provide system engineering support in the area of interface management, which includes identification, definition, and control of interfaces. The required support may include, but is not limited to:

• Analyzing and documenting whether system components work together to achieve the systems’ goals and continue to operate together as changes are made during systems’ lifecycles;

• Supporting the design and implementation of interfaces among new systems;

• Proposing and illustrating performance, physical, and functional characteristics in sufficient detail for all details on the interfaces to be determined solely from the information in the Interface Requirements Documents (IRDs) or Interface Control Documents (ICDs);

• Proposing required interface data and monitor submission of the data;

• Monitoring the interface requirements and design to detect and report any changes to characteristics that might affect compatibility among systems and equipment; and

• Communicating coordinated interface requirements and design decisions and changes to program office participants.

C.4.1.11 INFORMATION SECURITY

For both NAS and non-NAS systems, the Contractor must support the identification of threats; the assessment of risk and vulnerability; risk mitigation; incident detection and remediation; testing of proposed and applicable security solutions; and development of security policies and requirements. In addition, the Contractor must assist with evaluating, reviewing, defining, and providing recommendations regarding defense-in-depth security architectures; assessing the impact of proposed technologies; developing security plans; analyzing system and network security requirements; and validating systems-level solutions and alternatives. The Contractor must have a working knowledge of all aspects of physical and personnel security and their interrelations with information security.

The required support may include, but is not limited to:

• Supporting all activities associated with establishing and maintaining security policies and procedures for systems and networks; this includes supporting the analysis and prioritization of appropriate security-measure enhancements and upgrades and verifying and analyzing security features incorporated into new and modified systems; this also includes administering the security of software

C-15 | P a g e development and distribution platforms and, for the physical security of software-development systems, analyzing the source and impact of incursions or attempted incursions and proposing and implementing corrective responses;

• Supporting all activities associated with establishing and maintaining security policies and procedures for NAS and non-NAS systems and subsystems related to the development, maintenance, and support of the FAA Enterprise Architecture Framework including but not necessarily limited to Information System Security (ISS) portions; this includes but may not be limited to the development of all required ISS NAS EA views, datasets, and databases; the secure storage of the same; and participation in FAA NAS EA working groups;

• Maintaining awareness of applicable FAA, NIST, OMB, and other appropriate orders, policies, and guidelines, and monitoring programs and contracts to advise whether security measures are in compliance;

• Supporting the assessment of FAA security policies to advise whether they remain current as the technologies and mechanisms employed for sharing NAS data evolve;

• Providing information-security expertise to assist with analysis and certification and accreditation documentation for compliance with FAA, NIST, and other standards for accreditation; and

• Coordinating security audits and assist with the implementation of both short- and long-term mitigation strategies and alternatives for systems and networks.

C.4.1.12 CYBERSECURITY

The Contractor must provide cybersecurity expertise and support to the Customer Organization. This support requires expert knowledge of NIST standards, and federal regulations, directives, and guidelines.

It includes all aspects of a system’s security life cycle, from developing and maintaining Certification and Authorization (C&A) documentation to on-going operational security support.

The Contractor must apply the ATO Risk Management Framework to current standards, guidelines, and approaches. The Contractor must support the FAA’s requirement to ensure that the Customer Organization’s cybersecurity program adheres to Federal (NIST, OMB, DOT, and FAA) executive orders, national security directives, and other regulations.

The Contractor must coordinate with Customer Organization system owners to prepare, update, and maintain the necessary system security documentation for assessment and accreditation activities of the ATO Information Systems Security Program. The Contractor must use the ATO Information System Continuous Monitoring (ISCM) templates to support the effective and efficient security documentation practices.

The Contractor must provide expert analysis and recommendations on risk (to include impact and likelihood) and mitigation options for security findings, gaps and vulnerabilities. This includes developing appropriate responses to audit report findings. If risks cannot be resolved, the Contractor must work with the system owner to develop a Deviation Waiver Request (Risk Acceptance) based on thorough analysis and industry standards identifying the risk, impact/threat if exploited, existing countermeasures, risk level, and reason/justification for risk.

The Contractor must provide a monthly Plan of Action and Milestones (POA&M) report to track the status of all POA&Ms…