N66001-19-R-0035.pdf

CODE

(Hour)

PAGE(S)

until local time

X

A

X B

C

D

EX

X

G

F 37 - 49

50 - 64

H 65 - 68

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA

FAR (48 CFR) 53.214(c)

1 68

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N66001 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 17

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

19 - 20 X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 21 - 23 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror)

X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

24 - 35

PART II - CO NTRACT CLAUSES

NAVAL INFORMATION WARFARE CENTER PACIFIC

JOSE NETO, CODE 22550

JOSE.NETO@NAVY.MIL

53560 HULL STREET

SAN DIEGO CA 92152-5001

619-553-0901

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

30 Aug 2019

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6600119R0035

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Lot Engineering Services

CPFF

Base Period - 2 years

ADNS engineering services to be specified at the Task Order level in accordance with the PWS in Section C, herein.

FOB: Destination

PSC CD: R425

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 1 Lot Other Direct Costs (ODCs)

COST

Incidental material, travel, and other non-labor costs required in the performance of the service, not to include subcontractor and consultant costs.

Contract Data Requirements Lists (CDRLs)

Data in accordance with the DD Form 1423s as specified at the Task Order level.

Not Separately Priced (NSP)

1001 1 Lot OPTION Engineering Services

Option Period 1 - 2 years

1002 1 Lot OPTION Other Direct Costs (ODCs) of the service, not to include subcontractor and consultant. costs

OPTION Contract Data Requirements Lists (CDRLs)

2001 1 Lot OPTION Engineering Services

Option Period 2 - 2 years

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

2002 1 Lot OPTION Other Direct Costs (ODCs) of the service, not to include subcontractor and consultant. costs

MAX COST

OPTION Contract Data Requirements Lists (CDRLs)

3001 1 Lot OPTION Engineering Services

Option Period 3 - 2 years

3002 1 Lot OPTION Other Direct Costs (ODCs)

OPTION Contract Data Requirements Lists (CDRLs)

4001 1 Lot OPTION Engineering Services

Option Period 4 - 2 years

4002 1 Lot OPTION Other Direct Costs (ODCs)

Option Period 4- 2 years

OPTION Contract Data Requirements Lists (CDRLs)

Option Period 4 - 2 years

PWS

Performance Work Statement (PWS)

For

Automated Digital Network Systems (ADNS) Engineering Support Services

1.0 SCOPE

The Routing and Wide Area Networking Code 55160 and Routed Networks Integration & Test Code 55170 at Naval

Information Warfare Center , Pacific (NIWC Pacific) has identified a requirement for engineering, technical and programmatic services for communication and networking systems, and associated certification and information assurance for developments, current operations and planned upgrades to support engineering efforts for Program

Management Warfare (PMW) 160 Tactical Networks. The communication and networking systems described and referred to in this Performance Work Statement (PWS) are specialized tactical afloat network systems that enable

Command and Control (C2) in Naval/Joint/Coalition operations, providing the gateway to achieving information dominance in the cyberspace domain.

NIWC PAC Codes 55160 and 55170, establishes plans, manages and executes communication, networking and information assurance aspects for programs and projects in support of Department of Defense (DoD) requirements as well as associated composite programs. This begins at the concept formulation stages and extends through experimentation, system validation, fleet installation and operational support across the full life cycle of program development from concept formulation, technology development, engineering and manufacturing, production and deployment, operational support and sustainment, and finally disposal. It includes performing requirement analysis, hardware and software design, system engineering, system and sub-system design and integration, test and evaluation, risk analysis, schedule monitoring and technical management throughout the scope of the project or program. In addition, systems engineering practices include considerations for reliability, maintainability and affordability using proven best practices.

NIWC PAC Codes 55160 and 55170 maintain and support the infrastructure and test-beds needed to develop, demonstrate, and test concepts and capabilities to ensure high quality products and results. In addition, both codes develop and execute integrated applied and advanced research to technology programs. Acting as the NIWC technical authority for afloat networks, it provides technical leadership, technical expertise and consultation to the acquisition and Research Development Test & Evaluation (RDT&E) communities, military offices, commands and operational forces.

2.0 APPLICABLE DOCUMENTS

The following documents may be incorporated for individual delivery/task orders. Nothing in the documents however, shall supersede applicable laws and regulations, unless a specific exemption has been obtained. The

Contractor’s solution shall comply with current documentation, standards and guidance as outlined in each task order. Any additional MIL Documents, used in the individual delivery/task orders, shall have been reviewed IAW

DOD 4120.24-M, Defense Standardization Program (DSP) Policies and Procedures, and USD Policy Memo 05-3.

2.1 Optional Military Standards

