Sourced open data and public reuse context
Source records, publishing, and corrections: SAP PP
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Translate the operating setting into material masters, planning strategies, lot sizes, bills of material, routings, work centers, and order controls. Ask the consultant to trace one product from demand through confirmation and receipt. 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 demand-to-production exercise and require planning, supply, capacity, order, confirmation, quality, and costing 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: SAP PP
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Set boundaries among PP, Materials Management, Sales, Quality Management, plant maintenance, costing, warehouse tools, and manufacturing systems. Require a comparable integration example with recovery steps. 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 shop-floor or planning interface with mapping, timing, failure handling, replay, and production reconciliation. 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: SAP PP
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Define data, testing, cutover, and plant-support ownership. Candidates should cover materials, recipes or routings, resources, inventory, open orders, planning runs, interfaces, and operational 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 plant cutover or planning recovery the consultant owned, including stock, open orders, jobs, exceptions, and fallback. Define the identity authority, protected records, geographic layers, access groups, public boundary, retained logs, incident route, and review required after a system change.