Sourced open data and public reuse context
Source records, publishing, and corrections: Workday SCM
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Convert the operating setting into companies, cost centers, worktags, procurement rules, supplier controls, inventory locations, and approval chains. Ask how each choice reaches financial 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 requisition-to-payment scenario and require organization, supplier, item, approval, receipt, accounting, 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 SCM
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Define connections to Workday Financials, strategic sourcing, banks, tax, supplier networks, clinical or warehouse tools, and external catalogs. Require evidence from the matching interface pattern. 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 supplier or inventory interface with mapping, identity, error handling, monitoring, replay, and balancing. 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 SCM
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Set conversion, security, testing, cutover, and support ownership. Candidates should explain suppliers, items, balances, open documents, roles, reports, exceptions, and reconciliation. 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 supply-chain conversion or release the consultant owned, including data validation, role testing, open transactions, exceptions, 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.