BUILDER - PWS 25RNA000273 DRAFT.pdf

1 of 16 | P a g e Attachment 1 CONTRACT #: TBD

UNITED STATES DEPARTMENT OF ENERGY (DOE)

NATIONAL NUCLEAR SECURITY ADMINISTRATION (NNSA)

OFFICE OF INFRASTRUCTURE (NA-90)

OPERATIONS & MAINTENANCE DIVISION (NA-914)

BUILDER INFRASTRUCTURE MANAGEMENT - TECHNICAL SUPPORT

PERFORMANCE WORK STATEMENT (PWS) DRAFT

SOLICITATION: 89233125RNA000273 / CONTRACT: TBD

2 of 16 | P a g e

Attachment 1 CONTRACT #: TBD

1. EXECUTIVE SUMMARY

This PWS describes the performance objectives and standards that are expected of the Contractor to successfully deliver quality software and consulting services in support of the NNSA’s BUILDER Program.

“BUILDER” as mentioned herein, refers to the BUILDER Sustainment Management SystemTM developed by United States Army Corps of Engineers’ (USACE) Construction Engineering Research Laboratory (CERL), a branch of the Engineer Research and Development Center (ERDC).

1.1 Background

The NNSA is responsible for a vast and complex portfolio of cutting-edge research and development laboratories, manufacturing and production facilities, and mission enabling infrastructure. With its origins in the Manhattan Project, this portfolio of land, roads, utilities, and facilities is the foundation of the NNSA’s ability to conduct its mission and represents one of America’s premier assets for science, technology, innovation, and national security.

Unfortunately, investment in NNSA’s infrastructure has not kept pace with the growing need to modernize and replace degrading Cold War-era facilities and, as the 2018 Nuclear Posture Review confirmed, a renewed focus is required to recapitalize and revitalize our national security enterprise.

To meet this challenge, the NNSA is deploying a suite of holistic, data-driven, risk-informed tools and metrics to better assess risks, prioritize investments, and cost effectively modernize its aging infrastructure. Central to this new, Science-Based Infrastructure Stewardship approach is the BUILDER Sustainment Management System (SMS).

The BUILDER Sustainment Management System (SMS) is a web-based tool developed by the U.S. Army Corps of Engineers that provides a consistent, repeatable, quantitative method to track and predict the condition of assets and their system components and subcomponents. It uses a single, structure-based approach to assess infrastructure and to inform infrastructure renewal decisions based on current and predicted system conditions (using a 0-100 condition index score), mission priorities, and acceptable risk tolerance levels. BUILDER is recognized by the National Academies of Science as a best-in-class practice for infrastructure management and has been actively implemented across the NNSA real property infrastructure portfolio since 2014. For more information on BUILDER or other USACE SMS products visit:

https://www.sms.erdc.dren.mil/

The NNSA procured BUILDER in FY2014 and completed BUILDER implementation in FY2024 by using it to generate Deferred Maintenance (DM), Repair Needs (RN), Replacement Plant Value (RPV), and Overall Asset Condition for all active real property buildings, trailers, and other structures and facilities (OSF’s) as part of the annual Facilities Information Management System (FIMS) data submission (see section 1.2 for more information on FIMS). This contract provides the means for continued technical support to ensure

3 of 16 | P a g e the NNSA has accurate, consistent, and timely BUILDER data necessary to effectively manage its infrastructure and successfully meet federal real property reporting requirements.

The NNSA will likely transition to USACE’s Enterprise Sustainment Management System (ESMS) from the existing BUILDER software platform during this contract’s period of performance (including option periods). (ESMS is the next evolution of the SMS software solution and integrates BUILDER and its companion domains (e.g., PAVER, ROOFER, etc.) into a single platform). USACE expects to first release ESMS to a limited customer base in 2025 although the NNSA will not transition to the new tool until it has been properly vetted by the NNSA BUILDER Software Team which includes the Contactor executing this PWS. The tasks outlined in this contract to support BUILDER implementation/sustainment can also be interchangeably assigned to support ESMS and are expected to result in the same level of effort regardless of platform. Tasks will either be in support of BUILDER or ESMS and are not expected to be duplicative (e.g., the Contractor is not expected to create duplicate catalog items for BUILDER and ESMS, catalog development will be the same and feed either BUILDER or ESMS as appropriate).

