Sourced open data and public reuse context
Source records, publishing, and corrections: Dynamics 365 Business Central
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Translate the business setting into companies, dimensions, posting groups, workflows, and operational records. Ask the consultant to show the accounting result of each 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 transaction scenario and require company, dimension, posting, approval, inventory, 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: Dynamics 365 Business Central
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Set the extension and integration strategy. Require evidence from APIs, events, AL extensions, upgrades, monitoring, and the boundary with Power Platform or external products. 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 an extension or integration with upgrade safety, failure handling, authentication, monitoring, and operational support. 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: Dynamics 365 Business Central
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Define migration, testing, cutover, and support ownership. Candidates should explain opening balances, master data, open transactions, permissions, jobs, 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 cutover cycle the consultant owned, including migration order, reconciliation, permissions, exceptions, and sign-off. Define the identity authority, protected records, geographic layers, access groups, public boundary, retained logs, incident route, and review required after a system change.