Attachment_1_-_CSIS_-_SOW_DC.docx

Attachment (1)

SECTION C – STATEMENT OF WORK

COMMUNICATION SYSTEMS INTEGRATION SUPPORT (CSIS)

1 BACKGROUND & SCOPE:

In support of tasking from the Program Executive Office for Ships (PEO Ships), NAVSEA, NAVAIR, PEO C4I, and other federal agencies, the Naval Air Warfare Center Aircraft Division (NAWCAD) 4.11.3 Division (also known as Integrated Communications and Information Systems) is tasked to design, procure, integrate, test, train, deliver, and support Command, Control, Communication, and Computer (C4) systems, information systems, computer systems, and sensor systems for various platforms, including ships, Unmanned Aerial Systems (UAS), and shore installations.

ICIS Division is the lead capability integrator and product manager for the integration, test, production, and support of systems involved with this effort. The contractor shall support ICIS Division tasks under this contract. This includes local integration support, advanced research and development support, engineering and technical support, quality management support, and technical management support of final end item products supporting the Program Executive Office for Ships (PEO Ships), NAVSEA, NAVAIR, PEO C4I, and other federal agencies, in C4 programs consistent with the scope of this contract. The scope of the contract can include rapidly developed engineering designs and systems integration for end products intended for immediate war fighter use, and may include strategic and tactical airborne, land-based, and mobile, sea-based surface and sub-surface platforms. The following are representative of the programs, systems, and technology areas to which the requested engineering and technical services may be applied:

(a) Military and commercial radio communication systems

(b) Information and computer network systems

(c) Command and control systems

(d) Unmanned Aerial Systems

2 APPLICABLE DOCUMENTS:

The following documents and document sources are provided for reference, the most current version is to be used at the time of award. Requirements for ICIS Division products to have interoperability among military, civilian, U.S., and foreign users may dictate an adherence to a variety of specifications and standards. DoD systems adhere to Joint Technical Architecture (JTA) Standards (Current Version). Non-DoD systems may be governed by numerous commercial, national, or international standards. The standard development organizations listed are not all-inclusive and are presented only as representative sources of the technological interface details which may be required for systems integration under this contract.

