Please enable JavaScript to view this site.

Navigation: Invantive Estate > Veelgestelde vragen

Handling Sub- and Master Projects

In the screen Projects you can register and change projects. There are three possible project types:

An individual project: this may include financial data and reporting.

A subproject: this may include financial data and reporting. Moreover, they can be consolidated and reported within a master project.

A master project: it is not possible to include independent financial data and reporting. However, the numbers of the underlying subprojects can be consolidated and reported.

Changing an Individual Project into a Master Project

Perform the following steps to turn an individual project into a master project:

Make sure your filter is empty.

Give the existing project a temporary name: Go to Projects and select the project. Change the code of the project and select ‘Save’.

Create a new project as a master project. This can be done by creating a new project, but also through Copy Projects and just copy the project and subsequently change the project type from ‘Individual Project’ to ‘Master Project’.

Change the project type of the old project to ‘Subproject’.

Select in the data of the old project the new master project as master project.

Enter the cost type prefix. This prefix must be unique for all subprojects within the master project. The prefix is used to make the cost category of each subproject unique in the case of consolidated reporting.

Press ‘Save’.

Usage

You can have multiple subprojects under one master project.

Uncheck ‘Merge Subprojects’ in My Preferences if you do not want consolidated reporting or place a check mark for consolidated reporting.

X

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.

  
Disclaimer