iSHARE Trust Framework
Other resources
Version 2.1 (current version)
Version 2.1 (current version)
  • iSHARE Trust Framework
  • Introduction
    • Goals and scope of the iSHARE Trust Framework
    • Guiding principles
    • Governance
  • Releases
    • Release notes
    • Release planning
    • Version history
  • Main aspects of the iSHARE Trust Framework
    • Key functionality
      • Support Machine to Machine (M2M) interaction
      • Support Human to Machine (H2M) interaction
      • Facilitate portable identity(s) for parties and humans
      • Facilitate flexible authorizations, applicable in any context
      • Enable data exchange based on delegations - even between unknown parties
      • Enable control over own data through management of consent
      • Provide a Trust Framework
    • Technical overview
    • Framework and roles
    • Legal provisions
    • Operational provisions
  • Use cases
    • Use case: M2M interaction (with fine-grained authorization)
    • Use case: H2M interaction (with coarse-grained authorization)
    • Use case: portable identity
    • Use case: delegation (and management of consent)
  • Detailed descriptions
    • Functional
      • Primary use cases
        • 1. M2M service provision
          • 1b. M2M service provision with the EP as the delegation info PIP
          • 1c. M2M service provision with the AR as the delegation info PIP
          • M2M service provision including an app
        • 2. H2M service provision with identity info at the IP
          • Without Identity Broker
          • With Identity Broker
      • Secondary use cases
      • Licenses
      • Delegation paths
      • Functional requirements per role
        • Party identification
        • User interface requirements
    • Technical
      • Technical standards
      • Structure of delegation evidence
        • Example cases
    • Operational
      • Operational processes
        • Admission
        • Withdrawal or Downgrade
        • Warnings, Suspension and Exclusion
        • Incident Management
        • Change Management
        • Management reporting
      • Service levels
        • Service levels for Adhering Parties
        • Service levels for Certified Parties
      • Communication
    • Legal
      • Legal context
        • Dutch Civil Code
        • Regulation on Electronic Identification and Trust Services (eIDAS)
        • Applicable competition law
        • General Data Protection Regulation (GDPR)
  • Glossary and legal notices
    • Glossary
    • Legal notices
    • Assumptions
Powered by GitBook
LogoLogo

  • Cookie Policy

  • Privacy Policy

  • Imprint

  • Contact Us

Copyright © 2024 iSHARE Foundation

On this page
  • Goal
  • Responsibilities
  • Sequence
  1. Detailed descriptions
  2. Operational
  3. Operational processes

Management reporting

PreviousChange ManagementNextService levels

Last updated 2 months ago

This part of the iSHARE Trust Framework is considered normative and is therefore compliant with RFC 2119.

The management reporting process describes the steps that parties MUST take to deliver management information about the use and working of the iSHARE network.

Goal

The goal of the management reporting process is to monitor compliance to service level agreements, and to distribute info about the use of the iSHARE network.

Responsibilities

Several parties have responsibilities and tasks in the management reporting process:

  • The Scheme Owner is responsible for delivering its own management information on a quarterly basis, and to process received management information into a report that does not include commercially sensitive information;

  • The Data Space Governance Body is responsible for delivering management information timely on a monthly basis to the Scheme Owner.

  • The Certified Party is responsible for delivering management information timely on a monthly basis to the Data Space Governance Body for their data space.

Sequence

  1. On a monthly basis, Certified Parties and the Data Space Governance Body collect management information about:

    1. the use of the data space;

    2. compliance with the service level agreements.

  2. Certified Parties and Data Space Governance Body deliver the collected management information to the Scheme Owner in compliance with the standard format and service level;

  3. The Scheme Owner processes the received management information on compliance, and, if non-compliance is detected, follows the to assess whether this is an incident or structural non-compliance;

  4. The Scheme Owner verifies whether each party's management information on the use of the Trust Framework is correct:

    1. If correct, step 5 follows directly.

    2. If incorrect, a maximum of 5 working days are available for the party to rectify. If 5 working days are not enough, step 5 follows without the incorrect information;

  5. Quarterly, the Scheme Owner processes and anonymises (if necessary) the management information on the use of the Trust Framework into a report containing:

    1. Number of Certified Parties (also compared to last month and this month previous years);

    2. Number of Adhering Parties;

    3. Other information deemed necessary (to be decided); If incorrect information was found and could not be rectified within 5 days in step 4, a description of the missing management information.

  6. The Scheme Owner distributes the management report.

warnings, suspension and exclusion process