N00421-17-R-0049_Amendment_1.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this Amendment is to include the procurement's NAICS code information in Section A, to clarify experience as relevant experience in Section C paragraph 5.3.1, clarify proposal format and content instructions in Section L Part A paragraph 2.0 and 3.0, extend the Past Performance submittal date and time in Section L Part A 4.0 from Tuesday March 6, 2018 to Thursday March 8, 2018 at 2:00 local time, define Small Business Subcontracting Plan goals in Section L Part B 1.0 A (j) (2), corrected CPFF Table in Section L 3.0 3.6.2 Labor

Hours, and to re-issue Attachment P2 (Past Performance Information Form) so the option period numbers may be inserted.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 56

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 02-Mar-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0042117R0049

X 9B. DATED (SEE ITEM 11)

06-Feb-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

02-Mar-2018

CODE

NAVAL AIR WARFARE CENTER AD

CODE 2.5.1.11

21983 BUNDY ROAD

BLDG 441

PATUXENT RIVER MD 20670

N00421 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0042117R0049

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

POINTS OF CONTACT

CONTRACT SPECIALIST: Ken Turing

TELEPHONE NUMBER: 301-995-4213

EMAIL ADDRESS: kenneth.turing@navy.mil

CONTRACTING OFFICER: Candice Byrd

TELEPHONE NUMBER: 301-342-2581

EMAIL ADDRESS: candice.byrd@navy.mil

PCO: John Tomechko

TELEPHONE NUMBER: 301-737-7032

EMAIL ADDRESS: john.tomechko@navy.mil

CONTRACTING OFFICER REPRESENTATIVE: TO BE DETERMINED AT CONTRACT AWARD

(1) This acquisition is a full and open competition that will result in placement of a single award Indefinite

Delivery/Indefinite Quantity (ID/IQ) contract.

(2) The Product/Service Code (PSC) for this procurement is D318. The NAICS Code for this service procurement is

541512.

(3) The resulting ID/IQ contract will have a five year ordering period.

(4) This contract has Cost-Plus-Fixed-Fee (CPFF) and Firm-Fixed Price (FFP) line items for Labor and cost reimbursement line items for Travel and Material/ODC.

(5) The contractor will be required to have a TOP SECRET Facility clearance. IAW the National Industrial Security

Program Operating Manual (NISPOM) and the NAWCAD Contract Security Specification DD Form 254 Manual, Block 1.a FACILITY CLEARANCE REQUIRED indicates “the highest level of classified information the contractor will be required to access in order to perform this work.” Further, “A Contractor is required to have a

Facility Security Clearance (FCL) when one or more of its employees require a security clearance in performance of the contract and therefore access to classified information or materials. The FCL is an administrative determination that, from a national security standpoint, a facility is eligible for access to classified information at the same or lower classification category as the clearance being granted.” Therefore, since two positions (the Program Manager and the

Systems Engineer) require Top Secret clearances in performance of this contract, a Top Secret FCL is required.

Additionally, DD Form 254 block 1.b LEVEL OF SAFEGUARDING REQUIRED indicates the “level of classified material/information that the contractor will need to store at their facility.” The DD Form 254 for this solicitation states “NONE” in block 1.b and therefore, there is no requirement to safeguarded classified information at the contractor’s facility. Security clearance requirements for personnel are identified in the Performance-Based

Statement of Work (Section C), paragraph 5.5.

(6) Specifics associated with each requirement, including Period of Performance and CDRLs, will be established at the Task Order Level.

mailto:kenneth.turing@navy.mil mailto:candice.byrd@navy.mil mailto:john.tomechko@navy.mil

(7) For any task orders issued under the contract using NAVAIR clause 5252.216-9540 “Issuance of Orders using

