Manual File Reading at Scale
Supplier files were read by hand, absorbing about 800 man-days a year within an operations process staffed by 12.5 FTEs.
Inenco is a UK energy and utilities consultancy that helps businesses buy, manage, and reduce their energy. Its bureau, compliance, and optimization services depend on processing high volumes of data received from energy suppliers.
Because client reporting and procurement decisions rely on that supplier data, the speed and accuracy of processing it directly affect the service Inenco delivers.
Inenco wanted to stop reading supplier data files by hand and move to automated ingestion that could handle every supplier’s format. Each file needed to be validated on arrival, converted from its supplier-specific layout into one common data format, and loaded straight into Inenco’s Phoenix and ICMAS systems.
Alongside this, Inenco aimed to reduce its dependence on the legacy ICMAS codebase, give the operations team clear visibility of file processing, and expose core services through APIs for its website and mobile apps.
Energy and Utilities
SnapLogic
SnapLogic Integration, Data Automation
Supplier files were read by hand, absorbing about 800 man-days a year within an operations process staffed by 12.5 FTEs.
Each energy supplier sent data in its own layout, so there was no single, consistent way to process incoming files.
Because processing depended on people, any absence in the team slowed procurement and reporting for Inenco's clients.
Data reached the legacy ICMAS system through a two-stage ETL process that added rework and extra handling.
NeosAlpha helps energy and utilities organizations automate file ingestion, data mapping, and API enablement on SnapLogic, so teams spend less time on manual processing.
Book a Free Consultation CallSnapLogic pipelines check the syntax and columns of each supplier file as it arrives, catching problems before the data reaches downstream systems.
Our developers mapped every supplier's layout to a common data format (CDF), giving Inenco one consistent structure regardless of where the data comes from.
Validated data is staged and loaded directly into Phoenix and ICMAS through a single pipeline, replacing the earlier two-stage ETL.
Scanned invoices pass through ABBYY OCR and then enter the same validation and mapping flow as electronic supplier files.
A dashboard shows files received, validation errors, staged and processed, with a per-stage monitor covering the READ, CON, IMP and EDI stages.
A WSO2 API gateway fronts the Progress database, warehouse and TradePoint services, adding security, cataloging, auditing, caching and mediation for RESTful services. The Inenco Direct website uses these APIs for comparison quoting, and mobile apps reuse the same services.
We delivered the program in three phases: supplier EDI automation first, then expanded supplier coverage, then OCR-led processing of manual invoices.
Automated ingestion removed about 800 man-days of manual file reading from the operations workload every year.
Across the three phases, about 8.5 of the 12.5 FTEs in the process were freed to focus on client-facing and analytical work.
Moving processing into SnapLogic allowed Inenco to retire roughly a tenth of its legacy ICMAS code.
Data now flows from supplier file to Phoenix and ICMAS in a single pipeline, eliminating rework from the old process.
The operations team can see file volumes, errors, and progress at every stage in one dashboard.
Core services are available through managed APIs, supporting comparison quoting on Inenco Direct and reuse by mobile apps.
Tell us what you're looking for and we'll get you connected to the right people.