N66604-21-Q-0286.pdf

SEE ADDENDUM

(No Collect Calls)

N6660421Q0286 29-Jul-2021

b. TELEPHONE NUMBER

(401)-832-4381

8. OFFER DUE DATE/LOCAL TIME

02:00 PM 20 Aug 2021

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

N666049. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

CHELSEA ISHERWOOD

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

0 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

NAVAL UNDERSEA WARFARE CENTER

CHELSEA A ISHERWOOD, CODE 0223

CONTRACTS DEPARTMENT

1176 HOWELL STREET, BLDG. 1258

NEWPORT RI 02841-1708

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS AX

13b. RATING

DO-C9

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: (401) 832-4381 SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$30,000,000

NAICS:

541519

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF78

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

V1.2_JULY2020

FOR OFFICIAL USE ONLY

Section A - Solicitation/Contract Form

GENERAL INFORMATION

Distribution: FILE, KR, NUWC 01/115, PI: TBD

NUWCDIVNPT Action Number: 210286

NUWCDIVNPT PID Number: 02-0026

NUWCDIVNPT Requisition Number: 1300945145

NUWCDIVNPT POC: Chelsea Isherwood (Phone: 401-832-4381; Email: chelsea.isherwood@navy.mil)

DELIVERY MARK FOR

SUBMEPP Activity PO Box 2500 Portsmouth Naval Shipyard Portsmouth, NH 03804-2500

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Job Program Management and Technical Service

FFP

Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.1, 4.3, 4.4, 4.5, 4.7, 4.8, and 4.9 in Section C.

FY of Funds: 2021 Type of Money: O&MN Customer Code: SUBMEPP Sponsor: SUBMEPP

TI #: N/A

FOB: Destination

PSC CD: DD01

NET AMT

0002 1 Job OPTION Program Management and Technical Service

FFP

Program Management and Technical Service in accordance with the Statement of Work (SOW), paragraphs 4.2 and 4.6 in Section C.

FY of Funds: TBD Type of Money: TBD Customer Code: TBD Sponsor: TBD

TI #: N/A

0003 1 Lot

ODC

FFP

ODCs for Material and Travel in Support fo Services under CLIN 0001.

FY of Funds: 2021 Type of Money: O&MN Customer Code: SUBMEPP Sponsor: SUBMEPP

TI #: N/A

0004 1 Lot

DATA

FFP

Contract Data Requirements List (CDRLs)

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF WORK

(SOW)

Information Management Technology Configuration and Support Services for Maintenance and Ship Work Planning (M&SWP) v 3.0 for Submarine Maintenance

Engineering Planning and Procurement (SUBMEPP)

PR No. 1300945145

1.0 Background

Maintenance and Ship Work Planning (M&SWP) is the life cycle maintenance planning, scheduling and execution application that manages Intermediate (I) and Depot (D) level maintenance across the Navy Enterprise; Submarines, Carriers and Surface Ships, along with Submarine Trainers, Moored Training Ships (MTS), and other unique platforms.

M&SWP provides the three Navy Maintenance Planning Activities with the ability to prepare, issue, and maintain Work Packages for all D-level and I-Level availabilities. Objective Quality Evidence (OQE) and completions against scheduled maintenance requirements are collected, including completions brought in via an interface with the Navy Material Maintenance Management (3M)-Open Architecture Retrieval System (OARS) application. The Last Maintenance Accomplished date, material condition code and cost data are in the data captured by M&SWP. Maintenance history captured against component level maintenance requirements is used to determine future scheduling of maintenance requirements and future development of work packages.

M&SWP Version 3.0 is comprised of a suite of configured Commercial Off the Shelf (COTS) software applications. Siemens Teamcenter Product Lifecycle Management software is the main component application software of M&SWP 3.0, with eQ Technologic eQube-BI, eQube-MI, and Microsoft SharePoint software applications supporting.

M&SWP 3.0 is currently not production capable due to the need to perform software configuration changes to correct defects in the previously implemented business logic, the need for additional system enhancements, the need to correct and implement identified corrections to performance issues, and the need to build and migrate business data into the application.

Submarine Maintenance, Engineering, Planning and Procurement (SUBMEPP) requires Information Technology (IT) support services covering a full range of technical, functional and managerial expertise to support the SUBMEPP M&SWP 3.0 application. This program provides for a full range of technical and functional expertise to support the SUBMEPP M&SWP 3.0 Application.

The objective of this contract is to bring M&SWP 3.0 to a production ready state through the accomplishment of work tasks issued via Configuration Change Requests as described in section

4.0. The configuration change requests will be issued to implement the following system changes; resolution of approximately forty (40) configuration changes required to correct deficiencies in the application’s previously configured business logic, implementing identified performance fixes in all M&SWP 3.0 environments (i.e. production, preproduction, and development), implementing approximately five (5) application configuration enhancements to add business functionality, assisting with business data buildout/migration, and additional configuration changes that may be identified during the accomplishment of this contract.

Example Configuration Change Requests and associated work unit(s) have been provided in Appendix A to document the level of effort expectations of the government for each work task.