1.2 BUILDER Program Software Environments

The NNSA hosts three, separate BUILDER software environments each with its own dedicated purpose:

Production – primary BUILDER dataset which includes live program data and is used for generating all reporting metrics

Training – secondary BUILDER dataset used for training new users or testing data changes before they go live in Production

Integration – secondary BUILDER dataset used for testing software releases before they are deployed to the Production and Training environments, and for developing software integration protocols for linking outside systems to BUILDER such as site computerized maintenance management systems (CMMS)

BUILDER Environment URLs SPIRE Portal URLs SPIRE API URLs

Prod https://BUILDER.g2.doe.gov https://spireportal.g2.doe.gov https://spireapi.g2.doe.gov Trng https://BUILDERtraining.g2.doe.gov https://spiretrainingportal.g2.doe.gov https://spiretrainingapi.g2.doe.gov

Integ https://BUILDERtraining.g2.doe.gov https://spiretrainingportal.g2.doe.gov https://spiretrainingapi.g2.doe.gov

NNSA sites are expected to keep the Production environment up-to-date with the latest field data and ensure asset-level data is aligned with DOE’s FIMS and NNSA’s Program Management Information System, Generation 2 (G2) program. This alignment is especially critical in the last quarter of each fiscal year as NNSA Headquarters (NNSA HQ) prepares for the annual end of year (EOY) FIMS data submission.

G2 was deployed in FY2015 to provide real-time, actionable data to inform and track infrastructure investments and currently hosts BUILDER and its associated companion software programs. For more information on G2 visit: https://nnsa.energy.gov/g2 or G2 Online Training |

4 of 16 | P a g e

Review 360 (articulate.com).

FIMS is the Department's corporate real property database as mandated by DOE Order 430.1C.

FIMS is used to satisfy annual data reporting requirements for both DOE and the Federal Real Property Profile (FRPP) which is managed by the General Services Administration (GSA). For more information on FIMS visit: https://fims.doe.gov/fimsinfo/index.html. For more information on FRPP requirements visit: https://www.gsa.gov/policy-regulations/policy/real-property-policy/asset-management/federal-real-property-profile-management-system-frpp-ms.

Each BUILDER environment also has a companion SPIRE/HUB environment which is used for making bulk data changes to the BUILDER dataset and for supporting software integration (e.g., connecting each site’s respective computerized maintenance management systems (CMMS) to BUILDER).

Each BUILDER environment also interacts with the Cost Engine, a standalone software program used to generate accurate, NNSA-specific Replacement Plant Values (RPV). The NNSA plans to use the Cost Engine and its associated replacement cost data in perpetuity to continue supporting RPV calculations. The Cost Engine will continue to rely on SPIRE, a middleware software tool developed by DIGON Systems included in their HUB suite of products, to communicate with BUILDER.

1.3 Contract Vehicle and Period of Performance

The contract will be on a firm-fixed price basis, which includes a one (1) year base period and four (4) one-year option periods, with the following periods of performance:

Period of Performance Dates Base Period 26 APRIL 2025 – 25 APRIL 2026

Option Period #1 26 APRIL 2026 – 25 APRIL 2027 Option Period #2 26 APRIL 2027 – 25 APRIL 2028 Option Period #3 26 APRIL 2028 – 25 APRIL 2029 Option Period #4 26 APRIL 2029 – 25 APRIL 2030

1.4 Place of Performance

The primary place of performance will be the Contractor’s facility/facilities. Some meetings will be conducted at various locations around the NNSA complex (refer to Section 3).

1.5 Partnership Roles and Responsibilities

The NNSA BUILDER Program is managed by a cross-functional team of infrastructure experts including members from NNSA HQ, NNSA Field Offices (FO), NNSA Management & Operating (M&O) Partners, USACE’s Construction Engineering Research Laboratory (USACE-CERL), DOE’s Oakridge National Laboratory (ORNL), and various term-limited support contractors. Unless otherwise stated herein or by contract modification:

5 of 16 | P a g e

NNSA HQ refers to the Infrastructure Operations & Maintenance Division (NA-914), a suborganization of the NNSA Office Infrastructure (NA-90).

NNSA Field Offices refer to the Livermore Field Office, Los Alamos Field Office, Nevada Field Office, NNSA Production Office, Sandia Field Office (including the Albuquerque Complex), Savannah River Field Office, and the Office of Secure Transportation.

NNSA Management & Operating (M&O) Partners refer to the Kansas City National Security Complex (KCNSC), Nevada National Security Site (NNSS), Lawrence Livermore National Laboratory (LLNL), Los Alamos National Laboratory (LANL), Sandia National Laboratory (SNL), Savannah River Site (SRS), the Pantex Plant (PX), and the Y-12 National Security Complex (Y12).

The BUILDER Software Team refers to NNSA HQ and all software support contractors.

Each entity has separate and distinct duties and responsibilities as defined herein:

NNSA HQ is responsible for providing BUILDER program management, oversight, and policy definition.

G2/ORNL staff are responsible for hosting BUILDER/ESMS, the Cost Engine, HUB, and any other associated software applications on NNSA severs (either physically or via cloud services), providing helpdesk support, and managing the G2-BUILDER/SMS nightly data sync.

NNSA Field Offices are responsible for BUILDER program consultation and oversight of M&O implementation and sustainment work.

M&O Partners are responsible for executing BUILDER program requirements and maintaining the actual SMS dataset.

CERL is responsible for software development, helpdesk and technical support, program management consultation, and acts as a designated system administrator in BUILDER, ESMS, and G2.

Third party contractors are responsible for executing the terms of their contract to support BUILDER or ESMS implementation/sustainment.

1.6 Security Requirements

Contractor staff are not required to have DOE/NNSA Clearance at this time; however, the Contractor and its personnel accessing NNSA data must be U.S. citizens. If a need arises for security clearances, the Contractor and its personnel shall possess a DOE/NNSA “Q” Clearance or have the capability to obtain a DOE/NNSA “Q” Clearance at time of need.

1.7 Sharing of Sensitive Information

Support contractors are responsible for safeguarding NNSA information/data and shall limit the distribution of sensitive information to only that which is necessary for the execution of work under this contract and only to those team members executing the work.

“Sensitive information” includes information that could pose a security risk or aid those intending

6 of 16 | P a g e to do harm to Government persons or property. Examples include but are not limited to asset or component data, design analyses, as-builts or other drawings, specifications, location of deficiencies, operational information, and contingency plans.

BUILDER is an unclassified system authorized to handle Controlled Unclassified Information (CUI) data to include Unclassified Controlled Nuclear Information (UCNI). The Contractor must properly identify and mark all electronic and printed materials according to DOE/NNSA requirements. The Contractor shall coordinate with NNSA HQ to determine the best way to transmit CUI/UCNI data/files to protect them according to regulation (typically using the BUILDER SharePoint). Refer to the following guidance for more information:

o DOE Order 471.7, Controlled Unclassified Information (CUI) https://www.directives.doe.gov/directives-documents/400-series/0471.7-

BOrder/@@images/file Went into effect February 3, 2022, replacing DOE Order 471.3 Chg. 1, Identifying and Protecting Official Use Only Information, dated 1-13-2011, and DOE Manual

(M) 471.3-1 Chg. 1, Manual for Identifying and Protecting Official Use Only Information, dated 1-13-2011.

o More information about CUI federal requirements can be found at the following National Archives website: https://www.archives.gov/cui

2. TASKS

The Contractor is responsible for performing the tasks and submitting the deliverables outlined herein.

2.1 General Requirements

The Contractor is responsible for developing/maintaining the HUB software suite of products used in support of the NNSA BUILDER Program to include developing/maintaining digital custom reports, providing BUILDER data quality assurance reviews, developing/maintaining user/stakeholder training, and graphic design services. Scope includes a perpetual license to HUB including SPIRE, SAGE, FLOW, and ALLOY for which the Contractor shall provide user support helpdesk services.

