GridShepardFrom a model
to a defensible study.
Keep site revisions, analysis results, coordination views, and generated deliverables in the engineering workflow.
Model→Study→Review
SOFTWARE FOR POWER SYSTEMS
The bigger picture.
From study
to operation.
GridShepard brings the engineering work into view. Meet GridSentinel—a software suite for system studies, protection, maintenance, power quality, and the decisions between them.
One platform. More of the power-system lifecycle.
THE GRIDSENTINEL SUITEILLUSTRATIVE INTERFACE
EXAMPLE SUBSTATIONCOMMON EQUIPMENT CONTEXT
Versioned site model
ENGINEERING CONTEXT
Start with the system.
A versioned model, study results, and the record of how a decision was reached.
Short circuitCoordinationArc flash
Different disciplines.
A clearer view of the same system.
STUDYPROTECTMONITORMAINTAINPREPAREDOCUMENTGRIDSENTINEL BY GRIDSHEPARD ↘
MEET GRIDSENTINEL
A suite built around
the whole system.
Not every question starts with the same screen. Explore the workspace for the task at hand—from a protection event to a study package, a maintenance record, or a switching order.
ENGINEERING ANALYSISSUITE CAPABILITY
From the model
to the engineering decision.
Develop studies on a versioned site model, inspect the results, and prepare a reviewable deliverable.
- Short-circuit analysis
- Protection coordination and TCC views
- Arc-flash workflows and label packages
- Study reports, revisions, and review
STUDY WORKFLOWCONCEPT VIEW
Model→Calculate→Review→Package
Illustrative curves only. Study methods, input data, limits, and deliverables require qualified engineering review.
Follow the workflowThe suite descriptions reflect the current application source. Actual availability depends on configuration, data, integrations, and required licenses. The field workspace is a separate prototype; this page is not a live application or a production-readiness claim.
THE WORK BETWEEN THE MODULES
The output is only useful
if the context comes with it.
A calculation, a trip record, and a maintenance entry answer different questions. GridSentinel gives each discipline a place for the evidence and the decisions behind its work.
From a model
From an event
to an explanation.
Bring trip information, relay-setting checks, annotations, and PRC-030 analytics into the review process.
Event→Context→Findings
From an asset
to a traceable record.
Connect equipment identity, maintenance activities, templates, evidence, and qualified sign-off.
Asset→Work→Evidence
GRIDSENTINEL / FIELD WORKSPACEPROTOTYPE
DEMONSTRATION STATION52-01
Vacuum circuit breaker
CONTACT RESISTANCE · PHASE A
52.4 µΩ
Synthetic value · not an acceptance criterion
ONE PART OF A BIGGER PICTURE
The next workspace
is in the field.
The field-capture prototype extends the maintenance story: structured readings, supporting evidence, local drafts, and a distinct confirmation when GridSentinel has received the record.
Equipment QR navigation and field access to switching documents remain planned. Real-device, offline, access, and data-classification testing come before operational use.
Explore the field conceptYOUR ENVIRONMENT SETS THE BOUNDARY
A platform for the system.
A deployment for your environment.
GridSentinel’s internal application, configured integrations, and emerging field workflow have different jobs—and different access boundaries.
The engineering application.
Studies, events, assets, reports, and role-based workflows operate against the configured application database and evidence storage.
Connect the sources you approve.
Optional data integrations and workers depend on approved endpoints, credentials, supported formats, and compatible installations.
Initiate the connection from inside.
The field prototype uses a cloud inbox that the internal connector polls over outbound HTTPS. A queued form is distinct from an internal database receipt.
The field inbox contains approved metadata and submitted evidence. Data classification, retention, identity, and applicable security obligations require review before deployment.
GRIDSHEPARD SOFTWARE
More context.
Across the work that matters.
Find your starting point Explore the suite. Choose a workflow. Define the environment.