ERP Investment and TCO Pre-assessment Tool

Number of legal entities

Entity count affects consolidation, authorisation and reporting complexity.

Locations

Multiple sites change stock ownership, transfers and authorisation design.

Number of plants

Each plant brings its own work centres, capacity and costing setup.

Number of warehouses

As warehouses grow, bin management and counting discipline become necessary.

Number of countries

Each country means separate statutory rules, currency and reporting.

Group company structure

A group structure raises intercompany movement and shared data ownership.

Consolidation requirement

Consolidation requires the chart of accounts and reporting level to be defined up front.

Total headcount

Sets the scale of the training plan and change management.

ERP user count

A direct input to the licence line and to role-based authorisation.

Concurrent users

Some products license by concurrency; it also drives hardware sizing.

Mobile user requirement

Mobile use requires a separate interface and an offline behaviour decision.

Field sales users

Field use brings offline working and synchronisation design.

In-house capacity to change reports and screens

Without in-house capacity every small change becomes a consultancy line and annual cost turns unpredictable.

Company type

You can select more than one.

Select at least one option to continue.

Manufacturing type

Mixed-mode manufacturing cannot run on a single rule set; it produces the highest complexity.

Bill of material

Multi-level, versioned or order-time structures change the costing design.

Routings

Without routings, operation time and work centre cost cannot be attached.

Work centres

Without work centre hourly cost, actual cost cannot be calculated.

MRP

MRP gives no reliable output without clean BOMs and realistic lead times.

Capacity planning

Capacity planning needs work centre shift and efficiency data.

Advanced planning / APS

In most products APS is a separate module or product; licence and scope must be asked separately.

Lot / serial traceability

Traceability can be added to past data only as far as the source data allows; the cut-over date must be explicit.

Quality management

Quarantine, sampling and certificate processes directly affect stock movement.

Maintenance management

Planned maintenance shares the same calendar as capacity planning.

Actual costing

Actual cost cannot be calculated without routings, work centres and real consumption records.

Standard costing

Standard cost is for planning; the variance against actual is what gets managed.

By-product / scrap / rework

By-products and scrap require the cost allocation rule to be written up front.

Subcontracted operations

Subcontracting requires stock to be tracked while it sits outside the company.

Modules to be deployed

Mark the ones genuinely needed in the first phase.

Select at least one option to continue.

Integrations to be built

Mark the mandatory ones and those needed in the first phase.

How many integrations must be two-way or real time?

Two-way flows need separate design so retried requests never create duplicate records.

Is there an existing ERP?

With an existing system we discuss migration; without one, only master data loading.

How many systems will data come from?

Each source system means its own mapping and its own validation.

Data volume

Volume determines validation effort and the length of the cut-over window.

Which data will be migrated?

Opening balances, three years, or full history — scope is decided here.

Data quality

If quality is unknown it must be sampled before the scope decision.

Is a standard ERP enough for your processes?

The answer separates package, package plus configuration, and package plus custom modules.

Custom screens

Every custom screen is an item that must be retested at each upgrade.

Custom approval workflow

Approval flows must be designed together with the authorisation model.

Custom reports

What matters is not report count but whether the underlying data is born in the system.

Custom mobile application

A mobile app is planned like a separate product: releases, stores and offline behaviour.

Dealer or customer portal

A portal is exposed to external users, so it needs its own authorisation and security design.

Need to expose an API

In some products API access is a separate licence item; ask in writing before signing.

Legacy applications that will stay alive

Every application that stays requires written data ownership against the ERP.

ERP ecosystem under consideration (optional)

This choice does not change the result. The tool is product independent; complexity comes from your own structure.

Does the project have a defined owner?

An owner with the authority to settle cross-department scope conflicts is the quietest risk reducer in a project.

How much time can key users give the project?

Internal effort in analysis, data cleansing and testing is a real cost line.

Your in-house IT or development capacity

Without a key user who can change a report, every small change becomes an external cost line.

Are your processes documented?

Undocumented processes are the most common reason analysis takes longer.

Is there a fixed date pressure?

A fixed date from regulation, a period start or a contract directly affects the cut-over method.

Have you run a system project at a similar scale before?

Previous experience shortens scope and acceptance discussions noticeably.