Meeting Schedule

Attendees

  • Thibaut Wautelet

  • Douglas Mulhall
  • Jérôme Petry
  • Clément Gorlt
  • Anne-Christine Ayed
  • Judith Fleenor
  • Phil Archer
  • Lynn Bendixsen
  • Albert Johnson
  • Michael Nettles
  • Bryan Buecking
  • Drummond Reed

Agenda 


TimeItemLeadNotes
1 minWelcome & Antitrust Policy Notice

3 minIntroduction to PCDS Task Force

Thibaut W.



5 minContext of PCDS initiativeJérôme P.
  • Notes
10 minPresent draft document: Business requirements for the IT system

Thibaut W.

Clément G.

  • Notes
55 min

Discuss questions 1 & 2 in the draft document

  1. Are the governance framework, the IT framework and the business model clear?  
  2. Does the system structure look practical or is there a better way to meet the objectives? 

  • Notes
40 mins

Discuss questions 3-5 in the draft document

3. Which mechanism do you recommend to use to link the unique ID with a PCDS dataset, without requiring the dataset itself? 

4. Is the local node necessary for the system to function? 

5. What are your recommendations for the authorization mechanism for the local node creation?  



2 minsWrap-up / Next steps

Presentation & document

Recording

Notes

Monetization was identified as a high priority. 

  • In the business case, split customer needs into statutory requirements (existing and anticipated) and economic/CSR benefits.
  • Evaluate how to compare PCDS ‘costs' against social/economic gains.
    • Suggestion from chat: I am wondering if there are potential social and environmental impacts that has value to governmental entities that could be monetized? 
  • Do updates to slide presentation and business requirements draft as follows;
    •  Include matrix linking value propositions identified earlier (who gets what) with potential revenue models (who pays), in order to see which needs match which revenue model.
  • Consider market survey (what type?) to test needs and revenue assumptions. 
  • Investigate revenue model with industry associations also to get their members involved ( does that affect functional requirements?)
    NOTE: Industry associations tend to be the most conservative and don’t like paying fees, so this needs careful consideration.

Security & Trustworthiness

Terminology alignment with other systems



  • No labels