Using Safran Project System Administrationdownload.safran.no/Download/Doc/37/SA37.pdfThe Safran Project System Administrator, Sysadm or SA for short, is an application tool to help

Using Safran Project System Administration

Copyright (c) 1999 - 2011, Safran Software Solutions AS. All Rights reserved.

AccuracyAlthough every effort has been made to ensure the accuracy and completeness of this document, no warranty, expressed or implied, is made by Safran Software Solutions AS as to the accuracy of this publication and the features or the applicability of techniques suggested.

Copyright NoticeThe information provided in this manual is for informational purposes only. It may be changed without notice, and does not represent a commitment as to merchantability or fitness for a particular purpose by Safran Software Solutions AS.

The software described in this manual is provided by Safran Software Solutions AS under a Safran License Agreement. The software may be used only in accordance with the terms of the license agreement.No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Safran Software Solutions AS.

Safran is a registered trademark of Safran Software Solutions AS. Safran Project, Safran Details, Safran Enterprise Developer, Safran Planner, Safran for the Microsoft Project Platform, Safran for Microsoft Project, Safran Web Access and Working Smarter are trademarks of Safran Software Solutions AS.All other brands and product names are trademarks or registered trademarks are property of their respective holders.

i

CHAPTER 0

CHAPTER 0TABLE OF CONTENTS

Overview1 Using the Administrator's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Safran Project Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Distributing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Safran Project System Administration Features . . . . . . . . . . . . . . . . 3

Planning and Deploying Your Safran Project Installation

Deployment Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Stakeholders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Deployment Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Planning the Infrastructure and Safran Project Configuration . . . . 8

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Roll Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Safran Project Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Using the Safran Project System Administration Application

Starting Safran System Administration . . . . . . . . . . . . . . . . . . . . . . 11

Safran System Administration Window . . . . . . . . . . . . . . . . . . . . 12

Users and Security User Names and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Safran Project Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Safran Project User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Access and Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

User Access Object Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Application Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Defining and Maintaining Users

Adding a New Safran Project User . . . . . . . . . . . . . . . . . . . . . . . . . 16

Deleting a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Create a New Safran Project User Group . . . . . . . . . . . . . . . . . . . 18

Adding a User to a New Group . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Remove a User Group Membership . . . . . . . . . . . . . . . . . . . . . . 18

Delete a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Object Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Transferring ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Login Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Restricting Access to a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

ii

Managing the Safran Project Database

Initiating a New Database for Safran Project . . . . . . . . . . . . . . . . . 23

Upgrade a Safran Project Database to Latest Version . . . . . . . . . . 24

Database Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Look at Database Tables with Definitions . . . . . . . . . . . . . . . . . . 26

Look at Database Views and their Definitions . . . . . . . . . . . . . . . 26

Look at Database Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Look at Database Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Database Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Execute SQL Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Run a SQL Command-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Save Database Tables as OS-files. . . . . . . . . . . . . . . . . . . . . . . 29

Restore Database Tables from OS-files. . . . . . . . . . . . . . . . . . . 29

See all current Safran Project users (Sybase, SQL-Server only) 30

Update Database Statistics (Sybase, SQL-Server only) . . . . . . . 31

Maintain Database Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Browse Safran System Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Creating a New Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Delete an Existing Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Grant / Revoke Access to an Object . . . . . . . . . . . . . . . . . . . . . 34

Maintain Reports, Filter Groups and Pictures . . . . . . . . . . . . . . . . 34

The Report Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Report Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Filter Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Pictures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Setting up the Enterprise Fields and Codes.

Setting up the Enterprise Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Importing/Exporting Enterprise Fields and Codes . . . . . . . . . . . . 25

Setting Network Defaults Network Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

INDEX

1

C H A P T E R

OVERVIEW

Safran Project is a comprehensive project planning and project management and control software, engineered to let project organizations plan, organize track and monitor their work. Built on Microsoft SQL Server, Oracle and Sybase databases it provides organizations with enterprise project management scalability.

Your Safran Project installation includes the Safran Project application, the Safran System Administrator application and the Safran Report viewer software. Additionally your organization may have the companion products; Safran Details, Safran Details Developer, Safran Project Enterprise Developer or Safran Web Access.

The Safran Project System Administrator, Sysadm or SA for short, is an application tool to help you set up your databases for Safran Project, define users, user groups and permissions, maintain system and versions, upgrade your project management software and more.

Using the Administrator's GuideThis guide provides the System Administrator with the knowledge and skills necessary to plan, deploy and maintain a Safran Project installation. This includes installing, configuring and upgrading the Safran Project database structure (tables), creating users, permissions, creating objects and maintaining profiles.

As a system administrator you may want to read the Safran Project System Guide, which outlines the Safran database and table definitions, and includes the Safran Project data model. You may also want to refer to the Safran Project user guide “Exploring Safran Project” for details on system objects, SQL commands, and import/export features.

You should also read the Customer Release Notes and the Installation Guide to get an update on installation and system requirement information.

This guide is organized as follows:

Chapter 1: Overview, an introduction to the Safran Project System Administrator guide

SAFRAN PROJECT SYSTEM ADMINISTRATION

CHAPTER 12Overview

Chapter 2: Planning the Safran Project installation and deployment

Chapter 3: Users, security and permissions

Chapter 4. Maintaining Users and User Groups

Chapter 5: Maintaining the Safran Project Database.

Safran Project DocumentationThe Safran Project documentation consists of a set of on-line manuals available on the Safran Project CD-ROM. You can access online documentation by inserting the Safran Project CD-ROM in your workstation's CD-ROM drive, and opening the applicable .PDF file to view the information using Adobe Acrobat Reader. The following table describes each manual:

