Product Overview: Winner Bizz
Cyncly Agreement Document
1. FUNCTIONAL OVERVIEW AND KEY PROPERTIES
1.1 The Product is a bespoke business management solution designed specifically to cater for the needs of kitchen retailers.
1.2 Manage all of the Customer’s shops and/or development projects in one efficient system. Manages functionalities in every step from sales through to installation, across numerous projects in one place. Efficiently report on the ordering processes, and workforce allocation across multiple jobs, enabling oversight without the necessity of in-depth involvement in each individual project.
1.3 Key properties of the Product:
1.3.1 Kitchen business management solution, designed specifically to cater for the needs of kitchen retailers.
1.3.2 Fully integrated to the kitchen design tool Winner Design.
1.3.3 Complete kitchen retail management system.
1.3.4 Integrated document management.
1.3.5 Integrated Mail client: All communication in one place.
1.3.6 After sales management.
1.3.7 Task and resource planner for the fitters: the Product breaks projects down into scheduled tasks, with automatic reminders to help teams manage day-to-day work.
1.3.8 Configurable interface allows to connect easily to third party systems and BI systems.
1.3.9 Database as a service from the cloud.
1.3.10 Mobile Management: Organise installers and fitters with calendars and assembly plans that sync direct to their phones.
1.4 Limitations and Conditions:
Certain enhancements may be restricted for enriched specifications and data with certain catalogues.
1.5 Third-party Integrations:
The Product does not integrate with certain ‘closed’ third-party applications.
1.6 Market-specific Functionalities:
1.6.1 The diverse features in the Product are specifically tailored for designated markets and supplier groups.
1.6.2 IDM data, which includes Eancom ordering and ATAK validation processes.
1.6.3 Block calculation and core selections are exclusively applicable to specific suppliers.
1.7 Technological Advancements and Unique Selling Points:
The Product stands out with its vast global data repository and its seamlessly integrated online platform, which enhances the contract lifecycle management, project oversight, and the design process.
2. MARKETING AND GEOGRAPHICAL REGION
The Product is designed for the KB&F (Retail) market and is sold worldwide.
3. CONTRACT TYPE
The Product is designed to provide both Software as a Service (SaaS) and On-premise solution (for legacy customers). Contacts, projects, designs, and documents are stored on the Supplier’s online database (Azure) while the designing part and supplier catalogue data are running on local machines.
4. TERM
After a Minimum Period of 12 months or 36 months, as specified on the Order Form as the Duration (or for legacy agreements, the Term), this will automatically renew subject to the Conditions.
5. COMMERCIAL/BUSINESS MODEL AND ACCESS RIGHTS
The Product is subject to the following Access Rights:
5.1 The Customer has access to all the modules and extensions specified on its CSO customer file.
5.2 The Product offers two types of licence, a main licence and additional licences. Additional licences can only be acquired after obtaining a valid and live main licence.
5.3 Access Rights to the Product designing tools are controlled by a “named user license” model. The Customer has the ability to allocate the acquired licences to the Authorised Users.
5.4 There is no restriction on number of projects per Year.
5.5 Use of the Product is restricted to Authorised Users allocated licences by the Customer.
5.6 Customers wishing to use the product across multiple trading legal entities would need to purchase separate access rights for each brand or at least in the contract getting written permission to do so.
6. ARCHITECTURE
6.1 The Product has been designed to combine a SaaS solution with a local desktop installation. The SaaS component is developed as a native cloud solution, utilising Microsoft Azure public cloud resources.
6.2 The desktop application is installed in the Customers’ own computers. Regarding the hosted database, each Customer has its own instance.
6.3 The Product’s services are multi-tenant. Each Customer’s business data is securely stored in a dedicated private database (storage container). Data storage is region-specific, stored in a single Azure region (with backup in the same geographical area), chosen based on the geographic location of the Customer and in compliance with Data Protection Laws. For enhanced availability, such services may be hosted in multiple Azure regions.
6.4 The Product is accessible to Customers exclusively in a production environment. The Product is also made available in a test environment (sandbox) on request, allowing Customers to familiarise themselves with updates and upgrades before they are moved to the production environment.
6.5 The platform relies on Azure services and infrastructure, which showcases a service level exceeding 99.9%. Microsoft Service Level Agreements are listed here. There may be scheduled downtime for maintenance or upgrades, which will be communicated to the Customer in advance.
7. THIRD-PARTY SOFTWARE
The Supplier uses third-party software in the development and operation of the Product. The specific third-party software used will depend on the Customer’s individual needs and setup requirements. Use of this software is governed by the applicable agreements with each particular provider.
8. SECURITY MANAGEMENT PLAN
8.1 Microsoft Azure implements stringent physical access controls at data centers and server rooms.
8.2 Data transmission between the Customer and the SaaS application is secured using TLS 1.2 or higher encryption. Data at rest is encrypted using robust encryption methods to protect against unauthorised access.
8.3 The Supplier’s development team adheres to secure coding practices, with regular code reviews to identify and fix potential security vulnerabilities.
9. PREREQUISITES (FOR USING THE PRODUCT) / PLATFORM REQUIREMENTS
9.1 System Requirements are published and updated on the Supplier’s homepage: https://www.compusoftgroup.com/en-au/products/winner-bizz/#product-levels
9.2 Minimum configuration:
9.2.1 Operating system: Windows 8.1, Windows 10 (64bit), Windows 11.
9.2.2 Processor: IntelR Core™ i5, or i7.
9.2.3 RAM Memory: 8 GB.
9.2.4 AMD or Nvidia Chip, Minimum 2GB VRAM, should at least support OpenGL version 3.3 (NVidia Quadro not supported).
9.2.5 Hard disk: SSD 256.
9.2.6 Browser: Chrome 61, Firefox 55, Safari 10.1, or Edge 15.
9.2.7 Internet connection: 1Gbit/s (Wired connection- RJ45 - Cat 6 cabling).
9.3 Recommended configuration:
9.3.1 Operating system: Windows 10 (64bit), Windows 11.
9.3.2 Processor: IntelR Core™ i7, or i9.
9.3.3 RAM Memory: 16 GB.
9.3.4 Current generation AMD or Nvidia Chip, Minimum 4GB VRAM (NVidia Quadro not supported).
9.3.5 Hard disk: SSD 512GB M.2 NVMe.
9.3.6 Browser: Chrome 61, Firefox 55, Safari 10.1, Edge 15.
9.3.7 Internet connection: 1Gbit/s (Wired connection - RJ45 - Cat 6 cabling).
9.4 Port-related firewall settings:
The following ports must be open for output:
9.4.1 Port TCP 20 and 21 (FTPS) if used
9.4.2 Port TCP 25 (FTP)
9.4.3 Port TCP 80 (http/HTTPS)
9.4.4 Port TCP 443 (http/HTTPS)
9.4.5 Port TCP 587 (SMTP, with encryption)
9.4.6 Port TCP 995 IMAP
9.4.7 Port TCP 8080 (HTTP)
9.4.8 Port TCP 8081 (HTTP)
9.4.9 Port TCP 17656 to 17660 if Local SQL server
9.4.10 Port UDP 1434 if Local SQL server
9.4.11 Port TCP 1433 for cloud database
9.5 Browsers recommendations:
Internet Browser installed, up to date, and set as the default web browser for all users. Winner Bizz is a software solution, not meant at this stage to be used on mobile devices.
10. IMPLEMENTATION METHODOLOGY
10.1 The Product offers three types of installations:
10.1.1 Winner Bizz Cloud Installation, via the Supplier’s Flex platform for your location:
10.1.1.1 For European customers https://flex.compusoftgroup.com
10.1.1.2. For Australian and Pacific regions https://live-flex-au.compusoftgroup.com
10.1.1.3 For South Africa https://live-flex-za.compusoftgroup.com
10.1.1.4 For USA https://live-flex-eastus.compusoftgroup.com
10.1.2 Winner Bizz Cloud Silent Mode Installation:
IT professionals can install Winner Bizz on the User's computer through an automatic software deployment process and launch the installation of the Product in silent mode.
10.1.3 Local Installation:
A Customer is installed on a workstation and can be connected to the primary or secondary server or to a nomad (laptop) installation.
10.2 The first step in implementing the Product is discovery and requirements gathering, where the Supplier identifies and understands the Customer's needs and objectives for adopting the Product.
10.3 The Supplier's deployment team sends the Customer a link via our Winner back office. By clicking this link the Customer can register his user credentials. After login in the User can download the Product's iso-file.
10.4 Once the Order Form is signed, the Supplier notifies the deployment team. This team then adds the confirmed number of license keys to the Supplier's license registering tool. This is the same process for adding additional licenses.
11. SUPPORTED VERSION
11.1 All Customers are provided access to the latest version of the Product.
11.2 Updates and Upgrades are first made available in a staging environment. This allows Customers to familiarize themselves with the new version before it is deployed in the production environment. The advantage of first making updates and upgrades available in a staging environment is that it allows customers to become familiar with the new version without impacting their current operations. It can also help identify any potential issues before the version is moved into the production environment, reducing the risk of disruption.
11.3 The Supplier ensures that all customers have the same versions available to maintain consistency and ensure everyone benefits from the latest features and improvements.
12. SERVICE DESK
12.1 The standard service desk provides support from Monday to Friday, 09:00 to 17:00 in the time zone of the Customer’s respective service desk office. The service desk does not operate on weekends or public holidays of your respective service desk office. Extended service hours for Saturdays can be contracted as payable service via Success Plans for mid-business and Enterprise partners. For more information see https://www.compusoftgroup.com/support/.
12.2 Customers can contact the service desk by accessing the Product Support Centre by Winner Bizz (compusoftgroup.com) or by calling the respective service desk.
12.3 For Customers without an active Success Plan, there is no identified obligation that specifies Service Credit entitlement and therefore this is currently not being offered if failing to meet the Service Level for Incident management.
12.4 Termination:
12.4.1 Exclusive Online Termination Method:
The Customer must exclusively use the designated online form, accessible via https://spaces.cyncly.com/termination-request.html, to request termination of this Agreement. Any attempts to terminate this Agreement through other means shall be deemed invalid. The Agreement is only considered effectively terminated upon the Customer’s receipt of a formal confirmation email from Cyncly, verifying the processing of the termination request submitted through the online form. Cyncly reserves the right to review and verify the legitimacy of each termination request to ensure compliance with the Conditions set forth in the Agreement. The actioning of any termination request is contingent upon this investigation, and the Customer will be notified of the outcome accordingly.
12.4.2 Obligations and Product Specificity:
Termination of this Agreement does not absolve the Customer of any accrued obligations or liabilities, including outstanding Fees or Expenses, up to the termination date. This clause applies specifically to the Product identified in the Product Overview of this Agreement, with the understanding that terms for other Cyncly products are governed by their respective product overviews.
13. SERVICE LEVEL AVAILABILITY
13.1 The Service Level for Availability of the Product is 99%, subject to causes outside of the Supplier’s control.
13.2 Availability is calculated by the percentage of requested calls being served as expected.