Contents


Project Reporter Quick Start

Introduction to Project Reporter
         What is Project Reporter?
         Who should use Project Reporter?
         How Project Reporter works
         Hardware and software requirements
         Security guidelines
         Licensing model
         What's new in this version
         Upgrading from previous versions of Project Reporter

Installing Project Reporter
         Stand-alone installation (Windows only)
         Installing with Apache Tomcat
         Installing with JRun (3.0 or later)
         Installing with Caucho Resin
         Installing with BEA WebLogic
         Configuring Linux/Unix installations to display the Gantt chart properly
         Installing JDBC drivers for database access
         Configuring multiple instances of Project Reporter

Configuring and customizing Project Reporter
         Publishing reports to other users
         Providing direct access to individual project reports
         Using custom fields
         Working with subprojects and resource pools
         Putting hypertext links in data fields
         Adding your logo to Project Reporter pages

Administering Project Reporter
         Managing data sources and projects
                 Directory data sources
                 ODBC data sources
                 JDBC data sources
                 The default data source
                 Updating project data
                 Creating an ODBC Data Source Name (DSN)
         Managing groups
         Managing users
         Managing roles
         Managing views
                 Configuring natural language descriptions
                 Configuring the Gantt chart display
         Managing preferences
         License information
         Client statistics
         Report pages

Viewing reports in Project Reporter
         Logging in to Project Reporter
         Using the Home page
         Viewing summaries and item descriptions
         Changing the zoom level of the Gantt chart
         Sorting and filtering reports
         Working with Views
         Using report options
         Working with task links
         Terms and definitions used by Project Reporter
         Printing reports

Supported project data formats
         Microsoft Project .MPP files
                 Supported fields
         Microsoft Project 2000/2002 database format
                 Supported fields
         Microsoft Project 98 database format
                 Supported fields
         Project Reporter PRX export format
                 Using the PRX export macro with Microsoft Project 98 or 2000/2002
                 Supported fields
         Scitor PS7/PS8 files
                 Using the PS7/PS8 export scenario
                 Supported fields
         MPX files
                 Using MPX files from non-English software
                 Supported fields
         Summary of supported fields by data format
                 Project fields
                 Task fields
                 Resource fields
                 Assignment fields

Support/Troubleshooting

About Project Reporter

Contents
Project Reporter Quick Start

If you are installing Project Reporter for the first time, you can follow these steps to get up and running quickly.

If you are installing on Windows, and you do NOT already have a servlet-capable web server installed (e.g. Apache Tomcat, Macromedia JRun):

  1. If you are installing over a previous Beta version of Project Reporter 3, you must uninstall the previous version first. If you are updating a non-Beta version of Project Reporter 3, you do not need to uninstall the previous version, but you should use the .war file installer to perform the update.

  2. Download and run the stand-alone Windows installer for Project Reporter, which includes a version of the Apache Tomcat server.

  3. If you did not choose to install the Project Reporter server as a Windows NT service, start the server using the shortcut installed in your Start menu. A command window will appear; you can minimize this window, but do not close it, unless you want to stop the server.

  4. Open your web browser, and point it to the URL http://localhost:8080/projectreporter/prservlet to access Project Reporter's Login page.

  5. Log in to Project Reporter by clicking on the Enter as Guest button.

  6. You will be prompted to enter the serial number that you received when you downloaded or purchased Project Reporter. You must enter a valid serial number before proceeding.

  7. After entering a serial number, you will be redirected to the Projects page in the administration interface, where you can load a sample project.

  8. Once you have loaded one or more projects, you can return to the Home page, where you can view various types of reports on the sample projects.

  9. You can now use the administration page to customize Project Reporter for your organization, by:
    • Loading your own projects, from data sources that you create;
    • Customizing the built-in roles and views;
    • Creating groups to control which users can see which projects;
    • Adjusting the preferences to change how project data is displayed.

