Power Generation
Turn grid requirements into testable plant functions and records
Translate Turkish grid and project requirements into PPC functions, measurements, records, tests and operational documentation.
Operational problem
Renewable and hybrid plants combine multi-vendor equipment, point-of-connection constraints, local control and portfolio reporting. Visibility without a defined control boundary leaves operators with fragmented evidence and uncertain action paths.
EnergyPortal provides central operations and governed analytics, enPowerManager owns qualified plant-level control, Scadify connects and executes at the field edge, and Enlogy engineering defines integration, testing and commissioning responsibilities.
Core capabilities
Requirements and responsibility matrix
Configured according to the project’s data, control, approval and operating boundaries.
Active/reactive, voltage and frequency-related control implementation
Configured according to the project’s data, control, approval and operating boundaries.
Measurement, command and event recording
Configured according to the project’s data, control, approval and operating boundaries.
FAT/SAT, commissioning and site testing
Configured according to the project’s data, control, approval and operating boundaries.
TEİAŞ EK-18-oriented operational data and documentation support
Configured according to the project’s data, control, approval and operating boundaries.
Products and delivery responsibilities
Assemble the operating stack around the action.
Plant-level PPC, hybrid-source and grid-interface control.
View responsibility →EnergyPortalCentral visibility, analytics, reporting, workflows and governance.
View responsibility →ScadifyField acquisition, local automation, protocols and resilient execution.
View responsibility →Engineering & ServicesAssessment, integration, installation, testing and commissioning.
View responsibility →Operational workflow
From operational context to measured action.
- 01Review connection agreement and applicable criteria
- 02Map requirements to control and measurements
- 03Implement and integrate PPC/SCADA
- 04Test, record and correct deviations
- 05Prepare acceptance evidence and handover
Data sources and integrations
Connect the evidence that explains the decision.
- Plant meters and analyzers
- Inverters, turbine and storage controllers
- Weather and irradiance stations
- Point-of-connection measurements
- Plant SCADA and dispatch context
Governance and resilience
Grid-code and TEİAŞ requirements depend on the connection agreement, applicable technical criteria and tested project configuration. Software does not create compliance automatically.
Protocol roles, OEM compatibility, data retention, control limits and failure behaviour must be confirmed from the engineering-approved release and project documents.
Outcomes and KPI framework
Measure the operating result, not only the software activity.
Traceable plant and grid-interface control
Use an agreed baseline, operational definition and evidence source before assigning a target.
Consistent data quality and operational context
Use an agreed baseline, operational definition and evidence source before assigning a target.
Clear route from alarm or setpoint to accountable action
Use an agreed baseline, operational definition and evidence source before assigning a target.
Project-specific test and acceptance evidence
Use an agreed baseline, operational definition and evidence source before assigning a target.
Solution architecture
Make responsibility visible from field to enterprise.
EnergyPortal provides central operations and governed analytics, enPowerManager owns qualified plant-level control, Scadify connects and executes at the field edge, and Enlogy engineering defines integration, testing and commissioning responsibilities. The architecture separates observation, recommendation, human-approved action and local execution so that each team can see what it owns.
Engineering and implementation
Move from architecture to accepted operation.
Engineering scope can include single-line review, control responsibility, OEM/protocol assessment, network design, FAT/SAT, commissioning, grid tests, training and lifecycle support. Exact supply and acceptance responsibility is project-specific.
Publication boundary
Capabilities are described as supported or project-configured where appropriate. Customer identities, quantified results, certifications and regulatory acceptance are not inferred from the solution page.
Related solutions and products
Continue with the next operational question.
FAQ
Questions to resolve before implementation.
Does Enlogy certify that a plant is compliant?
No. Enlogy implements and tests project-specific functions; formal compliance depends on applicable requirements, evidence and acceptance.
Is EK-18 required for every plant?
Applicability depends on the plant, connection conditions and current TEİAŞ requirements. The project review determines the required scope.
Can existing PPC records be reviewed?
Yes. Existing control, measurement and test records can be assessed as part of an engineering review.
Next step