INNORIX in practice

Stories set in realistic company environments that show the part INNORIX plays in data operations and web services.

Server & Cloud-to-Cloud Transfer

  • Three different clouds

    Teams in the same company run on different clouds.

    Each team chose the cloud that fit its work. Now the data in those different environments has to be used together.

    Read the story
  • Old infrastructure → new infrastructure

    The servers and clouds used for years have to be replaced.

    Daily work goes on while the systems are replaced. How do the existing data and transfer jobs move across?

    Read the story
  • Zero people on transfers

    A company with nobody in charge of file transfer

    Every day a great deal of data moves between systems. Nobody manages that process by hand.

    Read the story
  • An unexpected failure

    The day nothing went to plan

    The day starts like any other. Then unexpected problems begin to pile up in the network and the storage.

    Read the story
  • End of one day, start of another

    When one team ends its day, another is waiting for that data.

    Work finished by one team becomes new work for another. In between is data that has to get there.

    Read the story
  • Data volume ×100

    In three years the data to handle grew a hundredfold.

    The data grew every year. Is the transfer infrastructure that used to be enough still enough?

    Read the story

Fleet-Scale Distribution

  • Thousands of devices, before 9 a.m.

    Tomorrow at 9 a.m., a new service starts nationwide.

    Preparation for the new service has begun. Each device connects differently, but the deadline is the same for all.

    Read the story
  • An error found after rollout

    An error is found in a file already delivered to thousands of devices.

    The rollout is already done and some devices are using the new file. Where does the fix start?

    Read the story
  • A ten-year technology gap

    A company running devices installed ten years ago alongside ones installed yesterday

    Different generations, operating systems and connections. All of them still do the same company’s work.

    Read the story
  • A fleet 100 times larger

    What happened at a company whose fleet grew a hundredfold?

    A few dozen devices became a nationwide fleet. Does the operating work have to grow with it?

    Read the story
  • Connection time unknown

    A company that never knows when or where its devices will connect

    Devices on the move and devices that connect now and then. The window to deliver files is different for each.

    Read the story
  • Thousands of devices, one version

    Thousands of devices, run in one consistent state.

    Thousands of devices running in different places. Every one of them has to be using exactly the right files.

    Read the story

Fleet-Scale Collection

  • Every site, before 9 a.m.

    Tomorrow morning's meeting needs data from every site nationwide.

    A day of data from every site has to come together for one meeting. The meeting time is already set.

    Read the story
  • Field data → company asset

    Data produced in the field becomes a company asset.

    Countless field devices produce new data every day. Data that used to stay on each device starts feeding new work.

    Read the story
  • One device → the whole fleet

    A problem on one device turns into an investigation of devices nationwide.

    A problem found at one site may exist on other devices too. Now the data from every device has to be checked.

    Read the story
  • Data from six months ago

    You need to know what happened in the field six months ago.

    Data that did not matter at the time is now the clue to the problem. Where are the files?

    Read the story
  • Collection that began with 100 devices

    At first it meant collecting data from 100 devices.

    More sites, more data to collect. How far can the collection setup designed at the start stretch?

    Read the story
  • Daily data, irregular connections

    Devices produce data every day, but they are not connected every day.

    Field work goes on while the network is down. When does the data that piles up reach the company?

    Read the story

Inter-Site Transfer

  • Work that runs around the clock

    As we head home, the other side of the world starts work.

    Before one side’s day ends, the other side’s work has to be ready. A company working across time zones.

    Read the story
  • Very different networks

    Not every site has a stable network.

    From a head office on a fast leased line to an overseas site with a shaky connection. The work matters just as much at both.

    Read the story
  • Acquisition → new work sites

    The sites of the company we acquired are now ours too.

    Two companies with different systems and security policies. Now they need a way to work together without tearing either down.

    Read the story
  • 3 TB, overnight

    The 3TB design the lab finished today is needed overseas tomorrow.

    After months of research the design is done. All of it has to arrive before the overseas site starts its next shift.

    Read the story
  • Moving a work site

    From next month, this work moves to another site.

    Work done in one place for years moves somewhere new. Its data and transfer setup have to be ready there too.

    Read the story
  • Many sites, one piece of work

    Sites are spread out, but the work is not split.

    Sites in different regions, each doing its part. They exchange data every day to finish one deliverable.

    Read the story

Embedded Web Upload & Download

  • 500 GB, straight from the web

    The file a customer wants to submit is 500 GB.

    The customer opened the web service as usual. Only the file size changed, and the existing service cannot handle it.

    Read the story
  • Eight weeks to launch

    A new web service has to launch in eight weeks.

    The schedule is already tight. The core features have to be built while the file transfer problem gets solved too.

    Read the story
  • Local service → global service

    Customers abroad started using a web service built for local customers.

    The service now reaches the world. Distance and network problems never seen at home begin to show up.

    Read the story
  • Work on the web, files by email

    Customers request work on the web service but send the files by email.

    The work system is digital, but the files still travel separately. Staff match the two up every single time.

    Read the story
  • File submitted → work begins

    What does a submitted file go through before it reaches the employee’s desk?

    For the customer it is one upload. Inside the company it starts validation, security checks, storage and delivery.

    Read the story
  • Replacing ten-year-old transfer technology

    The file transfer technology of a ten-year-old web service has to be replaced.

    Thousands of customers use it every day. The switch has to happen with the least possible impact on the work and the applications.

    Read the story

Multi-Stage Flow

  • File arrives → next work

    When a file arrives, the next piece of work begins.

    One file arrives, validation starts, new data is produced and passed to another system. The work follows the file.

    Read the story
  • Hundreds of automation programs

    What happened at a company running hundreds of automation programs?

    Every new task got a new program. At some point managing the programs became harder than the work itself.

    Read the story
  • Scheduled time, data not yet here

    Again today, not all the data arrived on time.

    Some data is ready, the rest has not arrived. Which work has to wait, and which can start now?

    Read the story
  • Five companies, one deliverable

    Five companies take part in finishing a single deliverable.

    Each company works in its own systems. One company’s output is the data the next one needs.

    Read the story
  • Next month, new procedures

    From next month, every procedure in the company changes.

    Teams, systems and the order of work all change at once. The many automated transfers have to follow the new procedures.

    Read the story
  • One request → the whole job

    What happened on the first day a company handed work to AI?

    An employee asks AI for what they need. From understanding the request to moving the data and finishing the work, what does it take?

    Read the story