---
# System prepended metadata

title: TEA Platform Co-Working
tags: [planning]

---

# TEA Platform Co-Working

## Upcoming accepted opportunities

| Date           | Title                        | Comments
|----------------|------------------------------|---------
| March 19–20    | AI UK 2024                   | ...
| March 27       | Lunch and Learn with DSIT    | ...
| July 1         | Turing Induction             | 15 minute presentation max (in the afternoon)

## Upcoming potential opportunities

| Date           | Title                        | Comments
|----------------|------------------------------|---------
| April 30–May 1 | Collaborations Workshop      | :bangbang: 1 Mar proposals due!! [Application draft](https://hackmd.io/uXH-VJKIRhej9wN1cT5cSA?both)
| May 13–24      | DSG with Mastercard          | :bangbang: 28 Feb info meeting with Jules Manser scheduled
| May–Nov        | Lunch and Learn with the ATI | Built on DSIT Lunch & Learn
| September 3–5  | RSECon24                     | :bangbang: March–May Call for Papers opens (do something with Shakir?)
| :interrobang: Unknown | Cross-sector deep-dive workshop on AI assurance and Digital Twins with Turing Strategic Partners | See email from Feb 6. Nico will tell Strategic Partners on Feb 27, then we'll see next steps
| :interrobang: Unknown | Stuart Lynn's NHS application area/Urban Analytics collab | Chris's conversations with Gavin Shaddick, Stuart Lynn, and Allaine Cerwonka about international communities who could contribute to platform
| :interrobang: Unknown | Karen Cordier from Project Bluebird was talking about a research theme that has an ethical element | [See Slack](https://alan-turing-institute.slack.com/archives/C06KGCWAW8G/p1708438959322179)

To add:
- https://blogs.uni-bremen.de/goodit2024/
- https://fair-impact.eu/fair-impact-open-calls-support
- https://www.ukri.org/opportunity/ukri-metascience-research-grants/

<!--
Update 06 Feb 2024: These notes have been transformed into issues in the GitHub repository.

## Notes on Platform Update

**PRIO 1**: Maybe we need to move away from Mermaid. Let's get a fullstack dev + RSE who can figure out a solution...

- "Reset namespace" button under dropdown menu should be "Case Properties" with a modal as a result
  - maybe Notes + Permissions goes there too?
- "Add Goal" button could be dynamic, so if you have a Goal selected, it would give options based on the selection?
- Remove tooltip from Goal?
- Goal descriptions should not be at most 40 characters... also it still saves, despite being more than 40 characters
- Collapse interactivity doesn't look the best, needs a review
- No need to see URL for Evidence on main board
- Some kind of better CTA on removing of elements with children
- "Url" should be capitalised everywhere
-->

## TEA Platform Handout 

:::success
**Planning Document**

See this document: https://hackmd.io/@tric-dt-hub/HySRbZhK6
:::

## TEA-DT Project Planning

:::success
**Planning Document**

See this document for project planning: https://hackmd.io/@tric-dt-hub/SJzlsrLY6
:::

## Ad-hoc "Coworking" Feb 06 2024

- [x] TEA-DT Developer Decision-Making
- Opportunities
    - DSG with Mastercard (searching for ethical AI and bias in financial AI models) or Theyr (in building user trust in shipping route optimisation) [**due 25 Feb**]
    - [Collaborations Workshop 2024](https://hackmd.io/uXH-VJKIRhej9wN1cT5cSA) [**due March 1**]
        - next step = Kalle to speak with Malvika (Co-I for TEA-DT; SSI Fellow) and Shakir to gauge interest and help with framing.
    - Shakir
        - https://qualitysafety.bmj.com/content/early/2023/09/20/bmjqs-2023-016042
        - RSE conference paper [due date unknown but likely April/May]
    - Deep-dive workshop on AI/DT/assurance
    - Chris: "I’ve also had some very productive conversations with Gavin Shaddick, Stuart Lynn, and Allaine Cerwonka about other areas of the Turing and International communities that would be keen to contribute to the TEA platform. Stuart’s interested in the NHS application area especially based on some of the work they’ve been doing in Urban Analytics."
- [x] Appendix 2 updates 
- Product compendium chat
- Move documentation from HackMD to site
    - :bangbang: Pending sign-off on first edits from Chris
    - Move ["New stuff for the User Guidance"](https://hackmd.io/osvTgcBpRmGjUr1Z6FWaYg?both#New-stuff-for-the-User-Guidance) into the site


## TTW Collab Cafe (Feb 7th 2024)

**Issue**: https://github.com/alan-turing-institute/AssurancePlatform/issues/328

**Miro**: https://miro.com/app/board/uXjVNvnjoB4=/

### AI UK

- pretty much all good
- [name=Chris] put the CEMRG case into the platform
- a user click-through demo?
    - Rich starting-task

### Next-step

- XML-type file format
    - why? (1) model-driven validation (say, XSLT or something?) + (2) easier file format to modularise? + (3) expert users might want to copy-paste plain text.
        - could we have a live editor/validator that quickly ensures that the format works? [new feature]
- Next.js -> full-JS stack
    - Rich can finish before Newcastle joins? Transforming the querying backend.
- consider storing objects differently?
    - [this requires more conversation about db stuff!]

:::success

**Key Points about Structured Assurance Case Metamodel's (SACM) XML-based Format**

- Interoperability: The XML format enables the exchange of assurance case data between various tools and systems that adhere to the SACM standard. This interoperability is crucial for collaborative environments where different stakeholders might use different tools to contribute to the assurance case.
- Machine-Readable: Being an XML-based format makes SACM data easily processable by software tools. This supports automation in the creation, verification, and reporting of assurance cases.
- Extensibility: XML's inherent flexibility allows for the SACM format to be extended or customized to meet specific project or domain requirements, while still maintaining compatibility with the core SACM standard.
- Standardization: The use of a common XML schema for SACM helps in standardizing the representation of assurance cases across different domains and industries. This standardization is beneficial for maintaining consistency and understanding across diverse projects and regulatory environments.

:::

### Design Sprint ideas

See: https://miro.com/blog/design-sprint-guide/

Step 1: Sprint master creates a design brief (with challenges/constraints/timeline) = change database/backend --> align more with standard (and allow for easy interface) = DEFINE

Step 2: Share design sprint board (and invite experts to lightning talks, say on SACM standard = UNDERSTAND)

Step 3: Collect data from open sources + team members on what's needed to accomplish our requirements

Step 4: Room booking + prep _ playbook (schedule/methods)

Step 5: DIVERGE = go to work!

Step 6: Decide

Step 7: Prototype

Step 8: Validate

### Kalle's time and expertise

TEA-DT: 0.2
TRIC-DT: 0.2
____________
           0.4

Asking questions and ensuring that we have all the required answers to move forward with prototyping *what we want* = and what is it that we want?

- Newcastle from April
- Rich from late Feb?

