Statement of Work (SOW) for Program and Business Digital Transformation Support

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Department 20, which is responsible for Machinery Programs and Platforms, as well as the Command Front Office, which is responsible for the management and coordination of business activities across the Command.

1.0.2 This contract is for non-personal services. It does not create employment rights with the U.S. Government whether actual, inherent, or implied

1.0.3 Government/Contractor Relationship

1.0.3.1 The services to be delivered under this Contract/Task Order are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract/Task Order between the Government and the Contractor's personnel. Therefore, it is in the best interest of the Government to provide both parties a full understanding of their respective obligations.

1.0.3.2 The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishable badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

1.0.3.3 Contractor personnel under this Contract/Task Order shall not engage in any of the inherently Governmental functions listed at FAR Subpart 7.5 or DFARS Subpart 207.5.

1.0.4 Employee Relationship:

1.0.4.1 The services to be performed under this Contract/Task Order do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

1.0.4.2 Rules, regulations, directives, and requirements that are issued by the U. S. Navy and NSWCPD under its responsibility for good order, administration, and security are applicable to all personnel who enter a Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.

1.0.4.3 Inapplicability of Employee Benefits: This Contract/Task Order does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

1.0.4.4 It is the Contractor's, as well as the Government's, responsibility to monitor Contract/Task Order activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

1.0.4.4.1 The Contractor shall notify the Contracting Officer in writing via letter or email within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this Section. The notice shall include the date, nature, and circumstances of the conduct; the name, function, and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct; identify any documents or substance of any oral communication involved in the conduct; and the Contractor's estimated date when, absent a response, cost, schedule or performance will be impacted.

1.0.4.4.2 The Contracting Officer will, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

(i) Confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) Countermand any communication regarded as a violation,

(iii) Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or

(iv) In the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it shall be furnished by the Contractor.

1.1 BACKGROUND

The Machinery Programs and Platforms Department (NSWCPD Department 20) is responsible for program management, engineering, technical, and logistics support for HM&E systems and equipment on U.S. Navy ships. To execute responsibilities, NSWCPD Department 20 requires the support of engineering, technical, logistic, and program management and business personnel to assist in the areas delineated in this Statement of Work (SOW). NSWCPD Department 20 shall have overall control and responsibility of the projects for which fall under this Contract.

1.2 SCOPE OF WORK

The Contractor shall provide expert database and software development, testing and maintenance to support digital integration services to NSWCPD. These digital transformation efforts shall improve support to U.S. Navy platforms including but not limited to: Carriers, Submarines, non-nuclear Surface Ships, and Cross-Platform applications. Tasking shall include:

· Tableau / software other than PowerPlatform / PowerBI

· Data analytics / Data validation

· Graphic Design / Graphic Interface Development

· Data management / warehouse management

· Consolidations / centralization of datasets from different, unconnected databases

· PowerAutomate Flow development and management

· Automation communications, administration, and updates

· Database development, management, sustainment, and maintenance

· Reference documentation

· Management/development of system architecture, reference diagrams, etc.

· Data warehouse support

· AI/ML components support

· Scheduling/IMS/Critical path analysis

· Predictive analytics

2.0 APPLICABLE DOCUMENTS

- Navy Issuances https://www.secnav.navy.mil/doni/default.aspx

- DOD Issuances https://www.defense.gov/Resources/Forms-Directives-Instructions/

- NAVSEAINST Library https://www.navsea.navy.mil/Resources/Instructions/

2.1 NAVSEA 0924-062-0010, Revision C with Change-3, Submarine Safety (SUBSAFE) Requirements Manual These documents can be referenced at: www.website.gov The Contractor shall reference and utilize the latest version available when performing tasks within this PWS.

3.0. REQUIREMENTS

Computer Programming/Software Development

1. The Contractor shall support the development, maintenance, and integration of command wide collaboration tools, websites, and databases. Tasking to include, but not limited to: development of new tools, transition and integration of existing tools and datasets, technical support, documentation, content updates, user enhancements, training guides, automation of dataflows and processes, front-end graphic design and back-end maintenance.

2. The contractor shall have experience using the Microsoft Power Platform, including but not limited to: PowerApps, PowerBI, Power Pages, Power Automate, Power Query, Dataverse, and the associated languages Power Fx, DAX, and Power Query M. The contractor shall manage and maintain existing Power Platform infrastructure including but not limited to: flows, data flows, CANVAS Apps, Model-driven apps, dataverse tables, security roles, column-level security, Power Admin Center functions, and PowerBI reports.

3. The contractor shall have experience with database management including but not limited to: how to store database information, ensure data is recoverable (aka Data Loss Prevention), and optimize database storage information so that corresponding tools can function as efficiently and quickly as possible.

4. The contractor shall have experience using Tableau, including but not limited to; importing or linking data, data manipulation, development of customized metrics.

