Sourced open data and public reuse context
Source records, publishing, and corrections: Workday HCM
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Translate the operating context into supervisory organizations, staffing models, business processes, and eligibility rules. Ask the consultant to explain the downstream effect of each design choice. 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 worker-event scenario and ask for organization, process, rule, 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 HCM
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Set the security and integration boundary. Require evidence from domain and business-process security, inbound or outbound interfaces, payroll vendors, benefits providers, or identity systems. 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 security or integration defect with the affected population, diagnosis, correction, and regression test. 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 HCM
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Define conversion and testing ownership. Candidates should cover worker data, organizations, compensation, benefits, calculated fields, reports, exceptions, and business 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 conversion cycle the consultant owned, including mapping, validation, exception handling, and acceptance. Define the identity authority, protected records, geographic layers, access groups, public boundary, retained logs, incident route, and review required after a system change.