Streamlined Procedures”, the rates in the Offeror’s submitted Cost Summary Spreadsheet (Attachment (P4) will be used to calculate the Independent Government Cost Estimate from which the value of the task order will be based.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

STATEMENT OF WORK

PERFORMANCE BASED STATEMENT OF WORK (PBSOW) TO SUPPORT THE

NAVAL AIR WARFARE CENTER AIRCRAFT DIVISION

REGIONAL MULTI-DOMAIN AWARENESS CAPABILITY

1. Scope:

The Naval Air Warfare Center - Aircraft Division (NAWC-AD) AIR 5.2 Patuxent River, Maryland requires contractor support to install, operate, and maintain United States Government owned surveillance systems. The systems requiring support are primarily, but not limited to, those developed by the Atlantic Test Range (ATR), such as the legacy SureTrak system and the newly developed/modified STING system.

This Performance Based Statement of Work (PBSOW) requires the contractor to provide support services to multiple customers, domestic and foreign, in support of the mission of the Regional

Multi-domain Awareness Capability (RMAC) Program Office. The contractor will provide technical and administrative services necessary to implement and support the RMAC program to include: system engineering, system architecture & design, sensor & system analysis, sensor & system integration, hardware analysis and testing, software development, site surveys, system installation, sensor installation, electrical analysis and troubleshooting, basic electrical installations and repairs, infrastructure modification and repairs, laboratory and field testing, data analysis, hardware and software maintenance, system operations, remote system monitoring & maintenance, training, logistics support, shipping, purchasing, inventory control and management, technical documentation, information assurance, information security, communication equipment installation and support, system integration with subsystems, subsystem analysis, basic technology research, project management, and program management.

The contractor will provide operation and maintenance services for existing and new systems including installations, integration of new capabilities, and developments and improvements to software and hardware components. This effort will require the Contractor to support high-level projects for government agencies and activities both inside and outside of NAWC-AD, including but not limited to other Department of Defense (DoD) and Federal Government agencies (Navy, Army, Air Force and NASA), State and Local Government and non-Government entities, and international installations in support of the Combatant Commands, such as United States

European Command (EUCOM), United States Africa Command (AFRICOM), United States

Southern Command (SOUTHCOM), United States Pacific Command (PACOM) and United

States Central Command (CENTCOM) and Department of State (DoS) requirements.

The contractor will be required to conduct analysis and testing on existing and new sensors and system platforms to include manned and unmanned aerial, surface, and subsurface platforms.

The contractor will integrate new sensors and platforms to enhance overall system capability to meet the demands of U.S. and partner nation requirements. The contractor will analyze other domain awareness systems for integration, augmentation, or collaboration with RMAC installations. The contractor may be required to install, maintain, support, or operate other domain awareness systems that are integrated into, used to augment existing capability, or are used in collaboration with RMAC installations.

2. Applicable documents:

2.1. RMAC Documents

2.1.1 SureTrak/STING/RMAC User’s Manual

2.2 NAVY Documents

2.2.1 NASPAXRIVINST 3432.1A – Operations Security

2.2.2 NASPAXRIVINST 5100.35D – Safety and Occupational Health (SOH) Manual

2.2.3 NASPAXRIVINST 5510.15Q – Regulations Governing Admission to Naval Air Station

Patuxent River, (NAS Pax River), Webster Field Annex, and Naval Recreation Center (NRC)

Solomons, Maryland

2.2.4 NASPAXRIVINST 12610.7H – Personnel Reporting Procedures During Emergency

Conditions

2.2.5 NAWCADINST 12620.1 CH-1 – Compressed Work Schedule

2.2.6 NAWCADINST 12792.1B – Civilian Drug-Free Workplace Program

2.2.7 OPNAVINST 3440.17A – Navy Installation Emergency Management Program

2.2.8 SECNAV M-5510.30 – Personnel Security Program

2.2.9 SECNAV M-5510.36 – Information Security Program

2.3 Federal / Department of Defense (DOD) Documents

2.3.1 DODM 5200.01, DOD Information Security Program

2.3.2 DODM 5220.22-M – National Industrial Security Program Operating Manual (NISPOM)

2.3.3 DODM 5400.07 – DOD Freedom of Information Act (FOIA) Program

2.3.4 DOD 5500.07-R – Joint Ethics Regulation (JER)

2.3.5 DODI 5230.24 – Distribution Statements on Technical Documents

2.4 Travel Documents

2.4.1 Joint Travel Regulations (JTR) Series

2.4.2 DODD 4500.54E, Foreign Clearance Program (FCP)

2.4.3 DODI 6205.4 – Immunization of Other Than U.S. Forces for Biological Warfare Defense

2.4.4 BUMEDINST 6230.15 – Immunizations and Chemoprophylaxis Reference

2.4.5 49 U.S.C. 40118 – Fly America Act,

2.5 Contract Documents / Clauses

2.5.1 DFARS 252.227-7020 – Rights in Special Works

2.5.2 DFARS 252.227-7022 – Government Rights (Unlimited)

2.5.3 DFARS 252.227-7023 – Drawings and Other Data to Become Property of Government

2.5.4 FAR Part 31 – Contract Cost Principles and Procedures

2.5.5 FAR Part 45 – Government Property

3. General Requirements: The objectives and requirements identified within this PBSOW are described in general terms. Each task order will address specific task requirements, project scheduling, and other related performance criteria as necessary. Tasking under this contract requires the contractor to provide services related to all phases of planning, development, engineering, design, procurement, site preparation, installation, testing, training, operation, and maintenance, as identified herein, in support of the RMAC program.

3.1 Compatibility: The Contractor shall maintain the capability to prepare documents and software packages compatible with the current Government IT operating environment through the security classification of Secret. The current Government IT operating environment required for this contract includes:

Microsoft Windows

Microsoft Office Professional Plus

Microsoft Project

Microsoft Visio

Adobe Acrobat Reader

The Contractor shall maintain the ability to interface with and transfer data to and from the requiring office using the most up-to-date version of the above software applications. The

Contractor shall maintain anti-virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with the

RMAC Program Office.

3.2 Work Location and Facilities

3.2.1 Work location: Approximately 60 percent of work will be performed at Government sites or customer locations and 40 percent of work to be performed at Contractor site. The majority of the customer locations are remote, OCONUS locations. Government sites include RMAC

Program Office and equipment preparation locations at Patuxent River Naval Air Station.

Customer sites are at various locations throughout the world. Contractors performing on-site support will be provided access to workspaces, telephones, and internet as required to respond to individual Task Orders. However, permanent seating on Government or Customer sites is not provided to Contractor employees under this contract.

3.2.2 The contractor shall have a facility within approximately twenty (20) miles of Patuxent

River Naval Air Station that allows for proper execution and required reviews under the terms of this contract and subsequent activities and audits on individual task orders. The cost of the contractor facility shall not be direct charged to the contract/task orders. The contractor’s facility is not necessary for the exclusive use of this contract and can be utilized on a shared basis. The

Government will not take possession of the facility after contract termination. The contractor’s facility shall:

a) be an environmentally controlled space.

