RFI No. CAO127-CAO4-6490 - New Budgeting System.pdf

Rev. 3/2026- Services

Request for Information No. CAO127-CAO4-6490

New Budget System

San Bernardino County Purchasing Department

777 E. Rialto Ave.

San Bernardino, CA 92415

August 2026

Request for Information No.

CAO127-CAO4-6490

Budget System Software and Implementation Services

I. INTRODUCTION

A. Purpose

San Bernardino County (County) is seeking information from qualified firms regarding commercially available software and related services for an enterprise budgeting system. The County is interested in solutions that can support a complex, decentralized public-sector budgeting environment, and improve budget development, forecasting, analysis, reporting, collaboration, transparency, and decision-making.

The County is conducting market research to better understand available approaches, capabilities, implementation considerations, and pricing structures before determining future requirements and next steps.

This Request for Information (RFI) is intended to solicit information (RFI Response) from prospective vendors about their capabilities to provide an enterprise budgeting system. The solicitation is issued solely for informational and planning purposes and does not create an obligation to purchase any product or service or proceed with a future acquisition.

A Request for Proposals (RFP) may be issued at a later date to obtain proposals and establish a contract for the implementation of a new enterprise budgeting system for the County. Vendors who wish to submit an RFI Response or participate in a future RFP (if issued) should register in the County’s Electronic Procurement Network (ePro).

B. RFI Contact All correspondence, including responses and questions, must be submitted to the person identified below (RFI Contact):

San Bernardino County Purchasing Department Attn: Ariel Gill

(909) 387-2070 Phone Ariel.gill@pur.sbcounty.gov Email

All questions should be submitted through ePro. RFI Responses will not be accepted by email. RFI Responses must be submitted electronically through ePro. All vendors must register with the ePro system prior to the date and time to submit the information.

C. Assistance To Respondents With A Disability Vendors with a disability may request accommodation regarding the means of communicating this RFI or participating in the RFI process. For more information, contact the RFI Contact no later than ten (10) days prior to the Deadline to Submit RFI Response.

II. RFI TIMELINE

Release of RFI August 21, 2026 Deadline for Submission of Questions September 4, 2026 5:00 PM PST Deadline to Submit RFI Response September 11, 2026 5:00PM PST Demonstration Week September 21-25, 2026

Request for Information No.

CAO127-CAO4-6490

Questions regarding the contents of this RFI must be submitted in writing on or before the Deadline for Submission of Questions through ePro. All questions will be answered and posted as an Addendum to the RFI in ePro.

To be considered, all RFI Responses must be submitted in the manner set forth in this RFI and it is the Vendor’s responsibility to ensure that its response arrives on or before the Deadline to Submit RFI Response.

III. SOLICITATION CONDITIONS

A. Incurred Costs The County is not obligated to pay any costs incurred by Vendor in the preparation of information in response to this RFI. Vendors agree that all costs incurred in developing information are the Vendor’s responsibility.

B. Amendments/Addendums to RFI The County reserves the right to issue amendments or addendums to this RFI if the County considers that changes are necessary or additional information is needed.

C. Public Records Act All information and other material submitted become the property of the County and are subject to release according to the California Public Records Act (Government Code § 7920.000). All information, including cost information, is subject to becoming a non-exempt public record.

If a Vendor believes that any portion of its information is exempt from public disclosure, it must indicate the specific portions believed to be confidential and not subject to disclosure on Attachment A - Public Records Act Exemptions. The Vendor also must include a brief description that sets out the reasons for exemption from disclosure. Each stated exemption must include a citation to supporting legal authority, including statutory authority or case law, to support exemption from the Public Records Act. Requested exemptions that do not meet the requirements of this section will not be considered.

The County will use reasonable means to ensure that such information is safeguarded, but will not be held liable for inadvertent disclosure of the information. Information marked “Confidential” in their entirety will not be honored, and the County might not deny public disclosure of any portion of information so marked.

