Internet of Events

PROCESS FRAMEWORK AUTOMATION

The Internet of Events (IoE) refers to a concept where significant events (the 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). This is a crucial set of embedded rules designed to interpret event data and manage workflows effectively.

As already mentioned, this ensures that every necessary process is either fully executed and authorised or, at a minimum, considered and indemnified.

The Digital Transformation Transfer Protocol (DTTP)

Below is a summarised representation of event document type definitions, organised by subsystem: Demand, Transformation, Service Delivery and Value. This categorisation offers an efficient 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, 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 practicality status changes.
  • Investment Portfolio: performance indicators, health and progress toward its value goals.

Demand Conrol Subsystem: Suggested Event ID Allocation

101000 innovation and creativity101005 improvement proposal101010 Financial Agenda Outcome101015 improvement request
102000 improvement audit request102005 improvement audit outcome102010 resource plan audit request102015 resource plan outcome
103000 value assessment audit request103005 value assessment outcome103010 business alignment status103015 technical aligngnment status
104000 strategic economic feasibility status104005 strategic operation feasiblity status104010 strategic technical feasibility status104015 strategic schedule feasibility status
105000 strategic feasibility audit request105005 strategic feasibility audit outcome105015 quality plan status105020 investment portfolio status
106000 stakeholder requirement delivered106005 development resource funded106010 implementation resource funded106015 feasibility issue
107000 delivery delay time107005 postponed107010 descoped107015 cancelled
 
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.

Transformation Control Substystem: Suggested Event ID Allocation

208000 vision requirement defined208005 vision requirement explication208010 requirement defined208015 requirement rejected
208020 requirement QA complete209005 solution optimum benefit209010 solutions work in progress209015 solutions rejected
210015 plan rejected210010 planning work in progress210020 development viable210025 development not viable
211010 unit test complete211011 security test complete211012 compliance test complete211015 security audit complete
211020 compliance audit complete211025 unit test audit complete211030 standards failure211035 data architecture audit complete
212005 configuration built212010 configuration work in progess212015 configuration functionally tested212020 configuration operationally tested
212025 configuration failure213005 risk identified213010 failure (risk associated)213015 failures (not risk associated)
214010 service assurance criteria achieved214015 deployment achieved214020 deployment failed
 
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.

Service Delivery Control Sub Stystem: Suggested Event ID Allocation

315000 service failure315005 non-service failure316005 request defect rate316010 service outage
316015 service satisfaction316020 update transformation effort316025 amend transformation effort316030 update WIP effort
316035 update rework effort316040 estimate mean delivery time317005 current batch duration317007 current online actual
317010 target batch duration317013 target online percentiles317015 test batch duration317017 test online percentiles
319005 maximum throughput capacity319010 actual throughput capacity319015 test throughput capacity318010 high/low/norm/avge I/O usage
318011 server with high average I/O318015 server with normal memory usage318016 server with high memory usage318017 server with low memory usage
318020 normal swap space usage318022 server high swap space usage318024 server with low swap space usage318025 network bandwith utilisation
318030 network latency utilisation318035 network available time utilisation
 
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.

Value Control Subsystem: Suggested Event ID Allocation

420000 improvement cost420005 improvement budget420010 finance cost420015 finance budget
420020 strategy cost420025 strategy budget420030 planning cost420035 planning budget
420040 feasibility cost420045 feasibility budget420050 portfolio cost420055 portfolio budget
420060 transform design cost420065 transform design budget420070 transform development cost420075 transform development budget
420080 transform qa cost420085 transform qa budget420090 transform implementation cost420095 transform implemantation budget
420100 service sla cost420105 service sla budget420110 service operation cost420115 service operation finance budget
420120 service efficiency cost420125 service efficiency budget420130 service capacity cost420135 service capacity budget
420140 service business cost420145 service business budget420150 actual revenue420155 projected actual revenue

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