b) include sufficient physical security to protect government assets.

c) include a conference room for a minimum of 15 people, containing sufficient equipment to conduct meetings with presentations and have video teleconferencing

(VTC) capability (not government furnished).

d) laboratory space with workbenches, and staging area for testing and shipment preparation of materials and equipment. The amount of space required will vary with each task order; however, approximately 2000 sqft. may be required to be available to support this contract. The space may be multi-use and/or used to support other efforts as long as it is available when needed in support of task order efforts.

e) establish and operate a Data Management Center (DMC) with government furnished computer equipment. The DMC should replicate a typical overseas operations center.

There is no requirement for the DMC to be as large as a normal operations center;

however, the room should comfortably accommodate two workstations with three monitors each, two large screen displays, communications equipment, and 2-5 additional personnel. The DMC must also contain an environmentally controlled space for a full size server rack. This rack may be located in the same room as the workstations or an adjacent server room.

3.3 Installation Closure: When Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at the facility performing non-mission essential work in support of such Federal employees shall follow their parent company’s policies.

3.3.1 While generally contractor personnel may not perform work on-site at a Government facility without supervision from Federal personnel, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential.

3.4 Contract Status Reporting: The Contractor shall be responsible for ensuring that all program management contract deliverables are tracked and submitted on time throughout the life of contract. At a minimum, the following are required documents:

3.4.1 Contractor Plan of Action Milestones (POA&M) (CDRL A001) – The (POA&M) as may be required by individual Task Orders, shall be delivered by the contractor. This document includes schedule, tasks, travel required and a concept of execution to ensure installation success as well as project success. The travel shall clearly identify trips required, the number of people on each trip, in-country coordination requirements, logistics, and transportation/security requirements. This document shall include a list of assumptions that could adversely affect a successful installation so that overall risk can be identified and addressed in a risk mitigation plan.

3.4.2 Work Breakdown Structure (WBS) (CDRL A002) – The contractor shall deliver a

