INNORIX in Practice, Multi-Stage Flow

To complete a single deliverable,
five companies take part.

Different systems, different work environments, different companies.
Today, they carry out a single project together.

TUESDAY MORNING
09:00 A new project begins.
Final deliverable submission
Wednesday 17:00
PROJECT / P-2026-118
1.8 TB Original project data created first

Tuesday 09:00PROJECT / P-2026-118

  • Company AOriginal data creationOn-premisesWork in progress
  • Company BData processingAWSWaiting for data
  • Company CData analysisMicrosoft AzureWaiting for data
  • Company DQuality validationPrivate CloudWaiting for data
  • Company EFinal deliverable productionOn-premisesWaiting for data

Tuesday 09:00Tuesday 18:00Wednesday 09:00Wednesday 17:00

Company A creates the original data

This is a fictional project in which five companies each work on their own infrastructure to complete a single deliverable.

INNORIX in PracticeScene 1 / 10

Tuesday morning09:00

Tuesday 09:00Scene 1 / 10

A project with five participating companies

Five companies carry out their own work for a single project.

Each company runs different infrastructure and business systems. Each company does its work in its own environment and delivers the output the next company needs.

This project starts at one company, but it is not completed at one company.

From the company that creates the original data to the company that produces the final deliverable, each company handles specialized work.

Instead of building a new joint business system, they use the infrastructure and business systems each company already operates.

PROJECT / P-2026-118

Data provider
Company A
Data recipient
Company B
Original data1.8 TBCreating

PROJECT / P-2026-118

One project, five work environments

Participating companyAssigned workInfrastructureBusiness system
Company AOriginal data creationOn-premisesData creation system
Company BData processingAWSData processing system
Company CData analysisMicrosoft AzureAnalysis system
Company DQuality validationPrivate CloudValidation system
Company EFinal deliverable productionOn-premisesDeliverable production system

Project schedule

Project start
Tuesday 09:00
Final deliverable submission
Wednesday 17:00
Participating companies
5
Initial original data
1.8 TB
Work period
2 days

The five companies take part in a single project,
but they do not work on the same infrastructure.

Live contextNow

09:00Tuesday morning

Company A, project manager09:00

Starting today, we begin creating the original data for project P-2026-118.

Work status by participating company
  • Company A Original data creationCreating data
  • Company B Data processingWaiting
  • Company C Data analysisWaiting
  • Company D Quality validationWaiting
  • Company E Final deliverable productionWaiting
Recent data movement
Company A / Company BOriginal data

1.8 TBCreating

Next story, Tuesday 10:20The first data crosses the company boundary. →

Tuesday 10:20Scene 2 / 10

The first data crosses the company boundary.

Company B does not need to change Company A’s work environment.

The original data created in Company A’s on-premises environment has been delivered to Company B’s AWS environment. Company B’s existing processing system starts its work.

The 1.8TB of original data created by Company A has been delivered to Company B.

Company A works in its own data center, and Company B operates its data processing system on AWS.

After receiving the data, Company B starts processing in its existing business system.

PROJECT / P-2026-118

Data provider
Company A
Data recipient
Company B
Original data1.8 TBDelivery complete

TUESDAY, 10:20

The two companies work in different environments.

Company AOn-premises

Original data

/projects/P-2026-118/raw/

  • raw_dataset_01640 GB
  • raw_dataset_02580 GB
  • raw_dataset_03580 GB

1.8 TBData delivery complete

Company BAWS

Data processing environment

P-2026-118 / Processing

  • Original data receivedComplete
  • Input data checkedComplete
  • ProcessingRunning

10:20Data processing started

Original dataset deliveryCompleted

Source
Company A / On-premises
Target
Company B / AWS S3
Size
1.8 TB
Started
09:40
Completed
10:20

Even without unifying the companies’ work environments,
the work continues through the movement of data.

Live contextNow

10:20Tuesday morning

Company B, data processing team10:20

We have received the original data. We will start processing.