Distributing InformationThe online documentation can be copied to a network drive, or to a project intranet for access by project participants. Each team member can then print only those portions that specifically relate to his or her role in the project.

Title Description

Exploring Safran Project The Safran Project user’s Guide. Provides a detailed description of how to use the system.

Safran Project Systems Guide A guide to system information such as data-base definitions, tables and fields.

Safran Project Installation Guide A guide to assist you when installing the Saf-ran Project software.

Safran Project Systems Admin-istrator

This Guide. Includes information about plan-ning and deploying a Safran Project imple-mentation, User and user access, groups and group access and how to use the features of the SA application.

Customer Release Note The Customer Release Note - CRN for short - contains information about new features, enhanced functionality and errors corrected in the last version of the software. The CRN also contains information about changes to the database, system requirements and sup-ported environments.


3

Safran Project System Administration FeaturesThe SA application offers a number of features to help you set up, control and

coordinate the use of Safran Project. Some of the features include:

• Initiate a new Safran Project database

• Upgrade a Safran database to latest versions

• Maintain/update list of valid user

• Maintain/update list of user groups

• Maintenance and transfer of ownership to objects

• Run SQL queries

• Maintain database profiles

• Grant/revoke access to objects

• Restrict access to application areas

• Maintain report groups

• Maintain filter groups.

• Create and update Enterprise Fields


CHAPTER 14Overview


5

C H A P T E R

PLANNING AND DEPLOYING YOUR SAFRAN PROJECT INSTALLATION

To Successfully deploy Safran Project a structured approach to all planning and deployment activities are recommended. This chapter gives a brief overview of some of the issues related to a successful implementation of Safran Project.

Enterprises often have a standard working practice or framework for deploying technology across their organizations. This framework may include definitions of roles and responsibilities, implementation checklists, configuration planning, planning the infrastructure and servers, definition and planning of end user training and a phased deployment.

What we aim for is a practical approach to system implementation that enables a struc-tured, visible and managed implementation.

Deployment TeamIf you are planning a Safran Project Enterprise implementation, you may need to consult with several people in the organization. Because job titles and responsibilities vary significantly from one organization to another some adaptation may be needed to make the roles listed below meaningful. Roles can be combined and roles may be filled by resources inside or outside the organization.

RolesRoles required in your deployment team may include:

• Business manager

• Project manager

• IT professional/network administrators

• Developer and system integrator


CHAPTER 26Planning and Deploying Your Safran Project Installation

• Tester

• End user trainer

StakeholdersIn an organization there are also several constituents or stakeholders to the implemen-tation project that play a vital role in the success of your deployment and implemen-tation. People within these groups help you and your team to identify business attributes and configuration characteristics for the deployment. The constituent groups are:

• Executive Management

• Finance

• Human Resources

• Project Management office

• IS/IT Technology

• Training

• Staff Managers

• Project Managers

• Project Team Members

Working together with these groups, and possibly others, your teams should gain a good understanding of the constituents perspective on project management within the organization. In addition to collecting valuable information it can also help to establish internal sponsors and discover any resistance to change.

If your organization has a group that sets and communicates project management standards, members of this team should be engaged in the deployment team. They should play a vital part in the deployment by developing standards, definitions and training materials.

Deployment PhasesYour organization may have a detailed framework for installation and deployment of technology projects, so you may want to check this with your technology or program manager. Safran recommends that installation and deployment of Safran Project should at least cover the 3 phases listed below.


7

NOTE:The number of issues addressed through a system implementation phase may vary according to the size of your company, number of projects, number of locations and number of users. A single user Safran Project personal edition would normally be a straight forward “follow the instructions” installation.

Phase Description

1 Planning Before you begin the installation, decide how your organization will implement Safran Project. Analyze current infrastructure and plan for high availability and scalability. Plan both desktop and server installa-tion.

2. Installation and test Install and configure infrastructure, servers and the database server software (Oracle, Microsoft SQL Server or Sybase). Define and configure users, user groups, access and permissions, corporate codes, cal-endars and resources. Test and stabilize the imple-mentation Set up reporting templates.

3. Roll-out Train the users and install the full scale implementa-tion of Safran Project according to your implementa-tion plan. Review the deployment and implementa-tion project.



Planning the Infrastructure and Safran Project ConfigurationBelow we have listed a few issues to be discussed during the planning phase of your Safran Project implementation and deployment project.

• Identify the number of users and their locations

• Analyze users, security, roles and access issues.

• Identify Safran Project components.

• Analyze current infrastructure and identify existing hardware as deployment candi-dates.

• Analyze your database servers.

• Analyze and identify your database server software and versions.

• Plan for scalability.

• Analyze system integration issues

• Identify tools that may assist in deployment.

• Analyze desktop hardware and software requirements.

• Identify corporate project management practices, standards and codes.

• Identify training requirements.

• Review codes and descriptions

• Review of live Projects

• Create the data migration plan.

• Select a test team or a pilot project.

InstallationOnce your network and infrastructure configuration document and Safran Project configuration document are approved you can start to set up your network and and prepare your servers and desktops. Install and configure the third party database server software and create database users. Now you can install the Safran Project database definitions, and create users and user groups. Once your network, servers and the project management database is installed, you can begin to install the Safran Project application according to your implementation plan.


9

Work with your Project Management group to set up calendars, codes, user fields, resources and templates. Perform any data migration procedures as needed to upgrade projects from your previous project management system to your new implementation of Safran Project. Your implementation team should work closely with your Project management group and the selected test pilots to make sure your implementation meets the requirements set out initially.

NOTE:Read the installation guide for details on supported environments and how to install the Safran Project software.

Roll OutThe roll-out phase covers introduction to Project Management theories and product training and practice. You will use the knowledge gained through the pilot project or pilot phase to successfully deploy the system throughout the enterprise and migrate project data to Safran Project according to your implementation plan.

