LogoLogo
  • Introducing the framework
    • Context
    • Definitions
    • Development of the framework
    • Who is the framework for?
  • Framework overview
    • Framework at a glance
  • Engage and convene
    • Stage outline
    • Activities
    • Supporting tools
  • Understand and plan
    • Stage outline
    • Activities
    • Supporting tools
  • Develop
    • Stage outline
    • Activities
    • Supporting tools
  • Learn and publish
    • Stage outline
    • Activities
    • Supporting tools
  • Implement
    • Stage outline
    • Activities
    • Supporting tools
  • Appendix one - Engagement protocol
    • Prioritisation matrix
    • Support tiers
    • Interaction process map
  • Appendix two - Governance and accountability structure guidance
    • Governance and accountability structures
  • Appendix three - MEL framework
    • Overview
    • Step by step guide
  • Appendix four - Data requirements framework
    • Data requirements framework
  • Appendix five - Use case template
    • Problem statement template
    • Use case prioritisation decision-making matrix
  • Appendix six - Funding model guidance
    • Funding model guidance
Powered by GitBook
On this page
  1. Appendix one - Engagement protocol

Interaction process map

PreviousSupport tiersNextGovernance and accountability structures

Last updated 11 months ago

The following process map outlines the ways in which the use case community interacts with OA governance through the different stages of the framework.

Interaction process map
Process map outlining the ways in which a use case community will engage with the OA community during the different stages of the framework. Stage one - engage and convene. The use case community informs the AEF, the AEF helps to catalyse the use case community, the AEF informs the W3C and Steering Committee. When the use case community is proposed by the OA community or identified by OA governance it is invited to present at the AEF. The use case community is then listed on the OA website. An open use case community provides an opportunity for the OA community to register the interest before it is convened, whereas a closed use case community goes straight to convening. Stages two to five - understand and plan, develop, learn and publish, and implement. The use case community informs the AEF and W3C, the AEF and W3C support the use case community as required, and the AEF and W3C inform the steering committee. Regular updates are provided by the use case community to the AEF and / or the W3C. Open working is encouraged via Slack, Google Drive and YouTube. Summary reports of KPIs, process evaluations and case studies are developed and published on the OA website. Where relevant, use case community implementations are integrated into OA infrastructure.