MPM Getting Started 3

Getting Started Version 3.2

Contents

About this Manual ...... 6 Contacting Technical Support ...... 8

1 Introduction to MPM ...... 11 1.1 MPM (Micro-Frame Program Manager) ...... 12 1.2 Backing Up MPM Files ...... 14

2 Installing MPM ...... 17 2.1 Introduction to Installing MPM ...... 18 2.2 Pervasive.SQL V9 Workgroup Engine (V9.5) ...... 22 2.3 Standalone Installation ...... 26 2.4 Administrator Installation ...... 34 2.5 Workstation Installation ...... 40 2.6 Database Engine Installation ...... 46 2.7 Pervasive System Analyzer ...... 52 2.8 Configuring MPM ...... 58

3 Using MPM ...... 61 3.1 Introduction to Using MPM ...... 62 3.2 Windows Features ...... 64 3.3 Logging In and Logging Out of MPM ...... 66 3.4 Running the User Logout Utility ...... 68 3.5 Using the Menu Manager ...... 70 3.6 The Open Dialog Box – Access to MPM Tasks ...... 72 3.7 Introduction to MPM Task Windows ...... 74 3.7.1 Navigating the Task Window ...... 76 3.7.2 Editing Data in the Task Window ...... 78 3.7.3 Changing the Display ...... 80 3.8 Setting MPM Options...... 82 3.9 Previewing Data ...... 86 3.10 Printing Data ...... 88 3.11 Multi-User Access & Record Locking ...... 90

4 Converting to MPM 3.2 ...... 93

4.1 Converting MPM 2.2, 3.0 and 3.1 Data to MPM 3.2 ...... 94 4.2 Converting the MPM System Files ...... 95 4.3 Converting Global and Project Files ...... 96

5 Data Warehouse ...... 99 5.1 Introduction to Data Warehouse ...... 100 5.1.1 Workflow Overview ...... 102 5.2 System Requirements ...... 104 5.3 Installation ...... 105 5.3.1 Server: Create the MPM32_DW Database and Tables .... 106 5.3.2 Server: Install the MPM Data Warehouse Controller ...... 110 5.3.3 Server: Configure the Data Warehouse Controller using the Controller.exe.Config File ...... 118 5.3.3.1 DriveInfo ...... 120 5.3.3.2 appSetting ...... 122 5.3.4 Server: Finalize the Data Warehouse Controller ...... 124 5.3.5 Client: Enable the Data Warehouse Scheduler in the MPM Project Maintenance Screen ...... 126 5.3.6 Uninstall Notes ...... 127 5.4 The Data Warehouse Scheduler ...... 128 5.5 The Data Warehouse Database ...... 132 5.6 Synchronization Tables ...... 133 5.7 Data Warehouse Troubleshooting ...... 134

Index ...... 136

About this Manual The Getting Started manual describes how to get started with MPM. The components include: Overview of MPM Installing MPM Using MPM MPM Documentation Set The Getting Started manual is part of a documentation set that includes: MPM Globals This manual describes how to set up and manage your Global

Sets in MPM, which are used in all your MPM projects. MPM Projects This manual describes how to set up and manage projects in MPM, define Work Breakdown Structures, establish baselines, track project milestones, replan projects, and report and analyze data. Standard Reports This manual describes reports available in MPM.

Modular Format This manual has been written using a modular format. Most topics are presented on two- facing pages in the manual. A topic begins in the upper left corner of the left page and ends in the lower right corner of the right page. Screen captures and other figures are always included on the two pages. In the rare instance when a topic extends past two pages, the symbol is displayed at the bottom of the right page. Topics may have subtopics, and these are also presented in a two-page module. There are a number of advantages to this format. All the information you need to understand a topic is presented on two facing pages. You do not have to flip back and forth through several pages. If you want to skip a topic, you simply turn the page. The next topic starts in the upper left corner.

Manual Conventions We believe the typographic conventions used in a manual should be self-explanatory. Below we note only those conventions that we feel you may not have seen before. Italics Italics are used for the titles of manuals, topics, and sub-topics when these are referenced within the text of the manual.

Ctrl+X This notation indicates that you should hold down the first key while pressing the second key.

File|Save The menu name and command names are separated by a vertical bar. You would read the example shown as “select the Save command under the File menu.” This symbol indicates that a topic continues for more than two pages. This does not happen often, but there are a few exceptions.

Terminology In a field as complex as project management, there are many technical terms used. Unfortunately, terms are not standard across all organizations and companies. To familiarize yourself with the terminology adopted for the MPM product, you might want to take a few minutes to review the glossary in Appendix A of the MPM Projects manual. Below are several terms used in the instructions. Click This term means to move the mouse pointer to an object and quickly press and release the left mouse button once. Double-click This term means to move the mouse pointer to an object and quickly press and release the left mouse button twice. For example, you double-click on icons to open Task windows. If MPM responds as if you only clicked once, you need to try again clicking twice faster. Choose You choose an item to carry out an action; for example, you choose the option on a menu.

Online Help Complete online Help is available. You can open Help from the Help menu, by pressing F1, or by clicking on Help buttons in dialog boxes.

Contacting Technical Support Planview offers a variety of support options. When contacting us for technical support, follow these steps: 1. Check this manual to be sure you are following the correct procedure. 2. Note the type of hardware you are using, including network hardware. 3. Record as much detail as possible regarding your problem before calling, especially the following information: Exactly what you were doing when the problem occurred Exactly what messages appeared on the screen What steps you performed to create the problem and any steps you took to solve it. 4. Try to replicate the problem keystroke for keystroke, just before calling. 5. Have the product up on your computer at the problem point, and keep this manual handy when you call.

How to Reach Us You can contact our Technical Support department at Planview’s California headquarters by telephone, voice mail, e-mail, FAX, or mail. If you are writing to Planview about a problem, send a complete description of the problem you are having, along with a data diskette if appropriate. Planview recognizes all data received from you as proprietary and maintains a rigid policy of nondisclosure and confidentiality pertaining to such data. Telephone Call (909) 937-2111 between 6:00 a.m. and 5:00 p.m. Pacific time, Monday through Friday.

Voice Mail After hours, leave a voice mail message by calling (909) 937-2111.

E-Mail [email protected]

Web Server You can reach us via our home page on the World Wide Web at: Home Page http://www.planview.com.

FAX You can fax information 24 hours a day to (909) 937-2107. Be sure to send your FAX to the attention of the MPM Technical Support department or to your MPM Technical Support representative.

Mail Planview, Inc. Attention: MPM Technical Support 430 N. Vineyard #220 Ontario, California 91764

1 Introduction to MPM

1.1 MPM (Micro-Frame Program Manager) ...... 12 1.2 Backing Up MPM Files ...... 14

1.1 MPM (Micro-Frame Program Manager)

Planview’s MPM (Micro-Frame Program Manager) is a comprehensive WBS- based system for integrating proposals, cost estimating, and program management. MPM meets all government proposal/reporting requirements and enables you to respond to the most complex Request for Proposal quickly and effectively. It is easy to use and intuitive, and provides project solutions and information in a real-time environment. The key features of MPM are described below. You can use MPM to: Price proposals and estimate costs Prepare pre-RFPs Run "what if" analysis Run proposal and comparison reports Prepare best and final offers Baseline Planning/Estimates to Complete

Apply indirect costs using burden templates Define multiple rate tables Rollover from proposal to baseline(negotiated estimates become baseline) Maintain integrated but separate baseline and estimate to complete Run multiple estimate at complete calculations MS Project Interface The Microsoft Project Interface is a powerful interface between Microsoft Project and MPM provides you with an easy to use method for linking Project data into MPM. Performance Measurement

Supports major earned value methods Can define 99 milestones per WBS element Integrated program log includes management reserve and undistributed budget Enter actuals by resource and/or element of cost Enter actuals manually or by batch import, including option to apply indirect costs Online control account plan for simplified reporting and statusing

C/SCSC Reporting

A complete set of standard reports User-defined report formats with numerous sort, conditioning, summary, and time window options Variance analysis Required government report formats including Cost Performance Report Formats, Cost/Schedule Status Report, and Contractor Cost Data Reports Direct report interface with Lotus and Excel Produce custom reports with Planview’s report writer, Crystal Reports for MPM™ Batch reporting options Subcontract Management

Develop baselines across PCs at distributed sites Automatic update of performance and actuals Track subcontractor cost variance and schedule variance Security Features MPM has built-in security which provides access control of project data and MPM features. If you require a top secret level or if you are in a Tempest environment, you can be sure that only those individuals expressly authorized by the MPM system administrator will have access to MPM. Within MPM, there can be multiple users who are designated as system administrators or project administrators. Administrators are authorized to grant individual users permission rights to projects or to features of MPM. See Chapter 8: Controlling Security Access to MPM in the MPM Globals Manual for complete details.

1.2 Backing Up MPM Files

Regular backups of data files are essential. Backups are especially important when running functions such as Project Date Shift, Estimate Adjust and Estimating. If you should have a failure part way through the Project Date Shift or Estimate Adjust process, it would be necessary to go to your backup to recover data. It is highly recommended that a full backup be made at regular intervals such as the end of each day or just before and just after a sizable amount of data is input. We recommend: Daily backups using a data compression tool such as WINZIP or PKZIP If on a network, daily incremental and weekly full backups using a tape backup on the network We recommend that one full backup should be maintained onsite and one offsite, and that at least five backup tapes be maintained, revolving them as needed to have the most recent data and four prior generations backed up. All MPM users should be logged out of MPM during a backup session to ensure that all files are backed up. If a backup is undertaken while some files are open, those files can be excluded from the backup.

Daily Backups We recommend that individual users always maintain a backup of their current project data to archive all projects and global data files on a daily basis. You can save space by using a compression program such as WINZIP or PKZIP. Following is an example of a backup procedure using PKZIP: 1. Back up the global files (see list of global files on opposite page). First, if you have done this before, delete the .ZIP file which contains the global files from yesterday. Next, using PKZIP, create a new .ZIP file that contains the files named *.LIB. 2. Back up each set of project files in a separate .ZIP file using the same technique, first deleting yesterday’s .ZIP files, then creating new .ZIP files for each project.

Daily and Weekly Backups using a Network Backup Tape If you are running on a network, make sure your network administrator makes daily incremental backups and weekly full backups as protection against server failures.

What to Back Up Backups should include the following files: Project Files (for each project – substitute the name of the project for project) projectA.MIL projectB.OBS projectC.AUD projectD.WTD projectE.BOE projectF.WRD projectG.ATX projectI.BWP projectN.USR projectP.WBS projectQ.LOG projectR.CLN projectT.HED projectU.RRH projectW.RRD projectZ.APP

Global Files CALENDAR.FSC CALENDAR.HOL EOCCODES.LIB RATE.LIB RESOURCE.LIB TEMPLATE.LIB

System Files *.DAT *.FMT

User Configuration Files WINMPM.CFG

2 Installing MPM

2.1 Introduction to Installing MPM ...... 18 2.2 Pervasive.SQL V9 Workgroup Engine (V9.5) ...... 22 2.3 Standalone Installation ...... 26 2.4 Administrator Installation ...... 34 2.5 Workstation Installation ...... 40 2.6 Database Engine Installation ...... 46 2.7 Pervasive System Analyzer ...... 52 2.8 Configuring MPM ...... 58

2.1 Introduction to Installing MPM

MPM is a feature-rich system and correctly installing the software is important for the system to work properly. Please read this entire section before you begin installing the MPM software.

Summary of Installation Types Standalone MPM software and Pervasive.SQL V9 Workgroup Engine is installed on individual PCs. For installation directions, see topic 2.3 Standalone Installation • Local or centralized administration of users and data based on the location of the MPM System folder. • Local executable files o Decreases network traffic o Multiple locations for software updates

Administrator MPM software and Pervasive.SQL V9 Workgroup Install files are installed on the network server. The software can be run by many users and administered from one central location. A Workstation installation must then be performed on every PC that needs to run the MPM software. For installation directions, see topic 2.4 Administrator Installation. • Centralized administration of users and data. • Centralized executable files o Increases network traffic o Single location for software updates

Workstation Only the MPM software files that must reside locally on each individual PC are installed. For installation directions, see topic 2.5 Workstation Installation. Database Only the Pervasive.SQL V9 Workgroup Engine is installed. For installation Engine directions, see topic 2.6 Database Engine Installation. • Install to Microsoft Windows-based server that contains MPM database files.

System Requirements PC IBM compatible PC – Pentium 233 or higher Requirements 64 MB RAM, 512MB RAM if using MSP Link Disk Space – 80 MB for the MPM software; additional disk space for each project. Windows 2000 or XP Internet Explorer 6.0 or later MS Installer 2.0* MS Project 2003 if using the MSP Link Interface Java Runtime Environment (JRE) Standard Edition (latest version) **

