Hiring brief scenarios
Build the SAP FICO brief around the work.
These scenarios connect location context to role responsibilities. Use them as prompts to verify with the employer, not as measures of Baltimore demand, clients, or candidate supply.
Sourced cybersecurity and technology context
Secure services, identity, and technical products: SAP FICO
Baltimore Together tracks technology as a city growth area and calls for stronger connections between employers, students, and Baltimore's software, data, digital-transformation, and information businesses. Translate the local business context into company-code, ledger, currency, cost-center, and profit-center requirements. Ask the consultant to separate legal reporting needs from management reporting choices. Cybersecurity work can cross identity, networks, cloud services, endpoints, protected data, incident response, audit records, and restricted facilities or contracts.
Evidence to request: Use an organization-design case and ask for the configuration objects, finance decisions, and reporting consequences. Define the protected service, threat and compliance boundary, user population, data classification, control owner, alert path, evidence retention, response authority, and recovery test.
Sourced life sciences context
Research, medical products, and health systems: SAP FICO
Baltimore Together's economic-development strategy sets a city objective to lead in life sciences and medical devices. Define the boundary between FICO and upstream or downstream systems. Require evidence from procure-to-pay, order-to-cash, payroll, banking, planning, or data-warehouse integration work that matches the opening. Life-sciences delivery may join experiments, clinical work, medical devices, laboratories, quality systems, protected records, manufacturing, and commercial operations with formal traceability.
Evidence to request: Review an integration defect that crossed module or system boundaries and score the consultant's tracing and ownership. Set the research or product stage, regulated boundary, source records, validation method, device or laboratory interfaces, access model, release authority, and reviewer.
Sourced manufacturing and logistics context
Port, production, and distribution operations: SAP FICO
Baltimore Together tracks industrial, manufacturing, and logistics work as a distinct part of the city's economic-development strategy. Set reconciliation and close acceptance criteria before sourcing. Candidates should explain balances, open items, asset values, cost allocations, and the sign-off path used during conversion or cutover. Port and factory systems can connect engineering changes, production, quality, inventory, freight, customs, carriers, maintenance, exceptions, and financial settlement across organizations.
Evidence to request: Request a redacted conversion reconciliation, close checklist, or test script with exceptions and approval evidence. Trace the product or shipment through plant, warehouse, port, carrier, customer, exception, and accounting steps with system authorities, timing, and support ownership.