WBS, as required by each Task Order that details the estimated costs of the effort required in each Task Order. These cost shall include labor, travel and material/other direct costs (ODC) required ensuring installation and project success.

3.4.3 Overtime Report (CDRL A003): This report documents overtime worked by contractor personnel, to include labor category, dates overtime occurred, work location, task order reference, description and date of the pre-approval documentation, and the amount of overtime for the associated invoice period. The report shall be updated throughout the period of each task order to capture the overtime required for the overall contract.

3.4.4 Monthly Financial Reports (CDRL A004), shall be developed and submitted to the

RMAC Program Office on a monthly bases, not later than the 10 th of each month, to include but not limited to:

a) Overall contract ceiling and funds expended;

b) Task order number, project title and period of reporting;

c) Ceiling, funds received, costs to date and the estimated costs to complete for each

Task Order;

d) Task order modifications, both awarded and required to include purpose of modification;

e) Total labor hours and cost expended, including fee (current and cumulative);

f) Detailed list and total material costs expended (current and cumulative);

g) Detailed list and total of travel expended (current and cumulative); and

h) Estimated total cost to complete; noting shortages or overages of the remaining ceiling and funding.

3.4.5 Monthly Operational Status Reports (CDRL A005): Monthly Contract and Task Order

Status Reports shall be developed and submitted to the RMAC Program Office on a monthly basis, not later than the 7 th of each month, unless otherwise specified in each task order. The

Contractor shall be responsible for collecting, integrating, and reporting all subcontractor reports.

The monthly operational status report shall include, at a minimum, the following items and data:

a) Period of reporting;

b) Details of open and completed task orders:

i. Task Order number, project title, and period of performance;

ii. Describe and identify modifications, both awarded and required;

iii. Details of work performed, including specified milestones and action items;

iv. Status of previously identified problems;

v. Identification of areas of concern, including technical issues, cost increases or schedule slippage;

vi. Status of deliverables; and

vii. Effort to be completed during next reported period.

3.4.6 Inventory List and Control Log (CDRL A006): The contractor shall maintain an

Inventory List and Control Log that tracks disposition of equipment and material through transfer to end user and/or disposal. The contractor shall make an inventory of all excess material and provide this inventory to the RMAC Program Office at the completion of site installation tasks. This material shall be identified as Ready for Issue (RFI), repairable, or disposable. Each month an updated document shall be delivered to account for all items purchased, including but not limited to the disposition (consumable, transferred or maintained in house), part number

(NSN nomenclature), quantity, cost, source of funding, and location of each item.

3.4.7 GFE Inventory (CDRL A007) - The Contractor shall maintain a continuous inventory of the equipment and non-consumable materials provided as Government Furnished Equipment

(GFE), which shall include location, responsible person (in possession of equipment) and operational status. The Contractor shall maintain a chronological log of all equipment received and generate an itemized Form DD1149 on all outgoing shipments. The current GFE Inventory will be provided at the time of Contract Award, during the Transition.

3.4.8 Task Order Close Out Reports (CDRL A008): Every task order requires the Contractor to submit a closeout report, which shall be completed within three (3) months of the contractor’s fiscal year following the final period of performance of each Task Order. The report shall include, at a minimum, the following information:

a) Financial Data – Breakdown of all costs (labor, travel, material, fee) per invoice, all personnel that were utilized/charged on the job, specify all work yet to be charged, all remaining funds, and balances available, if any, for return (de-obligation), etc.

b) Deliverable Status – Percentage job complete, any outstanding issues, CDRL status, list of any items/services under workmanship/manufacturer warranty, etc.

c) Government Property – All contractor-acquired property and government-furnished property provided on task orders shall either be consumed or returned to the government.

d) Material Transfer Documentation – All required forms must be completed and finalized.

3.5 Overtime:

Overtime as defined in this contract refers to hours in excess of a forty (40) hour work week.

Support requirements outside of normal working hours may occur, and the contractor shall ensure that qualified personnel are available to support these requirements through the use of overtime. Overtime cannot be charged directly to the contract unless a one-time initial approval is received from the Chief of the Contracting Office. Once the use of Overtime is approved by the Chief of the Contracting Office, the Government COR/TPOC shall be involved with the execution of Overtime under the contract. The contractor shall notify the COR/TPOC prior to working Overtime on any Task Order issued under the contract and Overtime will not be authorized until concurrence is received from the COR/TPOC. The COR/TPOC may provide concurrence for Overtime on a task, event, program, project, or general function basis. The use of OT shall be documented using the Overtime Report (CDRL A002).