Server IBM compatible PC – Pentium 450 or higher Requirements 256 MB RAM (without Data Disk Space – 125 MB for the MPM software; additional disk space for Warehouse) each project. Windows 2000 SP4, Windows 2003 Java Runtime Environment (JRE) Standard Edition (latest version) **

Server IBM compatible - Dual processor Pentium 2.8GHz or higher Requirements 150 GB hard disk drive (with Data 2GB RAM, 4GB or more preferred. 1 Warehouse ) Windows 2003 SP1 Pervasive.SQL V9 Workgroup Engine SQL Server 2005 SP1 (need not be collocated with MPM Data Server) .NET Framework 2.0 Java Runtime Environment (JRE) Standard Edition (latest version) **

*MS Installer: MS Installer 2.0 will be automatically installed during the MPM installation if it does not already exist or if there is an earlier version installed. Please note that a reboot is required after MS Installer is installed. ** Java Runtime Environment: This is only needed if the Pervasive Help and the Pervasive Control Center are to be accessed. 1 If you are installing the Data Warehouse please refer to Chapter 5 for Data Warehouse-specific requirements.

Previous Installations Before installing MPM 3.2, previous MPM installations should be uninstalled by using Add/Remove Programs in the Control Panel. We recommend that MPM 3.2 be installed in a different folder than the previous installation. It is necessary to uninstall/reinstall the Pervasive.SQL Database Engine on the machine acting as the gateway. In order for the new version of MPM to recognize your User IDs, Globals, and Projects, copy the following 3 system files from the previous MPM system folder to the new MPM system folder: global.dat, mpmusers.dat, proj.dat. Please contact MPM Customer Support if you need additional information.

Access Control Requirements For Windows 2000/XP/2003, you must have administrator rights to successfully install and uninstall MPM. If you are not sure whether you have administrator rights for a machine, check with your system administrator. Once installed, user access can be restricted based on the following criteria. It is important to grant users correct access to the MPM Executable, MPM System, and data folders. For Windows 2000/XP/2003, grant users Modify permissions to these folders. The executable files (*.EXE, *.DLL, *.MFL) can be flagged as Read-Only for added protection. No other files should be flagged as Read-Only. Please note that the Read- Only flag must be removed in order to install MPM updates. If user access to the Registry is limited, grant Full Control to the MPM and PERVASIVE SOFTWARE keys: HKEY_LOCAL_MACHINE\SOFTWARE\BUSINESS ENGINE CORPORATION\MPM 3.2 HKEY_LOCAL_MACHINE\SOFTWARE\PERVASIVE SOFTWARE

WARNING: The registry contains highly sensitive settings for the entire machine. An erroneous entry (or the lack of a required entry) can render a system useless until the registry is restored from backup or the operating system is reinstalled. We strongly suggest that only an experienced PC Technician or Network Administrator modify settings and permissions in the Registry. Planview will not be responsible for any mishap due to inaccurate registry changes.

2.2 Pervasive.SQL V9 Workgroup Engine (V9.5)

MPM 3.2 uses the Pervasive.SQL V9 Workgroup Engine (V9.5) Service Pack 2 which can run on a Microsoft Windows based workstation or server. This designated workstation or server is called a Gateway. The Gateway is a designated database engine that acts as a server engine for the Pervasive.SQL V9 Workgroup Engine. Before installing MPM you should decide what server(s) or workstation(s) will be the Permanent Gateway(s).

Gateway Configuration Consider what machine(s) you would like to act as your Gateway (database server). The designated Gateway machine will “serve up” the data requested by the other users. The Gateway must be a Windows-based machine. For optimum performance, the database engine should be running on the same machine as the data. If the data resides on another server, you can designate a different machine to be the Gateway. Please keep in mind the speed and reliability of the machine selected, since it will be acting as a server. Please refer to topic 2.6 Database Engine Installation for installation instructions. Gateway configuration is done in a file named MPMGATE.INI that is created in the MPM System folder when MPM is executed. If you have an engine running on the computer where your data is located, you do not need to do anything with your MPMGATE.INI file. If you do not, then we’ve provided the MPMGATE.INI to help you designate your Gateway computer(s) up front so you don’t have to select one when copying, moving, creating files or during conversion for each folder containing data.

MPMGATE.INI [Settings] UsePermanentGateway=yes [DefaultGateways] ;=gateway ;server=gateway

The UsePermanentGateway setting should always read “yes” unless you’ve made an informed decision to switch to a Floating Gateway.

The information in the [DefaultGateways] section is commented out and there just as an example. If you have one specific server you cannot put a database engine on, you should use an MPMGATE.INI setting like the SERVER=GATEWAY. You can have as many of these types of entries in the MPMGATE.INI as you need. For example, assume you have three projects that are located on a server in a remote location, and you cannot install a database engine on that server. The server’s name is NTSRV10. You have the database engine installed on your server that is named NTSRV8. In the MPMGATE.INI, you would enter NTSRV10=NTSRV8. Then when accessing data files on NTSRV10, MPM will use the database engine on NTSRV8 as the database server for those files. The other type of entry is =GATEWAY. This will set the Gateway as the same machine regardless of where the data is located. Here’s an example of where you would use this entry. Say you have your data spread across four different servers. You have a speedy Windows 2000 machine you would like to use as your Gateway for all of the data. You would set the =SPEEDY setting in the MPMGATE.INI and it would designate SPEEDY as the database sever for all of the folders containing data on all four servers. You can only have one setting in the MPMGATE.INI. Note: The Database engine is unable to access data on a local drive using a remote Database engine. For this reason MPM will attempt to use the local Database engine when data is being accessed from a local drive regardless of the [DefaultGateways] setting(s) defined in the MPMGATE.INI. The two settings can also be used in conjunction with each other. You can set specific gateways using the SERVER=GATEWAY settings, then the =GATEWAY to cover all other machines. When a Gateway is established a ~PVSW~.LOC file is located in the folder containing MPM data. A Gateway can be validated in Project and Global Maintenance by selecting Tools then Validate Gateway. If a Gateway is invalid a System Administrator can use the Validate Gateway utility to designate a new Gateway if necessary. In addition to the Pervasive.SQL V9 Workgroup Engine supplied with MPM, you can purchase the Server Engine, for Windows 2000/2003, directly from Pervasive.

Running Database Engine as a Service By default, the database engine does not run as a service, thus a user must be logged into the Gateway machine(s) at all times. However, you may configure the Pervasive.SQL V9 Workgroup Engine to run as a service. This allows the engine to start automatically when the operating system starts. A user is not required to log in to start the engine. This configuration requires SRVANY.EXE and SRVINSTW.EXE files found in the Windows 2000/2003 Resource Kit. The Resource Kit comes with MSDN and TechNet or it can be purchased separately. Check with your IS team to see if they have the Resource Kit before attempting this configuration. Detailed instructions are provided in the Pervasive Knowledgebase Article titled “Configure Workgroup or Workstation Engine to run as a Service under Windows 2000, XP.” This article can be found on the Pervasive web site http://www.pervasive.com.

Permanent Gateway Decision Process When accessing any MPM data (i.e., creating, copying, moving Globals or Projects or opening any applet), MPM validates the gateway by looking for the ~PVSW~.LOC file and confirming that the MicroKernel is running. The graphic below shows the process that is followed when data is accessed.

2.3 Standalone Installation

In a standalone installation, all MPM files are installed on a PC. As always, we strongly recommend that you quit all other Windows programs before installing. You will need approximately 150 MB of disk space to complete the installation.

Procedure To install the MPM software: 1. Insert the CD and it should automatically start to run. If necessary run the SETUP.EXE program.

MPM loads the Setup Wizard and displays the Welcome screen shown in Figure A. If you haven't already, we urge you to quit any other Windows programs.

Figure A. Installation Welcome screen 2. To continue with the installation, click Next.

MPM displays the Select Setup Type dialog box shown in Figure B.

Figure B. Select the type of installation.

3. Select the Standalone option and click Next.

MPM displays the User Information dialog box shown in Figure C.

Figure C. Enter your name, company, and activation key.

4. Enter your name, name of your company, and the activation key.

The Name and Company fields are free form. The Activation Key was shipped with your MPM package. If you have lost your Activation Key, please contact MPM Technical Support, as described in Chapter 1. If you enter an incorrect Activation Key, MPM will display an error message. You will not be able to continue the installation without the correct key. 5. After entering the information, click Next.

MPM displays the Choose Executable and System Folders dialog box shown in Figure D.

Figure D. Specify the directories for the files.

6. Accept the default MPM Executable and System folders, or click Browse to select different folders. If a folder you specified does not exist, setup will automatically create the folder. We recommend that MPM 3.2 be installed in a different folder than the previous installation.

The application files are installed in the MPM Executable folder. Pervasive.SQL V9 is installed in the PVSW folder under the MPM Executable folder. The system files are installed in the MPM System folder.

The MPM System folder is where your project, global, and user lists will reside. If you have an existing installation of a previous version of MPM, this is where the MPM system files such as MPMCTRL.DAT, PROJ.DAT, MPMUSERS.DAT, DISTCURV.DAT, and GLOBAL.DAT reside.

If you want to share data with other users, then the MPM System folder should point to a centralized location on the network. 7. After specifying the folders, click Next. If a folder already exists from a previous installation, MPM displays a dialog box asking if you want to overwrite the contents. This will replace any older MPM executable and/or supporting files, but will not replace any data files. To return to the Choose Executable and System Folders dialog box, click No. To continue the installation, click Yes. MPM displays the Select Program Folder dialog box shown in Figure E.

Figure E. Select a program folder.

8. Accept the suggested program folder or enter a new one. The program folder will be displayed in the Programs listing on the Windows start menu. 9. To continue the installation, click Next. MPM displays the Confirm Settings dialog box shown in Figure F.

Figure F. Confirm the settings.

10. If you want to change a setting, click the Back button. This will step you back through the previous screens. To confirm the settings and initiate the installation, click Next. MPM displays a status screen (See Figure G) showing the files being installed and will generate a file list in the MPM Executable folder.

Figure G. Installation begins. MPM then displays a dialog showing that Pervasive is being installed (See Figure H). Note: Pervasive can take several minutes to install and your screen will appear inactive during this time.

Figure H. Pervasive Installation. 11. When the installation is complete, MPM displays the confirmation screen shown in Figure I. We recommend that you review the ReadMe file for the latest information on MPM. By default, this option is checked in the dialog box.

Figure I. Setup is complete.

12. To complete the setup process and display the ReadMe file, click Finish. The Pervasive.SQL V9 Workgroup Engine will now be running on this machine.

Please note the icon in your taskbar. When necessary, MPM displays the reboot screen shown in Figure J. If the following screen is displayed, you need to restart the machine in order for MPM and the Database Engine to run successfully.

Figure J. Reboot the machine.

13. After rebooting, the Pervasive Engine will automatically start during system boot up.

What to Do Next You have completed the Standalone installation. We recommend that you run the Pervasive System Analyzer (See Section 2.7 Pervasive System Analyzer for details) in order to test the local Pervasive.SQL V9 Workgroup Engine. If you plan to store data on a server, review topic 2.2 Pervasive.SQL V9 Workgroup Engine and decide what machine(s) will act as your Gateway (database server).

2.4 Administrator Installation

In an Administrator install, all MPM files are installed onto a network server so the software can be run from a central network location. After completing the Administrator install, you will have to do a Workstation install on every PC that needs to run the MPM software. This installs the necessary files on the workstation.

The Administrator Installation will not install the database engine on the server. Refer to the Database Engine Installation for directions on installing the Pervasive.SQL V9 Database Engine on a Microsoft Windows based server.

The Workstation installation automatically uses the same MPM System Folder and Executable Folder specified during the Administrator Installation. For this reason, you do not want to install the Administrator installation from the server console pointing to a local server drive. Instead install the Administrator installation from a workstation to a mapped network drive or UNC. If using a mapped network drive, be sure the mapped drive is the same for all users. Before you begin installing MPM, we strongly recommend that you quit all other Windows programs prior to executing the installation procedure. You will need approximately 200 MB of disk space to complete the installation.

Procedure To install the Administrator version of MPM: 1. Insert the CD and it should automatically start to run. If necessary run the SETUP.EXE program. MPM loads the Setup Wizard and displays the Welcome screen shown in Figure A. If you haven't already, we urge you to quit any other Windows programs.

Figure A. Installation Welcome screen 2. To continue with the installation, click Next.

MPM displays the Select Setup Type dialog box shown in Figure B.

Figure B. Select the type of installation.