By submitting information with portions identified in Attachment A as “Confidential,” Vendor represents that it has a good faith belief that such portions are exempt from disclosure under the California Public Records Act. Vendor may be requested to obtain legal protection from disclosure should a Public Records Act request be received. In the event the County does not disclose the information marked “Confidential,” Vendor agrees to reimburse the County for, and to indemnify, defend (with counsel approved by County) and hold harmless the County, its officers, employees, agents, and volunteers from and against any and all claims, damages, losses, liabilities, suits, judgments, fines, penalties, costs and expenses, including without limitation, attorneys’ fees, expenses and court costs of any nature arising from or relating to the County’s non-disclosure of any such designated portions in information.

D. Material Misstatement/Misrepresentation If during the course of the administration of this RFI process, the County determines that Vendor has made a material misstatement or misrepresentation or that materially inaccurate information has been provided to the County, Vendor may be immediately terminated from the RFI process or any future RFP process, if any, which may result from this RFI process.

Request for Information No.

CAO127-CAO4-6490

E. Contingencies

This RFI does not commit the County to prepare and disseminate a RFP.

IV. SCOPE

A. Background Information

The County is evaluating options for an enterprise budgeting system that can support annual budget development and ongoing financial planning across a large organization with varied departments, funds, programs, organizational structures, and levels of user experience.

Including functionality for 50+ departments, 300+ users, 25,000+ budgeted positions, interfacing with SAP S4/Hana and Oracle Fusion Human Capital Management (HCM). The County is interested in understanding how current market solutions can improve the efficiency, consistency, visibility, and analytical value of the budget process.

Areas of interest include budget data entry, formulation, multi-year forecasting, what-if analysis, assumption management, detailed personnel cost budgeting, decision requests, workflow and approvals, version control, reporting and dashboards, budget book production, capital planning, cash forecasting, artificial intelligence (AI), system capacity and performance, user experience, administration, security, implementation, support, and pricing.

The County is also interested in capabilities and approaches that may not be identified in this RFI. Respondents are encouraged to describe additional functionality, emerging practices, or implementation strategies that have improved budgeting processes for comparable public-sector organizations.

B. Response Guidance

Please respond to the following:

1. For each capability discussed, identify whether it is standard functionality, configurable by customer administrators, requires custom development, depends on a third-party product, is planned for a future release, or is not available.

2. Clearly distinguish functionality that is generally available in production from functionality that is beta, preview, limited availability, or planned.

3. Identify any separate modules, licenses, services, or additional costs required for the capability.

4. Where relevant, provide examples from comparable public-sector implementations and identify any important limitations, prerequisites, or implementation considerations.

5. Identify capabilities or approaches not specifically requested in this RFI that you believe the County should consider when evaluating a modern enterprise budgeting system.

C. Company Overview & Public-Sector Budgeting Experience

Please provide information on the following topics:

1. Provide a brief overview of your company, including years in business, ownership structure, headquarters location, and number of employees.

Request for Information No.

CAO127-CAO4-6490

2. Describe your primary products and services as they relate to enterprise budgeting, planning, forecasting, reporting, and financial analysis.

3. Describe your experience serving counties, cities, state agencies, special districts, and other public-sector organizations.

4. Provide examples of customers comparable in organizational complexity, decentralized budgeting structure (50+ departments), and number of users (300+) to the County.

5. Describe functionality, implementation methods, or support practices specifically developed for public-sector budgeting environments.

6. Describe lessons learned from comparable implementations, including common challenges, adoption risks, and factors that contribute to a successful implementation.

7. Describe your product roadmap and long-term investment strategy for enterprise budgeting and financial planning technology.

D. System Architecture, Capacity, Scalability & Performance

1. Describe the solution architecture, hosting model, tenancy model, and supported deployment options.

2. Describe how the solution scales for a large, decentralized organization with many departments, funds, programs, users, budget versions, reporting dimensions, and concurrent planning activities.

3. Provide representative scale information from large production customers, such as named users, peak concurrent users, data volumes, planning models, dimensions, and annual processing volumes.

4. Identify practical, technical, or licensed limits on users, concurrent sessions, dimensions, hierarchy depth, data storage, versions, scenarios, attachments, reports, workflow tasks, or planning intersections.

5. Describe expected response times for common activities such as opening input forms, saving changes, running calculations, refreshing dashboards, loading and refreshing data, producing reports, and executing forecasts.

6. Provide available performance benchmarks or stress-test results relevant to a large public-sector budgeting environment and explain the assumptions behind the results.

