PPC Portal — iEnergia

Loading…

Phase progress

Immediate next actions

    Architecture Modes

    Three deployment topologies for direct and remote PoI meter configurations.

    Control timing classes

    ClassUse caseTarget periodNotes
    Fast controlLocal PoI feedback, inverter dispatch100 ms – 1 sOnly if network and devices support it
    Normal controlPMGD active/reactive dispatch1 – 5 sRealistic for Modbus TCP plants
    Slow correctionRemote meter reconciliation, PRMTE, reporting10 s – 15 minNot for fast closed-loop control
    Evidence/reportingCompliance, trends, audit1 min – dailyRaw + aggregated stored

    Data quality model

    FlagMeaningControl action
    GOODFresh, valid measurementNormal control allowed
    STALEAge > warn threshold, value may be oldFreeze or reduce setpoint
    BADProtocol error, impossible valueFallback mandatory
    ESTIMATEDDerived from model, not measuredShadow mode only
    MANUALOperator-entered valueManual override active

    Deployment modes

    ModeDescriptionWrites to devices?
    SimulatorFake meter + fake inverter fleetSimulator only
    Read-only liveLive reads, no device writesNever
    Shadow controlComputes setpoints but does not writeNever
    Limited pilotWrites to allowlisted devices, operator approvedYes, guarded
    ProductionFull control under accepted designYes, audited

    Hardware Tiers

    Three-tier selection: lab validation → industrial pilot → utility-grade production.

    Selection guidance

    Step 1: Start with Tier 1 (lab PC) for simulator, driver development, and dashboard proof-of-concept.
    Step 2: Move to Tier 2 (industrial IPC) for first read-only field pilot. Best ROI for iEnergia budget-constrained projects.
    Step 3: Tier 3 (utility-grade) only when distributor/CEN demands formal support, response-time evidence, or redundancy.

    Compliance Matrix

    PMG/PMGD Chile regulatory status — refresh required from official sources before finalizing design.

    Risk Register

    Technical, regulatory, cybersecurity, and field implementation risks.

    Test Scenarios

    Simulator scenario results — generated by scripts/run_scenarios.py. Simulator only; no hardware touched.

    PMG Llancay — first real plant (NUP 2438)

    9 MW, CGE / S-E El Peumo. Meter (ION8650) ~13 km away at the substation. CEN ensayos in simulation.

    Plant

    9 MW · 3× SG3125
    23 kV · 50 Hz · NOJA recloser

    PoI meter

    ION8650 @ El Peumo
    ~13 km · FortiGate VPN · edge relay

    SITR

    DNP3 via SEL RTAC
    <5 s · GPS ±100 µs

    CEN ensayos (cronograma de ensayos)

    Covers the CEN test schedule: 8-point PQ capability curve, voltage ±3% step (high/med/low load), reactive ±1 Mvar step, power-factor step, and the 20%/min active-power ramp. Voltage steps accept reach-target or saturate-at-capability (±3% needs ~±6 Mvar, available only at low load). Simulator only — see llancay/TEST_CONGRUENCE_CEN.md.

    Architecture Decision Records

    Key decisions with rationale — not to be overridden without an updated ADR.

    Coordinator Letters Watch

    CEN/Coordinador Eléctrico Nacional communications monitored for emerging PPC requirements.

    Last run

    Not yet run
    Required before architecture freeze

    Signals found

    0
    Items requiring PPC design action

    Status

    Pending
    Run coordinator_letters_watch_agent

    What to monitor

    SourceTopicWhy it matters
    cartas.coordinador.clPMGD control, consigna, reducción inyecciónActive curtailment commands may become mandatory
    coordinador.cl daily reportsCDC requesting PMGD injection reductionPPC must log, apply, and prove compliance
    CEN SSCC reports / workshopsVerification letters, future performance testsIBR/frequency/voltage requirements may expand
    CEN EDAC/CDT/IBR studiesInverter-based resource performancePPC feature requirements may evolve
    Distributor lettersProject-specific monitoring/control requirementsPlant-specific conditions may add PPC obligations

    PPC design requirements from watch

    FeatureReasonStatus
    External command source abstractionCDC, distributor, local HMI, scheduleImplemented
    Command lifecycle loggingReceived → validated → executing → completedImplemented
    Configurable ramp targetsPlant-specific, not hardcodedImplemented
    Fallback with priority hierarchyLink failure, bad quality, emergency stopImplemented
    Evidence CSV/JSON generationProve response time, ramp, command complianceImplemented
    Frequency/voltage support modesFuture IBR/SSCC requirementsPlaceholder

    Roadmap

    8 phases from foundation to production standard. Each phase has defined go/no-go gates.

    Go/no-go gates summary

    PhaseGate
    Phase 0Official sources recorded, unknowns listed, coordinator letters checked
    Phase 1Simulator passes step, ramp, dropout, stale-data, alarm tests
    Phase 2No hardcoded registers in core; write gate enforced; driver tests pass
    Phase 3Link quality evidence exists; remote loop stability simulated with latency
    Phase 4Compliance matrix current; evidence can be generated from logs
    Phase 51–2 weeks stable read-only logs; no unexplained outages
    Phase 6Operator approval; emergency stop validated; successful test report
    Phase 7FAT/SAT package signed; maintenance manual delivered

    Deployment Status

    Dashboard and PPC deployment tracking.

    Dashboard domain

    ppc.portal-ienergia.live
    Cloudflare Workers / Pages

    Deploy approved

    Pending approval
    Awaiting explicit operator confirmation

    Pre-deploy checklist

    • Run wrangler whoami to confirm Cloudflare account
    • Confirm ppc.portal-ienergia.live domain in Cloudflare dashboard
    • Run npm run dev in cloudflare-worker/ and verify local preview
    • Review status.json content for accuracy
    • Obtain explicit deploy approval from project owner
    • Run npx wrangler deploy from cloudflare-worker/
    • Verify live site at ppc.portal-ienergia.live

    Update workflow

    Run python scripts/generate_status_json.py to regenerate cloudflare-worker/public/status.json from the markdown planning files.

    Then re-deploy with npx wrangler deploy from cloudflare-worker/.

    Optionally automate with a GitHub Actions workflow on push to main.