Data sharing – agreement and contract creation

The Data Sharing module enables organizations to exchange data related to specific assets (trailer and truck) among different organizations. While sharing data, adherence to GDPR is ensured through value propositions and message configurations.

Business scenarios for sharing asset data #

Rental model

The data provider organization shares data of the rented vehicles with the consumer (rentee) on a short or long-term basis. The rentee can track the acquired assets data.

Inter-fleet collaborations

Two or more fleet companies that collaborate can share data among their organizations.

Workshop fleet coordination

Fleet companies can have a tie-up with a workshop in a specific region, in which case they can share asset information with the fleet workshops. These workshops can monitor the condition or asset status and initiate action if required, for example, in case of a vehicle breakdown.

OEM and fleet coordination

Data can be shared with the OEMs (Original Equipment Manufacturers), who can track the vehicle data, monitor its performance, and check for maintenance. In case of a breakdown or failure, they can determine whether the vehicle is not being used correctly (human error) or whether there is an underlying manufacturing defect.

The provider can share full, partial, or anonymized data to protect the users’ right to privacy.

Data sharing modes #

Sessions are a trigger mechanism for SCALAR to start sharing data to the data consumer organization based on the agreement and (optionally) a contract created by the data provider organization.

A Session manager creates a session to share data with one or more companies through the following modes: multi-level share and further share, also referred to as multi chain share.

Multi-level share denotes sharing data by one company to multiple companies through creation of agreements, contracts, followed by creation of sessions individually by the provider organization as illustrated.

Further share or multi-chain share: Subject to permission, the data consumer company that has received the data through data sharing can further share the data with another company, which is called further share or multi chain share.

The mode selection depends on the business model. Through both the modes, the primary data provider organization retains control over data sharing.

Data sharing documents #

The Contract manager creates the framework agreement and contract to regulate and manage data sharing with different data consumer organizations.

Data sharing application features

• Framework agreements
• Contracts
• Sessions
• OTP (One Time Password)

Create an agreement #

An agreement specifies the agreement details (provider and consumer organization information), assets, data sharing types, and data sharing mode.

1. In the Admin module > click Data Sharing . The Data sharing page is displayed.
   
2. Click the Framework agreements card. The Framework agreements page is displayed.
   
NOTE:
Framework agreements are listed on two tabs:
• Our agreements: agreements created by your organization to share data with a consumer organization.
• Shared with us: agreements that are shared with you by other organizations.
3. Click Create agreement. The Create new framework agreement page is displayed.
   
4. Enter information in the various fields as explained in this table, and then click Continue.
   
NOTE:

To progress to the next section, click Continue. To revert to the previous section, click Back.

