Accruent Staff Deliverable Checklist

Deliverable to be provided by Accruent staff to the Serraview Implementation Manager.

Integration API Setup

Application ID – Confirm Default ID is still valid

DC70CE56-462F-4A08-AA4D-D8D6E019EEEC

360Facility Implementation Manager Deliverable Checklist

Deliverables to be provided by the 360Facility Implementation Manager to both Serraview Staff and the Serraview Implementation Manager.

API Setup

360Facility Domain URL Address - Production -such as https://[client_instance].360Facility.com
360Facility Domain URL Address - Staging – such as https://[client_instance].stage.360Facility.com
360Facility Login User Name and Password (Used to enable the Serraview API to login to 360Facility.)

Configuration

Decision - Will “Priority Enabled” (Serraview displays the Priority selection field) be activated? Yes or No.
Decision - Will “Accruent 360Facility Allow Assignee Selection” be activated? Yes or No.
List of 360Facility Request Subtypes used to send 360Facility Parent Work Orders to Serraview.
List of 360Facility Statuses and the associated mapping to Serraview Statuses

Data Coordination Checklist

Responsible: 360Facility Implementation Manager and Serraview Implementation Manager

Coordination for the items below to be handled by the 360Facility Implementation Manager and the Serraview Implementation Manager.

Building Data

Confirm the intended or loaded Building IDs match in both systems.
Compare the list of the 360Facility Buildings to the Serraview list of buildings.360Facility may have more buildings loaded than in Serraview. A special region needs to be created in 360Facility to restrict the integration to only buildings that are loaded in both systems.

Region Hierarchy

Review the Region Hierarchy for both systems. This is optional and provided for coordination only in case the partner/customer would like the hierarchy to be the same in both systems. Does not affect the integration.

Guest User / People Data

Confirm the intended or loaded 360Facility Guest User / People Data contains one of the identifier methods required to match with the Serraview People Data.

User Data

Deliver list of any 360Facility Full Users that need to be created in Serraview so that the 360Facility Full User can use the hyperlink and login to Serraview.
If the integration workflow is going to be setup to enable direct assignment of a 360Facility (Parent) Work Orders to a Serraview User vs. the use of the generic Integration User, you must compare the 360Facility and Serraview User data to ensure one of the methods required to match is present. This information was provided for thoroughness only as it is not one of the common options represented in the scenario provided in Integration Workflow (Details are found in the 360Facility Work Order Integration document).

Serraview Staff Deliverable Checklist

Deliverables to be provided by Serraview Staff to Accruent Staff.

Configuration Setup

URL of the customer logo file.

Integration API Setup

The following are to be delivered via the API Secure Transfer File (Details are found in the 360Facility Work Order Integration document).

Serraview Domain URL Address – Production.
Serraview Domain URL Address – UAT.
Serraview Service Account ID*
Serraview Private Key*

*These items must be created and resent to Accruent for each environment (Production and UAT) and after each Serraview UAT refresh. For more information, refer to Set up the APIs for Serraview and 360Facility.

Serraview Implementation Manager Deliverable Checklist

Deliverables to be provided by Serraview Implementation Manager to the 360Facility Implementation Manager.

Configuration Setup

No deliverables

Data Load and Serraview User Set

Building Data

Confirm the intended or loaded Building IDs match in both systems.
List of the Buildings loaded in Serraview. (360Facility may have more buildings loaded than Serraview and 360Facility needs to be configured to restrict the integration to only buildings that will be loaded in both systems.)

Region Hierarchy

Provide the intended or loaded Region Hierarchy. This is optional and provided for coordination only in case the customer would like the hierarchy to be the same in both systems. Does not affect the integration.

People Data

Confirm the intended or loaded People Data contains one of the identifier methods required to match with the 360Facility Guest User Data.

User Data

Deliver list of any Serraview Users to be created as Users in 360Facility so they can use the hyperlinks to toggle between systems.

Test Plan for the UAT Environment

Responsible: 360Facility Implementation Manager and Serraview Implementation Manager

Prior to setting up the integration in a Production environment, the integration must first be set up and tested in an integrated testing environment.

Accruent’s term “Staging” is the same as Serraview’s term “UAT environment”.

Prerequisites

Complete the following:

Procedures in the 360Facility Work Order Integration document to set up the UAT environment.
Add a test guest user to both systems.

The Serraview API Service Account and Private Key need to be created after each UAT database refresh following the steps outlined in Setup the APIs (Details are found in the 360Facility Work Order Integration document) which includes the coordination with the Serraview and Accruent teams.

Test Plan

Below is an initial test script based on the scenario described in Integration Workflow (Details are found in the 360Facility Work Order Integration document). This is an end-to-end guide other tests may need to be performed based on the final setup.

You will need to engage the 360Facility Implementation Manager to run through this test with you. Serraview staff do not have access to the 360Facility system, and a 360Facility Implementation Manager will need to perform the indicated steps.

This test plan assumes the users are already familiar with Serraview and 360Facility for their respective organizations and are familiar with the integration steps and configuration.

Test

Expected Results

Create a 360Facility Work Order to send to Serraview

In 360Facility, create a work order on behalf of the Test Guest User, so this user appears as the requestor.

If the work order was not auto assigned to the Integration User, manually reassign it to the Integration User.

In Serraview:

The work order will be received.

In 360Facility:

The Serraview reference number / link will appear, along with the Serraview logo.

Confirm the Serraview Description field is populated

In Serraview:

360Facility Implementation Manager, that the correct values are display in the Description field:

[Date]T[Time],[360 Request SubType], [Requestor], [Requestor Phone], [Buildiing ID] – [Building Name]

