ProjectWise

By audience

BIM Manager

• Enforces one ISO 19650-style CDE across a multi-discipline infrastructure job instead of leaving DGN and DWG sets on project file servers.
• Managed WorkSpaces and WorkSets push a single approved MicroStation configuration to every seat, so seed files, levels and cell libraries do not drift between offices.

Civil Engineering

• Holds the corridor model, cross-sections and reference files together so an OpenRoads or Civil 3D reference never resolves to a stale local copy.
• Data Shortcuts for Civil 3D are created and consumed from inside ProjectWise, which is how shared surfaces and alignments stay controlled on DOT work.

Designer / Drafter

• Check-out locks a DGN to one editor and check-in releases it, which removes the read-only file collision that dominates shared-drive drafting.
• Version history means a superseded sheet can be recovered without hunting for a dated backup folder.

Project Engineer

• Transmittals and submittal packages are assembled from the controlled document set, so what was issued is recorded rather than reconstructed.
• Access control by discipline keeps subconsultant visibility scoped without duplicating the file set.

IT & Systems Administration

• Caching servers replicate the document store to remote offices, which is what makes large DGN sets usable outside the datacentre.
• The Bentley Web Services Gateway REST API allows scripted document and metadata access for internal integration work.

By phase

Design

• Design files are authored directly out of the CDE, so every reference and workspace resolves to the controlled copy for the life of the job.
• Discipline teams work concurrently against one federated document set instead of exchanging periodic file drops.

Pre-Construction

• Issued-for-tender document sets are assembled and locked from the controlled repository, giving a defensible record of what bidders received.

Construction

• Serves current issued drawings and specifications to the site team, with superseded revisions retained but clearly not current.
• Design changes during construction stay versioned in the same repository as the original issue, so the as-built trail is continuous.