All case studies
How we operate · After go-live

Go-Live Is Day One.Then We Watch.

Once a client's team works in a system AltaMatic built, a read-only watcher goes through what happened in it the day before: who signed in, what they changed, what anyone sent through the Report button, and anything that looks wrong. The report reaches the engineer responsible for that system every morning, so we see a problem in the system's own records, not only when someone calls.

9:00 am

every day, Edmonton time: yesterday's report arrives

EVERY MORNING, FROM THE DAY BEFORE01Read onlyIts own login, the listed columns, no writes02Who signed inAnd who has not signed in once yet03What changedEverything created and changed, and the action04The Report buttonEvery issue or idea staff sent from inside05Anything that looks wrongWrong-password tries close to a lockout06Report at 9:00 amTo the engineer on the system, Edmonton time
The short answer

How Does AltaMatic Watch a System After Go-Live?

Once a client's team works in a system AltaMatic built, a read-only watcher reports on it every morning at 9:00 am Edmonton time to the engineer responsible: who signed in the day before, what they changed, what staff sent through the in-app Report button, and anything that looks wrong. The watcher reads through its own login, limited to the columns listed for that system, and cannot change anything.

  • Who signed in
  • What changed
  • The Report button
  • Anything that looks wrong
  • Read only
  • Every morning
The story

The first weeks after go-live decide whether a system sticks.

A new system meets real work in its first weeks: a step nobody mentioned in discovery, a screen a crew lead can't find on a phone, a record that should have saved and didn't. Most people don't report these. They work around them, and the workaround becomes the process.

So we read the system itself. Every morning at 9:00 am Edmonton time, a watcher reports on the day before to the engineer responsible for that system: who signed in and who hasn't yet, what was created and changed, every note sent through the in-app Report button, and anything that looks wrong, such as wrong-password tries close to a lock-out. Each report starts where the last one ended.

The watcher reads through its own database login, which can read only the columns listed for that system and cannot write anything. Its code holds no client data and no passwords. It is set up project by project, and it runs today on one client system whose team is in testing.

At a glance

What it is
How AltaMatic operates what it ships
Status
Running on a client system in testing
When
9:00 am daily, and on demand
Access
Read only, listed columns
Reports to
The engineer on the system
Client data
Never in the watcher's code
What we built

What we read every morning.

Six things from the day before, straight from the system's own records.

01

Who signed in

Who is using the system, and who has not signed in once yet, so training goes where it is needed.

02

What changed

Everything created and changed the day before, with the action that made each change.

03

The Report button

Every issue or idea staff send from inside the system, read the next morning at the latest.

04

Anything that looks wrong

Wrong-password tries close to locking someone out, and anything else a person should look at.

05

Read only

Its own login reads only the columns listed for that system and cannot write.

06

Every morning

At 9:00 am Edmonton time, starting where the last report ended, and on demand.

Out of respect for our client

We will talk architecture, but the specifics stay private: how this system prices, the rates it runs on, and how it is tuned to this business belong to our client, and we keep them that way. When we build for you, your systems and your numbers get the same discretion.

Common questions

This Build, Answered.

What Does the Watcher Report?

What happened in the system the day before: who signed in, what they changed, what anyone sent through the in-app Report button, and anything that looks wrong. Each report starts where the last one ended, so no stretch of time is missed.

Can It Change Anything in My System?

No. It reads through its own database login, which can read only the columns listed for that system and cannot write. The watcher's code holds no client data and no passwords.

Who Sees the Report?

The AltaMatic engineer responsible for the system. It arrives at 9:00 am Edmonton time every day, and the engineer can run it again at any time.

Is It on Every System?

It is set up project by project, with the columns each system's watcher may read written down for that system. It runs today on one client system whose team is in testing.

How Does It Fit With Support?

It is part of operating what we ship. The operating arrangement agreed with each client says what is monitored, what is fixed and what response to expect; the watcher is how the monitoring part happens every day.

Your operation is next

Who Watches Your System After Launch?

30 minutes, free. We map how your work runs today, and show you how we would build the system and keep it running.

Edmonton, Alberta · No commitment · 587-937-6948

A

Alta

Online · AltaMatic

Hey — I'm Alta, AltaMatic's assistant. Tell me what kind of business you run and I'll show you what we'd build for it first.

Powered by AltaMatic · Edmonton