Operations & Data Analytics — York, PA
Operations run on data. I make it behave.
Pivota Systems is the solo analytics practice of Anthony Powers — Excel models, reconciliation logic, dashboards, and reporting automation, sharpened by nine years running data inside surgical services.
This is the chain I ran data for, for nine years. The software handles the ends well and the middle badly — the middle is where cases stall, charges slip, and custody gets fuzzy. Every operations chain has a middle like this. Fixing it is a data problem, and it's the one I know cold.
What I do
Data work for operations that can't stop moving.
Built in Excel, Power Query, Power BI, Access, and VBA — the stack your team already owns.
Reconciliation models
Excel and Power Query models that match records across sources on shared keys instead of eyeballs — so mismatches surface themselves.
Operational dashboards
Power BI and Excel reporting that gives operations and finance teams the numbers they act on, without a data team in the loop.
Reporting automation
VBA and Power Query routines that turn the manual steps — the mail-merges, the status chases, the double entry — into checked, repeatable ones.
Tracking databases
Access databases for the things spreadsheets keep dropping: inventory custody, vendor items, anything that needs one record per real-world thing.
Data cleanup & standardization
Untangling the workbook sprawl — duplicate names for the same item, broken lookups, three versions of the truth — into one keyed source.
Working with what you own
No rip-and-replace. I build the connective layer around the systems and licenses your team already pays for.
The work, in miniature
What reconciliation actually looks like.
A small illustration of the before and after. The data below is synthetic — built for this demo, drawn from nothing real — because that's the point: this class of problem doesn't need anyone's protected data to be shown, or solved.
| Case | Item (as typed) | Vendor sheet | OR log | Charge posted | Status |
|---|---|---|---|---|---|
| 2481 | ACET SHELL 54MM | ✓ | ✓ | ✓ | matched |
| 2482 | acet shell 54 mm | ✓ | ✓ | — | lookup failed — trailing space |
| 2483 | FEM STEM SZ 11 | — | ✓ | ✓ | used, not on vendor sheet |
| 2484 | TIB INSERT 10MM | ✓ | — | ✓ | charged, no usage record |
| 2485 | Tibial insert 10 | ✓ | ✓ | dup? | same item, two names |
| 2486 | SCREW 6.5 X 40 | ✓ | ✓ | — | never posted |
// three sheets, three owners, no shared key — every mismatch found by a person, or not at all
| Case | Item (catalog key) | Vendor | OR log | Charge | Status |
|---|---|---|---|---|---|
| 2481 | IMP-ACSH-54 | ✓ | ✓ | ✓ | reconciled |
| 2482 | IMP-ACSH-54 | ✓ | ✓ | ✓ | reconciled — key match, not text match |
| 2483 | IMP-FMST-11 | — | ✓ | ✓ | flagged → vendor sheet requested |
| 2484 | IMP-TBIN-10 | ✓ | — | ✓ | flagged → OR record requested |
| 2485 | IMP-TBIN-10 | ✓ | ✓ | ✓ | deduplicated to one item |
| 2486 | IMP-SCRW-6540 | ✓ | ✓ | — | flagged → charge queued |
// one catalog key across all three sources — mismatches surface themselves, with a next step attached
Who's behind it
Anthony Powers. Nine years running operational data inside surgical services across a multi-hospital system — where I kept ending up building the models, dashboards, and databases the official software should have provided and didn't.
Solo practice, on purpose. You work directly with the person doing the work — not an account manager standing between you and it.
Tell me where your chain breaks.
If cases stall, charges slip, or the implant record never quite matches reality, that's a conversation worth having. No pitch deck — just a look at what's actually happening.