Solicitation - N3943025R0013.pdf

SOLICITATION, OFFER AND AWARD 1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 7900)

RATING PAGE OF PAGES

2. CONTRACT NUMBER 3. SOLICITATION NUMBER 4. TYPE OF SOLICITATION 5. DATE ISSUED 6. REQUISITION/PURCHASE NUMBER

CODE7. ISSUED BY 8. ADDRESS OFFER TO (If other than item 7)

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

SOLICITATION

9. Sealed offers in original and copies for furnishings the supplies or services in the Schedule will be received at the place specified in item 8, or if hand carried, in the depository located in until local time

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR

INFORMATION

CALL:

A. NAME B. TELEPHONE (NO COLLECT CALLS)

AREA CODE NUMBER EXTENSION

C. E-MAIL ADDRESS

11. TABLE OF CONTENTS

(X) SEC. DESCRIPTION PAGE(S) (X) SEC. PAGE(S)DESCRIPTION

A B C D E F G H

I

J

K

L

M EVALUATION FACTORS FOR AWARD

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

REPRESENTATIONS, CERTIFICATIONS AND OTHER

STATEMENTS OF OFFERORS

PART IV - REPRESENTATIONS AND INSTRUCTIONS

LIST OF ATTACHMENTS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

CONTRACT CLAUSESSOLICITATION/CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/COSTS

DESCRIPTION/SPECS./WORK STATEMENT

PACKAGING AND MARKING

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

CONTRACT ADMINISTRATION DATA

SPECIAL CONTRACT REQUIREMENTS

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

OFFER (Must be fully completed by offeror)

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

10 CALENDAR DAYS (%) 20 CALENDAR DAYS (%) 30 CALENDAR DAYS (%) CALENDAR DAYS(%)

DATEAMENDMENT NO.AMENDMENT NO. DATE

15A. NAME AND

ADDRESS

OF OFFER-

OR

CODE FACILITY 16. NAME AND THE TITLE OF PERSON AUTHORIZED TO SIGN OFFER

(Type or print)

15B. TELEPHONE NUMBER

AREA CODE NUMBER EXTENSION

15C. CHECK IF REMITTANCE ADDRESS IS

DIFFERENT FROM ABOVE - ENTER SUCH

ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL OPEN COMPETITION:

10 U.S.C. 2304 (c) ( )41 U.S.C. 3304(a)

24. ADMINISTERED BY (If other than Item 7)

26. NAME OF CONTRACTING OFFICER (Type or print)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

25. PAYMENT WILL BE MADE BY

27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

CODE

ITEM

STANDARD FORM 33 (REV. 6/2014)

Prescribed by GSA - FAR (48 CFR) 53.214 (c)

SEALED BID (IFB)

NEGOTIATED (RFP)

(Hour) (Date)

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

N3943025R0013

Section A - Solicitation/Contract Form

Electronic Construction Management System (eCMS)

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

0001 eCMS Base Year - SBIR Phase I Orientation

Pricing Arrangement: Firm Fixed Price

1 Lot

0002 eCMS Base Year - SBIR Phase II Configuration

Pricing Arrangement: Firm Fixed Price

1 Lot

0003 eCMS Base Year - SBIR Phase III Deployment - Procon

Pricing Arrangement: Firm Fixed Price

1 Lot eCMS Base Year - SBIR Phase III Deployment - Procon In Operation

Pricing Arrangement: Firm Fixed Price

1 Lot

Option Line Item eCMS Option Year 1 Support

Pricing Arrangement: Firm Fixed Price

1 Lot

Option Line Item eCMS Option Year 2 Support

Pricing Arrangement: Firm Fixed Price

1 Lot

Option Line Item eCMS Option Year 3 Support

Pricing Arrangement: Firm Fixed Price

1 Lot

Option Line Item eCMS Option Year 4 Support

Pricing Arrangement: Firm Fixed Price

1 Lot

Option Line Item 0009 eCMS Optional 6-month extension

1 Lot

Pricing Arrangement: Firm Fixed Price

Section C - Description/Specifications/Statement of Work

STATEMENT OF WORK

1. Overview

Naval Facilities Engineering Systems Command (NAVFAC) seeks a cloud-based, commercial off-the-shelf (COTS) construction management system. The Federal Risk and Authorization Management Program (FedRAMP) will authorize the system as a Moderate Impact Level Cloud Service Offering (CSO). This construction management system will facilitate the review and approval of construction projects through document control, workflows, change order management, reporting, and collaborative communication between construction contractors and NAVFAC. NAVFAC is the Department of the Navy command that manages and engineers facilities, real estate, and construction for the Navy and Marine Corps. The Planning, Design, and Construction (PDC) Directorate delivers facilities project development, design, and construction and is the primary customer for this system. Facilities include shore, medical, waterfront, and ocean facilities.

2. Scope

