Amendment No. 00003_RFP No. 693JJ321R000013.pdf

PDF 261 KB Posted

Attached to
Federal Highway Administration, Office of Federal Lands Highway’s eDelivery Construction Management System
Solicitation number
693JJ321R000013
Issued by

About this file

This document contains an amendment to a request for proposal for an eDelivery construction management system. The Federal Highway Administration seeks a comprehensive web-based and mobile system to integrate construction estimating, electronic bidding, management, and documentation. The amendment provides answers to offeror questions, clarifies the scope addresses Attachments 3.1 through 3.9, and removes the word "necessary" from the statement of work. Offerors must utilize Attachments 3.6 and 3.7 to demonstrate how their proposed solution meets requirements, and all terms and conditions of the original solicitation remain unchanged.

View the file

Other files

Show all 14

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

(x)

693JJ321R000013

x x

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 electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT 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 letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

693JJ3

WASHINGTON DC 20590

1200 NEW JERSEY AVE., SE

OFC OF ACQUISITION AND GRANTS MGMT

FEDERAL HIGHWAY ADMINISTRATION

06/08/2021

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers 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

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

06/08/2021

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

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

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

ORDER NO. IN ITEM 10A.

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

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

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

Sarah Berman

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

Previous edition unusable

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

The purpose of this solicitation amendment is to release the questions and answers received for the Phase II proposal submissions - see continuation page. This amendment also provides an update to Attachment 3.1 - Statement of Work.

All other terms and conditions of the solicitation remain unchanged.

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

00003

Document Title Page # of the

Document Section & Paragraph Number Question Government Response

Attachment 3.1 SOW 4 C.4, C.5

We are interested in providing a valuable solution and want to be competitive with our proposal. A clear definition of the scope of work to be bid upon will help us provide an accurate proposal.

Please clarify which lists of requirements in the RFP should bid upon:

• Are we bidding on the list of requirements in Attachment 3.5?

• Are we bidding on the list of requirements in Attachment 3.6?

• Are we bidding on the list of “all the necessary requirements outlined in SOW

Attachment No. 1 – eDelivery System Requirements?” (quoted from paragraph C.4 in

Attachments 3.1) o If so, please define what is meant by “necessary requirements?”

• Are we bidding on all the requirements in Attachment 3.2 ‐ SOW Attachment No. 1 – eDelivery System Requirements?

The scope and requirements for performance and the eDelivery solution are contained within solicitation Attachment 3.1 ‐ Statement of Work and Attachment 3.2 ‐ SOW Attachment 1 ‐ eDelivery System Requirements.

In Phase I, the Offeror was required to utilize Attachment 3.5 to provide a written explanation to demonstrate its solution's capability to meet the high‐level eDelivery system requirements.

For Phase II, the Offeror shall utilize Attachment 3.6 to provide a written explanation demonstrating how its solution meets key eDelivery system requirements.

For the Phase II Live System Demonstration, the Offeror shall utilize Attachment 3.7 as a roadmap to provide a systematic demonstration of how its proposed solution meets all of the functional requirements in Attachment 3.2 ‐ SOW Attachment 1 ‐ eDelivery System

Requirements.

The SOW C.4 reference to "The Contractor shall implement and configure its eDelivery system to meet all the necessary requirements outlined in SOW Attachment No. 1 – eDelivery System

Requirements." means all of the requirements in solicitation Attachment 3.2 ‐ SOW Attachment

No. 1 ‐ eDelivery System Requirements.

A revised SOW is provided via amendment No. 00003 removing the word "necessary."

Request for Proposal 27 Table 4.3.1, Proposal Section

Long experience has shown us that demonstrations using actual, real‐life contract and project data from the agency provide for a more effective experience for our customers.

Are you willing to provide information about previous projects that have been let and awarded by FHWA in support of the demonstration?

We are not able to provide real life contract and project data for the the demonstrations.

Please demo the system with your project data.

FHWA Website FHWA Website FHWA Website In the Standard Pay Item spreadsheet from the FHWA website what are the “Bid_Dec”, “Pay_Dec”, and “Pay Item Type” columns for, and what do they mean?

“Bid_Dec” : Bid Decimal represents the precision at which particular pay item quantity will be bid

on. (For example a bid decimal of 1 means that quantity will be bid to the tenth, i.e. 19.6 tons; a

Bid decimal of 3 means a quantity will be bid to the thousands, i.e. 19.645 miles). “Pay_Dec”:

Pay Decimal works similarly, describing the precision in which a particular pay item may be measured and paid. (Currently all set to 3 decimals, but is actually based on unit price ranges).

"Pay Item Type": This is used as a an additional pay item description that allows pay items to be filtered into similar types/categories. Most items are classified as pay item type "N"(normal pay item). Some other examples of pay item types typically used on projects are: "NM" (Normal pay item, may need materials incentive), "NR" (Normal item, may need rougness incentive), "DI"

(Design Incentives are established 999 incentive pay items. These pay items are not included in the Estimate Total of Bid Items). Other pay item types appear in construction, such as QM

(Quality Materials Incentive), QR (Quality Roughness Incentive), MH (Materials on Hand).

Attachment 3.2 6, 7 Table 1.6.1 Please clarify the difference between “Construction Accounts” and “Construction

Engineering Accounts” as used by the FHWA.

"Construction Accounts" are the individual accounts that contain funds from different sources, and when added together the accounts fully fund a project. These are the accounts that are used to pay the construction contractor during a construction project. "Construction

Engineering Accounts" are not currently calculated in the system, but are used to track the cost of Labor for internal Engineers who are working on the development and construction of the project

Attachment 3.2 6 1.6.1F

Please give an example of when a user would enter an amount to override the calculated amount in a construction account. To be clear, what is the calculated amount based on in this account?

The calculated amount is based on the summation of the pay items that have been submitted and approved for payment for the given monthly pay estimate. The pay items will have an assigned account to pull the money from to pay the contractor. An example of when we would need to overide the calculated amount within a construction account would be if money from a new account becomes available and is added to a project, but needs to be spent immediately.

We would override the calculated amount that is set up with the original accont and then manually withdraw the money from the new account.

Request for Proposal 3 2.1.1

In reviewing FAR 52.227‐14, “Rights in Data”, it discusses “restricted computer software” and limited and unlimited rights. Our understanding from previous engagements, including with the FHWA, is that this FAR provides for the vendor to retain the intellectual property and ownership of the Commercial‐off‐the‐Shelf (COTS) software application even though it may be customized by the vendor for Agency use. We assume that the Agency will not have "unlimited rights" or the right to copy or distribute the software without express permission of the vendor.

The vendor agrees that all data captured by the software system or imported into the software system in the form of Agency data, is the property of the Agency and the vendor asserts no right of ownership to Agency data.

There is no question contained within the statement received. The Government notes that

Volume 3 ‐ Business Proposal provides the Offeror with latitude to provide non‐price related exceptions. If there are exceptions and assumptions about FAR 52.227‐14, the offeror may note these exceptions and assumptions in that section of its proposal for the Government's consideration.

FHWA RFQ No. 693JJ321R000013

Attachment 3.9 ‐ Question and Answer Model

Amendment No. 00003_RFP No. 693JJ321R000013
693JJ321R000013_Questions and Answers_Phase II_Final

File details come from the government source that posted it. Updated .