The following documents are referenced as guidance only. The following documents form a part of the PWS to the extent specified herein. Unless otherwise specified, the issues of the documents below shall be those listed in the

Department of Defense (DoD) Index of Specifications and Standards and supplement thereto, cited in the solicitation. The document used shall be the issue in effect at the date of award.

a) MIL-STD-461E Requirements for the Control of Electromagnetic Interference

Characteristics of Subsystems and Equipment

b) MIL-STD-449D Measurement of Radio Frequency Spectrum Characteristics

c) MIL-STD-961E Defense and Program-Unique Specifications Format and Content

d) MIL-STD-1472F Human Engineering

e) MIL-STD-1686C Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices) (Metric)

f) MIL-STD-1553B Digital Time Command/Response Multiplex Data Bus

2.2 Optional Military Handbooks

The following documents are referenced for guidance only. Nothing in this document or listed reference documents supersedes applicable laws and regulations unless a specific exemption has been obtained from the Government.

a) MIL-HDBK-881A Work Breakdown Structures for Defense Material Items

b) MIL-HDBK-61A Configuration Management Guidance

c) MIL-HDBK-470A Designing and Developing Maintainable Products and Systems

d) MIL-HDBK-454B General Guidelines for Electronic Equipment

e) MIL-HDBK-2036 Preparation of Electronic Equipment Specifications

f) MIL-HDBK-419A Grounding Bonding and Shielding for Electronic Equipment and Facilities Basic

Theory

2.3 Other Optional Publications

The following documents are referenced for guidance only. Nothing in this document or listed reference documents supersedes applicable laws and regulations unless a specific exemption has been obtained from the Government.

a) IEEE-1220-2005 Standard for Application and Management of the Systems Engineering Process

b) ISO/IEC-15288 (Revision 02) Systems Engineering – System Life Cycle

a. Processes

c) ANSI/EIA-632 Processes for Engineering a System

d) IEEE/EIA-12207.0 Standard for Information Technology – Software Life Cycle Processes

e) IEEE/EIA-12207.1 Standard for Information Technology – Software Life Cycle Processes – Life Cycle

Data

f) IEEE/EIA-12207.2 Standard for Information Technology – Software Life Cycle Processes –

Implementation Considerations

g) ANSI/EIA-649A National Consensus Standard for Configuration Management

Applicable documents will be added at the task order level and may include military standards, military handbooks, software development guidance, and other publications and will be referenced in individual task orders as required.

3.0 PERFORMANCE REQUIREMENTS

3.1 Technical Requirements

Under NIWC Pacific Transport and Computing Infrastructure (TCI) Portfolio construct, NIWC Pacific Codes 55160 and 55170 anticipate work that will include Surface Ashore, Surface Afloat, Submarine Shore, Submarine

Platforms, Airborne Shore, Airborne Platforms, Mobile, Joint, and Federal Infrastructure business areas with specific technologies such as network design and development, network monitoring, management and operations, common computing environment, infrastructure with associated hardware and software components, cloud computing, ashore and afloat data centers and server hosting environments, consolidated network enterprise services, wireless networking, and tactical, satellite and joint space communications. Transformation of a capabilities-based portfolio into a networked infrastructure enables Information Dominance through Navy and Joint net-centric operations.

Aligned with Program Executive Office (PEO) C4I Master Plan, three tenets guide the transition to a net-centric infrastructure:

Mission-centered (Mission): The TCI portfolio of systems is evolving to support the Navy’s focus on cross-functional mission execution in accordance with Naval Operation Concept for Joint Operations and the Chief of

Naval Operations (CNO) Information Dominance Vision. Careful consideration is being given to approved and evolving mission threads in order to validate the relevance of the portfolio over time. Key operational threads include: Anti-Submarine Warfare (ASW); Ballistic Missile Defense (BMD); Close Air Support (CAS); Commander

Joint Task Force (CJTF); Intelligence, Surveillance and Reconnaissance (ISR); Tasking, Collection, Processing, Exploitation, Dissemination (TCPED); Joint Force Maritime Component Commander (JFMCC); Maritime Domain

Awareness (MDA); Maritime Interdiction (MI)/Anti-Surface Warfare (ASuW); Navy Networking Environment

(NNE); and Anti-Access Area Denial (A2AD). The end objective is to deliver capabilities and services that are available upon demand and integrated in the context of the mission(s) to be executed, with the infrastructure supporting all mission applications being nearly transparent to the war fighter.

Standards-compliant (Technical): The transition is based on a standards-based open architecture that shall readily adapt to the incorporation of future technologies, shall facilitate the retirement of legacy capabilities, and shall reduce the facilities required to house legacy capabilities, resulting in significant savings in the long term.

