Sourced aerospace and advanced manufacturing context
Aircraft, precision parts, and production control: SAP Basis
Wichita's target-industry page describes an aerospace network with precision machine shops, tool and die firms, and subcontract manufacturers tied to global aviation supply chains. 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. Aircraft production can join controlled designs, parts, suppliers, machines, work orders, inspections, serial history, nonconformance, maintenance, and release authority.
Evidence to request: Review a landscape diagram and ask for sizing, isolation, identity, network, availability, and recovery decisions. Trace the aircraft part or assembly from approved design and source material through machine or production step, inspection, serial record, discrepancy, delivery, and authorized release.
Sourced health care and medical services context
Clinical workflows and protected records: SAP Basis
The Wichita page identifies health care as a target sector supported by regional medical systems, hospitals, clinics, and medical education. Define ownership for kernels, support packages, upgrades, transports, certificates, interfaces, and database maintenance. Require evidence from a controlled production change. Health systems can connect patient identity, appointments, clinical records, devices, laboratories, benefits, billing, consent, access, and regulated reporting.
Evidence to request: Use an upgrade or transport scenario with prerequisites, testing, downtime, communication, fallback, and evidence capture. Define the care or administrative workflow, patient record, protected data class, device or lab interface, consent and access rule, validation evidence, report, and acceptance owner.
Sourced it systems and support context
Software, cybersecurity, and communications: SAP Basis
Wichita's target-sector page includes IT systems and support across software, technology, cybersecurity, communications, networks, and technical education. Set the incident and continuity boundary. Candidates should cover alerting, work processes, dumps, locks, jobs, capacity, backups, failover, vendor escalation, and post-incident checks. IT roles can sit in product software, enterprise applications, network operations, cyber defence, data platforms, client support, or industrial systems.
Evidence to request: Ask for a production incident the engineer diagnosed, including signals, commands, recovery, business communication, and preventive work. State the product or service, users, infrastructure boundary, data rights, production authority, security control, release evidence, service target, and incident owner.