The Contractor must provide agency-specific software tools that are compatible with NNSA’s BUILDER instance and provide a means for connecting BUILDER to NNSA site maintenance systems, providing real-time data quality checks, and allow users to make bulk data edits.

2.1.1 UNIFORMAT II

BUILDER inventory shall be documented in accordance with the American Society of Testing and Materials (ASTM) Uniformat II convention as outlined in the Whole Building Design Guide (or as otherwise directed by CERL): http://www.wbdg.org/ffc/va/cost-estimating/tri-service-mod-uniformat

2.1.2 Real Property

7 of 16 | P a g e

The Contractor shall fulfill the requirements of this contract as they relate to real property implementation/sustainment. Programmatic or personal property are not included in the current scope, however, the Contractor shall consult on the feasibility of implementing programmatic equipment (if desired by the NNSA) during BUILDER Team discussions.

2.1.3 Server Management

NNSA hosts its own BUILDER instance on internal G2 servers managed at ORNL and is responsible for managing and maintaining the software and its constituent data. The Contractor is responsible for delivering HUB software compatible with current server requirements and for assisting with troubleshooting efforts should data or integration complications arise that affect BUILDER performance.

The Contractor is responsible for hosting an accessible server (EXTDEV2) for NNSA preview of the next release and a secondary accessible environment (EXTDEV) for end user acceptance and ongoing integration testing efforts. No actual NNSA BUILDER data is permitted to be on Contractor-hosted servers and should rather consist of artificial data representative of the NNSA complex.

2.1.4 Software Access and Permissions

NNSA HQ is responsible for granting/revoking user access to BUILDER, HUB, and the BUILDER SharePoint collaboration site. The Contractor shall supply NNSA HQ with a list of individuals who require BUILDER/HUB/SharePoint access, specifying what level of permissions is required (e.g., Master Planner) and whether they need typical user access or access to the API. ORNL staff shall assign the authorized software permissions and CERL shall consult as needed as permission capabilities change within the software or to troubleshoot any assignment issues.

The Contractor is responsible for regularly reviewing their access permissions and shall submit a quarterly BUILDER permissions report to NNSA HQ specifying which permissions remain active and which need to be revoked. Report format is left up to the Contractor but must include at a minimum:

Name Email (tied to BUILDER account) Phone Number Current BUILDER role (e.g., Master Planner, Read-Only) o Suggested action such as “maintain”, “revoke”, “modify” o Provide justification comment if role is recommended for “modify” o Whether individual requires API access

2.1.5 Software Tracking Using Microsoft Azure DevOps Services The Contractor shall leverage the NNSA BUILDER Program’s Microsoft Azure DevOps Services board for managing/communicating work deliverables, tracking software defects, etc. The Contractor will obtain access to the platform via the BUILDER Software Team and shall learn how to use it effectively for

8 of 16 | P a g e coordinated software development. The Contractor shall track all deliverables up to one year out and add tasks agreed upon by the BUILDER Software Team. Access to the NNSA BUILDER Program’s Microsoft Azure DevOps Services board is expected to be free to the Contractor and have unlimited users.

2.1.6 Software Updates and Patches

The Contractor is responsible for providing timely HUB software updates/patches and for coordinating with NNSA staff to ensure program integrity on a regular basis. The Contractor shall provide NNSA HQ with any relevant release notes at least two months prior to deployment and ensure updates are performed at the most opportune time to ensure limited disruption of service. ORNL and CERL will upload Contractor provided data/software updates unless otherwise agreed upon by the BUILDER Software Team. Updates should be coordinated with updates to other companion software applications such as the Cost Engine.

All updates are expected to be thoroughly vetted against the Contractor’s test environments (e.g., EXDEV or EXDEV2) prior to deployment to the NNSA Integration environment. Furthermore, the Contractor shall perform detailed smoke tests and regression testing after each deployment in each NNSA environment to ensure continued functionality and that products are free of bugs.

