Cerm MIS. CermBoXX 2.0. Technical Description

Cerm MIS CermBoXX 2.0 Technical Description

1 CERMBOXX... 4 1.1 INTRODUCTION... 4 1.2 WHAT IS THE CERMBOXX?... 4 1.3 WHY CERMBOXX?... 4 1.4 ADVANTAGES... 4 2 CERMBOXX : TECHNICAL DESCRIPTION... 5 2.1 CERMBOXX IN THE CUSTOMER S NETWORK... 5 2.2 INSIDE THE CERMBOXX... 5 2.2.1 Main virtual machines... 6 2.2.2 Optional virtual machines... 6 2.3 CERMBOXX WEBPAGE... 7 2.4 NETWORK SERVICES RUNNING INSIDE THE CERMBOXX... 7 2.4.1 SQL server engine service... 7 2.4.2 File share service... 7 2.4.3 CermBoXX Backup service... 7 2.4.4 Cerm Site Manager Service... 7 2.4.5 Cerm JDF service... 7 2.4.6 Cerm Folder Monitor service... 7 2.4.7 DataCap Counterbox service (optional service)... 8 2.4.8 Web4Label web services (optional service)... 8 2.4.9 Cerm EDI service... 8 2.4.10 Cerm Mobile Application Service... 8 2.5 THE CERMBOXX NETWORK CONFIGURATION... 9 2.5.1 Internal network configuration... 9 2.5.2 External network configuration... 9 2.6 HARDWARE REQUIREMENTS... 10 2.6.1 CermBoXX server hardware requirements... 10 2.6.2 CermBoXX resource requirements... 10 2.6.3 Supported Hypervisor versions... 10 2.7 MICROSOFT LICENSES... 10 2.8 MICROSOFT WINDOWS UPDATE AND WINDOWS DEFENDER... 11 2.8.1 Windows Update... 11 2.8.2 Windows Defender... 11 3 SETTING UP A CERMBOXX IN THE CUSTOMER S NETWORK... 11 3.1 TEST-DRIVE... 11 3.1.1 What is a test-drive?... 11 3.1.2 Test-drive preparation... 11 3.1.3 CermBoXX during the test period... 12 3.2 MIGRATION FROM TEST-DRIVE TO FINAL CERMBOXX... 12 3.2.1 The customer already has a server infrastructure with VMware ESX(i) or Microsoft Hyper-V... 12 3.2.2 The customer starts with new hardware... 12 4 THE CERM CLIENT... 13 4.1 INTRODUCTION... 13 Page 1 of 32

4.2 CERM CLIENT REQUIREMENTS... 13 4.3 INSTALLATION OF THE CERM CLIENT SOFTWARE... 13 4.4 CERM CLIENT SOFTWARE ON WINDOWS REMOTE DESKTOP SESSION HOST... 13 5 CERMBOXX MANAGEMENT TASKS... 14 6 THE CERMBOXX BACKUP SERVICE... 15 6.1 THE CERMBOXX BACKUP SERVICE IS RUNNING IN THE CERMBOXX. THE CERMBOXX BACKUP SERVICE INCLUDES 4 STEPS. 15 6.1.1 Step 1: backup databases... 15 6.1.2 Step 2: backup documents... 15 6.1.3 Step 3: backup to a remote share... 15 6.1.4 Step 4: reporting... 15 6.2 RESTORE... 15 6.3 CERMBOXX BACKUP SERVICE SCHEDULE... 15 7 DISASTER RECOVERY AND CERMBOXX... 17 7.1 INTRODUCTION... 17 7.2 THE CERMBOXX BACKUP SERVICE... 17 7.3 WHAT CAN CERM DO IN CASE OF A DISASTER?... 17 7.4 WHAT DO WE EXPECT FROM THE CUSTOMER (OR HIS IT PARTNER) IN CASE OF DISASTER?... 17 7.5 ADDITIONAL PRECAUTIONS TO LIMIT DOWNTIME... 17 8 PERIPHERALS... 19 8.1 SHORT DESCRIPTION... 19 8.2 PERIPHERAL TO ADD TO THE WORKING ENVIRONMENT OF THE WAREHOUSE MANAGER... 19 8.2.1 Mobile workstation handheld scanner... 19 8.2.2 Barcode label printer... 20 8.3 PERIPHERALS TO ADD TO THE WORKING ENVIRONMENT OF THE PRINTERS... 20 8.3.1 Barcode scanner... 20 8.3.2 Barcode label printer... 20 9 OPTIONAL CERMBOXX COMPONENTS... 21 9.1 THE CERM COUNTER SYSTEM - DIRECT MACHINE INTERFACE: PRESS COUNTER INFRASTRUCTURE... 21 9.1.1 Introduction... 21 9.1.2 Base-system... 21 9.1.2.1 CounterBoXX: details... 21 9.1.2.2 Counter-sensor: details... 22 9.1.2.3 CERM-DATACAP: details... 22 9.1.2.4 Cabling... 22 9.1.2.5 Network communication between the CounterBoXX and the CERM-DATACAP... 23 9.1.3 Technical installation procedure... 24 9.1.3.1 Introduction... 24 9.1.3.2 Step 1: Pre-installation steps... 24 9.1.3.3 Step 2: Installing the counter-sensor... 24 9.1.3.4 Step 3: Installing the CounterBoXX + connect the counter-sensors... 25 9.1.3.5 Step 4: Configuration of the CERM-DATACAP... 25 9.1.3.6 Step 5: Testing (and troubleshooting)... 25 Page 2 of 32