Furthermore, adherence to standards contained within the DoD Information Technology Standards Repository

(DISR) (https://disronline.disa.mil) and the Net-Centric Enterprise Solutions for Interoperability (NESI)

(http://nesipublic.spawar.navy.mil) shall enable the development of interoperable net-centric capabilities. Ongoing standards collaboration with the Intelligence Community (IC) is critical to promoting data interoperability between

DoD and IC systems through the implementation of shared cloud architectures and associated standards. Finally, commercial standards and best practices, such as those being developed by American National Standard Institute

(ANSI) under the Network Centric Operations Industry Consortium (http://www.ncoic.org/), shall be leveraged to guide the technical implementation of DoD’s net-centric and data-centric capabilities.

Directives-compliant (Programmatic): In order to deliver networked systems that are compliant with the latest policies, guidance and direction, focus of efforts shall leverage the following documentations:

a) Global Information Grid Architecture v2.0,

b) DoD Net-Centric Data Strategy,

c) DoD Architectural Framework v2.0,

d) DODI 5000.02, CJCSI 3170.01H which is the new update to the Joint Capabilities Integration and

Development System (JCIDS) instruction,

e) CJCSI 6212.01E which prescribes Net-Ready Key Performance Parameter (NR-KPP) compliance

f) Other technical directives and initiatives from DoD and DoN.

Systems Engineering for Networks and Communications: Systems engineering comprises the full scope of work from solution analysis, technology development, engineering and manufacturing development, production and deployment, operations and support across the complete end-to-end system and across the complete life cycle, in support of projects and programs for ships, submarines, aircraft, unmanned systems and shore facilities.

Solutions Analysis: The objective of Solution Analysis is to select and adequately describe a preferred materiel solution to satisfy the requirements of the stakeholders. A high level system model/architecture and preliminary system performance specification are developed, and establishes a basis for Technology Development.

Technology Development: The objective of Technology Development is to reduce technical risk and develop a sufficient understanding of the materiel solution to support sound decisions leading into Engineering and

Manufacturing Development. This includes maturing technology, prototyping system elements, and refining requirements, specifications, interfaces and system model/architectures.

Engineering and Manufacturing Development: The objective of Engineering and Manufacturing Development is to develop the detailed product baseline, verify it meets the system functional requirements, transform the preliminary design into a producible design, assess risk levels for the system, and prepare for production or deployment.

Production and Deployment: The objective of Production and Deployment is: to validate the product design and to deliver the quantity of systems required for full operating capability, including all enabling system elements and supporting material and services, delivery of the final product baseline as validated during operational testing, and support for the deployment and transition of capability to all end users, the warfighters, and supporting organizations. The maintenance approach, training, and technical manuals, should be integrated with Production and

Development along with specific test and evaluation as well as logistics and sustainment activities.

Operations and Support: The objective of Operations and Support is to execute a support program that meets operational support performance requirements and sustains the system in the most cost-effective manner over its total life cycle.

The following requirements comprise the scope of the anticipated Systems Engineering efforts to support NIWC

Pacific Codes 55160 and 55170 in their work related to networks and communications to enable net-centric capabilities of controllers, sensors, processors, monitoring and management components, platforms and installations across enterprise domains.

3.2 Systems Engineering: Capabilities, Requirements, and Assessments

3.2.1 Capabilities, Requirements and Assessments

The contractor shall analyze the capabilities and environmental constraints of network and communication systems identified by users, sponsors or stakeholders, and generate performance and functional requirements to realize those capabilities. The solution may be for a new project or upgrade to an existing system. The contractor shall decompose high level requirements into functional definitions, verification objectives, and full system specifications, identifying, enabling and critical technologies, constraints and risks. The contractor shall assess and analyze system concepts, functional capabilities, and performance specifications and validate against user needs. Assessments include system specifications, safety considerations, maintenance concepts, cost and manpower estimates, testing and support strategies, and feasibility studies of the impacts of integrating new capabilities or technology into existing or currently fielded systems.

The Contractor shall specify, design, develop, code, test, integrate and document software modules systems and subsystems to provide new functional capabilities and improve existing Naval Networking and Communications systems. The Contractor shall perform reverse engineering of software components and systems to support vulnerability and exploitation analysis. The functions to be implemented include the full spectrum of Naval

Networking and Communications Operations. The Contractor shall adhere to current standards and modern software development methodologies, including rapid prototyping to meet time critical requirements.

3.2.2 Science &Technology

The contractor shall support Science and Technology (S&T) research and generate concepts, designs and models that will realize future objectives and requirements. Research will push state-of-the-art capabilities enabling advances that will yield superiority for the warfighter, especially in the area of Information Dominance.