3. Select the Administrator option and click Next.

MPM displays the Enter Activation Key dialog box shown in Figure C.

Figure C. Enter the activation key.

4. Enter the activation key.

The Activation Key was shipped with your MPM package. If you have lost your Activation Key, please contact MPM Technical Support, as described in Chapter 1. If you enter an incorrect Activation Key, MPM will display an error message. You will not be able to continue the installation without the correct key. 5. After entering the information, click Next.

MPM displays the Choose Executable and System Folders dialog box shown in Figure D.

Figure D. Specify the directories for the files.

6. Accept the default Executable and System folders, or click Browse to select different folders. If a folder you specified does not exist, setup will automatically create the folder. We recommend that MPM 3.2 be installed in a different folder than the previous installation.

The application files are installed in the MPM Executable folder. The system files are installed in the MPM System folder.

7. After specifying the folders, click Next. If a folder already exists from a previous installation, MPM displays a dialog box asking if you want to overwrite the contents. This will replace any older MPM executable and/or supporting files, but will not replace any data files. To return to the Choose Executable and System Folders dialog box, click No. To continue the installation, click Yes. MPM displays the Confirm Settings dialog box shown in Figure E.

Figure E. Confirm the settings.

8. If you want to change a setting, click the Back button. This will step you back through the previous screens. To confirm the settings and initiate the installation, click Next. MPM displays a status screen showing the files being installed. When the installation is complete, MPM displays the confirmation screen shown in Figure F. We recommend that you review the ReadMe file for the latest information on MPM. By default, this option is checked in the dialog box.

Figure F. Setup is complete.

9. To complete the setup process and display the ReadMe file, click Finish.

What to Do Next

You have completed the Administrator installation. You should now perform the Workstation installation on each PC that will be running MPM. For directions on running the Workstation installation, see the next topic 2.5 Workstation Installation. If you have not done so, review topic 2.2 Pervasive.SQL V9 Workgroup Engine and decide which machine(s) will act as your Gateway (database server).

2.5 Workstation Installation

In a Workstation install, minimal MPM files and the Pervasive.SQL V9 Workgroup Engine are installed on the PC. Before you can perform the Workstation installation, you must have completed the Administrator installation The Workstation Installation will automatically use the MPM Executable and MPM System folders selected during the Administrator installation. We strongly recommend you quit other Windows programs before installing. Also, make sure you have 100 MB of free disk space.

Procedure To install the Workstation version of MPM:

1. Run the SETUP.EXE program from the SETUP subdirectory located in the directory designated as the MPM Executable Folder during the MPM Administrator install. Check with your System Administrator for the name of the directory. MPM loads the Setup Wizard and displays the Welcome screen shown in Figure A. If you haven't already, we urge you to quit any other Windows programs.

Figure A. Installation Welcome screen.

2. To continue with the installation, click Next.

MPM displays the User Information dialog box shown in Figure B.

Figure B. Enter your user name and company.

3. Enter your name and the name of your company and click Next.

MPM displays the Choose Working Directory dialog box shown in Figure C.

Figure C. Specify the directory.

4. Accept the default Working directory, or click Browse to select a different folder on the local drive. If a folder you specified does not exist, setup will automatically create the folder. Pervasive.SQL V9 is installed in the PVSW folder under the MPM Working Directory. 5. After specifying the folder, click Next. MPM displays the Select Program Folder dialog box shown in Figure D.

Figure D. Select a program folder.

6. Accept the suggested program folder, or enter a new one.

The program folder will be displayed in the Programs listing on the Windows Start menu. 7. To continue the installation, click Next.

MPM displays the Confirm Settings dialog box shown in Figure E.

Figure E. Confirm the settings.

8. When the installation is complete, MPM displays the confirmation screen shown in Figure F . We recommend that you review the ReadMe file for the latest information on MPM. By default, this option is checked in the dialog box.

Figure F. Setup is complete.

9. To complete the setup process and display the ReadMe file, click Finish. The Pervasive.SQL V9 Workgroup Engine will now be running on this machine.

Please note the icon in your taskbar. When necessary, MPM displays the reboot screen shown in Figure G. If the following screen is displayed then you need to restart the machine in order for MPM and the Database Engine to run successfully.

Figure G. Reboot the machine.

10. After rebooting, the Pervasive Engine will automatically start during system boot up.

What to Do Next You have completed the Workstation installation. We recommend that you now run the Pervasive System Analyzer (See Section 2.7 Pervasive System Analyzer for details) in order to test the local Pervasive SQL V9 Workgroup Engine. If you have not done so, review topic 2.2 Pervasive.SQL V9 Workgroup Engine and decide what machine(s) will act as your Gateway (database server).

2.6 Database Engine Installation

In a Database Engine install, Pervasive.SQL V9 Workgroup Engine (V9.5) Service Pack 2 is installed on a Microsoft Windows based workstation or server. The Workgroup Engine requires Windows 2000, XP, Windows Server 2000 SP4, or Windows Server 2003. The Database Engine Installation should be run if you are sharing data on the network and do not wish to use an engine from one of the workstations as the Gateway (or database server) engine. We recommend installing the Database Engine to every Microsoft Windows based server that contains MPM Projects, Globals, or System files for best performance and ease of use. Please refer to the “Previous Installations” section of 2.1 Introduction to Installing MPM for details.

By default, the database engine does not run as a service. A user must be logged into the Gateway machine(s) at all times. This user will need appropriate permissions to access MPM data. Please refer to the “Access Control Requirements” section of topic 2.1 Introduction to Installing MPM for specific information regarding access control requirements.

Pervasive.SQL V9 Workgroup Engine (9.5) Service Pack 2 can be configured to run as a service rather than a console application. Please refer to the “Running Database Engine as a Service” section of topic 2.2 Pervasive.SQL V9 Workgroup Engine for more information.

It is not necessary to run the Database Engine installation on any system that has a standalone or workstation installation. We strongly recommend you quit other Windows programs before installing. Also, make sure you have 100 MB of free disk space. The database engine cannot be installed from a remote location. To install the database engine on a Microsoft Windows based server, install from the server console to a physical drive letter, not a mapped or virtual drive letter.

Procedure To install the Database Engine: 1. Go to the server or workstation that will act as the Pervasive Gateway. Insert the CD and it should automatically start to run. If necessary run the SETUP.EXE program. MPM loads the Setup Wizard and displays the Welcome screen shown in Figure A. If you haven't already, we urge you to quit any other Windows programs.

Figure A. Installation Welcome screen.

2. To continue with the installation, click Next. MPM displays the Select Setup Type dialog box shown in Figure B.

Figure B. Select the type of installation.

3. Select the Database Engine option and click Next. MPM displays the Enter Activation Key dialog box shown in Figure C.

Figure C. Enter the activation key.

4. Enter the activation key.

MPM displays the Choose Destination folder dialog box shown in Figure D.

Figure D. Specify the directory.

6. Accept the default Destination folder, or click Browse to select a different folder on the local drive. If a folder you specified does not exist, setup will automatically create the folder. Pervasive.SQL V9 is installed in the PVSW folder under the Destination folder. 7. After specifying the folder, click Next. 8. When the installation is complete, MPM displays the confirmation screen shown in Figure E. We recommend that you review the ReadMe file for the latest information on MPM. By default, this option is checked in the dialog box.

Figure E. Setup is complete

9. To complete the setup process and display the ReadMe file, click Finish. The Pervasive.SQL V9 Workgroup Engine will now be running on this machine.

Please note the icon in your taskbar. When necessary, MPM displays the reboot screen shown in Figure F. If the following screen is displayed then you need to restart the machine in order for MPM and the Database Engine to run successfully.

Figure F. Reboot the machine.

10. After rebooting, the Pervasive Engine will automatically start during system boot up.

What to Do Next You have just completed the Database Engine installation. We recommend that you now run the Pervasive System Analyzer (See Section 2.7 Pervasive System Analyzer for details) in order to test the local Pervasive.SQL V9 Workgroup Engine. For information on setting up the engine to run as a service, please refer to the last paragraph of section 2.2 Pervasive.SQL V9 Workgroup Engine. If you have not installed the MPM software already, please refer to topic 2.1 Introduction to Installing MPM.

2.7 Pervasive System Analyzer

In order to test the local Pervasive SQL V9 Workgroup Engine, run the transactional and relational tests in Pervasive System Analyzer. Although you may skip this step of the installation, completion of this test is recommended. 1. From the Windows Start menu, select Programs\Pervasive System Analyzer to start the Pervasive System Analyzer. 2. The Pervasive System Analyzer wizard begins (See Figure A). Click Next to continue with the analysis.

Figure A. Pervasive System Analyzer Wizard.

3. The Analyzer Options Screen Displays (Figure B) 3.1 Select the Test Active Installation option. 3.2 Deselect the Test Network Communication option. 3.3 Click Next to continue with the analysis.

Figure B. Accept the default Analyzer Options.

4. To test the local Pervasive.SQL V9 Workgroup Transactional Engine, accept the defaults and click Next (Figure C).

Figure C. Analyze the Pervasive Transactional Engine. 5. Pervasive System Analyzer tests the Transactional Engine and when finished displays the Transactional Engine Test Results dialog box shown in Figure D. The Transactional Engine test is successful when all tasks are checked off.

Figure D. Test the Pervasive Transactional Engine. 6. After reviewing the Transactional Engine Test Results, click Next. MPM displays the Pervasive System Analyzer - Relational Engine Test dialog box shown in Figure E.

Figure E. Analyze the Pervasive Relational Engine.

7. To test the local Pervasive.SQL V9 Workgroup Relational Engine, accept the defaults and click Next.

Although you may skip this step of the installation by clicking Cancel, completion of this test is recommended. Pervasive System Analyzer will test the Relational Engine and when finished will display the Relational Engine Test Results dialog box shown in Figure F. The Relational Engine test is successful when all tasks are checked off.

Figure F. Test the Pervasive Relational Engine.

8. Click Next to complete the test. The Pervasive System Analyzer displays a summary of the tasks completed as well as an option to view the Log File (See Figure G).

Figure G. The Pervasive System Analyzer Summary Screen.

You have now completed the Pervasive System Analyzer test.

2.8 Configuring MPM

At this point, if you have followed the steps in this chapter, installation of MPM has been completed and your internal security has been established. To complete the setup process, verify the following information to make sure that MPM will function properly.

WINMPM.INI File The WINMPM.INI file is located in your Windows directory, and should contain: [Path] DataDirectory=C:\WINMPM\

In this example, C:\WINMPM is the location of the MPM System folder. This directory was specified during installation in the MPM System Folder field on the Choose Executable and System Folders dialog box.

Creating a Valid User List As part of the installation procedure, the MPM Administrator will need to create a list of individuals authorized to use MPM. The default login for the MPM Administrator is: User ID: SYSADMIN Password: MPM All MPM systems are delivered with the above default User ID and Password. The SYSADMIN User ID may not be changed or deleted. However, in order to protect the security of your system, we strongly recommend that the SYSADMIN password be changed immediately after MPM is installed, using the Change Password option on the Tools menu of the Menu Manager.

The password for the SYSADMIN user cannot be easily reset. If the MPM Administrator changes the default SYSADMIN password, and forgets the new password, contact Planview’s Technical Support for assistance. To create and update valid users, see Chapter 8: Controlling Security Access to MPM in the MPM Globals manual. Up to 300 users may be entered.

Subdirectory Organization Some System Administrators, particularly in a network environment, may wish to further enhance security features by restricting user access based on subdirectory organization. Careful consideration must be given to ensure that your subdirectory organization

conforms to the requirements of the MPM software. Please review the following explanations carefully. It is important to note that the software and projects must reside in a subdirectory (e.g., C:\WINMPM), not a root directory (e.g., C:\). For the same reason, you cannot map an MPM subdirectory to a root directory on another drive (e.g., C:\WINMPM to J:\).

Maintaining Project Files MPM provides features to create new project subdirectories, copy a project into another subdirectory, move a project from one subdirectory to another, etc. Some users have found that keeping each project in a unique subdirectory provides more effective data management and minimizes accidental loss of data. Additionally, we recommend that, as much as possible, project file manipulation be performed using only the Project Maintenance window.

3 Using MPM

3.1 Introduction to Using MPM ...... 62 3.2 Windows Features ...... 64 3.3 Logging In and Logging Out of MPM ...... 66 3.4 Running the User Logout Utility ...... 68 3.5 Using the Menu Manager ...... 70 3.6 The Open Dialog Box – Access to MPM Tasks ...... 72 3.7 Introduction to MPM Task Windows ...... 74 3.7.1 Navigating the Task Window ...... 76 3.7.2 Editing Data in the Task Window ...... 78 3.7.3 Changing the Display ...... 80 3.8 Setting MPM Options ...... 82 3.9 Previewing Data ...... 86 3.10 Printing Data ...... 88 3.11 Multi-User Access & Record Locking ...... 90

