Draft PWS for Sources Sought- 832268575.pdf

PERFORMANCE WORK STATEMENT (PWS)

as of 8 August 2022

Award/Mod Effective Version Date

Award

Contract Number: To Be Determined (TBD)

Task Order Number: Not Applicable (N/A)

Contractor Name TBD

Tracking Number: 832268575

Follow-on to Previous Contract and Task Order Number:

HC1028-18-D-0046

1. Contracting Officer’s Representative (COR)

a. Primary COR. See Points of Contact in Contract Administration Data

b. b. Alternate COR. See Points of Contact in Contract Administration Data

2. Contract Title

Outside the Continental United States (OCONUS) Information Technology (IT) Solutions II

3. Background

United States European Command (USEUCOM) and Naval Information Warfare Center (NIWC) Atlantic require engineering development, design, procurement, fabrication, configuration, integration, installation, logistics, maintenance, and life cycle support solutions for Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance/Information Technology (C4ISR), Information

Technology (IT), and Electronic Security System (ESS) systems. These systems will support USEUCOM initiatives to ensure Department of Defense Information Network (DoDIN) and cyberspace operations enable mission command of the USEUCOM Commanders Theater Campaign Plan (TCP), war plans, and orders.

4. Objectives

USEUCOM and NIWC Atlantic must be able to respond quickly and effectively in order to meet the operational requirements of USEUCOM and its subordinate commands in the rapidly changing environments across Europe and Southwest Asia. Cost effective and innovative system solutions are required to respond to routine, emergent, and evolving challenges of the warfighter in these regions. This contract integrates solutions with the objective of obtaining services to deliver an end product or a turnkey solution. This contract will be executed through the issuance of Task Orders (TO) that are determined to be within the scope and location of this contract. This contract will be executed with resources located near the USEUCOM Headquarters at Patch Barracks and in Stuttgart, Germany. The contractor may work primarily with or be required to obtain approved host nation Technical Expert Status Accreditation

(TESA) personnel for extended assignment.

4. Scope

The purpose of this contract is to provide streamlined delivery of IT solutions to the warfighter at shore installations in USEUCOM’s Area of Responsibility (AOR). The scope of this contract covers the entire spectrum of outcomes associated with the full lifecycle of delivery and support of IT capabilities. This

PWS covers requirements as it relates to IT experience with specific Commercial Off the Shelf (COTS) solutions and variations of project environments that range in risk and complexity based on size and other factors. This PWS encompasses project/program management, engineering, procurement, implementation, and testing requirements associated with the development, delivery of OCONUS IT solutions. Unless otherwise stated, all artifacts shall be developed in accordance with the Shore

Installation Process Handbook (SIPH).

4.1 Solutions.

The contractor shall provide the following turnkey solutions:

a. Inside/Outside Plant (ISP/OSP) Infrastructure

b. Active Infrastructure (AI)

c. Desktop Automated Information Systems (AIS)

d. Audio-Visual (AV)

e. Command Centers and Other Smart Facilities

f. Space Planning

g. Data Center

h. Cloud Computing

i. Knowledge Management (KM)

j. Command/Control (C2)

k. Unified Communications (UC)

l. Intrusion Detection Systems (IDS)

m. Access Control Systems (ACS)

n. Video Surveillance Systems (VSS) / Closed Circuit Television (CCTV)

o. Physical Security Information Management Systems (PSIMS)

p. Mass Notification Systems (MNS) and Public Address (PA) Systems

4.1.1 Inside/Outside Plant (ISP/OSP) Infrastructure

Inside/Outside Plant (ISP/OSP) Infrastructure is the cabling, which consist of fiber, copper, and coaxial cabling infrastructure, and its associated cable pathways (i.e., trays and conduit), mechanical/non-mechanical firestop, equipment cabinets, and grounding / bonding systems.

A representative list of materials/equipment, though not all encompassing, typical for ISP/OSP includes fiber and copper cabling, patch panels, connectors, enclosures, conduits, pathways, raceways, PDS/HCDS, cabling tray, pull tape/string, fire stopping materials. It also includes data transmission equipment/connections (e.g., multiplexers, network switches/routers) allowing for high data rate and reliable data transmission and communication between components of this subsystem and possibly with other subsystems.

4.1.2 Active Infrastructure (AI)

AI involves the execution of a set of functions required for controlling, planning, allocating, deploying, coordinating, and monitoring the resources of a telecommunications networks.

AI system includes IT hardware (wired and wireless), software, and processes for routing and switching of multiple network enclaves.

4.1.3 Desktop Automated Information Systems (AIS)

Desktop AIS is specialized equipment approved for secure multi-enclave computing, telephony, and video conferencing.

A representative list of equipment, though not all encompassing, typical for a Desktop AIS include computers (physical or virtual), monitors, headphones, Common Access Card (CAC) readers, secure

Keyboard/Video/Mouse (KVM) switches, analog/digital/VoIP telephones, and video teleconferencing system

4.1.4 Audiovisual (AV)

AV is specialized equipment approved for secure multi-enclave routing and displaying audio, video, and data inputs (computers, codecs, media players, microphones, keyboards, CAC readers, etc.) to outputs