The following documents form a part of this specification to the extent specified herein. Unless otherwise noted, the revision level and date for each document, specification or standard cited within this solicitation/contract (including any specifications or standards cited in any drawing, handbook, or referenced specification or standard cited within this solicitation) shall be that listed in the Department of Defense ASSIST Database (http://assist.daps.dla.mil/quicksearch/) in effect on the date of contract award.

Standards, Specifications, Instructions, and Developmental Organizations:

(a) DOD and/or Military, (e.g., DoD-STD and MIL-STD Series)

(b) Joint Technical Architecture (JTA)

(c) American National Standards Institute (ANSI)

(d) Society of Mechanical Engineering (ASME) Standards

(e) Association of Public-Safety Communications Officials – International (APCO) – Standards

(f) Electronic Components Industry Association (ECIA), (e.g. Recommended Standards RS Series)

(g) European Telecommunications Standards Institute (ETSI)

(h) Federal, (e.g. FED-STD, FIP Series)

(i) Federal Communications Commission (FCC)

(j) Institute of Electrical and Electronic Engineers (IEEE)

(k) International Standards Organization (ISO)

(l) International Telecommunications Satellite Organization (ITSO)

(m) International Telecommunications Union (ITU), formerly the CCITT

(n) National Institutes of Standards and Technology (NIST)

(o) Telecommunications Industry Association (TIA)

(p) DOD Standard Practice for System Safety (MIL-STD-882E, May 2012)

(q) Technical Data Packages (TDP) Option Selection Worksheet Product Drawings and Associated Lists (MIL-DTL-31000C, November 2009)

(r) NAVSEA Source Approval Request (SAR) for Ships’ Critical Safety Items

Instructions and Directives

NAVAL SYSTEMS ENGINEERING GUIDE, October 2004

Note: This standard establishes the requirements and reference documents applicable to the preparation and revision of engineering drawings and associated lists. In general terms of addressing the subject area of engineering drawing practices, this standard should be used in close conjunction with ASME Y14.24M, ASME Y14.34M, and ASME Y14.35M.

3 TECHNICAL REQUIREMENTS

Due to the nature of this effort, the Government has broken this Statement of Work (SOW) into two distinctive work areas. The first area of Engineering and Logistics covers all aspects of the Systems Engineering model from R&D, requirements definition, design, drawing package support, and engineering testing, to software engineering. Logistics as part of the C4 systems covers hardware configuration, technical manuals, procedures, and life cycle management process. These work areas are being solicited as IDIQ level of effort type work scopes (either CPFF or FFP) with a labor hour breakout by functional skill set or category provided elsewhere in the solicitation.

The second SOW area covers the anticipated Integration efforts under this solicitation. The Integration scope covers supporting the Governments lead for the buildup of systems from test bed set up, cable fabrication, equipment rack integration, cable run compliance through system check out, breakdown, delivery, to testing. This Integration effort is contemplated to be executed in a CPFF metric Performance Based environment or via a FFP order while ensuring compliance with the quality intent of ICIS’s ISO9001 certified processes. Metric standards are provided in the Integration section of this SOW and will be used to evaluate contractor’s performance during the evaluation process in CPARs and through the hybrid contract Quality Assurance Surveillance Plan (QASP).

Notwithstanding any interpretations to the contrary, the language in the following SOW sections is to emphasize that the role of the contractor under this effort is to support NAWCAD 4.11.3’s lead in the engineering, logistics and integration aspects of this effort.

ENGINEERING & LOGISTICS – STATEMENT OF WORK AREAS

(CPFF LOE & FFP LOE)

Supporting the C4 mission objectives of NAWCAD’s 4.11.3 Division, the contractor in a support role to the government lead shall provide the engineering and technical support services using various engineering methodologies necessary to assist the Government in the design, integration, testing and life cycle support activities for C4 hardware and software components into systems and subsystems that satisfy sponsor and end-user operational and technical requirements. To accomplish this scope, the contractor may be required to provide skilled personnel and processes to support the following efforts:

ENGINEERING

3.1 Engineering Requirements Research

3.1.1 Provide engineering and technical support for the evaluation of current and emerging technologies in the C4 arena to support the current and future needs of ICIS’s Federal-based sponsors. Following the engineering models, the contractor shall provide support in the requirements definition phase of determining technical requirements, functionality of current and future C4 systems and offering “Best Value” solutions and options for consideration by the Government.

3.1.2 Conduct market research and assess potential applications of emerging technologies to alleviate noted deficiencies, equipment obsolescence, enhance performance of existing systems, or provide the needed functionality required in response to new and emerging operational missions and threats. (CDRL A004)

3.1.3 Research and evaluate Commercial Off-The-Shelf (COTS) equipment and new and emerging technologies to identify the potential to improve the operational performance of existing systems, and recommend system changes.

3.1.4 At the Government’s discretion, the contractor shall be required to support the development of a Systems Engineering Management Plan (SEMP) for projects/programs deemed to have sufficient complexity. The SEMP will encompass the project/program’s technical approach including processes, resources, metrics, applicable performance incentives, and the timing, conduct, and success criteria of technical reviews for tasking that includes system design or delivery. (CDRL A002)

3.2 Engineering Requirements Definition

3.2.1 Provide engineering and technical support for the development of execution plans, procedures, testing protocols and life cycle considerations necessary to evaluate the operational and technical parameters of proposed C4 integrated systems and subsystems. Both hardware and software may be included in this support area. This support shall cover both new C4 systems, as well as upgrades to existing systems. Provide recommendations and solutions to improve and enhance designated systems. (CDRL A004)

3.2.2 Research, design and develop mechanical interfaces, isolation systems, positive restraint systems, and hardware to facilitate equipment integration, testing, and delivery.

3.3 Engineering Design & Drawing Management

3.3.1 Support the Government’s engineering processes as they relate to design, development, fabrication, and integration of equipment, ancillary hardware, interface units, and test fixtures not available from other sources or not otherwise provided. This may include engineering reviews of printed circuit board design and manufacture processes, test cable design and manufacture concepts, platform specific mock-up design and manufacturing processes and engineering assessments of metalwork design and manufacturing procedures. Assist in the development of engineering reports or installation drawings, procurement drawings, and technical documentation for such items. (CDRLs A003, A006)

3.3.2 Develop, review, and revise engineering drawings, as-built drawings, cable running sheets, and other related documentation to reflect approved system design and consistency with interfaces. The contractor shall provide technical and engineering support for the development, acquisition, validation, and correction of technical data and technical documentation required for the detailed design, modernization, integration, installation, operation, and maintenance of the upgraded systems. Drawings, data, and documents will be made available as Government Furnished Information (GFI) to the installer, operator and/or maintainer of the system. New or revised engineering drawings shall be provided in a format (AutoCAD, CV CADD, or ASCII format) which is compatible with the Initial Graphics Exchange Specification (IGES).

3.3.3 Support the research and development of detailed electrical/mechanical assembly and installation control drawing packages. (CDRLs A018, A019, A020)

3.3.4 Prepare individual equipment Outline and Installation Control Drawings for free-standing equipment with Government provided and approved Installation Requirement Document (IRD). (CDRL A003)

3.3.5 Verify, and report findings, that all GFI accurately reflects specified equipment configuration, and provides adequate information for integration, testing, and set-up of the equipment. (CDRL A004)

3.3.6 Support the continued verification and update of baseline and revised drawing documentation, as well as control drawings to reflect existing and projected configurations of systems, to include, but not limited to:

(a) Space arrangement drawings

(b) Cable block diagrams and cable run sheets

(c) Other associated engineering drawings, lists, and documentation. (CDRL A003, A018, A019, A020)

3.3.7 Develop, update, and maintain engineering guidance to include space arrangement drawings, elevation drawings, cable block diagrams, and cable run sheets to support the integration of systems and upgrades. The guidance shall identify all significant technical details necessary to properly integrate and install the subject equipment or system. (CDRL A004)

3.3.8 Review the drawings and technical documentation of interfacing systems to ensure compatibility with integrated system interfaces on legacy, current, and future systems. (CDRLs A004)

3.4 Engineering Configuration Control

3.4.1 Research and develop technical support for system configuration-control processes, including the development, revision, and updating of configuration-control documentation upon approval of the Government. Configuration management/control activities shall be applied to systems hardware, software, and associated technical documentation. (CDRLs A012, A013, A014)

3.4.2 Utilizing engineering configuration control processes, provide research and evaluate the operational performance and effectiveness of integrated systems. Provide recommendations for engineering, maintenance, or logistics changes required to correct or mitigate identified deficiencies. (CDRL A004)

3.4.3 Apply Government approved configuration control processes throughout the integration effort to identify changes to C4 cabinet installation, design, and interoperability (e.g., cables, connectors, backshells, and interconnections) necessary to ensure control of system integration. (CDRLs A023)

3.4.4 Provide configuration management efforts to identify, control, and account for the functional and physical characteristics of designated items, and maintain configuration control documents. This may include participating in configuration control boards (CCB) and maintaining documentation and tracking of CCB decisions. (CDRLs A014)

3.4.5 Revise existing Government manuals or develop inputs for new manuals as necessary. Manuals shall be prepared in accordance with current applicable Government specifications, and may include Interactive Electronic Technical Manuals (IETMs) and will be subject to Government review and approval. (CDRLs A011)

3.5 Engineering Testing Requirements

3.5.1 Conduct testing to ensure correct operation, compatibility with existing subsystems and equipment, and suitability for integration into the specified communications or information systems.

3.5.2 Coordinate and conduct pre-integration special testing, such as shock, vibration, Electromagnetic Interference (EMI), isolation and radiation hazards, and susceptibility to electronic countermeasures. (CDRL A021)

3.5.3 Conduct data collection and test result analyses, and report findings. (CDRL A008, A009, A010)

3.5.4 Identify and document discrepancies, actions taken to resolve discrepancies, and provide feedback to engineering or production personnel. Testing may include testing new equipment or designs for compatibility with legacy equipment/systems. (CDRLs A021)

3.5.5 Test and evaluate systems at facilities at NAVAIR Webster Field and Naval Air Station Patuxent River to provide an independent test and evaluation capability. The contractor shall support these efforts using laboratory capabilities which include facilities to assess:

(a) all types of Information Technology hardware and equipment

(b) Communications Security (COMSEC) devices

(c) environmental standards

3.5.6 Accomplish tests and inspections using the contractor's documented quality assurance process as outlined in the contractor's Quality Management Plan (QMP). (CDRL A016))