3.1 Introduction to Using MPM

MPM uses the Windows interface to give you easy access to your data. Common windows and menus work the same way throughout MPM. This chapter describes how the standard elements of the interface work. Once you know the standards, you will be able to use most of the MPM windows without further instruction. To understand each window and its individual features and use, refer to the MPM Projects manual.

Log In to MPM Before you can use MPM, you must log in. MPM provides this security feature to prevent unauthorized access to the MPM projects and data. The login procedure is described in detail in topic 3.3 Logging In and Logging Out of MPM. Figure A. MPM Login Window.

MPM Menu Manager The Menu Manager is the key to navigating within MPM. From the Menu Manager, you access all other windows inside MPM. The Menu Manager is described in detail in topic 3.5 Using the Menu Manager.

Dialog Boxes Figure B. MPM Menu Manager MPM displays dialog boxes when there is information needed to carry out your request. Dialog boxes contain questions you need to answer. Many Task windows in MPM need information from you before the window can be opened. These Task windows display an Open dialog box. For more information about Open dialog boxes, see topic 3.6 The Open Dialog Box – Access to MPM Tasks. Figure C. Elements of Cost Open Dialog box. Task Windows Use the Task windows to enter, track, update, and view the data in your projects. There are many Task windows in MPM. For information about using Task windows, see topic 3.7 Introduction to MPM Task Windows. Note: this chapter only provides general

guidelines. For specifics about a particular Task window, see the MPM Globals and MPM Projects manuals.

Standard Messages Throughout MPM, standard messages appear on the bottom of the window in the Status Bar (see Figure E below) or Figure D. Elements of Cost Task Window. in pop-up windows. These messages provide directions, information, and warnings to assist you in moving easily and efficiently through the various functions in MPM. We recommend you read all messages carefully. If MPM has paused and does not seem to be responding, check the Status Bar to see if MPM is displaying a message that it is processing a request.

Status Bar Initializing, please wait… Figure E. Elements of Cost Task Window and Status Bar. If the Status Bar is not showing, you can turn it on by selecting Status Bar on the View menu. To hide the Status Bar, choose the option again.

3.2 Windows Features

MPM for Windows 3.2 uses many standard Windows features. If you are new to Windows, we suggest you do the Windows online tutorial before attempting to use MPM.

Buttons and Tool Tips Command buttons appear in dialog boxes and take on many shapes and sizes within MPM. All buttons are labeled with text or a graphic indicating their function. To activate the desired command, position the mouse pointer over the desired button and click the left mouse button, or press Tab until the desired button is highlighted and press Enter.

MPM provides additional help through Tool Tips. If you position the mouse pointer over a command or tool button, MPM displays the name of the tool or a description of the function.

Data Entry Cells A data entry cell is an area in a grid where you can enter data. Some data entry cells contain default data, which you can choose to accept as-is, or type new information over the default. To edit the information in a cell, double-click in the cell or press F2. The text in the cell turns blue when you are editing the data. Many cells expect you to type text inside, however, some data entry cells are in the form of Check Boxes/Buttons, List Boxes, or Radio Buttons.

Check Boxes Check boxes are used to select or deselect options, or to expand or collapse levels of data. When you click a box, MPM displays a check mark and selects the option or expands the list under the box. Click again, and MPM removes the check mark and deselects the option or collapses the list.

Check Fields Check fields answer yes/no questions, usually when you are entering data. When you double-click in a check field, MPM displays a check mark. Double-click again, and the check mark is erased. You can also change its value by pressing the Spacebar when the check box is highlighted, or click the box, which acts like a list box to select the desired option.

List Boxes A List Box contains a list of possible options or values you can choose. To see all values, click the scroll arrows or drag the scroll bar. To scroll directly to a desired value (if it exists in the list), type the first character of the option you want. To select the desire value, bring the mouse pointer over the desired value and click on it with the mouse button, or press Enter.

Drop-Down List Boxes A Drop-Down List Box contains a list of possible options or values you can choose, with only one value showing; e.g., . To see all values, click the arrow button, which drops the list down and shows all values. To scroll directly to a desired value (if it exists in the list), type the first character of the option you want. To select the desire value, bring the mouse pointer over the desired value and click on it with the mouse button, or press the down-arrow to move to the desired value and press Enter.

Radio Buttons Radio buttons are used to select one of several options. When you click on the desired option, a black dot appears in the radio button to indicate the option is selected. You can select only one radio button in a group.

Accessing Online Help You can access the MPM Help system in one of the following ways: F1 Key When viewing an MPM window, press the F1 key to receive window-specific help or to reach the main help menu. Help Menu You can search for help by topic or keyword by selecting MPM Help Topics from the Help menu in any MPM window.

3.3 Logging In and Logging Out of MPM

When you launch (start) MPM, you are required to log in. MPM provides this security feature to prove you are authorized to access the MPM projects and data.

Your User ID Your User ID must be set up by the MPM Administrator. If you are the Administrator, or if you are working alone, use the User ID SYSADMIN.

Your Password Your Password must also be setup by the MPM Administrator. If you are the Administrator, or if you are working alone, use the password MPM. To change the password, see Changing Your Password later in this topic.

Launching MPM Launch MPM in one of the following ways: Double-click the MPM icon on your desktop. Click Start | Programs. From the Programs menu, select WinMPM 3.2 and then MPM for Windows 3.2. Using Windows Explorer, open the MPM folder and double-click the WINMPM.EXE icon. Figure A. MPM Login Window. MPM displays the Login window shown in Figure A.

Logging Into MPM 1. Enter your User ID and Password. 2. To display the Menu Manager shown in Figure B, click OK.

Figure B. The MPM Menu Manager.

Logging Out Once you are in the Menu Manager, you can log out by pressing Ctrl+L or choosing Logout on the File menu. MPM waits at the Menu Manager for the next login.

Closing MPM To close MPM, choose Exit on the File menu, press Alt+F4, or click the X box in the top right-hand corner of the window. If any MPM windows are open, they will all be closed automatically.

Changing Your Password To change your password, choose Change Password on the Tools menu in the Menu Manager window. MPM displays the Change Password dialog. Enter the old password, the new password twice for verification, and click OK. Figure C. Change Data Access Password dialog box Once you have logged into MPM, you will be able to edit only the project data to which you have been granted access. Check with your MPM Administrator for details.

3.4 Running the User Logout Utility

The User Logout Utility is provided for use in a network environment so that a System Administrator has the capability to clear any or all user login flags when the need arises. Only users who have been assigned System Administrator authorization level will have access to this utility. The Utilities tab is not displayed for those users who do not have System Administrator permissions. When a user is logged out by a System Administrator, the system allows any function the user has in progress to be completed. Users receive a message advising them that they have been logged out. Users are given the opportunity to save any modifications in the event their system is not set to automatically save.

Figure A. User Logout Utility Window

Procedure 1. From the Menu Manager window, select the Utilities tab and click on User Logout Utility. The window shown in Figure A displays a list of all users currently logged into MPM along with the date and time they logged in. The name of the System Administrator who is logging out users is not displayed in the list of users. 2. Place a check mark in the Logout column for each user to be logged out. 3. Click the Run icon on the tool bar to complete the logout. 4. Click the X in the top right-hand corner of the window to exit and return to the Menu Manager window.

3.5 Using the Menu Manager

Use the Menu Manager Window to access all of MPM’s Task windows. A toolbar gives you quick access to common tasks. Tabs allow you to access groups of the Task windows. Each Task Window can be accessed by double-clicking its icon, or by choosing the option on the File menu. Title Bar Menu Bar Tool Bar Tabs

Figure A. The Menu Manager with the Global Tab selected. Tabs Use the tabs on the Menu Manager to access the Task windows. MPM has six tabs: Globals: enter/maintain Global File sets; control security Projects: enter/maintain Project data Reports: select from a wide range of Reports Imports: import data into MPM from accounting, spreadsheet, other systems Exports: export data from MPM to a variety of external formats for use with other systems Interfaces: import data directly from MS Project using the MSP Link interface. Only one tab is on top at any one time. When you click on a tab, the Menu Manager window changes to show the Task windows available. For example, in Figure A, the Globals tab is selected. If you click the Projects tab, a different set of tasks is displayed.

Pull-Down Menus You access the menus from the Menu Bar. The Menu Manager has five menus: File, Edit, View, Tools, and Help. Many of the options on these menus are available in all Task windows. Some options, such as the Change Password option, are only available here.

Choosing a Menu Option Using the Mouse To choose a menu option, position the mouse pointer over the menu and click the left mouse button. Drag the mouse pointer down to the desired option, and double-click the mouse button. Some options under a menu have additional options. These additional options are indicated by an arrow symbol along the right edge of the menu. To display the additional options, move the cursor over the option with the arrow. In Figure B, the additional options for the Globals option are shown.

Choosing a Menu Option Using the Keyboard

You can also select menu options using the keyboard. Figure B. Click on a pull-down Some, such as Logout and Exit in Figure B, have a menu to see all its options. keystroke shown on the menu. For example, to logout, hold down the Control key and press the L key. In this manual, this type of keystroke combination is represented as Ctrl+L. All options also have Alt keystrokes. Notice how each option has one letter underlined. To select a menu option using the keyboard, hold the Alt key down and type the underlined letter. For example, to access the Close option on the File menu using the keyboard, press Alt+F to highlight the File menu, then type “C” to select the Close option. If a menu option or a button is grayed out, it is currently unavailable. This may be because you have not selected any data, or because your current settings do not permit the action provided by the option. Or you may not have been granted security access to that function. Check with your MPM Administrator for details.

Changing the Menu Manager View You can change the task listings view using the Menu Manager buttons. There are five buttons available on the Menu Manager Tool Bar: . The first four buttons change the task listing to show (respectively): large-sized icons, small icons, small icons in a list, and a detailed text listing. The text listing shows the version and modification dates of the task windows, which can be helpful in troubleshooting. See Chapter 9: Maintaining the MPM System in the MPM Globals Manual for details. The fifth button accesses the MPM options. See topic 3.8 Setting MPM Options for details.

3.6 The Open Dialog Box – Access to MPM Tasks

Most Task windows in MPM have an Open dialog box. Each Open dialog box is specific to the Task window. The Open dialog box asks you for information needed before opening the Task window, such as which project to open, the data you want to edit, and the starting view for the window. Figure A shows two Open dialog boxes. Compare the EOC Open dialog box, which has only one prompt (Global ID), to the OBS Open dialog box, which has two. Figure A. EOC and OBS Open Dialog Boxes.

Selecting Data to Download Some Open dialog boxes allow you to select the data to download. If you decide to use this feature, only the data you select on the Open dialog box is downloaded. Once the Task window is up, you can download additional data if needed. While loading data, MPM displays messages in the Status Bar. To cancel the download, press ESC. Selecting, or filtering, the data when you open a Task window can save a considerable amount of time when you are working with a project that has a large amount of data. Unless you specify a filter choice, MPM loads all the data into the Task window, which may take several minutes depending on the size of your project. It is recommended that you use the filtering options on the Open dialog box to limit the amount of information that is downloaded.

Filtering by WBS Legs The Expand/Collapse Box The Select/Deselect Box Some Open dialog boxes allow you to filter by WBS Leg, Loads the WBS Element and All Sub-elements expand/collapse the legs to see the available WBS legs, and Does not Load the WBS Element or Sub-elements select/deselect the desired leg(s).

Loads the WBS Element and The Expand/Collapse Box next to Selected Sub-elements each WBS Leg shows whether its children are displayed. A plus sign (+) indicates the WBS is collapsed and there are lower level WBS children that are not currently displayed. A minus sign (–)

indicates the WBS is expanded and all children are displayed. The lack of an Expand/ Collapse Box indicates the WBS element has no children. To select or deselect which WBS elements to download, click the check mark box. To download the WBS element and all of its children, collapse the WBS element and click its check mark box. To download the element plus several of its children, expand the WBS element and click the check mark boxes of the desired children. If a collapsed WBS element is not checked, the element and its children will not be downloaded. If no WBS elements are selected, MPM loads all WBS elements. MPM saves the WBS selections for the current project, and displays the same selections the next time you open the project.

Filtering the WBS by Manager Some Open dialog boxes offer an additional filter by Managers. For example, if you select Manager JONES, only the WBS elements assigned to Manager JONES are downloaded. MPM saves Manager selections for the current project, and displays the same selections the next time you open the project. To select a single manager, click on the manager’s name in the list. To select multiple managers, use the Shift and Ctrl keys as you would in any Windows application. To deselect all Manager filters, hold down the Ctrl key and click on the last manager’s name. The Manager field displays , indicating no manager has been selected.