(monitors, speakers, classification, displays, capture devices, etc.). AV is primary installed at conference rooms, collaboration rooms, training rooms, operations centers, command centers, auditoriums, and executive offices.

A representative list of equipment, though not all encompassing, typical for AV computers AV matrix switches, transmitters, receivers, controllers, touch panels, monitors, speakers, codecs, audio mixers, microphones, and other video teleconferencing systems and subsystems)

4.1.5 Command Centers and Other Smart Facilities

A Command Center is a facility that includes a multitude of systems that support the directing of operations. It includes systems used for gathering, processing, analyzing, displaying, and disseminating information such as operational data and related tasks.

A representative list of equipment, though not all encompassing, typical for a Command Center includes

Integrated Furnishing Systems (IFS), Desktop Automated Information Systems (AIS), Inside Plant (ISP) cabling, Active Infrastructure, Satellite Communication (SATCOM), Electronic Security Systems (ESS), and Audiovisual (AV) systems. The contractor shall have demonstrated experience in all phases and subject areas of these solutions.

A representative list of materials/equipment, though not all encompassing, typical for Integrated

Furnishing Systems (IFS) include specialized furniture that supports multi-enclave systems, command and control consoles, modular components with lay-in cable management, consoles, and workstations with integrated core for cable management and integration of IT components, and secure storage for documents and IT equipment. The integrated furniture is selected depending on the operational environment (e.g., Joint Operations Center, Emergency Action Cell, Intel Cell, Fusion Center, Conference

Room, and Leadership Office).

A representative list of materials/equipment, though not all encompassing, typical for AV Systems not limited to but including AV matrix switching, large screen displays, video walls, video processors, programmable control systems (touch panels, matrices, serial/IP control, IPTV distribution and decoding systems, lighting, etc.), speakers, microphones, audio amplifiers, Video Teleconferencing (VTC) suites, multi-display systems, media converters, and audio mixing and digital signal processing.

4.1.6 Space Planning

Space Planning for DoD facilities includes planning and designing IFS to ensures placement is coordinated with passive infrastructure, raised floor tile access, power outlet locations, AV system locations, and printer/shredder/ digital sender ancillary devices in Military Constructions (MILCON), renovations, and expansion. The contractor shall ensure the IFS selection adheres and is integrated with the Desktop AIS design and validates ergonomic flow of personnel within the operating environment.

4.1.7 Data Center & Cloud Computing

Data center is a facility that centralizes an organization’s shared IT operations and equipment for the purposes of storing, processing, and disseminating data and applications. A representative list of materials/equipment, though not all encompassing, typical of data center includes routers, switches, firewalls, storage systems, servers, and application delivery controllers. The facility where a data center is housed typically includes power subsystems, uninterruptible power supplies (UPS), ventilation, cooling systems, fire suppression, backup generators, and connections to external networks.

Cloud Computing is the delivery of computing services of a typical data center over the Internet, DoD network, or “the cloud.”

4.1.8 Knowledge Management (KM) & Command and Control (C2)

KM is the alignment of people and processes, enabled by technology, to facilitate the exchange of operationally relevant information and expertise to increase performance. C2 systems enable information superiority on the battlefield. They provide the commander with the information to make effective decisions and they provide the warfighter the capability to access the information necessary to complete their mission.

A representative list of solutions that are leveraged to support KM and C2 requirements includes business intelligence solutions such as Microsoft SharePoint and other commercially available tools, Global

Combat Support System, Global Command and Control System – Joint, Multinational Information

Sharing, and Joint Planning and Execution Services.

4.1.9 Unified Communications (UC)

Unified Capabilities are the integration of voice, video, and/or data services delivered ubiquitously across a secure and highly available network infrastructure, independent of technology, to provide increased mission effectiveness to the warfighter and business communities.

The contractor shall ensure that the networks providing UC services are designed to meet specific requirements to support the following voice, video, and data services (in accordance with the Department of Defense Unified Capabilities Framework) including but not limited to:

• Voice and Video Services Point-to-Point

• Voice Conferencing

• Video Teleconferencing (VTC)

• Email/Calendaring

• Unified Messaging. Provides access to voicemail via email or access to email via voicemail

• Web Conferencing and Web Collaboration

• Unified Conferencing

• Instant Messaging (IM) and Chat

• Rich-Presence Services

• Mobility

4.1.10 Intrusion Detection Systems (IDS)

An IDS is an automated system that detects an intrusion of a specified site, facility, or perimeter and triggers an alarm. An IDS consists of interior and/or exterior sensors, premise control unit (PCU), and a command-control system.

A representative list of equipment, though not all encompassing, typical for an IDS includes door monitoring contacts, passive infrared sensors, microwave sensors, glass break sensors, position switches, vibration sensors, fence sensors, buried line sensors, radar sensors, video motion detection sensors, arming control units or command keypads. It also included premise control units, system controllers, input/output device controllers, arming control units or command keypads, servers, workstations, storage/archive solutions, and application software which allow users to monitor, control, display, administer, store, archive, and report on status of system and individual alarm points. It also includes data transmission equipment/connections allowing for rapid and reliable data transmission and communication between components of this subsystem and possibly with other subsystems.

