DRAFT_CUXS_CSS SOW_V5.3.docx
DOCX document 116 KB Posted
- Attached to
- Counter Uncrewed Systems Support Services
- Solicitation number
- N00421-24-RFPREQ-4K0000T-1255
About this file
This document is a draft Statement of Work for Counter Uncrewed Systems (C-UXS) Support Services. As the organic Lead Systems Integrator (oLSI) for the Naval Air Warfare Center Aircraft Division (NAWCAD), the NAWCAD Combat Integration & Identification Systems (CI&IDS) Division has requirements for the support and sustainment of C-UXS systems, to include system integration, production and fabrication, in-service engineering, training, logistics engineering, supply and material control, testing, operations, laboratory and test bed maintenance, engineering, frequency spectrum authorization, and technical management.
The work is anticipated to be performed 78% at the contractor site and 22% at the government site (Webster Field, St. Inigoes, MD and NAS Patuxent River), with travel to other CONUS and OCONUS locations as required. The contract vehicle is expected to be a single award Indefinite Delivery Indefinite Quantity (IDIQ) with an estimated level of effort of 507,024 man-hours over a five year ordering period. The applicable NAICS code is 541330 with a small business size standard of $47.0 million. Responses are due by 15 November 2024.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATEMENT OF WORK FOR
COMBAT INTEGRATION & IDENTIFICATION SYSTEMS
COUNTER UNCREWED SYSTEMS SUPPORT SERVICES
Scope.
As the organic Lead Systems Integrator® (oLSI®) for the Naval Air Warfare Center Aircraft Division (NAWCAD), Webster Outlying Field (WOLF) operates under a product-based business model whereby NAWCAD WOLF civilians lead and manage the execution of the requirements with combined Government-Industry teams. Using this oLSI® approach, the Government maintains control of intellectual property and data rights, enabling WOLF to rapidly adapt solutions to the dynamic needs of the warfighter.
The NAWCAD WOLF Combat Integration & Identification Systems (CI&IDS) Division, operating under the oLSI® model, has requirements for the support and sustainment of Counter Uncrewed Systems (C-UXS) including, but not limited to, systems that provide detection, characterization, identification, mitigation, and assessment of friendly or adversarial platforms to include the tasks of provide support for system integration, production and fabrication, in-service engineering, training, logistics engineering, supply and material control, testing, C-UXS operations, laboratory and test bed maintenance, C-UXS engineering, frequency spectrum authorization, and technical management.
Applicable Documents.
Department of Defense (DoD) Specifications.
DoD National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule.
DoDM 5200.01 Vol. 2, Marking of Classified Information, Change 4, 28 Jul 2020.
SECNAV M-5510.36B, Department of the Navy, Information Security Program, 12 Jul 2019.
DoDI 5200.48, Controlled Unclassified Information (CUI), 6 Mar 2020.
DoDD 5400.07, DoD Freedom of Information Act (FOIA) Program, 5 Apr 2019.
DoDI 5230.24, Distribution Statements on Technical Documents, Change 3, 10 Jan 2023.
SECNAV M-5510.30C, Department of the Navy, Personnel Security Program, 24 Jan 2020.
OPNAVINST 3440.17A, Navy Installation Emergency Management Program, 1 Aug 2014.
SECNAVINST 5239.20A, Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification, 10 Feb 2016.
DoDD 8140.01, Cyberspace Workforce Management.
DoDI 1035.01, Telework and Remote Work, 8 Jan 2024.
DoDI 4151.19 (Change 2), Serialized Item Management (SIM) for Life-Cycle Management of Materiel, 31 Aug 2018.DoD Standards.
MIL-STD-882E w/change 1, Department of Defense Standard Practice: System Safety, 27 Sep 2023.
MIL-STD-881F, Department of Defense Standard Practice: Work Breakdown Structures for Defense Materiel Items, 13 May 2022.
MIL-STD-38784B, Department of Defense Standard Practice: General Style and Format Requirements for Technical Manuals, 16 Nov 2020.
MIL-STD-2106A, Department of Defense Standard Practice: Development of Shipboard Industrial Test Procedures, 4 Jun 2014.
MIL-STD-3034A NOT 2, Reliability-Centered Maintenance (RCM) Process, 27 March 2024 GEIA-STD-0007C, Logistics Product Data, 6 Nov 2019.
Other Government Documents.
National Institute of Standards and Technology (NIST) Special Publication (SP), 800-53A Rev. 5 National Security Decision Directive 298, dated 22 January 1988 Public Law 100-235, Section 3(d)(4).
NAWCADINST 3070.4, Operations Security, 11 Apr 2022.
S9081-AB-GIB-010, NAVSEAINST 4130, NAVSEA Reliability-Centered Maintenance Handbook.
NAVSEAINST 4130.12B, Configuration Management (CM) Policy and Guidance, 12 Jul 2004.
NAVAIRINST 13640.1C, Naval Aviation Metrology and Calibration Program, 28 Apr 2014.
NAVAIRINST 4355.19E, Systems Engineering Technical Review Process, 06 Feb 2015.
STANAG 4193, Technical Characteristics of IFF Fleet A and Fleet Interrogators and Transponders, Part I through XI.
SOP-CIIDS-B-SEC-002, Security.
SWP4K200T-001, CI&IDS Division Engineering and Design Packages.
SOP4K200T-016, Root Cause Analysis.
SOP4K200T-019, Supply Support Unit.
SOP4K200T-020, Testing.
SOP-CIIDS-T-008, Drawing Control.
Industry Documents.
American Society for Testing and Materials (ASTM) manual A.
International Organization for Standardization (ISO), ISO 9001:2015.
IPC J-STD-001, Requirements for Soldered Electrical and Electronic Assemblies.
ASME Y14.100 – 2017, Engineering Drawing Practices.
ASME Y14.24 – 2012, Types and Applications of Engineering Drawings.
ASME Y14.34 – 2013, Associated Lists.
ASME Y14.35 – 2014, Revision of Engineering Drawings and Associated Documents.
ASME Y14.41 – 2012, Digital Product Definition Data Practices.
Requirements.
General Requirements.
Compatibility. The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government Information Technology (IT) environment through the security classification of Top Secret (TS) as specified on the DD Form 254, Contract Security Classification Specification Form (Attachment XX). The current operating environment required for this Contract includes:
Microsoft Windows 16 Microsoft Project 2016 Microsoft Office Professional Plus 2016 Adobe Acrobat XI (Pro) Internet access
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 ensure that all media are virus free when delivered. The Contractor shall be capable of internet and Local Area Network (LAN) communications with the CI&IDS Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with CI&IDS Division during working hours whether at contractor work site or on travel.
Work Location, Facilities, and Telework
1.1.1.1 Work Location. Approximately 22% of work will be performed at Government site and 78% of work to be performed at contractor site. Government site(s) include Naval Air Station (NAS), Patuxent River and Webster Outlying Field, St. Inigoes, MD.
Government Site Requirements.
Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.
Contractor Site Requirements.
In support of the tasking outlined in this Statement of Work (SOW), the Contractor shall have the capability to host and conduct meetings at the classification levels up to TS with the capacity to support a minimum of 20 persons and have contractor-furnished telephone and Video Teleconference (VTC) capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in section 3.1.1.
Meeting Support. Meeting support shall be provided within a 100 drivable miles of the Government Program Office location at the CI&IDS Division of NAS Patuxent River and Webster Outlying Field St. Inigoes, MD.
The Contractor shall gain access to the appropriate corporate applications. These systems may include, but are not limited to, NMCI, One Touch, and Navy Enterprise Resource Planning (N-ERP). Contractor personnel assigned to perform work under this Contract who require access to Government IT Systems shall comply with Department of the Navy Information Assurance (IA) and personnel security requirements for accessing Government IT systems.
Telework.
The Contractor may allow contractor employees to telework (either in full time or in hybrid status) in accordance with (IAW) DoDI 1035.01, Telework and Remote Work and the table in section 3.4. The Contractor may utilize alternate worksites/locations to telework to support continued performance of SOW tasks IAW company policy. When using telework, the Contractor remains responsible for contract performance and compliance with any applicable cost accounting standards and contract cost principles/procedures.
Full time telework is defined as a position that does not require routine on-site performance. However, on-site performance may be necessary on occasion and shall be provided when requested by the Contracting Officer’s Representative (COR). Full time telework positions shall be staffed within 50 drivable miles of NAWCAD WOLF, St. Inigoes, MD.
Hybrid telework is defined as a position that requires routine on-site performance of two days per week. On-site performance may be required outside of routine on-site performance days, and shall be provided when requested by the COR. Hybrid telework positions shall be staffed within 50 drivable miles of NAWCAD WOLF, St. Inigoes, MD.
In the event that telework tools become unavailable while working off-site, the Contractor shall require teleworking employees to report on-site in order to access the tools required for performance of this Contract.
At any time during contract performance, the COR may determine that a position is no longer eligible for full time telework and/or hybrid telework by providing a notice 30 calendar days in advance so the Contractor can address changes needed to support mission requirements.
1.1.1.2 Industrial Space
The Contractor shall provide sufficient industrial space for the receipt, storage, inventory, and shipment of equipment associated with assigned projects. Historically, the space required to meet SOW requirements has been no less than 10,000 feet. Additionally, the space shall be equipped with Heating, Ventilation, and Air Conditioning (HVAC) systems capable of sustaining a controlled environment consistent with the storage, assembly, and operation of electronic equipment. The space shall be configured to meet requirements for receiving, material receipt inspection, storage awaiting build up, integration and testing, and storage of completed systems. The space shall be equipped to protect Government property and shall be located within 15 drivable miles of NAWCAD WOLF, St. Inigoes, MD. The Government will not have desk occupancy at the location and will not take possession of the facility at contract termination.
Contract Status Reporting. The Contractor shall provide the following documentation.
Monthly Progress and Financial Status Report. The Contractor shall provide a progress and financial status report IAW the Contract Data Requirement List (CDRL). The report shall include work accomplished since submittal of the last report, both monthly and cumulative work hour labor costs expended by labor category, and material and travel costs. (CDRL A001)
1.1.1.3 The Contractor shall prepare and deliver an Organizational Chart & Labor Mix Plan. (CDRL A002)
1.1.1.4 The Contractor shall provide a Certificate of Compliance with ISO 9001:2015. (CDRL A003) Work schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.
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 0730 to 1600 each Monday through Friday (except on the legal holidays as specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0600 and end as late as 1800 Monday – Friday. Core hours are 0900 to 1500 Monday through Friday and weekend work may be required.
CWS. CWS is an alternative work schedule to the traditional 5 8.5-hour workdays (which includes a 30-minute lunch break) worked per week. Under a CWS schedule, an employee completes the following schedule within a 2-week period of time: 8 weekdays are worked at 9.5 hours each (which includes a 30-minute lunch break), 1 weekday is alternately worked at 8.5 hours (which includes a 30-minute lunch break), and 1 weekday is not worked by the employee. The result is 80 hours worked every 2 weeks, with 44 work hours 1 week and 36 work hours the other.
The Contractor may allow its employees to work a CWS schedule provided the requirements of this 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 as required by the Government to the COR/Alternate Contracting Officer’s Representative (ACOR).
Holidays. The Government observes the Federal holidays identified on the Office of Personnel Management (OPM) website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview. With the exception of the events in section 3.1.4.1.3 below, the Contractor is permitted to observe Federal holidays IAW its corporate policy.
Installation Closure. When Federal facilities are closed by the Government or 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 (KO) must concur with any determination that work being performed by contractor personnel is mission essential.
Other Direct Costs (ODCs). Procurement (PROC); Operations & Maintenance (O&M); and Research, Development, Test & Evaluation (RDT&E).
Travel. Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking is required. If required, temporary travel locations include the Continental United States (CONUS) locations of Mobile, AL; San Diego, CA; Groton, CT; Key West, FL; Mayport, FL; Pensacola, FL; Kings Bay, GA; Avondale, LA; Bath, ME; Gulfport, MS; Pascagoula, MS; Stennis Space Center, MS; Nashua, NH; Moorestown, NJ; Greenlawn, NY; Long Island, NY; Syracuse, NY; Mechanicsburg, PA; Newport, RI; Charleston, SC; Millington, TN; Norfolk, VA; Wallops Island, VA; Bremerton, WA; Marinette, WI; and Sturgeon Bay, WI as well as the Outside the Continental United States (OCONUS) locations of Adelaide, Australia; Manama, Bahrain; Diego Garcia; Pearl Harbor, HI; Naples, Italy; Okinawa, Japan; Yokohama, Japan; Yokosuka, Japan; Sasebo, Japan; Rota, Spain; and Dubai, UAE. This list is not all inclusive as locations may change over the life of the Contract.
1.1.1.4.1 The Contractor shall make all travel arrangements for its personnel.
1.1.1.4.2 Travel authorization requests shall be prepared and submitted no less than five business days prior to travel for COR approval, when possible.
The Contractor shall not authorize travel without first obtaining Government approval for travel beyond a 50-mile radius of the Contractor's office whenever a task assignment requires work at a temporary alternate work site.
The Contractor shall prepare and deliver a trip report for each individual trip, whether the mission was completed in whole or in part. (CDRL A004) The Contractor shall prepare and send a Technical Assistance Performance Evaluation (TAPE) form to all sites at where work is performed under SOW paragraph 3.3. Upon return of the TAPE form, the Contractor shall deliver the completed form to the COR or to COR-designated personnel. (CDRL A005) Synchronized Pre-Deployment & Operational Tracker (SPOT). The Contractor may travel in combatant command locations. SPOT enables the validation of Contractors Authorized to Accompany the Force (CAAF) (i.e., contractor personnel associated with specific contracts and subcontracts); 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.dmdc.mil, to enter and maintain data with respect to traveling/deployment personnel and to generate LOAs.
1.1.1.4.3 LOA. The KO will provide the LOA for official travel OCONUS, when applicable. The LOA will identify local authorizations, privileges, etc. as specified by DoD requirements. All defense contractors working under this Contract shall carry an LOA, when applicable, with them at all times while deployed OCONUS.
Material. Incidental material will be required in the performance of this Contract, and all incidental material purchases shall be IAW CTXT.242.9520, Procedures and Approvals Required Prior to Incurring Direct Material Costs. 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 by way of a DD Form 250, Material Inspection and Receiving Report. Material costs may include general and administrative expenses but shall not include profit/fee. (CDRL A006) Subcontractors. Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this Contract. All provisions of this SOW shall flow down to subcontractors providing support under this Contract.
Management of Contractor Personnel. The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will 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 actions that give the perception of personal services.
Transition-Out Plan.
The Contractor’s overall transition-out plan shall be built around maintaining the mission of the CI&IDS Division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Prior to the 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, to include the minimum elements listed below IAW CDRL A007.
· Work turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the Contract to the successor company and establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.
· Quality Assurance (QA). The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.
· Risk mitigation strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.
· Data/information transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.
Technical Direction Letters (TDLs). When necessary, technical direction or clarification concerning the details of specific tasks set forth in the Contract and the Task Orders (TOs) will be given through issuance of written TDLs. TDLs will not, in any manner, alter the scope of the Contract or TO. For further direction see HTXT.242-9502, Technical Direction (Variation) in Section H of the Contract. The Contractor shall prepare and deliver a COR Management Report for TDLs IAW CDRL A001.
1.1.2 The Contractor shall report Organizational Conflict of Interest (OCI) Mitigation Plan compliance and compliance status changes. (CDRL A008) Vehicle and Equipment Operation. The Contractor shall ensure employees possess the required civilian licenses to operate the vehicles and equipment necessary to perform contract requirements IAW the SOW. Before operating any military or Government-owned and/or Government-leased vehicles or any Government-owned equipment, the contractor employee shall provide proof of a state authorized license (issued by an appropriate Governmental authority) to the KO or COR/ACOR. The state authorized license must be a driver's license issued by the state, District of Columbia, territory, or possession in which the employee is domiciled or principally employed.
Vehicles. The Contractor shall be required to transport Government-owned systems, subsystems, components, and sub-components on a daily basis. Contractor personnel may also be required to operate Government-owned and/or Government-leased vehicles in the performance of this Contract.
1.1.2.1 Government-provided vehicles. The Contractor shall be required, as defined at the TO level, to operate Government-owned or -leased vehicles in performance of the Contract. Government-owned or -leased vehicles that the Contractor may use includes, but is not limited to, general purpose passenger carrying vehicles, special-purpose (tactical) vehicles, and CI&IDS Division authorized vehicles. All vehicles shall be operated IAW Naval Air Systems Command (NAVAIR) and site-specific processes and requirements. In general, there is no need for specialized licenses; however, if a requirement is identified in a specific TO, there will be time allotted for individuals to obtain the necessary licensing. The Contractor shall report any damage observed on the vehicle/equipment, and shall notify the Government Project Lead (GPL) and COR of any need for service or repair of the Government-owned or -leased vehicles. When operating these vehicles, the Contractor shall ensure: possession of a current and valid operator’s license for all vehicles; compliance with all state, federal, and host nation laws pertaining to operating motor vehicles; compliance with NAVAIR policies when operating a vehicle (e.g., no cell phone use, stopping at runway crossings, etc.); use of the most cost-effective means to fuel vehicles; and operation of the vehicles in a safe manner and IAW the vehicle/equipment user/operator manual.
1.1.2.2 If the Contractor is involved in an accident while operating a Government-owned or Government-leased vehicle, they shall notify the GPL, the Procuring Contracting Officer (PCO), and the COR with a verbal report within 24 hours and shall provide an accident report within 48 hours. (CDRL A009) When operating any Government-owned or Government-leased 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.
Security.
Citizenship Requirements. Only U.S. citizens may perform under this Contract, unless waived by the Government. 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.
Investigative Requirements.
Unclassified: All contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAV M-5510.30C. All contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the OPM. The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government Security Office shall initiate the contractor employee's Electronic Questionnaire for Investigations Processing (eQIP) and shall perform a preliminary screening of the contractor employee'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 employee access to Government facilities and information and may prohibit the contractor employee from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the contractor employee's eQIP. In such cases, the contractor employee may not perform on the Contract.
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 Form 254, Contract Security Classification Specification Form. Contractor personnel shall require access to classified information in performance of this Contract up to and including TS facility level, with a safeguarding level of TS. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule. 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.
Contractor Personnel Labor Category Security Requirements. All personnel shall have the appropriate DoD Security Clearance Level or Interim Clearance IAW the chart below.
| LABOR CATEGORY |
| LEVEL |
| DoD SECURITY CLEARANCE LEVEL (INTERIM CLEARANCE ACCEPTABLE) |
| REQUIRED DAYS AFTER ISSUANCE OF CONTRACT |
| Administrative Assistant (Service Contract Act (SCA)) |
| N/A |
| Secret |
| 90 Calendar Days |
| Budget Analysts |
| Journeyman |
| Secret |
| 90 Calendar Days |
| Budget Analysts |
| Senior |
| Secret |
| 90 Calendar Days |
| Computer Hardware Engineers |
| Entry/Basic |
| TS/SCI |
| 90 Calendar days |
| Computer Hardware Engineers |
| Intermediate |
| TS/SCI |
| 90 Calendar Days |
| Computer Hardware Engineers |
| Advanced |
| TS/SCI |
| 90 Calendar Days |
| Computer Network Architects |
| Intermediate |
| Secret |
| Upon award |
| Computer Network Architects |
| Advanced |
| Secret |
| Upon Award |
| Drafter/CAD Operator III (SCA) |
| N/A |
| Secret |
| 90 Calendar days |
| Drafter/CAD Operator IV (SCA) |
| N/A |
| Secret |
| Upon award |
| Electrical Engineers |
| Junior |
| TS/SCI |
| 90 Calendar days |
| Electrical Engineers |
| Senior |
| TS/SCI |
| 90 Calendar days |
| Electro-Mechanical and Mechatronics Technologists and Technicians |
| Journeyman |
| Secret |
| Upon award |
| Electro-Mechanical and Mechatronics Technologists and Technicians |
| Senior |
| Secret |
| Upon award |
| Electronics Engineers, Except Computer |
| Journeyman |
| Secret |
| Upon award |
| Electronics Engineers, Except Computer |
| Senior |
| Secret |
| Upon award |
| Electronics Technician Maintenance I (SCA) |
| N/A |
| Secret |
| 90 days |
| Electronics Technician Maintenance II (SCA) |
| N/A |
| Secret |
| Upon award |
| Electronics Technician Maintenance III (SCA) |
| N/A |
| Secret |
| Upon award |
| Engineering Technician II (SCA) |
| N/A |
| Secret |
| 90 Calendar Days |
| Engineering Technician III (SCA) |
| N/A |
| Secret |
| Upon award |
| Engineering Technician IV (SCA) |
| N/A |
| Secret |
| Upon award |
| Engineering Technician V (SCA) |
| N/A |
| Secret |
| Upon award |
| Engineering Technician VI (SCA) |
| N/A |
| Secret |
| Upon award |
| General and Operations Managers |
| Senior |
| TS/SCI |
| 90 Calendar Days |
| Logisticians |
| Journeyman |
| Secret |
| Upon award |
| Management Analysts |
| Journeyman |
| Secret |
| 90 Calendar days |
| Material Coordinator (SCA) |
| N/A |
| Secret |
| 90 Calendar Days |
| Mechanical Engineer |
| Junior |
| TS/SCI |
| 90 Calendar Days |
| Mechanical Engineer |
| Journeyman |
| TS/SCI |
| 90 Calendar Days |
| Mechanical Engineering Technologists and Technician |
| Journeyman |
| TS/SCI |
| 90 Calendar Days |
| Mechanical Engineering Technologists and Technician |
| Senior |
| TS/SCI |
| 90 Calendar Days |
| Network and Computer Systems Administrator |
| Intermediate |
| TS/SCI |
| 90 Calendar Days |
| Network and Computer Systems Administrator |
| Advanced |
| TS/SCI |
| 90 Calendar Days |
| Project Management Specialist |
| Journeyman |
| TS/SCI |
| 90 Calendar Days |
| Software Developer |
| Entry/Basic |
| TS/SCI |
| 90 Calendar Days |
| Software Developer |
| Intermediate |
| TS/SCI |
| 90 Calendar Days |
| Software Developer |
| Advanced |
| TS/SCI |
| 90 Calendar Days |
| Supply Technician (SCA) |
| N/A |
| Secret |
| 90 Calendar Days |
| Technical Writer III (SCA) |
| N/A |
| Secret |
| 90 Calendar Days |
| Web and Digital Interface Designer |
| Intermediate |
| Secret |
| 90 Calendar Days |
Common Access Card (CAC)/Public Key Infrastructure (PKI) and System Authorization Access Request (SAAR).
SAAR. All contractor personnel requiring access to Government IT systems shall have an approved DD Form 2875, System Authorization Access Request (SAAR) form on file and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within 30 business days of their first day of work. SAAR forms shall be submitted to the COR, Government Technical Point of Contact (TPOC), or to the assigned Government Mission Partner Identity, Credential, and Access Management (MP ICAM) Trusted Associate (TA).
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 TA following completion of the Contract, relocation or termination of an employee, or upon request from the COR/PCO. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this Contract.
DD Form 254. The Contractor shall comply with security requirements specified in the DD Form 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 in accordance with the appropriate designation (Controlled Unclassified Information (CUI); Legacy For Official Use Only (FOUO); Covered Defense Information (CDI)). Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this Contract shall be referred to the TPOC/COR of this Contract for approval.
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 CUI and to control distribution of CUI IAW National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule and SECNAV M-5510.36B, Department of the Navy, Information Security Program. If the work is performed at the Government's facility, the Contractor shall comply with SOP-CIIDS-B-SEC-002, Security.
All contractor facilities shall provide an appropriate means of storage for CUI and materials. All CUI including legacy FOUO and CDI (meeting the definition DFARS Clause 252.204–7012, Safeguarding Covered Defense Information and Cyber Incident Reporting) generated and/or provided under this Contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, Controlled Unclassified Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF.
Any product containing CDI shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24, Distribution Statements on Technical Documents and have this statement displayed per DoDI 5230.24, Enclosures 3 and 4. Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this Contract shall be referred to the TPOC/COR of this Contract for approval.
All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement:
Distribution Statement (Insert Appropriate Letter and Authorization Title), (Insert Appropriate Reason Category) (dated – (Date of Distribution Authorization)). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: NAWCAD WOLF CI&IDS Installation and Certification COR, 17212 Webster Field Road, B8330, St. Inigoes, MD 20684.
Marking. All information generated by the Contractor shall be properly marked. Classified information shall be marked IAW DoDM 5200.01, Vol 2, Marking of Classified Information. CUI, including legacy FOUO information generated and/or provided under this Contract, shall be marked IAW DoDI 5200.48, Controlled Unclassified Information (CUI). Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DoDI 5230.24, Distribution Statements on Technical Documents and program Security Classification Guidance.
Public Release. Any CUI pertaining to this Contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or X (formerly known as Twitter), unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through the COR of this Contract.
Loss, compromise, and/or electronic spillage of classified information or CUI. All instances of loss, compromise, and electronic spillage of classified information or CUI shall be reported to the COR, TPOC, and Government Security Office within 72 hours of the incident occurring.
Operations Security (OPSEC). The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the Contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance (IA) and Communications Security (COMSEC). The OPSEC program shall be IAW National Security Decision Directive (NSDD) 298 and at a minimum shall include:
1) Assignment of responsibility for OPSEC direction and implementation.
2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.
3) Establishment of OPSEC education and awareness training.
4) Provisions for management, annual review, and evaluation of OPSEC programs.
5) Flow down of OPSEC requirements to subcontractors when applicable.
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; and protect sensitive unclassified information and activities that could compromise classified information or operations or degrade the planning and execution of operations performed by the Requirements Owner and Contractor in support of the mission. (CDRL A010) Antiterrorism Force Protection and Emergency Management. The work performed on this Contract is not Emergency Essential IAW OPNAVINST 3440.17A, Navy Installation Emergency Management Program 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.
1. Detailed Support Requirements.
System Integration.
| 3.3.1 (a) | (O&M) Provide support for engineering, integration, and technical tasking to perform system integration planning; maintenance of and updates to technical documentation; and the integration of hardware, software, and firmware into stand-alone and/or higher order systems, as necessary, to satisfy customer requirements in the O&M phase of the C-UXS project life cycle. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.7. |
| 3.3.1(b) | (PROC) Provide support for engineering, integration, and technical tasking to perform system integration planning; maintenance of and updates to technical documentation; and the integration of hardware, software, and firmware into stand-alone and/or higher order systems, as necessary, to satisfy customer requirements during the production and modernization phases of the C-UXS project life cycle. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.7. |
| 3.3.1(c) | (RDT&E) Provide support for engineering, integration, and technical tasking to perform system integration planning; maintenance of and updates to technical documentation; and the integration of hardware, software, and firmware into stand-alone and/or higher order systems, as necessary, to satisfy customer requirements in the development testing or evaluation phases of the C-UXS project life cycle. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.7. |
The Contractor shall assist in reviewing, preparing, and delivering detailed integration documentation for C-UXS, subsystems, components, and sub-components including, but not limited to, installation control drawings, interface control drawings, system block diagrams, system cable block diagrams, system cable/wire run sheets, equipment space arrangement drawings, elevation drawings, site installation drawings, and antenna systems arrangement drawings. (CDRLs A011, A012, A013, A014) The Contractor shall support the preparation and delivery of integration-related prototype fabrication drawings. (CDRL A011) The Contractor shall assist with the modification and fabrication of applicable integration fixtures and tools to satisfy integration-related applications. (CDRL A011) The Contractor shall assist with modifying or creating detailed electrical and mechanical assembly drawings, installation-engineering drawings, and reference and guidance drawings. (CDRL A012) The Contractor shall assist with creating, modifying, and updating operator and technical instruction manuals to reflect changes to system configuration or operation IAW MIL-STD-38784B, Department of Defense Standard Practice: General Style and Format Requirements for Technical Manuals. (CDRL A015) The Contractor shall assist by performing analyses of antenna design, characterization, and limitations and then by providing detailed analyses of antenna patterns and detailed antenna characterization reports for integration locations. (CDRL A016) The Contractor shall support integrating systems, subsystems, components, and sub-components into stand-alone or higher level assemblies IAW established project requirements. (CDRL A016) Production and Fabrication.
| 3.3.2(a) | (O&M) Provide production and fabrication of C-UXS, subsystems, components, and sub-components to support the CI&IDS Division’s oLSI® role in providing rapid product solutions to satisfy customer requirements in the O&M phase of the project life cycle. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.6. |
| 3.3.2(b) | (PROC) Provide production and fabrication of C-UXS, subsystems components, and sub-components to support the CI&IDS Division’s oLSI® role in providing rapid product solutions to satisfy customer requirements during the production and modernization phases of the project life cycle. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.6. |
| 3.3.2(c) | (RDT&E) Provide production and fabrication of C-UXS, subsystems, components, and sub-components to support the CI&IDS Division’s oLSI® role in providing rapid product solutions to satisfy customer requirements in the development testing or evaluation phases of the project life cycle. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.6. |
The Contractor shall assist by providing Level III drawing packages, IAW references ASME Y14.100 – 2017, Engineering Drawing Practices; ASME Y14.24 – 2012, Types and Applications of Engineering Drawings; ASME Y14.34 – 2013, Associated Lists; ASME Y14.35 – 2014 Revision of Engineering Drawings and Associated Documents; and ASME Y14.41 – 2012, Digital Product Definition Data Practices for the production of C-UXS, subsystems, components, and sub-components. (CDRL A013) The Contractor shall assist by participating in the initiation, technical review, cost impact estimation, resolution, and incorporation of Engineering Change Orders (ECOs) IAW SWP4K200T-001, CI&IDS Division Engineering and Design Packages. (CDRL A013) The Contractor shall assist by maintaining the configuration control of drawings at all times and by issuing drawings IAW SOP-CIIDS-T-008, CI&IDS Drawing Control.
The Contractor shall assist by providing subject matter expertise to internal and external vendors and machine shops for the purpose of producing or fabricating C-UXS.
The Contractor shall assist by providing detailed descriptions of all production and fabrication processes and procedures in the form of Standard Operating Procedures (SOPs) or Work Instructions IAW the CI&IDS Quality Program. (CDRLs A017 and A018) The Contractor shall assist with assembling, building, constructing, and fabricating systems, subsystems, components, and sub-components from lower-level subsystems, components, sub-components, or raw materials to deliver higher-level assemblies or completed products.
In-Service Engineering Support.
| 3.3.3(a) | (O&M) Provide support for in-service engineering services across all C-UXS and subsystems necessary to satisfy customer requirements during the O&M phase of the project life cycle. Applicable to SOW paragraphs 3.3.3.1 – 3.3.3.4. |
| 3.3.3(b) | (PROC) Provide support for in-service engineering services across all C-UXS and subsystems necessary to satisfy customer requirements during the production and modernization phases of the project life cycle. Applicable to SOW paragraphs 3.3.3.1 – 3.3.3.4. |
| 3.3.3(c) | (RDT&E) Provide support for in-service engineering services across all C-UXS and subsystems necessary to satisfy customer requirements in the development testing or evaluation phases of the project life cycle Applicable to SOW paragraphs 3.3.3.1 – 3.3.3.4. |
The Contractor shall assist by performing analyses to determine if defects exist, recommend improvements, document metrics, assess system performance to design specifications, and develop engineering changes to fielded systems.
The Contractor shall support documented performance and reliability metrics tied to key program performance and sustainment objectives. (CDRL A019) The Contractor shall assist by providing analyses of available operational and maintenance performance data to determine design defects detracting from the equipment or systems capability to perform intended operational requirements and to meet maintainability and reliability requirements. (CDRLs A019 and A020) The Contractor shall assist with providing recommended corrections or improvements for translation into detailed engineering changes. (CDRLs A021 and A022) The Contractor shall support the development of engineering changes and/or alterations to provide system improvements, correct deficiencies, and improve logistic support. (CDRLs A013, A016, A023) The Contractor shall assist with the development, review, and maintenance of base, shipboard, and shipyard inspection procedures. (CDRL A016) The Contractor shall assist with conducting system inspections IAW Government-approved platform inspection procedures and by providing an inspection report upon completion. (CDRLs A024 and A025) The Contractor shall assist the Government with the implementation and execution of system safety programs across C-UXS and subsystems IAW MIL-STD-882E w/change 1, Department of Defense Standard Practice: System Safety.
The Contractor shall support the GPLs with the development of project-specific hazard and mishap definitions; the collection and aggregation of defects and deficiencies; and the categorization of defects and deficiencies. (CDRL A026) The Contractor shall assist with the analysis of defects and deficiencies to determine their impact to safety based on the system-defined hazards. (CDRLs A020, A021, A022) The Contractor shall support documentation of safety-related defects and deficiencies. (CDRL A027) The Contractor shall assist by creating, maintaining, reviewing, and updating technical documentation related to the design, operation, and maintenance of C-UXS and subsystems.
The Contractor shall support the review of standards, system specifications, interface specifications, technical manuals, technical drawings, and other technical data IAW MIL-STD-38784B, Department of Defense Standard Practice: General Style and Format Requirements for Technical Manuals. (CDRLs A015, A016, A028, A029, A030) The Contractor shall assist with producing technical documents or technical document revisions upon Government approval of recommendations. (CDRLs A016, A028, A029) The Contractor shall support the development, review, and revision of Reliability Centered Maintenance (RCM) including, but not limited to, Planned Maintenance System (PMS) Maintenance Index Pages (MIPs), Maintenance Requirements Cards (MRCs), or equivalent for systems and equipment IAW MIL-STD-3034A NOT 2, Reliability-Centered Maintenance (RCM) Process, and maintain a library of all RCM data using the CI&IDS data repositories. (CDRL A030) The Contractor shall support scheduled technical assistance to ships and shore installations of C-UXS and subsystems. (CDRLs A021 and A022) The Contractor shall assist by providing Field Service Representative (FSR) capability to regions that can support emergency technical assistance to ships and shore installations of C-UXS and subsystems. Such locations are as defined by section 3.1.5.1.
The Contractor shall assist with telephone and email support to deployed users by providing an initial response within 72 hours of receipt, as defined by site prioritization. (CDRLs A021 and A022) The Contractor shall assist with inspecting, troubleshooting, and repairing and/or adjusting the equipment during planned and unplanned ship and site visits. (CDRLs A021 and A022) The Contractor shall support on-site engineering investigations to evaluate performance of systems and/or equipment in order to determine failure modes, corrective actions, and potential improvements. (CDRLs A016, A021, A022) The Contractor shall assist with providing technical library services for collecting, storing, retrieving, distributing, and accounting for operational, test, and simulation programs.
Training.
| 3.3.4(a) | (O&M) Provide training and training materials for C-UXS and subsystems to provide rapid product solutions to satisfy customer requirements in the O&M phase of the project life cycle. Applicable to SOW paragraphs 3.3.4.1 – 3.3.4.2. |
| 3.3.4(b) | (PROC) Provide training and training materials for C-UXS and subsystems to provide rapid product solutions to satisfy customer requirements during the production and modernization phases of the project life cycle. Applicable to SOW paragraphs 3.3.4.1 – 3.3.4.2. |
| 3.3.4(c) | (RDT&E) Provide training and training materials for C-UXS and subsystems to provide rapid product solutions to satisfy customer requirements in the development testing or evaluation phases of the project life cycle. Applicable to SOW paragraphs 3.3.4.1 – 3.3.4.2. |
The Contractor shall assist with providing formal classroom training.
The Contractor shall support the development and maintenance of training curriculums to support the delivery of formal classroom-based training programs to include laboratory training exercises. (CDRLs A031, A032, A033) The Contractor shall assist by scheduling and conducting classroom and laboratory training sessions and by submitting a Training Class Completion and Class Survey Report upon completion of each training class. (CDRL A032) The following are examples of typical course information.
| EQUIPMENT/SYSTEM |
| TYPE DESCRIPTION |
| SITE |
| LENGTH |
| NINJA |
| Maintenance Course |
| Webster Field |
| Up to one week |
| NINJA |
| Operator Course |
| Webster Field |
| Up to one week |
| SKYTRACKER Family of Systems (CORIAN, BEAM, AWAIR) |
| Maintenance Course |
| Webster Field |
| Up to one week |
| SKYTRACKER Family of Systems (CORIAN, BEAM, AWAIR) |
| Operator Course |
| Webster Field |
| Up to one week |
| Marine Air Defense Integrated System (MADIS), Light Marine Air Defense Integrated System( L-MADIS), Expeditionary Marine Air Defense Integrated System (X-MADIS) |
| Maintenance Course |
| Webster Field |
| Up to one week |
| Marine Air Defense Integrated System (MADIS, L-MADIS, X-MADIS) |
| Operator Course |
| Webster Field |
| Up to one week |
| ANDURIL Systems |
| Maintenance Course |
| Webster Field |
| Up to one week |
| ANDURIL Systems |
| Operator Course |
| Webster Field |
| Up to one week |
The Contractor shall assist in the training of the materials, knowledge, skills, and competencies required to troubleshoot, repair, and maintain the equipment under instruction.
The Contractor shall provide administrative support to the government for security escort requirements for visitors, foreign and domestic, attending training onboard NAS Patuxent River or Webster Outlying Field.
The Contractor shall provide technical support for the formal systems training program including technical reviews of training material; supplemental training material…
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 .