Table of Contents
The Request
The request originates from Ryder, typically via an email from Pat McNeil to support@decisiv.com, and contains information similar to the following:
"Hello,
Please add the following Ryder location and activate in Vision for all Ryder customers. Email FMSAPS_MMC@ryder.com needs to be added to the location profile.
Location code: 886 = DMS ID Field
Ryder - San Antonio - 3004
927 SBC Center Pkwy
San Antonio, TX 78219
Thank you,
Pat McNeil
Senior Project Manager"
Zendesk Actions
Start by completing the left side of your Zendesk ticket and provide a response to the customer with an expected completion time (complete within 24 business of receipt).
- Set the Brand to ASIST
- Assign it to yourself
- Set it as a Low priority and ticket type to Task
- Set Due Date for 24 business hours (2 days)
- Input the Requester Name
- Reason for Contact = 'New Ryder Location'
- Drop-Down Menus:
- User Type = 'Service Provider'
- Product = 'Portal'
- Portal = 'My Locations'
- My Locations = 'Location Access'
Service Location Creation
The following section details the Portal creation/configuration steps from within the UI itself.
Location ID
Ryder location ID’s are created differently compared to typical ASIST locations. Firstly, the Location ID’s have their own naming convention, which is 'RYDER####' (e.g.: 'RYDER1004').
The number corresponds to the last Ryder shop in the sequence, so our example 'RYDER1004' would be the 1,004th Ryder shop!
This Confluence page shows the naming convention for all major brands today including Ryder and should always be referenced when creating the Location ID itself.
Once the Location ID is established, make sure to take note of it, then continue on to the Portal Creation section below.
Portal Creation
General Info
- On the Dealer Editor page, click the ‘New Dealer’ button on the top right:
- On the Dealer Editor (create new dealer) page, input the following information:
- Location ID: (established using the Location ID section above)
- Name: RYDER - Location City - ####, (e.g. 'Ryder - San Antonio - 3004')
- OEMS: 'VLV'
- Service Networks: 'RYDER'
- Dealer Type: '[PAID] Service Location'
- DMS ID: The 'Location Code' included in the initial request from Ryder
- GROUP ID: '130' (always the same for new Ryder service locations)
- Address1: included in the initial request from Ryder
- City: included in the initial request from Ryder
- State: included in the initial request from Ryder
- Postal Code: included in the initial request from Ryder
- Time Zone: the time zone associated with the City/State of the new location (i.e. Eastern, Central, Mountain, Pacific, etc.).
Services
1. VLV - Enable (1.) Volvo.ASIST, (2.) Portal, and (3.) Insite Reporting:
Modules and Admin Notes
- Decisiv Vision: ENABLED
Save the New Portal
Once the above information is input the location must be saved to lock in the new configurations.
- Click the ‘Save Changes’ button at the bottom of the page.
- Upon saving the location, go back to the Modules and Admin Notes section and you will see a new drop-down at the top of the list called Level. Change the Level from ‘Basic’ to ‘PRO’:
- Click the ‘Save Changes’ button at the bottom of the page once more.
Email Templates
The Email Templates section is updated with the new basic location name (e.g. 'Ryder San Antonio'). The Name field on the Email Templates page does not accept symbols or punctuation and is updated so that the correct name is shown on future automated email correspondence between this service location and other parties.
- Access Pricing for the new location you just created.
- From the All Cases screen of the new location, click (Admin > Email Templates).
- On the Email Templates page, scroll to the bottom of the page, then replace the Default (‘Decisiv’) with the basic location name.
- Click the ‘OK’ button to lock in the changes.
Visibility Settings
Ryder shops should only be visible to a select group of service locations and fleets. The visibility setup is completed via the Edit Location page of a pre-existing Ryder shop. On the Edit Location page for the desired location, click the ‘Visibility’ button on the top right:
On the Dealer Visibility Page:
- Input Dealer ID 'RYDERMMC', then click the ‘+ ADD’ button
- Input Dealer ID 'SAIA', then click the ‘+ ADD’ button
- Input Dealer ID 'CARDINALLOGIST', then click the ‘+ ADD’ button
- Input Dealer ID 'OAKLEYTRANS', then click the ‘+ ADD’ button
- Input Dealer ID 'ASHREDAHEADFL', then click the ‘+ ADD’ button
API User
The API User FMSAPS_MMC@ryder.com must be added to each new Ryder service location (as well as Pat McNeil!) so that Ryder is able to see the new location within the Ryder network.
Since Ryder utilizes our API and not our UI, it is imperative that this user be added to the new location to initialize the API connection!
- In Dealer Editor, search for the new Location ID, then click the Dealer Name
- On the Current Users page, scroll to the bottom and within the Add User section, input FMSAPS_MMC@ryder.com then click the ‘Find User’ button:
- Input the following permissions, then click the ‘Save Permissions’ button:
- Report User
- API Integration Analyst
- Manager
- Dealer Administrator
- Repeat steps (2.) and (3.) above for email address pat_mcneil@ryder.com
Vision
New Ryder locations are added to the existing Ryder account in Decisiv Vision and they must be actively sending data before the request can be resolved.
Vision Data Initiation
For the new service location to start sending data to Vision there must be a case opened under the new portal first. To achieve this, a new case must be created on a test asset.
- From the All Cases screen at the new location, click the ‘Search’ button on the top right.
- On the Search page, search for test Asset SERIAL: BN529468.
- When the asset is returned click the ‘New Case’ button to the right:
- As soon as the new case is created, you will be brought to the case page by default. Immediately close the case by click the ‘Close Case’ button on the top right:
Vision Setup
The following instructions are for the configurations made directly in the Decisiv Vision platform.
- Log into https://vision.decisivapps.com/ with the admin account:
- Email: decisiv@decisiv.com
- Password: (1password vault)
- On the Home page, click the ‘Admin Menu’ button on the top left, then click ‘Manage Accounts’:
- On the Manage Accounts page, find the ‘Ryder’ account, then click on the account name itself:
- On the Ryder configurations page scroll down to the ‘Add Dealer’ field and type in the Location ID of the new Ryder shop you just created (it should automatically be recognized if data is being sent to Vision correctly):
- Once the new Location ID is added, scroll to the bottom right of the page and click the ‘Submit’ button:
Now the new Location ID must also be associated with the main Account Representative. To enable the Location ID for the Account Representative, do the following:
- On the Home page, click the ‘Admin Menu’ button on the top left, then click ‘Manage Accounts’.
- Find the ‘Ryder’ account like before, except this time click the ‘View’ link under the User List column:
- On the Manage Administrators page, click the name ‘Ryder Account Rep (Rep)’:
- On the Ryder configurations page scroll down to the ‘Add Dealer’ field and type in the Location ID of the new Ryder shop you just created (it should automatically be recognized if data is being sent to Vision correctly).
- Once the new Location ID is added, scroll to the bottom right of the page and click the ‘Submit’ button.
Resolution
Once the Portal is set up and is actively sending data to the Ryder Vision account, follow up and resolve the Zendesk ticket.
"Hi <requester first name>
The following location - (<Established Location Name>) has been created utilizing location ID (<Established Location ID>). During setup we have confirmed the following items:
-
- Locations Visibility has been applied for Ryder MMC
- Locations DMS ID has been populated
- Vision has been enabled
- API user has been applied
Please let us know if you require any additional assistance."
Click the 'Submit As Solved' button on the bottom right of the Zendesk ticket to resolve.
Comments
0 comments
Please sign in to leave a comment.