Filtering the WBS by Element Type Some Open dialog boxes offer an additional filter by Element Type. At least one Element Type option must be selected. To select elements that have not been assigned a type, click . MPM then downloads only the elements that match the Element Type(s) selected. For example, if you selected element type Work Package, only Work Package WBS elements are downloaded when the Task window opens.

Choosing a Starting View Some Open dialog boxes allow you to choose the tab (view) selected when the Task window is displayed. This handy feature can save you a little time also.

3.7 Introduction to MPM Task Windows

Use the MPM Task windows for entering, maintaining, and analyzing the MPM data. Each serves a unique purpose, but all have some similarities.

Working with Grids MPM has a powerful, spreadsheet interface, which provides easy access and viewing of all your data at a glance. When you need to create a new record (piece of data; e.g., another WBS element, or Contract Line Item), you insert a new row. All fields associated with that piece of data (e.g., the WBS ID, WBS Description, and Start Date of the new WBS element), are displayed as columns in the grid. If there are more rows than can be displayed on the grid, MPM adds a vertical scroll bar to the window. If there are more columns than can be displayed, MPM adds a horizontal scroll bar to the window. All windows have a toolbar with buttons. The buttons provide quick, easy access to the common tasks in the task window. Many buttons are the same in all Task windows. Some Task windows are split into two panes, like the WBS window shown in Figure A. The left pane displays items, the right pane displays the detail information associated with the item. For example, the left pane of the WBS window displays the WBS tree. You can use the left pane to find the leg of the tree you need, and MPM displays the detail about that leg in the right pane.

Left Pane Separator Right Pane Minimize, Maximize, Close Toolbar Horizontal Scroll Bar Row Number

Vertical Scroll Bar

Figure A. The WBS grid is split into a left and right pane.

Working with Window Panes Scrolling. To use the scroll bars to see more data, position the mouse pointer over the scroll bar button, click the left mouse button down, and drag the mouse along the bar. Or click the mouse button in the gray area in the scroll bar in front or behind the scroll bar button. Sizing Panes. To see more or less of one pane (in a window with two panes), click on the separator bar and drag it to the left or right. Selecting Rows/Columns. To highlight an entire row, click the row number. To highlight an entire column, click the column heading (field name).

Changing Window Characteristics Sizing Windows. To change the size of a window in one dimension, click on a window border and drag the border to the required size. To make a window bigger or smaller in both dimensions at the same time, position the mouse button in the lower right corner of the window. The cursor becomes a two-headed arrow . Click the mouse button and drag it to the left and/or up to make a window smaller, or right/down to make a window larger. Moving Windows. To move a window, click in the title bar of the window and drag it as desired. Hiding Windows. To hide (minimize) a window, click the button in the upper right corner. To unhide (maximize) a window, click the window name in the Windows taskbar.

3.7 Introduction to MPM Task Windows 3.7.1 Navigating the Task Window

Use the following guidelines to navigate through the fields in a Task window grid. To advance to the next field, press Tab, the right arrow, or the Enter key. To move back to the previous field, press the Shift+Tab or the left arrow key. To move between rows, press the Up and Down arrow keys. Use the horizontal and vertical scroll bars to bring additional columns and rows into view. When clicking and dragging the vertical scroll bar, a pop-up label displays the field (column) name in the grid. When clicking and dragging the horizontal scroll bar, a pop-up label displays the row number in the grid. You can also scroll down using the PageDown key, and scroll up using the PageUp key. To move to the last column (field) of a row, press the End key. To move to the beginning column (field) of a row, press the Home key. To move to the first cell in a row that contains data in a right pane, press Ctrl+G. To move directly to any cell, point to the cell with the mouse and click. Finding a Data Item There are several methods for finding a particular data item in a Task window: Use the Horizontal and/or Vertical Scroll Bars to scroll through your data Some Task windows have an option on the Edit menu called Find that you can use to search for a text string. This option works exactly the same in all Task windows in which it is available. To find a text string (for example, ENGINEER), enter the text and click Find Next. MPM searches for the text you entered in the current Task window. If MPM finds the text, MPM

highlights the cell and positions the cursor there. Figure A. The Find dialog box If MPM does not find the text, MPM displays an error message. If the text describes the contents of an entire cell, click Match Whole Cell Only. If you enter the text ENGINEER and click this check box, MPM will not find DESIGN ENGINEER or TEST ENGINEER, just ENGINEER. If you enter ENGINEER and click Match Case, MPM will match the text’s upper and lower case, and will only find ENGINEER, not Engineer or enGInEEr.

Canceling a Process To stop processing a request, or to escape from changes you made to data in a grid, press the Esc key. This key can also be used to close any dialog box. It is the equivalent to clicking Cancel.

Displaying and Hiding Fields MPM displays the fields as columns in the Task window. You can display or hide any combination of columns, using Column Hide on the Format menu. The Column Hide dialog box is shown in Figure B. Selected fields (columns) are hidden in the Task window.

Figure B. The Column Hide dialog box Below are guidelines for working with the Column Hide dialog box. To: Do this: Hide a single column Select the column and click OK. Hide two or more Select the first column, hold down the Shift key, select the contiguous columns last column, and click OK. For example, to select the Level through Description fields shown in Figure A, you would select Level, hold down the Shift key, and select Description. Hide two or more Select the first column, hold down the Ctrl key, select another noncontiguous columns column, etc. The columns do not have to be next to each other in the Column Hide dialog box. Click OK to accept your selections. Display all columns Select any column, hold down the Ctrl key, select the same column again, and click OK.

3.7 Introduction to MPM Task Windows 3.7.2 Editing Data in the Task Window

Data Entry Conventions Use the following conventions when entering data into the system: Press Tab or the arrow keys to advance the cursor to the next field (cell). Watch the Status Bar at the bottom of the window for prompts or error messages. To select an entire column in the window, click the column’s heading (field name). To select an entire row, click the row number at the left edge of the window. Selecting the entire row in this way selects ALL data including any fields which are currently hidden. If you subsequently copy the data, all data in that record is copied to the clipboard, not just the data in the fields currently displayed. Required Entries Many Task windows have fields which you must enter. For example, if you create a new WBS element in the WBS window, you must supply the WBS ID field. These fields show in the cell and must be filled in before saving the row.

Adding Data To add a new row of information: 1. Click on the row number where you would like to insert the new row. 2. Press the Insert key, or select Insert from the Edit menu. 3. Fill in the fields, and if desired, any optional fields.

4. To save your changes, click the Save button , choose Save from the File menu, or press Ctrl+S. You can also move the mouse pointer off the row, click, and respond Yes to the Save Data prompt.

Editing Data To change existing information: 1. If necessary, use the Horizontal Scroll Bar to show the desired field to be changed. If a field is not displayed, use Column Hide on the Format menu to display hidden field. See topic 3.7.1 Navigating the Task Window for details. 2. Bring the cursor to the desired row by clicking the mouse, using the arrow keys, or using Edit|GoTo. 3. Change the data in one or more editable fields in the current row.

4. To save your changes, click the Save button , choose Save from the File menu, or press Ctrl+S.

Deleting Data To delete an entire row of data in a grid: 1. Highlight the entire row by clicking the row number. 2. Press the Delete key, or choose Delete from the Edit menu. 3. If the Prompt for Save option has been set, MPM prompts for confirmation. To delete more than one row at one time: 1. Highlight the desired rows using Shift when clicking the row number. 2. Press the Delete key or choose Delete from the Edit menu. 3. If the Prompt for Save has been set, MPM prompts for confirmation.

Saving Data To save the data you have entered, do one of the following:

Click the Save button . Choose Save from the File menu or press Ctrl +S. If the Prompt for Save has been set, MPM prompts for verification when you click off the row.

3.7 Introduction to MPM Task Windows 3.7.3 Changing the Display

You can change the display to see only the data you need, which can make your data maintenance much easier. You can change the hierarchical display of the window, select the fields (columns) being displayed, set a filter, select the levels of data shown, and adjust the width and format of the column data.

Controlling Hierarchical Display Some task windows, such as the WBS window, have data which is hierarchical. WBS data, for example, has a hierarchical Tree in which it is created and maintained. You can control the way the WBS Tree is displayed using the expand and collapse check boxes in the left pane of the WBS window. You can expand or collapse the Tree to include only the data you currently need to see.

Displaying and Hiding Fields MPM displays the fields as columns in the Task windows. You can display or hide any or all of the columns, using Column Hide on the Format menu. See topic 3.7.1 Navigating the Task Window for details.

Setting a Filter Some Task windows allow you to set a filter. Setting a filter changes how much data you see in a grid. For example, if you were entering Estimates for WBS 1.X, you would only want to see the Estimates for 1.X, not all Estimates. Filtering your data makes it easy to see only the data you need, which can save you time and help prevent mistakes.

To set a filter, click the Filter button in the Toolbar, or choose Filter from the Tools menu. Some Task windows have many filters to choose from, including WBS identifiers, date ranges, and data elements specific to the Task window. All filters require criteria, meaning the dates in the range, the WBS ID, the element type, or whatever describes how you want to set the filter. When you want to turn off the filter and show all data, choose All Data from the Filter option under the Tools menu. If you want to know if a filter is set and its current setting, look at the Filter option on the Tools menu. If it says Filter: All Data, this indicates that no filter is currently set. If it says Filter: Alias, this indicates that a filter has been set using the Alias field.

Expanding and Collapsing the Data Levels Some Task windows have data which is in a hierarchical format, such as the OBS. Initially, all data levels are shown in the Task window. If you want to see more or less data in the hierarchy, do one of the following. To see the children of a collapsed level, click the parent, and then click the button. To collapse the children of a parent level, click the parent, and then click the button. To see only Level 1 (Top [applet]), click the button. To expand all collapsed levels, click the button. Changing Column Width To change the size of a column, position the cursor at the top of the column along the right edge so that the cursor becomes , and click and drag to stretch or shrink the width as desired. Or

choose Column Width on the Edit menu. The Figure A. Column Width dialog box Column Width dialog appears. You can specify the desired width, choose Best Fit (which scales the column width to an appropriate size), or Cancel or Help.

Changing the Dollar and non-Dollar Formats To change the format of dollar amounts, use Dollars on the Format menu. This option affects display of all dollar values on the right window pane and on the total window. The default is Option 0. Option 0 - 1,235: rounds dollar amounts to the nearest dollar. (default) Option 1 - 1,234.6: rounds dollar amounts to the nearest 10 cents. Option 2 - 1234.56: rounds dollar amounts to the nearest cents. To change the format of non-dollar amounts, use Non-Dollars on the Format menu. This option affects display of all non-dollar values on the right window pane and on the total window. The default is Option 2. Option 0 - 1,235: rounds non-dollar amounts to the nearest digit. Option 1 - 1,234.6: rounds non-dollar amounts to the nearest tenth. Option 2 - 1234.56: rounds non-dollar amounts to the nearest hundredth. (default)

3.8 Setting MPM Options

MPM Options Window MPM has a set of options which are used in all Task windows of MPM.

Click the Options button or choose Options on the Tools menu in any MPM Task window to access the MPM Options dialog box shown in Figure A. This window contains General, Informational, Integrated Planning, GDD, and Security options, which can each be accessed by the appropriate tab on this dialog box. Figure A. Options dialog box General MPM Options There are two General MPM options. These options are used by all Task windows. Save Confirmations Use this option to choose whether you want all data changes to automatically be saved in your project, or whether you want to be prompted before saving changes. This can be useful if you want to be reminded to check your work before saving it. Process Confirmations Use this option to choose whether you want to be prompted every time a process starts, or whether you want a process to start automatically. There are several Task windows which have processes that can take a long time to process. With the prompt on, you will know before a process starts, and if it is an inconvenient time for you, you can cancel the process and run it another time.

Organization Information Options There are two Information MPM options, which are used by MPM to identify your company and project: Organization (Enter the name of the organization for whom you are employed) Program (Enter the name of the program or department of which you are part)

Integrated Planning Options There are two Integrated Planning MPM options: Storage Options Use this option to choose how to save estimate changes: whether to save the changes in the Baseline only, in the Baseline and ETC, or to save the changes in the Baseline and prompt whether to also save them in the ETC. If you are in the initial planning stages of your project, you will probably be saving the Baseline and ETC together; after that, you may find one of the other options helpful. Historical Baseline Change Options Controlling baseline changes on a program is very important and also a challenge when using a live database because of the lack of traceability. To assist in minimizing the number of accidental changes that may occur to historical baseline estimates, MPM offers the “Prompt before saving modifications” options. For instance, if you were changing May forward and accidentally entered data in April…this will alert you that there is an impending change to history if you elect to continue. It gives you the option to Escape before the historical change is made. • Automatically save modifications – this is the default and will save any changes without a prompted warning message. • Prompt before saving modifications – If this option is selected, a warning message will display if historical data is altered giving you the option to cancel or proceed with the change:

• Historical period end month – This date is required if Prompt before saving modifications is selected. It defaults to the current month, but may be changed to reflect Current – 1, (which if this were the May current period, would represent the period of April).

GDD Options There are three GDD (Graphic Drill Down) MPM options: Legends and Labels When generating a graph, choose whether to show WBS IDs, WBS descriptions, or both within the graph. Graph Draw If you have a lot of data or are requesting a complex graph, you can choose to manually redraw your graph; otherwise, GDD automatically redraws the graph. 2D Line Graph Symbols If producing 2D line graphs, choose whether to display symbols for data types.

Security Options There is one MPM Security option: Features. When creating new users, you can choose whether to automatically or manually display the Features dialog box, which can be helpful when entering a lot of data.

Viewing Rollup Toggle Status To view your rollup toggle status, choose Rollup Toggle Status on the View menu in any of the Task windows. MPM displays the dialog in shown in Figure B. For instructions on using the rollup toggle, refer to Chapter 2: Creating and Figure B. Rollup Toggle Status Maintaining Project Settings in the MPM Projects manual.

3.9 Previewing Data

Use Print Preview to preview your data. Access Print Preview by clicking the button or by choosing Print Preview on the File menu. On some Task windows, MPM displays the Print Preview dialog box, which asks additional questions. Figure A shows the Print Preview dialog box from Integrated Planning, which asks whether to include Task Descriptions, and/or Resource BOEs, and allows you to specify a range of dates to be included. If you click OK, MPM displays the Print Preview window, shown in Figure B. Figure A. Print Preview dialog box from Integrated Note that the Preview only shows the columns and data Planning which you have displayed on the Task window. To add additional columns, exit the Preview and choose Hide Columns on the Format menu (see topic 3.7.1 Navigating the Task Window). To change the displayed set of data, exit the Preview and change the data shown in the Task window, either by downloading additional data or changing the onscreen filter.

Preview Options The report heading contains the project name and company name which you entered on the Project Maintenance screen. You can change the Preview’s headers, footers, and other elements of the display using the Preview Option buttons. Changes made to the report’s settings only apply to the current Preview session and are not saved. The Figure B. The Print Preview window showing WBS data function of each button is described in the table that follows.

To: Use these buttons: Scroll the Preview listing forward and backward Next and Previous See details or the entire page Zoom In and Zoom Out Change the Preview listing to display one or two pages One/Two Page Select a new font to be used in the Preview listing Font Change printer selection, orientation, and other printer options Setup Select the page(s) to print, print quality, and other printing Print options Change the text that appears at the top and bottom of each page Hdr/Ftr using the Header/Footer dialog box shown in Figure C Headers and Footers Click the Header button to display the Header Preview dialog box. Click the Footer button to display the Footer Preview dialog box. In both dialogs, any text placed in the Left Header/Footer box is placed on the left section of the Header Figure C. The Header/Footer Preview dialog boxes or Footer (left- justified); Center in the center (centered), and Right in the right section (right-justified). To insert the page number in the Header or Footer box, with the cursor in the desired box, click the Page button. To insert the Date, click Date. To insert the Time, click Time. When you preview or print this page, MPM inserts the current Page, Date and Time wherever you have indicated. Note the placeholders for each (&p, &d, and &t respectively) are inserted wherever the cursor was placed when you clicked the button. These placeholders can also be typed in directly. To close the Preview Window and return to the Task window, click the Close button.

3.10 Printing Data

Use Print to print your data in a list for review. Access Print by clicking the print button or by choosing Print on the File menu. On some Task windows, MPM displays the Print dialog box, which asks additional questions. Figure A shows the Print dialog box from Integrated Planning, which asks whether to include Task Descriptions, and/or Resource BOEs, and allows you to specify a range of dates to be included.

Figure A. Print dialog box from Integrated Planning

If you click OK, MPM displays the Print dialog box shown in Figure B.

Figure B. Windows Print dialog box. This window is the standard Windows Print dialog box for selecting page range, print quality, number of copies, and changing the print setup for your printer. Note that this window is specific to the printer you have currently selected, and may be different from the one shown in Figure B.

When you print, only the data displayed on the Task window will be printed. To add additional columns, exit the Print window and choose Hide Columns on the Format menu (see topic 3.7.1 Navigating the Task Window). To change the displayed set of data, exit the Print window and change the data shown in the Task window, either by downloading additional data or changing the onscreen filter.

3.11 Multi-User Access & Record Locking

In any multi-user environment, it is essential that the software protect the activities of one user from adversely affecting another. In MPM, every Task window employs some form of file/record locking. On a network, MPM automatically implements the file/record locking features.

File-Locking and Record-Locking MPM will file-lock (lock an entire database so that other users cannot access it) when a user runs utilities such as the Estimating Utilities or the WBS Leg utilities or performs other actions which involve the entire database (e.g., importing data/records). Some windows file-lock while the user is saving data. MPM will record-lock (lock a record or row in a database so that other users cannot change that row) when the user chooses to save that row. In most cases, the file or record is locked for only a moment while the update is being made. For example, when you save a WBS record, the WBS database is briefly locked during the save and then released. If locks weren't applied, it would be possible for another user to save the same WBS being entered at another machine. As a result, either a duplicate WBS would then exist or the pointers would become corrupted. If two users attempt to simultaneously update the same data, MPM notifies the current user that another user is adding or editing the same record.

Detail and Header Files Some Task windows file-lock entire databases, even entire projects, for a longer period of time. For example, when an estimate reprice is running, the estimate detail (.RRD) and estimate header (.RRH) files are locked and the locks do not come off until the reprice has finished. The .RRD, .RRH and .WBS files are locked during the following processes: Estimate Reprice Estimate Adjust Date Shift Rebuild Rollup Replanning When MPM gives the "Database Is Busy" message, it means that a user is attempting to lock a file or record which is already locked by another user. This message will continue to display and flash until either the lock is released, or the user presses ESC to abort the attempt. If multiple users are waiting for the same locked file, the first user that attempts to access the file after it is unlocked will get access to the file. There is no "first come first served" queue associated with a locked file. If a network seems excessively busy, it is probably because a user is either running Estimate Reprice or Estimate Adjust.

4 Converting to MPM 3.2

4.1 Converting MPM 2.2, 3.0 and 3.1 Data to MPM 3.2 ...... 94 4.2 Converting the MPM System Files ...... 95 4.3 Converting Global and Project Files ...... 96

4.1 Converting MPM 2.2, 3.0 and 3.1 Data to MPM 3.2

The first user to log into MPM 3.2 will be presented with a dialog box asking them if they want to convert their MPM System files. Once the MPM System files are converted, all project and global files that will be used or opened must be converted to MPM 3.2. The conversion utility allows MPM System Administrators to convert projects and globals individually, several at a time, or all at once. Pre-MPM 2.2 users will need to convert their data to MPM 2.2 prior to running the conversion utility.

Conversion Changes The MPM 3.2 conversion includes the following changes: The files are converted to the Pervasive.SQL V9 file format. Seven additional XRef fields added to the Project Mapping Field descriptions Added Autospread Estimates Added two Audit Trail tables A 450 character Project Description field is added to the proj.dat file. Disk Space Make sure that you have enough disk space to convert the files. To do this, double the size of the files you are converting. For example, (Holiday Calendar 1.4 MB) x (2) = 2.8 MB.

If you have not done so already, we strongly recommend reading topic 2.2 Pervasive.SQL V9 Workgroup Engine in this manual prior to converting.

4.2 Converting the MPM System Files

After backing up all of your system, project, and global files, you will be ready to begin the conversion process. When the first user (not limited to the System Administrator) logs into MPM 3.2, they are presented with the dialog box shown below.

Selecting Yes causes another dialog box to display asking you to confirm that you wish to continue with the conversion. Selecting No does not continue with the conversion of the MPM System files, and the menu manager opens with no tabs visible.

Selecting Yes converts all the MPM System files to the Pervasive.SQL V9 format. Selecting No does not continue with the conversion of the MPM System files, and the menu manager opens with no tabs visible

4.3 Converting Global and Project Files

You will not be able to use any project or global files anywhere in MPM until they are converted. Prior to running the conversion, global paths may be changed in Global Maintenance. However, projects must be converted before any changes are made in Project Maintenance. The conversion utility verifies the file version so it can display the proper conversion status: gray rows have been converted; white rows have not been converted. You must be logged into MPM as a System Administrator or you will not have access to the File Conversion tab. The following procedure will guide you through the file conversion process.

Procedure To convert the global and project files: 1. Log into MPM as a System Administrator to begin the global and project files conversion. 2. From the WINMPM – Menu Manager, click the File Conversion tab.

3. Click the File Conversion icon. A dialog box displays:

4. From the message box, click OK if you want to continue loading the conversion grid or click Cancel if you want to discontinue the file conversion process and return to the File Conversion tab. 5. From the File Conversion window, you will see a list of your files sorted by file type, with global files listed first followed by project files. This easy-to-read grid allows you to pick and choose the files you wish to convert by clicking in the Convert cell to place a check mark next to the project or global you wish to convert. To easily select all project and global files, use the Select All command under the Edit menu.

A blue icon next to a line item indicates that a project or global file has an invalid gateway and cannot be selected for conversion. Please refer to Chapter 2.2 Pervasive.SQL V9 Workgroup Engine for gateway information. A red icon next to a line item indicates that a project or global file does not exist and cannot be selected for conversion. You will not be able to access any file that has not been converted. We strongly recommend that when you convert project files, you convert the corresponding set of global files at the same time.

6. Click the Run Conversion icon on the toolbar. During the conversion process, the status bar will display messages to keep you apprised of the progress. The first message, “Checking Permanent Gateway”, may take several minutes, while the gateway is validated for all selected files. Then the conversion process begins and the status bar displays the files being converted and number of records being processed. Records are processed in groups of 200. 7. During the conversion process, the system logs any errors in the MPMCONV.LOG. This file is stored in the MPM System folder. After the conversion is completed and if there are errors, a dialog displays asking the user if they would like to review the log. If there are no errors after the conversion is completed, no dialog will be displayed. 8. Once the selected project/global files have been converted, they are highlighted in gray.

Figure A. File Conversion screen

Once you convert your files to MPM 3.2, you cannot use the converted files in previous versions of MPM.

5 Data Warehouse

5.1 Introduction to Data Warehouse ...... 100 5.1.1 Workflow Overview ...... 102 5.2 System Requirements ...... 104 5.2 System Requirements ...... 104 5.3 Installation ...... 105 5.3.1 Server: Create the MPM32_DW Database and Tables .... 106 5.3.2 Server: Install the MPM Data Warehouse Controller ...... 110 5.3.3 Server: Configure the Data Warehouse Controller using the Controller.exe.Config File ...... 118 5.3.3.1 DriveInfo ...... 120 5.3.3.2 appSetting ...... 122 5.3.4 Server: Finalize the Data Warehouse Controller ...... 124 5.3.5 Client: Enable the Data Warehouse Scheduler in the MPM Project Maintenance Screen ...... 126 5.3.6 Uninstall Notes ...... 127 5.4 The Data Warehouse Scheduler ...... 128 5.5 The Data Warehouse Database ...... 132 5.6 Synchronization Tables ...... 133 5.7 Data Warehouse Troubleshooting ...... 134

5.1 Introduction to Data Warehouse

The MPM Data Warehouse is a central repository for project and global data from any and all corporate locations. The consolidated data can be used for analysis and reporting as desired. The Data Warehouse consists of the following components:

Microsoft SQL Server schema optimized for MPM data.

MPM Data Warehouse Controller, an application which resides on the database server, or optionally on a separate host machine, and is responsible for managing the importation of MPM data.

MPM Data Warehouse Controller user interface. This interface is located in the MPM Project Maintenance window and is used to select and schedule project and global data for import by the Controller into the data warehouse. The following sections describe the installation and basic workflow of the MPM Data Warehouse. In addition, the MPM Installation CD contains an Entity Relationship Diagram (ERD) in Microsoft Visio version 2003 and 2002 as well as a data dictionary (MPM32_DW.HTML) to aid in designing reporting solutions. They are located in the Data Warehouse Documentation folder.

Planview strongly recommends a review of the entire chapter prior to beginning actual installation.

5.1 Introduction to Data Warehouse 5.1.1 Workflow Overview