The Contractor is responsible for providing virtual software training to users with each software update that expands or changes software functionality.

2.1.7 Software User Guide and Custom Reports

BUILDER has several SQL Server Reporting Services (SSRS) custom reports deployed to streamline the analysis of information from the database. The Contractor shall provide NNSA HQ with a custom report user guide with detailed instructions on how to run and use all custom reports (for standard BUILDER users).

The Contractor shall also develop and maintain custom reports to support NNSA data calls or general BUILDER data management. The Contractor shall gather report requirements from participation in monthly custom report working group meetings. Number of reports, report content, and report formatting shall be agreed upon by the Contractor and NNSA HQ but Contractor can assume creating at least two new custom reports per year and modifying/updating four existing BUILDER reports per year.

Steps for reports development include:

a. Design of a report mock-up based on user requirements

b. Revisions of the mock-up based on draft feedback

c. Program SQL code to BUILDER database requirements

d. Test internally on QA instance

e. Deploy to EXTDEV for NNSA HQ validation

f. Deployment and configuration support to Integration and Production environments on G2

The Contractor shall develop and maintain a SPIRE data dictionary which communicates technical

9 of 16 | P a g e requirements and will provide a companion user guide with detailed instructions on how to use each SPIRE message/end point.

The Contractor shall develop and maintain a HUB user guide with detailed instructions on how to use each product including screen captures and detailed functionality steps.

2.1.8 Data Migration

The Contractor shall consult on transferring existing BUILDER data to the new ESMS platform to ensure data integrity to include a written plan to be delivered in a format and at a time agreed upon by the Contractor and NNSA HQ. This written plan is expected to be a low-level effort and should document the Contractor’s recommendations purely for BUILDER Software Team communications and not expected to be a formally printed or overly complicated document.

2.1.9 HUB Software Enhancements – SPIRE

The Contractor shall offer support and technical consultations for any NNSA sites needing to change or introduce a new CMMS integration. Scope includes consultations on building a toolset for the automation of pulling RN/DM numbers using the Scenario endpoint.

The Contractor shall continue developing the SPIRE integration product based on direction from NNSA HQ. Release priority to be provided by NNSA HQ with scope that can include introduction of new application programming interfaces (API) endpoints or modifications of existing APIs. Major enhancements may include:

a. Two phases of adding cost modification features to the SPIRE endpoints

b. Explore options to reduce Gordian cost engine runtime

c. Enable the editing of the SecAltId in the Inventory Detail Message

d. Provide an endpoint that returns “All” Work in one call

e. Add a simplified Inspection Message at the Section level, without any Section Detail noise

2.1.10 HUB Software Enhancements – SAGE

The Contractor shall continue developing the SAGE product based on direction from NNSA HQ. Release priority to be provided by NNSA HQ with scope that includes introduction of new data quality rules or modifications of existing rules. Major enhancements may include:

a. Ability to make data changes directly on a SAGE report instead of in BUILDER

b. Ability to automatically make bulk changes without user approval on each change

c. Improved reporting on user edit activity

d. Enable multiple projects within a tenant concurrency

e. New data quality trend reporting

f. Create new quality assurance rules as directed by headquarters or sites

g. Modify Rule Books as directed by headquarters or sites

10 of 16 | P a g e

2.1.11 HUB Software Enhancements – ALLOY

The Contractor shall continue developing the ALLOY product based on direction from NNSA HQ. Release priority to be provided by NNSA HQ with scope that includes introduction of new in-application reports or modifications of existing reports. Major enhancements may include:

a. Add SPIRE type CSV reports, editable directly in the browser, with a Save button

b. Implement data warehouse trending on key performance metrics

2.1.12 HUB Software Enhancements – FLOW

The Contractor shall provide support and user training for FLOW (e.g., project creation, sync management, data reviews).

The Contractor shall continue developing the ALLOY product based on direction from NNSA HQ. Release priority to be provided by NNSA HQ with scope that includes introduction of new features or modifications of existing features. Major enhancements may include:

a. In-application data download (SPIRE files). Provides an option for users of the application to sync to BUILDER without a network connection to HUB

b. Emulate FLOW (create, edit sections in BUILDER data) directly in the HUB Portal

c. Windows version of FLOW

d. A ‘resync’ feature to allow a supervisor-level user to see the data of all other users before it uploads to BUILDER

2.1.13 Data Quality Assurance (QA)

The Contractor shall provide an update to the NNSA data Quality Plan and revise annually based on discoveries from the prior year.

The Contractor shall also coordinate in-person and remote site data reviews. During those data reviews, the Contractor shall provide each site a summary of issues found in SAGE and assist them with making corrections. As new site points of contact are added to the program, the Contractor shall provide advanced in-person data quality training.

The Contractor is responsible for developing and maintaining SAGE rulebooks which they will revise based on feedback from site QA reviews.

2.1.14 Graphic Design Support

BUILDER data provides leadership with metrics to make informed decisions, but a visual representation of those metrics often leads to a much greater understanding. The Contractor will provide a graphic artist in the creation of custom illustrations, photo edits, and page layouts, digital art materials to be used for training materials, PowerPoint slides and other documentation.

11 of 16 | P a g e

2.1.15 Training Materials and Knowledge Management

The Contractor shall provide the following services as needed:

a. Provide the NNSA access to DIGON-hosted online training content for both the standard BUILDER training modules as well as for the NNSA-specific training modules.

b. Provide 20 user accounts each year for a total of 100 over 5 years.

c. Provide users with online access; printed training materials to include exercise book, quick reference cards, and completion certificates; and emails reminding users of incomplete training.

d. Provide the NNSA with a monthly training tracker showing all registered trainees and their training status.

The Contractor shall contribute to the creation of NNSA BUILDER training material using Articulate 360 or another designated platform by NNSA-HQ. (The Contractor is not expected to pay for creator licenses to this software which will be covered by NNSA-HQ). Scope includes building approximately 3-minute-long training videos around specific topics based on priority set by NNSA. Topics to include:

a. Assessment tool options (BRED / FLOW)

b. Basics of OSFs

c. BUILDER Reporting (Steps to run, exports, request changes, dashboards)

d. Catalog basics and UNIFORMAT Classification

e. Condition color scales and usage

f. Direct rating guidelines

g. How NNSA creates a funding plan (DM / RN)

h. How the system identifies work needs

i. HUB Product Overviews (SPIRE, SAGE, ALLOY, FLOW)

j. Individual Site overviews (Scope, Integration, Inspections, etc.)

k. Lifecycle based planning (RSL, DL, RDL)

l. Mission Dependency Index creation and usage

m. Related systems data overlap (CMMS, G2, FIMS)

n. Section naming fundamentals

o. Steps for Access (BUILDER, HUB, etc.)

p. The NNSA complexes (OSFs, Buildings and Trailers, Leased, etc.)

q. UNIFORMAT II and the BUILDER catalog

r. What are Section Details and when are they needed?

s. What is BCI?

t. What is SAFER?

u. What is the NNSA RPV?

v. What is VAPER?

w. When and how to group sections

x. When should I reinspect?

12 of 16 | P a g e

3. MEETINGS, TRAVEL, & OTHER DIRECT COST REQUIREMENTS

The BUILDER Program hosts regular working-level team meetings throughout the year and two large-scale annual meetings; one (1) in Spring and one (1) in Fall. At the Spring meeting, typically held in March or April, the team provides updates on current fiscal year milestone progression and collectively develops draft mission priorities for the following fiscal year. The Fall meeting, typically held in late October or November, is used to finalize current fiscal year mission priorities and discuss lessons learned from prior year accomplishments.

3.1 Virtual Team Meetings

The Contractor shall attend the following meetings virtually as schedules allow:

Meeting # Meeting Name # of People Hours Frequency Type BP OP1 OP2 OP3 OP4

1 BUILDER Team Meeting 4 1 Biweekly Virtual X X X X X

2 Software Team Meeting 4 0.5 Biweekly Virtual X X X X X