A configuration Change Request may contain several work units.

1.1 Place of Performance:

1.1.1 Government project management and M&SWP 3.0 primary user base is located at Portsmouth Naval Shipyard in Kittery Maine and Norfolk Naval Shipyard in Portsmouth Virginia. M&SWP 3.0 resides in a government hosted datacenter and can be accessed remotely via government provided assets. The work within this contract can be accomplished remotely at vendor’s location including vendor telework. Vendor telework must be in accordance with a government approved vendor telework policy, which documents the requirements and captures OQE that all telework worksites are adequate to secure government provided assets and information including the safeguarding of Unclassified Naval Nuclear Propulsion Information (U-NNPI) information. Work must be performed satisfactorily while meeting contractually acceptable quality standards as if they were at the Government location.

1.1.2 Under no circumstances shall a contractor allow unauthorized personnel access to the government furnished equipment and information. The contractor shall be required to facilitate on-site inspections at the Government’s request.

1.1.3 The Government currently anticipates minimal travel associated with this contract.

Instances where travel may be required would be to participate in collaboration and testing events and is expected not to exceed 20 days over the period of performance. All travel costs incurred will be separately priced and executed in accordance with the Federal Acquisition Regulation (FAR) 31.205-46. A copy of this travel request shall be routed to the Contracting Officer Representative (COR). Upon validation of the travel requirement, the COR will forward the travel request to the contractor with COR approval. Any travel not directly related to this requirement, and that has not been validated by the COR, is not chargeable to the Government.

Upon return from travel, the contractor shall prepare a Trip Report providing the accomplishments of the travel. Report shall be submitted within 5 business days of return from travel.

1.1.4. Work Schedule and Hours of Operation: The Government’s primary operations are conducted Monday through Friday between the hours of 6:30am Eastern Standard Time (EST) through 4:00pm EST, except Federal holidays. The ten (10) Federal holidays include New Year’s Day, Martin Luther King Day, President’s Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving, and Christmas Day.

During certain operations the contractor shall be required to work outside of primary work hours to include but not limited to evenings and weekends. These operations include but are not limited to planned and unplanned service outages, planned and unplanned maintenance, and emergency operations.

1.1.5. Contingency Operations: SUBMEPP may be required to conduct business and operations from an alternate site as a result of severe weather conditions, emergency situations and as required by Continuity of Operation exercises. When required, the Contractors supporting this task order may be required to support the operation from an alternate location. The Government shall support the alternate site locations with Government Furnished Equipment as noted in section 1.1.5 as long as doing so does not conflict with the security requirements of the contract.

1.1.6. Government Furnished Property (GFP) and Government-Furnished Equipment (GFE)

1.1.6.1. The Government shall provide workstations and Government computers to the Contractor’s GFP manager, who will be responsible and accountable for all assets and distribution to contactor’s team. When required, the Government shall authorize resources to operate from alternate site locations. Primary and Alternate locations must meet requirements outlined in the Office of the Chief of Naval Operations Instructions (OPNAVINST) N9210.3, Dated Jun 7, 2010; SAFEGUARDING OF NAVAL NUCLEAR PROPULSION INFORMATION (NNPI). If personal, non-corporate controlled location are used (e.g. a home offices), the Industry Participant must develop policy showing how spaces will be certified and maintained in accordance with (IAW) OPNAVINST N9210.3, and forward to the Government Information Systems Security Manager (ISSM) for review and approval. Additionally, any forms or documentation invoked by said policy must be forwarded to the ISSM for review and approval prior to allowing GFE into the space. The resources to support the alternate site location(s) shall include the minimum equipment required to support the operation, and are the responsibility of the contactor to furnish. The primary office responsible for identifying and issuing GFE shall be Department of Defense (DoD) SUBMEPP.

1.1.6.2. Contactor personnel shall be required to obtain a Common Access Card (CAC) for Navy/Marine Corps Intranet (NMCI) network usage. It is the responsibility of the Contactor to identify their local or nearest CAC issuing facility, and coordinate pick-up as required after government sponsorship.

1.1.6.2.1. Certain contract personnel will be required to obtain an Alt-token for separation of duties requirements. The contractor will coordinate with the Government Program Manager (PM) and Information System Security Manager (ISSM) for issuance of Alt-Tokens. Alt-Tokens and CACs are used for authentication into government systems and shall be secured the same.

Therefore, nay and all security measures for CACs referenced throughout this document it is implied for Alt-Tokens as well.

1.1.6.3. Contactor Personnel may be issued Naval Sea Systems Command (NAVSEA) Badges if it is deemed necessary and regular visitation to the government site is expected. The badge shall be worn at all times on the upper part of the body so as to be clearly visible, and concealed on your person whenever the wearer leaves the Government Participants’ premises for any reason or any length of time.

1.1.6.4. Contactor personnel whose CAC card and NAVSEA Badge (if issued) are lost or stolen shall present documentation to the SUBMEPP Office of Security (OSEC) confirming that the identification (ID) is missing and describing the circumstances under which the loss occurred.

