Skip to content
TREN
Mipo field team working on site
How we work

From request to delivery and beyond, one line.

The same team is responsible throughout the process; there is no disconnect between procurement and technical implementation. Every step has a concrete, written output.

01 / 04

Analysis

Analysis and technical requirements

We listen to the requirement on-site and inspect the existing infrastructure in person. We do not quote until the scope is clear.

The goal of this stage is to identify not what the organisation wants but what it needs. Existing hardware, network, backup and processes are examined on-site; integration points and data flows are extracted. The output is a scope document signed by both parties.

Outputs of this step
  • Current state report
  • Technical requirements document
  • Scope boundary — what is included and what is excluded
  • Risk and dependency list
Typical duration 1–3 weeks
02 / 04

Procurement

Procurement and delivery

We source equipment and licences from the manufacturer or authorised distributor and manage the import and customs process ourselves.

Once the configuration is finalised, a supplier comparison is made; price, lead time and warranty conditions are evaluated together. For overseas procurement, the import, customs and logistics process is managed by us — the client has no work to do at this stage.

Outputs of this step
  • Configuration and price proposal
  • Delivery and timeline plan
  • Goods-in quality control record
  • Serial number and warranty inventory
Lead time varies by product and stock availability
03 / 04

Installation

Installation and integration

Our own field team carries out the installation and brings the system into operation alongside the existing infrastructure.

Installation is never subcontracted. Planned downtime windows are notified in writing in advance; for critical systems, parallel operation minimises downtime. Go-live is considered complete when the test report is signed.

Outputs of this step
  • Rack and network diagram
  • Configuration document
  • Go-live and testing report
  • User training
Typical duration 1–6 weeks
04 / 04

Support

Support and maintenance

After go-live, the same team stays on for support. One number, one responsible party, one file.

Under the maintenance agreement, the system is continuously monitored; updates are tested and applied in planned windows, and backup restore is regularly rehearsed. The periodic report presents completed work, open risks and recommendations in writing.

Outputs of this step
  • SLA-backed maintenance agreement
  • Monitoring and alerting infrastructure
  • Backup restore test report
  • Periodic maintenance and risk report
Annual agreement · periodic maintenance schedule
Common questions

Questions about the process.

It depends on the scope. A short discovery meeting is free; analyses that require an on-site detailed inspection and written report are priced separately. This fee can be deducted from the total if the project proceeds.

Out-of-scope requests are priced separately and added with written approval. No surprise additional costs arise; every change is on record.

Work that requires downtime is scheduled into planned windows and notified in writing in advance. For critical systems, the parallel operation method minimises downtime.

No. Source code, configuration documents, network diagrams and licences remain with the organisation. When you want to continue with another supplier, everything needed for handover is in your hands.

Yes. You can take only procurement, only installation, or only maintenance. The advantage of working end-to-end is that accountability is undivided, but it is not mandatory.

Let's talk about the process on your own project.

Share your needs; let's identify together which steps are required.