FAQ’s

Home > FAQ’s

System environment / further development

What does the system environment look like?

Figure system environment

blank

 

Can own requirements and further developments be commissioned?

Yes, in compliance with the Testify standard development process; in close cooperation with the client.

 

Can the software be functionally customized and adapted to individual needs?

Various functions and workflows are modular and flexible by issue and can be used according to the role concept. 
Further developments or customer-specific requirements are planned together with the customer in a requirements meeting and implemented in Testify Standard. Feature requests can be registered via a comfortable ticket portal if our SLAs are used. If required, the feature can be ordered after an internal refinement process. 

 

Can updates be postponed or rejected?

Yes, Deployment-Pipeline according to the hosting variant and SLA in coordination with the client.

 

Where is the data kept?

depending on the selected operating variant.
A) Software as a Service (SaaS) in Testify shared Cloud (Microsoft Azure): Data is held in central Testify Cloud (MS-Azure) (Netherlands and Northern Ireland)
B) Private Cloud: Installation and hosting in a specially set up MS Azure Cloud environment (resource group), incl. possibility for backup plan
C) Client’s MS Azure Subscription: Deployment and hosting in the customer Azure infrastructure with numerous additional functions, such as Azure AD connection
C) On Premise: Deployment and hosting in customer-supplied infrastructure depending on Testify System Requirements.

 

Is the data storage compliant with the GDPR?

Yes

 

If the data storage is provided by the manufacturer, is it redundant?

Yes, geo redundancy (Amsterdam and Northern Ireland in Microsoft data centers)

 

Are all GDPR requirements guaranteed to be met?

Yes, see privacy policy

 

How are the native iOS App and the Android app made available?

via iOS-App-Store; Android via Google-Play-Store;
alternatively via WebApp with the same functionality, e.g. in case of on-premise or client-side store restrictions

 

What effects can a version change (release) have? Is it possible to reject a change or postpone it until later?

New versions are released at regular intervals according to our standard release cycle (2 to 4 weeks). Thus, performance improvements are achieved and additional features are available. The basic operation does not change. Release updates are made available to the defined key users via our release notes in the online wiki before the update.

 

How do I put a shortcut from Testify on the desktop or autostart?

  • Android: Using the “Add to home screen” function

  • iOS: Using the “Add to home screen” function

  • Windows: can be placed on the desktop as a shortcut

Which hardware is supported by Testify?

  • Tablet

  • Desktop PC

  • Smartphone

Notifications

 

When are which mails sent?

Notification settings can be adjusted via Administration –> Users –> Notification settings. Here you can define to which event an (e-mail) message should be sent.

 

Is it possible to send mails to “Non-Testify users”?

No.

 

Working offline

 

What is meant by “offline functionality”?

Checklists can also be processed without a network connection. For this purpose, the data of the checklists available offline must be stored on the end device via the “Take offline” item in the task overview.

Then the checklist(s) is/are displayed under the menu item “Offline data” and can be used offline from there.

Issues can always be created and processed offline.

Note: If you have been working offline, it is essential that you synchronize your local data to the server before leaving Testify. As long as “0” is not displayed in the menu item “Offline Data” in the “WILL BE SYNCHRONISED” tab, not all data has been synchronized.

 

 

Checklists

 

Can tolerance ranges be defined, which generate an error message in case of deviations?

Tolerance ranges can be defined for the checks in a checklist (numerical checks) by specifying a lower and upper limit.

Furthermore, control/warning limits can be defined. Thus, control chart mgmt. use cases can be easily recorded and evaluated in our dashboards.

 

Is there something like a variant configurator to generate the appropriate test specification with the individual options of the machine after the receipt of a customer order and the resulting bill of materials?

It is possible based on an import of the variant from a previous system (SAP) in the sense of a parts list. The test specification (checklist in Testify) has to be set up in a modular way, so that you get a checklist for each variant that can be assigned. In addition, the usability of our checklist construction kit is very simple and intuitive, so that you can easily create a new checklist individually for each variant – this depends, of course, on how often such a process is triggered.

Can errors in the assembly line be reported to the foreman via the app?

Errors can be reported and even processed via Testify in the integrated issue process. Within this process, there are also various possibilities for automation such as the automated assignment of defined issues (issue category) to defined users or user groups including photo documentation.

Can a custom layout and branding be created?

