Day 1, 09:12Scene 1 / 15
The work starts in the web service.
The customer creates a new project and requests the work.
The company runs a web service that delivers specialist project work to its customers.
Customers sign in to request the work they need and follow the progress of their projects.
On Monday morning, a customer company registers a new project.
Projects / New project
New product development request
Project nameProduct development 2026
Requested delivery dateFriday
Project descriptionWe would like to start a new project based on our existing product materials. Detailed requirements will follow with the materials.
Attachments
Choose filesMaximum file size: 20 MB
Submit requestThe materials the customer wants to submit come to 4.8 GB.
The web service’s attachment feature cannot carry all of it.
So the customer registers the project first and decides to send the files to the manager separately.
It is a way of working both sides know well.
AT THIS MOMENTNow
Status in the web serviceRequest received
- Current materials
- Not submitted yet
- Where the materials are
- Customer workspace
NextWaiting for materials
Next story, Day 1, 09:24Materials by email →Day 1, 09:24Scene 2 / 15
The materials arrive by email.
The customer sends the project files to the manager’s email address.
Having registered the project, the customer emails the manager.
The documents small enough to attach go in the email; the rest follow as a download link.
INBOX, 09:24
Materials for the new project
FromCompany A
ToProject manager
Hello, we just requested a new project on your website.
Here are the materials for the work. Please download the large files from the link below.
project_requirements.pdf12 MB
source_materials_v1.zip4.8 GB, External link
Web service
Project #2048
Request received
No work files attached
Manager’s PC
Downloads
source_materials_v1.zip
Download complete
The manager reads the email and downloads the files.
Then they open the project in the web service and work out whether the downloaded files belong to it.
The project’s record is in the web service, but the materials needed to start the work are on the manager’s PC.
AT THIS MOMENTNow
Status in the web serviceIn progress
- Current materials
- source_v1.zip
- Where the materials are
- The manager’s email
NextDownload the files
Next story, Day 1, 10:42A revised file →Day 1, 10:42Scene 3 / 15
Another file for the same project arrives.
The customer sends revised files by messenger.
The customer finds mistakes in the materials sent that morning.
After correcting it, this time they send the file through the messenger they usually use with the manager.
Customer, 10:42
Some of the files I emailed earlier need changes.
Please go ahead with this one.
Manager, 10:45
Got it, I will check the revised files.
The manager’s project folder
| File name | Received from | Time |
|---|
| source_materials_v1.zip | Email | 09:24 |
| source_final.zip | Messenger | 10:42 |
The manager downloads the corrected file.
But whether the new file replaces everything or only part of it still has to be checked.
The other manager still has only what came by email that morning.
The web service has no record that the customer sent a revised file.
AT THIS MOMENTNow
Status in the web serviceIn progress
- Current materials
- source_final.zip
- Where the materials are
- Email, messenger
NextConfirm the final files
Next story, Day 1, 14:36An external share link →Day 1, 14:36Scene 4 / 15
This time the file cannot be attached at all.
The customer sends more files through an external share link.
In the afternoon the customer sends more materials.
8.6 GB of them.
The customer uploads them to the file-sharing service they use and sends a download link.
EXTERNAL FILE SHARING
Company A shared a file with you.
source_final_revised.zip
8.6 GB
Shared by Company AExpires in 7 days
Download filePROJECT #2048, how the materials arrived
| File | Delivered by | Held by |
|---|
| source_materials_v1.zip | Email link | Managers A, B |
| source_final.zip | Messenger | Manager A |
| source_final_revised.zip | External share link | Manager A |
For one project, the customer has used three ways of sending files.
The manager collects files from three places and sorts them on their own PC.
Which file the work should use now depends on conversations between managers and personal judgement.
AT THIS MOMENTNow
Status in the web serviceIn progress
- Current materials
- source_final_revised.zip
- Where the materials are
- Email, messenger, external sharing
NextDownload the file
Next story, Day 2, 11:30Work on the wrong file →Day 2, 11:30Scene 5 / 15
Each manager was using a different file.
Two managers work from different versions of the files.
The two staff on the project had been working on their parts since the morning.
Reviewing the results, they find they used different materials.
THE SAME PROJECT, DIFFERENT SOURCE MATERIALS
Two managers were working on the same project.
Manager A
Project #2048
Working source
source_final_revised.zip
8.6 GB
Received Mon 14:36
Progress
65%
Manager B
Project #2048
Working source
source_materials_v1.zip
4.8 GB
Received Mon 09:24
Progress
80%
PROJECT REVIEW MEETING, 11:30
Manager A: Didn’t the customer send new files yesterday afternoon?
Manager B: I was working from the files that came in the morning.
They decide to confirm the final materials with the customer.
Both had done their work properly, from the materials they had been given.
The problem was not a file that never arrived. It was that there was no place where everyone on the work could start from the same materials.
Part of the work had to be done again.
AT THIS MOMENTNow
Status in the web serviceIn progress
- Current materials
- Final version unclear
- Where the materials are
- Several managers’ PCs
NextStop and check
Next story, Day 3Reviewing the history →Day 3Scene 6 / 15
The web service held only the status of the work.
The operations team compares the project record with the file delivery history.
To find out what went wrong, the operations team reviews the project’s history.
The web service the company built has correctly recorded when the project was received, who handles it and its status.
But which files the work had actually used was hard to establish.
PROJECT HISTORY REVIEW
What the web service recorded, and what really happened
| Time | Recorded in the web service | What actually happened |
|---|
| Mon 09:12 | Project received | Project requested |
| Mon 09:24 | No record | Files sent by email |
| Mon 10:42 | No record | Revision sent by messenger |
| Mon 14:36 | No record | External share link sent |
| Tue 09:00 | In progress | Each manager works from their files |
| Tue 11:30 | In progress | Different files found in use |
| Tue 13:15 | In progress | Final files reconfirmed with customer |
What the operations team found
The work was managed, but the data the work used was not.
The team looks at other projects too.
They find customer materials that exist only in someone’s personal email, share links that have expired, and final results that exist only on one manager’s PC.
The company had built a system to manage the work, but moving the data the work needs still depended on individual tools and people.
AT THIS MOMENTNow
Status in the web serviceIn progress
- Current materials
- Delivery history incomplete
- Where the materials are
- Several outside services
NextReview how the work is run
Next story, Late in week oneDeciding to improve the service →Late in week oneScene 7 / 15
The work’s data will be managed in the web service too.
The development team integrates file transfer into the existing service.
The company is not trying to give customers a different service.
It decides to improve the web service customers already use, so they can submit materials, send revisions and receive finished results there.
The development team integrates INNORIX file upload and download into the existing service.
WEB SERVICE INTEGRATION
How work changes inside the same web service
Before
Customer workspace
Project #2048
Project information
The work requested
Managers and status
Attachments
Maximum file size: 20 MB
Choose filesProject activity
Status changes
After the integration
Customer workspace
Project #2048
Project information
The work requested
Managers and status
Project materials
Files and folders, INNORIX
Add project materialsProject deliverables
Register and download results
Project activity
Status and file delivery history
WEB SERVICE INTEGRATION
- Embedded file upload & download
- Project authentication
- File storage integration
- Transfer completion events
Customer accounts and project management stay as they were.
The team links each submitted file to its project and lets the managers see it once it has arrived intact.
Revisions, history and who may access what follow the web service’s existing policies.
INNORIX provides the file transfer technology this needs.
AT THIS MOMENTNow
Status in the web serviceImproving the service
- Current materials
- Materials submitted per project
- Where the materials are
- Customer workspace
NextIntegration test
Next story, Week twoConnecting what follows a file →Week twoScene 8 / 15
The team connects what happens after a file arrives.
The team does not stop at letting files go up and down.
The result of each transfer has to show up in the web service’s work.
A project must not show as ready before the customer’s materials have arrived intact, and when a revision is submitted, the project’s managers must be able to see it.
APPLICATION INTEGRATION
Project work and file transfer events
| Customer or manager action | Transfer status | Web service response |
|---|
| Project created | Not started | Waiting for materials |
| Materials submitted | Uploading | Materials arriving |
| Network dropped | Interrupted | Status kept, user informed |
| Transfer complete | Completed | Checked and registered to the project |
| Revision submitted | Completed | Revision registered, managers notified |
| Results registered | Completed | Customer told results are ready |
| Customer download | Completed | Download recorded |
INTEGRATION TEST
Project #TEST-2048
source_materials.zip12.8 GB
Transfer completed
- 14:32:08Transfer completion confirmed
- 14:32:09Materials registered to the project
- 14:32:12Managers told the work is ready
The team also keeps a finished transfer apart from finished work.
A file arriving intact does not complete the work by itself.
Review, approval and revision requests carry on as before.
AT THIS MOMENTNow
Status in the web serviceImproving the service
- Current materials
- Materials submitted per project
- Where the materials are
- Customer workspace
NextIntegration test
Next story, Month 1, 09:12A new project →