3.6 Engineering Change Management

3.6.1 Recommend modifications and corrective action to system hardware and software to correct design deficiencies discovered during design, integration, testing, delivery, and set up. (CDRL A004)

3.6.2 Collaborate with Government personnel to define the scope, requirements, risks and format of assigned products. (CDRLs A004, A014)

3.6.3 Support the collaboration of Government personnel and other stakeholders to research and develop the Detailed Project Schedules and Integrated Master Schedule for integration efforts, to include procurement, refurbishment, build-up, integration, testing, delivery and set-up. (CDRL A005, A022, A029)

3.6.4 Track planned versus actual expenditures to determine funding status as it relates to the approved budget, and support Earned Value Management (EVM) methods. (CDRL A022, A029)

3.6.5 Track and analyze actual progress versus planned progress for cost and schedule performance, and provide monthly status reports to NAWCAD. Report shall identify risks and shortfalls, and include plans for mitigation. (CDRL A001, A024)

3.6.6 Support internal and external working-level technical conferences and status meetings and provide minutes or report of formal and/or informal meetings as required. Provide representation and/or briefing materials to support meetings with peer groups or industry organizations such as Integrated Process Team (IPT) meetings, configuration control boards, other participating project entities, standards committees or commercial forums. (CDRLs A014)

3.6.7 Prepare training materials and conduct training on integrated systems. Training shall focus on operation of the integrated systems or sub-system and on unique subject matter not covered in military technical schools. Training materials shall include:

(a) Lesson Plan

(b) Instructor’s Guide

(c) Student Guides

(d) Presentation Material

(e) Block Diagrams

(f) Training Report

(g) Other material necessary to meet the training requirements by system

(CDRL A015)

3.7 Engineering Software Support

3.7.1 In support of the various C4 systems, the contractor shall provide required software support that will link the engineering, integration and logistic efforts to ensure the functionality of the system or subsystem.

3.7.2 Research, design and develop test software and procedures for automated testing, i.e., Automated Test Equipment (ATE), and Computer Controlled Equipment Testing (CCET), etc. (CDRL A004)

3.7.3 Research, develop, and update software applications to automate system design, i.e., cable routing optimization, antenna coupling, and range prediction. (CDRL A004)

3.7.4 Conduct software modeling to include 2-D/3-D visualization of system spaces, equipment modeling, space optimization, human engineering analysis support, and maintenance access studies support. (CDRL A004)

Integrated Logistics Support

3.8 Integrated Logistics Support

In executing ICIS’s C4 mission of designing, procuring, integrating, testing up to and including the after delivery support of the equipment systems developed; there is a need to establish a logistic function that will support the equipment lifecycle. In a Level-of-Effort approach the necessary personnel resources will be required to support the government’s efforts in ensuring updated manuals and training materials, parts control lists, drawing specifications, calibration specifications and other processes to ensure the equipment and overall system functions as designed. This effort can include supporting the end users in maintaining the operational effectiveness of the various C4 systems that are delivered under this contract. The contractor’s support can include the following areas:

3.8.1 Supporting the existing government library and automated database documenting all system technical data and Government Furnished Information (GFI), including drawings, technical manuals, test procedures and other technical documentation for use by program participants.

3.8.2 Providing logistical and technical support for the systems physical and software configuration audits, and validate physical configurations and that they remain valid with technical documentation used for maintenance and training purposes.

3.8.3 Providing technical and management support services to develop and maintain logistics planning and documentation support for non-Program of Record (POR) NAWCAD procured equipment and systems.

3.8.4 Logistic support to identify equipment requirements for integration, procurement of material, track acquisition status and equipment disposition, and report such provisioning actions. Contractor shall also be accountable for inspecting equipment upon receipt, testing, integration, and storage and control and delivery of material. (CDRL A004)

3.8.5 Provide for the scheduling and periodic calibration of general purpose and special purpose tools and electronic test equipment. Submit periodic reports of calibration activities for Government action and approval. (CDRL A004)

3.8.6 Identify material and equipment quantity and schedule requirements, including requirements for spare parts support at NAWCAD. Support planning and maintain reports for the procurement of all long lead items required to integrate, upgrade, modernize, repair, and maintain existing systems. (CDRL A004)

3.8.7 Procure materials IAW relevant contract clauses as required that are incidental to the services provided under the contract.

3.8.8 Support the research, development and maintenance of equipment via the Integrate Logistics Support (ILS) planning and management documentation including Integrated Logistics Support Plans (ILSPs), Equipment Logistics Data Sheets and Allowance Parts Lists (APLs) for each non-POR NAWCAD procured equipment.

3.8.9 Research and support development and maintenance of the maintenance planning requirement documentation. Prepare Planned Maintenance System (PMS) packages including Maintenance Requirements Cards (MRCs) and Maintenance Index Pages (MIPs) for Government approval on all NAWCAD procured equipment. (CDRL A025)

3.8.10 Support the research, development, and maintenance of Program Support Data (PSD) for NAWCAD procured equipment using the Parts Automated Reporting Tracking System.

3.8.11 Coordinate logistics support for NAWCAD procured equipment with the Navy Inventory Control Point and the Naval Sea Logistics Center.

3.8.12 Provide management oversight support for the Material Support Dates.

3.8.13 Support the Provisioning Technical Documentation to Navy Inventory Control Point and Naval Sea Logistics Center in Interactive Computer-Aided Provisioning System format.

3.8.14 Attend conferences and meetings to exchange technical information and propose the resolution of problems related to ILS. Provide meeting/conference minutes and respond to action items. (CDRL A014)