Work status by participating company
  • Company A Original data creationDelivery complete
  • Company B Data processingProcessing data
  • Company C Data analysisWaiting
  • Company D Quality validationWaiting
  • Company E Final deliverable productionWaiting
Recent data movement
Company A / Company BOriginal data

1.8 TBDelivery complete

Next story, Tuesday 13:40The work of two companies starts at the same time. →

Tuesday 13:40Scene 3 / 10

The work of two companies starts at the same time.

Outputs needed for different tasks are created from the same data.

Company B has created data for analysis and data for quality validation. Each set of files is delivered to the work environments of Company C and Company D.

Company B’s data processing work is complete.

The result is not a single file but a set of data with different purposes.

Company C needs data for analysis, and Company D needs the data required for quality validation.

PROJECT / P-2026-118

Data provider
Company B
Data recipient
Company C / D
Analysis and validation data666 GBDelivery complete

TUESDAY, 13:40

One task has produced two kinds of output.

Company B, data processing resultsAWS

Data createdSizePurpose
processed_dataset/482 GBData analysis
validation_dataset/180 GBQuality validation
quality_reference/4 GBValidation reference
internal_processing_logs/2.4 GBCompany B internal work

Company CMicrosoft Azure

482 GB

Files for data analysis

  • processed_dataset/

Analysis work started

Company DPrivate Cloud

184 GB

Files for quality validation

  • validation_dataset/
  • quality_reference/

Quality validation started

After one company’s work was completed,
the work of two different companies began.

Live contextNow

13:40Tuesday afternoon

Company B, data processing team13:40

We have delivered the analysis data and the validation data separately.

Work status by participating company
  • Company A Original data creationDelivery complete
  • Company B Data processingProcessing complete
  • Company C Data analysisAnalyzing
  • Company D Quality validationValidating quality
  • Company E Final deliverable productionWaiting
Recent data movement
Company B / Company C / DAnalysis and validation data

666 GBDelivery complete

Next story, Tuesday 15:10Not every company receives all the data. →

Tuesday 15:10Scene 4 / 10

Not every company receives all the data.

The scope of data each company needs differs with the work it performs.

Company C receives only the data it needs for analysis. Company D receives the original data for validation and the reference information, and the setup delivers only the completed result data to Company E, which is responsible for final production.

Taking part in the same project does not mean every company needs access to the same data.

Company D needs data close to the original to perform quality validation. Company C, on the other hand, needs only the processed data required for analysis.

Company B’s internal work records do not need to be delivered to other companies.

PROJECT / P-2026-118

Data provider
Company B
Data recipient
Company C
Analysis data482 GBDelivery complete

DATA BOUNDARIES

Each company receives only the data it needs.

Data typeCompany ACompany BCompany CCompany DCompany E
Original dataCreatesReceives———
Processed data—CreatesReceives——
Validation data—Creates—Receives—
Internal work records—Creates———
Analysis results——Creates—Receives
Final validation results———CreatesReceives
Final project deliverableReceives———Creates

This is the data creation and delivery scope defined in advance for the project.

Company B, data delivery conditionsFlow

