My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 09 -Agreements for Enterprise Resource Planning System Software
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2025
>
07/15/2025
>
Item 09 -Agreements for Enterprise Resource Planning System Software
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/9/2025 10:30:47 AM
Creation date
7/9/2025 9:26:33 AM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Information Technology
Item #
09
Date
7/15/2025
Destruction Year
P
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
81
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
City of Santa Ana, CA RFP No. 23-132 ERP System, Including Implementation Services <br />P a g e | 13 <br />Table 7 – Data Conversion Requirements <br />Current Repository Description <br />Infor Lawson ERP <br />(Current data goes back to 2006) <br />•General ledger financial data, vendor Information, customer <br />information, budget data, project data, capital asset data, <br />purchase orders, grant data, payment voucher data, <br />customer invoices, payment data/history, contracts, <br />inventory, various financial reports including but not limited <br />to Trial Balance, Revenues & Expenditure ledgers. <br />Questica <br />(Current data goes back to 2018) <br />•Budget detail data <br />•Budget summary data <br />High Line Corp. <br />(Current data goes back to 2000) <br />•Employee data, payroll history, job history, benefit elections, <br />position data/history, performance data, training history, <br />accrual balances. <br />4.5 Implementation Timeline <br />The City is seeking guidance from the Proposers based on their experience for the recommended module <br />phasing and timing. Proposers should clearly communicate all key assumptions along with their proposed <br />schedule. The City is open to suggestions for how best to implement the Proposer’s solution. The <br />Proposer’s recommended implementation timeline should be clearly articulated in their proposal <br />response as described in Section 6 – Implementation Approach and Work Plan under the Proposal <br />Submission Requirements discussed in Section 5 of this document. <br />4.6 Requirements <br />Proposers must respond to the ERP Requirements included in Appendix A – ERP Requirements; responses <br />should be entered into the document. Proposers are to respond to each of these requirements with one <br />of the following response codes: <br />•Y – Meets Requirement <br />•N – Does Not Meet Requirement <br />•W/C – Workaround Proposed or Customization Needed to Meet Requirement <br />•T – Third-Party Solution to Meet Requirement <br />Response Codes “Y” and “N” do not require written responses/comments unless the Proposers wish to <br />present additional benefits or opportunities related to their solution and the requirement. However, <br />response codes “W/C” and “T” do require written responses. For these response codes, Proposers must <br />describe how the requirement will be met.
The URL can be used to link to this page
Your browser does not support the video tag.