4.1.11 Access Control Systems (ACS)

An ACS is an automated system that interfaces with locking mechanisms to momentarily permit access to a controlled area. It does this by unlocking doors, gates, or turnstiles after verifying entry credentials, such as a user’s identification card. An ACS ensures that only authorized personnel can access a controlled area, which helps prevent unauthorized persons from entering it.

A representative list of equipment, though not all encompassing, typical for an ACS includes access devices, readers, biometric devices, door/portal sensors, Request-to-Exit (REX devices) badging equipment, biometric capture systems, locks, doors strikes, personnel access portals, local processors, servers, workstations, storage/archive solutions, and application software. It also includes data transmission equipment/connections allowing for rapid and reliable data transmission and communication between components of this subsystem and possibly with other subsystems.

4.1.12 Video Surveillance Systems (VSS) / Closed Circuit Television (CCTV) Systems

A CCTV system is an automated system that can view, monitor, and record security events. CCTV systems can be used both indoors and outdoors. They are used as an alarm assessment capability, an access control tool allowing remote operators to visually verify personnel prior to granting access to controlled areas, a general assessment tool enabling security personnel to view multiple areas/events from a centralized location, and a means to archive information that might be used as evidence in response to incidents.

CCTV system may be comprised of a wide variety of cameras/imagers, encoders and decoders, recorders, controllers, monitors, servers, workstations, storage/archive solutions, and video management system (VMS) application software which allows personnel to view, organize, and manipulate the data. It also includes data transmission equipment/connections allowing for rapid and reliable data transmission and communication between components of this subsystem and possibly with other subsystems.

4.1.13 Physical Security Information Management System (PSIMS)

A PSIMS is an automated system designed to integrate multiple, unconnected security applications and devices and control them through one comprehensive graphical user interface. It collects and correlates events from existing disparate security devices and information systems (video, access control, sensors, analytics, networks, building systems, etc.) to empower personnel to identify and proactively resolve situations.

PSIMS may be comprised of a server and application software that integrates with IDS, VSS, and other

Situational Awareness systems. Reporting, display, correlation and configuration of PSIMS data are performed on the user interface, which may consist of application software loaded on workstations. The

PSIMS also includes data transmission equipment/connections allowing for rapid and reliable data transmission and communication between components of this subsystem and possibly with other subsystems.

4.1.14 Mass Notification Systems (MNS) and Public Address (PA) Systems

Mass notification systems and public address systems provide real-time information and instructions to people in a building, area, site, or installation using intelligible voice communications along with visible signals, text, and graphics, and possibly including tactile or other communication methods. The purpose of mass notification system is to protect life by indicating the existence of an emergency and instructing people of the necessary and appropriate response and action.

A representative list of equipment, though not all encompassing, typical for a mass notification system includes a central control station, autonomous control units, local operating consoles, notification appliance networks, high power speaker arrays, and ancillary equipment. The MNS and PA systems also include data transmission equipment/connections allowing for rapid and reliable data transmission and communication between components of this subsystem and possibly with other subsystems. Many MNS solutions are required to interface with existing fire alarm systems, existing PA systems, existing telephone dialing systems, and other systems.

5. Performance Requirements

The following tasks may be included and/or specified in a TO:

• TASK 1: Program and Project Management

• TASK 2: System Engineering

• TASK 3: Software Engineering

• TASK 4: Cybersecurity

• TASK 5: Equipment/Material Procurement

• TASK 6: Pre-Installation Test and Checkout (PITCO)

• TASK 7: Cutover and Transition Plan

• TASK 8: Installation and Integration

• TASK 9: System Operational and Verification Test (SOVT)

• TASK 10: Training

• TASK 11: Logistics Support

5.1 TASK 1: Program and Project Management

5.1.1 Program Management

The contractor shall perform all the required processes to manage the programs associated with this IDIQ contract:

• Management of staffing and resources

• Training and certifications of personnel

• OCONUS hiring, deployments, and travel

• Management of TESA applications and applicants

• Quality Assurance

• Integrated Master Schedule (IMS)

• Contracts management

• Budgeting, proposal, and cost control

• Procurements

• Communications management

• Facility Management

5.1.1.1 Program Management Support

Some programs shall require a contractor to work closely with the Government project manager(s) and program manager(s) to support the needs of the program at the sponsor level. The contractor program management support will be tasked to perform the following actions but not limited:

• Coordinate meetings

• Develop agendas

• Develop briefs

• Develop Integrated Master Schedule (IMS)

• Prepare budget drills

• Gather information for data calls

• Attend meetings

• Generate meeting minutes

• Develop action items

• Develop Analysis reports

• Develop courses of actions

• Manage and update SharePoint and/or Teams site

• Support the Government on resource management

5.1.2 Project Management

5.1.2.1 TO Kickoff

