AssetPrime Implementation

A practical path from requirements to go-live

AssetPrime implementation brings together deployment planning, operating structure, asset-data preparation, user access, training and go-live guidance around an agreed scope.

Requirement-led setup
Self-hosted or managed cloud
Structured data preparation
User training and go-live guidance

Implementation Process

Eight stages with a clear purpose

The exact activities depend on the approved scope, but every implementation should establish what is being configured, who provides each input and how the result will be reviewed.

01

Requirement discussion

Review the organization, asset types, branches, locations, users, existing records and priority workflows that need to be managed.

Output: Agreed operational scope
02

Deployment selection

Confirm whether AssetPrime will use customer-controlled infrastructure or an optional AssetPrime-managed cloud environment.

Output: Confirmed deployment path
03

Implementation planning

Identify responsibilities, required inputs, configuration items, data-preparation work and the users involved in review and approval.

Output: Implementation checklist
04

System configuration

Prepare the agreed company structure, branches, locations, categories, units and other master data needed for daily asset operations.

Output: Configured operating structure
05

Asset-data preparation

Review the available asset register, remove avoidable duplication and prepare records in the agreed import structure before migration.

Output: Import-ready asset data
06

Users and access

Create users or employee records and configure relevant roles, menu permissions and location visibility for the agreed teams.

Output: Prepared user access
07

Training and validation

Walk users through the workflows relevant to their responsibilities and validate the configured structure with the designated team.

Output: Reviewed workflows
08

Go-live and support

Move into operational use after the agreed checks, with product support and workflow guidance available through the published channels.

Output: Operational handover

Shared Preparation

Implementation works best with clear responsibilities

Responsibilities and deliverables are confirmed for the agreed project. The following items show the typical preparation on each side.

Customer Inputs

Information and decisions your team provides

A responsible contact for requirements and approvals
Branch, location, department and room structure
Asset categories, units and other required master data
Existing asset records in an agreed spreadsheet format
User list, roles and required location access
Infrastructure access when self-hosted deployment is selected

AssetPrime Guidance

Product setup and workflow assistance

Requirement and workflow review
Deployment and setup guidance for the agreed model
Configuration guidance for master data and access
Asset-register import preparation guidance
User workflow training for the agreed scope
Go-live assistance and continuing product support

Data Preparation

Prepare clean asset records before import

Migration quality depends on the source records. Asset names, categories, units, serial numbers, locations and other agreed fields should be reviewed before the import file is finalized.

Standardize

Use consistent category, unit, branch and location names.

Deduplicate

Identify repeated records before preparing the final import.

Complete

Review missing identifiers and required asset information.

Approve

Have the responsible team review the prepared source data.

Deployment Selection

Choose where AssetPrime will operate

Deployment affects infrastructure ownership and implementation responsibilities. The selected model is confirmed before setup begins.

On-premise / self-hosted

AssetPrime is deployed on infrastructure controlled by the customer. The customer manages its server environment, operating system, network, backups and related infrastructure responsibilities.

AssetPrime-managed cloud

AssetPrime manages the application-hosting environment as an optional recurring service. The agreed commercial and operational responsibilities are confirmed before implementation.

Scope Clarity

Separate standard setup from custom requirements

Final inclusions depend on the selected plan and quotation. Requirements outside standard product setup are reviewed before they are promised or scheduled.

Typical implementation scope

Asset and stock master setup

Branch and location structure

User and employee setup

Role and location-based access

Import preparation for agreed asset records

Training on agreed AssetPrime workflows

Requires separate review

Custom workflows outside standard product behaviour

Third-party software or device integrations

Specialized scanner or hardware requirements

Large-scale cleansing of incomplete source data

Custom reports, fields or approval processes

Infrastructure work outside the agreed deployment service

After Go-Live

Continue with product support and workflow guidance

After handover, authorized contacts can use AssetPrime’s published support channels for product questions, issue reporting and workflow guidance. Software support and updates continue according to the agreed annual service arrangement.

Implementation expectations

Scope, responsibilities, schedule and deliverables are confirmed after requirements, deployment readiness and source-data quality are reviewed. Custom work is included only when it is documented in the agreed quotation or scope.

Frequently Asked Questions

Questions about AssetPrime implementation

01

What information is needed before AssetPrime implementation?

+

The initial discussion normally covers organization type, asset volume, branches, locations, users, existing asset records, priority workflows and the preferred deployment model.

02

Can existing asset data be imported?

+

Existing asset records can be prepared for import using an agreed structure. The quality and completeness of the source data should be reviewed before migration, and the exact import scope is confirmed during implementation planning.

03

Does AssetPrime provide user training?

+

Training can cover the AssetPrime workflows relevant to the agreed users and responsibilities. The training scope is confirmed as part of the implementation plan and quotation.

04

Can AssetPrime be implemented on customer infrastructure?

+

Yes. AssetPrime supports on-premise or self-hosted deployment on customer-controlled infrastructure, as well as an optional AssetPrime-managed cloud environment.

05

Are custom integrations included in standard implementation?

+

Not automatically. Integrations, specialized devices and non-standard workflows require technical review and separate scope confirmation before they are included in a quotation.

06

How long does implementation take?

+

The implementation schedule depends on the agreed scope, deployment readiness, data quality, number of locations, user setup and any separately scoped requirements. The working schedule is confirmed after these items are reviewed.

Plan Your Implementation

Start with your actual asset workflow

Share your asset types, locations, users, existing records and deployment preference. AssetPrime can then review the appropriate product, implementation and training scope.