Government and Contactor personnel shall not share CACs or passwords with anyone else. The COR shall report any violation or suspected violation to the Acquisition Specialist and SUBMEPP OSEC. Any violators shall be removed temporarily or permanently from the project.

If a Contactor employee has a CAC issued from a previous engagement with another agency that CAC shall be returned to that agency before issuance of a SUBMEPP sponsored CAC.

1.1.6.5. Contactor personnel shall be required to identify and coordinate with a local and nearby NMCI network access point for occasional direct network log-in (specifically for first time Government computer login, and as necessary to retain computer and network access).

1.1.6.6. Laptops shall follow the following GFP process:

The GFP provided to the contractor may include, but is not limited to, laptops to perform the services needed under this contract. The contractor shall manage GFP in accordance with FAR Part 45 and Defense FAR Supplement (DFARS) Part 245 and associated clauses incorporated in this contract. The contractor shall include a complete list of all GFP within the contractor's Monthly Status Report for verification by the COR and Property Administrator. The list shall include Item name, Item Description, National Stock Number, Cage, Part #, Model #, Serial #, Unique Item Identifier, quantity, Unit of Measure, Unit Cost, and indication of Use as Is. It is mandatory that the format be completed to the maximum extent possible.

1.2 Types of Funding

The funding for this contract is Operation and Maintenance Navy (O&MN).

2.0 Scope

The Contractor shall provide Program Management and Technical services support by performing the following tasks and completing the required deliverables identified in this SOW.

- Integrated Solutions Management

- Requirements Analysis

- Information and Knowledge Management

- Custom Application Configuration

- Product Integration

- Test and Evaluation (T&E)

- Cyber Security Assessment, Authorization, and Implementation

- Information Communication Technology

- Web Services

- Operations Support

- IT Support Services

3.0 Applicable Documents

3.1 DoD Issuances

3.1.1. DoDI I 8500.1 (latest series) “Cybersecurity”

3.1.2. DODINST 8510.01, (latest series) “Risk Management Framework (RMF) for DoD Information Technology (IT)”

3.1.3. DODD 8140.01, (latest series) “Cyberspace Workforce Management”

3.1.4. DoDM 8400.01-(latest series), “Accessibility Of Information And Communications Technology (ICT)”

3.2 Navy Issuances

3.2.1. OPNAVINST 5239.1 (latest series) Navy Information Assurance (IA) Program

3.2.2. SECNAVINST 5239.3 (latest series) Department Of The Navy Information Assurance (IA) Policy

3.2.3. SECNAVINST 5510.36 (latest series) Information Security Program. Manual

3.2.4. OPNAVINST N9210.3 (latest series) Safeguarding of Naval Nuclear Propulsion Information (NNPI)

3.3 SUBMEPP Issuances

3.3.1. SUBMEPP Work Procedure 1863-09 – Assessment and Authorization Overview and Support Information of SUBMEPP Systems and Applications

3.4. Industry Standards

3.4.1. FIPS 140-2 - Security Requirements for Cryptographic Modules

4.0 Technical Performance Requirements

4.1 Task 1- M&SWP 3.0 Sustainment Support:

4.1.1. Subtask 1 –Requirements and Scope: The contractor shall provide business and system analysis to:

4.1.1.1. Develop derived business requirements from higher level requirements identified in SUBMEPP Application Configuration Change Requests for government concurrence and acceptance. Derived requirements will specify what system changes and work under Subtasks 3, 4, 5, 7, 8 and 9 are necessary to support the higher level requirement in the SUBMEPP Application Configuration Change Request. Work units tasked via configuration change requests will not exceed a total of one hundred twenty (120) over the period of performance, averaging approximately ten (10) work units per month. At contract award, approximately forty (40) work units will be issued via configuration change requests. This will allow the contractor to evaluate, combine, prioritize, and develop an efficient execution plan based on a larger portion of the work required to be completed under this contract. Change requests may be and are encouraged to be bundled, worked concurrently, and delivered via a single system update where determined to be practical and efficient.

4.1.1.1.1. The contractor shall receive SUBMEPP Application Configuration Change Requests, setup and support business process exploration and requirement clarification events with government subject-matter experts (SMEs), as necessary. Events may be in person or remote.

4.1.1.1.2. The contractor shall deliver set(s) of derived requirements from the SUBMEPP Application Configuration Change Request for government review and acceptance. If comments are received, the contractor shall address any government comments against derived requirements.

4.1.1.2. The contractor shall identify all IT systems impacted by or required to support the SUBMEPP Application Configuration Change Request and its derived requirements, including but not limited to any software, applications, application components, hardware, networks or network components. For accepted 4.1.1.1 derived business requirements the contractor shall identify each IT system, IT system component or software configuration that needs to be modified that is necessary to support the SUBMEPP Application Configuration Change Request.

This includes but is not limited to any software, applications, application components, hardware, networks or network components that need to be changed to support the 4.1.1.1 derived business requirements.