If you are installing on a non-Windows platform:

  1. If you have not already done so, install a web server that supports Java Servlets, such as Apache Tomcat. (Tomcat can be downloaded free from jakarta.apache.org; it requires the Java 2 JDK, version 1.2 or later.

  2. To enable the generation of images for the Gantt chart display, you must configure the Java runtime options for your server to set the java.awt.headless property to true. For Apache Tomcat 4.1 on Linux, you can do this by adding the following line to the /etc/tomcat4/tomcat4.conf file:

    JAVA_OPTS="-Djava.awt.headers=true"

  3. Install Project Reporter by copying the projectreporter.war installer file to the webapps directory of your web server — for example, C:\Program Files\Apache Group\Tomcat 4.1\webapps.

  4. Wait a minute or so for the web server to automatically expand the .war file (some servers may require you to restart the server in order to initiate this expansion, or to expand the file manually).

  5. Proceed with Step 3 above.

See also
         Publishing reports to other users
         Administering Project Reporter

Contents
Introduction to Project Reporter

 

Contents
         What is Project Reporter?
         Who should use Project Reporter?
         How Project Reporter works
         Hardware and software requirements
         Security guidelines
         Licensing model
         What's new in this version
         Upgrading from previous versions of Project Reporter

Contents : Introduction to Project Reporter
What is Project Reporter?

"Instant web-based status reports, in plain English"

Project Reporter makes it easy to put your project schedules on the web, and view project information using automatically generated natural language reports.

Natural language text makes project information instantly and intuitively accessible, and since it's automatically generated, it's always up to date. There's nothing you need to write, and no special annotations of your project data are required.

Easy to use and administer

Project Reporter is designed for ease of use, both by project administrators and end users. Natural language-based reports make it easy for users to find the information they need — the meaning and significance of different data elements is explained in understandable terms, and hyperlinks in the text let users perform operations such as filtering in a completely intuitive manner.

Administration of Project Reporter is also simple and intuitive — by customizing the built-in roles and views, you can provide exactly the right kind of information to a range of users, from executives to team members.

Broad platform support

Project Reporter is designed to support a wide variety of client and server platforms. It supports several project data formats, from MPX files to enterprise-class databases — including Microsoft Project versions 98 to 2002, and Scitor Project Scheduler.

The Project Reporter server can be run on any Java-compatible platform, including Linux, and both Netscape and Internet Explorer browsers are supported (with no Java applets or ActiveX controls).

Contents : Introduction to Project Reporter
Who should use Project Reporter?

Project Reporter is not meant to be an all-purpose project management tool — rather, it is designed to allow you to easily and effectively disseminate project information to project stakeholders.

Stakeholders in a project may include the following:

Generally speaking, the further stakeholders are in the organizational structure from the core project team, the more interested they will be in the ease of access that Project Reporter provides to project information. Project managers will typically require software such as Microsoft Project for analytical functions (for example, resource levelling), and team members may require other software for reporting actual effort; but people in these roles can also benefit from Project Reporter's enhanced presentation of the state of the project.

Project Reporter is appropriate for organizations who wish to publish project information to a variety of types of users, both easily and inexpensively. Its web-based implementation makes it much more cost-effective than placing general-purpose project management software on every stakeholder's desktop.

Contents : Introduction to Project Reporter
How Project Reporter works

Project Reporter runs as a plug-in to a web server, allowing anyone with a compatible web browser to view the generated reports. Project Reporter requires a web server that supports Java Servlets, such as the Apache Tomcat server. Tomcat or similar servers can be used as stand-alone web servers in environments (such as a typical office intranet) without special security requirements. If stronger security is required (such as on extranets or the Internet), Tomcat and other servers can be configured to use SSL (Secure Sockets Layer), or to run in conjunction with the most popular third-party web servers, such as Microsoft Internet Information Services (IIS).

Project Reporter includes a web-based administration interface, which lets the project manager load multiple projects and manage user accounts and groups. Different report views can be created for different user roles, and virtually every detail of a view is configurable to control who sees what information.

To publish a project using Project Reporter, all the project manager needs to do is save it in one of the project file or database formats supported by Project Reporter, in a location accessible to the computer running the Project Reporter server. No special text or annotations are required in project files — Project Reporter generates status reports completely automatically. Once a new project has been loaded using the administration interface, it will be reloaded automatically every time the file or database is updated, and an up-to-date status report will be available instantly.

Contents : Introduction to Project Reporter
Hardware and software requirements

In order to run Project Reporter effectively, your computer should meet the following requirements.

Server requirements:

Recommended minimum hardware configuration:

Project Reporter requires version 1.2 or later of the Java Development Kit (JDK) from Sun Microsystems, available for download from http://java.sun.com/j2se/. Java virtual machines developed by Microsoft are not supported.

Project Reporter includes a customized version of the Apache Tomcat web server, but it can also be installed with other servers that support the Java Servlet specification, such as:

For environments requiring more advanced security provisions (such as restricting access from the Internet), many of these servers can be configured to use SSL (Secure Sockets Layer), or can be integrated with third-party web servers such as Microsoft Internet Information Services (IIS).

Clients require one of the following web browsers:

Other browsers may work, but have not been tested.

See also
         Supported project data formats

Contents : Introduction to Project Reporter
Security guidelines

Project Reporter allows you to create user accounts and passwords to control access to project information. However, these security features are designed more for convenience and ease of use than for impenetrability. The user account mechanism is designed to facilitate use of the same account by multiple users (provided that the licensing requirements are met), and passwords are transmitted in unencrypted form. Therefore, it is possible for a knowledgeable and determined user to gain access to project information that s/he would not normally be able to see.

If you wish to provide more robust security for reports generated by Project Reporter, you should configure it to work with one of the supported third-party web servers, which have more advanced support for user authentication and request filtering. You can also make use of supplementary security tools such as network firewalls and directory permissions.

Sample scenarios

Here are some examples of how you might configure Project Reporter for different user environments:

Environment Requirements Security
Simple intranet
  • All project information can be shown to anyone on intranet
  • Intranet is behind a firewall, or not connected to Internet
No special configuration required — use a stand-alone web server such as Apache Tomcat, and let all users enter as Guest (each user still requires a separate client license)
Restricted intranet
  • Project information can only be shown to people involved with project, and some users should not see cost information
  • Intranet is behind a firewall, or not connected to Internet
Use the stand-alone web server, but disable the Guest account and create separate report views with and without cost information included. Create separate individual or shared user accounts for users who should or should not have access to cost information, and assign the views appropriately to these accounts. Optionally, set operating-system permissions on directories used as data sources by Project Reporter, to prevent unauthorized direct access to project files via a shared file system.
Restricted extranet/Internet
  • Reports need to be accessed by people in branch offices or other outside sites
  • Outside users are on extranet or Internet
Use the stand-alone web server if you have a closed extranet, or configure a server such as Apache Tomcat with a third-party web server or SSL to restrict outside access to certain domains or users.
Unrestricted Internet
  • Reports are accessible to anyone visiting your public web site
Use the stand-alone web server and/or a third-party web server or SSL, and create a link from your home page which logs all users in as Guest (requires unlimited-client license).

See also
         Administering Project Reporter

Contents : Introduction to Project Reporter
Licensing model

Project Reporter is priced based on the number of client computers that can contact the server in order to view reports.

Each computer contacting the server counts as a separate client. A single client computer can be used by any number of users, with any number of login IDs, under the same client license. However, if the same user logs in from different client computers, or if the same login ID is used by different users from different client computers, a client license must be purchased for each client computer.

If a client license for a given client computer is not used for one month, it can be transferred to another client computer. Client computers are tracked using TCP/IP host names or numbers. As of Version 3.0, Project Reporter tracks clients with the aid of browser cookies, so that computers whose IP addresses change from time to time because of dynamic address protocols like DHCP (for example, when using a dial-up or VPN connection) are not counted multiple times.

Project Reporter provides a client statistics page, as part of the administration interface, which displays a list of the client computers that have contacted the server in the past month. This page can be used by system or project administrators to ensure compliance with the license terms.

See also
         Client statistics

Contents : Introduction to Project Reporter
What's new in this version

We are continually working to add new features to Project Reporter. Here are the latest improvements.

Users of previous versions of Project Reporter should consult the topic on Upgrading from previous versions of Project Reporter for more details on how various features have changed.

Version 3.03

Version 3.02

Version 3.01

Version 3.0

Contents : Introduction to Project Reporter
Upgrading from previous versions of Project Reporter

Users of versions of Project Reporter prior to Version 3.0 should note the following tips:

Contents
Installing Project Reporter

Project Reporter can be installed in different configurations, depending on your security requirements. Project Reporter requires a web server that supports Java Servlets (as of Version 3.0, Project Reporter no longer includes the JRun Servlet Engine). For users who do not already have a servlet-capable web server, we recommend the free Apache Tomcat server. Servers such as Tomcat can be used stand-alone in environments (such as a typical office intranet) without special security requirements. If stronger security is required (such as on extranets or the Internet), most of them can be configured to use SSL (Secure Sockets Layer), or to run in conjunction with the most popular third-party web servers, such as Microsoft Internet Information Services (IIS).

The following topics describe how to install Project Reporter in different configurations. For more information about which configuration is most appropriate for your environment, see Security guidelines.

Contents
         Stand-alone installation (Windows only)
         Installing with Apache Tomcat
         Installing with JRun (3.0 or later)
         Installing with Caucho Resin
         Installing with BEA WebLogic
         Configuring Linux/Unix installations to display the Gantt chart properly
         Installing JDBC drivers for database access
         Configuring multiple instances of Project Reporter

Contents : Installing Project Reporter
Stand-alone installation (Windows only)

If you do not already have a web server that supports Java Servlets (such as Apache Tomcat, Macromedia JRun, or IBM WebSphere), you can use the stand-alone installer for Project Reporter, which includes a modified version of the Apache Tomcat server. This installer is only available for Windows platforms.

The modified version of Tomcat in the stand-alone version is not configured to support the full range of Tomcat's functionality, such as:

If you wish to use these functions, you should install a full version of Apache Tomcat (or another servlet container), and follow the appropriate instructions to install Project Reporter with that server.

For detailed instructions on getting started after installation, see Project Reporter Quick Start.

Contents : Installing Project Reporter
Installing with Apache Tomcat

To install Project Reporter with the Apache Tomcat web server (Version 4.0 or later), perform the following steps: Note: If you wish to install the Project Reporter .war file without needing to restart the Tomcat server, you can also use Tomcat's manager application, by entering a URL similar to the following in your browser:

http://localhost:8080/manager/install?path=/projectreporter&war=file:/c/projectreporter.war

This requires the manager application to be enabled — see the Tomcat documentation for details.

See also
         Project Reporter Quick Start
         Configuring Linux/Unix installations to display the Gantt chart properly

Contents : Installing Project Reporter
Installing with JRun (3.0 or later)

To install Project Reporter with Macromedia JRun, version 3.0 or later, perform the following steps:

Note: Project Reporter no longer supports JRun 2.2, which was included with previous versions of Project Reporter.

See also
         Configuring multiple instances of Project Reporter
         Configuring Linux/Unix installations to display the Gantt chart properly

Contents : Installing Project Reporter
Installing with Caucho Resin

To install Project Reporter with Caucho Resin, perform the following steps:

See also
         Configuring Linux/Unix installations to display the Gantt chart properly

Contents : Installing Project Reporter
Installing with BEA WebLogic

To install Project Reporter with the BEA WebLogic server, perform the following steps:

See also
         Configuring Linux/Unix installations to display the Gantt chart properly

Contents : Installing Project Reporter
Configuring Linux/Unix installations to display the Gantt chart properly

If you are installing the Project Reporter server on Linux or another Unix platform, you may experience problems with the display of the Gantt chart in reports generated by Project Reporter. If the Gantt bar images fail to appear correctly, the following procedure will correct the problem.

In order to enable the generation of images for the Gantt chart display on Unix platforms, you must configure the Java runtime options for your server to set the java.awt.headless property to true. For Apache Tomcat 4.1 on Linux, you can do this by adding the following line to the /etc/tomcat4/tomcat4.conf file:

JAVA_OPTS="-Djava.awt.headers=true"

You should restart the server after changing this setting.

If you are using another web server, consult its documentation for information on how to configure runtime parameters for the Java virtual machine.

Contents : Installing Project Reporter
Installing JDBC drivers for database access

If you want Project Reporter to load project data from a database such as Oracle or SQL Server, you may wish to install a JDBC driver for this purpose. JDBC drivers can be used for better performance and reliability than ODBC on Windows platforms, or when the Project Reporter server is running on a non-Windows platform where ODBC is not supported.

The first step in installing a JDBC driver is to obtain the class files for the driver, and place them in the appropriate directory on the server where Project Reporter is running, relative to the directory containing the class files for the Project Reporter servlet. If you are using the Apache Tomcat server, which is included with some versions of Project Reporter, you can place the driver class files in expanded form in the WEB-INF/classes directory for the projectreporter web application, or in .jar form in the WEB-INF/lib directory.

Once you have put the driver class files in the correct location, you should restart the server and create a data source in Project Reporter to test the connection. For this step you will need information specific to your database installation, such as the name of the database host, the correct port number, a login ID and password, etc.

If the data source you create does not function properly, Project Reporter should display an error message that will help you diagnose the problem. The most common problems are that Project Reporter cannot access the driver classes (ClassNotFoundError), or that JDBC URL string, login ID, or password are not correct.

Contents : Installing Project Reporter
Configuring multiple instances of Project Reporter

It is possible to configure multiple instances of the Project Reporter servlet to run on the same web server or servlet engine. This allows you to specify a different configuration directory for each instance, so that all settings and administration functions (including data sources, user accounts, groups, report views, etc.) are managed separately for each instance.

Note: In order to use multiple instances of the Project Reporter servlet on the same server, you must obtain a separate license and serial number for each instance, and monitor the client statistics for that instance according to the license terms.

To create multiple instances of Project Reporter on the same server, perform the following steps (these instructions are also included in the web.xml file contained in the projectreporter.war archive):

  1. Install one instance according to the default instructions appropriate for your server.

  2. Create a copy of the resulting expanded directory — for example, copy C:\Program Files\Apache Tomcat 4.0\webapps\projectreporter to ...webapps\projectreporter2.

  3. In the copied directory, edit the web.xml file, and change the value of the webAppName parameter to match the name of the copied directory (e.g. projectreporter2).

  4. To access the new instance, use a URL of the form: http://localhost:8080/projectreporter2/prservlet (you may need to restart the server first).
Note that any changes you make from this point on to the copied instance will not be reflected in the original instance, and vice versa.

Contents
Configuring and customizing Project Reporter

Besides letting you manage projects, users, and groups, Project Reporter's administration interface gives you a wide variety of configuration options to control the appearance and content of generated reports. This section describes these options in greater detail.

Contents
         Publishing reports to other users
         Providing direct access to individual project reports
         Using custom fields
         Working with subprojects and resource pools
         Putting hypertext links in data fields
         Adding your logo to Project Reporter pages

Contents : Configuring and customizing Project Reporter
Publishing reports to other users

Once you have installed Project Reporter and verified that it is working correctly, you will want to make its location available to other users so that they can view reports. There are two main ways to do this:
  1. Notify other users of the URL (web-server address) of the login or entry page, so that they can enter this location in their web browsers;
  2. Create a link to Project Reporter on another web page, for example on your company's intranet.
You can also point users directly to Project Reporter's Home page rather than to the Login page, if this meets your security requirements.

Because the default URL for Project Reporter is fairly complex, the second method listed above is recommended (note that the web page that points to Project Reporter does not have to be located on the same web server as Project Reporter). If you use the first method, you should encourage users to bookmark the location of the login page, for convenience.

The actual URL that should be used to access Project Reporter will depend on how it is installed. For a default stand-alone installation with the Apache Tomcat server, the URL would be of the form:

http://myhost.mydomain.com:8080/projectreporter/prservlet

In some network configurations, it may be more convenient to use the host name without the domain name (i.e., substituting simply myhost for myhost.mydomain.com). This may avoid problems with firewalls, for example.

If you wish to send all users directly to the Home page (using the Guest account, which must be enabled), you should add the extension NoLogin to the URL, for example:

http://myhost.mydomain.com:8080/projectreporter/prservlet/NoLogin

Note: When creating a link to Project Reporter or directing users to a URL for it, it is important that you use a location such as those shown above, so that option settings can be tracked correctly; if users jump directly to other pages within Project Reporter's user interface, for example using bookmarks, there can be unexpected results.

For more details on the URLs used to access Project Reporter in different configurations, see Installing Project Reporter.

See also
         Providing direct access to individual project reports

Contents : Configuring and customizing Project Reporter
Providing direct access to individual project reports

If you wish, you can allow Project Reporter users to access individual project reports directly, without having to log in and use the Home page to select a report.

To enable this behavior, you must have the Guest account enabled. Note that this may reduce the overall security of your Project Reporter installation — this configuration is most appropriate for a relatively secure environment, such as a corporate intranet.

To make a project report directly available via a hyperlink on another web page, perform the following steps:

  1. Use the Projects page in the administration interface to load the project.
  2. Once the project has been loaded, the name of the project file displayed on the Projects page should become a hyperlink — if it does not, check to make sure that the Guest account is not disabled.
  3. Click on the hyperlink to open a new browser window, which displays the report for the project.
  4. Copy the URL displayed in the report window, and paste it into the HTML document that you wish to link to the report (using the appropriate <a> ... </a> syntax for an HTML link).
  5. Test the HTML page you are linking from, to ensure that the link works correctly.
  6. If you later unload the project (for example, if it becomes obsolete), remember to update the links in the other HTML page.

Contents : Configuring and customizing Project Reporter
Using custom fields

As of Version 3.0, Project Reporter no longer supports using different aliases for a custom field (Text1, Flag1, etc.) in different projects — it assumes that if you use custom fields, you give them the same label in all projects.

When editing Views in Project Reporter's administration interface, you can specify aliases for any custom fields displayed in views (as well as non-custom fields); but the same alias will be displayed for all projects.

Note: If you wish to use project-level custom fields, you should note the following tips:

Contents : Configuring and customizing Project Reporter
Working with subprojects and resource pools

As of Version 3.0, Project Reporter no longer requires any special naming conventions when saving resource pool projects, master projects, or subprojects. In previous versions, these conventions were used to provide hyperlinks between reports on related projects, as well as to determine how work and cost figures were recalculated in resource pool projects.

Project Reporter treats a project as a resource pool if it has no tasks (other than the root project summary task), and does not apply the Show resource work/cost for current project only option to resource pool projects. This means that resource work and cost figures for a resource pool project will reflect each resource's assignments in all projects that use the resource pool.

Note: Because of this convention, if you wish to be able to view summary work and cost information for resources in a resource pool, you should make sure that your resource pool projects do not contain any tasks. If they do, they will be treated as regular projects, and resource work and cost figures will be recalculated to reflect only assignments in the current project (unless you turn the Show resource work/cost for current project only option off).

Contents : Configuring and customizing Project Reporter
Putting hypertext links in data fields

Project Reporter lets you create links from project reports to other web documents, by entering hypertext URLs in various fields in your projects. For example, if you entered the URL http://www.cogentex.com/products/reporter within the Notes for a task, Project Reporter would automatically detect the presence of this URL, and use it to create a link to the Project Reporter home page in the generated report. This is similar to the way Microsoft Project recognizes URLs in Notes fields.

Hypertext links can be entered anywhere within the following fields:

Note: You should not enter any HTML tags in custom text fields or Notes fields. For example, you cannot create a hyperlink within a custom text field by entering this HTML code:

<a href='www.google.com'> Google </a>

Contents : Configuring and customizing Project Reporter
Adding your logo to Project Reporter pages

You can customize Project Reporter to display your corporate logo on the Login and Home pages, by simply replacing a GIF file in the installation directory.

To add your logo, follow these steps:

  1. Prepare a GIF image of your logo. The recommended size is between 30 and 50 pixels high, and up to 120 pixels wide. If the logo does not fill the entire image rectangle, you should either save it with a transparent background, or set the background color to white.
  2. Locate the empty placeholder GIF file in the html/images directory. In a default Windows installation with the Apache Tomcat server, the full path of this file is C:\Program Files\Apache Group\Tomcat 4.1\webapps\projectreporter\html\images.
  3. Rename the empty placeholder file, or move it to another directory. You should not simply delete it, in case you wish to remove your logo later — if this file is missing, you will see missing-image symbols in your browser when viewing Project Reporter.
  4. Copy your logo file into this directory, and rename it as custom-logo.gif. It will now be displayed by Project Reporter, in place of the empty placeholder image.
  5. If you later wish to remove your logo from Project Reporter, restore the original placeholder image to this directory, with its original filename.

Contents
Administering Project Reporter

The following topics describe techniques for administering the Project Reporter server, including: All of these functions can be performed from any web browser, using Project Reporter's web-based administration interface.

The Administration page is accessed via a link at the bottom of the Home page, which is the first page you see after logging in to Project Reporter. Note: This link is only visible if you logged in with a user account that has administration permissions.

Contents
         Managing data sources and projects
         Managing groups
         Managing users
         Managing roles
         Managing views
         Managing preferences
         License information
         Client statistics
         Report pages

Contents : Administering Project Reporter
Managing data sources and projects

The Projects page in the Administration interface displays appropriate commands for each data source or project you have configured:

This page also displays any groups to which projects have been assigned, in order to control which users have access to them.

Note: Although projects are listed in the Projects frame according to the data sources they belong to, this listing is independent of the Groups feature. You can add any project to any group, regardless of which data source it comes from.

Contents
         Directory data sources
         ODBC data sources
         JDBC data sources
         The default data source
         Updating project data
         Creating an ODBC Data Source Name (DSN)
See also
         Managing groups

Contents : Administering Project Reporter : Managing data sources and projects
Directory data sources

You should use a directory data source if your projects are not saved in a database such as Oracle or SQL Server. The appropriate file format to use for project data depends on the platform where you have the Project Reporter server installed: Once you create a directory data source, any new project files placed there will appear in Project Reporter's administration interface, so that you can load them. Once a project has been loaded, if the project file is updated on the server, it will be reloaded automatically so that Project Reporter users will see the updated information.

Using UNC names for directory data sources

If the Project Reporter server is running under Microsoft Windows, you can use UNC names (e.g. \\MyServer\projects\mpd) to refer to directories for .MPP, .MPD, .PRX, or .MPX files; however, this may cause problems in some cases when loading projects, due to the slower speed of file operations over the network. If the data source directory is on the same computer as the Project Reporter server, you should refer to it using a conventional path (e.g. c:\projects\mpd).

See also
         Microsoft Project .MPP files
         Microsoft Project 2000/2002 database format
         Microsoft Project 98 database format
         Scitor PS7/PS8 files
         Project Reporter PRX export format
         MPX files

Contents : Administering Project Reporter : Managing data sources and projects
ODBC data sources

You should use an ODBC data source if your projects are saved in a database such as Oracle or SQL Server, and the Project Reporter server is running on a Windows computer. You should also use an ODBC data source if you have multiple projects stored in the same .MPD or .MDB file (both of these file types use the Microsoft Access database format).

To create an ODBC data source in Project Reporter, enter the name of an ODBC Data Source Name (DSN) that you have previously configured using the Windows ODBC control panel. The ODBC DSN must be configured on the same computer that is running the Project Reporter server, but can refer to an MPD file or database on another computer on the network. It must be a "System" data source, so that it will be accessible at all times when the computer is running.

ODBC DSNs can only be used when the Project Reporter server is running on a Windows platform. They can be used for Oracle or SQL Server databases containing projects saved from Microsoft Project 98 or Project 2000/2002 (Project Reporter supports the same versions of these database servers that Microsoft Project does).

Note: As of Version 3.0, Project Reporter can load individual .MPD files directly, without requiring you to create an ODBC DSN, as long as each .MPD file contains only one project. However, you can still load individual .MPD files using an ODBC DSN if you wish.

After entering the name of the ODBC DSN, you will be given the option of entering a login name and password for access to the corresponding database. Note: Since this information is not stored in encrypted form by Project Reporter, in some cases you may wish to configure your database server with a new login name and password (with the appropriate read permissions for opening a read-only project in Microsoft Project 98 or Project 2000/2002), that will only be used by Project Reporter to access project information.

Contents : Administering Project Reporter : Managing data sources and projects
JDBC data sources

You should use a JDBC data source if your projects are saved in a database such as Oracle, Microsoft Access, or SQL Server, and the Project Reporter server is running on a non-Windows platform, such as Linux.

To create a data source using a third-party JDBC database driver that you have previously configured, enter the driver class name and URL string (you may need to consult your database administrator for this information). For example, when using Oracle's JDBC driver, for "JDBC driver class name" you would enter:

oracle.jdbc.driver.OracleDriver

and for "JDBC URL string" you would enter:

jdbc:oracle:thin:@mydbhost:1521:orcl

where mydbhost is the name of the host running the Oracle server.

JDBC drivers can be used for better performance and reliability than ODBC on Windows platforms, or when the Project Reporter server is running on a non-Windows platform.

See also
         Installing JDBC drivers for database access

Contents : Administering Project Reporter : Managing data sources and projects
The default data source

When you first install Project Reporter, it is preconfigured with a single directory data source, which contains sample project files.

Once you have configured Project Reporter to load your own project files or databases, you may wish to remove this data source.

Contents : Administering Project Reporter : Managing data sources and projects
Updating project data

After you load a project for the first time using Project Reporter's administration interface, the project will automatically be reloaded each time the project data changes.

The Project Reporter server scans the loaded projects and data sources every 30 seconds, checking for new, deleted, or updated projects, and takes the following actions:

When an updated project is reloaded, users viewing a report on the project will see a notice that they should reload the report pages to see the latest information.

Contents : Administering Project Reporter : Managing data sources and projects
Creating an ODBC Data Source Name (DSN)

Note: As of Version 3.0 of Project Reporter, this procedure is no longer required for loading projects stored in the MPD format (as long as there is only one project per file) — you can load MPD files directly, the same way you would load MPX or PRX files. The same applies to Scitor PS7/PS8 projects saved in .MDB files.

Creating an ODBC Data Source Name for an Oracle or SQL Server database

In order to use Project Reporter with project data stored in an Oracle or SQL Server database, you must first create an ODBC Data Source Name (DSN) on the computer running the Project Reporter server, unless you have already created one for other purposes. The following procedure assumes that you are running the Project Reporter server under Windows 95, 98, 2000, NT, or XP.

Note: Before creating an ODBC data source for an Oracle database, you must install the Oracle client software on the computer where you are creating the data source. Also, when creating a data source, you should select the "Microsoft ODBC for Oracle" driver instead of the "Oracle ODBC Driver".

  1. On the computer running the Project Reporter server, open the ODBC Data Sources applet in the Control Panel.
  2. Select the System DSN tab, and check to see if a data source has already been configured for your database. If a data source already exists, you may wish to skip the remaining steps and use it.
  3. Click the Add... button, which opens the Create New Data Source window. In this window, select the appropriate driver, and click the Finish button.
  4. In the following dialogs, enter the appropriate settings for your database, consulting a system administrator if necessary. During this process, you will be given an opportunity to make a test connection to the database.
  5. When you have finished configuring the new data source, its name should appear in the list of System data sources.
After creating the ODBC DSN, you need to create a link to it in Project Reporter, using the Add Data Source link on the Projects page in the administration interface.

Creating an ODBC Data Source Name for an .MPD file or .MDB file for PS7/PS8

If you are creating a DSN for an .MPD file containing multiple projects, use the above procedure, but with the following changes:

Contents : Administering Project Reporter
Managing groups

In order to control which projects are accessible to which user accounts in Project Reporter, you can use the Groups function. The following rules apply to groups: These rules mean that if you do not create any groups, all users will be able to view all reports (although you can still restrict which information particular users can see in a given report). If you do create groups, you may find these tips useful:

Note: Although projects are grouped on the Projects page according to the data sources they belong to, this grouping is independent of the Groups feature. You can add any project to any group, regardless of which data source it comes from.

Contents : Administering Project Reporter
Managing users

Project Reporter has two built-in user accounts, admin and guest, which initially have blank passwords and administrator permissions, and which belong to the Power User role, giving access to all of default views and report types. If you wish to use Project Reporter in an open environment, in which anyone who has access to the server can perform administrative tasks and view all project information, you do not need to do anything — each user can simply log in using the "Enter as guest" button. You can also have users access the Home page directly using the NoLogin URL extension, as described in Publishing reports to other users (note that this option requires the guest account to be enabled, although in some cases you may wish to remove its administrator permissions).

If you want to restrict who can perform administrative tasks (administering either projects or user accounts) or who can view certain project information, you must change the permissions of the built-in user accounts, and create new accounts with the appropriate roles. You may also wish to create new roles, and/or modify the default views. You should start by assigning a non-trivial password to the admin account, and either assigning a password to or disabling the guest account.

Note: Although Project Reporter does not display passwords in web pages, URLs, or configuration files, it does transmit them to the server in clear text — therefore, the basic log-in mechanism should not be relied upon for security beyond a group of relatively trusted users, such as a corporate intranet. For more information, see the security guidelines.

In some cases, you may find it useful to create user accounts that can be used by several people at the same time (although you must still comply with the licensing requirements regarding the total number of users). For example, if you want to make project information available to clients outside your organization, but do not want to create a separate user account for each person who might view the information, you could create a client account, and communicate the password to your clients. Project Reporter uses log-in names to maintain separate session information for each user, but this is also relative to the user's internet address, so that different users with the same log-in name will not interfere with each other's settings, as long as they are viewing the reports from different computers.

You can use the Client Statistics page to monitor use of Project Reporter, and ensure compliance with the licensing model.

In order to control which project reports a given user account will have access to, you can assign it to one or more groups.

See also
         Managing groups
         Client statistics
         Licensing model
         Publishing reports to other users
         Managing roles

Contents : Administering Project Reporter
Managing roles

Project Reporter lets you use roles to control which users see which project information. When you install Project Reporter, several roles are defined by default, which you can assign to any new user accounts that you create. You can also edit these roles to customize them, or create new roles from scratch.

Each role is defined by the report pages that it allows access to, and for each page, the views that are accessible within that page. So, for example, you might give executives access only to the Project Portfolio page, and include cost-related views in that page. For a project team member, you might give access only to the My Tasks page, and not display any cost-related views.

When managing roles and views, you should note the following tips:

See also
         Managing views
         Report pages

Contents : Administering Project Reporter
Managing views

Project Reporter lets you use views to control the content of generated reports. Each view defines a list of fields to be displayed in report tables, and also affects the content of the Gantt chart and textual descriptions.

Adding fields to views

On the Views page in the administration interface, you can use the Edit command to configure an individual view. You can add or remove fields (except for the built-in fields that are displayed at the top of the field list), and specify an alias for any field — this is particularly useful for custom fields (Task1, Flag1, etc.).

Contents
         Configuring natural language descriptions
         Configuring the Gantt chart display

Contents : Administering Project Reporter : Managing views
Configuring natural language descriptions

You can configure the natural language descriptions generated by Project Reporter by simply adding or deleting fields from individual views, since the descriptions automatically reflect the fields included in a given view.

There are two basic types of natural language description, both of which can be configured by changing the fields displayed in views:

Individual item descriptions reflect the fields included in a view, except for custom fields. For example, if you add the Cost Variance field to a view containing other cost-related fields, item descriptions for this view will reflect this — if the Cost Variance for a task is $100.00, part of the description of that task might say:

The cost for this task is $900 ($100 over the baseline amount).

If individual users do not want to view natural language descriptions at all for individual items, an option for this is available on the report options page.

For summary descriptions, including certain fields in a view will cause Project Reporter to display a breakdown based on the field, including hyperlinks that can be used to filter the list of items in the Gantt chart. For example, including the Cost Variance field in a view will result in summary descriptions like this:

28 of these tasks are over budget, 10 are on budget, and 16 are under budget.

Clicking on the links in this summary will apply different filters — for example, the over budget link filters the tasks to those with Cost Variance greater than zero.

The table below shows the fields that can be used to generate breakdowns in this fashion, along with a sample summary text for each:

Completion Status As of the current date, one of these tasks is unstarted, and two are finished.
Cost Variance With respect to cost, one of these tasks is over budget, and two are on budget.
Work Variance With respect to work, one of these tasks is over budget, and two are on budget.
Duration Variance With respect to duration, one of these tasks is over planned duration, and two are on planned duration.
Start Variance With respect to start date, one of these tasks is behind schedule, and two are on schedule.
Finish Variance With respect to finish date, one of these tasks is behind schedule, and two are on schedule.
CV With respect to Earned Value Cost Variance (CV), one of these tasks is over budget, and two are on budget.
SV With respect to Earned Value Schedule Variance (SV), one of these tasks is over budget, and two are on budget.
Free Slack / Total Slack With respect to free and total slack, one of these tasks has both free and total slack, and two have only total slack.
Leveling Delay With respect to delay due to resource leveling, one of these tasks has some delay, and two have no delay.

Contents : Administering Project Reporter : Managing views
Configuring the Gantt chart display

You can configure certain aspects of the Gantt chart display in Project Reporter by adding the appropriate fields to views, as follows:

Contents : Administering Project Reporter
Managing preferences

The Preferences page in the administration interface lets you set options for the display of various types of information in Project Reporter.

Note that these are global options, which govern all projects displayed in Project Reporter. Several of the options, such as those for currency and date formats, will override any corresponding settings in .MPD or other project files that are loaded.

These options include:

Contents : Administering Project Reporter
License information

The License Info page, which is accessed from the Administration page, displays the terms of your current Project Reporter license, as encoded in the serial number which you received when you downloaded or purchased the product. The serial number determines the expiry date of the license (if any), what version of Project Reporter you are entitled to use, and how many clients are allowed to access the server.

Note: If you do not have a valid serial number, you can access Project Reporter's Home page and administration interface, but you will not be able to view reports.

The Edit link on the License Info page takes you to a form where you can enter your name and organization, as well as a serial number. When entering a serial number, type all characters and hyphens exactly as they are written. Note that serial numbers may contain the numbers "1" or "0", but they do not contain the letters "l" or "o".

See also
         Licensing model

Contents : Administering Project Reporter
Client statistics

The Client Statistics portion of the License Info page displays a list of the client computers that have contacted the Project Reporter server in the last month. You can use this page to help you decide how to allocate server resources, as well as to ensure conformance with the terms of your license agreement.

The list of clients can be sorted on different fields by clicking on the table headings. The information displayed is updated and saved to a file each time a user logs in to Project Reporter, and is reloaded automatically when the server is restarted.

Note: As of Version 3.0, Project Reporter tracks clients with the aid of browser cookies, so that computers whose IP addresses change from time to time because of dynamic address protocols like DHCP (for example, when using a dial-up or VPN connection) are not counted multiple times.

See also
         Licensing model

Contents : Administering Project Reporter
Report pages

Project Reporter's reporting interface contains four different report pages, each of which displays a different type of report. You can enable or disable each report page for different roles, to control which users can view a given report type. You can also assign different views to each report page for a given role; the type of views (Project, Task, Resource or Assignment) you can use for each page depends on the report type.

The four report pages are:

Contents
Viewing reports in Project Reporter

This section describes Project Reporter's report interface, and tells you how to perform operations such as zooming, sorting, and filtering the Gantt chart, as well as printing.

Contents
         Logging in to Project Reporter
         Using the Home page
         Viewing summaries and item descriptions
         Changing the zoom level of the Gantt chart
         Sorting and filtering reports
         Working with Views
         Using report options
         Working with task links
         Terms and definitions used by Project Reporter
         Printing reports

Contents : Viewing reports in Project Reporter
Logging in to Project Reporter

The Log In page is the first page you see when you contact the Project Reporter server using your web browser, unless the server has been set up to not require logins. In order to view Project Reporter's Home page, you must either enter a user ID and password and click on the Log In button, or click on the "Enter as guest" button (depending on how Project Reporter is set up, the "Enter as guest" button may or may not be visible).

Project Reporter has two default user accounts, admin and guest, which initially have blank passwords (logging in as guest is the same as using the "Enter as guest" button). These accounts can be configured by disabling them, changing their passwords, or changing their administrator permissions.

After logging in, you will see the Home page.

Contents : Viewing reports in Project Reporter
Using the Home page

The Home page is your starting point for viewing reports in Project Reporter. Users with administrative rights can also use it to access the administration interface.

Depending on the permissions that have been set up for your user account, you can view one or more of the following report types:

Contents : Viewing reports in Project Reporter
Viewing summaries and item descriptions

Reports generated by Project Reporter let you view two types of information: A summary description is displayed when you first visit the report page, and when you change the current view or filter. Summary descriptions contain hyperlinks that you can use to apply filters, as in the following example: Selecting any of these links will apply the appropriate filter to the Gantt chart, and update the summary description to reflect the added filter. You can repeat this process to apply multiple filters.

To view a description of an individual item, select its icon in the Gantt chart, or click on its Gantt bar.

When viewing an individual item description, you can click on one of the links at the top of the description frame to return to a summary description. For example, if you have filtered a list of tasks to show only those in progress, you will see the following heading:

You can click on the In Progress link to return to a summary of the in-progress tasks, or the Project Tasks link to return to a summary of all the tasks.

Contents : Viewing reports in Project Reporter
Changing the zoom level of the Gantt chart

You can change the zoom level of the Gantt bars by clicking on the icon at the top of the Gantt chart.

There are four different zoom levels, which correspond to approximately one-eighth, one-quarter, one-third, and one-half of the screen width at a resolution of 1024 x 768 pixels. The default zoom level is the one quarter-screen setting.

Contents : Viewing reports in Project Reporter
Sorting and filtering reports

When viewing reports generated by Project Reporter, you can sort the items in the Gantt chart based on any field shown, and apply built-in or custom filters.

To sort the items in the Gantt chart based on a certain field (column), click on the field name in the column header. You can click again in the same column header to reverse the sort order.

You can apply a filter to the Gantt chart either by using hyperlinks in the textual description (see Viewing summaries and item descriptions), or by selecting the Filter option in the upper frame of the report window, and specifying the field and operator for the filter.

To remove a filter, use the links at the top of the description frame — for example, if you have filtered a list of tasks to show only those in progress, you will see the following heading:

You can click on the Project Tasks link to return to a summary of all the tasks.

Contents : Viewing reports in Project Reporter
Working with Views

When viewing a report generated by Project Reporter, you can switch views, in order to see different fields for the projects, tasks, resources, or assignments listed in the reports.

The fields in the current view determine what is shown in the Gantt chart and the table portion of item descriptions (displayed in the bottom frame), but also the content of the textual descriptions.

To change the current view, select a view from the drop-down list in the upper frame in your browser window. The number of views available for a given report type depends on how the administrator has configured Project Reporter.

Contents : Viewing reports in Project Reporter
Using report options

Project Reporter lets you set options that control the format of textual descriptions displayed in the lower frame. You can choose whether to display natural language (textual) descriptions, either at the summary level or for individual items. You can also set preferences for the terminology used to describe Earned Value fields (for example, BCWS vs. budgeted cost of work scheduled).

To set these options, select the Options link in the upper frame in your browser window, while viewing a report.

Contents : Viewing reports in Project Reporter
Working with task links

Whenever you see the name of a task in the text generated by Project Reporter, it will be a hypertext link, which looks something like this: Task #7.

This is actually two hypertext links, so you'll need to be careful where you click:

Although the task name in the heading of each task description is not a hypertext link, the yellow icon beside it is — you can use this link to highlight the task whose description you're reading again in the Gantt chart, after you've looked at other tasks in the Gantt chart and perhaps forgotten where you started.

Contents : Viewing reports in Project Reporter
Terms and definitions used by Project Reporter

This topic defines some of the terms used in the textual descriptions generated by Project Reporter.

Completion status

This refers to the status of a project, task, or milestone, with reference to the current project schedule. The possible values for a task or project are:

For a milestone, the possible values are: Note: Project Reporter assumes that milestones have zero duration and cost.

Earned value fields (BCWP, BCWS, ACWP, CV, SV, BAC, EAC, VAC, CPI, SPI, TCPI)

These fields are commonly used as metrics to evaluate the cost and schedule performance of a task or project. They stand for the following terms:

CV, SV, CPI, SPI, VAC, EAC, and TCPI are defined as follows: Note: Project Reporter uses the first definition of the CV field shown above (as do Microsoft Project 98 and Project 2000/2002), and recalculates CV where necessary. Project Reporter also calculates the TCPI field using the formula shown, in formats prior to Microsoft Project 2002 where it is not defined directly. Task EAC is not recalculated for formats prior to Microsoft Project 2002; in those formats it is taken to be the same as Cost.

Project Reporter also displays the following fields, where applicable:

Contents : Viewing reports in Project Reporter
Printing reports

If you wish to print reports generated by Project Reporter, you can obtain good results in either Microsoft Internet Explorer (version 5 or later), Netscape Navigator (version 6 or later), or Mozilla (version 1 or later) by using the default Print command. This will display the three frames of the report interface on a single page, allowing you to include the textual summary of a list of items (possibly with a filter applied), or of an individual item. However, it may not display all items in the Gantt chart, depending on the size of the project.

In Netscape or Mozilla, you can also right-click in the Gantt chart frame and select This Frame | Open Frame in New Window, and print from the resulting window. This will show all items in the Gantt chart, using as many pages as necessary.

In most cases, printing will work better if you set the page orientation to Landscape.

Contents
Supported project data formats

Project Reporter can generate reports from a variety of project data formats, stored in either files or databases. The following topics describe the supported formats, as well as specific data fields and features supported in each format. Reading the appropriate documentation for the format you are using will help you to obtain the best results from Project Reporter.

Contents
         Microsoft Project .MPP files
         Microsoft Project 2000/2002 database format
         Microsoft Project 98 database format
         Project Reporter PRX export format
         Scitor PS7/PS8 files
         MPX files
         Summary of supported fields by data format

Contents : Supported project data formats
Microsoft Project .MPP files

As of Version 3.0, Project Reporter supports the Microsoft Project .MPP file format, as long as the Project Reporter server is running on a Windows platform.

Note: To load .MPP files, you must have Microsoft Project 2000 or 2002 (Standard or Professional) installed on the computer where the Project Reporter server is running. .MPP files cannot be loaded on platforms other than Windows.

Note: .MPP files from Microsoft Project 98 can only be loaded if you have Microsoft Project 2000 installed on the Project Reporter server, as Project 2002 does not support the Project 98 .MPP format. Aside from this limitation, .MPP files are cross-compatible between Project 2000 and Project 2002 — so, for example, you can load Project 2002 .MPP files even if you only have Project 2000 installed on the Project Reporter server.

Contents
         Supported fields

Contents : Supported project data formats : Microsoft Project .MPP files
Supported fields

The following table lists all of the fields supported by Project Reporter when using Microsoft Project .MPP files.

Note that Project Reporter does not support enterprise fields in Microsoft Project 2002. The following new fields in Project 2002 are supported:

The following new fields in Project 2002 are not supported (but are supported when using the Project 2002 database format):

Project Task Resource Assignment
Author
Comments
Company
Current Date
Finish Date
Keywords
Manager
Name
Start Date
Subject
Actual Cost
Actual Duration
Actual Finish
Actual Overtime Cost
Actual Overtime Work
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Duration
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Constraint Date
Constraint Type
Contact
Cost
Cost Variance
Cost1-10
CPI
Created
Critical
CV
Date1-10
Deadline
Duration
Duration Variance
Duration1-10
EAC
Early Finish
Early Start
Effort Driven
Estimated
External Task
Finish
Finish Variance
Finish1-10
Fixed Cost
Fixed Cost Accrual
Flag1-20
Free Slack
Hyperlink
ID
Late Finish
Late Start
Leveling Delay
Milestone
Name
Notes
Number1-20
Outline Level
Outline Number
Overallocated
Overtime Cost
Overtime Work
Percent Complete
Percent Work Complete
Predecessors
Priority
Project
Recurring Task
Regular Work
Remaining Cost
Remaining Duration
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Resume
SPI
Start
Start Variance
Start1-10
Stop
Subproject File
Successors
Summary
SV
TCPI
Text1-30
Total Slack
Type
Unique ID
VAC
WBS
Work
Work Variance
Accrue At
Actual Cost
Actual Overtime Cost
Actual Overtime Work
Actual Work
ACWP (= Actual Cost)
Available From
Available To
BAC (= Baseline Cost)
Baseline Cost
Baseline Work
BCWP
BCWS
Code
Cost
Cost Per Use
Cost Variance
Cost1-10
CPI
CV
Date1-10
Duration1-10
EAC
Email Address
Finish1-10
Flag1-20
Group
Hyperlink
ID
Initials
Material Label
Max Units
Name
Notes
Number1-20
Overallocated
Overtime Cost
Overtime Rate
Overtime Work
Peak
Percent Work Complete
Project
Regular Work
Remaining Cost
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Standard Rate
Start1-10
SPI
SV
Text1-30
Type
Unique ID
VAC
Work
Work Variance
Actual Cost
Actual Finish
Actual Overtime Cost
Actual Overtime Work
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Confirmed
Cost
Cost Variance
Cost1-10
CPI
Critical
CV
Date1-10
Delay
Duration1-10
EAC
Finish
Finish Variance
Finish1-10
Flag1-20
Hyperlink
Leveling Delay
Notes
Number1-20
Overallocated
Overtime Work
Percent Work Complete
Priority
Regular Work
Remaining Cost
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Resource Unique ID
SPI
Start
Start Variance
Start1-10
SV
Task Summary Name
Task Unique ID
Text1-30
Unique ID
Units
VAC
Work
Work Contour
Work Variance

Contents : Supported project data formats
Microsoft Project 2000/2002 database format

Project Reporter supports the Microsoft Project 2000/2002 database format, either in .MPD files or on database servers such as Microsoft SQL Server.

Note: Beginning with Version 3.0, Project Reporter can load .MPD files directly, without requiring you to create a Windows ODBC data source name (DSN) (unless you store multiple projects in the same .MPD file).

If you are storing your projects in a database such as Microsoft SQL Server, Microsoft Project 2000/2002 requires you to configure an ODBC data source name (DSN) in order to load or save projects. You can use this same DSN to create an ODBC data source in Project Reporter, if the DSN exists on the same computer where the Project Reporter server is running. If the Project Reporter server is running on another computer, you must create a DSN on that computer, pointing to the same database.

Contents
         Supported fields

Contents : Supported project data formats : Microsoft Project 2000/2002 database format
Supported fields

The following table lists all of the fields supported by Project Reporter when using the Microsoft Project 2000/2002 database format. The notation "2002" indicates fields that are only supported by Microsoft Project 2002.

Note that Project Reporter does not support enterprise fields in Microsoft Project 2002. The following new fields in Project 2002 are supported:

Project Task Resource Assignment
Author
Comments
Company
Current Date
Finish Date
Keywords
Manager
Name
Start Date
Subject
Actual Cost
Actual Duration
Actual Finish
Actual Overtime Cost
Actual Overtime Work
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Duration
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Constraint Date
Constraint Type
Contact
Cost
Cost Variance
Cost1-10
CPI
Created
Critical
CV
Date1-10
Deadline
Duration
Duration Variance
Duration1-10
EAC
Early Finish
Early Start
Earned Value Method (2002)
Effort Driven
Estimated
External Task
Finish
Finish Variance
Finish1-10
Fixed Cost
Fixed Cost Accrual
Flag1-20
Free Slack
Hyperlink
ID
Late Finish
Late Start
Leveling Delay
Milestone
Name
Notes
Number1-20
Outline Level
Outline Number
Overallocated
Overtime Cost
Overtime Work
Percent Complete
Percent Work Complete
Physical Percent Complete (2002)
Predecessors
Preleveled Finish
Preleveled Start
Priority
Recurring Task
Regular Work
Remaining Cost
Remaining Duration
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Resume
SPI
Start
Start Variance
Start1-10
Stop
Subproject File
Successors
Summary
SV
TCPI
Text1-30
Total Slack
Type
Unique ID
VAC
WBS
Work
Work Variance
Accrue At
Actual Cost
Actual Overtime Cost
Actual Overtime Work
Actual Work
ACWP (= Actual Cost)
Available From
Available To
BAC (= Baseline Cost)
Baseline Cost
Baseline Work
BCWP
BCWS
Code
Cost
Cost Per Use
Cost Variance
Cost1-10
CPI
CV
Date1-10
Duration1-10
EAC
Email Address
Finish1-10
Flag1-20
Generic (2002)
Group
Hyperlink
ID
Initials
Material Label
Max Units
Name
Notes
Number1-20
Overallocated
Overtime Cost
Overtime Rate
Overtime Work
Peak
Regular Work
Remaining Cost
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Standard Rate
Start1-10
SPI
SV
Text1-30
Type
Unique ID
VAC
Work
Work Variance
Actual Cost
Actual Finish
Actual Overtime Cost
Actual Overtime Work
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Confirmed
Cost
Cost Variance
Cost1-10
CPI
Critical
CV
Date1-10
Delay
Duration1-10
EAC
Finish
Finish Variance
Finish1-10
Flag1-20
Hyperlink
Leveling Delay
Notes
Number1-20
Overallocated
Overtime Work
Percent Work Complete
Priority
Regular Work
Remaining Cost
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Resource Unique ID
SPI
Start
Start Variance
Start1-10
SV
Task Summary Name
Task Unique ID
Text1-30
Unique ID
Units
VAC
Work
Work Contour
Work Variance

Contents : Supported project data formats
Microsoft Project 98 database format

Project Reporter supports the Microsoft Project 98 database format, either in .MPD files or on database servers such as Microsoft SQL Server.

Note: Beginning with Version 3.0, Project Reporter can load .MPD files directly, without requiring you to create a Windows ODBC data source name (DSN) (unless you store multiple projects in the same .MPD file).

If you are storing your projects in a database such as Microsoft SQL Server, Microsoft Project 98 requires you to configure an ODBC data source name (DSN) in order to load or save projects. You can use this same DSN to create an ODBC data source in Project Reporter, if the DSN exists on the same computer where the Project Reporter server is running. If the Project Reporter server is running on another computer, you must create a DSN on that computer, pointing to the same database.

Contents
         Supported fields

Contents : Supported project data formats : Microsoft Project 98 database format
Supported fields

The following table lists all of the fields supported by Project Reporter when using the Microsoft Project 98 database format.

Project Task Resource Assignment
Author
Comments
Company
Current Date
Finish Date
Keywords
Manager
Name
Start Date
Subject
Actual Cost
Actual Duration
Actual Finish
Actual Overtime Cost
Actual Overtime Work
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Duration
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Constraint Date
Constraint Type
Contact
Cost
Cost Variance
Cost1-10
CPI
Created
Critical
CV
Date1-10
Duration
Duration Variance
Duration1-10
EAC
Early Finish
Early Start
Effort Driven
External Task
Finish
Finish Variance
Finish1-10
Fixed Cost
Fixed Cost Accrual
Flag1-20
Free Slack
Hyperlink
ID
Late Finish
Late Start
Leveling Delay
Milestone
Name
Notes
Number1-20
Outline Level
Outline Number
Overallocated
Overtime Cost
Overtime Work
Percent Complete
Percent Work Complete
Predecessors
Preleveled Finish
Preleveled Start
Priority
Recurring Task
Regular Work
Remaining Cost
Remaining Duration
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Resume
SPI
Start
Start Variance
Start1-10
Stop
Subproject File
Successors
Summary
SV
TCPI
Text1-30
Total Slack
Type
Unique ID
VAC
WBS
Work
Work Variance
Accrue At
Actual Cost
Actual Overtime Cost
Actual Overtime Work
Actual Work
ACWP (= Actual Cost)
Available From
Available To
BAC (= Baseline Cost)
Baseline Cost
Baseline Work
BCWP
BCWS
Code
Cost
Cost Per Use
Cost Variance
Cost1-10
CPI
CV
Date1-10
Duration1-10
EAC
Email Address
Finish1-10
Flag1-20
Group
Hyperlink
ID
Initials
Max Units
Name
Notes
Number1-20
Overallocated
Overtime Cost
Overtime Rate
Overtime Work
Peak
Regular Work
Remaining Cost
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Standard Rate
Start1-10
SPI
SV
Text1-30
Unique ID
VAC
Work
Work Variance
Actual Cost
Actual Finish
Actual Overtime Cost
Actual Overtime Work
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Confirmed
Cost
Cost Variance
Cost1-10
CPI
Critical
CV
Date1-10
Delay
Duration1-10
EAC
Finish
Finish Variance
Finish1-10
Flag1-20
Hyperlink
Leveling Delay
Notes
Number1-20
Overallocated
Overtime Work
Percent Work Complete
Priority
Regular Work
Remaining Cost
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Resource Unique ID
SPI
Start
Start Variance
Start1-10
SV
Task Summary Name
Task Unique ID
Text1-30
Unique ID
Units
VAC
Work
Work Contour
Work Variance

Contents : Supported project data formats
Project Reporter PRX export format

Project Reporter includes an export macro for Microsoft Project that exports project data in a proprietary PRX (Project Reporter Export) format. This format is recommended for users who are running the Project Reporter server on a non-Windows platform such as Linux, and who do not store their projects on a database server such as Microsoft SQL Server.

Contents
         Using the PRX export macro with Microsoft Project 98 or 2000/2002
         Supported fields

Contents : Supported project data formats : Project Reporter PRX export format
Using the PRX export macro with Microsoft Project 98 or 2000/2002

The Project Reporter installation includes an export macro to create PRX files from either Microsoft Project 98 or Project 2000/2002. The macro automatically saves the current project as a PRX file in a designated directory, which should be set up as a data source directory for Project Reporter.

To install the macro, follow these steps:

  1. Open the macro file in Microsoft Project 98 or 2000/2002 (the file is located in the Project Reporter installation folder). If you see a warning dialog about the macros in this file, select "Enable macros".
  2. Select Organizer from the Tools menu, and click on the Modules tab in the Organizer dialog that appears. You will see lists of the macros and forms available in your global template on the left, and in the file you opened on the right. Select all of the items in the list on the right, and click "Copy" to place them in your global template. This will make the macro available in any project file you open.
  3. (Optional) Use the Tools | Customize | Toolbars menu command to create a custom toolbar button to run the export macro.

To run the export macro, use the custom toolbar button, or select Macro | Macros... from the Tools menu, then select "ExportToProjectReporter" and click "Run"). A dialog box will appear in which you can specify the name of the PRX file and a directory to export to. Click on the Export button to save the file.