3.3 Systems Engineering: Architecture Research and Design

A detailed architecture design establishes the initial building blocks and framework for a project demonstration or a system deployment, and shall address all interfaces and interactions internal and external to the system.

3.3.1 Enterprise Level

The contractor shall develop enterprise level architectures that address and are consistent with DoD rules and policies to provide frameworks for data, application, technology and business strategies and that are technically feasible and responsive to changing mission needs. The contractor shall mature technology to higher readiness levels. The contractor shall produce DoD Architecture Framework (DoDAF) documents showing integrated architectures across multiple views.

3.3.2 Tactical Level

The contractor shall develop architectures that extend to the tactical level and may transverse the GIG which shows interfaces and connectivity between shore terrestrial locations and forward deployed nodes either stationary or mobile. This would include components, interfaces, software to achieve system requirements and insure compatibility across the DoD enterprise, and with other tactical users.

3.3.3 System Level

The contractor shall design systems for reliability, maintainability, and supportability, which reduce the overall program risk from the viewpoint of cost, schedule and performance. The contractor shall provide redesign plans for improvements to capabilities of next generation systems.

3.4 Systems Engineering: Engineering Development

3.4.1 Network and Communication Development

The contractor shall develop, build and integrate the components and sub-systems required to realize capability requirements and/or designed system architectures.

The contractor shall develop software and applications required to realize designed system functionality and capability.

The contractor shall develop, build and integrate networking and processing capabilities in virtualized environments utilizing emerging technologies.

3.4.2 Integration with Communication Systems

The contractor shall perform systems engineering and technical analyses to support the integration of communications connectivity via commercial or military Satellite Communications (SATCOM) systems, and direct

Line of Sight (LOS) communication systems with existing and future networks. Engineering development shall extend to multi-band commercial systems, components, antennas including low observable multi-function antenna systems, as well as electromagnetic interference evaluation of platforms and facilities to ensure electromagnetic compatibility.

3.4.3 Improvements and Technical Evaluations

Based on technical evaluations and reviews, the contractor shall re-design sub-systems or systems for better functionality, reliability and sustainability that mitigate risk in planned operations.

3.4.4 Engineering Documentation and Reviews

The contractor shall perform documentation and distribution of engineering and computer related information. The contractor shall develop block diagrams, technical sequences, flow charts, and work breakdown structures. The contractor shall develop, modify, and/or update specifications; Computer Aided Design-Computer Aided

Manufacturing (VISIO) and manual wiring diagrams; top-level assembly drawings and detailed design drawings;

parts lists, assembly breakdown lists; interface control documentation to describe the physical, functional, and performance interfaces; and hardware, software, and system-level performance requirements.

The contractor shall develop technical documentation for new and ongoing systems. Documentation shall include preparing or updating: Analysis of Alternatives (AoA), System Design Document (SDD), Template Change

Document (TCD), Device Templates, Bill of Materials (BoM), Version Description Document (VDD), Simplified

Network Drawings (SND), Detailed Network Drawings (DND), Network Connections and Configuration Matrix

(NCCM), Port Jack Layout, Tool Kits, Platform System Configuration Matrix (PSCM), System and Platform

System Operational Verification Test (SOVT), test plans, test reports, implementation plans, recommendations, bulletins, outlines and white papers. The contractor shall develop documentation for information systems and associated interfacing systems.

The contractor shall develop and/or provide inputs to: System Engineering Plans (SEPs), Engineering

Implementation Plans (EIPs), Site Telecommunications Engineering Development Plans (STEDPs) required for

Navy communications sites, and other engineering documentation required to satisfy coordination and tasking for networks and communications system implementation.

The contractor shall support technical and programmatic reviews in preparation for Milestone Decisions and other program events.

3.4.5 Security Controls and System Scanning Support

The contractor shall perform and document vulnerability assessments to identify weaknesses in the system that can be exploited and the necessary mitigations to overcome them, documented in a Plan of Action & Milestones

(POA&M). Assessments shall be of system design, development, production or operations relating to network infrastructure. The contractor shall conduct Certification Test & Evaluation (CT&E) and Security Test & Evaluation

(ST&E) on networks and connected devices to determine whether all applicable Security Controls are satisfied, and findings are corrected, remediated or mitigated.

The contractor shall ensure all applicable Information Assurance Vulnerability Alerts (IAVAs) have been addressed and security updates are current, as well as remediate additional findings discovered during testing or received through agency announcements.

3.5 Systems Engineering: Developmental Testing

The contractor shall perform and/or participate in testing of hardware and/or software developed by contractor or government developers in government designated facilities, test ranges, planned exercises or field tests.