9.1.3.7 In case of 2 or more Cerm counter systems... 25 9.1.3.8 Extra Cerm Counter System in the same LAN as the CermBoXX... 26 9.1.3.9 Extra CounterBoXX on another site and/or another network of the CermBoXX... 27 9.1.4 Good/bad toggle switch (optional)... 27 9.1.5 Workflow description... 28 9.2 WEB4LABELS... 29 10 IMPORTANT THINGS TO KNOW ABOUT CERMBOXX... 30 10.1 CERMBOXX IS A BLACKBOX... 30 10.2 CERMBOXX SUPPORT NETWORK... 30 10.3 CERMBOXX UPDATES... 30 10.3.1 CermBoXX distributed updates... 30 10.3.2 Cerm software updates... 30 10.4 DATABASE MAINTENANCE... 31 10.5 CERMBOXX ONLINE BACKUP... 31 10.6 THE CERM MIS TEST ENVIRONMENT... 31 11 FAQ... 32 11.1 IS THERE AN ANTI-VIRUS RUNNING ON CERMBOXX?... 32 11.2 CAN CERMBOXX RUN IN THE CLOUD?... 32 11.3 HAS THE CUSTOMER S IT ADMINISTRATOR ACCESS TO THE CERMBOXX WINDOWS VIRTUAL MACHINES?... 32 11.4 HAS THE CUSTOMER ACCESS TO THE CERM MIS DATABASE?... 32 11.5 WHAT IS THE CERMBOXX S IP ADDRESS?... 32 Page 3 of 32

1 CermBoXX 1.1 Introduction This document gives you a technical description of the CermBoXX. The CermBoXX is the backbone for the Cerm MIS 1. The CermBoXX contains all required data and services for the Cerm MIS. The purpose of this document is to give the IT responsible or the IT partner of the customer all the necessary information and insights about the technical part of the Cerm MIS. 1.2 What is the CermBoXX? The Cerm MIS is a client-server based application. The client part of the Cerm MIS will run on the windows client of the customer (PC, Terminal Server, Citrix, ) The server part of the Cerm MIS is the CermBoXX. The CermBoXX hosts all Cerm MIS server components. Adding a CermBoXX in the customer's network requires no changes to existing IT Infrastructures. Your current IT supplier remains responsible for the performance of your existing IT infrastructure (network, mail server, fileserver, printer server, domain controller, ). The CermBoXX will be plugged into your existing IT infrastructure without affecting existing network functionalities. The CermBoXX will run side by side with your existing network services. 1.3 Why CermBoXX? The Cerm MIS is a combination of several network services (SQL Database Engine, file shares, windows services, web services, hotfolders, EDI links, ). Cerm MIS requires all these network services to run in the customer s network. All the required network services are combined in 1 solution: CermBoXX. Combining all required services of the Cerm MIS in the CermBoXX results in a stable, manageable and standardized Cerm MIS. 1.4 Advantages Running the Cerm MIS on a CermBoXX has these advantages: The Cerm MIS is delivered as a set of pre-configured templates, this reduces the on-site installation and configuration time. There is no need for an on-site visit of a Cerm IT consultant. All technical configuration tasks will be done in advance or remotely. A clear situation for your local IT partner: The CermBoXX will be supported by Cerm, your local IT partner remains responsible for all other network and server components. 1 Cerm MIS: Cerm Management Information System. In this document Cerm MIS means the complete Cerm software solution. Page 4 of 32

2 CermBoXX : Technical description 2.1 CermBoXX in the customer s network The diagram above shows an overview of the customer s components and the Cerm MIS components: The grey colored parts are the customer s components already present in the network or that will be in the future. These are PC s, servers, printers, network devices, presses, The green colored parts are the components the Cerm MIS requires in the customer s network. These are the 3 main Cerm MIS components: The CermBoXX hosts all Cerm MIS server components: database engine, jdf services,... The Cerm Client runs the Cerm-end-user software on the existing windows environment. The Press Counter Box is an optional component for receiving real-time information from the presses, see chapter 9.1 of this document for more information about this component. The Cerm client software is the only component running on the existing windows environment of the customer. The client environment can be a windows PC or a Remote Desktop Session Host (Terminal Server) with or without Citrix. 2.2 Inside the CermBoXX From IT infrastructure point of view, a CermBoXX is a set of 3 to 5 pre-configured virtual machines. The exact number of virtual machines depends on the customer s needs. (required components) The virtual machines run on a VMware based ESXi environment (ESXi 6.0 and ESXi 6.5) or Microsoft Hyper-V. Page 5 of 32

2.2.1 Main virtual machines These are the CermBoXX main virtual machines with their properties: CERM-RSM o Role : runs the network configuration of the CermBoXX o CPU : 1 core o RAM : 512 MB o HDD : 4 GB o OS : Linux Debian 7 CERM-DATA o Role : runs the SQL server 2017 database engine and file shares o CPU : 4 cores o RAM : 8 GB o HDD : 150 GB o OS : Windows 2016 Server Std. CERM-ENGINE o Role : runs the Cerm services, scheduled tasks and hotfolder. This is also the environment for executing CermBoXX maintenance tasks. o CPU : 4 cores o RAM : 8 GB o HDD : 50 GB o OS : Windows 2016 Server Std. 2.2.2 Optional virtual machines These are the CermBoXX optional virtual machines with their properties: CERM-W4L o Role : runs IIS 10 with the Cerm web services for the Web4Labels component o CPU : 2 cores o RAM : 4 GB o HDD : 30 GB o OS : Windows 2016 Server Std. CERM-DATACAP o Role : this is the software part of the counter system o CPU : 1 core o RAM : 4 GB o HDD : 30 GB o OS : Windows 10 Prof. The resources are the required resources at the start of the Cerm MIS project. These resources can be adjusted based on the changing needs of the customer. Page 6 of 32