5. The contractor shall have programming experience using Oracle database, including creation, troubleshooting, and maintenance. Contractor shall also have experience using a Front End to talk with and interact with the Oracle database.

6. The contractor shall have experience with Microsoft access database programming.

7. The contractor shall experience using Microsoft Excel, including but not limited to; create and manage formulas, set up conditional formatting, create bar and line charts/graphs, burn down tables, creation and execution of macros.

8. The contractor shall have experience using Microsoft SharePoint and Teams, including but not limited to; create and manage SharePoint sites, SharePoint Lists and Forms, SharePoint document libraries, use access lists, and Teams organization.

9. The contractor shall have experience of Microsoft Office products including, but not limited to, Word, PowerPoint, Visio, OneNote, Planner, and Project to develop formulas, macros and tools to analyze and maintain data for programmatic needs; efforts include work with large data sets that will be integrated into different management tools, databases and reports.

10. The contractor shall maintain a Graphical Style Guide and maintain and generate report templates in accordance with it. The Graphical Style Guide should include a consistent and repeatable color scheme, layout, navigation menus, font, and overall general style. Comment by Walls, Anthony J CIV USN NSWCDIV PHL PA (USA): May need a CRDL to correspond to this.

11. Contractor shall provide documentation of all requirements IAW NSWCPD SEP (Systems Engineering Process).

12. Contractor shall deliver Computer Software Products IAW for all developed applications.

13. All tools and processes shall be compliant with PEO Digital, authorized cloud based database and NMCI requirements.

14. All tools and programming executed under this contract will belong to the government (DON). The contractor shall deliver complete documentation, including Git repository handovers, deployment scripts, system interface diagrams, and a clear transition plan for Navy civilian/military IT personnel to maintain the tools/applications post-contract.

15. Contractor shall develop all software using a DevSecOps development environment.

16. Contractor shall perform Automated and Manual Developmental and Operational Testing.

17. Contractor shall inherit and implement all cyber controls from hosting web site.

18. Contractor shall have a methodology to identify bugs, prioritize issues, and track the implementation of the fixes. All bugs, issues, fixes must be logged in written format that can be reviewed by the government.

19. Contractor shall automate deploy of software releases utilizing a change control platform approved for use by the host website. Develop and maintain financial and workload planning databases utilizing existing NAVSEA Information Systems.

Support of Existing Tools

1. The contractor shall have familiarity with NSWCPD TIPC (Task Information and Planning Center), which is a PowerApp/Dataverse tool. Or an equivalent tool that tracks tasks, and their corresponding funding requirements.

2. The contractor shall have familiarity the NSWCPD System Health Assessment Database (SHA Database), which is an Oracle database tool. Or an equivalent tool that tracks tasks and corresponding risks.

3. The contractor shall have familiarity with the NSWCPD CHATS (Cyber Health Assessment Tool), which is a PowerApp/Dataverse tool or an equivalent tool that tracks Cyber RMF (Risk Management Framework) schedules and risks.

4. The contract shall have familiarity with Navy wide resource planning tools such as WAAP and TCHA (Technical Capabilities Health Assessment).

5. The contract shall have familiarity with NAVSEA Enterprise Planning System (NEPS), and the ability to acquire accounts. The contractor shall understand NEPS terminology, and how to export NEPS data for use in other tools.

6. The contractor shall acquire a NAVSEA Flankspeed Account.

7. The Contractor shall acquire a Navy ERP account. The contractor shall have an understanding of ERP and the ability to leverage standard ERP reports.

8. The contractor shall acquire an EDW/EDC Account.

Application Development Process

· Application Development Optional Application Development tasks will be executed ad hoc over the life of this contract. The contractor shall execute the below steps for Application Development.

· Identify Stakeholder Requirements: The contractor shall connect with current and potential future users to hear about their workflows, research needs, backlogs, and goals; conduct interviews, focus groups, surveys, and ethnographic work to help steer the details of the task.

· Database Build: The contactor shall integrate new data into existing databases or set up a new database; update cleaning processes, ETL pipelines, and schemas to facilitate the transfer and storage of data.

· Front End Design: The contractor shall design visualizations and user interactions based on stakeholder requirements.

· Front End Development: The contractor shall develop the output from the design step; build application programming interfaces to move data to the front end; deploy code to the container hosting environment.

· Application Testing: The contractor shall perform initial testing and run code through scanning pipelines; assist the Navy in performing user acceptance testing.

· Agile Development Methodology - The contractor shall adhere to Agile Software development methodology in execution of both Expansion and Application Development CLINS. This will include Agile Ceremonies (e.g., Sprint Planning, Sprint Review, and User Acceptance Testing) and will rely on the government Product Owner for prioritization of requirements.

Reports

· The contractor shall provide monthly reports.

· The contractor shall provide monthly status reports outlining work accomplished as well as a financial summary of monthly costs incurred, expenditures to date, amount of funds remaining, and estimated dates when funds will be expended. Financial information shall broken-down by labor and other direct costs as well as by technical instruction.

