N00421-14-R-0085.doc

Section A - Solicitation/Contract Form

GENERAL INFORMATION

Contract Specialist:

Jonathan Igwebueze, AIR-2.5.1.4.11 Phone: 301-737-2107 Email: jonathan.igwebueze1@navy.mil Contracting Officer:

Frank Douglass, AIR-2.5.1.4

Phone: 301-737-7556 Email: frank.douglass@navy.mil

(1) This acquisition is an unrestricted competition that will result in placement of a single award Indefinite Delivery/Indefinite Quantity (ID/IQ) contract. Both completion and term task orders will be issued under this single award task order contract. NAVAIR clause 5252.211-9503 LEVEL OF EFFORT (COST REIMBURSEMENT) (NAVAIR)(DEC 2012) will be included in term task orders.

(2) The Product/Service Code (PSC) for this procurement is AC64.

(3) The resulting ID/IQ contract will have an ordering period of five years.

(4) This contract has cost plus fixed fee and cost reimbursement (non-fee bearing) line items.

(5) The contractor will be required to have a SECRET facility clearance and a SECRET clearance for the personnel identified in Paragraph 11.3 of the Performance Based Statement of Work in Section C. The contractor will not be permitted access to classified information until a final DD254 is incorporated as an attachment to the contract award.

Section B - Supplies or Services and Prices

Navy Working Capital Funds (NWCF) Labor

CPFF

NWCF labor in accordance with Performance Based Statement of Work (PBSOW) in Section C.

FOB: Destination

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

RDT&E Labor

Research Development Test & Evaluation (RDT&E) labor in accordance with Performance Based Statement of Work (PBSOW) in Section C.

FIXED FEE

TOTAL EST COST + FEE

Other Procurement Navy (OPN) Labor

OPN labor in accordance with Performance Based Statement of Work (PBSOW) in Section C.

FIXED FEE

TOTAL EST COST + FEE

Aircraft Procurement Navy (APN) Labor

APN labor in accordance with Performance Based Statement of Work (PBSOW) in Section C.

FIXED FEE

TOTAL EST COST + FEE

Ship Conversion Navy (SCN) Labor

SCN labor in accordance with Performance Based Statement of Work (PBSOW) in Section C.

FIXED FEE

TOTAL EST COST + FEE

Foreign Military Sales (FMS) Labor

FMS labor in accordance with Performance Based Statement of Work (PBSOW) in Section C.

FIXED FEE

TOTAL EST COST + FEE

Operations&Maintenance Navy (O&MN) Labor

O&MN labor in accordance with Performance Based Statement of Work (PBSOW) in Section C.

FIXED FEE

TOTAL EST COST + FEE

Travel in support of CLIN 1001 (NWCF)

COST

ESTIMATED COST

Travel in support of CLIN 1002 (RDT&E)

ESTIMATED COST

Travel in support of CLIN 1003 (OPN)

ESTIMATED COST

Travel in support of CLIN 1004 (APN)

ESTIMATED COST

Travel in support of CLIN 1005 (SCN)

ESTIMATED COST

Travel in support of CLIN 1006 (FMS)

ESTIMATED COST

Travel in support of CLIN 1007 (O&MN)

ESTIMATED COST

Material in support of CLIN 1001 (NWCF)

ESTIMATED COST

Material in support of CLIN 1002 (RDT&E)

ESTIMATED COST

Material in support of CLIN 1003 (OPN)

ESTIMATED COST

Material in support of CLIN 1004 (APN)

ESTIMATED COST

Material in support of CLIN 1005 (SCN)

ESTIMATED COST

Material in support of CLIN 1006 (FMS)

ESTIMATED COST

Material in support of CLIN 1007 (O&MN)

ESTIMATED COST

NMCI in support of CLIN 1001 (NWCF)

ESTIMATED COST

NMCI in support of CLIN 1002 (RDT&E)

ESTIMATED COST

NMCI in support of CLIN 1003 (OPN)

ESTIMATED COST

NMCI in support of CLIN 1004 (APN)

ESTIMATED COST

NMCI in support of CLIN 1005 (SCN)

ESTIMATED COST

NMCI in support of CLIN 1006 (FMS)

ESTIMATED COST

NMCI in support of CLIN 1007 (O&MN)

ESTIMATED COST

Technical Data

Technical Data IAW DD1423, Contract Data Requirements List (CDRLs), Exhibit A. Not Separately Priced

ESTIMATED COST

CLAUSES INCORPORATED BY FULL TEXT

5252.211-9503

LEVEL OF EFFORT (COST REIMBURSEMENT) (NAVAIR)(DEC 2012)

(a) The level of effort estimated to be ordered during the term of this contract is 620,640 man-hours of direct labor including authorized subcontract labor, if any. The contractor shall not, under any circumstances, exceed one hundred (100%) percent of the total level of effort specified in the contract/order.