Contents : Supported project data formats : Project Reporter PRX export format
Supported fields

The following table lists all of the fields supported by Project Reporter when using the PRX export format with Microsoft Project 98 or 2000/2002.

Project Task Resource Assignment
Author
Comments
Company
Current Date
Finish Date
Keywords
Manager
Name
Start Date
Subject
Actual Cost
Actual Duration
Actual Finish
Actual Overtime Cost
Actual Overtime Work
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Duration
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Constraint Date
Constraint Type
Contact
Cost
Cost Variance
Cost1-10
CPI
Created
Critical
CV
Date1-10
Deadline
Duration
Duration Variance
Duration1-10
EAC
Early Finish
Early Start
Earned Value Method (2002)
Effort Driven
Estimated
External Task
Finish
Finish Variance
Finish1-10
Fixed Cost
Fixed Cost Accrual
Flag1-20
Free Slack
Hyperlink
ID
Late Finish
Late Start
Leveling Delay
Milestone
Name
Notes
Number1-20
Outline Level
Outline Number
Overallocated
Overtime Cost
Overtime Work
Percent Complete
Percent Work Complete
Physical Percent Complete (2002)
Predecessors
Preleveled Finish
Preleveled Start
Priority
Project
Recurring Task
Regular Work
Remaining Cost
Remaining Duration
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Resume
SPI
Start
Start Variance
Start1-10
Stop
Subproject File
Successors
Summary
SV
TCPI
Text1-30
Total Slack
Type
Unique ID
VAC
WBS
Work
Work Variance
Accrue At
Actual Cost
Actual Overtime Cost
Actual Overtime Work
Actual Work
ACWP (= Actual Cost)
Available From
Available To
BAC (= Baseline Cost)
Baseline Cost
Baseline Work
BCWP
BCWS
Code
Cost
Cost Per Use
Cost Variance
Cost1-10
CPI
CV
Date1-10
Duration1-10
EAC
Email Address
Finish1-10
Flag1-20
Group
Hyperlink
ID
Initials
Material Label
Max Units
Name
Notes
Number1-20
Overallocated
Overtime Cost
Overtime Rate
Overtime Work
Peak
Percent Work Complete
Project
Regular Work
Remaining Cost
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Standard Rate
Start1-10
SPI
SV
Text1-30
Type
Unique ID
VAC
Work
Work Variance
Actual Cost
Actual Finish
Actual Overtime Cost
Actual Overtime Work
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Confirmed
Cost
Cost Variance
Cost1-10
CPI
Critical
CV
Date1-10
Delay
Duration1-10
EAC
Finish
Finish Variance
Finish1-10
Flag1-20
Hyperlink
Leveling Delay
Notes
Number1-20
Overallocated
Overtime Work
Percent Work Complete
Priority
Project
Regular Work
Remaining Cost
Remaining Ovt. Cost
Remaining Ovt. Work
Remaining Work
Resource Unique ID
SPI
Start
Start Variance
Start1-10
SV
Task Summary Name
Task Unique ID
Text1-30
Unique ID
Units
VAC
Work
Work Contour
Work Variance