There is a character limit, so not all of the above may show.

Confirm the Request Subtype matched a Serraview Request Type

In Serraview:

The Serraview Request Type/Subtype will display.
If the drop-down field is populated with Other, then Serraview did not find a match. Compare the field values with the 360Facility Implementation Manager.
If the drop-down is blank, then the ID associated with the value “Other” is not correct.

Confirm a match on Requestor was found

In Serraview:

In the Contacts section, confirm Serraview found a match for the Requestor.

Confirm a match on Location

In Serraview:

In the Location section, confirm the correct building was selected.

Test the status update and mapping

In Serraview, edit the Service Request and change the status to the first on the list, such as “Acknowledged”. Repeat for each status except for Closed or Work Complete.

Prerequisite

Print out the status mapping configured.

In 360Facility:

Confirm that the status updates were received and mapped to the appropriate status.

Test the Parent Work Order link from Serraview to 360Facility on the Overview tab

In Serraview, from the Overview tab, click the Accruent 360 Facility Link # in the upper right corner of the screen.

In Serraview:

The Serraview User to confirm that the 360Facility sign-in page displays.

The Serraview tester will not be able to sign-in to 360Facility, but you can confirm that the sign in page display, and the URL contains the 360Facility Work Order Number.

Test the Parent Work Order link from Serraview to 360Facility on the Work Orders tab

In Serraview, from the Work Orders tab, click the parent work order # in the upper right corner of the screen.

In Serraview:

The Serraview User to confirm that the 360Facility sign in page displays.

The Serraview tester will not be able to sign-in to 360Facility, but you can confirm that the sign in page appears, and the URL contains the 360Facility Work Order Number.

Test the Parent Work Order link from 360Facility to Serraview

In 360Facility, from the top of the Parent Work Order, click the Serraview SR ID link next to the logo.

From 360Facility:

After the link is selected, the Serraview login page will be displayed.
Similar to clicking a link in Serraview, the user is presented with the login page only; there is no single sign-on.

Create a Child Work Order

In Serraview, from the Work Orders tab, create a Facilities Request.

Select any values.

In Serraview:

Confirm the new work order was added to the Child Work Order grid.
If the Allow Assignee configuration is turned off, then confirm with the 360Facility Implementation Manager that 360Facility correctly auto populated an Assignee.

Update the Child Work Orders in 360Facility

In 360Facility:

· Confirm the Child Work Order was received and is populated with the selected values.

· Tester to add a comment.

· Change the Status (Anything but “Closed”)

· Change the Assignee

· Add costs

· Change the Scheduled for date

In Serraview:

Confirm all of the changes noted updated correctly.

Test the View link for a Child Work Order

In Serraview, click the “View” link of one of the Child Work Orders.

In Serraview:

The Serraview User to confirm that the 360Facility sign in page displays.

The Serraview tester will not be able to sign-in to 360Facility, but you can confirm that the sign in page displays, and the URL contains the 360Facility Work Order Number.

Test closing the Parent Work Order in Serraview – Part 1

In Serraview, from the Overview tab, change the status to “Closed”

Serraview will display following error message: Please correct the following validation errors before continuing: All child work orders need to be closed before the service request can be closed.

Test closing the Parent Work Order in Serraview – Part 2

In 360Facility, close all Child Work Orders for the Parent Work Order being tested.

In Serraview, from the Overview tab, change the status to “Closed”

In Serraview:

The Work Order should successfully save without errors.

In 360Facility:

Confirm the status of the Work Order updated to “Closed”.

Test cancelling a Parent Work Order in 360Facility

· In 360Facility, create a Parent Work.
· In Serraview, create a Child Work Order
· In 360Facility, change the work order status to “Cancelled” or “Entered in Error”

In Serraview:

The Work Order’s status changes to “Canceled”.

Production Go-Live Checklist

The schedule, process and requirements to facilitate going live with the integration will vary per account. This section is a general guide for reference only.

Suggest going live with both 360Facility and Serraview prior to implementing the integration.
Complete all configuration in the Production environments except for the Serraview Integration Setup for 360Facility and any security roles for production users.

In 360Stage / Serraview UAT Environment

Refresh the 360Facility stage and Serraview UAT environments from Production.
Follow the steps in the Serraview Integration Setup for 360Facility to create the Service Accounts and establish the APIs.
Follow the testing steps provided above Test Plan.
Turn over to the partner for UAT workflow review and business process testing.
The 360Facility Implementation Manager or Partner will provide integration training.

In the Production Environments

Make any updates learned from the testing/training in production.
Follow the steps in the Serraview Integration Setup for 360Facility to create the Service Account and establish the APIs.
Partner / customer must approve all testing to see if the APIs are working. (Partner has strict access rules around activity in production. Partner to participate in the Production testing.)
- Identify a specific building approved for testing.
- In 360Facility, restrict the configuration so that no production work orders are accidentally assigned to the integration user.
- Partner or the 360Facility Implementation Manager to alert the assignees for the designated building that testing will to occur. (For both Serraview Parent Work Orders and 360Facility Child Work Orders.)
- Clearly include the text, “Testing please ignore” in all test parent and child work orders.

When it has been determined that the integration is ready

In 360Facility, temporarily disable the Mulesoft configuration on the Integration User to prevent work orders from sending to Serraview until the Go-Live date.
In 360Facility, update configuration such as routing rules and participating regions.
In Serraview, update the Security Roles for the participating users to see the Work Orders tab.
At the designated Go-Live date, the 360Facility Implementation Manger to restore the Mulesoft configuration.