Loading...
HomeMy WebLinkAboutAppendix ACity of Miami, Florida RFP No. 03-04-151 Appendix A -- Functional Requirements This appendix contains the functional requirements identified during the BPR project described in Section 1. The table below identifies the process areas contained in this appendix. No Process Area 1 Accounts Payable 2 Accounts Receivable 3 Benefits Administration 4 Billing 5 Budget Formulation 6 Business Performance Reporting 7 Cash Management 8,. Compensation Administration 9 Employee Data Management 10 Exit Management 11 Fixed Assets 12 General Accounting_ 13 Grant & Project Accounting 14 Grants 15 Learning & Development 16 Organizational Effectiveness 17 Outlook / Interim Forecast 18 Payroll 19 Item Master 20 Requisition and PO Processing 21 Supplier Partnering 22 Supplier Performance Measurement 23 Contracting 24 Recruiting & Selection 25 StratelicwResource Management 26 Time & Attendance 27 Travel Expense 28 Treasury / Capital Management The ERP-SI must have a thorough understanding of the requirements included in this workbook. It is required that you download ,the "ERP-SI Functionality Response.xls" Excel Spreadsheet from htto://ci.miami.fl.us/procurergegt/ERP/ERP-SI Functionality Resoonse,xls. Appendix "A' 64 City of Miami, Florida RFP No. 03-04-151 Functional Requirements Evaluation Instructions Please complete the following columns as indicated: Oracle Module: Indicate the specific Oracle Module that will address this functionality. If no Oracle Module enter N/A and complete either the 3rd Party Software column, or enter Y in the Customization column. In Scope: If this functionality is within the scope of your proposal, please indicate by entering Y, otherwise enter N. Optional Service: If this functionality is not within the scope of your proposal, but is being offered as an optional service, please indicate Y, otherwise indicate N. Note that if this is marked as Y, the optional service section of the Cost Proposal must have been completed. 3rd Party Solution: If a 3rd Party Software solution will be utilized to meet this requirement, please indicate the software to be utilized as originally noted in your proposal. Customization: If a customization is required to fulfill this requirement, please indicate with a Y, otherwise enter N. Please provide a separate summary of all customizations noted and provide an estimated cost to complete the customization(s). A customization is defined as a systematic change to the underlying source code of the application which may adversely impact a software upgrade. Other modifications that utilize ERP provided toolkits, and that still provide a viable upgrade path (i.e. Custom Workflows) are not considered a customization, but should be clearly identified with a comment. Appendix "A" 65