4.1.1.2.1. For each system and component the contractor shall identify any changes necessary to support Government accepted 4.1.1.1 derived requirements.

4.1.1.2.2. For each change the contractor shall:

4.1.1.2.2.1. Identify if the change can be accomplished Out of the Box (OOTB) by configuring inherent application functionality.

4.1.1.2.2.2. Identify any impacts to system functionality including but not limited to: impact to workflows and dataflows of the system the change resides in, and impacts to system inputs and outputs of other interfacing systems.

4.1.1.2.2.3. Gather, provide, and present required information on application configuration changes for approval to the SUBMEPP configuration control board to support SUBMEPP’s application configuration control process.

4.1.1.2.2.4. The contractor shall design all solutions with Cybersecurity, Information Assurance, System Security, and Security Technical Implementation Guides (STIGs); such that when changes are implemented those requirements are included. For any changes that affect the security posture of the system, the contractor shall obtain approval from the Government Information Systems Security Manager (ISSM).

4.1.1.2.2.5. Identify any updates or changes required to user groups and /roles and associated permissions.

4.1.1.2.3. The contractor shall present findings from 4.1.1.1.1 and 4.1.1.1.2 for initial government review and concurrence. The contractor shall address any government comments provided during the review and concurrence process. Government concurrence must be attained prior to any configuration work (4.1.3).

4.1.1.2.4. Once concurrence is attained, contractor shall update the project schedule and gain government concurrence. The schedule update shall include periods for:

Work duration Development, pre-production, and production environment implementation Contractor change and regression testing Government change and regression testing Defect resolution

4.1.1.3. The contractor shall develop a list of SUBMEPP documentation to be updated, developed, and maintained during the SUBMEPP Application Configuration Change Request based on the proposed design intent of system configuration. This list will be compiled from SUBMEPP’s document library (including but not limited to process tables, derived specification documentation, Department of Defense Architecture Framework (DoDAF), assessment and authorization (A&A) Artifacts) and as indicated in the SUBMEPP Application Configuration Change Request.

4.1.2 Subtask 2 – Project Management: The contractor shall provide project management support for the IT projects worked under this SOW. The contractor shall ensure project goals and constraints are met, and deliverables are complete. The Project manager shall develop a test strategy to include regression testing, full vendor testing and end-to-end government acceptance testing. At a minimum the contractor shall be required to perform the following tasks in support of the objective:

4.1.2.1 Supports the operation of this SOW by providing daily oversight of the contracted personnel and providing other similar management responsibilities.

4.1.2.2 Maintains the project schedule, projecting and accounting for task work durations, implementation dates, testing windows, defect resolution periods, and assigned personnel, ensuring that target task frequencies are being met.

4.1.2.3 Facilitates weekly project planning meetings with government; meeting should cover work accomplished, qualitative risk assessments, key issues, milestone status, and the project schedule.

4.1.2.4 Conducts analytical studies and reports project metrics and status to include but not limited to using earned value calculations, cost benefit analysis, performance charts and quantitative risk assessments.

4.1.3 Subtask 3 – Application Configuration

4.1.3.1 TeamCenter Development and Configuration

4.1.3.1.1 Configure the M&SWP 3.0 TeamCenter (including but not limited to: Business Modeler Integrated Development Environment (BMIDE) configuration, TeamCenter Environment Manager (TEM) based updates, run time configuration, handler development and configuration (including C code handlers), data model changes, Workflow development, front end application configuration, TeamCenter application configuration at the server, Rich Access Client (RAC) configuration (including Jar files) and Navy/Marine Corps Intranet (NMCI) software packaging, thin client configuration (including Active workspace)) to meet the design intent and the accepted derived business requirements as defined in the SUBMEPP Application Configuration Change Request.

4.1.3.1.1.1 All developed code (eg. C++, JAVA) for the government and not part of the core TeamCenter application for release, will be submitted to and reviewed by the government

ISSM

4.1.3.1.1.2 All developed code (eg. C++, JAVA) for the government and not part of the core TeamCenter application for general release will be stored at the government location for configuration control purposes.

4.1.3.1.2 Support current TeamCenter modules and applications (Including but not limited to:

Service Planner, Service Manager, Service Scheduler, TeamCenter Security Services, TC Business Logic, TeamCenter File Management Services) and the implementation of future TeamCenter modules and applications.

4.1.3.1.3 Support the current installed version of M&SWP 3.0 TeamCenter or higher versions.

4.1.3.1.4 Support upgrading of M&SWP 3.0 to a later version of TeamCenter without regression of any M&SWP 3.0 custom configuration or custom functionality. This includes packaging and providing a single click installation method which can be automatically deployed to government NMCI workstations via NMCI remote installation methods when the RAC requires to be updated. Additionally, a single click RAC uninstaller must be provided, such that the RAC may be removed from NMCI workstations via NMCI remote software management methods.

4.1.3.1.4.1 Deliver and install all M&SWP 3.0 Teamcenter software and configuration packages including signed and compiled code in support of M&SWP 3.0 Teamcenter software and configurations.

