Built around your operation
Asset and maintenance management software for Sri Lankan businesses
Plan asset registers, branch maintenance requests, approvals, parts, documents and service histories with a custom business management platform.
Kaduwela, Sri Lanka · Local and remote delivery
Multi-branch operators, maintenance teams and facilities managers
Where to begin
A request in a message thread should become a job with a clear owner and history.
Asset and maintenance software should connect each asset to its location, responsible team, requests, approvals, work performed and supporting documents. Begin with one recurring maintenance process and define how a request becomes an accepted, closed job.
Follow the work
A connected operating flow
- 01
Register
Identify the asset, location, custodian and useful supporting records.
- 02
Request
Describe the issue and route it to the person who can triage the work.
- 03
Approve and act
Track approval, assignment, materials and documents around the job.
- 04
Verify and close
Confirm the result and retain a service history for the next decision.
Build an asset register people can keep current
An asset register is useful when the team can identify the right equipment and its current location. Agree the identifiers, serial numbers, custodian fields, photos and documents the operation needs. Decide who can create, move, retire or correct an asset record.
Start with a manageable group of assets and test the process for a relocation or replacement. A spreadsheet import can establish a starting point, but a named owner and a correction workflow keep the register useful after launch.
- Stable identifiers and location ownership
- Relevant manuals, warranties and service documents
- Controlled transfers and lifecycle changes
Turn branch requests into accountable maintenance work
A branch should be able to describe an issue without knowing the internal maintenance structure. Triage establishes urgency, responsibility and the next action. Approvals should reflect the business’s spending and operational rules.
Define statuses in terms staff can act on: submitted, reviewed, assigned, waiting for material, completed and accepted are possible examples. Record why a job is waiting and who can unblock it. Closing a request should capture the work done rather than simply removing it from a list.
Keep parts, evidence and service history together
A repair may involve an issued spare part, an external quotation, a service report and a completion photograph. Connecting those records to the request and asset makes future investigation easier. Confirm how stock issues and returns should affect the inventory module if the systems are connected.
Useful management views can summarize outstanding work, recurring failures and spending by asset or branch. Agree the definitions and source records first, so teams know what a report includes and which incomplete entries may affect it.
Use the Choice Park project as a concrete discussion point
The published Choice Park implementation brings assets, stock and GRN work, branch maintenance, accounts, fleet, documents, reporting and Keen AI into an operational platform. Its case study shows the connected workspaces and the business context.
Your project can start with the asset and request workflow that needs the most attention. Existing tools, integrations, approval rules and document storage should be reviewed before deciding which modules to build or connect.
Acceptance starts with the real task
What to demonstrate before rollout
0 of 8 reviewed
Use this as a discussion checklist. Ticks are kept only while this page is open.
Download the blank checklistDelivered work you can inspect
Relevant client implementations
Questions before the next step
Common planning questions
Is this limited to an equipment list?
A scoped platform can connect the register to branch requests, approvals, documents, parts and service history. Agree the required workflow rather than treating every register as a complete maintenance system.
Can we begin with one branch or department?
Yes. A representative pilot can validate asset naming, request routing and approval responsibilities before expanding the same process.
Can documents remain attached to the correct asset or request?
Document storage, access, file types, retention and backup should be included in the specification. The published Choice Park project includes a document and reporting workspace.
Can existing inventory or accounting tools be connected?
Integration depends on their available interfaces, data ownership and the events to exchange. Those constraints are reviewed before an integration approach is proposed.
Bring the operating problem
Let’s work through your actual requirements.
Tell us your business type, users, branches, current system and the task you want to improve. We’ll use that context to discuss the right next step.