Files to includeDelivery targetRun condition
processed_dataset/*Company CProcessing complete
validation_dataset/*Company DProcessing complete
quality_reference/*Company DProcessing complete
internal_processing_logs/*Not deliveredExcluded

Even within a single project,
the data delivery scope is configured differently for each company.

Rather than sharing files with all participating companies, this structure delivers the data allowed for each task directly to designated targets.

Live contextNow

15:10Tuesday afternoon

Company C, analysis team15:10

We have received all the data needed for analysis.

Work status by participating company
  • Company A Original data creationDelivery complete
  • Company B Data processingProcessing complete
  • Company C Data analysisAnalyzing
  • Company D Quality validationValidating quality
  • Company E Final deliverable productionWaiting
Recent data movement
Company B / Company CAnalysis data

482 GBDelivery complete

Next story, Tuesday 16:30A problem was found during validation. →

TIME TRANSITION

TUESDAY, 16:30

Work was already under way at several companies.

The project was progressing smoothly.

Data analysis was in progress at Company C, and quality validation was nearly complete at Company D.

Company D, quality validation team16:30

We found problems in some of the data during quality validation.

Of 2,400 files in total, 18 files need correction. The analysis results that used this data also need to be checked.

validation_report.jsonaffected_files.csv2 attachments, 24 MB

Validated
2,400 files
To correct
18 files
Final submission due
Tomorrow 17:00

Other companies are already using this data.

INNORIX in PracticeScene 5 / 10

Tuesday afternoon16:30

Tuesday 16:30Scene 5 / 10

A problem was found during validation.

The next tasks have already started, and errors were found in some of the data.

Company D found quality problems in 18 data files. It delivers the validation results and the list of files to correct to Company B, and holds the final use of those outputs.

Who should correct the data in which the problem was found?

The problem Company D found had arisen in Company B’s data processing.

There was no problem with the original data created by Company A. So there is no need to create the original data again or to rerun the work of every company from the beginning.

However, some of Company C’s analysis results must reflect the corrected data.

PROJECT / P-2026-118

Data provider
Company D
Data recipient
Company B
Validation results, list of files to correct24 MBDelivery complete

QUALITY VALIDATION

Check the scope of work that needs correction.

Company D, quality validation results16:30

Normal files
2,382
Files to correct
18

These results were created by Company D’s existing quality validation system.

Participating companyCurrent statusRequired follow-up work
Company AOriginal data normalNo further work
Company BProblems in some processed dataReprocess 18 files
Company CAnalysis in progressRe-analyze related results
Company DValidation problem foundRe-validate corrected data
Company EWaiting for final productionWaiting for validated data

New data deliveryCompany D / Company BDelivery complete

validation_report.jsonaffected_files.csv24 MB

The company that found the problem and
the company that must fix it are different.

Live contextNow

16:30Tuesday afternoon

Company D, quality validation team16:30

We found items that need correction in 18 files. We are delivering the validation results.

Work status by participating company
  • Company A Original data creationDelivery complete
  • Company B Data processingPreparing correction
  • Company C Data analysisSome results on hold
  • Company D Quality validationCorrection requested
  • Company E Final deliverable productionWaiting
Recent data movement
Company D / Company BValidation results, list of files to correct

24 MBDelivery complete

Next story, Tuesday 18:10The corrected data is delivered again. →

Tuesday 18:10Scene 6 / 10

The corrected data is delivered again.

There is no need to restart the work of all five companies from the beginning.

Company B reprocesses only the files that need correction. It delivers the corrected data to Company C and D, and the affected analysis and validation are performed again in the existing business systems.

Company B has finished reprocessing the files to correct.

The corrected files are created as a new version so that they can be distinguished from the existing project data.

Company C receives the files needed for re-analysis, and Company D receives the files for re-validation.

PROJECT / P-2026-118

Data provider
Company B
Data recipient
Company C / D
Corrected data v23.6 GBDelivery complete

TUESDAY, 18:10

Only the corrected data is delivered again, not the entire project.

Initial processed datav1

2,400 files

666 GB

  • processed_dataset/v1/
  • validation_dataset/v1/

Existing delivery records kept

Corrected datav2

18 files to correct

3.6 GB

  • corrections/v2/
  • correction_manifest.json

Corrected data delivery run

Project correction deliveryRuns

TargetDatasetSizeStatus
Company CCorrection v22.4 GBCompleted
Company DValidation v21.2 GBCompleted

Follow-up work on the corrected data

  • Company C Re-analysis based on corrected dataReady to run
  • Company D Quality re-validation of corrected dataReady to run

As the corrected data is delivered again,
the follow-up work of the related companies continues.

Deciding what to correct, re-analysis and re-validation are performed in each company’s existing business systems. INNORIX handles the delivery of the designated corrected files and the follow-up transfers that result.

Live contextNow

18:10Tuesday afternoon

Company B, data processing team18:10

We have finished reprocessing the files to correct. We are delivering the new version.

Work status by participating company
  • Company A Original data creationDelivery complete
  • Company B Data processingCorrection complete
  • Company C Data analysisPreparing re-analysis
  • Company D Quality validationPreparing re-validation
  • Company E Final deliverable productionWaiting
Recent data movement
Company B / Company C / DCorrected data v2

3.6 GBDelivery complete

Next story, Wednesday 09:00The final results of two companies are ready. →

THE NEXT DAYWednesday 09:00Scene 7 / 10

The final results of two companies are ready.

The data Company E needs for final production is ready.

Company C’s analysis results reflecting the corrections and Company D’s final validation results have been created. Each is delivered directly to Company E, and final production starts after all the required results are confirmed.

Overnight, Company C created analysis results reflecting the corrected data, and Company D completed re-validation.

Now the data needed by Company E, which is responsible for producing the final deliverable, is delivered.

Company E needs the final results of both companies. It cannot start final production with only the analysis results or only the validation results.

PROJECT / P-2026-118

Data provider
Company C / D
Data recipient
Company E
Final analysis, validation results68.4 GBDelivery complete

WEDNESDAY, 09:00

The outputs of two companies needed for final production

Company C, data analysis

68 GB

  • analysis_results_v2/
  • analysis_summary.json

08:42Delivery complete

Final analysis results

Company D, quality validation

400 MB

  • validation_report_v2.pdf
  • quality_results_v2/

09:00Delivery complete

Final validation results

Company E, final deliverable productionOn-premises

Required dataDelivery completedStatus
Company C’s final analysis results08:42Complete
Company D’s final validation results09:00Complete
Project data version check09:00Complete

Data ready for delivery to the final production system

The results of work performed at different companies
become the start of new work at another company.

Live contextNow

09:00Wednesday morning

Company D, quality validation team09:00

Validation of the corrected data is complete. We are delivering the final validation results.

Work status by participating company
  • Company A Original data creationComplete
  • Company B Data processingComplete
  • Company C Data analysisAnalysis complete
  • Company D Quality validationValidation complete
  • Company E Final deliverable productionIn final production
Recent data movement
Company C / D / Company EFinal analysis, validation results

68.4 GBDelivery complete

Next story, Wednesday 14:20A single deliverable is complete. →

Wednesday 14:20Scene 8 / 10

A single deliverable is complete.

The work performed at five companies is completed as a single deliverable.

Company E’s existing production system has created the final deliverable. After checking the project identification information, the data versions used and the validation results, it prepares the final delivery.

Company E has finished producing the final deliverable.

The final deliverable reflects Company C’s analysis results and Company D’s validation results.

Now it is time to deliver the completed deliverable to Company A, which first started the project.

PROJECT / P-2026-118

Data provider
Company E
Data recipient
Company A
Final project package126 GBPreparing delivery

WEDNESDAY, 14:20

The work of five companies has been completed as a single deliverable.

FINAL PROJECT PACKAGEP-2026-118

  • final_deliverables/124 GB
  • project_documentation/1.6 GB
  • analysis_summary/280 MB
  • quality_report/120 MB

126 GBFinal project deliverable

Work reflected in the deliverable

  • Company A Original data creationComplete
  • Company B Data processing and correctionComplete
  • Company C Final data analysisComplete
  • Company D Final quality validationComplete
  • Company E Deliverable productionComplete

Final project deliveryFlow

SourceCompany EFinal deliverables
TargetCompany AProject repository

Data delivered after final submission approval

The project was carried out at five companies,
but there is one final deliverable.

Live contextNow

14:20Wednesday afternoon

Company E, production team14:20

Production of the final deliverable is complete. We are preparing the files for submission.

Work status by participating company
  • Company A Original data creationComplete
  • Company B Data processingComplete
  • Company C Data analysisComplete
  • Company D Quality validationComplete
  • Company E Final deliverable productionCreating final deliverable
Recent data movement
Company E / Company AFinal project package

126 GBPreparing delivery

Next story, Wednesday 16:42The project is complete. →

Wednesday 16:42Scene 9 / 10

The project is complete.

Along with the final deliverable, the data delivery process can also be checked.

The final deliverable has been delivered to Company A, which started the project. Each company checks the transfer records it is responsible for, and authorized project managers check the delivery process through the shared run records.

The final deliverable has been delivered to Company A, which started the project.

Receiving the final deliverable alone does not explain the whole project process.

It must be possible to check which data was delivered to which company, which files were delivered again during the correction, and which data versions were reflected in the final result.

PROJECT / P-2026-118

Data provider
Company E
Data recipient
Company A
Final project package126 GBDelivery complete

PROJECT COMPLETION

Until a single deliverable is completed

Participating companies
5
Final deliverable
126 GB
Final delivery complete
16:42

Project work in progressCorrections and follow-up work

Project transfer historyP-2026-118

SourceTargetDatasetStatus
ABOriginal dataCompleted
BCAnalysis datasetCompleted
BDValidation datasetCompleted
DBCorrection requestCompleted
BCCorrection v2Completed
BDValidation v2Completed
CEAnalysis resultsCompleted
DEValidation resultsCompleted
EAFinal deliverablesCompleted

Company A, project manager16:42

We have received the final deliverable. Thank you, all participating companies, for your work.

Not only the deliverable,
but also the data movement that went into making it remains on record.

Live contextNow

16:42Wednesday afternoon

Company A, project manager16:42

We have received the final deliverable. We will wrap up the project.

Work status by participating company
  • Company A Original data creationComplete
  • Company B Data processingComplete
  • Company C Data analysisComplete
  • Company D Quality validationComplete
  • Company E Final deliverable productionFinal delivery complete
Recent data movement
Company E / Company AFinal project package

126 GBDelivery complete

Next story, One week laterA new project begins. →

THE NEXT PROJECTOne week laterScene 10 / 10

A new project begins.

The five companies do not work together only for this project.

The next project uses new original data, and the data processing and analysis conditions may also change slightly.

But the participating companies and the data delivery method can reuse the existing setup.

ONE WEEK LATER

A new project, the existing collaboration environment

Previous projectP-2026-118

1.8 TB original data

  • Company A, data creationComplete
  • Company B, data processingComplete
  • Company C, data analysisComplete
  • Company D, quality validationComplete
  • Company E, final deliverable productionComplete

Project complete

New projectP-2026-119

2.4 TB new original data

  • Company A, data creationIn progress
  • Company B, data processingWaiting
  • Company C, data analysisWaiting
  • Company D, quality validationWaiting
  • Company E, final deliverable productionWaiting

New project started

The project changes, but
there is no need to build a new inter-company data delivery environment every time.

Live contextNow

One week later

Company A, project manager16:42

We have received the final deliverable. We will wrap up the project.

Work status by participating company
  • Company A Original data creationComplete
  • Company B Data processingComplete
  • Company C Data analysisComplete
  • Company D Quality validationComplete
  • Company E Final deliverable productionFinal delivery complete
Recent data movement
Company E / Company AFinal project package

126 GBDelivery complete

ONE PROJECT. FIVE COMPANIES.

Five companies
do not need to work the same way.

On their own infrastructure, using their own systems,
each receives the data it needs and carries out its work.

  • Company AOriginal creationOn-premisesComplete
  • Company BData processingAWSComplete
  • Company CData analysisAzureComplete
  • Company DQuality validationPrivate CloudComplete
  • Company EDeliverable productionOn-premisesComplete

FINAL PROJECTP-2026-118

126 GB

Wednesday 16:42Final delivery complete

The work differs from company to company.
But it all leads toward a single result.
INNORIX

THE TECHNOLOGY BEHIND THIS STORY

Multi-Stage Flow

Delivers data created at different companies and systems to the work environments that need it, and configures follow-up file transfers based on the results of preceding work and run conditions.

View product details