Draft PWS - USMC ESS BPA.docx

United States Marine Corps Electronic Security Systems

PERFORMANCE WORK STATEMENT (PWS)

1. Contracting Officer’s Representative (COR).

a. Primary COR. See DITCO Additional Text G1 - Points of Contact

b. Alternate COR. See DITCO Additional Text G1 - Points of Contact

c. Property Administrator (PA) See DITCO Additional Text G1 - Points of Contact

2. Contract Title. United States Marine Corps (USMC) Electronic Security Systems (ESS)

3. Background. The USMC and Naval Information Warfare Center (NIWC) Atlantic requires engineering development, design, procurement, fabrication, configuration, integration, installation, logistics, maintenance, and life cycle support solutions for ashore ESS. These systems will support the operational requirements of USMC facilities where emergency management, public safety, law enforcement, security, and command & control are of high or vital interest. This PWS provides the general guidelines and specific requirements to develop, deliver, and sustain electronic security and emergency management system solutions that protect our Nation's critical infrastructure, personnel, assets, and resources worldwide.

4. Objectives: USMC and NIWC Atlantic must be able to respond quickly and effectively in order to meet the operational requirements of the USMC in the rapidly changing environments. 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 BPA will be executed through the issuance of call orders that are determined to be within the scope and location of this BPA. This BPA encompasses project/program management, engineering, procurement, implementation, and testing requirements associated with the development and delivery of ESS solutions.

5. Scope. The purpose of this Blanket Purchase Agreement (BPA) is to provide streamlined delivery of ESS service solutions to the warfighter at shore installations worldwide in response to time sensitive, emergent mission and special security program requirements. The scope of this BPA covers the entire spectrum of outcomes associated with the full lifecycle of delivery and support of ESS capabilities to include automated Access Control Systems (ACS), Intrusion Detection Systems (IDS), Closed Circuit Television (CCTV), and Mass Notification Systems (MNS).

This BPA covers requirements as it relates to ESS 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. Support under this BPA includes supply requirements and encompasses project/program management, engineering, and other technical support requirements associated with the development, delivery, sustainment, and management of ESS solutions.

6. Performance Requirements. The following paragraphs list all required non-personal services tasks that will be required throughout the BPA. The contractor shall provide necessary resources with knowledge and experience as cited in the personal qualification clause to support the listed tasks. Contractors shall perform requirements in accordance with (IAW) Federal Acquisition Regulation (FAR) and/or Defense Federal Acquisition Regulation Supplement (DFARS), which do not include performance of inherently Government functions. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

Contractor shall perform all the required processes to manage the programs associated with this BPA contract to include but not limited to:

0. Management of staffing and resources.

0. Training and certifications of personnel.

0. Outside Continental Contiguous United States (OCONUS) hiring, deployments, and travel.

0. Management of Technical Expert Status Accreditation (TESA) applications and applicants.

0. Quality Assurance.

0. Integrated Master Schedule (IMS).

0. Contracts management.

0. Budgeting, proposal, and cost control.

0. Procurements.

0. Communications management.

0. Facility Management.

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

· Task 1: 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.

6.1 Task 1. Project Management.

6.1.1 Subtask 1 – Call Order Kickoff. No later than (NLT) ten (10) business days post call order award, the contractor shall develop and submit a call 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 call order kickoff in person or virtual.

6.1.2 Subtask 2 – Plan of Action and Milestones (POA&M). The contractor shall develop a POA&M for all tasks and milestones associated with the call order PWS and submit to the COR, NLT ten (10) business days post call 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 call 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 (MS) 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 IMS to track the coordination of projects associated with USMC. 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.

6.1.3 Subtask 3 – Weekly Meetings. If required on a call 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 call 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 a call 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.

6.1.4 Subtask 4 – Project Change Request (PCR). The contractor shall inform the COR and other Government stakeholders of any potential cost, schedule, and performance changes on a call order. The contractor shall provide the analysis and the potential impact on a PCR. The Government will review the PCR, make any necessary changes, perform independent analysis, develop an Independent Government Cost Estimate, and formally initiate the PCR with relevant Government stakeholders. Upon approval of the PCR from the Government, the COR will submit a call order modification request to the Contracting Office. Note that until the modification of any changes has been awarded by the Contracting Officer (KO), the contractor is not authorized to proceed to execute any requested changes.

6.1.5 Subtask 5 – Monthly Status Report. The contractor shall develop and submit a call order status report monthly at least 30 days after call order award on the 10th of each month for those months the call order is active. The contractor shall report on various call order 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.

