Navigation: » No topics above this level «

Processes

In this screen you can register and change processes, along with their history. Open screen in browser Open Form

A process is an activity to be executed to complete a project. Normally, not all activities are recorded as a process. Usually only the critical activities or the activities that should be monitored separately, are registered as a process. An example of a process that should be monitored separately is a process that has to be performed by several people,

Tasks on a project Screen

The meaning of the entry fields is:

General
Code	The unique code for a process, for example, a contract.
Description	A short description of the target or the problem.
Project	The project to which the process belongs.
Planned Hours	The total number of planned hours to compete the process.
Prognosis to Go Hours	Estimation of the remaining hours required to complete the process.
Hours Determined on	The date on which the forecast of the hours needed to complete the process was made.
Process Holder	The person currently responsible for the following up of the process.
Reported By	The person who has reported the process.
On Behalf of	The organization on behalf of which the process is created.
Origin	The origin of the process.
Supplier Reference	A reference of a Supplier to this process. This can be for instance a report number of a service provider for the heating.
Customer Reference	A reference of the buyer to this process. This can be for instance a reference to a purchasing order.
Category	Processes are grouped according to categoryën. Examples of a process categoryën are: ‘documentation’, ‘failure’ and ‘installation’.
Unit	The unit where the process relates to, see Units.
Fixed Price	You can fill in a fixed price here, if this is relevant on the process.
Impact	The gravity of the problem in case of an unfinished process.
Deadline	The date on which the process should be finished.
Planned Start of Realization	The date on which you planned to start on the running of the process.
Status	The status of the process.
Next Review	The date on which the next review of the process should take place.
Documents	Linked documents, see Linking Documents.
Progress (%)	The percentage which shows how long the process still has to go to be finished.
Remarks	Free text field in which notes concerning the process are taken up.
Contract (not visible)	Pattern for the contract code belonging to process units. With this pattern, placeholders are replaced by actual values during invoicing. The following placeholders are supported: ':pjt_code_short, ̔ ':today̕, ̔:pjt_code̕, ̔:ust_code̕, ̔:unt_serial number, ':tak_code', ̔:hour_yyyy_delivered', ':hour_mm_delivered' and ̔:hour_dd_delivered'.
Process Notes
Category	Process notes are grouped to Process Note Categories. Examples of note categories are: ‘telephone conversations’, ‘emails’ en ‘steering committee meetings’.
Publishing Text	Indicator whether the process note should be displayed to users who have a role that does not allow to see all process notes. The administrator can indicate in the screen Roles if the user is allowed to see all documents with the indicator ‘See all Process Notes’.
Text	Free text box where notes can be added. The entry field grows according to the size of the data entered.
Classifications
Classification	The classification of the process. A classification is a label that can be linked to a project, an organization, a process, a document or a person. Using these labels you can find your information more efficient.
Units Used
Grouping	Group of the process unit. Can be used for accumulation of the task units in task-related groups, such as those are generated by Payment Schedules.
Unit	The unit that is used for the realization of the process, see Units.
Stock	Payment Schedule of the unit.
#Units	The number of units used to achieve the process.
Process Unit Status	Reference to a Process Unit Status.
Unit Sales Price	The price for the used units for the total number of units on this line.
#Billable	The number of units that can be invoiced.
Completed	Delivery date of the units.
Date Start Rate	The date and the number of units in usage.
VAT Code	Reference to a VAT code as registered in VAT codes.
Redemption Price	Purchase price of the Unit.
Booked	The units are booked when checked.
Explanation	Possible explanation.

The meaning of the other fields:

Status Filter	Here you can choose the status filter. The filter has three values: ‘open processes’; ‘closed processes’ and ‘all processes’.
Process Owner Filter	Here you can choose the filter for the process owner.
Counterparty	A reference from a supplier or customer to this process.
Status	Code of the status.
Status Description	Description of the status.
On Behalf of	The organization on behalf of which the process is created.
Name	The name of the process detector.
Product group	The product group to which the process is related. See Product Group.
Product	The Product type.
Unique Identifier (SN)	The unique address, location or serial number of the unit.
Contains	A text you want to search the contents of all visible processes. The process related process notes and linked documents to the process are also searched. The text may be expressed as an expression in Oracle Text. Often used search queries are: •‘area’: documents containing the word ‘area’. •‘area or surface’: documents containing the word ‘area’ or the word ‘surface’. •‘area or surface * 3’: documents containing the word ‘area’ or the word ‘surface’ where the occurrence of the word ‘surface’ counts three times as heavy as the word ‘area’. •‘area’ and ‘surface’: documents containing both the word ‘area’ and the word ‘surface’. •‘?area’: documents with both the word ‘area’ and words that look like ‘area’. •‘area-surface’: documents containing the word ‘area’ but preferably without the word ‘surface’. •‘area;surface’: documents containing the word ‘area’ near to the word ‘surface’. •‘area not surface’: documents containing the word ‘area’ but preferably without the word ‘surface’. •‘$area’: documents containing the word ‘area’ and inflections from it like for example ‘areas’. •‘% area’: documents containing all terms that begin with ‘area’. •‘area or ( surface and feet )’: documents containing the word ‘area’ or containing a combination of the words ‘surface’ and ‘feet’.
Created at - by	Date at which the process is created and by which the user.
Last Change	Date at which the process was last modified.
Source ID	The unique number of the kind of data which you want to link the process. This field is filled automatically when you open this screen via a ‘Process’ link in another window. This field together with the field ‘Source’ makes is possible to retain the relation with the origin of an object for the workflow processes.
Source	The type of data (message, order, project, etc.) to which you want to link the process. This field is filled automatically when you open this screen via a ‘Process’ link in another window.
Statistics
Spent (hours)	The number of hours spent to the process up to this moment.
Invoiced (hours)	Number of hours invoiced.

All changes to a process and process notes lead automatically to a message to the process owner by email.

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Invantive Estate

Processes

Important Safety and Usage Information