The contractor shall support test director in monitoring, measuring, recording and reporting events incorporated in planned testing, including Test Readiness Reviews (TRRs). The contractor shall participate in Developmental Test

& Evaluation (DT&E), and document test results of enterprise-wide systems, information systems, network components, equipment, and subsystems with interfacing C4ISR systems aboard ships, submarines, aircraft, unmanned systems and shore facilities. The contractor shall analyze and identify causes of problems and failures and report corrective actions or measures. The contractor shall support Operational Assessments (OAs).

3.6 Systems Engineering: Operational Testing and Evaluation

The contractor shall support Operational Test and Evaluation (OT&E) and Follow-on OT&E (FOT&E) and all other types of testing mandated to achieve full deployment or fielding.

The contractor shall support evaluation of effectiveness, suitability and/or survivability.

3.7 Systems Engineering: Production Documentation and Reviews

3.7.1 Configuration Support

The contractor shall complete and finalize all documentation required for system production and deployment, include schematics, architectures, interface drawings, and configuration management data.

The contractor shall develop, implement and maintain configuration management, including configuration audit plans covering hardware and software in an integrated approach. The contractor shall verify and maintain complete and accurate configuration identification of each Configuration Item (CI) or Computer Software Configuration Item

(CSCI) and government-approved, established Functional, Allocated, and Product baselines for equipment or systems.

3.7.2 Baseline Documents and Databases

The contractor shall draft and update baseline documents related to systems engineering which include documents referenced in Section 3.4.4 in addition to Test Readiness Reviews (TRRs) and Developmental Test & Evaluation

(DT&E) system concepts, system configurations, specifications, reports, accreditation documents, line drawings, Standard Operating Procedures (SOPs), architecture drawings, equipment lists, manufacturing processes or procedures, test and inspection plans or procedures, surveys, quality assurance provisions, inspection and test equipment requirements, packaging lists, software documentation, training manuals, maintenance and supply documentation. The contractor shall input or update similar information in established databases for retention, tracking or maintenance of critical information and configurations.

3.7.3 Configuration Status Accounting

The contractor shall provide configuration status accounting, which shall delineate the status of changes from the baseline, the status of proposed changes, and the status of implementation of approved changes. Configuration accounting shall be achieved through utilization of CMPro database, or an approved application as authorized by

NAVWAR.

3.8 Systems Engineering: Installation

The contractor shall support site visits, develop site in-briefs and out-briefs, develop site survey checklists, generate installation schedules and identify potential risks.

The contractor shall evaluate operational impact due to planned installations and advise on the best course of action to minimize disruptions.

The contractor shall provide input to, review and modify Installation Design Plans (IDPs) as required for Fleet

Readiness Certification Board (FRCB) submission. IDP shall include as block diagram, rack elevations, Heating, Ventilation, & Air Conditioning (HVAC) and power calculation, cabling and connector information, BoM, cable running sheets, final as-built drawings and all other required installation documentation.

The contractor shall generate, identify and verify material lists or BoMs, deliver required equipment and incidental materials necessary to complete the site installation, system integration or upgrade.

The contractor shall perform installation and integration of components or equipment, subsystems, systems, and networks in facilities, ships, submarines, aircraft or unmanned platforms. The contractor shall perform testing and troubleshooting to determine whether the installation has met stated objectives, and perform any corrections or modifications required to achieve full functionality and installation requirements.

The contractor shall support in the creating, planning and execution of System Operational Verification Tests

(SOVTs) in accordance with NIWC 5.0 processes as the final check-out demonstrating a successful, functional installation.

3.9 Systems Engineering: Operational Support to Platforms or Facilities

The contractor shall participate in the maintenance and support of platforms or facilities to ensure continued operations, including following logistics support plans to ensure parts and repair functions.

The contractor shall perform operability support, system configuration testing support, troubleshooting at the component to device level, software loading and updating, system monitoring and failure analysis, and recommendations for improved reliability.

The contractor shall provide system administration to address network and computer security updates quarterly, at a minimum, and maintain overall system security within compliance.

3.10 Systems Engineering: Upgrades

The contractor shall provide system modernization support through technical inputs, participation in system modernization planning.

The contractor shall utilize the Enterprise Change Request (ECR) process and control mechanism to implement upgrades and improvements to operational systems, and support the efforts necessary to complete these processes.

The contractor shall provide analysis and problem resolution study results supporting the improvement of specified networks, communication or information systems. The contractor shall provide inputs to system integration and interoperability requirements for new or enhanced Commercial off the Shelf (COTS) / Government off the Shelf

(GOTS) products. The contractor shall provide reports showing the impacts of changes to baseline hardware and software.

3.11 Systems Engineering: Program and Project Management Support