The contractor shall provide one year of site/unlimited use licenses for software and software support that allows designated NAVFAC employees and contracted firms to manage the full lifecycle of a project from initiation/induction, planning, design, procurement, and construction phases. The system shall meet FedRamp moderate security requirements. The system shall simultaneously scale and accommodate over 5,000 projects and over 20,000 internal and external users. The contractor shall provide and update training material for the new system. The system shall adhere to NAVFAC Information Technology Center (NITC) Risk Management Framework (RMF) standards, including obtaining and maintaining an Authority to Operate (ATO). The system shall store Controlled Unclassified Information (CUI) files and data related to each project loaded into the system. NAVFAC shall not store any classified data in the system. The system shall not store personally identifiable information (PII) in the system. The system shall incorporate workflows, process tracking, collaboration, and business intelligence. NAVFAC may store procurement-sensitive data in the system. The system will service a user community comprising construction contractors and NAVFAC personnel. As such, the system shall utilize security measures to protect procurement-sensitive data. NAVFAC currently has an existing CMiC product running the current eCMS that is on its last option year. The vendor will provide mapping for data migration to transport the existing eCMS data into the awarded vendor database and related system configuration elements, if necessary. The new vendor shall work with NITC and CMiC to mutually develop a data transfer process to incorporate all the current eCMS data in the incumbent system into their application to provide a continuance of service for existing projects.

2.1. Period of Performance

The Period of Performance (PoP) shall be five years after date of award and shall be inclusive of one base year followed by four (4) one-year option periods. An optional 6-month extension CLIN shall be incorporated pursuant to FAR 52.217-8 Option to Extend Services.

3. Requirements

3.1. System Capability

3.1.1. The system shall support up to 30,000 users (estimated one-third Government and two thirds non-Government) and be scalable up to 50,000 users.

3.1.2. The system shall support a minimum of 10,000 projects and will be scalable up to 20,000 projects.

3.1.3. The system shall support a simultaneous demand load of at least 1,000 users worldwide.

3.1.4. The system shall provide the capability to upload and download specific sets of data. This will allow the system to integrate with other NAVFAC systems. Specific tasks include the following:

3.1.4.1. Develop eCMS Integration strategy along with NAVFAC, NITC and the eCMS Change Control Board (CCB).

3.1.4.2. Evaluate and prioritize enterprise application integration with NAVFAC, NITC and the eCMS CCB.

3.1.4.3. Test, implement, and deploy enterprise application integration requirements via NITC.

3.1.5. Report permissions assigned to any user or group of users

3.1.6. Report permissions assigned to any or all user groups

3.1.7. Archive user groups that are no longer required.

3.1.8. The system shall support both design-build and design-bid-build projects.

3.1.9. The system shall allow NAVFAC administrators to set up projects upon contract award and assign different access levels to personnel on their project team.

3.1.10. The system shall enable uploading files in bulk or batch and shall be capable of running in the background.

3.1.11. Integrated Email and Browser-based Workflow Management

3.1.11.1. The system shall provide email capabilities to manage document workflow to facilitate collaboration

3.1.11.2. The system shall capture and record e-mail responses, attachments, and action codes from users responding to the system-generated e-mail.

3.1.12. Native File Integration

3.1.12.1. The system shall provide a web based viewing capability for Computer Aided Design (*.dwg, *.dxf), schedules (e.g. *.xer, *.

prx, *.p3, *.mpp,), portable documents (*.pdf), office (*.doc, *.xls, *.ppt), building information modeling (*.rvt, *.rfa, *.rvg, *.rft, *.

rte) files.

3.1.12.2. The system shall allow users to edit files in the system in native file format (including, but not limited to; MS Word, MS Excel, ACAD, Oracle P6, Adobe, NavisWorks, Sketchup Pro, Revit, PDF, etc.) when processing a document in a review cycle using web browser.

3.1.12.3. The system shall allow users to upload NAVFAC Construction Standard Forms

3.1.12.4. The system shall enable users to digitally sign files to indicate approval / acceptance

3.1.12.5. The system shall allow users to upload NAVFAC Safety forms

3.1.12.6. The system shall capture metadata when a user uploads NAVFAC forms.

3.1.13. Notifications

3.1.13.1. The system shall enable mass notifications, including system status, from within the system

3.1.13.2. Enable triggered and ad hoc notifications of changes in status projects and tasks.

3.1.13.3. The system should enable alerts on the user home page

3.1.13.4. The system should enable alerts on the login screen

3.1.13.5. The system shall allow individual users to receive informational notifications

3.1.13.6. The system shall allow user groups to receive informational notifications

3.1.13.7. The system shall allow users with the appropriate permissions to create new notifications

3.1.13.8. The system shall able to track if review emails were received by individual users

3.1.13.9. The system shall be able to disable/enable tracking for emails

3.1.14. Record Integration

3.1.14.1. The system shall enable users to relate or link data records to other data records

3.1.14.2. The system shall enable users to link data records to files

3.1.15. Projects

3.1.15.1. The system shall support a standardized naming convention for projects

3.1.15.2. The system shall capture command echelon level information for a project

3.1.15.3. The system shall provide project statuses of "Open", "Closed", or "Archived"