3.8.15 Assist in the research, development and documentation of an Interim Repair Parts requirements for NAWCAD procured equipment. (CDRL A004)

INTEGRATION – STATEMENT OF WORK AREAS

(CPFF Performance Based & FFP)

3.9 Integration of C4 Systems

The integration process within ICIS has been established and refined over many years, to a level that allows the Government the ability to expect this work to be performed in a CPFF Performance Based acquisition or in a Firm Fixed Price (FPP) environment with metrics and clear objectives once an engineering drawing package is approved and ready for build out. Despite not knowing the exact type of C4 system that may be supported, there exists enough performance metrics on the cabinet/rack types, cable configurations and equipment needs that allows the Government to expect and for the contractor to execute the various Integration CLINs/Sub-CLINs in a metric performance based or in FFP type orders. In support of the integration section of this SOW, the intent is for the contractor to be able to perform within the following parameters:

It is expected that the Contractor shall integrate a minimum of two and a maximum of seven UHF/VHF and/or HF systems per calendar year, with each system generally consisting of 7-10 racks of C4 Equipment, 285-410 components and 500-850 fabricated data/control, power, and RF cables per system. Each system shall be delivered to various CONUS or OCONUS locations upon completion of acceptance testing. Contractor shall deliver a summary report for each integrated system (CDRL A033). The Contractor will also deliver the test reports/results for each integrated system (CDRL A034).

The determination of CPFF Performance Based or FFP order will be decided when the delivery order SOW is defined.

3.9.1 The contractor shall support integration efforts and production planning, including:

(a) Utilizing drawing packages, the contractor shall develop production schedules for the various equipment suites/cabinets/racks utilizing Microsoft Project. The schedules shall be in enough detail to support EVM, and the tracking of work elements to a WBS level as the drawings and customer may require. It is expected that the contractor will have 10 business days to complete the first draft after task assignment. Final version will be due 5 business days after Government issued comments. (CDRL A029)

(b) The contractor shall coordinate the availability of needed integration required resources such as man-power, material, travel, software and facilities (if needed). This Resource Loading Report will be provided within 10 business days after task assignment. (CDRL A004)

(c) Within 10 days after task assignment, the contractor shall develop, apply and submit to the Government for approval a performance work process with instructions as appropriate for the execution of the integration steps. Utilizing the Government metric standards, the contractor shall develop specific performance metrics governing the integration work steps, receipt of material and present how it will comply with the contractor’s quality plan, as well as the Government’s ISO 9000 standards. (CDRLs A005).

Performance standards will be agreed to as individual work complexities may require, but as an integration benchmark, the contractor will be expected to meet, or be comparable to, the following cabinet integration metrics/performance standards:

Total Man-hours to Integrate (Eng. Tech or Electronics Tech.)

Materials list:

Cables per cabinet

Main equipment per cabinet

Components per cabinet

Timeline for completed and accepted cabinets

Notes

In the above metric standards, the Government recognizes that these standards have been developed over time using numerous projects. There is also recognition that sponsor requirement changes, technology refresh, SCA Wage Determination revisions and parts availability (among other events) will all impact the final outcome. It is the Government’s intent to apply a plus or minus 5% to the above numbers in the evaluation process for CPFF completion orders after having an open discussion with the contractor on the results outside this established metric range. The drawing packages for these identified C4 cabinets are available for review. For FPP orders, the Government recognizes that the risk will shift to the contractor and understands that Delivery Order pricing will reflect that fact.

3.9.2 Utilizing the metrics established above, the contractor shall provide technical support for the integration of subsystems, components, and equipment that will be incorporated into larger C4 systems. System integration includes:

(a) integrating platform-specific cabinets/racks

(b) developing and integrating required cables and connectors

(c) integrating equipment to equipment platform-specific cables

(d) procuring required material

(e) integrating associated software

(f) implementing quality/verification approaches to ensure the integrated system meets design specifications and requirements consistent with the approved QMP and the metrics noted above.

(g) supporting overall management of integration efforts, from planning to final delivery and set-up.

3.9.3 The contractor shall resolve problems during system integration, testing, delivery, and set up, and prepare change requests as required. Once properly documented by the Government to a needed change or correction, the contractor shall have 72 hours in which to initiate corrective measures. The contractor shall pursue this correction with all due diligence until satisfied and corrected. (CDRLs A004, A005, A029)

3.9.4 The contractor shall provide reports detailing all technical information relative to discrepancies associated with the integration or testing of any electrical, mechanical, or Information Technology equipment, group, or system. (CDRL A017)

3.9.5 The contractor shall fabricate or procure metalwork and woodwork items, to include:

(a) equipment cabinets, racks, and cases

