Get Started. It's Free
or sign up with your email address
Rocket clouds
Crimson by Mind Map: Crimson

1. Customer UX

1.1. Signup - Get user persona

1.1.1. Persona-customized experience

1.1.2. Get user persona

1.1.3. Email address with link for setting up password -> Onboarding

1.2. Onboarding

1.2.1. (1) Select Stream source

1.2.1.1. ThethingsNetwork

1.2.1.2. Thingsboard

1.2.1.3. AWS IoT

1.2.1.4. Generic HTTP Client

1.2.2. (2) Setup integration keys / fields / guides for integrating the client

1.2.3. (3) Wait for data to be reported

1.2.3.1. (3a) Trigger test telemetry report and show the result

1.2.4. (4) Once data is received, device(s) is/are shown in the parking lot

1.2.5. (5) From the parking log, user can

1.2.5.1. modify a device metadata using the fields in the telemetry report. AUTOMAPPING1

1.2.5.2. System must ask the customer if it wants to apply AUTOMAPPING1 to all the rest of the devices from that stream

1.2.5.2.1. Reference Hevodata

1.2.5.3. Create a container and add the device in. Option to apply to other devices.

1.2.6. (6) View rules that are automatically created

1.2.6.1. User can update

1.2.6.1.1. Thresholds

1.2.6.1.2. Reference Value

1.2.6.2. Show alerts that will be generated once the rule is set to live

1.2.7. (7) Redirect the user to a main dashboard showing

1.2.7.1. Dashboards automatically generated based from containers and type of devices

1.2.7.1.1. Automatically created

1.2.7.2. Number of devices for mapping (parked devices)

1.2.7.3. Warnings/Critical device/containers

1.2.7.4. Estimated monthly cost

1.2.7.5. Limits and actual rates

1.2.7.5.1. Bandwidth utilization

1.2.7.6. Rules

1.3. Account management

1.3.1. See billing reports

1.3.2. Setup billing details

1.3.2.1. Setup credit card details

1.4. Integrations

1.4.1. Stream Source (with downlink)

1.4.1.1. TTI

1.4.1.2. TB

1.4.1.3. Generic HTTP Client 1

1.4.1.4. Generic HTTP Client 2

1.4.2. Stream Destination

1.4.2.1. Elasticsearch

1.4.2.2. AWS IoT

1.4.2.3. AWS S3

1.4.2.4. MongoDB Atlas

1.4.3. Notification Channels

1.4.3.1. Slack

1.4.3.2. Freshdesk

1.4.3.3. Promotexter

1.4.3.4. Pagerduty

1.5. Device Management

1.5.1. Devices

1.5.1.1. List devices

1.5.1.2. Filter by container

1.5.1.3. View telemetry by device

1.5.1.4. Types

1.5.1.4.1. Sensors

1.5.1.4.2. Actuator

1.5.1.5. Mapping Templates

1.5.2. Containers

1.5.2.1. View aggregated telemetry by device

1.5.3. Parking lot

1.5.3.1. List of unknown devices which doesn't fit into any telemetry mapper

1.5.4. Telemetry Mappers*

1.5.4.1. Each device needs a mapper

1.6. Rules

2. Customer Types

2.1. Non-techie but with Xiaomi devices at home/office

2.1.1. Needs onboarding using Xiaomi context

2.1.1.1. Low focus

2.2. Developer/Integrator with know-how on TTI/AWS IOT/ and doesn't have an IoT platform yet or Developer who wants to create an extended visualization to their current IOT platform

2.2.1. Needs guidance / sample codes on how to integrate their current platform

2.2.1.1. Predefined list

2.2.1.1.1. Must always be updated

2.2.1.1.2. Needs integration developers

2.2.1.2. Option to integrate an unknown source

2.2.1.2.1. Admin must be notified if a new one is added for curation and possibly adding to the predefined list

2.2.2. Needs simple workflow from integration, visualization and alert configuration

2.2.2.1. Needs easy to use tool for device population

2.2.2.1.1. Upload CSV file

2.2.2.2. Needs easy to use tool for device group / container definition

2.2.2.2.1. Visualization of the container with zoom to see devices

2.3. Tech lead with a big team /

2.3.1. Needs teams, access rights

2.4. System Integrator with multiple customers

2.4.1. Needs sub-account management

2.5. A customer already using a competitor platform but wants to migrate

2.5.1. Needs migration support tools

3. Entities

3.1. Customer

3.1.1. has many Devices

3.1.1.1. belongs to one group

3.1.1.2. has many device types

3.1.1.2.1. has one mapping template

3.1.1.3. has a timeseries / state / logs for each telemetry

3.1.1.4. has events

3.1.1.5. has alerts

3.1.1.6. has many rules

3.1.1.7. has geomapping data

3.1.1.8. has device name

3.1.2. Has many groups

3.1.2.1. has geomapping data

3.1.2.2. aggregated all devices / timeseries data

3.1.2.3. last value for state telemetry

3.1.2.4. has device count

3.1.2.5. has events

3.1.2.6. has alerts

3.1.2.7. has many rules

3.1.3. has many Dashboards

3.1.3.1. has multiple dashboards

3.1.3.2. has multiple panels

3.1.3.2.1. has viewport mapping

3.1.3.2.2. has chart

3.1.4. has many Rules

3.1.4.1. has triggers

3.1.4.2. has actions

3.1.4.3. has type

3.1.4.3.1. device

3.1.4.3.2. container

3.1.5. has many Event

3.1.5.1. has type

3.1.6. has many Alerts

3.1.6.1. has type

3.1.6.1.1. info

3.1.6.1.2. warning

3.1.6.1.3. critical

3.1.6.2. has status

3.1.6.2.1. open

3.1.6.2.2. closed

3.1.7. has many Integrations

3.1.8. Users

3.1.9. Billing detail

3.1.9.1. has credit card info

3.1.10. Has many groups

4. Automatically Generated

4.1. Main Dashboard

4.1.1. A parent dashboard would show panels containing containers as the series

4.1.2. 1 panel for each device type in every container

4.1.2.1. Temperature

4.1.2.1.1. Temperature Timeseries

4.1.2.1.2. Humidity Timeseries

4.1.2.2. Motion

4.1.2.2.1. State timeseries

4.1.2.3. Vibration

4.1.2.3.1. Bed activity timeseries

4.1.2.3.2. state timeseries

4.2. Container Dashboard

4.2.1. For every container added, a container dashboard will automatically be created. This will follow hierarchy.

4.2.1.1. User would be able to browse from the main dashboard to every container dashboard

4.3. Rules

4.3.1. Device

4.3.1.1. For every device added, apply the default device rule

4.3.1.1.1. Temperature

4.3.1.1.2. Motion

4.3.2. Container

4.3.2.1. For every container added, apply the default container rule

4.3.2.1.1. Temperature

4.3.2.1.2. Motion

4.4. Mapper

4.4.1. For every Stream source added, a stream mapper is applied to all incoming data

4.4.2. For every device added, a telemetry mapper is applied depending on the type

4.5. Container aggregated data

4.5.1. Once a device is added in the container, its telemetry will be included in the aggregated data of the container.

5. Applications

5.1. Ingest API

5.2. Data API

5.3. Portal

5.4. Rule Engine API

5.5. Outbound Service

6. 3rd-party Application

6.1. Subscription/Billing

6.2. Authentication