Amendment 2.docx

SAP

State of South Carolina

Request for Proposal

Amendment 2

Solicitation:

Date Issued:

Procurement Officer:

Phone:

E-Mail Address:

Mailing Address:

5400021405 12/07/2021

NATHAN DAWSON

(803) 737-9931 ndawson@mmo.sc.gov SFAA, Div. of Procurement Services 1201 Main Street, Suite 601 Columbia SC 29201

DESCRIPTION: SCDOT Software Applications Enhancement

USING GOVERNMENTAL UNIT: SC Department of Transportation

SUBMIT YOUR OFFER ON-LINE AT THE FOLLOWING URL: http://www.procurement.sc.gov

SUBMIT OFFER BY (Opening Date/Time): 01/06/2022 11:00 am (See "Deadline For Submission Of Offer" provision)

QUESTIONS MUST BE RECEIVED BY: 10/22/2021 11:00 am email questions to ndawson@mmo.sc.gov (See "Questions From Offerors" provision)

NUMBER OF COPIES TO BE SUBMITTED: Two (2) Online submissions – One (1) Original and One (1) Redacted Copy Initial here if NO redacted copy is necessary___________ See Section II A “Submitting Confidential Information” clause, and Section IV “Submitting Redacted Offers” clause

CONFERENCE TYPE: Pre-Proposal Conference DATE & TIME: 10/21/2021 11:00 am

(As appropriate, see "Conferences - Pre-Bid/Proposal" & "Site Visit" provisions) LOCATION: WebEx Online Conference

(email ndawson@mmo.sc.gov before 12:00 noon on 10/20/2021 for call-in instructions)

(See Section IIB “Conference – Pre-Bid/Proposal” clause)

You must submit a signed copy of this form with Your Offer. By signing, You agree to be bound by the terms of the Solicitation. You agree to hold Your Offer open for a minimum of 90 calendar days after the Opening Date.

(See "Signing Your Offer" provision.)

NAME OF OFFEROR

(full legal name of business submitting the offer) Any award issued will be issued to, and the contract will be formed with, the entity identified as the Offeror. The entity named as the offeror must be a single and distinct legal entity. Do not use the name of a branch office or a division of a larger entity if the branch or division is not a separate legal entity, i.e., a separate corporation, partnership, sole proprietorship, etc.

AUTHORIZED SIGNATURE

(Person must be authorized to submit binding offer to contract on behalf of Offeror.)

DATE SIGNED

TITLE

(business title of person signing above)

STATE VENDOR NO.

(Register to Obtain S.C. Vendor No. at www.procurement.sc.gov)

PRINTED NAME

(printed name of person signing above)

STATE OF INCORPORATION

(If you are a corporation, identify the state of incorporation.)

OFFEROR'S TYPE OF ENTITY: (Check one) (See "Signing Your Offer" provision.)

___ Sole Proprietorship ___ Partnership ___ Other_____________________________

___ Corporate entity (not tax-exempt) ___ Corporation (tax-exempt) ___ Government entity (federal, state, or local)

COVER PAGE - ON-LINE ONLY (MAR. 2015)

SAP

SAP

PAGE TWO

