CoMET Draft PWS.pdf

NASA’s Construction Management Enterprise Tool (CoMET)

Draft Performance Work Statement (PWS)

DRAFT

NASA Construction Management Enterprise Tool Performance Work Statement

1. BACKGROUND

The National Aeronautics and Space Administration (NASA) Office of Strategic Infrastructure (OSI) assures that the appropriate infrastructure/systems are available to meet NASA’s mission requirements. To this end, the Facilities and Real Estate Division (FRED) and the Design, Construction, and Demolition (DCD) Branch lead NASA’s program to fund, plan, design, construct, operate and maintain a highly complex and aging portfolio.

Currently, each of NASA’s Centers and Center Facilities manage capital projects through differing software and solutions that integrate differently at the Center-level and do not integrate at the Agency level. To ensure capital project delivery, improve oversight and reporting capabilities, and to mitigate risk, NASA requires a Commercial Off the Shelf (COTS) enterprise-level construction project management solution that is Owner/Project Manager centered and aligns with industry standards for capi al program and project management.

2. OBJECTIVE

NASA OSI seeks to acquire a commercial-off-the-s lf (COTS) solution for capital program and project management; along with the y tem admin tration and technical support services to provide, configure, implement, and administer the configured COTS solution. The configured COTS solution shall be known s NASA s Construction Management Enterprise Tool (CoMET). All references in thi scope f work to CoMET shall refer to the contractor-provided and contractor-configured COTS sol tion. The scope of work included within this Performance Work Statemen (PWS) in des the configuration, integration, and administration of the new softw e-as-a-service (i.e., cloud-based) enterprise-wide solution that includes hosting licensi g, co figuration, data architecture, integration, testing, training, maintenance/supp rt services, nd system administration.

NASA’s objectives wi h the a quisition of CoMET is to implement a configured COTS solution that will:

(1) Process, store, and report planning, design, and construction data for capital projects.

The data sets include contractor submittals, Requests For Information (RFIs), change orders, drawings, construction specifications, cost estimates, schedules, submittal registers, daily reports, issue logs, and all other required documentation to track and manage capital projects from initiation of planning through facility activation and turnover.

(2) Enable seamless collaboration, integration, accountability, reporting, and information access at NASA Centers and Facilities across NASA and outside NASA.

(3) Perform the following specific capabilities for each capital program and project:

• Planning Management

• Document Management

• Schedule Management

• Cost Management

• Budget Management

• Workflow/Approval Management

• Reporting and Data Analysis with Dashboard capabilities.

(4) Enable information to be stored, viewed, analyzed, reproduced, and updated with a minimal amount of effort and no duplication of effort through a Graphical User Interface (GUI). Provide an intuitive, effective, easy to learn, and responsive end user experience to improve project team member productivity in the delivery of construction projects across the Agency. Dispositioning of actions shall be easy to set-up and easy to use.

(5) Implement an enterprise-wide system of record and system of reporting allowing rapid, real-time data reporting at the user, Center, and Agency level. Ensure Agency level capability for management to view, search, query, and run reports on all data entered across the Agency.

(6) Provide the capability to ensure data has acc ss control cap bilities to limit accessibility based on user role, Center assignment, or Program/Project assignment.

Allow authorized agency level management to acc s data for roll-up reporting and analysis.

(7) Ensure consistent and compliant handling f planning, design, and construction contract documentation, improve risk analysis and risk mitigation though accurate and real-time access to project data.

The contractor shall provide a cl ud-based configured COTS offering, shall meet the technical and operational req ireme ts herein, shall ensure integration with specified information techn logy (IT) sy tems and software, and shall operate and maintain CoMET in accordance with ind stry best p actices, Federal Regulations, and NASA guidelines. The contractor shall provide a solution that is Federal Risk and Authorization Management Program (FedRAMP) Mo rate Authorized at the time of contract award. The Government intends to achieve Agency Authority to Operate (ATO), in accordance with NPR 7120.7, within 270 calendar days of Notice To Proceed (NTP).

3. BASE SCOPE

3.1.Functional Standards.

3.1.1. COTS Solution. Kahua™ shall be the COTS software vendor for this requirement.

3.1.2. General Functional Requirements. The contractor shall provide a logical, standardized, configurable user interface for each assigned user role for a project.

The contractor shall provide a project manager focused, user‐friendly system. The contractor shall provide pre‐configured, customizable dashboards that display selectable data related to all aspects of project management and project delivery to include, but not limited to, project cost, schedule, scope, and workflow response status/performance. The contractor-provided solution must provide an efficient method of navigation and shall provide a single launch page that leverages click‐ through navigation to manage multiple projects.

3.2.Accessibility.

3.2.1. Section 508 Compliance. NASA is committed to providing accessible Information and Communication Technology (ICT) to individuals with disabilities, including members of the public and federal employees. The contractor-provided solution shall meet or exceed all requirements of Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d).

3.3.Data Rights and Purchase Authorization.