· The contractor shall provide monthly trip reports for any travel incurred.

· The contractor shall provide a monthly report listing all contractor personnel by name and program supported.

Disclaimer: The contractor will have access to procurement sensitive information for Naval Surface Warfare Center Philadelphia Division (NSWCPD). The contractor will be expected to sign a Non-Disclosure Agreement and a Non-Compete that precludes interest and ability to bid on any NSWCPD contracts for a specific period of time.

4.0 DATA REQUIREMENTS

TBD

5.0 SECURITY REQUIREMENTS

5.1 SECURITY TRAINING. The Contractor is responsible for completing all required Government mandated training to maintain security and network access to government sites and IT systems to include but not limited to: Antiterrorism Level 1 Awareness; Records Management in the DON: Everyone's Responsibility; Training and Readiness: The Active Shooter; NAVSEA Introduction to Controlled Unclassified Information; Operations Security (OPSEC); NAVSEA Counterintelligence Training; Privacy and Personally Identifiable Information (PII) Awareness Training; NAVSEA Physical Security training and Cybersecurity 101 Training. Certificates of successful completion shall be sent to the COR and as otherwise specified in the contract.

5.1.1 In accordance with the National Industrial Security Program Operating Manual (NISPOM) (37 CFR Part 117), Contractor personnel that require access to Department of Navy (DON) information systems and/or work on-site require an open investigation or favorable adjudicated Tier 3 investigation. An interim clearance is granted by DCSA and recorded in the Defense Information System for Security (DISS). Must have a favorable fingerprint an open or closed investigation with a favorable adjudication in DISS is required prior to issuance of a badge providing access to NSWCPD buildings. Furthermore, if the Navy Central Adjudication Facility has made an unfavorable determination, access will be denied. For Common Access Card (CAC) you must have an open investigation and/or a favorably adjudicated investigation. Interim security clearance is acceptable for a CAC.

Access will be denied for anyone that has eligibility pending in DISS. Vetting through the National Crime Information Center, Sex Offender Registry, and the Terrorist screening database shall be process for a contractor that does not have a favorable adjudicated investigation.

5.1.2 Within 30 days after contract award, the contractor shall submit a list of all contractor personnel, including subcontractor employees, who will have access to DON information systems and/or work on-site at one of the NSWCPD sites to the appointed Contracting Officer Representative (COR) via email. The contractor shall provide each employee's first name, last name, contract number, the NSWCPD technical code, work location, whether or not the employee has a CAC and or Standard Access Control Badge (SACB), the systems the employee can access (including, NMCI, RDT&E, and the systems described in Section 3.0), and the name of the Contractor's local point of contact, phone number and email address. Throughout the period of performance of the contract, the Contractor shall immediately provide any updated information to the COR when any Contractor personnel changes occur including substitutions or departures.

5.2 ON SITE WORK. Contractor personnel that require a badge to work on-site at one of the NSWCPD sites must provide an I-9 form to verify proof of citizenship. The I-9 form shall be signed by the company Facility Security Officer or the company Human Resource Department. In addition to the I-9 form, Contractors shall also bring their birth certificate, current United States Passport or naturalization certificate and state issued REAL ID to the NSWCPD Security Officer at the time of badge request to verify citizenship. Any contractor that has unfavorable information that has not been favorably adjudicated, by Department of Defense Central Adjudication Facility (DOD CAF) will not be issued a badge. Finally, contractors shall supply a copy of their OPSEC Training Certificate or other proof that the training has been completed.

5.2.1 RESERVED

5.2.4 Reserved

5.3 DD254 REQUIREMENT. This effort requires access to classified information up to the Secret level. No classified data will be generated or stored by the Contractor. The Contractor is required to have and maintain a Secret clearance. The requirements of the attached DD Form 254 apply.

5.3.1 The contractor is required to maintain a Facility Security Clearance (FCL) in accordance with the DD254 to perform certain work under the contract. Although it is not required at time of award, it shall be obtained within 30 DAYS after award. Otherwise the government will have no obligation to continue ordering work under the contract and may not exercise any of the available options.

5.3.2 The Contractor shall appoint a Facility Security Officer (FSO), who shall (1) be responsible for all security aspects of the work performed under this contract, (2) assure compliance with the National Industrial Security Program Operating Manual (NISPOM) (32 CFR Part 117), and (3) assure compliance with any written instructions from the NSWCPD, Security Office.

5.3.3 Contractor must submit a flow down request for sharing of classified and other sensitive information between prime and subcontracts in writing to the COR and Security Contracting Officer (SCO), louise.r.brunson.civ@us.navy.mil. Each request must reference a contract number identifying the specific information for which approval is sought, a justification for needing to share the information, the contractor's name and its contract number under which the requested information will be shared.

