N66001-19-R-0036.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 19 Oct 2019

X

A X B X C

D

EX

X G F 42 - 53

54 - 67 H 68 - 72

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 72

(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 1 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 - 8

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

9 - 20 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 23 - 25 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 - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

26 - 40

PART II - CONTRACT CLAUSES

NAVAL INFORMATION WARFARE CENTER PACIFIC

ERWIN C.CABLAY CODE 22550

ERWIN.C.CABLAY@NAVY.MIL

53560 HULL ST

SAN DIEGO CA 92152-5001

619-553-7708

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

20 Sep 2019

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N6600119R0036

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Lot CANES Engineering Services

CPFF

Base Period (1st Year) Services in accordance with the Performance Work Statement (PWS) in Section C, as specified in individual task orders.

FOB: Destination

PSC CD: AD24

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 1 Lot Other Direct Costs (ODC)

COST

Base Period (1st Year) ODC including but not limited to travel, materials, and equipment in support of

CLIN 0001.

0003 1 Lot Contract Data Requirements List (CDRL)

FFP

Base Period (1st Year) Not Separately Priced. Data in accordance with DD Form 1423 as specified in individual task orders.

NET AMT

1001 1 Lot OPTION CANES Engineering Services

CPFF

Option Period One (2nd Year) Services in accordance with the Performance Work Statement (PWS) in Section C, as specified in individual task orders.

1002 1 Lot OPTION Other Direct Costs (ODC)

COST

Option Period One (2nd Year) ODC including but not limited to travel, materials, and equipment in support of

CLIN 1001.

1003 1 Lot OPTION Contract Data Requirements List (CDRL)

FFP

Option Period One (2nd Year) Not Separately Priced. Data in accordance with DD Form 1423 as specified in individual task orders.

2001 1 Lot OPTION CANES Engineering Services

CPFF

Option Period Two (3rd Year) Services in accordance with the Performance Work Statement (PWS) in Section C, as specified in individual task orders.

2002 1 Lot OPTION Other Direct Costs (ODC)

COST

Option Period Two (3rd Year) ODC including but not limited to travel, materials, and equipment in support of

CLIN 2001.

2003 1 Lot OPTION Contract Data Requirements List (CDRL)

FFP

Option Period Two (3rd Year) Not Separately Priced. Data in accordance with DD Form 1423 as specified in individual task orders.

3001 1 Lot OPTION CANES Engineering Services

CPFF

Option Period Three (4th Year) Services in accordance with the Performance Work Statement (PWS) in Section C, as specified in individual task orders.

3002 1 Lot OPTION Other Direct Costs (ODC)

COST

Option Period Three (4th Year) ODC including but not limited to travel, materials, and equipment in support of

CLIN 3001.

3003 1 Lot OPTION Contract Data Requirements List (CDRL)

FFP

Option Period Three (4th Year) Not Separately Priced. Data in accordance with DD Form 1423 as specified in individual task orders.

4001 1 Lot OPTION CANES Engineering Services

CPFF

Option Period Four (5th Year) Services in accordance with the Performance Work Statement (PWS) in Section C, as specified in individual task orders.

4002 1 Lot OPTION Other Direct Costs (ODC)

COST

Option Period Four (5th Year) ODC including but not limited to travel, materials, and equipment in support of

CLIN 4001.

4003 1 Lot OPTION Contract Data Requirements List (CDRL)

FFP

Option Period Four (5th Year) Not Separately Priced. Data in accordance with DD Form 1423 as specified in individual task orders.

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

Performance Work Statement (PWS) Engineering and Support Services for Consolidated Afloat

Network and Enterprise Services (CANES) Programs

1.0 SCOPE

The Afloat Network Design and Architecture Code 55130 and Network Test and Integration Code 55190 at Naval Information Warfare Center, Pacific (NIWC Pacific) have identified a requirement for engineering, technical and programmatic services for networking, communication, and computer systems, and associated certification and information assurance for developments, current operations and planned upgrades to support Program Management Warfare (PMW) 160 Tactical Networks. The networking, communication and computer systems described and referred to in this Performance Work Statement (PWS) are specialized tactical systems fielded through various Consolidated Afloat Networks and Enterprise Services (CANES) Programs of Record (POR) baselines or variants, that enable Command and Control (C2) in naval, joint, coalition operations, providing the gateway to achieving Information Warfare Dominance in the cyberspace domain.

Under NIWC Pacific Transport and Computing Infrastructure (TCI) Portfolio construct, NIWC Pacific Codes 55130 and 55190 anticipate work that will include the Ashore, Afloat, Subsurface, Airborne, Mobile, and Joint domains 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, cybersecurity engineering, software engineering and automation, and tactical and satellite communications. Transformation of capabilities-based portfolio into a networked and computer infrastructure enables Information Warfare 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.

2.0 APPLICABLE DOCUMENTS

Applicable documents will be added at the task order level and may include military standards, military handbooks, software development guidance, and other publications.

3.0 TECHNICAL REQUIREMENTS

The following requirements comprise the scope of systems engineering, technical and programmatic efforts anticipated to support NIWC Pacific Codes 55130 and 55190 work related to CANES Programs for networks, communications and computer systems which enable net-centric capabilities across Naval and Joint enterprise domains.

3.1 Systems Engineering: Capabilities, Requirements, and Assessments

3.1.1 Capabilities, Requirements and Assessments

The contractor shall analyze the capabilities and environmental constraints identified from users, sponsors or stakeholders of CANES networks and communication systems, and generate performance and functional requirements to realize those capabilities. The solution may be for a new project or upgrade to existing CANES systems.

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.

3.1.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 Warfare Dominance.

3.2 Systems Engineering: Architecture Research and Design

3.2.1 Enterprise Level

The contractor shall develop CANES architectures that are aligned strategically with DoD enterprise architectures and are consistent with DoD rules and policies to provide frameworks for data transport, core services, application functionality, avoid technology obsolescence, and utilize accepted business strategies. The contractor shall mature technology to higher levels of readiness. The contractor shall produce DoD Architecture Framework (DoDAF) documents showing integrated architectures across multiple views.

3.2.2 Tactical Level

The contractor shall develop CANES architectures that extend to the tactical level that may transverse the Global Information Grid (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.2.3 System Level

The contractor shall design CANES systems based on given requirements for reliability, maintainability, and supportability, and that 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.3 Systems Engineering: Engineering Development

3.3.1 Network Development

The contractor shall develop, build and integrate components and sub-systems required to realize capability requirements and/or designed system architectures. The contractor shall develop software and applications required to realize CANES designed system functionality and capability. The contractor shall develop, build and integrate CANES networking and processing capabilities in virtualized environments utilizing emerging technologies.

3.3.2 Improvements and Technical Evaluations

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

3.3.3 Use of Prototypes

The contractor shall use prototypes to mature system designs and drawings, and to evaluate selected technology for future production or manufacturing. The contractor shall build or fabricate assemblies and systems including Engineering Development Models (EDM) when needed and which align with the CANES acquisition strategy.

3.3.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, work breakdown structures. The contractor shall develop, modify, and/or update specifications; 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 technical manual, user manuals, operation and maintenance manuals, standard manuals, style guides, 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), Contractor Integrated Technical Information System Implementation Plans (CITIS_IPs), 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 prepare and provide inputs for Program Protection Plans which includes Security Classification Guides (SCG), Counterintelligence Support Plans and Information Assurance documentation.

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

3.4 Systems Engineering: Cyber Security Assessment and Authorization (A&A)

The contractor shall provide Assessment and Authorization (A&A) support, Information Assurance Vulnerability Management (IAVM), Cyber Security support for CANES programs.

3.4.1 Risk Management Framework for DoD IT

The contractor shall develop, review and/or modify 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 and/or modify ATO with conditions 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 Authorization packages include: Security Assessment Plan (SAP), Security Assessment Report (SAR) and Plan of Actions and Milestones (POA&M); Additional artifacts may be required by the accrediting authorities such as; 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.).

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