Sections and field	Action
Basic details
Agreement name	Assign a name for the agreement
Agreement description	Provide a description of the agreement details
Entity details
Shared entity	Select the shared entity type: Asset or Communication unit
Entity type	Select the asset type NOTE: Currently, asset type selection is implemented for trucks and trailers. In future, asset type implementation will be extended to other vehicles, such as cars, vans, and buses.
Data sharing preferences
Data sharing type	Select the data sharing type model, for example, ‘Rental services’
Further share	Select the required option: Allowed or Forbidden NOTE: Further share allows further data sharing to other organizations by the data consumer organization
Multi share	Select the required option: Allowed, Forbidden, Forbidden with alert NOTE: To control the sharing of asset data with multiple organizations, you can create multiple sessions having similar or overlap duration.
Contracts and value propositions
Contract details	Select the required option to indicate whether contract creation is mandatory under the framework agreement for sessions to be created: Mandatory, Optional, or Not required
Data sharing copy preferences	For each value proposition (explained in the next field description), the associated message services are configured based on GDPR guidelines. Asset and personal data (for example driver details) can be shared with one of the following stakeholders: * Both * Provider only * Consumer only * Both with provider anonymization * Both with consumer anonymization To comply with the default SCALAR Data sharing copy preferences, click Yes. The Override data sharing copy preferences dialog is displayed. Select the checkbox “I consent to share data to both the provider and the consumer organizations” to override the data sharing copy preferences. The data will be shared with the provider and the consumer organizations. You can override data sharing copy preferences at the message service level and at the value proposition level. To configure the copy preferences, you can reach out to the SCALAR Commercial Backoffice (CBO) team.
Value propositions	You can choose to share the asset data with or without defining value propositions. Scenario 1: Data sharing through value propositions In the Value propositions section: * Select Allow all to select all configured value propositions * Select Allow selected to select one or more value propositions The value propositions defined for this organization are displayed. Select the checkbox next to the required value proposition. Concept: Value propositions are customized value packs configured for an organization to enable data sharing. These are predefined custom products for data sharing business configured for the customer. These value propositions are designed specifically based on the customer’s business requirements with the help of the CBO. The data will be shared based on the value propositions selection. Value propositions are configured based on the entity (asset) and data sharing type. For each value proposition, the message services are configured based on GDPR guidelines. For example, messages related to position data can be configured to be shared with the consumer only. Scenario 2: Data sharing without selection of value propositions You can proceed to share data without selection of value propositions: in that case, the Value propositions section will not be displayed. In the Data sharing copy preferences section, for the “Do you want to comply with the default SCALAR Data sharing copy preferences?” question, click No to proceed. The asset data will be shared with both the provider and the consumer organization(s).
Consumer and payer details In this section, the consumer organization is fetched or created and the payer information is selected.
Consumer already exists on SCALAR?	Click Yes or No to indicate whether the customer is registered on the SCALAR platform
Consumer One Time Password (OTP)	If the data consumer organization is already registered on the SCALAR platform, enter the data sharing OTP provided by them, and then click Verify. After the OTP validation, the data consumer organization details are displayed. If the data consumer organization is not registered on the SCALAR platform, they must be onboarded (select No). For more information, see Onboarding a New Data Consumer Organization.
Select consumer	From the list, select an organization with which you already have an active framework agreement On selection of the consumer organization, the Contract manager user name is auto populated.

After entering details in the various sections, click Continue. An acknowledgment message is displayed confirming submission of the framework agreement.

Onboarding a new data consumer organization #

Framework agreement creation for data sharing requires a new data consumer organization to be onboarded or registered with ZF, as explained in this section.

1. On the Add new framework agreement page, scroll through to view the Consumer and payer details section, and then in the Consumer is already existing on SCALAR field, click No.
   
NOTE:

To ensure data privacy, the data provider is set as the organization owner and payer, as reflected in the Organization owner and Payer fields. They will be billed for the (new) organizational subscriptions and data sharing usage.

2. Enter details in the Data consumer details section as explained in this table to onboard the data consumer organization.
NOTE:

This step results in creation of a new organization in SCALAR and a user with administrator
rights.

Available fields

Field	Action
Organization name	Enter the name of the organization for which the new organization and data sharing agreement are to be created
First name	Enter the first name of the data consumer
Last name	Enter the surname of the data consumer
Email address	Enter the email address of the data consumer
Organization profile	Select the required organization profile to apply the configured domain settings to the data consumer (child) organizations In this example, ‘TestProfile2’ profile is selected. NOTE: Organization profiles are created in the Settings module. This feature saves on the manual efforts required to configure the same SSO settings for multiple child organizations. Through this feature, the parent organization can configure an SSO profile (domain and connection settings) as a one-time activity and at a later stage, through Data sharing > Framework agreement. When creating a new consumer organization, these SSO profiles can be reused to copy or apply the entire SSO configurations automatically. Therefore, for data sharing agreements with child organizations, you can apply the same profile, eliminating the need to enter domain settings multiple times. For more clarity, go through the illustration in the next section.
Invitation language	Select the language in which the Welcome email will be composed
Create new Machine-to-Machine integrator	To create an integrator for data sharing, select the checkbox For more information, see Create a Machine-to-Machine integrator for data sharing. NOTE: If the data provider does not opt for the Machine-to-Machine integrator, they can still proceed with the organization creation. The agreement will therefore not contain integrator details.

3. Click Save. A confirmation message is displayed. Click Create and save. The data consumer will receive two emails: an email that contains a link to review the agreement and another email that contains an invitation with a request to complete the account setup.

Illustration

