Scania Cloud (Input)

​

Links to Relevant Documents

• https://developer.scania.com
• https://developer.scania.com/doc/api-spec/fms/4-rfms
• https://developer.scania.com/doc/api-authentication/fms

​

Connector Overview

​

Core Functionality

• Secure OAuth 2.0 authentication with Scania APIs.
• Automatic vehicle (VIN) discovery after authentication.
• Subscription-aware resource selection.
• Configurable polling intervals for each resource.
• Reliable publishing into Kafka topics.
• Automatic retry, pagination handling, and rate-limit compliance.
• Persistent state tracking across connector restarts.

​

Supported Scania Resources

• Vehicle Status
• Vehicle Position
• Service Planning
• Vehicle Evaluation
• Exceptions
• Driving Time
• Driver Evaluation
• Tachograph Files
• Driver Card Activities

​

How It Works in Condense

1. Authenticate using the Scania Client ID and Client Secret.
2. Fetch all accessible vehicles associated with the account.
3. Select one or more VINs.
4. Configure resources, polling frequency, and destination Kafka topics.
5. Deploy the connector.
6. Condense continuously polls Scania APIs and publishes normalized events into Kafka topics.

​

Prerequisites

• Active Scania Data Access subscription.
• Access to the Scania Developer Portal.
• Existing Kafka topics in the Condense workspace.

​

Configuration

​

Authentication

• Client Secret is always masked.
• Credentials are securely stored.
• Authentication is validated before VIN discovery.
• Connector deployment is blocked if authentication fails.

​

Vehicle Discovery

• Fetch VINs retrieves all vehicles available under the authenticated Scania account.
• VIN selection supports:
  • Search
  • Pagination
  • Select All
  • Manual Refresh

​

Resource Configuration

• Resource Type
• Polling Frequency
• Output Kafka Topic

​

Sample Configuration

{
  "title": "Scania Fleet Connector",
  "clientId": "client_abc123",
  "clientSecret": "********",
  "vins": [
    "YS2R4X20005399401",
    "YS2R4X20005399402"
  ],
  "resources": [
    {
      "resource": "Vehicle Position",
      "pollingFrequency": 60,
      "outputTopic": "scania_vehicle_position"
    },
    {
      "resource": "Vehicle Status",
      "pollingFrequency": 300,
      "outputTopic": "scania_vehicle_status"
    }
  ]
}

​

Deployment

• Initializes polling schedules.
• Starts data collection.
• Publishes events into Kafka topics.
• Tracks connector runtime and health.

​

Monitoring

• Connector Status
• Runtime Health
• Processing Logs
• Event Throughput
• Last Successful Synchronization

​

Troubleshooting

​

Authentication Failed

• Invalid Client ID or Client Secret.

• Verify the credentials generated in the Scania Developer Portal.

​

No VINs Available

• No vehicles associated with the account.
• Subscription not yet activated.

• Verify vehicle subscriptions.
• Retry after subscription activation.

​

Resource Unavailable

• Required Scania subscription is missing.

• Subscribe to the required Scania Data Access package.

​

No Data Published

• Invalid Kafka topic.
• Polling configuration incorrect.

• Verify the output topic exists.
• Confirm polling configuration.

​

Rate Limit Reached

• Polling frequency exceeds API limits.

• Increase polling interval.
• Allow the connector to resume automatically after backoff.

​

Limitations

• Vehicle access is restricted to the authenticated Scania account.
• Data availability depends on active Scania subscriptions.
• Driver-related information may be restricted by Vehicle Keeper policies.
• Subscription changes may take up to 24 hours before becoming available.

​

Best Practices

• Use dedicated Kafka topics for each Scania resource.
• Configure polling intervals according to business requirements.
• Rotate API credentials regularly.
• Monitor connector health and synchronization status.
• Grant the connector only the required API subscriptions.
• Use separate connectors for different fleets or environments when required.