Bentley Systems

Service Level Agreement – ProjectWise Design Integration Server

This Service Level Agreement outlines Bentley's commitment to 99.9% system availability for its hosted ProjectWise Design Integration Servers and Identity Management System, detailing terms for SLA updates, subscriber rights, maintenance scheduling, and performance measurement methods while supplementing existing licensing and subscription agreements.

This Service Level Agreement (SLA) applies to Bentley-hosted instances of ProjectWise Design Integration Servers and the Bentley Identity Management System (IMS). The terms and conditions supplement ProjectWise licensing and applicable Bentley subscription program terms. For information regarding Bentley’s security, privacy, and compliance standards, refer to the Bentley Trust Center.

Bentley reserves the right to update and amend this SLA. Updated SLAs become effective:

  • For SELECT and E365 Program subscribers, 30 days following prior notice.
  • For EPS Program subscribers, at the end of the contract term during which the subscriber has been notified of an SLA update.

Subscribers using ProjectWise under an annual subscription term may terminate their subscription immediately following the 30-day notice period for SLA updates.

Availability Commitment

Bentley designs the ProjectWise environment to provide System Availability to the ProjectWise Design Integration Servers and Bentley Identity Management System as follows:

  • Availability Commitment: 99.9%
  • System Availability Period: 24×7

This commitment guarantees that users will be able to log in, navigate, and access documents within the ProjectWise system 99.9% of the time.

Bentley measures performance against the Availability Commitment during a calendar month using the following calculation:

Availability % = (Available Minutes – Unscheduled Downtime Minutes) / Available Minutes
  • Maintenance Windows are published and used to apply required patches to the IT infrastructure. Maintenance may also be used to upgrade ProjectWise software if time allows. Maintenance Windows are scheduled outside of core business hours where practical.
  • The Availability Commitment excludes downtime due to Scheduled Maintenance.
  • Unscheduled Downtime Minutes start from the minute the issue is reported by the Subscriber or detected by Bentley and end when the service is restored.
  • Bentley may subtract from the calculated downtime any time waiting for a response from the Subscriber.
  • Only “Critical” Incidents (see below) are considered as Unscheduled Downtime.
  • Where Bentley provides multiple production services (different URLs), availability is calculated for each URL.
  • Bentley reserves the right to update the software as needed to provide higher quality of service, with best efforts to communicate and conduct updates outside business hours. If an update requires the Subscriber to update ProjectWise client software, that information will be provided as soon as possible.

Remedies

Bentley provides remedies for any documented critical incident where Bentley fails to meet the Availability Commitment during any single calendar month (the “Cover Period”). Upon the first instance per URL, Bentley will make a good faith effort to understand the cause and make reasonable repairs. In addition, Bentley will provide a Service Credit as described below. If the Monthly Subscription covers multiple Fully Qualified Domain Names (FQDNs), the remedy is calculated based on the impacted FQDN, the number of active cloud-hosted users for the given month, and corresponding downtime.

Service Credit Table:

  • Availability 98% — 99.8%: 2% of Monthly Subscription for affected Service
  • Availability 95% — 97.9%: 4% of Monthly Subscription for affected Service
  • Availability Below 95%: 5% of Monthly Subscription for affected Service

Service Credits are applied only against future amounts due in the next billing cycle for Hosting Fees. Service Credits do not entitle the Subscriber to any refund or payment. The Service Credits are the sole and exclusive remedy for failure to meet the Availability Commitment.

In respect of all other claims, losses, or damages, Bentley’s liability shall not exceed the applicable monthly subscription fees during which the event giving rise to the liability occurs.

Support Objectives

Bentley, in consultation with the Subscriber, classifies each reported, verifiable, and reproducible incident per the following:

Priority Classification:

  • Priority 1 (P1) – Critical: System Down – Multiple users at one or multiple sites cannot access the system and no workaround exists.
  • Priority 2 (P2) – High: Users can login and use the system, but there is significant degradation of functionality or performance. Product usage can continue in a restricted fashion, but some important functionality may be unavailable.
  • Priority 3 (P3) – Medium: A non-critical service is not available causing inconvenience, but business operations can continue without major disruption.
  • Priority 4 (P4) – Low: The product or service behavior varies from user expectations, but normal business operations can continue.

The provision of a workaround or temporary fix will reduce the Priority of an incident. Bentley reserves the right to determine the priority classification. “Response Times” and “Resolution Times” commence from the point when accurate and complete information regarding the incident has been communicated and documented within Bentley’s Incident Tracking system.

If the resolution of any P2, P3, or P4 issue requires an update, fix, or patch to Bentley commercial software, additional development, testing, and release tasks may be required. Bentley’s support obligations in these instances are governed by the SELECT Program Agreement or other relevant agreement, not this SLA.

“Day” for support of P2 through P4 incidents is defined as the standard working days of the affected geographic region, excepting Public Holidays.

Incident Response and Resolution Targets:

  • P1 – Critical: Resolution Target: ASAP; Initial Response Target: 1 Hour; Update Interval: 1 Hour
  • P2 – High: Resolution Target: 2 Days; Initial Response Target: 2 Hours; Update Interval: 1 Day
  • P3 – Medium: Resolution Target: 7 Days; Initial Response Target: 4 Hours; Update Interval: 7 Days
  • P4 – Low: Resolution Target: 30 Days; Initial Response Target: 24 Hours; Update Interval: Mutually Agreed

Critical incidents are worked continuously until resolved or an acceptable workaround is delivered.

Response, Resolution, and Update target levels are indicators and serve as benchmarks for Bentley Support teams.

Limitations

This SLA and any applicable Service Levels do not apply to performance or availability issues:

  1. 1.Due to factors outside Bentley's reasonable control (e.g., natural disaster, war, terrorism, riots, government action, or network/device failure external to Bentley’s data centers).
  2. 2.Resulting from the use of services, hardware, or software provided by Subscriber, including inadequate bandwidth or third-party software/services.
  3. 3.Caused by Subscriber’s use of a Service after instruction from Bentley to modify use.
  4. 4.During or with respect to preview, pre-release, beta, or trial versions of a Service, feature, or software.
  5. 5.Resulting from Subscriber’s unauthorized action or lack of action, or from Subscriber’s employees, agents, contractors, or vendors, or anyone gaining access to Bentley network by means of Subscriber’s passwords or equipment, or resulting from Subscriber’s failure to follow appropriate security practices.
  6. 6.Resulting from faulty input, instructions, or arguments (e.g., requests to access files that do not exist).
  7. 7.Resulting from use of sandbox, proof of concept, development, QA, or other non-production systems.

Unless explicitly included by Bentley Systems.

Service Termination and Subscriber’s Data

Upon termination of the Service, Bentley will deactivate any remaining Subscriber accounts and, upon written request, provide an export of Subscriber’s data in a standard, generally accepted electronic form within ten (10) business days, with no restrictions on its use by the Subscriber. Unless otherwise requested, Bentley will delete all copies of Subscriber’s data from its servers within two (2) weeks of being notified that the Subscriber has successfully read the files, or within four (4) weeks of the data being provided if no confirmation or associated Service Request is received.

Note: It may take up to an additional 30 days for backups of that data to expire.