No later than (NLT) ten (10) business days post Task Order award, the contractor shall develop and submit a Task Order Kickoff brief consisting of the minimum information and/or documents: staffing plan or organizational resource chart, draft schedule, primary objective and scope, issues and risks, and assumptions for review. The Contractor shall coordinate with the COR to schedule the TO Kickoff in person or virtual.

5.1.2.2 Plan of Objectives and Milestones (POA&M)

The Contractor shall develop a Plan of Action and Milestones (POA&M) for all tasks and milestones associated with the Task Order PWS and submit to the COR, no later than (NLT) ten (10) business days post Task Order award. The POA&M shall show the completion of all tasks, including review periods for ten (10) business days. The POA&M shall also include all task order and installation milestones. It shall utilize a Work Breakdown Structure (WBS) to compartmentalize the effort into definable work efforts and to show assigned resources to each work element and the amount of time in business days necessary to complete each element. The POA&M shall show the interdependencies between all tasks and subtasks.

It shall have a Forecasted versus Actual versus Baseline tracking basis and shall identify tasks, dependencies, baseline start dates, baseline finish dates, baseline durations, actual start dates, actual finish dates, actual durations, forecasted start dates, forecasted finish dates, forecasted durations, and percent complete for each task and subtask. It shall be developed in Microsoft Office Project 2016 or later version.

A draft POA&M, baseline POA&M, and monthly POA&M updates shall be submitted. Monthly updates for the POA&M and all other monthly project management artifacts shall be submitted simultaneously prior to the 10th of each month at which time the Government COR has five (5) business days to provide comments and the Contractor shall update three (3) business days thereafter. At the discretion of the

Government, the Contractor shall re-baseline the POA&M and provide weekly schedule updates.

The Contractor shall coordinate with the Government to integrate the POA&M into the Integrated Master

Schedule (IMS) to track the coordination of projects associated with USEUCOM. At the discretion of the

Government, the Contractor shall integrate the re-baselined POA&M into the IMS providing up to four intra-monthly IMS updates.

5.1.2.3 Weekly Meetings

If required per Task Order, the Contractor shall host a weekly web conference and audio teleconference with the COR and other Government stakeholders to discuss the schedule, upcoming activities, action items, risks, and issues with the Task Order. Prior to the meeting, the Contractor shall provide a Weekly

Activity Report (WAR) to include a stoplight report including high-level schedule, milestones and deliverables, funding report, list of actions, list of risks/issues. The time of the weekly meeting will be determined with the COR post award of this Task Order.

The Contractor shall develop and deliver meeting reports, which shall include participants, objective, agenda, conclusion, and action items. The Contractor shall submit meeting reports to the Government for review within one (1) business day following meetings.

5.1.2.4 Project Change Request (PCR)

The contractor shall inform the COR and other Government stakeholders for any potential cost, schedule, and performance changes on a Task Order. The contractor shall provide the analysis and the potential impact into a PCR. The government will review the PCR, make any necessary changes, perform independent analysis, and develop Independent Government Cost Estimate (IGCE), and formally initiate the PCR with relevant Government stakeholders. Upon approval of the PCR from the Government, the

COR will submit a Task Order modification request to the Contracting Office. Note that until the modification of any changes has been awarded by the Contracting Officer, the contractor is not authorized to proceed to execute any requested changes.

5.1.3 Task Order Administration

5.1.3.1 Monthly Status Report (MSR)

The contractor shall develop and submit a TO status report monthly at least 30 days after TO award on the 10th of each month for those months the TO is active. The contractor shall report on various TO functions performance, schedule, financial, business relations, and staffing plan/key personnel. The

Contractor shall develop and deliver, each month, a monthly progress report which shall describe sponsor information, project information, 30-day look back of activities and deliverables, 30-day look ahead of schedule of activities and deliverables, contract history, project status, deliverable status, action items, requests for information, risks/issues, and service requests. All active and completed tasks within the reporting period level of effort tasks shall be identified with a description, completion status, estimated completion date, total amount, and any comments on the status.

The Contractor shall also include a monthly financial report that includes a roll-up of the labor charges and a line-by-line Other Direct Cost (ODC) charges (travel, materials, subcontracts, etc.). The financial report shall include month-to-month tracking by TO, CLIN structure, billed to date, invoicing, funds remaining, and invoiced/paid dates. Travel charges shall be broken down to show traveler’s per diem, lodging, air fare, rental car, G&A, and other fees, etc. The materials shall be broken down to show which materials are ordered, shipped, or delivered, purchase order number, invoice number, shipping costs, G&A, and other fees, etc. The subcontracts shall be broken down to show which services are ongoing, completed, and associated invoices, charges and payments, and any leasing invoices, changes, and payments tied.

5.1.3.2 Task Order Closeout Report

The contractor shall develop a TO Closeout Report and submit it no later than 15 days before the TO completion date. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontracting information.

5.1.3.3 Lessons Learned

If required on a Task Order, the contractor shall develop a TO Lessons Learned to document the errors, failures, successes, and rooms for improvement. The Task Order PWS may require lessons learned sessions between the Contractor and Government to review lessons learned reports and make decisions on how to use the knowledge gained. Lessons can be identified at any point during the project and does not need to be conducted only at the end of the TO.