6.1.6 Subtask 6 – Monthly Financial Reports. 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 call order, Contract Line-Item Number (CLIN) structure, billed to date, invoicing, funds remaining, and invoiced/paid dates. Travel charges shall be broken down to show travelers per diem, lodging, air fare, rental car, General and Administrative (G&A) costs, 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. Activities completed by subcontractors 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.

6.1.7 Subtask 7 Call Order Closeout Report. The contractor shall develop a call order Closeout Report and submit it NLT 15 days before the call order completion date. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontracting information.

6.1.8 Subtask 8 – Lessons Learned. If required on a call order, the contractor shall develop a call order Lessons Learned to document the errors, failures, successes, and rooms for improvement. The call 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 do not need to be conducted only at the end of the call order.

Deliverables:

6.1.1

6.2 Task 2. System Engineering Support.

6.2.1 Subtask 1 – Research, Analysis, Planning and Preparation. If required on a call order, 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, software (SW) support, and other logistic needs as required. Cost data will provide the procuring activity with estimated budgetary information for planning purposes.

The contractor shall investigate and provide detailed analysis and/or studies to evaluate equipment or system components with regard to operational, standardization, and logistics considerations and make recommendations for improvement.

The contractor shall provide signal processing, structural, packaging, and human engineering studies and analysis. Examples: analyze circuitry of sensor printed circuit cards to determine cause of high failure rate and recommend corrective action; terminal box design - evaluate state-of-the-art surge suppression devices to minimize dimensions of enclosure for termination of multi-pair cable.

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 prepare reports, plans, summaries and/or briefings that describe the topics described above. Unless otherwise specified in each call order, the contractor's format is acceptable.

As part of delivery of ESS and IAW individual call orders, the contractor shall integrate new equipment technologies into existing system architectures as specified in the call order. The contractor may apply a systems 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. The contractor shall utilize proven technologies, products and processes wherever possible.

In support of research and development (R&D) efforts, the contractor shall support the development and application of scientific and analytical disciplines to conduct fundamental research; scientific study and experimentation directed toward advancing the state-of-the-art or increasing knowledge or understanding; concept formulation; assessment of system and subsystem requirements; development, analysis and evaluation of concepts, technologies, systems and subsystems; and development of operational concepts and tactics with the end goal being the application of results to developing new, or improving existing, war fighting capabilities.

The contractor shall provide prototyping, engineering and testing services and shall perform hardware (HW) design and prototyping that includes requirements for differing HW prototypes, capable of operation under field conditions. The contractor shall support SW design, development, and test in support of requirements as cited in individual call orders.

In support of modeling & simulation efforts, the contractor shall apply a standardized, rigorous, structured methodology to create and validate a physical, mathematical, or otherwise logical representation of a system entity, phenomenon, or process. The contractor shall be able to use models, including emulators, prototypes, simulators, and stimulators, either statically or over time, to develop data as a basis for making managerial, technical, strategic, or tactical decisions.

In support of system design & documentation, the contractor shall be able to support the engineering effort required to prepare and assure that the detailed technical data documentation that is necessary to support system development reflects the latest design, configuration, integration, and installation concepts. Technical documentation shall be in the form of paper, electronic (digital) or interactive computer systems.

The contractor engineering support shall create and revise engineering documents, Configuration Management and Control, maintenance and service manuals, procedural and operator manuals, and other engineering related manuals, policies, procedures, guides and reference material to include computer aided design, drawings and associated parts lists.

In support of configuration management and as outlined in Military Handbooks (MIL-HDBK-61A), the contractor shall apply engineering analytical disciplines to identify, document, and verify functional, performance, and physical characteristics of systems, to control changes and non-conformance, and to track actual configurations of systems and platforms. The contractor shall develop configuration management plans as directed in the call order as part of the General PM documents.

In support of interface development, the contractor shall provide support for SW and HW configuration and/or development of commercial products in order to provide for required communication and interaction between vital components in a system of systems environment. The contractor shall support the development of custom interfaces as directed by the call order.

6.2.2 Subtask 2 – Site Survey Reports. If required on a call order, 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.

6.2.3 Subtask 3 – Requirements Development. If required on a call order, the contractor shall gather, develop, and track requirements. The contractor shall develop the following requirements documentation if required per each call order PWS:

· Conceptual design depicts a diagram of the intended design.