Organization A (parent) enters into a data sharing agreement with organizations B, C, and D (child). Organization A can configure domain settings for child organizations by creating a single profile, e.g. ‘Profile1’. When creating the framework agreement for each child organization, organization A can select and apply profile ‘Profile1’, which reduces manual data entry.

If you need different domain settings for another child organization, create a new profile. For example, for child organization E, a new profile ‘Profile2’ can be created and applied.

For more information on creating and managing profiles, see Settings management.

Create a Machine-to-Machine integrator for data sharing

A data provider organization can access the newly created consumer organization either through the UI or through integrators. An M2M (Machine-to-Machine) integrator can be created while onboarding the consumer to SCALAR.

1. On the Add new framework agreement page, in the Consumer and payer details section, select the Create new Machine-to-Machine integrator checkbox. The New organization creation dialog is displayed.
NOTE:

Select No for the field Consumer already exists on SCALAR? .



2. To confirm the action, click Create and save. The new organization, the Machine-to-Machine integrator, and a user with administrator rights are created. While accessing the organization data through the APIs, the Administrator can start using the integrator details to perform the required operations.

View integrator details

The integrator details: client ID and secret can be viewed on the framework agreement page.

1. On the Framework agreement page, click the required agreement. The agreement page is displayed.
2. In the Organization details section, click View details.
   
   The Integrator details dialog is displayed. Click the menu icon to open the shortcut menu.
   
   • Click Copy to copy the client ID
   • Click Reveal to view the secret

View framework agreements #

On the Framework agreements page, you can view the agreements created by your organization and those shared with your organization.

1. In the Admin module, from the left navigation pane > click Data sharing . The Data sharing page is displayed.
2. Click the Framework agreements card. The Framework agreements page is displayed.
   

Available columns

Column	Description
Agreement name	Name assigned to the agreement
Data sharing type	Business model based on which the data sharing agreement is created, for example, Rental services
Consumer organization	Data consumer organization with which the data is shared
Status	Approval status: Active (Approved or Approval pending) or Inactive (Rejected or Stopped) NOTE: Agreements that are discontinued or rejected become inactive.

Customize column view

You can choose to display or hide columns on the Framework agreements page.

1. On the Framework agreements page > click Columns. The Column display list is displayed.
   
2. To hide columns from the Column display list, clear the checkboxes. The contract list view is rendered based on the selected columns.

Create a contract #

Contract creation is a second-level process and optional. You can specify details, such as asset type, contract validity, and session count in the contract.

1. In the Admin module > click Data Sharing . The Data sharing page is displayed.
2. Click the Contracts card. The Contracts page is displayed.
   
NOTE:
Contracts are listed on two tabs:
• Our contracts: contracts that are created by your organization.
• Shared with us: contracts that are shared by another organization with your organization.
3. Click Create contract. The Create contract dialog is displayed.
   
4. From the Data consumer organization list, select the organization for which the contract is to be created, from the Framework agreement list, select the agreement under which the contract is to be created, and then click Continue. The Create contract page is displayed.
   
NOTE:

Basic details such as the framework agreement, data consumer organization, and asset type are filled in in the Basic details section based on the selections made earlier.

The following images are a continuation of the Create contract page.





5. Enter details in the Basic details, Value proposition, and Contract validity sections as explained in this table.

Section and field	Action
Basic details
Contract name	Assign a name for the contract
Contract description	Enter the description of the contract details
Session count	Enter the number of sessions to be created, which effectively denote the number of assets to be shared NOTE: A single session enables the data provider to share data for one asset.
Value proposition	Select a value proposition to be defined in the contract Value propositions are configured for your organization in the Value proposition module by the CBO based on the entity type (for example, Truck) and data sharing type (for example, Rental services). Selection of value propositions while creating sessions will be limited to those defined in the contract.
Contract validity
From date, To date, and Time	Select the date range and time during which the contract will be valid  NOTE: * If the From date is not specified, the contract will start immediately, while if the End date is not filled in, the contract will stay valid and not be discontinued automatically. * The session time will be rounded off to the nearest hour. For example, if the session time is at 7:45 PM, the data sharing session can start at the 7:45 PM. However, the time shown in the app will be 7:00 PM. * The session scheduler is run every five minutes. Therefore, there might be an expected delay in starting the data sharing session. For example, if the session is to start at 7:47 PM, the data sharing can be expected to start from 7:50 PM.