3 Custom Reports Working Group Meeting 4 0.5 Monthly Virtual X X X X X

NOTE: Biweekly refers to every other week

3.2 Travel Requirements

The Contractor shall attend the following meetings and site visits, in-person, as schedules allow:

3.2.1 Team Meeting Table

Trip # Team Meeting Name # of

People # of Workshop

Days # of Travel

Days 1 Base Period: FY26 Fall BUILDER Team Meeting 2 2 2 2 Base Period: FY26 Spring BUILDER Team Meeting 2 2 2 3 Option Period #1: FY27 Fall BUILDER Team Meeting 2 2 2 4 Option Period #1: FY27 Spring BUILDER Team Meeting 2 2 2 5 Option Period #2: FY28 Fall BUILDER Team Meeting 2 2 2 6 Option Period #2: FY28 Spring BUILDER Team Meeting 2 2 2 7 Option Period #3: FY29 Fall BUILDER Team Meeting 2 2 2 8 Option Period #3: FY29 Spring BUILDER Team Meeting 2 2 2 9 Option Period #4: FY30 Fall BUILDER Team Meeting 2 2 2

10 Option Period #4: FY30 Spring BUILDER Team Meeting 2 2 2

3.2.2 Site Visit Table

Trip # Site Visit Name # of People # of Visit Days # of Travel Days 1 Base Period: Misc. Site Visit (1) 2 2 2 2 Base Period: Misc. Site Visit (2) 2 2 2 3 Option Period #1: Misc. Site Visit (1) 2 2 2 4 Option Period #1: Misc. Site Visit (2) 2 2 2

13 of 16 | P a g e

5 Option Period #2: Misc. Site Visit (1) 2 2 2 6 Option Period #2: Misc. Site Visit (2) 2 2 2 7 Option Period #3: Misc. Site Visit (1) 2 2 2 8 Option Period #3: Misc. Site Visit (2) 2 2 2 9 Option Period #4: Misc. Site Visit (1) 2 2 2

10 Option Period #4: Misc. Site Visit (2) 2 2 2

Travel costs incurred by the Contractor will be reimbursed on a Cost Basis. Prior to booking and conducting Travel in performance of this contract, estimates and travel plans shall be submitted to, and approved by, the Contracting Officer’s Representative (COR), no less than seven (7) calendar days before travel occurs.

3.3 Other Direct Costs (ODCs)

ODCs are expected during performance of this contract. ODC costs incurred by the Contractor will be reimbursed on a Cost Basis. Unless otherwise permitted by the COR, prior to purchase, the Contractor shall submit ODC estimates for COR Approval. The following list are examples of, but not limited to, potential ODCs:

- Server/Software Fees

- Training Materials (Printed)

4. QUALITY CONTROL/ASSURANCE

4.1 Inspection and Acceptance Criteria

Final inspection and acceptance of all work products will be performed by NNSA HQ (in coordination with the IPT). Certification by the Site or Government representatives of satisfactory deliverables is contingent upon the Contractor performing in accordance with the terms and conditions of the contract. General quality measures, as set forth below, will be applied to each work product received from the Contractor:

Timeliness: Work Products shall be submitted on or before the agreed upon deadline as specified in the contract scope of work or submitted in accordance with a scheduled date determined by NNSA HQ in consultation with the Contractor.

Format: Work Products shall be submitted in the format specified in the contract scope of work or via media mutually agreed upon by NNSA HQ and the Contractor.

Completeness: Work Products shall be reviewed for completeness to ensure it meets the requirements specified in the contract scope of work.

Spelling and Grammar: All deliverables must be free of spelling and grammatical errors.

4.2 Contractor Performance

14 of 16 | P a g e

NNSA HQ will provide regular informal performance feedback to the Contractor and will formally conduct annual Contractor performance appraisals using the Federal Government’s Contractor Performance Assessment Reporting System (CPARS). The Contractor will be graded against the following categories:

Quality Schedule Cost Control Management Small Business Utilization Regulatory Compliance Other Areas