(Return Page Two with Your Offer) HOME OFFICE ADDRESS (Address for offeror's home office / principal place of business)

NOTICE ADDRESS (Address to which all procurement and contract related notices should be sent.) (See "Notice" clause)

_________________________________________________ Area Code - Number - Extension Facsimile

_________________________________________________ E-mail Address

PAYMENT ADDRESS (Address to which payments will be sent.) (See "Payment" clause)

____Payment Address same as Home Office Address ____Payment Address same as Notice Address (check only one) ORDER ADDRESS (Address to which purchase orders will be sent) (See "Purchase Orders and "Contract Documents" clauses)

____Order Address same as Home Office Address ____Order Address same as Notice Address (check only one)

ACKNOWLEDGMENT OF AMENDMENTS

Offerors acknowledges receipt of amendments by indicating amendment number and its date of issue. (See "Amendments to Solicitation" Provision)

DISCOUNT FOR PROMPT PAYMENT

(See "Discount for Prompt Payment" clause)

PREFERENCES - A NOTICE TO VENDORS (SEP. 2009):

Preferences do NOT apply to Requests for Proposals per SC Consolidated Procurement Code §11-35-1524(E)(5)

PREFERENCES - ADDRESS AND PHONE OF IN-STATE OFFICE:

Preferences do NOT apply to Requests for Proposals per SC Consolidated Procurement Code §11-35-1524(E)(5)

____In-State Office Address same as Home Office Address ____In-State Office Address same as Notice Address (check only one)

PAGE TWO (SEP 2009)

End of PAGE TWO

AMENDMENT #2

Solicitation #5400021405

AMENDMENTS TO SOLICITATION (JAN 2004)

(a) The Solicitation may be amended at any time prior to opening. All actual and prospective Offerors should monitor the following web site for the issuance of Amendments: www.procurement.sc.gov (b) Offerors shall acknowledge receipt of any amendment to this solicitation (1) by signing and returning the amendment, (2) by identifying the amendment number and date in the space provided for this purpose on Page Two, (3) by letter, or (4) by submitting a bid that indicates in some way that the bidder received the amendment. (c) If this solicitation is amended, then all terms and conditions which are not modified remain unchanged. [02-2A005-1]

Highlighted text is added to the original provision. Stricken text is deleted.

SAP

Section VII. of the solicitation is amended as follows: S

VII. TERMS AND CONDITIONS -- B. SPECIAL

OFFSHORE CONTRACTING PROHIBITED (FEB 2015)

No part of the resulting contract from this solicitation may be performed offshore of the United States by persons located offshore of the United State or by means, methods, or communications that, in whole or in part, take place offshore of the United States. [07-7B122-1]

Section VIII. of the solicitation is amended as follows: SA

VIII. BIDDING SCHEDULE / PRICE-BUSINESS PROPOSAL

PRICE PROPOSAL (JAN 2006)

Notwithstanding any other instructions herein, you shall submit the following price information as a separate document:

Provide hourly labor rates for the following categories and place each person named on a submitted resume into the labor category (or categories) for which you propose to bill their time.

These hours are the estimated annual usage for evaluation purposes only.

1. Project Manager

$__________ hourly rate x 1,000 annual estimated hours x 6 years = $___________ TOTAL 1

Duties to include: Assist in requirements gatherings, and manage each project task order to ensure accurate design and on time delivery. Project Managers may need to spend a lot of time on each project during the initial and final phases, but should typically spend no more than 20% of the total time charged to a project during the design phase.

2. Technical Lead

$__________ hourly rate x 2,700 annual estimated hours x 6 years = $___________ TOTAL 2

Duties to include: Assist in requirements gathering, assist in managing projects as needed, oversee the technical development of projects, thoroughly test code before deployment, assist in writing code.

3. Senior Software Developer

$__________ hourly rate x 5,000 annual estimated hours x 6 years = $___________ TOTAL 3

Duties to include: Assist in requirements gathering, analyze work to be delivered, develop code and oversee the development of code by others, assist in thoroughly testing code before deployment.

4. Software Developer

$__________ hourly rate x 7,300 annual estimated hours x 6 years = $___________ TOTAL 4

Duties to include: Develop code; assist in thoroughly testing code before deployment. At least 50% of the coding should be done by this category of developer.

5. Junior Software Developer

$__________ hourly rate x 2,650 annual estimated hours x 6 years = $___________ TOTAL 5

Duties to include: Assist in code development; assist in thoroughly testing code before deployment.

6. Tester

$__________ hourly rate x 1,000 annual estimated hours x 6 years = $___________ TOTAL 6

Duties to include: Test code during and before deployment. Includes taking software through everyday usage to ensure no bugs or glitches exist that would present problems for users.

7. Technical Writer

$__________ hourly rate x 300 annual estimated hours x 6 years = $___________ TOTAL 7

Duties to include: Produces technical documentation. This documentation includes online help, user guides/manuals, white papers, design specifications, system manuals, project plans, test plans, business correspondence, etc.

TOTAL 1 + TOTAL 2 + TOTAL 3 + TOTAL 4 + TOTAL 5 + TOTAL 6 + TOTAL 7

= TOTAL TO BE EVALUATED

[08-8015-1]

QUESTIONS FROM OFFERORS - AMENDMENT (JUN 2017)

THE SOLICITATION IS AMENDED AS PROVIDED HEREIN. INFORMATION OR CHANGES RESULTING FROM QUESTIONS WILL BE SHOWN IN A QUESTION-AND-ANSWER FORMAT. ALL QUESTIONS RECEIVED HAVE BEEN REPRINTED BELOW. THE “STATE’S RESPONSE” SHOULD BE READ WITHOUT REFERENCE TO THE QUESTIONS. THE QUESTIONS ARE INCLUDED SOLELY TO PROVIDE A CROSS-REFERENCE TO THE POTENTIAL OFFEROR THAT SUBMITTED THE QUESTION. QUESTIONS DO NOT FORM A PART OF THE CONTRACT; THE “STATE’S RESPONSE” DOES. ANY RESTATEMENT OF PART OR ALL OF AN EXISTING PROVISION OF THE SOLICITATION IN AN ANSWER DOES NOT MODIFY THE ORIGINAL PROVISION EXCEPT AS FOLLOWS: UNDERLINED TEXT IS ADDED TO THE ORIGINAL PROVISON. STRICKEN TEXT IS DELETED. [02-2A097-1]

The following questions were received pursuant to the original date and time specified on the front of the solicitation:

1. Question: In one of the solicitations from the State of SC that we responded to last year, there was a specific requirement that we do not the work offshore. Are there similar such requirements for this solicitation?

State’s Response: No work offshore will be permitted. See the added clause in Section VIIB in this Amendment.

2. Question: Section III. 3.1.1 Project Programming System (P2S), p15: “We would like to explore integrating P2S with FMIS to eliminate double keying of authorization data and provide real time data.”

a. Please quantify 'real-time' data. How often after creation of a project in P2S does FMIS need to have that data?

b. Are project updates being sent to FMIS? How often (real time, etc.)?

c. Are project deletes being sent to FMIS?

d. Can project data be updated in FMIS such that it should flow BACK to P2S?

e. Can you provide a sample data file or specification?

State’s Response:

a. With FMIS being a federal system P2S would likely not be allowed direct constant access to the data. “Real-Time” in this case would be a nightly upload of FMIS data into P2S and P2S data to FMIS. The federal government has very specific guidance on this matter which may be found on FHWA’s website. Also, it is likely that a nondisclosure agreement may need to be signed.

b. No – we are manually keying project authorization requests in P2S and FMIS.

c. No – we are manually keying this information in P2S and FMIS.

d. See a. Not currently – this is the functionality we would like to explore.

e. See FHWA requirements manual

3. Question: Section III. 3.1.1 Project Programming System (P2S), p15: “A needed upgrade to P2S would be the ability to directly interface with SAP (SCEIS) to allow a daily upload of project expenditure data.”

a. Does SCEIS have a facility to ingest data daily now?

b. If so:

· How is the data sent to SCEIS (file-based, web service, etc.)?

· Does SCEIS have a non file-based method of integration?

· Who creates this data file currently (SAP)?

c. Can you provide a sample data file or specification?

State’s Response: SCEIS has the capability for a daily interface. This will be a new interface that will need to be developed in cooperation with the SCEIS team. A partial list of documented IOG (Interface Operational Guides) can be found on the SCEIS.SC.Gov website http://sceis.sc.gov/page.aspx?id=142

4. Question: Section III. 3.1.1 Project Programming System (P2S), p15: “Another needed upgrade is for P2S to directly interface with SCEIS to have WBS elements created daily instead of once a week.”

a. How is this data sent currently (on the one time per week) (e.g. File-based, web service, etc.)?

b. Is there a non file-based method of receipt?

c. Can you provide a sample data file or specification?

State’s Response: This is currently a file-based interface. A partial list of documented IOG (Interface Operational Guides) can be found on the SCEIS.SC.Gov website http://sceis.sc.gov/page.aspx?id=142

5. Question: Section III. 3.1.1 Project Programming System (P2S), p15: “We currently seek reimbursement for eligible expenditures with FHWA through our legacy system”

a. Is this the same as the daily WBS elements to SCEIS (above)?

b. Please confirm that the data for this exists in the SAP database. How is this data retrieved (SAP report; custom SQL query, etc.)?

c. Is this currently a file-based export/import? Does destination have a non file-based integration endpoint?

d. Can you provide a sample data file or specification?

State’s Response: This is a different interface going from the SCDOT ENTIRE system to FHWA’s FMIS system. The statement was informational only. The system of record for billing FHWA is currently the SCDOT ENTIRE system and not SAP. All data required for billing is not currently in SAP. As noted in the same paragraph, SCDOT is in the process of planning for a project to migrate Federal Billing to the SAP-based SCEIS platform.

6. Question: Section III. 3.1.1 Project Programming System (P2S), p15: “A field should be added to P2S to include federal project agreement end dates to help the agency comply with 2 CFR 200.”

a. Is this the only change or are we to review CFR 200 and perform a gap analysis on the P2S system?

State’s Response: a. Currently, this is the only change.

7. Question: Section III. 3.1.1 Project Programming System (P2S), p16: “A more in-depth report ability is needed in P2S, including a more detailed way to produce adhoc reports.”

a. Is this part of this proposal? This may indicate the need for a data warehouse and reporting system outside of the software application itself. Is this in-line with the goals for this request?

State’s Response: a. Yes, this is part of the proposal. P2S currently leverages SSRS 2017 and produces reports within the application. This is fine and can continue for all “boxed” reports. For ADHOC and what-if scenarios Microsoft Power BI is the platform of choice. It would be acceptable to include ADHOC reports within the application, omitting the Power BI platform.

8. Question: Section III. 3.1.2 Automated Stateside Transportation Improvement Program (STIP), p17: “There is also a public facing STIP application that requires maintenance and updating.”

a. If maintaining and updating the application is part of this request, it would be most helpful to have an idea of how many features are currently known enhancements and some idea of those.

State’s Response: a. The map would require updating to enhance the appearance and functionality. There is a need to create custom searches and to list and print those searches rapidly and effectively. Here is a link to the current public facing STIP: http://206.74.144.42/estip/home/main

9. Question: Section III. 3.1.2 Automated Stateside Transportation Improvement Program (STIP), p17: “There is functionality to perform “what if” scenarios with data contained in previous and pending revisions but we would like this expanded to use hypothetical data.”

a. Can this be further clarified? How much data is involved in a ‘scenario’?

State’s Response: The scenario option is required to gain the ability to add Projects and/or Programs into the STIP to see how it would affect the financial constraint of the overall STIP and Program Category. We would like to add Projects and/or Programs as a scenario and be given the ability to save the scenario and then be able to apply the scenario if it is approved. The amount of data involved needs to capture all Project Identifiers (Project Name, County, COG/MPO, Planned Values), Program Categories and Programs. In our current STIP if you were to add one Mega Project and with that one change it can be reflected on multiple reports, so it is difficult to calculate the amount of data involved.

10. Question: Section III. 3.1.3 Right of Way Data Management System (RWDMS), p18.

a. Are there any enhancements/changes to this system?

State’s Response: At this time no changes or enhancements are planned, however, future required enhancements are possible.

ALL OTHER TERMS, CONDITIONS, BIDDING INSTRUCTIONS, AND SPECIFICATIONS REMAIN UNCHANGED. IF THERE ARE ANY QUESTIONS OR IF ANY CONFUSION OR UNCERTAINTY ARISES AS A RESULT OF THIS AMENDMENT, IT IS THE SOLE RESPONSIBILITY OF THE OFFEROR TO CONTACT THE PROCUREMENT OFFICER FOR CLARIFICATION. CONTACT INFORMATION CAN BE FOUND IN THE TOP RIGHT HAND CORNER OF THE COVER PAGE OF THIS AMENDMENT. REFERENCE THE “DUTY TO INQUIRE” CLAUSE IN THE ORIGINAL REQUEST FOR PROPOSAL.

Page Page image1.png