Work · Corning
One home for test data from Corning's outside manufacturers
- Client
- Corning, manufacturing, United States
- Service
- Product development
- Period
- From August 2026
- Team
- In partnership with Cramick IT
Factories making Corning's optical products sent their test results as spreadsheets in their own formats. We built the part that turns any of those files into one record of every unit and every measurement, and the pipeline that ships it.
- the problem
Test data arrived as each factory's own spreadsheets in shared folders, with no automation and no single view. The new test lab had no way to take requests.
- what we did
Ingestion that reads every factory's format and registers new products and specs by itself, plus a build-once pipeline from development to staging.
- where it is now
Running on staging. The lab request module is built and waiting to go live.
The problem
Corning's optical business has many of its products made by outside manufacturers. Each factory tests what it builds and sent the results to Corning as CSV, JSON or Excel files, dropped into shared folders. Every factory had its own layout, nothing was read automatically, and there was no way to look across factories, products or units.
At the same time a new test lab was being set up to check samples from those factories, and it had no system for taking work requests.
What we did
Eagle Eye II is Corning's platform for this data, built on Azure. Our part was getting the data in, and shipping the whole thing safely.
Files arrive by SFTP, through a storage drop, a watched folder or an API. Each one is stored as received, then read by a parser that fits the factory's format: CSV, JSON, Excel, the original Eagle Eye format so older test stations keep working, and spreadsheet layouts described in configuration rather than code.
A new product used to need its test plan and specification set up by hand before its first file could be read. Now a file that names an unknown product, plan or measurement registers it on the spot, and the pass/fail limits travel with each measurement. For unfamiliar spreadsheets, the system suggests a column mapping using AI.
Engineers browse from a unit to its measurements to a single test step. Releases are built once and promoted from development to staging through a gated pipeline. For the lab we built a request flow: a step-by-step form with drafts and attachments, request numbers, email updates, and a queue for the lab manager.
What was hard
No two factories send the same spreadsheet. Some are turned on their side. Some have a different number of test steps per unit. One fiber-array workbook holds 254 measurements per unit in merged header blocks spread across three sheets.
A measurement and its limits were stored as one thing. That's why every new product needed setting up first. Separating what a measurement is from what counts as a pass made automatic registration possible.
Not every gap is a failure. A measurement with no limits to judge it against must not show up as a fail, and a missing measurement is reported rather than holding back the whole file. A factory re-sending the same file is recognised from its contents and ignored.
What's next
Production, then the outcomes we can write up with Corning.
Timeline
- Jun 2026Eagle Eye II project starts
- Aug 2026Pipeline: build once, promote from development to staging
- Aug 2026New products, plans and specs register themselves from incoming files
- Aug 2026Parsers for rotated, variable and multi-sheet spreadsheets; the original Eagle Eye format accepted
- Oct 2026Lab request module built
- NextProduction
Who worked on it
Aleksa Kuzman
Ingestion, automatic product and spec registration, delivery pipeline, lab requests
Next step
Have something like this? Tell us about it.
The first call is free, takes 30 minutes and commits you to nothing.
Book a call