Sourced open data and public reuse context
Source records, publishing, and corrections: Oracle EBS
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Translate the operating setting into operating units, ledgers, inventory organizations, responsibilities, workflows, and module setup. Ask the consultant to explain how the design affects transactions and accounting. A public-data service needs named owners for source records, publication rules, refresh timing, metadata, legal review, corrections, and downstream applications that the publishing team does not control.
Evidence to request: Use a cross-module process case and require organization, configuration, responsibility, workflow, interface, and accounting decisions. Identify each source system, dataset owner, publication test, refresh schedule, restricted field, correction route, consumer, and support handoff connected to the role.
Sourced enterprise applications and infrastructure context
Shared services across departments: Oracle EBS
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Define ownership for interfaces, conversions, reports, extensions, workflows, APIs, and database objects. Require evidence from a comparable custom object with support and upgrade consequences. A shared service may support departments with separate case records, approvals, retention rules, operating hours, budgets, and legacy systems while one central team owns infrastructure and support.
Evidence to request: Review a RICE object or production defect with code or setup, logs, data impact, correction, testing, and deployment control. Name the departments, user groups, service owner, application and hosting boundary, approval path, maintenance window, legacy connections, and acceptance evidence.
Sourced cybersecurity and geographic data context
Identity, location, and disclosure boundaries: Oracle EBS
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Set patching, testing, cutover, incident, and migration duties. Candidates should cover dependencies, clones, concurrent jobs, open transactions, reconciliations, fallback, and transfer to support. Constituent and location records can cross identity, field access, map layers, integrations, operational use, audit logs, and public-disclosure rules that require separate review owners.
Evidence to request: Ask for an EBS upgrade, patch, or migration cycle the consultant owned, including prerequisites, downtime, validation, exceptions, and recovery. Define the identity authority, protected records, geographic layers, access groups, public boundary, retained logs, incident route, and review required after a system change.