Batteries and fuel cells
Operational Reality

Sample War Map

Batteries and fuel cells War Map

Battery-pack manufacturer scaling from pilot to series · 1 plant in Hauts-de-France · 140 employees

Output is meant to double by December, but engineering changes take 23 days to reach the line and cell traceability for one line still lives in CSV files. A shortage list rebuilt by hand each morning decides what gets built.

A War Map is an operating map built from real cases and expert interviews. It shows where the business is fragile, what that costs, and what to fix first.

What you receive

  1. 01Operational Reality

    How the work really runs: people, systems, handoffs and exceptions.

  2. 02Findings

    What it costs: quantified problems, process gaps and key-person risks.

  3. 03Implementation plan

    What to fix first: prioritized systems, timeline and value drivers.

Request a Strategy Session

30 minutes. We recommend the right starting point.

Read the sampleSee all industry War Maps

Battery-pack manufacturer scaling from pilot to series · 1 plant in Hauts-de-France · 140 employeesThis War Map shows how we turn an operational review into an implementation plan. The dates show a possible sequence; the scope and schedule of a real engagement are agreed with you.

Operational Reality

This is what we deliver: a map of where the business is fragile, what it costs, what to automate first, and which systems should exist so leadership can stop carrying the operation by hand.

Illustrative five-week work plan, June 1 to July 3, 2026. Eleven interview roles across nine departments, three assembly lines and seven systems. The final week covers validation and handover.

Engineering change lead time
23 days
from approval to effective on the line, against 10 planned
Rework from outdated BOMs
46 packs
built on a superseded revision after 3 changes last quarter
Traceability for one pack
2 days
to rebuild the cell history of a line-3 pack for a customer
11
Team members interviewed
across 9 departments
7
Systems accessed
2 with critical gaps
17
Workflows documented
12 with manual exceptions
25
Friction points identified
6 classified as critical

Five-week sample timeline · five work blocks

