Enterprise Resource Planning and Implementation System

The Vendor is required to provide enterprise resource planning system and implementation services for include:
- Finance and payroll
•    State fund accounting: general ledger must support multi-fund, multi-year accounting, automated inter-fund entries, and encumbrance accounting. 
•    Budgeting: budget development and budgetary control; position control budgeting (integrating HR and finance) and grant-based budgeting. 
•    Payroll: must handle complex retroactive pay calculations, 10-month vs. 12-month pay spreading, and multi-role employees. 
•    Purchasing: requisition workflows, approval hierarchies, and bid management. 
•    State reporting: automated generation of the state st-3 (annual financial report) and ESSA transparency reporting. 
•    Accounts payable 
•    Accounts receivable 
•    Contract and vendor management 
•    Grants management (federal, state, and local) 
•    Fixed assets 
•    Inventory (where applicable) 
•    Financial reporting, including state -required schedules (see next section)
- Human capital management (HCM)
•    Core HR and employee master records: "hire to retire" lifecycle including specific tracking of state civil service titles, statuses (provisional vs. permanent), and exam lists.
•    Time and attendance: rules-based accruals for sick and vacation banks
•    Benefits administration: open enrollment, carrier reporting, and retiree benefits.
•    Position control
•    Leave management
•    Collective bargaining and labor rule configuration
•    State retirement reporting support
•    Staff certification and compliance tracking
- System-wide requirements
•    Strong role-based security
•    Comprehensive audit trails
•    Reporting and ad-hoc query tools usable by district staff
•    Configurability without heavy customization
•    Support for public-sector accounting and labor structures
- Technical and hosting requirements
•    Acceptable models:
o    SaaS: web-native software hosted in the public cloud.
o    Hosted and managed: software hosted in the vendor’s private cloud or third-party data center, managed fully by the vendor.
•    Maintenance: the vendor must be responsible for all server patching, backups, security updates, and database maintenance.
- User access and mobility
•    General staff (self-service): functions such as viewing pay stubs, requesting time off, or approving requisitions must be accessible via a standard web browser (chrome and edge) or mobile app without requiring VPNs or client installations. 
•    Core administrative users: for "power users", the district accepts the use of secure remote access technologies or installed clients, provided they are secure and performant.
- Implementation strategy
•    Implementation methodology and governance
•    Data migration strategy from oracle fusion cloud
•    Testing and validation approach
•    User training and knowledge transfer
•    Go-live and stabilization support
•    Ongoing support and maintenance model
•    Upgrade planning and management, including training on changes
•    Recommended implementation timing (when to start discovery, when to go live) and timeline (from start date to target stabilization date).