3.6 Travel/Temporary Duty (TDY): When personnel are temporarily deployed offsite, both

CONUS and OCONUS, the contractor shall modify the traveler’s working hours to best support the assigned tasking and minimize overall cost.

3.7 Travel: The Contractor may be required to travel both CONUS and OCONUS in performance of an individual task order. Costs associated with travel and lodging shall be reimbursed in accordance with the Joint Travel Regulation (JTR) and with NAVAIR clause

5252.232-9509 Travel Approval and Reimbursement Procedures.

The COR/TPOC shall approve all travel performed in support of this contract prior to the commencement of the travel. COR/TPOC approval for local travel expenses is required.

The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements and shall be coordinated with the RMAC Program Office for each individual task order.

This contract requires the contractor to conduct site surveys, installations, maintenance, and training anywhere in the world. Most installations are conducted in very remote locations, harsh environments, and under extreme conditions. In some cases basic living conditions are not met and normally expected services such as lodging and electricity may not be available. In those cases, sometimes even food and water is not locally available and must be planned for and brought in with the installation team.

Remote installations are also conducted in locations where it is possible to contract various diseases not normally experienced in the United States. The contractor is required to follow the guidance provided by the Combatant Command (COCOM) for each corresponding Area of

Responsibility (AOR) and ensure that contractor personnel are medically qualified and prepared for travel to include chemical prophylaxis, such as anti-malaria medication and vaccinations such as Yellow Fever, Hepatitis A/B, Measles, Mumps, and Rubella (MMR), etc.

The remote installation locations are inherently less secure. The contractor will be responsible for adhering to any/all Force Protection (FP) guidance as established by the Chief-of-Mission through the Regional Security Officer (RSO), the COCOM, and/or the Government representative on-site. The Government representative on-site will establish a FP plan prior to each installation effort.

The contractor is responsible for obtaining passports and visas for its personnel and shall submit electronic clearances through Aircraft and Personnel Automated Clearance System (APACS) and/or eCountry Clearance (eCC), as required by Foreign Clearance Guide (FCG).

The contractor shall submit a written request to the COR/TPOC for approval, no less than 30

(thirty) days prior to incurring any travel expenses, or as specified in the Task Order. Contractor personnel shall document all travel expenses on a travel expense report or voucher and provide copies, to include receipts, to the COR/TPOC within 7 (seven) days after return from travel, or as specified in the Task Order.

The contractor shall comply with all rules associated with travel as required by the Joint Travel

Regulations and the Foreign Clearance Guide.

3.8 Material / ODCs: Prior written approval of the COR/TPOC shall be required for all purchases of all materials / ODCs. Under individual Task Orders, the contractor may be required to provide a material list to be approved by the COR/TPOC. Acceptance of this deliverable shall constitute written approval of those purchases. Any material provided by the contractor is subject to the requirements of the Federal Acquisition Regulation (FAR), the Defense Federal

Acquisition Regulation Supplement (DFARS), and applicable Department of the Navy regulations and instructions. All materials / ODCs not consumed or transferred during the performance of this contract shall become Government property upon completion of this contract. This material / ODCs shall be transferred to the COR/TPOC by way of Material

Inspection and Receiving Report (DD Form 250).

In-country / local labor or services hired in support of installation tasks shall also be approved by the Government in advance and billed as a Material / ODC expenses under this contract.

The costs of general purpose business expenses required for the conduct of the contractor’s normal business operations are not an allowable direct cost in the performance of this contract.

General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies.

3.9 Subcontractor Management. The prime contractor may disseminate portions of individual task orders to subcontractors based upon areas of expertise. The contractor may subcontract with other companies to establish a strong technical capability to meet diverse task order requirements. The prime contractor shall be held fully responsible for all aspects of task order performance and oversight, regardless of any arrangement between the prime and its proposed subcontractors. Subcontractors performing under this contract shall be approved by the

Contracting Officer. All provisions under this contract shall be clearly and effectively communicated flow down to all subcontractors providing support under this contract

3.10 Management of Contractor Personnel: The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. The contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services