(b) platform-specific jigs, mock-ups, and installation aids

(c) shipping containers

The Government is expecting a timeline metric of 100% on all deliverable submissions. On all other SOW areas, the Government is expecting a minimum quality standard of 95% accuracy on written and verbal inputs.

4 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 of specific DOs to be issued under this contract. The quality management system shall meet the intent of the American National Standards Institute/American Society for Quality ANSI/ASQ ISO 9001:2008, and/or equivalent governing body. Regardless of the standards that are applied, the contractor’s quality approach shall be clearly defined and recognize the need to focus on customer satisfaction, defect prevention over inspection, management responsibility and continuous improvement. (CDRL A016)

4.1 Inspection System Plan (ISP)

The contractor shall submit an Inspection System Plan (ISP) for approval not later than 15 days after contract and first DO award. The ISP may include generic contractor procedures, for the level of effort CLINs, however for the CPFF Performance Based Completion and Fixed Price Integration effort, the ISP shall be specific regarding the work requirements stated in the SOW. (CDRL A030)

4.2 Planning Review

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.

4.3 Quality Management Plan

A draft copy of the contractor’s Quality Management Plan, as approved by the contractor’s management and that demonstrates conformance to the selected quality standard, shall be submitted as an addendum to the Technical Volume as required in Section L of the solicitation. The contractor’s Quality Management Plan shall address all areas of work to be performed under the contract resulting from this solicitation to include hardware and software systems engineering, integration and installation, configuration management, logistics and contractor’s method for monitoring and reporting on the identified integration metrics. As with the ISP, the Government for the Performance based CLINs is expecting a level of detail that indicates the contractor grasps the Integration scope and the metrics that will be used to evaluate performance. The contractor will be required to provide a final version of this plan after award. (CDRL A016)

4.4 Process Documentation

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 A005)

5 FACILITIES

5.1 Contractor-Provided Industrial Facility

5.1.1 The contractor shall fully staff and operate an industrial space to support the receipt, storage, inventory, and shipment of equipment associated with assigned projects. Minimum industrial space size is 6,000 sq. ft. The space shall be configured to provide distinct and securable areas for receiving, material receipt inspection, storage awaiting buildup, integration and testing, and storage of completed systems. 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 facility shall be protected by burglar and fire alarms, and a fire protection system. The contractor shall furnish and equip the facility to occupancy status and shall provide all equipment and material required for use in the facility. Recognizing the phase-in staffing requirements of this solicitation, consideration of a “flexible” facility plan could serve as advantageous to both the contractor and Government.

5.1.2 The contractor is responsible for determining the size of the contractor’s facility for engineering and office space that is needed to house the staffing levels and the staffing timing required by this solicitation and the contractor’s proposal. All facilities must meet the standards for access prescribed by the Americans with Disabilities Act of 1995. The geographic location of the contractor’s primary facility shall be within a 45 mile driving distance to NAWCAD, St. Inigoes, MD.

5.1.3 The contractor shall provide and maintain the capability to transport C4 Systems related equipment and incidental material between the contractor’s local facilities 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. This will be a directly chargeable item on a delivery order and is included within the solicitation-mandated Other Direct Cost amount.

5.2 Government-Provided Integration and Production Facilities