PWS

Task#

Deliverable Title Format Due Date Distribution/

Copies

Frequency and Remarks

6.2.2.1 TO Kickoff Brief MS Office and

PDF

NLT 10 business days after award

1 copy to the COR

One Time

6.2.2.2 Plan of Objectives

and Milestones

(POA&M)

MS Project

2016 or later and PDF

NLT 10 business days after award and

10th of each month

1 copy to the COR

1 baseline and monthly

6.2.2.3 Weekly Activity

Report

MS Office and

PDF

1 business day after weekly meeting

1 copy to the COR

Weekly

6.2.2.4 Project Change

Request (PCR)

PDF As Required 1 copy to the COR

As Required

6.2.3.1 Monthly Status

Report

MS Office, PDF

10th of each month 1 copy to the COR

Monthly

6.2.3.1 Monthly Financial

Report

MS Office 10th of each month 1 copy to the COR

Monthly

6.2.3.2 TO Closeout

Report

MS Office, PDF

NLT 15 days before

TO completion date

1 copy to the COR

One Time

6.2.3.3 Lesson Learned

Documentation

MS Office, PDF

Within 30 days of

Government Request

1 copy to

As Required

5.2 TASK 2: System Engineering

5.2.1 Research, Analysis, Planning and Preparation

The contractor shall research, analyze, and translate data into qualitative and quantitative technical requirements and architectures to allow for planning and project start-up. This includes site survey and analysis, identification of requirements, statement of existing systems/equipment/technologies, considerations and comparisons of candidate solutions, recommendations, scheduling, and implementation schedule, WBS, logistics support, and cost.

Research involves investigation of existing or proposed functions of a site, including mission requirements, existing capabilities, physical specifications/limitations, problem areas, inter facility and intra facility requirements, environmental impacts, scientific research affects, and special considerations.

Analysis includes evaluation of requirements derived from data gathered during the site survey. It also includes considerations and comparisons of candidate solutions, discussing the advantages and disadvantages of the systems/equipment/technologies explained above. Based upon these considerations, the contractor shall make recommendations for and report on the best solution.

Planning and Preparation includes the implementation schedule, presenting a systematic and integrated approach to accomplishing new installations and/or upgrade existing equipment, including dates of procurement, shipment/transit, installation and checkout, methods of dual operations, and training. It also reflects the logistics support approach for training, maintenance, parts support, documentation, and other logistic needs as required. Cost data will provide the procuring activity with estimated budgetary information for planning purposes.

The contractor shall perform tests and studies associated with system design, integration, installation, and operation. The test data and reports will be of sufficient depth and breadth to provide the government with technical data and viable design options for future systems development. Furthermore, a variety of evaluation and decision point data may be required to assess system compatibility, reliability, vulnerability, etc.

The contractor shall integrate new equipment technologies into existing system architectures. The contractor shall apply a system engineering approach to ensure that mission objectives and system criteria requirements are fulfilled. Emphasis shall be on the demonstration of clear and measurable improvements in the performance, logistics supportability, reliability, and maintainability of the item.

The contractor design concepts shall include provisions for continuous technological improvement to maximize opportunities for product improvement available from emerging technological advances in the marketplace. Proven technologies, products and processes shall be utilized wherever possible.

5.2.2 Site Surveys, Analysis, and Reports

The contractor shall conduct site surveys to determine the optimum location and configuration for an equipment/system installation including any site preparation requirements. The contractor shall gather all pertinent environmental, engineering, configuration, and design information relevant to site conditions, analyzing the collected data, performing necessary calculations to make technical recommendations, and preparing technical reports and documentation (such as Site Survey Report) for a specific installation.

5.2.3 Requirements Development

The contractor shall gather, develop, and track requirements. The contractor shall develop the following requirements documentation if required per each Task Order PWS:

• Conceptual design depicts a diagram the of the intended design.

• System Requirements Matrix (SRM) identifies the details of operational spaces, personnel, and systems to map to the C4I requirements. The OSM provides a numerical value for C4I requirements.

• Requirements Traceability Matrix (RTM) provides the details of the integrated system capability framework, identifying and tracking the requirements for each system. The RTM documents the derivation of each requirement.

• Requirements Analysis Document (RAD): Consolidates the SRM, RTM, and “Lucky Charms” information into a single deliverable document. Includes graphical representations of spaces, classification boundaries, and high-level design concepts.

• Site Requirements Package presents the passive infrastructure requirements to support C4I installation efforts.

• Military Construction (MILCON) Base Electronic System Engineering Plan (BESEP) presents building requirements to the A&E firm from a C4ISR perspective. This document specifies construction requirements needed to adequately support the C4ISR systems to be installed in the building.

• Requirements Baseline Document (RBD) consolidates and summarizes the requirements into a single deliverable for customer and stakeholder signature. Upon signature of the RBD, the requirements are baselined. Any changes to any requirements to be tracked with the RTM.