4.1.3.2 eQ Product Development and Configuration

4.1.3.2.1 Configure the M&SWP 3.0 eQ-Technologic products (including but not limited to eQube MI, eQube BI TcRA, eQube GMP, eQube TM, M&SWP 3.0 eQube plugin jar’s, M&SWP 3.0 java code and eQube connectors) to other applications. Develop interfaces, reports, eQube Meta-Language Views (MLVs), eQ-MI processes, eQube BI cubes, and eQube scripts) to meet the design intent and the accepted derived business requirements as defined in the SUBMEPP Application Configuration Change Request.

4.1.3.2.1.1 All developed code (eg. C++, JAVA) for the government and not part of the core TeamCenter application for release, will be submitted to and reviewed by the government

ISSM

4.1.3.2.1.2 All developed code (eg. C++, JAVA) for the government and not part of the core TeamCenter application for general release will be stored at the government location for configuration control purposes.

4.1.3.2.1.1 Integrate and configure other eQ-Technologic products or connectors into M&SWP

3.0 or other SUBMEPP applications to include SharePoint.

4.1.3.2.1.2 Configure eQ-Technologic products to provide system-to-system interfacing between SUBMEPP applications or between maintenance planning activity’s applications.

4.1.3.2.1.3 Configure eQ-Technologic products to provide ad-hoc, scheduled and canned reports to meet the accepted derived requirements and design intent of the SUBMEPP Application Configuration Change Request.

4.1.3.2.1.4 Configure eQ-Technologic products to provide repeatable processes for querying, updating, populating or transforming M&SWP 3.0 system data.

4.1.3.2.2 Deliver and install all M&SWP 3.0 eQ software and configuration packages including signed and compiled code in support of M&SWP 3.0 eQ software and configuration

4.1.3.3 Microsoft SharePoint Product Development and Configuration

4.1.3.3.1 Configure the M&SWP 3.0 SharePoint environment to meet the design intent and the accepted derived business requirements as defined in the SUBMEPP Application Configuration Change Request.

4.1.3.3.1.1 Integrate with current and future versions of TeamCenter and eQ-Technologic products and connectors.

4.1.3.3.1.2 Configure and maintain SharePoint products to provide data entry and transformation, document management, storage, system-to-system interfacing between SUBMEPP applications and maintenance planning activity’s applications and Sharepoint, and reporting and extraction tools, or functionality as defined within the SUBMEPP Application Configuration Change Request.

4.1.3.3.2 Support current SharePoint environment and the implementation of future versions and applications.

4.1.3.3.3 Deliver and install all M&SWP 3.0 SharePoint software and configuration packages including signed and compiled code in support of M&SWP 3.0 SharePoint software and configuration

4.1.4 Subtask 4 – Application and Server Setup and Configuration.

4.1.4.1 Provide recommendation on server settings and server service settings to support M&SWP 3.0 application, to support enhancement of M&SWP 3.0, to support upgrading M&SWP 3.0 component application versions, and to support development of new M&SWP 3.0 functionality.

4.1.4.1.1 Provide recommendations on settings of Operating Systems including but not limited to Windows Server 2012, Windows Server 2016 and Red Hat Enterprise Linux 7 and their replacement versions for implementation by Government or Government Data Center personnel

4.1.4.1.2 Provide recommendations on settings of middleware including web servers, application servers and content management servers to support M&SWP 3.0 applications and development of M&SWP 3.0 applications for implementation by Government or Government Data Center personnel.

4.1.4.1.2.1 Provide support for all current M&SWP 3.0 software or software components.

4.1.4.1.2.2 Provide support for deployment and configuration of future M&SWP 3.0 software and software components.

4.1.4.1.3 Provide recommendation on settings for M&SWP 3.0 Database servers and services including but not limited to Microsoft SQL Server and Oracle for implementation by Government or Government Data Center personnel

4.1.4.1.4 Provide recommendations on upgrading of Operating Systems and middleware supporting M&SWP 3.0.

4.1.4.2 Provide recommendations for the support of M&SWP 3.0 servers and services installed in government approved hosted datacenters (such as Defense Information Systems Agency (DISA), Naval Information Warfare Systems Command (NAVWAR), a Navy approved Cloud environment, and the Portsmouth Naval Shipyard (PNSY) datacenter) while maintaining adherence to datacenter policies.

4.1.5 Subtask 5 – Data Mapping, Migration and Transformation Activities: The contractor shall provide the following data mapping and migration support when tasked via a SUBMEPP application configuration change request. Over the period of performance of this contract multiple data mapping and migration efforts may be requested via a configuration change request. The Government will perform migration activities under this contract with the contractor being responsible for supporting the Government migration process. The contractor will be responsible for reviewing the Government’s migration processes, providing recommendations and assistance with performing the following migration efforts efficiently and providing assistance with developing automation of the process to gain efficiency.

4.1.5.1 Map data housed in Applications or Databases

4.1.5.1.1 Provide assistance mapping data sources including database structure, field definitions and restrictions and data relations and their constraints.