Finally your deployment team should review the entire deployment project.



Safran Project ArchitectureThe basic architecture of Safran Project consist of set of applications that run on your network connection to a SQL database.

On the client level you can install the Safran Project Enterprise Client or a Safran Personal Edition Client. The Personal Edition client comes with a standalone database, and is a smart and suitable choice for your lap top implementation, and it is easy to bring with you as a single user system on travel, to the site office and more. The Personal edition may also be used as a Enterprise Client accessing your corporate Safran Project database and projects.

You will also find the report spooler application. This application allows you to schedule report packages to be run at regular intervals at any time day and night. The reports spooler software should be installed on a pc of its own. One that is not shut down during the night, so that it can keep track of scheduled reports 24/7.

The Safran Web Access client is the browser based client that allows project members, stakeholders, team members, project managers and executives to view project and portfolio reports.


11

C H A P T E R

CHAPTER 3USING THE SAFRAN PROJECT SYSTEM ADMINISTRATION

APPLICATION

The Safran Project System Administration application is used to initiate and maintain your Safran Project application and database. To be able to access the Safran Project SA, a database and at least one user with database administrator privileges. Creating databases (and schemes in Oracle) is normally among the tasks that the IS department like to consider their domain. Therefor we recommend that you contact your IS department and work closely with them. Please also read the installation guide before starting the installation of Safran Project.

If you are running a Safran Project personal edition with a Sybase Adaptive Anywhere run-time database, the database is already set up together with a DBA user, and the Safran Project SA application can be utilized after installing the software.

Starting Safran System AdministrationDepending on you installation there are three ways to start Safran Project System Administration.

1 Using an Icon. For convenient access, a windows capability allows a short-cut icon to be added to your desktop.

2 Using the windows Start Menu. Another windows capability that is available for initiating programs is the Start Menu.

3 Choose the program file (.EXE) from the appropriate directory window in your windows explorer.

USING SAFRAN PROJECT SYSTEM ADMINISTRATION

CHAPTER 312Using the Safran Project System Administration Application

To login, Select Database system, enter your System Administration Log in ID and Password, and specify database name. The system administration login and password should be provided by your IT/IS department. If you do not know this information you should check with your IS department.

The ODBC button allows you to browse for your Sybase Adaptive Anywhere database(s) Pressing the “more” button allows you to enter required detailed infor-mation about database system, server (location) and database name.

Safran System Administration WindowThe main System administration window is illustrated and described below.


13

The Safran Project System Administration application is a neat system providing you with a focused set of features and menu options.

The main tool bra provides you with short- cut access to functions from the File and Tools menus; Change Database, Save, Users/Groups, Database Objects, Database Profiles, Object Browser, Report Browser, Report Groups and Windows Restrictions.

Use the The File menu to change database, save your changes and exit the Safran Project System Administration application. The Change Database option allows you to monitor, update and maintain several Safran Project databases and installations from one Safran Project System Administration session.

The Tools Menu lets you add and modify users and user groups, work with database tables, view, procedures and more, Crete database profiles, view and maintain project definitions, network definitions, Calendar sets, Profile sets, User field sets, Resource sets, Symbol sets, Rule sets and Network Groups. You can also add, and maintain


CHAPTER 314Using the Safran Project System Administration Application

report groups and filter groups and change ownership of reports, set login configu-ration, set access restrictions to Safran Project windows, define Enterprise fields to be used for this database and set network defaults.

For details on the different functions and options please see the relevant chapters in this guide.


11

C H A P T E R

USERS AND SECURITY

Safran Project provides two mechanisms for protecting against unauthorized access:

• User name and password - to prevent “outsiders” accessing your project data

• Access permissions - to control the actions authorized users are allowed to perform on the objects in your Safran Project implementation.

User Names and PasswordsWhen you start your Safran Project session and select the database you wish to use in your Safran session, Safran Project asks for your user name and password. It checks the information in the user tables of that database to see if they are a valid combination and, if so, starts your Safran Project session.

Safran Project UsersControl with who can access Safran Project is mainly kept by creating users, who can be granted or denied access to Projects, Networks and Sub Networks, Network Groups Calendars, User field sets, Resource sets, Symbol sets, Rule sets, Rate sets and Profile sets. The users are kept in the table "users" with columns "login_name" and "full_name".

Each Safran Project user must also be a database user. If a user is created in the System Administration Application, the application checks if a corresponding user exists, and creates a new user if necessary. (A corresponding login must be created first, by the database system administrator). All Safran Project users should be members of at least one database group. When a Safran Project database is initiated, a default group is initiated, and this group is granted "all" privilege to all the tables, as well as "execute" privilege to stored procedures. Initially, all Safran project users should be assigned to this group.


CHAPTER 412Users and Security

If the system administrator wants to differentiate the database privilege between different groups of users a new group may be added, and some of the users moved from the default group to this new group. The system administrator must then keep track of which users belong to which database group, and grant and revoke privilege accord-ingly.

Safran Project User GroupsTo simplify access control, Safran project users can be organized in user groups.

NOTE:These are NOT identical to DBMS groups, it is important to keep these two concepts apart.

When you select the access permission for the objects in your Safran Project database, you can give all the members of a group the same permission.

A user can be member of several groups.

Information about groups are kept in two tables: One table "user_groups" keeps the definition of the groups, with columns "group_id", a numeric identificator for the group, and "name", to keep a descriptive name for the group; another table "group_members" with column "group_id" and "login_name", keeps track of which user is member of which groups.

When a Safran Project database is initiated, the default group "public" is created, with group_id=1. All new users are given membership in this group. A user can be a member of one or more groups.