3.1.15.4. The system shall allow users to assign a project status to a project

3.1.15.5. The system shall default all new projects as "Open" status

3.1.15.6. The system shall provide folders for organizing project documentation for all projects

3.1.15.7. The system shall provide a folder structure for organizing the folders associated with a project

3.1.15.8. The system shall provide the following folders for a project: default folder for a project, Contract Items folder, Meeting Minutes folder, Plans & Specifications folder, Submittals, RFIs, Quality Assurance & Performance Assessment folder, Schedule folder, Contract Modifications folder, Acceptance folder, Base Access Request folder, and an Other folder.

3.1.16. File Upload

3.1.16.1. The system shall allow users to upload documents, photographs and videos

3.1.16.2. The system shall capture the "File Type" of the file uploaded as "Document", "Photo", or "Video"

3.1.16.3. The system shall require a minimum resolution requirements or minimum DPI upon photo upload

3.1.16.4. The system shall require users to upload a file to a project and project folder

3.1.17. Data Entry Forms

3.1.17.1. The system shall allow users to upload data entry forms with predefined fields

3.1.17.2. The system shall provide default data entry forms

3.1.17.3. The system shall allow users to configure default data entry forms

3.1.17.4. The system shall allow users to create new data entry forms

3.1.18. Metadata

3.1.18.1. The system shall capture metadata for each uploaded document including: upload time, upload user name, upload user ID, upload file size, upload file project name, and upload document Echelon.

3.1.18.2. The system shall provide a document type attribute with the following values: Contract Item, Meeting Minutes, Plans & Specifications, Submittal, RFI, Quality Assurance & Performance Assessment, Schedule, Contract Modification, Acceptance, Base Access Request

3.1.18.3. The system shall require users to select a document type when uploading a document

3.1.18.4. The system shall allow users to provide comments for a document as part of the upload process

3.1.19. File Management

3.1.19.1. The system shall retain an audit trail of any edits or deletions to files in the system

3.1.19.2. The system shall allow users to predefine naming conventions for project files

3.1.19.3. The system shall allow users to assign custom labels to project files

3.1.19.4. The system shall capture the file versions as "1" upon initial upload

3.1.19.5. The system shall increase the file versions number by 1 whenever an edit is made to an uploaded file

3.1.19.6. The system shall allow users to upload the same file name multiple times as separate versions of that file

3.1.19.7. The system shall allow users to link document data between folders

3.1.19.8. The system shall allow users to send predefined documents to users within the system

3.1.20. Project Schedules

3.1.20.1. The system shall provide the ability to view a project schedule within the application

3.1.20.2. The system shall provide tasks for a project schedule

3.1.20.3. The system shall provide subtasks for a project schedule

3.1.20.4. The system shall allow users to associate owners to tasks and subtasks in a schedule

3.1.20.5. The system shall allow users with appropriate permissions to assign scheduled completion dates to tasks and subtasks in a schedule

3.1.20.6. The system shall allow users to baseline a schedule within the system

3.1.20.7. Ability to establish and maintain history for baselines for schedule, cost, and scope, with unlimited baselines and comparison tracking tools. Integrated baseline change management tools to document evolution of approved baseline changes (e.g. approver, date distributed, date approved, change impact, duration of time to document approval, etc.). [Note this is different from contract changes /modifications]

3.1.20.8. Ability to document and monitor and control project risks via risk register to include assigning a risk owner and tracking residual risk. Output reports to graphically capture overall project risk, top risks, and risk by project phase.

3.1.20.9. Ability to document and track project issues and escalate through workflows to assigned leadership teams for resolution.

3.1.20.10. The system shall allow users to provide an actual completion date for a task or subtasks in a schedule

3.1.20.11. The system shall provide a graphical alert that a tasks or subtask has exceeded it schedule completion date

3.1.20.12. The system shall allow users to link a document to a task or subtask in a project schedule

3.1.21. Drawings

3.1.21.1. The system shall provide a comprehensive markup tool for document and drawing review. Markup tool shall provide document versioning. Markup tool shall track user, user comments, and responses.

3.1.22. Review Cycle

3.1.22.1. The system shall provide review cycle workflows

3.1.22.2. The system shall allow users to initiate a workflow process for a system record or an uploaded file

3.1.22.3. The system shall allow users to approve system records and files using workflow capabilities as part of a review cycle

3.1.22.4. The system shall allow users to reject system records and files using workflow capabilities as part of a review cycle

3.1.22.5. The system shall allow users to edit system records and files using workflow capabilities as part of a review cycle

3.1.22.6. The system shall allow users to route system records and files to the previous reviewer after editing using workflow capabilities

3.1.22.7. The system shall allow users to delegate review responsibilities to other users

3.1.22.8. The system shall allow users to set deadlines as part of a review cycle

3.1.23. Workflow

Workflow describes requirements around work processes associated with each object type (e.g., RFI, Submittal, Punch Lists, Non-compliance Notices, Daily Reports, etc.). While the individual workflows for each object type may differ, the workflow requirements are -for the most part - common (e.g., "create a workflow" or "modify a workflow"). NAVFAC and Contractor personnel carry out many processes to execute a project. For example, the steps necessary to submit and process a Request for Information (RFI) are well defined and must be executed consistently so that meaningful process performance metrics can be measured.

