Onboarding

LAUNCHING A PILOT PROJECT

Starting the future together

Are you curious about using a new software solution, but recoil at the thought of making the changeover? Do you fear losing valuable working time? That’s entirely understandable! In many cases implementing new solutions brings about not just an abrupt stop with your previous system, but also a double burden for your whole team. Good to know, then, that you can forge new trails in a relaxed manner — for example with COMAN.

With our pilot project, we accompany your journey over the course of 14 weeks in just three stages. During this time, you only need integrate one key user and can try out COMAN in parallel with your usual processes. Compare your previous workflows directly with the new possibilities we offer and see the added value. Convinced? You’ll have another pleasant surprise – as the data from your pilot project becomes the framework for your follow-up projects. Just one of the ways that we help keep your efforts required for full integration low.

Go straight ahead

SIMULTANEOSLEY

Our system’s test phase runs parallel to your previous, unchanged working methods. You can now effortlessly evaluate both workflows in real time and discover the world of advantage we provide.

ONE TO ONE

We rely on delivering close support – which is why there is only one contact person on each side: our COMAN Application Specialist and your key user. Through this interface, you can then both, one by one, bring other stakeholders and decision-makers on board.

FUTURE MODEL

From your existing project standards and workflows, we create your initial, individual data model, which you can easily reuse, extend and add to all your future themes and settings.

PILOT PROJECT PROCEDURE

Who takes which steps?

CLIENT

COMAN

PREPARATION – WEEK 1

1. Kick-off meeting

Joint status comparison, goal setting and runtime.
We get to know each other, then set priorities and goals together.

2. Identify pilot project

Select an appropriate project.

3. Designate key user

Determine the contact person who will be the person in charge.

4. Server setup

We set up the appropriate infrastructure together with your IT team. For pilot projects we can use our servers (ISO 27001), for future cooperation we will happily use yours.

5. Provide project data

Provide us with your CAD layouts, quantity structures, schedules and relevant checklists, and other important data.

VORBEREITUNG – WOCHE 2

6. Initialize data model

As basis for both your first and later projects, we build and configure your individual data model – based on established workflows, milestones and processes. From these components we establish new standards for working on your projects.

7. Transfer data

We marry your provided dates, quantity structures and documents with our Smart Objects. These bundle all related information at one point and help you visualize it as required.

8. Set up interfaces

If you want to integrate an additional application such as a ticket system, we now tie the prerequisites for synchronization with our data hub.

9. Customizing

Common setup of views, access rights and reports: Who sees what, when and in which form?

10. Web training

In a lean launch, we get your participants on board together.

PILOT RUN TIME – WEEKS 3 > 14

11. Progress tracking + monitoring

You’re off! Simply document your milestones, play through possible additional topics for your deployment, and learn about the benefits we bring at your own pace.

11. Consulting, support + guidance

New experiences always bring about new questions. It’s for this reason we will remain constantly at your side. And if necessary, we’ll continue to look after new issues for you.

12. Projekt review

We evaluate the results of the pilot together, answer each other’s questions and discuss both further roll-out and your need for additional adjustments or, for example, interfaces.

“When can we get started?”

Contact now

SOFTWARE INTRODUCTION WITH COMAN

Approaching possible hurdles, and how we overcome or prevent them.

Even though the term onboarding is more used in human resources, it fits perfectly with our approach to software implementation. This is because we take you with us on a journey into the future, on which we have taken numerous well-known companies. The special thing about the COMAN way is that anyone who uses our on-site management software in plant engineering or other industrial sectors benefits from the experience of all the other users. By constantly and practically adapting our software to the daily challenges of our customers, we develop features and solutions that benefit everyone in the COMAN community.

We know that introducing new software is characterized by a number of hurdles – because in most cases there is a deep intervention in the established processes and structures of a company. However, when introducing COMAN software, hardly any new steps are necessary at first, because by integrating your interfaces and standards to our data hub, you can keep your existing tools and systems. We dock with you, so to speak. Of course, a certain amount of change and adaptation of familiar processes is part of implementing something new – but then again, introducing new software is usually because you want to change and improve things.