7. Describe how the platform manages peak demand during department submission deadlines, central review periods, executive review, and other high-volume events.

8. Describe batch processing, calculation scheduling, job monitoring, error handling, restart, and recovery capabilities.

9. Describe system availability commitments, planned maintenance practices, performance monitoring, and customer visibility into service health.

E. User Interface, Accessibility & User Experience

1. Describe the primary user experience for various levels of the organization, including central budget staff, department budget staff, executives, approvers, analysts, and occasional users.

Request for Information No.

CAO127-CAO4-6490

2. Describe role-based home pages, task lists, notifications, search, navigation, drill-down, drill-through, and contextual help capabilities.

3. Describe how the solution supports users who enter or review budget information only periodically and may have limited system training.

4. Describe the extent to which forms, layouts, dashboards, menus, prompts, and task flows can be configured by County administrators without Vendor assistance.

5. Describe spreadsheet connectivity, including refresh, write-back, formula support, governed templates, and controls intended to prevent version inconsistency.

6. Describe mobile or responsive capabilities and identify which functions are supported on mobile devices.

7. Describe accessibility conformance, including support for Web Content Accessibility Guidelines (WCAG), Americans with Disabilities Act (ADA), and Section 508 of the Rehabilitation Act requirements.

8. Describe personalization options and controls for maintaining a consistent enterprise experience.

F. Budget Formulation & Annual Planning

1. Describe the annual budget process supported by the solution from cycle setup through department entry, review, revision, executive consideration, adoption, and finalization.

2. Describe how a new budget cycle can be initialized using historical actuals, current budget, current estimates, prior-year requests, targets, or other baseline information.

3. Describe support for revenue and expenditure budgeting across configurable organizational and financial dimensions.

4. Describe support for base budgets, target budgets, reductions, enhancements, supplemental requests, one-time items, ongoing items, and other configurable request types.

5. Describe how users can create and manage assumptions such as inflation, growth rates, internal rates, vacancy assumptions, cost escalation, and other budget drivers.

6. Describe monthly or periodic spreading, current estimates, year-end estimates, seasonal patterns, and manual or rules-based adjustments to distribution patterns.

7. Describe support for fund balance, reserves, transfers, internal charges, balancing requirements, validation rules, and exception handling.

8. Describe the ability to establish targets or constraints by department, fund, program, account, or other dimension and monitor compliance during budget development.

9. Describe post-adoption budget amendment, revision, and reforecasting capabilities, including approvals, version control, and audit history.

10. Describe how the solution supports multiple budget calendars, simultaneous planning cycles, and different planning methods for different areas of the organization.

G. Multi-Year Forecasting, What-If Analysis & Assumption Modeling

1. Describe multi-year planning capabilities, including supported forecast horizons and the ability to maintain different horizons by planning process.

Request for Information No.

CAO127-CAO4-6490

2. Describe how users can create, copy, compare, branch, merge, freeze, and archive scenarios, forecasts, and reports.

3. Describe how changes to assumptions such as inflation, revenues, service levels, staffing, program changes, or cost drivers can be modeled and reflected across future years.

4. Describe account-level, trend-based, driver-based, and rules-based forecasting approaches and how different methods can be applied within the same plan.

5. Describe predictive forecasting capabilities that use historical data. Explain minimum data requirements, treatment of seasonality, confidence ranges, model selection, and user overrides.

6. Describe sensitivity analysis and the ability to identify which assumptions have the greatest effect on projected results.

7. Describe how forecast accuracy and variance can be measured over time and how forecasting methods can be refined.

8. Describe governance and audit capabilities for assumptions, formulas, overrides, and forecast methodologies.

H. Personnel Cost Budgeting

1. Describe capabilities for budgeting filled positions, vacant positions, proposed positions, eliminated positions, temporary positions, and partial-year changes.

2. Describe how the solution models salaries, step changes, negotiated increases, effective-dated changes, overtime, differentials, allowances, and other configurable compensation elements.

3. Describe benefit and related personnel cost calculations, including configurable rates, effective dates, tiers, caps, and other calculation rules.

4. Describe how users can drill into a personnel cost total and review the assumptions, formulas, and components that produced the result.

