5.4.1.

3 Synchronize All
Synchronizes the global data (new users, projects added, projects removed, projects moved) and all
subscribed projects.
• Open the main menu File → Offline→ Synchronize all
5.4.1.4 Subscribe Project for reading only
• Open the Data Manager and navigate to the project
• Right-click on the project stub. A context menu is shown.
• Select Subscribe project in Offline mode for reading only
Then the project is retrieved from the Offline Proxy Server and stored in the local Offline DB cache.
5.4.1.5 Subscribe Project for reading and writing
Write access to the project is required.
• Open the Data Manager and navigate to the project
• Right-click on the project stub. A context menu is shown.
• Select Subscribe project in Offline mode for reading and writing
5.4.1.6 Unsubscribe Project
• Open the Data Manager and navigate to the project
• Right-click on the project. A context menu is shown.
• Select Unsubscribe project in Offline mode
5.4.1.7 Add a new project
A new project is created in Offline mode. It is available only in this Offline session. Later this project
should be published to other users and synchronized to the Online database.
• Create new project or import an PFD file with a project
• Open the Data Manager and navigate to the project
• Right-click on the project stub. A context menu is shown.
• Select Subscribe project in Offline mode for reading and writing

• if it is now more than a day beyond the object retention period since last activation, and the project
hasn’t been purged since then.
• if the project is considered to have invalid metadata (e.g. is a pre 14.0 legacy project, or a PFD
import without undo information).
Once housekeeping is configured to purge projects you can consider disabling the automatic purging
of projects on activation, thus preventing the Yes/No dialogue popping up. To do this set ’Automatic
Purging’ to Off on the Storage page of the Project properties dialogue. You can also set this parameter
to Off for many projects at a time (see methods described in section 5.5.4).
5.5.6 Configuring emptying of recycle bins
If ‘Delete recycle bin objects’ is set on the SetHousekeeping object, then when housekeeping executes,
each user’s recycle bin in turn will be examined. Entries older than the number of days specified on the
SetHousekeeping object (see figure 5.5.2) will be deleted.
5.5.7 Monitoring Housekeeping
Once deployed, how do you know that housekeeping is operating effectively? For example, it could be
failing every night with a connection error. An administrator should regularly check that housekeeping
is working. The primary check is to inspect the HOUSEKEEPING_LOG table via SQL or the data
browsing tools of your multi-user database. For each run, housekeeping will insert a new row to this
table showing the start and end date/time and the completion status (success or failure). Other statistics
such as the number of deleted projects are kept. Note that absence of a row in this table for a given
scheduled day indicates that the task failed before it could connect to the database. In addition to the
HOUSEKEEPING_LOG table, there is also a detailed log of a Housekeeping run in the log file of the
Housekeeper user.
5.5.8 Summary of Housekeeping Deployment
The basic steps to implement housekeeping are:
1. Set up the Windows Scheduled Task, as described in the PowerFactory Installation Manual..
2. Configure users expected to be active during housekeeping, as described in section 5.5.2.
3. Configure the SetHousekeeping object as described in section 5.5.3.
4. If using the project deletion task, configure automatic deletion properties for new projects, as
described in section 5.5.4.
5. If using the project deletion task, configure automatic deletion properties for existing projects, as
described in section 5.5.4.
6. Regularly monitor HOUSEKEEPING_LOG table to check for success after housekeeping runs, as

User Accounts, User Groups, and

described in 5.5.7.

Profiles
This chapter provides details of how to create and manage user accounts, user groups, and profiles.
Key objectives of the user account managing system are to:
• Protect the ’system’ parts of the database from changes by normal (non-Administrator) users.
• Protect parts of the databases belonging to user “A" from changes by user “B".
• Facilitate sharing of user data.
The user account managing system provides each user with their own “private" database space. The
user is nevertheless able to use shared data, either from the common system database or from other
users, and may enable other users to use data from their private database.
The user account managing system manages this whilst using only one single database in the background,
which allows for simple backup and management of the overall database.
The default name for a PowerFactory user is the Windows user name, which is automatically created
when PowerFactory is started for the first time.
6.1 PowerFactory Database Overview
A brief introduction to the top level structure of the PowerFactory database is convenient before presenting
the user accounts and their functionality.
The data in PowerFactory is stored inside a set of hierarchical directories. The top level structure is
constituted by the following folders:
The Configuration folder Contains company specific customizing for user groups, user default settings,
project templates and class templates for objects. Configuration folder is read only for
normal users.
The main Library folder Contains all standard types and models provided with PowerFactory. The
main library folder is read only for normal users.
The System folder Contains all objects that are used internally by PowerFactory. The system folder is
read only for all normal users. Changes are only permitted when logged on as the Administrator,
and should be conducted under the guidance of DIgSILENT customer support.

6.2 The Database Administrator

A database administrator account is created with the PowerFactory installation. The main functions of
the administrator are:
• Creation and management of user accounts.
• System database maintenance under the guidance of the DIgSILENT customer support.
Under a multiuser database environment, the administrator is the only user with permissions to:
• Add and delete users.
• Define users groups.
• Set individual user rights.
• Restrict or allow calculation functions.
• Set/reset user passwords.
• Create and edit Profiles (see Section 6.4 for details).
The administrator is also the only user that can modify the main library and the system folders. Although
the administrator has access to all the projects of all the users, it does not have the right to perform any
calculation.
To log on as administrator, there are two options:
• Select the Shortcut in the Windows Start Menu PowerFactory 15.1 (Administrator).
• Log into PowerFactory as a normal User and select via the Main menu Tools → Switch User. Select
Administrator and enter the corresponding password. By default the administrator password
is Administrator.