TCP/IP MPM 3.2 Server Site 1

1 Controller TCP/IP w/Pervasive.SQL

TCP/IP 2 SSIS MPM 3.2 Server Packages Site 2

SQL Server Database

MPM 3.2 Server MPM Data Warehouse Server Site 3

Typical MPM Data Warehouse Configuration The MPM Data Warehouse extract, translate, and load (ETL) process consists of two components, a Controller and a collection of SQL Server Integrated Services (SSIS) data transformation packages.

1. The controller is a Windows Service component which polls the MPM system folders on regular intervals and initiates the ETL process. It requires the Pervasive engine to be deployed along with it if not already installed. The Controller may be installed on the MPM Data Warehouse Server or optionally on any other machine which has full network access to all MPM Data Server locations along with the MPM Data Warehouse Server. For each MPM system folder the Controller reads an associated Scheduler.dat file and identifies which Projects should be synched and at what interval. The project data is then copied to a temporary repository on the MPM Data Warehouse server for processing by the SSIS packages. 2. The SSIS Package component receives the names and locations of the projects as input for processing. It then establishes a connection to Pervasive, extracts data from the different project related files (WBS, RRH, RRD, BOE etc) and transforms the data, as defined by the SQL Server 2005 database schema. There is one package per project file, i.e., one package for loading WBS, one package for loading BOE, one package for loading Overtime, etc. Note that that there isn’t an exact one to one correlation between individual MPM project files and MPM Data Warehouse project tables. The project tables are optimized for reporting and analysis. See the ERD and Data Warehouse Data Dictionary for further details. Each SSIS Package deletes the existing related MPM Data Warehouse project data first, and then performs a bulk insert. There is no update operation. The delete logic uses the ProjectKey and GlobalKey to delete the project specific data. Once the synchronization is complete, the temporary repository project data and related connections are removed from the MPM Data Warehouse server.

5.2 System Requirements

Data Warehouse server and network environment The minimum requirements for the Data Warehouse server and environment are:

IBM compatible - Dual processor Pentium 2.8GHz or higher

150GB hard disk drive

2GB RAM, (4GB or more preferred.)

Windows 2003 SP1

Pervasive.SQL V9.5 Workgroup Engine (installed on the Data Warehouse Controller machine)

SQL Server 2005 SP1

.NET Framework 2.0

Common network between host MPM data system(s) and Data Warehouse server with connections via TCP/IP

Java Runtime Environment (JRE) Standard Edition (latest version)*

MPM client machines and data

All project and global data must be in MPM version 3.2 format

MPM data and system folder(s) are shared and accessible from the MPM Data Warehouse server.

Java Runtime Environment (JRE) Standard Edition (latest version)*

* Java Runtime Environment: This is only needed if the Pervasive Help and the Pervasive Control Center are to be accessed.

5.3 Installation

The following steps need to be completed in order to successfully install the MPM Data Warehouse:

Server Side Installation/Configuration

Create the MPM32_DW Database and Tables

Install the Data Warehouse Controller

Configure the Data Warehouse Controller service

Finalize the Data Warehouse Controller

Client Side Installation/Configuration

Set up the Project Maintenance Screen for the Scheduler

This section will take you through each of these steps.

5.3 Installation 5.3.1 Server: Create the MPM32_DW Database and Tables

In order to create the MPM database on the Data Warehouse server you need to connect to the SQL Server as the database administrator. Once the connection is established with the SQL Server, follow the steps below to create the database: 1. Right click the Databases folder and select New Database

Figure A: Select New Database 2. Enter the following Database Name: MPM32_DW

Figure B: Enter the Database name 3. Click OK to create the database. 4. Once the database is created run the script ‘MPM 3.2 Data Warehouse Create Table Script.sql’ against the database. This will create the tables and views necessary for the SQL Server Integrated Services (SSIS) Packages. a. Expand the Databases folder. b. Right click the MPM32_DW Database and select ‘New Query.’

Figure C: Select New Query c. In notepad, open the ‘MPM 3.2 Data Warehouse Create Table Script.sql’ script and copy the contents into the New Query Window. This script can be found on the MPM Install CD in the MPM Data Warehouse Create Table Script folder. d. Press F5 to run the script and create the necessary tables and views.

5.3 Installation 5.3.2 Server: Install the MPM Data Warehouse Controller

The Data Warehouse Controller (DWC) was developed using the Integration Services runtime environment and requires this environment to run successfully. The DWC can be run in two different configurations. Single Server: Install the DWC on the same server where SQL 2005 SP1 (with Integrations Services) is running.

Two Servers: Install and run the DWC on a separate server. This will work as long as Integration Services SP1 is installed and running on that machine. Minimum requirements for each configuration Single server solution • Windows 2003 SP1 (Controller is installed • SQL Server 2005 SP1 on the SQL Server) • Integration Services SP11 • NET 2.0 Framework • Data Warehouse Controller service (from the MPM 3.2 CD) • Pervasive.SQL v9.5 (from MPM 3.2 CD)* Two server solution Server 1 • Windows 2003 SP1 (Data Warehouse Controller is installed • SQL Server 2005 SP1 on a server other than Server 2 the SQL Server 2005 • Windows 2003 SP1 machine) • Integration Services SP1 (installed from SQL Server 2005 CD and Service Pack 1 for SQL Server 2005)** 1 • .NET 2.0 Framework • Data Warehouse Controller service (from MPM 3.2 CD) • Pervasive.SQL v9.5 (from MPM 3.2 CD)* * Recommended configuration is as a Windows Service. Set up the service with a user account having read / write access to the MPM system and data folders as well as administrator rights on the machine hosting the Data Warehouse Controller Service. The Pervasive engine should be installed at the local console and not via remote access. ** Running Integration Services on a machine other than where SQL Server is installed may require additional SQL Server licensing. 1 See “Verify whether Integrated Services are Installed” and “Verify whether Integrated Services are upgraded to SP1 or higher” below for further information.

Verify whether Integration Services are Installed Open Computer Management or SQL Server Configuration Management, open SQL Server 2005 Services node. If you've installed SSIS, there should be a service called SQL Server Integration Services. If this service is missing, SSIS is not installed on this machine. Following steps can be followed to upgrade the Integration Services runtime environment: 1. Run the SQL Server 2005 SP1 executable. The setup automatically detects the installed components. 2. Select 'Integration Services' component from the list of components to be installed.

Verify whether Integration Services are upgraded to SP1 or higher 1. Navigate to the SQL Server 2005 installation folder (Example: C:\Program Files\Microsoft SQL Server) and locate the file named 'MsDtsSrvr' under path '\90\DTS\Binn'. 2. Right click on this file and select 'Properties'. 3. Select the Version tab and verify that the File Version is 9.0.2047.0 or higher (9.0.3042.0 for SP2).

Installing the Data Warehouse Controller To install the Data Warehouse Controller open the Data Warehouse Controller folder on the MPM CD and double click on Setup. The installation wizard will guide you through the install.

1. Review system requirements and observe Pervasive limitations.

2. Enter the location of the first MPM database server. If you wish to map a drive to this location or enter subsequent sites (MPM System folders) refer to section 5.3.3 for details of the Controller.exe.config file after completing the Controller installation.

Site Name - enter the name of the site

There is no specific naming convention for Site Names but each site must be uniquely named. Site names are limited to a maximum of 100 characters. Alphanumeric, special characters and spaces are permitted with the exception of single quotes and pipe ( | ). MPM Data Folder Path - enter the UNC path of the MPM System folder. Integrated Service (SSIS) Folder Path - enter the UNC path for the SSIS packages.

Prior to installation, this folder must be shared and the installer must have full control permission. After the install is complete full control permission may be removed, however the folder must remain shared.

The folder path may not point to the DWC folder.

3. The user name and password must be a Database Administrator using SQL Server Authentication, NOT Windows authentication.

4. This completes the Data Warehouse Controller installation.

5.3 Installation 5.3.3 Server: Configure the Data Warehouse Controller using the Controller.exe.Config File

The Data Warehouse Controller is configured using the Controller.exe.Config file. This XML format file is located at the root level of the folder where the Controller is installed. It can be used to specify multiple MPM sites (multiple MPM System folders), polling intervals, and associate drive mappings used by client machines with the UNC path necessary for data transfer between the Data Warehouse server and MPM server(s). This section illustrates the contents of the Controller.exe.Config file and gives examples of common changes made to this file.

Using a standard text editor the file may be modified to add/change MPM Data Server paths as well as change the MPM Data Warehouse polling intervals. Other settings are not normally changed once the Data Warehouse is initially configured. Note that XML tags e.g. , are case sensitive.

Sample Configuration File

M \\ServerA\MPM32TSData SiteA U \\mpmqa2k313\MPM32TSData2 SiteRoot

value="Server=mpmqa2k313;Database=MPM32_DW;User Id=DBA;Password=SimpleOne" />

There are three sections in the above file:

configSections - used internally to define areas of the file. It should not be modified.

DriveInfo - used to specify the Universal Naming Convention (UNC) path for a mapped drive.

appSettings - used to specify MPM Data Server sites as well as the location of other internal required folders. Only the MPM Data Server site information should be modified.

5.3.3 Server: Configuring the Data Warehouse Controller using the Controller.exe.Config File 5.3.3.1 DriveInfo The ‘DriveSection’ node in the configuration file allows mapped drives for Project and Global paths in MPM to be associated with UNC paths used by the Data Warehouse server when transferring data. All mapped drives are defined in the configuration file along with the site name and associated UNC path. The site name and drive letter are used to determine the UNC Path for the mapped drive of a particular site, which allows for situations where multiple sites use the same drive letter for different UNC paths. All mappings must be to existing sites defined in the appSettings section of the config file. For example, SiteA and SiteB could both use drive letter M:\ that is mapped to different servers, MPMServ1 and MPMServ2. During initial installation only the UNC path of the first site is specified and added to the Controller.exe.config file. To add a mapped drive add the drive letter parameter line with corresponding drive label as indicated below. To add an additional mapped drive, add a new node in the as indicated below: M \\ServerA\MPM32Data SiteA

The example shown above indicates there is an M (DriveLetter) drive for site A (SiteA) which points to \\ServerA\MPM32Data (UNC Path). While processing projects on the SiteA site, all M drive mappings in project and global file paths will be replaced with the \\ServerA\MPM32Data path. If the same site has multiple drives, then an entry is added for each mapped drive: M \\ServerA\MPM32Data SiteA Q \\ServerB\WINMPM\WINMPMData SiteA

In the above example the same site SiteA, has drives M and Q. For instances where a mapped drive is not specified in the configuration file, the MPM Data Warehouse Controller uses the Project/Global path as stated in MPM. For example, if the Project/Global path for project SVIIBL4 is set to \\SERVERC\MPM32\DATA\SVIIBL4 in the Project Maintenance screen, then the controller will use this path to copy the Project/Global data for the project. A default drive mapping is provided in the config file. It is mapped to the ‘T’ drive. You may optionally remap to the drive letter of your choice or ignore if drive mapping is not used.

5.3.3 Server: Configuring the Data Warehouse Controller using the Controller.exe.Config File 5.3.3.2 appSetting

The appSetting node of the Controller.exe.config file specifies the parameters necessary for the Controller to interact with the Pervasive.SQL and SQL Server 2005 databases as well as determining the polling interval for reading the Scheduler.dat file. The individual parameters are described below:

DataFolder-SiteName_1 specifies the MPM system folder path for the site designated during installation.

(Optional) DataFolder-SiteName_2, 3 etc, specify additional sites after initial installation.

MinWorkerThreads and MaxWorkerThreads indicate the number of threads used for importing the projects. Since the Controller works in Single Threaded Mode both values are set to 1.

MPMDDF_FolderPath contains the path for the Master DDF files ‘MPMFILE.DDF’, ‘MPMFIELD.DDF’, ‘MPMINDEX.DDF’ used to create the DDF files for the project currently being imported.

PollInterval contains the interval at which the controller will read the Scheduler.dat file. This is in hours .i.e. 3 = 3 hours, .25 = 15 minutes.

ProcessingFolder contains the Install Folder location specified during the installation.

SQLConnectionString contains the connection information for the MPM Data Warehouse SQL Server engine. The database name and the server are both hard- coded.

SQLDSN contains the OLEDB Connection Information for the MPM Data Warehouse SQL Server engine.

SSISPackageDTSConfigPath contains the path for the configuration file used by SSIS Packages.

SSISPackagePath contains the path for the SSIS Master Package file. This file is the starting point of execution for the SSIS Packages.

ControllerServer is the name of the machine hosting the MPM Date Warehouse Controller.

LoadAuditData determines whether audit trail data will be included in the project synchronization. It is off by default. Set to ‘Y’ to include. Note this table could become extremely large depending on the level of audit being performed at the project level.