The contractor shall provide technical and programmatic input and participate in the development of the Integrated

Defense Acquisition and Technology for Navy, Joint and Coalition communications and networked systems.

The contractor shall participate in technical working group as well as technical interchange and integrated product team (IPT) planning meetings, preparing briefs and keeping meeting minutes. The contractor shall work with and advise on process improvement.

3.11.1 Network Timing Support

The contractor shall provide network timing support for all network systems utilizing current and future timing technologies.

3.12 Process Improvement Planning

The contractor shall work collaboratively with NIWC Pacific Codes 55160 and 55170 to establish and implement a

Process Improvement Plan to improve the state of service management and engineering practices based on assessments of identified projects. The plan shall detail a logical set of activities to: (1) Improve service management and engineering processes to address the strengths and weaknesses of the organization identified in the initial appraisal; (2) Monitor progress throughout the improvement initiative; and (3) Rate the organization's maturity once a defined set of process areas have been improved. The plan shall delineate: the appropriate Program

Management Guide and the Capability Maturity Model Integration (CMMI) process areas most applicable to the organization based on the initial appraisal; the objectives of the organization; and the availability of resources within the organization. Furthermore, the plan shall identify the processes for the organization to address within the CMMI for Services categories which are: Process Improvement, Project and Work Management, Support, Service

Establishment and Delivery, and Engineering. The plan shall identify activities, resources and timeframes needed to execute critical improvement activities to help the organization prepare for operational assessments.

3.13 Software

3.13.1 Application Integration and Application Development

The contractor shall investigate, analyze and document application requirements in a feasibility assessment for each application, and shall provide the data needed for the ADNS, Legacy and Application Integration engineering teams to ensure the Navy application provider’s requirements are met.

The contractor shall review the System of System (SoS) architectures as designed and ensure alignment of applications with the ADNS Functional Specification, as well as recommend updates to either the application or the

ADNS Program technical documentation.

4.0 CYBER SECURITY

4.1 Cyber Security Work Force

Cyber Security Work Force (CSWF) certifications are required for contractor personnel under this contract. All IA functions to be performed under this contract will be identified at the task order level in the performance work statement. Task order performance work statements will specify, as applicable: IA workforce category, level, training, and certification requirements for contractor personnel with privileged access working in IA Technical

(IAT) environments, IA Management (IAM) personnel with significant IA tasks, Computer Network Defense

Service Providers (CND-SPs), and IA Systems Architects and Engineers (IASAEs). Task orders with IA functions will include a requirement for the contractor to report IA certification status and compliance.

4.1.1 CSWF Personnel

The Contractor shall ensure personnel supporting this contract who are performing IA functions that are designated as IA Workforce positions IAW DoD 8570.01-M shall be trained and certified in accordance with DFARS Clause

252.239-7001 Information Assurance Contractor Training and Certification. The contractor shall follow

SECNAVINST 5239.3A of 20 Dec 2004 & DoD 8500.2 of 6 Feb 2003 when performing IA tasks orders. The

Contractor shall meet applicable information assurance certification requirements, including (1) DoD‐approved IA workforce certifications appropriate for each specified category and level and (2) appropriate operating system certification for information assurance technical positions as required by DoD 8570.01‐M.

4.1.2 CSWF Certifications

The contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions, reporting current IA certification status and compliance using a CDRL

Contractor Roster, Data Item Description # DI‐MGMT‐81596, for individual task/delivery orders. Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

4.2 Systems Engineering: Cyber Security Certification and Accreditation (C&A)

The contractor shall provide results, documentation, mitigation, schedules and plans to ensure the Information

Assurance posture meets required policy and that required authorizations are obtained and maintained.

4.2.1 DoD Information Assurance Certification and Accreditation Process (DIACAP)/Risk Management

Framework (RMF)

The contractor shall develop, review or modify submission documentation for Interim Authority to Test (IATT) approvals to allow systems to test in simulated operational environment; or to use live data for a specific time period when specific test objectives cannot be met in a test environment.

The contractor shall develop, review or modify submission documentation for Interim Authority to Operate (IATO) or Authority to Operate (ATO) approvals, through execution of RMF packages and provide support during collaboration of risk determination to achieve full package approval.

RMF packages include: RMF Scorecard; Navy System Identification Profile (SIP); C&A plan; system description, diagrams and topologies; description of protections in place both physical and internal; Ports, Protocols and Services

(PPS) list; Logical Network Diagram (LND) description; interdependencies; test plans, schedules, environments, configurations, locations and results of the proposed tests (i.e. Security Scans, Security Technical Implementation

Guides (STIGS) etc.); and a Plan of Actions and Milestones (POA&M). Additional items may be added by accrediting authorities.