Contents : Supported project data formats
Scitor PS7/PS8 files

Project Reporter includes an export scenario that can be used to load projects stored in Scitor PS7 or PS8 files. In order to use this scenario, you must load it into PS7/8, and configure an ODBC Data Source Name (DSN) to which to export your project data. You can then load projects from that DSN into Project Reporter. The DSN can refer to a Microsoft Access file, or any database for which you have an ODBC driver.

Note: although PS7/8 supports exporting MPX files, these are not recommended for use with Project Reporter, due to differences in the interpretation of certain fields. You should use the provided ODBC export scenario instead.

Contents
         Using the PS7/PS8 export scenario
         Supported fields

Contents : Supported project data formats : Scitor PS7/PS8 files
Using the PS7/PS8 export scenario

Installing and configuring the export scenario

Exporting a project

When you export a project for the first time, you need to load it using Project Reporter's administration interface. After that, Project Reporter will reload the project automatically each time you perform another export.

Contents : Supported project data formats : Scitor PS7/PS8 files
Supported fields

The following table lists all of the fields supported by Project Reporter when exporting projects from Scitor PS7 or PS8. Where PS7/PS8 field names do not correspond exactly to those used by Project Reporter, the supported PS7/PS8 fields are listed in parentheses.

Project Task Resource Assignment
Notes
As Of Date
Finish Date
Manager
Name
Start Date
Actual Cost
Elapsed Duration
Actual Finish
Actual Start
Actual Labor
ACWP (= Actual Cost)
Base Cost
Base Cost
Base Finish
Base Labor
BCWP
BCWS
Task Type
Total Cost
Cost Variance
CPI
Critical
CV
Date 1-2
Required Date
Duration
EAC
Early Finish
Early Start
External Task
Schedule Finish
Base 1-5 Finish
#
Late Finish
Late Start
Delay
Name
Notes
Outline Level
Outline Index
Percent Complete
Percent Work Complete
Predecessors
Priority
Remaining Cost
Remaining Duration
Remaining Labor
SPI
Schedule Start
Base 1-5 Start
Subproject File
Successors
Summary
SV
TCPI
Text 1-5
ID
VAC
WBS
Total Work
Work Variance
Cost
Cost Variance
CPI
EAC
Email Address
#
Availability
Name
Notes
Number 1-5
Overtime Cost
SPI
Type
ID
Actual Cost
Actual Labor
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Base Cost
Base Finish
Base Start
Base Labor
BCWP
BCWS
Total Cost
Cost Variance
Base 1-5 Cost
CPI
Critical
CV
Delay
EAC
Finish Date
Base 1-5 Finish
Number 1
Percent Work Complete
Priority
Remaining Cost
Remaining Labor
Resource Unique ID
SPI
Start Date
Base 1-5 Start
Schedule Variance
Task Summary Name
Task Unique ID
Text 1-2
ID
Total Units
VAC
Total Labor
Work Variance

