> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/the-portal-explained/things-manager/connectivity/m2m-connectivity-configuration.md).

# M2M connectivity configuration

The M2M Connectivity configuration page gives you the opportunity to choose the **communication** and **rate plan** that best suits your application.

#### Cisco synchronisations

For M2M connectivity, the information is synchronised with the source system, **Cisco Control Center**. This **sync** is performed daily. If you’ve made changes directly in Cisco Control Center, the list may show **outdated** information. However, when you view an **individual** connection, the latest data for that item is always retrieved.

You can check when the **last synchronisation** took place by clicking the <img src="/files/9tG2znCN2kI0fuOAYqeI" alt="" data-size="line"> icon.

<div align="left"><figure><img src="/files/26bDzdO5uYlr3KhGDjnt" alt="" width="386"><figcaption><p>Last Cisco sync</p></figcaption></figure></div>

#### Search by ICCID

Use the search field to look up the **ICCID** number of the simcard. If you enter **part** of the number, you’ll get a list of all ICCIDs containing **those** digits.

<div align="left"><figure><img src="/files/gBBsp71EfsFjlShwBkXY" alt=""><figcaption><p>Search field</p></figcaption></figure></div>

#### Open ICCID details

In the Things Portal, we can show you all M2M **details** for an ICCID, such as activation dates, usage, and technical information.

1. Click **anywhere** on the line or the <img src="/files/y9PPmDNZiHvGoyY2Uswa" alt="" data-size="line"> icon at the **end** of the row
2. When the **Cisco** button is available, you can open the ICCID information in **Cisco Control Center** directly from the Things Portal

{% hint style="warning" %}
If you are **not** logged in to Cisco Control Center, you will **first** see a login screen when you click the Cisco button.

If you are **already** logged in, clicking this button will **immediately** open the ICCID in Cisco Control Center.
{% endhint %}

<div align="left"><figure><img src="/files/OY4vkxYQYT81coHZouPN" alt=""><figcaption><p>Open ICCID details</p></figcaption></figure></div>

In the **M2M detail** overview, you will find all the **information** and can adjust **settings**:

1. [Device Summary](#device-summary) Summary of the device linked to the SIM card (optional)
2. [M2M Summary](#m2m-summary) Summary of the ICCID reference and status
3. [M2M Details](#m2m-details) Change the Communication and Rate Plan
4. [M2M Connectivity Configuration](#m2m-connectivity-configuration) View device details and change the device linked to the ICCID
5. [Billing](#billing) Show the billing details for the ICCID
6. [Ownership](#ownership) View the project and linked account details

<div align="left"><figure><img src="/files/6ozUQmVFTR3xBa6f3tFP" alt=""><figcaption><p>ICCID details</p></figcaption></figure></div>

#### Device Summary

In the **Connectivity Details** overview, you can also see the device **linked** to an ICCID. When you click on the device properties, you are automatically redirected to **Device Details**. A more detailed explanation of how this works can be found in [IoT Devices](/kpn-things/the-portal-explained/things-manager/iot-devices.md).

{% hint style="info" %}
For connectivity in a **Tailored** project, linking a device is **optional**. It can be used to keep track of which connectivity is associated with which device. However, the data is handled **outside** the Things Portal, and device management is not mandatory for Tailored projects.
{% endhint %}

Below is a brief description of the **fields** displayed:

1. **Label** This is the name of the device
2. **Barcode** This is the unique identifier of the device, such as a barcode or serial number
3. **Device type** This defines the type of device and determines which decoder is applied
4. **Processing** This shows whether the data is processed and delivered to an endpoint
5. **Flows** This shows which data flow the device is linked to

<div align="left"><figure><img src="/files/vrytofYLAhpFTxpvdaWd" alt=""><figcaption><p>Device Summary</p></figcaption></figure></div>

#### M2M Summary

In the **M2M Summary Details** overview, you see an overview of the current settings of the simcard.

Below is a brief description of the **fields** displayed:

{% hint style="info" %}
For a **Tailored** project, the clickout button <img src="/files/310S1l8guFyDf5mvPj3m" alt="" data-size="line"> to Cisco Control may be available.
{% endhint %}

1. **Cisco** Clickout button to Cisco Control Center
2. **ICCID** This is the unique identifier of the simcard
3. **Connection** This is the status of the simcard
4. **Comm Plan** This shows the current communication plan setting&#x20;
5. **Rate Plan** This shows the current rate plan setting &#x20;

<div align="left"><figure><img src="/files/Hh9Zhnth8fEwJdOpU9Xy" alt=""><figcaption><p>M2M Summary</p></figcaption></figure></div>

#### M2M Details

You can change the simcard settings in the this section. If you are a **Tailored** user and also use **Cisco** for simcard management, you’ll notice that this information is synchronized automatically.

{% hint style="warning" %}
When you change simcard settings directly in **Cisco**, the updated information will be visible in Things Portal **after** the daily [Cisco synchronization](#cisco-synchronisations).
{% endhint %}

<div align="left"><figure><img src="/files/DLYuN7CVdVX9mfDdmqip" alt=""><figcaption><p>M2M Details</p></figcaption></figure></div>

**1. Connection**

This hows the **current** status of the SIM card. You can **change** this status in this menu. Below is an **overview** of the available statuses, their meaning, and when to use them.

<div align="left"><figure><img src="/files/lF0zZT38JnJ4vI8XxFpJ" alt=""><figcaption></figcaption></figure></div>

| Status           | Description                                                                                   | When to use                                                     |
| ---------------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| Activated        | simcard is live and ready for data, voice, or sms services                                    | for simcards actively in use by a customer or device            |
| Activation Ready | simcard is configured and ready for quick activation after exceeding a minimum data threshold | for simcards prepared for deployment or large rollouts          |
| Deactivated      | simcard was active but is now turned off                                                      | for simcards that are temporarily not in use but reusable later |
| Retired          | simcard is permanently disabled and cannot be reactivated                                     | for simcards that are lost, damaged, or no longer needed        |

**2. Last message**

The **Last Message** field shows when data was last received from the SIM card. It provides an indication of whether the SIM is **functioning** correctly or when it was **last used**.

**3. Edit Communication and Rate Plan**

You can use the **pull-down** menus to change the SIM card settings. The available options may vary. If you are a **tailored** customer, there might be custom options designed specifically for your environment.

<div align="left"><figure><img src="/files/KpHlKiaF7ySVmGH2pfVt" alt=""><figcaption><p>Communication and Rate Plan</p></figcaption></figure></div>

{% hint style="success" %}
**Out-of-bundle usage and costs**

This is designed to ensure **continuity** and prevent your device from suddenly **losing** connectivity. This means there is no abrupt internet interruption, and you can **continue** using your device without disruption.

\
Please make sure that out-of-bundle usage remains within **reasonable** limits to avoid unnecessary or unexpectedly high **costs**.

In case you are unsure about the **average** usage of a new device, we recommend **monitoring** its consumption closely to prevent surprises.

\
If usage **exceeds** your bundle, you can always **upgrade** your bundle before the end of the month. In that case, we will charge the cost of the higher bundle, and any out-of-bundle usage incurred **earlier** in that month (before the adjustment) will **not** be charged separately.
{% endhint %}

**4. Communication and Rate Plan information**

These are the **current** settings for this simcard. When you change the communication and rate plan, the **new** settings will appear here.

**5. APN(s)**

The **Access Point Name** (APN) determines which gateway delivers your data traffic. This value cannot be set separately. It is linked to your **communication plan**. When you change the communication plan, the APN shown here may also change. For customers without a **Tailored** subscription, the APN is always kpnthings2m2m, ensuring that traffic is delivered to the **Things Portal**.

#### M2M Connectivity Configuration

In this section, you can **disconnect** a SIM card from a device or **link** it to one. If there are issues with a SIM card, you can insert a different SIM card into the device and **confirm** the swap in the Things Portal.

<div align="left"><figure><img src="/files/memcxg0fJUTrrxTWzmep" alt=""><figcaption><p>M2M Connectivity Configuration</p></figcaption></figure></div>

**1. M2M Connectivity Configuration details**

Here you can **view** the hard configured **details** of the SIM card.

**2. M2M Device Configuration**

The **IMEI** number (International Mobile Equipment Identity) is a unique 15-digit code that identifies your **device**. This number is linked to the device, not to the SIM card.

**3. Unlink SIM card**

This action **disconnects** the SIM from the device. Besides ending the **administrative** link, flows and destinations also stop the delivery of device data.

**4. Switch SIM card**

If you don't want to end a relationship between a SIM and a device but want to link the device to a different SIM, you can use this function to select **another** SIM.

**5. Link  Device**

When a SIM is not **linked** to a device, you can select a device here.

{% hint style="info" %}
&#x20;This option is only **available** if no device is currently linked.
{% endhint %}

#### Billing

Billing shows the current billing **status**, including the start date of connectivity and whether the grace period or minimum term has **passed**.

<div align="left"><figure><img src="/files/ilMM76StINWJ2V5PxuA4" alt=""><figcaption><p>M2M Billing information</p></figcaption></figure></div>

**1. Billing state note**

If it is not immediately clear why connectivity is billed, the note **explains** the reason, for example because a contract term has expired or because it simply became active through usage.

**2. Billable**&#x20;

This section shows whether the SIM is currently **billable**, indicated with a simple **yes** or **no**.

{% hint style="warning" %}
From the **connectivity** list, you can easily filter all **billable** SIMs and recommend deploying these **first** to make sure they are put to use.
{% endhint %}

**3. Shipped date**

This date shows when the SIM was **registered** in the system and for **physical** SIMs, the date on which it was shipped.

**4. Grace period and end data**

The grace period is the **timeframe** within which a SIM becomes **billable** in accordance with the contract. If a grace period applies, you will see its **duration** here and the date on which it will end.

**5. First activation date**

This date indicates when data **usage** was first observed for the SIM.

**6. Minimum term and end date**&#x20;

The minimum term is the **timeframe** within which a SIM stays **billable** in accordance with the contract. If a minimum term applies, you will see its remaining **duration** here and the date on which it will end.

#### Ownership

Ownership shows which account and project in the Things Portal the connectivity **belongs** to.

<div align="left"><figure><img src="/files/uEzdLaUPICTvCWnMdcmD" alt=""><figcaption><p>M2M Ownership</p></figcaption></figure></div>

**1. Things Customer**&#x20;

This is the name of your own Things Portal **client**.

**2. Project**&#x20;

This is the project where the **connectivity** is managed. Each project is linked to a **single** Cisco account or Cisco Customer.

**3. Connectivity provider**&#x20;

This is the connectivity solution **linked** to the project. The provider is **M2M Cisco**, with the account acting as the provider. In most cases, it includes the **name** of the Cisco account, or a combination of the Cisco account and Cisco customer, where applicable.

**4. Cisco Account**

This is the account as it exists within **Cisco**.

{% hint style="info" %}
For a **Tailored** customer, there is always a dedicated, individual account. For **Modular** or **Explorer** customers, this account level is labeled as such, under which a **Cisco Customer** account exists.
{% endhint %}

**5. Cisco Customer**

This is an optional **sub-level** within Cisco accounts.

{% hint style="info" %}
For a **Tailored** customer, connectivity can be grouped within Cisco at this level. For Modular or **Explorer** customers, this level shows the customer account as it is known and linked to the **project**.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kpnthings.com/kpn-things/the-portal-explained/things-manager/connectivity/m2m-connectivity-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.