The contractor shall input all artifacts into Enterprise Mission Assurance Support Service (eMASS) or the current, approved database for tracking C&A compliance.

The contractor shall create documentation of Assessment and Authorization (A&A) that meet the submission requirements found within the RMF. The contractor shall follow the RMF activities to ensure security controls are implemented and information system security policy is being followed.

The contractor shall ensure that security posture of the configuration baseline meets requirements stated in all applicable DoD/DoN security documents.

5.0 TRAVEL

During the effort, travel is anticipated to the following CONUS and OCONUS locations and applies to the base period and each option period of performance exercised by the Government:

Destination Days Travelers Trips

Wahiawa, HI 10 2 10

Naples, IT 10 1 3

Manama, Bahrain 10 1 3

Providence, RI 10 1 2

Charleston, SC 10 1 2

Norfolk, VA 10 2 10

5.1 Foreign Travel Requirements

If foreign travel is required, all outgoing Country/Theater clearance message requests shall be submitted to the

NIWC Pacific foreign travel team, Topside, Building 27, 2nd Floor – Room 206 for action. A Request for Foreign

Travel form shall be submitted for each traveler, in advance of the travel, to initiate the release of a clearance message at least 40 days in advance of departure. Each Traveler must also submit a Personal Protection Plan and have a Level 1 Antiterrorism/Force Protection briefing within one year of departure and a country specific briefing within 90 days of departure. Anti-Terrorism/Force Protection (AT/FP) briefings are required for all personnel

(Military, DoD Civilian, and contractor) per OPNAVINST F3300.53C. Contractor employees must receive the

AT/FP briefing annually. The briefing is available https://atlevel1.dtic.mil/at/, if experiencing problems accessing this website contact ssc_fortrav@navy.mil. Forward a copy of the training certificate to the previous email address or fax to (619) 553-6863; SERE 100.1 Level A Code of Conduct training is also required prior to OCONUS travel for all personnel. SERE 100.1 Level A training can be accessed at https://www.nko.navy.mil. Other specialized training for specific locations may also be required; contact the NIWC Pacific foreign travel team.

6.0 GOVERNMENT FURNISHED EQUIPMENT / INFORMATION

The Government will provide the contractor access to information and documentation (relative to the requirements) within 10 days of written request. NIWC Pacific will provide contractor personnel access to development, installation, and maintenance sites to support the efforts outlined in Paragraph 3.0 of this document.

7.0 SECURITY

The security requirement for this tasking will be Secret. The work performed by the Contractor will include access to unclassified and Secret data, information, meetings, and spaces. Individual task orders awarded under this basic contract will specify security clearance level required for contractor personnel. The security clearance of the contractor personnel assigned to the task order must be appropriate for the associated Secret material/equipment.

Individual task orders may also require contract personnel to be North Atlantic Treaty Organization (NATO) briefed and complete the derivative classification training prior to being granted access to the Secure Internet Protocol

Router Network (SIPRNet); training is provided by the facility security officer.

As required by National Industrial Security Program Operating Manual (NISPOM) Chapter 1, Section 3, contractors are required to report certain events that have an impact on: 1) the status of the facility clearance (FCL); 2) the status of an employee's personnel clearance (PCL); 3) the proper safeguarding of classified information; 4) or an indication that classified information has been lost or compromised. Contractors working under NIWC Pacific contracts will ensure information pertaining to assigned contractor personnel are reported to the Contracting Officer

Representative (COR)/Technical Point of Contact (TPOC), the Contracting Specialist (CS), and the Security's COR in addition to notifying appropriate agencies such as Cognizant Security Agency (CSA), Cognizant Security Office

(CSO), or Department Of Defense Central Adjudication Facility (DODCAF) when that information relates to the denial, suspension, or revocation of a security clearance of any assigned personnel; any adverse information on an assigned employee's continued suitability for continued access to classified access; any instance of loss or compromise, or suspected loss or compromise, of classified information; actual, probable or possible espionage, sabotage, or subversive information; or any other circumstances of a security nature that would affect the contractor's operation while working under NIWC Pacific contracts.

Applicable documents: SECNAVINST 5510.30 (Series), Department of Navy Personnel Security Program, 06/2006

SECNAVINST 5510.36 (Series), Department of Navy Information Security Program, 06/2006, OPNAVINST

F3300.53C (Series), Navy Antiterrorism Program DOD 5200.01 Volumes 1 through 4 (Series), DOD Security

Program, DOD 5220.22-M (Series), and National Industrial Security Program Operating Manual (NISPOM)

