Sourced open data and public reuse context
Source records, publishing, and corrections: Workday Financials
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Connect the business setting to company, cost center, worktag, ledger, and business-process design. Ask how each choice affects accounting, security, reporting, and operating teams. 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 an accounting-design scenario and require worktag, process, control, security, and reporting 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: Workday Financials
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Define integrations for banking, procurement, payroll, expenses, tax, or external reporting. Require evidence from error handling, balancing, monitoring, and support handoff. 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 finance interface failure with balancing evidence, correction, replay, and communication to the process owner. 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: Workday Financials
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Set conversion and close criteria. Candidates should explain opening balances, suppliers, customers, assets, transactions, reconciliations, period close, and issue sign-off. 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 a mock close or conversion reconciliation owned by the consultant, including exceptions and approval. Define the identity authority, protected records, geographic layers, access groups, public boundary, retained logs, incident route, and review required after a system change.