4.1.5.1.2 Provide assistance develop a Data Structure Diagram or an Entity Relation Model to depict source data entities and their constraints.

4.1.5.2 Provide assistance in data mappings of target data systems including database structure, field definitions and restrictions and data relations and their constraints.

4.1.5.2.1 Provide assistance in developing a Data Structure Diagram or an Entity Relation Model to depict target data entities and their constraints.

4.1.5.3 Migrate data between approved Applications

4.1.5.3.1 The contractor shall provide support for migrations to SUBMEPP Databases or Applications including but not limited to current Oracle relational databases, SQL databases, Windchill, TeamCenter or SharePoint application.

4.1.5.3.2 The contractor shall provide support for migrations from SUBMEPP data sources including but not limited to: Oracle relational databases, SQL databases, Access databases and various file formats and libraries such as excel, txt, csv, xml and pdf.

4.1.5.3.3 The contractor shall provide support for migration to and from data sources owned by other Navy activities, DoD activities or DoD contracted partner activities.

4.1.5.3.4 The contractor shall assist in identify data type mismatches, conflicting constraints, and any other conflicts and discrepancies in data structure between a migration data source and migration target system.

4.1.5.3.4.1 The contractor shall provide assistance in developing a list of any conflicts or discrepancies between a source and target system and for each discrepancy identify:

4.1.5.3.4.1.1 The contractor shall provide assistance in assessing the impact of the discrepancy to the target data system on any functionality, workflows, data processing or outputs of the system.

4.1.5.3.4.1.2 The contractor shall provide assistance in assessing if the discrepancy can be rectified with a data transformation prior to, during or post migration.

4.1.5.3.4.1.3 The contractor shall provide assistance in assessing if the discrepancy must be rectified with a data cleansing or data quality corrective action within the source data system. If the source data system is M&SWP 3.0, the contractor shall identify if data corrective actions can be scripted or automated or require manual effort.

4.1.5.3.5 The contractor shall support the transformation of data prior to, during or post migration to meet data integrity needs, data quality needs and business needs of the target system.

4.1.5.3.6 The contractor shall provide assistance performing data cleansing actions or data quality corrective actions to meet the business needs of a data system.

4.1.5.4 The contractor shall assist in creating or Transform Data to meet business needs or to address data quality issues, including assisting with the creation or alteration of data to support a M&SWP 3.0 configuration change.

4.1.5.5 Staff in support of Subtask 5 must be compliant with security, training and Cyber Security Workforce (CSWF) requirements listed in paragraphs 4.1.8, 4.2 and 4.3.

4.1.6 Subtask 6 – Information Assurance and Cyber Security Configuration. No Configuration Change Requests will be issued for tasking under this subtask. The work incurred by this subtask is required to be completed in addition to and outside of the configuration change request process.

4.1.6.1 Ensure system conforms to the published DISA released STIG requirements as applicable to M&SWP Applications.

4.1.6.1.1 Configure and maintain M&SWP 3.0 Applications to meet current DISA STIG Requirements that are current when the change is implemented.

4.1.6.1.2 Assist hosted data center and government admin staff in meeting DISA STIG requirements when data center policy precludes necessary permissions for direct contractor action to meet STIG requirements.

4.1.6.1.3 Implement STIG changes within forty-five (45) days of a new STIG being released or updated.

4.1.6.1.4 Evaluate all current STIGs over the contract period of performance to ensure continued compliance with the STIGs as changes are implemented within the system.

4.1.6.2 Review and configure system security complying with guidance, directives, and issuances from the United States Cyber Command (USCYBERCOM), including but not limited to; Communication Tasking Orders (CTOs), Task Order (TASKORD), Operational Orders (OPORD), Information Assurance Vulnerabilities (IAVs) and other security requirements tracked in the Vulnerability Remediation Asset Manager (VRAM) system.

4.1.6.3 Maintain security posture of IT systems by ensuring Navy, DoD, DISA and industry recommended security patches are installed.

4.1.6.3.1 Patch SUBMEPP M&SWP 3.0 IT systems to maintain their security posture.

4.1.6.3.2 Where hosted data center policy excludes permissions to perform patching, the contractor shall assist data center staff and government admins with ensuring that SUBMEPP systems maintain their security posture via patching.

4.1.6.4 Adhere to the National Institute of Standards and Technology (NIST) Risk Management Framework to maintain an Authority to Operate (ATO) for M&SWP.

4.1.6.5 Provide application, database, and system administration support to include but not be limited to;

Creating application user accounts [Routine] Unlocking application user accounts [Routine] Modifying user permissions/roles [Routine] Identifying errors and performance issues and providing remediation support [Routine] Ensuring data is accessible and available from authorized sources and secure from unauthorized sources [Critical] Monitor system logs and automated systems daily for Operation Environment system outages and incidents and initiate incident response procedures and take corrective actions as necessary [Critical]

Perform the manual installation of software, software patches, and security updates to client systems as required by NMCI and project initiatives for all Contractor held government furnished computers [Routine].