5. Describe support for vacancy factors, turnover, attrition, hiring dates, position changes, and scenario-based staffing assumptions.

6. Describe allocation of position costs across multiple funds, departments, programs, grants, projects, or other dimensions, including changes over time.

7. Describe controls for protecting sensitive detail while still allowing authorized users to budget and analyze personnel costs.

8. Describe reconciliation and exception-reporting capabilities for personnel cost budgets.

I. Workflow, Collaboration, Version Control & Auditability

Please respond to the following:

1. Describe configurable workflow and approval capabilities for department preparation, central review, management review, executive review, and other approval stages.

2. Describe task lists, due dates, reminders, escalations, notifications, assignments, comments, notes, and attachments.

3. Describe version and scenario management, including working versions, baselines, snapshots, approved versions, locks, and side-by-side comparisons.

Request for Information No.

CAO127-CAO4-6490

4. Describe the ability to identify who changed data, what changed, when it changed, and the reason for a change.

5. Describe restoration, rollback, and recovery options when changes need to be reversed.

6. Describe how late-cycle changes flow through calculations, dashboards, reports, narratives, and other affected outputs.

7. Describe concurrent editing controls and how the system prevents users from unintentionally overwriting one another.

8. Describe delegation and temporary reassignment of tasks when staff are absent.

J. Reporting, Analytics & Dashboards

1. Describe standard budget, forecast, variance, trend, and management reports included with the solution.

2. Describe ad-hoc reporting capabilities for business users and identify the level of technical knowledge required.

3. Describe dashboards, charts, key performance indicators, alerts, drill-down, drill-through, and interactive analysis capabilities.

4. Describe support for different points of view by department, fund, program, account, period, scenario, version, and other dimensions.

5. Describe year-end estimate reporting and comparison of adopted budget, revised budget, actuals, forecast, and proposed budget.

6. Describe export capabilities and supported output formats, including accessible formats.

7. Describe data lineage and the ability for users to trace a reported amount to its source, calculation, assumption, adjustment, or supporting detail.

8. Describe self-service capabilities for creating new reports and dashboards without vendor involvement.

K. Budget Book & Narrative Reporting

Please respond to the following:

1. Describe capabilities for combining narrative, financial tables, charts, images, and other content into a coordinated budget publication as well as how outputs do or do not meet ADA compliance in accordance with WCAG 2.1 Level AA standards.

2. Describe how values, tables, and charts can be linked to source data and refreshed when underlying data changes.

3. Describe authoring options, including browser-based editing and integration with common document-authoring tools where available.

4. Describe section ownership, review cycles, comments, workflow, approvals, sign-off, and change history for narrative content.

5. Describe support for reusable templates, standardized styles, cross-references, tables of contents, page numbering, and publication consistency.

6. Describe production of print-quality and accessible digital outputs and explain how large publications are assembled and refreshed.

7. Describe how the solution handles last-minute changes while minimizing manual updates across repeated tables, charts, and narrative references.

Request for Information No.

CAO127-CAO4-6490

L. Capital Budgeting & Project Planning

1. Describe support for capital requests, project narratives, multi-year project costs, project schedules, and funding plans.

2. Describe configurable project scoring, prioritization, ranking, and comparison capabilities.

3. Describe how project funding sources can be assigned, constrained, changed, and displayed over multiple years.

4. Describe support for project phases, carryforward, reappropriation, commitments, and changes to project estimates.

5. Describe dashboards and visual analysis for comparing projects, costs, funding, timing, and priority.

6. Describe workflow and approval capabilities for capital requests and changes.

M. Data Management & Interoperability

1. Describe methods for importing, exporting, synchronizing, and validating data from existing

County systems and data sources, include Enterprise Resource Planning (ERPs) such as SAP S/4HANA and Oracle Fusion HCM.

2. Describe available interfaces and integration methods, including application programming interfaces, flat files, secure file transfer, middleware, event-based methods, and other supported approaches.

3. Describe scheduled and on-demand data refresh capabilities, including incremental loads, full loads, validation, reconciliation, error queues, and restart procedures.

4. Describe metadata and hierarchy management, including effective dates, reorganizations, mappings, alternate hierarchies, and change approval.