A detailed list of rating criteria can be supplied to the Contractor by the NNSA Contracting Officer upon request. For more information visit: https://www.cpars.gov/cparsweb/home.

5. DELIVERABLES

5.1 Reporting Requirements Checklist

The Contractor is responsible for submitting all reports according to the “Reporting Requirements Checklist” and as outlined below:

Contract Status Report o Delivery Method: Email to the NNSA Program Manager (formatting at Contractor discretion) o Delivery Deadline: At the end of every month o Description: concise narrative of work status being performed under the contractual agreement. NNSA management uses this report to monitor status and to provide early recognition of potential problem areas. The report should highlight changes to objectives, changes to technical approach, task variances from baseline in excess of stipulated thresholds by reporting element, causative factors, and actions taken or proposed to resolve them, as well as factors with potential for causing significant variances in the future. Task progress may also be highlighted. The report should identify open action items and to whom these actions are assigned.

Conference Record o Delivery Method: Email to the NNSA Program Manager (formatting at Contractor discretion) o Delivery Deadline: within 48 hours of meeting unless otherwise agreed to by the NNSA

Program Manager o Description: Meeting minutes that capture significant decisions, direction or redirection, or required actions. It is required for any meeting, conference, or phone conversation in which a decision is made that may change the schedule, labor, cost, or technical aspects of the contractual agreement or the approved baseline plans.

15 of 16 | P a g e

5.2 Deliverables

The Contractor shall provide deliverables as dictated by the Deliverables table below:

PWS

Section Deliverable Due Date Deliver To Format

1 2.1.4 BUILDER Permissions Report

Beginning of each quarter (October, January, April, June)

NNSA BUILDER

Program Manager

Text summary sent via email and included in Azure Boards

2 2.1.6 Software Release Notes 2 months prior to Deployment to NNSA environments

NNSA BUILDER

Program Manager

Marked up BUILDER/SPIRE user report sent via email

3 2.1.7 BUILDER Custom Report

User Guide

Within 30 days of contract award and updated as reports are changed

NNSA BUILDER

Program Manager

Microsoft Word Document sent via email

4 2.1.7 New BUILDER Custom

Reports

At least 2 per year or as agreed upon by NNSA Program Manager & Contractor

NNSA BUILDER

Software Deployment Team

Deployable report format compatible with

BUILDER/NNSA

environment

5 2.1.7 Updated Existing BUILDER Custom

Reports

At least 4 per year or as agreed upon by NNSA Program Manager & Contractor

NNSA BUILDER

Software Deployment Team

Deployable report format compatible with

BUILDER/NNSA

environment

6 2.1.7 SPIRE Data Dictionary

Within 30 days of contract award and updated as SPIRE is changed

NNSA BUILDER

Program Manager

Microsoft Excel Document sent via email

7 2.1.7 HUB User Guide

Within 30 days of contract award and updated as HUB is changed

NNSA BUILDER

Program Manager

Microsoft Word Document sent via email

2.1.9 - 2.1.12

HUB Software Updates

Twice per year or as agreed upon by NNSA Program Manager & Contractor

NNSA BUILDER

Software Deployment Team

Deployable software format compatible with

BUILDER/NNSA

environment

9 2.1.13 SAGE Rulebooks

Within 30 days of contract award and updated as rulebooks are changed

NNSA BUILDER

Program Manager

Deployable software format compatible with

BUILDER/NNSA

environment and companion Microsoft Excel Document sent via email

16 of 16 | P a g e

10 2.1.14 Graphic Designs As agreed upon by NNSA Program Manager & Contractor

NNSA BUILDER

Program Manager

As agreed upon by NNSA Program Manager & Contractor

11 2.1.15 DIGON BUILDER Training

Tracker 1st Business day of each month

NNSA BUILDER

Program Manager

Microsoft Excel Document sent via email

12 5.1 Contract Status Report

Last Business day of each month and before end of contract.

NNSA BUILDER

Program Manager

Text summary sent via email

13 5.1 Conference Record

48 hours after the conclusion of meetings outlined in Section 3.2.

NNSA BUILDER

Program Manager

Text summary sent via email