One row per week. Open a week to see each working day.

  1. Week 1
    Jun 1 to Jun 5

    Ramp-up leadership and the line

    Scope set against the ramp-up plan. Lines, shortage meeting, engineering changes and test benches shadowed.

    People: Antoine Mercier, Lucie Bertin, Florian Meyer, Sarah Kone, Yann Le Goff, Damien Petit, Hugo Lambert

    Daily detail · 5 days
    Jun 1
    Kickoff + Scope Alignment

    Agreed scope against the ramp-up plan: 450 packs a month today, 900 targeted by December. Chose engineering changes, shortages, traceability and customer documents as priority flows.

    Antoine Mercier · CEO and Co-founder
    Business CentralExcel
    Jun 2
    Line Walk and Shift Handover

    Walked the three assembly lines. Lines 1 and 2 record cell-to-module genealogy in the MES. Line 3, added in January, saves barcode scans to CSV files on a station PC.

    Florian Meyer · Production Manager
    MESTest data
    Jun 3
    Morning Shortage Meeting

    Sat in the 8:30 shortage meeting. 31 part numbers on the list, 9 with no confirmed supplier date. Sarah had rebuilt the list by hand from 6:45 using Business Central and supplier emails.

    Sarah Kone · Supply Chain Manager
    Business CentralExcelTeams
    Jun 4
    Engineering Change Lifecycle

    Traced an engineering change: approved in Jira, BOM revised in PDM, then retyped by hand into Business Central, work instructions and the MES routing. About 14 changes a month during ramp-up.

    Yann Le Goff · Engineering Director
    JiraPDMBusiness Central
    Jun 5
    Test Benches and Data

    End-of-line results are saved as CSV files on bench PCs. For lines 1 and 2, a nightly script links them to serial numbers. For line 3, the link is made by hand.

    Hugo Lambert · Test and Validation Engineer
    Test dataMES
  2. Week 2
    Jun 8 to Jun 12

    Quality, customers, shipping and funding

    PPAP, customer, dangerous goods and grant flows mapped. One traceability request replayed end to end.

    People: Inès Chabert, Pauline Royer, Kevin Da Silva, Marion Aubert, Hugo Lambert

    Daily detail · 5 days
    Jun 8
    PPAP and Sample Requests

    9 PPAP packages open for 4 customers, tracked in Excel. Each needs up to 18 elements. Most of the delay comes from chasing the latest controlled version of each document.

    Inès Chabert · Quality Manager
    ExcelPDMTeams
    Jun 9
    Customer Programme Reviews

    Weekly customer status reports are built by hand from Business Central, the shortage list and the MES. Delivery promises change after each shortage meeting.

    Pauline Royer · Customer Programme Manager
    TeamsBusiness CentralExcel
    Jun 10
    Dangerous Goods Shipping

    About 35 shipments a week of class 9 lithium batteries (UN3480 and UN3481). Each needs the right UN38.3 test summary. Pre-production prototypes ship under special provision 310 with separate paperwork.

    Kevin Da Silva · Logistics and Dangerous Goods Coordinator
    Business CentralExcel
    Jun 11
    Grant Reporting

    The company receives France 2030 support with a milestone report every six months. Each report takes Marion about 110 hours: timesheets by work package, invoices and evidence.

    Marion Aubert · Finance and Grants Controller
    Business CentralExcel
    Jun 12
    Traceability Request Replay

    Replayed a recent customer request for the cell history of one line-3 pack. It took 2 days elapsed and 3 person-days: scan files, bench CSVs, incoming cell tests and supplier lot certificates.

    Inès Chabert · Quality Manager
    MESTest dataExcel
  3. Week 3
    Jun 15 to Jun 19

    Follow-up shadowing and data analysis

    One change followed to the line. 3 months of change, shortage and line-stop data analysed.

    People: Damien Petit, Florian Meyer

    Daily detail · 5 days
    Jun 15
    Following One Change to the Line

    Followed a busbar change from approval to first pack: 26 days. The new part arrived on day 12. Work instructions and the MES routing were updated on day 24.

    Damien Petit · Manufacturing Engineering Lead
    JiraPDMMES
    Jun 16
    Second-Shift Shadow

    Spent the afternoon shift on line 3. Two stops for missing parts, and one for a work instruction that did not match the parts delivered.

    Florian Meyer · Production Manager
    MESTest data
    Jun 17
    Engineering Change Data

    Analysed 42 changes from the last 3 months: 23 days on average from approval to effective, and 3 changes built on a superseded BOM, leading to 46 reworked packs.

    JiraBusiness Central
    Jun 18
    Shortage and Line-Stop Data

    Analysed 3 months of shortages and stops: 31 hours of line stops for missing parts, 64% of them on parts with a confirmed date that slipped.

    Business CentralMES
    Jun 19
    Process Map Construction

    Built process maps for all 17 workflows and compared each one with the written process.

  4. Week 4
    Jun 22 to Jun 26

    Internal Analysis

    7 opportunities scored, value modelled and the battery passport gap assessed.

    People: No interviews this week

    Daily detail · 5 days
    Jun 22
    Opportunity Scoring

    Identified 7 opportunities across 4 departments. Scored each by complexity, value, dependencies and who signs off.

    Jun 23
    Battery Passport Gap Review

    Compared current data with what the EU Battery Regulation requires for industrial batteries over 2 kWh from February 2027. Line-3 traceability is the main gap.

    Jun 24
    Value Model

    Modelled released capacity, rework avoided, line stops avoided and margin brought forward. Kept revenue timing separate from capacity.

    Jun 25
    Roadmap Design

    Sequenced shortages and documents first, the BOM flow next, and line-3 traceability as the base for the passport.

    Jun 26
    Internal QA

    Checked every figure against interviews and data extracts. Removed overlaps between friction rows.

  5. Week 5 · Handover
    Jun 29 to Jul 3

    Validation and handover

    Findings validated with the leads. War Map delivered and first initiatives agreed.

    People: Lucie Bertin, Yann Le Goff, Sarah Kone, Inès Chabert, Marion Aubert, Antoine Mercier

    Daily detail · 5 days
    Jun 29
    Validation with Operations Leads

    Walked through maps, friction rows and the roadmap. Yann asked that effectivity dates stay an engineering and production decision. Plan updated.

    Lucie Bertin · COO
    Jun 30
    Validation of Finance Figures

    Checked rework cost, freight and grant figures against the ledger. Agreed to show margin brought forward as a separate line.

    Marion Aubert · Finance and Grants Controller
    Business CentralExcel
    Jul 1
    Final QA

    Final pass on numbers, wording and the roadmap. Prepared handover material.

    Jul 2
    Pre-Handover Review

    Reviewed findings and priorities against the ramp-up plan and the battery passport deadline.

    Antoine Mercier · CEO and Co-founder
    Jul 3
    Final Handover + War Map Delivery

    Delivered the War Map. Agreed on the first three initiatives and a named owner for each.

    Antoine Mercier · CEO and Co-founder

