BCP Portal
BCP has started an interactive Alpha workflow demonstration focused on total-loss and post-incident EV battery coordination.
Alpha Pilot · Synthetic Data Only. Explore proposed Battery Passport, early OEM engagement, traceability and chain-of-custody workflows.
BCP Digital Platform
Switch stakeholder roles, create a demonstration case, request an OEM status package, open a Battery Passport and review an append-only custody history.
This interactive Alpha demonstrates proposed BCP workflows using synthetic data. It is not an operational emergency, regulatory, insurance, transport or battery-safety system.
Preparing the Foundation
The Alpha makes proposed coordination concepts tangible while keeping production systems, real records and controlled access out of scope.
Digital Product Architecture
The public Alpha demonstrates selected case-management and traceability concepts. Other product spaces remain in discovery or are planned for the future.
Case coordination
A future workspace for coordinating battery cases, decisions, evidence and handovers.
/portal/casesTraceability
A future infrastructure layer for battery identity, lifecycle events and chain-of-custody signals.
/portal/traceabilityCollaboration
A future collaboration environment for participating organisations, working groups and shared activities.
/portal/partnersWorkforce capability
A future access point for role-based learning, competency pathways and training resources.
/portal/trainingDecision intelligence
A future operational view of validated indicators, infrastructure activity and system learning.
/portal/dashboardKnowledge development
A future working environment for evidence, frameworks, contributions and controlled knowledge development.
/portal/workspaceExpansion Architecture
The architecture separates public storytelling, demonstration workflows, future application modules and shared services.
The website remains the authoritative public layer for the BCP story, knowledge and ecosystem engagement.
The public demonstration uses local synthetic data and is clearly separated from operational services.
Each future application retains its own route boundary, release lifecycle and product responsibilities.
Design tokens, components, accessibility, content language and navigation remain consistent across products.
Identity, permissions, data, audit and integration can be introduced when requirements are approved.
Public content, demonstrations, controlled workspaces and operational records remain distinct.
Current Boundary