Wednesday April 19, 9:00am – 17:00pm
Attendees
- Rob Akershoek, DXC Technology (Co-Chair)
- Satya Misra, HCLTech (Co-Chair)
- Etienne Terpstra-Hollander, OpenText (Vice Chair)
- Lars Rossen, OpenText
- Maarten Keverkamp, OpenText
- Stephanie Ramsay, RTX
- Michelle Supper, ServiceNow
- Andreas Hartmann, Leipzig University of Applied Sciences
- Dan Warfield, CC & C Solutions
- Don Brancato, Boeing
- David Lounsbury, TD Consulting
- Judith Jones, ATE Enterprises
- Jon Johnson, NASA SEWP
- Eric Choi, NASA SEWP
- Al Marshall, NASA SEWP
- Michelle Horrobin, The Open Group (Forum Director)
- Corinne Brouch, The Open Group
- Chris Franklin, The Open Group
Agenda
This was revised on the day the meeting, so it varies from the previously published agenda.
- Welcome and introductions
- Presentation – Core Committee topic updates:
a. Risk & Compliance
b. Asset Management
c. Capacity Management
d. Improved Meta Model
e. Security Management
- IT4IT Pilot 2023, roadmap, and planning:
a. Technical Corrigendum
b. Snapshot
Presentation link (BOX location) HERE
Discussion Points
Welcome and introduction
Michelle Horrobin, Digital Portfolio Forum Director, opened the meeting and welcomed the attendees. The agenda was presented.
Presentations
Risk & Compliance
Detailing the risk and compliance functional components (and data objects) as part of the Governance, Risk and Compliance supporting function.
Four proposed options were presented:
- Add business process, business capability and data object in EA
- Add risk management functional component
- Move policy management to risk and compliance
- Add compliance management FC
There followed a discussion regarding policies, controls, and legislation requirements; as well as on risk assessment / risk / threat etc. component and data objects and why these should be added to the IT4IT Standard.
Next steps agreed (added to Action section below):
- Rob to provide summary update to the next Core meeting
- Rob (with Michelle) to set up project meetings
Asset Management
Proposal Statement:
The additional guidance materials allow additional coverage in the market, as financial and legislation (as part of Governance, Risk, Compliance) gets better documented and explained. This may lead to better adoption of the standard by Business Stakeholders.
Working group meetings are planned and will commence within the next few weeks. Member participation for this group will include the following volunteers:
- Michelle Supper
- Jon Johnson
- Eric Choi
- Satya Misra
- Etienne Terpstra-Hollander
- Don Brancato
The content for a white paper was proposed to include:
- Drivers for asset management (why)
- Positioning asset management in IT4IT value streams (what)
- Embedding asset management into IT4IT
This included discussions regarding:
- Asset management lifecycle
- Describe changes from classical ITAM to now cloud consumption impact & management storyline
- Started paper from Charlie Betz, stored as a wiki
- References to other documents; e.g., DPBoK™ Standard
- Consider value stream (value/impact to P&L)
- Don: Enterprise Asset Management (lives above the capability)
- Be clear on what an asset is and what scope is
- Tangible or something on the balance sheet?
- Is a digital product an asset?
- Ownership, allocation of “resource” and “pool”
- Create storylines on the different types of Asset management, EAM, ITAM, HAM, SAM, CloudAM, etc.
- How do we do it with what we have today?
It was agreed the work group initial focus needs to be on what classes as an asset and asset management.
Next steps agreed (added to Action section below):
- Maarten (with Michelle) to set up work group meetings
- Maarten to ensure the term and scope of asset / asset mgmt. is the initial focus of the work group
Capacity Management
Proposal Statement:
Capacity Functional Component and its data object can be added to IT4IT Reference Architecture to manage effective and cost-efficient capacity planning through the managing the digital lifecycle:
An overview of current work group status and list of people involved was presented, along with the problem statement. Options for the approach was provided (refer to the presentation slides), along with a proposal for a white paper.
A Work Group has already commenced and is to be held every Thursday at 1500hrs CET (1400hrs UK / 0900 EST). The next one will be Thursday 27th April 2023. This is in process of being set up in Plato.
There followed a discussion regarding:
- Describing all options (2) in the workgroup to inform the outcome / direction of the white paper
- User cases / considerations for capacity management
- Business capacity requirement, service capacity, component capacity
- Be clear on the problem trying to be solved by capacity management
- Suggested 3rd option – part of product design? Explore value stream
Next steps agreed (added to Action section below):
- Satya to ensure the term and scope of capacity mgmt is the initial focus of the work group – what is the problem trying to be solved?
- Satya to include exploring the three options with the workgroup and bring back the details to the core committee for progression / approval
- ALL – add issues in GitLab® or participate in the work group (inform Satya)
- Michelle H to finalize set up of meetings and a slack channel for this work group
Improved Meta Model
Proposal Statement:
The current 3.0 meta model of IT4IT is an evolution over the 2.1 model but have several issues. It is not fully supporting the Business layer of architecture, as its starting point was application components and functions. It is unclear at points. Dataflows are not fully formalized and the associated distinction between SoR and SoE is not clear. Data Objects are potentially business objects but is documented as “records with fields”. There are several other challenges that this work will try to address.
- Approved Proposal BOX Link: HERE
- Presentation BOX Link: Not yet available
It was noted that a work group has not started yet, as this topic is at an earlier stage of progression.
Highlighted the questions and issues with the models/diagrams in V3.0.
General consensus is that this is the right approach, and some tweaks were discussed for the (future) work group to consider re the model in the use case but not in the Standard.
ArchiMate element discussed, along with inconsistencies with models and images.
A white paper does not apply here, but it was agreed that GitLab issues need to be raised.
A summary update was agreed for the next Core Standard standing committee meeting.
Next steps agreed (added to Action section below):
- Andreas (with Michelle) to set up work group meetings if needed
- Andreas – add as issues in GitLab
Security Management
Proposal Statement:
Detailing the security management components (and data objects) as part of the IT4IT reference architecture (in collaboration with the Security Forum).
There was a discussion regarding areas where this could be included within the Standard, with a focus on working out security risk architecture first and then progress from there. Noting to continue to align in the future with the Security Forum.
There is already a joint work group for this work with the Security Forum and work is already in progression.
IT4IT Pilot 2023
A timeline of dates for the IT4IT Pilot 2023 (including Technical Corrigendum and Snapshot releases) was discussed and is now summarised in a visual format (post meeting) HERE.
The initial focus will be on the Technical Corrigendum, as that requires Company Review.
The Company Review will form the basis of the IT4IT Pilot 2023 as the review process will be completed via the new digital platform (Antora & GitLab) as opposed to the traditional Plato review process.
An overview / demo of the above digital platform was provided, highlighting that the CRs and content are in the Antora platform. There will be help and guidance provided on this throughout the Pilot.
Consensus Item 2023-04-18 001
The IT4IT 2023 Pilot timeline was approved at the meeting – noting that the timescales are tight but achievable for the type of content required. This will be project managed by the Digital Portfolio Forum Director and the content will be managed by the IT4IT Core Standard standing committee. Updates will be provided to the IT4IT Steering Committee.
AOB
There was no AOB raised / discussed.
Action Items
2023-04-19 001: Rob Akershoek to provide a summary update of the Risk & Compliance topic at the next Core Standard standing committee meeting.
2023-04-19 002: Rob Akershoek & Michelle Horrobin to establish work group meetings for the Risk & Compliance topic.
2023-04-19 003: Maarten Keverkamp & Michelle Horrobin to establish work group meetings for the Asset Management topic.
2023-04-19 004: Maarten Keverkamp to ensure the term and scope of asset / asset management is the initial focus of the work group for Asset Management topic.
2023-04-19 005: Satya Misra to ensure the term and scope of capacity management is the initial focus of the work group for the Capacity Management topic.
2023-04-19 006: Satya Misra to include exploring the three options with the Capacity Management Work Group and bring back the details to the Core Standard standing committee for progression / approval.
2023-04-19 007: ALL – add in any relevant issues for Capacity Management into GitLab, and/or inform Satya Misra if wishing to join in the Capacity Management Work Group.
2023-04-19 008: Michelle Horrobin to finalize set up of meetings and a slack channel for the Capacity Management Work Group.
2023-04-19 009 (TBC): Andreas Hartmann & Michelle Horrobin to establish work group meetings for the Improved Meta Model topic (if needed).
2023-04-19 010: Andreas Hartmann to add the identified elements from the Improved Meta Model presentation as issues in GitLab.
2023-04-19 011: Michelle Horrobin to create an initial project plan for the IT4IT Pilot 2023 and share with both the IT4IT Steering and IT4IT Core Standard standing committees.
Meeting Closed