---
tags: SIG Events, VSMI, CDEvents
---

## Reference/working material
[VSMI Reference Architecture](https://docs.google.com/presentation/d/16-c-Kui3LKmiIc54N7f_4tebTt-zcbCnKDypksT5WRo/edit#slide=id.p)

[VSM & CDF Joint Charter](https://docs.google.com/document/d/1iX3RJ2KH4h-WM-sltfzatNtDzdMpN0T8nm4IylGhPdY/edit)

## Open issues

### Data store
Where to keep all data? Some data lake will be needed.

### Scope of VSM vs CDEvents
- VSM is mostly interested in historical data, to see trends on the value in a system of work, while CDEvents is both interested in historical data (visualization, metrics, etc) AND realtime data for triggering and such
- There is an overlap between the data for VSM and the data for CI/CD. CI/CD data is probably not a pure subset of VSM data.
- VSM is more about inspecting how a “system of work” is evolving over time and with new/improved/changed value added to it

## 27.06.2023

Attendees:
- \<add me\>
- Andrea Frittoli, IBM, UTC+1
- Emil Bäckmark, Ericsson, UTC+2
- Steve Pereira, VSMC
- Victor Lu

Notes:
- VMSI Topology presented
- Activity layer
- Ingress: Real time integration - CDEvents as a protocol here
- History: Data store, data lake
- VSMI Architecture (Broker, Datastore, Model & Ontology layer)
- VSM Platform (Observation, Intelligence/Insights, Prediction)
- VSMI Ontology
- Data vs Models
- Models are about representation. There may be some default representation, but it also may be left to the specific VSM Platform
- Data are about activities. In one event there would be multiple entities and systems associated
- TODO
- Revisit charter to finalize
- Steve to add an example of model/data
- Steve to add a lifecycle example