SATCOM_PWS_N0042118R0053.docx
DOCX document 160 KB Posted
- Attached to
- Global Radio Frequency and Intelligence Networks (GRFIN) (formerly Satellite Communications (SATCOM)) Federal contract opportunity
- Solicitation number
- N00421-18-R-0053
About this file
This sources sought notice is seeking capabilities statements from interested businesses to support the Naval Air Warfare Center Aircraft Division (NAWCAD) Special Communications Mission Solutions (SCMS) Division. The anticipated requirement is for system engineering services to perform tasks in support of assigned Satellite Communication, Radio Frequency, Video, and Networking Technology projects including requirements definition, solution definition, integration, installation verification/validation, and operation and sustainment. The estimated period of performance consists of one five-year ordering period starting in April 2019. Services may be performed at contractor and government sites, including potential travel to locations within and outside the continental United States. Interested businesses must submit capabilities statements by April 23, 2018 demonstrating their ability to meet the requirements in the attached draft performance work statement, including the NAWCAD standard labor category qualifications and the ability to obtain the required facility and personnel security clearances. The government will evaluate the responses to determine if the interest warrants an unrestricted competition or a small business set-aside.
DRAFT PWS FOR SOURCES SOUGHT
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| GRFIN SOW 1-28-20.docx | DOCX document | |
| NAVAIR-Industry_Communication_Plan.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Draft SATCOM Performance Work Statement
1.0 SCOPE. The contractor shall provide system engineering services to perform tasks in support of assigned Satellite Communication (SATCOM), Radio Frequency (RF), Video, and Networking Technology projects including: requirements definition; solution definition; integration, installation verification/validation; operation and sustainment. Assigned efforts will involve the integration/installation of new SATCOM RF, Video, and Networking systems/equipment; the upgrade/modernization of existing systems/equipment; and the use of legacy, current, and emerging SATCOM, RF, video, and networking technologies to meet unique requirements. These systems are primarily made up of Commercial-off-the-Shelf (COTS) equipment. Tasking will span the entire systems engineering life-cycle or some portion thereof. Tailoring of the systems engineering process will be required to meet rapid project life cycles. SATCOM RF, video, and networking systems supported by this contract will range from stand-alone systems up to global, integrated communication solutions that combine satellite and terrestrial networks supporting converged voice, video and data, and will take various forms including dismounted portable, mobile, and fixed-site applications. While contract performance will take place primarily within Continental United States (CONUS) locations, completion of some projects will require travel to Outside of the Continental United States (OCONUS) locations.
1.1 Background: The Naval Air Warfare Center Aircraft Division (NAWCAD) Special Communications Mission Solutions (SCMS) Division (AD-4.11.4), located at Webster Field Annex, St. Inigoes, MD, integrates and delivers products for Command, Control, Communications, Computers, Combat, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems. These critical C5ISR solutions are funded by a broad range DoD and non-DoD customers, including joint forces commands, warfighters and disaster recovery/first responders. The SCMS Division is the organic Lead System Integrator (oLSI) using a rapid engineering process to provide solutions with a blend of COTS, government off the shelf, and fully customized products. The SCMS Division will be integrally involved in the design, production and support of these SATCOM, RF and Network Technology products.
| 1.2 | Technologies: Although not inclusive, communications-electronics areas of particular interested to the SCMS Division are: |
| a. | |
| Military Satellite Communications: Ultra High Frequency (UHF), Super High Frequency (SHF), Extremely high frequency (EHF), Global Positioning System (GPS), Global Broadcast Service (GBS), and Quad-Band Systems |
| b. |
| Commercial Satellite Communications: iDirect, Very Small Aperture Terminal (VSAT), International Maritime Satellite (INMARSAT), Iridium, Ku, C, Ka and X Systems |
| c. |
| Digital Networking Technologies: Personal Area Network (PAN), Local Area Network (LAN), Wide Area Network (WAN) and Metropolitan Area Networks (MAN) of various topologies and being connected via copper, fiber optics or wireless connections. Networking protocols, Asynchronous Time-division Multiplexing (ATM), Frame Relay, Integrated Services Digital Network (ISDN), Digital Subscriber Line (DSL), Synchronous Optical Network (SONET), Transmission Control Protocol/Internet Protocol (TCP/IP), Multi-Protocol Label Switching (MPLS), Voice over Internet Protocol (VOIP), Quality of Service, and latency are all important areas of interest with these technologies |
| d. |
| Operations Disaster Recovery/Continuity of Operations/Data Replication/Storage Area Networks/ Network Attached Storage |
| e. |
| Encryption and Information Technology (IT) Security Technologies: Integration and installation of current Type 1 approved cryptographic devices into electronic systems and the design and configuration of multilevel/multi-domain security systems |
| f. |
| Multimedia Systems: fixed, mobile, and portable equipment and control systems (AMX, Crestron, and InfoComm) |
| g. |
| HF Radio Communications/Technologies: Automatic Link Establishment (ALE), Near Vertical Incidence Skywave (NVIS), Internet Protocol (IP) over HF and MANET |
| h. |
| Short Haul Tactical Communications: UHF/Very High Frequency (VHF) Line of Site (LOS), HAVEQUICK, Single Channel Ground and Airborne Radio System (SINCGARS), and Microwave |
| i. |
| Broadcast Engineering: Analog and Standard Definition (SD)/high definition (HD) digital, including radio, television, and audio/video equipment |
| j. |
| Electrical Power Generation/Distribution technology: fixed, mobile, and portable integration platforms |
2.0 APPLICABLE DOCUMENTS: The following documents and document sources are provided for reference. Requirements for SCMS Division products to have interoperability among military, civilian, United States (U.S), and foreign users may dictate an adherence to a wide variety of specifications and standards. DoD systems shall adhere to Joint Technical Architecture (JTA) Standards (Current Version). Non-DoD systems may be governed by numerous commercial, national or international standards. The standards, specifications, and instructions development organizations listed are not all-inclusive and are presented only as representative sources of the technological interface details which may be required by systems developed with this contract. Likewise, the documentation listed is not all-inclusive, but representative of the types of information that may be required for efforts on this contract. 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 a Task Order (TO) is awarded.
| 2.1 |
| Department of Defense (DoD) Manuals |
| 2.1.1 |
| DoD 5220.22-M |
| National Industrial Security Program Operating Manual (NISPOM), 29 February 2006 |
| 2.1.2 |
| DoDM 5200.01 |
| DoD Information Security Program: Controlled Unclassified Information (CUI), Volume 4, Enclosure 3 (pages 11-18), 24 February 2012 |
| 2.1.3 |
| SECNAV M-5510.36 |
| Information Security Program, 30 June 2006 |
| 2.1.4 |
| SECNAV M-5510.30 |
| Personnel Security Program, June 2006 |
| 2.2 |
| DoD Standards |
| 2.2.1 |
| MIL-STD-1791 |
| Designing for Internal Aerial Delivery in Fixed Wing Aircraft |
| 2.2.2 |
| MIL-STD-188-125-2 |
| High Altitude Electromagnetic Pulse (HEMP) Protection for Ground-based C4I Facilities Performing Critical, Time-urgent Missions – Part 2 – Transportable Systems |
| 2.2.3 |
| MIL-STD-209K |
| Interface Standard for Lifting and Tie Down Provisions |
| 2.2.4 |
| MIL-STD-461F |
| Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment |
| 2.2.5 |
| MIL-STD-464C |
| Electromagnetic Environmental Effects Requirements for Systems |
| 2.2.6 |
| MIL-STD-882E |
| System Safety |
| 2.3 |
| DoD Handbooks |
| 2.3.1 |
| MIL-HDBK-1785 |
| Systems Security Engineering |
| 2.3.2 |
| MIL-HDBK-237D |
| Electromagnetic Environmental Effects and Spectrum |
| 2.3.3 |
| MIL-HDBK-237D |
| Supportability Guidance for the Acquisition Process |
| 2.3.4 |
| MIL-HDBK-502 |
| DoD Handbook Product Support Analysis |
| 2.4 |
| DoD Instructions |
| 2.4.1 |
| DoDD 8140.01 |
| Cyberspace Workforce Management |
| 2.4.2 |
| DoDI 8500.01 |
| Cybersecurity |
| 2.4.3 |
| DoDI 8510.01 |
| Risk Management Framework (RMF) for DoD Information Technology (IT) |
| 2.4.4 |
| NASPAXRIVERINST 5100.35D |
| Occupational Safety and Health (OSH) Manual |
| 2.4.5 |
| NAWCADINST 3432.1B |
| NAWCAD Operations Security Plan |
| 2.4.6 |
| OPNAVINST 3432.1 |
| Operation Security |
| 2.4.7 |
| OPNAVINST 3440.17A |
| Navy Installation Emergency Management Program, 1 August 2014 |
| 2.4.8 |
| SECNAVINST 5000.2E |
| Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System |
| 2.5 |
| Other Government Documents |
| 2.5.1 |
| 5000 Series |
| Department of Defense Instructions |
| 2.5.2 |
| CNSSP No. 7 |
| Policy on the Use of Commercial Solutions to Protect National Security Systems |
| 2.5.3 |
| Intelligence Community Standard Number 705-1 |
| Physical and Technical Security Standards for Sensitive Compartmented Information Facilities, Effective 17 September 2010 |
| 2.5.4 |
| NACSIM/NACSEM |
| National Communications Security Information Memoranda and Emanations Memoranda |
| 2.5.5 |
| NAVSEA S9095-AD-TRQ-010/TSTP |
| Total Ship Test Program Manual |
| 2.5.6 |
| N/A |
| SCMS Drawing Standard Operating Procedure |
| 2.5.7 |
| N/A |
| SCMS Program Management Plan |
| 2.5.8 |
| N/A |
| SCMS Systems Engineering Management Plan |
| 2.5.9 |
| N/A |
| Criteria for Commercial Solutions for Classified (CSfC) Solution Integrators, V2.1 13 August 2014 |
| 2.5.10 |
| DoD Directive 5230.24 |
| Distribution Statements on Technical Documents, Change 1, Effective 28 April 2016 |
| 2.5.11 |
| DoD 5400.7-R |
| Freedom of Information Program Regulation, Chapter 3 (pages 31-42), September 1998 |
| 2.6 |
| Industry Documents |
| 2.6.1 |
| GEIA-STD-0007 |
| Tech America Logistics Product Data Standard |
| 2.6.2 |
| N/A |
| Federal Motor Vehicle and Carrier Safety Standards and Regulations |
| 2.6.3 |
| N/A |
| Federal, e.g. FED-STD, FIP Series |
| 2.6.4 |
| N/A |
| High Density Television – Standards |
| 2.6.5 |
| N/A |
| Society of Automotive Engineers (SAE) Handbook |
| 2.6.6 |
| NSTISSI |
| National Security Telecommunications Information Systems Security Issuances |
| 2.7 |
| Developmental Organizations: |
| 2.7.1 |
| American National Standards Institute (ANSI) |
| 2.7.2 |
| American Society of Mechanical Engineering (ASME) Standards |
| 2.7.3 |
| Association of Public-Safety Communications Officials – International (APCO) – Standards |
| 2.7.4 |
| BiCSi A Telecommunications Association |
| 2.7.5 |
| Committee on National Security Systems |
| 2.7.6 |
| Defense Threat Reduction Agency (DTRA) |
| 2.7.7 |
| Department of Defense |
| 2.7.8 |
| Electronic Industries Association (EIA), e.g. Recommended Standards RS Series |
| 2.7.9 |
| European Telecommunications Standards Institute (ETSI) |
| 2.7.10 |
| Federal Communications Commission |
| 2.7.11 |
| Federal Motor Vehicle and Carrier Safety Standard and Regulations |
| 2.7.12 |
| Global Information Grid (GIG) |
| 2.7.13 |
| International Standards Organization (ISO) |
| 2.7.14 |
| International Telecommunications Union (ITU), formerly the CCITT |
| 2.7.15 |
| International Telecommunications Satellite Organization (INTELSAT) |
| 2.7.16 |
| Internet Engineering Task Force (IETF) |
| 2.7.17 |
| Institute of Electrical and Electronic Engineers (IEEE) |
| 2.7.18 |
| Joint Technical Architecture (JTA) |
| 2.7.29 |
| National Bureau of Standards |
| 2.7.20 |
| National Institute of Standards and Technology |
| 2.7.21 |
| National Security Telecommunication and Information System Security (NSTISS) |
| 2.7.22 |
| National Television Standards Committee (NTSC) |
| 2.7.23 |
| Society of Automotive Engineers (SAE) |
| 2.7.24 |
| Telecommunications Industry Association (TIA) |
| 2.7.25 |
| Worldwide Aeronautical Radio Commission (WARC) – Standards |
3.0 REQUIREMENTS
3.1 General Requirements.
3.1.1 Compatibility. The contractor shall maintain the capability to prepare documents and software packages compatible with the Government IT environment through the security classification of unclassified information systems. The current operating environment required for this contract is identified in the SCMS Division AD-4.11.4 Research, Development, Test and Evaluation (RDT&E) Network Standard Operating Procedures (SOP) for both contractor site and government site staff (Attachment X).
The contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall maintain state-of the-art virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with the SCMS Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with SCMS Division during working hours whether at Contractor work site or on travel.
Access to NMCI is not anticipated for this contract. If determined to be necessary, the government will provide all NMCI services; to include IT related hardware, software, and support necessary for the performance of this contract. Coordination of these services is to be conducted through the Contracting Officer’s Representative (COR)/Alternate Contracting Officer’s Representative (ACOR).
3.1.2 Work Location and Facilities.
3.1.2.1 Work location. Approximately 7 percent of work will be performed at Government site and 93 percent of work to be performed at Contractor site. Government site(s) include Building 8185, St. Inigoes.
3.1.2.1.1 Government Site Requirements. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks. The SCMS Division may provide limited shared laboratory and integration space for the contractor for on-site work requirements located at NAWCAD, Patuxent River, St. Inigoes, MD. If the contractor chooses to alter the work area in any manner, they shall have prior approval from the COR/ACOR and shall be responsible for the cost of any modifications approved. The cost shall not be a direct charge to the Government. On a limited case by case basis, special purpose equipment may be provided for use in the test and evaluation of Government furnished property as directed by SCMS Division.
All contractor-owned desktop computers provided for Government facility access will be submitted for re-imaging and validation scanning prior to allowing network connection. Approval is required by COR/ACOR and SCMS Network Information Site Security Officer prior to connection. All connected desktops will be subject to continuous monitoring.
3.1.2.1.2 Contractor Site Requirements. The contractor shall provide its own support facilities within 50 ground transportable miles of NAWCAD, St. Inigoes, MD to perform the requirements of this contract. The contractor shall obtain facility clearance at TOP SECRET per the contract DD254 within 90 days after contract award. The contractor shall provide all equipment and office/facility furnishings to support the PWS/SOW requirements for contractor-site requirements. The government does not intend to assume responsibility to retain the facility or take control of the title after the contract is completed. It is anticipated that the cost of the facilities will be proposed as an indirect charge to the Government, and the facility may not be located on Government property.
The contractor’s facility shall contain assembly, test, and storage space, as well as attendant office space for the support staff considering integration materials will be provided by the Government to the contractor.
The contractor may propose an alternate location for integration efforts only, if there is a cost savings to the Government.
3.1.2.1.3 Industrial Support Facilities. The contractor shall provide sufficient industrial space on an indirect cost basis, for the storage, integration, and testing of electronic equipment and systems associated with assigned projects. The Government estimates approximately 6,000 square foot is required at contract award and that up to 15,000 square feet will be required during contract execution. The space shall be configured to meet requirements for receiving, material receipt inspection, equipment testing, storage awaiting buildup, a buildup area (including foundation, cabinet, and cable buildup), storage awaiting integration and testing, and storage of completed systems. The space shall be capable of sustaining a controlled environment consistent with the storage, assembly, and operation of electronic equipment. The contractor shall have an approved Property Management System and adequately protect Government property. The Contractor shall furnish and equip the facility to meet requirements. The Contractor's facility shall be within 50 ground transportable miles of Government Program Office location at NAWCAD 4.11.4, NAS Patuxent River, Webster Field Annex, St Inigoes, MD. Cost of the facility shall not be a direct cost to the Government. The Government will not take possession of the facility at contract termination.
3.1.2.2 Government and Contractor Furnished Vehicles. Transportation vehicles may be provided by the Government and Contractor to support and meet delivery and pick up of Government provided equipment and integration materials when scheduled. The contractor shall request an authorization from the Contracting Officer prior to ordering a vehicle from the Interagency Fleet Management System (IFMS). The transportation vehicles shall not be used to transport Government personnel.
3.1.2.2.1 When operating Government vehicles, the contractor shall ensure the following:
(a) Possession of a current and valid operator’s license for all vehicles;
(b) Compliance with all state and federal laws pertaining to operating motor vehicles;
| (c) | Compliance with NAWCAD command policies when operating a vehicle (i.e., no cell |
| phone use, stopping at runway crossing, etc.); | |
| (d) | Use the most cost-effective means to fuel vehicles (i.e., NAWCAD fuel farms); |
| (e) | Operation of the vehicles in a safe manner and in accordance with the vehicle/equipment user/operator manual. |
| (f) | Operators shall comply with licensing requirements of country, state, and local Non Tactical Vehicle (NTV) laws. |
| (g) | The COR/ACOR and Contracting Officer are to be provided evidence of NTV liability insurance covering bodily injury and property damage protecting the Contractor and DoD against third-party claims arising from the ownership, maintenance or use of a NTV In Accordance With (IAW) Federal Acquisition Regulation (FAR) 28.307-2(c). |
3.1.2.2.2 The contractor shall report any known or realized accidents involving the Government owned or leased vehicles to the Government Technical Point of Contact TPOC. If the contractor is involved in an accident while operating a Government owned or leased vehicle, they shall notify the Government TPOC, the Contracting Officer, and the COR/ACOR within 24 hours and shall provide an accident report using Standard Form 91, Motor Vehicle Accident Report, and Form 94, Statement of Witness Report, within 48 hours.
3.1.2.2.3 When operating the vehicle, the contractor shall utilize the Government Smart Card for fueling, maintenance, and repair services. Contractor use of the Smart Card will be in accordance with the requirements and regulations contained in the GSA Fleet Services Card User Guide (www.gsa.gov/fleetcard). When operating the vehicle, the contractor shall be responsible for any costs associated with violations such as speeding tickets, parking tickets, reckless driving, and any damage caused to the vehicle as a result of vehicle code violations. The contractor shall be responsible for reimbursing the Government for any unauthorized charges made by the contractor, its employees, and subcontractors on the Smart Card.
3.1.3 Contract Status reporting. The contractor shall provide the following documentation.
3.1.3.1 Monthly Progress and Financial Status Reports. The contractor shall provide a progress and financial status reports IAW CDRLs A001 and A002. The reports shall include work accomplished since submittal of the last report, both monthly and cumulative man-hour labor costs expended by labor category, and material and travel costs.
3.1.3.2 Reserved.
3.1.3.3 Segregation of Cost and Invoice Requirements Report. The contractor shall provide supporting data with each invoice IAW CDRL A003.
3.1.3.4 Workforce Report. The contractor shall provide workforce data IAW CDRL A004.
3.1.3.5 Trip/Meeting Report. The contractor shall provide Trip/Meeting Reports IAW CDRL A005.
3.1.4 Work Schedule to include Compressed Work Schedule (CWS), Overtime, Holidays, and Installation Closure.
3.1.4.1 Work schedule: The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from 0X00 to 1X00 each Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday –Friday.
3.1.4.1.1 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 may allow its employees to work a CWS schedule provided the requirements of this PWS/SOW are met. If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, 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. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the Government. The overall schedule must be provided to the ACOR/COR.
3.1.4.1.2 Holidays: The Government observes the following holidays:
New Year’s Day, January 1 Martin Luther King’s Birthday, the third Monday in January President’s Birthday, the third Monday in February Memorial Day, the last Monday in May Independence Day, July 4 Labor Day, the first Monday in September Columbus Day, the second Monday in October Veteran’s Day, November 11 Thanksgiving Day, the fourth Thursday in November Christmas Day, December 25
With the exception of the events in section 3.1.4.1.3 below, the contractor is permitted to observe the above Holidays in accordance with its corporate policy.
3.1.4.1.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 that facility in support of such Federal employees shall follow their parent company’s policies While generally contractor personnel may not perform work on-site at a Government facility without oversight 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.1.4.1.4 Overtime. Overtime shall be in accordance with (IAW) Section I Clause 52.222-2.
3.1.4.1.5 Telework. The contractor, with COR/ACOR concurrence, may allow its employees to telework on a case by case basis depending on the nature of support provided by the contractor's employee. DoD Instruction 1035.01 of 4 April 2012 will be used as a guide for determining situations where teleworking is feasible. The Government reserves the right to prohibit telework where the Government determines it to not be in the Government's best interest.
3.1.5 Other Direct Costs (ODCs). ODCs ceiling amounts are based on a per annum not-to-exceed amount. Approvals shall be obtained per applicable contract clauses in Section H.
3.1.5.1 Travel. Travel will be allowable only when it is essential to the performance of the tasks detailed in Section 3.3. The COR/ACOR approval shall be obtained per the Travel Approval and Reimbursement Procedures clause (5252.232-9509). Reimbursement for travel performed shall be IAW the DoD Joint Travel Regulation (http://www.defensetravel.dod.mil/site/travelreg.cfm). The COR/ACOR shall approve all travel performed in support of this contract prior to the commencement of the travel and result in a trip report in accordance with CDRL A005. Travel may include general and administrative expenses, but shall not include profit. Temporary travel locations will be determined by the Government during performance of the awarded task orders. Temporary travel locations include all 50 states, the District of Columbia, United States Territories, South Korea, Japan, Germany, United Kingdom, Afghanistan, Qatar, and Turkey; this list is not all inclusive as locations may change over the life of the contract. The contractor is responsible for making all travel arrangements for its personnel.
3.1.5.1.1 Synchronized Pre-deployment and Operational Tracker (SPOT). The contractor may travel in United States Central Command (USCENTCOM) Area of Responsibility (AOR) locations. In accordance with Clauses 252.225-7040 and 5152.225-5908, SPOT enables the validation of Contractors Authorized to Accompany the Force (CAAF), their authorization and eligibility for access to specific DoD facilities, and their eligibility for specific Government-Furnished Support (GFS). The contractor shall initiate a Letter of Authorization (LOA) for each prospective traveler. The contractor shall use the SPOT link https://spot.altess.army.mil to enter and maintain data with respect to traveling/deployed personnel, and to generate LOA.
3.1.5.1.2 Letters of Authorization. The Contracting Officer will provide LOA for official travel OCONUS, when applicable, supporting the contract. LOA will identify local authorizations, privileges, etc. as specified by DoD requirements. All defense contractors working under this contract shall carry LOA, when applicable, with them at all times while deployed OCONUS.
3.1.5.1.3 Quarterly Contractor Census Reporting. The prime contractor shall provide census reporting IAW CDRL A006. The COR may require SPOT quarterly reporting for travel to additional in-garrison travel locations.
3.1.5.1.4 Local Travel Reimbursement. Reimbursement of contractor travel to and from NAWCAD 4.11.4, NAS Patuxent River, Webster Field Annex and the contractor’s facility and the surrounding area, by the contractor or subcontractor located within 50 miles of the base, shall not be authorized.
3.1.5.2 Material. Material will be allowable only when it is incidental and approved per the clause "Restriction on the Direct Charging of Material (NAVAIR 5252.242-9515 Variation) (May 2017)”. Any material provided by the Contractor is subject to the requirements of the FAR, the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable Department of the Navy regulations and instructions. If the contractor’s Task Order proposal includes a detailed list of materials with associated part numbers and prices, then the COR/ACOR and PCO’s acceptance of the contractor’s proposal shall constitute written approval of those purchases. All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The contractor shall transfer all materials not depleted to the COR/ACOR by way of Material Inspection and Receiving Report (DD Form 250). ODCs may include general and administrative expenses but shall not include profit.
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.1.6 Subcontractors. Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this PWS/SOW shall flow down to subcontractors providing support under this contract.
3.1.7 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.1.8 Transition Strategy. The overall strategy shall be built around maintaining the mission of the SCMS Division SATCOM projects with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the contract, the contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The contractor shall submit a Transition Out Plan IAW CDRL A007.
3.2 Security.
3.2.1 Citizenship Requirements: Only U.S. citizens may perform under this contract.
3.2.2 Investigative Requirements.
3.2.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.2.2.2 Classified. All 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 DoD Manual (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.2.2.3 Personnel Security. Personnel must have, or be able to obtain the appropriate security clearance as stated on the DD Form 254. One person proposed for each of the labor categories below shall obtain the clearance specified within the number of days specified. In addition to these categories, Secret clearances may be required for other labor categories depending on actual tasking throughout the duration of the contract per resultant task orders. Proof of U.S. citizenship is required to be permitted access to government installations, aircraft, and ships.
| Position/Labor Category |
| Level |
| Security Clearance Level |
| Within how many days of award |
| Manager/Operations Managers |
| Senior |
| Top Secret |
| 45 |
| Manager/Operations Managers |
| Journeyman |
| Top Secret |
| 45 |
| Electrical Engineers |
| Journeyman |
| Top Secret |
| 45 |
| Software Developers, Systems Software |
| Journeyman |
| Top Secret |
| 45 |
| Software Developers, Systems Software |
| Junior |
| Top Secret |
| 45 |
| Computer and Information Research Scientist |
| Journeyman |
| Top Secret |
| 45 |
| Information Security Analysts |
| Journeyman |
| Top Secret |
| 45 |
| Computer Systems Analysts |
| Journeyman |
| Top Secret |
| 45 |
*Interim clearances are acceptable.
Note: The contractor shall apply the above levels of security clearance requirements to their proposed workforce in support of the PWS/SOW as applicable.
3.2.3 System Authorization Access Request (SAAR-N), Common Access Card (CAC)/Public Key Infrastructure (PKI).
3.2.3.1 SAAR-N. All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form Chief of Naval Operations (OPNAV) 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR-N forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf. SAAR-N forms shall be submitted to the COR/ACOR, Government Technical Point of Contact (TPOC), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Agent.
3.2.3.2 Common Access Cards (CAC) / Local Badges. Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel 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 COR following completion of the contract, relocation or termination of an employee, or upon request from the COR/ACOR. The Government will provide the contractor access to Government facilities, as required, for performance of task orders under this contract.
3.2.3.3 Public Key Infrastructure (PKI). Employees requiring access to various DoD resources (i.e. RDT&E Network, DoD websites and networks) from a contractor facility are mandated by DoD policies to use Government-approved Public Key Infrastructure (PKI) along with an appropriate hard key (i.e. Smart Card). Defense Information Systems Agency (DISA) will be the primary source for these certificates.
3.2.3.4 DD Form 254. The contractor shall comply with security requirements specified in the DD-254 attached 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” (FOUO). Distribution is authorized to the Requiring Office’s Organization and supported Activities only. Other requests for deliverables under this contract shall be referred to the COR/ACOR of this contract for approval. The DD Form 254 requires a TOP SECRET facility with no level of safeguarding required within 90 days after contract award. During contract performance, the contractor will require access to the following, per the DD Form 254:
| a. |
| COMSEC Information |
| b. |
| Intelligence Information – Non-SCI |
| c. |
| North Atlantic Treaty Organization (NATO) Information |
| d. |
| FOUO Information |
| e. |
| SIPRNET, Secure Terminal Equipment, and secure facsimile and Focal point (FP) material |
| f. |
| Receive and generate classified material |
| g. |
| Fabricate, modify, or store classified hardware |
| h. |
| Access to U.S. Classified information outside the U.S., Puerto Rico, U.S. possessions and trust territories; |
| i. |
| Require a COMSEC Account |
| j. |
| Tempest Requirements |
| k. |
| Operations Security (OPSEC) Requirements |
| l. |
| Authorized to use the Defense Courier System. |
3.2.4 Information Security. 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 when work is performed at the contractor’s facility. If the work is performed at the Government’s facility, the Contractor shall comply with facility security procedures and controls.
3.2.4.1 Marking. All information generated by the contractor shall be properly marked. FOUO 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.2.4.2 Public Release. No information pertaining to this contract 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 appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through the office listed in Block 12 of the contract’s approved Contract Security Classification Specification, DD Form 254.
3.2.4.3 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/ACOR, TPOC and Government Security Office within 24 hours of the incident occurring.
3.2.5 Operations Security (OPSEC): The contractor shall prepare an OPSEC plan for Government review IAW CDRL A023.
3.2.5.1 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 NISPOM and DoDM 5200.01, Information Security Manual. The DoD Contract Security Classification Specification, DD Form 254, specified in Section J, defines program specific security requirements. All controlled unclassified information shall be appropriately identified and marked as FOUO IAW DoDM 5200.01, Information Security Program: 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 IAW OPSEC requirements. The contractor will include OPSEC as part of its ongoing security awareness program.
3.2.5.1.1 FOUO information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01 (DoD Information Security Program: CUI Vol. 4 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.
3.2.5.1.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.
3.2.5.1.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. This program may include IA and Communications Security (COMSEC). 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. |
3.2.5.2 While performing aboard NAVAIR or NAWCAD sites, the contractor shall: comply with facility OPSEC program instruction; contribute to organization-level OPSEC efforts; include OPSEC as part of its ongoing security awareness program; take all required Agency training, be responsive to the Supporting OPSEC Manager on a non-interference basis; and protect sensitive unclassified information and activities, which could compromise classified information or operations or degrade the planning and execution of operations performed by SCMS Division and the contractor in support of the mission.
3.2.6 Anti-Terrorism Force Protection and Emergency Management: The work performed on this contract is not Emergency Essential in according 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. Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials direct curtailment of operations to “Mission Essential Only”. All Contractor personnel assigned to a government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.
3.3 Detailed Support. The contractor shall provide systems engineering services to SCMS Division in the performance of studies and application of leading edge technologies for SATCOM RF, video, and networking projects in the developmental, production, or operational phases IAW the SCMS Systems Engineering Management Plan (current version). Specifically the contractor shall perform planning and execution efforts for Research and Development; Systems Design and Engineering Support; Installation, Integration and Test and Evaluation (T&E) Support; and, Operations, Maintenance and Training Support. Integration in the context of this requirement includes the rapid design incidental to the installation, customization of installation components, fabrication of components incidental to the installation, procurement of incidental materials, installation, verification, testing and certification, maintenance and logistics incidental to installation and grooms.
The contractor shall report results of surveys, analysis and associated technical data IAW Exhibit A. Performance of work shall be measured IAW the Quality Assurance Surveillance Plan (QASP) or Contract Surveillance Plan (CSP), as appropriate to the resulting task orders. Each individual task order will contain the appropriate version of the language based on whether or not the task order is performance based on non-performance based. No item in this PWS/SOW shall be interpreted to permit the contractor to perform any services that are inherently governmental services or personal services as defined in FAR 2.101; if any provision of the SOW conflicts with this term, this prohibition shall take precedence.
3.3.1 Research and Development
3.3.1(a) Research and Development efforts using Research, Development, Test and Evaluation (RDT&E) funds, perform planning and execution of development and design efforts for SATCOM, RF, Video, and Networking Technologies systems, and subsystems to include research, development, design and redesign, studies, analysis and prototyping of newly designed systems. Applicable to paragraphs 3.3.1.1, 3.3.1.2 and 3.3.1.3.
3.3.1(b) Research and Development efforts using Procurement funds, perform planning execution of efforts to support modernization and modifications of SATCOM, RF, Video, and Networking Technologies systems, and subsystems to include production engineering, fabrication and assembly. Applicable to paragraphs 3.3.1.1.2, 3.3.1.1.5, and 3.3.1.3.2.
3.3.1(c) Research and Development efforts using Working Capital Fund (WCF) funds, perform the planning and execution of development and design efforts and modernization and modification efforts for SATCOM, RF, Video, and Networking Technologies systems. Applicable to paragraphs 3.3.1.1, 3.3.1.2 and 3.3.1.3.
3.3.1(d) Research and Development efforts using Non-DoD funds, perform the planning and execution of development and design efforts and modernization and modification efforts for SATCOM, RF, Video, and Networking Technologies systems, and subsystems. Applicable to paragraphs 3.3.1.1, 3.3.1.2 and 3.3.1.3.
3.3.1(e) Research and Development efforts using Operations and Maintenance (O&M) funds, perform evaluation of operational and technical support of fielded/in-service and out-of-production SATCOM, RF, Video, and Networking Technologies systems, and subsystems. Applicable to paragraphs 3.3.1.1, 3.3.1.2 and 3.3.1.3.
3.3.1.1 Evaluation of Capabilities
3.3.1.1.1 The contractor shall provide special engineering and cybersecurity support to research new and emerging communications and network technologies, which have the potential to benefit state of the art communications and network capabilities or improve existing system performance.
3.3.1.1.2 The contractor shall identify, review and compare new and emerging technologies for application within associated communications and network systems; conduct market studies to assess the readiness of the technology, risk factors including but not limited to technical maturity or available products, financial stability of potential vendor, and effects of inserting emerging technology into a communications and network project; re-design system architectures to integrate new and emerging technologies; and design or redesign systems for covert operations, concealment, feature disguise, tamper-proof operation, fail-safe operation, intrusion detection/self-destruct features, and extreme environment operations.
3.3.1.1.3 The contractor shall identify opportunities for technology transition and exploitation to meet performance requirements and support the evaluation and implementation of applicable technologies including but not limited to maintaining knowledge of cybersecurity threats and gaps; maintaining knowledge of emerging commercial and DoD C5ISR technologies and programs; and evaluation of the applications and implementation of emerging technologies as they apply to SCMS project performance, threats, and gaps.
3.3.1.1.4 The contractor shall conduct a requirements analysis, derive system, subsystem and component requirements and specifications and document results, including but not limited to preparation of a requirements traceability matrix; develop concept, preliminary, and detailed designs of system based on approved requirements. Prepare and deliver Requirements Traceability Matrix IAW CDRL A009.
3.3.1.1.5 The contractor shall evaluate existing and new systems capabilities to meet design goals, planned and future mission requirements and standards in an operational environment and be interoperable with existing or new/future systems.
3.3.1.1.6 The contractor shall identify risk or low-performance areas, define alternate design methodologies, and recommend design modifications; define points of design inadequacy within the specified component or system for the desired application (e.g., response time, frequency coverage).
3.3.1.2 Evaluation of System Concepts
3.3.1.2.1 The contractor shall evaluate system concepts considering program needs, existing systems, human interfaces, information handling, data base management, and communications networking.
3.3.1.2.2 The contractor shall identify alternatives, formulate performance criteria, evaluate alternatives, and perform sensitivity checks considering trade-offs including but not limited to supportability, technology availability, reliability, compatibility, interoperability, and cost effectiveness.
3.3.1.2.3 The contractor shall prepare documentation and participate in technical reviews. Prepare and deliver system concept deliverables IAW CDRLs A010, A012 and A013.
3.3.1.3 Prototyping
3.3.1.3.1 The contractor shall develop prototypes for developmental projects using approved designs. Prepare and deliver prototype documentation IAW CDRLs A010, A012, A013, A014, A015 and A016.
3.3.1.3.2 The contractor shall perform limited fabrication, including but not limited to the electrical and mechanical connections for the production of mock-ups and prototype systems; mockups shall be used to perform system development, testing, and demonstration prior to production.
3.3.1.3.3 The contractor shall deliver prototypes to the location designated in the task order and provide user training. Prepare and deliver prototype user training IAW CDRL A017.
3.3.2 Systems Design and Engineering Support
3.3.2(a) System Design and Engineering efforts using Research, Development, Test and Evaluation (RDT&E) funds, perform planning and execution for SATCOM, RF, Video, and Networking Technologies systems, and subsystems design engineering on new, developing or existing systems undergoing improvement. Applicable to 3.3.2.1, 3.3.2.2, and 3.3.2.3.
3.3.2(b) System Design and Engineering efforts using Procurement funds, perform planning execution of efforts for SATCOM, RF, Video, and Networking Technologies systems, and subsystems including production engineering, fabrication and assembly. Applicable to paragraphs 3.3.2.2, and 3.3.2.3.
3.3.2(c) System Design and Engineering efforts using Working Capital Fund (WCF) funds, perform the planning and execution of development and design efforts and modernization and modification efforts for SATCOM, RF, Video, and Networking Technologies systems, and subsystems. Applicable to paragraphs 3.3.2.1, 3.3.2.2, and 3.3.2.3.
3.3.2(d) System Design and Engineering efforts using Non-DoD funds, perform the planning and execution of development and design efforts and modernization and modification efforts for SATCOM, RF, Video, and Networking Technologies systems, and subsystems. Applicable to paragraphs 3.3.2.1, 3.3.2.2, and 3.3.2.3.
3.3.2(e) System Design and Engineering efforts using Operations and Maintenance (O&M) funds, perform operations and technical support of fielded/in-service and out-of-production SATCOM, RF, Video, and Networking Technologies systems, and subsystems. Applicable to paragraphs 3.3.2.2.1, 3.3.2.2.2, 3.3.2.3.1, and 3.3.2.3.5.
3.3.2.1 System Design
3.3.2.1.1 The contractor shall evaluate the feasibility and supportability of proposed design solutions considering intrasystem and future intersystem performance.
3.3.2.1.2 The contractor shall provide recommendations for SATCOM, RF, Video,…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .