Loading...

Work

We leave the names off the site. We still show the work.

These are three pieces of work, with the identifying detail removed. Each one crossed more than one practice: software, security, cloud, the network, or the Windows and Mac ecosystems.

01

Specialty pharmacy

One setup for clinics on Windows and Mac

A multi-state pharmacy group had a clinical app that behaved differently on Windows and on Mac. Sign-in and updates were not the same in every clinic.

Scope

  • We set one standard for sign-in, apps, and updates, on Windows and on Mac.
  • We applied that standard to the computers the clinics already used.
  • We rebuilt the visit application so it worked the same way on both.
  • We wrote the setup down so a difficult morning did not depend on one person.

What changed. The first region ran on one standard, on Windows and on Mac. The visit application no longer depended on a setup the company did not control.

Practices: Workplace Loading..., Software consulting Loading....

02

Regional freight

Dispatch, billing, and the terminal network

Dispatch ran on the computers in the terminal. The Wi-Fi and the firewall were part of the same complaint. Drivers kept a phone app and a paper backup. Billing failed without anyone noticing until morning.

Scope

  • We set up a place in the cloud for the connection between systems, with a log the night operator could read.
  • We replaced the nightly batch with a job that someone watches, and that sends an alert when it fails.
  • We brought the computers in the terminal onto one standard for sign-in and apps, on Windows and on Mac where both were in use.
  • We wrote instructions for the two failures that had been waking people up.

What changed. The morning shift stopped rebuilding the previous night’s paperwork from scratch. The nightly run became a job with an owner and an alert.

Practices: Cloud Loading..., Network and infrastructure Loading..., Workplace Loading....

03

Credit union

Branch systems, before an exam made them urgent

A multi-state credit union was piloting appointments however a branch manager preferred. The computers were a mix of Windows and Mac, and vendor access had outgrown the spreadsheet that tracked it. An examiner would have read both.

Scope

  • We set a baseline for sign-in and computer protection at the pilot branches, on Windows and on Mac.
  • We put reviews of vendor access on a calendar, so they actually happen.
  • We built a small tool for appointments on the computers the branches already used.
  • We added an assistant on member chat and on the branch phone line. It books routine appointments and hands the rest to a person.

What changed. The pilot branches share one standard on Windows and on Mac. Routine calls and chats get an answer. Reviews of who can open what happen because they are on the calendar.

Practices: Cybersecurity Loading..., Software consulting Loading..., Workplace Loading..., AI integration Loading....

Let's work together

If one of these is close, tell us the difference.

Tell us what is similar, and what is different. The difference is the useful part.