Yes, the Testify (Web)App can be given your own corporate design, using our white labeling options.

Interfaces

 

What kind of interface is there?

Third-party systems are integrated via our public Rest API. In addition, there are standard connectors to the most widely used third-party systems.

 

What options are there for connecting your own interfaces?

Our Customer Success Team will be happy to help you and  provides you with advice.
office@testify.io

 

Monitoring

 

Is there a monitoring set up?

Yes, via Application Insights at Testify Shared Infrastructure.

 

Incident Management

 

How are we informed by the manufacturer about outages (start, end, intermediate status)?

By SLA’s with proactive notification to defined key users from Testify App Insights Monitoring

 

Are we informed about problems of all components?

Yes, about all components that could potentially affect the customer.

 

How quickly and how often will we be informed?

That depends on the classification of the business-critical components.

 

What is the content of the information?

start/end of the outage, reason, approach, workaround, impact

 

Through which reporting channels can outages and problems be reported?

Via our intuitive Customer Service Desk, when using our SLA packages.

 

Can it be determined who may report insicents to the manufacturer?

Yes, with the jointly defined Testify key users

 

Data protection

 

What personal data can be collected?

User name (e-mail address), title, first name, last name, language

 

What can personal data be used for?

Used to identify and assign a user in Testify. Contact through Testify.

 

Authorization procedure

 

How does the authorization of users on the system or in the app work?

Username + Password (via Identy Server)
Integration via Active-Directory possible, incl. Azure AD Look-up

 

Role concept

 

What does the role concept look like?

Based on available functions, roles can be designed individually and with fine granularity.

 

What roles are there?

Pre-defined standard roles such as issue-processor, quality manager and administrator are provided. Own role definitions can also be created and adapted individually.

 

How are roles and authorizations assigned?

All actions visible in the frontend (buttons, features, functions, etc.) can be individually authorized for each role. In connection with the creation of groups, we thus enable our customers to map their individual organizational structures – this functionality has already been tested with customers from various industries and of various sizes (from local players to multinational corporations).

 

Are the roles strictly predefined or can they be customized according to requirements?

Roles can be created individually and independently according to internal company guidelines and responsibilities.

 

If so, how precisely can individual roles be defined (e.g. admin role: one role with all rights or several admin roles with possibly restricted rights)?

We recommend that you define a role for a defined user group with all rights to avoid possible deadlock problems in advance. In addition, however, you can create your personal administrators with limited rights in various roles and thus map your corporate structure.

 

Security

 

Is the software regularly checked for known security vulnerabilities?

Yes, regular penetration tests are performed to ensure security.

 

Operation

 

What do the contracts look like?

SaaS – License agreements in combination with SLA
For interface project additional Software Delivery Agreement

 

How is the operation contractually regulated?

via SaaS license agreements and SLA
Special conditions for On Premise Hosting (e.g.: license audits)

 

Is monitoring regulated by contract?

Yes, depending on the chosen hosting variant and SLA

 

How is the Incident Management contractually regulated?

Via a Service Level Agreement.

 

How long are the contract periods, version periods? How long does the support last?

The PoC is for a minimum of 3 months and a maximum of 6 months as an accompanied test phase. The following conditions apply for a transition to regular operation:

Maintenance

 

Will there be a separate maintenance contract?

No, maintenance is defined in our general SaaS license agreements and SLA’s.

 

Price models

 

What does the price model look like?

Please contact us at office@testify.io

 

Application documents

 

Is there a user manual?

Yes, an online wiki including feature FAQ’s and regular detailed release notes. 

 

Who conducts trainings on the system?

Initial training is carried out by Testify (knowledge transfer) by key users defined by the company. Further training of the end-users by your company.

 

Can we develop trainers ourselves?

Yes, this is recommended by Testify. In line with the key user principle, we recommend that you nominate one or more employees to ensure the transfer of knowledge. Based on this, the training of your end-users can be ensured.

Live Demo

What is a Live Demo?

In a live demo of the Testify application we show you in a personal team video conference all core functions of the Testify application and your personal use case is discussed in detail. You can book the live demo under this link. Our Customer Success Team will then contact you with possible appointment suggestions. The live demo is free of charge and without obligation. 

What do I need for the Live Demo?

For the Live-Demo you need a working internet connection as well as a laptop or stand PC. You will receive a Microsoft Team appointment from our Customer Success Team, which you can join with a link.