3.11 Transition Strategy: The overall strategy shall be built around maintaining the mission of

RMAC Program Office with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs.

3.12 Security Requirements: The majority of the effort on this contract is unclassified.

However, most labor categories will have an occasional need for clearance at the Secret level as noted in paragraph 5.5 Labor Qualifications. On rare occasions, there are some efforts on this contract that may require the contractor Program Manager and/or the Senior Systems Engineer to participate in Top Secret level meetings/briefings that affect the execution of work under this contract so a Top Secret security clearance is required for those positions. The purpose of these briefings is to inform the contractor of details associated with system development and/or operational effort. Under this contract, the contractor will not be required to develop, transport, or store classified documents. Any classified material that will be handled by the contractor will provided and stored at government locations, in accordance with appropriate security standards and regulations.

3.12.1 Citizenship Requirements: Only U.S. citizens may perform under this contract. If the

Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

a. The individual's name, date and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific government contract (specify contract number).

e. A statement that the Contractor has obtained an export license for the information required to perform the contract.

3.12.2 Investigative Requirements

3.12.2.1 Unclassified: All Contractor personnel must be eligible to perform Non-Critical

Sensitive work as defined by SECNAV M-5510.30. All Contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the Office of Personnel Management.

The Contractor shall submit a request for personnel security investigation to the Government

Security Office. The Government Security Office shall initiate the Contractor’s Electronic

Questionnaire for Investigations Processing (eQIP)), shall do a preliminary screening of the

Contractor’s eQIP for suitability and derogatory information. The Contractor employee shall provide all requested information pursuant to the Privacy Act of 1974. The Government

Security Office may deny the Contractor access to Government facilities and information and may prohibit the Contractor from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor’s eQIP, In such cases, the Contractor employee may not perform on the Contract.

3.12.2.2 Classified: Applicable contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the

Contract’s DD-254, Contract Security Specification. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

3.12.3 Base Access: The contractor shall submit an unclassified visit request for government approval to obtain base passes and registration for contractor personnel. The first submission of the unclassified visit request should occur after award but prior to start of contract with additional requests being submitted as new personnel are acquired.

Contractor CACs and facility specific identification badges will be issued by the Government to contractors requiring on-site access and shall be visible at all times while personnel are at the

Government site. The contractor shall furnish all requested information required to facilitate issuance of identification badges. All CACs and identification badges issued to Contractor employees shall be returned to the Trusted Agent at the Government following completion of the contract, relocation or termination of an employee, or upon request from the Contracting

Officer’s Representative. The Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract.

3.12.4 DD-254: The contractor shall comply with security requirements specified in the DD-254 included as Attachment 1 to this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as

“For Official Use Only”.

3.12.5 Information Security: If the work is performed at the Contractor’s facility, the

Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM), and

SECNAV M-5510.36.

3.12.6 Marking: All information generated by the Contractor shall be properly marked. For

Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate

Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance

3.12.7 Public Release: No information pertaining to this contract or any effort under the individual task orders shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by the

COR/TPOC and/or appropriate U.S. government authority. Proposed public releases shall be submitted for approval prior to release through the Public Affairs Office, Patuxent River Naval

Air Station.

3.12.8 Loss, Compromise and/or Electronic Spillage of Classified or Controlled

Unclassified Information: All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR/TPOC and

Government Security Office within 24 hours of the incident occurring.

3.12.9 Operations Security (OPSEC): The contractor shall comply with activity OPSEC program instructions, guidance and contribute to organization-level OPSEC efforts. The contractor will include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The contractor will protect identified critical information, sensitive unclassified information and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed.

While performing aboard NAVAIR or NAVAIR sites, the contractor shall comply with facility

OPSEC program instructions and contribute to organization-level OPSEC efforts. Include

OPSEC as part of its ongoing security awareness program and take all required Agency training.

Be responsive to the Supporting OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed.

3.12.10 Emergency Management: The work performed on this contract is not Emergency

Essential in accordance with OPNAVINST 3440.17A and Government Emergency

Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of

Operations Plans and directives

3.13 Quality Control: The Contractor shall maintain an effective quality control program to ensure services are performed in accordance with the PBSOW and the Quality Assurance