Contents : Supported project data formats
MPX files

Project Reporter can load projects stored in the MPX (Microsoft Project Export) file format, which is supported by several project software packages.

Note: Because the MPX format supports only a limited range of project data, you should use this format only if you have no other choice. Users of Microsoft Project 98, in particular (the last version of Microsoft Project to support saving to MPX files) should use .MPP or .MPD files instead, or .PRX files if the Project Reporter server is running on a non-Windows platform.

Consult the following topics for details of the MPX features supported by Project Reporter.

Contents
         Using MPX files from non-English software
         Supported fields
See also
         Microsoft Project .MPP files
         Microsoft Project 2000/2002 database format
         Microsoft Project 98 database format

Contents : Supported project data formats : MPX files
Using MPX files from non-English software

If you are using a non-English version of Microsoft Project or other project management software, you may experience compatibility problems with your MPX files. The MPX format sometimes includes language-dependent words and phrases which are not recognized by Project Reporter.

Note: If you are using the English version of Microsoft Project or other compatible software, and simply using another language to enter the names of tasks and resources, your MPX files should be compatible with Project Reporter. It is only versions of the software whose user interface is in another language ("localized" versions) that may not be compatible.

Project Reporter currently supports the following versions of Microsoft Project:

Note: As of Version 3.0, Project Reporter only supports a global option for MPX language; the language cannot be set independently for individual MPX files, as in previous versions.