6. After entering information in the various sections, click Save. The contract is created.

View contracts #

On the Contracts page, you can view contracts created by your organization and those shared with the organization.

1. In the Admin module, from the left navigation pane > click Data Sharing . The Data sharing page is displayed.
2. Click the Contracts card. The Contracts page is displayed.

Available columns

Field	Description
Contract name	Name assigned to the contract
Framework agreement	Name assigned to the framework agreement
Data consumer	Organization with which the data is shared
Session count	Number of sessions allowed to be created for the contract
Value proposition	Value proposition assigned to the consumer organization under the contract
Valid from	Date and time stamp from when the contract validity is effective
Valid till	Date and time stamp up to when the contract is valid
Status	Contract status: Active or Inactive NOTE: Contracts that are discontinued or rejected become inactive.

Customize column view

You can choose to display or hide columns on the Contracts page.

1. On the Contracts page > click Columns. The Column display list is displayed.
   
2. To hide columns, from the Column display list, clear the required checkboxes. The contract list view is rendered based on the selected columns.

Generate OTP for data sharing #

For using the Data sharing module, the data consumer organization can enter into a business collaboration agreement with the data provider organization. For agreement creation, the data consumer organization must generate an OTP and share it with the data provider organization.

The OTP is a user authentication code shared by a data consumer to indicate consent for data sharing and to verify the consumer organization information by the provider.

1. In the Admin module, from the left navigation pane > click Data Sharing . The Data sharing page is displayed.
2. Click the Data sharing OTP card. A confirmation message is displayed.
   
3. Click Generate OTP. The data sharing OTP is generated.
   
   
4. Click Copy OTP to copy the OTP to the clipboard and share it with the data provider organization through an official communication channel.

After the Contract manager has created the agreement and optionally, the contract, the Session manager can create sessions to initiate data sharing. The data is transmitted to the data consumer organization until the contract or session validity period.

Extend contract #

The contract validity period can be extended from the Contracts page.

1. Select the contract for which the validity must be extended. The contract information page is displayed.
2. Go to the Contract validity section, and then click the Extend validity link.
   
   The To date and Time fields are now enabled.
   
   
3. Click the To date and the Time fields to select the end date and time of the contract validity.
NOTE:

Only the To date field is enabled. You cannot change the start date of the contract.

4. In the Sessions linked section, select the checkboxes next to the session names to extend the contract validity for one or more sessions. 
5. Click Save. The contract validity period is extended.
NOTE:

The text ‘extension’ is appended to an extended contract. This helps to distinguish between the original and extended contracts. The session count remains the same.



NOTE:

In this example, the first contract is valid till 14-Nov-24. After being extended, its validity is from 14-Nov-24 to 27-Nov-24.

6. After a contract is extended, a session is auto-generated on the Sessions page.



NOTE:

In this image, session ID S1595 is associated with the parent contract, while session ID S1737 is associated with the extended contract.

Stop contract #

Contracts can be discontinued if they are no longer required.

• On the contract information page > go to the Stop this contract section, and then click Stop contract. The parent contract, extended contract, parent sessions, and extended sessions are discontinued. The status of the contract changes to Inactive.
  

Stop agreement #

If a business engagement is to be discontinued, the framework agreement can be stopped.

• On the framework agreement information page > go to the Stop this framework agreement section, and then click Stop agreement. All the contracts and sessions under the framework agreement are discontinued.
  

Role and permissions #

This matrix outlines the responsibilities of the Contract manager and Session manager role and the accompanying permission sets.

Role	Responsibility	Permission
Contract manager	Create framework agreements and contracts	FULL CRUD (create, read, update, and delete) access to Framework Agreements & Contracts (and template)
		READ Sessions
		To support the functionality of the screens, READ access to APIs are required
Session manager	Create sessions under a framework agreement and contract	Full CRUD for sessions
		API read rights on contracts and framework agreements to be able to render the session screens