nepsi reporting task force’s tasks

NEPSI Reporting Task Force’s Tasks

Select the appropriate contractorSelect the appropriate contractor Customised MappingCustomised Mapping

Prepare and send the EC grant requestPrepare and send the EC grant request

Prepare a list of essential system / contract featuresPrepare a list of essential system / contract features Prepare a list of project deliverablesPrepare a list of project deliverables (Reporting system in 23 (Reporting system in 23 languages, presentation of the tool to the Council, guidance for languages, presentation of the tool to the Council, guidance for use) use)

Prepare guidance to be embedded in the software (use of Prepare guidance to be embedded in the software (use of the software and information to report)the software and information to report) OngoingOngoingArrange translation of software and guidanceArrange translation of software and guidance

Determine and organise training neededDetermine and organise training needed

Check within sectors for specific reporting issuesCheck within sectors for specific reporting issues TodayToday

Define and organise communication strategyDefine and organise communication strategy

… and develop a software meeting SDA requirements and signatory associations’ structures

NEPSI Software Project Timetable

06 September 2007 Site Collection (SC) system design (data collection and consolidation) 13 September 2007 NEPSI TF approval of Site Collection Design28 September 2007 Enrolment System (ES) Design (enrolment of reporting entities from NEPSI to site)28 September 2007 Site Collection system translation begins03 October 2007 NEPSI TF approval of Enrolment System flow charts22 October 2007 NEPSI TF approval of Enrolment System design20 November 2007 Enrolment System translation begins20 November 2007 Unification of SC and ES systems3-20 December 2007 Bata version testing by NEPSI 20-31 December 2007 Final modifications01 January 2007 Handover

The deadline has already expired, but Customised Mapping is working on other features until the NEPSI TF approval (see next slides).

Translations: NEPSI Software and related

documents

Reactivation of Translators’ Network

StartStart BU - BU -

BulgarBulgarCS - CS - CzechCzech

DA - DA - DanishDanish

DE - DE - Germ.Germ.

ET - ET - Eston.Eston.

EL - EL - GreekGreek

EN - EN - EnglisEnglis

Annex III - Reporting FormatAnnex III - Reporting Format NowNow IMAIMA donedone donedone donedone donedone donedone donedone

NEPSI Reporting System GuidanceNEPSI Reporting System Guidance ?? xx xx xx xx xx xx xx

NEPSI Reporting System InstructionsNEPSI Reporting System Instructions 28-09-0728-09-07

Agreement and Good Practice GuideAgreement and Good Practice Guide 20082008 xx donedone donedone donedone donedone donedone donedone

ES - ES - SpanishSpanish

FR - FR - FrenchFrench GA - IrishGA - Irish IT - ItalianIT - Italian LV - LV -

LatvianLatvianLT - LT - Lithuan.Lithuan.

HU - HU - Hungari.Hungari.

MT - MT - MalteseMaltese NL - DutchNL - Dutch

donedone donedone donedone donedone donedone donedone donedone donedone

xx xx xx xx xx xx xx xx

donedone donedone donedone donedone donedone donedone donedone donedone

PL - PolishPL - Polish PT - PT - Portug.Portug.

RO - RO - Roman.Roman.

SK - SK - SlovakSlovak

SL - SL - SloveneSlovene FI - FinnishFI - Finnish SV - SV -

SwedishSwedish

donedone donedone UEPGUEPG donedone donedone donedone donedone

xx xx xx xx xx xx xx

donedone donedone xx donedone donedone donedone donedone

x Subcontracted

Translators’ Network

The network of translation validators used for the Agreement and GPG needs to be reactivated.

TASK: Translate reporting system instructions for site and company level (online, directly into the software, short words and sentences)

START: 28 September 2007, can be made progressively.

FINISH: 20 November 2007

An explanation e-mail will be sent to NEPSI signatories’ secretariats on MONDAY 17 SEPTEMBER, including a list of previous contacts and contacts already found. NEPSI secretariats to contact volunteers themselves. State of affairs and launch of second call on FRIDAY 21 SEPTEMBER.

Progress on Reporting Software

SiteCompany

(national legal entity)

National sector level

European Sector Level (IMA-Europe)

NEPSI Council

European Sector Level (IMA-Europe)

Cc: Group Company

OR

EnglishNational Language

Info available to Unions through NEPSI Council

Deadline for filling in:

01/04/08

NEPSI Council meets:

17-18/06/08

Finalised:

01/05/08

Finalised:

15/05/08

Finalised:

01/04/08

Filling inMay be delegated

to higher levels

Automatic consolidation processAt each level, access to consolidated report and individual reports from members / sites (1 level

below)

Reporting consolidation still under

discussion

Invitation (system enrolment request) Process

Access Rights

Reports Issued

NEPSI Reporting Data Flow: Basic Enrolment Chain

Reporting data flow and access to data

NEPSI SecretariatNEPSI SecretariatDefines and INVITESDefines and INVITES

EU Sector AssociationsEU Sector AssociationsDefine and INVITEDefine and INVITE

