Documentation

Exercise Workbook
IoT UI Development with ThingWorx
Milestone 2
Milestone 2: Power System
Application - Experience
From the IoT Modeling with ThingWorx course, we learned that our Mars Colony story picks up
with Mars’ researchers setting-out to launch their first interstellar ship called the Apollo class 4
cruiser. This ship is responsible for taking humanity out into the furthest reaches of space on a
quest of discovery. Many more of its kind will be built from the ground-up in shipyard factories
that are part of the Mars’ larger power system.

The outcome of the IoT Modeling with ThingWorx course was the IoT system of the Mars’
shipyard power system so that researchers could monitor, control, and automate different
aspects of the shipyard factories. We learned that power generation and sustainability can be
difficult and complex in the shipyard factories. Between the dust storms, ship building robots,
and other power fluctuations to consider, Mars’ power system needed this IoT system to
manage its efficiency. Two key managers of the shipyard and IoT system emerged: A Power
System Administrator and Yard Administrator.

In this course, we will design and build a user interface for the power system administrator,
Karen Lee, so she can manage the power system across the factory. To help us develop the UI,
we will be using the ThingWorx UI Build Process to guide our decision making and
implementation.

UI Development Documentation Exercise Workbook |1

ThingWorx UI Build Process Framework

Right now, we are in the Experience stage. Our goal in this stage is to summarize at a high-level
what was completed in the IoT Modeling with ThingWorx course. This includes details of who is
the user of the application, what entities were created, and which services do we have that
support the data and actions within in the application. All of this acts as the starting point of
how we will design the UI.

User Story Document

Let’s first review the user story information, details, and access information that was part of IoT
Modeling with ThingWorx’s documentation exercises. These deliverables set the stage and
succinctly defines the user of the application and UI requirements. To avoid building a single
application that does everything, it is best to think of applications as role-based, where the
features are focused on a single role.

UI Development Documentation Exercise Workbook |2

IoT Modeling with ThingWorx User Story Outcome

IoT Modeling with ThingWorx User Details and Access Information Outcomes

UI Development Documentation Exercise Workbook |3

Which Data and When?

Next, let’s review the entities and services from the model that support the data and actions
that Karen needs in this power system application. These outcomes will help us identify which
entity data we need to add the UI and identify which widgets will bring the captured data to
life.

IoT Modeling with ThingWorx Entity Outcomes

UI Development Documentation Exercise Workbook |4

IoT Modeling with ThingWorx Entity Outcomes

UI Development Documentation Exercise Workbook |5

UI Development Documentation Exercise Workbook |6
IoT Modeling with ThingWorx Entity and Services Outcome

UI Development Documentation Exercise Workbook |7

Summarized UI Build Experience

Now that we have reviewed the user of the application and the data captured from our model,
lets summarize the user, use cases, and data for our UI in a concise form. We will use them in
the next stage of the ThingWorx UI Build Process, the Design stage.

ThingWorx UI Build Process – Experience Stage

User Interface – Power System Application

User(s) Karen Lee, Power System Administrator
Device(s): computer work station, tablet

User IoT Use Case(s) Monitor

▪ Power system aggregate data
▪ Power system asset data
Control
▪ Shipyard overall status for low-power emergencies
▪ Individual assets during shipyard low power via
manual shutdown
▪ Shipyard no low-power state time horizon
Automate
▪ Shutdown of non-critical assets for low-power
emergencies
▪ Low-power state based on power production and
consumption

Modeled Data • PowerStorage – Thing, no services

• PowerProducerTS – Thing Shape, no services
• PowerConsumerTS- Thing Shape, overridable
Shutdown service
• PowerSystemServices – Thing, 4 wrapped services
• Shipyard – Thing, Rollup service

UI Development Documentation Exercise Workbook |8