The basic Cinegy support procedures and workflow are described in this post. Recommendations on achieving smooth and efficient support process and cooperation are provided throughout.
Cinegy support process covers the following cases:
Pre-sales questions. This usually comes from the potential customers/projects and are covered by the sales team providing initial feedback and assistance. When technical support is required, the sales team handles the questions through the internal channels to the support team. The support team is not involved directly into the pre-sales process.
USB hardware dongle update request. When the license on the hardware dongle should be upgraded/changed/renewed, a special ticket type is created. It should contain the dongle upgrade request file together with formal description of the required changes. The ticket can be submitted by the partner on behalf of the customer. Once registered, the request has to be approved by the corresponding account manager. Once the confirmation is received the dongle upgrade will be processed, and the activation code will be provided.Note
Please note that approval is usually possible only within CET business hours unless pre-approved beforehand. So please avoid last minute requests or requests during weekends/holidays as the response time is not guaranteed.
Hardware related questions and requests. Cinegy does not provide an explicit list of hardware configurations and/or vendors to be used as the software can run on commodity hardware with certain parameters to be met. In most cases, the Cinegy System Recommendations document should be used. It is up to the partner to select vendor and machine configuration available locally, precheck typical scenarios and recommend custom configurations to the end user. Cinegy does not provide hardware maintenance support and can only provide general recommendations. Cinegy does provide reasonable help troubleshooting possible hardware issues but does not accept hardware failure complaints.
Issues with the product installation. Each installation is different and has its own unique features. Cinegy describes general installation process and provides product documentation to be learned by partner/customer. It is highly advised for partners to participate in Cinegy training courses in order to become a certified Cinegy Partner. Most of the initial support will be covered by the certification course and this knowledge could reduce deployment time and trivial case support tickets.
Issues with usage/configuration. Most of the tickets are related to specific technical issues appeared during the product configuration and/or usage. Prior to making a request to Cinegy, partner/customer shall make reasonable efforts to resolve the issue using the Documentation from the Cinegy website, Cinegy Open, and Knowledgebase section from the Cinegy Helpdesk portal. In case the issue is not covered by the listed sources, a new ticket should be registered in the system. It is highly recommended to raise a separate ticket for each unique problem to simplify the tracking and support process.
Feature requests processing. In case the issue is identified as a missing feature/new functionality request, its type is changed to feature request. The feature requests processing will be described later.
So what are the ways to register support requests?
Cinegy Helpdesk. The recommended and preferred way is creating tickets on the Cinegy Helpdesk portal – a web-based tool for issues tracking, knowledgebase, troubleshooting, etc. Requests registered in such a way are processed according to SLA, and can be easily tracked.
Email. While it is possible to send emails only to email@example.com, the response time is not guaranteed in this case, and the request will be answered with best endeavors.
Live chat. Cinegy also provides an alternative way of requesting support – mostly for short questions when clarifications are required. The live chat request will be picked up and processed by the first free Cinegy support team member. Live chat can result in a proper ticket in case the issue requires additional technical investigation and cannot be resolved during the chat. More details about live chat are given below.
Remote access. The request for the remote access to the partner/customer system will go through a responsible account manager (Cinegy sales team). Once approved, the support team will request the connection information and proceed with the remote investigation. Please note, that remote access request should be reasonable, and initial technical info about the case should be provided prior to the connection to allow us to prepare necessary tools and/or tests beforehand reducing the required remote session time. It is also possible that Cinegy support team will request remote access to the problematic system to speed up the issue investigation. The preferred way of remote access is via TeamViewer v11.
Registering in Cinegy Helpdesk
The default URL is the following: https://helpdesk.cinegy.com/index.php?. The following page will be opened:
Before accessing the Cinegy Helpdesk portal, customers should create a dedicated account by completing the registration process. Only registered users have access to the tickets.
To start the registration process, go to the "Register" tab; the following form will appear:
Then specify your company details, such as its name and address, and your customer account number. Specify your name, email and enter the password for your account. Please, make sure that the email address entered is valid.
Once the "Register" button is pressed, the account verification message will be sent to the email address you specified.
To complete the registration process you have to confirm the validity of the email address by following the link provided in the email.
In case of the successful validation, you will be able to log in to the Cinegy Helpdesk portal to get access to all content.
Live chat is an embedded feature of Cinegy Helpdesk portal and allows you to contact Cinegy Support team in live mode.
It is expected to be used for short technical questions/issues that require clarifications. A chat may be transformed/routed into a proper Helpdesk ticket if additional technical support is required. Alternatively, a remote session may be accompanied by the live chat.
|Please note, that Live chat is not guaranteed out of business hours German time (CET). Logging issues to Cinegy Helpdesk directly is the recommended way of communication out of business hours in Germany.|
To raise a live chat request, please fill in required details. This will speed up the response time and initial processing as the best available Cinegy support team member will be selected to proceed. Please, have your information about Dongle ID and customer organization ready when starting a chat.
If there is no staff member available at the moment, the system will ask the customer to create a new ticket.
Understanding Ticket Fields
When creating a new ticket to speed up the support process, please provide detailed information on the issue itself and the customer/installation where it is topical.
Dongle ID is a very important bit of information. It is used to identify the end customer and their SLA status. Further ticket processing is only possible when correct Dongle ID is provided. Without the dongle ID, the ticket processing and response time are not guaranteed. The Dongle ID should correspond to the product where the issue is experienced.
In the "Dongle ID" field specify your dongle ID that can be verified in the Cinegy License Viewer utility as follows:
Priority defines the ticket response timing and should be carefully selected to avoid "slow" support for critical issues. When logging an issue, customer will be asked to assign a priority level to their issue. Each ticket is assigned priority that defines the general ticket processing rules and response time limits.
Critical/Emergency should be assigned in case of:
Major functional failure for which there is no workaround at the time the call is logged.
Causes the software or operating system to fail completely.
Requires constant restart of the software or operating system.
Prevents the software installation.
Irretrievable data loss/corruption or severe memory leak.
High/Urgent should be assigned in case of:
Explicitly documented major functionality of the software is missing or not usable.
Obscure, difficult to reproduce, infrequent crashes or hangs.
Software cannot be used as designed, advertised or documented.
Documentation defect has caused a severe error, installation failure or data corruption.
Normal should be assigned in case of:
It does not meet the criteria of priority 1 or priority 2.
Incorrect functionality, cosmetic issue or documentation issues that do not impact core functionality of the product.
Problem does not cause the product to abort or amend.
Defect found in a minor function.
Misspellings in documentation or in product screens.
Additional functionality to be added.
Changing the behavior of the system.
|Please note, that the support team during the ticket processing may initiate the priority change either increasing or decreasing it according to the definitions described above. In order to keep the support process clear and structured we ask to follow the ticket priority levels as much as possible. It is required due to response times associated with priority levels as well as ticket processing rules.|
Products and Versions
It is important to correctly identify the product customer is having an issue with and its version. This will reduce the time required for the support team to confirm the issue and suggest a workaround or provide a fix.
|Please note, that Cinegy only supports the currently released version (N) of the Cinegy products and an immediate previous one (N-1). Cinegy will not proceed requests for support of any other versions, and will close the incident referring customer to the current version.|
When making each request, customer shall provide diagnostic information including but not limited to – hardware details (models, versions, drivers), workflow details (when specific actions are being performed), any logs and dumps from the corresponding product, etc.
If required information is not provided, it may be requested by the Cinegy support personnel.
The system will try to suggest you the articles from the Knowledgebase section that might be related to your problem. Please, review them before submitting your ticket to avoid duplication.
Cinegy Support Tools
To collect the required technical info, we follow an identical procedure in every ticket, the same questions will be asked in different tickets to collect required data. The process of data collection could be a possible source of human errors as data is in different files/formats and locations.
Technical details are very important to speed up the support process. In order to help customers collect the required info automatically without possible human errors, Cinegy provides the Cinegy Support Tools package that consists of several applications. These tools are designed to detect possible issues and collect data automatically. The tools set is being actively extended – new versions will be published once additional features are added.
What are the benefits of Support Tools usage?
The Cinegy Support Tools package is maintained by Cinegy, so it is able to troubleshoot up-to-date versions of Cinegy products.
The package will be frequently extended with additional utilities that should help customers speed up processing of their issues.
The Cinegy Support Tools package is publicly available on our Cinegy portal.
The tools are aimed at providing information in a clear and easy to understand way, thus reducing the operator skills required to identify possible issues while providing enough technical data for deep analysis. This also reduces the number of requests from the support team for providing specific technical details as most of them are already included into the report by default.
|The support personnel request the report almost every time the new ticket is being created. Please, provide such a report on a regular basis.|
Cinegy Reporting Tool
Once started, Cinegy Reporting Tool automatically scans the system and detects all Cinegy products installed in the system. For each of the product selected by the operator, technical details are collected into the report, which is further packaged as an archived file containing all information required for the support team to start the issue investigation – the machine hardware configuration, products with exact builds, log and dump files, etc.
No special training is required to generate such a report. The data collection process is represented in a wizard-like form focusing the operator on a particular area on each step.
Having launched Cinegy Reporting Tool, on the "Welcome" page you will be asked to choose the report generation mode.
Cinegy Reporting Tool is provided in the form of a wizard that guides user through the simple steps allowing easy and convenient workflow.
The initial screen provides user with the general overview of the tool purpose and allows him to select one of two report generation modes:
Typical – when minimal user interaction is required. By default information about all installed products in the system with their configurations and the most recent (up to 10 days old) logs and dumps files will be collected.
Advanced – when user can modify any report generation settings for technical data collection.
|For complete description of the Cinegy Reporting Tool operation, please refer to the Cinegy Reporting Tool Manual.|
Cinegy Report Viewer
Cinegy Report Viewer is the second tool in the Cinegy Support Tools package.
The interface allows a support person (or anyone else) to open the report packages generated by Cinegy Reporting Tool and review the collected data in a human friendly form.
The collected data is grouped into different sections ensuring quick and simple analysis.
Virtually no skills are required to operate the viewer. However, technical training is required to interpret some data.
Once a report file is opened, Report Viewer will show the collected info grouped into sections that correspond to each Cinegy product included into the report.
Each section can be further expanded providing additional info on the selected product. Each section may contain the following information:
Categories – where most of the configuration settings can be reviewed.
Files – where the list of collected files is displayed; individual files extraction for examination is available, if required.
Errors – that lists errors detected during the information collection.
DLLs – that lists the product DLLs together with their advanced details like version, size, etc.
Summary – that is identical to the information shown in Cinegy Reporting Tool when report generation is finished.
For complete description of the Cinegy Report Viewer operation, please refer to the Cinegy Report Viewer Manual.
Processing the Ticket According to SLA
The support team should have a clear idea about the end customer SLA type and ticket priority. Based on this info, the response time limits are defined for the support process. The information about response timing is available in your SLA.
Initial response is the automatic reply from Cinegy Helpdesk after the ticket is registered in the system to acknowledge this fact and inform the customer about the ticket ID assigned to his request. This unique ID identifies the issue and should be present in all communications threads related to this issue.
After the initial response, the customer will receive notifications about new staff posts that should come within the defined feedback interval.
The support person will request the technical information that is essential for the ticket analysis. In case such information is not provided, we cannot guarantee the prompt ticket resolving. If the customer does not update the ticket with the required information, it will be closed in two weeks as expired.
So based on the info provided earlier, the initial ticket processing procedure is as follows:
End customer that experiences the issue is identified.
Dongle ID and the associated SLA type is identified.
According to the SLA status and the priority assigned, the initial response from the support team is generated.
Next updates to the ticket should fall into the defined feedback intervals.
The ticket will be closed when the fix or workaround is provided, and confirmation from the customer that the issue is solved is received.
The ticket will be closed as expired in case it is not updated from the customer’s side within two weeks from the post that requires actions on the customer’s side. The expiration period may be extended in case this is negotiated with the support team. In such case the explicit update date is defined when the support team will request status update.
The ticket may be closed on the customer’s request in case the issue is no longer topical and cannot be reproduced on both sides.
Tickets Processing Stages
Resolution/investigation for the ticket has different stages:
the problem is unclear, the support team is collecting additional info from the customer;
the issue is being analyzed/tested on the Cinegy side;
the logs/dumps are being investigated by the development team and other technicians;
the remote session is initiated in specific cases;
the problem is identified as a bug; the workaround (if any) is provided. According to the priorities and roadmap, the development team fixes the bug.
Once again – it is important to know that Cinegy only supports the current released and immediate previous version of the product. Support for all other versions is not guaranteed, and customer will be advised to upgrade to the supported versions to continue issue investigation. It may also happen that the released versions already contain the fix for the issue raised in the ticket.
|Please note, that in some cases the ticket investigation requires deep technical analysis. In such cases, the issue will be internally passed to the developer/technician and processed. The support team will do their best to provide suitable workaround while the fix is not available. This may include loaning additional temporary licenses to run additional copies of the product, suggesting workflows that allow avoidance of the issue by adding reasonable number of additional steps, etc.|
Once the issue is reproduced and identified as a defect in Cinegy software, the corresponding info will be added to the ticket. The ticket will be updated with the info about the fixing progress.
The ticket will be closed once the fix is provided to the customer and accepted or when the official product release containing the fix is published on the Cinegy portal.
The ticket may be re-opened by customer in case the issue is still topical and further processing is required.
According to the priorities and roadmap, the development team fixes the bugs:
the issue should be reproduced;
the solution to the problem should be found;
the problem is being fixed and the new version is being tested;
the fix is ready, but only for the development branch;
the decision about porting the fix to the current released branch or targeting the next major release should be made by the product manager;
the new release package will be provided to customers when the bug-fix release is ready.
Feature Requests Processing
The following diagram explains the feature request process between customer and Cinegy:
In case the issue is identified as a missing feature/new functionality request, its type is changed to feature request. A special form is provided by the support team within the ticket, and it should be filled in by the partner providing business requirements/describing the required functionality to be requested. The ticket will be closed by the support team, and the form should be provided to a responsible sales manager. Cinegy considers a customer feature request, and internally discusses its value.
Discussions between customer and Cinegy are initiated and proceed until clear understanding of the feature request scope is reached. Once the feature is accepted, it is put into the development roadmap.
In case feature implementation is accelerated by paid development, customer will be updated on the feature progress. Once the feature is implemented and the corresponding version of product is released, the feature request will be closed.