Product · Integration and security
Built for operations and for security teams
Flexgy integrates as one more layer, next to your grid engine. In the pilot it only reads: it writes to no operational system.
Integration
What goes in and what comes out.
- Inputs
- The candidate limit from your engine, node measurements and forecasts, and the topology.
- Outputs
- The decision (act, limit or abstain) and its Evidence Passport in JSON and PDF.
- Engines
- Vendor-agnostic: ADMS, DERMS or in-house calculation. No need to switch vendors.
- Connection
- Via API or file exchange, depending on what your control centre already uses.
Deployment and data
- Where
- On the DSO’s infrastructure or private cloud. No dependency on external services in real time.
- Data
- Grid data. No personal data of end customers.
- Confidentiality
- Grid data is handled under a confidentiality agreement and deleted at the end of the pilot if so agreed.
- Shadow mode
- Read-only: decides in parallel with real operations without writing to any OT system.
- Traceability
- Every decision is stored in a passport with a fingerprint (hash) to detect alterations.
What we do not have yet
Flexgy is a new company and does not yet hold security certifications (such as ISO 27001). We would rather say so here. In the demo we explain the controls we apply today and our certification plan, and we answer your vendor questionnaire.
Security questions: seguridad@flexgy.com
What it is not
- Not a DERMS nor a load-flow engine.
- It does not control the grid on its own.
- Not a compliance certificate: it produces the evidence that can support one.