Manage the devices across every factory and branch in one place
See the Windows and Linux servers and the work PCs scattered across your factories and branches at a glance in Devices in INNORIX Studio. Instead of running a separate file transfer setup wherever devices happen to sit, review connection states and the paths transfers use, and manage site-to-site Flows and Runs from one operating screen. A new site can be brought in without disturbing the devices and transfers you already run.
Wie es aufgebaut ist
- Connect the devices at each site.
Install and authenticate the Agent on the supported servers and PCs at each factory and branch, or register them with Bulk provisioning where that suits. Confirm in Devices that they are online.
- Decide how you will tell devices apart.
Use the device name, group, tag and search features Studio actually provides to identify factory, branch and role. Where there is no separate grouping feature, apply a consistent device naming rule such as
SEOUL-FACTORY-01. - Check connection and paths per device.
In Devices, review the state and the detail of each device and confirm the access rights needed on the paths files are read from or written to.
- Compose the transfers between sites.
In Flows, set the head office server and the factory or branch servers as source or target and compose the transfers you actually need, whether distribution or collection. Where a Flow already exists, confirm the devices and paths attached to it are correct.
- Watch transfers and operations in one place.
In Runs, review the running, completed and failed results per site, and for a disconnected device or a failed job, check that device network, permissions and run records.
Wo es eingesetzt wird
- Running production files across factories
Each factory server connects to the central Studio so that collecting production output to head office and distributing reference files to the floor are managed together. Source and target paths are kept distinct per factory.
- Running branch servers nationally
Transfer jobs that used to be checked branch by branch are reviewed by the central operations team in Runs, which shows where a transfer stopped.
- Exchanging data between overseas sites and head office
Overseas branch servers connect to the head office server with scheduled transfers that account for time zones and line quality. Long-distance transfer performance is verified on the real circuit.
- Extending operations when a new factory opens
New factory devices are registered, identified according to the existing naming rule and permission policy, and attached to the distribution and collection Flows they need.
- Distributing design and configuration files per factory
Approved files from head office are delivered to several factory servers and completion is confirmed per factory. A completed delivery and a file actually applied to the equipment are verified separately.
- Handling incidents across sites
When a transfer fails at one branch, the job is found in Runs and the device connection state in Devices, separating a network problem from a file path or permission problem.
- Standardising distributed transfer operations
File transfer paths and run times that differ site by site are organised around Flows, so handover and audit can read the run records easily.
Anwendungsleitfäden
Häufig gestellte Fragen
Is there a file transfer solution that manages servers across many factories and branches on one screen?
INNORIX Studio is a platform that connects servers and PCs in many locations to Devices and runs device-to-device file transfers as Flows and Runs. It can be used to review device state and transfer results per factory and branch centrally.
Can factory and head office servers on different networks be connected?
INNORIX supports transfer setups between devices across several network environments. Whether a connection is actually possible, though, depends on device network reachability, firewall, proxy and private network setup, security policy and the product deployment method, so a connection test up front is needed.
Can a mix of Windows and Linux servers across factories be managed together?
Devices on different supported operating systems — Windows, Linux, macOS — can be connected and run together. The supported Agent version, install rights and path access method for each OS have to be confirmed individually.
Can devices across sites be viewed separately per location?
Device names and the search and classification features Studio actually supports can be used to identify devices per site. Whether a particular group, tag or folder feature is offered has to be confirmed on the product version, and an operating procedure should not be designed around a classification feature that is not provided.
If a factory device is offline, do transfers at other branches stop too?
How it is handled depends on how the transfer job is composed and on the state of each target. On a job involving several devices, you can review the affected devices and the failed Run and recover only the targets you need. It is not guaranteed that jobs on other devices are always unaffected in every environment.
Can device access and file transfer permissions be set differently per branch?
In multi-site operations, what matters is separating user roles, device access scope and Flow execution rights. Confirm the actual INNORIX permission model and what your deployment plan supports, then set the rights for central administrators and site owners accordingly.
Can a central operator see transfer failures across several branches?
Runs in INNORIX Studio shows the state and the result of transfer jobs. When deciding the cause of a problem, it is better to review the Runs records together with the online state of that device, the network and the storage path permissions.
Does a new factory or branch mean rebuilding the transfer system?
You extend by registering the devices at the new site and adding them to the Flow or Dataset you need. Whether the source, target, schedule and permissions of an existing transfer can be preserved depends on how that Flow and Dataset are composed.