3.3.1. In accordance with FAR 52.227-14 Rights in Da a General (May 2014), the contractor shall provide the Government with unrestrict d ownership rights to the project data within the software/program.

3.3.2. IT Purchase Authorization.

3.3.2.1. In accordance with DRD 012 – Com ercial IT Authorization Report, the contractor shall ensure all IT p oducts and ervices direct charged to the contract are approved through the NASA OC O’s Commercial IT Request (CITR) Application. This includes, but s no limit d to, Federal Information Technology Acquisition Reform Act (FITARA), Supply Chain Risk Management (SCRM), IPv6, and 508 compliance No purchases of commercial IT products or services should be made p ior to dination and approval by the OCIO. Contractor shall report purchases mo thly utilizing the Commercial IT Authorization Report (CITAR) Templ te (CITAR DRD).

3.3.2.2. This contract s all only be used to purchase software, software maintenance, hardwar or hardwa e maintenance necessary for the performance of this contract. NASA sh ll own the license(s) or subscriptions for any software or applications p r hased. All hardware shall be titled to NASA.

3.4.Security Requirements.

3.4.1. Compliance with Standards, Policies, and Reporting Requirements.

The contractor shall be subject to all NASA and Federal IT Security standards, policies, and reporting requirements. The contractor shall meet and comply with all NASA IT Security Policies and all applicable NASA and Federal standards and guidelines, and other Government-wide laws and regulations for protection and security of Information Technology. The contractor shall comply with the following policies and regulations:

a. Federal Information Security Management Act of 2002 (44 U.S.C. 3541 -

3549)

b. Homeland Security Presidential Directive (HSPD)-12: Policy for a Common

Identification Standard for Federal Employees and Contractors

c. Americans with Disabilities Act - Section 508 (29 U.S.C 794d)

d. NPD 2800.1, Managing Information Technology

e. NPR 2800.1, Managing Information Technology

f. NPR 2800.2, Information and Communication Technology Accessibility

g. NPR 2841.1, Identity, Credential, and Access Management

h. NPD 1382.17, NASA Privacy Policy

i. NPD 2810.1, NASA Information Security Policy

j. NPD 1382.17, NASA Privacy Policy

k. NPD 1420.1, NASA Forms Management

l. NPD 1440.6, NASA Records Management

m. NPD 1490.1, NASA Printing, Duplicating, a d Copying Management

n. NPD 2200.1, Management of NASA Scientific nd Technical Information

o. NPR 1382.1, NASA Privacy Procedural Requiremen s

p. NPR 1441.1, NASA Records Management Program Requirements

q. NPR 2200.2, Requirements for Documentation, Approval, and Dissemination of NASA Scientific and T ch ical Information

r. NPD 2540.1, Acceptable Use of Gover ment Office Property Including

Information Technol gy

s. NPD 2830.1, NASA Enterprise Architecture

t. NPR 1040.1, NASA Continuity of Operations (COOP) Planning Procedural

Requir men s

u. NPR 3600.2, NASA Telework Program

v. NPR 2810.1, Se urity of Information and Information Systems

w. NPR 2810 7 Controlled Unclassified Information

x. NPR 2830.1, NASA Enterprise Architecture Procedures

y. NPR 7120.7, NASA Information Technology and Institutional Infrastructure

Program and Project Management Requirements

