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.
| Rev | Description | Date |
|---|---|---|
| A | First issue | 2026-11-17 |
| B | Added integration hub and BizTalk mapping, item 9 | 2026-11-18 |
| C | Added concept render, view A | 2026-11-18 |
| D | Added hosted demo on Azure, note 1 | 2026-11-18 |
Parts list
| Item | Part number | Description | Status |
|---|---|---|---|
| 1 | LDM-DOC-001 | Business analysisThe need, as-is and to-be process, value case and KPIs | Document |
| 2 | LDM-DOC-002 | Solution architectureOrchestration vs. RPA, error handling, Blue Prism in production | Document |
| 3 | LDM-DOC-003 | Demo scriptA 15-minute walkthrough of every path through the process | Document |
| 4 | LDM-MDL-010 | Process modelThe executable BPMN for an engineering change request | Model |
| 5 | LDM-SYS-020 | System landscapeSubmit change requests and watch Jira, ERP and ServiceNow update | Checking |
| 6 | LDM-SYS-021 | Camunda Operate and TasklistFollow running changes and make the board decision (demo / demo) | Checking |
| 7 | LDM-SYS-022 | Legacy ERP screensThe screens the RPA bot works in, with no API (demo / demo) | Checking |
| 8 | LDM-SRC-100 | Source codeJava job workers, RPA bot, mock systems, process tests | GitHub |
| 9 | LDM-DOC-004 | Integration and BizTalkSupplier change notices through a message hub: XSD, XSLT maps, retries, and the BizTalk and Sentinet mapping | Document |
General notes
- Items 5–7 are live once the stack runs:
make localon your own machine, ormake azure-upfor a hosted copy on Azure that others can open. - Items 5–7 run on a hosted copy on Azure, rebuilt from the source in
item 8. Ask the presenter for the Camunda login. Locally the stack starts with
make local. - Volumes, times and costs in item 1 are assumptions to validate, not programme data.
- The RPA bot stands in for a Blue Prism digital worker. Item 2 explains the mapping.
- All tests run with
mvn verify: 8 process scenarios on a real engine and 10 unit tests.