Cloudflow and CERM integration

Transcription

1 Cloudflow and CERM integration

2 Contents Introduction... 3 Requirements...3 General requirements... 3 Software requirements... 3 CERM requirements... 3 HYBRID requirements... 3 Integration... 4 Required setup... 4 Scenarios... 4 Complete integration...4 Only approval with HYBRID Software...7 Conditions... 7 Included...7 Not included...8

3 Introduction 3 Introduction This whitepaper describes the current standard integration between CERM MIS and HYBRID Software s CLOUDFLOW server. The integration consists of a module that handles communication between CLOUDFLOW and CERM. The communication is based on: JDF Sample workflows of CLOUDFLOW WORKSPACE and PACKZFLOW. The configuration of CLOUDFLOW will be executed by a HYBRID solution engineer. A consultant from CERM will handle the setup in CERM. The CERM HYBRID Software connection is also described in the CERM manual and can be found here: Requirements General requirements CERM MIS and CLOUDFLOW need to be installed on the same network. Software requirements The minimum software requirements are: CERM v7.11 or higher. CLOUDFLOW WORKSPACE or higher. PROOFSCOPE for advanced online approval. PACKZ for prepress jobs (one-up editing) PACKZFLOW for prepress jobs (one-up editing) and production jobs (step and repeat) CERM requirements CERM needs to be in use and ready for real production. CERM users need to be able to create products based on reference calculations, sales orders and production jobs. Ganged layouts (i.e. multi-grid or multi-product Step & Repeat layouts) need to be created using Autoplan. This tool helps creating the high-level JDF which describes the Step & Repeat that will be created by the CLOUDFLOW workflow solution. Multi size products (e.g. a combination of front, back and neck label) within one job need to be produced in CERM using Kit products. Refer to for more information. HYBRID requirements The CLOUDFLOW server needs to be in use and ready for real production or isolated testing. Once implemented, the CLOUDFLOW server will start acting when receiving messages from CERM.

4 Integration 4 The 3 days integration package includes initial communication setup and training on how to use data obtained in workflows. There must be a clear vision on what is expected from the integration and what actions or workflows should be triggered on what event. Integration Required setup Action tags of the status names should be described as in the CERM manual: Modules/Products/Product_statuses/Implementation_product_statuses.htm The use of prepress jobs is mandatory. More info is available in the CERM manual: onlinehelp/modules/jdf/prepress_jobs.htm The default setup of the product directory structure should be based on data that doesn't change, so without anything related to the customer in it. In general we advise to define the following structure based on the product ID in CERM: \\[fileserver]\productimages\<#afg ref index=1 count=3>\<#afg ref>. Example \\Fileserver\productimages\250\ The default setup of the job directory structure should be based on data that doesn t change, so without anything related to the customer in it. In general we advise to define the following structure based on the job ID in CERM: \\[fileserver] \jobs\<#ord ref index=1 count=3>\<#ord ref>. Example \\Fileserver\jobs\664\ Scenarios There are two use case scenarios: Complete integration (prepress / approval / production) Only approval with HYBRID Software Complete integration In case of a complete integration, the following steps take place: 1. Product Creation in CERM In CERM, a product is created. The product details are stored in a JDF file and is transferred to CLOUDFLOW. 2. Link artwork with product in CERM 1. Artwork is delivered and added to the product in CERM. 2. CERM notifies CLOUDFLOW via a JMF file. 3. CLOUDFLOW analyzes the file. 4. CLOUDFLOW creates a preview to visualize the artwork in CERM. 5. CLOUDFLOW reports the trim box size and used inks to CERM via an XML file. 6. CERM verifies the trim box size and imports the inks. 7. CERM sends a Size OK or Size Not OK status to CLOUDFLOW via a JMF file.