• In some areas of the Navy, the Base Electronics System Engineering Plan (BESEP) is the basis or preliminary technical reference governing installations of electronics facilities or portions of the facilities. The BESEP normally includes a listing of components to be installed, shows preliminary design of the installation, describes the functions, and required interface with existing or planned systems, and when finished provides an authoritative engineering plan and major equipment/material list necessary for determining final design specifications.

If required on a Task Order, the contractor shall develop or update and track requirements using Model-based System Engineering (MBSE) tools such as Cameo System Modeler tool suite. The contractor shall develop an integrated system model that can be importable/exportable to and from mainstream Systems

Modeling Language (SysML) MBSE tools without loss in formatting or integrity.

5.2.4 Installation Design Documents

The contractor shall develop various technical requirements, specification, and drawing documents to support installation design. The contractor shall consider cost effectiveness, reduction of risks, constraints, and schedules. The contractor shall prepare all documentation using Government-provided information, as necessary, and format it into prescribed Government structure corresponding to the requiring agency, Department of Defense (DoD) and Navy instructions, standards, and specifications.

5.2.5 Installation Design Plan (IDP)

The contractor shall develop 30%, 60%, and 90% IDPs utilizing System of Systems Engineering

Approach. The IDPs shall be developed in accordance with Shore Installation Process Handbook (SIPH) and comply with USEUCOM/2nd Signal Brigade standards.

5.2.5.1 Installation Design Plan (IDP) Structure

IDPs are the components of the design, which show the physical work to be done to accomplish the required capability. IDPs support the other design components created during the systems engineering phase. The contractor shall develop IDPs in accordance with the SIPH. The IDP shall consist of these engineering drawing elements as a minimum:

• Title - Title of design plan, Drawing Number with revision, drawing index, and signature block.

• Vicinity Map - Illustrates the geographical location of the installation and other important, related areas

• Site Map - Illustrates the Military Base plan and/or the immediate site affected by the new installation. The Site Map shall show all new installations of items outside existing buildings and installations involving new buildings. Outside cable plant installations also require a Site

Map showing where the cable will be installed.

• Site Plans – Site Plans identify the overall site where the work will be performed with callouts to the Project Location Plans.

• Master Parts Lists - Lists all Equipment, Materials, References, Legend, and Acronyms.

• Technical Data Summary - Lists dimension, electrical load, and heat output of the equipment to be installed.

• Floor Plans and Elevations - Identify the location of equipment to be installed within buildings.

Depicts specific placement of all equipment for each installation location within scaled floor plans, maps or areas. This drawing depicts new equipment locations by plan, elevation, and sectional views, so that a complete understanding of the configuration and location of all units of equipment to be installed is conveyed.

• Antenna Layouts and Elevations - All IDPs for projects that will install an antenna shall include an Antenna Layout and Elevations drawing. Depicts the locations of antennas, towers or platforms to be installed including any vital alignment information (e.g., elevation and azimuth).

• Simplified Block Diagram - Illustrate how major pieces of equipment are interconnected and will provide high- level information about signal flow for individual circuits or groups of circuits.

• Cable Block Diagrams - Show all cables and electrical wiring to be installed, modified, reconnected, removed, or upgraded.

• Cable Running Sheets - List end-point connections, wire/fiber color, and signal names for all conductors in each installed cable

• Circuit Diagrams - Contains circuit diagrams depicting terminations of cables and connectors at each system unit. If multi-conductor cables or different colored conductors are used, list colors on drawing.

• Cable Routing Layouts - identify the locations, via use of site maps, types of trench locations and routing in earth, cable trays, ducts, conduits, and other fixed hardware used to route and protect cables and wires inside of concrete, asphalt, stone or other material for the purpose of installing cable or conduit below or above ground. or, in other words, make cable pathways

• Cable Plant - includes the plant conduit plan, plant cable plans, outside plant data

• Fabrication and Assembly Details - Depicts all mounts, brackets, installation assemblies, and chassis or towers to be manufactured. The drawing shall define all features of the assembly including configuration, dimensions, tolerances, materials, and mandatory processes such as surface preparation and finish, protective coatings, symbols, nomenclature, accompanying component/material lists and detailed specifications that are necessary to manufacture, fabricate, and assemble all items that cannot be procured.

• Mechanical Assembly and Mounting Details - Depicts how an item, product or assembly might be mounted, hung, installed, set, or otherwise attached to doors, walls, ceilings, buildings, structures, or other equipment. These illustrations may be drawn in plan, elevation, sectional or isometric views, so as to show the correlation between the product and the immediate surroundings. Where placement and/or installation of the item require any additions or modifications to the existing Government facilities, all additions and/or modifications shall be referenced and depicted.

Installation Design Plans will normally be developed in three phases – Preliminary, Final and As-Built.

The Government will require a minimum of ten (10) business days to review and provide comments. The

Contractor shall respond to the review and comments using a design review comments resolution matrix.

The Contractor shall incorporate changes to the next stage/iteration of the IDP. The Contractor shall coordinate a design review meeting within five (5) days from receipt of the Government review and comments.

The contractor shall not commence any installation tasks until the Government has reviewed and approved the final IDP submittal. It is the contractor's responsibility to advise the COR when the IDP has been completed to the following stages. All IDPs should be developed using AutoCAD (version 2018 or newer) and delivered in a standard AutoCAD format or in Revit. In some TOs, more simple designs or portions of the designs will be required, and the format can be in Microsoft Visio or equivalent.

