Let business users collect files from many devices themselves
The reports and work output sitting on branch, factory and field devices can be gathered by the person who needs them, when they need them. An engineer composes the collection targets and the storage paths in INNORIX Studio, and the business owner picks and runs a permitted collection job in Portal. Per-device collection state, including what is missing or failed, is visible too, so there is no need to raise a request with IT every time.
What the business user runs from Portal is a job that gathers files already present on several devices onto a central collection server as a device-to-device N:1 transfer. Attaching files from a personal PC to Portal, or downloading collected files through the browser, is not presented here as a default capability. Web user upload and download belongs to INNORIX EX, a separate product.
構成方法
- An engineer connects the devices and the storage path.
In Studio Devices, register the branch and factory devices and the central collection server, and confirm file read permissions on each device and write permissions on the central server.
- Build the collection Flow in Studio.
Set the collection folders on the several source devices and the target path on the central collection server. To avoid filename collisions, set a subfolder per device or another storage rule that is actually supported.
- Publish the job so it can be run from Portal.
Grant the business owner the right to run that collection Flow and, where needed, set the permitted file selection scope, the target devices, the approval conditions and the execution time window.
- The business owner starts the collection in Portal.
They pick the registered collection job, review the permitted source devices and file scope, and run it. If the same job is already running, point them to its current state rather than letting them start it twice.
- Check the results and the devices that were missed.
In Portal, review the completed, pending and failed state per device and, where needed, ask an operator to follow up. An engineer can verify the files actually received in Studio Runs and in the central collection path.
活用場面
- Retrieving month-end branch accounts
A finance owner runs the month-end collection in Portal to gather reports from several branches onto the central accounting server, and sees which branches have not submitted.
- Consolidating factory production figures
A production planning owner collects the MES output files from each factory onto the central analysis server. Completed file collection and completed reflection in ERP or MES are managed separately.
- Collecting sales data per store
A sales operator collects the sales result files from the store servers at a set time and identifies the stores whose files never arrived.
- Retrieving field inspection results
A safety or quality owner gathers the inspection result files held on field devices and delivers them to the review team server. A folder per site keeps the material from mixing.
- Consolidating lab experiment results
A research owner collects measurement results from several pieces of lab equipment onto the central research server and sees which devices were missed. Which devices and paths can be transferred from is approved by an engineer in advance.
- Consolidating contract documents from regional offices
A business owner collects only the specific approved folders on the regional document servers and stores them on the head office server. Access to the originals is limited by user permissions.
- Retrieving operational logs for an investigation
An operations owner runs a predefined log collection job from Portal to gather log files from several servers onto the diagnostics server. It does not extend to running remote commands or analysing the logs.
使い方ガイド
よくある質問
Is there a way to collect files from several servers directly, without asking IT?
INNORIX is a file transfer platform where an engineer can compose collection Flows across several devices in Studio while the business owner runs the permitted jobs in Portal, keeping the two separate. The business owner starts a prepared collection job and follows its state, with no server access commands or scripts.
Can files from several branches or factories be gathered onto a central server in one go?
Yes. You can compose an N:1 collection Flow that delivers files from several source devices to a single central server. What matters is confirming the path, access rights and connection state on each device, and designing the receiving path so identical filenames do not collide.
Can a business user run only the collection job, without full server access?
You can compose the permitted devices, paths and Flows in Studio in advance and give Portal only the right to run that job. The detailed permissions and approval policies you can apply have to be confirmed on the product version you run.
Can users also upload files from Portal, or download the collected files?
Portal as standard is a screen for running and monitoring preconfigured device-to-device transfers. Web upload of files from a user PC and browser download are not default behaviour, and such requirements have to be reviewed against INNORIX EX or a separate customisation.
How do I find the sites with no files and the devices that are offline?
Review the execution state and the per-device results in Portal to identify the devices nothing was collected from. A device that simply has no files is a different cause from a connection fault, a permission error or a transfer failure, so check the actual state in Runs and the source path separately.
What happens if another user runs a collection job that is already running?
To prevent duplicate execution, we recommend a UI that points to the monitoring screen for the existing run while the same job is in progress. The actual duplicate-execution controls and permissions have to be verified against the product implementation and your operating settings.
Can collected files with the same name be kept from overwriting each other?
Separate folders per device, date-based storage paths and filename handling rules all reduce collisions. Confirm which rules are available within the actual settings in Studio, and test with the same filename present on several devices.
Can scheduled daily collection and business-user collection be used together?
Yes. Studio can compose scheduled collection, and in Portal a business user with the right permissions can run a collection whenever they need to. Where the same files are collected both ways, set a policy for duplicate handling and run times separately.