5 Integration 5 3. Make Artwork print-ready CLOUDFLOW is triggered by the JMF file and starts a prepress workflow containing the following steps: The workflow is put on hold and the operator performs manual actions on the one-up file in PACKZ. Trapping. Note: Trapping can be done in PACKZ or in the workflow with PACKZFLOW. Proof files are created by adding an info panel to the file. By default, the list of variables from CERM include: Substrate_ID Substrate Previous_job Paper_type Winding Press Proof Width Height Previousproduct ProductVersion Radius Core_diameter Max_diameter Quantity_reel Shape Contact_ Contact_language The approval details are added here in order to automate the next step (4. Approval Request). After this, CLOUDFLOW notifies CERM with an updated status. 4. Approval Request 1. The status update in CERM triggers an approval workflow in CLOUDFLOW via a JMF file. 2. The CLOUDFLOW workflow sends an approval request by . This contains a direct link to: Visualize the soft proof. Approve/reject the file using approve/reject buttons.

6 Integration 6 In PROOFSCOPE it is possible to: Switch on/off separations. Perform measurements on densities and distances. Add annotations. Detect barcodes. Approve/reject a file with the Approve/Reject buttons. Delegate an approval with the Delegate button. If the file is rejected in PROOFSCOPE, an updated version of the label can be provided in CERM (e.g. from within the CERM Web4Labels interface). In case the Unique name mode in the CLOUDFLOW Copy or Move nodes is set to Sequential, add always, the updated versions are the file is saved on the server next to the original one. The updated file is opened in PROOFSCOPE. Thanks to the version management, versions can be compared by using: A delta mode. A blinking mode. An automatic switch. For more information, refer to the CLOUDFLOW Reference Manual. 5. Production 1. The products are ordered in CERM. 2. The step and repeat schema is defined in CERM by the Auto-plan module (see CERM Requirements).

7 Conditions 7 3. A JDF layout file is created containing the production details, S&R schema and marks information. Press Diecut Cylinder Bag Dierepeat ProductionType Type_colour_1 Type_colour_2 Type_colour_3 ToolNumber1 ToolType1 ToolKeyword1 ToolStatus1 ToolAmountWidth1 ToolAmountHeight1 4. The JDF Layout file is transferred to CLOUDFLOW. 5. In CLOUDFLOW, a workflow is started that creates the step and repeat layout, based on CERM JDF layout and adds the correct printing marks that were configured in CLOUDFLOW Live Objects. Only approval with HYBRID Software In case of a complete integration that only contains approval with HYBRID software, only step 4 of the complete integration is needed. Conditions Included The following is included in the standard integration setup: 3 days of integration and training (as described in this white paper). Setup of the standard CLOUDFLOW workflows for automatic start based on product status. Setup of the JDF listener and configuration of CLOUDFLOW to act on JDF messages. Setup of file stores to match the CERM environment. Setup of PDF Preflight if applicable. Setup of automated step and repeat based on CERM JDF file. Setup of a default proof mark and report using the following LiveObjects. xx...

8 Conditions 8 Setup of PROOFSCOPE Approval workflow. Setup of ink and pagebox reporting for CERM. Setup of Proofing PDF and preview for CERM. Not included The following is not included in the standard integration setup. General The standard workflows are examples on how to implement CLOUDFLOW workflows in a prepress and production environment for narrow-web roll-fed label production, based on the conventions agreed by the CERM implementation. If the prepress and production procedures are different compared to the intended implementation, the workflows need to be customized in order to match the method of working and needs. These customizations are not part of the standard implementation. Technical limitations Some customers use processes that still need manual tools. Non-90-degree-based rotations of stations. Multiple approvers. This is supported via the Delegate function in PROOFSCOPE. Communication on plate/cliché ID/numbers. Communication on Layouts combining labels with different sizes/shapes except for CERM Kits products. Communication on Layout for sheet fed printing. Communication on colour details per production method. Different status for Front/Back Labels: need to be approved as one PDF. CLOUDFLOW can only communicate one status per product to CERM. Re-use of step and repeat: the CERM integration process assumes the step and repeat is always repeated. During installation Installation of hardware and operating system. Configuration of infrastructure. Migration of data structures (this needs to be done beforehand or after installation). Development of new LiveObject templates. Installation and training of CLOUDFLOW. Any other task that is not specified as part of the integration. As mentioned before, customizations are possible and due to the nature of CLOUDFLOW can be very elaborate and powerful. Special wishes or requirements can be discussed with a HYBRID Sales representative in order to explore possibilities.