5.2.5.1.1 IDP Phases

(a) Preliminary IDP (30% and 60%)

The first phase of the engineering design process is the development of a Preliminary IDP. The

Preliminary IDP shall consist of a System Specification and preliminary drawings and serves as the basic or preliminary technical reference governing the installation of systems, sub-systems, and equipment. It shall include a listing of equipment or components to be installed, specify preliminary design of the installation, describe the functions and the planned operation of the intended system, define the required interface with existing and/or planned systems, detail required support and test equipment, and detail the facilities or physical plant requirements required to support the planned system installation. The

Preliminary IDP describes an authoritative engineering plan and some major equipment/components necessary for subsequent completion of the final IDP drawings and design specifications. The Preliminary

IDP will identify any existing equipment for removal, re-installation, replacement, or modification to meet system specifications.

(b) Final IDP (90%)

The phase of the engineering design process, prior to installation, is the development of the Final IDP.

The Final IDP shall be a comprehensive design comprised of engineering planning documents as well as engineering drawings. The engineering planning documentation shall include a listing of equipment. The contractor shall develop or modify electrical, electronic, mechanical, and configuration design drawings and documentation with installation and safety procedures and specifications for system/sub-system/equipment installation. Lists of performance tests, support equipment, and a bill of installation equipment and materials shall be provided as part of the IDP. The IDP shall be delivered as set forth in the deliverable of this contract document or as specified in the applicable TO PWS.

(c) As-Built IDP

The third and last phase of the engineering design process is the development of the As-Built IDP. The

As-Built IDP consist of the final installed system and equipment. It shall incorporate all the redlines during installation that are changes from the Final IDP.

5.2.5.1.2 List of Materials (LOM)

The Contractor shall develop the LOM required to be procured to support the project, project phase, and/or Task Order. The LOM is a separate spreadsheet and shall match parts lists and technical data summary in the IDP. The LOM must include the minimum information: manufacturer, part number, description, quantities, unit of measurement, list price, and extended price, technical data (size, weight, power ratings, heat output, etc.). The preliminary LOM shall be submitted along with the 60% IDP submission. The Government will require a minimum of ten (10) business days to review and provide comments. The Contractor shall address the comments and provide an updated LOM with corrections within ten (10) business days or the due date to be specified in a TO.

Additional LOMs can be submitted as the IDP is finalized. In some instances, the Government may require the contractor to develop and submit a preliminary LOM at 30% IDP to mitigate some schedule risks. The Contractor shall not proceed with any procurements of the materials without approval from

Government

PWS

Task#

Deliverable Title Format Due Date Distribution/

Copies

Frequency and Remarks

6.3.1 Research, Analysis, Planning, and Preparation

reports, summaries, and briefings

MS Office, PDF

As required 1 copy to the COR

As Required

6.3.2 Site Survey Report MS Office, PDF, JPEG

pictures

TBD at TO Level 1 copy to the COR

1 draft and 1 corrected

6.3.3 Requirements

Documents

MS Office, PDF, Cameo

TBD at TO Level 1 copy to the COR

1 draft and 1 corrected

6.3.9.5 Installation Design

Plan (3 Phases)

AutoCAD, PDF, RVT, VSD

TBD at TO Level 1 copy to the COR

30%, 60%, 90%, Redlines, As-builts

6.3.9.5 List of Material

(LOM)

MS Office

Excel

60% IDP 1 copy to the COR

1 at 60% IDP and as required afterwards

5.3 TASK 3: Software Engineering

Some systems of systems will require custom software development for communication and interaction between vital components. The contractor shall develop custom software. Software engineering includes the design, development, and documentation of software to support a specific Government requirement.

The contractor shall utilize certified software and computer personnel. The contractor (prime and/or subcontractor) that is responsible for leading software development efforts shall define a software development approach appropriate for the computer software effort to be performed under each task. The contractor shall document the approach in a Software Development Plan (SDP). The contractor shall follow this SDP for all computer software to be developed or maintained under this effort. The contractor shall develop one SDP to support the unique software requirements for each TO/project. As required, the

Government will identify specific SDP project requirements at the TO level.

PWS

Task#

Deliverable Title Format Due Date Distribution/

Copies

Frequency and Remarks

6.4 Software

Development Plan

(SDP)

MS Office, PDF

TBD at TO Level 1 copy to the COR

1 draft and 1 corrected

5.4 TASK 4: Cybersecurity

The contractor shall develop Cybersecurity artifacts that are compliant with the relevant Department of

Defense (DoD) and Army Cybersecurity policies and standards including DoD 8500.1, DoD 8510.1//Risk

Management Framework (RMF), National Institute of Standard and Technology (NIST) Special

Publication (SP) 800-53. All artifacts shall follow the latest version of the Navy RMF Processing Guide

(RPG). The contractor shall develop the following Cybersecurity RMF artifacts to include but not limited to the following:

• Hardware List

• Firmware List

