Case studies
Each entry is classified by evidence. Software we own and build is labeled as an Oscillate product. Everything else is published as an implementation scenario until it is verified as a client project - never as a success metric pack.
Archive
Cards show classification, industry, the operational problem and the primary service. Verified outcomes appear only when evidence supports them.
CImplementation scenario
ManufacturingExcel / VBA automation
Weekly production packs depended on consolidating many workbooks by hand.
Implementation scenario focus
Weekly production packs depended on consolidating many workbooks by hand.
CImplementation scenario
DistributionMS Access database development
A shared Access orders file was hitting size and locking limits under concurrent use.
Implementation scenario focus
A shared Access orders file was hitting size and locking limits under concurrent use.
CImplementation scenario
OperationsSpreadsheet to web migration
Project status lived in emailed spreadsheets with no single live record.
Implementation scenario focus
Project status lived in emailed spreadsheets with no single live record.
CImplementation scenario
ManufacturingLegacy system integration
Warehouse updates depended on daily manual export, reformat and import from ERP.
Implementation scenario focus
Warehouse updates depended on daily manual export, reformat and import from ERP.
CImplementation scenario
FinanceData analytics & reporting
Month-end packs were assembled by hand from accounting exports and spreadsheets.
Implementation scenario focus
Month-end packs were assembled by hand from accounting exports and spreadsheets.
CImplementation scenario
ManufacturingManufacturing reporting automation
Shift output reached management only after paper logs were compiled the next day.
Implementation scenario focus
Shift output reached management only after paper logs were compiled the next day.
DOscillate product
Website templatesWeb application development
One catalogue had to serve both a source-code download and a delivered-website engagement.
What we built
One catalogue had to serve both a source-code download and a delivered-website engagement.