Surveillance Plan (QASP). The Contractor shall implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Government shall evaluate the Contractor’s performance under this contract in accordance with the QASP, Section J Attachment 2.

4. Detailed Support Requirements

4.1 Program Management Services (Labor: CLINS 0001 through 0012)

The contractor shall work directly with the Government Program Manager (PM), and when applicable and approved by RMAC Program Office, provide support at the sponsor level.

Regardless of the level of support, the contractor shall ensure that the government’s requirements are met on schedule and within budget. As directed in task orders, the contractor shall coordinate meetings, prepare budgets, develop agenda items, attend high-level meetings, generate minutes, and track action items. Program management support may require significant coordination and interface between the contractor and various DoD and non-DoD activities located both CONUS and OCONUS.

4.2 Engineering Services (Labor: CLINS 0001through 0012)

The contractor shall perform engineering services as required by task orders. The contractor shall support the engineering effort required to prepare technical data documentation. The contractor shall ensure that all technical data documentation that is necessary to support system development reflects the latest design, configuration, integration, and installation concepts.

Engineering support will normally require general engineering support, systems engineering (to include prototype design and development), and software engineering. As part of this task, the contractor may be responsible for any or all of the following:

4.2.1 General Engineering (Labor: CLINS 0001through 0012)

The contractor may be required to perform general engineering services under specific tasks orders. Examples of general engineering tasks that may be required are:

a. Obtain and provide detailed reliability/maintainability predictions and historical performance and failure data for components, equipment, systems and subsystems.

b. Conduct builds and tests for integrated systems. This shall include, but is not limited to, installation tests and systems tests for system validation for all system performance requirements. This work may be conducted at Government facilities, contractor facilities, or a project site.

c. Review technical reports/studies as required to fulfill specific requirements.

d. Conduct assessments to quantify and assess vulnerability of electronic sensors or equipment to natural and manmade (artificial) sources that would affect system performance.

e. Develop probability of detection models at the device, subsystem, and site levels.

4.2.2 System Engineering (Labor: CLINS 0001through 0012)

The contractor may be required to perform system engineering services under specific tasks orders. Examples of systems engineering tasks that may be required are:

4.2.2.1 Design and Development (Labor: CLINS 0001through 0012)

System Design and Engineering Development shall apply when the task requires new parts design, software development or modification, or added functionality for a system and/or subsystem. The contractor shall use a systems engineering approach in the accomplishment of design, engineering, development, and manufacturing efforts, which in turn shall ensure that mission objectives and system requirements relating to individual task orders are met. Important factors shall include the demonstration of clear and definable improvements in the performance, accuracy, reliability, maintainability, supportability, deployability, survivability, cost effectiveness and/or service life of the hardware and/or software item, subsystem, system, or process. New parts, software, or systems shall be designed and produced to integrate with existing system components and software if applicable. System Design, Engineering, and

Development activities shall take into account maintenance, repair, and operational support requirements, including corrosion prevention, electromagnetic compatibility, Radio Frequency

(RF) compatibility, human factors engineering, and software systems remote log-in. New designs resulting in system enhancement are strictly prohibited from removing ANY existing capability without expressed documented consent from the RMAC Program Office.

All designs shall use Commercial Off the Shelf (COTS), standard parts and materials whenever practical. The requirements for installation, operation, maintenance, removal, and repair shall be satisfied by the use of tools and resources commonly available in the region of system installation. Any deviations from this requirement must have advanced written approval from the RMAC Program Office.

System designs shall consider the latest technology available. To the greatest extent possible, the government will provide known information on applicable technologies available in government laboratories; this technology and technology available in industry shall be considered in system design/redesign. COTS equipment and software meeting the requirements of individual task orders should be used whenever possible, when suitable Government owned solutions are not available.

4.2.2.2 System Integration (Labor: CLINS 0001through 0012)

The contractor shall integrate new sensors and capabilities, as directed by individual task orders.

This integration shall enhance the RMAC system capabilities, based on customer requirements and operational needs.

4.2.2.3 Prototype (Labor: CLINS 0001through 0012)

When required by an individual task order, the contractor shall build prototype and/or preproduction units, conduct tests and evaluate the item(s) against specified requirements, and deliver an industry standard technical documentation package. The contractor may also be required to perform first article testing. These efforts may involve a multitude of system platforms, including manned/unmanned aerial, surface, and subsurface platforms.