5. Describe data quality rules, duplicate detection, missing-data checks, outlier checks, balancing, and exception workflows.

6. Describe master-data governance capabilities and explain how changes are propagated across planning models, reports, and security.

7. Describe the County's ability to extract all County-owned data, metadata, audit history, documents, and configuration information in usable formats.

8. Describe data archival and retention capabilities, including access to historical budget versions and prior planning cycles, specifically including fixed asset and salaries and benefits details.

9. Describe tools available to monitor interfaces, troubleshoot failures, reconcile results, and provide operational visibility to County administrators.

N. Artificial Intelligence & Advanced Analytics

1. Describe AI-enabled functionality currently available in production that is relevant to budgeting, forecasting, analysis, reporting, or administrative work.

Request for Information No.

CAO127-CAO4-6490

2. Describe natural-language capabilities for querying budget data, generating explanations, identifying trends, or navigating the system.

3. Describe AI-assisted variance analysis, anomaly identification, forecast insight, narrative drafting, document review, summarization, and other supported use cases.

4. For generative AI features, describe how responses are grounded in authorized data and how source references, evidence, or traceability are presented to users.

5. Describe human-review controls, approval steps, audit logging, and methods for correcting or challenging AI-generated output.

6. Describe how role-based access and data security are enforced when AI features are used.

7. Describe what data is used to train shared models and identify customer controls over model training, retention, prompts, outputs, and third-party model providers.

8. Describe model monitoring, testing, bias or quality evaluation, hallucination mitigation, and incident handling.

9. Describe AI usage limits, consumption metrics, separate licensing, and cost controls.

10. Describe your AI roadmap for the next 24 months and clearly distinguish committed items from aspirational items.

11. Describe AI features and controls, including AI processing region (internal or third party), permission trimmed responses, model selection, prompt and output retention and logs, and agentic actions (if AI can make changes to data and any guardrails which may apply).

O. Performance Measures & Outcome-Oriented Budgeting

1. Describe capabilities for maintaining performance measures, targets, service levels, workload indicators, and outcome measures alongside financial budgets.

2. Describe how performance measures can be connected to departments, programs, budget requests, initiatives, or funding decisions.

3. Describe support for target setting, historical trends, commentary, variance explanations, and status indicators.

4. Describe dashboards and reports that combine financial information with performance or outcome information.

5. Describe controls for measure definitions, ownership, certification, and audit history.

P. Administration, Configuration & Release Management

1. Describe administrative tools available for managing users, roles, security, dimensions, hierarchies, forms, assumptions, calculations, workflows, reports, dashboards, approval stages during a cycle, and planning cycles.

2. Identify which administrative activities can be performed directly by County staff and which typically require vendor or consulting support.

3. Describe configuration promotion between development, test, training, and production environments.

4. Describe sandbox, preview, or test capabilities for evaluating changes before production deployment.

5. Describe audit history for administrative and configuration changes.

Request for Information No.

CAO127-CAO4-6490

6. Describe release cadence, notice periods, customer controls, regression testing support, feature enablement, and handling of breaking changes.

7. Describe tools for bulk administration of users, security, metadata, forms, and configuration.

8. Describe documentation, diagnostics, logs, and monitoring available to County administrators.

Q. Security, Privacy, Accessibility & Business Continuity

1. Describe the solution's security architecture and major technical and administrative controls.

2. Provide information regarding current independent certifications, attestations, and security assessments relevant to the service.

3. Describe encryption standards for data in transit and at rest, and key-management practices.

4. Describe identity and access capabilities, including single sign-on, multi-factor authentication, automated provisioning, and enterprise identity integration.

5. Describe role-based access, dimensional security, privileged access controls, segregation of duties, and audit logging.

6. Describe backup, disaster recovery, and business continuity capabilities, including recovery time objective, recovery point objective, redundancy, and testing cadence.

7. Describe incident response, vulnerability management, penetration testing, breach notification, and customer communication practices.

8. Describe data retention, deletion, legal hold, data residency, subcontractor, and customer data ownership practices.

9. Describe accessibility compliance and the availability of current accessibility conformance documentation.

R. Implementation, Data Conversion & Transition Approach

Please respond to the following:

1. Describe your typical implementation methodology and governance approach for a large public-sector budgeting system.

