Internet of Events

PROCESS FRAMEWORK AUTOMATION

The Internet of Events (IoE) refers to a concept where significant events—actions, activities or occurrences within a system or process—are continuously tracked, analysed and responded to in real-time through interconnected digital technologies.

These events seamlessly trigger workflow activities via the Digital Transformation Transfer Protocol (DTTP)—a crucial set of embedded rules designed to interpret event data and manage workflows effectively.

Below is a summarised representation of event document type definitions, categorised by subsystem: Demand, Transformation, Service Delivery and Value—providing a streamlined approach to capturing and managing digital event data.

Demand Events
The global digital transformation market is growing rapidly. By 2034, the market is generally expected to expand significantly, with forecasts suggesting growth factors ranging from 1.5x to 3x, depending on specific sectors.

  • Innovation and Improvement: Proposals, ADT Financial Agenda Outcome and improvement requests.
  • Audits: Requests and outcomes for improvement, resource planning and value assessments.
  • Feasibility & Alignment: Economic, operational, technical and schedule feasibility, alongside business and technical alignment.
  • Stakeholder Requirements: Funding, delivery issues, delays and project status changes.
Transformation Events
Digital transformation is a systems engineering process for developing, maintaining and delivering optimal solutions to meet related business requirements. As the business-technical ecosystem changes, many businesses continue to turn to technology as a means to shape their business future.
 
  • Requirements & Vision: Defining, explication, acceptance, or rejection, including QA completion.
  • Solution Progress: From optimum benefit identification to work-in-progress and rejections.
  • Planning & Development: Evaluating the viability of plans and development stages.
  • Testing & Auditing: Completion of unit, security and compliance tests, including audit outcomes.
  • Configuration & Risk Management: Building configurations, testing, identifying risks and assessing failures.
  • Deployment & Assurance: Achieving or failing deployment, meeting service assurance criteria.
Service Delivery Events
Digital service delivery is a systems engineering process that includes the monitoring of; business throughput, service delivery, service availability, service satisfaction, defect rates, breaches of security, work in progress and rework levels. The service workflow includes optimising technical architectures to accommodate planned changes in capacity and utilisation.
 
  • Failures & Defects: Monitoring service and non-service failures, defect rates and outages.
  • Service Satisfaction & Transformation Efforts: Tracking satisfaction, update efforts and rework.
  • Batch & Online Performance: Analysing current, target and test batch durations and online performance metrics.
  • Throughput Capacity & Network Metrics: Monitoring maximum, actual and test capacities, network bandwidth, latency and server metrics.
Value Events
Digital value examines whether expected benefits, effectiveness and efficiency has been achieved throughout project lifecycles. It also evaluates the ongoing benefit up until the associated deliverable is no longer relevant.
 
  • Improvement & Financial Costs: Tracking costs and budgets for improvements and financial agendas.
  • Strategy & Planning: Monitoring costs and budgets for strategic and planning activities.
  • Feasibility, Portfolio, & Transformation: Costs and budgets for feasibility, portfolio, design, development, QA and implementation.
  • Service Operations & Efficiency: Managing costs and budgets for SLA, operations, efficiency, capacity and business.
  • Revenue Tracking: Actual and projected revenue outcomes.

Control Workbench Example

The data format below represents the necessary elements for a dataflow under the Digital Transformation Authority, with the Document Type Definition (DTD), Schema Definition and example XML format for this specific demand event.
 
  • Markup declarations are control statements that specify how other markup (such as tags) within a source file is to be interpreted.
  • The markup declarations for “demand event | financial agenda outcome | id 101010″ could be defined as follows:

Document Type Definition (DTD)

<!ELEMENT finAgendaOutcome (pid, stat, type, event, time)>
<!ELEMENT pid (#PCDATA)>
<!ELEMENT stat (#PCDATA)>
<!ELEMENT type (#PCDATA)>
<!ELEMENT event (#PCDATA)>
<!ELEMENT time (#PCDATA)>


XML Schema Definition (XSD)

<xs:element name=”finAgendaOutcome”>
<xs:complexType>
<xs:sequence>
<xs:element name=”pid” type=”xs:projId”/>
<xs:element name=”stat” type=”xs:status”/>
<xs:element name=”type” type=”xs:requestType”/>
<xs:element name=”event” type=”xs:eventId”/>
<xs:element name=”time” type=”xs:timestamp”/>
</xs:sequence>
</xs:complexType>
</xs:element>

Extensible Markup Language (XML)

<finAgendaOutcome>
<projId>PA01-0000598</projId>
<status>Funding Available</status>
<requestType>Business</requestType>
<eventId>101010</eventId>
<timestamp>1661925740</timestamp>
</finAgendaOutcome>

back