Scalatris
ENGINEERED TO ELEVATE ISSUE #16
THE FACTORY FORWARD · 15 SEPTEMBER 2026 · 5 MIN READ, DESIGNED TO RUN IN 30
Your production constraint may be nowhere near the machine.
▸ FIELD NOTE. A filed 8-K, a Regulation 30 letter, and fifteen days to full restoration.
▸ TOOL TO TRY. The Dark-Shift Test: one order, one whiteboard, thirty minutes.
▸ THIS WEEK'S NUMBER. 15 days, from the company's own filing.
I said last week we would stay with the mandate. We will. Something happened in between that deserves the floor first.
On 25 August, Boston Scientific identified a cybersecurity incident. The network outage that followed cut access to business applications, and the company says that affected its ability to manufacture, process customer orders and ship them. Its assessors found no evidence that the manufacturing systems themselves were compromised. Fifteen days later, on 9 September, it said manufacturing, order fulfilment and shipping were fully restored.
THE GAP
What the assessors found vs. what the filing says stopped.
MANUFACTURING SYSTEMS
No evidence of compromise
Independent assessors, company update, 9 September.
ORDER TO GATE
Manufacture, process and ship: impacted
Form 8-K, Item 1.05, filed 8 September.
OUR READING
The failure point did not begin at a machine. It began in the systems that turn capacity into a shipment. That is the operating lesson.
Both columns quoted from the company's own filing and update. The reading is ours, not the company's.
ONE FIELD NOTE
The event
What happened. The 8-K, filed 8 September, says the outage "impacted the Company's ability to manufacture as well as process and ship customer orders", and that the company will miss its guidance for the quarter and the year. It will put a number on that on 28 October.
What it costs to skip this. Jaguar Land Rover, owned by Tata Motors, disclosed a cyber incident on 2 September last year; production returned to normal only by mid-November. Its CFO put the cost at around 50,000 units, plus £260 million of exceptional charges before lost sales, with no cyber insurance. Bajaj Auto disclosed a ransomware attack on 23 June, told the exchanges three days later that manufacturing and sales were operating normally, and later told analysts it had suspended operations for a few days as a precaution.
The wrong diagnosis
The reflex is to file this under IT. Ring the vendor, check the backups, ask about the firewall. Do that. It is still not the operating problem.
The operating problem is that between a customer's order arriving and a truck leaving your gate there is a chain of screens, logins, files and people, and nobody has tested it one link at a time. An attack is one way to break a link. So is a dead laptop, a portal that is down, or the person who holds the GST login being on leave the day the order is due.
Walk the chain as it actually runs, not as the org chart describes it.
The order arrives on email or WhatsApp and is keyed into Tally or the ERP by one person. Planning lives in a spreadsheet, or in one planner's head. Material confirmation is the stock ledger on the same machine. Quality release is a signature, or an entry in a system only the QC head logs into. The invoice comes out of Tally. For many goods movements above ₹50,000, an e-way bill has to exist on the government portal before the truck moves, subject to the GST rules and exceptions that apply to you. That is one more login on one more machine. The gate pass prints from the same office PC. The transporter is booked on WhatsApp from the dispatch supervisor's own phone.
Count the single points. One Tally machine. One GST login. One planner. One phone. None of them is on the shop floor. All of them stand between a finished pallet and a customer.
Our reading: this is dependency concentration, and size does not protect you from it. Boston Scientific had outside responders and still needed fifteen days. In a smaller plant the exposure can be sharper when access, files and process knowledge sit with one person.
ONE TOOL TO TRY
The Dark-Shift Test
Pick one live customer order due to ship this week. Trace it from receipt to gate exit. At every step, write the system, the login, the file and the person it needs. Circle anything with one owner, one copy or one way in. Beside each circle, write what would move the order tomorrow if that dependency disappeared.
This is not a new discipline; anyone who has run a process FMEA or a continuity plan will recognise the shape. The difference is scope: one real order, three people, one whiteboard, thirty minutes, and the question asked of the office chain rather than the machines.
Default chain, to adapt:
Order received → Planning → Production release → Material confirmation → Quality release → Invoice → E-way bill and compliance → Gate pass → Transporter handoff
At each step, six questions. What system? Whose login? Is there a second authorised user? Is there an offline or printed copy? What is the manual fallback, and who can approve it? How long before shipment stops?
Run it Monday
No software, no consultant.
Pick the order. One real order due this week, the one the customer will ring about. (5 minutes)
Three people, one whiteboard. The planner, whoever raises invoices and e-way bills, and the dispatch supervisor. Draw the chain as boxes. (10 minutes)
Circle. Every box with one owner, one copy or one way in. (5 minutes)
Write the fallback beside each circle. One sentence, such as "Second user on the e-way portal, activated today." If you cannot name one, leave it blank. The blank is the finding. (10 minutes)
One line for the MD. "Order [number] stops at [step] if [dependency] is unavailable. Fallback: [what you wrote, or none yet]."
That line is the deliverable.
Step 3 does the work. One owner is not a problem by itself. One owner with no second way through is.
Optional AI assist. To tidy the chain before the session, paste this into a company-approved tool with customer names and prices removed. The whiteboard remains the test.
Help me structure one customer order's path from receipt to gate exit. The steps, in my own words: [PASTE]
For each step, the system, login, file and person involved, or UNKNOWN: [PASTE]
1. Rewrite the steps as a numbered chain. Add nothing I did not describe.
2. Under each step, list the system, login, file and person. Keep UNKNOWN as UNKNOWN.
3. Flag every step with one owner, one copy or one way in as SINGLE POINT.
4. For each SINGLE POINT, suggest one manual fallback for a person to check.
5. End with what I must verify in person.
This is a draft for a whiteboard session, not a finding.What good looks like
Good is not a second ERP or a standby server. Some of the gaps this test exposes may need little capital: a documented fallback, a second authorised user, a current offline copy, or clarity on who can approve the manual route.
Four low-cost controls are worth checking first: a printed open-order list refreshed weekly; a book of pre-numbered manual gate passes; a second authorised user on every portal you ship through; and a current offline copy of the books, stored separately and checked periodically. They do not close every gap. They show you, cheaply, which gaps are open.
None of that is capex. Diagnosis first, then a list.
YOUR ONE MOVE THIS WEEK
Run the Dark-Shift Test on one order before the truck for it is booked.
Thirty minutes, three people, one whiteboard, one line for the MD. Nothing to download, nothing to install.
If you run it, reply with the category of your first single point: login, laptop, person, portal or spreadsheet. No names, no company.
THIS WEEK'S NUMBER
15 days
From the day Boston Scientific identified the incident to the day it said manufacturing, order fulfilment and shipping were fully restored. Restoration was progressive.
Source: Boston Scientific Form 8-K, Item 1.05, filed 8 September 2026; company update, 9 September 2026.
WHAT WE DO NOT KNOW
There is no public data on how often this happens to Indian plants below the listed-company line. Bajaj Auto has not said which systems were affected. Boston Scientific has not said how it was entered or what it cost.
COMING NEXT TUESDAY
Back to the mandate. August was the softest month for Indian factory orders in five years and the first in thirty with job cuts. Next week: the mandate that gets pulled back after one bad month, and whether the report you wrote for good months said less than you thought.
P.S. Run the test again after every new system, every new portal, and every time the person holding a login changes.
Until next Tuesday,
Sachin
Founder, Scalatris LLP · scalatris.com