Often, the introduction of a new software solution in plant engineering or other areas fails because the documentation and information transfer regarding the new processes are inconsistently implemented. However, since these aspects around status capture are at the core of our interpretation of project management in plant engineering, and thus a path to the Digital Project Twin, you can free yourself from this concern.

The biggest challenge in a software implementation is usually the additional burden on the people involved. This is where our Application Specialists come in. They take care of your questions about efficient project work with COMAN during the pilot phase. Productivity and motivation can often be lost if those involved do not actually have time for an introduction ‘on the side’ or if those involved are not made clearly aware of the advantages that will directly result for them in the future: less effort in data maintenance, less susceptibility to errors in activities and better plannability. COMAN visualizes all of this. Our Smart Objects, coupled with an intelligent system of roles, rights and views, allow us to illustrate for each individual the influence of the status of other trades on their own work and scheduling.

FAQs

More questions about onboarding? Read on for our answers!

What type of project is suitable for the pilot?

Whether you choose a simple or complex project in which there are many different participants, you can start small and expand at any time. It is precisely in the coordination of internal departments and external trades that we can best demonstrate our advantages. This is also true if the target and actual values of the initial project already differ from each other, because it is precisely these inevitable deviations and the COMAN way of dealing with them that we illustrate to you in our pilot project in particularly transparent ways.

How time-consuming is the pilot in real implementation?

Our experience and target are 14 weeks: two weeks of preparation on our side after consultation with the customer and twelve weeks of pilot runtime. But since projects and milestones differ greatly per customer, there may be deviations from time to time, or we can decide on an individual schedule together at the beginning. The common goal is not to complete the project within the pilot period, but to give you a feeling for the added value. Here, experience shows that the first 2-3 weeks are completely sufficient. In the following weeks, you will already begin to contribute your own ideas and you can, of course, continue to work with us seamlessly while we evaluate the pilot and discuss future collaboration.

Can I bombard you with questions at any time?

Yes, at any time. We even ask for it, because we work in a particularly process-oriented way, adapted to individual customer needs.

We have very special processes that absolutely have to be taken into account, how flexible are you?

This is our strength. Our software is designed to be as flexible as we learned to be as a start-up, so that we can map your individual processes, standards and tools one-to-one or connect them via intelligent interfaces. Strict quality standards, exact documentation requirements or complex release processes – throw everything at us that others have difficulties with!

What kind of interfaces do you offer?

You can find a first overview here. In short: anything that can exchange data via API or in the simplest case file-based can be integrated.

I want to continue after the test, what happens now?

Based on our experience from the pilot project, we now know your needs so that we can agree on the scope of the license and further adjustments. Of course, if your pilot project had a longer duration than the agreed test period, it will continue seamlessly so that no one’s work is interrupted. Once the contract has been signed, you can directly use COMAN in your further projects and continue to be closely supported by our COMAN Application Specialists, if desired. Together we can carry on and expand the added value of the solution step by step.

How much should I budget for the pilot project?

Just get in touch and our sales department will contact you soon.

FURTHER INFORMATION

Learn more about software implementation

POST

Implementing innovation through software in a team

PRODUCTLANDSCAPE

TTS – Our solution that synchronizes your data

ARTICLE

LAUNCHING A PILOT PROJECT

SIMULTANEOSLEY

ONE TO ONE

FUTURE MODEL

PILOT PROJECT PROCEDURE

1. Kick-off meeting

2. Identify pilot project

3. Designate key user

4. Server setup

5. Provide project data

6. Initialize data model

7. Transfer data

8. Set up interfaces

9. Customizing

10. Web training

11. Progress tracking + monitoring

11. Consulting, support + guidance

12. Projekt review

“When can we get started?”

SOFTWARE INTRODUCTION WITH COMAN

FAQs

FURTHER INFORMATION

Implementing innovation through software in a team

TTS – Our solution that synchronizes your data

Software acceptance factors in companies