Operations Security (OPSEC): OPSEC is a five step analytical process (identify critical information; analyze the threat; analyze vulnerabilities; assess risk; develop countermeasures) that is used as a means to identify, control, and protect unclassified and unclassified sensitive information associated with U.S. national security related programs and activities. All personnel working under this task will at some time handle, produce or process Critical

Information or Critical Program Information, and therefore all Contractor personnel must practice OPSEC. All work is to be performed in accordance with DoD OPSEC requirements, and in accordance with the OPSEC attachment to the DD254.

Applicable documents: National Security Decision Directive 298 (Series), National Operations Security Program

(NSDD) 298, 01/22/88, DOD 5205.02 (Series), DOD Operations Security (OPSEC) Program, 11/03/08, OPNAVINST 3432.1 (Series), DON Operations Security, 11/04/11, SPAWARINST 3432.1 (Series), Operations

Security Policy, 02/02/05.

8.0 OTHER

8.1 Enterprise Contractor Manpower Reporting Application (ECMRA)

The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the NIWC Pacific via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom-Telecommunications Transmission

(D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address https://www.ecmra.mil/.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year

(FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://www.ecmra.mil/.

For purposes of ECMRA reporting, the Product Service Code applicable to the contract/order is D316.

8.2 Deliverables

Data deliverables will be specified in the Contract Data Requirements List (CDRL), DD 1423-1 for individual Task

Orders.

8.3 Network Access

Contractors, including sub-contractors, will require access to classified networks to perform and complete the work authorized under this contract. Access will include connectivity to Secret level networks (i.e. SIPRnet, etc.), and may include assess to web-sites, databases, email or other applications deemed necessary. Network access is only required at government facilities.

8.4 Communication Security Material System

Communication Security Material System (CMS) access will be required for work on this contract.

8.5 Contractor Employee Identification

Contractor employees shall identify themselves as contractor personnel by introducing themselves or requesting they be introduced as contractor personnel and display distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and formal and informal written correspondence.

8.6 Place of Performance

The government will provide access to the Automated Digital Network System (ADNS) Development Test Lab, Buildings – 596, 620, 623 and 660, at the Monument Area, the E2C test facility, Building 605 at the Seaside Area, and the Joint Integrated Communications Facility at the Old Town Campus, NIWC Pacific in San Diego, CA in the performance of this task. These facilities host the ADNS development test beds, which incorporate all needed

COTS/GOTS equipment including radio frequency systems and cryptological devices. Performance may also take place at contractor facilities and travel locations listed above in paragraph 5.0.

8.7 Inspection and Acceptance

Quality assurance of contractor services will be performed by the Contracting Officer’s Representative (COR)

Lance McDonald, Code 55160, NIWC-PAC, (619) 400-7141, lance.g.mcdonald1@navy.mil. All deliverables shall be delivered to Naval Information Warfare Center Pacific, San Diego, for review and inspection by the government

COR.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government

0002 Destination Government Destination Government

0003 Destination Government Destination Government

1001 Destination Government Destination Government

1002 Destination Government Destination Government

1003 Destination Government Destination Government

2001 Destination Government Destination Government

2002 Destination Government Destination Government

2003 Destination Government Destination Government

3001 Destination Government Destination Government

3002 Destination Government Destination Government

3003 Destination Government Destination Government

4001 Destination Government Destination Government

4002 Destination Government Destination Government

4003 Destination Government Destination Government

CLAUSES INCORPORATED BY REFERENCE

52.246-3 Inspection Of Supplies Cost-Reimbursement MAY 2001

52.246-5 Inspection Of Services Cost-Reimbursement APR 1984

Section F - Deliveries or Performance

DELIVERIES OR PERFORMANCE

The period of performance of the contract, for the purpose of issuing Task Orders is as follows:

CLIN(S) PERIOD(S) OF PERFORMANCE FOR ISSUING ORDERS

Base: 0001 – 0003 From date of award through two years thereafter

Option 1: 1001 – 1003 From effective date of option 1 exercise through two years thereafter

Option 2: 2001 – 2003 From effective date of option 2 exercise through two years thereafter

Option 3: 3001 – 3003 From effective date of option 3 exercise through two years thereafter

Option 4: 4001 – 4003 From effective date of option 4 exercise through two years thereafter

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 N/A N/A N/A N/A

0002 N/A N/A N/A N/A

0003 N/A N/A N/A N/A

1001 N/A N/A N/A N/A

1002 N/A N/A N/A N/A

1003 N/A N/A N/A N/A

2001 N/A N/A N/A N/A

2002 N/A N/A N/A N/A

2003 N/A N/A N/A N/A

3001 N/A N/A N/A N/A

3002 N/A N/A N/A N/A

3003 N/A N/A N/A N/A

4001 N/A N/A N/A N/A

4002 N/A N/A…