The contractor shall create documentation of Assessment and Authorization (A&A) that meet the submission requirements found within the Risk Management Framework (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 the security posture of the configuration baseline meets requirements stated in all applicable DoD/DoN security documents.

3.4.2 Security Controls and System Scanning Support

The contractor shall provide and document vulnerability assessments to identify weaknesses in the system that can be exploited and mitigations to overcome them. The contractor shall document the information in a 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 conduct preliminary control testing which will allow for discovery and remediation of initial vulnerabilities prior to the formal assessment. The Defense Information Systems Agency (DISA) provides a comprehensive list of all applicable Security Requirements Guides (SRG), Security Technical Implementation Guides (STIGs) and Security Content Automation Protocol (SCAP) benchmarks. The Contractor shall leverage these guides and benchmarks for security control implementation and testing. Only Navy approved testing tools should be used throughout the A&A process.

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

3.4.3 Cyber and Multi-Domain Systems

The contractor shall provide engineering and technical services to develop systems which will operate across the cyber domain to allow Tasking, Collection, Processing, Exploitation and Dissemination (TCPED) of vital and time-sensitive data.

The contractor shall support engineering development for networks and systems across multiple security enclaves up to and including the TS/SCI Level. The contractor shall be able to achieve data transport, sharing and interoperability across multiple security domains using message guards or switches, including multi-user connectivity from data servers.

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: Production

The contractor shall support Low-Rate Initial Production (LRIP), Full-Rate Production (FRP), Full-Rate Deployment (FRD) preparation and planning. The LRIP, FRP/D production requirements include EMP-hardening;

TEMPEST-certification; and/or environmental testing (dust, heat, shock, vibration, humidity, etc.); and electromagnetic or similar physical parameters.

3.7 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 the evaluation of effectiveness, suitability and/or survivability.

3.8 Systems Engineering: Training

The contractor shall prepare training curricula, student and instructor guides, and related training materials. The contractor shall conduct training courses in classroom and operational environments as well as conduct system operational training.

3.9 Systems Engineering: Production Documentation and Reviews

3.9.1 Configuration Support / Configuration Management

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.9.2 Baseline Documents and Databases

The contractor shall draft and update baseline documents related to systems engineering which include system concepts, system configurations, specifications, reports, accreditation documents, line drawings, Standard Operating Procedures (SOPs), architecture drawings, equipment lists and Bill of Materials (BoMs), Configuration Item Configuration Documentation (CICD), manufacturing processes or procedures, test and inspection plans or procedures, surveys, quality assurance provisions, inspection and test equipment requirements, packaging lists, software documentation, technical manuals, 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. The contractor shall ensure proper configuration management is maintained via the PMW 160 CCB/PTRB/CMPro workflow processes.

3.9.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. The contractor may use the government-approved Automated Data Processing (ADP) system(s) for configuration status accounting.

Configuration accounting shall be achieved through utilization of CMPro database, as used by SPAWAR.

3.9.4 Reviews

The contractor shall support technical, programmatic, production and/or sustainment planning meetings or reviews.

3.10 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 prepare installation plans, Fleet Readiness Certification Board (FRCB) submissions, Base Electronic System Engineering Plans (BESEPs), Shipboard Alteration (SHIPALT) packages, and plans supporting certifications or approvals that are incidental to the system installation. The contractor shall evaluate operational impact due to planned installations and advise on best course of action to minimize disruptions.

The contractor shall provide input to, review and modify Installation Design Plans (IDPs) as required for FRCB submission. IDP shall include as block diagram, rack elevations, 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 planning and execution of System Operational Verification Tests (SOVTs) as the final check-out demonstrating a successful, functional installation.

3.11 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 will meet required system availability requirements.

The contractor shall perform Communications Security (COMSEC) field and 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 and overall system security compliance.

3.12 Systems Engineering: Logistics Support

3.12.1 Integrated Logistics Support (ILS) Planning

The contractor shall develop and maintain Integrated Logistics Support Plan(s) (ILSP); User's Logistics Support Summary(s) (ULSS); Logistics Requirements and Funding Summary(s) (LRFS); Logistics Support Analysis Plan(s) (LSAP); Computer Resources Integrated Support Document (CRISD) and life cycle cost estimating. The impacts on all ILS elements shall be discussed in all ILS Plans, system engineering analyses and engineering change proposals.

The ILS elements include the following: (1) Technical data; (2) Training and training support; (3) Maintenance; (4) Supply support; (5) Configuration management; (6) Support equipment; (7) Manpower and personnel; (8) Packaging, handling, storage and transportation; (9) Computer resources support; (10) Facilities; and (11) Design interface.

3.12.2 Logistic Support Analysis

The contractor shall perform Logistic Support Analysis (LSA) of systems supported by NIWC Pacific Codes 55130 and 55190. The LSA process is iterative and may be continued through the life cycle of the systems to address engineering changes. These analyses shall include at a minimum: (1) identification of hardware or software for which the Government will not or may not receive full rights due to constraints imposed by regulations or laws limiting the information that must be furnished because of proprietary or other source control considerations; (2) development of supportability, cost, and readiness objectives including risk assessment; and (3) development of supportability related to design constraints for inclusion in specification(s) and other requirement documents.

3.13 Systems Engineering: Upgrades

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

The contractor shall utilize Engineering Change Request (ECR), Engineering Problem Report (EPR) Enterprise Change Notice (ECN), Engineering Change Proposal (ECP), Request for Change (RFC), Request for Deviation (RFD), or Request for Waiver (RFW) as a process and control mechanism to implement upgrades and improvements to operational systems, and support the efforts necessary to complete these processes. For approved ECRs and new baselines, the contractor shall recommend solutions and ensure the solutions address communication and network related deficiencies, design changes, design improvements, and end of support/end of life issues.

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 COTS/GOTS products. The contractor shall provide reports showing the impacts of changes to baseline hardware and software.

3.14 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, Technology and Logistics Life Cycle Management Framework for Navy, Joint and Coalition communications and networked systems.

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

3.15 Network and Computer Support

3.15.1 Network Systems Maintenance (for NIWC Pacific)

The contractor shall provide network system maintenance and administration support. Including software and hardware maintenance, system integration and systems interface support of the systems.

The contractor shall provide analysis and administration support to projects requiring access to IT data, including design, development, and maintenance of tables; creation and maintenance of data dictionaries; and creation of bridges to populate new tables; file transfer and reformatting, troubleshooting, error investigation and correction, and production of specialized internal reports.

The contractor shall perform network system maintenance and quality assurance through validation and the integrity of access capability for operational and management query and reporting.

3.15.2 Network Operations Support

The contractor shall provide operations support for the networks of systems or projects that are outside the scope of the Navy/Marine Corps Internet (NMCI). The contractor shall support the operation, troubleshooting and deployment of CANES.

The contractor shall perform network database management support; perform network monitoring and statistical analysis; network control; and test equipment operation support. The contractor shall analyze the existing CANES design and provide communication and network related engineering and technical support, such as: network access services, transport services, network services, internal and external wireless services, and Quality of Service (QoS) solutions.

The contractor shall provide upgrade development and implementation support for Gigabit-capable Passive Optical Networks (GPON) that includes implementation for data, voice, and video. The contractor shall support virtualized network operations.

The contractor shall provide network contingency support; technical inputs; participate in network contingency planning; and provide execution support.

3.15.3 Computer Operations Support

The contractor shall provide computer operations and maintenance for computer systems ranging from laptops to servers with operating systems used by DoD, including maintaining logs and records of jobs processed.

The contractor shall monitor systems for equipment failures, errors in performance, and security issues.

The contractor shall support virtualized computer operations.

The contractor shall reload systems after power outages and maintenance, perform backups, and restore files. The contractor shall install new software; software patches; security updates; and hardware based on project, program, or security requirements.

3.16 Process Improvement Planning

The contractor shall work collaboratively with NIWC Pacific Codes 55130 and 55190 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. Process improvement plans shall include details which delineate methods from the Agile software development as an approach to project management. These methods shall assist the government teams in responding to the unpredictability of constructing CANES software.

Furthermore, the process improvement plans shall utilize Agile software development frameworks to include but are not limited to the following, Adaptive software development (ASD), Agile modeling, Agile unified process (AUP), Disciplined agile delivery, Dynamic systems development method (DSDM), Extreme programming (XP), Feature-driven development (FDD), Lean software development, Kanban, Rapid application development (RAD), Scrum and Scrumban. The plan shall identify activities, resources and timeframes needed to execute critical improvement activities to help the organization prepare for appraisals.

3.17 Software

3.17.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 CANES, 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 CANES Functional Specification. Contractor shall provide recommended updates to either the application or the CANES Program technical documentation.

The contractor shall provide feedback and guidance to application providers regarding the AI Process including key dates, submission requirements, data requirements, test event schedules, and validate the application/system programmatic functional areas. The contractor shall work with the specific application providers to mitigate gaps and potential programmatic risks to integration.

The contractor shall work with application providers to investigate, define and document an integration solution, and ensure that the integration solution is aligned with Cyber Security and programmatic requirements IAW with applicable documents.

The contractor shall provide technical support by creating, updating and maintaining the existing AI documentation (i.e. HACSIM, AI Feasibility Assessments, and Service Request Forms) and clarification of integration solutions to application providers in support of fleet implementations.

The contractor shall develop applications to meet functionality defined in programmatic requirement documents.

3.17.2 Software Development Planning

The contractor shall define a software development approach appropriate for the computer software effort to be performed under this solicitation. This approach shall be documented in a Software Development Plan (SDP). The contractor shall follow this SDP for all computer software to be developed or maintained under this effort.

The SDP shall define the offeror’s proposed life cycle model and the processes used as a part of that model. In this context, the term “life cycle model” is as defined in IEEE/EIA Std. 12207-2008. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of this solicitation. In accordance with the framework defined in IEEE/EIA Std. 12207-2008, the SDP shall define the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks. Because IEEE/EIA Std. 12207-2008 does not prescribe how to accomplish the task, the offeror must provide this detailed information so the Government can assess whether the offeror’s approach is viable. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, as a minimum, specific standard, methods, tools, action, strategies, and responsibilities associated with development and qualification.

4.0 REPORTS, DATA and DELIVERABLES

4.1 Deliverables

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

4.2 Contractor Manpower Reporting

The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for 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.

5.0 OTHER

5.1 Security

The security requirement for this tasking will be up to and including Top Secret and Sensitive Compartmented Information. The work performed by the Contractor will include access to unclassified and up to Top Secret/SCI data, information, meetings, and spaces. Individual task orders awarded under this basic contract will specify security clearance level required for contractor personnel. Individual task orders may require contract personnel to have access to Communications Security (COMSEC) material or be a COMSEC Material System (CMS) user. The security clearance of the contractor personnel assigned to the task order must be appropriate for the associated COMSEC 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)/Joint Worldwide Intelligence Communications System (JWICS)/NSAnet; training is provided by the facility security officer.

