The Caldera Prime Centre production integartion can be enabled on a production centre company inside our platform
The screens above show the details needed to enable the Prime Centre integration
Enabled - Yes / No
Auto Transfer Enabled - Yes / No this determines if jobs are sent to S3 as soon as they are ready without manual intervention
Run Interval - How often the integration should run
Start Timestamp (UTC) - Sets the earliest creation time of a job the integration will pick up
Preferred Artwork Format - The artwork format we send to S3
Local Output Path - The local path files will be output
Filesystem Type - S3
Filesystem Root - The directory relative to root
Bucket - The name of the S3 bucket connected
Region - The Amazon region of the S3 bucket
Access Key - The Access Key for the S3 bucket
Access Secret - The Access Secret for the S3 bucket
We utilise an established method of communication with Caldera which is XML data to provide prepress instructions for how our platform generated files need to be managed
As Caldera runs locally we have to get the output files from the system into the input folders for Caldera efficiently. Our solution is that we push the files into an S3 bucket and then a service called rClone can be run locally to mount S3 as a network drive which is then directly synced and available from the machine running Caldera. The input folder can be set to listen to this shared drive and and pull files in when ready. Full details of how to configure rClone is available here - https://www.nakivo.com/blog/mount-amazon-s3-as-a-drive-how-to-guide/ . Please Note, there are other tools that allow you to access S3 in similar ways, rClone is just an example of one and is not affiliated with us.
The below video was done by Caldera and helps give some context around the capabilities of the Prime Centre Software
Custom Gateway have produced a production solution we call Hotfolder Feed. This is made up of the system modules we offer and an local piece of software used to manage queues and move artwork and jobsheets to printing locations. A high level view of ...
Note - The Kornit Quick P PRODUCTION INTEGRATION should not be used in conjunction with the RIP INTEGRATION of the same name. The RIP INTEGRATION performs the same functions as the PRODUCTION INTEGRATION and should be used on its own. Like other ...
The default production integration is "Standard Download". This does not need to be enabled as a fixed integration on the production centre and it is only replaced if another integration is enabled which alters the default behaviour. This integration ...
Custom Gateway have produced an integration with Print Factory - https://app.printfactory.cloud/ This is a Production Integration as the Production Module allows jobs to be sent to Print Factory which then managed print and production itself. The ...
Production Integrations are how we interface with printers and production machines. Production Integrations can be triggered in 2 ways and different integrations can support these or not Manual Push - From the Production module in the Jobs screen you ...