Request, install and maintain DoD certificates on IT systems [Scheduled] Create and publish knowledge base articles as required for continued operation through the period of performance [Scheduled]

4.1.6.6 Staff need to be compliant with security, training and CSWF requirements. Execution of subtask 6 will require a combination of system administrator(s) and database administrator(s).

The navy requires separation of duties such that the system administrator cannot also be the database administrator.

4.1.7 Subtask 7 – Government Acceptance Testing and Validation

4.1.7.1 The Contractor shall maintain a Test Plan to test all system design and configuration and submit it for government approval.

4.1.7.1.1 The Test Plan shall ensure the complete traceability of each requirement and derived requirement, architecture element, and design specification to provided COTS/Configured functionality within the Application enhanced by or developed by the approved SUBMEPP Application Configuration Change Request.

4.1.7.1.2 The Test Plan shall include provisions for regular Testing Status Reports, a testing specific Project Management Plan, testing specific Project Schedules, and the development and maintenance of Test Cases that include the test steps necessary for a user to verify SUBMEPP Application Configuration Change Request requirements and derived requirements.

4.1.7.1.3 The Test Plan and Testing Project Schedule shall include full system testing including regression testing for functionality already present in the system.

4.1.7.1.4 The Test Plan shall include both contractor and government unit testing, integration testing, technical testing, user acceptance testing (including acceptable results), security and information assurance testing, software installation verification, and operational assessments.

4.1.7.1.5 The Test Plan and Test Project Schedule shall include defect identification and resolution (correct or revise system configuration and functionality) in agreement with Navy Maritime Maintenance Enterprise Solution (NMMES) test and evaluation document current at the time of contract award.

4.1.7.2 The Contractor shall perform contractor testing (and provide testing documentation) IAW its approved Test Plan.

4.1.7.3 The Contractor shall deliver all deliverables in the accepted Test Plan in agreement with the timelines laid out in the Test Plan and Testing Project Schedule.

4.1.7.4 The contractor shall resolve (correct or revise system configuration and functionality) defects identified by government testing IAW the accepted Test Plan.

4.1.8 Subtask 8 – Training

4.1.8.1 The contractor shall develop or update and maintain SUBMEPP training documentation for applications developed or enhanced by the approved SUBMEPP Application Configuration Change Request. Documentation shall be provided to the government for review, comment, and concurrence. The contractor must incorporate government comments prior to submitting documentation for final government approval.

4.1.8.2 All contractor enrolled in CSWF will have a training plan on record outlining when the required OS/CE certifications will be completed and identifying any Continuous Learning Units (CLUs) requirements for their certifications.

4.1.9 Subtask 9 – System Documentation

4.1.9.1 The contractor shall develop, update and maintain the SUBMEPP system documentation identified in the approved SUBMEPP Application Configuration Change Request.

Documentation shall be provided to the government for review, comment, and concurrence. The contractor must incorporate government comments prior to submitting documentation for final government approval.

4.1.9.1.1 The contractor shall develop, update, and maintain new and existing SUBMEPP system documentation associated with the application(s) developed or enhanced by the approved SUBMEPP Application Configuration Change Request.

4.1.9.1.2 The contractor shall deliver all signed and compiled code to the Government. This includes but is not limited to compiled “C’ code for Team Center, and compiled Java code for eQ products. All source code developed under this contract shall be delivered to the government free of proprietary markings, and shall be delivered with either government purpose rights, or unlimited rights.

4.2 Personnel

4.2.1. CSWF Personnel Certification: Contract personnel supporting this effort shall possess and maintain baseline security certifications in accordance with DoD 8140.01 “Cyberspace Workforce Management”, SUBMEPP requirements, and their supporting issuances. Contractor staff shall have all baseline security certifications prior to onboarding. All other certifications including but not limited to computing environment and SUBMEPP required certifications shall be completed within one hundred eighty (180) calendar days.

4.2.2. Mandatory Training: In addition to any CSWF training and certification required by DoD Manual 8140.01 and its supporting issuances, all personnel supporting tasks under this contract shall complete training as required by federal, departmental, and SUBMEPP policy. Mandatory training requirements are subject to change at any point during the life of the contract. Contractor Training Requirements:

4.2.2.1. In accordance with Submarine Maintenance, Engineering, Planning and Procurement Instruction (SUBMEPPINST) 12410.3, Employee Training and Development Manual, the contractor shall complete required mandatory training for onsite and offsite contractor personnel.

4.2.2..2 Deliverable Product and Schedule: The Contractor shall create and maintain a training and certification program. The Contractor shall create and maintain a matrix detailing the specific training credentials of each employee

4.2.2.3. In addition to CSWF, federal, departmental and SUBMEPP training, the contractor shall complete M&SWP 3.0 application specific training or have experience implementing and configuring core M&SWP 3.0 application software.

4.3 Security Requirements

4.3.1 Contractor employees shall be required to comply with all Government security regulations and requirements. Initial and periodic security training and briefings shall be provided by Government security personnel. Failure to comply with security requirements can be cause for removal of access to Government systems and Information, and remediation.

