Scenario. Your multi-depot electrification program is at a critical integration milestone. The utility requires specific grid fault ride-through thresholds to maintain regional stability. The OEM charging vendor proposes alternative protection relay settings to maximize equipment uptime and warranty coverage. Simultaneously, the agency's internal safety team demands stricter isolation protocols following a recent industry incident. You must facilitate a cross-functional decision on the final protection coordination strategy, balancing grid reliability, vendor constraints, and safety compliance.
Problem to solve. Drive alignment across three competing technical priorities, establish a defensible protection coordination baseline, and sequence a decision that satisfies grid code, vendor warranties, and agency safety mandates.
Format
cross-functional-decision · 40 min · ~2 hr prep
Success criteria
- Surface and reconcile conflicting technical standards without deferring the decision
- Establish clear accountability for fault detection and isolation responsibilities
- Negotiate a unified testing and validation protocol acceptable to all parties
- Document trade-offs and decision rationale for program governance
What to review beforehand
- Grid code compliance requirements for fault ride-through
- Standard protection relay coordination principles
- Agency safety protocols for high-voltage isolation and emergency shutdown
Ground rules
- You are facilitating the discussion and driving toward a technical decision
- Balance competing incentives without playing favorites
- Focus on risk allocation, validation sequencing, and decision clarity
Roles in scenario
Utility Interconnection Engineer (cross_functional_partner, played by cross_functional)
Motivation. Protect regional grid stability and enforce strict fault ride-through thresholds to prevent cascading outages.
Constraints
- Regulatory mandates from state utility commission
- Limited flexibility on relay tripping curves
- Must validate settings before interconnection approval
Tensions to introduce
- Insist that vendor-proposed settings violate grid code minimums
- Threaten to delay interconnection if utility standards aren't met
- Push for conservative isolation that may reduce charging uptime
In-character guidance
- Cite specific grid code sections and historical fault data
- Remain data-driven but inflexible on regulatory baselines
- Acknowledge vendor constraints but prioritize system-wide reliability
Do not
- Do not solve the coordination problem for the candidate
- Do not concede on core grid code requirements without technical justification
- Do not escalate hostility or dismiss other parties' constraints
OEM Charging Vendor Representative (external_partner, played by peer)
Motivation. Maximize equipment uptime, protect warranty coverage, and avoid unnecessary hardware modifications.
Constraints
- Warranty voided if settings exceed manufacturer limits
- Hardware cannot be retrofitted without significant cost
- Commercial SLAs tied to charging availability metrics
Tensions to introduce
- Argue that utility thresholds are overly conservative and reduce operational efficiency
- Push for adaptive relay logic that shifts responsibility to software
- Highlight cost and timeline impacts of hardware changes
In-character guidance
- Present vendor testing data and warranty documentation
- Emphasize uptime commitments and commercial penalties
- Remain collaborative but firm on technical and contractual limits
Do not
- Do not volunteer alternative compliance pathways unless asked
- Do not agree to unilateral changes without candidate negotiation
- Do not become adversarial or dismiss grid safety concerns
Agency Safety & Compliance Lead (peer, played by peer)
Motivation. Ensure zero-risk isolation protocols and absolute compliance with agency safety standards following recent industry incidents.
Constraints
- Mandatory safety review before commissioning
- Strict adherence to internal emergency shutdown protocols
- Zero tolerance for unvalidated fault detection gaps
Tensions to introduce
- Demand redundant isolation layers regardless of cost or complexity
- Question the reliability of vendor software-based fault logic
- Insist on extended validation testing before deployment
In-character guidance
- Reference recent incident reports and internal safety mandates
- Prioritize personnel safety and regulatory audit readiness
- Challenge assumptions about software reliability and fault detection speed
Do not
- Do not solve the trade-off problem for the candidate
- Do not accept compromises that bypass formal safety validation
- Do not dominate the conversation or shut down technical debate
Scoring anchors
- Exceeds
- Rapidly maps technical boundaries, facilitates a structured trade-off framework, drives explicit accountability mapping, and secures a unified validation protocol that satisfies all parties while protecting agency risk.
- Meets
- Identifies key constraints from each party, facilitates a balanced discussion, establishes a conditional decision with clear validation steps, and documents trade-offs for program governance.
- Below
- Struggles to synthesize competing technical demands, allows ambiguity in fault responsibility, defers decision-making, or fails to establish a defensible compliance and testing pathway.