Projects

Business problems. Working solutions.

Examples of improving field administration, preparing data for payroll and connecting business systems. The Allnorth work was completed during my employment; Integration Hub and Transformer were built for a client.

Work completed during my employment at Allnorth

EMS Extension

Supporting field administration and payroll around an ERP. Field LEM processing and the UKG export were two workflows within this application.

Field LEM processing

Field time and expenses with less manual processing.

The problem

Field time, expenses and contractor invoices required substantial effort from administration and accounting. Completing the entries extended into evenings and weekends, while coding and rate discrepancies created further work before transactions could be finalized.

What changed

I developed a workflow that checked incoming records, matched the applicable contractor pay and billing rates, and prepared timesheets and expense reports for direct import into the ERP. Approved timesheets also supplied the vendor invoices, removing another manual preparation step. Generated documents were sent to contractors for review and acceptance.

Results

The changes ended the evening and weekend entry work for these transactions. Hundreds of vendor invoices could be prepared in minutes. More consistent matching of contractor, equipment and travel rates meant fewer payment complaints, fewer client billing problems and less underbilling caused by incorrect project rates.

Discuss an ERP integration

BST to UKG payroll preparation

Keep project detail in BST and prepare employee time for UKG’s pay rules.

The problem

Allnorth needed detailed time transactions in BST for project accounting, while UKG Workforce Management needed employee time in a different form to apply its pay rules. The available BST export did not provide the required information and coding.

What changed

I extended EMS Extension to read time entries from the local copy of BST data and prepare them for UKG import. It added the information and codes needed for project uplifts, night-shift premiums, paid time off and overtime, while excluding contractors from the employee payroll file.

Results

Project detail remained in BST, and UKG received employee time in the structure its pay rules required. The work connected the two systems while preserving the different meaning each needed from the same time records.

Explore ERP Migration and Integration

ERP reporting platform

Make business information accessible around an existing ERP.

The problem

Allnorth’s BST10 ERP held information needed by finance, the project management office and the field, but the available interfaces did not cover their reporting and custom application needs.

What changed

I built a reporting and application platform around a read-only local copy of the ERP data. SQL views and procedures made that information usable, while custom applications kept their own records in separate databases.

Results

The same consistent copy supported spreadsheets, Power BI, resource scheduling, revenue forecasting and variance analysis. It also supplied the reference information used by EMS Extension for field administration and payroll preparation.

Custom client projects

Built for a client

Integration Hub and Transformer were designed and built for a client, who owns the applications.

Integration Hub

Keep shared records aligned across business systems.

The problem

When several applications hold the same employee, project or supplier information, maintaining each copy becomes a recurring job. Differences accumulate, and reporting becomes harder to trust.

What changed

I designed and developed Integration Hub to check configured source systems for changes to records such as employees, projects, vendors and cost codes. It distributes the relevant updates to connected applications using agreed rules, reducing the need to maintain those records separately.

Power users can configure supported integrations through the application without writing code. They need appropriate system access and an understanding of the data being exchanged.

Results

The application provides a defined way to keep shared records aligned across systems with different interfaces. Where direct updates are unavailable, it can prepare an import file and send it to the person responsible for loading it. File preparation is automated; that destination import remains a manual step.

Discuss a systems integration

Transformer

Turn assessment findings into an improvement plan you can follow through.

The problem

An assessment can identify a long list of problems without making the next steps clear. Some findings share a cause, others depend on changes elsewhere, and addressing them one by one can leave important gaps unresolved.

What changed

I developed Transformer to give teams a shared record of those findings, connected to what the business needs to do and the processes and systems that support it. Users can identify gaps, group related work into initiatives, and use that evidence to prioritize the changes.

Results

As the work progresses, teams can return to the same record to review what has been addressed and what remains. The findings stay connected to the work intended to resolve them, supporting follow-through beyond the original assessment report.

Discuss a process improvement project

Looking for GKC products?

Data Discovery and Email Archiver have their own product pages, with demonstrations and pilot discussions available.

Let’s talk about what needs to change.

Describe the problem in your own words. That is enough to start a conversation.