EDMS budget without surprises: how to calculate the total cost of ownership for 3–5 years
Licences for an electronic document management system are already included in the estimate, but this is not yet the project budget. Before deciding to launch, it is necessary to evaluate process configuration, archive migration, integrations, infrastructure, training, support, and future changes. The TCO model turns these components into a list of verifiable assumptions: what is one-off, what is recurring, what the amount depends on, and what data the vendor and internal team still need to provide.
First, define the boundaries of the TCO calculation
A financial model starts not with the final sum, but with the project boundary. It is necessary to determine which departments and users are included in the first phase, which document types are moving to the EDMS, how many environments are required, and which external systems will exchange data. Without this framework, two vendor proposals may look comparable, even though they actually cover a different scope of work.
For a working model, it is convenient to divide costs into four baskets. This division does not replace accounting classification, but it shows management where a figure is already confirmed and where it remains an assumption.
- One-off: design, configuration, initial connection, environment preparation.
- Regular: access to services, maintenance, hosting, backup, and administration.
- Variable: migration, training, customisations, and integrations, the volume of which depends on actual data.
- Unconfirmed: items without a commercial proposal, technical assessment, or process owner's decision.
CapEx and OpEx should be kept in separate columns as working categories. The final allocation must be confirmed by the finance department in accordance with the organisation's accounting policy and contract terms. The CIO's task is not to make an accounting conclusion, but to show the full composition of costs and the moment they arise.
Break down each item by its trigger condition
A single line "EDMS implementation" hides different pricing mechanisms. A licence depends on the delivery model and the number of users, migration depends on the state of the archive, and integration depends on systems, formats, and the parties' responsibilities. Therefore, each line of the estimate must contain not only the amount, but also the unit of estimation, data source, owner of the assumption, and the condition for recalculation.
| Item | Nature of cost | What to include | What to confirm |
|---|---|---|---|
| Right of use | One-off or regular | Licences, subscription, test and production environments | Licensing model, number of users, rules for volume changes |
| Implementation | Mostly one-off | Assessment, design, configuration of routes and templates | Boundaries of the basic package and list of separately paid works |
| Infrastructure | One-off and/or regular | Servers or cloud resources, storage, backup, monitoring | Requirements for capacity, availability, recovery, and volume growth |
| Integrations | One-off with subsequent maintenance | Connectors, APIs, gateways, exchange testing, and error handling | Number of systems, interface owners, limits, and change procedure |
| Migration | Variable | Inventory, cleansing, metadata mapping, transfer, and reconciliation | Volume, formats, source data quality, and acceptance criteria |
| Training and changes | One-off with repeated cycles | Training of administrators, key users, and preparation of instructions | Number of roles, training format, post-launch support |
| Maintenance and updates | Regular | Support lines, response times, new versions, and out-of-package works | Scope of services, SLA, tariff, and rules for its revision |
| Protection and compliance | One-off and regular | Requirements audit, access control, logging, checks, and documentation | Data categories, regulatory requirements, and responsible specialists |
It is not necessary to fill in all the amounts in the table immediately. A "requires assessment" mark is more useful than a nominal figure that no one can justify. After receiving proposals, such a matrix allows comparing the same scope, rather than just the totals on the last page.
Compare on-premises and cloud environments by cost structure
Cloud and on-premises deployment change the TCO structure, but neither in itself determines the cheaper option. For an on-premises environment, you need to consider hardware, system software, backup, operation, and updates. For a cloud one — resource consumption, data storage, backup, network traffic, administration, and tariff change conditions.
- Initial resources. What environments are needed for development, testing, training, and production.
- Growth. How the need for storage and capacity changes along with the archive and number of users.
- Recovery. Who is responsible for backups, recovery testing, and acceptable downtime.
- Operation. Which team administers the platform, monitoring, updates, and incidents after launch.
The Law of Ukraine "On Cloud Services" defines the roles of cloud service providers and users, but specific requirements depend on resources, data, and user status. Therefore, the budget should contain a separate task to define requirements for a specific project, rather than a ready-made conclusion transferred from another organisation.
Separately evaluate integration and regulatory assumptions
Resolution of the Cabinet of Ministers of Ukraine No. 55 approves the model instruction on documenting managerial information in electronic form and the regulations on electronic interaction of executive authorities. For institutions covered by these rules, this is a separate source of requirements for documents and exchange; they should not be transferred to other organisations without a legal review.
The cost of integration appears not only at the moment of connector development. It includes format alignment, test environment, authentication, logging, error reprocessing, and maintenance after one of the interfaces changes. The owner of each external system must confirm the availability of documentation, test data, and specialists for acceptance.
For the SEEAV (System of Electronic Interaction of Executive Bodies), the official procedure distinguishes between web access via a browser and programmatic connection of an internal EDMS via an API. These options differ in the scope of work. Before evaluation, you need to choose the connection method, check the joining procedure, the use of QES, and technical settings. The tariff page contains one-off and regular payments and their effective date, so the figures should be double-checked before approving the estimate.
- Data: information categories, storage location, periods, and access rules.
- Documents: attributes, templates, signing, versioning, and archiving rules.
- Exchange: connection type, formats, QES, testing, and responsibility for errors.
- Control: action log, differentiation of rights, backup, and evidence of procedure execution.
IQusion describes Megapolis.DocNet as a web-oriented system for working with documents, cataloguing, search, and electronic archive using QES and with the possibility of cloud deployment. When evaluating a specific configuration, it is worth separately checking the required modules, configuration scope, and external connections; the product page does not determine the full project budget.
Complete the budget with a list of unconfirmed parameters
Before defending the budget, each variable or unknown item must have an owner and a clarification date. If the vendor cannot name the sum yet, record the method of its determination: archive audit, technical assessment, pilot migration, integration specification, or commercial proposal. This allows separating the decision to start from an unjustified promise of a final price.
- What is included in the basic cost of implementation, and which configurations are evaluated separately?
- What support and update services are included in the regular payment and how is the tariff reviewed?
- What data is needed to estimate migration and how will the parties verify the completeness of the transfer?
- Who develops, tests, and maintains each integration after an external API changes?
- What infrastructure resources, environments, backup, and monitoring are included in the proposal?
- What requirements for data, access, signing, and archiving must a profile specialist confirm?
What should be defended is not a single figure, but a manageable model: confirmed amounts, recalculation rules, and open questions with responsible persons. Then management sees not just a funding request, but a cost control mechanism during the implementation and operation of the EDMS.
Frequently Asked Questions
How to budget for EDMS support if the vendor has not yet provided the final tariff?
Record the scope of services, unit of calculation, validity period of the proposal, and the date of re-verification. Until a commercial proposal is received, such an item should remain an unconfirmed assumption, not an exact sum.
Can an on-premises EDMS be immediately classified as CapEx, and a cloud one as OpEx?
No. CapEx and OpEx in the TCO model are working categories. The final classification of specific payments must be confirmed by the finance department according to the organisation's accounting policy and contract terms.
What do you need to know before estimating archive migration?
You need an inventory of sources, volume and formats of files, state of metadata, card mapping rules, acceptance criteria, and a method for control reconciliation after transfer.
