REMINDERCheck in on the

COLLABORATE mobile app

Using Primavera Analytics across multiple remote site locations

Prepared by:Alexander VosDirector of SchedulingPeter Kiewit Sons

A pragmatic approach to remote site connections.

Session ID#: 15474

IntroductionAlexander VosDirector of Scheduling■ Peter Kiewit Sons for 6 years■ From: Oak Ridge, NC■ Live in Omaha, NE■ Experience in both construction field and IT

■ Engineering and Construction■ North America and Australia■ Multiple projects in remote locations

Objectives

■ Explain the tiered environment strategy developed for remote sites

■ How “check in/check out” can benefit this process■ Demonstrate the benefits and understanding of what

analytics is, use cases, and examples

Tiered Environments I-V

Individual Laptop “Tier V”•EPS Tree Matching Corporate EPS

•“Administrator” Profile•Local Database and Client Install

•Limited options for IM maintenance

•No VDI, EPPM, TM, etc

JobSite Server “Tier IV”•Database on Jobsite server•Local client Install•Maintained by IM Dept•No VDI, EPPM, TM, etc•Preferred remote setup

District Office  “Tier III”•Database on District Office Server

•Maintained by IM•No VDI, EPPM, TM, etc•Most uncommon setup

Exception “Tier II”•Same as above•Reserved for anomalies

Main Database “Tier I”•Database in Data Center•EPPM•Client available on Citrix (VDI)•Maintained Corporately•Standard Master Data

REPORTS TO P6 ANALYTICSCHECK IN/OUT FEATURE TO ALLOW ANALYTICS

What does the Tier I environment look like?

This is a subtitle or bulleted list

PrimaveraProfessional (VDI)

XENA

Primavera EPPM (Web 

Based)

Import/ Export

Updates

KMC

EPPM Dashboards

Analytics

Dashboards

BI Publisher REPORTS

Primavera 

Member

Primavera Team 

Member

iOS

HTTP

Context Sensitive Help

Tier I and II Environment

ETL

ODSEnergy

Infrs

Tech/IM

X01

X02

Tiered Environments

■ Tier 1 and Tier 2 – Are different but share the following attributes▪ “Hooked up” to Analytics▪ EPPM, Client on Citrix▪ Inside Corporate Data Center

■ Tier 3 / Tier 4 / Tier 5 – Used for remote sites or areas with remote connectivity and here are the shared attributes▪ Projects checked into Tier I minimum monthly for reporting▪ Kiewit Standardized EPS root possessing a placeholder in Tier 1

for the respective project

Tier V Environment

■ Installed on end user machine referred to “stand alone”■ Individual projects will need to be checked in and checked out

into Tier I Environment▪ Minimum checked in Monthly▪ Allows for Analytics

■ Does not require internet access (except during Check In/Out)▪ Can be checked in while on “turnaround”▪ File can be sent to Corporate to check it in

Tier V Environment Installation Preparation

■ Primavera V7.3 Oracle Stand Alone Data Base with Developer Kit (SDK) installed.

■ Oracle XE Database■ Use the SDK to populate standard master data■ Upgrade Data Base to Primavera Release 8.2.2.1■ Establish upgraded Data Base as “Gold Standard”■ Restore Primavera “Gold Standard” Data Base on end user

machine

What determines if a Tier V environment is needed?■ Internet connection speed

▪ 1800 m/s■ Client requirements

Tier V Environment Schedule Process

Individual Laptop “Tier V”4. Check the file into the database5. Develop schedule with project team6. Matching the update periods, check the schedule back into the Tier I environment

Main Database “Tier I”1. Create EPS node within Standard Structure2. Create Project File with associated master data3. Check the file out of the main database7. “ETL”s will the pick up updated information for analytics and reporting

Has anyone ever used the Check in/out feature?

This is a subtitle or bulleted list

Check ‘it’ Out… or In – What?

■ Schedules can be checked out (exported) so that they can be worked on remotely – a sort of ‘versioning’.

■ Difference between checked out and export – checked out schedules cannot be modified until they are checked back in – regardless of user access.

■ Multiple schedules can be checked out (as an export to an XER) to the same user.

■ Existing schedules can be replaced with the remote copy by using the Check In (import) wizard.

■ As with the export option, baselines are not included.■ A ‘reflection’ schedule cannot be merged into a source

schedule that is checked out.■ Past period actuals cannot be modified when the schedule is

checked out.

Check ‘it’ Out… or In – Why?

■ The Kiewit enterprise structure (library of projects) is the standard for all databases (‘remote’ included)▪ All project schedules

(‘remote’ included) will have their place (EPS node) in the Enterprise Project Structure

▪ Consistency is key for analyses and reporting

Check ‘it’ Out… or In – When?

■ There are two options when checking in (update project or replace project).

■ Update Project – does not delete baselines■ Replace Project – DOES DELETE baselines. However, the

user is warned that all project data will be deleted, including BASELINES.

■ Check Out▪ After ‘initial’ schedule is added, project team has been assigned

■ Check In▪ After schedule baseline is submitted▪ After schedule update has been submitted and approved

Check ‘it’ Out…

■ Open the schedules to be checked out – rules of the XER will apply (i.e. can be multiple files).

■ File menu, Check Out

■ Select the schedule(s) from the Open Projects list. ▪ (Note: The schedule must be

open in order to check it out.)

■ Type the name of the file and the location to save the XER.

■ Click Finish

Check ‘it’ Out… or In – How? (cont.)

■ Select the data to check in by modifying the layout configuration in the Update Project Options dialog box▪ Note: Global data is not

affected by the Delete option

Check ‘it’ Out… or In – How? (cont.)

■ Open the schedules to be checked in

■ File menu, Check in■ Select the file to check in■ Double click the Import Action

field to select how the project data is checked in

■ Click Finish

Check ‘it’ Out… or In – Who?

■ Check Out access▪ User must have Project

Security Profile option, “CheckIn / CheckOutProject”

■ Check In access▪ Users much have Project

Security Profile option, “CheckIn / CheckOutProject”

▪ User must have Global Security Profile option, “Import Global Information”

Analytics

■ Dashboard to manage Tier III-V environments■ Project Code denotes the environment■ Other Project Codes show additional details■ Conditional Formatting shows if the data date is over 60 days

from Data Date

Tier V

Analytics demonstration

Analytics Production Link

This is a subtitle or bulleted list

Please complete the session evaluationWe appreciate your feedback and insight

You may complete the session evaluation either on paper or online via the mobile app