5.3.4 The contractor shall forward signed copies of DD254s provided to subcontractors to the Naval Surface Warfare Center Philadelphia Division (NSWCPD), ATTN: Security.

5.3.5 The contractor shall direct the subcontractor to obtain approval, through the prime Contractor, for the public release of information received or generated by the sub through the prime Contractor.

5.3.6 The contractor shall submit the subcontractor request for public release through the technical point of contact identified on the DD 254.

Additional information related to the facility clearance process can be obtained by visiting www.dss.mil or http://www.dss.mil/isec/pcl_index.htm.

5.4 OPERATIONS SECURITY (OPSEC)

5.4.1 The Contractor shall protect critical information associated with this contract to prevent unauthorized disclosure. The NSWC Philadelphia Division's (NSWCPD) Critical Information List (CIL)/ CIIL (Critical Indicators and information list) will be provided on site, if warranted. Performance under this contract requires the contractor to adhere to OPSEC requirements, which may include the NSWCPD Contractor OPSEC Plan. When the NSWCPD Contractor OPSEC Plan is required, the contractor shall return acknowledgment of the plan within 15 days of receipt. During the period of this contract, the Contractor may be exposed to, use, or produce, NSWCPD Critical Information (CI) and/or observables and indicators which may lead to discovery of CI. NSWCPD's CI will not be distributed to unauthorized third parties, including foreign governments, or companies under Foreign Ownership, Control, or Influence (FOCI) unless such FOCI has been appropriately mitigated through measures approved by the Defense Counterintelligence and Security Agency. Questions concerning these requirements shall be directed to the PCO.

5.4.2 CUI correspondence transmitted internally on the contractor's unclassified networks or information systems, and externally, shall be protected per NIST SP-800-171, Protecting Controlled Unclassified Information (CUI) in Non-federal Systems and Organizations.

Assembled large components/systems being transported to and from testing areas, other production or government facilities (whether or not on public roadways) shall be in an enclosed van trailer or covered flatbed trailer. Component/System outside storage, staging, and test areas shall be shielded/obscured from public view wherever physically possible.

5.4.3 NSWCPD's CI shall not be publicized in corporate wide newsletters, trade magazines, displays, intranet pages or public facing websites. Media requests related to this project shall be directed to the PCO, and the COR who will forward the required to the NSWCPD Public Release Authority for review.

5.4.4 Any attempt by unauthorized third parties to solicit, obtain, photograph, or record, or; incidents of loss/compromise of government Classified or CI, Business Sensitive, Company Proprietary information related to this or other program must be immediately reported to the contractor's Facility Security Officer and Cognizant Security Office and/or the Naval Criminal Investigative Service, and the NSWC PD Security Division (Code 105).

5.4.5 This SOW has been reviewed against the requirements of SECNAVINST 4200.35. SAIRC controls are not required.

5.5 RECEIPT, STORAGE, AND GENERATION OF CONTROLLED UNCLASSIFIED INFORMATION (CUI) All Controlled Unclassified Information (CUI) associated with this contract must follow the minimum marking requirements of DoDI 5200.48, Section 3, paragraph 3.4.a, and include the acronym "CUI" in the banner and footer of the document. In accordance with DoDI 5200.48, CUI must be safeguarded to prevent Unauthorized Disclosure (UD). CUI export controlled technical information or other scientific, technical, and engineering information must be marked with an export control warning as directed in DoDI 5230.24, DoDD 5230.25, and Part 250 of Title 32, CFR. Nonfederal information systems storing and processing CUI shall be protected per NIST SP-800-171, or subsequent revisions. All transmissions to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) and posting on social media websites (Facebook, Instagram, Twitter, LinkedIn, etc.) are prohibited. Destroy CUI associated with this contract by any of the following approved methods: A cross-cut shredder listed on the “NSA/CSS Evaluated Products List for High Security Crosscut Paper shredders”; a certified commercial destruction vendor; a central destruction facility; incineration; chemical decomposition; pulverizing, disintegration; or methods approved for classified destruction.

5.6 Planning, Programming, Budgeting and Execution (PPBE) Data.

When contractor employees, in the performance of their duties, are exposed to Planning, Programming, Budgeting and Execution (PPBE) data, a Non-Disclosure Agreement (NDA) with all affected contactor personnel must be executed in coordination with the COR and PCO to ensure safeguarding disclosure of this data. Additional NDAs for access to government databases that contain PPBE data may be required.

5.7 U-NNPI SECURITY REQUIREMENTS

N/A

5.8 U-NNPI

N/A

5.9.2 Specific Requirements for Protecting U-NNPI

N/A

6.0 PLACE OF PERFORMANCE

6.1 The contractor's primary place of performance shall be at the contractor's facility (or via telework). It is estimated that 90% of the work will occur at the contractor facility (or via telework), with up to 10% of work on-site at the NSWCPD facility (Philadelphia Navy Yard). While it is anticipated that the contractor will primarily perform its work at a contractor site or via telework, the contractor may have to visit NSWPCD on an ad-hoc basis.

