Demo listing. This page uses illustrative seed metadata to demonstrate the Atlas. Claims shown here are not verified product facts.
GridCrew
Energy & Utilities
Field-service management for utilities: work orders, crew scheduling and dispatch, mobile execution and AI-assisted job prioritisation.
Last verified 15 Sept 2026 · Updated 23 Sept 2026 · Metadata v1
Problem
Field work is planned on spreadsheets and radios; crews are dispatched inefficiently and repeat visits are common.
Outcome
Better crew utilisation, fewer repeat visits and real-time visibility of field work.
Who uses it
- Field Technician
- Operations Analyst
- COO
Key capabilities
Work-order management
IncludedPlanned, reactive and emergency work orders.
Domain:
workordersCrew scheduling and dispatch
IncludedSchedule by skill, location and shift.
Domain:
dispatchJob prioritisation
AI-assistedIncludedRecommend priority by risk and customer impact.
Mobile execution
IncludedChecklists, photos and signatures on mobile.
Domain:
executionRoute optimization
ConfigurableOptimize daily routes across crews.
Typical workflow
Reactive fault response
Trigger: A fault is reported or detected
Automated
Stage 1: Create work order
System
AI-assisted
Stage 2: Recommend priority
System
Task
Stage 3: Dispatch crew
Dispatcher
Task
Stage 4: Execute job on site
Field technician
Human checkpoint
Stage 5: Close and review
Supervisor
Task Automated AI-assisted Human checkpoint Decision
About this foundation
GridCrew manages planned and reactive field work for utilities and energy operators. Work orders are prioritised by risk and customer impact, crews are scheduled by skills and location, and technicians complete jobs on mobile with photos and checklists. Supervisors see progress and repeat-visit causes.
Related applications
- • Addresses the same problem: Manual Workflow, Poor Visibility
- • Shared capabilities: Workflow Automation, Reporting
- • Addresses the same problem: Manual Workflow, Poor Visibility
- • Shared capabilities: Scheduling & Dispatch, Workflow Automation
- • Addresses the same problem: Manual Workflow, Poor Visibility
- • Shared capabilities: Reporting
- • Addresses the same problem: Manual Workflow
- • Shared capabilities: Workflow Automation, Reporting
- • Addresses the same problem: Manual Workflow
- • Shared capabilities: Workflow Automation, Reporting
- • Addresses the same problem: Poor Visibility
- • Shared capabilities: Reporting
Reactive fault response
Trigger: A fault is reported or detected
Automated
Stage 1: Create work order
System
AI-assisted
Stage 2: Recommend priority
System
Task
Stage 3: Dispatch crew
Dispatcher
Task
Stage 4: Execute job on site
Field technician
Human checkpoint
Stage 5: Close and review
Supervisor
Actors
Dispatcher, Field technician, Supervisor
Outputs
- Completed work order
- Crew utilisation report
Evidence generated
- Job photos and checklist
Exceptions
- Parts unavailable reschedules job
Task Automated AI-assisted Human checkpoint Decision
Included ships in the foundation · Configurable is switched or tuned per customer · Extension is customer-specific build scope · Planned is on the roadmap and not available today.
Work-order management
IncludedPlanned, reactive and emergency work orders.
Domain:
workordersCrew scheduling and dispatch
IncludedSchedule by skill, location and shift.
Domain:
dispatchJob prioritisation
AI-assistedIncludedRecommend priority by risk and customer impact.
Mobile execution
IncludedChecklists, photos and signatures on mobile.
Domain:
executionRoute optimization
ConfigurableOptimize daily routes across crews.
GIS network model integration
ExtensionAsset network model from GIS.
- Architecture class
- Domain-driven design, OpenAPI-first
- Bounded contexts
- 7
- API-first
- Yes — OpenAPI contracts are authoritative
- Identity
- Enterprise OIDC / SAML via the fazeZERO identity blueprint; tenant-aware role-based access.
- Multi-tenancy
- Tenant-aware
- Service boundaries
- 7 bounded contexts behind one API server.
- Integration approach
- Ports-and-adapters: every external system sits behind an adapter; OpenAPI contracts for inbound APIs.
- Eventing
- Integration events via transactional outbox.
- Storage abstraction
- Repository interfaces; DynamoDB or relational adapters.
- Deployment pattern
- Containerized API + web application; infrastructure as code per cloud profile.
- Architecture version
- 1.0
Approved domain names
- assets
- workorders
- crews
- dispatch
- execution
- reports
- identity
- Web Application
- API Server
- Application Services
- Domain / Generated Core
- Adapters
- Customer Systems
Generator source, templates and factory orchestration are proprietary and are not part of this listing.
Reference Adapter: shipped and tested · Previously Integrated: delivered before · Standard API Pattern: integrates via a documented pattern · Customer-Specific: built in your implementation.
ERP
| Integration | Status | Direction | Method |
|---|---|---|---|
| IBM Maximo / EAM | Customer-Specific | bidirectional | REST API |
Identity
| Integration | Status | Direction | Method |
|---|---|---|---|
| Microsoft Entra ID | Reference Adapter | bidirectional | OIDC |
Deployment
- Deployment models
- Customer Cloud
- Cloud profiles
- Azure Profile, AWS Profile, Google Cloud Profile
- Containerized
- Yes
- Regions
- GCC, GLOBAL
Cloud profiles describe approved deployment patterns. They are not formal marketplace certifications.
Data handling
- Stores customer data
- Yes
- Data leaves customer environment
- Configurable
- Uses external AI provider
- Configurable
- Sends logs externally
- No
- PII expected
- Determined during customer configuration
- Data-residency support
- Yes
- Subprocessors required
- Determined during customer configuration
Identity & access
- Authentication
- OIDC, Entra ID, SAML
- Authorization
- Role-Based, Tenant-Aware
- Source availability
- Proprietary
Support
- Implementation
- Delivered by fazeZERO or a certified partner during the Solution Definition and AI Production Sprints.
- Production support
- Production support available under a separate support agreement.
- Contact
- support@fazezero.com
Badges
Deployment-Ready Foundation
Application has passed the defined fazeZERO scaffold, build and testing baseline.
Customer-specific integration, security, configuration, hardening and acceptance remain part of implementation.
Issued 23 Sept 2026
fazeZERO Verified
Listing metadata and published technical claims have been reviewed by fazeZERO.
Issued 23 Sept 2026
Evidence shows that this listing represents real engineering. Internal metrics are only published when fazeZERO has approved them for publication.
Build
Automated tests
Deployment validation
- Last verification
- 15 Sept 2026
- Release
- 1.0.0
- Architecture version
- 1.0
- Listing metadata version
- 1
- Last published
- 23 Sept 2026