Client Guide : Using Xinet Pilot : Workflows

Local workflow:
In a local workflow, Xinet Pilot can be thought of as an extension to your file system. Instead of being limited to working with your job folders and assets on a mounted/shared volume, you can use the Xinet Pilot user interface to benefit from its additional features such as searching. Xinet Pilot has a dynamic ‘always in-sync’ enterprise database which is not only for searching for file or folder names but also for searching for custom and standard metadata values manually or automatically applied to assets. Applying facets to filter your search query results assists you in easily finding the assets your productions team. In addition, to complement our feature rich application, configurable complex business rules can also be applied to your environment, setup by your Xinet Creative Hub Administrator, to hide assets not relevant for a particular group of users.
Once you have found what you are looking for, using the various browse, search, and filter features, you can either open the file directly from the Xinet Pilot interface with a simple click of a button, or you can display the asset in question in its corresponding file system location on a mounted volume. In addition, an asset can be dragged and dropped into a picture frame of an Adobe CC layout application, such as InDesign or straight into Photoshop, for composing.
For example, you can work on a layout document in Adobe CC, such as InDesign, and save the file. The document’s linked images and fonts are saved on the Xinet server. Because of Xinet’s dynamic and integrated workflow automation engine, an action can be set up to trigger an email to be sent to the client asking them to review the layout document. The client would use a standard Web browser to log into a branded Xinet Portal site and add annotations to that layout document and set a Approved field to ‘rejected’. The change of the Approval field value could (among a large set of other things) set the workflow status and notify the production staff that work needs to be done on the layout document. In addition, by clicking a dynamically generated link in a notification email, a production operator could simply view the annotated asset in Pilot. It only requires a click on a button to then open the layout document directly from within the Pilot user interface to start working on the requested layout modifications.
Remote workflow:
Pilot is connected using a HTTP connection to the Xinet server and therefore can be accessed by a remote team to work in collaboration with the in-house production team.
In a remote workflow, images can be dragged and dropped into a picture frame of an Adobe CC layout application such as InDesign. A low resolution proxy file (FPO) is automatically downloaded to the remote users Mac client and placed into the picture box of an InDesign file. For more information about working with FPO’s, see Working with image proxies.
Pilot has a unique uploading feature which allows users to upload not only multiple files, but also multiple folders including sub-folders and a combination of all. Files and/or folders that need to be uploaded, can be specified in a Finder window or dragged and dropped into the Upload dialog box and if configured, metadata entered is be applied to all of files at the same time the upload tales place.