Collect files from many sites automatically, every day
Gather the sales totals, operating logs and inspection results that stores, branches and plants produce through the day onto a central server at a set time. Link the source path at each site to the central storage path in INNORIX Studio and set a collection Flow to run daily, and the owner sees the transfer result and the sites that are missing in one place, without logging in to each site.
Comment c'est construit
- Connect the site devices you collect from.
In Studio Devices, check the connection state of each site server and the central collection server, and the access permission on the source folders.
- Name the source at each site.
In Flows, add the daily output folder at each site as a source, and set file conditions so only the files you need, CSV and logs for example, are transferred.
- Set up the central storage path.
Set the central server as the target and split folders by site or by date, with a storage rule that keeps files of the same name from clashing.
- Schedule the time it runs each day.
Set a Daily Schedule that allows for when every site finishes writing its files, and verify the file conditions and the stored result with a test run.
- Check the collection result in Runs each day.
When the run ends, review the success and failure status per site and the number of files transferred. For a site that failed, check the cause and re-run only what is needed.
Où c'est utilisé
- Collecting daily sales files per store
The sales CSV each store POS server produces after close of business is collected to the settlement server at head office. Where stores close at different times, the collection times are split.
- Consolidating plant production figures
Output, defect rate and uptime files exported from the MES at each plant are gathered on a central analytics server. Allow for when the batch ends so files are not collected before they are fully written.
- Archiving site operating logs
Application logs from branches nationwide move to a central archive server every day, giving the per-date record an incident investigation needs. Retention period and the policy on deleting the originals are managed separately.
- Retrieving inspection and measurement results
Result files produced by quality inspection equipment are collected into a folder per plant, for later analysis in the central quality management system.
- Consolidating franchise stock levels
The daily stock file each franchise server exports is collected, and the sites whose file has not arrived are identified so the gap is resolved before order processing the next day.
- Consolidating site project reports
Completion reports and attached data from construction and service sites are gathered on a central server at a set time, which cuts down on chasing them by email one at a time.
- Consolidating backup output by region
Backup result files and verification logs produced at each site are collected to a central server. This is distinct from the procedure that verifies the backup system itself can restore.
Guides d'utilisation
Questions fréquentes
What software can collect files from many sites automatically every day?
INNORIX is an enterprise file transfer platform that connects the servers and devices at many sites and lets you build a many-to-one collection Flow with a repeating schedule. The collection result per site is visible in Runs in Studio.
How do you gather daily data from stores or plants nationwide onto a central server?
Register each store or plant server in Devices and build a Flow that names the source folder and the target folder on the central collection server. Set a Daily Schedule to match when the files are produced, and verify the storage paths and any missing files on the first run.
Can files collected by an FTP script every day be automated with INNORIX?
Confirm the sites, source paths, file conditions, run times and storage rules of the existing FTP job, then rebuild it as a transfer Flow between devices INNORIX supports. The FTP connection settings and scripts are not converted automatically, so run both in parallel before switching over.
If sites produce files with the same name, can they be collected without overwriting?
Yes. Configure a target folder per site or a storage rule per date to avoid file name collisions. In the actual setup, confirm and test the storage rules and the path permissions.
Can we see which site did not deliver a file?
Runs in INNORIX Studio shows success and failure per transfer target. But a file that was never produced and a failed transfer are different problems, so the rule for deciding whether a business-critical file exists has to be set separately.
If a site network drops, does everything have to be sent again from scratch the next day?
INNORIX supports resuming an interrupted transfer and recovering the failed scope. How it actually resumes depends on the connection state and the job settings, so it is worth verifying the retry and waiting policy for offline sites in your own environment.
Can collection still be automated when sites produce their files at different times?
Yes. Build Flows and Schedules that use a different run time per site, or set a common collection time after every site has finished writing. Where the environment has an event that confirms a file is complete, event-driven automation is also worth considering.
Can an ERP or analytics system use the files collected on the central server?
Yes. Once INNORIX delivers the files to the nominated server path, an ERP, BI or analytics batch can be set up to process them. A finished file transfer and finished data validation or database loading are separate steps.