Home / Continuity & Risk

Continuity
& Risk

Delivery is led by one senior specialist. That is the reason a platform reaches production in weeks instead of quarters, and it is the reason any competent maintenance planner or IT manager should ask what happens if that person is unavailable. This page is the answer, and it is the answer that appears in the contract.

Ask about the terms The commitments

The honest version

Said plainly, once.

BCM is a specialist practice, not an agency with a bench. The work on every platform described on this site was designed, built and deployed by the same person, and that person is who you deal with. There is no account manager between you and the engineer, no handover to a delivery team who were not in the scoping conversation, and no junior learning your operation at your expense.

The cost of that arrangement is capacity, which is why client numbers are deliberately limited and why any proposal states what else is running. The benefit is speed and the fact that the person who understands your operation is the person changing the code. Everything below exists so that the cost side is managed rather than ignored.

Commitments

The commitments, in writing.

Each of these appears in the agreement rather than in a conversation. They exist because a recurring commitment on a production system deserves specifics, not reassurance.

Never held hostage

No Phone Home, No Kill Switch

The platform runs on your server with no licence check and no vendor callback, so it cannot be switched off remotely and it does not stop working if BCM is unreachable for a week. Your production reporting is never one expired login away from dark.

Your control room

Documented For The People On Shift

Every build ships with operating documentation written for dispatch and supervision: which dashboard answers which question, how to restart a service, what a stale data warning means, and who to call. Development, decoding, and changes stay with BCM.

Escrow

Source Held In Escrow

Source is deposited in escrow and released to your operation on triggers written into the agreement: BCM ceasing to trade, or a sustained failure to meet the response commitments below. Procurement gets a real answer, and neither of us has to pretend the day to day is self-serve.

Why it lasts

The Pit Changes. The Platform Has To.

New benches, new equipment, a rehandle rule nobody wrote down, a fault code the fleet has never thrown before, a report the general manager wants by Thursday. A platform that stops being fitted to the operation starts losing value in weeks. Keeping it matched to the mine is what the subscription buys.

ResponseAgreed response windows for production issues, written into the subscription rather than left to goodwill, and excluding declared leave periods given reasonable notice.
Included support16 to 32 hours a month depending on platform size, covering incident response, monitoring, patching, configuration changes and small report edits. New modules and new integrations are quoted rather than absorbed. Beyond the allowance, $240 an hour in business hours and $360 outside them.
EscalationA named site contact on your side who knows the daily checks, so a routine restart never waits on an outside call.
EscrowSource deposited with a third party and released only on the triggers set out in the agreement.
If it endsYour data stays yours and the platform you have keeps running as delivered. Updates, new decoding, new reports, and support stop with the subscription.

Capacity

Limits, stated up front.

Concurrent buildsOne major platform build at a time per client, and a stated number across all clients. If a start date depends on finishing elsewhere, the proposal says so.
Support allowance16 to 32 hours a month depending on platform size, which is what makes the workload predictable enough to commit to response windows at all.
LeaveResponse commitments exclude declared leave periods given reasonable notice. A practice that pretends otherwise is one that will miss a commitment eventually.
GrowthAdditional specialists are added as the client base grows rather than in advance of it, and any change to who supports your site is told to you before it happens, not after.

Next step

Bring the objection, not the benefit of the doubt.

If your procurement or IT group has a specific concern about single-supplier risk, it is a better conversation than a general one. Most of the answers are already written down.

Start a conversation Ask about the terms Platforms See everything BCM builds

Location Timmins, Ontario, Canada

Continuity& Risk