SIM for Things Portal
SIM for Things Portal
Breadcrumbs

Enterprise Backend Configuration – Initial Setup

This page describes the default configuration elements that are created for an Enterprise account in the SFT platform and the optional configuration choices a customer can make before integrating its backend systems and portal.

The goal is to explain what exists by default, what can be reused as-is, and what can be customised depending on the customer’s business model.



Default Configuration on Enterprise Creation

When an Enterprise account is created in the SFT platform, a set of default configuration elements is automatically provisioned under the customer’s account. These elements allow the Enterprise to start using the platform without requiring immediate manual configuration.

Service Profiles

Default Service Profile

By default, a Service Profile named DEFAULT is created for the Enterprise account.

This default Service Profile:

  • Includes all services available to the Enterprise (e.g. Data, SMS)

  • Reflects the full service scope granted under the commercial agreement

  • Can be used directly when defining plans and offerings

If Customer X intends to offer all available services to its end customers, this default Service Profile can be used.

Custom Service Profiles (Optional)

Customer X may choose to create custom Service Profiles if it wants to restrict which services are offered.

For example:

  • If the Enterprise has access to Data and SMS

  • But wants to offer Data-only connectivity to travelers

In this case, a new Service Profile can be created containing only the desired services.

Roaming Profiles

Default Roaming Profile

A Roaming Profile is also created automatically for the Enterprise account, with the name DEFAULT.

  • It Includes all network coverage available to the Enterprise

  • it is automatically updated when coverage changes occur

    • New networks added

    • Networks removed

This makes the default Roaming Profile suitable for customers who want:

  • Full coverage

  • Minimal operational maintenance

Custom Roaming Profiles (Optional)

Customer X may create custom Roaming Profiles to limit coverage for specific offerings or use cases.

However, when using custom Roaming Profiles:

  • Coverage updates are not applied automatically

  • Any new network added to the Enterprise coverage must be manually added

  • Removed networks however are automatically been deleted

Because Customer X controls traveler access primarily through Addons, it is generally recommended to:

  • Use the DEFAULT Roaming Profile

  • Control access and eligibility at the commercial level rather than at the coverage level

APN Configuration

A default APN plan is created automatically for the Enterprise account.

This APN plan:

  • Is associated with the default connectivity configuration

  • Can be reused for most standard use cases

  • Does not require modification unless specific APN behaviour is needed

Default Plans

Two default Plans are created for the Enterprise account:

  • DEFAULT POSTPAID PLAN

  • DEFAULT PREPAID PLAN

Both plans:

  • Are linked to the DEFAULT Service Profile

  • Are linked to the DEFAULT Roaming Profile

  • Provide a ready-to-use baseline for endpoint provisioning

These plans can be:

  • Used directly

  • Cloned and customised

  • Extended with Addon Plans depending on the business model

Customer X can modify these two plans to add Notifications, Benefits and Counters

The simplest and most efficient configuration for Customer X is to use the default plans created under the Enterprise account.

Using the default plans ensures that:

  • Travel SIM users have access to all services available to the Enterprise

  • Travel SIM users have access to full network coverage

  • No additional configuration is required at the service or coverage level

Because Customer X intends to control actual traffic usage exclusively through Addon Plans, it is recommended to:

  • Use the DEFAULT PREPAID PLAN

  • Configure all endpoints as prepaid

This approach ensures that:

  • Endpoints can attach to the network

  • Traffic is only allowed when a valid Addon is present

  • The Enterprise is protected from unintended charges outside of purchased add-ons