Charge Point Operator Dynamic Tariff Sync and Roaming SLA Default Notice
Issue a high-stakes operational default notification to an EV charge point operator failing dynamic tariff synchronization.
Use this template when an EV charging network operator repeatedly fails real-time tariff updates and uptime SLAs on your e-roaming platform. It delivers a structured, legally sound remediation and financial sanction email.
Role: Lead EV Roaming and Retail Marketplace Operations Manager at a national clean transportation energy platform.
Context
- Roaming Platform: {{roaming_hub_platform}}
- Defaulting Operator: {{charge_point_operator}}
- Station Uptime Deficit: {{uptime_deficit_percentage}}
- Tariff Sync Latency: {{tariff_sync_latency_hours}}
- Grid Infrastructure Affected: {{impacted_substations}}
- Contractual Penalties Accrued: {{penalties_accrued}}
Task
Draft a formal operational SLA breach notice and remediation demand email to the operations executive at {{charge_point_operator}}, addressing dynamic tariff synchronization lag, out-of-spec station availability, and initiating penalty recovery under {{roaming_hub_platform}} agreements.
Method
- Reference the Master Roaming Interoperability Agreement and dynamic roaming tariff schedules executed between both parties.
- Present the measured {{tariff_sync_latency_hours}} delay against the contractually mandated 15-minute OCPI/eMIP synchronization ceiling.
- Highlight consumer billing discrepancies and EV driver overcharging risks across {{impacted_substations}} feeder zones.
- Contrast the measured {{uptime_deficit_percentage}} against the 99.5% public charger availability threshold.
- Formulate the financial penalty ledger confirming {{penalties_accrued}} in debit deductions against the upcoming bi-weekly settlement cycle.
- Mandate an end-to-end sandbox tariff push test and OCPI 2.2.1 endpoint validation within 5 business days.
- Detail the progressive delisting schedule that will hide non-compliant charging nodes from driver discovery apps if fixes fail.
Constraints
- MUST cite precise OCPI/OICP communication protocol standards and timestamped sync logs.
- MUST clearly define the exact settlement ledger deductions without vague contractual language.
- MUST NOT provide extensions beyond the standard 5-business-day platform cure cycle.
- Tone must be assertive, operational, and uncompromising on consumer price transparency.
Output format
- Subject: Operational SLA Breach Notice | [Platform] vs [CPO Entity] | Priority Tier 1
- Header: Key Metrics Dashboard (Operator, Total Out-of-Spec Ports, Total Fines, Cure Deadline)
- Section 1: Formal Notification of Contractual Non-Performance (max 120 words)
- Section 2: Telemetry & Pricing Inconsistency Evidence (bulleted technical log extract)
- Section 3: Financial Settlement Deductions & Offset Calculation (max 150 words)
- Section 4: Mandatory Technical Remediation Schedule (4-step chronological requirement)
- Sign-off: E-Mobility Marketplace Operations Executive Team
Self-review
- Are the OCPI protocol requirements and dynamic pricing latency metrics clearly specified?
- Is the monetary penalty structure directly tied to the variables provided?
- Does the remediation timeline give clear technical criteria for restoring full platform discoverability?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.