Stakeholders

Skip to end of metadata
Go to start of metadata

(part of the InLOC work)

Stakeholders and sources

This information is unlikely to be complete.

Here are lists of stakeholders and sources surveyed in alphabetical order within their groups.

Stakeholders involved with material similar to InLOC, or that could be represented with InLOC

With source material, and a model that is explicit and formal or formalisable

With source material, but no explicit formalisable model

With an explicit model, but little if any real life source material

Stakeholders who may refer to learning outcome or competence definitions

A detailed model of LOCs is not needed for these purposes.

Stakeholders who may wish to prototype InLOC systems

Companies

Projects

European agencies who might have an interest


Original InLOC Stakeholder Liaison Plan

This is left here for historical interest: it was the intended plan during the funded project.

Rationale

Even as a team, without the close involvement of others we cannot ensure the uptake and adoption of our outputs. This Stakeholder Liaison plan is designed to promote the adoption of our outputs, while at the same time acting as a common thread supporting the main tasks and outputs, and reducing the chance that work is duplicated.

Relationship with the main outputs

The Information Model encompasses the models used by, developed by, or implicit in the information of interest to, the various stakeholders, gathered through this process.

The Guidelines covers topics of importance to the stakeholders, discovered and checked by us through this liaison process.

The Application Profiles are adapted more closely than the general information model to the models relevant to the particular applications, as discovered through liaison.

The Bindings that we document as outputs are those that stakeholders tell us are actually or potentially useful.

Stakeholder sources

These include: tool developers; users of the structures (EC, agencies, employers, LET and awarding bodies); groups with models (including standards bodies); bodies of content; related specifications; and technical approaches.

Source and stakeholder liaison tasks

  • S1. Compile and maintain a list of stakeholders and sources. Document organisations (but not individual contacts) on wiki.
  • S2. Document information from stakeholder sources. The key information about stakeholders is what they would want or need from the InLOC model, or eventual specification, to secure their adoption of InLOC outputs; and what Guidelines documentation is needed to facilitate their use. Document on wiki.
  • S3. Express relevant models. Some are implicit, and to be drawn out, ensuring they are understandable by both team and owning stakeholders. Document on wiki.
  • S4. Integrate model with growing core. This involves tracking the features of the models, and ensuring that the growing core model covers all important ones.
  • S5. Refer the InLOC model back to relevant stakeholders. This is essential feedback, after the interim report and CWAs have been first drafted. It is aimed to convince the stakeholders to adopt the InLOC model.

Overall process

The liaison process is thus in two stages. First, the requirements are gathered and models surfaced. This will enable the team to develop a good Information Model and Guidelines that is at least reasonably fit for purpose. Second, the initial Information Model and Guidelines will be carefully checked with the most significant stakeholders, making whatever improvements are needed to ensure the eventual adoption of InLOC outputs.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.