2. Provide a representative implementation timeline covering discovery, design, configuration, data conversion, testing, training, parallel operation, cutover, stabilization, and post-go-live support.

3. Describe phased, modular, and enterprise-wide deployment options and the advantages and risks of each approach.

4. Describe County staffing and resource requirements by implementation phase, including expected participation from central budget staff, department users, technical staff, security staff, and executive sponsors.

5. Describe data conversion capabilities for historical actuals, budgets, forecasts, organizational structures, budget versions, reports, documents, and audit information.

6. Describe support for parallel operation with an existing budget system and reconciliation between systems.

7. Describe testing methodologies, including functional, integration, performance, security, user acceptance, regression, and cutover testing.

Request for Information No.

CAO127-CAO4-6490

8. Describe organizational change management, communications, training, adoption, and stakeholder engagement services.

9. Describe knowledge transfer, configuration documentation, and practices intended to make County staff self-sufficient after implementation.

10. Identify key implementation risks from comparable projects and explain how you would mitigate them.

S. Training, Support & Service Levels

1. Describe training provided to system administrators, central budget staff, department users, approvers, executives, report developers, and technical staff.

2. Describe available delivery methods, training environments, documentation, embedded help, knowledge bases, and ongoing learning resources.

3. Describe post-implementation support services, support hours, escalation paths, severity definitions, and target response and resolution times.

4. Describe customer success, account management, periodic health checks, and upgrade planning services.

5. Describe premium support, managed services, or staff-augmentation options where available.

6. Provide typical service-level commitments for availability, support response, critical incidents, and performance.

T. Pricing Structure

Please provide approximate budgetary information sufficient for market research and planning.

Identify assumptions and exclusions.

1. Describe your pricing model and primary pricing metric, such as named users, concurrent users, modules, organizational size, data volume, and/or other measures.

2. Identify estimated one-time implementation costs and the major factors that cause those costs to increase or decrease.

3. Identify estimated annual subscription, licensing, hosting, maintenance and support costs, and/or any other ongoing costs.

4. Identify optional modules, add-ons, premium features, or third-party products and their approximate costs.

5. Identify costs associated with interfaces, data conversion, additional environments, storage, retention, training, premium support, and professional services.

6. Identify separate AI licensing, consumption, model, agent, or usage costs and available cost controls.

7. Describe typical annual price escalation and any minimum term or usage commitments.

8. Identify anticipated future costs that should be considered over a 10-year total-cost-of-ownership period.

9. Provide an illustrative price range for an organization of comparable size and complexity, with assumptions clearly stated.

Request for Information No.

CAO127-CAO4-6490

U. Demonstration Guide & Business Scenarios The County may invite respondents to demonstrate current production functionality.

Demonstrations should use realistic public-sector budgeting examples and should clearly identify any functionality that is custom, third-party, preview, or planned. Respondents should be prepared to demonstrate the following scenarios and explain where alternative approaches may provide greater value:

1. Annual budget cycle: Create a new budget cycle from prior information, establish assumptions and targets, distribute work to departments, enter and validate requests, route submissions for review, address exceptions, and finalize an approved version.

2. Department reduction and enhancement exercise: Provide a department with a required reduction target while allowing separate enhancement requests. Show how the system validates the target, captures justification, compares alternatives, and routes the package for review.

3. Five-year what-if scenario: Create a five-year forecast, change multiple assumptions such as inflation, revenue growth, service levels, staffing, or cost escalation, and compare the financial impact across scenarios.

4. Historical forecasting and forecast accuracy: Use historical information to create a forecast, show the selected method and confidence information, allow a user override, and later compare the forecast with actual results to assess accuracy.

5. Personnel cost budgeting: Model filled and vacant positions, an effective-dated cost change, a vacancy assumption, a new proposed position, and allocation of one position across multiple funding dimensions; then drill into the calculation. Demonstrate time for calculations for 25,000+ positions.

6. Late-cycle executive change: Make a material last-minute change after department review, show who changed it and why, compare the new version with a prior snapshot, refresh affected calculations, and identify every report or narrative output changed by the update.

7. Monthly and year-end reporting: Produce a budget-to-actual report, year-end estimate, multi-year trend, dashboard, and batch report for different user roles, with drill-through capability to supporting detail and clear data lineage.