2.3 CermBoXX webpage The CermBoXX has a webpage providing the customer basic information about the CermBoXX. This Information can be found on the CermBoXX webpage: Instructions + download of the Cerm client software for the initial installation on the Windows client. Overview of the active IP addresses of the virtual machines. Hyperlink to make an RDP connection to the CERM-ENGINE in the CermBoXX. A link to the advanced setup page of the CermBoXX (CermBoXX configurator). A link to the support portal of Cerm. 2.4 Network services running inside the CermBoXX This is an overview of the network services running inside the CermBoXX. 2.4.1 SQL server engine service Runs on: CERM-DATA Description: The Cerm MIS software uses a database to store the data. The CermBoXX runs Microsoft SQL server 2017 Express or Standard Edition. The default name of the Cerm MIS database is sqlb00. Important remark: CermBoXX also supports hosting of the Cerm SQL server database on an external host. Customers already having a SQL server engine running in their network can be used to host the sqlb00 cerm database. Hosting the Cerm database outside the CermBoXX also has some consequences: o The CermBoXX Backup service (see 2.4.3) will no longer backup all Cerm MIS data, an additional backup process is needed on the customers SQL server host o The Cerm MIS test environment (see 10.6) feature is not supported when external hosting of the Cerm MIS database is used 2.4.2 File share service Runs on: CERM-DATA Description: The Cerm MIS also needs a windows file share to store Cerm MIS related documents. The network location of this share is \\CERM-DATA\sqlb00. 2.4.3 CermBoXX Backup service Runs on: CERM-ENGINE Description: By default, he CermBoXX Backup service runs twice a day. The CermBoXX Backup service backups all Cerm customer s data and configuration parameters of the CermBoXX to an external network location. See chapter 6 for a more detailed explanation about the CermBoXX Backup service. 2.4.4 Cerm Site Manager Service Runs on: CERM-ENGINE Description: The Cerm Site Manager Service broadcasts initial configuration data to the windows clients during installation of the Cerm client software. 2.4.5 Cerm JDF service Runs on: CERM-ENGINE Description: The Cerm JDF 2 service is a communication service to exchange data with other graphical software solutions running in the customer s network (Example: Esko AE). 2.4.6 Cerm Folder Monitor service Runs on: CERM-ENGINE 2 JDF : Job Definition Format is a technical standard to facilitate cross-vender workflows implementations in the graphical industry. Page 7 of 32

Description: The Cerm Folder Monitor service executes preconfigured service actions. This service is used for processing information from files coming into a hotfolder. The Cerm Folder Monitor service is also needed to import the data generated by the DataCap Counterbox service (see chapter 2.4.7). 2.4.7 DataCap Counterbox service (optional service) Runs on: CERM-DATACAP Description: The DataCap Counterbox service is the software part of the counterbox. The counterbox contains a PLC hardware device that retrieves real time information from the presses and converting equipment. The DataCap Counterbox Service communicates with the PLC counterbox through the customer s network. See also chapter 9.1 for more details. 2.4.8 Web4Label web services (optional service) Runs on: CERM-W4L Description: The Cerm MIS has an optional web module: Web4Labels. Web4Labels enables the customer s clients to look up their product catalogue, their order history, and create new purchase order through an online web tool. CERM-W4L runs the Cerm web services in IIS10 3. See also chapter 0 for more details. 2.4.9 Cerm EDI service Runs on: CERM-ENGINE Description: The Cerm EDI 4 service is a service to send/receive digital order data to suppliers of the customer. 2.4.10 Cerm Mobile Application Service Runs on: CERM-ENGINE Description: For warehouse activities, the customer needs WIFI scanners to run the Cerm Mobile Applications. The WIFI scanner makes a RDP connection to the CERM-ENGINE to start the Cerm Mobile Application. This service is only used if the customer doesn t have a Windows Remote Desktop Session Host (Terminal Server)! The CermBoXX is licensed by default to run 2 concurrent RDS sessions; 3 IIS10: Internet Information Services 10: This is the windows 2016 R2 webserver product. 4 EDI: Electronic Data Interchange is a standard for digital exchange of orders Page 8 of 32

