ProjectWise for Utilities Gary Cochrane IMSE – Geospatial Sales NAOU

Agenda Main Topics –ProjectWise Architecture –Competitive Advantages –Future Competitive Advantages 2 |

Agenda Competitive Advantages in Utilities –Legacy Data –Engineering Workflows with Internal Engineering and External Engineering Contractors –CAD Integration MicroStation, AutoCAD, and ESRI –Critical Infrastructure Protection NERC Compliance (for Electric Utilities) –Geo referencing of asset-related documents –Collaboration process featuring Navigator and Dynamic Plot 3 |

Agenda Near-term future Competitive Advantages –Dynamic Composition Service –Transmittals –Integration with eB for Records Management –Mobile access and tablet devices –Point Clouds and Raster streaming 4 |

ProjectWise V8i Overview Part 1 Gary Cochrane IMSE – Geospatial Sales NAOU

ProjectWise is not a product ProjectWise is: –A Brand name representing all Bentley server products –ProjectWise has traditionally referred to Bentley’s solution for Engineering Content Management –With XM (and later editions), it is now a family of products that can be combined to form a solution for Engineering Content Management and Distribution ProjectWise is NOT: –Ironically, ProjectWise is not a project management solution E.g. Primavera, Meridian Prolog, etc.

ProjectWise Mission Statement According to Gary –To organize, manage, and find engineering content Such that content can be leveraged and re-used –To eliminate geographic and time zone barriers And facilitate extended project teams –To manage work processes for extended teams By enabling/enforcing standards, thus improving the quality of project deliverables

Focusing on Content Management ProjectWise provides: –Centralized control of Distributed content In other words, content is stored near the user This approach minimizes the effect of slow network connections –Alternately, ProjectWise can be configured for centralized storage Such that all files are in a single “data center” location Places much more emphasis on network speed, but offers easier administration, and more security

Introducing the modules Each solution comprises one or more of the following server modules –PW Integration Server –PW Caching Server –PW Web Server / Web View Server –PW Publishing Server –PW InterPlot Server –PW Dynamic Plot Server –PW Geospatial Management –PW Oracle Connector –PW ESRI ArcGIS Connector

Geospatial Server A bundled collection of modules to meet needs of typical Utility/Mapping organization –PW Integration Server –PW Caching Server –PW Web Server / Web View Server –PW Publishing Server –PW InterPlot Server –PW Dynamic Plot Server –PW Geospatial Management –PW Oracle Connector –PW ESRI ArcGIS Connector

New Modules for 2012 These modules are not available yet, but expected to ship in 2012 –PW Dynamic Composition Server –PW Transmittals Server –PW Mobile Access Server –PW Streaming Server ?? For Point Clouds and Raster Delivered with SS4, but unsure of pricing/packaging

ProjectWise Integration Server Central component of every ProjectWise solution –Formerly known as PW Application Server –Mandatory; (at least) one in every PW Configuration Possibly more than one in large organizations (defined as greater than 500 simultaneous users) Or possibly more than one to provide redundancy Or possibly more when multiple sites operate independently of each other and don’t want to rely on other sites…

Essential Components Oracle, or Microsoft SQL Server * Not supplied by Bentley In this configuration, all files stored on Integration Server * Via File Storage service

Adding Single Sign-On

Users not prompted for password when logging in to ProjectWise * User authentication via Windows domain / Active Directory

Quote / Proposal Shopping Cart for configuration shown thus far: –Qty (1) PW Integration Server With deployment services –Qty (X) ProjectWise Passport Licenses (Named User client licenses)

Scaling Up As usages grows… –It may become necessary to move file storage to a second server This gives the Integration Server one less job to do –In this case, the configuration would include the ProjectWise Caching Server But only used for File Storage since we are talking about a single site In other words, even though it’s called the Caching Server, it can also act as just a file server

ProjectWise Caching Server Primary function is to provide remote file storage –Formerly known as ProjectWise Distributed File Server And prior to that, known as the ProjectWise File Transfer Server –Provides 3 services File Storage File Caching ProjectWise Gateway Service (more on this later)

Adding Remote Storage

Files may still be stored on Integration Server if desired PW Caching Server enables file storage on remote servers, thus reducing load on the Integration Server

Central Control of Distributed Content Caching Server

Updated Quote / Proposal To previous quote, Add –Qty (1) PW Caching Server w/ deployment services For File Storage separate from Integration Server

Adding Remote sites Remote sites may be supported: –With minimal investment No PW server infrastructure Only add PW Passport licenses for remote clients Typical for small sites –With additional investment for better performance, e.g. PW Caching Server to provide: Remote file storage Remote file caching

Multiple Site support – Entry Point No PW server infrastructure at Site two. Performance will be highly dependent on bandwidth between sites. ProjectWise DFT greatly enhances performance in this scenario

ProjectWise Data Transmission TCP Port 5800, login encrypted, all other transmissions in the clear

Multiple Site support - Better PW Caching Server provides file storage at Site 2. Performance is significantly enhanced for remote users (assuming their files are stored on PW Caching Server2). Local file transfer

Multiple Site Support - Best PW Caching Server provides file storage at Site 2, and file caching for files stored at Site 1. Performance is optimized for Site2 users. PW Caching Server provides file storage at Site 1, and file caching for files stored at Site 2. Performance is optimized for Site1 users.