8. Budget book refresh: Create a publication section containing narrative, financial tables, and charts; route it for review; change an underlying budget amount; refresh linked content;

show the change history; and produce an accessible final output.

9. Capital request prioritization: Create several project requests with multi-year costs, funding plans, narratives, and scoring criteria; rank them; change available funding; and show how priorities and visual comparisons update.

10. Cash forecast exception: Generate a periodic cash forecast, identify a projected low-cash period, change an assumption, compare scenarios, and show alerts or other decision-support features.

11. Data-quality failure and recovery: Load a file or data set containing missing, invalid, duplicated, or out-of-balance information. Show validation, exception handling, correction, reconciliation, restart, and audit history.

12. Peak-period system performance: Explain and, where practical, demonstrate how the platform performs when many users are entering, saving, calculating, approving, and reporting at the same time. Provide realistic scale assumptions and monitoring information.

Request for Information No.

CAO127-CAO4-6490

13. Occasional-user experience: Have an infrequent department user sign in, identify assigned tasks, enter a request, attach support, respond to an error, submit for review, and determine status without administrator assistance.

14. AI-assisted budget analysis: Use AI for a budget-related task such as variance explanation, anomaly identification, forecast insight, document review, or narrative assistance. Show source grounding, permissions, human review, auditability, and how incorrect output is corrected.

15. Administrator self-service: Using customer administrator tools, add or change a form, workflow step, hierarchy item, assumption, security rule, dashboard, or report and explain when vendor assistance would be required.

16. Post-adoption amendment: Process a budget amendment after adoption, route it for approval, preserve the adopted baseline, update the revised budget, and report adopted versus revised budget with a complete audit trail.

17. System exit and data portability: Explain and demonstrate how the County could export its data, metadata, historical versions, documents, and audit information in usable formats if the County later transitions to another system. Show live or documented interface to SAP S/4HANA and to Oracle Fusion HCM, identifying method (API vs file), direction, trigger (real-time vs batch), and reconciliation.

If your organization is interested in providing a demonstration, please reach out to the RFI Contact listed above.

V. RFI RESPONSE SUBMISSION

A. General

1. All interested and qualified Vendors are invited to submit information for consideration.

2. RFI Responses must be received by the designated date and time. All vendors must register with the ePro system prior to the date and time to submit the RFI Response.

Electronic response must be submitted through the San Bernardino County Electronic Procurement Network (ePro) https://epro.sbcounty.gov/epro/.

B. RFI Response Format

1. Presentation

Format the RFI Information to fit on an 8-½ x 11 sheet of paper with margins of at least ¾ inches. Text should be single spaced and font size should be no smaller than 11 point.

Each page, including attachments, must be clearly and consecutively numbered.

2. Cover Letter

3. Table of Contents

All pages of the RFI Information must be clearly and consecutively numbered and correspond to the Table of Contents.

4. System Information and Description

The RFI Response should include the following:

Request for Information No.

CAO127-CAO4-6490

a. A brief synopsis of the Vendor’s understanding of the County’s needs and how the Vendor plans to meet them.

b. A detailed statement of the proposed business enterprise budgeting solution.

c. Response to the information requested in Section IV, Scope.

d. An explanation of any assumptions or constraints.

5. Cost

Provide any available pricing information or a pricing range.

6. Public Records Act Exemptions

Complete Attachment A – Public Records Act Exemptions, if applicable.

Request for Information No.

CAO127-CAO4-6490

ATTACHMENT A – PUBLIC RECORDS ACT EXEMPTIONS

VENDOR NAME

ADDRESS

TELEPHONE# ( ) FAX # ( )

Vendor requests that specific portions of the contents of this RFI Information be held confidential and not subject to public disclosure pursuant to the Public Records Act. The specific portions are detailed below: (Please identify and list your exemptions by indicating the Section or Paragraph number, and Page number, of the RFI Information where the content is contained.) Each stated exemption must include a citation to supporting legal authority, including statutory authority or case law, to support exemption from the Public Records Act. Requested exemptions that does not meet the requirements of this section will not be considered.

ATTACHMENT A – PUBLIC RECORDS ACT EXEMPTIONS