DeutschEnglish

The Software

In Action

For You

N5-Process Solution

Document your company on the basis of processes
leer
struktur

Structure processes
Define your process landscape from the top down, from the top process level to any depth of detail. Methodical and clear-cut for intuitive use.

 turtle

Who? How? What? What with?
Configure processes completely and from end to end based on the turtle model. Select process responsibility, inputs and outputs, requirements and much more.
leer leer leer
beziehungen

Define interactions
Define the inputs and outputs of your processes and then select the activities to deliver and receive. That makes for consistency of processes!

 lenken_process

Control and archive
After editing, send your documentation for review. Once approved, the new version is published and the old version is archived.
leer
aenderungen_process

Track changes
The automatic revision service makes it easy for you to keep track of all changes in your management system documentation.

 vorgaben_process

Define defaults
The various location documentations consist of defaults and locally created processes and documents as specifications in separate process landscapes.
leer
dokumente_process

Requirements under control
Are legal, standards-related or customer requirements hailing down on you? N5-Solutions offers you the solution to creating the desired transparency.

 n5-process_200

Structure and View

Freely structure the process map
Process types can be designed individually in terms of content and graphics
Unlimited number of process levels
There is no technical restriction of the detail depth for process models
Top-down modeling
Processes must be modeled from top down (increasing detail depth)
Different content views
E.g. as a graphic, in tree structures, etc.
Graphic design options
Symbol libraries and drawing aids are available
Functions for copying and structuring
Processes can be copied, moved and easily edited
Swim-lane functions
Interactions between processes can be depicted in swim lanes of the responsible departments

Process Contents

Process responsibilities can be defined in the organigram
E.g. by defining a function in the organigram - no free text definitions
Additional applicable documents from the centrally controlled document pool
Further applicable documents are controlled independently and can be linked to the process
Define interactions
Previous and subsequent processes are defined by means of input and output links
Add formated descriptive texts
Supplementary descriptions can be added and formated individually
The requirements from any number of catalogues can be linked
Requirements from any catalogue desired can be assigned to processes individually
Target figures can be defined
Key figures can be structured in scorecards, defined using any units desired and can be selected for processes
Process risks can be described
Potential interfering influences can can be described for each process
Quality gates (milestones) can be added
Milestones with test requirements can be defined between individual processes and can be visualized

Flow Chart

Library of symbols (shapes) and connecting lines
Symbols and lines can be managed and also blocked from use
Drawing aids are available
Orientation functions, paper format settings, etc.
Responsibilities, participation and reporting obligations can be defined in the organigram
E.g. by defining departments in the organigram - no free text definitions
Additional applicable documents from the centrally controlled document pool
Further applicable documents are controlled independently and can be linked to process steps
Definition of hyperlinks
Links to external sources (HTTP, file, etc.) are possible
Inputs and outputs can be defined
Inputs and outputs are explicitly-named process attributes
Add formated descriptive texts
Supplementary descriptions can be added and formated individually
Target figures can be defined
Key figures can be structured in scorecards, defined using any units desired and selected for process steps

Publication

Automatic publication for viewing on the intranet
Released processes can be published on the intranet with no technical effort
Print version
An accurately formated output (e.g. PDF) incl. all information of relevance for control is available and can be saved or printed
Change notices
Notifications are made regarding an edited process version
Version history
All versions of a process documentation are traceable and can be called up
Notification / Distribution list
Affected employees are informed of changes automatically 
Searches can be configured
Desired search parameters can be enabled individually (possibly with a separation between editing and reading mode)

Process Maps for Areas of Applicability

Separate process maps can be created for individual areas of applicability
E.g. for locations, divisions

The process maps can be designed individually in terms of content
Processes, documents, organigrams, users, etc.

The process maps can be designed individually in terms of graphic appearance
Design of the reading mode, etc.

Navigation to process maps is supported
E.g. by developing a location selection page (map), selection boxes, searches

Interactions between process maps can be documented

Input/output mapping across process map boundaries

Editing access to individual process maps can be restricted for users

Mandating of work areas

 

 

 

 

 

 

 

 

 

 

 

 

Defaults for Processes

Default processes can be passed on to subordinate process maps
Changes to default processes are also passed on

Default processes can be partially adapted in subordinate process maps

Change of selected attributes of processes (e.g. process responsibility)

Local processes can be created beneath default processes

Addition of local specifics at lower levels

Several processes can be passed on from top to bottom

“Copying” of several default processes in a single action

Changes to default processes and default documents are passed on downwards

Local adaptations remain unaffected

Local administrators are notified of changes
Automatic e-mail function

 

 

 

 

 

 

 

 

 

 

 

 

Review and Archiving

Automatic archiving function

When a new version is released, the previous version is archived by the system - no manual intervention is required

Previous versions are available at all times
The history of processes / documents can be called up at any time

Creation of an historical documentation status as of an effective date
Compilations of the documentation in its entirety for a selected date can be created

Invalid processes / documents remain in the database

Access at any time, even to components which are already invalid

Review cycles can be defined for each process / document

Specification of a follow-up interval

Default lists for processes and documents in need of rework are available
General review lists for supervisors and personalized lists for creator, etc.

Review memorandums are also recorded in the workflow
The date of the last review, the reviewer and comments can be seen

All information of relevance for control is documented

Both in the on-screen view and the printout

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Workflow of Processes

The workflow is implemented in a role-based manner

The creator, examiner and releasing user can be defined

The phases of creation, checking, release and released are supported
Normative requirements made of the workflow are fulfilled

The users are notified

After completion of a phase, the users concerned are notified by e-mail

Version management is supported
The current version builds on the previous version

Personalized work lists are available
Individual users have personalized overviews available for “My Processes”, etc.

Notification feature can be freely managed
Workflow notifications can be customized in terms of content and the distribution list

The workflow status for each process / document is clearly visible
Marking of processes and documents with respect to current status

 

 

 

 

 

 

 

 

 

 

 

Revision Service

Changes made to processes are indicated automatically

The system automatically compares a version to its previous version

Changes made to processes and documents can be described and commented on manually

Authors, examiners and releasers can provide notes regarding the version

Change notes are clearly visible in the process / document
All readers receive information about the relevant changes

There is a chronological change overview of all content
List of all changes by date

Interested parties are notified automatically
Reading users are automatically notified of changes

Change requests can be sent to the authors

Electronic auto-suggest feature

 

 

 

 

 

 

 

 

 

 

Copyright © - N5 GmbH - All rights reserved

Imprint