IIC Business Strategy and Solution Lifecycle
Project Management: Ensures that UX principles are followed, shared resources are
managed efficiently, DevOps alignment, system architecture adherence, and
management of the agile release stream.
Asset Preparation team: This team has to ensure the integration of the IIoT solution with
all aspects of the asset`s lifecycle, including design, manufacturing and after-sales
services. It can also include environment preparation.
Teams for key solution elements:
o Backend Services, including Asset Data Management and Analytics, Domainspecific Application Services, Processes Management, EAI (Enterprise Application
Integration)
o Communication Services, including definition of Service Conditions, Set-Up and
Management
o On-Asset Components, including hardware, operating system and application
logic
Cross-Cutting Concerns team: This team is responsible for Security, Asset Lifecycle
Management (e.g., Asset Activation) and Solution Integration and Test.
Solutions Infrastructure and Operations team This team is responsible for infrastructure
set-up, operations preparation and application lifecycle management
Efficiently managing the interactions of these different teams is a challenging task. Figure 9
outlines a structure that can support this task. At the top-level is project management. On this
level, the central project backlog is managed. The key entities here are project epics (a highlevel specification artifact from the agile toolbox), which are used to capture larger bodies of
work. Furthermore, the overall system architecture is managed on this level. It is on this level
where compliance with the IIRA has to be ensured. The individual IIoT solution teams are
structured as described above. Here, the epics are broken down into more fine-grained user
stories, which are managed in the individual team backlogs. For the on-asset components (e.g.,
gateways deployed on the asset), it may make sense to chose longer sprint cycles or project
iterations, because hardware development is often not moving as fast as software
development. However, sprint cycles should be aligned across the individual workstreams.
IIC Journal of Innovation
- 53 -