Attachment_04_Product_Background_051724.docx
DOCX document 133 KB Posted
- Solicitation number
- S-KS0043-00010843
- Issued by
- Marion County, Oregon
About this file
This document is an attachment to an RFP issued by the City of Salem, Oregon for Enterprise Resource Planning (ERP) software and implementation services. It requests detailed information about the proposed software solution, including the product name, provider, history, current version, user counts, key recent enhancements, technology architecture, and a description of the vendor's product portfolio and innovation approach. The RFP identifies a specific contract opportunity, RFP No. 245050, which is being issued by the State of Oregon. The RFP seeks proposals for the implementation of the ERP software solution, with details on software licenses, functions, metrics, quantities, and dependencies.
The document indicates the City of Salem is seeking an integrated ERP solution with robust data and analytics capabilities. Vendors are required to provide information on their approach to emerging technologies like AI and GenAI as they relate to the proposed solution. Pricing, set-asides, incumbent providers, funding sources, and other contractual terms are not explicitly covered in this attachment, but would likely be addressed in the overall RFP documentation.
View the file
Other files
Show all 23
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
RFP for ERP Software and Implementation Services City of Salem, Oregon
Attachment 4 Product Background
Proposed Solution Information
Solution Product Name:
Firm Providing Solution:
Solution History:
Current Version of the Solution:
Date of Release for Current Version:
Date of Release for Current Major Version:
Date of First Release of Solution:
Identify any Precursor Software Products or Alternate Names for Solution
What is the number of local government customers using Current Major Version:
What is the number of solution users from the largest local government customer using Current Major Version:
Current Version
| What Were Top Five Enhancements in Current Version of the Software |
| 1 |
How as Software Changed Over Previous Three (3) Years
Attach additional pages if necessary
Biggest Limitation of Current Major Version?
Date of next Release of Software
Does the proposed solution have a product roadmap? (Yes/No). If Yes, describe.
Date of next Major Version Release of Software
Solution Architecture:
Briefly describe the proposed solution’s technical architecture. Attach a summary-level technical architecture document.
What is the proposed solutions database technology/infrastructure?
What is the proposed solutions server technology/infrastructure?
What is the proposed solutions file and data storage technology/infrastructure?
Third-Party Components/Products:
List any Third-Party or Open-Source Components/Products embedded in the Software
List any Third-Party or Open-Source Components/Products required for Use with the Software
List any Third-Party or Open-Source Components/Products Recommended for Use along with the Software
Product Portfolio & Innovation
List any other solutions/products that are directly offered by your organization.
List any other solutions/products that are offered by your organization through a partnership with a third party.
Are all of the products/solutions currently provided by your organization integrated with each other.
List any other solutions/products that your organization plans to offer in the next several years.
What is your organizations approach to AI/GenAI, specifically as it relates to the proposed solution?
What is your organizations approach to data/analytics, specifically as it relates to the proposed solution?
Describe the proposed solutions data/analytics capability/functionality.
Include all software licenses proposed on the form below providing the following information:
Software Product Name. Provide the name of the software product as it is expected to appear on any license agreements or official product listings.
Function. Describe the function of the software product. If multiple software products share a similar function, be specific on role of the software and what is and is not allowed with each license License Metric. Define how the software product is licensed. If license is based on quantity, or if the cost of an enterprise license is based on metric, proposers must provide definition for the metric as it appears in contract documentation.
Quantity /Access Limitations. Define any licensed quantities or access limitations to the proposed software.
Dependencies. Define any proposed or third-party components/products that are required to utilize the software product.
| Software Product Name |
| Function |
| License Metric |
| Quantity/ Access Limitations |
| Dependencies |
image1.png
File details come from the government source that posted it. Updated .