Just imagine: A tax audit is due. The tax auditor needs production data from 2019. The system that recorded this data back then was replaced in 2022. The data is in the archive - somewhere. The quality team submits an IT ticket. IT opens the ticket, prioritizes, searches for the archive, exports, converts and sends back a CSV. Three days later.
This is not an exceptional case. It is part of everyday life in manufacturing companies that see their data archive as an IT task rather than a departmental resource. IT becomes a bottleneck - not out of malice, but because archive access is structurally organized incorrectly.
This article analyzes the four access models for production data archives, identifies the technical requirements for genuine self-service and shows which model makes sense for which use case in production.
|
THE MOST IMPORTANT FACTS IN BRIEF
|
|
BRIEFLY SUMMARIZED
|
The problem: IT as a structural archive bottleneck
The archive bottleneck is not a technical problem. It is an organizational problem caused by a wrong technical decision: Data archives are managed as IT systems, not as departmental resources. The consequence is a dependency chain in which every data request runs through IT.
What typical archive access looks like today
|
01 Request is created Quality / Controlling / Sales |
02 Create IT ticket 10-30 min. department |
03 Prioritize ticket 1-3 working days waiting time |
04 Search archive 1-4 hours IT |
05 Export + conversion 30-120 min IT |
06 Clarify queries +1-2 days |
07 Transfer data Total duration: 3-7 days |
Seven steps for a request that would be completed in 30 seconds in a well-structured archive solution. This is no exaggeration. It is the measurable reality in companies without self-service archive access.
What this bottleneck really costs
|
Task type |
Tickets / year |
IT effort (h) |
Extrapolation of costs |
|---|---|---|---|
|
Retrieve production data from legacy system |
60-80 |
2-4 h |
9,600-28,800 €/year |
|
Batch verification for quality inspection |
40-60 |
1-3 h |
4,800-21,600 €/year |
|
Document reconstruction for tax inspection |
10-20 |
3-6 h |
3,600-14,400 €/year |
|
Archive data for customer complaints |
30-50 |
1-2 h |
3,600-12,000 €/year |
|
Legacy system access for audit |
20-30 |
4-8 h |
9,600-28,800 €/year |
|
Total overhead p.a. |
approx. 40,000 - 70,000 € p.a. Opportunity Cost IT |
||
WHAT ELSE THIS OVERHEAD COSTS - BEYOND THE MONEY
-
Delays in decision-making: Controlling waits 3 days for production data - and makes decisions based on incomplete information.
-
Audit stress: During audits, everyone runs to IT at the same time. This costs IT capacity precisely when it is most scarce.
-
Employee frustration: Departmental employees who have to open IT tickets for simple data retrieval systematically develop workaround strategies - shadow copies, local exports, email attachments.
-
Legacy system dependency: As long as IT handles archive access via the legacy system, the system cannot be switched off - even if it no longer fulfills any other functions.
|
3-7 days Typical waiting time for archive access CSP customer projects |
80-300 € Costs per IT archive ticket Incl. IT overhead |
65 % IT tickets could be solved self-service CSP analysis |
0 min. Waiting time with self-service archive CHRONOS practice |
A comparison of the four access models for data archives
|
MODEL 1 Status quo in most companies IT-centralized access |
|
|
All archive access is handled by IT. Departments submit tickets, IT searches, exports and transfers the data. The archive is an IT system with IT access logic. |
|
|
✓ Advantages
|
Disadvantages
|
|
Suitable for: Small IT organizations with few archive accesses p.a. Highly sensitive data without self-service capability. Verdict : Works - but does not scale and is expensive. |
|
|
MODEL 2 IT DELEGATES ACCESS TO KEY ROLES Delegated access |
|
|
Selected department employees ('key users', 'data stewards') receive direct archive access and serve as the first point of contact for their department. IT remains responsible for complex requests. |
|
|
✓ Advantages
|
✗ Disadvantages
|
|
Suitable for: Medium-sized companies with defined specialist departments. Good intermediate step in the migration to self-service. Verdict : Good compromise - but not the final solution. |
|
|
MODEL 3 SPECIALIST DEPARTMENT ACCESSES DIRECTLY - WITHOUT IT Self-service archive access |
|
|
Every authorized department employee can directly access the archive data released for their role - via a simple interface, without a ticket, without waiting time. All accesses are fully logged. |
|
|
✓ Advantages
|
Disadvantages
|
|
Suitable for: Companies with a high archive access volume, clear role structures and the goal of switching off legacy systems. Verdict : The target state for most production companies. |
|
|
MODEL 4 SELF-SERVICE + IT CONTROL ACCORDING TO DATA SENSITIVITY Hybrid access model |
|
|
Archive data is classified according to sensitivity: Routine production data and quality data are accessible via self-service, highly sensitive data (personnel data, contract documents, financial data) remain IT-controlled. |
|
|
✓ Advantages
|
Disadvantages
|
|
Suitable for: Large production companies with a heterogeneous database and different compliance requirements for each data type. Verdict : Best practice for companies with 500 or more employees. |
|
Role matrix: Who needs access to what in production?
The most frequent failure of self-service archive projects has a single reason: the role matrix was not created. Without a clear answer to the question "Who can see what?", self-service either remains a security risk or is implemented so restrictively that it adds no value.
The following matrix shows typical roles in production companies with the recommended archive access in each case.
|
Role / data type |
Production logs |
Batch records |
Quality data |
Financial accounting documents |
Employee data |
Supplier data |
|---|---|---|---|---|---|---|
|
Quality manager |
✓✓ Self-Serv. |
✓✓ Self-Serv. |
✓✓ Self-Serv. |
○ Read access no. |
- |
○ Read access no. |
|
Production manager |
✓✓ Self-Serv. |
✓✓ Self-Serv. |
✓ restricted |
- |
- |
○ Read access no. |
|
Shift leader |
○ Reading access no. |
✓ restricted |
- |
- |
- |
- |
|
Controlling |
- |
- |
✓ restricted |
✓✓ Self-serv. |
- |
- |
|
Distribution/CS |
- |
- |
✓ restricted |
- |
✓✓ Self-Serv. |
- |
|
HR department |
- |
- |
- |
- |
✓✓ Self-Serv. |
- |
|
purchase |
- |
- |
- |
- |
- |
✓✓ Self-Serv. |
|
Data protection officer |
○ Read access no. |
○ Read access no. |
- |
- |
✓✓ Self-Serv. |
- |
|
External auditor (audit) |
○ Read access no. |
○ Read access no. |
○ Read access no. |
○ Read access no. |
- |
- |
|
IT administrator |
✓✓ Admin |
✓✓✓ Admin |
✓✓✓ Admin |
✓✓✓ Admin |
✓✓✓ Admin |
✓✓✓ Admin |
|
Legend: ✓✓ = Self-service unrestricted ✓ = Self-service with date limitation/project binding ○ = Read access with log entry - = no direct access, IT ticket required |
||||||
PRACTICAL TIP: HOW TO CREATE THE ROLE MATRIX
Step 1: Workshop with department heads - Which archive data do you need and how often? What for?
Step 2: Data categorization according to sensitivity (public / internal / confidential / strictly confidential)
Step 3: For each combination of role × data category: self-service, restricted access or IT ticket?
Step 4: Legal check - which accesses require data protection agreements (e.g. employee data)?
Step 5: Technical implementation in the archive solution - configure access rights according to role matrix
Experience: A complete workshop takes 2-4 hours. This saves years of IT tickets.
Five technical requirements for genuine self-service archive access
Self-service archive access is not a question of goodwill. It is a question of the technical foundations. If one of these five prerequisites is missing, self-service becomes a security or compliance risk - or simply cannot be used.
Prerequisite 1 - Open, manufacturer-independent archive format
|
Without this requirement Departments can only open data if the original system is still running. Legacy system remains active - exclusively as an archive access tool. |
With this requirement Archive data is in an open, standardized format (e.g. CSV, XML, PDF/A) - readable with any standard tool, without special software or a running source system. |
|
Why this counts: This is the most common cause of forced legacy system runtimes: The system is no longer running for its function - but only so that someone can open the archive data. |
|
Prerequisite 2 - Role-based access control (RBAC)
|
Without this prerequisite Everyone sees everything or no one sees anything. IT refuses to introduce self-service because they have no differentiated control. |
With this requirement Each role has precisely defined read authorization to exactly the data categories it needs for its work. Other data does not technically exist for this role. |
|
Why this matters: Without RBAC, self-service archive access is a data protection breach in waiting. With RBAC, it is often more secure than IT-centralized access - because access is logged. |
|
Requirement 3 - Complete audit trail of all accesses
|
Without this prerequisite No one knows who has accessed which archive data and when. Compliance requirements cannot be met. |
With this requirement Every access to archive data is logged automatically and unalterably: Who, when, which data, for how long. The audit trail itself is audit-proof. |
|
Why this counts: Paradoxically, many companies do not have a complete audit trail in the IT-centric model - because IT accesses are often not logged individually internally. Self-service with logging is often more transparent. |
|
Requirement 4 - Simple, browser-based search interface
|
Without this requirement Department employees cannot technically find archive data - they do not know how to use the archive CLI. Self-service fails due to usability. |
With this prerequisite An intuitive search interface - comparable to an internal Google search - enables every department employee to find archive data by date, batch, order number or customer number. |
|
Why this counts: The technically best archive is worthless if the quality manager searches for 20 minutes and then opens an IT ticket after all. Usability is not an optional extra - it is the basic requirement for acceptance. |
|
Requirement 5 - Export function for standard formats
|
Without this prerequisite Department employees cannot transfer archive data to their working environment. Data can be found but cannot be used. |
With this requirement One-click export to Excel, PDF, CSV or XML - without IT involvement, without conversion effort. The department receives the data in the format it works with. |
|
Why this counts: The last mile of self-service is often forgotten: Finding data is good, being able to use data is the goal. Without a simple export, the ticket still ends up in IT. |
|
Security and compliance for departmental access
The most common objection to self-service archive access comes from IT or the data protection officer: 'If everyone can access the archive, we lose control'. This objection is justified - but only if self-service is implemented incorrectly.
When implemented correctly, self-service archive access is often better than IT-centralized access from a security perspective. The reason: in the IT-centralized model, an IT employee accesses many data categories - and this access is not always logged individually. In the self-service model, each user only accesses their defined data categories - and each access is logged automatically.
|
Security aspect |
IT-centralized model |
Self-service model |
|---|---|---|
|
Breadth of access |
IT employee sees all data |
Business department only sees approved categories |
|
Logging |
Often summarized: 'Ticket processed' |
Fully automatic: who, what, when, how long |
|
Risk of incorrect access |
High: IT could provide incorrect data |
Low: technically limited to permitted data |
|
GDPR compliance |
Dependent on IT discipline |
Technically enforced by RBAC |
|
Auditability |
Medium: manual documentation |
High: automatic, unchangeable trail |
|
Response time in the event of a security incident |
Slow: IT ticket for blocking |
Immediate: Access rights can be revoked centrally |
Legacy systems and archive access: The hidden dependency cycle
There is a structural reason why many legacy systems in production companies continue to be operated for years after their actual replacement: They serve as archive access tools. The function of the system is done - but without the system, no one can open the historical data.
This is a cycle: The legacy system is not shut down because you still need to access the data. The data is not migrated because the legacy system is still running. The legacy system costs licenses, maintenance, security patches and IT capacity - for a single function: archive access.
WHAT A LEGACY SYSTEM THAT CONTINUES TO RUN AS AN ARCHIVING TOOL REALLY COSTS
-
License costs: Outdated ERP systems, MES or quality software typically cost €20,000-80,000 p.a. in end-of-life phases - often for maintenance contracts without further development.
-
IT costs: Keeping a system alive means security patches, infrastructure, backup - even if it only has an archive function. Typically 0.2-0.5 FTE IT expenditure p.a.
-
Security risk: End-of-life systems are no longer supplied with updates. Every connection to the network is a potential gateway - just so someone can call up production data from 2017.
-
Knowledge dependency: who still knows how to use the old system? With every change of employee, the risk increases that no one can navigate the system.
The solution is not to continue operating the legacy system. The solution is to migrate the data to a manufacturer-independent, self-service-capable archive - then the system can be switched off.
The most expensive legacy systems in production companies are not those that are still in active use. They are the ones that only run so that someone can call up archive data once a month.
-Korbinian Hermann Managing Director, CSP Intelligence GmbH
CHRONOS: Self-service archive access for production data in practice
Frequently asked questions
