01
Settings history
Every change to engine, inventory, auto-assembly and approval settings, field by field.
Silent Setting Change
Someone changed a setting and nobody noticed.
A tolerance loosened, an approval limit raised, a detector switched off — one quiet change can undo every control behind it. Otiox's Model Studio records every change to engine, inventory and approval settings field by field, lets you add the reason, and can require a second person to approve rule and matching changes before they apply.
app.otiox.comFig. 00
Command · model studio
Every change, with a reason
Settings history and approvals
SettingChanged byReason
Approval of model changesOwnerAudit request
Matching toleranceProposedAwaiting approval
Detector thresholdOwnerToo noisy
Second approver required
Propose
Changes apply after someone else approves.
Every control change has an owner and a reason.
01The Challenge
The control was there. Then someone turned it off.
Approval thresholds and matching tolerances are changed in a settings screen with no reason asked and no trace kept. When the audit asks who changed it and why, there is no answer.
- 01Settings changed without a trace
- 02No reason recorded
- 03One person can loosen any control
- 04No version of 'how it was'
02SEE IT IN OTIOX
The same situation, in the product.
Real screens from the Otiox demo workspace, step by step.
- 01
Settings history with reasons
Each change with who, when and the reason added to it.
03
How It Works
Purpose-built features that solve these exact problems.
02
Reasons
Add the reason afterwards; it is kept with the change.
03
Second approver
When on, rule and matching changes are proposed, approved by someone else — never the author — then activated.
04
Versions
Each activation is a new model version; decisions and predictions record the version in force.
04
What You'll Gain
Tangible improvements that impact your bottom line.
- 01Four-eyes control
No one loosens a rule alone.
- 02Answers for the audit
Who, when, what and why.
- 03Reproducible results
Every prediction tied to the model version.
- 04Calm changes
Proposals reviewed before they apply.
05
Real-World Scenarios
See how this works in practice.
Scenario 1
Loosened tolerance
A matching tolerance is widened to clear exceptions.
Scenario 2
Approval limit raised
A purchase approval threshold goes up quietly.
Scenario 3
Detector switched off
A noisy check is disabled without discussion.
06
The Transformation
From chaos to clarity.
Before
- Changes leave no trace
- No reason kept
- One person, full control
- No versions
After
- Every change recorded
- Reason attached
- Second approver required
- Each change a new version
07
Frequently Asked Questions
Quick answers to common questions.
01Which settings are tracked?
Integrity and predictive engine settings, detector thresholds, inventory, auto-assembly, approval rules and matching tolerances — from the day recording was turned on.
02Can the author approve their own change?
No. Approval must come from someone else.
03Who can propose or approve?
Team permissions: Model changes — propose, and Model changes — approve.
04Is anything recorded before it was turned on?
No; the page says earlier changes were not kept anywhere.
Silent Setting Change
Ready to transform your silent setting change?
See how Otiox can solve your specific challenges.