Lindormen

The next fighter jet to come, and every engineering change that comes with it.

A fighter programme lives on engineering changes. This sheet indexes a working case study of how they are automated: a change request moves from Jira to an updated bill of materials, with Camunda orchestrating the work and an RPA bot entering it in the ERP. Pick a numbered item on the drawing or in the parts list.

RevDescriptionDate
AFirst issue2026-11-17
BAdded integration hub and BizTalk mapping, item 92026-11-18
CAdded concept render, view A2026-11-18
DAdded hosted demo on Azure, note 12026-11-18
Concept render of the Lindormen, a tailless delta-wing fighter in grey, flying above clouds and snowy mountain tops.
View A Concept render, AI-generated from the drawing below
Top view of the fictional Lindormen fighter, 17.2 m long with an 8.3 m span, with numbered callouts that link to the parts list 17.2 m 8.3 m 1 2 3 4 5 6 7 8 9

Parts list

ItemPart numberDescriptionStatus
1LDM-DOC-001 Business analysisThe need, as-is and to-be process, value case and KPIsDocument
2LDM-DOC-002 Solution architectureOrchestration vs. RPA, error handling, Blue Prism in productionDocument
3LDM-DOC-003 Demo scriptA 15-minute walkthrough of every path through the processDocument
4LDM-MDL-010 Process modelThe executable BPMN for an engineering change requestModel
5LDM-SYS-020 System landscapeSubmit change requests and watch Jira, ERP and ServiceNow update Checking
6LDM-SYS-021 Camunda Operate and TasklistFollow running changes and make the board decision Checking
7LDM-SYS-022 Legacy ERP screensThe screens the RPA bot works in, with no API (demo / demo) Checking
8LDM-SRC-100 Source codeJava job workers, RPA bot, mock systems, process testsGitHub
9LDM-DOC-004 Integration and BizTalkSupplier change notices through a message hub: XSD, XSLT maps, retries, and the BizTalk and Sentinet mappingDocument

General notes

  1. Items 5–7 are live once the stack runs: make local on your own machine, or make azure-up for a hosted copy on Azure that others can open.
  2. Volumes, times and costs in item 1 are assumptions to validate, not programme data.
  3. The RPA bot stands in for a Blue Prism digital worker. Item 2 explains the mapping.
  4. All tests run with mvn verify: 8 process scenarios on a real engine and 10 unit tests.