Guide Purpose:

• This guide IS designed to:
  • Show how to build a profile request in confluence
• This guide IS NOT designed to:
  • Show profile configuration parameters or define the categories within

Understanding a Customers Request

We got a request to build a new profile for a customer. Attached to the email request is the profile request form and an additional note to set the minimum distance between events has 3 ft. For more information on understanding the request form please refer to our guide on Submitting a Profile Request.

1. Review the body type to know what type of truck and line of business we are building this truck for
2. Review the product section to see what products will be added on to the profile as highlighted in the BLUE box
3. Review the Verif-Eye hardware and the calculation type as highlighted in the ORANGE box
4. This section as highlighted in the GREEN box shows if OSV video and contamination video will be enabled
5. The additional information contains any other information needed to complete the profile. Also refer to the email for any additional information
   

Building the New Profile in Confluence

Properties Page

Please refer to our guide on profile configuration in confluence to understand how to get to Customer Fields Trials page to create a new profile in confluence and naming convention for a new profile.

1. CCM ID: This ID will be provided from the system once the profile has been configured. Please reach out to the Dev team to get this ID
2. Status: This should be active to show the profile is going to be in use
3. Environment: Production is used here because this profile will be going on an active vehicle
4. Safety: This will be “ON” since the customer wants Magnif-Eye turned on
5. PSV: Insert the Very-Eye hardware selected in the request here
6. Type: Insert the calculation Type selected in the request here
   

1. Threshold: Since this is a distance calculation and its for an AFL, use the default threshold of 2ft except otherwise stated by the requestor.
2. Tablet to Gateway: This is turned “ON” for every vehicle
3. Contamination: The requestor asked for Purif-Eye video to be turned on, this means contamination will be turned “ON”
4. Heil: This is turned “ON” for every vehicle
5. DM01: This is turned “ON” for every vehicle
6. J1939: This is turned “ON” for every vehicle
   

MCF Configuration

Identify which profile type will be modified creating this new profile based on the request

1. Media Event: This will be changed to modify the service and safety events selected by the requestor. Because this varies, there are no profile selection or confluence link. We use see below for those sections as they will be modified within this confluence being built.
   1. Safety Events are turned on by default.
2. Tablet to gateway: We need to make changes to this profile type since we turn it on for every vehicle
3. Telemetry: The requestor asked we change the minimum distance between events has 3 ft which is not the default Telemetry configuration. This section needs to be changed to reflect the telemetry ICP that will meet the requestors needs.
4. Generic Telemetry: This will need to be changed from the default to the new standard of having Heil, DM01, and J1939 on.
   

1. To make these changes more prominent to the support team, we highlight the background of the sections that needs to change. We do this by selecting the cell options and changing he cell background to subtle GREEN. We will see this being done in the coming pages below
   

Editing Tablet_On MCF Configuration Row

1. Select the Tablet Integration ICP from the ICP profile
2. Select the Tablet_ON ICP profile
3. Copy the confluence link
   

1. Change the profile selection column to reflect the name of the ICP profile selected
2. Insert the confluence link copied form the ICP profile to the confluence link using “Paste in Plain text or ctrl+shift+V”
3. Select the columns changed and use the cell option button to change the cell background color to subtle GREEN
   

Editing Telemetry MCF configuration Row

1. Select the Telemetry ICP from the ICP profile
2. Select the ICP profile that fits the Request
   1. In this case Resi_AFL_ASL_Distance
3. Copy the confluence link
   

1. Change the profile selection column to reflect the name of the ICP profile selected
2. Insert the confluence link copied form the ICP profile to the confluence link using “Paste in Plain text or ctrl+shift+V”
3. Select the columns changed and use the cell option button to change the cell background color to subtle GREEN
   

Editing Generic Telemetry MCF configuration Row

1. Select the Generic Telemetry ICP from the ICP profile
2. Select the ICP profile that fits the Request
   1. In this case J1939_DM01_Heil
3. Copy the confluence link
   

1. Change the profile selection column to reflect the name of the ICP profile selected
2. Insert the confluence link copied form the ICP profile to the confluence link using “Paste in Plain text or ctrl+shift+V”
3. Select the columns changed and use the cell option button to change the cell background color to subtle GREEN
   

Editing Service Event Columns

For more information on the parameters used in the service event section of this profile, please refer to our guide on Understanding Profile Special Configuration Parameters guide.

1. Di1_Active: This is the default port used for service verification if one hardware is installed. since we are using an inclinometer, the recommended stated capture is from Hot to Cold (1 → 0) for an AFL
2. Event Creation: This will be Enabled
3. Camera Image: Specify the cameras that will be used to capture an event image (In this Case Cam 2,3,4,5,6,7, and 8)
4. Camera Video: Specify the PSV and Contamination labelled camera to capture event recordings (In this case Cam 4and 5)
5. Threshold/Special Settings: Insert the Threshold for distance calculation (In this case 2ft)
6. To Blink: This needs to be changed to RED to show then the Inclinometer is triggered
   

1. Service Exception: This is a Tablet to Gateway Event to trigger an exception event from the tablet to the gateway.
2. Event Creation: This will be Enabled
3. Camera Image: Specify the cameras that will be used to capture an event image (In this Case Cam 2,3,4,5,6,7, and 8)
4. To Blink: This needs to be changed to RED to show when service exception is used
   

Editing Telemetry ICP Within the Profile Page

1. Select the Telemetry Page as highlighted in the BLUE box
2. Click the Edit icon (Icon looks like a pen) from the change options as highlighted in the ORANGE box
   

1. Use the “Page to Include” to search for Telemetry ICP that will be used for this profile
2. Select the Telemetry ICP once found
   

1. Telemetry ICP will change to the new selected ICP as highlighted in the BLUE box
   

Editing Generic Telemetry ICP Within the Profile Page

1. Select the Generic Telemetry Page as highlighted in the BLUE box
2. Click the Edit icon (Icon looks like a pen) from the change options as highlighted in the ORANGE box
   

1. Use the “Page to Include” to search for Generic Telemetry ICP that will be used for this profile
2. Select the Generic Telemetry ICP once found
   

1. Generic Telemetry ICP will change to the new selected ICP as highlighted in the BLUE box