Continue building the business case
Add regional context, test the assumptions, and move into a conversation only when the question is clear.
Decision intelligence
Decision intelligence
Your operating scope travels with you
Explore and save equipment, ARKASH modules, and operating touchpoints to build a live decision brief.
This blueprint shows a potential operating architecture and evaluation criteria. Actual targets and outcomes are defined after baseline measurement and validated during discovery and pilot.
A bank, CIT operator or service partner needs to establish whether access administration is a measurable source of cost or delay, before committing to a new lock and management system.
Scope the access points and current approval workflow, then evaluate TMD Security hardware and access management against a measured baseline. TMD describes centrally managed permissions, mobile one-time-code access and closure records for supported locks. CashPrime proposes a controlled pilot covering operational fit, integration, support and accountable handover; ARKASH connectivity is a separately scoped integration, not an assumed built-in capability.
Baseline → target → verify
Access-related workload
Measured with the customer during discovery and pilot.
Baseline → target → verify
Service restoration
Measured with the customer during discovery and pilot.
Baseline → target → verify
Access evidence
Measured with the customer during discovery and pilot.
From the lock to the operating model
Start with the operating question, not the lock count. Choose the material problem, then define the evidence that justifies investment or shows that a process change should come first.
Build a scenario with your numbersSeparate time spent on access from the actual replenishment or repair. A long visit is not automatically a lock problem.
Record approval, arrival, access and verified closure times. Price field time and control-room time separately, using actual paid or contracted rates.
Recoverable hours create capacity. Count a financial saving only when overtime, invoices or another documented cost can actually change.
Access may be one delay within a longer outage. Dispatch, travel, spare parts and the repair itself still need their own owners.
Compare equivalent service tickets before and during a controlled pilot. Track time to authorized access, repair completion and return to service separately.
If access is not the bottleneck, improve dispatch or maintenance first. Never treat faster access as proof of higher network availability.
Buying a connected lock does not define who approves a visit, who reviews an exception or who owns an unresolved closure.
Agree a permission matrix, approval ownership, event retention and incident escalation. Test these controls with authorized test accounts before rollout.
Retain required dual control, approved crew sizes and emergency procedures. Security, compliance and insurance owners must sign off the chosen configuration.
Agree data ownership, hosting, retention, service-provider access, available connectivity and lock maintenance. Review the operator, relevant authority and insurer requirements for each site. A smart lock does not automatically establish compliance or change approved dual-control rules.
A business case built on your inputs
Enter the baseline you intend to test. No assumed savings percentages or bank results are prefilled. This calculator works locally; it does not send or store your inputs.
Complete the inputs to calculate your scenario. Actual savings require measurement and approval, not just a calculator result.
Screening estimate for a steady operating year. Excludes financing, tax, rollout ramp-up, downtime, availability revenue and avoided fraud losses. Negative values mean costs exceed the assumed benefit.
Before you buy: acceptance guide
These are CashPrime proposed tests, not customer results. Agree the sample, baseline and pass criteria before the pilot, then compare results under equivalent conditions.
In an authorized test environment, confirm that only approved roles, devices and schedules can complete the intended access event. Keep required dual control and test removal of a test user.
Keep as evidence: Approved permission matrix, expected decisions, observed event records and security-owner sign-off.
Use manufacturer-approved test procedures to confirm closure evidence, unresolved-event escalation and alarm handback. Agree who responds, within what window, and how the incident is closed.
Keep as evidence: Linked access and closure records, notification receipt, named incident owner and resolution timestamp.
Agree and test the documented outage and recovery procedure on a non-production setup. Compare equivalent access events and reconcile recovered time with actual contractual or operating costs; do not monetize the same benefit twice.
Keep as evidence: Recovery evidence, comparable timestamps, priced integration and support scope, and finance-approved realizable benefits.
Keep the configuration, software version, test conditions, raw results, costs, service exclusions and acceptance-owner sign-off. Publish a customer name or outcome only after permission and measurement checks.
Solution Blueprint — Banking · Global
Solution Blueprint — Currency Exchange · Middle East & Africa
Solution Blueprint — CIT Operations · Global
We measure the baseline, map the cash flow, and define verifiable targets before deployment.
