Google Sign-In Required

Use your company Google account to access the BetterFleet private content.

Back to private home

BetterFleet Support Private
Skip to content
BetterFleet Dev Wiki
Mobile Operations Companion Deliverables (Stories)
Initializing search
    bf-dev
    • Home
    • Process
    • Products
    • Reference
    • Decisions
    • Work
    • Operations
    bf-dev
    • Home
      • Process Handbook
      • BetterFleet Workflow Map
      • Product Development System
      • Product Engineering Workflow
        • Process Workflows
        • Work Intake and Weekly Planning
        • Product Engineering Workflow in Linear
        • Product Engineering Delivery
        • Agent Guidance
        • Workflow
        • Skills
        • Skill Sources
        • Process Guides
        • GitLab Feature Flags
        • In-App Docs Authoring
        • Release Notes
        • Process Templates
        • Release Plan: <title>
      • Process Publishing
      • Product overview
        • General Reference
          • Core Domain Training
          • System Topology
          • Two-Axis Ontology Model
          • Ontology Primer
          • Worked Example
          • Evidence, Ownership, and Lineage
          • Energy Management
          • Standards and Protocol Map
          • Charging, Roaming, and Commercial Model
          • Charge Planning and Operations
          • Cross-Cutting Domains
          • Domain Coverage Matrix
        • BetterFleet Product Ontology
        • Core Operations Data Ontology
        • BetterFleet R&D Plan
        • Index
        • Architecture
        • Manage Product Capabilities
        • Manage Data and State
        • Manage Service Interaction Flows
        • Manage Reference
        • Manage Internal Application Diagrams
          • Manage Authorization And Permissions
          • bf-manage-core Auth and Authorization Model
          • Manage Authorization and Permissions
          • bf-manage-web Auth and Permission Model
          • Manage Service Catalog
          • bf-depot-sim
          • bf-digital-twin (Manage Role)
          • bf-fleet-health
          • bf-manage-connect
          • bf-manage-core
          • bf-manage-incidents
          • bf-manage-roaming
          • bf-manage-sitepwrmon
          • bf-manage-web
          • bf-schedule-creator (Manage Role)
          • bf-support-microsite
          • bf-telematics
        • Index
        • Architecture
        • Plan Reference
        • Plan Internal Application Diagrams
        • Plan Migration and Flags
        • Plan Simulation Request Lifecycle
          • Plan Service Catalog
          • bf-bnl-schedule-analysis-compute
          • bf-bnl-settings
          • bf-bnl-ui
          • bf-digital-twin (Plan Role)
          • bf-route-modelling
          • bf-schedule-creator (Plan Role)
      • Where to Ask Product Questions
      • Reference
        • Platform Reference
        • Platform Architecture
        • Script Runtime Model
        • Compose Profiles and Modes
        • Repository Map
        • Monolithic Git Transition FAQ
        • Monolithic Git Sizing
        • CI and Release Integration
        • Shared Reference
        • Shared Infrastructure Architecture
        • Secrets and Env Strategy
        • Vendors and Local Dependencies
        • System Reference
        • Cloud Data Dependencies
        • Ports and URLs
        • Service Matrix
          • API Docs
          • OCPI API Docs
          • OCPP API Docs
          • OSCP API Docs
          • VDV API Docs
          • Yard State API Docs
        • System Design
        • System Design: BBA Microgrid Controller Generic Packet Translation
        • System Design: Depot Simulation
        • System Design: IoT Sensor Packet
        • System Design: Microgrid Energy Orchestration
          • System Design: OCPP Profile 3 And ISO 15118 PKI
          • Architecture: BetterFleet OCPP Profile 3 and ISO 15118 PKI
          • Specification: BetterFleet OCPP Profile 3 and ISO 15118 Certificate Lifecycle Management
          • System Design: On-Prem Control
          • Challenge
          • Specification: BetterFleet On-Prem Continuity Control
          • System Design: OSCP
          • OSCP Protocol Documentation
          • Depot Sim Testing Requirements
          • System Design: OSCP Flexibility Provider Domain
      • Decisions
        • Architecture Decision Records
        • 0001 - Record architecture decisions
        • 0002 - Cognito for Authentication and Authorisation
        • 0003 - AWS Amplify for Authentication
        • 0004 - DynamoDB for default database
        • 0005 - Data Persistence
        • 0006 - Trunk-Based Development
        • 0007 - Generalised principle for automation
        • 0008 - Naming Repositories, Services, and URLs
        • 0009 - Use Timezone Aware DateTimes and UTC
        • 0010 - Use semantic release
        • 0011 - Centralized feature flag repository
        • 0012 - Use Named Exports in Storybook
        • 0013 - RESTful TITLE GraphQL
        • 0014 - Service Granularity
        • 0015 - Async/co-routine exception handling pattern
        • 0016 - Logging & log levels
        • 0017 - Instantiated Models
        • 0018 - Repository Pattern for Database Access
        • 0019 - Use of Design Tokens in TypeScript React Application
        • 0020 - API backwards compatibility and versioning
        • 0021 - Alembic Migration strategy
        • 0022 - Consistent react-hook-form usage
        • 0023 - Domain Event-Driven Architecture
        • 0024 - Domain Event Bus Tech Stack
        • 0025 - No enum types in DB table columns
        • 0026 - In-Memory Ormar Stores for Repository testing
        • 0027 - Storing Tab State in Query and Local Storage
        • 0028 - Adopt OpenTelemetry Semantic Conventions for Structured Logging
        • 0029 - Adopt RFC 9457 for HTTP Error Responses
        • 0030 - Use GitLab registry and Terraform state for ECS services
        • 0031 - Adopt DDD, Hexagonal Architecture, and CQRS for Python Domain Services
      • Work
        • Active Work
          • Work: Bba Microgrid Controller
          • Implementation Specification: BBA Microgrid Controller
          • BBA Microgrid Controller Deliverables (Stories)
          • Work: BFDev Monolithic Git
          • Challenge
          • Specification: BFDev Monolithic Git v2
          • BFDev Monolithic Git v2 Stories
          • Work: Complex Circuit Load Balancing
          • Implementation Specification: Complex Circuit Load Balancing
          • Complex Circuit Load Balancing Deliverables (Stories)
            • COR-10 and COR-11 Consolidation Review
          • Work: Dispatch Reliability and Reconciliation
          • Challenge
          • Specification: Dispatch Reliability and Reconciliation
          • Dispatch Reliability and Reconciliation (Unit User Stories)
            • Dispatch populated vehicle cards grey surface snapshot
            • Dispatch Visual Review
          • Work: Enable Scheduled Managed Charger Access
          • Challenge: Enable Scheduled Managed Charger Access
          • Specification Exploration Dossier: Enable Scheduled Managed Charger Access
          • Specification Review: Enable Scheduled Managed Charger Access
          • Specification: Enable Scheduled Managed Charger Access
          • Work: Guided Cut-Off and Release Orchestration
          • Specification: Guided Cut-Off and Release Orchestration
          • Guided Cut-Off and Release Orchestration (Unit User Stories)
          • Work: Production Deployment Validation
          • Challenge
          • Work: Scheduled Report Parity
          • Specification: Scheduled Report Parity
          • Work: Telematics
          • Telematics EventBridge Path
          • Telematics Ingress Architecture
          • Specification: Telematics Migration into bf-manage-core with 5-Minute Freshness and Health Visibility
          • Telematics Core Migration MVP (Implementation-Time BDD)
          • Work: Vector Derms
          • Implementation Specification: Vector DERMS
          • Vector DERMS Deliverables (Stories)
          • Work: Visiting Vehicle Charging Visibility
          • Specification: Visiting Vehicle Charging Visibility
          • Visiting Vehicle Charging Visibility (Unit User Stories)
          • Work: Workspace Owned Stripe Roaming
          • Specification: Workspace-Owned Stripe Credentials for Roaming Payments
        • Backlog Work
          • Work: Microgrid
          • Microgrid Backlog Stories
          • Work: Mobile Ops Companion
          • Challenge
          • Specification: Mobile Operations Companion v1
          • Mobile Operations Companion Deliverables (Stories)
            • Context Summary
            • Mobile Shell and Route Gating
              • User Story
              • Acceptance Criteria
            • Mobile Home Summary
              • User Story
              • Acceptance Criteria
            • Yard Visibility Companion
              • User Story
              • Acceptance Criteria
            • Chargers Mobile Visibility and Actions
              • User Story
              • Acceptance Criteria
            • Active Incidents Mobile Flow
              • User Story
              • Acceptance Criteria
            • Accessibility, Docs, and Regression Safety
              • User Story
              • Acceptance Criteria
          • Work: Oscp
          • OSCP Backlog Stories
        • Archived Work
          • Work: Code Canonical Orchestration
          • Challenge
          • Specification: Product Engineering Workflow
          • Product Engineering Workflow Deliverables (Unit User Stories)
          • Work: Release Notes Automation
          • Release Plan: Release Notes Automation
          • Release Notes Automation Backlog Stories
      • Operations
      • Onboarding Runbook
        • Operations Runbooks
        • Production Hotfix Release
        • Staging Hotfix Release
        • Manage Staging Release Validation
        • Terraform Plan Dry Runs
        • Operations Tooling
        • Code Indexing
        • Operations Evidence
        • Database Restoration Test Report
      • Daily Operations Runbook
      • Testing Guide
      • Troubleshooting
    • Context Summary
    • Mobile Shell and Route Gating
      • User Story
      • Acceptance Criteria
    • Mobile Home Summary
      • User Story
      • Acceptance Criteria
    • Yard Visibility Companion
      • User Story
      • Acceptance Criteria
    • Chargers Mobile Visibility and Actions
      • User Story
      • Acceptance Criteria
    • Active Incidents Mobile Flow
      • User Story
      • Acceptance Criteria
    • Accessibility, Docs, and Regression Safety
      • User Story
      • Acceptance Criteria
    1. Home
    2. Work
    3. Backlog
    4. Mobile ops companion

    Mobile Operations Companion Deliverables (Stories)¶

    Context Summary¶

    • Product area: BetterFleet Manage.
    • Scope basis: docs/work/backlog/mobile-ops-companion/spec.md.
    • Delivery intent: a small, isolated mobile slice that solves high-value depot-walk tasks without changing desktop behavior.
    • Phase 1 focus: depot-scoped awareness and limited charger operations.

    Mobile Shell and Route Gating¶

    User Story¶

    As a mobile user, I want a dedicated /mobile shell with focused navigation so I can move between mobile tasks quickly without changing the desktop experience.

    Acceptance Criteria¶

    • A new /mobile/* route namespace exists behind manage-mobile-ops.
    • /mobile/* renders through a dedicated mobile shell rather than the desktop sidebar layout.
    • Desktop routes and layout behavior remain unchanged.
    • The mobile shell exposes navigation for Home, Yard, Chargers, and Incidents.
    • The mobile shell clearly communicates when the app is in all-depots mode and the mobile slice requires a specific depot.

    Mobile Home Summary¶

    User Story¶

    As a yard operator, I want a mobile home summary so I can quickly see what needs attention at the selected depot.

    Acceptance Criteria¶

    • /mobile shows selected-depot context and quick navigation.
    • The page shows site alert banners for the selected depot.
    • The page shows summary counts for active incidents, chargers needing attention, vehicles needing attention, and charging now.
    • Each summary item links to the relevant mobile screen.
    • Empty and error states are readable on a phone-sized screen.

    Yard Visibility Companion¶

    User Story¶

    As a depot-floor operator, I want a list-first mobile yard view so I can check vehicle and charger status while walking the yard.

    Acceptance Criteria¶

    • /mobile/yard renders a primary accessible list of live yard items.
    • When depot layout data is available, the page also renders a read-only visual yard representation.
    • When depot layout data is missing, the page falls back to the list-only experience.
    • The list exposes the same live assets and statuses represented in the visual yard state when layout data is available.
    • Statuses are communicated with text, not color alone.

    Chargers Mobile Visibility and Actions¶

    User Story¶

    As an operator with charger permissions, I want a mobile charger list and detail flow so I can inspect charger state and safely request common interventions.

    Acceptance Criteria¶

    • /mobile/chargers shows a filterable mobile list of chargers for the selected depot.
    • Charger cards show charger state, connection state, connector summaries, connected vehicle, SoC, and estimated time to target when available.
    • /mobile/chargers/:chargePointId shows charger detail and connector detail.
    • Mobile charger detail exposes only soft reset, remote start/stop, and remote cable release.
    • Existing permission checks and feature flags still gate action visibility.
    • Each operational action requires accessible confirmation and announces success or failure feedback.

    Active Incidents Mobile Flow¶

    User Story¶

    As an operations user, I want an active-incident mobile flow so I can review an issue and jump to the affected charger quickly.

    Acceptance Criteria¶

    • /mobile/incidents shows active incidents only for the selected depot context.
    • Incident cards show title, severity, reference ID, created time, and affected asset hints when available.
    • /mobile/incidents/:incidentId shows read-only incident detail, affected assets, event timeline, and troubleshooting context.
    • Incident detail links to mobile charger detail when an affected charger is known.
    • Incident resolution is not available in the mobile slice for phase 1.

    Accessibility, Docs, and Regression Safety¶

    User Story¶

    As a delivery team, I want the mobile slice to be accessible and documented so we can release it safely and iterate without confusion.

    Acceptance Criteria¶

    • The delivered mobile slice remains usable from 320px widths upward and supports 200% zoom/reflow expectations.
    • Interactive controls have clear labels, visible focus styles, and touch-friendly sizing.
    • The mobile slice has targeted automated coverage for its helper logic and critical component behavior.
    • In-app help includes a mobile-operations guide describing the new mobile flow and scope boundaries.
    • Unreleased release notes mention the new feature flag and mobile companion capability.
    Made with Material for MkDocs
    BFDev Docs Assistant
    New conversation?
    Ask one focused question at a time, this helps the assistant provide accurate answers about what's been implemented in BetterFleet.