JCIM
JCIM led
- Controlled project-room architecture
- Workflow and access governance
- Platform operation, support and onboarding
Bosch · ECU software configuration platform
Enabling customer self-service without exposing protected ECU know-how
Custom ECU changes moved through email, quotation, resource planning, development, testing and patch delivery. At the same time, every participant needed to protect source code, compiler environments and proprietary engineering knowledge.
USERCustomer workspaceapproved actions
CONTROLLABLE GLASS SCREEN
Rights follow the workflow
PROTECTEDTools · Compiler · IPnot exposed
JCIM / INDUSTRIAL SYSTEM EVIDENCEREF 06–A
01Within a day
02Protected IP
03Governed self-service
The challenge
- A customer request could take weeks or longer to pass through the full organisational chain.
- Customers had little visibility into timing and quality while sales, engineering and commercial administration all had to participate.
- Multiple parties needed to collaborate on one software artefact without disclosing more intellectual property than necessary.
What JCIM did
- 01
JCIM designed a controlled shared project room in which users could perform approved work without receiving unrestricted access to the underlying environments.
- 02
JCIM embedded the existing configuration software and compiler tools into a governed workflow rather than replacing tools that already worked.
- 03
The access layer behaved like a controllable glass screen: users could interact with the process, while the platform decided which actions were allowed to reach protected systems.
- 04
JCIM reused existing business context and perimeter controls so rights followed the approved workflow instead of creating a second, disconnected authorisation universe.
- 05
JCIM operated and supported the platform and invested heavily in onboarding external users so self-service remained controlled and repeatable.
Responsibility boundary
BOSCH / PARTNERS
Bosch / partners brought
- Specialist tools and protected know-how
- Approved business context
- Configuration and compiler environments
What changed
Selected feature-change processes moved from weeks of organisational coordination to a controlled workflow that could be completed within a day.
Customers could initiate and progress approved changes directly instead of starting every request with an email and quotation cycle.
The platform supported collaboration between parties that needed to work together but could not expose their complete source code or engineering environments to one another.
05
Human Logic
The solution did not ask the parties to trust one another more. It made collaboration possible while assuming that trust would remain limited. Every participant gained enough access to complete the job, but not enough to compromise the others’ protected knowledge.
06
What this proves
This case shows how JCIM turns bespoke engineering work into a governed service: preserve specialist tools, remove organisational overhead and make the repeatable path visible and controllable.
NEXT PROOF
Bring us the industrial problem that does not fit neatly into one department.
We will identify the smallest real proof that can turn uncertainty into a controlled management decision.