Your IT needs to work.
Even when someone is absent.
Does one person hold the knowledge and access? Does a recurring fault interrupt work? I investigate the affected area, address the commissioned causes and configure access and recovery so your designated contacts can use them.
Who can keep things running when the key person is absent?
Knowledge held by one person
Knowledge and access hang on individual people. What happens if one of them leaves tomorrow?
Recurring faults
Saving, sign-in or data transfer keeps stalling. The cause has not yet been reliably isolated.
Untested recovery
Backups exist, but the required workflow has not yet been restored from them under agreed conditions.
Missing traceability
Changes and decisions remain non-transparent.
Unaudited access
Access rights that were never cleanly reviewed or removed.
Postponed updates
Updates that keep getting pushed back.
An initial assignment focuses on one of these areas. Systems, test cases and potential changes are agreed in advance.
What you can use
after the assignment.
Depending on the commissioned area, you receive tested corrections, configured access or a tested recovery procedure. The proposal defines scope and test criteria. Price on request.
The relevant assignment includes:
- Supported causes and clearly stated open questions
- Commissioned corrections tested against the affected workflow
- Agreed access with named owners and cover
- Recovery tests within the agreed scope, with results recorded
- Training and documentation for use and future changes
How I work
1. Assess the area
I examine symptoms, dependencies and responsibilities. You see what is supported by evidence and where further checks are needed.
2. Prepare the change
I establish the backup, test run, maintenance window and rollback procedure. The agreed change starts after your approval.
3. Implement and test
I implement the commissioned change and test the affected workflow with your contacts. Remaining limitations are recorded.
4. Hand over knowledge
Your team knows the access arrangements, responsibilities and procedure for a fault. Training and documentation support continued use without constant questions to me.
Two minutes to save a file.
Then 0.1 seconds.
I systematically isolated a recurring delay until a faulty network device was identified as the cause. After replacement, the workflow became reliable again.
The case study at ORVANIS shows the investigation, intervention and result. The figures relate to this specific case.