/
Rules, Principles, SLA

Rules, Principles, SLA

Owned by Janina Mincer-Daszkiewicz
Last updated: 17 Apr 25 by Paul Leys
3 min read

The EWP infrastructure is a critical shared resource which is essential for the implementation of the Erasmus+ Programme and is financed by the European Commission. It is therefore necessary to establish and maintain an acceptable use policy for connecting to – and utilizing – the network and its central resources. The AUP is enforced by the EWP consortium in coordination with DG EAC of the European Commission.

General mandatory rules

  1. All transactions using the EWP must be for non-commercial purposes and solely related to administration of Erasmus+ mobility exchanges or other European initiatives.

  2. All software used for network nodes accessing the EWP must be compliant with the established mandatory business requirements (when applicable) and semantic and functional interoperability standards published in the EWP Developers’ Guide (including the Service Baseline section). This is meant to guarantee full interoperability between any EWP nodes connected to the network.

  3. Once officially established, mandatory conformance testing will apply and only service providers (and the associated EWP nodes) having passed these tests will be allowed to offer/continue services in the network.

  4. All connected service providers must support the common EWP service desk and respond to related open tickets within a timeframe defined in the Service Level Agreement (SLA) annexed to this AUP.

  5. The EWP Acceptable User Policy is an integral part of the Memorandum of Understanding signed by the service providers. It will be enforced as set out in Appendix 1 and failure to comply with the rules, principles of SLA may lead to exclusion from the EWP network.

Appendix 1 AUP Enforcement Principles

The following standard principles will apply as part of the enforcement of the AUP when violations incur:

  1. EWP Consortium will make contact by email to the official contact in order to clarify the issue and assist in resolving the situation in cooperation with the provider(s) concerned in a reasonable timeframe.

  2. If the actions taken under 1 lead to resolving the situation, no further actions are taken.

  3. In case there is a clear violation of the AUP and the concerned provider does not actively collaborate to resolve the situation, the provider in question will be put on formal notice about the violation of the AUP and given a fixed time to rectify to issue.

  4. Providers put on notice for AUP violations may be identified on a public list for the EWP in order to keep the EWP constituency informed about the situation.

  5. In case the identified AUP violation has not been rectified within the time limit given, the provider may be disconnected from the network.

  6. There will be full transparency ensured regarding proceedings resulting from violations of the EWP AUP.

Appendix 2 AUP Service Level Agreement (SLA)

The SLA associated with the AUP is defined as follows.

  • Tickets transmitted from the EWP service desk must be acknowledged at reception and resolved within maximum

    • 5 working days in case of commercial 3rd-party mobility software providers,

    • 7 working days in case of HEI in-house mobility software providers.

  • If tickets cannot be resolved during the time limit, the EWP service desk must be notified with a clear justification and what the expected time for resolving it will be, referencing the ticket number. If the proposed delay is not well justified this will trigger the AUP violation procedure set out in Appendix 1.

  • The EWP service desk must be notified when the ticket has been resolved referencing the ticket number.

Related content