Documentation shall be revised to include information derived from the development, test and evaluation of these items or products. When deemed appropriate by the RMAC Program Office, the contractor shall also provide for rapid delivery of limited production quantities as specifically described by a task order. The customer requirements supported by this task order may require limited operational implementation of RMAC related prototype efforts in a “rapid response” environment.

4.2.2.4 Software Engineering (Labor: CLINS 0001through 0012)

Software engineering includes the design, development, testing and documentation of software to support a specific government requirement. The contractor shall utilize certified software and computer personnel. The contractor shall define a software development approach appropriate for the computer software effort to be performed under each task. The contractor shall document the software development approach in a Software Development Plan (SDP). The contractor shall follow this SDP for all computer software to be developed and maintained under this effort.

All software developed under this contract, to include new work and revisions of existing software, will be owned by the Government and the source code will be delivered to the RMAC

Program Office at the completion of each software development task.

All software modifications and enhancements shall meet government requirements for that particular task without adversely affecting ANY existing capability unless the contractor has received prior express, written consent from the RMAC Program Office.

Additional software engineering tasks may include, but are not limited to:

a. Develop and design software architecture and systems;

b. Test software systems;

c. Maintain design and code base;

d. Develop and update user manuals and support documents;

e. Conduct software de-bugging;

f. Conduct remote software support for current installations and new efforts;

g. Analyze software effectiveness/impact in new systems design and integration;

h. Develop software solutions for system enhancement and capability improvement; and

i. Software documentation.

4.3 System Installation (Labor: CLINS 0001through 0012)

The contractor shall install, or assist the Government in installing, component or system hardware and software as specified by individual task orders. When system installation is required, the contractor shall assist the government in identifying all equipment and utilities required for installation at the installation site. Examples of system installations tasks that may be required by task order are:

4.3.1 Site Preparation/Infrastructure Modification (Labor: CLINS 0001through 0012;

Material: CLINS 0013 through 0018)

The contractor shall conduct site surveys and perform site analysis to ensure that all infrastructure is suitable for the planned equipment/system installation. The assessment should ensure that long term viability is considered and that all factors that could contribute to a failed installation or early degradation of the system are identified. The contractor shall conduct minor alterations and/or incidental improvements that are non-construction in nature to facilities, existing equipment, and platforms to ensure the greatest probability of long term success.

Infrastructure deficiencies that are identified during the site survey, but are outside the scope of this contract, will be identified to the Contracting Officer’s Representative (COR) for repair or replacement through another method or source. In support of equipment/system installations, the contractor shall consider infrastructure to include, but not limited to:

a. Stable power;

b. Sufficient internet;

c. Suitable sensor platform/tower;

d. Environmentally suitable enclosure for powered computer systems – moisture/humidity, anti-corrosive, temperature, etc.;

e. Suitable facility to contain system equipment;

f. Proper grounding of facility, sensor platform, etc.;

g. Infrastructure/platform distances – cable runs and communication connections;

h. Obstructions – for sensors, installation efforts, communications, etc.; and

i. Existing sensor/system interference

4.3.2 Develop Installation Design Plans and Other Installation Documentation (Labor:

CLINS 0001through 0012)

The contractor shall develop and provide Installation Design Plans that include all necessary documentation to fully support a system installation. The purpose of this documentation is to ensure an efficient and successful installation effort and to facilitate long term sustainment of the system. The Installation Design Plan shall be updated and included in the Task Order Close Out

Report (CDRL A005)

Examples of system installation documentation may include, but not be limited to:

a. Master List of Equipment and Materials. The Master List of Equipment/Materials shall contain a list of all equipment to be utilized, a list of all installation material to be used, and all associated hardware. This sheet should detail which equipment and material is

Government Furnished Equipment/Material (GFE/M), Contractor Furnished

Equipment/Material (CFE/M), and spares.

b. Equipment Location Drawing. The equipment location drawing(s) shall depict the location of all equipment and the quantity of equipment at the location.

c. Block Diagram. Block diagrams shall depict, by means of single lines and graphic symbols, the course of an electrical or communication circuit, or system of circuits and the major component devices or parts used therein. The block diagram shall also act as a cabling diagram of the system. Cables between blocks shall be identified by a cable designation number and a jack, plug, or terminal block designator.