Favoriot Ecosystem Plan

A Flexible Subscription Framework for Scalable IoT Deployment

The Favoriot Ecosystem Plan is a structured yet flexible subscription framework that enables organisations, universities, system integrators, and enterprises to manage multiple IoT user accounts from a single administrative control point. It is built around date-range subscriptions, centralised account provisioning, and controlled access to dashboards and API features.

This ecosystem approach moves beyond individual account subscriptions and introduces a manager-driven model that provides oversight, scalability, and operational flexibility.

Based on the Product Workshop documentation, the following sections describe how the ecosystem plan operates and what makes it distinctive.

1. Platform Architecture and Access Structure

The ecosystem operates through two clearly separated portals:

• platform.favoriot.com – End-user access (students, developers, engineers)
• manager.favoriot.com – Administrative access for subscription managers

This separation ensures role clarity. End users focus on building, deploying, and analysing IoT data. Managers focus on provisioning, monitoring usage, and controlling subscription validity.

Each subscribed ecosystem package provides one dedicated manager account. If an organisation subscribes to multiple ecosystem packages, they receive multiple manager accounts—one per subscription.

This architecture ensures:

• Logical separation of projects or departments
• Independent subscription control per package
• Clean management of API entitlements per plan

2. Date-Range Based Subscription Model

Unlike conventional fixed 1-year or 3-year bundled contracts, the Favoriot Ecosystem Plan is structured around custom date ranges.

This means subscriptions can be:

• Monthly
• Weekly
• Multi-year
• Custom-defined periods

Validity is defined by a start date and an end date. There is no rigid package duration. The organisation determines the duration of the subscription.

Example:

• Manager subscription validity: 1 January 2026 – 31 December 2026
• Sub-accounts created under this manager must expire within this window.

This flexible model is particularly useful for:

• Universities running semester-based courses
• Training programmes
• Project-based industrial deployments
• Pilot deployments with defined timelines

3. One Manager Account Per Ecosystem Subscription

Each ecosystem package provides:

• One manager account
• Full administrative control over sub-accounts
• Visibility into usage statistics and account activity

If an organisation subscribes to:

• 1 Developer Ecosystem → 1 Manager Account
• 1 Beginner Ecosystem → 1 Additional Manager Account

These are independent and do not overlap.

The manager account is not a tiered beginner account. It is an administrative role focused on control and oversight rather than operational IoT use.

4. Flexible Account Quotas

The ecosystem model does not impose rigid bundle limits, such as default limits of 100 or 200 accounts per package.

Instead:

• Quotas are tied to what has been subscribed.
• Within the quota, managers can create accounts freely.
• If 20 beginner accounts are subscribed, the manager can create up to 20 accounts.
• These accounts can be used by students, developers, or internal teams.

There is flexibility in allocation. If an account expires or is deleted, the manager may reuse the allocation, depending on policy.

5. Account Provisioning Methods

Managers can provision accounts using two methods:

5.1 Manual Creation

Through a form interface requiring:

• Name
• Email (mandatory)
• Contact number
• Country
• User ID
• Password (manual entry or auto-generated)
• Expiration date
• Remarks

Mandatory fields are clearly marked in the system.

5.2 Bulk Upload (CSV/Excel)

For universities or large deployments, managers can:

• Prepare a CSV/Excel file
• Include required fields (Name, Email, User ID, etc.)
• Upload the file
• Automatically generate multiple accounts at once

This bulk approach supports academic cohorts, training batches, and enterprise onboarding at scale.

6. Password and Security Flow

Password management follows a structured process:

1. The manager creates an account.
2. A password can be auto-generated or manually assigned.
3. The manager must save or copy the password during creation.
4. User must perform a password reset via email verification before logging in.

The reset process involves:

• Email verification code
• User-initiated password reset
• Activation of login credentials

This ensures security compliance while maintaining manager oversight.

Managers cannot arbitrarily access user passwords after they are created, preserving basic user security integrity.

7. Expiration Control and Validity Management

One of the strongest features of the ecosystem plan is granular expiration control.

Key principles:

• Sub-account expiration cannot exceed the manager subscription validity.
• Managers may assign shorter validity (e.g., 1 week, 1 semester).
• Expiration can be updated at any time during the subscription window.
• Expiring accounts are visible in dashboard indicators.

The manager dashboard includes:

• Total accounts created
• Active accounts
• Expired accounts
• Accounts nearing expiration

This makes renewal planning easier, particularly for:

• Academic semesters
• Corporate training cycles
• Project-based deployments

8. API Entitlement Based on Plan

API usage is governed by the subscribed ecosystem plan, not by the manager identity.

Each plan carries:

• Specific API entitlements
• Feature availability
• Dashboard capabilities

All sub-accounts under that ecosystem inherit the entitlements of that specific subscription.

This ensures consistent feature allocation across users within the same plan.

9. Public Dashboard Management

Favoriot supports public dashboards under controlled settings.

Important conditions:

• Only dashboards explicitly marked as “public” can be accessed publicly.
• Private dashboards remain inaccessible externally.
• Public dashboards can be shared via URL.
• Manager can copy and distribute the public link.

If an account expires:

• Data accessibility may be affected.
• Live analytics may return errors.
• Previously stored data may remain viewable depending on system behaviour.

Testing is required to fully define post-expiry dashboard visibility rules .

10. Full Manager Control

Manager privileges include:

• Creating accounts
• Editing account details (except password retrieval)
• Assigning expiration dates
• Deleting accounts anytime
• Monitoring API utilisation
• Viewing usage statistics
• Redirecting directly into sub-accounts via management interface

This “full control and access” capability ensures organisations maintain governance over their IoT deployments.

11. Use Cases

11.1 Universities

• Create 20–100 student accounts per semester
• Assign semester-based expiration
• Bulk upload via CSV
• Monitor project progress
• Share public dashboards for grading or showcase

11.2 Corporate Training

• Short-term access accounts
• One-week or one-month validity
• Renewal control
• Centralised oversight

11.3 System Integrators

• Create project-based accounts
• Isolate client deployments under separate ecosystem packages
• Control expiration post-project
• Maintain API-based control aligned with subscription

12. Current Operational Considerations

The workshop discussion identified several areas requiring refinement:

• Clarification of notification email routing
• Public dashboard behaviour post-expiry
• Inability to filter based on the remarks field
• Need for clearer password reset communication workflow

These are operational improvements rather than structural weaknesses.

13. Core Strength of the Ecosystem Plan

The defining characteristics of the Favoriot Ecosystem Plan are:

1. Date-range flexibility
2. One-manager-per-package governance
3. Bulk provisioning capability
4. Plan-based API entitlement control
5. Centralised expiration management
6. Public dashboard sharing mechanism

It shifts from a simple “individual account subscription” model to a managed IoT environment model.

Conclusion

The Favoriot Ecosystem Plan introduces a structured yet adaptable framework for managing IoT users at scale. By separating manager and platform access, allowing flexible subscription durations, and enabling bulk provisioning, it supports educational institutions, enterprises, and system integrators with operational clarity and governance control.

Rather than offering rigid bundles, it provides configurable access windows, granular account control, and plan-aligned API entitlements. This makes it particularly suitable for academic environments, project-based deployments, and scalable IoT programmes.

The ecosystem approach strengthens governance while preserving deployment flexibility, aligning technical infrastructure with real-world operational needs.