GridShepardStart at the right device.
A planned QR entry point connects a physical asset to its identity, history, and assigned work.
QR navigation · planned GRIDSENTINEL / FIELD WORKSPACE CONCEPT
Good work.
Clear records.
The work happens in the field. The record should, too. Bring electrical testing, equipment details, and maintenance evidence into one connected workflow.
In development. Grounded in real field workflows.
THE FIELD WORKSPACEINTERACTIVE CONCEPT
GridShepard / Field record
DEMONSTRATION STATION Saved on device
52-01
Vacuum circuit breaker
CONTACT RESISTANCE01 / 03
µΩ
✓ Procedure linked / Instrument recorded
A MORE COMPLETE HANDOFFCatch the gaps.
Catch the gaps.
Before leaving site.
A collection workflow that asks for the details a paper form can miss.
Equipment & work order✓ Identified
Instrument & calibration✓ Recorded
Procedure & acceptance reference✓ Linked
Missing or inapplicable readingsReason required
A complete record still needs qualified review. Collection checks do not determine equipment acceptance or compliance.
A VISIBLE DELIVERY TRAILKnow where
Know where
the record stands.
Designed to distinguish a local save from an internal database confirmation.
- 1Saved on device
Retained locally during a service interruption.
- 2Queued in cloud
Awaiting the internal connector.
- 3Saved in GridSentinel
Confirmed after the internal database commit.
Illustrative workflow. This homepage does not send, save, or synchronize test records.
SYNTHETIC EXAMPLE Values are illustrative, not acceptance criteria.
A record made at the equipment.
Built to follow the work all the way back.
Built to follow the work all the way back.
ONE WORKFLOW. THE EQUIPMENT YOU KNOW.
⌁ Transformers⊞ Circuit breakers⏚ Disconnect switches
START WITH WHAT MATTERS FROM THE BASKET TO THE BACK OFFICE
One record.
Less chasing.
Paper gets the job done—until a value is missing, a photo lives on another phone, or someone has to type it all again. GridShepard starts where that friction starts.
Record it once, in the field.
Structured readings, explicit reasons for omissions, instrument details, and supporting evidence.
Field forms · prototypeClose the loop with the office.
An outbound connector brings records into GridSentinel and returns a distinct database receipt.
Connector · prototypeDESIGNED AROUND THE CREW
Less friction.
More context.
From the first measurement to the next maintenance cycle, the equipment stays at the center.
Made for the moment.
One reading at a time. Large controls. A numerical entry workflow that can be evaluated with an external keypad.
Glove, iPad, and keypad use require field validation.01
Field forms that ask the next question.
Capture as-found and as-left readings, procedure references, calibration details, conditions, and findings. Missing information becomes visible before submission.
Available in the local prototype02
Work that survives a lost signal.
Local drafts and a frozen submission queue support interruptions. Clear delivery states distinguish device storage, cloud acceptance, and an internal database commit.
Prototype · real-device testing pending03
Evidence alongside the reading.
Attach supporting photos and reports to the record, rather than reconstructing the story later from separate messages and files.
Attachments in the local prototype04
The next job already in view.
The product direction brings equipment QR navigation, outstanding issues, maintenance assignments, and switching documents into the same workspace.
Planned product directionCONNECTED, ON YOUR TERMS
Keep your internal
systems internal.
The proposed cloud inbox waits for GridSentinel’s connector to initiate outbound HTTPS. It does not need an inbound route to your internal database.
Start with a defined pilotPROPOSED DATA FLOWOUTBOUND INITIATED
Field workspaceLocal draft → cloud inbox
FIELDAuthenticated form submission
Cloud inboxQueue metadata, forms & attachments
CLOUDInternal connector initiates HTTPS
INTERNAL NETWORK
GridSentinel connectorValidate → commit → return receipt
Queued metadata and evidence do enter cloud storage. Classification, access, retention, and any applicable NERC CIP requirements need a separate deployment review. No compliance status is implied.
A PRACTICAL PLACE TO START
One crew. One workflow.
A better record.
Start with a small, approved equipment set and learn from the people doing the work.
Explore the rollout checklist. No signup.