Note: If you are using a non-English version of Microsoft Project or other compatible software, or if you are using an English version with non-English system settings for date formats, you must use a numeric date format in your MPX files. The date format must specify months, days, and years as numbers, without names of days or months. For example, in a French-speaking environment the date format "15.3.99" would be supported, but the format "Lundi 15 Mars 1999" would not. The format "Lundi 15.3.99" will normally be supported, but may cause errors in some system configurations.

If you are using Microsoft Project, the date format used in MPX files is controlled by the Date Format option, accessible via the Tools | Options | View menu command (changing the date format settings in Microsoft Project's Export Table Definition dialog does not have any effect).

Contents : Supported project data formats : MPX files
Supported fields

Because MPX files can contain virtually any combination of task and resource fields, Project Reporter does not necessarily support all variants of the MPX format. The minimum set of fields required to generate meaningful reports in Project Reporter is as follows: If any of these required fields is missing in an MPX file, Project Reporter will display an error message when you attempt to load it.

If you are working with subprojects or or cross-project dependencies, you should also include the task fields Project, Subproject File, and Successors.

Following are some general guidelines on the MPX variants supported by Project Reporter:

The following table lists all of the fields supported by Project Reporter when using MPX files.

Project Task Resource Assignment
Author
Comments
Company
Current Date
Finish Date
Keywords
Manager
Name
Start Date
Subject
Actual Cost
Actual Duration
Actual Finish
Actual Start
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Duration
Baseline Finish
Baseline Start
Baseline Work
BCWP
BCWS
Constraint Date
Constraint Type
Contact
Cost
Cost Variance
Cost1-3
CPI
Created
Critical
CV
Duration
Duration Variance
Duration1-3
EAC
Early Finish
Early Start
Finish
Finish Variance
Finish1-5
Fixed Cost
Fixed
Flag1-10
Free Slack
ID
Late Finish
Late Start
Delay
Milestone
Name
Notes
Number1-5
Outline Level
Outline Number
Percent Complete
Percent Work Complete
Predecessors
Priority
Project
Recurring Task
Remaining Cost
Remaining Duration
Remaining Work
Resume
SPI
Start
Start Variance
Start1-5
Stop
Subproject File
Successors
Summary
SV
TCPI
Text1-10
Total Slack
Unique ID
VAC
WBS
Work
Work Variance
Accrue At
Actual Cost
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Work
Code
Cost
Cost Per Use
Cost Variance
EAC
Email Address
Group
ID
Initials
Max Units
Name
Notes
Overallocated
Overtime Rate
Overtime Work
Peak
Percent Work Complete
Regular Work
Remaining Cost
Remaining Work
Standard Rate
Text1-5
VAC
Work
Work Variance
Actual Cost
Actual Work
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost
Baseline Work
Cost
Cost Variance
Critical
Delay
EAC
Finish
Overtime Work
Percent Work Complete
Priority
Regular Work
Resource Unique ID
Start
Task Summary Name
ID
Units
VAC
Work
Work Variance

Contents : Supported project data formats
Summary of supported fields by data format

This section lists the project data fields supported by each project data format in Project Reporter, for comparison.

Note that some fields are supported only indirectly, in that they are used to generate reports and Gantt chart views, but are not available to be inserted in tables and filters — for example, the Summary and Predecessors fields for a task.

Contents
         Project fields
         Task fields
         Resource fields
         Assignment fields

Contents : Supported project data formats : Summary of supported fields by data format
Project fields

MPX MPD-98 MPD-2000/2002 MPP PRX PS7/PS8
Author  
Comments (Notes)
Company  
Current Date (As Of Date)
Finish Date
Keywords  
Manager
Name
Start Date
Subject  

Contents : Supported project data formats : Summary of supported fields by data format
Task fields

MPX MPD-98 MPD-2000/2002 MPP PRX PS7/PS8
Actual Cost
Actual Duration (Elapsed Duration)
Actual Finish
Actual Overtime Cost    
Actual Overtime Work    
Actual Start
Actual Work (Actual Labor)
ACWP (= Actual Cost)
BAC (= Baseline Cost) (Base Cost)
Baseline Cost (Base Cost)
Baseline Duration  
Baseline Finish (Base Finish)
Baseline Start  
Baseline Work (Base Labor)
BCWP
BCWS
Constraint Date  
Constraint Type (Task Type)
Contact  
Cost (Total Cost)
Cost Variance
Cost1-10 (Cost1-3)
 
CPI
Created  
Critical
CV
Date1-10   (Date 1-2)
Deadline     (Required Date)
Duration
Duration Variance  
Duration1-10 (Duration1-3)
 
EAC
Early Finish
Early Start
Earned Value Method     (2002 only)   (2002 only)  
Effort Driven    
Estimated      
External Task  
Finish (Schedule Finish)
Finish Variance  
Finish1-10 (Finish1-5)
(Base 1-5 Finish)
Fixed Cost  
Fixed Cost Accrual (Fixed)
 
Flag1-20 (Flag1-10)
 
Free Slack  
Hyperlink    
ID (#)
Late Finish
Late Start
Leveling Delay (Delay)
(Delay)
Milestone  
Name
Notes
Number1-20 (Number1-5)
 
Outline Level
Outline Number (Outline Index)
Overallocated    
Overtime Cost    
Overtime Work    
Percent Complete
Percent Work Complete
Physical Percent Complete     (2002 only)   (2002 only)  
Predecessors
Preleveled Finish      
Preleveled Start      
Priority
Project      
Recurring Task  
Regular Work    
Remaining Cost
Remaining Duration
Remaining Ovt. Cost    
Remaining Ovt. Work    
Remaining Work (Remaining Labor)
Resume  
SPI
Start (Schedule Start)
Start Variance  
Start1-10 (Start1-5)
(Base 1-5 Start)
Stop  
Subproject File
Successors
Summary
SV
TCPI
Text1-30 (Text1-10)
(Text 1-5)
Total Slack  
Type    
Unique ID (ID)
VAC
WBS
Work (Total Work)
Work Variance

Contents : Supported project data formats : Summary of supported fields by data format
Resource fields

MPX MPD-98 MPD-2000/2002 MPP PRX PS7/PS8
Accrue At  
Actual Cost  
Actual Overtime Cost    
Actual Overtime Work    
Actual Work  
ACWP (= Actual Cost)  
Available From    
Available To    
BAC (= Baseline Cost)  
Baseline Cost  
Baseline Work  
BCWP    
BCWS    
Code  
Cost
Cost Per Use  
Cost Variance
Cost1-10    
CPI  
CV    
Date1-10    
Duration1-10    
EAC
Email Address
Finish1-10    
Flag1-20    
Generic     (2002 only)      
Group  
Hyperlink    
ID (#)
Initials  
Material Label      
Max Units (Availability)
Name
Notes
Number1-20   (Number 1-5)
Overallocated  
Overtime Cost  
Overtime Rate  
Overtime Work  
Peak  
Percent Work Complete      
Project        
Regular Work  
Remaining Cost  
Remaining Ovt. Cost    
Remaining Ovt. Work    
Remaining Work  
Standard Rate  
Start1-10    
SPI  
SV    
Text1-30 (Text1-5)
 
Type    
Unique ID   (ID)
VAC  
Work  
Work Variance  

Contents : Supported project data formats : Summary of supported fields by data format
Assignment fields

MPX MPD-98 MPD-2000/2002 MPP PRX PS7/PS8
Actual Cost
Actual Finish    
Actual Overtime Cost    
Actual Overtime Work    
Actual Start    
Actual Work (Actual Labor)
ACWP (= Actual Cost)
BAC (= Baseline Cost)
Baseline Cost (Base Cost)
Baseline Finish   (Base Finish)
Baseline Start   (Base Start)
Baseline Work (Base Labor)
BCWP  
BCWS  
Confirmed    
Cost (Total Cost)
Cost Variance
Cost1-10   (Base 1-5 Cost)
CPI  
Critical
CV  
Date1-10    
Delay
Duration1-10    
EAC
Finish (Finish Date)
Finish Variance    
Finish1-10   (Base 1-5 Finish)
Flag1-20    
Hyperlink    
Leveling Delay    
Notes    
Number1-20   (Number 1)
Overallocated    
Overtime Work  
Percent Work Complete
Priority
Project          
Regular Work  
Remaining Cost  
Remaining Ovt. Cost    
Remaining Ovt. Work    
Remaining Work   (Remaining Labor)
Resource Unique ID
SPI  
Start (Start Date)
Start Variance    
Start1-10   (Base 1-5 Start)
SV   (Schedule Variance)
Task Summary Name
Task Unique ID  
Text1-30   (Text 1-2)
Unique ID (ID)
(ID)
Units (Total Units)
VAC
Work (Total Labor)
Work Contour    
Work Variance

Contents
Support/Troubleshooting

If you experience problems when using Project Reporter, please consult this documentation and the on-line FAQ (Frequently Asked Questions) before contacting technical support. The FAQ can be found on the Project Reporter support page at http://www.cogentex.com/products/reporter/support.shtml.

Note that some topics from previous versions of the FAQ have been merged into Project Reporter's main documentation package, which you are reading now.

Administering Project Reporter

Contents
         Administering Projects
         Adding a Data Source
         Setting data source properties
         Using groups
         Editing a group
         Managing User Accounts
         Editing user properties
         Using Roles
         Editing a role
         Managing views
         Editing a view
         Setting preferences
         Managing Licenses

Administering Projects

You can use this page to load projects, so that users will be able to view reports on them.

To load a project, you must set up a data source for it. When you first install Project Reporter, a default data source directory is created, containing sample project files. You can add your own project files to that directory, or you can add a new data source using the link at the bottom of the table.

If you have just added a project to a data source or directory but it is not yet visible on this page, click on the Scan for new projects link, or wait a minute and then refresh the page to see if Project Reporter has found it.

See also
         Managing data sources and projects
         Updating project data

Adding a Data Source

There are three types of data sources that Project Reporter can use.

Directory data sources

Use a directory data source if you are using Microsoft Project or other supported project management software, and you do not use SQL Server or Oracle to store your project data.

ODBC data sources

Use an ODBC data source if you use Oracle or Microsoft SQL Server to store your project data, and the Project Reporter server is running on a Windows computer.

JDBC data sources

Use a JDBC data source if you use Oracle or Microsoft SQL Server to store your project data, and the Project Reporter server is running on a non-Windows platform, or you wish to have better database performance.

See also
         Using UNC names for directory data sources
         ODBC data sources
         JDBC data sources

Setting data source properties

Select the Load new projects automatically option if you want Project Reporter to automatically load any new projects that appear in the directory or database (it will take minute or two for changes to be recognized). Projects that are deleted will also be unloaded automatically.

For an ODBC or JDBC data source, you must enter an appropriate login ID and password so that Project Reporter can access project data.

For a directory data source, you can set the default language for MPX files (you can ignore this option if you do not use MPX files).

See also
         ODBC data sources
         JDBC data sources
         Using MPX files from non-English software

Using groups

You can use Groups to control which users have access to which projects.

If you wish to restrict access to certain projects, you should create one or more groups, each containing one or more projects and a list of users who should have access to them.

If no groups are created, all users will be able to view all projects that are loaded.

See also
         Managing groups

Editing a group

To edit a group, simply select the checkboxes corresponding to the projects and users you wish to include in the group.

If you wish to delete a group, you can do so from the main Groups page.

See also
         Managing groups

Managing User Accounts

You can use this page to create and manage user accounts for Project Reporter.

A user account can be assigned to an individual, or shared by several people.

You can assign one or more roles to each user account, to control access to different views.

See also
         Managing users

Editing user properties

This page lets you set properties for a user account.

See also
         Managing users

Using Roles

Roles determine which types of reports a user can access, and which views are available within each report page.

Each role can be assigned to one or more user accounts.

See also
         Managing roles

Editing a role

This page lets you determine the views that are associated with a role. Each view is associated with a report page.

To add a view to a report page, select the view from the drop-down list in the Add View column, and click the Add button.

You can click on the up and down arrows to change the order of the views for a report page, or click on the x icon to delete a view.

See also
         Report pages

Managing views

You can use this page to create and manage views. A view is a list of fields that is displayed in the Gantt chart portion of the reports generated by Project Reporter.

Views can be defined for projects, tasks, resources, or assignments, and can be assigned to different roles to control who can see them. If you create a new view, remember to assign it to a role on the Roles page.

To create a new view, select the Add View link at the bottom of the table.

See also
         Managing views

Editing a view

This page lets you determine the fields that are shown in a view. Each view is associated with one or more roles.

To add a field to a view, select the field from the Add Field list, and click the Add button. If you wish, you can also specify an alias, to be displayed in place of the field name shown.

You can click on the up and down arrows to change the order of the fields for a view, or click on the x icon to delete a field.

If you wish to restrict a view to a certain subset of projects, tasks, resources, or assignments, you can specify one or more default filters for the view, by clicking on the Add Filter button.

Setting preferences

You can use this page to set display options for reports generated by Project Reporter.

Note that the settings of these options will override any corresponding settings in the project files or databases that you load in Project Reporter.

See also
         Managing preferences

Managing Licenses

You can use this page to enter your serial number for Project Reporter. Note that reports will not be available in Project Reporter unless a valid serial number is entered.

You can also monitor the number of users that have contacted the server in the past month, in order to ensure compliance with the terms of the license.

See also
         License information
         Licensing model
         Client statistics

Contents
About Project Reporter

Version 3.03

(c) 1998-2004 CoGenTex, Inc. All Rights Reserved.

Web site: www.cogentex.com/products/reporter

Support page: www.cogentex.com/products/reporter/support.shtml

Support e-mail:

Some distributions of Project Reporter include software developed by the Apache Software Foundation (http://www.apache.org/).