TKC Institute

TKC Institute  /  The IMSplus ecosystem

Five applications, one login, one audit trail

A person is set up once. When they leave, access is withdrawn once. Every action any of the five takes lands in the same append-only log — which is a different thing from five systems each keeping its own partial story.

The applications

Three stand alone. All five share the same spine.

Most organisations start with one. Nothing has to be migrated again when the second arrives — it is the same org chart, the same permissions, the same trail.

IMSplus
The core
Stands alone

The quality and compliance system, and the layer the others authenticate against.

  • ISO 9001, ISO/IEC 17025 and ISO/IEC 27001 today
  • Other standards configurable, not coded
  • Audits, findings and corrective action
  • One account per person; one place to grant or withdraw access
  • Two-factor where you want it
  • An append-only log across every application
DocPlus
Document control
Stands alone

Scan or upload, and the document is stored with a tracking number, read by OCR so its text is searchable, and sent into the process it belongs to.

  • A drag-and-drop builder sets who does what, in which order
  • Every view, download and print recorded against the document
  • Access by document type — payroll is not visible to the floor
  • Documents of external origin filed the same way as your own
  • Files can stay in your own SharePoint, OneDrive or Google Drive
  • No delete button anywhere in the store
HRplus
The employee record
Stands alone

Everything the HR office is asked for, each item carrying its own approval chain and its own printable record.

  • Employees, compensation history, contracts and gratuity
  • Leave — applications, balances, approvals
  • Staff loans, schedules and payroll deductions
  • Appraisals against a competency rubric you set
  • Training applications, cost approval and the evidence it worked
  • KPI plans, promotions and acting appointments
  • Insurance, retirement and union membership
SERVICEplus
Service requests
Part of the ecosystem

Ticketing for the internal teams people queue outside: HR, IT, facilities, procurement.

  • Requests raised, assigned and tracked to resolution
  • On the same login and the same trail as everything else
  • Usually out of scope for a first phase, and there when the need appears
CMSplus
Complaints
Part of the ecosystem

Case management for complaints — the record a regulator or a customer asks to see.

  • Logging, investigation and resolution tracking
  • Decisions and reasons attached to the case, visible to every later step
  • Usually out of scope for a first phase, and there when the need appears

What they share

One ecosystem, not five systems bolted together

One identity

One account per person across all five. Set up once, withdrawn once. Two-factor where you want it.

One structure

Your org chart, roles and approval chains are configured in the console rather than written into code — so they change when you change.

One trail

An append-only log across every application. Nothing is edited away; a correction is a new entry beside the original.

What it replaces

What you do today, and what it becomes

Approvals by email
Approvals on the record, with the approver’s name, decision, comment and time.
A shared drive nobody trusts
One indexed store, searchable by content, with access set by document type.
Spreadsheets tracking staff
Employee records, leave, training and appraisals in one place, each with its own chain.
“Ask Marcia, she’ll know”
A trail that survives the person who built it.

Where it runs

On AWS, with your files in your own cloud

No server in your building to patch or replace. The documents stay in your own tenant — SharePoint, OneDrive or Google Drive. You keep custody of the files; the system keeps the index, the permissions and the trail.

Start a trial Request a quote