Quick Reference

Group Models
Facilities & Standards GeneratorFacility · PerformanceStandard · MonitoringRequirement
Monitoring & Assessment ComplianceObservation · ComplianceAssessment · ComplianceEvidence
Non-Compliance & Rectification NonCompliance · RectificationPlan

8 models in total.

Key status vocabularies (enums)

  • PerformanceStandard.parameter: reactive_power · ride_through · frequency_response · voltage_control · active_power · model_validation …
  • ComplianceAssessment.outcome: compliant · non_compliant · partially_compliant …
  • NonCompliance.materiality: low · medium · high · critical
  • RectificationPlan.status: draft · in_progress · complete · verified …

The demo data set

The Northgate Solar Farm facility NBSF (solar, 180 MW, registered) with a reactive-power standard PS-S5251 (S5.2.5.1) and a ride-through standard PS-S52511 (S5.2.5.11). Quarterly SCADA monitoring MON-RP produced observation OBS-RP-Q3 (within requirement), and the Q3 assessment ASMT-Q3 is compliant. But the ride-through standard has an open non-compliance NC-RT-01 (high — the commissioning ride-through test tripped), with rectification plan RP-RT-01 (retune control + repeat) in progress.

9 rows across all 8 models.

Translation & modelling notes

  • Source is the pack's application { entity E { field: type; } } dialect, machine-translated to native DSL by a dedicated converter: each entity gets a surrogate Int pk, its business key kept as a required unique String, ref(T) → Int [ref], enum(...) inlined, list → Text.
  • NonCompliance.description was renamed summary so its <fk>_name shows the non-compliance id (it has no title/code). ComplianceEvidence uses a polymorphic subject_id. suspected/verified/notification_required are Booleans.
  • Denormalisation is intentional (child rows carry parent codes alongside the FK). Post-seed scan: zero Text leaks.
  • The workflow/governance/events are Phase 2 (page 03).