2.5 The CermBoXX network configuration 2.5.1 Internal network configuration This is a screen capture of the network configuration of an ESXi server running the CermBoXX Virtual machines: On Microsoft Hyper-V, the network configuration is similar. All CermBoXX virtual machines are connected to a virtual switch INTERNAL. This virtual switch has no linked physical network adapter. The CERM-RSM and CERM-DATACAP are connected to the customer s LAN through the virtual switch. The INTERNAL switch has a management port with IP address 10.252.1.253/24 (only in a VMware environment). All IP addresses of the CermBoXX belonging to the customer s LAN are configured on the CERM-RSM. The CermBoXX uses DNAT configuration rules to forward the customer s LAN IP-addresses to the according CermBoXX virtual machines. 2.5.2 External network configuration These are the CermBoXX external network configuration requirements: Up to date network (UTP level minimum CAT5, 1000MB/s, switches) Network printers: Printers are directly connected to the customer s network, not through a PC or another client device. The Cerm MIS stores information about the customer s printers (for printing documents and labels) into the customer s Cerm database. A printer connected through a PC (and not in the network) is hard to manage in the Cerm MIS for use by multiple users. Share access to a fileserver or backup server for external backup used by the CermBoXX Backup Service. The Cerm MIS software and the CermBoXX will send emails, therefor the CermBoXX and the clients running the Cerm client software need SMTP access to the customer s SMTP server. To help the customer testing his SMTP server, Cerm has developed a SMTP test tool. (http://www.cerm.be/hd/onlinehelp/system/installation/smtp/smtp_test_programs.htm) Page 9 of 32

2.6 Hardware requirements The CermBoXX virtual machines require a hardware server with VMWare ESXi or Microsoft Hyper-V There are 2 possible start situations for the hardware server: The customer starts with a new hardware server. The customer already has a server infrastructure with VMware ESX or Microsoft Hyper-V 2.6.1 CermBoXX server hardware requirements These are the server hardware requirement for a new hardware server running the CermBoXX virtual machines : CPU: 1x Intel Xeon SixCore 2,4 GHz(or higher) RAM: 32 GB HDD: 4x 300 GB SAS 15k rpm (RAID5) RAID Controller (at least 400 IOPS on attached datastore) Redundant power supply 2 Network cards (1Gb/s) Important remarks: HDD datastore: 400 IOPS is a minimum. Cerm recommends disksystems based on SSD to achieve much higher IOPS resulting in better database performance. It is strongly recommended to connect the server hardware running the CermBoXX virtual machines with a UPS! 2.6.2 CermBoXX resource requirements If the customer already has an infrastructure with VMWare ESXi or Hyper-V, these are the required (available) resources: CPU: 4 cores RAM: 32 GB Free HDD space: 500 GB IOPS datastore: at least 400 IOPS (see also important remark in 2.6.1) 2.6.3 Supported Hypervisor versions These are the supported VMWare ESXi versions to run CermBoXX virtual machines: VMWare ESXi 6.0 VMWare ESXi 6.5 All Microsoft Hyper-V versions are supported to run the CermBoXX virtual machines. 2.7 Microsoft licenses CermBoXX 2.0 runs on Windows 2016 Server Std. Operating System Environments (OSEs). The Windows 2016 Server licensing model is core-based. This means the number of needed licenses depends on the physical cores and processors in the hardware server running the OSEs. For a hardware server up to 2 processors and 8 cores per processors, the following Microsoft licenses are needed for the CermBoXX 2.0 main virtual machines: 8x WinSvrSTDCore 2016 SNGL OLP 2Core CoreLic (9EM-00124) 1x OfficeStd 2016 SNGL OLP (021-10554) 5x WinCAL (R18-05123) 2x RDSCAL user (6VC-03224) When adding the CERM-W4L to the CermBoXX, an extra license package is needed: 8x WinSvrSTDCore 2016 SNGL OLP 2Core CoreLic (9EM-00124) General information: The number between the () is the official Microsoft part number in the Microsoft Open License program. Page 10 of 32

For hardware servers having more processors and/or cores, additional licenses are required. Please check this Windows 2016 Licensing Datasheet for all licensing details: https://download.microsoft.com/download/7/2/9/7290ea05-dc56-4bed-9400-138c5701f174/ws2016licensingdatasheet.pdf Important remarks: The CermBoXX Virtual Machines are running on a hypervisor. VMware ESXi and Microsoft Hyper-V are both supported for the CermBoXX virtual machines. Depending on the hypervisor choice, the hypervisor may also need licenses. Ask your IT partner for more information. Windows CAL: Each user and/or device accessing a licensed Windows Server 2016 requires a Windows Server CAL. A Windows Server CAL gives a user or device the right to access any edition of Windows Server of the same or earlier version. Each Window Server CAL allows access to multiple licenses of Windows Server. Cerm assumes the customer already has sufficient CAL for his existing Windows network. SQL server licensing: Depending on the needs of the customer, we can choose to run SQL server 2017 Std. (instead of the express edition). In this case, an additional Microsoft license is required: o 2x SQLSvrStdCore 2017 SNGL OLP 2Core (7NQ-01158) The customer has the choice to buy the Microsoft licenses from his IT partner or Cerm. Due to a Microsoft policy, Cerm can only buy Microsoft licenses in Europe. Cerm customers outside Europe will have to buy these Microsoft licenses from their local IT Partner. 2.8 Microsoft Windows Update and Windows Defender To protect the Windows 2016 virtual machine environments, all Windows virtual machines have Windows Update and Windows Defender activated. 2.8.1 Windows Update Windows updates are activated on all Windows virtual machines in the CermBoXX. The installation of Windows updates runs during a prefined maintenance window. This maintenance window is scheduled by default on Sunday morning between 3.00 AM Active hours 8.00 PM to 8.00 AM?? 2.8.2 Windows Defender Windows Defender is installed and activated in all Windows virtual machines in the CermBoXX. 3 Setting up a CermBoXX in the customer s network 3.1 Test-drive 3.1.1 What is a test-drive? A new Cerm MIS customer will always starts working on a test-drive. Using a test-drive allows the customer to test the Cerm MIS software free of charge during a trial period. The Cerm consultant will deliver a pre-configured CermBoXX on the first day of his visit to the customer. During this test period, the CermBoXX will run on PC hardware. The customer doesn t have to buy hardware or make configuration changes in his network to run the CermBoXX during the test period. 3.1.2 Test-drive preparation A CermBoXX running on PC hardware for the test period will always be prepared by a Cerm technical consultant at the Cerm headquarter, located in Belgium. To prepare the CermBoXX for the test period, the customer has to deliver some basic Page 11 of 32

information about his network. A Cerm consultant will deliver an excel file during the first take-in meeting. The customer has to return the completed excel file to Cerm. These are the requirements for the CermBoXX to be able to connect in the customer s network: 5 free fix IP addresses (all IP addresses need internet access) Subnet mask, gateway, dns and local dns suffix Proxy server (if needed for internet access) SMTP server (with username and password if needed) Network backup location (UNC path with username and password) Time zone location of the CermBoXX 3.1.3 CermBoXX during the test period There are no software or other limitations during the test-drive period on level of CermBoXX. All CermBoXX main virtual machines are running during this test-drive period. The optional CermBoXX virtual machines are not available on the CermBoXX during this period. 3.2 Migration from test-drive to final CermBoXX Before the customer goes live with the Cerm MIS, the CermBoXX virtual machines need to be migrated from the pc hardware to server hardware. The customer needs VMWare ESXi or Microsoft Hyper-V infrastructure to execute the migration to the final CermBoXX. The test-drive runs always on VMware ESX(i). If the customer chooses Hyper-V as hypervisor, the Cerm IT consultant will convert the virtual machines to Hyper-V during the migration process. There are 2 possible start situations: The customer already has a server infrastructure with VMware ESX(i) or Microsoft Hyper-V. The customer starts with a new hardware server 3.2.1 The customer already has a server infrastructure with VMware ESX(i) or Microsoft Hyper-V A Cerm IT consultant will migrate the CermBoXX virtual machines to the customer s Hypervisor infrastructure remotely. Of course, the Cerm IT consultant will contact the customer s local IT administrator before adding the CermBoXX virtual machines to an existing and running VMWare infrastructure. 3.2.2 The customer starts with new hardware In this case, we ask the customer s local IT administrator to execute these preparation configuration steps: Connect the new hardware server in the network of the customer. Configuration of the RAID system of the disk datastore Install the hypervisor (VMware ESX(i) or Microsoft Hyper-V) Communicate the ip address and credentials for accessing the hypervisor with the Cerm IT consultant A Cerm IT consultant will migrate the CermBoXX virtual machines to the customer s Hypervisor infrastructure remotely. Page 12 of 32

4 The Cerm client 4.1 Introduction The Cerm MIS client runs on the existing windows client infrastructure of the customer. The client can be a PC, a Windows Remote Desktop Session Host (Terminal Server) with or without Citrix, Windows OS in Parallels or VMware fusion for Mac,... Technically, installing the Cerm Client Software is done by installing or deploying one cerm.msi file on a Windows machine. 4.2 Cerm Client requirements CPU: multi-processor with high clock speed RAM: 4 GB HDD: 10 GB of free space 1 GB connection with the customer s LAN (and CermBoXX) Other software: Acrobat reader, Office 32-bit (all office versions starting from office 2007 are supported) OS: Windows 2008 R2, Windows 2012 R2, Windows 2016, Windows 7, Windows 8 or Windows 10 Screen resolution : minimum 1024 x 768 (recommended: 1280 x 1024 or higher) Important remarks (in order of importance): For performance reasons, the Cerm MIS client and the CermBoXX must run in the same LAN and subnet! Choose windows clients with a high CPU clock speed. The client s CPU clock speed has a direct impact on the performance of the Cerm MIS. A clock speed of 3.2 GHz (or higher) is recommended. Consider also to use an SSD disk in your windows client. SSD disk on the client will also have positive impact on the performance of the Cerm MIS. 4.3 Installation of the Cerm Client software This is the procedure to install Cerm client software on a windows client: Browse to the CermBoXX webpage. Download the installation file cerm.msi from the webpage. Install the cerm.msi on the Cerm client. IMPORTANT: Make sure you have full administrator rights on the Windows client to install (or update) the Cerm client software. During the Cerm client software installation, the following system files will be created or updated: C:\windows\system32\drivers\etc\hosts C:\programdata\cerm\database\connectiondefs.ini These 2 files are protected by Windows UAC. This is the reason full administrator rights are needed during the installation or upgrade process. 4.4 Cerm client software on Windows Remote Desktop Session Host The Cerm client software and CermBoXX must run in the same LAN and same subnet. If the customer wants to use the Cerm MIS on several sites, a Windows Remote Desktop Session Host (Terminal Server) is the best choice to run the Cerm client software. A Windows RDS Server also has some other advantages: In the production area, the customer doesn t have to install and maintain PC s. Thin clients can be used to run the Cerm client software. The update process of the Cerm client software only must run once on the RDS Server. Central management of the user sessions. A system administrator can take over the session of an end-user for support. Central management of the printing devices. Page 13 of 32

5 CermBoXX Management tasks Several management tasks can be executed on the CermBoXX : Updating the Cerm software on the CermBoXX. Management of the running Cerm related services. Management of the optional components: CERM-DATA and CERM-W4L Creation or update of the test database. Toolset for general management tasks. The CermBoXX Management tasks are available on the CERM-ENGINE virtual machine. The customer can make an RDP connection to the CERM-ENGINE through the CermBoXX webpage: http://www.cerm.be/hd/onlinehelp/system/installation/cermboxx_management.htm Page 14 of 32

6 The CermBoXX Backup service 6.1 The CermBoXX Backup service is running in the CermBoXX. The CermBoXX Backup service includes 4 steps. 6.1.1 Step 1: backup databases All Cerm databases are backed up to the local backup folder inside the CermBoXX. The CermBoXX Backup service uses the SQL server functionalities to backup each database to a.bak file. 6.1.2 Step 2: backup documents All Cerm documents are backed up locally inside the CermBoXX. The CermBoXX Backup service takes advantage of the Volume Shadow Copy Services. The CermBoXX Backup service makes volume shadow copies, this results file versioning of all documents. In this step, the CermBoXX configuration files are also copied to backup location. The backup location in the CermBoXX is accessible from within the customer s network via: \\CERM-DATA\Cerm_backup$ User: CermSys Pass: SysCerm01. 6.1.3 Step 3: backup to a remote share During the nightly backup, the CermBoXX Backup service copies the result of backup step 1 and 2 to a remote share on a customer's (backup) server or NAS. It is highly recommended to backup these files to a portable medium and store this backup outside the customer s building. A second recommendation is to keep more than one backup on a portable medium (e.g. one portable medium per day of the week). 6.1.4 Step 4: reporting The CermBoXX Backup service also creates a detailed backup report. Immediately after the backup is finished, this report will be e-mailed to the person who is responsible to check the CermBoXX backup: If the backup was successful, the email report will show a OK green status. In case of some warnings, the email report will show a WARNING yellow status. In case of any error, the email report will show a FAILED red status. In case of problems or questions about the CermBoXX Backup service, you can contact a Cerm System Administrator via the Cerm online ticket system (https://support.cerm.be). 6.2 Restore If a restore is needed, Cerm uses this method: Database restore: Restoring can be done by overwriting an existing database with the content of the backup. In case of a necessary restore we use the "SQL Server Management Studio" to fulfill this task. Documents restore: Depending on the circumstances, restoring files from backup will be starting from the file versioning or copying back from the remote backup share in the customers network. 6.3 CermBoXX Backup service schedule The CermBoXX Backup service creates 2 backups a day: NOON backup o Only steps 1, 2 and 4 are carried out at noon. o This backup starts at 12:30 PM. Page 15 of 32

NIGHT backup o All steps (1, 2, 3 and 4) are running at night. o This backup starts at 11:45 PM. Page 16 of 32

7 Disaster Recovery and CermBoXX 7.1 Introduction Sometimes, things can go really wrong. In some circumstances, we have to decide to rebuild the CermBoXX from scratch. This chapter gives you an overview of: The existing backup procedure in the CermBoXX. What can Cerm do in case of a disaster? What do we expect from the customer (or his IT partner) in this case? Additional precaution a customer can take to limit downtime. 7.2 The CermBoXX Backup Service Each CermBoXX has a configured CermBoXX Backup Service. The CermBoXX Backup Service: Takes a backup of all the customer s related data (Cerm database, Cerm documents, CermBoXX configuration files, ). Makes a local backup on the CermBoXX and a remote backup to a server on your network. Runs by default twice a day. Sends an email report to the local IT responsible. Responsibilities of the customer: Check the backup report daily. Contact Cerm in case of problems with the CermBoXX Backup Service. Organize a secure physical backup of the Cerm Data in a remote location or to an offline medium (tape, USB disk,.). ALWAYS KEEP IN MIND THE CERM DATABASE IS YOUR DATA, TAKE CARE OF IT! 7.3 What can Cerm do in case of a disaster? Cerm has a team of 5 Cerm IT consultants to assist you with all your technical questions. In case of a disaster, they can assist you during the complete restore process of the CermBoXX. Cerm uses this procedure to rebuild a CermBoXX : Downloading the CermBoXX templates from the internet. Activating/importing the CermBoXX templates on the hypervisor server. Importing/restoring your Cerm data from your backup into the CermBoXX. 7.4 What do we expect from the customer (or his IT partner) in case of disaster? A successful restore of a CermBoXX requires these things of the customer: Access to hypervisor server connected to the customer s network. Internet access from within the customer s network. Access to the Cerm backup location (the remote backup location of the CermBackup component). The guarantee that the last CermBoXX backup was successful (backup report email). On-site assistance of the IT responsible. 7.5 Additional precautions to limit downtime Always connect the server hosting the CermBoXX with a UPS. This will reduce the downtime related to power failure or power fluctuations. The CermBoXX consists of 3 to 5 virtual machines. VMware ESXi and Microsoft are well used in the IT market and has several backup possibilities: There are various kinds of third party software available to make a backup of the VMware ESXi virtual machines. Page 17 of 32

The CermBoXX virtual machines can run on a SAN system with a failover configuration. Of course, this requires additional hardware. You can also consider installing a second CermBoXX as part of your disaster recovery plan. You can always contact a Cerm IT consultant (technical.support@cerm.net) if you need additional information about this topic. Page 18 of 32

8 Peripherals 8.1 Short description If you want to use the Cerm warehouse management software, you will need some hardware peripherals. The peripherals listed in this document are suggested by Cerm. These are the only peripherals which Cerm has tested with the Cerm MIS software. There are, off course, a lot of peripherals which can be used in combination with the Cerm software, which makes it impossible for Cerm to test them all with the software. If you prefer to use other devices, we strongly advise to check the compatibility with the Cerm software. You can use our Scanner and printer validation tool Cerm Barcode Test. More information can be found in following link: http://www.cerm.be/hd/onlinehelp/system/installation/printersscanners/cerm_barcode_test.htm The barcode printers and scanners must be installed and tested before the visit of the Cerm consultant! Please use the Cerm Validation tools to check if all devices are Cerm-Ready. Timing must be discussed with the CERM consultant in advance. REMARK: Cerm will not sell, support or configure the devices described in this document. The devices are only suggested by Cerm. Please contact a local reseller of such devices to get the most accurate and correct information. Please choose a local reseller who can execute (or assist you with) the configuration of all peripherals. 8.2 Peripheral to add to the working environment of the warehouse manager 8.2.1 Mobile workstation handheld scanner A WiFi scanner is necessary to inventory your stock and keep track of the locations of the reels in real time. We suggest the model Zebra MC32N0-GI4HCHEIA, which includes Windows CE 7.0 and is a Gun model. Extra required parts Single Slot Cradle & Power Supply: CRD3000-101RES USB Cable: 25-68596-01R Remarks/Requirements A Stable WiFi network which covers the whole shop floor and warehouse with a strong signal is fundamental for a successful mobile scanner implementation. The scanner will connect to the Cerm application through RDP. There are 2 options: o If you have a Remote Desktop Server, you can connect to it and you ll be able to use full functionality (scan + print). o If you don t have an RDS, you can connect to the CermBoXX. It will be possible to use the scanning part of the application, but you won t be able to print box labels directly from the application (only scan). Cerm has a European Partner (www.zetes.com) who can deliver the Zebra MC32N0-GI4HCHEIA preconfigured to connect with the Cerm MIS. Send an email to technical.support@cerm.net for more information. When you consider choosing another brand or model, the handheld scanner must have at least these properties: o Wifi connectivity Page 19 of 32

o Windows CE 7.0 o RDP client (with autostart) o Display: 240 x 320 pixels o Scanner: 1D and 2D 8.2.2 Barcode label printer A barcode printer is needed to be able to print labels to identify goods during picking and shipping. Specifications Label printer ZEBRA GK420d with network adaptor (TCP/IP) Always configure a barcode label printer with Seagull Scientific printer drivers: http://www.seagullscientific.com/drivers/windows-printer-drivers/ Also, test the your configuration with the Cerm Barcode Test Tool: http://www.cerm.be/hd/onlinehelp/system/installation/printersscanners/cerm_barcode_test.htm 8.3 Peripherals to add to the working environment of the printers 8.3.1 Barcode scanner This device is connected to the USB port of the workstation. It is necessary to scan the EPSMA-code of the reel for monitoring material consumption. Specifications Datalogic Gryphon GD4130 with USB adaptor. This scanner is also available cordless (Datalogic Gryphon GM4130). 8.3.2 Barcode label printer This device is needed to print a new ID-label for the remaining material reel (100 x 150 mm). If you produce instant finished rolls on the printing press for your customer, you must provide an extra printer, because the size of the labels for the finished goods will be different (100 x 18 mm). Specifications : see Fout! Verwijzingsbron niet gevonden. Page 20 of 32

9 Optional CermBoXX components 9.1 The Cerm Counter system - Direct Machine Interface: Press counter infrastructure 9.1.1 Introduction Cerm is capable to receive machine information in real time from your printing and converting equipment. We succeed in this by installing an inductive sensor on each machine that must be monitored. The information from the sensors will be captured by a PLC component and processed by a dedicated software part that processes the information and imports it into the Cerm database. Because of this installation Cerm can show print speed, calculate the exact material consumption, etc. We built it in a way so you can do the cabling, placing of the counter-sensors and mounting of the CounterBoXX yourself. 9.1.2 Base-system The Cerm counter system always contains the following parts: CounterBoXX with Siemens PLC (network version) and UPS. This is the central part of the Cerm counter system. Counter-sensors: for each printing or converting machine you want to monitor you need a counter-sensor. Each counter-sensor is connected directly to the CounterBoXX. CERM-DATACAP: This is the software part of the Cerm counter system. The CERM-DATACAP is a Virtual VMware ESX(i) machine preinstalled with Siemens OPC-server and DataCap software to import the counter data from the CounterBoXX into the Cerm database. Important facts about the Cerm counter system: A Cerm counter system can run in only 1 site. This means, for each production site you want to monitor, you need a Cerm counter system including all parts (CounterBoXX, Counter-sensors and CERM-DATACAP). All 3 parts need to be installed in each production site, it is not possible to split up the 3 parts over different sites. A Cerm counter system has a maximum of 20 connected counter-sensors. If you want to monitor more than 20 machines on 1 site, a second Cerm counter system is required. In most cases, the Cerm counter system is used in combination with other modules in the Cerm software (warehousing of material, rolls and boxes, ). In this case, additional hardware (printers, scanners, ) is needed. Please read the chapter about peripherals for more details. 9.1.2.1 CounterBoXX: details The CounterBoXX is the central part of the Cerm counter system, all parts are connected to the CounterBoXX. The CounterBoXX must be mounted on the wall somewhere central in the customer s production area. Some technical properties of the CounterBoXX The dimension are: H: 50cm x W: 50cm x D: 22 cm. The weight is 24 kg. Page 21 of 32

This is an inside view of the CounterBoXX describing all the modules: 9.1.2.2 Counter-sensor: details For each machine you want to monitor, you need a counter-sensor. The Counter-sensors are delivered in a counter-sensor kit. The counter-sensor kit content: The inductive sensor (with short cable and M12 connector male) M12 connector female A copper mounting plate Mounting tools (tight straps, iron shackle) The sensor counts by detecting the differences between the magnetic induction of the different materials (copper versus iron). The counter-sensor is a IE5352 type. We always advice the customer to buy an extra counter-sensor kit for fast replacement in case of a technical malfunction. 9.1.2.3 CERM-DATACAP: details CERM-DATACAP is a windows 10 Pro virtual machine. This CERM-DATACAP virtual machine is pre-configured to communicate with the CounterBoXX to import real-time counter data into the Cerm Database. The Microsoft Windows license for the Windows 10 Pro is included in the purchase cost of a Cerm counter system. The Windows 10 Pro license will be activated during the setup of the Cerm counter system. CERM-DATACAP is a VMware virtual machine. This means you need a VMWare ESX(i) server (or PC) to host the CERM- DATACAP in the same network as the CounterBoXX. There is no hardware server (or PC) included in the Cerm counter system, the customer must deliver a VMware ESX(i) environment. There is always a CERM-DATACAP available in the CermBoXX. This means if the CounterBoXX is installed in the same network as the CermBoXX, there is no need for additional hardware. 9.1.2.4 Cabling All parts (CounterBoXX, counter-sensors and CERM-DATACAP) will be connected to each other by cables, there is no wireless communication possible for the Cerm counter system. This is an overview of all needed cables for the Cerm counter system: CounterBoXX: Electricity cable: The CounterBoXX needs power. Network cable: A UTP (minimum CAT5) network cable connected with the customer s local network with RJ45 connector. Page 22 of 32

Signal cables: All counter-sensors will be connected separately to the CounterBoXX, 1 signal cable per countersensor. This must be a 5x 0.75 shielded cable (For US: 18 AGW). The maximum length of this cable is 100 meter. Counter-sensor: Signal cable: a 5x 0.75 shielded cable coming from the CounterBoXX. Off course this is the same cable as mentioned in point 1. CounterBoXX. CERM-DATACAP: CERM-DATACAP is a virtual machine running on a VMWare ESX(i) server. This VMWare ESX(i) server must be connected to the customer s network by a UTP cable (minimum CAT5). Remark about the cabling: Cerm asks to provide a 5x 0.75 shielded cable. The default configuration of the Cerm counter system will only use 3 of 5 available wires. The default Cerm counter system can be extended with a Good/bad toggle switch needing 2 extra wires. In this case, an extension of the Cerm counter system will not result in extra cabling. 9.1.2.5 Network communication between the CounterBoXX and the CERM-DATACAP There are 2 network protocols used for communication between the CounterBoXX and the CERM-DATACAP: TCP/IP: The CounterBoXX has a dedicated IP address (10.255.255.1/29), the CERM-DATACAP has also a dedicated IP address (10.255.255.2/29). SIMATEC industrial Ethernet: This is a Siemens network protocol for PLC specific reasons. This network protocol runs on the Ethernet level. Because of the need for both network protocols, the CounterBoXX and the CERM-DATACAP always have to be connected with the same physical network or VLAN. In technical terms, there must be a direct Ethernet connection between the CounterBoXX and the CERM-DATACAP. The picture below shows all 3 Cerm Counter System parts including the Cerm database with their cable connections and network addresses: Page 23 of 32

9.1.3 Technical installation procedure 9.1.3.1 Introduction The Cerm counter system is built so the customer can take care of all the technical onsite work (cabling, placing the counter-sensors, connecting the cables, mounting the CounterBoXX). This is a brief overview of the technical installation procedure: Cerm will deliver the customer: A pre-installed CounterBoXX A pre-installed VMware ESX(i) virtual machine template (already on the CermBoXX) The ordered amount of press counter-sensor kits An installation schema (included in the CounterBoXX) The customer will take care of: Mounting of the CounterBoXX Cabling & connecting Installing the counter-sensors & connection boxes A Cerm consultant will do: Configuration of the CERM-DATACAP Testing and give assistance during calibration 9.1.3.2 Step 1: Pre-installation steps Some steps can already start, even before your Cerm counter system has arrived. 1. Look for a good central place to mount the CounterBoXX in your production area. On this central place you can already install and provide the needed cables: A 5 x 0.75 shielded cable from the wall-mount CounterBoXX to each machine (Incoming cables from presses) Electricity Network-cable 2. On each machine, you can already provide: A small connection box near the place where the counter-sensor will be mounted (see also picture 3. Connection box further in this document) 5 x 0.75 shielded cable coming from the CounterBoXX. 9.1.3.3 Step 2: Installing the counter-sensor A detailed description about how to install the counter-sensor can be found in this document: http://www.cerm.be/hd/onlinehelp1/downloads/technical/installation_counters.pdf Please pay attention to these points when installing the counter-sensors: The copper must be installed on a machine shaft with a fixed diameter. The space between the copper and the counter-sensor must be between 2 and 3 mm. The relationship between the rotation speed of this shaft (with the counter-sensor on it) and the speed of the paper must always be 1 on 1. Even with a counter-sensor installed, it must still be possible to use the maximum roll width of the press (this can be critical on some machines). Be aware the shaft is ferromagnetic Preferable, the counter-sensor is installed at the beginning of the machine. Page 24 of 32

1. 2. 3. 1. Counter-sensor close to the shaft 2. Copper plate on the shaft 3. Connection box 9.1.3.4 Step 3: Installing the CounterBoXX + connect the counter-sensors A detailed description of connecting the counter-sensor can be found in this document: http://www.cerm.be/hd/onlinehelp1/downloads/technical/installation_sensor.pdf These are the installation steps of the CounterBoXX: Mount the CounterBoXX to the wall. Connect the network cable with the Network connector inside the CounterBoXX. There are 2 RJ45 network connections in the CounterBoXX. It doesn t matter which one is used, both network connections are activated. Connect the electricity cable with the Fuse Module. When all cabling is done, the CounterBoXX can be started by switching ON the Fuse Module. 9.1.3.5 Step 4: Configuration of the CERM-DATACAP This step will be remotely executed by a Cerm consultant. The Cerm consultant needs information from the customer to be able to configure the CERM-DATACAP. Please deliver the following information for each machine: The ID of the machine in the Cerm software The diameter of the shaft having the counter-sensor. The connection place of the cage clamp in the CounterBoXX. These are the things the Cerm consultant will do: Activating the Microsoft Windows license. Configuration of the communication between CounterBoXX and the Cerm database. Parameterization in the Cerm software. Assistance during calibration of the presses. 9.1.3.6 Step 5: Testing (and troubleshooting) In case of troubles, please read the Machine counter troubleshooting guide: http://www.cerm.be/hd/onlinehelp/modules/production/shopfloor/counters/machine_counter_trouble_shooting.htm This document is a list of checks the customer can do to verify the Cerm counter system is working properly. 9.1.3.7 In case of 2 or more Cerm counter systems It is possible to connect 2 or more Cerm counter systems with 1 CermBoXX. There are 2 possible situations: An extra Cerm Counter System can be added to a network already having a Cerm Counter System. An extra Cerm Counter System can be installed in a remote network. Page 25 of 32

Both situations are explained in detail in this chapter. 9.1.3.8 Extra Cerm Counter System in the same LAN as the CermBoXX This situation needs additional configuration or preparation steps: The CounterBoXX will be delivered with another dedicated IP: 10.255.255.3/29. A second CERM-DATACAP (CERM-DATACAP2) will be added to the CermBoXX. The CERM-DATACAP2 will also have another dedicated IP: 10.255.255.4/29. You also see the CERM-ENGINE virtual machine in the above picture. The CERM-ENGINE is responsible for the import of the counter data coming from every CounterBoXX into the Cerm Database (CERM-DATA). Page 26 of 32

9.1.3.9 Extra CounterBoXX on another site and/or another network of the CermBoXX This situation needs additional configuration or preparation steps: The CERM-DATACAP2 virtual machines needs a VMWare ESX(i) platform in the same site/network of the CounterBoXX2. The customer must deliver this ESX(i) platform (server or PC). A permanent connection is mandatory between the customer network with the CermBoXX and the customer network with the extra Cerm Counter System. WAN and LAN connections are supported. 9.1.4 Good/bad toggle switch (optional) Optionally the Cerm Counter System can read good/bad quantities. There is a solution available with an external switch (red/green) on the machine. This will need: 1 extra counter port per machine in the CounterBoXX Extra cables from the CounterBoXX to the machine (wire 4 & 5 of the shielded 5x 0.75 cable) An extra 'toggle button' on the press You must decide if the good/bad functionality will be used before the installation (during ordering the CounterBoXX). If the good/bad switch must be implemented after the completion of the CounterBoXX installation A recabling of the CounterBoXX A reconfiguration of the PLC software in the CounterBoXX It will halve the number of connections for counter-sensors. Page 27 of 32

9.1.5 Workflow description As additional information, this is the overview of the complete workflow of the Cerm counter system: 1. Counter-sensor detects the revolutions of the shaft. 2. The PLC in the CounterBoXX counts the shaft revolutions within a specific time frame. 3. The CERM-DATACAP converts the PLC data to an XML file. 4. The XML file will be processed by a Cerm hot folder on the CERM-ENGINE. 5. CERM-ENGINE will put the data into the Cerm database. Page 28 of 32

9.2 Web4Labels Technical description about the Web4Labels will be available soon Page 29 of 32

10 Important things to know about CermBoXX 10.1 CermBoXX is a blackbox The CermBoXX is designed as a blackbox solution. Cerm doesn t expect the customer to install or maintain the CermBoXX. Cerm will remotely manage the CermBoXX. Therefore, the administrator password will not be communicated to the customer. However: The customer has full access to his database and all database related functionalities. The customer can execute basic maintenance tasks on the CermBoXX (see chapter 5). One of the main goals of the CermBoXX is being as independent as possible from the existing customer s network. The CermBoXX will not be a member of the customer s domain. Changes in the customer s domain will not affect the reliability of the CermBoXX. Cerm will not allow the customer to install additional software on a CermBoXX virtual machine. Also adding additional SQL server databases to the CermBoXX, for use with other software, is not allowed. 10.2 CermBoXX support network The CermBoXX support network is a secured VPN infrastructure connecting every CermBoXX in 1 dedicated VPN network. A CermBoXX has a dedicated VPN connection with the Cerm support network. The CermBoXX support network is used for: Running CermBoXX distributed updates (see chapter 10.3.1). Remote access from Cerm headquarter to the customer s CermBoXX, for remote support and training sessions. This CermBoXX support network gives the Cerm employee full direct access to the CermBoXX virtual machines connected with the INTERNAL switch (see chapter 2.5.1). It has no direct connection with other hosts in the customer s network. Some interesting things about the CermBoXX support network: The VPN connection is established during the startup of the CermBoXX by the CERM-RSM virtual machine. The used VPN software is OpenVPN (https://openvpn.net). The VPN tunnel is established to a VPN server running in a secure datacenter. Of course, a CermBoXX of customer A has no access to a CermBoXX of customer B. 10.3 CermBoXX updates 10.3.1 CermBoXX distributed updates Cerm continuously adjusts and improves the CermBoXX concept. To reduce the costs of implementing these changes and guarantee a stable environment, these changes are grouped into (at least) 2 main updates a year. For practical reasons, these update sessions are bundled with the update of the regular Cerm software. Between the 2 main updates, other updates can be rolled out for specific reasons. All CermBoXX distributed updates are managed and executed by the Cerm technical team through the CermBoXX support network (see chapter 10.2). The customer is not involved in this update process. The CermBoXX distributed update includes: Updates/Patches for the existing OS environments. Software Maintenance Tasks and General Checks. Installation of the next Cerm software release (only on the CermBoXX). 10.3.2 Cerm software updates The Cerm MIS software runs on the CermBoXX virtual machines. Page 30 of 32