AEGIS_RCS_-_PWS_(pre-tarb)_Sources_Sought.docx
DOCX document 139 KB Posted
- Attached to
- AIR-4. 11, N00421-18-R-0013 AEGIS AD-4. 11. 3
- Solicitation number
- N00421-18-R-0013
About this file
Statement of Work
View the file
Other files
| File | Type | Posted |
|---|---|---|
| AEGIS_RCS_-_PWS_SOW.pdf | ||
| AEGIS_Contract_CLIN_Structure_Synopsis_1.pptx | PPTX presentation | |
| AEGIS_RCS_-_Labor_Hours.pdf |
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
Performance Work Statement (PWS) and Statement of Work (SOW) for AEGIS Radio Communication System (RCS)
1.0 SCOPE
The Ship & Air Integrated Warfare (SAIW) Division, Naval Air Warfare Center Aircraft Division (NAWCAD) 4.11.3, located in St. Inigoes, Maryland, is an organic Lead Systems Integrator (oLSI) providing design, procurement, integration, testing, and training of Command, Control, Communications, Computers, and Intelligence (C4I) electronic systems that meet the requirements of the U.S. Navy operating forces are the responsibility of the Program Executive Office for C4I (PEO C4I). In support of the Program Executive Office for Ships (PEO Ships), Naval Sea Systems Command (NAVSEA), and PEO C4I, the SAIW Division is tasked to design, procure, integrate, test, train, deliver and support C4I electronic RCSs for ships of the U.S. Navy including, but not limited to, AEGIS destroyers and cruisers, amphibious assault ships, aircraft carriers, sea-lift ships, and other surface combatant and comparable ships. The SAIW Division is tasked to perform research and development, engineering, technical, and logistics support services to deliver fully integrated and tested C4I electronic radio communication systems for shipboard installation.
This PWS/SOW supports the SAIW Division in the research, development, design, integration, testing, installation, training, and certification of shipboard C4I electronic communication systems; the research, development, design, integration, testing, installation, training, and certification of like systems at shore sites associated with the deployment of fleet support to surface ships; and the research, development, design, integration, testing, installation, training, and certification of mobile and airborne C4I electronic communication systems designed to interface with the C4I electronic architecture of surface ships.
2.0 APPLICABLE DOCUMENTS
2.1 DoD Specifications
2.2 DoD Standards
2.2.1 MIL-STD-31000A, Technical Data Packages
2.2.2 MIL-STD-100E, Engineering Drawing Packages
2.3 Other Government Documents
2.3.1 SECNAVINST 5216.5D, Department of the Navy Correspondence Manual
2.3.2 DoD Directive 5000.3, Test and Evaluation
2.3.3 OPNAVINST 3432.1A, Operations Security
2.3.4 NAWCADINST 3432.1A, Operations Security
2.3.5 NAWCADINST 5510.1A, NAVAIRWARCENACDIV Information, Personnel and Industrial Security Program Manual
2.3.6 NAVAIRINST 5216.8C, NAVAIR Supplement to the Department of the Navy Correspondence Manual
2.3.7 NAVAIRINST 4355.19D, Systems Engineering Technical Review Process
2.3.8 NAWCADINST 5239.1, NAVAIRWARCENACDIV Information Systems Security (INFOSYSSEC) Program
2.3.9 NAWCADINST 7320.1A, NAVAIRWARCENACDIV Property Management Process for Minor Property and Class 5 and Class 4 Plant Property
2.3.10 DoD Integrated Master Plan and Integrated Master Schedule Preparation and User Guide
2.3.11 DoD 5220.22-M, National Industrial Security Program Operating Manual
2.3.12 SAIW Product Realization Standard Operating Procedure (SOP)
2.3.13 DoD-D-1000 Military Specification Drawing, Engineering and Associated Lists
2.3.14 DoD-D-1000 NAVAIRINST 3960.4B, Project Test Plan Policy and Guide for Testing Air Vehicles, Air Vehicle Weapons, and Air Vehicle Installed Systems
2.3.15 NAVSEA 0900-LP-095-2010, Ship Construction Tests and Trials Manual
2.3.16 NAVSEA T 9050-AA-DIR-010/AEGIS, AEGIS Ship Test Procedure Preparation Directive
2.3.17 NAVSEA 0900-LP-095-6010, Planning Guide Total Ship Test Program for Ship Production
2.3.18 NAWCADINST 2400.1B, Radio Frequency Management
2.3.19 OPNAVINST 5000.49A, Integrated Logistics Support (ILS) in the Acquisition Process
2.3.20 SECNAVINST 5239.3, NAVAIR Information Assurance Workforce Improvement Program
2.3.21 General Arrangements, Top Side Configuration
2.3.22 Guided Missile Destroyer, DDG 51 Class, Radio Communications Inter-Space Block Diagram
2.3.23 Guided Missile Destroyer, DDG 51 Class, Communication Center and Transmitter Room Space Arrangement of Equipment Envelopes
2.3.24 Guided Missile Destroyer, Radio Communications Intra-Space Cable Block Diagram
2.3.25 Guided Missile Destroyer, Communications Center and Transmitter Room Arrangement of Equipment
2.3.26 SAIW Product Realization Standard Operating Procedure (SOP)
2.4 Industry Documents
2.4.1 ANSI/ASQ ISO 9001:2008 American National Standards Institute/American Society for Quality
2.4.2 ANSI/TIA-568 Structured Cabling Standards and Practices
2.4.3 Electronic Industries Alliance (EIA) 632 Standard- Processes for Engineering a System
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. The current operating environment required for this contract includes:
Microsoft Windows 10 Microsoft Project 2010 Microsoft Office Professional Plus 2010 Adobe Acrobat XI (reader) Internet access AutoCAD
CATIA
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 Local Area Network (LAN) communications with the SAIW Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the SAIW Division during working hours whether at Contractor work site or on travel.
3.1.2 Work Location and Facilities
3.1.2.1 Work Location: Approximately 49 percent of work will be performed at Government sites and 51 percent of work to be performed at Contractor sites. The Government site for this effort will require performance at the Naval Air Station (NAS) Patuxent River, Webster Field Annex. 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 geographic location of the Contractor’s primary facility with respect to NAS Webster Field must be within a fifty-mile driving distance of the Government Program Office at Webster Field.
3.1.2.2 Government Provide Integration Facilities: The Government will provide integration facilities at the System’s Integration Lab (SIL). The SIL is a group of Government owned integration and test facilities located on the NAWCAD Webster Field Annex. The facility is jointly occupied by Government and Contractor personnel currently performing RCS integration production services. The facility contains offices, shop area, CMS vault, loading docks, receiving/staging area, and test beds. The successful offeror responding to this solicitation shall share the shop and receiving/staging areas with other Contractors, as well with the incumbent Contractor during any required transition period. The Contractor shall provide on-site staff with the necessary management, administrative support, and office supplies/equipment for its use at the SIL.
Test Beds: Test beds are equipped and furnished for RCS integration and for Stages 3, 4, 6, and 7 testing. A Government supplied test bed will be assigned to the successful offeror for integration and testing of each RCS.
Classroom: The Government will provide an on base classroom for On the Job Training (OJT). If OJT is required to be off base, the conference room referenced in paragraph 3.1.2.3.1 below will be made available.
Physical Security Checks: Contractors assigned to work in Government facilities may be required to assist with end-of-day physical security checks, but will not be delegated the primary responsibility for such checks.
3.1.2.3 Contractor Provided Support Facilities: The Contractor shall provide off-base support facilities for the performance of this contract. If permanent facilities are not available to a Contractor at time of contract award, a plan of interim facilities availability shall be provided as part of the proposal. The Contractor’s permanent administrative and engineering services facility must be in place not later than 120 days after contract award. Cost of all facilities as outlined in section 3.1.2 and its subparts shall not be a direct cost to the Government.
Office Space: The Contractor shall provide sufficient office space for the administrative and technical support personnel required by this contract to directly support NAWCAD production and integration. A conference room shall also be included. The minimum net square footage required is 15,000. As part of this requirement, the Contractor shall also provide office space at the shipbuilder(s) facilities. Based on current shipbuilding initiatives, these offices will be at Bath, Maine and Pascagoula, Mississippi. The minimum net square footage required at each of these sites shall be 400.
Industrial Space: The Contractor shall provide sufficient industrial space for the storage and testing of electronic equipment and materiel. The minimum net square footage required is 30,000, not necessarily in one building. This includes space to provide distinct and securable areas for receiving, receipt inspection, testing and storage of parts and equipment. Additionally, the space shall be equipped with heating, air conditioning and ventilation (HVAC) systems capable of sustaining a controlled environment consistent with the storage of electronic equipment. The facility shall be equipped with fire detection, alarm and fire suppression systems and be protected against unlawful entry. The Contractor shall furnish and equip the facility to occupancy status and shall provide all equipment and materiel required for use in the facility.
Transportation: The Contractor shall provide and maintain the capability to transport RCS related equipment and incidental materiel between the Contractor’s local facilities, such as their receiving facility, and Webster Field, St. Inigoes, MD on a routine basis. The transport must be capable of hauling items requiring an access of 8 ¼ feet high and 7 ½ feet wide with a length of up to 24 feet. In order to prevent damage, the transport must be covered.
3.1.3 Contract Status Reporting
3.1.3.1 Financial Progress Reports: Financial progress reports shall be prepared monthly. In order to reduce the administrative burden presented by creating a unique reporting requirement and to allow these reports to be entered on the Contractor’s timesheet/payroll system, the actual periodicity of these reports will be determined by the Contractor’s existing accounting system. Under either circumstance, the purpose of this report is to provide SAIW with the current financial status of the contract at the CLIN/SLIN, ACRN and TDL level. When applicable, this report shall include prior year(s) expenditures. (CDRL A022)
3.1.3.2 Reporting of Costs: Contractor shall report costs to support invoice reviews, which are conducted as part of quality surveillance practices. (CDRL A023)
3.1.3.3 Monthly Status Report: The Contractor shall provide a monthly status report identifying all work performed during the reporting period. (CDRL A012)
3.1.3.4 Enterprise-wide Contractor Manpower Reporting Application (ECMRA): The Contractor shall report Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for NAWCAD via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:
(1) W, Lease/Rental of Equipment;
(2) X, Lease/Rental of Facilities;
(3) Y, Construction of Structures and Facilities;
(4) S, Utilities ONLY;
(5) V, Freight and Shipping ONLY.
The Contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil.
Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil. (CDRL A027)
3.1.4 Work Schedule
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 0800 to 1630 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.
Compressed Work Schedule (CWS): CWS is an alternative work schedule to the traditional five 8 ½-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 ½ hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8½ 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, with agreement by the Contracting Officer’s Representative (COR)/ Alternate Contracting Officer’s Representative (ACOR), may allow its employees to work a CWS schedule. 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. If agreement to implement the CWS schedule is reached with the COR, the overall schedule must be provided and approved. Key Contractor personnel, at the discretion of the COR, may not be allowed to work a CWS schedule even if the remaining employees are permitted to do so.
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. In the event any of the above holidays occur on a Saturday or Sunday, or CWS alternate Friday, then such holiday shall be observed in accordance with COR direction.
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 performing non-mission essential work 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 supervision from Federal personnel, in very limited circumstances, work being performed by Contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by Contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by Contractor personnel is mission essential.
Overtime: Overtime cannot be charged directly to the contract unless first approved in writing by the COR.
Telework: The Contractor, with COR 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. For regular reoccurring telecommuting to be authorized by the COR and the Contracting Officer, a written company policy for telecommuting must be in place with the Contractor covering all terms and conditions to include, but not limited to:
(1) A written agreement between the company and employee;
a) Work site of telecommute;
b) Time and Attendance; Work Performance; Overtime;
c) Security and Equipment;
d) Liability and Injury Compensation; Standards of Conduct; Mileage Savings;
e) Length of Agreement;
f) Specifics of the employer's telework and emergency planning policies.
2) Proposed definitive amount of work or level of effort to be accomplished.
3) Expected savings to the Government if authorized to Telecommute.
4) Measures in place to ensure project will be on schedule and auditable for reimbursement.
5) Access to NMCI, if access is required for performance.
Items (3.1.4.1.5)(1) through (3.1.4.1.5)(5) must be addressed in the Contractor's request for telecommuting. 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):
COR concurrence and Contracting Officer approval is required is required for procurement of all software licenses regardless of total value.
COR concurrence or Contracting Officer approval is not required for procurements of any items (excluding software licenses) with a total value of $3,500.00 or less.
COR concurrence is required for procurements of any items (excluding software licenses) with a total value between $3,500.01 and $150,000.00.
COR concurrence and Contracting Officer approval is required for procurements of any items (excluding software licenses) with a total value between $150,000.00 and $700,000.00.
No single procurement with a total value of $700,000.01 or greater is authorized under this contract.
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. Reimbursement for travel performed shall be in accordance with the DoD Federal Travel Regulation (http://www.defensetravel.dod.mil/site/travelreg.cfm). The COR shall approve all travel performed in support of this contract prior to the commencement of the travel. COR approval for local travel expenses is required. 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 CONUS locations; no OCONUS travel is anticipated at this time. This list is not all-inclusive, as locations may change over the life of the contract. Travel authorization request shall be prepared in accordance with the sample in Section J of the solicitation and submitted no less than five business days prior to travel (or less if emergent requirements so dictate) COR approval. (CDRL A004) CONUS: CONUS locations may include but is not limited to St. Inigoes, MD, Bath, ME, Pascagoula, MS, San Diego, CA, Mayport, FL, and Norfolk, VA.
Reserved Reserved Reserved Local Travel Reimbursement: Reimbursement of personal travel to-and-from NAWCAD 4.11.3, 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.
Travel with Government Personnel: The Contractor may, on occasion, be required to provide transportation to Government members of the travel team when it is deemed most economical to the Government and is otherwise in the Government’s best interest, and the cost for such transportation will be reimbursed in accordance with the ODC CLINs included in this contract.
Travel Reporting and Monitoring: The Contractor shall report all travel costs in the monthly status report, and shall monitor all travel costs to ensure each CLIN/SLIN, ACRN and/or TDL is not exceeded. (CDRL A004)
3.1.5.2 Materiel: All incidental materiel purchases will be approved per the solicitation clause "Restriction on the Direct Charging of Material (NAVAIR 5252.242-9515 Variation) (OCT 2013)" and 5252.232-9509 "Travel Approval and Reimbursement Procedures (NAVAIR) (OCT 2013).” Any materiel provided by the Contractor is subject to the requirements of the Federal Acquisition Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable Department of the Navy (DoN) regulations and instructions. All materiel not depleted during the performance of this contract shall become Government property upon completion of this contract. The Contractor shall transfer all materiel not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Other Direct Charges 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.
3.1.7 Transition Strategy: The overall strategy shall be built around maintaining the mission of the program/ division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. During the transition period, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation.
3.1.7.1 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. Establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.
3.1.7.2 Quality Assurance: The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.
3.1.7.3 Risk Mitigation Strategies: The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period. (CDRL A026)
3.1.8 Non-Disclosure Agreements (NDAs), Non-Government Purposes, and Conflicts of Interest
3.1.8.1 NDA: In the performance of the contract, the Contractor may have access to non-public proprietary information. The Contractor shall require that any employee performing services under the contract execute an NDA satisfactory to the Contracting Officer and the entity for which the information belongs. The NDA shall acknowledge the Contractor and employee's duties with respect to non-public information and promise to comply with those obligations. Copies of the executed NDAs shall be provided to the Government.
3.1.8.2 Non-Government Purposes: Consistent with the terms and conditions of paragraph (e)(5) of NAVAIR 5252.209-9510, “Organizational Conflicts Of Interest (Services)”, with respect to proprietary data of third parties, and DFARS 252.227-7025, “Limitations On The Use Or Disclosure Of Government-Furnished Information Marked With Restrictive Legends”, with respect to technical data, the Contractor shall not use, modify, reproduce, release, perform, display, or disclose any non-public information provided to or obtained by the Contractor in the course of performing the contract for other than Government purposes, and shall not do so for any commercial or personal purpose.
3.1.8.3 Conflicts of Interest: In the event the Contractor knows of, or identifies, an employee who has a commercial interest in the subject matter of any proposed or on-going agreement related to the services to be performed herein, the Contractor shall consider such interest a potential conflict of interest under paragraph (g) of NAVAIR 5252.209-9510, and promptly disclose it to the Contracting Officer.
3.1.9 Quality Management: The Contractor shall develop, implement, document, and maintain a quality management system to ensure conformance with contractual requirements and the specific quality and performance requirements under this contract. The quality management system shall be certified (prior to award) to the American National Standards Institute/American Society for Quality (ANSI/ASQ) ISO 9001:2008 (or later versions), from the ISO governing body. The Contractor’s quality approach should be clearly defined and recognize the need to focus on customer satisfaction, defect prevention over inspection, management responsibility and continuous improvement. (CDRL A019)
3.1.9.1 Inspection System Plan: All performance under this contract shall be subject to the approval of the Government. The Contractor shall submit an Inspection Test Plan. (CDRL A020)
3.1.9.2 Procedures and Work Instructions: All processes used to fabricate, assemble, modify, install, and test products shall be documented and updated. These written procedures and work instructions shall be made available to the employees required to perform the specific task. All procedures and work instructions shall be consistent with the Contractor’s quality management system. (CDRL A009)
3.1.9.3 Product Quality: A thorough review of quality requirements shall be conducted to identify the controls, processes, skills, fixtures, tools, and test equipment needed to ensure product quality. The planning review shall also update inspection and testing techniques, instrumentation, and manufacturing methods and processes. Standard program data (test results, defects/failures identified, calibration results, etc.) that may be required by the Government to compile trend evaluation shall be available upon request. (CDRL A019)
3.1.9.4 Reserved
3.1.10 Technical Direction Letters (TDLs)
3.1.10.1 Use of TDLs: TDLs may be used to allow the Government the flexibility to provide technical direction and clarification to the Contractor, which may redirect the contract effort, require pursuit of certain lines of inquiry, or fill in details to meet the requirements previously identified in paragraph 3.3 of the PWS/SOW. TDLs shall be generated, issued, revised and approved by means of an automated process capable of sharing data with the Government’s Management Information System in accordance with Section H, NAVAIR Clause 5252.242-9502 “Technical Direction” (NAVAIR)(APR 2011).
3.1.10.2 Clarification of Work: The Government anticipates that the TDLs will be used primarily to provide clarification regarding work already in execution in the event unforeseen circumstances dictate an adjustment in schedule and timeline. TDLs will not be utilized to create new work or additional tasking. The acquisition of U.S. Naval vessels is the responsibility of NAVSEA; whereas, the C4I electronic systems are the responsibility of PEO C4I. Along with NAVSEA and PEO C4I, NAWCAD has been tasked by PEO Ships to design, procure, integrate, test, train, deliver, and support C4I electronic Radio Communications Systems (RCSs) for ships of the U.S. Navy. As a result of the various organizations’ responsibilities and schedules impacting one another and potential unforeseen circumstances, it may be necessary to shift work emphasis between work areas or task. Examples of unforeseen circumstances are delays as a result of natural disasters and unscheduled/unanticipated fiscal realignments, resulting in successive scheduling changes. Furthermore, the duration of this contract coupled with outside influences, such as shipbuilder tasks and technology infusion, ensures variations in work areas and integrated/testing execution. Under this contract, TDLs will be used in addition to the Government’s Management Information System to provide the Contractor additional clarification / specificity regarding work already initiated and ongoing to ensure execution aligns with these variations. It is imperative to the successful delivery of the RCS that the Government provides this clarification on specific tasking through the duration of the contract. Situations that require clarification include, but are not limited to: drawing development and review processes, specific equipment testing execution, storage and handling practices for specific Navy electronic equipment, and engineering data format.
3.1.10.3 Project/TDL Closeout: The Contractor shall submit project/TDL/CLIN/SLIN closeout reports, which shall be signed by the Contractor's program manager. (CDRL A021)
3.1.11 Quality Surveillance and Performance Standards: The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables as provided in the Quality Assurance Surveillance Plan and Contract Surveillance Plan (QASP/CSP), Attachment 1.
The Government will evaluate Contractor performance in the areas of Quality, Schedule, Cost Control, Business Relations, Management, Small Business Compliance, and Other areas in accordance with the procedures and criteria established in the QASP/CSP.
3.1.12 Government Furnished Property (GFP)/Government Furnished Information (GFI): The Government has available at NAWCAD 4.11.3, for on-base and off-base usage, various Special Purpose Test Equipment (SPTE), and other special tools that are necessary to perform RCS design engineering, production, integration, testing, or installation functions. The items are shared by Government engineers and by Contractor support personnel working on other contracts. Previous usage history and anticipated usage on this contract does not support procuring complete sets for each Contractor. Therefore, these items will also be made available to the Contractor under this contract on an as required basis. If usage is higher than expected, the SAIW Division will provide additional assets as required. Items which will be available will be controlled and stored in the Ships Communication Tool room, located at St. Inigoes, MD. Authorized items are those within the Ships Communication Tool room inventory database. See Scheduled Government Furnished Property (SGFP) and Requisitioned Government Furnished Property Forms, Section J – Exhibit/Attachments, Attachment (F).
3.2 Security
3.2.1 Citizenship Requirements: Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:
(1) The individual's name, date, and place of birth, position title, and current citizenship.
(2) A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.
(3) A statement of the unusual expertise possessed by the applicant.
(4) A statement that access will be limited to a specific Government contract (specify contract number).
(5) A statement that the Contractor has obtained an export license for the information required to perform the contract.
3.2.2 Investigative Requirements: 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 all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract. Personnel must be able to obtain DoD and DHS clearances as detailed by the table below.
3.2.3 Security Clearance Information:
| Labor Category |
| DoD Security Clearance Level |
| Required Days After Award |
| Computer Engineer, Junior |
| Secret (1) |
| 30 |
| Computer Engineer, Journeyman |
| Secret (All) |
| 30 |
| Computer Engineer, Senior |
| Secret (All) |
| 30 |
| Computer Programmer III |
| Secret (1) |
| 30 |
| Electrical and Electronic Engineering Technician (Electronics Technician Maintenance II) |
| Secret (All) |
| 30 |
| Electrical and Electronic Engineering Technician (Electronics Technician Maintenance III) |
| Secret (All) |
| 30 |
| Electrical Engineer, Junior |
| Secret (1) |
| 30 |
| Electrical Engineer, Journeyman |
| Secret (All) |
| 30 |
| Electrical Engineer, Senior |
| Secret (All) |
| 30 |
| Engineer (Systems Engineer), Journeyman |
| Secret (1) |
| 30 |
| Engineer (Systems Engineer), Senior |
| Secret (2) |
| 30 |
| Engineering Technician II |
| Secret (1) |
| 30 |
| Engineering Technician III |
| Secret (1) |
| 30 |
| Engineering Technician IV |
| Secret (All) |
| 30 |
| Logistician, Journeyman |
| Secret (All) |
| 30 |
| Logistician, Senior |
| Secret (All) |
| 30 |
| Management Analyst (Systems Analyst), Journeyman |
| Secret (All) |
| 30 |
| Management Analyst (Systems Analyst), Senior |
| Secret (2) |
| 30 |
| Manager (Project Manager), Senior |
| Secret (All) |
| 30 |
| Manager (Program Manager), Senior |
| Secret (All) |
| 30 |
| Mechanical Engineer, Junior |
| Secret (1) |
| 30 |
| Mechanical Engineer, Journeyman |
| Secret (All) |
| 30 |
| Mechanical Engineer, Senior |
| Secret (All) |
| 30 |
3.2.4 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N).
3.2.4.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 OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty days of their first day of work. Instructions for processing the SAAR-N forms are available at: http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf. SAAR-N forms shall be submitted to the COR, Government Technical Point of Contact (TPOC), or to the assigned Government Trusted Associate Sponsorship System (TASS) Trusted Associate. (CDRL A024)
3.2.4.2 Command 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 and shall conform to all applicable regulations concerning their use and possession. ID media is U.S. Government property and shall be surrendered to the Pass and ID Office upon expiration or termination of employment. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site in accordance with Naval Air Station, Patuxent River (NASPAXRIV) Instruction 5510.15, Regulations Governing Admission to, NASPAXRIV Webster Field, and Navy Recreation Center Solomons following completion of the contract, relocation or termination of an employee, or upon request from the COR. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract.
3.2.4.3 DD-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”. Distribution is authorized to the Requiring Office’s (RO’s) Organization and supported activity only. Other requests for deliverables under this contract shall be referred to the COR of this contract for approval.
3.2.5 Information Security: If the work is performed at the Contractor’s facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with DoD 5220.22-M and SECNAV M-5510.36.
3.2.5.1 Marking: All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance.
3.2.5.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 Government authority. Proposed public releases shall be submitted for approval prior to release through the SAIW Division.
3.2.5.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, TPOC and Government Security Office within 24 hours of the incident occurring.
3.2.6 Operations Security (OPSEC): The Contractor shall comply with activity OPSEC program instructions, guidance and contribute to organization-level OPSEC efforts. The Contractor will include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The Contractor will protect identified critical information, sensitive unclassified information and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed by the RO and Contractor in support of the mission.
While performing on board NAVAIR or NAVAIR sites, the Contractor shall comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts. Include OPSEC as part of its ongoing security awareness program and take all required Agency training. Be responsive to the Supporting OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the RO and Contractor in support of the mission.
The Contractor shall prepare and deliver an OPSEC Plan for Government review upon award. (CDRL A025)
3.2.7 Anti-Terrorism Force Protection and Emergency Management: The work performed on this contract is not Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. 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 following subparagraphs describe the engineering services, production support, and training support to be accomplished under the contract. The Contractor shall not perform any inherently governmental functions as defined in FAR 2.101.
3.3.1 Engineering Services (CLINs 0001, 0011, 0021, 0031, 0041, 0051, 0055, 0059, 0063)
The Contractor shall provide support services to the Government in the following: engineering analysis, technical documentation review and production, system assessment, and technical services to analyze, evaluate, and produce design change documentation and proposals for system upgrades to the ship class RCS. All drawings and technical documentation from the previous RCS will be provided by the SAIW Division as GFI.
3.3.1.1 Systems Engineering: The Contractor shall provide engineering and technical support services to produce and upgrade the ship class RCS design including but not limited to:
Review the analysis documentation for the previous RCS. This documentation contains all of the technical documentation to fully define the RCS, including; Cable Block Diagrams, Cable Running and Routing Sheets, Space Arrangement Drawings, Equipment Technical Manuals, equipment Outline and Installation Drawings.
Within the Turnkey Process, the Navy has reserved Not-to-Exceed (NTE) Equipment Envelopes on the ship (ref. the Turnkey Management Plan). Equipment Envelopes are the physical and functional specifications of equipment which cannot be exceeded. These include, but are not limited to:
· Size of equipment (height, width, and depth)
· Weight
· Amount of power consumed and heat produced
· Maintenance and operation access
Equipment Envelopes details will be provided by the SAIW Division to the Contractor. The Contractor shall provide support services under this tasking including but not limited to:
Review individual system and equipment changes from the previous RCS.
Research and evaluate equipment parametric data and compare to the established NTE envelopes. (CDRL A003)
Determine if new sub-systems or equipment will remain within the NTE envelopes parameters. Assist in developing impact assessments for sub-systems or equipment that do not remain within the NTE envelopes. (CDRL A003)
The Contractor shall review and provide comments on the phased GFI delivery schedule. Determine the impact of new equipment and systems on the phased GFI and submit review comments. (CDRL A001)
The Contractor shall analyze and assess an Automated Test Equipment (ATE) Stage 2 test capability for RCS equipment and implement new technology to improve testing of the RCS and associated equipment. Assist in producing ATE Stage 2 test procedures. Stage 2 testing defined in NAVSEA T9050-AA-DIR-010/AEGIS, Rev. G. or current version, as Installation and Inspection Tests. (CDRLs A002, A008)
The Contractor shall review the feasibility of proposed design changes to the RCS. Determine extent of impacts for these proposed changes, including impacts to NTE design parameters.
The Contractor shall conduct operational impact analyses of proposed design changes. Analysis should include, but is not limited to, radio circuit quantities, types and setups, operator positioning, and equipment ergonomics. (CDRL A003) The Contractor shall conduct research on ship specifications to validate proposed changes will meet specifications. Produce reports documenting this research, to include impact assessments and recommendations. (CDRL A003) The Contractor shall perform the systems engineering necessary to implement directed changes to the RCS. Research the requirement; evaluate the availability of sufficient data to complete design; participate in Government led technical reviews; conduct NTE budget study to ensure parametric values are not exceeded; produce system design packages, reports, and recommendations as a result of these analyses. (CDRL A003) The Contractor shall analyze and assess potential applications of emerging technologies to the RCS. Identify the suitability of commercial-off-the-shelf (COTS)/non-developmental-item (NDI) equipment to satisfy RCS functional requirements. (CDRL A003) The Contractor shall evaluate deficiencies, including environmental considerations of COTS/NDI equipment candidates and propose resolutions. (CDRL A003) The Contractor shall conduct performance testing of COTS/NDI equipment to evaluate its compliance with performance specifications and to assess its interoperability within the RCS. (CDRL A003) The Contractor shall attend conferences and meetings to exchange programmatic information related to the RCS. Provide meeting/conference minutes and respond to action items. (CDRL A004) The Contractor shall produce a Quarterly Consolidated Engineering Services Report detailing engineering tasking accomplishments during the period. (CDRL A005) The Contractor shall assist in producing baseline equipment documents of RCS configurations. Typical data included in documents would be equipment nomenclatures and variants, software and firmware versions, and physical layouts. (CDRL A001) The Contractor shall assist in producing technical data inputs defining RCS changes that will be utilized for the submission of RCS design changes to PEO Ships or, as appropriate, other PEOs. (CDRL A001) The Contractor shall analyze and assess available software used for automated testing (i.e., Automated Cable Tester, Computer Controlled Equipment Testing (CCET), Stage 2 ATE, etc.). (CDRL A003)
1. The Contractor shall assist in delivering new, or revising available, software used for automated testing (i.e. Automated Cable Tester, CCET, Stage 2 ATE, etc.). (CDRL A015) The Contractor shall conduct 2-dimensional and 3-dimensional software modeling of the RCS. Modeling will include the RCS compartment as well as individual equipment located within the RCS. (CDRL A006) The Contractor shall utilize the models generated in paragraph 3.3.1.1.18 to analyze the RCS for space optimization and ergonomics.
The Contractor shall assess existing and new software applications to automate system design (e.g. cable routing optimization, antenna coupling, antenna range prediction). Produce reports documenting this assessment and recommendations. (CDRL A003) The Contractor shall utilize software applications identified in paragraph 3.3.1.1.20 to optimize utilization in system design.
The Contractor shall prepare technical briefs and presentations to support program reviews conducted by the Government. These reviews typically occur every two months and cover the current status of all aspects of the Engineering effort. (A018)
3.3.1.2 RCS Technical Data and Documentation: The Contractor shall provide technical and support services for the review and production of technical data and documentation required to define the RCS. This data and documentation will be utilized by the shipbuilders to prepare the ship for installation of the RCS. The Contractor shall provide support services in the following tasks including but not limited to:
The Contractor shall prepare 3-D room arrangement drawings depicting the RCS equipment and equipment cabinets, and annotate to reflect parametric values such as size, weight, center-of-gravity, and cooling requirements. (CDRL A006) The Contractor shall research detailed electrical/mechanical Installation Requirement Drawings (IRDs) defining equipment and equipment cabinets within the RCS, and assist in production of the IRDs. (CDRL A006) The Contractor shall review IRDs for Program of Record (PoR) systems within the RCS to determine impacts to overall RCS design. (CDRL A001) The Contractor shall assist in developing Outline and Installation Drawings for freestanding equipment or cabinets for which no IRDs are available. (CDRL A006) The Contractor shall assist in producing and reviewing the drawings to be delivered to the shipbuilder to prepare the ship and install the system on the ship. These drawings shall be provided to the shipbuilders based on the Phased GFI delivery schedule. This delivery schedule shall be provided when approved. A Preliminary and Final version of each drawing shall be produced and delivered. A list of deltas between the Preliminary and Final version of each drawing shall be produced. A typical list of drawings required to define the RCS includes but is not limited to:
· Preliminary/Final Outline and Mounting of Method Mounted Equipment Drawings
· Preliminary/Final Cabinet Foundation Outline and Mounting Drawings
· Preliminary/Final 60/400 Hz One-Line Power Diagrams
· Preliminary/Final System Main Cable Routing Sheets
· Preliminary/Final Installation Aid Fixtures (IAF) Backplane Drawings
· Preliminary/Final Intra-Compartment/Inter-Cabinet Cable Running Sheets
· Preliminary/Final Intra-Compartment/Intra-Cabinet Cable Block Diagrams
· Preliminary/Final Space Arrangement Drawings
(CDRL A006)
The Contractor shall assist in producing and reviewing the RCS contractual drawings to depict the design of the RCS that reaches outside the Radio compartment on the ship. Assess and produce new versions of these drawings by incorporating approved design changes directed via the Configuration Control Baseline Implementation Letter (CCBL). The CCBL implementation will occur twice a year. A typical list of these drawings includes but is not limited to:
· Inter-Compartment Cable Block Diagram
· Topside Antenna and Equipment Arrangements Drawings
(CDRL A006)
The Contractor shall assist in producing a Government accessible database of all RCS technical data and GFI, including drawings, technical manuals, test procedures and other technical documentation for use by program participants. Data and documentation will be stored in electronic format. (CDRL A015) The Contractor shall assist in developing a list of all RCS equipment that does not have a standard Navy technical manual. (CDRL A001) The Contractor shall use the list developed in 3.3.1.2.9 to research, develop, and/or revise technical manuals for all equipment used in the RCS that have not been documented as Navy standard.
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.