B_08_02_Amendment_0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

Issuing answ ers to questions recieved, update to the Scope of Work, and extending proposal due date. All terms and conditions remain the same.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 6

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 24-Oct-2024

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X W912EK25R0005

X 9B. DATED (SEE ITEM 11)

09-Oct-2024

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

24-Oct-2024

CODE

CONTRACTING DIVISION

US ARMY CORPS OF ENGINEERS 1500 ROCK ISLAND D

ROCK ISLAND IL 61201

W912EK 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912EK25R0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

QUESTIONS AND ANSWERS

Automated Workflows

1. What types of custom workflows will need to be built?

This is provided in the SOW.

2. How complex are the workflows (e.g., branching logic, dependencies between tasks)?

The complexity can range from simple linear workflows (e.g., document approvals) to more intricate ones involving branching logic, dependencies between tasks, conditional triggers, and multi-step approvals. The complexity can range from simple linear workflows (e.g., document approvals) to more intricate ones involving branching logic, dependencies between tasks, conditional triggers, and multi-step approvals.

Document and Compliance Management

1. How many types of documents will the system need to handle?

Since I am no sure the exact aim of the question, I will answer in two ways. Technically, it will handle Microsoft Word and PowerPoint as well as Adobe .pdf. In the realm of documentation types, it will handle SOPs, checklists, how-to guides, go-bys, and any other procedural guidance necessary for the functioning of an efficient Quality Management System as defined by ISO 9000:2015.

2. What level of access control or encryption is required for documents?

This is inluded in the copliance reference in 2.0.9

Training and Testing

1. How detailed should the training and testing modules be?

This is provided in the SOW.

2. Will there be different levels of users (e.g., admins, managers, trainees) with different access to training content?

While there are various levels of users with regard to administration and document management, all training content will be available to all users with the ability of an administrator to assign training to a specific user or user group

3. Should the system include support for tracking certifications or test scores?

Yes

Reporting and Metrics

1. What kind of reporting dashboards are expected (e.g., static reports, dynamic charts)?

This is provided in the SOW.

2. Are there specific metrics or KPIs that need to be tracked for compliance?

This is provided in the SOW.

3. Will the system need to export reports to formats such as Excel, PDF?

This is provided in the SOW.

Integrations

1. Does the system need to integrate with any existing platforms (e.g., SharePoint, Active Directory)?

No

User Management

1. How many different user roles will the system support?

Generally, there are two user roles: Document Manager and Document Approver.

2. Is there a need for multi-tenancy, i.e., supporting different departments or units within USACE?

No.

Deployment

1. Where will the application be hosted (e.g., US Government Cloud, AWS GovCloud, on-premises)?

US Government Cloud (MS Azure instance managed by USACE).

2. Will there be staging, production, and development environments?

Production and Development only.

Timeline and Milestones

1. Are there specific deadlines for deliverables within the 10.5-month base year?

This is in the updated SOW.

2. How often will progress need to be reported to USACE?

As needed based on helpdesk assistance.

SCOPE OF WORK

Statement of Work (SOW)

USACE Quality Management Software

1.0 GENERAL: This statement of work is for a quality information system (QMIS). This QMIS is required to continue supporting the utilization of specific features that will provide sustainable growth for USACE organization such as:

Accreditation Management Document Management Process Management Testing and Training Integrations Automated Workflows

The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor, who in turn is responsible to the Government.

2.0 DESCRIPTION OF SERVICES: USACE requires a complete QMIS application that:

1. Provides document and compliance management

2. Provides document and compliance control

3. Provides standard workflows plus the ability to build custom workflows

a. Custom workflows can include document approvals, non-conformance handling, audit processes, training sign-offs, and risk mitigation actions. Workflows may also be built for automated compliance checks and notifications for accreditation processes.

4. Sends automatic email notifications

5. Develops, assigns, and tracks training and testing

a. Training modules should include detailed, structured content with multimedia support (e.g., videos, quizzes, certifications). The testing modules should allow for varied difficulty levels and track test scores.

6. Allows Personnel and group management

7. Provides reporting capabilities, i.e. data and metrics associated with documents (quantity and properties), workflows, training/testing. This will include capability to download and incorporate in reporting admin-level dashboards. Exported CSVs for more detailed analysis and data visualization outside the QMIS.

8. Has applicable security measures applicable for USACE re: access and controls.

9. Complies with USACE Software Assurance and Vulnerability Management in accordance with

DODI 8510.01 RISK MANAGEMENT FRAMEWORK FOR DOD SYSTEMS

3.0 SCOPE: This SOW covers a 10.5-month base year and four 12-month option years for subscriptions and licenses to effectively manage quality in USACE, promotes business growth and development by centralizing all key functions, and embedding quality into the day-to-day. In addition, the QMIS will assist in gaining full visibility of activities, reduce time and resources spent on administration and turn potential risks into opportunities.

Annual Subscriptions Shall Include:

151 Dedicated Users, 80 Concurrent; View-only document access for whole enterprise Automated, customizable workflow capability QMIS Program and Project Management Support Technical support Consulting support (training, implementation) Includes ISO Standards: ISO 9000:2015, ISO 9001:2015, ISO 9004:2015

The Government requests as a deliverable a license to utilize the software as well as how-to documents for administration and end-user tasks. Access to helpdesk services as needed by the users is also required.

All contract personnel performing IA/IT services must comply with DoD training and certification requirements specified in DoD 8570.01-M, Information Assurance Workforce Improvement Program, and maintain required background investigations specified in RA policy. Contract personnel shall provide the Government representative with documentation of certification(s) prior to performing on the contract. In accordance with applicable DoD, Army, and USACE regulations, the Contractor shall ensure that all information systems (IS) and platform information technology (PIT) systems developed and/or supported under this contract comply with cybersecurity and architectural requirements, including, but not limited to: security technical implementation guides (STIG)(e.g., the current version of the Application Security and Development STIG, and the internet access point (IAP) demilitarized zone (DMZ) STIG), and the use of security controls developed under the risk management framework documentation for the system or platform. The Contractor shall address questions regarding these provisions to the Government representative, who will coordinate between the Contractor and the USACE Chief Information Officer (CIO).

4.0 GOVERNMENT FURNISHED EQUIPMENT: The Government will not provide equipment for the performance of these services since this is a subscription not an actual product that would need GFE for the support.

5.0 CONTRACTOR FURNISHED EQUIPMENT: N/A

6.0 PLACE OF PERFORMANCE: Awardee Virtual Website

7.0 PERIOD OF PERFORMANCE:

License keys shall be delivered electronically the day before the start of each performance period.

Base 15 Nov 2024 to 30 Sep 2025

Option Yr 1 1 Oct 2025 to 30 Sep 2026

Option Yr 2 1 Oct 2026 to 30 Sep 2027

Option Yr 3 1 Oct 2027 to 30 Sep 2028

Option Yr 4 1 Oct 2028 to 30 Sep 2029

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 25-Oct-2024 02:00 PM to 29-Oct-2024 02:00 PM.

(End of Summary of Changes)