Complex processes.
Clear solutions.

Give every request a clear next step.

Approval work becomes difficult to track when decisions, purchasing, and receiving happen in separate conversations.

The approach

Use explicit states, configurable approval rules, and receiving checks. Keep incomplete requests open so a partial delivery doesn't disappear from view.

Try this

Change the request amount, advance through approvals, then record a partial or complete delivery.

Spot drift before it crosses a safety limit.

My run-chart project monitors measurements against upper and lower safety specifications and sends alerts when readings trend toward either out-of-spec zone, supporting intervention before a limit is crossed.

The approach

Make both safety boundaries visible, monitor direction as well as individual readings, and distinguish an early trend warning from an actual specification breach. Give the team a clear signal to investigate and act.

Try this

Load an upward or downward trend, then add a measurement beyond either safety limit. Compare the early-warning alert with the out-of-spec alert.

Make messy imports easier to resolve.

A small data issue can interrupt a much larger process when a file moves between operational systems.

The approach

Validate required fields, quantities, and duplicate identifiers before import. Explain the exact row-level issue so a user can correct it without guessing.

Try this

Validate the sample batch, apply the example corrections, then validate again to unlock the simulated import.

Reshape legacy data for a new schema.

My Access-to-PostgreSQL migration work included substantial parsing and transformation into newly named destination fields. This fictional example demonstrates how legacy values can become structured, usable SQL data.

The approach

Define the destination fields, parse combined source values, normalize formats, and map the results into the new schema. Preserve source identifiers and isolate parsing or conversion failures before loading, then reconcile the results.

Try this

Try the parser to split a legacy string into newly named fields. Then run the sample batch migration, correct an invalid amount, and retry without duplicating loaded records.

Connect ERP structure to QA and scheduling.

My QAD-to-SQL BOM work brought product structure and routing into a SQL database, then translated that data for an ATS instance supporting QA checks and scheduling software. The import was updated to use SQL bulk loading in place of Excel interop.

The approach

Stage the exported data, validate parent/component relationships, and connect routing operations to the BOM. Preserve hierarchy so component quantities can be calculated across assembly levels, then translate the relevant structure and operation data for downstream QA and scheduling use.

Try this

Load the sample structure into the simulated reporting database. Change the build quantity to recalculate component demand, preview the translated QA and scheduling records, or introduce a missing routing operation to see the validation block.

Turn inventory exports into manageable uploads.

My inventory program bridges equipment-vendor exports with a legacy QAD environment, parsing and reformatting records before splitting the output into batches compatible with the existing import process.

The approach

Translate the vendor's export structure into the fields needed by the receiving system. Keep records intact when splitting the output and make batch sizes clear so the upload process is manageable.

Try this

Parse the fictional vendor export, review the mapped fields, and change the batch limit. An invalid quantity is held for correction; accepted rows are split without dropping or duplicating records.

Keep authorization and its documents together.

Chemical change requests need supporting safety and disposal documentation. A separate manual upload step makes that documentation harder to keep connected to the request.

My contribution

Created a Power Apps chemical change and authorization process with supporting automation. Users attach SDS/MSDS and disposal documents to the request; the flow files them in a centralized SharePoint library and links them to the correct request. The process also displays manager comments when needed.

Outcome

Removed the separate task of navigating to SharePoint to manually file documents, while centralizing request documentation for easier retrieval and traceability.

Try this

Select the sample attachments and submit. See the linked library records appear automatically, then advance a generic approval.

Make engineering documentation more dependable.

An evolving PFMEA (Process Failure Mode and Effects Analysis) Excel workbook was easy to break as users maintained it. The engineering content needed a more dependable way to be entered and updated.

My contribution

Built a SQL database with a Microsoft Access front end from a living Excel workbook provided by a mechanical engineer. Translated the engineering workbook into database records and an interface users could use to enter and update PFMEA information. The source template combined process steps and requirements, failure modes and effects, cause/control libraries, severity-occurrence-detection rankings, action priorities, and corrective-action follow-up.

Outcome

Made the documentation process less brittle by moving it out of an easily broken spreadsheet and into a structured database application.

Try this

Edit a fictional record through the form, save it, and review its sample revision history. The demo leaves risk scoring and engineering approval criteria undefined.