Caching Server Example S1 C1 S2 C2 FILE-A FILE-B Permanent Storage Temporary Storage

User 2 needs File-B (Local Transfer) S1 C1 S2 C2 FILE-A FILE-B Permanent Storage Temporary Storage

User 2 needs File-A (WAN Transfer) S1 C1 S2 C2 FILE-A FILE-B FILE-A Permanent Storage Temporary Storage

Updated Quote / Proposal To base quote, Add –Qty (2) PW Caching Server w/ deployment services For File Storage (“Better” configuration) For File Caching (“Best” configuration) –Note: You could move the original PW Caching Server from site 1 to site 2 And therefore only need to purchase 1 Caching Server However all files at site 1 would then be stored on the Integration Server again

Clients ProjectWise Explorer is the primary client –Provides richest user experience Intended for Content Creators, or “doers” Must be installed on each machine, thus known as “thick client” ProjectWise also supports login from Web browser clients –Must purchase PW Web Server to enable –Provides subset of PW Explorer functionality Intended for Occasional users, Viewers, and Reviewers –Currently limited to Internet Explorer No Firefox, Chrome, Safari, etc.

PW Web Server / Browser

Adding PW Web Server / Browser In this example, the PW Web Server is available to internal users only. Although not shown, one PW Web Server can serve browser clients at both the local and remote sites

PW Web Data Transmission TCP Port 80, e.g. standard http TCP Port 5800

Updated Quote / Proposal Shopping Cart for configuration shown thus far: –Qty (1) PW Integration Server With deployment services –Qty (2) PW Caching Server With deployment services –Qty (1) PW Web Server With deployment services –Qty (X+Y) ProjectWise Passport Licenses X to cover PW Explorer users Y to cover PW Web browser users No difference in price

Updated Quote / Proposal Note: PW Web server provides: –Basic content management functionality, Log-in, search, modify properties, simple check-out No reference file support, title block support, workspace support, etc. If web users need to view/redline drawings using only a browser, add: –Qty (1) PW Publishing Server With services $$ to integrate with PW Web Client licensing –Web browser users still require a PW Passport

PW Web View Server For strictly Read-only users –PW Web View Server may be more attractive Users may log-in, search, view, etc. Users may not check-out, markup (redline), modify properties, etc. –Browser users accessing PW via Web View Server do *not* require a PW Passport Web View Server is more expensive than Web Server, but client access is free Attractive option if an organization has a large quantity of read- only users 38 |

External Browser Users Within Information Technology, it is common practice to create a network “neutral zone” to support external users –This is a network that can be reached by both internal users and external users –Often referred to as a DMZ This is an accepted term within IT circles –Created by implementing multiple firewalls, or high- end single firewalls

Neutral Zone (DMZ) Configuration In this example, the PW Web Server has been moved into the neutral zone. Internal browser clients may still access PW via the Web Server.

Neutral Zone Configuration

By moving the PW Web Server to the neutral zone, External browser clients may also access PW via the Web Server.

Updated Quote / Proposal Same as previous scenario (from a software perspective) –Qty (1) PW Integration Server w/ deployment services –Qty (2) PW Caching Server w/ deployment services –Qty (1) PW Web Server w/ deployment services –Qty (X+Y) ProjectWise Passport Licenses X to cover PW Explorer users Y to cover PW Web browser users –No difference in Software price However, Bentley will include additional Services $$ in anticipation of DMZ / Firewall issues…

External Users The previous configuration addressed external Web browser users (Content Consumers) –What if an organization needs to provide for external “Content Creators”? The ProjectWise Explorer client is internet-ready However, rarely will the network security policy of an organization accommodate direct access by external users

ProjectWise Gateway service The ProjectWise Gateway service was designed to solve such problems –It acts as a “go-between” the ProjectWise Integration server and external PW Explorer users –This item is not in the Price Book Therefore no software or SELECT fee Included with the purchase of PW Integration Server Only adds implementation services to deploy

External Editor support

One last twist Rather than require a second machine in the DMZ –The ProjectWise Gateway service can be installed on the same machine as the ProjectWise Web Server

External Editor support

Minimizing DMZ Investment

PW DMZ Data Transmission By default TCP Port 5800, all the way through

PW DMZ Data Transmission TCP Port 5800 internal, TCP Port 443/SSL external,

PW Passport client licensing ProjectWise Client licensing is “Named User” –You need one for each user Does not matter if they are PW Explorer users, or PW Web browser users –Client licenses are not “poolable”, “shareable”, or “floatable” Usage is measured based on the number of unique names that access the system Unlike MicroStation, NOT based on peak concurrent usage

Client Licensing Mitigating factors –PW Passport license fee dropped to US MSRP $360 At one time, was $1,000 –Bentley SELECT provides 1 PW Passport for each MicroStation license covered This license is not an owned asset, but a benefit of SELECT If SELECT contract is cancelled, this benefit is forfeited –PW Passport covers access to all Bentley servers Also covers access to desktop applications including: –Bentley Navigator, Dynamic Plot Client, InterPlot Client, and more

Summary This should help you understand common ProjectWise configuration scenarios –This discussion was limited to “ProjectWise Classic” –Next week, we will look at SharePoint and associated Bentley solutions –We will also look at Geospatial components of ProjectWise