If performance will be on a Government site, it will take place at NSWCPD (Naval Surface Warfare Center Philadelphia).

6.1.1 Performance will occur at the following government sites: NSWCPD (Naval Surface Warfare Center Philadelphia), Philadelphia, PA.

6.1.2 N/A 6.1.3

N/A 6.1.4 N/A

6.1.5 Reserved

6.1.6 Early Dismissal and Closure of Government Facilities

N/A 6.1.7 N/A

7.0 TRAVEL

7.1 The Contractor may be required to travel from the primary performance location when supporting this requirement on an ad-hoc basis. The yearly estimated number of trips is shown in the below table.

7.2 The number of times the Contractor may be required to travel to each location cited above may vary as program requirements dictate, provided that the total estimated travel cost is not exceeded. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. All travel shall be approved before travel occurs. Approval may be via email by the Contracting Officer (PCO), the Contacting Officer's Representative (COR) or the fully executed Technical Instruction (TI) signed by the Contracting Officer.

7.2.1 In accordance with the TI instructions, before initiating any travel the Contractor(s) shall submit a detailed and fully-burdened estimate that includes the number of employees traveling, their expected travel costs for airfare, lodging, per diem, rental car, taxi/mileage and any other costs or actions requiring approval. The travel estimate shall be submitted to the Contracting Officer's Representative (COR) and Contract Specialist. Actuals cost, resulting from the performance of travel requirements, shall be reported as part of the Contractor's monthly status report. The reportable cost shall also be traceable to the Contractor's invoice

7.3 All travel shall be conducted in accordance with FAR 31.205-46, Travel Costs, and B-231-H001 Travel Cost (NAVSEA) and shall be pre-approved by the COR (CDRL A002).

7.4 Travel Costs

7.4.1 The current "maximum per diem" rates are set forth in the (i) Federal Travel Regulations for travel in the Continental United States; (ii) Joint Travel Regulations for Overseas Non-Foreign areas (e.g., Alaska, Hawaii, Guam, Puerto Rico, etc.); and (ii) Department of State (DOS) prescribed rates for foreign overseas locations.

7.5 Reserved

8.0 GOVERNMENT FURNISHED PROPERTY

Government-Furnished Property (GFP) means property in the possession of, or directly acquired by, the Government and subsequently furnished to the Contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes Contractor-Acquired Property (CAP).

All Government Property is property of the U.S. Government and shall not be transferred to any individual or agency, public or private, without the express written approval of the originating Contracting Officer. Accountability for Government Property under this contract/order shall be managed in accordance with FAR Part 45, DFARS Part 245, and the Government Property clauses included within the Solicitation and Contract.

GFP is required for completion of task(s) under this SOW. See GFP attachment for detailed information. All GFP identified in the GFP attachment will be provided no later than INSERT DATE TBD The Contractor shall notify the COR via email, with the TPOC and PCO Cc'd, of any GFP received in error or not on an approved GFP attachment in EDA within seven (7) business days of physical receipt of the property.

8.1 Reporting Requirements.

The Contractor shall follow all reporting requirements to accurately account for GFP.

8.1.1 PIEE Shipment Reporting.

Contractor Receipt Reporting: Clause 252.245-7005 "Management and Reporting of Government Property" requires the Contractor to report receipt of all GFP using the PIEE GFP Module, regardless of whether the Government has submitted a PIEE electronic shipment.

Contractor Shipment Reporting: Clause 52.245-1 "Government Property" (including Alternates 1 & 2) requires the Contractor to report to the Government when GFP is returned. Clause 252.245-7005 requires this notification to be an electronic shipment through the PIEE GFP Module.

A DD Form 1149 shall accompany all government property shipped between the Government and the Contractor using a third party, such as UPS, FedEx, or USPS. The DD 1149 does not take the place of the PIEE shipment. It is a requirement in addition to the PIEE shipment

8.1.2 Inventory Reporting.

The Contractor shall submit a Government Property Inventory Report (Periodic) in accordance with CDRL XXXX. The CDRL identifies all reporting requirements. The Contractor shall continue to submit an inventory report IAW the CDRL even if all GFP has been returned to the Government. The Contractor shall also submit a Government Property Inventory Report (Final) in accordance with CDRL XXXX. When the Contractor has never received any GFP, the Contractor shall annually certify to the Procuring Contracting Officer (PCO) via email, with the Contracting Officer's Representative (COR) and Technical Point of Contact (TPOC) Cc'd, that it does not have any GFP.

The Contractor shall also provide support within a reasonable timeframe after any Government request (to include by DoD support agencies such as DCMA) to support any Government audit in which GFP, or its related documentation, is requested as part of normal audit processes.

