When is an inventory needed?
Problems we help solve
Without an up-to-date inventory, it is difficult to assess risk, plan a budget or quickly respond to a failure. We organise information that is usually scattered between the administrator, suppliers, invoices and employees' memories.
- There is no single list of servers, devices, systems and licences.
- It is not known which services are critical and what they depend on.
- Accesses, administrative accounts and providers are not described.
- The company wants to take control of the environment after changing suppliers.
- A modernisation or audit requires a reliable starting point.
Fit
Who is this service for?
Companies before the audit
We prepare basic data needed for environmental assessment.
Companies changing IT services
We organise the knowledge needed to safely assume responsibility.
Companies after years of development
We connect dispersed information about systems, equipment and suppliers.
Companies before modernisation
We determine what exists, what is dependent and what cannot be omitted.
Service scope
What does an IT inventory include?
Infrastructure
We describe the technical elements of the environment.
- servers, NAS, switches and firewall,
- computers and peripheral devices,
- network, addressing and locations.
Systems and services
We map applications and their dependencies.
- email, ERP, CRM and databases,
- cloud services,
- connections between systems.
Access and providers
We organise responsibilities and contacts.
- administrative accounts,
- internet, hosting and application providers,
- support scopes and contracts.
Risks and shortcomings
We indicate elements that need to be supplemented.
- lack of documentation,
- unknown passwords or owners,
- equipment and licences to be replaced.
Outcomes
What will you receive?
- an ordered list of the most important IT resources,
- description of systems, suppliers and dependencies,
- indication of gaps in documentation and liability,
- material for audit, modernisation or takeover of service,
- recommendations on which elements need to be clarified first.
The inventory can be light and practical, or more detailed if it is to support an audit, migration or modernisation plan.
Delivery approach
How is the service delivered?
- Scope. We determine which areas of the environment are to be described.
- Data collection. We analyse devices, systems, contracts and available documents.
- Verification. We check dependencies, owners and missing information.
- Rationalisation. We combine information into a clear structure.
- Conclusions. We indicate deficiencies, risks and quick corrective actions.
- Handover. We discuss documentation and how to continue maintaining it.
Delivery standards
How do we ensure usability?
- We describe information so that it is useful during failures and changes.
- We separate confirmed data from data requiring further verification.
- We do not create documentation for documentation's sake.
- We include suppliers because they are often part of the real maintenance process.
- We indicate who should update information after changes.
Cost
What determines the price?
Price depends on the number of devices, systems, locations, suppliers, level of detail of documentation and availability of source information.
FAQ
Frequently asked questions
Does the inventory include passwords?
It may include a description of how access is managed, but we only transfer sensitive data itself in an agreed and secure manner.
Do you need administrator access?
Yes, some information, but the scope can start with documents, contracts and conversations with responsible persons.
Does an inventory replace an audit?
No. The inventory describes what exists, and the audit assesses quality, risks and recommendations for changes.
Can it be updated later?
Yes. We prepare the documentation so that it can be developed after subsequent changes.
Will it help when changing IT providers?
Yes. This is one of the best times to organise your knowledge about the environment.