· System Requirements Matrix (SRM) identifies the details of operational spaces, personnel, and systems to map to the Command, Control, Communications, Computers, and Intelligence (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 consolidates the SRM, RTM, and “Lucky Charms” information into a single deliverable document. It 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 Base Electronic System Engineering Plan (BESEP) presents building requirements to the Architecture and Engineering 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 shall be tracked with the RTM.

· In some areas of the Navy, the 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.

The contractor shall follow processes as described in section 1.1 of the technical proposal for systems engineering approach on the development of an Installation Design Package (IDP). Approach shall be aligned to ISO/IEC 15288 framework of processes. The requirements for documentation and analysis processes shall be heavily supported by Model-based System Engineering (MBSE) methodologies and Cameo Systems Modeler.

The contractor shall develop or update and track requirements using 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 MBSE tools without loss in formatting or integrity.

The contractor shall ensure requirements analysis process are IAW NIWC MBSE Guidebook and MBSE best practices.

6.2.4 Subtask 4 – Installation Design Documents. If required on a call order, the contractor shall develop various technical requirements, specifications 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, DoD and Navy instructions, standards, and specifications.

6.2.5 Subtask 5 – Installation Design Plans. If required on a call order, the contractor shall develop 30%, 60%, 90%, final, and As-Builts IDPs utilizing System of Systems Engineering Approach. The IDPs shall be developed IAW Shore Installation Process Handbook (SIPH) and comply with USMC Drawing Standards.

6.2.5.1 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 IAW PWS reference Para 2.2.n “Shore Installation Process Handbook," latest version, with emphasis on “Installation Design Plan (IDP) Development” and "Appendix Q1 – Installation Design Plan (IDP) Development." The IDP shall reflect all call order installation deliverables. The IDP shall consist of these engineering drawing elements as a minimum:

· Title – Title of design plan, Drawing Number with revisions, 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 site work will be performed with callouts to the Project Location Plans.

· Master 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 HW 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, and 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.

IDPs will normally be developed in five phases – Preliminary 30%, 60%, 90%, Final and As-Built. Determination of this will be at the call order level.

The contractor shall not commence any installation tasks until the Government has reviewed and approved the final IDP submittal. The contractor shall advise the COR when the IDP has been completed to the following stages. The contractor shall develop all IDPs using AutoCAD and delivered in a standard AutoCAD format (.dwg) and delivered in a standard format. The product AutoCAD and Revit versions shall be current or within two versions of the current version.

6.2.5.1.1 IDP Phase/Types. The contractor shall be capable of developing and providing IDPs (CDRL A003) as follows:

6.2.5.1.1.1 Preliminary IDP (30%, 60%, and 90%). The first phase of the engineering design process is the development of a Preliminary IDP. The Preliminary IDP consists of System Specification and preliminary drawings and serves as the basic or preliminary technical reference governing the installation of systems, sub-systems, and equipment. It normally includes a listing of equipment or components to be installed, specifies preliminary design of the installation, describes the functions and the planned operation of the intended system, defines the required interface with existing and/or planned systems, details required support and test equipment, and details the facilities or physical plant requirements required to support the planned system installation. The Preliminary IDP describes an authoritative engineering plan and major equipment/components list 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.

Upon completion, the Preliminary IDP will represent 30%, 60%, and 90% drafts of the Final IDP as follows:

· Thirty Percent Preliminary IDP – General Documentation/Technical Report: The contractor shall deliver the 30% Preliminary IDP within the time specified in each call order PWS after the Site Survey is completed. The 30% Preliminary IDP shall consist of:

· Preliminary Title Sheet.

· Title.

· Drawing number.

· Preliminary Functional Interface Diagram.

· Preliminary Sheet Index.

· Preliminary Reference Documents.

· Preliminary Base Map.

· Preliminary Location Map.

· Preliminary Site Plan.

· Preliminary Master Lists:

· Master List of Equipment.

· Master List of Material.

· Master List of references.

· Master List of Legend, Acronyms and Abbreviations.

· Preliminary Floor Plans with Equipment Arrangements and Elevations.

· Preliminary Antenna Layouts and Elevations.

· Preliminary Simplified Block Diagram.

· Preliminary Cable Block Diagrams.

· Preliminary Cable Plant - Includes the plant conduit plan, plant cable plans, outside plant data.

Note: "Preliminary" indicates the contractor's first draft in which all known revisions and information have been incorporated.

· Sixty Percent Preliminary IDP – General Documentation/Technical Report: The contractor shall deliver the 60% Preliminary IDP within the time specified in each call order PWS after the Site Survey is completed. The 60% Preliminary IDP shall consist of:

· Updated Title Sheet.

· Title.

· Drawing number.

· Updated Functional Interface Diagram.

· Updated Sheet Index.

· Updated Reference Documents.

· Updated Base Map.

· Updated Location Map.

· Updated Site Plan.

· Updated Master Lists:

· Master List of Equipment.

· Master List of Material.

· Master List of references.

· Master List of Legend, Acronyms and Abbreviations.

· Updated Floor Plans with Equipment Arrangements and Elevations.

· Updated Antenna Layouts and Elevations.

· Updated Simplified Block Diagram.

· Updated Cable Block Diagrams.

· Preliminary Cable Running Sheets.

· Preliminary Circuit Diagrams.

· Preliminary Cable Routing Layouts.

· Updated Cable Plant.

· Preliminary Fabrication and Assembly Details.

· Preliminary Mechanical Assembly and Mounting Details.

· Corrected Drawings from the 30% Design Review.

· Note: The contractor shall be responsible for returning the NIW Atlantic review copy of the 30% preliminary IDP with the 60% Preliminary IDP submittal.

· Ninety Percent Preliminary IDP – General Documentation/Technical Report: The contractor shall deliver the 90% Preliminary IDP within the time specified in each call order PWS after the Government returns the 60% review comments. The 90% Preliminary IDP shall consist of:

· Completed Title Sheet.

· Completed Functional Interface Diagram.

· Completed Sheet Index.

· Completed Reference Documents.

· Completed Base Map.

· Completed Location Map.

· Completed Site Plan.

· Completed Master Lists:

· Master List of Equipment.

· Master List of Material.

· Master List of references.

· Master List of Legend, Acronyms and Abbreviations.

· Completed Floor Plans with Equipment Arrangements and Elevations.

· Completed Antenna Layouts and Elevations.

· Completed Simplified Block Diagram.

· Completed Cable Block Diagrams.

· Completed Cable Running Sheets.

· Completed Circuit Diagrams.

· Completed Cable Routing Layouts.

· Completed Cable Plant.

· Completed Fabrication and Assembly Details.

· Completed Mechanical Assembly and Mounting Details.

· Corrected drawings from the 60% review.

Note: The contractor shall be responsible for returning the NIW Atlantic review copy of the 60% preliminary IDP with the 90% Preliminary IDP submittal.

6.2.5.1.1.2 Final IDP. 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 will normally include a list of equipment. Utilizing a previously prepared Project Management Plan, or other provided reports or information, 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 CDRL of this contract document or as specified in the applicable call order PWS. Guidance or standard plans or drawings are considered inclusive of the installation drawings identified above.

· One Hundred Percent (Final) IDP – General Documentation/Technical Report: The contractor shall deliver the 100% Final IDP within ten (10) working days after the Government returns the 90% review comments. The 100% Final IDP shall consist of all corrected drawings from the 90% Preliminary IDP (a completed IDP). The contractor shall be responsible for returning the NIW review copy of the 90% preliminary IDP with the 100% IDP submittal.

A final submittal of the IDP with corrections from the 100% review shall be made to NIW within seven (7) working days of delivery of the Government’s comments for the 100% review. The final submittal will consist of three (3) sets of 11” x17” sized drawings, two (2) set of IDP AutoCAD drawings on separate Compact Disks. The contractor shall fully document the schedule for the IDP design submittals in the POA&M for the subject call order.

6.2.5.1.1.3 As-Built IDP and Incidental Construction Drawings. The last phase of the engineering design process is the development of the As-Built IDP. The contractor shall maintain two redline copies of the IDP during the course of the installation. During the course of an installation, the contractor shall update redlines daily to As-Built conditions, using red for all deletions and green for all additions. Upon installation completion, the contractor shall provide one redline copy to the designated call order COR who will deliver it to the customer to be retained at the installation site. The contractor shall photo copy the redline IDP and deliver the photocopy to the designated call order COR. The contractor shall retain the second set and use them to update the AutoCAD drawing files to reflect As-Built conditions. The contractor shall deliver the final As-Built IDP consisting of three (3) sets of 11” X 17” sized drawings, and two (2) sets of IDP AutoCAD drawings files on separate Compact Disks. All drawings shall be submitted in an editable AutoCAD format (.dwg) and/or Adobe Portable Document Format (.pdf) as specified in the call order.

6.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 call 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 call order.

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 procurement of the materials without approval from Government.

Deliverables:

6.3 Task 3. Software Engineering.

If required on a call order, Systems of Systems (SoS) 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 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 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 SDP with corrections within ten (10) business days or the due date to be specified in a call order. 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 call order/project. As required, the Government will identify specific SDP project requirements at the call order level.

Deliverables:

6.4 Task 4. Cybersecurity.

If required on a call order, the contractor shall develop Cybersecurity artifacts that are compliant with the relevant 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. 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.

· System Enterprise and Information Security Architecture Diagram.

· System Authorization Boundary (Defense Information Systems Agency (DISA)- Connection Process Guide compliant diagram).

· Information Flows/Paths.

· Security Assessment Plan (SAP).

· Test Plan (Cybersecurity Component of SOVT).

· Security Categorization Form/RMF Step 1.

· Identified Inheritable Controls/RMF Step 2.

· Security Technical Implementation Guides (STIG) 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 Defense Cyberspace Work Force (DCWF) includes all contractor personnel who perform cyberspace work. IAW DFARS Subpart 239.71 and DoD Directive (DoDD) 8140.01 contractor personnel performing cybersecurity functions shall adhere to the procedures defined in DoD MANUAL 8140.03 for the qualification of personnel identified as members of the DoD cyberspace workforce. Contractor personnel shall meet workforce qualification requirements prior to the start of the call order performance period or before assignment to the call order during the performance period and a member of the DCWF.

DCWF contractor personnel shall perform cyberspace work. IAW DOD MANUAL 8140.03 Cyberspace Workforce Qualification and Management Program, the DCWF is comprised of numerous qualification areas. The contractor shall be fully qualified in the qualification area by qualification standards and requirements IAW DoDD 8140.01 and 8140.03.

The contractor shall support and follow DoD Instruction (DoDI) 8510.01 when deploying, integrating, and implementing IT capabilities. The contractor shall support Government personnel to ensure compliance with all current USMC 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 Code of Federal Regulations (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 IAW the latest DoD and USMC 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 IAW latest 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 USMC 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 IAW established DoD/USMC 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. IAW DoD RMF and NIWC-Atlantic guidance documents, RMF is comprised of the following six Steps: Step One – Categorize, Step Two – Select, Step Three – Implement, Step Four – Assess, Step Five – Authorize, Step Six – Monitor. The contractor shall perform the ISSE role within Enterprise Mission Assurance Support Service pursuant to DoD, USMC, and Army.

DOD MANUAL 8140.03 and DFAR’s Procedures, Guidance, and Information (PGI) 239.7102-3 have promulgated that contractor personnel shall have documented current Cyberspace Workforce Qualification status within their contract. The contractor shall develop, maintain, and submit a DCWF Report monthly or as required at the call order level (Note: If initiated at the call order level, report is not necessary at contract level). IAW clause DFARS 252.239-7001, if Cyberspace Workforce support is provided, the contractor shall provide a DCWF list that identifies those individuals who are Cyberspace Workforce 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.

Deliverables:

Service List

6.5 Task 5. Equipment/Material Procurement.

If required on a call order, the contractor shall procure incidental materials to support the IT installation. The contractor shall be responsible for material logistical aspects (crating, agricultural inspection, insurance, customs (if applicable), inspection, secure shipment practices, shipping, etc.) of all Contractor Furnished Equipment (CFE) and Contractor Furnished Material.

6.5.1 Subtask 1 – Procurement. The contractor shall ensure acquisition selection factors include price, availability, reliability, and supportability within current supply system. The contractor shall keep source selection records and make them available for Government review as needed. The contractor shall provide all data and cost estimate necessary to justify a fair and reasonable price per item procured. The contractor shall have an adequate accounting system to track all items and the delivery status. The contractor shall have an adequate property management system to track the items and locations. The contractor shall store all items procured at the contractor’s facilities and ensure they are integrated into a system or transported by the contractor to the Government specified location. The contractor shall generate inventory tracking report(s). The contractor shall provide additional deliverable documentation per Government direction.

The contractor shall recommend items that conform to applicable product validation, identification, and tracking requirements.

· Equipment/Material Research – The contractor shall research specified equipment and/or material within the parameters of this contract.

· Product Certification – The contractor shall be a registered and certified integrator, partner, or Value-Added Reseller for the systems at the level required by the call order prior to submitting bids or within the time stipulated by the request for proposal. The contractor shall maintain required partnerships throughout the length of the call orders.

· Product Validation – The contractor shall certify that it purchases supplies from authorized resellers and/or distributers. Unless otherwise specified, the contractor shall certify that the products are new, in their original box. The contractor shall obtain all manufacturer products submitted in task/delivery order offers from authentic manufacturers or through legal distribution channels only, IAW all applicable laws and policies at the time of purchase.