• Software List

• Ports/Protocols/Service List

• In-Flows Table List

• System Enterprise Diagram

• Authorization Boundary/Network Diagram (DISA-CPG compliant diagram)

• Data Flow Diagram

• Security Assessment Plan

• Security Assessment Plan (SAP)

• Test Plan (CS Component of SOVT)

• Security Categorization Form/RMF Step 1

• Identified Inheritable Controls/RMF Step 2

• Security Technical Implementation Guides (STIGs) Checklist

• Cybersecurity POA&M

• RMF Security Plan

• RMF Risk Assessment Report (RAR)

• Cybersecurity Threat Security Plan

• Security Control Implementation/Configuration Test Plan (timeline, resources)

The Cyberspace workforce elements addressed include contractor personnel performing functions in designated Cyber IT and Cybersecurity positions. In accordance with DFARS Subpart 5239.71 and DoDD

8140.01 contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01-M and subsequent manual [DoD 8140] when applicable prior to accessing DoD information systems. Proposed contractor Cyber IT and cybersecurity personnel shall be appropriately qualified prior to the start of the task order performance period or before assignment to the task order during the performance period and a member of the

Cybersecurity Workforce (CSWF).

CSWF contractor personnel shall perform cybersecurity functions. In accordance with DoD 8570.01-M

Information Assurance Workforce Improvement Program Manual, the CSWF is comprised of the following categories: Information Assurance Technical (IAT) and IA Management (IAM)); and specialties: Computer

Network Defense Service Providers (CND-SPs) and IA System Architects and Engineers (IASAEs).

Based on the IA function provided by the individual, an IA designator is assigned that references an IA category or specialty.

The contractor shall support and follow DoDI 8510.01 when deploying, integrating, and implementing IT capabilities. The Contractor shall support Government personnel to ensure compliance with all current

USEUCOM IT and cybersecurity policies. The contractor shall follow DoDI 8510.01 prior to integration and implementation of IT solutions or systems. The contractor shall ensure all software recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, 26 CFR Part.

Contractor personnel recommending or purchasing commercial software products, hardware, and related services supporting NIWC-ATLANTIC programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest Department of Defense (DoD) and USEUCOM policies.

The contractor shall ensure that all products recommended and/or procured that impact cybersecurity are selected from the National Information Assurance Partnership (NIAP) Validated Products List. The contractor shall ensure the products chosen are based on the appropriate Evaluated Assurance Level

(EAL) for the network involved and are utilized in accordance with latest Defense Information Systems

Agency (DISA) policy at time of order. The contractor shall store all product information and have it available for Government review at any time.

The contractor shall ensure any equipment/system installed or integrated into USEUCOM platform will meet the cybersecurity requirements as specified under DoDI 8500.01. The contractor shall ensure that any design change, integration change, configuration change, or installation of hardware and software is in accordance with established DoD/USEUCOM/Army cyber directives and does not violate the terms and conditions of the authorization issued by the appropriate Authorization Official.

The contractor IAT personnel shall perform RMF Information Systems Security Engineer (ISSE) cybersecurity roles and responsibilities. In accordance with DoD RMF and NIWC-Atlantic guidance documents, RMF is comprised of the following 6 Steps: Step 1 – Categorize, Step 2 – Select, Step 3 –

Implement, Step 4 – Assess, Step 5 – Authorize, Step 6 – Monitor. The contractor shall perform the ISSE role within eMASS pursuant to DoD, USEUCOM, and Army.

DoD 8570.01-M and DFAR’s PGI 239.7102-3 have promulgated that contractor personnel shall have documented current cybersecurity certification status within their contract. The contractor shall develop, maintain, and submit a CSWF Report monthly or as required at the TO level (Note: If initiated at the TO level, report is not necessary at contract level). IAW clause DFARS 252.239-7001, if cybersecurity support is provided, the contractor shall provide a Cybersecurity Workforce (CSWF) list that identifies those individuals who are IA trained and certified. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor personnel. The contractor shall verify with the COR or other Government representative the proper labor category cybersecurity designation and certification requirements.

PWS

Task#

Deliverable Title Format Due Date Distribution/

Copies

Frequency and Remarks

6.5 Hardware List MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Firmware List MS Office, PDF

TBD at TO Level 1 copy to

As required

6.5 Software List MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Ports/Protocols/

Service List

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 In-Flows Table List MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Ports/Protocols/

Service List

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 System Enterprise

Diagram

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Authorization

Boundary/Network

Diagram

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Data Flow Diagram MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Security

Assessment Plan

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Test Plan (CS

Component of

SOVT)

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 STIG Checklists MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Cybersecurity (CS)

POA&M

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 RMF Security Plan MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 RMF Risk

Assessment

Report (RAR)

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Cybersecurity

Threat Security

Plan

MS Office, PDF

TBD at TO Level 1 copy to the COR

As required

6.5 Cybersecurity

Workforce (CSWF)

Report

MS Office, PDF

TBD at TO Level 1 copy to

5.5 TASK 5: Equipment/Material Procurement

The contractor shall procure incidental materials to support the IT installation.