Transparency & standardization
Teamwork
Standardization of workflows. Increased transparency.
Your multi-project platform for coordinating the processes of distributed teams.
Role & task management
Building industry
Coordinated collaboration through clear role and task management. Coordinated implementation of control and monitoring tasks, e.g. SiGeKo, construction supervision, quality and HSE monitoring.
Alignment of planning & implementation
Industry
Ensure your process excellence by continuously comparing planning and implementation. Agile project‑, product- and process-management to control efficient and customer-oriented procedures.
Ownership & availability
Infrastructure
Ensuring the ownership and availability of your data. Transparent multi-contracting over the entire life cycle: planning, implementation, monitoring, deviation management.
Knowledge management & knowledge distribution
Shipbuilding
Improved knowledge management and dissolution of knowledge monopolies. Interface optimization at all levels: Planning, engineering, logistics, production and quality assurance
Evaluation & key figures
Renewable energies
Visibility of weak points and bottlenecks through evaluation options and key figures. Integrated management of planned and unplanned processes to ensure the highest possible system availability.
Features
The features of PROCESSREMOTE create the foundation for sustainable flow in your processes. Continuous improvement thus becomes a self-runner.
versatile
Management of scheduled or event-initiated processes and process deviations
Checklists, protocols, inspections, audits, surveys in connection with construction supervision, quality assurance, HSE management, planned and unplanned processes such as installation, commissioning or maintenance tasks or trouble shooting — ProcessRemote supports you throughout the entire process: from planning to results analysis.
Simple meeting minutes, action lists or note or idea logs can also be easily mapped using the flexibly definable process element types.
Whether your processes are to be implemented in large-scale projects, in locally or organizationally distributed projects or in projects with complex products — ProcessRemote supports you in recording, providing and continuously updating relevant information in a structured manner.
ProcessRemote is based on structuring principles such as project structure elements (e.g. the individual wind turbine in a wind farm) and product components (e.g. a generator within a machine network).
Using an individually definable process structure, your sustainable project management is made possible.
PMI-inspired
Proven best practices and transparency in operational project and asset management
ProcessRemote enables you to handle your project and asset processes in a multi-project landscape in line with PMI (Project Management Institute) standards. Proven PMI concepts regarding organization/responsibility management, project structure organization and scheduling ensure efficient implementation of planning and operational processes.
ProcessRemote clearly displays the results of the project planning phase by means of a work breakdown structure or WBS and a backlog of the project processes, e.g. the execution and/or monitoring and control process group.
ProcessRemote allows you to manage project participants with their respective responsibilities at company and individual level.
Assign an authorization to the active and passive stakeholders according to their respective project role or the work packages defined therein and control them.
ProcessRemote ensures sustainable, structured process data availability and seamless traceability of project data.
connective
Seamless collaboration via web and mobile app via the Azure backend — in addition to OData API
Technically speaking, you work with your ProcessRemote instance as a tenant on the Microsoft Azure platform.
Access is either via the Blazor web interface, the ProcessRemote mobile app or via an OData interface.
Each Tennant has a completely separate, individually manageable data area.
Process planning in terms of content, scheduling and responsibility as well as project management are carried out on the web-based administration platform.
The handy ProcessRemote app also guides and tracks your processes at the various project locations.
If your network connection is insufficient, you can also run your processes offline.
In the course of automatic synchronization, all data is later updated for you and brought completely up to date.
An OData interface for administered data exchange is available for connecting ProcessRemote to other management systems, such as ERP.
thought out
Integrated planning, operational processes, implementation status and KPIs at a glance
The challenges in the execution of projects often do not lie in the overarching planning or in the technically clean execution of work within a discipline.
On the other hand, all kinds of interfaces — technical, organizational, process-related, process deviations, the implementation of process improvements or, for example, the inclusion of new stakeholders in ongoing processes — continue to cause difficulties.
It can happen that individual processes that have been temporarily de-prioritized are not resumed, the overview of the backlog is lost or logically or locally related information is not recognized and treated as such.
ProcessRemote supports you in creating transparency and consistency.
Through process versioning, various categorization forms, a result assessment at process step level, a concept for handling process deviations, a continuous change log or the process-related storage of files or images, you always have an overview and maintain control using reports and dashboards.
Use cases
Project management
ProcessRemote: easy to implement, reliable to control!
Project and process planning takes place in the back office and provides all the necessary basics for your distributed teams — e.g. location, scheduling and content planning, methods and structures for meeting minutes or action list management.
By tracking implementation in the field, you can ensure that targets are achieved.
Checklists/protocols
Store your paper checklists and protocol-like work instructions in ProcessRemote and assign them to your products and projects.
Provide targeted guidance for individual work steps and keep track of the status of all work.
Do you want to handle deviations from expected results in a structured way?
ProcessRemote also provides the right methods for this.
Multi-Contracting
Managing a multicontract setup presents the leading party with numerous challenges.
PROCESSREMOTE supports you here in a variety of ways: Provide your partners with access to the platform you operate and ensure efficient interface management in this way.
Maintain ownership of process data and ensure that dependencies remain manageable.
Audits
The preparation and execution of an audit is often a complex procedure that is intended, among other things, to serve the sustainable development of the audited area.
ProcessRemote supports you in the execution and processing of audits as well as in the sustainable development, application and implementation of standard measures that must be implemented in the event of deviations being identified.
Inspections
Inspections usually follow a defined inspection protocol.
In ProcessRemote, this is stored together with a result type definition (e.g. OK, nOK, a numerical value or selection text).
Findings can also be recorded without a connection to a predefined protocol, photos can be added and the connection to the project or product components can be established.
Trouble shooting
The aim of troubleshooting is to carry out work promptly and cost-effectively.
ProcessRemote supports you in identifying and applying proven methods for solving errors on site — even in offline mode.
Information recorded during the work process can then be used to further develop the solution processes.
Surveys
Surveys are used to systematically gather an opinion or to collect distributed information, e.g. through interviews.
ProcessRemote is an ideal platform for planning and implementing these processes.
Import your survey schemes and make them available to colleagues working in the field quickly and easily.
This allows you to view and evaluate data collected in real time.
Product management
ProcessRemote is based on consistently ensuring that your process information is product-related.
A product can be diverse, e.g. a machine, a service or even a higher-level support process.
In most cases, the product-related processes are implemented by specialists from various disciplines who implement planned and unplanned processes in an interlocking manner.
In complex projects, different products are often implemented in parallel, e.g. the production, installation, commissioning, acceptance and quality assurance of a turbine together with the planning and construction of a transformer station.
At the product level are product structuresthe associated product processes, a scheduled product backlog and the responsibilities at discipline level are defined in abstract terms.
In concrete terms, these processes with specific deadlines and responsibilities within product instances planned and implemented.
This is done transparently and controlled in the respective projects.
Product structures
The product components are defined in hierarchical form.
In addition to the product name, other relevant properties can be stored.
For example, you can map plant structures in a parts list or defined auditing aspects in a tree structure, thereby ensuring that your process data is linked to the relevant products or their components.
The product structure information is of course also available to users of the mobile ProcessRemote app, ensuring consistent information structuring even when used remotely.
Product instances
Product instances are the specific characteristics of your product — e.g. the specific wind turbine of type X that is to be installed at a specific location.
As soon as you assign a wind turbine type X project structure element to your project, the predefined product components and the processes defined at product level are generated automatically.
The responsibilities are specifically assigned to the discipline-related work packages and an initial baseline schedule is derived for your product.
If individual product structure-related characteristics are relevant for the generated PIs (e.g. serial numbers of a gearbox), these can also be stored.
Product backlog
ProcessRemote enables dynamic management of your product scheduling in the backlog through the automatic dependency of process components on reference milestones.
As soon as either reference dates or the date offsets provided in the backlog change, the baseline dates of the process and the process elements defined in it are automatically shifted.
Your advantage: An initial project plan for your processes is available in just a few steps, ensuring that no planned process is neglected.
Product processes
The processes consist of individual process elements that are arranged in a sequence and hierarchy.
Process elements are always based on a predefined type, which controls the properties and behavior of each individual process element.
All processes are derived from process templates.
These can be further developed and are versionable.
The backlog to be implemented at the time of execution always refers back to the version active at that time, which automatically controls the further development of the process.
Distributed management
Structures
A balance of predefined and freely configurable structures for an optimum level of transparency and efficiency in management.
Collaboration
All of your company’s stakeholders, whether employees, customers, suppliers, shareholders or business partners, can be involved according to their role.
Workflow
Using a simple example, we will show you how the systemic concepts interlock and how the individual system objects are connected and developed.
Let’s get started — project, structural elements, a first work package
Setup
Define the project structures and assign the respective products — for example, map a wind farm with its locations and assign the turbine types as a product.
You have already defined the work package structure and the people responsible for it.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.
No work without an order — you can also guarantee this systemically
Order
In addition to the customer, the individual items and the target project are defined for an order — regardless of whether it is placed externally or internally.
In the next step, the requested order scope is pre-planned operationally by assigning the process backlogs to these items.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.
Product-related or individual processes are pre-planned in the backlog
Backlog
The purpose of a backlog item is to map the expected workload in the form of pre-planned processes.
The backlog provides a scope, deadline and responsibility baseline for the implementation of each of your project structure elements.
With just a few clicks, you can create a baseline plan for your project.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.
Concretize the timeline of your baseline planning by fine-tuning processes
Planning
Depending on the respective boundary conditions and priorities, you can detail the implementation of your backlog in the calendar overview.
Adjust the responsibilities at work package and team level.
As soon as you have provisionally completed the planning of a process, the status is set from “planned” to “InWork”.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.
Distributed execution of your processes
Execution
Entsprechend der Arbeitspaket-Depending on the authorization of the members of their work packages, they can handle the planned and unplanned processes via the web application or the mobile app.
If the work is carried out outside of mobile network coverage, synchronization before and after the work is carried out ensures the availability of work content and results.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.
Dynamic handling of your standard processes, e.g. after the occurrence of a finding
Customization
If process deviations occur, the relevant additional information can be stored logically in addition to the standard processes.
If a correction process is already planned, it can be called up and inserted seamlessly.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.
Overview of the success and status of process implementation
Conclusion
The open/closed status of the process elements makes it possible to see at a glance where the expected results have not been achieved and the criticality of a deviation. Once a process has been provisionally completed, it is released — a process is only closed when all process elements have themselves been closed.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.
Clear reports show the evaluated implementation status of your processes
Reporting
You can view or print out a snapshot of the process implementation at any time.
The level of detail of this output can be set via parameters according to the respective requirements.
If required, a report is distributed for the process release in accordance with the RASCI definitions of your WBS.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.
Clear presentation of your KPIS
Dashboarding
A target/plan/actual comparison of your planning can be visualized in the same way as a deviation analysis for individual process steps across your distributed projects.
Backlog analyses are also informative, e.g. to map and evaluate outstanding work volumes across the various disciplines of your organization.
Transcript
You have created an order item with reference to the project.
In the next step, you plan the implementation of the order in the form of a backlog.
As an example, create a backlog item for the project structure element GT05.
You give this a name.
Then assign the order item you have just created and select the template for the process to be implemented.
You also define a move-in date — in this case an individual date in March 2025.
They also stipulate that the process should be carried out twice at intervals of 6 months.
Save this.
You can now see the created backlog item in the GT05 project structure element.
Initially, the associated processes have not yet been created.
After saving the new definitions, you will be asked to confirm the creation of the two associated processes.
The two newly created processes are now available for further processing in the Process tab with the status “Created” at a time interval of 6 months.