5.3 Installation 5.3.4 Server: Finalize the Data Warehouse Controller

Once the MPM Data Warehouse server and Controller have been installed and configured the following steps must be accomplished. On the machine which contains the MPM Data Warehouse Controller: 1. Open Control Panel | Administrative Tools | Services. 2. Set up the MPM Data Warehouse Controller Service with a user account having administrator rights to this machine as well as read / write access to the MPM system and data folders. 3. Add a new entry to the server hosts file: a. With Windows Notepad or similar text file editor, open hosts file normally located at C:\Windows\System32\drivers\etc\hosts. b. Add a new line "127.0.0.1 " where is name assigned to machine on which the Data Warehouse Controller is installed. 4. Start the service manually from the server console or preferably set the service to automatic startup and start. Do not start the service via a remote connection.

5.3 Installation 5.3.5 Client: Enable the Data Warehouse Scheduler in the MPM Project Maintenance Screen

By default the Data Warehouse scheduler is not enabled in the MPM client. In order to have access to it, a statement must be added or changed in the MPM Options file. 1. Open the MPMOPT.INI file in notepad. This file is located in the MPM System folder. 2. Change the Scheduler entry to “Y” in the [DataWarehouse] section: [DataWarehouse] Scheduler=Y 3. Save and close MPMOPT.INI

5.3 Installation 5.3.6 Uninstall Notes

To uninstall the MPM Data Warehouse the following must be accomplished:

Controller 1. From the Services applet stop the MPM Data Warehouse Controller. 2. Remove MPM Data Warehouse Controller via the Add | Remove Program applet. 3. Remove Pervasive.SQL (labeled MPM 3.2) via Add | Remove Program applet IF not required for normal MPM data use.

MPM Data Warehouse Database 1. Remove MPM32_DW database according to SQL Server 2005 standard Database delete steps.

MPM 3.2 Workstation On each client machine which is a part of the MPM Data Warehouse configuration: 1. Open the MPMOPT.INI file in notepad. This file is located in the MPM System folder. 2. Change the Scheduler entry to ”N” in the [DataWarehouse] section: [DataWarehouse] Scheduler=N 3. Save and close MPMOPT.INI

5.4 The Data Warehouse Scheduler

Once installed, the primary user interface with the MPM Data Warehouse is the Data Warehouse Scheduler which allows you to set up a schedule for a project’s data synchronization with the Data Warehouse Controller. The scheduler can be accessed by clicking on the Scheduler button in the Project Maintenance screen, or by selecting Tools│Schedule for Synchronization (see Figure A below).

Figure A: Accessing the Scheduler

Setting the Schedule Frequency You can set the schedule frequency to:

Run Immediate - The synchronization will be done immediately after the controller picks up the job. See Section 5.3.3.2 appSetting for information on the controller’s polling frequency.

Daily - You indicate the frequency of the daily run along with the start date, end date and time.

Weekly - User will specify the days of the week when the synchronization should be done along with the start date, end date and time.

Monthly - User will specify the day of month when the synchronization should be done along with the start date, end date and time.

The Synchronization Status Column The Synchronization Status column entry for a specific project in the Project Maintenance screen will be blank until a project is scheduled. Once the project is scheduled, the information in the column will be as follows: Type: (None/Daily/Weekly/Monthly) Status: (Scheduled) Date Time: (MM/DD/YYYY HH:MM:SS)

Note: The Date Time will be blank until the process has run for the first time then it will display the date and time that the schedule last ran.

During the run, the status will change to “Processing”.

After the data is imported for the project the status will be changed to Success/Failure, depending on the import status, and Date Time will contain the next scheduled run. While the actual status will be updated according to the above scenarios, it will be necessary to close and reopen the Project Maintenance screen in order to refresh the status display.

5.5 The Data Warehouse Database

The Data Warehouse database is a SQL Server 2005 database, which contains tables to stage the final data. The Data Warehouse consists of the following information. The tables and views listed below must not be modified. Doing so will cause unpredictable results and may result in corrupt Data Warehouse data. See the Users Guide for sample user views and other information pertaining to the use of the MPM Data Warehouse. Tables: dbo.DM_Audit dbo.DM_Overtime dbo.DM_AuditDollarType dbo.DM_ProgramLog dbo.DM_AuditEstimateType dbo.DM_Project dbo,DM_AuditOperationType dbo.DM_ProjectHeader dbo.DM_AuditRecordType dbo.DM_Resource dbo.DM_BasisofEstimate dbo.DM_Site dbo.DM_Burden dbo.DM_SpreadCurve dbo.DM_BurdenApplyToType dbo.DM_ValueType dbo.DM_BurdenTemplates dbo.DM_WBS dbo.DM_CLIN dbo.DM_WBSBCWPBase dbo.DM_COC dbo.DM_WBSElementType dbo.DM_CostElementType dbo.DM_WBSEVM dbo.DM_EOC dbo.DM_Week dbo.DM_EstimateType dbo.DM_Year dbo.DM_FiscalCalendar dbo.FT_ResourceRollupDetail dbo.DM_Global dbo.FT_ResourceRollupDetailWeekly dbo.DM_HeaderThresholdReportLabels dbo.FT_ResourceRollupEOC dbo.DM_HeaderThresholdsReports dbo.FT_ResourceRollupSummary dbo.DM_LaborLookup dbo.FT_WBSBCWP dbo.DM_Milestone dbo.SSISDetailLog dbo.DM_OBSPerformingDept dbo.SSISMasterLog dbo.DM_OBSResponsibleDept

Views: dbo.View_Burden dbo.View_OBSPerformingDept dbo.View_BurdenRates dbo.View_OBSResponsibleDept dbo.View_BurdenTemplates dbo.View_SpreadCurve dbo.View_CLIN dbo.View.WBS dbo.View_ElementofCost dbo.View_Week dbo.View_HeaderThresholds

5.6 Synchronization Tables

The SSISMasterLog and the SSISDetailLog tables are used to store the status of synchronization where the ProjectID and SiteName are the keys for extracting project specific rows from the details table. These tables contain the following fields: SSISMasterLog EventKey int IDENTITY(1,1) NOT NULL ProjectID varchar (20) NULL LastRunDateTime datetime NULL Status varchar (10) NULL SiteName varchar (100) NULL

SSISDetailLog EventDetailKey int NOT NULL EventKey int IDENTITY(1,1) NOT NULL OperationType(Delete/Insert) varchar (10) NULL PackageName varchar (100) NULL EventDescription text NULL RecordCount int NULL Along with the Controller event log this information is useful for investigating configuration, permissions and performance issues.

5.7 Data Warehouse Troubleshooting

Data Warehouse hangs or displays Btrieve Error 100

If the Data Warehouse hangs or displays a Btrieve Error 100 (No cache buffers are available) when synchronizing some projects, increase the Pervasive Cache Allocation Size setting on the server running the Data Warehouse Controller. Use the following guidelines to determine the appropriate size: If the combined size of the .RRH and .RRD tables or .RRH and .WRD tables is greater than 72 MB, then the Cache Allocation Size parameter should be increased from the default 33554432 bytes (32 MB) to 45% or more of the combined size of the two tables. The Cache Allocation Size of the Pervasive Engine (MicroKernel) • MicroKernel uses this cache when accessing any data files. • MicroKernel uses values that are multiples of 16 KB or 16,384 bytes • Overall performance is usually best when the Cache Allocation Size is a value less than 40% of the physical memory on the system, and the Configuration setting Max MicroKernel Memory Usage is set to a value greater than 40%. Example: RRH = 22 MB RRD = 77 MB Total = 99 MB

45% of 99 MB = 44.55 MB 45.55 MB * 1024 = 45619.2 KB 45619.2 KB * 1024 = 46714060.8 bytes Round to a multiple of 16,384 bytes: 46714060.8 bytes / 16384 = 2851.2 = 2852 (rounded up) 2852 * 16384 = 4660168 bytes In this example, 4660168 bytes is the suggested Cache Allocation Size if less than 40% of total physical memory.

Changing the Pervasive Cache Allocation Size Setting Follow these directions to change the Pervasive Cache Allocation Size setting. From the Data Warehouse Controller (DWC) server console (do not use Remote Desktop or any other remote program):

1. Open the Pervasive.SQL 9 Control Center (PCC). 2. Under Engines, right-click the server name for the server running the DWC and click Properties. 3. Select Performance tuning. 4. Change Cache Allocation Size in byte(s) to the recommended Cache Allocation Size, e.g. 4660168 from the above example. 5. Click Apply. 6. Close PCC. 7. Stop and restart the Pervasive engine on the DWC server (or reboot the DWC server). 8. Try to synchronize the project again.

Index

previewing, 86 A printing, 88 saving, 79 Access Control Requirements, 20 Data access, 67 Adding data, 78 Data entry cells, description, 64 appSetting, 122 Data items, finding, 76 Data levels, expanding and collapsing, 81 Data Warehouse B appSetting, 122 Backups, 14 configure controller, 118 Baseline Planning, 12 Create MPM32_DW database and Buttons and Tool Tips, description, 64 tables, 106 database, 132 DriveInfo, 120 C enable scheduler, 126 finalize controller, 124 C/SCSC Reporting installation, 105 see Government Reporting, 13 introduction, 100 Cancelling processes, 77 scheduler, 128 Check boxes, description, 64 scheduler frequency, 128 Check fields, description, 65 synchronization status column, 131 Choosing a starting view, 73 Synchronization Tables, 133 Column width, changing, 81 system requirements, 104 configure Data Warehouse controller, 118 uninstall, 127 Configuring MPM, 58 workflow overview, 102 Configuring Pervasive Gateway, 22 Deleting data, 79 contacting Customer Support, 9 Detail and header files, when locked, 91 controller (Data Warehouse) Displaying and hiding fields, 77 configure, 118 Dollar formats, changing, 81 finalize, 124 DriveInfo, 120 Converting Global and Project files, 96 Drop-down list boxes, description, 65 Converting MPM 2.2 to MPM 3.1, 94 Converting MPM 3.0 to MPM 3.1, 94 Converting the MPM System Files, 95 E Create MPM32_DW database and tables, 106 Editing data, 79 Creating Valid User List, 58 enable Data Warehouse scheduler, 126 Customer Support, contacting, 9 Estimates to Complete, 12 Expanding and collapsing data levels, 81 D F Data adding, 78 Fields, displaying and hiding, 77 deleting, 79 File Conversion Utility, 94 editing, 79 File locking, 90

Files MPM backing up, 14 checking the configuration, 58 Filtering downloads by introduction, 12 Element Type, 73 Security, 13 WBS legs, 72 MPM options, setting, 82 WBS Manager, 73 GDD options, 84 Filters, setting, 80 General options, 82 finalize Data Warehouse controller, 124 Historical Baseline Change options, 83 Finding data items, 76 Integrated Planning options, 83 Organization Information options, 82 G Security options, 84 MPM System Files, converting, 95 GDD options, setting, 84 General options, setting, 82 N Global and Project files, converting, 96 Government Reporting Non-Dollar formats, changing, 81 overview, 13 O H On-line Help, accessing, 65 Help, On-line, accessing, 65 Open dialog box, using, 72 Hierarchical displays, controlling, 80 Organization Information options, setting, Historical Baseline Change options, 82 setting, 83 P I Password, 66 installation Password, changing, 67 Data Warehouse, 105 Performance Measurement, 12 Integrated Planning options, setting, 83 Pervasive Gateway Configuration, 22 Introduction Previewing data, 86 Data Warehouse, 100 Printing data, 88 MPM, 12 Processes, cancelling, 77 Pull-down menus, 70 L R List boxes, description, 65 Logging in, 66 Radio buttons, description, 65 Logging out, 66 Record locking, 90 Rollup Toggle status, viewing, 84 M S Menu Manager changing the view, 71 Saving data, 79 using, 70 scheduler (Data Warehouse), 128 Menu options enable, 126 choosing with a mouse, 71 scheduler frequency (Data Warehouse), choosing with the keyboard, 71 128

Security window panes Overview, 13 scrolling, 75 Security options, setting, 84 selecting rows and columns, 75 Selecting data to download, 72 sizing, 75 Starting view, choosing, 73 using, 75 Subdirectory Organization, 58 Technical Support, contacting, 9 synchronization status column (Data Warehouse), 131 U Synchronization Tables (Data Warehouse), 133 uninstall Data Warehouse, 127 system requirements User ID, 66 Data Warehouse, 104 V T View Tabs, function, 70 changing in Menu Manager, 71 Task windows hiding, 75 introduction, 74 W moving, 75 workflow overview, 102 navigating, 76 sizing, 75