4.3.2 Personnel Security Requirements

4.3.2.1 Personnel Investigations: This effort involves the Contractor having access to Controlled Unclassified Information, and Privileged Information Technology (IT) System access. As such, it is requested, but not required, that the Contractor sponsor background investigations to the maximum practical extent. Where not possible or practical, the Government Participant shall sponsor Contractor investigations for Information and IT systems access. All Contractor personnel background investigations shall be verified by the SUBMEPP Security prior to performance.

4.3.2.2 The Contractor shall perform the following checks below to identify which users (employees or sub-participant employees) of DoD Information Systems (IS) are either privileged users (e.g., system administrators, system architects, or database administrators) or general users (e.g., non-IS associated system users).

4.3.2.2.1 For general users (non-privileged access) of information systems ensure they meet the following: Prior to being granted access to the Non-Classified Internet Protocol Router Network (NIPRNet), Contractor personnel shall minimally have a favorably completed National Agency Check (NAC) and a Common Access Card (CAC) with Public Key Infrastructure (PKI) Certificates issued.

4.3.2.2.2 Individuals performing work in privileged information system roles (e.g., system administrators, system architects, or database administrators) shall also undergo successful Scope Background Information Tier 5 (T5) with 5-year reviews.

4.3.2.3The Contractor must submit the request for investigation, either directly or through coordination with SUBMEPP Security, as soon as a position offer is tendered to an employee, including all requisite forms (E-QIP or Word Fillable SF 86 and fingerprint cards).

4.3.2.4 Interim IT-I (privileged) or IT-II (general user) access may be granted pending the completion of the Tier 5 (T5) or Tier 3 (T3) background investigation respectively, however that decision and authority is the responsibility of the SUBMEPP Commanding Officer, and interim access is not guaranteed. The NAC portion of the T5 or a previous valid NAC with Local Agency Checks and Credit Check (NACLC), Defense National Agency Check with Inquiries(DNACI), Tier 3 Investigation or Entrance National Security Check (ENTNAC) must be completed and favorably adjudicated before interim IT-I access will be considered. If the employee is not able to obtain an interim IT level approval commensurate with their position and duties within ninety (90) days of being assigned, they will not be eligible to continue work on this contract.

4.3.2.5 Citizenship Requirements: The Contractor is responsible for ensuring that all persons working on the program are U. S. citizens, and furnish evidence such as a birth certificate, naturalization papers, or passport upon Government Request. Industry and sub-Contractor personnel who hold current foreign passports shall not be permitted to work on this program.

Only if there is reliable documentary evidence that the foreign passport has been destroyed, invalidated or surrendered, might an Industry or sub-Contractor employee be permitted to perform on this program as according to Defense Security Service (DSS) requirements (11/20/2009). Each dual citizenship case shall be reviewed on a case by case basis. There is no guarantee that the individual shall be permitted to perform on this program.

4.3.2.6 Security Reporting Requirements: Should the Industry or sub-Contractor receive information regarding an employee which may affect the access of that employee to a SUBMEPP facility, (e.g., knowledge of arrests, felony conviction, misdemeanor conviction, use of or addiction to drugs or chemicals or both, abuse of alcohol, indebtedness, a change in or treatment of mental health, or any behavior, activities, or associations which tend to show that the individual is not reliable or trustworthy) , the Contractor shall advise the SUBMEPP Security immediately

4.3.2.7 Personnel Cybersecurity Workforce Certifications and Credentials

4.3.2.7.1 Contractor personnel who perform cybersecurity and cyberspace work roles must meet and maintain the qualification requirements in accordance with DoDD 8140.01, SECNAV 5329.2, and their supporting issuances. Personnel requiring privileged access to accomplish tasks will have their CSWF baseline certification prior to working on said tasks. Additional CSWF Operating System/ Computing Environment (OS/CE) requirements will be accomplished with in one hundred eighty (180) calendar days from assignment to SUBMEPP’s CSWF program.

4.3.2.7.2 Qualifications: Due to the nature of services to be provided, it is necessary that personnel be experienced and knowledgeable in the field of network management, software development and cybersecurity. At a minimum, the personnel shall possess the following education andcertification and experience requirements:

Additional Baseline Certifications for COMPTIA A+ Certification:

a. COMPTIA Network+ Certification

b. COMPTIA Security+ Certification

c. System Security Certified Practitioner (SSCP)

d. Certified Information Systems Security (CISSP)

e. Certified Information Security Auditor (CISA)

f. GIAC Security Essentials Certification (GSEC)

g. Security Certified Network Professional (SCNP)

h. Security Certified Network Architect (SCNA)

i. GIAC Security Expert (GSE)

Additional Baseline Certifications for COMPTIA Security+

a. System Security Certified Practitioner (SSCP)

b. Certified Information Systems Security (CISSP)

c. Certified Information Security Auditor (CISA)

d. GIAC Security Essentials Certification (GSEC)

e. Security Certified Network Professional (SCNP)

f. Security Certified Network…