8.1.3 Lost, Damaged or Stolen GFP Reporting.

Clause 52.245-1 (including Alternates 1& 2) requires the Contractor to investigate and report to the Government (to the COR via email, with the TPOC and PCO Cc'd) all incidents of lost or damaged Government property as soon as the discovery is made. Clause 252.245-7005 requires the Contractor to report loss of Government property by using the Property Loss functionality within the PIEE GFP Module. The Contractor shall support the Government's process to assign liability and document the loss in support of lost, damaged or stolen GFP.

8.1.4 Excess Property Reporting.

In accordance with Clause 52.245-1 paragraph (f)(viii)(A), the Contractor shall promptly disclose to the COR via email, with the TPOC and PCO Cc'd, Government property in its possession that is excess to contract performance. This reporting requirement also applies to excessive CAP, which must also be disclosed as soon as the material is identified as excessive.

8.2 Loss of Government Property.

Lost, Damaged or Stolen GFP shall be processed in accordance with the processes in Clause 52.245-1.

8.3 Property Management and Use.

The Contractor shall perform property management in accordance with Clause 52.245-1.

8.4 Subcontractor Requirements.

In accordance with Clause 52.245-1, the Contractor shall award subcontracts that clearly identify Government property that will be provided and the extent of any restrictions or limitations on their use. The Contractor shall also ensure appropriate flow down of contract terms, conditions and all relevant contractual information to all subcontractors who will use GFP. This includes dissemination of all information necessary for the subcontractor to properly track GFP in their property management system, such as the contract/order number, the serial management requirements and unit acquisition cost(s). It is the Contractor's responsibility to assure that subcontracts are properly administered and periodically reviewed for compliance.

8.5 Contractor Acquired Property (CAP).

All CAP is titled to the Government and shall be treated to the same standard as GFP. CAP may be bought back by the Contractor in accordance with Clause 52.245-1. All CAP not bought back by the Contractor shall be processed following PCO or Property Administrator (PA) (if assigned) instructions in the PIEE GFP Module.

8.6 Property Disposition.

All GFP shall be dispositioned to the Government as soon as it becomes excessive to contract performance unless otherwise directed in writing by the PCO or Property Administrator. GFP may be dispositioned by being returned to the Government, having custodianship transferred to another contract, having the item(s) scrapped, processing the item(s) through Plant Clearance, or abandoning the property with the Contractor. Regardless of the method, all Government Property shall be processed by the end of contract PoP.

Disposition shall be processed as instructed by the PCO, COR (if delegated), PA (if assigned), and Plant Clearance Officer (PLCO) (if assigned) following the guidance provided in accordance with Clause 52.245-1 paragraph (j) (including Alternates 1 & 2) and Clause 252.245-7005.

8.6.1 Property Disposition Instructions.

Unless directed otherwise, all GFP shall be returned to the Government Clause FAR 52.245-1, Clause 252.245-7005, as well as PCO instructions, and contract mod directions.

All GFP shall be returned to the follow address:

NWSC Philadelphia Division 1601 Langley Ave, Building 542 Philadelphia, PA 19112 Transfer to Another Contract: If instructed by the PCO, the Contractor shall transfer the property to another Government contract in accordance with Clause 252.245-7005. The Contractor shall coordinate the transfer with the gaining contractor and provide all necessary documentation.

Sale to a Third Party: The Contractor may be authorized to sell the property, including scrap, to a third party, subject to Government approval. The Contractor shall comply with all applicable regulations regarding the sale of Government property. Any proceeds from the sale of Government property shall be remitted to the Government in accordance with Clause 252.245-7005.

Abandonment/Destruction: The PCO or PLCO may without further approval-

(1) Direct the contractor to destroy Government property;

(2) Abandon non-sensitive property at the contractor's or subcontractor's premises; or

(3) Abandon sensitive property at the contractor's or subcontractor's premises, with contractor consent.

The Contractor shall comply with all applicable environmental regulations regarding the abandonment or destruction of property. The Contractor shall provide documentation of the destruction to the Contracting Officer and follow all prescribed instructions in accordance with Clause 52.245-1.

Plant Clearance: If instructed, the Contractor shall complete the plant clearance inventory schedule using the Plant Clearance capability of the PIEE GFP module to generate an electronic equivalent of the SF 1428, Inventory Disposal Schedule. The Contractor shall obtain PCO or PLCO approval prior to disposal of GFP in accordance with Clause 52.245-1.

8.7 Property Tagging.

The Contractor can either tag issued equipment or use the provided NSWCPD Plant property barcodes, or NMCI asset tags. If the contractor chooses to use their own tag, it shall not cover the NSWCPD barcode, or NMCI asset tag. The NSWCPD barcode, and/or NMCI asset tag number, when provided, shall be used on GFP inventory reports per DI-MGMT-80441D.

8.8 Property Closeout.

The Contractor shall aid the PCO and Property Administrator (if assigned) in contract closeout by promptly performing and reporting any issue that may prevent contract property closeout in accordance with Clause 52.245-1paragraph (f)(X) (including Alternates 1 & 2). This includes reporting, investigating and securing closure of all loss of Government property cases; physically inventorying all property upon termination or completion of this Contract/TO; and disposing of items at the time they are determined to be excess to contractual needs, per PCO/PA instructions.

9.0 GOVERNMENT FURNISHED INFORMATION

9.1 GFI is for informational purposes and that use by the Contractor is optional.

10.0 PURCHASES

10.1 Only items directly used and incidental to the services for this Contract/Task Order and for work within the scope of the Statement of Work/Performance Work Statement, shall be purchased under the Other Direct Cost (ODC) line items. Purchases of an individual item that is valued above $350,000 shall be approved by the Contracting Officer prior to purchase by the Contractor. The purchase request and supporting documentation shall be submitted via email to the Contracting Officer and the Contracting Officer's Representative (COR) it shall be itemized and contain the cost or price analysis performed by the Contractor to determine the reasonableness of the pricing. Include the following language where negotiated subcontracts are expected: Provide copies of price estimates from at least 2 vendors.

10.2 Information Technology (IT) equipment, or services must be approved by the proper approval authority. All IT requirements, regardless of dollar amount, submitted under this Contract/Task Order shall be submitted to the PCO for review and approval prior to purchase. The definition of information technology is identical to that of the Clinger-Cohen Act, that is, any equipment or interconnected system or subsystem of equipment that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. Information technology includes computers, ancillary equipment, software, firmware and similar procedures, services (including support services), and related resources.

11.0 Counterfeit Material Prevention

11.1 Electronic End-Items

Please select the SOW language appropriate for your procurement from Appendix D (Appendix B to this document) of the COUNTERFEIT MATERIEL PROCESS GUIDEBOOK, Office of the Assistant Secretary of the Navy (Research, Development & Acquisition) Acquisition and Business Management June 2017.

11.2 Non-Electronic Materials

11.2.1 Department of the Navy contractors (and their subcontractors at all tiers) who obtain critical or high risk materiel shall implement a risk mitigation process as follows:

11.2.1.1 If the materiel is currently in production or currently available, materiel shall be obtained only from authorized suppliers

11.2.1.2 If the materiel is not in production or currently available from authorized suppliers, materiel shall be obtained from suppliers that meet appropriate counterfeit avoidance criteria

11.2.1.3 Contractor shall notify the contracting officer when critical or high risk materiel cannot be obtained from an authorized supplier;

11.2.1.4 Contractor shall take mitigating actions to authenticate the materiel if purchased from an unauthorized supplier

11.2.1.5 Contractor shall report instances of counterfeit and suspect counterfeit materiel to the contracting officer and the GIDEP as soon as the contractor becomes aware of the issue.

12.0 PERSONNEL

12.1 Personnel Requirements. All persons proposed in key and non-key labor categories shall, at the time of proposal submission be U.S. citizens.

12.2 Clause 52.222-2 "Payment for Overtime Premiums" will provide for the total approved dollar amount of overtime premium or will state "zero" if not approved. If overtime premium has not been approved under this contract in accordance with Clause 52.222-2, overtime effort to be performed shall be requested from the Contracting Officer prior to performance of premium overtime. For overtime premium costs to be allowable costs; the Contracting Officer is required to approve the performance of overtime prior to the actual performance of overtime. The dollar amount in FAR 52.222-2 shall equal overtime premium negotiated between the Government and the prime contractor. This overtime premium amount shall equal the prime contractor's unburdened premium OT labor costs plus the subcontractors' fully-burdened premium OT labor costs.

12.3 The level of effort for the performance of the resultant Contract/Task Order is based on the labor categories and hours per year provided in the table below. The Management and Support labor category is intended to capture corporate and local-level management, as well as general and administrative support, to include administrative/financial/clerical, program control, and Task Order or contract business management/administration (to include progress report preparation). Offerors are cautioned that the costs of such support services are generally considered to be indirect in nature. However, the Offeror is permitted to include direct labor costs for "Management and Support" hours when it is in accordance with its standard DCAA-approved practice to do so. If an Offeror does not propose Management and Support labor hours, no labor costs associated with Management and Support effort will be allowable for payment as a direct charge.

DATABASE MANAGEMENT ANALYST III

DATA SCIENTIST II

MODEL BASED SYSTEMS ENGINEER II

MODEL BASED SYSTEMS ENGINEER III

*These hours are only included when the labor efforts for this category are charged direct in accordance with the firm's approved Accounting Policy and Procedures and/or Disclosure Statement, and the table shall reflect 480 hours per year (2,400 hours total). Otherwise, these hours shall be charged indirect and the table shall reflect 0 hours for this labor category.

12.4 Key Personnel

12.4.1 The Contractor shall allow as many personnel as practicable to remain on the job to help the successor maintain the continuity and consistency of the services required by this Contract/Task Order in accordance with Clause 52.237-3 Continuity of Services (Jan 1991). The Contractor also shall disclose necessary personnel records and allow the successor to conduct on-site interviews with these employees. If selected employees are agreeable to the change, the Contractor shall release them at a mutually agreeable date and negotiate transfer of their earned fringe benefits to the successor.

12.4.2 In accordance with C-237-H002 Substitution of Key Personnel, the following labor categories are designated as the target Key Personnel for this contract. Resumes will be submitted for each category in the quantities indicated by the key category description. Target qualifications are listed below for each education and work experience qualifications for each key personnel labor category. The proposed combined expertise of all proposed key personnel shall cover at a minimum all requirements for task areas (insert specific paragraph references) in the performance work statement.

12.4.3 The Contractor shall provide individuals to fill the key positions identified below.

12.4.4 The Contractor shall indicate within the personnel section of its proposal, and/or indicate within individual submitted resume(s), any personnel security clearance requirements as stipulated in section 12.1 above.

MANAGER, PROGRAM/PROJECT II (one resume required):

Target Education: Bachelor's level degree in any technical or managerial discipline.

Target Experience: Five (5) years of experience in the operation, maintenance and testing of U.S. Navy machinery controls system. This individual shall have five (5) years of experience as a Program Manager, to include contract and sub-contract management, budgeting, scheduling, planning, estimating, and progress.

12.5 Non-Key Personnel

In the performance of this effort, the Contractor shall fully staff the non-key positions listed below with qualified individuals. The Contractor shall provide individuals to fill the non-key positions identified below:

ANALYST, FINANCIAL SYSTEMS I

Minimum Education: Bachelor's Degree Minimum Experience: No professional experience required.

COMPUTER PROGRAMMER II

Minimum Education: Bachelor’s degree in from an accredited college or university in Computer Programming, Information Technology, Software Engineering, Computer Engineering, or equivalent.

Minimum Experience: Three (3) years of professional experience in computer design, software development or computer networks. This experience should include at least one (1) year with Power BI/Power Apps or equivalent system.

COMPUTER PROGRAMMER III

Minimum Education: Bachelor’s degree in from an accredited college or university in Computer Programming, Information Technology, Software Engineering, Computer Engineering, or equivalent.

Minimum Experience: Seven (7) years of professional experience in computer design, software development or computer networks. This experience should include at least three (3) years with Power BI/Power Apps or equivalent system.

DATABASE MANAGEMENT ANALYST III

Minimum Education: Master's Degree Minimum Experience: 10 years of professional experience administering, testing, and implementing computer databases

DATA SCIENTIST II

Minimum Education: Bachelor's Degree Minimum Experience: 3 years of professional experience with data science.

ENGINEER, COMPUTER II

Minimum Education: Bachelor's level degree in Computer, Electrical or Electronics Engineering or Mathematics with field of concentration in computer science from an accredited university.

Minimum Experience: Three (3) years of professional experience in computer design, software development or computer networks. Must have one (1) year of experience reviewing, analyzing, and modifying programming systems, including encoding, testing, debugging and installing. Must have one (1) year of experience gathering requirements from users, creating specifications and developing code.

ENGINEER, COMPUTER III

Minimum Education Requirements: Bachelor's degree in Computer, Electrical or Electronics Engineering or Mathematics with field in concentration in computer science from an accredited university.

Minimum Work Experience: Seven (7) years of professional experience in computer design, software development or computer networks. Must have three (3) year of experience reviewing, analyzing, and modifying programming systems, including encoding, testing, debugging and installing. Must have three (3) year of experience gathering requirements from users, creating specifications and developing code.

LOGISTICIAN II

Minimum Education: Bachelor's Degree Minimum Experience: Three (3) years of experience in the development of updating ILS products for US Navy HM&E Systems.

MODEL BASED SYSTEMS ENGINEER II

Minimum Education: Bachelor's Degree in engineering, operations research, or other sciences where the utilization of advanced math skills is required (e.g. business, mathematics, statistics, and probability) Minimum Experience: 3 years of professional experience performing Model Based Systems Engineering

MODEL BASED SYSTEMS ENGINEER III

Minimum Education: Master's Degree in engineering, operations research, or other sciences where the utilization of advanced math skills is required (e.g. business, mathematics, statistics, and probability) Minimum Experience: 10 years of professional experience performing Model Based Systems Engineering

12.6 DON Cyberspace IT (Information Technology) / Cybersecurity & Information Assurance Functions and Personnel Requirements (DELETE SECTION IF NOT APPLICABLE) The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including—

(1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and

(2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.

(b) Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

(c) Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

Reminder: The SOW for requirements involving Cyber IT/CSWF/IAWF functions must be reviewed by the NSWCPD Cybersecurity…