Member National Sector Member National Sector AssociationsAssociationsDefine and INVITEDefine and INVITE

Member CompaniesMember CompaniesDefine and INVITEDefine and INVITE

SitesSitesFILL IN REPORTFILL IN REPORT

PublicPublic

National AuthoritiesNational AuthoritiesECEC

NEPSI CouncilNEPSI CouncilISSUESISSUES

NEPSI Council Executive NEPSI Council Executive SummarySummary

NEPSI Council Summary NEPSI Council Summary reportreport

Customised Mapping System

POSSIBILITIES

System reportsBased on the consolidation of

site data at all stages, according to ownership

(invitation) chain

Analyst reports

Ad hoc, flexible, can be

produced by an analyst (DB

management)

NEPSINEPSI

EU Sector AssociationsEU Sector Associations

Member National Sector Member National Sector AssociationsAssociations

Member CompaniesMember Companies

+

NOT COSTED

1. Each hierarchical tier is responsible for the tier below it:

• Enrolment of users at NEPSI, EU Sector, National Sector and Company levels

• Entering of site data at Site level

Possibility for “bulk enrolment”: import of a previously generated list of e-mailaddresses.

Invitations / System enrolment requests

2. The system depends upon a knowledge by each tier of the entities immediately below it

• For a Site to be created there must be an EU Sector, a National Sector and a Company somewhere in the ownership chain

► Each EU sector association should enquire on where levels might be skipped, (e.g. direct company member).

► For direct entering of site data by levels above site, all levels must still be created. 3. Options: review requests, issue reminders, editable list of previous invitation

recipients, incorrectly completed site questionnaires may be unlocked by any tier above it (proxy rights required).

Enrolment procedure: Definition of the entities in the level immediately beneath (e.g. at EU Sector level, enter name of national sector association, sector, country, e-mail address of the contact).

Invitation (system enrolment requests) of defined entities (further users down the enrolment chain) by automatic generation of an e-mail and unique hyperlink for recipient, leading to the switchboard for his level and allowing him to define and invite users further down.

Security: Unique code for identification included in hyperlink, password required.

Consolidation procedure: A (reporting) chain is formed of the different links/nodes enrolled from NEPSI to site. Consolidated reports are ownership-based i.e. consolidation up the invitation chain created from NEPSI to site.

Reporting data flow and access to dataIssues identified

Any node can only have ONE parent

In a company : • Site 1 and site 2 may belong to different sectors• Site 1 may have an extractive and a manufacturing activity. In this

case site 1 should be regarded as 2 sites belonging to 2 different sectorsIn these cases, the “company” node will have two parent national associations

And a national association : • May be a member of several sectors at EU level

The “national association” node will have two parent EU associations

Consolidated reports are ownership-based i.e. consolidation up the invitation chain created from NEPSI to site.

This feature and the fact that any node can only have one parent results in the impossibility for one site report to be consolidated up multiple chains


NEPSI

IMA-Europe

Group Comp 1

Company 3 (UK)

Site 3

UK Association

UEPG

Site 4

Example:

Chain 1

Chain 2

Chain 3


NEPSINEPSI MandatoryMandatory

EU SectorEU Sector MandatoryMandatory

National SectorNational SectorMandatoryMandatory

Group CompanyGroup Company OptionalOptional

CompanyCompany MandatoryMandatory

SiteSite MandatoryMandatory

Reporting data flow and access to dataPossible solution

Reminder: For a Site to be created there must be an EU Sector, a National Sector and a Company somewhere in the ownership chain Current node types and

status:


NEPSINEPSI MandatoryMandatory

EU SectorEU Sector MandatoryMandatory

National SectorNational SectorOptionalOptional

Group CompanyGroup Company OptionalOptional

CompanyCompany MandatoryMandatory

SiteSite MandatoryMandatory

Proposed node types and status:

We cannot have National Sector node AND Group Company node… let’s have one OR the other, which corresponds to our EU associations’ structure…


A meeting between the NEPSI reporting Task Force and the contractor will be arranged to discuss all problematic issues (in the UK).

See mail sent on 14 September by IMA-Europe: meeting to be held between 1 and 5 October in London

Actions for NEPSI Signatories’Secretariats

► If not yet done, send list of national NEPSI Contacts (received: BIBM,

CAEF, CEEMET, CEMBUREAU, CERAME-UNIE, EUROMINES, UEPG)

► Once presentation on reporting received, check for internal specific reporting issues

► Re-activate Translators’ Network and find replacements if needed

► If not yet done, reply to IMA-Europe 31 August mail on Budget issuesA written summary of the meeting will be sent on Monday, 17 September. All participants in the meeting have agreed to send identified reporting issues to the NEPSI Secretariat by the beginning of next week. These will be compiled and forwarded to Customised Mapping. Additional contributions welcome

Conclusion

The system must be flexible enough to easily allow consolidation of site reports in line with the Agreement and signatories’organisation.

The system can not be too flexible as it must allow to:

• Preserve data integrity• Avoid duplication• Ensure data confidentiality• Ensure robust and correct automated reports (outcomes)

nepsi reporting task force’s tasks

Documents