Language Support

The following languages are support for Expedition Professional version 10.0 using Sybase as the database platform:

French Canadian

UK English

US English

The following languages are support for Expedition Professional 10.0 using Oracle as the database platform:

French Canadian

UK English

US English

Russian (International version of Expedition Professional 10.0 only)

Simplified Chinese (International version of Expedition Professional 10.0 only)

Hungarian (International version of Expedition Professional 10.0 only)

Currencies

The following currencies codes are no longer available in Expedition:

ATSITL

BEFIEP

FIMLUF

FRMNLG

DEMPTE

GRDESP

These codes all now fall under the Euro (EUR)

Supported Operating System

Sybase ASA v7.04 database server:

Windows 2000 (all types) SP3 and higher

Windows XP Professional SP1 and higher

Windows Server 2003

Novell Netware version 5

 Oracle 9.2 database server:

Windows 2000 (all types) SP3 and higher

Windows XP Professional SP1 and higher

Windows Server 2003

Sun Solaris 2.8 (Sparc)

Expedition Professional 10.0 Web/Application Server:

Windows 2000 (all types) SP3 and higher

Windows XP Professional SP1 and higher

Windows Server 2003

Client:

Windows 98 SE

Windows 2000 (all types) SP3 and higher

Windows XP Professional SP1 and higher

(Note – Windows NT is no longer supported)

Deployment

Expedition can be deployed to all project team members and even third parties due to its 100% Browser-based interface. Expedition Professional 10.0 has several installation options based on your deployment. These options include:

Stand-alone installation for single users: This option installs the database and Web/application software on one machine for single user access.  

Multi-user installation using a single database and Web/application server: This installation uses a single server containing both the Web/application and database software. This configuration allows users to access Expedition Professional 10.0 using this one centralized server. It is recommended that this configuration only be used for Intranet access and not for Internet access.

Note: This server cannot be used as a client machine.

Multi-user installation using a separate database and Web/application server: This configuration provides optimal system performance and is recommended for Internet access.

Note: These servers cannot be used as a client machine.

Windows Services

If you are running the Sybase version of the database server, it will now automatically be setup as a Windows Service on all Windows Operating Systems.There is no change on Novell servers.

The Expedition Professional Web/Application server will automatically be set up as a Windows Service.

For more detailed information, please refer to the Installation Guide.

Security Settings/User Profiles

Expedition Professional 10.0 provides the enhanced security required to deploy to every project team member.By creating custom security templates, you can specify assign view, add, edit, delete, export rights for each module for each person as well as field level security for critical field modules such as RFIs.These security templates ensure everyone sees only the information they need to without any concerns over exposing private data.

Test Environment

Before installing Expedition Professional 10.0 in a production environment, Primavera recommends setting up a test environment prior to converting live production data.As part of this testing, Primavera recommends that backup copies of your production databases are used in the test environment.This procedure is recommended to ensure your upgrade of live production data proceeds as smoothly as possible.It is strongly recommended that you test all functionality that you use or are planning on using.This includes all reports, forms, emailing,the use of the Letters module and printing.

Considerations and Verifications

After converting test data to Expedition Professional 10.0, it is important to verify key functionality, and become familiar with the many improvements Primavera has made.

Hardware requirements and network architecture

With Expedition Professional 10.0, all project data will be accessed via a browser-based interface.

For this setup a web server and database server are required.The Expedition Professional 10.0 Installation Guide provides minimum hardware requirements for both the web/application server and a Sybase database server.The following are general recommended memory requirements based upon the number of total projects in all databases that are running and the number of concurrent users that will be using the system.These recommendations are based upon performance testing that was done by Primavera.

NOTE: Concurrent users are defined as users actively using the system, not the number of user logged in, number of user ID抯 or amount of serial numbers installed

Hardware memory recommendations for Web/Application server:

1 – 10 users, less than 100 projects512 MB RAM

1 – 10 users, 100 – 750 projects768 MB RAM

1 – 10 users, 750 – 1500 projects1 GB RAM

1 – 10 users, greater than 1500 projects1.25 GB RAM or greater

11 – 50 users, less than 100 projects768 MB RAM

11 – 50 users, 100 – 750 projects1 GB RAM

11 – 50 users, 750 – 1500 projects1.25 GB RAM

11 – 50 users greater than 1500 projects1.50 GB RAM greater

50 – 100 users, less than 100 projects1 GB RAM

50 – 100 users, 100 – 750 projects1.25 GB RAM

50 – 100 users, 750 – 1500 projects1.50 GB RAM

50 – 100 users, greater than 1500 projects1.75 GB RAM or greater

The CPU for the Application/Web Server is recommended to be 2.0 Ghz or higher.

Hardware memory recommendations for Database server: (Sybase)

Total database size less than 250 MB512 MB RAM

Total database size 250 MB- 750 MB768 MB RAM

Total database size 750 MG and above1GB RAM or greater

