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
Visiting Vehicle Charging Visibility (Unit User 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)
            • Context Summary
              • Show away-from-home charging in the home-depot vehicle view
            • User Story
            • Acceptance Criteria
            • Dependencies
            • Split Signals
              • Show visiting vehicles in the hosting-depot vehicle view
            • User Story
            • Acceptance Criteria
            • Dependencies
            • Split Signals
              • Show cross-depot context in the troubleshooting timeline
            • User Story
            • Acceptance Criteria
            • Dependencies
            • Split Signals
              • Show cross-depot meaning in Charging Sessions
            • User Story
            • Acceptance Criteria
            • Dependencies
            • Split Signals
              • Keep Vehicle Charging Summary aligned with Charging Sessions
            • User Story
            • Acceptance Criteria
            • Dependencies
            • Split Signals
          • 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)
          • 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
      • Show away-from-home charging in the home-depot vehicle view
    • User Story
    • Acceptance Criteria
    • Dependencies
    • Split Signals
      • Show visiting vehicles in the hosting-depot vehicle view
    • User Story
    • Acceptance Criteria
    • Dependencies
    • Split Signals
      • Show cross-depot context in the troubleshooting timeline
    • User Story
    • Acceptance Criteria
    • Dependencies
    • Split Signals
      • Show cross-depot meaning in Charging Sessions
    • User Story
    • Acceptance Criteria
    • Dependencies
    • Split Signals
      • Keep Vehicle Charging Summary aligned with Charging Sessions
    • User Story
    • Acceptance Criteria
    • Dependencies
    • Split Signals
    1. Home
    2. Work
    3. Active
    4. Visiting vehicle charging visibility

    Visiting Vehicle Charging Visibility (Unit User Stories)¶

    Context Summary¶

    • Product area: BetterFleet Manage multi-site depot operations and reporting.
    • Primary entrypoints: depot vehicle views, troubleshooting timeline, Charging Sessions, and Vehicle Charging Summary.
    • Repo scope: bf-manage-web and bf-manage-core.
    • Scope basis: spec.
    • Scope decision: multi-site overview statistics and other summary surfaces stay out of scope for this story set.
    • Story slicing decision: report follow-through stays separate from depot vehicle and timeline visibility slices.
    • Cross-cutting delivery rule: every story that changes bf-manage-core must be reviewed against bf-manage-core/docs/DDD/agent.md; any boundary-review, validation, or other architecture follow-through should be tracked as execution-only Linear issues rather than broad canonical stories.
    • Linear mirror rule: each UUS in this file should map to one Linear story issue under the MPS: Visiting Vehicle Charging Visibility project.

    Show away-from-home charging in the home-depot vehicle view¶

    User Story¶

    As a depot manager viewing my home-depot fleet, I want to see when one of my vehicles is actively charging at another depot so that I can understand its live charging state without switching depot context.

    Acceptance Criteria¶

    • When a vehicle whose home depot is the selected depot is actively charging at another depot, the home-depot vehicle view shows that the vehicle is charging and identifies the charging depot.
    • When a vehicle whose home depot is the selected depot is actively charging at that same depot, the home-depot vehicle view keeps the current local charging meaning instead of showing away-from-home wording.
    • When a vehicle whose home depot is the selected depot is not actively charging, the away-from-home charging indicator does not appear.
    • Existing vehicle-view interactions such as filtering, sorting, and pagination remain available.

    Dependencies¶

    • None.

    Split Signals¶

    • Exact presentation choice such as separate section, separate table, or inline indicator stays inside this story and does not require a second canonical story.
    • Multi-site overview totals or summary cards remain out of scope.

    Show visiting vehicles in the hosting-depot vehicle view¶

    User Story¶

    As a depot manager viewing vehicles at a hosting depot, I want to see which active charging vehicles come from another home depot so that I can understand who is visiting my site.

    Acceptance Criteria¶

    • When a vehicle from another home depot is actively charging at the selected depot, the hosting-depot vehicle view shows the vehicle and identifies its home depot.
    • When a vehicle actively charging at the selected depot belongs to that depot, the hosting-depot vehicle view keeps the local vehicle meaning instead of showing visiting wording.
    • When a charging vehicle at the selected depot has no home depot assigned, the hosting-depot vehicle view shows an explicit unassigned-home-depot state instead of another depot name.
    • Existing vehicle-view interactions such as filtering, sorting, and pagination remain available for visible rows.

    Dependencies¶

    • None.

    Split Signals¶

    • Surfacing parked or otherwise non-charging visiting vehicles would be a separate story.

    Show cross-depot context in the troubleshooting timeline¶

    User Story¶

    As a depot operator using the troubleshooting timeline, I want charging-session entries to show whether the vehicle is visiting and where it belongs so that I can interpret sessions without manual lookup.

    Acceptance Criteria¶

    • When the selected depot's timeline includes a charging session for a vehicle whose home depot differs from the charging depot, the charging-session details show both the home-depot meaning and the hosting-depot meaning for that session.
    • When the selected depot's timeline includes a charging session for a vehicle whose home depot matches the charging depot, the timeline keeps the existing local charging meaning instead of showing visiting wording.
    • When the selected depot's timeline includes a charging session for a vehicle with no home depot assigned, the timeline shows an explicit unassigned-home-depot state.
    • Existing timeline incident and event visibility remains available for the same charging session.

    Dependencies¶

    • None.

    Split Signals¶

    • Timeline filtering or grouping changes beyond the session-level context are separate stories.

    Show cross-depot meaning in Charging Sessions¶

    User Story¶

    As a finance or reporting user, I want Charging Sessions to show home-depot and charging-depot meaning for cross-depot sessions so that I can interpret who owns the vehicle and where charging occurred.

    Acceptance Criteria¶

    • When a charging session belongs to a vehicle whose home depot differs from the charging depot, Charging Sessions presents explicit cross-depot meaning in both on-screen and exported output.
    • When a charging session is local to the selected depot, Charging Sessions keeps the current local interpretation instead of adding cross-depot wording.
    • When a charging session belongs to a vehicle with no home depot assigned, Charging Sessions shows an explicit unassigned-home-depot state instead of leaving depot meaning ambiguous.
    • Existing date-range, sorting, pagination, and current attribution-related fields remain available.

    Dependencies¶

    • None.

    Split Signals¶

    • New report filters, aggregations, or summary widgets beyond the current report contract are separate stories.

    Keep Vehicle Charging Summary aligned with Charging Sessions¶

    User Story¶

    As a finance or reporting user, I want Vehicle Charging Summary to use the same cross-depot meaning as Charging Sessions so that summary output does not conflict with session output.

    Acceptance Criteria¶

    • When Vehicle Charging Summary includes charging activity for vehicles away from home or visiting the selected site, the summary uses the same cross-depot meaning defined for Charging Sessions.
    • When Vehicle Charging Summary includes only local charging activity, the summary keeps the current local interpretation instead of adding cross-depot wording.
    • When Vehicle Charging Summary includes charging activity for a vehicle with no home depot assigned, the summary shows an explicit unassigned-home-depot state instead of leaving depot meaning ambiguous.
    • Existing summary navigation, date-range behavior, and current report interactions remain available.

    Dependencies¶

    • Show cross-depot meaning in Charging Sessions

    Split Signals¶

    • Any future attempt to align additional reporting surfaces to this contract should be shaped as separate stories instead of widening this one.
    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.