z. The following handbooks relevant to the development, authorization, and maintenance of NASA information systems. (Current versions as posted on https://cset.nasa.gov/ascs/cspd-handbooks/)

i. ITS-HBK-AASTEP0.v1.0.0 Step 0: Prepare Policy

ii. ITS-HBK-AASTEP1.v1.0.0 Step 1: Categorize Policy

iii. ITS-HBK-AASTEP2.v1.0.0 Step 2: Select Policy

iv. ITS-HBK-AASTEP3.v1.0.0 Step 3: Implement Policy

v. ITS-HBK-AASTEP4.v1.0.0 Step 4: Assess Policy

vi. ITS-HBK-AASTEP5.v1.0.0 Step 5: Authorize Policy

vii. ITS-HBK-AASTEP6.v1.0.0 Step 6: Monitor Policy

Note: Cybersecurity Handbooks, and standards that apply to specific tasks or requirements are accessible internal only at https://cset.nasa.gov/ascs/cspd-handbooks/ and must be obtained from the Contracting Officer.

3.4.2. Access Control and Authentication.

The contractor COTS solution shall support a secure, multi-factor authentication (MFA) method for Government-consuming end users to access the service and for Government personnel who will perform administrative duties. The contractor shall support integration of the service with multi-factor NASA authentication services including SAML 2.0 and Federal Government Personal Identity Verification (PIV) Card access. A user inside NASA’s firewall shall be able to access the solution without having to provide sepa ate credentials. The contractor provided solution shall support an MFA solutio t at aligns with all applicable Federal IT security standards and policies. Access co trols must comply with the applicable portions of all NASA and Fede al IT Security standards and policies listed in Paragraph 3.4.1. These policie include session timeouts and inactive user lockouts. The information system/IT solution shall support role-based access controls to distinguish between end users eeding access to different levels of data (e.g., end users only needing a c ss to non-s nsitive data and end users needing access to sensitive data).

3.4.3. Email Notification o Users

The contractor shall pro ide the capability for system user notifications to be sent with a “.gov” d main.

3.4.4. In accord nce with DRD 011 - Security Requirements for Unclassified IT Resources, e contr ctor shall submit Information System Security and C-SCRM Plan(s), Non-F d ral System Certification, Information on Employees in Sensitive Positions/Assignments Report, IT Security Point of Contact, IT Security Awareness Training, and IT Security Role Based Training.

3.4.5. FedRAMP Moderate Authorized. CoMET shall be FedRAMP Moderate Authorized and shall maintain authorization through the performance period of the contract.

3.4.6. All work associated with the performance of this contract shall be performed off-site. Access to NASA Center/Sites/Facilities will not be required.

3.5.Technical Requirements

3.5.1. General Functional Requirements.

Provide an enterprise-wide Software-as-a-Service (SaaS) solution that provides on-line collaboration between the Government and its design, construction, and support services contractors to manage cradle-to-grave capital project management through the handling and management of data, information, workflows, approvals, and documents associated with all aspects of design and construction project management. The solution shall provide management of workflows and documentation including, but not limited to: Planning Documents, Functional Requirements Documents, Project Approval Documents, Requests for Information (RFIs), Design Documents (Drawings and Specifications), Performance Work Statements, Submittals, Schedules, Contract Modifications/Change Orders, Quality Control, Quality Assurance, Quality and Performance Assessment, Safety Notices, Status Reporting, Project Portfolio Management, Resource Planning, Payment Compliance, Invoicing, Correspondence, and general ledger/accounting.

The system shall have the capability of storing, arch ving, and transferring data.

All data and information managed within the sys m shall remain the property of the Government in accordance with Data Righ s req irements outlined in the Paragraph 3.3.

3.5.2. User Access and Licensing.

This contract shall only be used to purch s software, software maintenance and/or support, hardware, or hardware maintenanc necessary for the performance of this contract. NASA shall own the l cens (s) or su scriptions for any software or applications purchased. All hardware hall e titled to NASA. Provide site-unlimited use licenses i he quan ies described below. The site-unlimited license shall be vali for a t rm of ne one-year base period with four one-year options.

- Admi istra r Lic nses = 50

- U er Licenses NASA, NASA Contractor, or Non-NASA External Users) =

3.5.3. Software Techn al & Operational (T&O) Requirements and Capabilities.

The software solution shall meet the technical and operational capability requirements in Attachment E - Technical & Operational Requirements & Capabilities.

3.5.4. Software System Integration.

The software solution shall have the capability to integrate with existing software systems in use across NASA in a manner that allows seamless data transfer and sharing. The software solution shall support future real-time data integration via an Application Programming Interface (API) for enterprise applications. Under this scope of work, any data exchange with the specified systems will be conducted manually through exported and imported data sets. The vendor shall configure and secure a File Transfer Protocol (FTP) folder within the FedRAMP environment to enable the automated monthly exchange of government flat file data. This setup will support the seamless transfer and integration of updated information into the system. The contractor shall be responsible for ensuring the cleansing/organization of the flat file data to ensure seamless transfer and integration into the software solution. These software systems include multiple platforms and programs handling data related to Real Property, Financial Reporting, Geospatial Information, Work Request Systems, and document storage.

At a minimum, integration shall be required for the following on-prem systems:

3.5.4.1. Real Property Management System (RPMS); The RPMS is the system for recording all NASA land, buildings, and other structures. It is integrated with NASA’s financial system, SAP. The RPMS provides the capability of inventory management and asset valuation of NASA’s real property portfolio. RPMS is a customized RE-FX Module in SAP. Manual data migration shall be required once during initial software integration and monthl thereafter. The vendor shall configure and secure an FTP folder within the K hua FedRAMP environment to enable the automated monthly exchange of g vernment flat file data. The data to be manually migrated will be provided as n exported XLSX files (Microsoft Excel Spreadsheet). File size is approximately 2MB. The "Real Property Unique ID" (RPUID) serves as the unique id ntifier f r NASA real property. The software solution shall support future re l ime data integration via an Application Programming Interface (API) for enterpris applications.

3.5.4.2. Systems, Applications, and Pro cts in Data Processing (SAP); The functional scope of SAP Core Financial at NASA includes budget execution, purchasing, cost managem nt, ac ounts payable, accounts receivable, and standard general l dger – ach of these functions are executed and represented in SAP as modules. he so twar lution shall support future real-time data integration via an App ication Programming Interface (API) for enterprise applicati ns and have th capability for SAP to populate WBS, Fund Source, and PR nu ber.

3.5.4.3. Invoi e Routing and Information System (IRIS); IRIS is a web application u ed a ross the Agency to process requests for Cost, Goods Receipts, Funding, and Invoice Approvals. The software solution shall support future real-time data integration via an Application Programming Interface (API) for enterprise applications.