The CPU for the database server has a direct impact on performance.If the performance of the current Expedition 8.x server is performing to satisfaction, there may be no need to change the CPU.If there are plans to purchase a new database server, Primavera suggests a 2.8 Ghz or higher.A server with multiple processors also provides greater performance.

Oracle: Expedition Professional 10.0 will only work with Oracle version 9.2.
Versions 9.01 and 8.1.7 are no longer supported.

(Expedition 9.0 and Expedition 9.1 can use either Oracle 9.01 or Oracle 9.2) 

Client installation/Requirements

Client workstations will automatically download the Java Runtime Engine (JRE), version 1.4.2_04, from the Expedition Web/Application server.Windows User must have installation rights, Power User or Administrator, to install the JRE.Users are required to have the ability to run REGEDIT.EXE on their workstations.

The client workstation requires enough available RAM to properly display all the data returned to the browser.  Variables to condiser, operating system resource requirements, number of projects contained in the active groups, report and form sizes, other processes active outside of the Expedition requirements.  The varying size of report and form procession will increase the RAM requirement.  Additionally, each project lised in a project tree requires additional RAM to display.  As the number of projects increases, so too does the memory requirements for the client.  In order to determine your requirements, please refer to the following information:

1-1500 projects in a group, 128MB RAM300 Mhz processor (minimum)

> 1500 projects in a group, 256MB RAM400Mhz processor (minimum)

MS Excel XP or greater is required on the client workstation for the Send to Excelfunction

MS Word 2000, MS Word XP or MS Word 2003, are required on the clientworkstation for the Letters module to function using MS Word templates.

NOTE: It is no longer a requirement for the client and the Expedition Web/App Server to have the same version Word.

Email Configuration

An issue faced with configuring SMTP mail to work with Expedition is Corporat Mail/Spam filters that block TCP/IP address without a successful reverse domain lookup.  Some email relays might reject mail from Expedition in the case where the reverse DNS lookup fails. The solution for this is to add the Expedition IP address to the access list on the SMTP relay or to have a valid DNS entry for the Expedition server.

NOTE: There is a known incompatibility between Java and NTLM authentication used in Microsoft’s ISA Proxy Server.At this point Java Applet’s cannot be used in conjunction with ISA’s Integrated Authentication.This problem is not specific to Expedition; all Java 1.4 Applets will have this problem.Basic Authentication or not authenticating users through ISA is the current work around if Microsoft抯 ISA Proxy Server is used.

There is a known issue with using an underscore or any non-alpha numeric character, within the Web Server’s DNS name. Please refer to Solution Number:  200221114935, in the Expedition Knowledge base, for more details

Verify the Change Management Process

Starting with version 9.0 of Expedition, Notices, Requests and Trends will no longer be able to be generated through Change Management.If you are using one of these documents types in your Change Management workflow, you will need to modify your Change Management workflow.Only Proposal and Change Order type documents can be created. In order to accommodate this change, Primavera has increased the number of Proposal and Change Order types to 99.

Change Management records that use Notice, Trends or Requests that were created prior to upgrading will be converted and available in 10.0.You will not lose any data.

Verify cost categories for your existing Contracts and related Change Documents

Expedition Professional 10.0 now provides separate modules for budgeted and committed contracts. Expedition will prompt you to assign cost categories to contracts converted from previous versions of Expedition that have not been assigned a cost category of either budgeted or committed when you open the document. All related change documents are automatically assigned to the selected budgeted or committed category.In addition, if you open a change document that is related to a contract that has not been assigned to either the budget or committed cost category, Expedition will prompt you to select a cost category for the contract.

Verify existing Purchase Orders and related Change Documents

Expedition automatically converts all purchase orders that are not assigned to a cost category to the commitment side. All change documents linked to the purchase orders are also automatically assigned to the same cost category. Purchase orders that were distributed to the budgeted side of the cost worksheet are converted and accessible through the application.

Verify access to existing Funding data

Although the capability to distribute costs directly to a funding cost account is not currently available, those projects using funding in previous versions of Expedition are converted with data viewable through Expedition reports. Funding capability will be implemented in a future Expedition release.

Letters

MS Word 2000, MS Word XP or MS Word 2003 are the formats that are supported for version 10.0.It is no longer a requirement for the Web server and the client machines to all have the same version ofWord installed.

Prompts cannot be used on Letters templates.For example, a FILLIN field added to a letter template in Expedition, will cause a prompt screen to appear on the webserver/application server.This prompt cannot be passed to the client.

Control Center changes

Beginning with version 9.0 of Expedition, Expedition Mobile and Analyzer control center objects and functionality are no longer available.

Schedule integration

Though, you can connect to aP3e/c version 3.51 schedule, it is recommended that you upgrade to version 4.1 and install the latest service pack.The latest service pack for version 4.1 is available through the Primavera Knowledge base.At the time this document was written, the latest service pack for was available via the Primavera Knowledge base in Solution: prim23877 - Primavera Project Management Version 4.1 Service Pack 3

The Primavera Expedition Professional Technical Architecture document for version 10.0 is available through the Primavera Knowledge base.Please refer to Solution Number:PRIM18036