NOP Portal - Help
Portlets from A to Z > Network Events > Roles and Responsibilities
Roles and Responsibilities

The use of the NET requires the definition of new roles and responsibilities for users providing event data to NET, both prior to and post event, in order to define ways of working with the tool and to ensure the integrity of the data displayed.

NET Actors

The following actors are defined in the NET application:

Originator

Originator of the event e.g. ANSP, Airport Authority, FMP, Mil Authority, IATA, NM, AXIS team, RNDSG, event organiser or host.

Source/Editor

Creator and editor of an event in NET e.g. OPL ERNIP, OPL Strategic Planning, OPL Strategic ATFCM, APC, MILO. 

Contributor

Contributors to an event in NET e.g.. OPL Strategic ATFCM, NMOC/Pre-tactical, NMOC/ENV, NMOC/COM, NMOC Post Ops, PFR-Performance, Contributors are able to change data, add data and delete (soft delete -automatic archive) an event as it progresses through the lifecycle, with respect to their business responsibilities, subject to coordination with the Source/Editor.

Data Administrator

Data Administrators have read/write access on ANY EVENT and monitor the resolution of duplicates, data inconsistencies and errors. 

NET Roles

There are basically two main roles in this context, READER and AUTHOR. Each is divided in two sub-categories, as described below:

  • READER - includes
    • The Reader (any Portal User) may view and print published events, query published events, and download the queried data as CSV file;
    • The Subscriber (any Protected Portal authenticated user) has subscribed to get Notifications;
  • AUTHOR - includes
    • The Author (authenticated and recognized contributor) has the same rights as the Reader and may in addition perform the following actions:
      • View drafts
      • Create events
      • Update events
      • Publish events
      • Delete events
      • Rollback to previous version of an event
    • The Administrator (specific role restricted to a smaller number of individuals, internal or external to Eurocontrol) has the same rights as the Author and gets additional administrative privileges including the possibility to update the responsible data source of an event. 

    Responsible Data Source

    NET supports the visualisation and edition of events that may be created and partially maintained in external data sources (i.e. Airport Corner and ERNIP currently).

    To prevent edition conflicts between NET and the external data source of an event, the concept of Responsible Data Source has been introduced. The Responsible Data Sources currently introduced in NET are: APC (Airport Corner), ERNIP, WIND (Web Interface for NOP Data), NET.  Only the first two remain active (operational) in parallel with NET, while WIND (former ATFCM Events) has been integrated fully and replaced by NET.

    An event is always associated to a Responsible Data Source which in turn is the only data source allowed to modify certain data fields of the event. Those protected data fields are marked with (*) in NET Editor. There is no specific identification of those fields in Event Viewer.

    Only the ADMINISTRATOR can change the Responsible Data Source of an event in NET.

    Field Editability Rules

    An event can be modified by AUTHOR only. However depending on the responsible data source, some fields are editable or not, and some other fields are automatically updated by the system.

    The following editability levels are defined in NET:

    • SYSTEM: fields that are updated by the system only and therefore never edited by AUTHOR;
    • RESTRICTED: fields that are editable by AUTHOR only if responsible data source is NET;
    • DEFAULT: fields that are always editable by AUTHOR

    Field Visibility Rules

    Some fields are considered sensitive and as such are only shown to authenticated users.

    The following field visibility levels are defined in NET:

    • READER: fields visible to any READER
    • READER (CFMU): fields visible to any READER whose ANU1 is CFMU
    • AUTHOR: fields visible to AUTHOR only

    Depending on your privileges, some fields may therefore be visible to you - or not...