Access and PermissionsAccess is set on different objects: Networks, Subnetworks, Projects, Calendars, Userfield Configurations, Profilesets, Resource Sets, Global Sets, Symbol Sets, Rule Sets and Windows. On Networks and Subnetworks there are four access-levels: Read, Test, Update and Exclusive - on the other object types the only levels are Read and Update.

The owner of a Safran Project object is the user logged on to Safran Project when the object is created. Normally it is the owner who grants other users access to his or her object. New Safran Project objects can also be created by the system administrator from the SA application. And the system administrator is also allowed to grant users access to all Safran Project objects.

If a user has "read" privilege to an object, the user is allowed to report on this object, and to look at its data, but not to change its contents.

"Update" privilege allows the user to fully load and change/update the data.

"Test" access on a network allows the user to open the network in one of the editors, and to alter the network logic and activities at will. The results cannot be saved back to the database, but the network can be saved under a different name.


13

"Exclusive" means that no other users can open the network for update while this user has the network open.

Access can be given to groups, or individual users. Any user's privilege to any object equals the maximum privilege the user has individually or as a member of a group. If a user is member of the public group, and this has "read" privilege to a network, the user can be given "test" privilege separately to allow the user to perform a "what if" - analysis.

To Delete a Safran Project Object you must be the owner of that object, or you must be the system administrator logged on to the SA application.