(b) FAR Clause 52.232-20, "Limitation of Cost" applies to fully funded orders and FAR Clause 52.232-22, "Limitation of Funds" applies to incrementally funded orders. Nothing in this clause amends the rights or responsibilities of the parties hereto under either of those two clauses. In addition, the notifications required by this clause are separate and distinct from any specified in either FAR Clause 52.232-20 or FAR Clause 52.232-22.

(c) In the event that less than one hundred (100%) percent of the established level of effort of the contract/order is actually expended by the end of the performance period, the Government shall have the option of:

(1) Requiring the Contractor to continue performance, subject to the provisions of the FAR Clause 52.232-20 or 52.232-22, as applicable, until the effort expended equals 100% of the established Level of Effort; or

(2) Effecting a reduction in the fixed fee by the percentage by which the total expended man-hours is less than one hundred (100%) percent of the established Level of Effort.

(d) The contractor agrees that effort performed in fulfillment of level of effort obligations under this contract shall include only verifiable effort in direct support of the work specified. It shall not include efforts such as work performed in transit to or from an employee's usual workplace, work during lunchtime activities, or effort performed at other non-work locations.

(e) In performing the contract/order, the contractor may use any reasonable combination of hours for the labor categories in support of section C of this contract/order.

Section C - Descriptions and Specifications

PBSOW

PERFORMANCE BASED

STATEMENT OF WORK (PBSOW)

ENGINEERING AND INTEGRATION SUPPORT

FOR

RELATIVE NAVIGATION SYSTEMS FOR AIR TRAFFIC CONTROL

The Air Traffic Control (ATC) Systems Division, NAWCAD, provides engineering support for aircraft and shipboard systems that provide and/or receive data that is used for marshal, approach, final, tanking and departure phases of flight. The ATC is acquiring program management and engineering support for manned and unmanned programs that utilize relative navigation (RelNav) systems for air traffic control, approach and landing, and refueling.

1.0 SCOPE. This SOW establishes the requirements for Production and Engineering Services in support of the programs and entities listed above. ATC performs the following tasks to support its customers: requirements definition support and analysis; Concept of Operations (CONOPS) development; prototyping; test and evaluation; technical assistance; systems analysis and engineering; software development, integration and maintenance; hardware development, installation and maintenance; test data acquisition, reduction and analysis; technical logistics support; configuration management; training support; modeling and simulation; program and project management.

