Skip to content

Proof-of-Concept guidelines

We are delighted that you would like to evaluate our platform as part of a Proof-of-Concept (PoC). The following suggestions, recommendations and templates will help you to carry out the PoC promptly and successfully.

Preparation & planning

1. Participants

The following participants in various roles are involved in the PoC:

Role Name Contact details
Decision maker A
Project manager B
Administrator C
PoC Executor & Tester E
Interested G

2. Customer motivation

What is the customer's motivation for the PoC and how useful could a future use of be for this motivation in their organisation?

Motivation Customer benefit
(low, medium, high)

3. Customer requirements

What are the customer's requirements that should be verified as part of the PoC?

Level Requirement Executed & tested
Functional 1.
Non-functional 1.
AI content 1 .

Info Executed & tested should be documented during the PoC.

4. Success criteria

What are the criteria for a successful PoC from the customer's point of view, which leads to the use of in their company?

Criteria Type
(must, nice to have, surprising)

Info Fulfilled criteria should be documented to the end of the PoC.

5. Activity & time planning

Activity Organizer Time Estimated time Notes
Preparation 60 minutes
PoC KickOff 30 minutes
JoureFix weekly 30 minutes per JF
Setup environment 15 minutes
Setup inventory (OneImporter/OneGate and importer configs) 15 minutes
Config 15 minutes
Core solution - Inventory & change mgt
60 minutes
Other solutions (security, goverance, process monitoring) depends on customer
PoC results presentation 45 minutes
Coordination of further procedure 30 minutes

Tip Planning should take place during or after the kick-off and be communicated to all those involved.

Procedure for the implementation

1. Setup a PoC environment

To carry out the PoC, the team provide you with a free environment in the SaaS instance for 30 days. All participants receive technical access including administration rights for the PoC environment. After setup, you will receive two e-mails from the SaaS environment. You can use the links contained in the emails to set your initial password and receive a link to the environment.

Estimated time required: 15 minutes

2. Install OneImporter & OneGate

In this step we install the OneImporter and OneGates, which we need for the inventory of the data sources requested by the PoC customer.

Reading tip: The difference between OneImporter & OneGate

Administrative access to the corresponding hosts is required once to install OneImporter and OneGate.

A corresponding installation wizard is available in the user interface for the installation (goto install wizzard). You can download, install, run, stop and uninstall the OneImporter and OneGates using the command line commands.

Automation tip: The command lines for installing OneImporter and OneGate can be easily integrated into DevOps Pipeline (e.g. Ansible).

Estimated time required: 15 minutes

3. Set up the inventory configurations

The importer configurations must now be defined, which are executed by the OneImporter or the OneGate and inventory data from a data source or a third-party system. The configurations are generally kept so simple that they can be defined in one minute per importer configuration.

The following table contains links to the relevant information. Get an overview of the available importers and configurations and implement them in the platform.

Description Link
Overview of all available importer integrations
Manual that describe importer specific configuration attributes
Set up inventory importer configuration in

Tip: First obtain the access data for the data sources and external systems to be inventoried. This usually takes the longest :-)

Estimated time required: 5 minutes per importer configuration

4. Use of inventory & change tracking

If you have inventoried data from your IT landscape or your business environment, then you need to learn the basic functionalities for handling the data in the platform. This includes

Function Note
Instance viewer Understand how an instance and its changes are structured and how you can analyse them.
Reporting Create your own customer (pivot) report.
Topology Create and use your own topology.
Change tracking Understand how you can analyse changes over time.

For each basic function, an overview of the functionality including a practical implementation should be trialled.

Estimated time required: 120 minutes

5. Evaluate solutions delivers standard solutions that create added value for companies on the basis of inventory data. Depending on customer requirements, these should be selected from the following list:

  • [ ] Product end-of-live assessment
  • [ ] Security vulnerability assessment
  • [ ] Governance policy verification
  • [ ] Change request execution monitoring
  • [ ] Protection requirement assessment
  • [ ] Risk management
  • [ ] Service & experience monitoring
  • [ ] Technology radar
  • [ ] Delta topology analysis
  • [ ] Process & job monitoring

For each solution, an overview of the performance including practical implementation should be obtained.

Estimated time required: 60 minutes per solution

6. Finalisation

The following activities are recommended for the professional finalisation of a PoC:

  1. Finalise documentation of the PoC process and results.
  2. Present the PoC results to all those involved to ensure a common understanding of the pros and cons.
  3. Coordinate the next steps between the customer and

Estimated time required: 4 hours