Definition
First activation time is when plan charges begin after an IoT SIM is activated. It can be immediate, or it can wait until first use. That choice drives data billing, the plan period, and how long a resource sits idle. The IoT Cloud Platform stores it on the SIM product or on the project. It does not set how many days the SIM has in which to be activated.
The two starts
- Immediate: Charges start as soon as the SIM is activated, and the plan period starts at that moment. This fits a project that deploys in bulk and expects the SIM online the same day.
- First use: Charges wait until the device attaches for the first time, and the plan period starts then. This fits a pre-installed SIM and plug-and-play, so warehouse time after the device ships does not start the plan.
Beside the activation window
Activation validity says the latest date the SIM must be activated after it is stocked. First activation time says when charges start once that has happened. Together they cover a common case: the SIM must be activated within 90 days of stocking, and activation is set to first use. The device can then sit in a warehouse for months after it leaves the factory, and no plan fee runs until the user attaches for the first time.
Which start fits which sale
A pre-installed SIM, or a device sold with the SIM already in it, is usually first use. The device may sit for months before it reaches the user, and an immediate start would bill that idle time. A bulk project that should be online as soon as it is activated uses immediate. The choice lives on the card activation policy, next to activation validity, so stock and billing are controlled separately. It can differ by SIM product, by project, and by operator.
What to pick
Connected vehicles, shared devices, and consumer electronics that ship with a SIM should use first use, so the plan does not run while the device is still in stock. An enterprise buying for itself, a bulk project, or a “activate and use today” deployment can use immediate, so the resource is billable as soon as it is opened. The choice has to agree with the plan period and with data billing, or the cycle on the bill will not match the rule operations thinks is in force.
Where the monthly cycle actually starts
Immediate start means the plan period begins at activation. First-use start means it begins at the first attach. On a monthly plan, if first use is on day 15, the period runs from day 15 to day 45. The data plan has to state that start, so it matches the first-activation-time rule rather than always assuming the calendar month of activation.
Which attach actually counts as first use
First activation time governs the moment the plan cycle and the charges begin. It does not govern how many days the SIM has in which to be activated. Immediate effect means the moment the activation receipt succeeds is the cycle start. That fits a project whose devices must be online the same day. First-use effect waits for an attach that is accepted as formal, or for a first volume that passes a threshold, and only then does the cycle begin. The threshold has to be written down: any signaling counts, or business traffic must pass a number of bytes. If a production-line test or an accidental registration in the warehouse also counts as first use, a preinstalled SIM has already started drawing the monthly bundle before it leaves the factory. Test traffic should be marked, and it should not push the start. In SimtoLink card activation policy, the start method is stored by product or by project. The activation API only opens the SIM. It does not quietly change the start rule in the same call.
The activation date and the billing-start date are different fields
The date the SIM status becomes activated, and the cycle start on the bill, are allowed to be different days. Under first-use effect, the stretch in between is silent or waiting to start. The SIM may already be able to go online, but the plan days have not begun. If the query page shows only one “activation time,” support will use it to argue with the user about when the plan expires. Show both the time activation completed and the time billing started. Usage before the start also needs a rule: count it as a postpaid test fee, drop it, or deduct it from the included amount after activation. Before dropping it, confirm the operator will not charge the enterprise for that usage. If an immediate-effect SIM is activated at 15:00, a monthly bundle counted by calendar day might run a full month from midnight that day, or from 15:00 to the same moment next month. The two expiry dates differ by a day, and the renewal reminder will be wrong. After the choice is made, the expiry job, the suspend job, and the invoice period use the same expiry function.
When this overlaps activation validity, which deadline arrives first
If activation validity expires while the SIM is still unactivated, the path is reclaim or a flag, and there is no first activation time yet. If the SIM is already activated, configured for first use, and the device has never gone online, the validity job should not take the SIM back, because the activation condition is already met. Some projects mistakenly set both cutoffs to the same number of days, so “must be activated within ninety days” and “must produce traffic within ninety days after activation or be suspended” get tangled in one rule. If the second rule is needed, call it overdue without use. Do not reuse the activation-validity job. Changing the plan should not rewrite a first start time that has already occurred. The new plan uses its own cycle from the moment the change takes effect. When historical SIMs are imported, a backfilled start time should also record whether the basis was a usage record or a manual entry, so there is an explanation later for why the cycle began so early. If a backfilled start time is earlier than the activation receipt, a reason is required. Otherwise the billing job uses the receipt time, not the date in the spreadsheet.