2.0 APPLICABLE DOCUMENTS. The following is a list of known documents that will be needed, used and referred to during the performance of the technical and engineering services required by this SOW Unless otherwise noted, the revision level and date for each document, specification or standard cited shall be that listed in the Department of Defense ASSIST Database (http://assistdocs.com/search) in effect on the date of contract award or at the time an option is exercised. When referenced document titles, revision letters and dates of issue are omitted for brevity of reference, the short form reference shall be understood to be the specific issue identified in this section.

NUMBER

TITLE

DoD Manual 5200.01 DoD Information Security Program, Vol 1 through 4

DoD Instructions 5000.2 Operation of the Defense Acquisition System

NAVAIRINST 4355.19D

Systems Engineering Technical Review Process Naval Systems Engineering Guide

Other Documents:

National Industrial Security Program Operating Manual (NISPOM)

DoD Joint Travel Regulations, Vol 2

UCAS Common Objectives Document (COD)

Concept of Operations for Future Air Traffic Control Operations using the Sea-based Joint Precision Approach and Landing System (JPALS)

3.0 REQUIREMENTS. The Contractor shall provide support in defining customer requirements and engineering support for the JPALS, X-47, UCAS, UCLASS, STUAS, Firescout, NAVY and Air Force AAR, SALRS, and SALTI Programs and shall work in conjunction with the respective teams within the ATC Systems Division. Support shall include analysis, recommendations, alternatives, reviews, research and plans.

3.1 Detailed Requirements.

3.1.1 Carrier (CV) Suitability (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall provide CV Suitability products and services to include, at a minimum, system engineering, operational assessment analysis, training support, development of the concept of operations, future air traffic control requirements and design analysis, CV integration, test and evaluation associated with the RelNav landing systems, associated CV work centers and their systems/sub-systems.

3.1.1.1 Progress Reports. The Contractor shall provide monthly Contractor’s Progress, Status and Management Reports for the RelNav CV Suitability team progress including Automated Air Refueling (AAR), Air/Ship Integration (A/SI) and War Fighter Networking (WFN) efforts (CDRL A001) as required by individual task orders.

3.1.1.2 Briefings and Plans. The Contractor shall provide architecture briefings and plans for the AAR, A/SI and WFN efforts (CDRL A004) as required by individual task orders.

3.1.2 Systems Engineering and System Acquisition Support (1001, 1002, 1003, 1004, 1005, 1006, and 1007). It is the Government’s intention to conduct a set of system engineering reviews, at their discretion, for projects that include system design and delivery as outlined in NAVAIRINST 4355.19D. In the case that the NAVAIRINST is not applicable, the Government will specify in writing the relevant directive to be followed. For non-acquisition category (ACAT) programs, it is likely that, at a minimum, System Requirement Reviews (SRRs), Preliminary Design Reviews (PDRs), Critical Design Reviews (CDRs) and System Verification Reviews (SVRs) will be conducted on projects where a system will be developed or delivered. Other reviews that may occur at the Government’s discretion are: Initial Technical Reviews (ITRs), Alternative System Reviews (ASRs), System Functional Reviews (SFRs), Software Specification Reviews (SSRs), Integration Readiness Reviews (IRRs), Test Readiness Reviews (TRRs), Physical Configuration Audits (PCAs) and In Service Reviews (ISRs). A Design Review Information Package shall be provided for each Review (CDRL A005) as required by individual task orders.

In an effort to successfully navigate the System Engineering Technical Review (SETR) process, the Contractor must have a robust Systems Engineering model utilized in the engineering of their systems. Upon contract award, the Contractor’s System Engineering process will be reviewed by the Government for completeness and acceptability.(CDRL A008) Additionally, at the Government’s discretion, the Contractor shall be required to develop a Systems Engineering Plan (SEP) (CDRL A006) for projects/programs deemed to have sufficient complexity. The SEP will encompass the project/program’s technical approach, including processes, resources, metrics, applicable performance incentives and the timing, conduct and success criteria of technical reviews for tasking that includes system design or delivery.

The Contractor shall provide engineering and program management expertise to support systems engineering and acquisition. Specifically, the Contractor shall:

a.

Develop, maintain and update program documents including: Concept of Operations (CONOPS) (CDRL A007); Capability Description Document (CDD) (CDRL A008); System Requirements Document (SRD) and Demonstration SRD (CDRL A009); Cost Analyses (CDRL A010); Analyses of Alternatives (AOA) (CDRL A011); Acquisition Strategies (CDRL A012); Program Schedules (CDRL A013); Test and Evaluation Master Plans (TEMP) (CDRL A014); Specifications, Engineering Change Proposal (ECP) documentation (CDRL A015); Configuration Control Board (CCB) documentation (CDRL A016); Software Support Activity (SSA) requirements documentation (CDRL A017); Interface Control Documents (ICD) (CDRL A018); Test and Evaluation Requirements Analysis (TERA) (CDRL A019) and other documents essential to the system acquisition process. (CDRL A008) b.

Provide systems engineering support to the Carrier Suitability team for the purposes of developing the AAR technology as related to UCAS operations in the CV control area.

c.

Identify system and integration requirements and evaluate integration performance. (CDRL A021) d.

Attend and participate in Design Reviews, Risk Meetings, Systems Working Group Meetings, Technical Interchange Meetings, Program Review Meetings and Test Planning Meetings in support of system/software development and test and evaluation projects. (CDRL A030) e.

Provide assistance in the development of Technology Maturation and Technology Readiness Assessments (CDRL A020).

f.

Provide support for Technical Demonstrations including planning and documentation.

g.

Analyze system operational requirements, functional requirements, installation requirements, operator interface requirements, hardware-software requirements and specifications for new or modified systems and equipment providing an analysis report (CDRL A021).

h.

Ensure proper flow-down and traceability of requirements throughout the requirements-to-design process (CDRL A022).

i.

Support system integration efforts. This encompasses on-site system and software engineering support for the systems engineering projects, including requirements development, software configuration management, unit testing and installed system testing. (as required by individual task orders.)

3.1.3 Technical Development Planning 1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall provide engineering and program management expertise to support technical development planning. The Contractor shall:

a.

Provide alternatives and recommendations for program development, test and evaluation, and fleet support (CDRL A019 & CDRL A023).

b.

Perform technical reviews of flight tests and demonstrations and provide recommendations for meeting project objectives (CDRL A023) c.

Coordinate with appropriate NAVAIR activities for program development and technical review.

d.

Attend meetings as authorized by Government personnel as technical and subject matter experts with Navy, other DOD and Government organizations, and other Contractor organizations as necessary to disseminate/gather information and/or coordinate the program activities. (CDRL A030) (as required by individual task orders)

3.1.4 Modeling and Simulation (M&S) Support for CV Suitability (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall support M&S efforts to include design development, analysis and test and evaluation. The Contractor shall:

a. Develop hardware-in-the-loop models of RelNav Systems to be used in simulations. Simulations may be designed to provide performance data (CDRL A024), safety analysis data (CDRL A021), certification data (CDRL A025) and other documentation for landing systems.

b. Develop cost and lead time estimates for simulations to be developed (CDRL A026).

c. Provide support for budgeting and planning for simulation software purchases.

d. Conduct analysis to ensure that simulation designs are cost effective and satisfy requirements (CDRL A021).

e.

Analyze requirements and design simulations for platforms and provide design alternatives with tradeoff analysis and risk assessments (CDRL A011).

f.

Aid in the development of specifications detailing design and expected performance (CDRL A027).

g.

Prepare status reports describing simulations under development (CDRL A028).

h.

Provide professional engineering skills and knowledge in solving problems that arise during the development or modification of simulation systems.

i.

Review simulation designs and conduct reviews.

j.

Integrate Unified Modeling Language (UML) use cases into the simulation environment.

k.

Monitor and assess simulation development and collaborate in resolving issues.

l.

Identify problems found during development and provide corrective recommendations (CDRL A023).

m.

Develop, participate in and evaluate human-machine interface demonstrations. (CDRL A023).

3.1.5 Certification Planning (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall support the development of a certification plan for ATC Operations in the CV environment by providing inputs, reviewing and commenting as required on the proposed Certification Methodology, testing, coordinating the development of certification criteria and documentation and supporting civil interoperability planning, certification and rule-making efforts associated with flight in the National Airspace (NAS), including participation in Radio Technical Commission for Aeronautics (RTCA) committees, working groups and other relevant forums as directed by the Government. Ensure timely coordination of the Navy Modernization Process (also known as SHIPMAIN) and certification process (CDRL A025).

3.1.6 Test and Evaluation Support (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall provide test and evaluation engineering expertise to support test planning, management, execution and system integration efforts. This encompasses on-site system and software engineering support for the systems engineering projects, including requirements development (CDRL A009), software configuration management, unit testing and installed system testing. The Contractor shall support data collection, analysis (CDRL A021), and test reports (CDRL A029), and coordinate test activities and resources with Government and commercial service providers.

3.1.7 Concept of Operations (CONOPS) (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall work with the system vendors, OPNAV and the fleet to write and update the CONOPS for both Operational Assessment and Fleet Introduction (CDRL A007). The Contractor shall:

a.

Plan, participate in, record meeting minutes and/or conduct meetings and briefings with operational decision makers, pilots, controllers, deck personnel and/or air boss to obtain fleet feedback and acceptance (CDRL A004 & A030).

b.

Provide requirements definition support and clarification. Focus on system capabilities, including the operational concept, environment, scenarios and end user expectations (CDRL A009).

c.

Develop, for Government approval, the release schedule for CONOPS updates and coordinate with Fleet Project Teams on same (CDRL A007).

d.

Serve the Integrated Product Teams and Future Air Traffic Control (FATC) lab evaluations to evaluate architecture options and provide definition.

3.1.8 Data Link (DL) Technology Support (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall provide engineering support for evaluation of candidate DL systems in support of developmental RelNav systems and provide analysis and troubleshooting of DL systems that are under test. The Contractor shall:

a.

Identify and clarify operational DL requirements.

b.

Evaluate performance by participating in and recording meeting minutes of periodic demonstrations, team meetings, technical discussions and teleconferences (CDRL A030).

c.

Evaluate DL such as the Tactical Targeting Network Technology (TTNT) DL technology, as related to UCAS operations in the CV control area.

d.

Coordinate with Joint Tactical Radio System (JTRS) Program Office for future integration of candidate waveforms.

e.

Coordinate with lead platforms in development and integration of DL solutions as required and directed by the Government.

f.

Provide engineering support for evaluation of the candidate DL technologies as related to sea based operations.

g.

Operate and troubleshoot DL systems in support of lab testing and flight testing.

3.1.9 RelNav Landing Systems Requirements & Design Analysis (1001, 1002, 1003, 1004, 1005, 1006, and 1007).

3.1.9.1 Analysis.

3.1.9.1.1 Design Analysis. The Contractor shall conduct design analysis of RelNav systems for applicable Navy platforms. The analysis shall include each simulation’s capabilities, interfaces, assumptions, limitations, architecture, hardware/software requirements and Life Cycle Costs (CDRL A027).

3.1.9.1.2 System Interface Requirements. The Contractor shall identify and capture interface requirements for RelNav systems under development (CDRL A018).

3.1.9.1.3 CONOPS. The Contractor shall identify and capture the following CONOPS requirements (CDRL A007).

a.

CONOPS scenarios for manned, unmanned and mixed flight ops for Carrier Control Area (CCA) and AAR b.

Operator-Issued Data Link Commands c.

Voice Recognition to Data Link Commands d.

Voice over IP (VoIP) e.

Data to Voice f.

Data Link to Speech Synthesis

3.1.9.2 Simulation Design.

3.1.9.2.1 Integration Lab Simulation/Stimulation. The Contractor shall design lab simulations to stimulate operational components for integration testing purposes.

3.1.9.2.2 CONOPS Lab Simulation/Stimulation. The Contractor shall design a simulator to evaluate and demonstrate ATC proposed operational procedures and man-machine interfaces for CCA unmanned operations. The Contractor shall develop scenarios to demonstrate and validate unmanned and mixed operations CONOPS. The proposed CONOPS simulator shall support fully simulated, as well as live unmanned and simulated legacy aircraft scenarios.

3.1.10 Design Integration (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall design and integrate Shipboard-Relative Global Positioning System (SRGPS) prototype equipment. Integrations may be required in aircraft platforms, ship platforms, the fixed site and mobile van configurations. The design shall include hardware (HW) and software (SW) platform emulation, required HW interfaces to the host platform and all required hardware including sensors, data recorders, racks, wiring and connectors. The Contractor shall prepare and deliver integration design documentation for both the initial design and for the as-built configuration (CDRL A027).

3.1.11 Ship Integration (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall provide support to the ATC Systems Division with required expertise, information and documentation to support management of all the programs, systems and products relating to ship integration of the JPALS, UCAS, UCLASS and other applicable landing systems into the shipboard environment, including coordination with PMA-251 (Landing Systems), Program Executive Officer (PEO) Aircraft Carrier, Naval Air Systems Command (NAVAIR), Naval Sea Systems Command (NAVSEA) and other Government entities, to collect data for costing and integration on related ship systems and subsystems. The technical support shall consist of system engineering, operational assessment analysis (CDRL A021), training, revisions to the operational concept (CDRL A007) and gap analyses (CDRL A021) of future air traffic control requirements. This includes general investigative research in ship integration to support JPALS, UCAS and UCLASS milestone decisions, system requirements documentation (CDRL A009), assistance in the development of a shipboard integration guide (CDRL A031) and presentations of program information.

3.1.11.1 Alteration Installation Team (AIT). The Contractor shall provide AIT services, which will be used for the installation and integration of NAVAIR Air Traffic Control Systems aboard Navy vessels. In order to provide AIT services, the Contractor must have specific knowledge associated with navigating the SHIPMAIN, approvals and associated documentation needed to successfully check into the Naval Regional Maintenance and Modernization Coordination Offices (RMMCO), the ability to provide highly precise survey data used to calculate touchdown points and lever arms and the ability to coordinate with Naval Planning Yard activities to have installation drawing packages approved.

3.1.12 Aircraft Integration (1001, 1002, 1003, 1004, 1005, 1006, and 1007). The Contractor shall provide support to the ATC Systems Division, NAWCAD Code 4.11.1, with required expertise, information and documentation to support management of the aircraft integration of RelNav systems into air platforms including providing assistance in coordinating across PMAs, including PMA-209 (Common Avionics) and specific Air Platform IPTs. The Contractor shall perform liaison duties with the lead platforms including, but not limited to, the F/A-35 Joint Strike Fighter, UCAS, UCLASS and F/A-18, supporting the coordination of interim solutions. The Contractor shall aid lead platforms with gap analysis (CDRL A021) and provide recommendations to the Government regarding cost and schedule (CDRL A010) for aircraft integration. In addition, the Contractor shall provide technical support in developing an aircraft integration guide. (CDRL A031) Additional technical support shall consist of systems engineering, operational assessments analyses (CDRL A021), training applications (CDRL A032), revisions to operational concepts (A007) and evaluation of future air traffic control requirements (CDRL A009). The Contractor shall also provide phase in plans for platform integration (CDRL A033), both forward-fit and retrofit.

3.1.13 Program Management Support (1001, 1002, 1003, 1004, 1005, 1006, and 1007).

3.1.13.1 Contract Management. The Contractor shall provide a monthly Contractor’s Progress, Status and Management Report (CDRL A001), which shall cover overall status and specific status on each effort on the contract and shall also deliver a monthly Funds Expenditure Report (CDRL A002) and Voucher Reconciliation Report (CDRL A003) as required by individual task orders.

3.1.13.2 Project Management. The Contractor shall also monitor work performed against milestones planned to assure that each project objective is met according to schedule. The Contractor shall respond to administrative and programmatic data calls, provide administrative planning related to program events and day-to-day operations and activities of assigned projects, support administrative planning, record keeping, data entry and communications including the following:

a.

Support development of life cycle cost estimates, Work Breakdown Structure (WBS) and WBS Dictionary development, Management Control System (MCS) execution and other program management tasks as assigned (CDRL A010).

b.

Perform cost analysis in support of systems development, test and evaluation, fielding, operations and support (CDRL A010).

c.

Provide cost support for Joint Services cost estimating and analysis efforts. These include services such as preparing earned value management documentation (CDRL A034), life-cycle-cost estimates and analysis (CDRL A035), budget submittal documentation, schedules, tracking status and funding expenditures, and resources.

d.

Participate in the development of acquisition documents, schedules and budgets for the systems in accordance with the Program Planning Budgeting System (PPBS) and DoD 5000.2. The acquisition plans, schedules and budgets will account for specific program elements, platform implementations and execution goals.

e.

Provide alternatives and recommendations for program development, test and evaluation, and fleet support (CDRL A023).

f.

Coordinate with appropriate NAVAIR activities for program development and technical reviews.

g.

Attend meetings as authorized by the Government as technical and subject matter experts with Navy, other DoD and Government organizations as necessary to disseminate/gather information and/or coordinate the program activities and provide meeting minutes (CDRL A030).

h.

The Contractor shall provide risk management support, which includes identification, assessment, management and tracking of program risks using the risk management database software tool prescribed by the Government. The Contractor shall schedule and convene regular Risk Board meetings and attend other associated meetings as required to support the Risk Management effort. The Contractor shall track risk actions (CDRL A036), publish minutes of meetings (CDRL A030), maintain and update the risk database and provide risk training.

i.

Provide support for the configuration control board of the appropriate documentation in support of the developmental programs.

4.0 PROGRESS REPORTS.

4.1 Funds and Time Expenditure Report. The Contractor shall prepare monthly funds and time expenditure reports, which depict the costs associated with each SOW paragraph, including a breakout of costs per task, monthly and year-to-date work hours (straight time and overtime), hourly rate and costs expended per individual (CDRL A002). These reports may be reviewed by a support Contractor for compilation of data and verification purposes. The support Contractor will submit a nondisclosure form to the Government (CDRL A037).

4.2 Voucher Reconciliation Report. The Contractor shall provide a voucher reconciliation report that explains any discrepancies from the funds and time expenditure reports and the vouchers within 10 working days after delivery of each voucher (CDRL A003).

4.3 Progress Report. The Contractor shall prepare monthly Contractor’s Progress, Status and Management Reports describing tasks performed (CDRL A001).

4.4 Segregation of Costs and Invoice Requirements. The Contractor shall provide monthly funds expenditure reports in accordance with the requirements set forth in the Segregation of Costs and Invoice Requirements below. Report data shall be separated by contract line item and shall be reported for both the current period and the contract to date. This data shall directly correspond to the monthly vouchers and any discrepancies shall be explained. These reports may be reviewed by a support Contractor for compilation of data and verification purposes. A nondisclosure agreement will be submitted by the support Contractor (CDRL A037).

The Contractor shall segregate costs incurred under this contract at the lowest level of performance, either by task or by subtask, rather than only on a Contract Line Item Number (CLIN) or total contract basis and shall submit invoices reflecting costs incurred at that level. In addition, the Contractor shall submit invoices containing summaries of work charged during the period covered, as well as overall cumulative summaries for all work invoiced to date.

When there is more than one line of accounting, the Government will describe each Accounting Classification Reference Number (ACRN) preceding the accounting citation in the contract to a particular CLIN. The Government will pay Contractor invoices by charging only an ACRN corresponding to the CLIN invoiced. Accordingly, when there are many lines of accounting, the Government will fund each CLIN separately and it will summarize the funding level for each CLIN. The Contractor’s invoices shall state separate incremental and cumulative amounts for each CLIN with further segregation by task and subtask showing each element of cost.

Invoices shall contain the following cost elements by schedule and include supporting detail. Invoices shall be submitted with two attachments. The first attachment shall contain Schedules A through D, F and G and shall be provided as fully burdened. The second attachment shall contain Schedule E.

Invoice summary for current billing period and cumulative:

(Schedule A) - Direct Labor $

(Schedule B) - Material $

(Schedule C) - Travel $

(Schedule D) - Other Direct Charges $

(Schedule E) - Indirect Charges $

(Schedule F) - Adjustments $

TOTAL $

(Schedule G) - Outstanding Commitments

Schedule A - DIRECT LABOR

Period Covered Cumulative

Employee Labor Hours Billed Burdened Hours Burdened

Identifier Category Off-site On-site* Cost** Billed Costs*

TOTAL _______ _______ $_______ _______ $______

* On-site work is considered to be work performed at a Government installation. Off-site work is work performed at the Contractor’s facility.

** Unburdened rate information shall be made available upon request. When requested, unburdened rate information shall not include indirect costs and shall reflect the actual rate paid.

Schedule B – MATERIAL

Material charges shall be itemized and shall include the invoice number, date, total amount, company, purchase order number and description of the item. A copy of the paid invoice shall be made available upon request.

Schedule C – TRAVEL

Travel charges shall be itemized and shall include the dates of travel, names of individuals traveling, destination, purpose and total cost. A copy of the travel voucher shall be made available upon request. Copies of back-up receipts need not be submitted; however, they should be retained and are subject to review.

Schedule D - OTHER DIRECT CHARGES

Other direct charges shall be itemized. Copies of invoices shall be available upon request. Subcontractor invoices shall be in the same format and require the same detail.

Schedule E - INDIRECT CHARGES

Indirect charges include those charges based upon a rate that is subject to verification by Defense Contract Audit Agency (DCAA) at contract closeout.

Schedule F – ADJUSTMENTS

Current fiscal year invoice adjustments shall be shown in this section along with the justification. Adjustments that pertain to prior fiscal years shall be invoiced separately.

Schedule G - OUTSTANDING COMMITMENTS

Any authorized expenditure that remains unpaid but will be reimbursed pending the receipt of a supplier invoice or travel claim shall be shown in this section.

Invoices that must be segregated by CLIN can either have the CLINs itemized on each schedule or each CLIN can be presented individually. The Contractor is not authorized to claim nor will the Navy pay for direct costs associated with preparation of an invoice.

Program management/support charges are limited to the first level supervisor.

4.5 Material. It will be necessary for the Contractor to have a material funding allocation (CLIN) to immediately respond to system development requirements, system failures and system operation requirements that provides sufficient funding for both the prime and all subcontractor’s immediate material needs. All incidental material will be approved per the H-1 Clause - RESTRICTION ON THE DIRECT CHARGING OF MATERIAL.

4.5.1 Material Tracking Report. The Contractor shall prepare quarterly material tracking reports that include the burdened and unburdened current and cumulative costs and any record of material transferred to the Government via Form DD1149 (CDRL A038).

4.6 Non-Disclosure Agreement List. In the performance of the contract, the Contractor may have access to non-public proprietary information. The Contractor shall require that all employees performing services under the contract execute a non-disclosure agreement satisfactory to the Contracting Officer. The non-disclosure agreement shall acknowledge the Contractor and employee’s duties with respect to non-public information and promise to comply with those obligations. Copies of the executed non-disclosure agreements shall be provided to the Government (CDRL A037).

Consistent with the terms and conditions of paragraph (e)(5) of NAVAIR 5252.209-9510, “Organizational Conflicts of Interest (Services),” with respect to proprietary data of third parties, and DFARS 252.227-7025 “Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends,” with respect to technical data, the Contractor shall not use, modify, reproduce, release, perform, display, or disclose any non-public information provided to or obtained by the Contractor in the course of performing the contract for other than Government purposes, and shall not for any commercial or personal purpose. The Contractor is responsible for executing non-disclosure agreements for the use of proprietary data owned by third parties with the data owner.

In the event that the Contractor knows of or identifies that it has a commercial interest in the subject matter of any proposed or ongoing agreement related to the services to be performed herein, the Contractor shall consider such interest a potential conflict of interest under paragraph (g) of NAVAIR 5252.209-9510, and promptly disclose it in writing to the Contracting Officer.

5.0 FACILITIES/PROPERTY.

5.1 Government Accessible Facilities. The Government will provide facilities or access to facilities and equipment in which to perform applicable performance work statement requirements. These facilities are located at Patuxent River and St. Inigoes, Maryland.

5.2 Contractor’s Facilities. The Contractor’s facility shall consist of engineering and support staff offices, design, implementation, document development, production equipment and storage spaces as necessary to fulfill the requirements of this SOW. Facilities shall be within 30 ground miles of Patuxent River, MD. The Contractor shall provide all office/facility furnishings for Contractor Facilities to support the SOW requirements. The Contractor’s facility shall meet the requirements of the DD254 form applicable to this contract.

6.0 TRAVEL. The Contractor may be required to travel to provide a range of site support services, including but not limited to, attending meetings/conferences, training, installation, integration, maintenance or system tests to support field experiments and tests and evaluation in support of manned and unmanned programs that utilize RelNav systems for air traffic control, approach and landing, and refueling. Travel shall be reimbursed, exclusive of fee, in accordance with FAR 31.2 and the Joint Travel Regulations. The Contractor shall provide personnel with passports and be able to support travel requirements within a 24 hour notice. The costs associated with obtaining passports for contractor personnel shall not be billed as a direct charge to this contract. The number of trips to each destination will vary as program requirements dictate. The contractor is responsible for making all travel arrangements for its personnel. Contractor personnel shall complete trip reports documenting the purpose of the trip, persons contacted, commitments, accomplishments, outstanding problems and recommendations after trip completion (CDRL A039).

7.0 OPERATIONS SECURITY (OPSEC). The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified and classified information and to control distribution of controlled unclassified and classified information in accordance with the National Industrial Security Program Operating Manual (NISPOM) and the DoD Information Security Program Manual (DoD 5200.01). The attached DoD Contract Security Classification Specification and DD Form 254 defines program specific security requirements. All controlled unclassified information shall be appropriately identified and marked as For Official Use Only (FOUO) in accordance with DoD 5200.01, Information Security Program: Controlled Unclassified Information (CUI) Volume 4 (enclosure 3) and DoD 5400.7-R (Freedom of Information Act Regulation) (Chapter 3). All Contractor facilities shall provide an appropriate means of storage for controlled unclassified and classified documents, equipment and materials in accordance with OPSEC requirements.

7.1 For Official Use Only (FOUO) information generated and/or provided under this contract shall be marked and safeguarded as specified in DoD 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-17) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf and DoD 5400.7-R, Freedom of Information Program Chapter 3 (pages 31-42) available at http://www.dtic.mil/whs/directives/corres/pdf/540007r.pdf.

7.2 All controlled unclassified technical information shall be appropriately identified and marked with the distribution statement identified on the source document or as directed by the COR.

7.3 The Contractor shall develop, implement and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment and material used or developed by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

a. Assignment of responsibility for OPSEC direction and implementation.

b. Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

c. Establishment of OPSEC education and awareness training.

d. Provisions for management, annual review and evaluation of OPSEC programs.

e. Flow down of OPSEC requirements to subcontractors when applicable.

The Contractor shall prepare an Operations Security Plan for Government review in accordance with CDRL A040.

7.4 The contractor will occasionally need access to Communications Security (COMSEC) material to perform various equipment tests. Cryptographic keying material is required for use in labs in NAWCAD, Patuxent River, building 2110. There may be times where COMSEC materials will have to be accessed at other facilities in order to perform the duties in this SOW. All personnel who require access to classified COMSEC information in the performance of their duties shall be briefed before access is granted. Depending on the nature of COMSEC access required, either a COMSEC briefing or a Cryptographic Access Briefing will be given. A Government employee will be required whenever contractor access to COMSEC is necessary.

7.4.1 COMSEC Briefed List. The contractor shall provide the Government COMSEC Custodian an up-to-date list of contractor personnel that have been COMSEC briefed and who require access at the Government facility in performance of this contract in all instances in which personnel are added or removed (CDRL A041).

7.4.2 COMSEC Adherence. The contractor personnel shall adhere to COMSEC rules and regulations as mandated by command policy and procedures. The contractor personnel shall be responsible for assisting Government personnel both with daily inventories of COMSEC material or equipment, and in controlling access to COMSEC-restricted areas.

8.0 WORK SCHEDULE. The Contractor shall provide the required services and staffing coverage during normal working hours (NWHs). NWHs are usually 8.5 hours (including a 30-minute lunch break), from 0730-1600 each Monday through Friday (except on the legal holidays specified elsewhere). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800 Monday - Friday. Services and staffing shall be provided for each office at least 8 hours per day (during the 8.5 hour workday which includes the 30-minute lunch break).

Government employees are allowed to voluntarily work a "Compressed Work Schedule" (CWS). CWS is an alternative work schedule to the traditional five 8.5 hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.

The Contractor awarded this contract, with agreement by the COR, may allow its employees to work a CWS schedule. Any Contractor that chooses to allow its employees to work a CWS schedule in support of this contract agrees that any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the government. Furthermore, all Contractors shall comply with the requirements of the Fair Labor Standards Act and particularly with Section 7 regarding compensatory overtime. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the Government facility.

8.1 Restricted Entry to Workplace. In the event that the Contractor is restricted from entry to the workplace due to non-controllable emergencies such as weather, power outages, etc., the Contractor shall not charge the non-work time as direct labor to the contract.

9.0 INFORMATION TECHNOLOGY (IT) CLAUSES

9.1 Clinger-Cohen Act. In 1996, Congress enacted the Clinger-Cohen Act (CCA) requiring agencies to use a disciplined capital planning and investment control process to acquire, use, maintain and dispose of information technology. In accordance with the following Department of Defense Directive (DoDD), Department of Defense Instruction (DoDI), Office of the Secretary of Defense (OSD) memo and Secretary of the Navy Instruction (SECNAVINST), CCA compliance is required for all programs that contain IT, including IT in weapons and weapons system programs. The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively. The authority to grant compliance with CCA and approve the Information Assurance (IA) strategy depends on the Acquisition Category (ACAT). Any material purchased under this contract must comply with the CCA; Applicable requirements and materials purchased under this contract require prior PCO approval.

a. DoDD Number 5000.01 “The Defense Acquisition System,” May 12, 2003, Certified Current as of November 20, 2007

b. DoDI 5000.02, “Operation of the Defense Acquisition System,” December 8, 2008

c. OSD Memo, “Clinger-Cohen Act Compliance Policy,” March 8, 2002

d. SECNAVINST 5000.2D, “Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System,” October 16, 2008

9.2 System Software / Application Compliance. All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance, DoD/NAVAIR Functional Area Management (FAM) Policies and Guidance, Network and Server Registration and Web Enablement mandates.

9.3 Software Development/Server Procurement. Any tools developed that will be hosted by the NMCI or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.

9.4 NAVY MARINE CORPS INTRANET (NMCI) INSTRUCTION

The Contractor is advised that IT services shall be ordered from the NMCI contract in accordance with the provisions of 5252.237-9503. The Contractor shall order NMCI seats and services and provide a copy of purchase order itemized by name, seat type and locations to the NAVAIR NMCI Customer Technical Representative (CTR) via the local NMCI POC. Where applicable, application tool suites under this effort shall be modernized and developed in accordance with the Navy Enterprise Application Developer’s Guide (NEADG), which includes FAM, NMCI and Task Force Web requirements. Any tools developed that will be hosted by NMCI or run on NMCI workstations will need to be certified for NMCI and comply with NMCI and Navy policy.

9.5 Information Assurance (IA). NAVAIR’s IA Program is a unified approach to protect unclassified, sensitive or classified information, and is established to consolidate and focus efforts in securing that information, including its associated systems and resources. IA is required operationally throughout the DON. The DON CIO is responsible for IT within the Navy, as mandated by the Clinger-Cohen Act, and is the lead for departmental compliance with the Federal Information Security Management Act of 2002. All IA shall be in compliance with the following listed instructions, to include those referenced within the below listing:

a. ASD (NII) Directive-Type Memorandum (DTM) 08-027 – “Security of Unclassified DoD Information on Non-DoD Information Systems”, July 31, 2009

b. Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3170.01G (series), “Joint Capabilities Integration and Development System”, March 1, 2009

c. CJCSI 6211.02C (series) –…