What We Heard

“

“We planned to double output this year. Every week the same three things slow us down: a part, a change, a document.”

Lucie Bertin, COO
“

“My morning starts with a list nobody trusts, so I check it line by line before the 8:30 meeting.”

Sarah Kone, Supply Chain Manager
“

“An engineering change is approved in a day. Getting it into the BOM, the instructions and the stock takes more than three weeks.”

Yann Le Goff, Engineering Director
“

“When a customer asks for the cell history of one pack from line 3, I lose two days and Hugo loses one.”

Inès Chabert, Quality Manager
“

“Each grant report takes me nearly three weeks. Most of it is finding timesheets and matching invoices to work packages.”

Marion Aubert, Finance and Grants Controller

Team Members Interviewed

AM
Antoine Mercier
CEO and Co-founder · Executive
LB
Lucie Bertin
COO · Operations
YL
Yann Le Goff
Engineering Director · Engineering
HL
Hugo Lambert
Test and Validation Engineer · Engineering
IC
Inès Chabert
Quality Manager · Quality
FM
Florian Meyer
Production Manager · Production
DP
Damien Petit
Manufacturing Engineering Lead · Production
SK
Sarah Kone
Supply Chain Manager · Supply Chain
KD
Kevin Da Silva
Logistics and Dangerous Goods Coordinator · Logistics
MA
Marion Aubert
Finance and Grants Controller · Finance
PR
Pauline Royer
Customer Programme Manager · Programmes

Systems Accessed

Microsoft Dynamics 365 Business CentralERP
Automatic
Purchasing, stock, sales and costing work. BOMs updated by hand from PDM. No feed of supplier confirmations.
SolidWorks PDMEngineering data
Automatic
Drawings and BOM revisions under version control. No link to Business Central or the MES.
JiraEngineering change tracking
Manual
Action needed
Engineering changes approved here. Downstream implementation tracked in comments and emails.
MES (in-house, built for the pilot line)Manufacturing execution
Broken
Action needed
Genealogy for lines 1 and 2. Line 3 runs outside it, with barcode scans saved to CSV files.
End-of-line test benchesTest results
Manual
Action needed
Results saved as CSV files on bench PCs. Linked to serial numbers nightly for lines 1 and 2, by hand for line 3.
ExcelOperational layer
Manual
Action needed
Shortage list, PPAP tracker, grant reporting and dangerous goods checklist.
Microsoft TeamsCollaboration
Automatic
Daily meetings and customer channels. Decisions on shortages and changes stay in chat threads.
Automatic
Manual
Broken
Next Chapter
Findings

Strategy Session · 30 min

A real engagement is scoped in the Strategy Session and may begin with a War Map or a bounded Feasibility Sprint.

Request a Strategy Session