Although there is no requirement for the contractor to access NATO on this contract per Naval Intelligence Security Policy Directive 17-008 those contractors that have SCI access and those cleared SCI with JWICS or SIPRnet accounts shall be North Atlantic Treaty Organization (NATO) read-on and complete the derivative classification training prior to being granted access to JWICS/SIPRnet; training is provided by the facility security officer.

Specific requirements provided in the Department of Defense Contract Security Classification Specification, DD Form 254.

Contractors performing tasks at the TS or below level without SCI access shall only receive the North Atlantic Treaty Organization (NATO) awareness brief and complete the derivative classification training prior to being granted access to SIPRnet; training is provided by the facility security officer.

Contractor personnel assigned to this effort who require access to SCI data and spaces must possess a current SSBI with ICD 704 eligibility (which replaced DCID 6/4 eligibility).

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, 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.

If foreign travel is required, all outgoing Country/Theater clearance message requests shall be submitted to Commanding Officer, Attn: Foreign Travel Team, NIWC Pacific, 53560 Hull Street, Building 27, 2nd Floor -Room 206, San Diego, CA 92152 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 30 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 at Joint Knowledge Online (JKO): https://jkodirect.jten.mil (prefix): course number: US007; title: Level 1 Anti-terrorism Awareness Training, 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.2 Level A code of conduct training is also required prior to Oconus travel for all personnel. Sere 100.2 Level A training can be accessed at http://jko.jfcom.mil (recommended), https://jkodirect.jten.mil/atlas2/faces/page/login/login.seam, recommended course: prefix: J3T: course #: A-US1329, for civilian, military, and contractors. Personnel utilizing this site must have a CAC. A Sere 100.2 Level A training disk can be borrowed at the NIWC Pacific Point Loma Office or Old Town Campus Office. Specialized training for specific locations, such as SOUTHCOM human rights, or U.S. forces Korea entry training, may also be required; NIWC Pacific security personnel will inform you if there are additional training requirements. Finally, EUCOM has mandated that all personnel going on official travel to the EUCOM AOR must now register with the Smart Traveler Enrollment Program (STEP). When you sign up, you will automatically receive the most current information the State Department compiles about your destination country.

You will also receive updates, including Travel Warnings and Travel Alerts. Sign up is one-time only, after you have established your STEP account, you can easily add official or personal travel to anywhere in the world, not just EUCOM. http://travel.state.gov/content/passports/en/go/step.html

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), 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.

5.1.1 Network Access

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

5.2 Communication Security Material System

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

5.3 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.

5.3.1 CSWF…