5.2.1 The Government’s intent is to support as much of the integration efforts that can be done in the Government’s spaces. Therefore, initially it will provide integration and production facilities and limited office space located on the NAWCAD Webster Field Annex. The integration and production facilities are occupied by Government and contractor personnel currently performing system integration and production services and contain offices, shop areas, a CMS vault, loading docks, a receiving/staging area, and test beds. The successful offeror responding to this solicitation shall share the shop and receiving/staging areas with existing contractors as required. Integration space shall be allocated based on specific tasking, but as an initial estimate and for proposal purposes the contractor shall estimate 15 full time positions will be on base in the Government integration facility with another 5 positions being provided office space on base (a total 20 positions on Government site). The rema`inder of the positions shall be assumed and proposed as if they are located in contractor facilities. Individuals located on site at the Government location must provide their own computers, software, supplies, desks, chairs, tools, etc. The Government will provide access to copiers, internet service and limited phone support.

Note: It is not mandatory that the contractor bid, nor imply that they have facilities to cover the full solicitation staffing on day of award. The facilities plan should be flexible and correlate to the offeror’s staffing plan.

5.2.2 Contractors assigned to work in Government facilities shall be required to assist with end-of-day physical security checks, but will not be delegated the primary responsibility for such checks. The workspaces will normally be available from 0600 to 1800 Monday through Friday. Exceptions to these hours shall be coordinated with the COR.

6 IT CLAUSES

The Government will provide all necessary reference documents not generally available to the Contractor as required. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

The Contractor shall not purchase any Information Technology (IT) equipment on behalf of NAVAIR in support of this Contract without a Naval Air Systems Command (NAVAIR) Command Information Officer (CIO) signed "IT" approval.

It is the Government's responsibility to ensure that any IT procurement (hardware/hardware maintenance, software/software maintenance, support services, web services, telecommunications, etc.) procured by the Contractor under the scope of this Contract that contains IT meet the following requirements.

6.1 Information Assurance

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

All Information Assurance (IA) shall be in compliance with the following listed instructions to include those referenced within the below listing:

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

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

(c) CJCSI 6211.02C (series) – “Defense Information System Network (DISN): Policy and Responsibilities,” 9 July 2008

(d) CJCSI 6212.01E (series) – “Interoperability and Supportability of Information Technology and National Security Systems,”15 December 2008

(e) CJCSI 6250.01C (series) – “Satellite Communications,” 30 April 2007

(f) CJCSI 6510.01E, “Information Assurance (IA) and Computer Network Defense (CND),” 15 August 2007

(g) (Chairman of the Joint Chiefs of Staff Manual) CJCSM 6510.01A – “Information Assurance (IA) and Computer Network Defense (CND) Volume I (Incident Handling Program”, 24 June 2009

(h) [Chief of Naval Operations/Headquarters, United States Marine Corps] CNO N614/HQMC C4 – “Navy-Marine Corps Unclassified Trusted Network Protection (UTN-Protect) Policy, Version 1.0,” 31 October 2002

(i) Defense Acquisition Guidebook – Chapter 7 “Acquiring Information Technology, Including National Security Systems,”; Section 7.5 “Information Assurance (IA)”

(j) DoD 5220.22-M, “National Industrial Security Program Operating Manual,” February 28, 2006 (NISPOM)

(k) DoD 8570.01-M, “Information Assurance Workforce Improvement Program”, 19 Dec 2005 (Incorporating Change 2, Feb 25, 2010)

(l) DoDD 8000.01 “Management of the Department of Defense Information Enterprise,” February 10, 2009

(m) DoDD 8100.02, “Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current as of 23 April 2007

(n) DoDD 8500.01E (series), “Information Assurance (IA),” October 24, 2002, Certified Current as of April 23, 2007

(o) DoDD 8570.01 “Information Assurance Training, Certification, and Workforce Management,” August 15, 2004, Certified Current as of April 23, 2007

(p) DoDI 4630.8, “Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS),” June 30, 2004

(q) DoDI 8500.2, “Information Assurance Implementation,” February 6, 2003

(r) DoDI 8510.01, “DoD Information Assurance Certification and Accreditation Process (DIACAP),” November 28, 2007

(s) DoDI 8520.2, “Public Key Infrastructure (PKI) and Public Key (PK) Enabling, April 1, 2004

(t) DoDI 8551.1, “Ports, Protocols, and Services Management (PPSM),” August 13, 2004

(u) DoDI 8580.1, “Information Assurance in the Defense Acquisition System,” July 9, 2004

(v) DoDI 8581.01, “Information Assurance (IA) Policy for Space Systems Used by the Department of Defense,” June 8, 2010

(w) DON CIO Memo 02-10, “Department of the Navy Chief Information Officer Memorandum 02-10 Information Assurance Policy Update for Platform Information Technology,” 26 April 2010

(x) DON ltr 5239 NAVAIR 726/2322 of 18 Feb 09, “NAVAIR Data at Rest Policy”

(y) Federal Information Processing Standards Publications (FIPS PUB) [http://www.itl.nist.gov/fipspubs/by-num.htm]

(z) (National Security Telecommunications and Information Systems Security Policy) NSTISSP No. 11, “Revised Fact Sheet National Information Assurance Acquisition Policy,” July 2003

(aa) (Office of the Chief of Naval Operations) OPNAV INST 5239.1C, “Navy Information Assurance (IA) Program,” 20 Aug 08

(ab) SECNAV M-5239.1, “Department of the Navy Information Assurance Program; Information Assurance Manual,” November 2005

(ac) SECNAVINST 5230.15, “Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software,” 10 April 2009

(ad) SECNAVINST 5239.3B, “Department of the Navy Information Assurance Policy,” June 17, 2009

(ae) SECNAVINST 5239.19, “Department of the Navy Computer Network Incident Response and Reporting Requirements,” 18 March 2008

(af) The National Security Act of 1947

(ag) Title 40/Clinger-Cohen Act

For more information on determining the applicability of these documents to the specific requirements of your program, contact your local information assurance point of contact for assistance. An IA Manager is available via the NAVAIR portal at https://mynavair.navair.navy.mil/portal/server.pt/gateway/PTARGS_32_0_856_0_-1_47/http;/C27VMWARPAXR274.nadsusea.nads.navy.mil;11930/collab/do/document/overview?projID=135128&documentID=290394

6.2 Systems and Networks.

All IT procured on behalf of NAVAIR shall meet all DoD/DON and NAVAIR IA polices. Failure to follow these policies will result in denied access to NMCI, One Net, Integrated Shipboard Network System (ISNS) and other DON, DoD and Joint Networks. These IA policies are standard across the Department and ensure IA compatibility and interoperability. IT systems and or networks operated by contractors subsequent to a NAVAIR contract, regardless of the level of data processed shall be operated and in accordance with the NISPOM.

6.3 System Software / Application Compliance

All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly Business Management Modernization Program (BMMP)), Department of the Navy (DON)/Naval Air Systems Command (NAVAIR) Functional Area Manager (FAM) Policies and Guidance, Network and Server Registration, and Web Enablement mandates.

6.4 Web Sites, Web Enablement and Application / System Development, Modification, and Maintenance Support Services

All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and strategies, and should be integrated within the NAVAIR Enterprise portal and collaborative environment whenever possible. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure in accordance with Legacy Shutdown guidance. Policies include, but are not limited to:

(a) OMB Management of Federal Information Resources, OMB CIRCULAR NO. A-130 Revised http://www.whitehouse.gov/omb/circulars_a130_a130trans4

(b) OMB Policies for Federal Agency Public Websites, OMB M-05-04 http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-04.pdf

(c) Section 508, Rehabilitation Act of 1973 http://www.section508.gov/

(d) Department of Defense Web Policies and Guidelines http://www.defense.gov/webmasters

(e) Navy Information Operations Command (NIOC) Norfolk Web Risk Assessment Team Website https://www.nioc-norfolk.navy.mil/wra/index.html

(f) DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B http://www.doncio.navy.mil/PolicyView.aspx?ID=421

(g) NAVAIR CIO Website (NAVAIR specific policy and guidelines https://mynavair.navair.navy.mil/portal/server.pt/community/dcio_applications_integration___business_intelligence_%287_2_2%29/1491/web_enablement/57583

(h) DISA Hosting of All Navy Websites (NAVADMIN 061/08)http://www.npc.navy.mil/NR/rdonlyres/A4E463D0-02AF-4094-A054-BB1D807F631B/0/NAV08061.txt

(i) Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07 http://www.npc.navy.mil/NR/rdonlyres/787908B8-55E8-4A6F-9BD8-A74B3C0824F0/0/NAV07145.txt

(j) DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified Web Sites and Uniform Resource Locators http://www.doncio.navy.mil/PolicyView.aspx?ID=577

6.5 Software Development/Server Procurement

Any tools developed that will be hosted by the Navy Marine Corps Intranet (NMCI) or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.

6.6 Enterprise Architecture

6.6.1 Contractor Networks and Connections. Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non-government, external IP space via the NAVAIR-provided Virtual Private Network (VPN) Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

6.6.2 Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the NAVAIR Enterprise Architect (AIR-7.2.3) prior to build out.

6.6.3 Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.

6.6.4 IT Approval. The contractor shall not purchase any IT equipment on behalf of NAVAIR in support of a contract without a NAVAIR CIO signed IT approval.

6.7 Contractor Networks

Contractor-owned equipment shall be permitted connections to NAVAIR/DoD networks in order to carry out the performance of this contract. All Contractor-owned hardware and/or software shall meet DoDI 8500.2 IA Controls, is subject to validation scanning and must be approved by the NAVAIR site IA Manager prior to connection. The following specific criteria must be met before being connected to any DoD or NAVAIR network in support of this contract.

Requirements include:

(a) Network Vulnerability Scanning. NAVAIR Deputy CIO for Information Assurance maintains authorized auditing tools and shall provide for firewall/port scans, device discovery scan, vulnerability assessment, and other requirements as required to ensure secure interoperability with DoD Contracts. The contractor shall be responsible for the remediation of any equipment that fails these audits prior to the connection the system to the networks; Results of approvals shall be documented via Memorandum of Agreement with the Facility Security officer and the Defense Security Service Representative for that contractor;

(b) Extent of Validation Scanning. To prevent scanning of “corporate” assets, all such networks, equipment and connections shall be physically segregated from any government/contractor “corporate” networks that are not in direct support of DoD contracts;

(c) Circuit Provisioning. Any circuit or connection between NAVAIR…