Amendment 1.pdf
PDF 194 KB Posted
- Attached to
- RE-BID FME FLOW ENABLEMENT SERVICES
- Solicitation number
- 5400029714
- Issued by
- Richland County, South Carolina
About this file
Amendment 1 to the RE-BID FME Flow Enablement Services request for proposals issued by the South Carolina Department of Transportation (SCDOT) modifies the original solicitation for enablement, training, advisory, and technical support services related to Safe Software FME Flow, an enterprise data automation and integration platform to be performed in Richland County, South Carolina. The scope of work encompasses four mandatory workshops—Introduction to FME Flow and Automation Contexts, Automation in Action, Identification of Automation Opportunities, and Automation Roadmap Review—delivered on a firm-fixed-price basis, along with two supporting activities comprising automation project evaluation and preparation of an enablement summary report. Optional services include as-needed advisory and technical support billed at a Not-to-Exceed hourly rate and instructor-led classroom and virtual training offerings with vendor-proposed discount percentages. Proposals must be submitted online through www.procurement.sc.gov by May 19, 2026, at 2:30 PM, with offeror questions due by May 5, 2026, at 12:00 PM. Award notification will be posted on June 19, 2026. The initial contract term runs three years from May 20, 2026, through May 19, 2029, with automatic one-year renewal periods thereafter unless the state elects not to renew with at least thirty days' notice. No pre-bid conference, mandatory site visit, or bidders' meeting is scheduled.
Pricing for mandatory base enablement services is established on a firm-fixed-price basis, with as-needed support available hourly subject to a Not-to-Exceed cap estimated at approximately 120 hours annually. Optional training services are available at vendor-proposed discount rates, though the agency makes no commitment to purchase these optional offerings. The solicitation contains no explicit budget value or award range and specifies no set-aside designations, disadvantaged enterprise restrictions, or preferences limiting eligible respondents to particular organizational categories. No incumbent vendors or current contractors are identified in the available documentation. Offerors must demonstrate a minimum of three years' experience delivering FME Flow services, experience operating in public-sector or enterprise IT/GIS environments, and qualified personnel possessing FME Flow and FME Form expertise or equivalent qualifications as an authorized Safe Software partner. Award will be made to the highest-ranked responsive and responsible offeror based on evaluation criteria weighted as follows: Technical Approach and Understanding (40 percent), Firm Experience and Relevant Past Performance (25 percent), Proposed Project Team and Qualifications (15 percent), and Price (20 percent).
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Solicitation.pdf | ||
| Pricing Sheet.xlsx | XLSX spreadsheet |
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
SAP
State of South Carolina
Request for Proposal
Amendment #1
Solicitation:
Date Issued:
Procurement Officer:
Phone:
E-Mail Address:
Mailing Address:
5400029714 05/07/2026
AMY SABOL
803-737-0834 SabolAC@scdot.org SCDOT Procurement Office PO Box 191 Columbia SC 29202-0191
DESCRIPTION: FME Flow Enablement, Training, and Support Services 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): 05/19/2026 14:30:00 (See "Deadline For Submission Of Offer" provision) QUESTIONS MUST BE RECEIVED BY: 05/05/2026 12:00:00 EXPIRED (See "Questions From Offerors" provision) NUMBER OF COPIES TO BE SUBMITTED: One (1) Online CONFERENCE TYPE: Not Applicable
DATE & TIME:
(As appropriate, see "Conferences - Pre-Bid/Proposal" & "Site Visit" provisions)
LOCATION: Not Applicable
AWARD &
AMENDMENTS
Award will be posted on 06/19/2026. The award, this solicitation, any amendments, and any related notices will be posted at the following web address: http://www.procurement.sc.gov
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 ninety (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)
mailto:SabolAC@scdot.org http://www.procurement.sc.gov/ http://www.procurement.sc.gov/
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)
Amendment No.
Amendment Issue Date
Amendment No.
Amendment Issue Date
Amendment No.
Amendment Issue Date
Amendment No.
Amendment Issue Date
DISCOUNT FOR
PROMPT
PAYMENT
(See "Discount for Prompt
Payment" clause)
10 Calendar Days (%) 20 Calendar Days (%) 30 Calendar Days (%) _____Calendar Days (%)
PAGE TWO (SEP 2009) End of PAGE TWO
AMENDMENTS TO SOLICITATION
(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]
QUESTIONS FROM OFFERORS-AMENDMENT
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
PROVISION. STRICKEN TEXT IS DELETED. [02-2A097-1]
QUESTIONS AND ANSWERS ARE BELOW. THE SCDOT’S ANSWER APPEARS IN RED.
Question 1:
We’re currently working on the pricing sheet for the RFP and have a quick question. We noticed that the activities and workshops are divided into six separate units, each requiring an individual price. However, our approach has been structured as a complete package rather than as standalone units. Would it be acceptable for us to provide a price with a note indicating that it reflects the full package, including the four workshops and the two activities?
SCDOT Response:
No Change. The solicitation pricing sheet is structured into a total quantity of six (6) workshops and activities, with each item identified separately for scoping purposes. Offerors should make their best effort to provide unit cost information for the individual workshops and activities. If your proposed approach is based on a bundled or complete package methodology, you may include explanatory notes within your pricing submission describing how the pricing was derived and that it reflects a comprehensive package inclusive of the workshops and activities.
However, Offerors should still provide pricing aligned to the bid schedule to the greatest extent practicable to support evaluation and comparison purposes.
Question 2:
Does SCDOT currently use FME or is this an entirely new implementation?
SCDOT Response:
No Change. SCDOT currently maintains an existing FME environment and this is not considered an entirely new implementation. The intent of this solicitation is to support enablement, training, roadmap development, and tactical implementation assistance to help expand and mature SCDOT’s use of FME capabilities across the agency.
Question 3:
If this is not a new FME implementation, what specific FME software and version are currently used by SCDOT?
SCDOT Response:
No Change. FME Flow 2025.2.1
Question 4:
What is the extent of SCDOT's GIS and IT staff experience using FME?
SCDOT Response:
No Change. SCDOT GIS staff currently have experience using FME Form. SCDOT IT staff currently have limited to no direct experience with FME. The purpose of this solicitation is to further expand organizational knowledge, operational maturity, and broader adoption of FME capabilities across both GIS and IT functions.
Question 5:
Will an upgrade from FME Desktop/FME Server to FME Form/FME Flow be required?
SCDOT Response:
No Change. No upgrade is currently required as part of this solicitation. However, Advanced Advisory and Enablement Support may be used for leveling, optimization, expansion, or maturation of existing FME environments and capabilities, as appropriate to support SCDOT’s operational and strategic objectives.
Question 6:
Is the SCDOT FME deployment cloud or on-prem?
SCDOT Response:
No Change. SCDOT’s current FME deployment is hosted on-premises.
Question 7:
Is environment isolation (e.g. separate DEV, TEST, STG, PRD environments) currently used by SCDOT?
SCDOT Response:
No Change. SCDOT currently maintains only a production (PROD) FME environment. Separate DEV, TEST, or STG environments are not currently implemented.
Question 8:
Does SCDOT's IT Team have experience with FME's infrastructure requirements and is there established coordination between them and SCDOT's GIS team?
SCDOT Response:
No Change. SCDOT’s IT team currently has limited experience with FME-specific infrastructure requirements.
Coordination does exist between the IT and GIS teams; however, one of the objectives of this solicitation is to help strengthen operational alignment, knowledge transfer, governance, and enterprise support capabilities related to FME and associated infrastructure.
Question 9:
What external systems are currently in use or in planning that would need integration with FME (see pg. 18 3.4:
Integration with external systems, applications, and APIs)?
SCDOT Response:
No Change. SCDOT currently utilizes and/or is planning integrations with GIS, AASHTOWare solution APIs, and possibly other enterprise project-related systems. Additional systems and integration opportunities may be identified over time as organizational needs evolve. The intent of this procurement is not to define a fixed implementation scope for specific integrations, but rather to expand SCDOT’s organizational knowledge, operational maturity, and understanding of FME capabilities related to integration, automation, data movement, and enterprise workflows.
Question 10:
Is an ESRI ArcGIS Enterprise or ArcGIS Online organization system in place that currently integrates or is anticipated to integrate with FME?
SCDOT Response:
No Change. SCDOT currently utilizes both ESRI ArcGIS Enterprise and ArcGIS Online environments. These platforms are not currently integrated with FME; however, one of the objectives of this solicitation is to assist SCDOT with evaluating, enabling, and expanding integration capabilities between FME and ESRI platforms, as appropriate.
Question 11:
Does SCDOT still have any ArcGIS Desktop (i.e. ArcMap) workflows that will need to be supported or replaced?
SCDOT Response:
No Change. SCDOT may still maintain a limited number of legacy ArcGIS Desktop (ArcMap) workflows within GIS
Office. However, the overall direction is toward modernization and broader adoption of current-generation GIS and integration platforms.
Question 12:
What database (e.g. Oracle, SQL Server, etc.) does SCDOT currently use and what is the version? When is the next database upgrade planned?
SCDOT Response:
No Change. SCDOT currently utilizes both Microsoft SQL Server (MSSQL) and Oracle database platforms across its environment. Specific versions may vary by system and application. There are no major database platform upgrades currently scheduled at this time.
Question 13:
What server OS (e.g. Windows Server 2022 Standard or Datacenter) does SCDOT currently use and when is the next upgrade planned?
SCDOT Response:
No Change. SCDOT currently utilizes Microsoft Windows Server 2022 within its environment. There are no major server operating system upgrades currently planned at this time.
Question 14:
What geospatial data formats (e.g. file geodatabase, shapefile, ArcSDE enterprise geodatabase, etc.) does SCDOT use?
SCDOT Response:
No Change. SCDOT utilizes a variety of geospatial data formats across its environment, including but not limited to file geodatabases, shapefiles, ArcSDE/enterprise geodatabases, and other industry-standard GIS and spatial data formats as needed to support operational and business requirements.
Question 15:
Are python scripts currently scheduled to run regularly or used on an as-needed basis (see pg. 18 3.4: Conversion of existing Python-based ETL processes into FME Workspaces)?
SCDOT Response:
No Change. SCDOT currently does not have Python-based ETL scripts configured as part of the existing FME environment. References within the solicitation are intended to address potential future use cases and capability expansion opportunities.
Question 16:
What is the existing and anticipated user base for FME Form and FME Flow?
SCDOT Response:
No Change. The existing and anticipated user base for FME Form and FME Flow may include SCDOT GIS staff, IT Services personnel, Engineering Support functions, and potentially advanced business users as organizational adoption and use cases expand over time.
Question 17:
What user authentication is in place for login (e.g., Windows/Azure AD or general built-in users)?
SCDOT Response:
No Change. SCDOT currently utilizes Active Directory and Azure-based Single Sign-On (SSO) authentication mechanisms for user access management.
Question 18:
What is the anticipated duration of FME support and maintenance required by SCDOT?
SCDOT Response:
No Change. Please refer to the solicitation section titled “MAXIMUM CONTRACT PERIOD - ESTIMATED (JAN 2006)” for the anticipated duration of support and maintenance associated with this procurement.
File details come from the government source that posted it. Updated .