3.5.4.4. Real Estate Agreement Management System (REAMS); Real Estate Agreement Management System (REAMS). The software solution shall support future real-time data integration via an Application Programming Interface (API) for enterprise applications.

3.5.4.5. Maximo; Maximo supports center installations of the Office of Strategic Infrastructure (OSI). Each Center’s facility office is the primary user and beneficiary of IBM Maximo Support. The software solution shall support future real-time data integration via an Application Programming Interface (API) for enterprise applications.

3.5.4.6. KSC EWRS; The Kennedy Space Center Electronic Work Request System (EWRS) captures raw Local Authority project data from an authoritative Electronic Work Request System (EWRS) system. The software solution shall support future real-time data integration via an Application Programming Interface (API) for enterprise applications.

3.5.4.7. NASA Institutional Geospatial Information System (GIS) Portal (https://sscsdchqg.ndc.nasa.gov/arcgisportal/apps/sites/#/hqgismain) and Center GIS; The NASA Institutional GIS Portal and Center GIS databases house significant facility, institutional, and real property data for the Agency. The software solution shall support future real-time data integration via an Application Programming Interface (API) for enterprise applications.

3.5.4.8. NASA IBM TRIRIGA

(https://facspace.msfc.nasa.gov:9443/app/tririga/#">https://facspace.msfc.nasa.go v:9443/app/tririga/#); The current NASA Program and Project database housing project approval documents (NASA Form 1509s) and other facilities/project related data. Manual data migration shall be required once during initial software integration and monthly thereafter. The vendor shall c nfigure and secure an FTP folder within the Kahua FedRAMP en ironment to enable the automated monthly exchange of government flat file data. The data to be manually migrated will be provided as an exported .XLSX files (Mi osoft Excel Spreadsheet) or Tab delimited format. File size is f a file data fo approximately 2,000 projects. The "Global Unique ID - SPEC_ID and cord Id - trildTX" fields serve as the unique identifier for TRIRIGA p oj cts. The software solution shall support future real-time data nteg ation v a an Application Programming Interface (API) for enterprise applications

3.5.5. Workflow & Form Integ ation.

3.5.5.1. W rkflow - Th contractor shall provide a solution configured in a manner that replic tes, align with, and integrates the workflow associated with the requirements for p anning, approving, and acquiring NASA Facility Projects outlined in NPR 8820.2 and NPD 8820.2. Workflows shall be customizable and configurable by Administrators to incorporate specific Center requirements for workflows, approvals, and processes.

3.5.5.2. NASA Standard Form Integration; The contractor shall integrate into Workflow Approvals standard and customizable NASA Forms. At a minimum, the following forms shall be fully integrated into the contractor provided solution.

Forms available at https://nef.nasa.gov/.

3.5.5.2.1. NASA Form 1509

3.5.5.2.2. NASA Form 1579

3.5.5.2.3. NASA Form 1739

3.5.5.2.4. NASA Form 1046

3.5.5.2.5. NASA Form 1878

3.6.Execution Requirements.

The contractor shall provide all material, equipment, and labor necessary to perform all tasks associated with the licensing, hosting, configuration, testing, integration, data migration, implementation, training, and administration of the contractor provided solution. This shall include, but is not limited to, technical implementation of all system enhancements including beta testing, minor releases, major releases, software updates, and configuration changes.

3.6.1. Contractor Quality Management.

In accordance with DRD 001 – Quality Management Plan (QMP), the contractor shall identify and implement its approach for providing and ensuring quality by developing and submitting a Quality Management Plan (QMP) for approval by the Government no later than 30 days after Notice To Proceed (NTP). The QMP shall describe the application of the appropriate methodology (i.e., quality control and/or quality assurance) for accomplishing performance requireme ts. The QMP shall describe how the appropriate methodology integrates with the Government’s requirements.

The contractor shall make appropriate modifications to the QMP (at no additional cost to the Government) in order to ensur it remains relevant and accurate throughout the performance period. The Government has the right to require revisions of the QMP (at no cost to the Government) s ould the QMP fail to deliver the quality of the services required at any time during perf rmance.

3.6.2. Data Architecture Plan. In accor an e with DRD 002 – Data Architecture Plan, the Contractor shall crea e an submi for approval, NLT 90 calendar days after NTP, a Data Architecture Plan (DAP) based n technical discovery and scope for Government approval The ontr r shall maintain and update the data architecture plan throughout the dura on of the task order.

3.6.2.1. Th Contractor shall include a description of the database technology to be used and he process s employed to manipulate data.

3.6.2.2. The Co tracto shall describe security boundaries and interconnects in the

DAP.

3.6.2.3. The Contractor shall include an expected data model, entity relationship diagram and a data dictionary or equivalent information to permit the Government to maintain NASA's enterprise data model.

3.6.2.4. The DAP shall describe interfaces for sharing structured data with other IT systems.

3.6.2.5. The Contractor shall provide a data schema for data downloads and transfers so NASA can inventory the type, quantity, structure, and relationships of data housed in the contractor provided solution.

3.6.3. Data Exchange. The software solution shall be able to exchange data according to industry best practices and in compliance with all Federal guidelines. The Contractor shall be able to exchange data via Extract Transform Load (ETL) tools and Application Program Interfaces (APIs).

3.6.4. Configuration, Integration, and Testing (CIT).

The contractor shall provide all material, equipment, and labor associated with the contract requirement to execute configuration, integration, and testing of CoMET to meet the requirements of the contract. CIT of CoMET shall be executed by the contractor in coordination with the Government.

3.6.4.1. General Scope: The contractor shall provide a dedicated management and technical team responsible for the configuration, integration, and testing of the contractor provided solution. The team shall include a configuration, integration, and testing project manager (CIT PM) with overall responsibility for managing this scope of the contract. Starting NLT 60 calendar days after NTP, the CIT PM shall conduct no less than a bi-weekly update meeting with the Government’s Contracting Officer’s Representative (COR) to ensure transparency, communication of issues, and report of progress. The contractor shall provide a meeting agenda, host the meeting virtually, and provide meeting minutes to the Government no more than 72 hours after each weekly meeting. In a manner compatible with industry and government best p actices for COTS configuration, the contractor shall perform all work associat d wi h the configuration of the contractor supplied solution to meet all requirements f the RFP, to meet any additional objectives below, and to complete all tasks ou lined in the contract.

Use modern integration solutions so at the onfigured solution can easily integrate with other enterprise documen management solutions, digital signature solutions, and applications as NASA archi cture evolves. Configuration efforts shall be conducted in a manne that nsures that the application continues to meet all required security protocols, does not in oduce vulnerabilities to data security, and remains compatibl ith exi ing NASA network and IT functions.

3.6.4.2. Requiremen :

3.6.4.2.1. Configurat n of the software/application to meet the requirements of the contract shall em hasize out-of-the-box functionality.

3.6.4.2 2 The Contr ctor shall propose and implement configurations and solutio s that ar operable and maintainable within COTS releases, upgrades, patches, platf rm updates, bug fixes, and other industry standard software modifications.

3.6.4.2.3. The Contractor shall propose and implement configurations and solutions that enhance and do not degrade operability, including all integrations.

3.6.4.2.4. The Contractor shall propose and implement configurations and solutions that follow industry best practices and comply with all NASA IT Security Policies, all applicable NASA standards and guidelines, and other government-wide laws and regulations.

3.6.4.2.5. CIT shall address the complete life-cycle of capital projects which includes, but is not limited to, planning/formulation/requirements definition, design, advertise & award, construction, and outfitting/activation, and shall account for multiple methods of project delivery (i.e., design-bid-build, design-build) and project types.

3.6.4.2.6. Capital project types shall include but are not limited to: Institutional Construction of Facilities (CoF), Program-Direct CoF, Non-CoF, Energy Savings Performance Contracts (ESPC), Demolition, Utility Energy Service Contracts (UESC), Enhanced Use Lease (EUL), and National Historic Preservation Act (NHPA) projects. CoMET shall provide for categorization of projects by “type” or “program”, with the ability to create additional categories and/or re-name categories. Additionally, CoMET shall provide the ability for a user to build a “Portfolio” of capital projects that can be either individually selected or selected based on any number of parameters established by the user.

3.6.4.2.7. Ensure configuration efforts are coordinated and integrated with the Government COR.

3.6.4.2.8. Provide detailed written descriptions and demonstrations of the configuration steps performed, to include a de ailed demonstration of the software programming changes.

3.6.4.2.9. Establish and maintain priorities of work fo the configuration efforts.

Communicate and coordinate priorit zation of efforts with the COR.

3.6.4.3. Tasks:

3.6.4.3.1. CIT Plan. In accordance with DRD 003 - Configuration, Integration, and Testing (CIT) Plan, th co tractor sh ll develop and submit for approval, NLT 60 calendar days after the cont ct effective start date, a comprehensive plan covering all aspects of CoMET configuration, integration, and testing.

The CIT Plan shall, at minimum, provide a detailed description of the CIT approach, milestone s hedule, r sks, risk mitigation, and measurements of success. The C T P an shall address the contractors plans to configure the database ystem w th emphasis on out-of-the-box functionality over cust mization The CIT Plan shall address testing of the solution to demonstrate compliance with the requirements of the contract and Attac ment E - Technical & Operational Requirements & Capabilities.

The test plan and shall include a traceability matrix showing requirements, test procedures, pass/fail parameters, and actions to remediate failures.

3.6.4.3.2. For all requirements listed in the contract, the contractor shall expeditiously execute configuration of CoMET to meet the requirements.

Configuration efforts shall be prioritized in coordination with the COR, documented, and tracked to closure. In accordance with DRD 004 – Configuration Status & Functional Demonstration, no less than monthly and starting NLT 90 calendar days after NTP, the CIT PM shall provide a written report of configuration status and demonstrate the function of the contractor provided solution.

3.6.4.3.3. NASA Customization. Integrate into all CoMET modules data fields, nomenclature, references, insignia, and formatting to ensure the application, reports, and dashboards clearly identify capital project ownership by NASA.

3.6.4.3.4. Capital Project Status Reports. Develop both template and customizable (via field selection) “Project Status Reports” and “Program Status Reports” exportable in a compatible electronic format (minimally exportable as Microsoft PowerPoint, Microsoft Excel, and Adobe Acrobat PDF) that includes the following basic project data presented in an easily readable format:

3.6.4.3.4.1. Basic Capital Project Information: Includes a short, representative statement of the project. The title should start with the project category (e.g., Renewal, Repair, Demolition), the name of the system or building to be impacted, and the real property/building number.

The real property/building name and number should match the official name and number recorded in the Agency’s Real Property Management System (RPMS). Additional fields shall also include: Client/User Name, Project Personnel (e.g., Project Manager, Design Manager, Construction Manager, Contracting Officer’s Represen ative, Contracting Officer, Inspector, Safety Officer, Contractor P rs nnel), Contract Number, Delivery Method, and Procurement Type.

3.6.4.3.4.2. Capital Project Schedule Status: Start, Award Dates by Phase, Notice To Proceed Date Ne d By Dates, Original (Baselines) and Scheduled Completion Dates, Beneficial Occupancy Dates, Final Payment Dates, and Percent Compl te by pha Indicators of Contract Time Growth shown as “perc ntage d color coded red/yellow/green based on parameters to be provide b the Government. Color coding parameters shall be cust miza le by Admin Users.

3.6.4.3.4.3. Capital P ject Status Photo: Imported JPEG photo.

3.6.4.3 4 4 Capital Project Scope: Imported text description of project s ope. Tr ncate as necessary.

3.6. 3.4.5. Capital Project Budget Status: By phase (study, design, con truction outfitting) summary of original contract award amount/bid amount modifications amount, current total amount, pending changes amount, total estimated contract amount, and total current budget; Fiscal Year; % obligated and % expensed; Approved Facility Project Cost Estimate (AFPCE); Supervision, Inspection, and Engineering Services (SIES); Contingency Amount; Approved Design Cost; Actual Design Cost; etc. Additional customizable fields shall be allowable. Status indicators of Contract Schedule Growth shown as “percentage” and color coded red/yellow/green based on parameters to be provided by the Government shall be displayed. Color coding parameters shall be customizable by Admin Users.

3.6.4.3.4.6. Contract Status Code: Imported from project data entry indicating current status of contract (project development & planning, study, design, advertise & award, construction, activation, disposal/deconstruction).

3.6.4.3.4.7. Remarks: Include the ability to add free text comments for the purpose of capturing information to be shared on the Project Status Report.

3.6.4.3.5. Integrated Project Dashboards. The contractor shall configure and provide a series of customizable project and program dashboards, integral to CoMET, that provide real-time data for projects selected through the selection of any set of parameters. Parameter selections shall include, but are not limited to: Project Type, NASA Center, Program Type, Dollar Value, Fiscal Year, Status, Project Phase.

3.6.4.3.5.1. Project Dashboards shall incorporate visuals, charts, tiles, and lists in a manner that presents information for project managers, project executives, and management. The dashboard shall visually depict project status; emphasize key metrics related to scope, schedule, and budget; show overdue items; and allow f r customization (add/delete) of project elements.

3.6.4.3.6. Portfolio. Each user shall have the ability to reate an individualized “Portfolio” of projects on which they can run reports or export data in multiple formats to include, but no limi ed to, Microsoft Excel, Microsoft Word, Adobe Acrobat, and Microsof PowerPoint. A “Portfolio” can be created using any number of filters determined by the user to select projects.

3.6.4.3.7. Workflow Approvals

3.6.4.3.7.1. The ontrac or shall coordinate with the Government to configure and crea e templa e workflows for approval routing. The configuratio shall address all requirements herein and includes, but is not limi fun ing releases, change order approvals, additional funding r quests, ro ting f documents for review/approval, RFI response drafting nd release, ansmittal/submittal review/approval, and official cor esponde ce.

3.6.4.3.7.2. Workflow approvals that require user signature shall incorporate the ability to apply electronic signatures, via Adobe Acrobat and the use of Government issued Personal Identity Verification (PIV) credential. The contractor provided solution shall incorporate the ability to notify individuals, via automated email, that a workflow approval has been assigned to them or is awaiting their approval.

3.6.4.3.7.3. Each workflow shall include reference to a “workflow approval diagram” that shows the specific routing/process for each workflow in order to allow users to visually verify workflow process, assigned individuals, and current status.

3.6.4.3.7.4. Workflow Approvals shall be configurable by system admin users to allow for customization by NASA Center.

3.6.4.3.7.5. Workflow approvals shall include approval documents, NASA Forms, correspondence, quality control/assurance reports, findings, deficiency lists, submittals, Request for Information, design documents, Architect’s Supplemental Instructions, and other items.

3.6.4.3.7.6. Integrated Standard Forms, NASA Forms, NASA

Electronic Forms, and other PDF forms shall be integrated in a manner that allows the software solution to recognize data from tagged form fields and appropriately process steps of a workflow for a document type or populate data fields in libraries or modules in the software solution.

3.6.4.3.7.7. The software shall include an Automatic Identification and

Data Capture (AIDC) feature to be able to route in this manner or needs to integrate with a third party AIDC that complies with the all the software security requirements.

3.6.4.3.8. Non-NASA External Users Role Based Se urity. CIT shall address and provide proof of concept for a cess by non-NASA external users (i.e., construction contractors, architect ngineers, external consultants, support contractors). The contractor provided solution shall enable full functionality for non-NASA external u er with the option to limit access to certain functionalities thru role-bas d sec ity templates as directed by the Government.

3.6.4.3.9. Softwa e System Integra on. As part of CIT, ensure integration with specified softw re s stems t all real-time, seamless data transfer and sharing.

3.6.4.3.10. Form tegra ion. As part of CIT and as specified, ensure integration int Workflow Approvals standard and customizable NASA Forms.

3.6.4.3.11. Custom Schedule Milestones. CoMET shall have the capability to create Agen y, Center, Program, Project, or user specific milestone dates and incorporate those dates into reporting and reporting parameters.

3.6.4.3.12. CIT Validation Reviews. In accordance with DRD 005 – Configuration, Integration, and Testing (CIT) Validation Reviews, the contractor shall provide a comprehensive demonstration to the Government no less than monthly to demonstrate progress made during CIT. Each demonstration shall be conducted virtually with the ability to support no less than 100 Government attendees. The demonstrations shall be conducted in the form of a “design review” with the contractor responsible for capturing all comments, dispositioning comments as “accepted, for information only, or rejected,” and providing a subsequent report to the Government detailing the results of the validation demonstration along with actions to be complete in order to resolve remaining CIT tasks.

3.6.4.3.13. Test Results. In accordance with DRD 006 – Configuration, Integration, and Testing (CIT) Test Results, the contractor shall submit, with 15 calendar days of the completion of testing, the results of testing IAW the approved CIT Plan.

3.6.5. System Administration.

3.6.5.1. General Scope. The contractor shall provide system administration and technical support to users and administrators for the full range of support necessary to operate the contractor provided solution.

3.6.5.2. Objectives:

3.6.5.2.1. Provide system administration and technical support that is timely and effective. Services shall include all resources necessary to support the assigning of users to projects with proper roles nd categorizations, creation and management of lookup lists, creation an generation of reports/register views/exports, monitoring of the system f r co tent quality and consistency, and the manual migration of relevant data and do uments.

3.6.5.2.2. Help Desk. Provide Help De k and Technical Support available during regular business days and hours (M-F, n Federal Holidays. 9:00am to 5:00pm EST). Help Desk service re uests shall be logged and tracked through completion. Suppo t shall be p ovided in a manner consistent with industry standards (i.e., Tie 1 – b ic functional questions, password resets, etc. and Tier 2 – access assignm nts, in depth functional questions, troubleshooting)

3.6.5.2.3. Outage Notifica on. Provide for notification to all users of unplanned outages within 15 minut f occurrence and planned outages 72 hours and 24 hours in advance f those outages taking place. In the case of service interruptions, indica e response times and update frequencies until resolution.

Pla ned outages shall, to the maximum extent, be scheduled outside of normal busin ss hours.

3.6.5.3. Tasks:

3.6.5.3.1. In accordance with DRD 007 – System Administration Plan, the contractor shall develop and implement a System Administration Plan that provides service to users and administrators for the full range of support necessary to use the contractor provided solution. The contractor shall submit, NLT 150 days after NTP, the System Administration Plan for approval to the Government.

3.6.5.3.2. The Government requires the full range of system administration services and technical support services for CoMET across NASA. The plan shall address, at a minimum, the following aspects of support: concept, implementation schedule, access, and tools. The concept for System Administration Plan shall, at a minimum, address industry standard items such as software updates/patches, outages, operating system and supported browser compatibility, additional feature development, usability problems, basic performance troubleshooting, and resolution of “bugs.”

3.6.5.3.3. Setup Headquarters, Center, and Center Facilities projects and user accounts through a managed system that standardizes, tracks, manages, and logs requests. Enable, within the approval workflow, the ability for designated NASA users to have approval/disapproval authority for assignment of user roles, initiation of projects, deletion of projects, and configuration of data associated with user account set-up and project set-up.

3.6.5.3.4. Assign users to projects with proper roles and categorizations.

3.6.5.3.5. Create, modify, and manage lookup lists.

3.6.5.3.6. Resolve data discrepancies and work with users to correct errors in data, workflows, reporting, or dashboards.

3.6.5.3.7. Monitor system for content quality and consistency.

3.6.5.3.8. Attend regularly scheduled virtual meetin s with Headquarters, Center, and all stakeholders.

3.6.5.3.9. Apply routine and non-routine configuration changes as necessary to ensure the software solution remains op rational.

3.6.6. Record Data Transfer. The contra tor shall s pport regular and recurring transfer of data from CoMET to a designat d Gov ment data repository for the purposes of record keeping and data safe storage Record data shall be transferred no less than monthly in coordination with e Gov rnment.

3.7.Project Schedule.

3.7.1. In accordance with DRD 008 – Project Schedule, the contractor shall create and maintain a p oject sch dule. Contractor shall update and submit a project schedule, for review nd approval monthly. The schedule shall provide the level of detail to address majo milestone , logic paths, relationships, and critical path to allow for satisfactory proj ct pl nning and execution. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all scheduled activities. Administrators, Managers, Software Developers, Subcontractors and Suppliers working on the project must also contribute to developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Initial schedule shall be submitted NLT 30 calendar days after NTP.

3.7.2. The contractor shall execute all required activities in a manner that supports the deployment of the fully operational contractor provided solution and shall occur no later than 270 calendar days after Notice to Proceed.

3.8.Training.

3.8.1. This scope consists of the planning, development, and execution of training associated with the full functionality of the contractor provided solution. Training shall consist of tailored materials, manuals, and sessions appropriate for users, administrators, and read-only users.

3.8.2. General Scope: The contractor shall provide trainers responsible for all aspects of the development and roll-out of training for the Government.

3.8.3. Objectives:

3.8.3.1. Provide comprehensive training to all users, administrators, and read-only users to ensure adequate knowledge and understanding of the use of the ECPM solution.

3.8.3.2. Conduct regular and recurring (reference Paragraph 3.8.1.4.4.) training sessions to maximize training attendance.

3.8.3.3. Ensure all training sessions are recorded and become the property of the Government for use in future on-demand traini g

3.8.4. Tasks:

3.8.4.1. In accordance with DRD 009 – Tr ining Plan, the contractor shall submit for approval, no less than 60-days after Notice T Proceed (NTP), a Training Plan for review and approval by the Governmen The training plan shall address, at a minimum, the following: training objective format, content, sample materials, and draft agenda. All training materi ls inclu ing recorded training sessions, are the property of the Government and an be distributed within NASA and to its subcontractors at no addi onal co t.

3.8.4.2. Develop and produce CoMET specific Training Manual in electronic format for distrib tion to administrators, and read-only users.

3.8.4.3. Maintain training related materials that reflect current CoMET configur tions. M terial shall include, but is not limited to, charts, graphics, presen tions, traini g scripts, training manuals/guides, cheat sheets, role-based training c rriculums recorded/on-demand video, and other documents defined in the Contract r’s tr ining plan.

3.8.4.4. Train system users in all facets of CoMET using a combination of recorded on-demand and synchronous virtual training techniques. At a minimum, the contractor shall:

3.8.4.4.1. Provide semi-monthly virtual training upon the full release of CoMET to the enterprise (NLT 270 calendar days after NTP in accordance with Paragraph 3.7.2.) for no less than eight weeks with an anticipated length of 2-hours per session.

3.8.4.4.2. Reserved

3.8.4.4.3. Reserved

3.8.4.5. Record and make available for unlimited use all training sessions. Recorded sessions shall be bookmarked by topic area in order to allow ease of access by users.

4. PERIOD OF PERFORMANCE.

4.1.Period of Performance. The period of performance shall consist of a 12-month Base

Year and up to four (4) 12-month Option Years with a 6-month option to extend services in accordance with 52.217-8.

4.1.1. Base Year. The Base Year shall include the scope associated with licensure, hosting, configuration, implementation, testing, and launch of fully operational contractor provided solution, as well as the associated training and systems administration.

4.1.2. Option Year 1 – 4.

4.1.2.1. Base Scope. The scope shall include the scope for continuation of licensure and hosting 50 administrator and 450 user licenses. The scope shall include all material, equipment, and labor necessary to perform all tasks associated with the continued licensing, hosting, and security complian e of the contractor provided solution.

4.1.2.2. Option Scope. The scope shall include:

4.1.2.2.1. Option Item #1 - Training. Pr vide quarterly t aining sessions for all option years executed by the Gov rnment

4.1.2.2.2. Option Item #2 - System Administration. The contractor shall provide system administration and technical s pport to users and administrators for the full range of support necessary to operate the contractor provided solution as outlined in Paragraph 3.6.5

5. PHASE-IN AND PHASE-OUT

5.1.1. Phase-In.

Not applicable

5.1.2. Phase-Out.

5.1.2.1. In ac ordance w th DRD 010 – Phase-Out Plan, the Contractor shall maintain full complia ce du ing the period of time leading up to the contract’s expiration or termination. The Contractor shall submit to the Government a Phase-Out Plan sixty (60) calendar days before the contract’s completion or termination. The phase-out plan shall address not less than the following.

5.1.2.1.1. Procedures for retaining the staffing levels necessary to maintain required services through the day of the contract’s expiration or termination.

5.1.2.2. The Contractor shall coordinate its phase-out activities with the incoming

Contractor to affect a smooth and orderly transition at the end of the contract’s period of performance.