Sourced financial services and insurance context
Accounts, policies, and financial controls: SAP Basis
A September 2025 City of Des Moines official statement lists financial-services and insurance organizations among the metropolitan area's larger employers. 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. Financial and insurance systems can connect accounts, policies, premiums, claims, payments, identity, risk rules, approvals, reconciliations, statements, reporting, and audit evidence.
Evidence to request: Review a landscape diagram and ask for sizing, isolation, identity, network, availability, and recovery decisions. Name the account, product, policy, transaction, or claim, source ledger, money movement, identity model, control owner, reconciliation, close or reporting date, and support obligation.
Sourced health care and education context
Protected care and learning records: SAP Basis
The same Des Moines document lists hospitals, clinics, a health-benefits firm, and public education among the metropolitan area's larger employers. Define ownership for kernels, support packages, upgrades, transports, certificates, interfaces, and database maintenance. Require evidence from a controlled production change. Health and education environments may join patient or student records, appointments, benefits, billing, learning systems, workforce data, access controls, retention, and reporting.
Evidence to request: Use an upgrade or transport scenario with prerequisites, testing, downtime, communication, fallback, and evidence capture. Set the care, benefits, teaching, or administrative workflow, authoritative record, protected data class, access reviewer, integration, reporting rule, retention requirement, and acceptance owner.
Sourced distribution and agricultural manufacturing context
Equipment, seed, freight, and inventory flow: SAP Basis
Des Moines' 2025 employer table also includes distribution and data-center work, farm equipment, seed manufacturing, package shipping, agricultural tires, and other manufacturing. Set the incident and continuity boundary. Candidates should cover alerting, work processes, dumps, locks, jobs, capacity, backups, failover, vendor escalation, and post-incident checks. These operations can cross product engineering, seeds or materials, production, quality, equipment, warehouses, carriers, inventory, status events, delivery, and financial settlement.
Evidence to request: Ask for a production incident the engineer diagnosed, including signals, commands, recovery, business communication, and preventive work. Choose the product or shipment, then trace its source specification, production or receipt, quality gate, serial or lot, inventory event, carrier handoff, delivery exception, settlement, and owner.