KDaptive

The operational model

One record model. Every operational piece, connected.

Requests, the records they reference, the rules that move them, and the reporting that comes out the other end all run on the same underlying model — not a ticketing tool with extra tabs bolted on.

  • Requests
  • Customers
  • Locations
  • Assets
  • SLAs
  • Time & billing

The connected platform model

Records reference each other — nothing is re-typed.

A request stores an ID for its customer, its location, and any asset involved, never a copy of their data. Update a location once and every request referencing it reflects the change instantly.

Service delivery

  • Requests
  • Customers
  • Locations

Operational records

  • Assets
  • Attachments
  • Custom Fields

Coordination & reporting

  • SLAs
  • Time & billing

Core operational records

Customers, contacts, locations, and assets, related on purpose.

A customer can have many contacts and locations. A location can have many assets. A request can name any combination of them — giving a technician full context without leaving the record, and a manager visibility across a whole site or asset.

Platform capabilities

Eighteen operational areas, grouped into five categories.

Which of these are active for your organization depends on your solution and module entitlement.

Service delivery

  • Requests / Tickets
  • Customers
  • Contacts
  • Locations

Operational records

  • Assets
  • Attachments
  • Custom Fields
  • Notifications

Service levels & coordination

  • SLA Management
  • Business Hours
  • Time Tracking

Access & accountability

  • Roles & Permissions
  • Audit Logs
  • Email-to-Request
  • Search

Insight & configuration

  • Reporting & Dashboards
  • Organization Settings
  • Terminology

Request lifecycle

From intake to reporting, one record, tracked the whole way.

Assignment rules decide who a request goes to. SLA targets start counting immediately, tracked against your business hours. Every transition is captured in the request's own history — the same record reporting later draws from.

  1. Intake

    Portal, email, or manual entry

  2. Assignment

    Routed by your rules

  3. Work

    SLA running, time logging

    JT1h 40m left

  4. Resolution

    Closed, full history attached

  5. Reporting

    Feeds dashboards automatically

Service levels, business hours, and time

Coordination that runs on its own, not on follow-up.

SLA targets, business hours, and logged time all attach to the request they belong to — visible on the record itself, not scattered across email threads someone has to reconcile later.

Reporting and dashboards

SLA health, aging, and team workload — always current.

Resolution time, SLA compliance, request aging, workload by technician, and activity by location or customer all draw from the same records your team already works in — a view of the platform, not a system reassembled for every report.

Security and tenant isolation

Every action attributable. Every organization isolated.

Access control and accountability aren't an add-on — they're how the platform is structured. Requests can also arrive by email without manual entry, and search finds any record fast.

  • Role-based permissions

    Every action is checked against a role's permissions, on the server, for every request.

  • Full audit log

    Administrative and record changes are recorded with who made them and when.

  • Tenant data isolation

    Each organization's records, members, and configuration are isolated from every other organization on the platform.

Solution and configuration model

What's provisioned for your organization — and what you configure from there.

Your KDaptive solution and module entitlement set which capabilities you have. Within that, custom fields, roles, workflow rules, and terminology adjust per organization — how records relate stays the same for every one.

Organization settings

Meridian Facilities Group

Terminology

Call it a Ticket, a Case, or a Work Order — the label changes everywhere it appears, without touching how the platform behaves underneath.

Platform termThis organization
  • TicketWork Order
  • CustomerClient
  • LocationSite

See what is already ready — and what we would tailor for you.

In a working session, we'll review how your organization operates, show the capabilities KDaptive already provides, and identify the workflows, terminology, permissions, and rules that should be customized before launch.

Book a DemoExplore the Platform

Pricing depends on your solution, selected capabilities, number of users, and how much tailoring your operation needs — we'll work it out together.