User Access Object TypeThere are two tables for access control: "user_access", with the columns "login" (user), "object_id", "object_type" and "access_level" (From 1(Read) to 4 (Exclusive); and "group_access" with "group_id", "object_id", "object_type" and "access_level".

Code Safran Project Object Access levels

N Network 1=read,2=test,3=update,4=exclusive

S Sub-Network 1=read,2=test,3=update,4=exclusive

R Resource set 1=read,2=update

J Project 1=read,2=update

P Profile set 1=read,2=update

C Calendar 1=read,2=update

U User field set 1=read,2=update

W Window 1=read,2=update

A Rule set 1=read,2=update

B Symbol set 1=read,2=update

G Network Group 1=read,2=test,3=update,4=exclusiv

L Global Sets 1=read,2=update

O Rate Sets 1=read,2=update


CHAPTER 414Users and Security

Application WindowsWhereas access must be set explicitly on standard object for a user to be able to access them, windows are by default accessible for all users. To restrict user access to a window, this window must be added to the list of windows with limited access. If a window has restrictions, only users granted access to the window can open it.

NOTE:See the system guide “System Tables and Definitions” for a model of user access and objects.


15

C H A P T E R

DEFINING AND MAINTAINING USERS

On of the primary functions of Safran Project System Administration is the creation and maintenance of Safran Project users. Every user that will be accessing Safran Project must be defined as a valid Safran Project user.

The User Maintenance option allows you to:

• Create New users

• Create New user Groups

• Delete Users

• Delete User Groups

• Change/modify Users full Name

• Remove/add Group memberships

• Set login method

• Change object ownership

• Set windows restrictions

Select Tools>Users/Groups from the main menu or click the Users Icon on the main toolbar.


CHAPTER 516Defining and Maintaining Users

The User Maintenance window is a two -paned windows with a hierarchic out-line style window on the left and a list of users, groups, and user details on the right.

If you in the left pane select “users” the right pane displays a list of all defined users with login Id and full name.

If you in the left pane clicks on the users icon and select a individual user, the right pane displays the login Id and the full name together with any group membership of that individual user.

Selecting user groups in the left pane window displays a list of defined user groups in the right pane.

Selecting a user group in the left pane, displays group memberships in the right pane.

NOTE:To save any changes, choose "Save" from the File-menu (You may also click on the "Save" Icon on the window toolbar, or press Control + "S"). If you should close the window without saving, you will also be prompted to save before closing.

Adding a New Safran Project User

NOTE:In Oracle the system administrator must create a database user. In SQL-Server and SQL Anywhere a database login must be created before a database user is created. A database login can only be created by a database system admin-istrator. Be sure that these are in place before creating corresponding Safran Project Users, as it is not possible to create a Safran Project User without a corre-sponding database user.

In the user/group maintenance window, select "Users" in the outliner pane, and then "Add user" on top of the user-list. ("New" from the Edit menu or press Control + "N", has the same effect). The "Initiate new Safran Project user"-window will appear:


17

Now you can select a name from the user name drop down, which contains users in the database who are not registered as Safran Project users (In SQL-Servers, along with Server login who are not users in this database). Choosing a user may also initiate the "full name" field, enabling you to choose next.

All Safran Project users must be assigned to a group. Select your group from the drop down list box and press the create button to create your new user.

Deleting a UserIn the user/group maintenance window, select the user. Choose "Delete" on the "Edit" menu (you may also click on the "Delete" icon on the window toolbar, or press Control + "D"). You should now be prompted to confirm deletion of the user. Dropping a user into the dust bin when "Users" is selected in the left pane has the same effect. You may also drop a user when that user is selected in the left pane, by clicking on the icon in the right pane, and drag the user to the dust bin.

NOTE:Before deleting or removing a user from your Safran Project database, please read the “object Ownership” section carefully. Deleting users also removes his or hers filters, layouts and report specifications



Create a New Safran Project User GroupIn the user/group maintenance window, select "User Groups" in the outliner pane, and then "Add user" on top of the user-list. ("New" from the Edit menu or press Control + "N", has the same effect). The "Initiate new Group" - window will open:

You should now enter the new group's name. Having done that you click "OK", and the new group is created and ready to accept members.

Adding a User to a New GroupIn the user/group maintenance window, select the user. The user name and full name will appear in the right pane, above the list of groups the user currently is a member of. Drag the icon to the left of the name, and drop it on the group to which you want the user added.

Remove a User Group MembershipIn the user/group maintenance window, select the user, and the list of groups the user is a member of, will be shown. Click on the group, and drag it to the dust bin in the bottom right corner. This will remove the group from the list.

OR:

Select the group, and the list of users will be shown. Drag the user over to the dust bin instead. The user will disappear from the list.

NOTE:You cannot remove a user from the "Public" group!


19

Delete a GroupIn the user/group maintenance window, select the group. Choose "Delete" on the "Edit" menu (you may also click on the "Delete" icon on the window toolbar, or press Control + "D"). You should now be prompted to confirm deletion of the group. Dropping a group into the dust bin has the same effect.

NOTE:You are not allowed to delete the "public" group.

Object OwnershipBy default the user creating any of the Safran objects ( projects, networks, symbol sets, resource sets, rule sets, userfield sets, calendar sets, profile sets and user saved report specifications and filters) is defined as the Owner of the objects.

For all objects other than filters and report specifications the owner assigns user access to these objects. This may also be done by the System administrator. All users may use filters or report specifications created by any user, but they are not allowed to modify or alter any of these.

When you remove a user from the system, the object owner is no longer valid. The system administrator is now the only one who can grant users access to the Safran objects, other than reports and filters. The system administrator may also change Ownership from one user to another on all objects.

Removing a user also remove his or hers filters , layouts and report specifications as these are “private”. However if a users report specifications or filters should be available to other users, you should transfer ownership to a new user.

Transferring ownershipTo transfer object owner ship before removing a user from the system, select Tools>Users/Groups. In the User Maintenance window highlight the owner/user and select the Owned Objects option (the Key icon, or Edit>Ownership). The SAfran Project System Administration application now provides yo with a list of all objects defined by and owned by the selected user.



To transfer ownership select the object type and transfer all objects of this type by using the Transfer all to option or transfer named object individually to any users by selecting the transfer to option.

NOTE:Ownership for objects other than reports and filters may also be changed using the Object Browser option.

Login MethodThe System administrator can define user login method:

• Normal

• Extended security

The extended security option uses hidden login name and password to the safran database.

The Systems option configuration also allows you to specify default user group for new users.

NOTE:These options apply to all users

Select Tools>System Options.


21

Restricting Access to a WindowYou may want to restrict access from some of the areas or features of Safran Project, allowing only some of the users to e.g. update project information, update calendars, run the initial Baseline, have Access to the SQL window etc. To do that, you restrict access to the relevant window.

From the main menu choose "Tools", then "Window Restrictions". The window for window access control opens up. In the left pane of this window there is a tree view with "Restricted Windows" on top, exploding to show the names of all windows with access restrictions implemented.

Initially the right pane gives you the same list of restricted windows. Selecting a window-name in the left pane gives you the usual access-control module, enabling you to grant/revoke access to the window, to users and groups in the usual manner.

To place restrictions on a new window, you may push the "Add Restriction"-button with the top level selected in the left pane. You can also choose "New" - then "Window" - from the "Edit" menu (Or click on the "new" icon on the window toolbar, or press Control + "N"). You are then presented with the list of windows, where you make your choice and push OK.




23

C H A P T E R

MANAGING THE SAFRAN PROJECT DATABASE

This chapter contains information on how to initiate a new database for Safran Project, how to upgrade your Safran Project database to latest version and use the database utilities and system objects features of Safran Project System Administration. For details on tables and table definitions please see the Safran Project systems guide - System tables and definitions.

Initiating a New Database for Safran Project

From the main menu choose Tools>Database Objects. Then highlight "Utilities", and double-click "Upgrade Database". You should now see the "Database Upgrade" - Window, with an edit to input the directory where the initialization files reside (if the


CHAPTER 624Managing the Safran Project Database

SQL-files have not been moved since installation, the default should be correct). You can enter the path directly in the edit box, or use "Browse" to select the correct directory.

When the correct path is entered, the "Status message" should display "Ready to initiate Safran Project Database". Push the "Upgrade"-button to start database initial-ization. The SQL-command files will be run - if any errors should occur, you will get a message asking you to Continue or abort, telling you what the problem is. Normally no such problems should occur. After creating the necessary database objects, the database is ready for Safran Project use.

NOTE:When setting up a database in Microsoft SQL Server 2005 make sure the collation is set to Latin_1_General_CI_AS or Danish_Norwegian_CI_AS. Database creation, initialization and updating must be done by a dbo account to ensure the default schema is used.

Upgrade a Safran Project Database to Latest Version

NOTE:For Oracle users: You need to know the names of the table spaces to be used for table data and indices. If these are anything but "safran_data" for the data and "safran_index" for the indices, you need to edit the SQL-command files named "spdbxxx.sql", in the "ORA" sub-directory. You must replace "tablespace safran_data" and "tablespace safran_index" with the correct names, or, if indices shall be kept with the data, remove all "tablespace safran_index".

From the main menu choose "Tools", then "Database Adm." and "Database upgrade". You should now see the "Database Upgrade" - Window, with an edit to input the directory where the upgrade files reside (if the SQL-files have not been moved since installation, the default should be correct). You can enter the path directly in the edit box, or use "Browse" to select the correct directory.


25

When the correct path is entered, the "Status message" should display "Ready to update database from version <current version>". Push the "Upgrade"-button to start database upgrading. The SQL-command files will be run - if any errors should occur, you will get a message asking you to Continue or abort, telling you what the problem is. Normally no such problems should occur. After performing any changes to the database, all Safran procedures and triggers are recompiled.

If the database already is upgraded to the latest version, the status message will display "Database already upgraded to <New version>". You will have check-boxes asking if you want to recompile procedures and/or triggers. By checking one or both of these, and pressing the "Upgrade"-button, re compilation will be performed.

Database ObjectsUsing Safran Project System Administration you can browse through different types of database objects; Tables with their definitions, Database views and their definitions, view database triggers and the procedures stored in the database and check their source, and invoke a set of database utilities.

From the main menu choose "Tools", then "Database Objects". This will open the Database Object Window:

All the lists and definitions are display only.



Look at Database Tables with DefinitionsFrom the database objects window, select "Tables" in the left pane. This places a list of all defined tables in the right pane. If you expand the "Tables"-entry in the left pane, all the tables will be listed under this entry. Selecting one of those gives you the list of column and column types in the right pane.

NOTE:A detailed table and column definition together with a database model can be found in the Safran Project System guide.

Look at Database Views and their DefinitionsFrom the database objects window, select "Views" in the left pane. This places a list of all defined Views in the right pane. If you expand the "Views"-entry in the left pane, all of the views will be listed under this entry. Selecting one of those gives you the view definition in the right pane.

Look at Database TriggersFrom the database objects window, select "Triggers" in the left pane. This places a list of all defined triggers in the right pane. If you expand the "Triggers"-entry in the left pane, these will be listed under this entry. Selecting one of those gives you the trigger definition (source) in the right pane.

Look at Database ProceduresFrom the database objects window, select "Procedures" in the left pane. This places a list of all stored procedures in the right pane. If you expand the "Procedures"-entry in the left pane, all the procedures will be listed under this entry. Selecting one of those gives you the procedure definition (the source code) in the right pane.

Database UtilitiesThe database utilities of the database objects option allows you to

• Execute SQL queries

• Run SQL command files and scripts

• Upgrade your Safran Project database

• Save database tables as OS-files

• Restore database tables from OS-files

• See all current Safran Project users (Sybase SQL-Server only)

• Update Database Statistics (Sybase SQL-Server only)


27

Execute SQL QueriesFrom the "Utilities" section of the "Database Objects" window, double-click the "SQL Queries" - icon. You will then be presented with a window for entering SQL commands.

You can open a multi line edit window by double clicking in the single line database queries window. You can use this window to write more complex SQL statements. From this window you may also save your SQL statements to file for later re-usage. This window also allows you to open and run SQL queries previously saved to file.

NOTE:Be aware that commands entered in this window will be executed and committed immediately, and there are no "Oops…" options. If you delete something here, it stays deleted. So, be careful what you ask for, cause you just might get that!

If you enter any query with "Select <column-list> from <single table> where <…>" - syntax, you will get the result-set presented in a window. The systems checks to see if there is a unique key/index on the table, and - if so - makes the result set updateable, marking key/index columns red to indicate their being part of the update-key.

Please refer to the Exploring Safran Project book for a detailed description of this utility. This book also contains a list of SQL commands.



Run a SQL Command-FileFrom the "Utilities" section of the "Database Objects" window, double-click the "SQL Queries" - icon. This action will open the "Run SQL Command File" window.

In this window you are supposed to enter a SQL-Command file name. You may either enter the file name directly into the edit, or use the "Browse" button to open the standard "Find File…" window.

You must also inform the system whether each command should be committed after execution (default), or all commits shall be done after execution of the document. (Sybase SQL-server requires commit after each command for all commands that may include table creation.) You must also specify the command delimiter used in the command file, default is ";".

To execute the command file, press the "Run"-button. The system then executes the commands within the file, informing you of any (non-fatal) errors occurring during execution, and giving you the options to continue or abort if errors occur. When the operations are successfully completed, the window gives you a message telling you the number of lines in the file.


29

Save Database Tables as OS-filesFrom the "Utilities" section of the "Database Objects" window, double-click the "Backup to Files" - icon. You should now see the "Export tables" - Window,

with a list of the database tables, and the option to tick off the tables you want to backup. You need to specify the path where the backup files should be saved (keeping in mind that if you back up some of the larger tables, you may need quite a lot of space). You can enter the path directly in the edit box, or use "Browse" to select the correct directory. After that you select the table(s) that shall be backed up, and press "Save" to back up.

Restore Database Tables from OS-filesFrom the "Utilities" section of the "Database Objects" window, double-click the "Restore from Files" - icon. You should now see the "Restore tables" - Window, initially empty.

You need to specify the path where the backup files were saved. You can enter the path directly in the edit box, or use "Browse" to select the correct directory. After having entered the path, a list of the tables that was backed up will appear in the table-list. You may now tick off the tables you wish to restore, and press the "Restore"-button to perform the restore.

NOTE:The restore function does not perform any overwrites, or checking of prior existence - it just restores the table as it was when backed up. If not all data is deleted from the table prior to restoring data, the restore action may cause SQL-



errors such as duplication of unique column values. If you perform a restore of the activity table, you may need to check (and update) the sequence_log table for the correct values in the "next_id" columns.

See all current Safran Project users (Sybase, SQL-Server only) From the "Utilities" section of the "Database Objects" window, double-click the "Logged in users" - icon. This action opens up a window looking like this (sorry, not many logged in here…)


31

If you suspect that any Safran Project user hangs, and that this may be caused by another process, you may select the "Show Blocked Processes Only"-option. This sets a filter on the users-list, showing only users that currently are waiting for a database lock to be released. To identify the blocker, note the number under "Blocked by", and repush the button (now renamed to "Show All Processes"). If the blocker is a Safran Project user, you can find him as a Process ID (If there are many users, pushing the "Process ID" header will sort the list on Process ID). If the blocking process ID is not on the list, it does not belong to a Safran Project user.

Update Database Statistics (Sybase, SQL-Server only) From the "Utilities" section of the "Database Objects" window, double-click the "Update Statistics" - icon. This brings up this window:

Sybase SQL-server keeps track of the index configuration and the table layout, as well as the "spread" of the index keys, in system tables. These are used to optimize database queries. When a lot of changes and/or insertions/deletes have been done on a database table, the information stored in these tables becomes incorrect. As a result of this, wrong indexes may be selected for data retrieval, and performance drops. The tables initially selected, are the ones who most commonly affect report performance etc. You may switch selection on and off for each individual table. When you have checked off the ones whose statistics you want to update, you press "OK", and the update statistics process starts. This process may take some time.



Maintain Database Profiles To ease switching between Safran Project database, login information may be kept in a "Database Profile". Creation and maintenance of these profiles are done from the system administration tool, by choosing "Tools", from the main menu, then "Database Profiles". This action opens the window for profile maintenance:

The outermost level in the left pane holds the DBMS's, and may be exploded to show each profile registered for this DBMS. When a DBMS is selected, a list of profiles - with a "new profile"-option on top - is shown in the right pane. When a profile is selected, details regarding the selected profile are shown on the right. The profile infor-mation consists of a name, the Database Management System (DBMS), the server name (not relevant for Sybase SQL Anywhere), database name (not relevant for Oracle Systems) and connection arguments (Db-Param), which may vary.


33

Browse Safran System Objects From the main menu choose "Tools", then "Object Browser.

This initiates the object browser, which starts of with a tree view giving you the list of the Safran system object types: Projects, Networks, Calendar Sets, Profile sets, Userfield Sets, Resource Sets, Symbol Sets and Rule Sets. By expanding one of these system types (clicking the "+" - sign, or pressing "->" with the type selected), you get to see the list of objects of this type kept in the database.

Using the Object Browser you can

• Add new objects

• Delete objects

• Grant / revoke access to objects

• Update and modify information related to the selected type of object

The System object browser is a tab separated window , where the first tab presents details about the object, the second tab keeps the object access, and the third (and for some objects also the fourth) tab holds object type specific information.

For details on each specific object, see the Safran Project User Guide, as the objects in this browser is identical to the objects under Safran Project's Setup menu.

Creating a New ObjectTo create a new system object from within the object browser, you must either have the corresponding type selected, or an object of the type selected, with the "Details" tab in front. You then select "New" from the "Edit" menu, (or press the "New" icon, or Press Ctrl + "N"). A new object is created, an ID for the object is generated, and the object gets the name "<New - ID>".

The creation of a new object is automatically saved to the database, and closing the object browser without saving, does not revoke this action.



Delete an Existing ObjectTo delete a system object from within the object browser, you must have the object to be deleted selected, with the "Details" tab in front. You then select "Delete" from the "Edit" menu, (or press the "Delete" icon, or Press Ctrl + "D"). The system then checks whether deletion is allowed (you cannot delete a calendar being used by a network etc.), and prompts for confirmation. If confirmation is given, the object is deleted. It is also at the same time deleted from the database, and closing the object browser without saving does not revoke this action.

Grant / Revoke Access to an ObjectThe "Access" tab of the object browser is in itself a tab type object with two tabs: "User Access" and "Group Access". These two pages work in an identical manner: You have two lists: one holding the users (groups) with access to the object, one holding users (groups) without access. To grant access to a user (group) not currently having any, you can either select the user (group) and press "New", or "drag" the user (group) from the list of users (groups) not having access, and "drop" her on the list of users (groups) having access. After having done this, You can select access level from the drop down of levels. Revoking access work likewise: Press "Delete" with the user (group) whose privilege shall be revoked selected, or perform the reverse "Drag & Drop" - action.

Granting and revoking access must be "Saved" to be committed to the database.

Maintain Reports, Filter Groups and PicturesThe Tools> Report Maintenance options contains 4 sub options: Report Browser, Report Groups, Filter Groups and Pictures.


35

The Report Browser.

This browser has two views: By User, and by Report type. In the user view, the "highest level" is the users. Exploding the user level brings up a list of the report type where this user has defined reports. Exploding the report type level leads to the report definition saved by this user of this type, listed.

In the Report Type view, the "highest level" is the report type (Barchart, Progress Summary etc.). Exploding this level brings up the users having saved reports of this type, and by exploding this level again, you can bring up the reports of this type, saved by the selected user.

You may delete out-of-date or redundant report definitions from this browser, as long as they are not part of a report package (see Safran Project User Guide for an expla-nation of Report Packages). All maintenance of report packages takes place within Safran Project.

By selecting a single report definition in the left pane, you can see details about how this report definition is saved.

NOTE:You can NOT update report definitions from here.

Report GroupsTo ease report selection in large organizations where users may be part of very different project organization, with varying report needs, reports may be added to groups. When finding a specific pre-defined report not saved by yourself, instead of searching through all reports saved by other users (most of which may be irrelevant to your needs), you may now search only within your group.



The report group feature is also used to manage reports available and executable through Safran Web Access Client. These reports are added to the group SWA.

To maintain report groups you select "Tools" from the main menu, then "Report Maintenance" and "Report Groups". The Report Groups Window looks like this:

The left pane shows the report groups listed in a three view, the center part list reports in the selected group displaying report type, saved by and report name. At the right all available reports are listed in a three view by report type. To add a new report specifi-cation to your group select the report in the right list window and drag it across to your report group in the left most window.

From this window you may:

• Add an new Report Group

• Delete en existing Report Group

• Save all changes

• Refresh, annul all changes

• Add reports to selected Groups

• Remove reports from a Report Group


37

Filter GroupsThe Filter Group option allows you to create groups of already defined filters. Filters that can be to select activities by discipline, area, project phase and more. The filter group feature is currently used to allow Safran Web Access to select Safran data by pre defined filters.

The filter group window is split into 3 sections. At the left the are the defined filter groups with the named filters displayed in a three view. The center sections shows the filter definition, and at the right are available filters listed by user/creator. You can select an available filter in the right most part and drag it across to your filter group to add it to the group. Drag it across in the opposite direction to remove it from the group.

PicturesPictures or logos that you want to use in the report headers or as back ground pictures for Editor layouts and histogram/S-Curves can be saved sa picture blobs to the safran database. This enables you to have a set of defined standard logos to be used by several users.The logo “database” can be update both by using the SAfran Project Client and



the Sys. adm client. Using Logos or pictures from the database enables all users of a report specification to have their report printed with logo, whether he or she is using a Safran Project Client or a Web Access Client and accessing other users reports.

The Picture database Manager (Tools>Report Maintenance>Pictures) displays thumb-nails of all pictures or logos saved to the safran database. You can use this window to add new Pictures, To delete, to Protect a picture and to display a full resolution of a selectyed picture or logo. If you protect a Picture it can not be deleted from the database by any user.


23

C H A P T E R

SETTING UP THE ENTERPRISE FIELDS AND CODES.

Typically, activities within a project share codes and values so that the planner or project manager can group and select data and information across these codes. You are likely to find both organizational and work break down structures, like department, Project phase, sub phases, work packages, document packages procurement packages and more.

Likewise many organizations and firms code their project at project level to be able to distinguish project of different type, from different regions etc and also to be able to roll up information from separate projects into portfolios and summarize data to higher level. For example you may want to summarize Live projects or you may want to summarize projects in Bid phase, or projects across geographical regions.

With Safran you can define Enterprise Fields and Codes to be shared across your projects. Ideally, one person or group is responsible for controlling and setting up the enterprise fields. The coordinator works with the project managers to develop and define these standards. Once defined for the Safran Project database, they are shared across all projects saved to this database.

User fields are defined at project level and assigned at activity level. The Enterprise Fields are defined at database level and assigned at project level.

Setting up the Enterprise FieldsTo create or modify the Enterprise fields choose the Tools>Enterprise Fields option.

Safran lets you add enterprise fields of these types; Flag, text or string, date time and Reference. The Enterprise reference field is in its form identical to the project reference field in that it contains a “label” together with predefined codes, description and sort field.


CHAPTER 724Setting up the Enterprise Fields and Codes.

All Enterprise fields are defined by a field type, field number and a label. Even though Safran Project supports unlimited numbers of enterprise fields, most corporations are likely to have a somewhat limited number of field and codes.

Once defined, you can use these codes across all projects saved to this Safran Project database. Enterprise fields can also be used for sorting, selecting, summarizing and grouping information across projects, and adds a valuable capability to Safran Project and to users of Safran Web Access logged into and accessing the Safran Project database.

The Open Network window lets you organize and group your networks according to enterprise values. The enterprise fields and codes are also displayed in the main section of the screen.


25

Importing/Exporting Enterprise Fields and Codesprimarily targeting organizations that have deployed Safran Project with multiple databases and import/export functions is associated with the Setup of Enterprise Field and codes. This can of course also be used to import these codes from other system assuming they are provided in the correct format.

You can import codes only to a defined field or definitions and code.Like ways you can export codes only or definitions and codes. Data exported will be in txt format. Make sure that data to be imported are in the same format.


CHAPTER 726Setting up the Enterprise Fields and Codes.


27

C H A P T E R

SETTING NETWORK DEFAULTS

Many firms and organizations use standard corporate definitions for calendars, user fields, resource definitions, resource profiles and symbols.

To support and strengthen the corporate set-up, Safran Project support a network default definition.

Network DefaultsChoose the Tools>Network defaults option to open the defaults set-up window. Here you can select the network “configuration” to be used as default for all new networks to this database. It saves the users time when defining new networks and it ensures that corporate standards are used. However when you create a new network in Safran Project, you can select other sets and overwrite these standards.


CHAPTER 828Setting Network Defaults


25

CHAPTER 0INDEX

AAccess 12, 14, 34

Exclusive 13Read 12Test 12Update 12

Add User 16, 18Add user 18

BBackup to Files 29

Cchange database 13Create User group 18Creating a new object 33Current SP users 30

DDatabase Objects 25Database Procedures 26Database Profile 32Database Tables 26Database Triggers 26Database Utilities 26Database Views 26Delete 13Delete a group 19Delete an existing object 34Deleting a user 17

EEnterprise Codes 23Enterprise Fields 23

field types 23Exclusive 13

Export tables 29Extended security 20

FFilter Groups 34, 37

IInitiate 23Initiating a new database 23

LLogin 12, 20

NNetwork Defaults 23Normal 20

OObject

Access 34Creating 33Deleting 34

Object Ownership 19OS-files 29Ownership 19

PPictures 34, 37Public 12

RRead 12Remove group membership 18Report Browser 34Report Groups 34, 35Reports 34

26

Restore database tables from OS-files 29Restrict access 21Restricted Windows 21Run a SQL Command-File 28

SSafran Project Users 11Save database tables 29SQL Queries 27Starting 11System Objects 33

TTest 12Transferring 19Transferring ownership 19

UUpdate 12Update Database Statistics 31Upgrade Database 23Upgrade database 24User 18User Group

Add user 18User groups 12

Create 18Users

Add 16Deleting 17

WWindows 14Windows access 21

Documents

Using Safran Project System Administrationdownload.safran.no/Download/Doc/37/SA37.pdfThe Safran Project System Administrator, Sysadm or SA for short, is an application tool to help