Sourced open data and public reuse context
Source records, publishing, and corrections: SAP Basis
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Map the operating setting to system sizing, landscape separation, identity, network paths, high availability, and recovery objectives. Ask the engineer to explain the limits that drove the design. 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: Review a landscape diagram and ask for sizing, isolation, identity, network, availability, and recovery 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 Basis
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Define ownership for kernels, support packages, upgrades, transports, certificates, interfaces, and database maintenance. Require evidence from a controlled production change. 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: Use an upgrade or transport scenario with prerequisites, testing, downtime, communication, fallback, and evidence capture. 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 Basis
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Set the incident and continuity boundary. Candidates should cover alerting, work processes, dumps, locks, jobs, capacity, backups, failover, vendor escalation, and post-incident checks. 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 production incident the engineer diagnosed, including signals, commands, recovery, business communication, and preventive work. Define the identity authority, protected records, geographic layers, access groups, public boundary, retained logs, incident route, and review required after a system change.