3.1.23.1. The system shall provide a default workflow for the following: Meeting Minutes, Plans & Specifications, Submittals, RFIs, Quality Assurance & Performance Assessment, Schedule, Contract Modifications, Acceptance, and Contractor.

3.1.23.2. The system shall allow users to initiate each workflow using workflow capabilities

3.1.23.3. The system shall require final approval from Government users for each workflow document.

3.1.23.4. Approve documents based on workflows (e.g. change request form to modify a project baseline, request for a Promise to Pay (PTP) or Authority to Obligate (ATO, generate SAT-TO documents to route for approval, etc). Enable authorized users to review and approve and digitally sign documents based on workflows and assigned project roles to formally indicate acceptance/approval. Signed files/records are locked and cannot be edited

3.1.24. Reporting Requirements

Reporting describes requirements around extracting and organizing, extracting, and making information available to users. Reporting could take the form of displaying a single set of record data in a consistent format so that the data can be transmitted to others (e.g., a single Submittal Record report that can be printed or sent via eMail). It could also take the form of an entire set of record data that can be downloaded / printed (e.g., a record of all Submittals within a specific timeframe or with a given adjudication status). Finally, reporting includes the dynamic presentation of system and project performance data as "dashboards" that are commonly used to prepare briefings (e.

g., a dashboard displaying RFI performance measures such as cycle time, trends, and record counts for a given FEC).

3.1.24.1.1. Reporting Data

3.1.24.1.2. The system shall provide users with a defined data hierarchy

3.1.24.1.3. The system shall allow users to aggregate data at each of the Command Echelon levels.

3.1.24.1.4. Reporting Capabilities

3.1.24.1.5. The system shall provide reporting capabilities

3.1.24.1.6. The system shall allow users to generate predefined reports

3.1.24.1.7. The system shall allow users to create customized ad hoc reports

3.1.24.1.8. The system shall allow users to report on all metadata captured during document upload

3.1.24.1.9. The system shall allow users to aggregate reporting data at the enterprise level

3.1.24.1.10. The system shall allow users to aggregate reporting data at the echelon level

3.1.24.1.11. The system shall allow users to aggregate reporting data at the project level

3.1.24.1.12. The system shall allow users to aggregate reporting data at the project document level

3.1.24.1.13. The system shall allow users to aggregate reporting data based on project document access type

3.1.24.1.14. Provide dashboards with graphic review of project performance.

3.1.24.1.15. The system shall allow users to download / print / export reports and dashboards to a .DOCX, .PDF, .XLSX, .XML, CSV, or .TXT file type

3.1.24.2. Reporting Templates

3.1.24.2.1. The system shall be able to generate cycle-time reports for RFIs and Submittals

3.1.24.2.2. The system shall be able to generate cycle-time reports for RFIs and Submittals from an enterprise level

3.1.24.2.3. The system shall be able to generate cycle-time reports for RFIs and Submittals by Echelon

3.1.24.2.4. The system shall be able to generate cycle-time reports for RFIs and Submittals by user group

3.1.24.2.5. The system shall be able to generate cycle-time reports for RFIs and Submittals by individual users

3.1.24.2.6. The system shall be able to generate deadline reports for all document workflows

3.1.24.2.7. The system shall be able to generate deadline reports by document type

3.1.25. Other

3.1.25.1. The system shall support NAVFAC document naming convention

3.1.25.2. The system shall enable adding a limited number of custom fields of various types (i.e., text, date, numeric)

3.2. System Configuration

3.2.1. The system shall be accessible via the Internet with no application installation required.

3.2.2. The system shall provide a centralized project stakeholder directory that allows project teams to record, categorize, and manage stakeholder information, including roles, contact details, engagement preferences, and influence levels. It shall enable targeted communication through automated notifications and customizable reports based on stakeholder roles and interests, ensuring timely updates on project progress and changes.

3.2.3. System shall be capable of establishing Portfolio, Program, Project, Product hierarchy.

3.2.4. Provide mobile access and work on designated mobile computing devices.

3.2.5. Employ Asynchronous programming to function on a low bandwidth system (5mbps+).

3.2.6. User and User Groups Administration

3.2.6.1. Security setting and permissions will be configured for each user group and will be editable. Administrators will be able to assign one or more roles to each user with log-in credentials for specified projects (i.e., a given user may fill one role on one project and a completely different role on a different project).

3.2.6.2. The ability to manage user (whether NAVFAC or Contractor) access to a project is very important. NAVFAC Administrators will be able to assign this permission to a specified user group (e.g., Construction Manager).

3.2.6.3. The system will utilize multiple user groups to govern access to the views, forms, workflows, dashboards, notifications, and reports that comprise the system. An initial list of user groups upon award of the contract by the government. It is very likely that other user groups will be added over time

3.2.6.4. Efficiently manage user assignment to one or more user groups

3.2.6.5. Manage user group permissions at a granular level.

3.2.7. The system shall provide document workflow processes for various project roles.

3.2.8. The system shall support a logical folder structure with control access based on permissions and roles for various project members from NAVFAC and the Contractor.

3.3. System Deployment/Operations

3.3.1. Documentation - Provide User, Administrator, and System Release Documentation for eCMS User Community, eCMS Development Group, eCMS Contractor Support Group and NITC.

3.3.2. Virtual Seminars - The vendor shall provide a minimum of two people, a senior staff member and a junior staff member, to host a week-long workshop/seminar for the eCMS CCB. The vendor and eCMS CCB will mutually agree to an agenda for the week long workshop/seminar. Topics for the agenda can include, but are not limited to training, discussion and previews of upcoming new features and enhancements, and detailed discussion of previously occurring issues and problems within the system.

3.4. System Enhancements

3.4.1. System Enhancements - Implement software enhancements to the eCMS application. Specific tasks include:

3.4.1.1. Identify emerging eCMS enhancements in consultation with NAVFAC and the eCMS CCB

3.4.1.2. Assist in developing eCMS System Enhancement strategy along with NAVFAC and the eCMS change control board (CCB).

3.4.1.3. Develop analysis and cost information for proposed software enhancements/modernizations, including third-party vendors.

3.4.1.4. NAVFAC shall either approve, or reject, each proposal for enhancements or modernizations. NAVFAC shall prioritize each proposal, if NAVFAC approves the proposal.

3.4.1.5. Propose and deliver business process updates in coordination with software updates on an as needed basis.

3.4.1.6. Each business process update shall adhere to all relevant NITC cybersecurity and operational processes, standards and best practices.

3.4.1.7. The contractor shall deliver each business process in coordination with NITC, whenever necessary, to ensure continuity of operations for eCMS and all other NITC applications.

3.5. System Risk Management/Information Assurance

3.5.1. Roles and Permissions

3.5.1.1. All users shall be required to access the system through a two-factor cryptographic authentication process.

3.5.1.2. The system shall provide different levels of access to NAVFAC and non-NAVFAC personnel based on role and organizational level (e.g., staff, supervisor, enterprise, and Military).

3.5.2. The system shall allow authorized users to create new workflow processes.

3.5.3. The system shall allow users with appropriate permissions to add, rename, remove, and control access of folders.

3.5.4. The system shall allow users with appropriate permissions to upload, edit, and comment on project schedules.

3.5.5. The system shall allow users with appropriate permissions to link documents to schedule items.

3.5.6. The system shall allow users with appropriate permissions to view reports and dashboards for project documentation.

3.5.7. The system shall allow users with appropriate permissions to designate a folder as "Government Only"

3.5.8. The system shall allow users with appropriate permissions to designate a folder as "Contractor Only"

3.5.9. The system shall allow users with appropriate permissions to designate a folder as "Collaborative"

3.6. System Support

3.6.1. Support - Support for eCMS will follow the following scheme:

- Tier 1 Basic help desk resolution and service desk delivery Handles basic issues, like password resets or common software problems

- Tier 2 In-depth technical support Addresses more complex issues that require more technical knowledge

- Tier 3 Expert product and service support Handles advanced technical issues, like diagnostic testing and in-depth analysis

3.6.2. The contractor shall provide Tier 3 support for eCMS. This support shall include eCMS software errors, configuration problems, and menu and other display problems.

3.6.2.1. NITC and other parties will address Tier 1 and 2 problems. NITC will address Tier 3 problems that the eCMS project team directly relates to the eCMS application and database server environment, as well as networking problems within the Navy/Marine Corps Intranet (NMCI), Navy ONE-Net (OCONUS Enterprise Network) and the NAVFAC Azure Cloud.

3.6.3. The contractor shall provide application support twenty-four hours per day, seven days per week. Because of the time zone difference between the NAVFAC Command Customer, who represents the eCMS field user community, and is located in Washington, D.C. and NITC, the Contract Customer, located in Port Hueneme, CA, the business hours are 8:00am - 8:00pm EST.

3.6.4. The response time during business days and hours is one hour or less.

3.6.5. The response time outside of business days and hours is up to two hours or less.

3.7. System Training

3.7.1. Training - Provide remote, live, routine training sessions of existing and new functions for eCMS user community, eCMS CCB, eCMS Contractor Support Group and NITC.

3.8. NAVFAC expects that NAVFAC administrators shall be able to perform all the actions identified above using existing system functionality and without the need for any custom code.

3.9. Proposed Project Team

3.9.1. Project Manager, Sr. - Plan, initiate, and manage information technology (IT) projects. Lead and guide the work of technical staff.

May supervise the project team. Serve as liaison between business and technical aspects of projects. Plan project stages and assess business implications for each stage. Monitor progress to assure deadlines, standards, and cost targets are met. Possesses and applies a comprehensive knowledge across key tasks and high impact assignments. Plans and leads major technology assignments. Evaluates performance results and recommends major changes affecting short-term project growth and success. Functions as a technical expert across multiple project assignments.

3.9.2. Project Manager, Jr. - Plan, initiate, and manage information technology (IT) projects. Lead and guide the work of technical staff.

Serve as liaison between business and technical aspects of projects. Plan project stages and assess business implications for each stage.

Monitor progress to assure deadlines, standards, and cost targets are met. Applies fundamental concepts, processes, practices, and procedures on technical assignments. Performs work that requires practical experience and training. Work is performed under supervision.

3.9.3. Analyst, Sr. - Analyze science, engineering, business, and other data processing problems to implement and improve computer systems. Analyze user requirements, procedures, and problems to automate or improve existing systems and review computer system capabilities, workflow, and scheduling limitations. May analyze or recommend enhancements or modifications to the system.

3.9.4. Analyst, Jr. - Analyze science, engineering, business, and other data processing problems to implement and improve computer systems. Analyze user requirements, procedures, and problems to automate or improve existing systems and review computer system capabilities, workflow, and scheduling limitations.

3.9.5. DBA, Sr. - Administer, test, and implement computer databases, applying knowledge of database management systems. Coordinate changes to computer databases. Design strategies for enterprise database systems and set standards for operations, programming, and security. Design and construct large relational databases. Integrate new systems with existing warehouse structure and refine system performance and functionality. May plan, coordinate, and implement security measures to safeguard computer databases.

3.9.6. Tech Writer - Write technical materials, such as equipment manuals, appendices, or operating and maintenance instructions. May assist in layout work.

3.10. Program Management

The Contractor shall provide the program management, control and reporting functions necessary to manage and direct the accomplishments of the efforts required under this SOW.

3.10.1. Program Manager

The Contractor shall designate a Program Manager (PM) who shall have responsibility for the overall program and act as the primary technical point of contract with NITC for all matters pertaining to this contract. The Program Manager shall keep the COR informed of the status of the technical and management efforts and expenditures on the contract by means of monthly reports, by telephone conversations, and by meetings at NITC.

3.10.2. Project Plans/Schedules

The Contractor shall generate and maintain schedules for each task assignment in both GANTT and PERT format, or other appropriately designated scheduling format. The Contractor shall ensure that adequate resources are assigned to the tasks to be accomplished and shall report deficiencies. On significant tasking, when directed by the COR, the Contractor shall also implement a formal risk management system (RMS) with which the Contractor shall continually assess technical, cost and schedule risk and implement/recommend and report on measures planned and implemented to mitigate high and medium risks.

3.10.3. Monthly Status Reporting

The Contractor shall provide highlights of actions that occurred during the month relative to contract performance. The Contractor shall provide information on deliverables, meetings, and hours of work performed. Actual and projected slippages and ahead of schedule accomplishments shall be reported along with their actual and projected impact on overall contract performance.

3.10.4. Financial Reporting

The contract financial status shall be reported monthly. The financial status report shall include current month contract expense, as well as cumulative contact expenses. The Contractors shall also include detailed financial and staffing level information on individual tasks and programs.

4. Deliverables

4.1. Software

4.1.1. One year of site/unlimited use licenses for software per year of contract

4.2. System Enhancements

4.2.1. Analysis, Design, Architecture, Mapping, and Implementation Document

4.2.2. Test Plan, Business System Deployment POA&M

4.3. Application Integration

4.3.1. Analysis, Design, Architecture, Mapping, and Implementation Document

4.3.2. Test Plan, Business System Deployment POA&M

4.4. Training and Documentation

4.4.1. User, Administrator, System Release Documentation

5. References

The following reference(s) are identified as applicable to this contract:

5.1. NIST 800-53A -- Federal Information Management Act (FISMA) of 2002 (NIST 800-53A, Guide for Assessing the Security Controls in Federal Information Systems)

5.2. SECNAVINST 5239.3A -- Secretary of Navy Instruction (SECNAVINST) 5239.3A, DON Information Assurance Policy

5.3. DoDI 8500.1 -- Department of Defense Instruction (DoDI) 8500.1 Cybersecurity

5.4. NIST SP-800-37 -- National Institute of Standards and Technology (NIST) SP-800-37 Guide for the Security Certification and Accreditation of Federal Information Systems

5.5. NIST SP-800-53 -- NIST SP-800-53 Recommended Security Controls for Federal Information Systems

5.6. DCID 6/3 -- DCID 6/3 Protecting Sensitive Compartmented Information Within Information Systems (DCID 6/3)--Manual

5.7. Executive Order 12958 -- Executive Order 12958, National Security Information, Executive Office of the President, July 1995

5.8. National Security Directive 42 -- National Security Directive 42, National Policy for the Security of National Security Telecommunications and Information Systems, Executive Office of the President, July 1990

5.9. Office of Management and Budget Circular A- 130 -- Office of Management and Budget Circular A-130, Management of Federal Information Resources, Executive Office of the President, 8 February 96

5.10. Public Law 100-235 -- Public Law 100-235, 101 STAT.1724, Computer Security Act of 1987, 8 January 1988

5.11. NSTISS Policy No. 200 -- National Security Telecommunications and Information Systems Security (NSTISS) Policy No. 200, National Policy on Controlled Access Protection, National Security Telecommunications and Information Systems Security Committee, July 1987

5.12. DITSCAP 5200.40 -- DoD Information Technology Security Certification and Accreditation Process (DITSCAP) 5200.40, 7 October 1999

5.13. DoDI 8510.bb -- DoDI 8510.bb, Department of Defense Information Assurance Certification and Accreditation Process (DIACAP)

5.14. DoDI 8510.01 -- Risk Management Framework (RMF) Reissues and renames DoD Instruction (DoDI) 8510.01

5.15. DoDI 8500.00 -- Reissues and renames DoD Directive (DoDD) 8500.01E (Reference (a)) as a DoD Instruction (DoDI) pursuant to the authority in DoDD 5144.02 (Reference (b)) to establish a DoD cybersecurity program to protect and defend DoD information and information technology (IT).

5.16. DOD 8570.01M -- Department of Defense 8570.01 Manual - Information Assurance Workforce Improvement Program

5.17. CJCSI 6510.01F -- Information Assurance (IA) and support to Computer Network Defense (CND) 09 Feb 2011

5.18. Safeguarding Controlled Unclassified Information

5.19. The Contractor shall protect all CUI information per DoD 5200.01 volumes 1-3, DoD 5200.48, 32 CFR Part 117, and Navy Information Security Program manuals. Contractor/Subcontractor personnel shall not disclose and must safeguard procurement sensitive information, computer systems and data, privacy act data, and government personnel work products, which are obtained or generated in the performance under this contract. This includes but is not limited to electronic transmission of material.

5.20. Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code (USC), section 552a and applicable agency rules and regulations.

5.21. Contract and Subcontractor shall be held liable for all PII and CUI data breaches where it is culpable (e.g., unauthorized disclosure, contract proprietary information, social security numbers, etc.).

5.22. All contractors shall take the DoD Mandatory Controlled Unclassified Information (CUI) Training every year and submit training certificate to the CORs. Link provided is: https://securityawareness.usalearning.gov/cui/index.html

5.23. Upon completion of this contract, all CUI documentation (reports, working papers, photographs, drawings, government furnished equipment or information, etc.) shall be turned over to: NAVFAC EXWC, Code SH, 1000 23rd Avenue, Building 1100, Port Hueneme, CA 93043-4370.

5.24. Accessing DoD IT Systems

5.25. Contractors who require access to DoD IT systems shall have an adjudicated investigation at the appropriate level required by the Authority To Operate for that system.

5.26. At a minimum, personnel accessing DoD IT systems shall complete the current fiscal year DoD Cyber awareness training and have a system authorization access request on file with the Command's Information System Security Manager.

5.27. Security Clearance Requirement.

5.28. This effort will involve the Contractor to access and potentially populate information/material at the Controlled Unclassified Information (CUI) level and/or access restricted areas. At a minimum all Contractor and Subcontractor employees must have a current (within the past 5 years) favorable Tier 3 or equivalent investigation or higher investigation prior to starting work on the contract. Personnel who require administrative access to IT systems must have a current (within the past 5 years) favorable Tier 5 or equivalent investigation prior to starting work. All service and support on this contract are required to be U.S. citizens and must be able to obtain and maintain favorable adjudication of the aforementioned Personnel Security Investigation (PSI). As this is an unclassified contract, NAVFAC EXWC Security will be responsible for ensuring contractors meet the PSI requirements.

5.29. Contractor and Subcontractor personnel cannot begin work on the contract until written concurrence from the government security management office is obtained, stating that the employee has met the criteria to support this contract. In support of this requirement, the contractor shall submit a list reflecting all personnel working on the contract 14 days after the contract has been awarded. This list shall be updated as needed due to personnel changes.

5.30. The government retains the right to request removal of Contractor/Subcontractor personnel, who regardless of prior clearance or adjudication status whose actions, while assigned to this contract, are determined by the COR or government security management office to conflict with the interest of the government. If such a removal occurs, the Contractor shall assign qualified personnel, who is able to meet the criteria of this contract, to any vacancy.

5.31. The Contractor/Subcontractor shall report any personnel who are no longer working under this contract effort within 48 business hours to the Contracting Officers Representative (COR).

5.32. Logical and Physical Access

5.33. Contractors and Subcontractors may require logical or physical access to DoD installations and or Navy Information Technology (IT) systems. Common Access Cards (CAC) will only be issued in accordance with DoDI-5200.46. Contractors shall submit required paperwork to the COR and all CAC issuances will be conducted by the government security management office. Contractor employees who do not require access to Navy IT systems or physical access to a single DoD installation will use the local defense Biometric Identification System (DBIDS).

DBIDS processing is the responsibility of the Contractor.

6. COR Designation

6.1. The Contracting Officer's Representative (COR) for this task order is Mariah Mitchell, (805-982-4914); mariah.e.mitchell2.civ@us.navy.

mil.

6.2. The Technical Contracting Officer's Representative (TCOR) for this task order is Charles Lindsey, (805-982-5991); charles.r.lindsey.civ@us.

navy.mil.

7. Clearances and Licensing

7.1. All contractor employees with access to NMCI shall complete at a minimum the DoD Cyber Security Challenge training prior to submitting request for access. Access to NMCI or other information systems is subject to approved System Authorization Access Request (SAAR) or SAAR-N submitted through the CSO.

7.2. To obtain a NMCI account, in addition to submitting a SAAR or SAAR-N form, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions. The Government may also periodically request IA certification status of KTR personnel. 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.

Requirements Requirement is for a cloud-based COTS construction management system that meets FedRAMP moderate security requirements.

Section D - Packaging and Marking

Section E - Inspection and Acceptance

Overall Contract Inspection/Acceptance Locations

Inspection and Acceptance Location

Both Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles Lindsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Inspection and Acceptance Location

Both Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles Lindsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Inspection and Acceptance Location

Both Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles Lindsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Inspection and Acceptance Location

Both

Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles Lindsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Option Line Item

Inspection and Acceptance Location

Both Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles Lindsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Option Line Item

Inspection and Acceptance Location

Both Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles Lindsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Option Line Item

Inspection and Acceptance Location

Both Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles Lindsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Option Line Item

Inspection and Acceptance Location

Both Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles Lindsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Option Line Item

Inspection and Acceptance Location

Both Destination Instructions: Inspection and acceptance will be governed by the table provided in DFARS 252.232-7006 Wide Area Workflow Payment Instructions (Jan 2023)

DoDAAC: N62583 CountryCode: USA

NAVAL FACILIITES ENGINEERING AND

EXPEDITIONARY WARFARE CENTER, 1000 23RD AVENUE

PORT HUENEME, CA 93043-4301

UNITED STATES

Charles LIndsey, NAVFAC Information Technology Center (NITC), Port Hueneme Email: charles.r.lindsey.civ@us.navy.mil Telephone: 805-982-5991

Section F - Deliveries or Performance

Line Item Delivery Schedule Quantity Address and POC

Period of Performance From 23 Jun 2025 To 22 Jun 2026

1 Lot

Period of Performance From 23 Jun 2025 To 22 Jun 2026

1 Lot

Period of Performance From 23 Jun 2025 To 22 Jun 2026

1 Lot

Period of Performance From 23 Jun 2025 To 22 Jun 2026

1 Lot

Option Line Item

Period of Performance From 23 Jun 2026 To 22 Jun 2027

1 Lot

Option Line Item

Period of Performance From 23 Jun 2027 To 22 Jun 2028

1 Lot

Option Line Item

Period of Performance From 23 Jun 2028 To 22 Jun 2029

1 Lot

Option Line Item

Period of Performance From 23 Jun 2029 To 22 Jun 2030

1 Lot

Option Line Item

Period of Performance From 23 Jun 2030 To 22 Dec 2030

1 Lot

Section G - Contract Administration Data

G.1 TYPE OF CONTRACT

This contract is a Firm Fixed Price type contract.

G.2 AUTHORIZED CHANGES ONLY BY THE CONTRACTING OFFICER

(a) Except as specified in paragraph (b) below, no order, statement, or conduct of the Government personnel who visit the contractor's facilities or in any other manner communicates with contractor personnel during the performance of this contract shall constitute a change under the "Changes" clause of this contract.

(b) The contractor shall not comply with any order, direction or request of Government personnel unless it is issued in writing and signed by the Contracting Officer, or is pursuant to specific authority otherwise included as part of this contract.

(c) The Contracting Officer is the only person to approve changes in any of the requirement of this contract and notwithstanding provisions contained elsewhere in this contract, the said authority remains solely the Contracting Officer's. In the event the contractor affects any changes at the discretion of any person other than the Contracting Officer, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in changes incurred as a result thereof. The address and telephone number of the Contracting Officer is:

NAME: Lorie Aguon (or any Contracting Officer with the appropriate warrant)

ADDRESS: NAVFAC EXWC, 1100 23rd Ave. Building 1100, Port Hueneme, CA 93043-4347

CONTACT: (805) 396-9133, lorraine.m.aguon.civ@us.navy.mil

G.3 CONTRACTING OFFICER'S REPRESENTATIVE (COR)

(a) The COR for this contract is:

See COR designation letter.

(b) The COR will act as a Contracting Officer's Representative for technical matters, providing technical clarification, as necessary, with respect to the specification or statement of work, and monitoring the progress and quality of the contractor's performance.

(c) The COR is not an Administrative Contracting Officer and does not have the authority to direct the accomplishment of an effort which is beyond the scope of the statement of work. When in the opinion of the contractor, the COR requests effort outside of the existing scope of the contract, the contractor shall promptly notify the Contracting Officer. No action shall be taken by the contractor until the Contracting Officer has issued a modification to the contract or until the issue has otherwise been resolved.

(d) In the event that the COR…