Standardized Implementation of ProjectWise in Multiple Offices Across the EnterpriseJeff Burrill, Federal Aviation Administration

What Did We Do?Deployed ProjectWiseMay – Sept. 2006• ProjectWise installation/configuration• Folders created: ~100,000• Files imported: ~600,000• Currently:

• ~130,000 folders• ~900,000 files

Where Did We Do It?9 Regional Offices• 1 - fully deployed, near standard• 1 - recently deployed, standard• 3 - previously deployed, but stopped• 4 - no previous ProjectWise history

FAA Regions/Offices

Why Did We Do It?We needed a solution• Volumes of electronic files and data• Organizational changes• 9/11• Security• MicroStation standard• Sufficient infrastructure available• Costs, Disparate Systems• History

EDMS History Repeating• 5 previous attempts (at least)• Alternate systems evolved• 9 offices, 9 systems

EDMS: Electronic Drawing Management System

Why ProjectWise?• Cost savings• Drawings vs. documents• Proven• Customizable, Scalable• Easy interface• Features, Security• Integration• Met specification

How did we do it?• On-site installation• Standardized installation/configuration• Localization• Legacy data migration• Training

• Administrators (prior)• Users (during)

Pick A Standard• Standards are great… use them.• The nice thing about standards:

There are so many to choose from!• We need a standard to direct how we deal

with all standards.• De facto standards require no enforcement,

but are difficult to change without enforcement.

Software Standards• Windows 2003 server• Back-up software (local)• Oracle 10g R2• ProjectWise 8.5.1.52 (client & server)• ProjectWise Export/Import Tool

Hardware Standards• Difficult to accomplish• Generally:

• 2 GB RAM• 100 GB HD drive space (RAID)• 100 Mb or 1 Gb LAN (dual NIC preferable)• Backup drives (disk and/or tape)

• New servers bought where needed• Services split across 2 - 3 servers• Servers < 3 years old

Configuration StandardsDeveloped in 2002FAA standards applied to ProjectWise• Environment• Interface• Workflows, Messaging agents, Attribute

mappings, Groups• Folder Structure• Naming conventions

Environment Customization• Automated data population• FAA drafting standards applied• Leveraged SQL and Oracle functions• Look-up tables (w/web editing)• Utilities developed by Bentley:

• Folder creator• Serial number generator• File type detection• Semi-automated data extraction

Deployment• 1 – 2 weeks at each office• Cohesive personnel• General process:

• Installation/configuration• Installation of template database• Population of look-up tables• Created import spreadsheets *• Import files and data *• On-site training (Bentley)

Data Preparation *• Import spreadsheet template• Mapped data fields• Versions/revisions applied• Scrubbed data• Files correlated

* = 800 lb. GorillaLegacy Data is the 800 lb. gorilla• 800/20 rule as applied to data migration• 20% task, 800% time

Recommendations for a large import:• Understand existing data• Develop good test set• Get import sheets right• E/I tool and files on ProjectWise file server

It’s Done! Now What?Back-up• Files• Data

Keep it clean - monitor• Check-outs• Workflows• Audit Trails• Anything else pertinent

Our Future• Digital InterPlot• ProjectWise XM (testing)• Customization (Bentley, SDK)• Work assignment/project management

Lessons Learned• Know everything• Resource availability• Good vs. perfect plan• Beware the cutting edge• Switch and stay• Disable legacy system• Gatekeeper syndrome• Database expertise• Nothing is ever standard• Project is never finished

Staying Out of Trouble•Awareness•Empathy•Courage•Honesty•Politics

We’re Done!We’re just not finished.

QUESTIONS?