DG-ENVec.europa.eu/environment/waste/shipments/pdf/electronic... · 2016-12-19 · Customer DG-ENV Document Electronic Data Exchange for Waste Shipment Regulation About Main document

European Commission DG ENV - Specific Contract No 000906 - No 07.0201/2015/SI2.708107/ENV/A2

Electronic Data Exchange for Waste Shipment Regulation

Page 1 of 382 ABAROA Consortium

03/10/2016 Final Version

Ver. DATE AUTHOR DESCRIPTION

Final

Version 30/11/2016 ABAROA Final version : Main document

Customer

DG-ENV Document Electronic Data Exchange

for Waste Shipment

Regulation

About Main document that sets out the reporting

package of the Electronic Data Exchange for the

Waste Shipment Regulation study

Edificio Miribilla Santiago Compostela, 12, 4ª A

48003 Bilbao – Spain

Tel: +34 944 276 308 Fax: +34 944 271 547

Bilbao | Madrid | Barcelona | Pamplona





Table of Contents

1 Introduction to Waste Shipment Regulation ........................................................... 19

1.1 Introduction ................................................................................................................................... 19

1.2 Scope ................................................................................................................................................ 19

1.3 Definitions ...................................................................................................................................... 20

1.4 Methodology................................................................................................................................. 21

1.5 Current Situation .......................................................................................................................... 22

2 Solution overview ....................................................................................................... 22

2.1 Integration ...................................................................................................................................... 22

2.1.1 Adapter Example ..................................................................................................................... 23

2.2 API Protocol ................................................................................................................................... 25

2.3 Security Considerations............................................................................................................. 28

2.3.1 System security ........................................................................................................................ 28

2.3.2 Digital Signatures and SSL Certificates .......................................................................... 34

2.3.3 Timestamps ............................................................................................................................... 35

2.3.4 Monitoring / Logging ........................................................................................................... 36

2.3.5 Message Inspection ............................................................................................................... 37

3 Links to annexes ......................................................................................................... 38

4 Links to accompanying documents .......................................................................... 38

5 Conclusion ................................................................................................................... 38

ANNEX 1: Domain Objects ................................................................................................. 42

1 Introduction ................................................................................................................ 42

2 Domain Objects .......................................................................................................... 42

2.1 Acknowledgement ...................................................................................................................... 44

2.2 Address ............................................................................................................................................ 45

2.3 Agent ................................................................................................................................................ 46





2.4 AgentAuthorisations .................................................................................................................. 49

2.5 Carrier ............................................................................................................................................... 50

2.6 Comment ........................................................................................................................................ 50

2.7 CompetentAuthority .................................................................................................................. 52

2.8 ConcernedCountry ...................................................................................................................... 54

2.9 Contract ........................................................................................................................................... 55

2.10 Country ............................................................................................................................................ 57

2.11 CustomsOffice............................................................................................................................... 58

2.12 Facility .............................................................................................................................................. 59

2.13 FacilityPreconsent ........................................................................................................................ 60

2.14 FinalCarrier ..................................................................................................................................... 63

2.15 FinancialGuarantee ..................................................................................................................... 65

2.16 Illegality ........................................................................................................................................... 66

2.17 InformationRequest .................................................................................................................... 69

2.18 IntendedCarrier ............................................................................................................................ 70

2.19 MovementDocument ................................................................................................................. 71

2.20 MovementShipment ................................................................................................................... 75

2.21 Notification .................................................................................................................................... 76

2.22 NotificationAttachment ............................................................................................................. 80

2.23 NotificationShipment ................................................................................................................. 81

2.24 Notifier ............................................................................................................................................. 83

2.25 Objection ........................................................................................................................................ 84

2.26 ObjectionType............................................................................................................................... 87

2.27 Operation ........................................................................................................................................ 88

2.28 Passage ............................................................................................................................................ 92

2.29 Quantity ........................................................................................................................................... 93

2.30 Receipt ............................................................................................................................................. 95

2.31 RecoveryDisposal ......................................................................................................................... 98

2.32 Request ............................................................................................................................................ 99

2.33 RouteCustomsOffice .................................................................................................................. 99





2.34 RouteSection ............................................................................................................................... 101

2.35 Routing .......................................................................................................................................... 102

2.36 UNClass ......................................................................................................................................... 104

2.37 Waste.............................................................................................................................................. 106

2.38 WasteIdentification ................................................................................................................... 106

2.39 WasteProducer ........................................................................................................................... 110

2.40 WrittenConsent .......................................................................................................................... 111

2.41 CommentType ............................................................................................................................ 114

2.42 ConcernedCountryType .......................................................................................................... 114

2.43 IllegalShipmentType ................................................................................................................. 115

2.44 IllegalityResponsibleType ....................................................................................................... 116

2.45 MeansOfTransport .................................................................................................................... 117

2.46 NotificationStatus ...................................................................................................................... 117

2.47 OperationCode ........................................................................................................................... 118

2.48 OperationStage .......................................................................................................................... 123

2.49 OperationType ............................................................................................................................ 123

2.50 PackagingType............................................................................................................................ 124

2.51 PhysicalCharacteristic ............................................................................................................... 124

2.52 QuantityUnit ................................................................................................................................ 125

2.53 RequestType ................................................................................................................................ 125

2.54 RoleType ....................................................................................................................................... 126

2.55 RoutePointType .......................................................................................................................... 127

2.56 ShipmentStatus .......................................................................................................................... 127

2.57 ShipmentType ............................................................................................................................. 128

2.58 StatusType .................................................................................................................................... 128

ANNEX 2: Requirements Model ...................................................................................... 129

1. Introduction .............................................................................................................. 129

2. Requirements Model ................................................................................................ 129

2.1 Requirements Model diagram .............................................................................................. 130





2.2 Activity Diagrams ....................................................................................................................... 131

2.2.1 Process Notification ............................................................................................................. 131

2.2.2 Process Information Request ........................................................................................... 143

2.2.3 Process Objection ................................................................................................................. 145

2.3 Requirements .............................................................................................................................. 146

2.3.1 Central Application .............................................................................................................. 146

2.3.2 Shared Application ............................................................................................................... 247

2.3.3 Non-Functional ...................................................................................................................... 258

ANNEX 3: Service Definition ............................................................................................ 265

1 Introduction .............................................................................................................. 265

2 Service Definition ..................................................................................................... 265

2.1 Services .......................................................................................................................................... 267

2.2 Bindings ......................................................................................................................................... 269

2.2.1 bdComments .......................................................................................................................... 271

2.2.2 bdInformationRequest ........................................................................................................ 273

2.2.3 bdMovementDoc .................................................................................................................. 276

2.2.4 bdNotification ........................................................................................................................ 282

2.2.5 bdNotificationDoc ................................................................................................................ 285

2.2.6 bdObjections .......................................................................................................................... 290

2.2.7 bdPreConsents ....................................................................................................................... 293

2.2.8 bdTransverse .......................................................................................................................... 296

2.3 PortTypes ...................................................................................................................................... 299

2.4 Messages ...................................................................................................................................... 301

2.4.1 msgAcknowledgeNotificationRequest ......................................................................... 303

2.4.2 msgAcknowledgeNotificationResponse ...................................................................... 303

2.4.3 msgAddCommentRequest ................................................................................................ 303

2.4.4 msgAddCommentResponse ............................................................................................. 303

2.4.5 msgApproveNotificationRequest ................................................................................... 303

2.4.6 msgApproveNotificationResponse ................................................................................ 304





2.4.7 msgCloseInformationRequestRequest ......................................................................... 304

2.4.8 msgCloseInformationRequestResponse ...................................................................... 304

2.4.9 msgCloseObjectionRequest ............................................................................................. 304

2.4.10 msgCloseObjectionResponse .......................................................................................... 304

2.4.11 msgConfirmReceiptRequest ............................................................................................. 305

2.4.12 msgConfirmReceiptResponse .......................................................................................... 305

2.4.13 msgConfirmRecoveryDisposalRequest ........................................................................ 305

2.4.14 msgConfirmRecoveryDisposalResponse ..................................................................... 305

2.4.15 msgCreateConsentRequest .............................................................................................. 305

2.4.16 msgCreateConsentResponse ........................................................................................... 306

2.4.17 msgCreateInformationRequestRequest ....................................................................... 306

2.4.18 msgCreateInformationRequestResponse .................................................................... 306

2.4.19 msgCreateMovementDocRequest ................................................................................. 306

2.4.20 msgCreateMovementDocResponse .............................................................................. 306

2.4.21 msgCreateNotificationDocRequest ............................................................................... 307

2.4.22 msgCreateNotificationDocResponse ............................................................................ 307

2.4.23 msgCreateObjectionRequest ........................................................................................... 307

2.4.24 msgCreateObjectionResponse ........................................................................................ 307

2.4.25 msgCreateReasonedExplanationRequest .................................................................... 307

2.4.26 msgCreateReasonedExplanationResponse................................................................. 308

2.4.27 msgCustodyTransferRequest ........................................................................................... 308

2.4.28 msgCustodyTransferResponse ........................................................................................ 308

2.4.29 msgDeleteCommentRequest ........................................................................................... 308

2.4.30 msgDeleteCommentResponse ........................................................................................ 308

2.4.31 msgExtendConsentPeriodRequest ................................................................................. 309

2.4.32 msgExtendConsentPeriodResponse .............................................................................. 309

2.4.33 msgExtendPeriodRequest ................................................................................................. 309

2.4.34 msgExtendPeriodResponse .............................................................................................. 309

2.4.35 msgIllegalShipmentRequest ............................................................................................. 309

2.4.36 msgIllegalShipmentResponse .......................................................................................... 310





2.4.37 msgIssuePreConsentRequest ........................................................................................... 310

2.4.38 msgIssuePreConsentResponse ........................................................................................ 310

2.4.39 msgRecordPassageRequest .............................................................................................. 310

2.4.40 msgRecordPassageResponse ........................................................................................... 310

2.4.41 msgReopenInformationRequestRequest .................................................................... 311

2.4.42 msgReopenInformationRequestResponse ................................................................. 311

2.4.43 msgReopenObjectionRequest ......................................................................................... 311

2.4.44 msgReopenObjectionResponse ...................................................................................... 311

2.4.45 msgRevokePreConsentRequest ...................................................................................... 311

2.4.46 msgRevokePreConsentResponse ................................................................................... 312

2.4.47 msgSearchAgentRequest .................................................................................................. 312

2.4.48 msgSearchAgentResponse ............................................................................................... 312

2.4.49 msgSearchNotificationRequest ....................................................................................... 312

2.4.50 msgSearchNotificationResponse .................................................................................... 312

2.4.51 msgSearchWasteRequest .................................................................................................. 313

2.4.52 msgSearchWasteResponse ............................................................................................... 313

2.4.53 msgSolveInformationRequestRequest ......................................................................... 313

2.4.54 msgSolveInformationRequestResponse ...................................................................... 313

2.4.55 msgSolveObjectionRequest.............................................................................................. 313

2.4.56 msgSolveObjectionResponse .......................................................................................... 314

2.4.57 msgSubmitNotificationRequest ...................................................................................... 314

2.4.58 msgSubmitNotificationResponse ................................................................................... 314

2.4.59 msgUpdateCommentRequest ......................................................................................... 314

2.4.60 msgUpdateCommentResponse ...................................................................................... 314

2.4.61 msgUpdateMovementDocRequest ............................................................................... 315

2.4.62 msgUpdateMovementDocResponse ............................................................................ 315

2.4.63 msgUpdateNotificationDocRequest ............................................................................. 315

2.4.64 msgUpdateNotificationDocResponse .......................................................................... 315

2.4.65 msgWithdrawConsentRequest ........................................................................................ 315

2.4.66 msgWithdrawConsentResponse ..................................................................................... 316





2.5 Types .............................................................................................................................................. 316

2.5.1 AcknowledgeNotificationRequestType ........................................................................ 318

2.5.2 AcknowledgeNotificationResponseType ..................................................................... 318

2.5.3 AddCommentRequestType ............................................................................................... 319

2.5.4 AddCommentResponseType ............................................................................................ 320

2.5.5 ApproveNotificationRequestType .................................................................................. 320

2.5.6 ApproveNotificationResponseType ............................................................................... 321

2.5.7 CloseInformationRequestRequestType ........................................................................ 322

2.5.8 CloseInformationRequestResponseType ..................................................................... 322

2.5.9 CloseObjectionRequestType ............................................................................................ 323

2.5.10 CloseObjectionResponseType ......................................................................................... 324

2.5.11 ConfirmReceiptRequestType ............................................................................................ 324

2.5.12 ConfirmReceiptResponseType ......................................................................................... 325

2.5.13 ConfirmRecoveryDisposalRequestType ....................................................................... 326

2.5.14 ConfirmRecoveryDisposalResponseType .................................................................... 327

2.5.15 CreateConsentRequestType ............................................................................................. 327

2.5.16 CreateConsentResponseType .......................................................................................... 328

2.5.17 CreateInformationRequestRequestType ...................................................................... 329

2.5.18 CreateInformationRequestResponseType ................................................................... 330

2.5.19 CreateMovementDocRequestType ................................................................................ 330

2.5.20 CreateMovementDocResponseType ............................................................................. 332

2.5.21 CreateNotificationDocRequestType .............................................................................. 332

2.5.22 CreateNotificationDocResponseType ........................................................................... 333

2.5.23 CreateObjectionRequestType .......................................................................................... 334

2.5.24 CreateObjectionResponseType ....................................................................................... 335

2.5.25 CreateReasonedExplanationRequestType .................................................................. 336

2.5.26 CreateReasonedExplanationResponseType ............................................................... 337

2.5.27 CustodyTransferRequestType .......................................................................................... 337

2.5.28 CustodyTransferResponseType ....................................................................................... 338

2.5.29 DeleteCommentRequestType .......................................................................................... 339





2.5.30 DeleteCommentResponseType ....................................................................................... 339

2.5.31 ExtendConsentPeriodRequestType ................................................................................ 340

2.5.32 ExtendConsentPeriodResponseType ............................................................................ 341

2.5.33 ExtendPeriodRequestType ................................................................................................ 342

2.5.34 ExtendPeriodResponseType ............................................................................................. 342

2.5.35 IllegalShipmentRequestType ............................................................................................ 343

2.5.36 IllegalShipmentResponseType......................................................................................... 344

2.5.37 IssuePreConsentRequestType .......................................................................................... 345

2.5.38 IssuePreConsentResponseType ....................................................................................... 346

2.5.39 RecordPassageRequestType............................................................................................. 346

2.5.40 RecordPassageResponseType ......................................................................................... 347

2.5.41 ReopenInformationRequestRequestType ................................................................... 348

2.5.42 ReopenInformationRequestResponseType ................................................................ 349

2.5.43 ReopenObjectionRequestType ........................................................................................ 349

2.5.44 ReopenObjectionResponseType ..................................................................................... 350

2.5.45 RevokePreConsentRequestType ..................................................................................... 351

2.5.46 RevokePreConsentResponseType .................................................................................. 351

2.5.47 SearchAgentRequestType ................................................................................................. 352

2.5.48 SearchAgentResponseType .............................................................................................. 352

2.5.49 SearchNotificationRequestType ...................................................................................... 354

2.5.50 SearchNotificationResponseType ................................................................................... 354

2.5.51 SearchWasteRequestType ................................................................................................. 355

2.5.52 SearchWasteResponseType .............................................................................................. 356

2.5.53 SolveInformationRequestRequestType ........................................................................ 356

2.5.54 SolveInformationRequestResponseType ..................................................................... 357

2.5.55 SolveObjectionRequestType ............................................................................................ 357

2.5.56 SolveObjectionResponseType ......................................................................................... 358

2.5.57 SubmitNotificationRequestType ..................................................................................... 359

2.5.58 SubmitNotificationResponseType .................................................................................. 359

2.5.59 UpdateCommentRequestType ........................................................................................ 360





2.5.60 UpdateCommentResponseType ..................................................................................... 360

2.5.61 UpdateMovementDocRequestType .............................................................................. 361

2.5.62 UpdateMovementDocResponseType ........................................................................... 362

2.5.63 UpdateNotificationDocRequestType ............................................................................ 363

2.5.64 UpdateNotificationDocResponseType ......................................................................... 364

2.5.65 WithdrawConsentRequestType ....................................................................................... 364

2.5.66 WithdrawConsentResponseType .................................................................................... 365

2.5.67 acknowledgeNotificationRequest .................................................................................. 366

2.5.68 acknowledgeNotificationResponse ............................................................................... 366

2.5.69 addCommentRequest ......................................................................................................... 366

2.5.70 addCommentResponse ...................................................................................................... 366

2.5.71 approveNotificationRequest ............................................................................................ 367

2.5.72 approveNotificationResponse ......................................................................................... 367

2.5.73 closeInformationRequestRequest .................................................................................. 367

2.5.74 closeInformationRequestResponse ............................................................................... 367

2.5.75 closeObjectionRequest ....................................................................................................... 368

2.5.76 closeObjectionResponse .................................................................................................... 368

2.5.77 confirmReceiptRequest ...................................................................................................... 368

2.5.78 confirmReceiptResponse ................................................................................................... 368

2.5.79 confirmRecoveryDisposalRequest .................................................................................. 369

2.5.80 confirmRecoveryDisposalResponse ............................................................................... 369

2.5.81 createConsentRequest ........................................................................................................ 369

2.5.82 createConsentResponse ..................................................................................................... 369

2.5.83 createInformationRequestRequest ................................................................................ 370

2.5.84 createInformationRequestResponse ............................................................................. 370

2.5.85 createMovementDocRequest .......................................................................................... 370

2.5.86 createMovementDocResponse ....................................................................................... 370

2.5.87 createNotificationDocRequest......................................................................................... 371

2.5.88 createNotificationDocResponse ..................................................................................... 371

2.5.89 createObjectionRequest ..................................................................................................... 371





2.5.90 createObjectionResponse.................................................................................................. 371

2.5.91 createReasonedExplanationRequest ............................................................................. 372

2.5.92 createReasonedExplanationResponse .......................................................................... 372

2.5.93 custodyTransferRequest ..................................................................................................... 372

2.5.94 custodyTransferResponse.................................................................................................. 372

2.5.95 deleteCommentRequest .................................................................................................... 373

2.5.96 deleteCommentResponse ................................................................................................. 373

2.5.97 extendConsentPeriodRequest ......................................................................................... 373

2.5.98 extendConsentPeriodResponse ...................................................................................... 373

2.5.99 extendPeriodRequest .......................................................................................................... 374

2.5.100 extendPeriodResponse ....................................................................................................... 374

2.5.101 illegalShipmentRequest...................................................................................................... 374

2.5.102 illegalShipmentResponse .................................................................................................. 374

2.5.103 issuePreConsentRequest.................................................................................................... 375

2.5.104 issuePreConsentResponse ................................................................................................ 375

2.5.105 recordPassageRequest ....................................................................................................... 375

2.5.106 recordPassageResponse .................................................................................................... 375

2.5.107 reopenInformationRequestRequest .............................................................................. 376

2.5.108 reopenInformationRequestResponse ........................................................................... 376

2.5.109 reopenObjectionRequest ................................................................................................... 376

2.5.110 reopenObjectionResponse................................................................................................ 376

2.5.111 revokePreConsentRequest ................................................................................................ 377

2.5.112 revokePreConsentResponse ............................................................................................. 377

2.5.113 searchAgentRequest ............................................................................................................ 377

2.5.114 searchAgentResponse ........................................................................................................ 377

2.5.115 searchNotificationRequest ................................................................................................ 378

2.5.116 searchNotificationResponse ............................................................................................. 378

2.5.117 searchWasteRequest ........................................................................................................... 378

2.5.118 searchWasteResponse ........................................................................................................ 378

2.5.119 solveInformationRequestRequest .................................................................................. 379





2.5.120 solveInformationRequestResponse ............................................................................... 379

2.5.121 solveObjectionRequest ....................................................................................................... 379

2.5.122 solveObjectionResponse .................................................................................................... 379

2.5.123 submitNotificationRequest ............................................................................................... 380

2.5.124 submitNotificationResponse ............................................................................................ 380

2.5.125 updateCommentRequest .................................................................................................. 380

2.5.126 updateCommentResponse ............................................................................................... 380

2.5.127 updateMovementDocRequest ........................................................................................ 381

2.5.128 updateMovementDocResponse ..................................................................................... 381

2.5.129 updateNotificationDocRequest ....................................................................................... 381

2.5.130 updateNotificationDocResponse .................................................................................... 381

2.5.131 withdrawConsentRequest .................................................................................................. 382

2.5.132 withdrawConsentResponse .............................................................................................. 382





Index of Figures

Figure 1: Integration Architecture ............................................................................................................ 23

Figure 2: SOAP communication ................................................................................................................ 26

Figure 3: SOAP envelope ............................................................................................................................. 27

Figure 4: Proposed Architecture – Authentication............................................................................. 33

Figure 5: SOAP digital signatures ............................................................................................................. 34

Figure 6: Trusted timestamping ................................................................................................................ 36

Figure 7: ICAP SOAP malware inspection .............................................................................................. 37

Figure 8: Domain Objects ............................................................................................................................ 43

Figure 9: Acknowledgement ....................................................................................................................... 44

Figure 10: Address ............................................................................................................................................ 45

Figure 11: Agent ................................................................................................................................................ 46

Figure 12: AgentAuthorisations ................................................................................................................... 49

Figure 13: Carrier ............................................................................................................................................... 50

Figure 14: Comment ........................................................................................................................................ 51

Figure 15: CompetentAuthority ................................................................................................................... 52

Figure 16: ConcernedCountry ...................................................................................................................... 54

Figure 17: Contract ........................................................................................................................................... 56

Figure 18: Country ............................................................................................................................................ 57

Figure 19: CustomsOffice ............................................................................................................................... 59

Figure 20: Facility ............................................................................................................................................... 59

Figure 21: FacilityPreconsent ........................................................................................................................ 60





Figure 22: FinalCarrier ...................................................................................................................................... 63

Figure 23: FinancialGuarantee ...................................................................................................................... 65

Figure 24: Illegality ............................................................................................................................................ 67

Figure 25: InformationRequest .................................................................................................................... 69

Figure 26: IntentedCarrier .............................................................................................................................. 70

Figure 27: MovementDocument ................................................................................................................. 72

Figure 28: MovementShipment ................................................................................................................... 75

Figure 29: Notification ..................................................................................................................................... 76

Figure 30: NotificationAttachment ............................................................................................................. 80

Figure 31: NotificationShipment ................................................................................................................. 81

Figure 32: Notifier ............................................................................................................................................. 83

Figure 33: Objection ......................................................................................................................................... 84

Figure 34: ObjectionType ............................................................................................................................... 87

Figure 35: Operation ........................................................................................................................................ 88

Figure 36: Passage ............................................................................................................................................ 92

Figure 37: Quantity ........................................................................................................................................... 94

Figure 38: Receipt ............................................................................................................................................. 95

Figure 39: RecoveryDisposal ......................................................................................................................... 98

Figure 40: Request ............................................................................................................................................ 99

Figure 41: RouteCustomsOffice ................................................................................................................. 100

Figure 42: RouteSection................................................................................................................................ 101

Figure 43: Routing .......................................................................................................................................... 102

Figure 44: UNClass .......................................................................................................................................... 105





Figure 45: Waste .............................................................................................................................................. 106

Figure 46: WasteIdentification ................................................................................................................... 107

Figure 47: WasteProducer ............................................................................................................................ 110

Figure 48: WrittenConsent ........................................................................................................................... 111

Figure 49: Requirements Model ................................................................................................................ 130

Figure 50: Process Notification activity ................................................................................................... 132

Figure 51: Action-Requirement Matrix ................................................................................................... 133









Figure 60: Process Information Request activity ................................................................................. 144


Figure 62: Process Objection activity ....................................................................................................... 145


Figure 64: Central Application .................................................................................................................... 146

Figure 65: Create consent_ActivityGraphWithAction ........................................................................ 149

Figure 66: Create consent - Export_ActivityGraphWithAction ....................................................... 152

Figure 67: Withdraw consent_ActivityGraphWithAction .................................................................. 154





Figure 68: Create notification document_ActivityGraphWithAction ........................................... 157

Figure 69: Create notification document ............................................................................................... 158

Figure 70: Acknowledge notification_ActivityGraphWithAction ................................................... 167

Figure 71: Acknowledge notification - Export/Import_ActivityGraphWithAction .................. 170

Figure 72: Create movement document_ActivityGraphWithAction ............................................ 173

Figure 73: Create movement document ................................................................................................ 174

Figure 74: Start shipment_ActivityGraphWithAction ......................................................................... 180

Figure 75: Custody transfer_ActivityGraphWithAction ..................................................................... 182

Figure 76: Record passage_ActivityGraphWithAction ....................................................................... 184

Figure 77: Illegal shipment_ActivityGraphWithAction ...................................................................... 186

Figure 78: Confirm receipt_ActivityGraphWithAction ....................................................................... 189

Figure 79: Confirm recovery/disposal_ActivityGraphWithAction ................................................. 192

Figure 80: Create information request_ActivityGraphWithAction ................................................ 198

Figure 81: Create information request .................................................................................................... 199

Figure 82: Create information request - Export/Import_ActivityGraphWithAction .............. 201

Figure 83: Create information request .................................................................................................... 202

Figure 84: Solve information request_ActivityGraphWithAction .................................................. 203

Figure 85: Reopen information request_ActivityGraphWithAction.............................................. 205

Figure 86: Close information request_ActivityGraphWithAction .................................................. 207

Figure 87: Create objection_ActivityGraphWithAction ..................................................................... 213

Figure 88: Create objection ......................................................................................................................... 213

Figure 89: Solve objection_ActivityGraphWithAction ....................................................................... 218

Figure 90: Reopen objection_ActivityGraphWithAction ................................................................... 220





Figure 91: Close objection_ActivityGraphWithAction ....................................................................... 222

Figure 92: Issue pre-consent_ActivityGraphWithAction ................................................................... 224

Figure 93: Revoke pre-consent_ActivityGraphWithAction .............................................................. 226

Figure 94: Extend period_ActivityGraphWithAction .......................................................................... 227

Figure 95: Extend consent period_ActivityGraphWithAction ......................................................... 229

Figure 96: Add comment_ActivityGraphWithAction .......................................................................... 231

Figure 97: Update comment_ActivityGraphWithAction ................................................................... 233

Figure 98: Delete comment_ActivityGraphWithAction ..................................................................... 235

Figure 99: Approve notification_ActivityGraphWithAction ............................................................. 237

Figure 100: Create reasoned explanation ................................................................................................ 238

Figure 101: Create reasoned explanation_ActivityGraphWithAction ............................................. 239

Figure 102: Submit notification_ActivityGraphWithAction ................................................................ 241

Figure 103: Search agent_ActivityGraphWithAction ............................................................................ 243

Figure 104: Search notification_ActivityGraphWithAction ................................................................. 245

Figure 105: Search waste_ActivityGraphWithAction ............................................................................ 247

Figure 106: Shared Application .................................................................................................................... 248

Figure 107: Agent management .................................................................................................................. 249

Figure 108: Notification not transmitted_ActivityGraphWithAction .............................................. 253

Figure 109: Notification not acknowledged_ActivityGraphWithAction ........................................ 255

Figure 110: Tacit consent_ActivityGraphWithAction ............................................................................ 256

Figure 111: Waste not received_ActivityGraphWithAction ................................................................ 258

Figure 112: Non-Functional Requirements.............................................................................................. 259

Figure 113: Performance ................................................................................................................................. 260





Figure 114: Scalability ...................................................................................................................................... 261

Figure 115: Security .......................................................................................................................................... 262

Figure 116: Testability ...................................................................................................................................... 263

Figure 117: Usability ......................................................................................................................................... 263

Figure 118: Overview ........................................................................................................................................ 266

Figure 119: WasteService ................................................................................................................................ 268

Figure 120: Bindings ......................................................................................................................................... 270

Figure 121: PortTypes ...................................................................................................................................... 300

Figure 122: Messages ....................................................................................................................................... 302

Figure 123: Types ............................................................................................................................................... 317





1 Introduction to Waste Shipment Regulation

1.1 Introduction

The European Union (EU) has a system to supervise and control shipments of waste within

its borders and within the countries of the European Free Trade Association (EFTA),

the Organisation for Economic Cooperation and Development (OECD) and non-EU

countries that have signed the Basel Convention.

It lays down rules for controlling waste shipments in order to improve environmental

protection.

It also incorporates the provisions of the Basel Convention and the revision of the OECD’s

2001 decision on the control of transboundary movements of wastes destined for recovery

operations in EU law (i.e. where a waste is processed to recover a usable product or

converted into a fuel).

Regulation (EC) No 1013/2006 of the European Parliament specifies the procedures for

controlling waste shipments. This Regulation applies to waste shipments:

between EU countries within the EU or transiting via non-EU countries;

imported into the EU from non-EU countries;

exported from the EU to non-EU countries;

in transit through the EU, on the way to or from non-EU countries.

It covers almost all types of waste, with the exception of radioactive waste; waste generated

on board ships; shipments subject to the approval requirements of the animal by-product

regulation; certain shipments of waste from the Antarctic; imports into the EU of certain

waste generated by armed forces or relief organisations in situations of crisis, etc.

1.2 Scope

The scope of this project is producing a technical study which proposes a software solution

with a sufficient level of technical detail to begin its subsequent development, taking into

account the current situation (described below).

http://www.efta.int/

http://www.oecd.org/

http://eur-lex.europa.eu/legal-content/EN/AUTO/?uri=uriserv:l28043


http://www.oecd.org/env/waste/30654501.pdf




http://eur-lex.europa.eu/legal-content/EN/AUTO/?uri=uriserv:sa0025

http://eur-lex.europa.eu/legal-content/EN/AUTO/?uri=uriserv:sa0025





This study consists of a reporting package which defines the technical and organisational

requirements for the practical implementation of an Electronic Data Interchange (EDI) for

the submission of documents and information in accordance with the newly amended

Article 26(4) of Regulation (EC) No 1013/2006. It describes the protocol of data exchange

forming the basis for the Commission to adopt an implementing act establishing the

technical and organisational requirements for the practical implementation of EDI for the

submission of documents and information.

This report makes up the reporting package and includes an introduction to the study, the

solution overview, technical annexes and links to accompanying documents. It is made up

of the following main sections:

The first section (Introduction to Waste Shipment Regulation) outlines the context

of Waste Shipment Regulation, describes the scope of the project, defines the used

methodology and provides an overview of the current situation.

The second section (Solution overview) covers aspects of the proposal related to

integration, communication and security.

The third section (Links to related annexes) lists the individual annexes providing

technical details of the proposal: data model, functional/non-functional

requirements and services.

The fourth section (Links to annexes) refers to additional information used in the

study, such as survey results and feedback from Waste Shipment Regulation

stakeholders and the additional resources generated.

The fifth section (Conclusion) sums up the main aspects of the project.

Finally, included as separated annexes: Domain Objects, Requirements Model and

Service Definition.

1.3 Definitions

This section is an overview of terms used throughout this document:

Subject Description

API Application Programming Interface is a set of routines, protocols and tools for building

software applications. It expresses a software component in terms of its operations, inputs,

outputs and underlying types, defining functionalities that are independent of their respective

implementations. This allows definitions and implementations to vary without compromising

the interface.

Agent Any user (Producer, Licensed producer, Collector, Dealer, Broker, Disposal facility, Recovery





facility or Laboratory) participating in the Waste Shipment Regulation.

CA Competent Authority

EU Login Authentication service of the European Commission allowing users to access a wide range

of Commission information systems, using a single username and password. Once a user is

logged in, EU Login will remember the user as long as the browser is kept open. During that

time, users do not have to identify themselves again, no matter how many online services of

the Commission are accessed

EDI Electronic Data Interchange

ICAP Internet Content Adaptation Protocol

IT Information Technology

JSON JavaScript Object Notation

REST Representational State Transfer

SaaS Software as a Service

SMS Short Message Service

SOAP Simple Object Access Protocol

SSL Secure Sockets Layer is a cryptographic protocol designed to provide communication

security over a computer network

SSO Single Sign-On

UML Unified Modeling Language

WSDL Web Services Description Language is an XML-based interface definition language that is

used for describing the functionality offered by a web service; providing a machine-readable

description of how the service can be called, what parameters it expects and what data

structures it returns

WSR Waste Shipments Regulation

XML eXtensible Markup Language

1.4 Methodology

A series of steps and tools to use have been previously defined for this study in order to

submit a high quality technical and functional proposal.

In a first phase, a feasibility analysis review of all documentation surrounding the Waste

Shipment Regulation was conducted.

Having gathered the information, ABAROA defined the data model in line with Regulation

(EC) No 1013/2006, using Unified Modeling Language (UML).

Next, ABAROA defined the business rules, message protocol and safety of the proposed

system, according to the entities diagram.

Given the magnitude of the project and the importance of cooperation between the

relevant entities, small draft deliverables involving their participation have been produced.





This has been accomplished either through surveys or feedback and comments provided by

email.

Highly specialized experts in waste management and evaluation have been involved in the

project, reviewing and validating the obtained deliverables. These are experts with extensive

work experience with public entities and with relevant participation in the functional design

of a management computer system for environmental sector companies.

The European Commission has also been actively involved, clarifying issues and answering

questions.

Enterprise Architect has been used as a design tool for UML, business rules, Web Services

and structuring/generating documentation.

1.5 Current Situation

Based on the previously performed study of TRASYS1, the current situation is characterized

by the wide variety of existing tools, where each owner covers certain regulatory

requirements electronically. The need for an EU-wide solution which respects and allows for

the possible integration and adaptation of all existing tools arises from this current

situation.

2 Solution overview

2.1 Integration

The proposed solution was based on a hybrid topology architecture consisting of a Central

Application and a Shared Application for Member States having no solution of their own.

The key elements of this architecture are as follows:

The purpose of the Central Application is to act as a central point of communication for

all national systems, maintaining the required Waste Shipments information in a central

1 http://ec.europa.eu/environment/waste/shipments/pdf/4a_Annex%202_Review_of_IT_systems_EDI_for_WSR.pdf

http://ec.europa.eu/environment/waste/shipments/pdf/4a_Annex%202_Review_of_IT_systems_EDI_for_WSR.pdf





database. The business logic will be located here and will be consumed directly by Member

State systems as well as by the Shared Application.

Shared Application is a web application that can be accessed by all parties of Member

States not having an existing IT solution.

Waste Shipment Systems are IT solutions already in place which are managed by

Member States. Member States will be able to connect their own national systems to the

Central Application. Existing national systems would need to implement an 'Adapter' to

transform messages to and from their data format to the Central Application data format.

Figure 1: Integration Architecture

The main advantage of this architecture integration is that it supports both Member States

with existing systems and Member States without solutions of their own. Furthermore,

single common back office business logic will be used independently of the integration

method.

The scope of the proposed solution comprises the entire Waste Shipment Regulation. The

aim is to support all documents and information to be transmitted electronically even if it

co-exists with the paper form. The system is divided into different logical modules allowing

for a step-by-step adoption. Therefore, those parts that cannot be used at a particular

moment or that may be used at a later stage (for example, pre-consented facilities), can be

integrated/included in those later stages.

2.1.1 Adapter Example

The UN/CEFACT standard is already supported by several Member States systems, such as

EUDIN and Nordic TFS. For a complete list of IT systems, please consult ‘Annex 2: Review of

Waste Shipment System

Member State

Shared Application(Website)



Member State

Member State

Member State

Member State

Member State

Central Application(API)

Adapter

Adapter

Adapter





IT systems, studies and projects’ document at

http://ec.europa.eu/environment/waste/shipments/studies.html

The following example shows the data correspondence between UN/CEFACT and the

defined solution that an adapter should take into consideration before calling 'Central

Application (API)'.

In particular, the following example table details the data type correspondences in order to

confirm the receipt of the waste by the facility. This example shows how the defined

solution goes beyond what it is defined by UN/CEFACF, including all the data requirements

defined in the Regulation (EC) No 1013/2006.

In the left-hand column the 'ConfirmReceiptRequestType' data type attributes are

listed; which it is the request parameter for the Web Service operation defined to

confirm waste receipts by facilities.

In the right-hand column UN/CEFACT 'TMWCertificateOfWasteReceiptMessage' data

type attributes are listed regarding 'written confirmation of receipt of the waste'.

WSR - ConfirmReceiptRequestType UN/CEFACT version="5.0" - TMWCertificateOfWasteReceiptMessage

movementDocumentID ReferencedWasteTransportMovement

receipt/receivedOn ReceivedWasteMaterial/ReceiptDateTime

receipt/rejected ReceivedWasteMaterial/RejectionIndicator

receipt/rejectionReason ReceivedWasteMaterial/RejectionReason

receipt/receivedWasteQuantity Not found. However, if the waste quantity has not changed, it could

be derived from the notification document.

receipt/receivedWasteUnit Not found. However, if the waste quantity unit has not changed, it

could be derived from the notification document.

http://ec.europa.eu/environment/waste/shipments/studies.htm





receipt/operationCode Not found. However, if the operation code has not changed, it could

be derived from the notification document.

receipt/facilityType Not found. However, if the facility type has not changed, it could be

derived from the notification document.

receipt/approximateDate Not found.

2.2 API Protocol

Different software systems will need to exchange data to comply with Regulation (EC) No

1013/2006 regarding transboundary waste movement processes. ABAROA therefore,

recommended EDI protocol which is a SOAP-based Web Services; a method of

communication allowing software systems to exchange data over the Internet. More

lightweight solutions, such as REST Web Services (REST-XML, REST-JSON) may be used for

the 'Shared Application'. However, REST is not recommended for incoming requests from

external systems to the 'Central Application'. REST inherits security measures from the

underlying transport, meaning that all security measures applied to HTTP are inherited. This

transport level security, secures messages only while they are on the wire.

In contrast to the above, SOAP defines its security via WS-Security with added extensions

over the years, (XML-Encryption, XML-Signature, etc.) to deal with specific transactional

messaging security considerations. It has been adopted by well-known consortiums such as

OASIS and W3C. WS-Security stablishes a message level security - even if messages leave

the transport channel, they are still protected and also allow to partly encrypt messages.

This cannot be done with transport level security.

Client Server

HTTPS

SOAP Request

SOAP Response

HTTPS





Figure 2: SOAP communication

Interoperability is the most important benefit of Web Services. Web Services are

virtually platform-independent due to the use of standards-based communications

methods. Member States will be able to use them from the software systems they

are already using for transboundary waste movement processes or directly, for

example through a common portal hosted at the Commission’s level.

Usability allows the business logic of many different systems to be exposed over

the Web. Instead of re-inventing the wheel, service clients’ implementation only

includes additional application-specific business logic on the client-side. This allows

for developing services and Member States´ client-side code using the desired

programming languages and tools.

Reusability of Web Services provides a close to zero-coding deployment. This

makes easy to re-use components and to deploy legacy code as a Web Service.

Deployability - Web Services are deployed over standard internet technologies and

use proven community standards. For example, underlying security (such as SSL) is

already built-in. Since remote system authentication will be required, the channel

should be encrypted using 2-way SSL, i.e. using client and server certificates.

Securing the communication using 2-way SSL will ensure the identities between the client

and the server. In 2-way SSL authentication, the SSL client application verifies the identity of

the SSL server application and then the SSL server application verifies the identity of the

SSL-client application. The involved certificates for this purpose could be issued by a

Commission Certification Authority.

However, digital signatures of the SOAP payload are highly recommended to also ensure

integrity; meaning that data cannot be modified in an unauthorized or undetected manner

and non-repudiation. This implies that one party of a transaction cannot deny having

received a transaction nor can the other party deny having sent a transaction.

Therefore the SOAP XML messages exchanged will have the structure depicted below.





Figure 3: SOAP envelope

The API Functional Requirements described in the following sections cover the

requirements that will be exposed on the system. These will be consumed by both external

systems and by the foreseen common portal hosted at the Commission level. Web Service

methods, defined on the WSDL file, will implement these requirements by acting as the

interface between requestors and the system back office which manages transboundary

waste movement processes.

SOAP fault message

If an error occurs during processing (e.g. a Member State sending an invalid request to the

API) the response will be a SOAP fault element in the body of the message returned to the

client/sender. For instance, the SOAP v1.1 fault mechanism returns specific information

about the error, including:

faultcode: text code used to indicate a class of errors.

faultstring: text message explaining the error.

faultactor: text string indicating what caused the fault.

detail: element used to carry application-specific error messages. The detail element

can contain child elements called detail entries.

SOAP Envelope

SOAP Header

WS Security Header

Digital Signature

SOAP Body

Body Message





2.3 Security Considerations

This security analysis is based on the hybrid system described in the

'3a_ArchitectureOverview_EDI_for_WSR.pdf'2 document, Appendix 2: Hybrid Architecture

Illustrative Scenario.

2.3.1 System security

Three main fundamental pillars are defined regarding the system security:

Communication channel protection 2.3.1.1

Every communication in the system for exchanging messages must guarantee that:

Every party is able to verify the identity of other parties.

Messages cannot be intercepted to be read/modified by third parties not involved

in the system.

Being a SaaS solution based on Web Services, all the information traffic will be transmitted

through the HTTP protocol. To secure the communication channel, ABAROA proposes the

use of 2-way SSL. This approach will secure communications and will establish a trust

scheme to ensure that received messages are authentic and that remote national systems

are authenticated. 2-way SSL, i.e. using server and client digital certificates, prevents

malicious parties intercepting and replaying messages, whereas the use of server and client

certificates allows both communicating systems to securely establish the identity of each

other. This means that by using HTTP over SSL, both the communication channel and the

information transmitted will be encrypted. Moreover, the limited number of channels makes

use of 2-way SSL realistic and simplifies certificate management.

This solution requires client certificates and server certificates in order to allow both

participants to authenticate each each other.

2 http://ec.europa.eu/environment/waste/shipments/pdf/3a_ArchitectureOverview_EDI_for_WSR.pdf

http://ec.europa.eu/environment/waste/shipments/pdf/3a_ArchitectureOverview_EDI_for_WSR.pdf





This type of protection is required between:

The Member States national systems and the Central Application.

The Shared Application and the Central Application.

Digital signature 2.3.1.2

The defined EDI must comply with Directive 1999/93/EC on electronic authentication or at

least provide the same level of security set out in the Directive. There were several studies

carried out regarding the use of digital signatures in the scope of waste shipments at the

European Union level, as shown below:

Study #1: Digital applications and movement tracking forms according to EC-

legislation 1013/20063

Each system participant should provide a secure digital signature that also assures the

identity of the involved parties:

A public key

A private key

A digital certificate issued by a third party

A public key, as its name suggests, is known by everyone. It is used to encrypt and decrypt

messages.

The private key must only be known by its owner and it is also used to encrypt and decrypt

messages.

A message encrypted by a private key can only be decrypted using the associated

public key.

A message encrypted by a public key can only be decrypted using the associated

private key.

3 http://www.oecd-ilibrary.org/environment/digital-applications-and-movement-tracking-forms-according-to-eg-

legislation-1013-2006_tn2010-560

http://www.oecd-ilibrary.org/environment/digital-applications-and-movement-tracking-forms-according-to-eg-legislation-1013-2006_tn2010-560

http://www.oecd-ilibrary.org/environment/digital-applications-and-movement-tracking-forms-according-to-eg-legislation-1013-2006_tn2010-560





This study discards the use of digital signatures due to the high number of participants

involved and the need of an agreement when acquiring and maintaining digital certificates.

Moreover, the study considers that interchanged documents should be accessible during

the whole process and that using signatures will ensure that the documents will be

encrypted and only readable by the recipient.

Study #2: Description of the EUDIN messaging system interface for the exchange of

transboundary movements of waste4

In this platform, digital signatures as a security measure were also dismissed for the

following reasons: lack of a common European Union scheme regarding legal recognition

of digital signatures; non-mature handling of e-ID schemes for transboundary purposes and

significant administrative costs.

Study #3: Feasibility Study for the establishment of an Electronic Data Interchange for

Waste Shipments5

The advantages of digital signatures for message exchanges are: authentication, non-

repudiation and integrity.

The holder of the certificate used to generate the signature is an important element to

consider. The guarantees that you have can only originate from the system itself. They

cannot be extended to the actual user who performed the original action.

The preference is for personal digital signatures which can be used for authentication and

non-repudiation mechanisms.

As EUDIN suggests, the handling of e-ID schemes for transboundary purposes is not

mature enough to be relied upon and some Member States lack of such a scheme to begin

with. The proposal in this case would be for a Commission Certification Authority to issue

certificates specifically for this purpose.

The use of personal digital certificates will be a problem for those Member States with

existing waste movement software solutions, as it would imply using two applications in

4http://www5.umweltbundesamt.at/dataharmonisation/dl/TMW_MessagingSystemInterface_v0.11_Description_Rev01.pd

f

5 http://ec.europa.eu/environment/waste/shipments/pdf/4a_Annex%202_Review_of_IT_systems_EDI_for_WSR.pdf

http://www5.umweltbundesamt.at/dataharmonisation/dl/TMW_MessagingSystemInterface_v0.11_Description_Rev01.pdf

http://www5.umweltbundesamt.at/dataharmonisation/dl/TMW_MessagingSystemInterface_v0.11_Description_Rev01.pdf

http://ec.europa.eu/environment/waste/shipments/pdf/4a_Annex%202_Review_of_IT_systems_EDI_for_WSR.pdf





parallel, or the existing systems would need adaptation to use the appropriate certificates

and the common message format. This message reformating before routing to the central

EU node would change the message contents and invalidate any signature.

The study suggests not considering using compulsory digital signatures for authentication

and non-repudiation. The architecture of the proposed hybrid system requires that

messages are always routed through national CA nodes, meaning that every

communication passes through multiple verification steps at trusted nodes. On the other

hand, message integrity is provided by securing and encrypting the communication channel

between the national and central nodes.

The study does, however contemplate the phased adoption of national e-ID schemes as

they are implemented and as their transboundary handling matures.

------------------------------

The conclusion of the studies described above is that the key issues related to digital

signatures are the legal validation and verification of certificates among the EU Member

States. Both eIDAS6 regulation and STORK

7 (Secure idenTity acrOss boRders linked) project

aim to solve these problems by offering a predictable legal framework to enable secure and

seamless electronic interactions between businesses, citizens and public authorities.

The current project also dismisses compulsory digital signatures, even though they are

recommended (e.g for non-repudiation purposes). The proposed architecture along with 2-

way SSL communication establishes a trust scheme to ensure message integrity and parties’

authentication.

Nevertheless, the certificate maintenance derived from 2-way SSL, as in digital signatures,

includes:

Creating certificates. Server certificate and client certificates need to be created;

Delivering certificates. Created client certificates need to be securely delivered to

the server to ensure who the receiver is;

6 https://ec.europa.eu/digital-single-market/trust-services-and-eid

7 https://www.eid-stork.eu/

https://ec.europa.eu/digital-single-market/trust-services-and-eid

https://www.eid-stork.eu/





Verifying certificates. Client certificates need to be verified by the server taking into

account revocation lists and expiration dates;

Managing the certificates’ lifecycle. This involves revoking certificates that can no

longer be trusted (e.g the certificate key has been compromised) and issuing new

certificates when they expire.

Shared application - Authentication 2.3.1.3

ABAROA recommends using EU Login along with an additional 2nd

authentication factor

due to the communication channel encryption not guarantying user identity and the

drawbacks of digital signatures detailed above. EU Login is the European Commission

Authentication Service which allows users to access a wide range of Commission

information systems, using a single username and password (SSO).

EU Login addresses issues such as appropriate password strength, account blocking,

password history and offers related services such as password regeneration.

EU Login supports a 2nd

factor authentication using SMS challenges. A 2nd

factor is

considered mandatory for a system in which establishing user identity is critical for

its overall trust. An SMS challenge offers the simplest approach to avoid the need

for measures like sending secure token generators to end-users.

A study of EU Login capabilities reveals that there is already an EU Login-STORK8

9

integration including an EU Login module to authenticate users using e-IDs. The aim of the

project is to establish a European e-ID Interoperability Platform that will allow citizens to

establish new e-relations across borders, just by presenting their national e-ID. STORK may

solve the digital signature issues at European level.

8 https://www.eid-stork2.eu/images/stories/documents/stork%202.0_pressrelease_final2.pdf

9 https://www.eid-stork.eu/index.php?option=com_content&task=view&id=255&Itemid=69

https://www.eid-stork2.eu/images/stories/documents/stork%202.0_pressrelease_final2.pdf

https://www.eid-stork.eu/index.php?option=com_content&task=view&id=255&Itemid=69





Proposed architecture – Authentication/Authorisation

Shared Application(Website)

Central Application(API)

ECAS

HT

TPS

Re

qu

est

(S

OA

P/R

est

)STORK

Web Services

MS Waste Shipment System

Adapter

Ce

rt. A

uth

. R

EQ

HTTPS Response (SOAP/Rest)

HTTPS Request (SOAP/Rest)

Figure 4: Proposed Architecture – Authentication

ABAROA proposes architecture-based on a hybrid model using STORK to validate

certificates from the Central Application and EU Login as the authentication system for

users willing to connect to the Shared Application. A further analysis will be required

regarding:

STORK: verifying it is a fully functional system. There are already some pilot projects

in the public health and banking sectors.

EU Login integration with the Shared Application.

EU Login-STORK integration is currently a feasible secure solution to allow users to access

the system using their national authentication IDs (e-ID).

STORK could be dismissed if there is no need to support e-IDs. In this case, digital

signatures will be performed using servers’ own certificates. The main aspects of the

proposed system are explained in the sections below.





2.3.2 Digital Signatures and SSL Certificates

Digital signatures and SSL certificates are two of the main system security points already

described. Both use digital certificates even though they operate in different application

functionality levels. However, the same certificate could be used for the following, due to

the information gathered about the system requirements:

Identity authentication

Digitally signing to ensure data integrity and origin

Encrypting the data exchanged so only the recipient can read the content.

There are three XML signature types according to its placement:

An XML signature used to sign a resource outside its containing XML document is

called a detached/external signature;

it is called an enveloped signature if it is used to sign some part of its containing

document (shown in the diagram below).

it is called an enveloping signature if it contains the signed data within itself.

Figure 5: SOAP digital signatures

To be able to digitally sign a SOAP message ABAROA recommends relying on libraries

which provide an XML security standard implementation supporting XML-Signature Syntax





and XML Encryption Syntax. An example of this is Apache Santuario10

; an open source

library providing implementation of the primary security standards for XML.

2.3.3 Timestamps

ABAROA proposes a timestamp mechanism in order to guarantee that certain data existed

at a particular point-in-time without the possibility of the owner to backdate the

timestamps. The reason for this is the messages/documents used in the system may include

legal constraints regarding waste shipments.

Time Stamping Authority (TSA)

A Time Stamping Authority is a trusted third party that issues timestamps which are used to

prove the existence of certain data before a certain point. The trust relationship with TSAs is

similar as with Certificate Authorities (CAs). The timestamping technique is based on digital

signatures and hash functions.

First, a hash is calculated from the data and sent to the TSA. The TSA concatenates a

timestamp to the hash and calculates the hash of this concatenation. This hash is in turn

digitally signed with the private key of the TSA. This signed hash + the timestamp are sent

back to the requester of the timestamp which stores these values with the original data.

Secure timestamp with no TSA

Specific algorithms such as Bitcoin ‘blockchain’ can be used as an alternative to generate

secure timestamps without a TSA. For example, BTProof uses this kind of approach for

timestamps.

10 http://santuario.apache.org/

http://santuario.apache.org/





Figure 6: Trusted timestamping

2.3.4 Monitoring / Logging

Application logging should always be included for security events. Application logs are

invaluable data for: identifying security incidents; monitoring policy violations; helping to

defend against vulnerability identification and detecting attacks by providing information

about problems and unusual conditions, etc.

The application logs must record the ‘4 Ws’ (when, where, who, what) for each event:

When

o Log date and time

Where

o Application identifier

o Service

o Code location

Who

o Source address





o User identity

What

o Type of event

o Severity of event, log level (trace, debug, info, warning, error, fatal)

o Description

2.3.5 Message Inspection

Binary files including executables and document types that can contain malware can be

posted using a Web Service in several ways. These files can be sent as a parameter of a Web

Service method: they can be sent as an attachment using SOAP with Attachments or using

DIME (Direct Internet Message Encapsulation) and WS-Attachments.

An attacker can craft an XML document (SOAP message) to send to a Web Service that

contains malware as an attachment. Therefore, ABAROA recommends an ICAP-enabled

Antivirus scanner server in order to run preliminary checks of the SOAP requests before the

Waste Shipment Regulation business logic processing starts. ICAP is a lightweight HTTP-like

protocol generally used to implement virus scanning and content filters.

ICAP-enabled Antivirus scanner Server

Web Service Consumer

ICAP

Web Service Provider

HTTP HTTP

Figure 7: ICAP SOAP malware inspection





3 Links to annexes

Below is list of the annexes which make up the reporting package:

ANNEX 1: Domain Objects

ANNEX 2: Requirements Model

ANNEX 3: Service Definition

4 Links to accompanying documents

During the production of the current technical study several questions and feedback texts

were transmitted either by email or in the form of online surveys. This information was

taken into account, significantly shaping the project’s final outcome. A list of documents

accompanying this main document is shown below:

001_Questions and feedback.pdf: Input from the European Commission and

involved stakeholders

002_Waste Shipment Regulation Survey.pdf: Survey Waste Shipment

003_Waste Shipment Regulation Survey Part 2.pdf: Survey Waste Shipment part 2

Find also below the additional resources automatically generated from Enterprise Architect:

004_Domain Objects types.xsd: Domain objects schema definition

005_Service Definition_WSDL.wsdl: Web service definition

5 Conclusion

Based on the specifications, the goal of this project consisted of a reporting package

defining the technical and organisational requirements of an Electronic Data Interchange

for the submission of documents and information of waste shipments.





This scope has included all activities covering the technical and organisational

requirements:

Alignment with the newly amended Article 26(4) or Regulation (EC) No 1013/2006.

Coverage of all the technical elements addressed in ANNEX 1 and ANNEX 2 (data

definition and structure, business rules, list of messages, formats and exchange

methods).

Involvement of stakeholders in defining the protocol

Consideration of international standards

Consideration of electronic authentication methods, in accordance with Directive

1999/93/EC.

With regard to advantages or disadvantages, this proposal aims to solve the problems

occurring due to the diversity of tools used in various countries by offering a common

system for managing the whole waste shipment workflow.

The following are the most significant aspects of the designed solution:

The single format proposed for all countries covers the whole waste shipment

workflow (the current ones do not cover all steps).

The protocol designed focuses in the newly amended Article 26(4) of

Regulation (EC) No 1013/ 2006 and takes into consideration the application of all

provisions of the Regulation in the Member States. In contrast to this, the existing

national tools do not cover all Regulation provisions and they are tailor-made to

suit the requirements of specific stakeholders.

This proposal offers a generic solution to those who do not have any tool

implemented. In this way, they do not have to choose between existing national

tools or even proprietary software from other countries.

Minimum implementation effort required for those who use their own tools. The

selected protocols and formats offer a good convertibility between other

standards such as UN/CEFACT (see the example in section 2.1.1).

The idea of a single solution for all waste shipment-related processes simplifies the

development of software and allows it to evolve together with its protocol in a

stepwise manner that facilitates any future preventive and corrective

maintenance.





Regarding requirements involved in this solution, the following section summarises the

main findings of this study, classified according to their nature (technical, organisational,

standards and security).

Technical specifications

Technical design is a one of the fundamental parts of this study. The EDI proposal considers

the whole waste shipment workflow with all the restrictions and limitations. This is reflected

in the data model, the business rules/requirements and messages/services definition

annexes:




The study comprises the current document (Portable Document Format, .PDF) and a

technical section implemented with Enterprise Architect application in form of an .EAP file

(Enterprise Architect Project). This type of software offers users functionalities for designing

and formulating custom software systems. In this way, this file includes a source code and

developers’ comments, facilitating the possible development of the designed solution.

In terms of technical requirements, all EU Member States should ensure that the designed

model and business rules cover all provisions of Regulation (EC) No 1013/2006 and that

they all comply with the designed solution. Countries choosing to use an existing national

tool must ensure compatibility with the proposed protocol by building an adapter.

Organisational requirements

ABAROA has considered the following organisational requirements for the study, in

addition to the identified technical requirements:

A common understanding of the Regulation and compliance with it.

Agreement with the entire content of the proposal is a fundamental premise of all

EU Member States and stakeholders involved.

Effort from all parties involved to build individual or group adapters. For example, a

group adapter could be developed by those countries whose tools use the

UN/CEFACT standard.





All EU Member States must approve a detailed development plan and make a

commitment to work together to integrate all waste shipment regulation

requirements.

The development plan will cover the technical specifications of the existing study

and will be implemented in a step by step manner taking into account the need for

collaboration with all relevant stakeholders, including IT experts, Member State

representatives, the European Commission, etc.

International standards

ABAROA sees the need for a unified treatment and management of data in a single format

in view of the current situation which is characterized by a wide variety of tools and

standards such as UN/CEFACT (Adapter Example). For this reason, it is proposed not to use

a specific standard used by any existing tool. Instead, the solution should be based on a

new protocol which is more in line with the Regulation itself and which goes hand in hand

with the analysed and designed data model and business rules.

Regarding development, this is the most effective choice for all countries, since it offers

suitable software for all stakeholders, without favouring one side or another. All countries

without tools should implement the whole solution and those who have their own tools

should build adapters.

Other considerations

The current study dismisses compulsory digital signatures, even though they are

recommended (e.g. for non-repudiation purposes). Nevertheless, the defined protocol can

support digital signatures. Digital signature support could be built as an additional layer

since they are not tied to the proposed system.

Several proposals have been included throughout the study such as the use of a hybrid

topology architecture consisting of a Central Application and a Shared Application for

Member States having no solution of their own. Other main study proposals include 2-way

SSL to ensure the identities between the involved parties and EU Login as the

authentication service for the system. EU Login allows users to access a wide range of

Commission information systems and also already provides sensitive security-wise

implementations such as password strength validation, account blocking and password

regeneration.






1 Introduction

This annex provides details about Regulation (EC) No 1013/2006 of the European

Parliament and of the Council of 14 June 2006 on shipments of waste. In particular, this

annex defines the domain model of the proposed solution; representing the meaningful

real-world concepts pertinent to the Waste Shipment Regulation that need to be modeled

in software.

2 Domain Objects

Domain models are generally implemented as an object model within a layer that uses a

lower-level layer for persistence and provides an API to a higher-level layer to gain access

to the data and behaviour of the model.

Find below the Unified Modelling Language (UML) class diagram that represents Waste

Shipment Regulation domain model. These UML diagrams were implemented with

Enterprise Architect and can be found in the .EAP (Enterprise Architect Project) file included

in the solution package.





Domain Objects diagram

Figure 8: Domain Objects

Code Lists

«enumeration»

IllegalityResponsibleType

Notifier

Consignee

Other

Notification

+ notificationID: int

+ serialNumber: string

+ exporter: Notifier

+ exporterSignedAt: date

+ importer: Agent

+ producerSignedAt: date

+ notificationType: OperationType

+ preconsentedRecoveryFacility: boolean

+ liabil ityInsuranceEvidence: boolean

+ contractEvidence: boolean

+ notificationStatus: NotificationStatus

Agent

+ agentID: int

+ name: string

+ contactPerson: string

+ telephone: int

+ fax: int

+ email: string

+ certificate: base64Binary

Address

+ street: string

+ zipcode: string

+ city: string

+ state: string

+ country: Country

Country

+ code: string

+ name: string

+ isMemberState: boolean

+ isEFTAMember: boolean

+ isBaselParty: boolean

+ isOECD: boolean

+ isInConflict: boolean

WasteProducer

+ site: string

+ generationProcess: string

«enumeration»

OperationType

Disposal

Recovery

«enumeration»

ShipmentType

Individual

Multiple

«enumeration»

PackagingType

Drum

Wooden barrel

Jerrican

Box

Bag

Composite packaging

Pressure receptacle

Bulk

Other

Operation

+ operationID: int

+ operationCode: OperationCode

+ operationStage: OperationStage

+ facil ity: Facility

+ facil ityInformation: int

+ facil ityType: OperationType

+ actualSite: string

+ technologyEmployed: string

+ reasonOfExport: string

+ parentOperation: int

+ methodOfDisposal: string

+ recoveredMaterialAmount: double

+ estimatedValue: double

+ costOfRecovery: double

+ costOfDisposal: double

WasteIdentification

+ designationAndComposition: string

+ physicalCharacteristics: PhysicalCharacteristic

+ baselAnnexVIIIorIX: int

+ codeOECD: int

+ ecList: int

+ exportCountryCode: string

+ importCountryCode: string

+ other: string

+ codeY: int

+ codeH: UNClass

+ unClass: UNClass

+ unNumber: int

+ unShippingName: int

+ customsCode: int ConcernedCountry

+ country: Country

+ competentAuthority: CompetentAuthority

+ specificPoint: string

+ countryType: ConcernedCountryType

+ pointType: RoutePointType

RouteCustomsOffice

+ routeCustomsOfficeID: int

+ entry: string

+ exit: string

+ export: string

Acknowledgement

+ acknowledgementID: int

+ receivedOn: date

+ sentOn: date


WrittenConsent

+ consentID: int

+ givenOn: date

+ withdrawnOn: date

+ validFrom: date

+ validUntil: date


+ hasSpecificConditions: boolean

+ specificConditions: string

+ tacit: boolean

Quantity

+ quantity: double

+ unit: QuantityUnit

+ estimatedQuantityMin: double

+ estimatedQuantityMax: double

«enumeration»

QuantityUnit

Tonnes (Mg)

Kg

m3

Litres

«enumeration»

ConcernedCountryType

Export/Dispatch

Transit

Import/Destination

NotificationShipment

+ shipmentType: ShipmentType

+ numberOfShipments: int

+ firstDeparture: date

+ lastDeparture: date

+ packagingType: PackagingType

+ specialHandlingRequired: boolean

Mov ementDocument

+ movementDocumentID: int

+ notificationIdentifier: string

+ shipmentSerial: int

+ shipmentTotalNumber: int



+ importer: Agent

+ importerSignedAt: date

+ actualWasteQuantity: double

+ actualWasteUnit: QuantityUnit

+ withdrawndAt: date

+ additionalInformation: string

+ shipmentStatus: ShipmentStatus

AgentAuthorisations

+ agentAuthorisationID: int

+ registrationNumber: string

+ role: RoleType

«enumeration»

RoleType

Producer

Licensed producer

Collector

Dealer

Broker

Disposal facil ity

Recovery facil ity

Laboratory

Carrier

Customs office

«enumeration»

MeansOfTransport

Road

Trail/Rail

Sea

Air

Inland waterways

«enumeration»

PhysicalCharacteristic

Powdery/powder

Solid

Viscous/Paste

Sludgy

Liquid

Gaseous

Other

«enumeration»

OperationCode

D1

D2

D3

D4

D5

D6

D7

D8

D9

D10

D11

D12

D13

D14

D15

R1

R2

R3

R4

R5

R6

R7

R8

R9

R10

R11

R12

R13

UNClass

+ unClass: string

+ hCode: string

+ characteristics: string

Mov ementShipment

+ shipmentDate: date


+ numberOfPackages: int


Waste

+ wasteCode: string

+ wasteType: string

+ description: string

CompetentAuthority

+ name: string

+ deparment: string

+ country: Country

Facility

FacilityPreconsent

+ facil ityPreconsentID: int

+ preconsentedAt: date

+ wasteCode: Waste

+ validFrom: date

+ validUntil: date

+ informationRequestsUntil: date

+ preconsentedQuantity: double

+ quantityUnit: QuantityUnit

+ recoveryOperation: OperationCode

+ employedTechnology: string

+ revokedAt: date

Carrier

Routing

+ exportCountry: Country

+ exportCompetentAuthority: CompetentAuthority

+ exportSpecificPoint: string

+ importCountry: Country

+ importCompetentAuthority: CompetentAuthority

+ importSpecificPoint: string

+ alternativeRoute: Routing [0..*]

RouteSection

+ distance: long

Objection

+ objectionID: int


+ objection: ObjectionType

+ waste: Waste

+ quantity: double




+ objectionDate: date

+ objectionStatus: StatusType

+ comments: string

«enumeration»

RoutePointType

Entry

Exit

Contract

+ contract: base64Binary

+ exporterAccepted: boolean

+ exporterAcceptedAt: date

+ importerAccepted: boolean

+ importerAcceptedAt: date

FinancialGuarantee

+ financialGuarantee: base64Binary

+ transportCosts: double

+ operationCosts: double

+ storageCosts: double

+ dispatchCAAcceptance: boolean

+ destinationCAAcceptance: boolean

+ additionalFinancialGuarantee: double

Notifier

«enumeration»

OperationStage

Interim operation

Non interim operation

«enumeration»

RequestType

Notification

Movement

Additional

NotificationAttachment

+ notificationAttachmentID: int

+ name: string

+ attachment: base64Binary

InformationRequest

+ informationRequestID: int


+ request: Request

+ requestDate: date

+ requestStatus: StatusType

+ comments: string

ObjectionType

+ objectionType: OperationType

+ objectionCode: string

Request

+ requestType: RequestType

+ requestCode: string

«enumeration»

NotificationStatus

Draft

Submitted

Approved

Acknowledged

Completed

Rejected

Expired

«enumeration»

StatusType

Open

Solved

Closed

IntendedCarrier

+ carrier: Carrier

+ meansOfTransport: MeansOfTransport

FinalCarrier

+ custodyTransferID: int

+ carrier: Carrier


+ dateOfTransfer: dateReceipt

+ receiptID: int

+ receivedOn: date

+ rejected: boolean

+ rejectionReason: string



+ receivedWasteQuantity: double

+ receivedWasteUnit: QuantityUnit

+ approximateDate: date


+ sentOn: date

Recov eryDisposal

+ completedOn: date

+ sentOn: date

«enumeration»

ShipmentStatus

Shipped

Received

Received - Interim

Recovered / Disposed

Recovered / Disposed - Interim

Passage

+ passageID: int

+ customsOffice: CustomsOffice

+ passageType: ConcernedCountryType

+ passageDate: date

+ country: Country

+ entry: string

+ exit: string

CustomsOffice

«enumeration»

IllegalShipmentType

A

B

C

D

E

F

G1

G2

G3

Other

Illegality

+ il legalityID: int

+ il legalityType: Il legalShipmentType

+ il legalityTypeOther: string

+ detectedBy: Agent

+ detectedOn: date

+ responsible: Il legalityResponsibleType

+ measures: string

Comment

+ commentID: int

+ commentType: CommentType

+ commentCreationDate: date

+ commentUpdateDate: date


+ comment: string

+ deleted: boolean

«enumeration»

CommentType

G

NNT

NNA

inherits

inherits

delivers notification to

authorizes

inherits

0..*1

1

has many0..*

0..*

has many

1

1

has many0..*

1..*has many

1

inherits

realized by

0..*

1

1

has

2

1

contains

1

1..*contains

1

0..*

1

1

1

reviewed by

1contains

1

generates

1

contains

1

1contains

1

inherits

given by

0..*

1

1..*has many

1

0..*

has many

1

1has many

1..*

1

has one or many

1..*

1

contains

11

has1

concerns to

0..1

1

granted by

1

contains1

1

1

1

contains1

1

1..*

0..*

1

belongs to





2.1 Acknowledgement

Competent authority notification acknowledgement.

Figure 9: Acknowledgement

OUTGOING STRUCTURAL RELATIONSHIPS

Realization from Acknowledgement to CompetentAuthority

Aggregation from Acknowledgement to Notification

ATTRIBUTES

acknowledgementID : int Public

Description:

Acknowledgement ID

receivedOn : date Public

Description:

The date the notification was received

sentOn : date Public

Description:

The date the acknowledge was sent

Acknowledgement

+ acknowledgementID: int

+ receivedOn: date

+ sentOn: date






competentAuthority : CompetentAuthority Public

Description:

Competent Authority issuing the acknowledge

2.2 Address

Agent address information.

Figure 10: Address


Aggregation from Address to Agent

ATTRIBUTES

street : string Public

Description:

Street

zipcode : string Public

Description:

ZIP code / postcode

Address

+ street: string

+ zipcode: string

+ city: string

+ state: string

+ country: Country





city : string Public

Description:

City

state : string Public

Description:

State

country : Country Public

Description:

Country

2.3 Agent

Agent details. Encompassing any party involved in the system such as facilities, notifiers and

carriers.

Figure 11: Agent

Agent

+ agentID: int

+ name: string

+ contactPerson: string

+ telephone: int

+ fax: int

+ email: string

+ certificate: base64Binary





INCOMING STRUCTURAL RELATIONSHIPS

Realization from CompetentAuthority to Agent

Generalization from Facility to Agent

Generalization from Carrier to Agent

Generalization from Notifier to Agent

Generalization from CustomsOffice to Agent

Generalization from WasteProducer to Agent

Aggregation from Address to Agent

ATTRIBUTES

agentID : int Public

Description:

Agent ID

name : string Public

Description:

Agent name

contactPerson : string Public

Description:

Agent contact person





telephone : int Public

Description:

Agent telephone

fax : int Public

Description:

Agent fax

email : string Public

Description:

Agent email address

certificate : base64Binary Public

Description:

Agent X.509 Public Key Certificate

ASSOCIATIONS

Association (direction: Unspecified)

Source: Public (Class) Agent

Cardinality: [1]

Target: Public (Class) AgentAuthorisations

Cardinality: [1..*]





2.4 AgentAuthorisations

Agent authorisations/roles details. An agent may have multiple authorisations, each linked

with a unique registration number. For example, a facility that can act both as a disposal or

a recovery facility will have two different registration numbers.

Figure 12: AgentAuthorisations

ATTRIBUTES

agentAuthorisationID : int Public

Description:

Agent Authorisation ID

registrationNumber : string Public

Description:

Agent registration number for each agent role

role : RoleType Public

Description:

Agent role:

Producer

Licensed producer

Collector

Dealer

Broker

Disposal facility

AgentAuthorisations

+ agentAuthorisationID: int

+ registrationNumber: string

+ role: RoleType





Recovery facility

Laboratory

Carrier

Custom office

ASSOCIATIONS


Source: Public (Class) Agent

Cardinality: [1]

Target: Public (Class) AgentAuthorisations

Cardinality: [1..*]

2.5 Carrier

Carrier (agent) dealing in waste transport.

Figure 13: Carrier


Generalization from Carrier to Agent

2.6 Comment

Comments added to a notification. They could be general comments or structured

comments accommodating the reasoning behind a notification not being transmitted or a

notification not being acknowledged.

Agent

Carrier





Figure 14: Comment


Aggregation from Comment to Notification

ATTRIBUTES

commentID : int Public

Description:

Comment ID

commentType : CommentType Public

Description:

Comment type:

G - General

NNT - Notification not transmitted

NNA - Notification not acknowledged

commentCreationDate : date Public

Description:

Comment creation date

Comment

+ commentID: int

+ commentType: CommentType

+ commentCreationDate: date

+ commentUpdateDate: date


+ comment: string

+ deleted: boolean





commentUpdateDate : date Public

Description:

Comment last update date


Description:

Competent authority who created the comment

comment : string Public

Description:

Comment description / content

deleted : boolean Public

Description:

Whether the comment is deleted

2.7 CompetentAuthority

Body designated by a concerned country as the competent authority or authorities

responsible for implementing waste shipment regulation.

Figure 15: CompetentAuthority


CompetentAuthority

+ name: string

+ department: string

+ country: Country

delivers notification to





Realization from CompetentAuthority to Agent

Realization from CompetentAuthority to CompetentAuthority


Realization from Notification to CompetentAuthority

Realization from RouteSection to CompetentAuthority

Realization from CompetentAuthority to CompetentAuthority

Realization from Acknowledgement to CompetentAuthority

Realization from FacilityPreconsent to CompetentAuthority

ATTRIBUTES


Description:

Competent authority name

department : string Public

Description:

Competent authority department






Description:

Competent authority country

2.8 ConcernedCountry

Concerned country details related to a route section.

Figure 16: ConcernedCountry

ATTRIBUTES


Description:

Route section country


Description:

Route section competent authority

specificPoint : string Public

Description:

Route section specific point

ConcernedCountry

+ country: Country


+ specificPoint: string

+ countryType: ConcernedCountryType

+ pointType: RoutePointType





countryType : ConcernedCountryType Public

Description:

Route section country type:

Export/Dispatch

Transit

Import/Destination

pointType : RoutePointType Public

Description:

Route section point type:

Export/Dispatch

Transit

Import/Destination

ASSOCIATIONS

Association (direction: Unspecified) has

Source: Public (Class) RouteSection

Cardinality: [1]

Target: Public (Class) ConcernedCountry

Cardinality: [2]

2.9 Contract

Details of the contract between the Notifier and the consignee for the recovery or disposal

of the notified waste.





Figure 17: Contract

ATTRIBUTES

contract : base64Binary Public

Description:

Contract document (binary)

exporterAccepted : boolean Public

Description:

Contract accepted by the Exporter

exporterAcceptedAt : date Public

Description:

Contract accepted by the Exporter date

importerAccepted : boolean Public

Description:

Contract accepted by the Importer

importerAcceptedAt : date Public

Description:

Contract accepted by the Importer date

Contract

+ contract: base64Binary

+ exporterAccepted: boolean

+ exporterAcceptedAt: date

+ importerAccepted: boolean

+ importerAcceptedAt: date





ASSOCIATIONS

Association (direction: Unspecified) contains

Source: Public (Class) Notification

Cardinality: [1]

Target: Public (Class) Contract

Cardinality: [1]

2.10 Country

Country details.

Figure 18: Country

ATTRIBUTES

code : string Public

Description:

Country code (ISO 3166-1)


Description:

Country name (ISO 3166-1)

Country

+ code: string

+ name: string

+ isMemberState: boolean

+ isEFTAMember: boolean

+ isBaselParty: boolean

+ isOECD: boolean

+ isInConflict: boolean





isMemberState : boolean Public

Description:

Whether the country is a member state

isEFTAMember : boolean Public

Description:

Whether the country is an EFTA member

isBaselParty : boolean Public

Description:

Whether the country is party to the Basel Convention

isOECD : boolean Public

Description:

Whether the OECD Decision applies to the country

isInConflict : boolean Public

Description:

Whether the country is in a situation of crisis, peacemaking, peacekeeping or war

2.11 CustomsOffice

Customs office (agent) carrying out controls on waste shipments.





Figure 19: CustomsOffice


Generalization from CustomsOffice to Agent

2.12 Facility

Details of the recovery or disposal facility (agent) receiving the waste.

Figure 20: Facility


Generalization from Facility to Agent


Realization from Receipt to Facility

Realization from Operation to Facility

ASSOCIATIONS

Agent

CustomsOffice

Agent

Facility





Association (direction: Unspecified) has many

Source: Public (Class) Facility

Cardinality: [1]

Target: Public (Class) FacilityPreconsent

Cardinality: [0..*]

2.13 FacilityPreconsent

Details of pre-consents the competent authorities of destination having jurisdiction over

specific recovery facilities may decide to issue.

Figure 21: FacilityPreconsent


Realization from FacilityPreconsent to CompetentAuthority

ATTRIBUTES

facilityPreconsentID : int Public

Description:

Facility Pre-Consent ID

FacilityPreconsent

+ facil ityPreconsentID: int

+ preconsentedAt: date

+ wasteCode: Waste

+ validFrom: date

+ validUntil: date

+ informationRequestsUntil: date

+ preconsentedQuantity: double


+ recoveryOperation: OperationCode

+ employedTechnology: string

+ revokedAt: date





preconsentedAt : date Public

Description:

Pre-consent creation date

wasteCode : Waste Public

Description:

Pre-consented waste

validFrom : date Public

Description:

Pre-consent valid from (date)

validUntil : date Public

Description:

Pre-consent valid until (date)

informationRequestsUntil : date Public

Description:

The time allowed to receive further information or documentation from the Notifier.

preconsentedQuantity : double Public

Description:

Pre-consent waste quantity

quantityUnit : QuantityUnit Public





Description:

Pre-consented waste quantity unit

recoveryOperation : OperationCode Public

Description:

Pre-consented recovery operation:

D1

D2

D3

D4

D5

D6

D7

D8

D9

D10

D11

D12

D13

D14

D15

R1

R2

R3

R4

R5

R6

R7

R8

R9

R10

R11

R12

R13

employedTechnology : string Public





Description:

Pre-consented employed technology

revokedAt : date Public

Description:

Pre-consent revoked at (date)

ASSOCIATIONS


Source: Public (Class) Facility

Cardinality: [1]

Target: Public (Class) FacilityPreconsent

Cardinality: [0..*]

2.14 FinalCarrier

The actual/final carrier for a specific route section performing the custody transfer taking

possession of the consignment.

Figure 22: FinalCarrier

ATTRIBUTES

custodyTransferID : int Public

Description:

FinalCarrier

+ custodyTransferID: int

+ carrier: Carrier


+ dateOfTransfer: date





Custody Transfer ID

carrier : Carrier Public

Description:

Carrier

meansOfTransport : MeansOfTransport Public

Description:

Means of transport:

Road

Trail/Rail

Sea

Air

Inland waterways

dateOfTransfer : date Public

Description:

Custody transfer date

ASSOCIATIONS



Cardinality: [1]

Target: Public (Class) FinalCarrier

Cardinality: [1]





2.15 FinancialGuarantee

Details on financial guarantees or equivalent insurance for a notification for the intended

movements of waste.

Figure 23: FinancialGuarantee

ATTRIBUTES

financialGuarantee : base64Binary Public

Description:

Financial guarantee document (binary)

transportCosts : double Public

Description:

Costs of transport (Article 6.1.a)

operationCosts : double Public

Description:

Costs of recovery or disposal, including any necessary interim operation (Article 6.1.b)

storageCosts : double Public

Description:

Costs of storage for 90 days (Article 6.1.c)

FinancialGuarantee

+ financialGuarantee: base64Binary

+ transportCosts: double

+ operationCosts: double

+ storageCosts: double

+ dispatchCAAcceptance: boolean

+ destinationCAAcceptance: boolean

+ additionalFinancialGuarantee: double





dispatchCAAcceptance : boolean Public

Description:

Competent authority of Dispatch financial guarantee approval (Article 6.4)

destinationCAAcceptance : boolean Public

Description:

Competent authority of Destination financial guarantee approval (Article 6.4)

additionalFinancialGuarantee : double Public

Description:

Additional financial guarantee (Article 6.4)

ASSOCIATIONS



Cardinality: [1]

Target: Public (Class) FinancialGuarantee

Cardinality: [1]

2.16 Illegality

Details regarding an illegal shipment.





Figure 24: Illegality


Aggregation from Illegality to MovementDocument

ATTRIBUTES

illegalityID : int Public

Description:

Illegality ID

illegalityType : IllegalShipmentType Public

Description:

Illegality type:

A - Without notification to all competent authorities concerned pursuant to this Regulation

B - Without the consent of the competent authorities concerned pursuant to this Regulation

C - With consent obtained from the competent authorities concerned through falsification,

misrepresentation or fraud

D - In a way which is not specified materially in the notification or movement documents

E - In a way which results in recovery or disposal in contravention of Community or international

rules

F - Contrary to Articles 34, 36, 39, 40, 41 and 43

G1 - In relation to shipments of waste as referred to in Article 3(2) and (4), has resulted from: the

waste being discovered not to be listed in Annexes III, IIIA or IIIB

G2 - In relation to shipments of waste as referred to in Article 3(2) and (4), has resulted from: non-

compliance with Article 3(4)

G3 - In relation to shipments of waste as referred to in Article 3(2) and (4), has resulted from: the

Illegality

+ illegalityID: int

+ il legalityType: Il legalShipmentType

+ illegalityTypeOther: string

+ detectedBy: Agent

+ detectedOn: date

+ responsible: Il legalityResponsibleType

+ measures: string





shipment being effected in a way which is not specified materially in the document set out in Annex VII

Other

illegalityTypeOther : string Public

Description:

Illegality type 'Other' description

detectedBy : Agent Public

Description:

The Agent who detected the illegality

detectedOn : date Public

Description:

Illegality detected on (date)

responsible : IllegalityResponsibleType Public

Description:

Illegality responsible:

Notifier

Consignee

Other

measures : string Public

Description:

Measures taken including possible penalties





2.17 InformationRequest

Details of the information request issued by concerned competent authorities, considering

that additional information and documentation needs to be added to a notification.

Figure 25: InformationRequest


Aggregation from InformationRequest to Notification

ATTRIBUTES

informationRequestID : int Public

Description:

Information Request ID


Description:

Competent Authority issuing the request for information and documentation

request : Request Public

Description:

Request (request type + request code)

InformationRequest

+ informationRequestID: int


+ request: Request

+ requestDate: date

+ requestStatus: StatusType

+ comments: string





requestDate : date Public

Description:

Date of the request creation

requestStatus : StatusType Public

Description:

Request status:

Open

Solved

Closed

comments : string Public

Description:

Additional comments

2.18 IntendedCarrier

The intended carrier for a specific route section which is foreseen to perform the custody

transfer taking possession of the consignment.

Figure 26: IntentedCarrier

ATTRIBUTES

carrier : Carrier Public

IntendedCarrier

+ carrier: Carrier






Description:

Carrier

meansOfTransport : MeansOfTransport Public

Description:

Means of transport:

Road

Trail/Rail

Sea

Air

Inland waterways

ASSOCIATIONS



Cardinality: [1]

Target: Public (Class) IntendedCarrier

Cardinality: [1]

2.19 MovementDocument

Details of the movement document for transboundary movements/shipments of waste.





Figure 27: MovementDocument


Realization from MovementDocument to Notification


Aggregation from Illegality to MovementDocument

Aggregation from MovementShipment to MovementDocument

Aggregation from Passage to MovementDocument

Aggregation from Receipt to MovementDocument

ATTRIBUTES

movementDocumentID : int Public

Description:

Movement Document ID

Mov ementDocument


+ notificationIdentifier: string

+ shipmentSerial: int

+ shipmentTotalNumber: int



+ importer: Agent

+ importerSignedAt: date

+ actualWasteQuantity: double

+ actualWasteUnit: QuantityUnit

+ withdrawndAt: date

+ additionalInformation: string

+ shipmentStatus: ShipmentStatus





notificationIdentifier : string Public

Description:

Notification serial number to which the movement document is related

shipmentSerial : int Public

Description:

Serial number of the shipment

shipmentTotalNumber : int Public

Description:

Total intended number of shipments

exporter : Notifier Public

Description:

Exporter - Notifier

exporterSignedAt : date Public

Description:

Exporter - Notifier signature date

importer : Agent Public

Description:

Importer - Consignee





importerSignedAt : date Public

Description:

Importer - Consignee signature date

actualWasteQuantity : double Public

Description:

Actual waste quantity

actualWasteUnit : QuantityUnit Public

Description:

Actual waste quantity unit

withdrawndAt : date Public

Description:

Shipment withdrawn at (date)

additionalInformation : string Public

Description:

Additional information

shipmentStatus : ShipmentStatus Public

Description:

Shipment status:

Shipped

Received

Received - Interim

Recovered / Disposed





Recovered / Disposed - Interim

2.20 MovementShipment

Details of the shipment related to a movement document.

Figure 28: MovementShipment


Aggregation from MovementShipment to MovementDocument

ATTRIBUTES

shipmentDate : date Public

Description:

Actual date of shipment

packagingType : PackagingType Public

Description:

Packaging type:

Drum

Wooden barrel

Jerrican

Box

Bag

Mov ementShipment

+ shipmentDate: date


+ numberOfPackages: int






Composite packaging

Pressure receptacle

Bulk

Other

numberOfPackages : int Public

Description:

Number of packages

specialHandlingRequired : boolean Public

Description:

Special handling requirements required

2.21 Notification

Details of the notification for transboundary movements/shipments of waste.

Figure 29: Notification


Realization from Notification to CompetentAuthority

Notification


+ serialNumber: string



+ importer: Agent

+ producerSignedAt: date

+ notificationType: OperationType

+ preconsentedRecoveryFacility: boolean

+ liabilityInsuranceEvidence: boolean

+ contractEvidence: boolean

+ notificationStatus: NotificationStatus






Realization from MovementDocument to Notification

Aggregation from WrittenConsent to Notification

Aggregation from NotificationShipment to Notification

Aggregation from Comment to Notification

Aggregation from Acknowledgement to Notification

Aggregation from Objection to Notification

Realization from Notifier to Notification

Aggregation from Operation to Notification

Aggregation from NotificationAttachment to Notification

Aggregation from WasteIdentification to Notification

Aggregation from InformationRequest to Notification

ATTRIBUTES

notificationID : int Public

Description:

Notification ID





serialNumber : string Public

Description:

Notification serial number

exporter : Notifier Public

Description:

Exporter - Notifier

exporterSignedAt : date Public

Description:

Exporter's - Notifier's declaration date

importer : Agent Public

Description:

Importer - Consignee

producerSignedAt : date Public

Description:

Generator's - Producer's declaration date

notificationType : OperationType Public

Description:

Notification type:

Disposal





Recovery

preconsentedRecoveryFacility : boolean Public

Description:

Whether the recovery facility is pre-consented

liabilityInsuranceEvidence : boolean Public

Description:

The existence of insurance against liability for damage to third parties

contractEvidence : boolean Public

Description:

The evidence of the contract or a declaration certifying its existence in accordance

notificationStatus : NotificationStatus Public

Description:

Notification status:

Draft

Submitted

Approved

Acknowledged

Completed

Rejected

Expired





ASSOCIATIONS

Association (direction: Unspecified) has one or many


Cardinality: [1]

Target: Public (Class) WasteProducer

Cardinality: [1..*]



Cardinality: [1]

Target: Public (Class) FinancialGuarantee

Cardinality: [1]



Cardinality: [1]

Target: Public (Class) Routing

Cardinality: [1]



Cardinality: [1]

Target: Public (Class) Contract

Cardinality: [1]

2.22 NotificationAttachment

Documents attached to a notification.

Figure 30: NotificationAttachment


NotificationAttachment

+ notificationAttachmentID: int

+ name: string

+ attachment: base64Binary





Aggregation from NotificationAttachment to Notification

ATTRIBUTES

notificationAttachmentID : int Public

Description:

Notification Attachment ID


Description:

Attachment file name

attachment : base64Binary Public

Description:

Attachment document (binary)

2.23 NotificationShipment

Details of the shipment related to a notification document.

Figure 31: NotificationShipment

NotificationShipment

+ shipmentType: ShipmentType

+ numberOfShipments: int

+ firstDeparture: date

+ lastDeparture: date








Aggregation from NotificationShipment to Notification

ATTRIBUTES

shipmentType : ShipmentType Public

Description:

Shipment type:

Individual

Multiple

numberOfShipments : int Public

Description:

Total intended number of shipments

firstDeparture : date Public

Description:

Intended period of time for shipment(s) (first departure)

lastDeparture : date Public

Description:

Intended period of time for shipment(s) (last departure)

packagingType : PackagingType Public

Description:

Packaging type:





Drum

Wooden barrel

Jerrican

Box

Bag

Composite packaging

Pressure receptacle

Bulk

Other

specialHandlingRequired : boolean Public

Description:

Special handling requirements required

2.24 Notifier

Notifier (agent) details. Notifier identifies:

in the case of a shipment originating from a Member State, any natural or legal person

under the jurisdiction of that Member State who intends to carry out a shipment of

waste or intends to have a shipment of waste carried out and to whom the duty to

notify is assigned.

in the case of import into, or transit through the Community, of waste that does not

originate in a Member State, any of the following natural or legal persons under the

jurisdiction of the country of dispatch intending to carry out a shipment of waste or

intending to have, or who has already had, a shipment of waste carried out.

Figure 32: Notifier

Agent

Notifier






Generalization from Notifier to Agent

Realization from Notifier to Notification

2.25 Objection

Details of the objection raised by competent authorities concerned regarding a planned

shipment of waste destined for disposal (Art. 11) or a planned shipment of waste destined

for recovery (Art. 12).

Figure 33: Objection


Aggregation from Objection to Notification

ATTRIBUTES

objectionID : int Public

Description:

Objection ID

Objection

+ objectionID: int


+ objection: ObjectionType

+ waste: Waste

+ quantity: double


+ facil ity: Facil ity


+ objectionDate: date

+ objectionStatus: StatusType

+ comments: string






Description:

Competent Authority issuing the objection

objection : ObjectionType Public

Description:

objection (objectionType + objectionCode)

waste : Waste Public

Description:

Waste related with the objection

quantity : double Public

Description:

Waste quantity related with the objection

quantityUnit : QuantityUnit Public

Description:

Waste quantity unit related with the objection

facility : Facility Public

Description:

Facility (in the country of destination)

operationCode : OperationCode Public





Description:

Operation code:

D1

D2

D3

D4

D5

D6

D7

D8

D9

D10

D11

D12

D13

D14

D15

R1

R2

R3

R4

R5

R6

R7

R8

R9

R10

R11

R12

R13

objectionDate : date Public

Description:

Objection date





objectionStatus : StatusType Public

Description:

Objection status:

Open

Solved

Closed

comments : string Public

Description:

Reasons for objecting and additional comments

2.26 ObjectionType

Objection type (Objection) details.

Figure 34: ObjectionType

ATTRIBUTES

objectionType : OperationType Public

Description:

Objection type:

Disposal

Recovery

ObjectionType

+ objectionType: OperationType

+ objectionCode: string





objectionCode : string Public

Description:

Article 11.1, Article 12.1

2.27 Operation

Waste recovery/disposal operation details.

Figure 35: Operation


Realization from Operation to Facility

Aggregation from Operation to Notification

ATTRIBUTES

operationID : int Public

Description:

Operation ID

Operation

+ operationID: int


+ operationStage: OperationStage

+ facility: Facility

+ facil ityInformation: int


+ actualSite: string

+ technologyEmployed: string

+ reasonOfExport: string

+ parentOperation: int

+ methodOfDisposal: string

+ recoveredMaterialAmount: double

+ estimatedValue: double

+ costOfRecovery: double

+ costOfDisposal: double






Description:

Operation code:

D1

D2

D3

D4

D5

D6

D7

D8

D9

D10

D11

D12

D13

D14

D15

R1

R2

R3

R4

R5

R6

R7

R8

R9

R10

R11

R12

R13

operationStage : OperationStage Public

Description:





Operation stage:

Interim operation

Non interim operation


Description:

Facility

facilityInformation : int Public

Description:

Used in case of subsequent operations

facilityType : OperationType Public

Description:

Facility type:

Disposal

Recovery

actualSite : string Public

Description:

Actual site of disposal/recovery

technologyEmployed : string Public

Description:

Technology employed





reasonOfExport : string Public

Description:

Reasons for export

parentOperation : int Public

Description:

Parent operation

methodOfDisposal : string Public

Description:

Planned method of disposal for the non-recoverable fraction after recovery

recoveredMaterialAmount : double Public

Description:

The amount of recovered material in relation to non-recoverable waste

estimatedValue : double Public

Description:

The estimated value of the recovered material

costOfRecovery : double Public

Description:

The cost of recovery

costOfDisposal : double Public





Description:

The cost of disposal of the non-recoverable fraction

2.28 Passage

Details of the recording passage of the consignment through the customs offices.

Figure 36: Passage


Aggregation from Passage to MovementDocument

ATTRIBUTES

passageID : int Public

Description:

Passage ID

customsOffice : CustomsOffice Public

Description:

Customs office

Passage

+ passageID: int

+ customsOffice: CustomsOffice

+ passageType: ConcernedCountryType

+ passageDate: date

+ country: Country

+ entry: string

+ exit: string





passageType : ConcernedCountryType Public

Description:

Passage type:

Export/Dispatch

Transit

Import/Destination

passageDate : date Public

Description:

Passage date


Description:

Country

entry : string Public

Description:

Entry

exit : string Public

Description:

Exit

2.29 Quantity

Waste quantity.





Figure 37: Quantity


Aggregation from Quantity to WasteIdentification

ATTRIBUTES

quantity : double Public

Description:

Quantity

unit : QuantityUnit Public

Description:

Quantity unit

estimatedQuantityMin : double Public

Description:

Estimated minimum weight

estimatedQuantityMax : double Public

Description:

Estimated maximum weight

Quantity

+ quantity: double

+ unit: QuantityUnit

+ estimatedQuantityMin: double

+ estimatedQuantityMax: double





2.30 Receipt

Details of the confirmation of receipt of the waste issued by facilities.

Figure 38: Receipt


Aggregation from Receipt to MovementDocument

Realization from Receipt to Facility


Aggregation from RecoveryDisposal to Receipt

ATTRIBUTES

receiptID : int Public

Description:

Receipt ID

Receipt

+ receiptID: int

+ receivedOn: date

+ rejected: boolean

+ rejectionReason: string

+ facil ity: Facil ity


+ receivedWasteQuantity: double

+ receivedWasteUnit: QuantityUnit

+ approximateDate: date


+ sentOn: date





receivedOn : date Public

Description:

Shipment date of reception

rejected : boolean Public

Description:

Shipment rejected

rejectionReason : string Public


Description:

Facility issues the receipt

facilityType : OperationType Public

Description:

Facility type:

Disposal

Recovery

receivedWasteQuantity : double Public

Description:

Received waste quantity

receivedWasteUnit : QuantityUnit Public

Description:





Received waste quantity unit

approximateDate : date Public

Description:

Approximate date of disposal/recovery


Description:

Disposal/recovery operation:

D1

D2

D3

D4

D5

D6

D7

D8

D9

D10

D11

D12

D13

D14

D15

R1

R2

R3

R4

R5

R6

R7

R8

R9

R10

R11





R12

R13


Description:

Send date (receipt)

2.31 RecoveryDisposal

Details of the confirmation of recovery/disposal of the waste issued by facilities.

Figure 39: RecoveryDisposal


Aggregation from RecoveryDisposal to Receipt

ATTRIBUTES

completedOn : date Public

Description:

Date of the completion of the disposal/recovery


Description:

RecoveryDisposal

+ completedOn: date

+ sentOn: date





Send date

2.32 Request

Request (Information Request) details.

Figure 40: Request

ATTRIBUTES

requestType : RequestType Public

Description:

Request type:

Notification

Movement

Additional

requestCode : string Public

Description:

Annex II: Part1, Part2 or Part3 codes.

2.33 RouteCustomsOffice

Customs offices linked to a route section.

Request

+ requestType: RequestType

+ requestCode: string





Figure 41: RouteCustomsOffice

ATTRIBUTES

routeCustomsOfficeID : int Public

Description:

Route Customs Office ID

entry : string Public

Description:

Custom office of entry into the Community

exit : string Public

Description:

Customs office of exit from the Community

export : string Public

Description:

Customs office of export from the Community

RouteCustomsOffice

+ routeCustomsOfficeID: int

+ entry: string

+ exit: string

+ export: string





ASSOCIATIONS



Cardinality: [1]

Target: Public (Class) RouteCustomsOffice

Cardinality: [0..*]

2.34 RouteSection

Route section details.

Figure 42: RouteSection


Realization from RouteSection to CompetentAuthority

ATTRIBUTES

distance : long Public

Description:

Distance (km)

ASSOCIATIONS


Source: Public (Class) RouteSection Target: Public (Class) ConcernedCountry

RouteSection

+ distance: long





Cardinality: [1]

Cardinality: [2]



Cardinality: [1]

Target: Public (Class) IntendedCarrier

Cardinality: [1]



Cardinality: [1]

Target: Public (Class) RouteCustomsOffice

Cardinality: [0..*]



Cardinality: [1]

Target: Public (Class) FinalCarrier

Cardinality: [1]


Source: Public (Class) Routing

Cardinality: [1]

Target: Public (Class) RouteSection

Cardinality: [1..*]

2.35 Routing

Routing details (point of exit from and entry into each country concerned, including

customs offices of entry into and/or exit from and/or export from the Community) including

possible alternatives. It is composed of route sections.

Figure 43: Routing

Routing

+ exportCountry: Country

+ exportCompetentAuthority: CompetentAuthority

+ exportSpecificPoint: string

+ importCountry: Country

+ importCompetentAuthority: CompetentAuthority

+ importSpecificPoint: string

+ alternativeRoute: Routing [0..*]





ATTRIBUTES

exportCountry : Country Public

Description:

Export country

exportCompetentAuthority : CompetentAuthority Public

Description:

Export competent authority

exportSpecificPoint : string Public

Description:

Export specific point

importCountry : Country Public

Description:

Import country

importCompetentAuthority : CompetentAuthority Public

Description:

Import competent authority

importSpecificPoint : string Public

Description:

Import specific point





alternativeRoute : Routing Public

Multiplicity: ( [0..*], Allow duplicates: 0, Is ordered: False )

Description:

Alternative route

ASSOCIATIONS


Source: Public (Class) Routing

Cardinality: [1]

Target: Public (Class) RouteSection

Cardinality: [1..*]



Cardinality: [1]

Target: Public (Class) Routing

Cardinality: [1]

2.36 UNClass

UNClass details.

1 - H1 - Explosive

3 - H3 - Flammable liquids

4.1 - H4.1 - Flammable solids

4.2 - H4.2 - Substances or wastes liable to spontaneous combustion

4.3 - H4.3 - Substances or wastes which, in contact with water, emit flammable gases

5.1 - H5.1 - Oxidising

5.2 - H5.2 - Organic peroxides

6.1 - H6.1 - Poisonous (acute)

6.2 - H6.2 - Infectious substances





8 - H8 - Corrosives

9 - H10 - Liberation of toxic gases in contact with air or water

9 - H11 - Toxic (delayed or chronic)

9 - H12 - Ecotoxic

9 - H13 - Capable, by any means, after disposal of yielding another material, e.g.,

leachate, which possesses any of the characteristics listed above

Figure 44: UNClass

ATTRIBUTES

unClass : string Public

Description:

UN Class

hCode : string Public

Description:

H-code

characteristics : string Public

Description:

Characteristics

UNClass

+ unClass: string

+ hCode: string

+ characteristics: string





2.37 Waste

Waste details.

Figure 45: Waste

ATTRIBUTES

wasteCode : string Public

Description:

Waste code

wasteType : string Public

Description:

Waste type

description : string Public

Description:

Waste description

2.38 WasteIdentification

Details on the waste intended to be shipped for this notification, such as waste

classification, waste quantity and physical characteristics.

Waste

+ wasteCode: string

+ wasteType: string

+ description: string





Figure 46: WasteIdentification


Aggregation from WasteIdentification to Notification


Aggregation from Quantity to WasteIdentification

ATTRIBUTES

designationAndComposition : string Public

Description:

Designation and composition of the waste

physicalCharacteristics : PhysicalCharacteristic Public

Description:

Physical characteristics:

Powdery/powder

WasteIdentification

+ designationAndComposition: string

+ physicalCharacteristics: PhysicalCharacteristic

+ baselAnnexVIIIorIX: int

+ codeOECD: int

+ ecList: int

+ exportCountryCode: string

+ importCountryCode: string

+ other: string

+ codeY: int

+ codeH: UNClass

+ unClass: UNClass

+ unNumber: int

+ unShippingName: int

+ customsCode: int





Solid

Viscous/Paste

Sludgy

Liquid

Gaseous

Other

baselAnnexVIIIorIX : int Public

Description:

Basel Annex VIII (or IX if applicable)

codeOECD : int Public

Description:

OECD code (if different from 'baselAnnexVIIIorIX')

ecList : int Public

Description:

EC list of wastes

exportCountryCode : string Public

Description:

National code in country of export

importCountryCode : string Public

Description:

National code in country of import





other : string Public

Description:

Other (specify)

codeY : int Public

Description:

Y-code

codeH : UNClass Public

Description:

H-code

unClass : UNClass Public

Description:

UN class

unNumber : int Public

Description:

UN number

unShippingName : int Public

Description:

UN shipping name

customsCode : int Public

Description:





Customs code (HS)

2.39 WasteProducer

Waste producer (agent) details. A waste producer is anyone whose activities produce waste

(original producer) and/or anyone who carries out pre-processing, mixing or other

operations resulting in a change in the nature or composition of this waste (new producer)

(as defined in Article 1(1)(b) of Directive 2006/12/EC).

Figure 47: WasteProducer


Generalization from WasteProducer to Agent

ATTRIBUTES

site : string Public

Description:

Waste producer site

generationProcess : string Public

Description:

Waste producer process of generation

Agent

WasteProducer

+ site: string

+ generationProcess: string





ASSOCIATIONS

Association (direction: Unspecified) has one or many


Cardinality: [1]

Target: Public (Class) WasteProducer

Cardinality: [1..*]

2.40 WrittenConsent

Details of the concerned authorities' consent regarding a notified shipment.

Figure 48: WrittenConsent


Aggregation from WrittenConsent to Notification

ATTRIBUTES

consentID : int Public

Description:

Consent ID

givenOn : date Public

WrittenConsent

+ consentID: int

+ givenOn: date

+ withdrawnOn: date

+ validFrom: date

+ validUntil: date


+ hasSpecificConditions: boolean

+ specificConditions: string

+ tacit: boolean





Description:

Consent issued on (date)

withdrawnOn : date Public

Description:

Consent withdrawn on (date)

validFrom : date Public

Description:

Consent valid from (date)

validUntil : date Public

Description:

Consent valid until (date)


Description:

Competent authority issuing the consent

hasSpecificConditions : boolean Public

Description:

Whether the consent has specific conditions

specificConditions : string Public

Description:

Specific conditions on consenting





tacit : boolean Public

Description:

Whether the consent is tacit





2.41 CommentType

Enumeration: Comment types.

ATTRIBUTES

G : Public

Description:

General

NNT : Public

Description:

Notification not transmitted

NNA : Public

Description:

Notification not acknowledged

2.42 ConcernedCountryType

Enumeration: Concerned country types.

ATTRIBUTES

Export/Dispatch : Public

Transit : Public

Import/Destination : Public





2.43 IllegalShipmentType

Enumeration: Illegal shipment types (Article 2.35).

ATTRIBUTES

A : Public

Description:

Without notification to all competent authorities concerned pursuant to this Regulation

B : Public

Description:

Without the consent of the competent authorities concerned pursuant to this Regulation

C : Public

Description:

With consent obtained from the competent authorities concerned through falsification, misrepresentation or

fraud

D : Public

Description:

In a way which is not specified materially in the notification or movement documents

E : Public

Description:

In a way which results in recovery or disposal in contravention of Community or international rules

F : Public

Description:





Contrary to Articles 34, 36, 39, 40, 41 and 43

G1 : Public

Description:

In relation to shipments of waste as referred to in Article 3(2) and (4), has resulted from: the waste being

discovered not to be listed in Annexes III, IIIA or IIIB

G2 : Public

Description:

In relation to shipments of waste as referred to in Article 3(2) and (4), has resulted from: non-compliance with

Article 3(4)

G3 : Public

Description:

In relation to shipments of waste as referred to in Article 3(2) and (4), has resulted from: the shipment being

effected in a way which is not specified materially in the document set out in Annex VII

Other : Public

2.44 IllegalityResponsibleType

Enumeration: Illegality responsible types.

ATTRIBUTES

Notifier : Public

Consignee : Public





Other : Public

2.45 MeansOfTransport

Enumeration: Means of transport.

ATTRIBUTES

Road : Public

Trail/Rail : Public

Sea : Public

Air : Public

Inland waterways : Public

2.46 NotificationStatus

Enumeration: Notification statuses.

ATTRIBUTES

Draft : Public

Submitted : Public

Approved : Public





Acknowledged : Public

Completed : Public

Rejected : Public

Expired : Public

2.47 OperationCode

Enumeration: Operation codes.

ATTRIBUTES

D1 : Public

Description:

Deposit into or onto land (e.g. landfill, etc.)

D2 : Public

Description:

Land treatment (e.g. biodegradation of liquid or sludgy discards

in soils, etc.)

D3 : Public

Description:

Deep injection (e.g. injection of pumpable discards into wells,

salt domes of naturally occurring repositories, etc.)

D4 : Public





Description:

Surface impoundment (e.g. placement of liquid or sludge

discards into pits, ponds or lagoons, etc.)

D5 : Public

Description:

Specially engineered landfill (e.g. placement into lined discrete

cells which are capped and isolated from one another and the

environment, etc.)

D6 : Public

Description:

Release into a water body except seas/oceans

D7 : Public

Description:

Release into seas/oceans including sea-bed insertion

D8 : Public

Description:

Biological treatment not specified elsewhere in this list which

results in final compounds or mixtures which are discarded by

means of any of the operations in this list (D)

D9 : Public

Description:

Physico-chemical treatment not specified elsewhere in this list which results in final compounds or mixtures

which are discarded

by means of any of the operations in this list (D) (e.g., evaporation,





drying, calcination, etc.)

D10 : Public

Description:

Incineration on land

D11 : Public

Description:

Incineration at sea

D12 : Public

Description:

Permanent storage (e.g., emplacement of containers in a mine,

etc.)

D13 : Public

Description:

Blending or mixing prior to submission to any of the operations in

this list (D)

D14 : Public

Description:

Repackaging prior to submission to any of the operations in

this list (D)

D15 : Public

Description:





Storage pending any of the operations in this list (D)

R1 : Public

Description:

Use as a fuel (other than in direct incineration) or other means to

generate energy (Basel/OECD) - Use principally as a fuel or other means to generate energy (EU)

R2 : Public

Description:

Solvent reclamation/regeneration

R3 : Public

Description:

Recycling/reclamation of organic substances which are not used as

solvents

R4 : Public

Description:

Recycling/reclamation of metals and metal compounds

R5 : Public

Description:

Recycling/reclamation of other inorganic materials

R6 : Public

Description:

Regeneration of acids or bases





R7 : Public

Description:

Recovery of components used for pollution abatement

R8 : Public

Description:

Recovery of components from catalysts

R9 : Public

Description:

Used oil re-refining or other reuses of previously used oil

R10 : Public

Description:

Land treatment resulting in benefit to agriculture or ecological

improvement

R11 : Public

Description:

Uses of residual materials obtained from any of the operations

numbered R1-R10

R12 : Public

Description:

Exchange of wastes for submission to any of the operations

numbered R1-R11





R13 : Public

Description:

Accumulation of material intended for any operation in this list (R)

2.48 OperationStage

Enumeration: Operation stages.

ATTRIBUTES

Interim operation : Public

Non interim operation : Public

2.49 OperationType

Enumeration: Operation types.

ATTRIBUTES

Disposal : Public

Recovery : Public





2.50 PackagingType

Enumeration: Packaging types.

ATTRIBUTES

Drum : Public

Wooden barrel : Public

Jerrican : Public

Box : Public

Bag : Public

Composite packaging : Public

Pressure receptacle : Public

Bulk : Public

Other : Public

2.51 PhysicalCharacteristic

Enumeration: Physical characteristics.

ATTRIBUTES

Powdery/powder : Public





Solid : Public

Viscous/Paste : Public

Sludgy : Public

Liquid : Public

Gaseous : Public

Other : Public

2.52 QuantityUnit

Enumeration: Quantity units.

ATTRIBUTES

Tonnes (Mg) : Public

Kg : Public

m3 : Public

Litres : Public

2.53 RequestType

Enumeration: Request types.





ATTRIBUTES

Notification : Public

Movement : Public

Additional : Public

2.54 RoleType

Enumeration: Role types.

ATTRIBUTES

Producer : Public

Licensed producer : Public

Collector : Public

Dealer : Public

Broker : Public

Disposal facility : Public

Recovery facility : Public

Laboratory : Public





Carrier : Public

Customs office : Public

2.55 RoutePointType

Enumeration: Route point type.

ATTRIBUTES

Entry : Public

Exit : Public

2.56 ShipmentStatus

Enumeration: Shipment status.

ATTRIBUTES

Shipped : Public

Received : Public

Received - Interim : Public

Recovered / Disposed : Public

Recovered / Disposed - Interim : Public





2.57 ShipmentType

Enumeration: Shipment type.

ATTRIBUTES

Individual : Public

Multiple : Public

2.58 StatusType

Enumeration: Information Request / Objection status type.

ATTRIBUTES

Open : Public

Solved : Public

Closed : Public






1. Introduction

This annex provides details about the Regulation (EC) No 1013/2006 of the European


annex defines the requirements model of the proposed solution; establishing the needs of

stakeholders which are to be solved by software products.

2. Requirements Model

The requirements model for Waste Shipment Regulation is a structured catalogue of end-

user requirements. These are represented as either Requirement or Feature elements. The

model is divided into three sub-catalogues:

1. 'Central Application' functional requirements package, contains requirements and

features that represent functional behaviour and features that the API under

development must support.

2. ‘Shared Application' functional requirements package, contains requirements and

features that represent functional behaviour and features that the shared website

under development must support.

3. 'Non-functional' requirements package, contains constraints and performance levels

the system must meet. For example response times, transactions per second,

security strength.





2.1 Requirements Model diagram

Figure 49: Requirements Model

Shared Application

+ System Administration

+ Transverse

+ Schedulers

+ ECAS user authentication

Non-Functional

+ Performance

+ Scalability

+ Security

+ Testability

+ Usability

The 'Shared Application' functional

requirements package details behavioral

requirements that specify the proposed website

will contain.

The Non-Functional Requirements package specifies

the various operational parameters that define the

environment in which the system will exist. These are

criteria which define performance levels, scalability,

security requirements, backup, disaster recovery and

other operational requirements.

Central Application

+ Notification management

+ Transverse

The 'Central Application' functional requirements

package details behavioral requirements that specify

how the proposed API will process and handle

information. It details the features and rules that must

be present to fully implement the functionality desired.





2.2 Activity Diagrams

In this section the activity diagrams detail the proposed solution workflows to comply with

WSR.

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. In the Unified Modeling

Language, activity diagrams are intended to model both computational and organizational

processes. Activity diagrams show the overall flow of control.

Activity diagrams are constructed from a limited number of shapes, which are connected

with arrows. The most important shape types are:

rounded rectangles which represent actions;

diamonds represent which decisions;

bars which represent the start (split) or end (join) of concurrent activities;

a black circle which represents the start (initial state) of the workflow;

an encircled black circle which represents the end (final state).

2.2.1 Process Notification

2.2.1.1 Within the Community

TITLE II

SHIPMENTS WITHIN THE COMMUNITY WITH OR WITHOUT TRANSIT THROUGH THIRD

COUNTRIES





Process Notification activity diagram

The activity diagram below depicts waste shipment notification workflow regarding Regulation (EC) No 1013/2006 ‘Title II’: Shipments within the

community with or without transit through third countries.

Figure 50: Process Notification activity

Sh

ipm

en

t

Ca

rrie

rF

ac

ilit

yN

oti

fie

r

Co

nc

ern

ed

CA

s

No

tifi

ca

tio

n

CA

of

Tra

ns

itC

A o

f D

isp

atc

hN

oti

fie

r

START

END

Need

info?

Create

Notification

document

Submit

Notification

Need

info?

>3 days since

last

Notification

update?

Approv e

Notification

Create reasoned

explanation

CA

of

De

sti

na

tio

n

Satisfied? Acknowledge

Notification

Process Information

Request

Objections?

>3 days since

last

Notification

update?

Process

Objection

Not in the

Directive

Not in the

Directive

> 30 days in

SUBMITTED

status

Not in the

Directive

DRAFT

SUBMITTED

EXPIRED

APPROVED

Process Information

Request

COMPLETED

>3 days since

last

Notification

update?

> 30 days in

APPROVED

status

Create reasoned

explanation

ACKNOWLEDGED

YES:

Not in the

Directive

Objections?

Create consent

Process

Objection

>7/30 days

since

Notification

acknowledged?

NO:

Not in the

Directive.

Tacit

Consent?

> 30 days in

ACKNOWLEDGED

status

Not in the

Directive

Create

Mov ement

document

Start shipment

Withdraw consent

All concerned

CAs consent?

>30 days since

Notification

acknowledged?

START

>7/30 days

since

Notification

acknowledged?

Confirm receipt

Confirm

recov ery/disposal

SHIPPED

RECEIVED

RECOVERED /

DISPOSED

Waste

Shipment

Custody transfer

Addtional

carriers?

Interim?

END

Addtional

country,

same

country?

Process notification

RECEIVED -

INTERIM

RECOVERED /

DISPOSED -

INTERIM

REJECTED

Update mov ement

document

[NO]

[NO]

[YES]

[NO][NO]

[YES]

[NO]

[NO]

[NO]

[YES]

[NO]

[YES]

[NO]

[YES]

[TACIT]

[YES]

[NO]

[YES]

[YES]

[NO]

[YES]

[YES]

[NO]

[NO]





Action-Requirement Matrix diagram

Figure 51: Action-Requirement Matrix

2.2.1.2 Within Member States

TITLE III

SHIPMENTS EXCLUSIVELY WITHIN MEMBER STATES

Article 33.3

Member States may apply the system provided for in Titles II and VII within their jurisdiction

2.2.1.3 Exports

TITLE IV

EXPORTS FROM THE COMMUNITY TO THIRD COUNTRIES

2.2.1.3.1 Disposal - EFTA

Exports of waste for disposal

Article 35

Procedures when exporting to EFTA countries






The activity diagram below depicts waste shipment notification workflow regarding Regulation (EC) No 1013/2006 ‘Title IV’: Exports from the

community to third countries; ‘CHAPTER 1’: Exports of waste for disposal; ‘Article 35’: Procedures when exporting to EFTA countries.


Sh

ipm

en

t

Ca

rrie

rF

ac

ilit

yN

oti

fie

r

Co

nc

ern

ed

CA

s

No

tifi

ca

tio

n

CA

of

Tra

ns

it i

n t

he

Co

mm

un

ity

CA

of

Dis

pa

tch

No

tifi

er

START

END

Need

info?

Create

Notification

document

Submit

Notification

Need

info?

>3 days since

last

Notification

update?

Approv e

Notification

Create reasoned

explanation

CA

of

De

sti

na

tio

n

Satisfied?

Acknowledge

Notification

Process Information

Request

Objections?

>3 days since

last

Notification

update?

Process

Objection

Not in the

Directive

Not in the

Directive

> 30 days in

SUBMITTED

status

Not in the

Directive

DRAFT

SUBMITTED

EXPIRED

APPROVED

Process Information

Request

COMPLETED

>3 days since

last

Notification

update?

> 30 days in

APPROVED

status

Create reasoned

explanation

ACKNOWLEDGED

YES:

Not in the

Directive

Objections?

Create consent

Process

Objection

>30 days since

Notification

acknowledged?

NO:

Not in the

Directive.

Tacit

Consent?

> 30 days in

ACKNOWLEDGED

status

Not in the

Directive

Create

Mov ement

document

Start shipment

Withdraw consent

All concerned

CAs consent?

>30 days since

Notification

acknowledged?

START

>30 days since

Notification

acknowledged?

Confirm receipt

Confirm

recov ery/disposal

SHIPPED

RECEIVED

RECOVERED /

DISPOSED

Waste

Shipment

Custody transfer

Addtional

carriers?

Interim?

END

Addtional

country,

same

country?


RECEIVED -

INTERIM

RECOVERED /

DISPOSED -

INTERIM

REJECTED

Update mov ement

document

CA

of

Tra

ns

it o

uts

ide

th

e

Co

mm

un

ity

>60 days since

the Notification

receipt?

YES:

Not in the

Directive

Acknowledge

Notification

Cu

sto

ms

off

ice

Record passage

> 42 days in

SHIPPED status

> 60 days in

ACKNOWLEDGED

status

[NO]

[NO]

[YES]

[NO]

[YES]

[NO]

[NO]

[YES]

[YES]

[NO]

[YES]

[NO]

[YES]

[NO]

[YES]

[TACIT]

[NO]

[YES]

[NO]

[NO]

[YES]

[NO]

[NO]

[YES]

[NO]







2.2.1.3.2 Recovery - OECD

Exports of waste for recovery

Article 38

Exports of waste listed in Annexes III, IIIA, IIIB, IV and IVA






The activity diagram below depicts waste shipment notification workflow regarding Regulation (EC) No 1013/2006 'Title IV': Exports from the

community to third countries; 'CHAPTER 2': Exports of waste for recovery; ‘Article 38’: Exports of waste listed in Annexes III, IIIA, IIIB, IV and IVA.


Sh

ipm

en

t

Ca

rrie

rF

ac

ilit

yN

oti

fie

r

Co

nc

ern

ed

CA

s No

tifi

ca

tio

n

CA

of

Tra

ns

it O

EC

DC

A o

f D

isp

atc

hN

oti

fie

r

START

END

Need

info?

Create

Notification

document

Submit

Notification

Need

info?

>3 days since

last

Notification

update?

Approv e

Notification

Create reasoned

explanationC

A o

f D

es

tin

ati

on

Satisfied? Acknowledge

Notification

Process Information

Request

Objections?

>3 days since

last

Notification

update?

Process

Objection

Not in the

Directive

Not in the

Directive

> 30 days in

SUBMITTED

status

Not in the

Directive

DRAFT

SUBMITTED

EXPIRED

APPROVED

Process Information

Request

COMPLETED

>3 days since

last

Notification

update?

> 30 days in

APPROVED

status

Create reasoned

explanation

ACKNOWLEDGED

YES:

Not in the

Directive

Objections?

Create consent

Process

Objection

>7/30 days

since

Notification

acknowledged?

NO:

Not in the

Directive.

Tacit

Consent?

> 30 days in

ACKNOWLEDGED

status

Not in the

Directive

Create

Mov ement

document

Start shipment

Withdraw consent

All concerned

CAs consent?

>30 days since

Notification

acknowledged?

START

>7/30 days

since

Notification

acknowledged?

Confirm receipt

Confirm

recov ery/disposal

SHIPPED

RECEIVED

RECOVERED /

DISPOSED

Waste

Shipment

Custody transfer

Addtional

carriers?

Interim?

END

Addtional

country,

same

country?


RECEIVED -

INTERIM

RECOVERED /

DISPOSED -

INTERIM

REJECTED

Update mov ement

document

CA

of

Tra

ns

it N

OT

OE

CD

>60 days since

the Notification

receipt?

YES:

Not in the

Directive

Cu

sto

ms

off

ice

Record passage

> 42 days in

SHIPPED status

> 60 days in

ACKNOWLEDGED

status

[NO]

[YES]

[NO]

[NO]

[YES]

[YES]

[YES]

[YES]

[NO]

[NO]

[NO]

[YES]

[YES]

[NO]

[NO]

[NO]

[YES]

[TACIT]

[NO]

[YES]

[NO]

[YES]

[NO]

[NO]

[NO]







2.2.1.4 Imports

TITLE V

IMPORTS INTO THE COMMUNITY FROM THIRD COUNTRIES

2.2.1.4.1 Disposal - Party to the Basel Convention or crisis/war

Imports of waste for disposal

Article 42

Procedural requirements for imports from a country Party to the Basel Convention or from

other areas during situations of crisis or war






The activity diagram below depicts waste shipment notification workflow regarding Regulation (EC) No 1013/2006 'Title V': Imports into the

community from third countries; 'CHAPTER 1': Imports of waste for disposal; 'Article 42': Procedural requirements for imports from a country

Party to the Basel Convention or from other areas during situations of crisis or war.


Sh

ipm

en

t

Ca

rrie

rF

ac

ilit

yN

oti

fie

r

Co

nc

ern

ed

CA

s

No

tifi

ca

tio

n

CA

of

Tra

ns

it i

n t

he

Co

mm

un

ity

CA

of

Dis

pa

tch

No

tifi

er

START

END

Need

info?

Create

Notification

document

Submit

Notification

Need

info?

>3 days since

last

Notification

update?

Approv e

Notification

Create reasoned

explanation

CA

of

De

sti

na

tio

n

Satisfied?

Acknowledge

Notification

Process Information

Request

Objections?

>3 days since

last

Notification

update?

Process

Objection

Not in the

Directive

Not in the

Directive

> 30 days in

SUBMITTED

status

Not in the

Directive

DRAFT

SUBMITTED

EXPIRED

APPROVED

Process Information

Request

COMPLETED

>3 days since

last

Notification

update?

> 30 days in

APPROVED

status

Create reasoned

explanation

ACKNOWLEDGED

YES:

Not in the

Directive

Objections?

Create consent

Process

Objection

> 30 days since

Notification

acknowledged?

NO:

Not in the

Directive.

Tacit

Consent?

> 30 days in

ACKNOWLEDGED

status OR

situations of

crisis/war

Not in the

Directive

Create

Mov ement

document

Start shipment

Withdraw consent

All concerned

CAs consent?

>30 days since

Notification

acknowledged?

START

>30 days since

Notification

acknowledged?

Confirm receipt

Confirm

recov ery/disposal

SHIPPED

RECEIVED

RECOVERED /

DISPOSED

Waste

Shipment

Custody transfer

Addtional

carriers?

Interim?

END

Addtional

country,

same

country?


RECEIVED -

INTERIM

RECOVERED /

DISPOSED -

INTERIM

REJECTED

Update mov ement

document

CA

of

Tra

ns

it o

uts

ide

th

e

Co

mm

un

ity

>60 days since

the Notification

receipt?

YES:

Not in the

Directive

Acknowledge

Notification

Cu

sto

ms

off

ice

Record passage

[NO]

[NO]

[YES]

[NO]

[NO]

[NO]

[NO]

[YES]

[YES]

[YES]

[TACIT]

[YES]

[YES]

[YES]

[NO]

[YES]

[NO]

[NO]

[NO]

[NO]

[YES]

[NO]

[YES]

[NO]

[NO]







2.2.1.4.2 Recovery - OECD or crisis/war

Imports of waste for recovery

Article 44

Procedural requirements for imports from an OECD Decision country or from other areas

during situations of crisis or war






The activity diagram below depicts waste shipment notification workflow regarding Regulation (EC) No 1013/2006 'Title V': Imports into the

community from third countries; 'CHAPTER 2': Imports of waste for recovery; 'Article 44': Procedural requirements for imports from an OECD

Decision country or from other areas during situations of crisis or war.


Sh

ipm

en

t

Ca

rrie

rF

ac

ilit

yN

oti

fie

r

Co

nc

ern

ed

CA

s

CA

of

Tra

ns

it

No

tifi

ca

tio

n

CA

of

Dis

pa

tch

No

tifi

er

START

END

Need

info?

Create

Notification

document

Submit

Notification

Need

info?

>3 days since

last

Notification

update?

Approv e

Notification

Create reasoned

explanation

CA

of

De

sti

na

tio

n

Satisfied?

Acknowledge

Notification

Process Information

Request

Objections?

>3 days since

last

Notification

update?

Process

Objection

Not in the

Directive

Not in the

Directive

> 30 days in

SUBMITTED

status

Not in the

Directive

DRAFT

SUBMITTED

EXPIRED

APPROVED

Process Information

Request

COMPLETED

>3 days since

last

Notification

update?

> 30 days in

APPROVED

status

Create reasoned

explanation

ACKNOWLEDGED

YES:

Not in the

Directive

Objections?

Create consent

Process

Objection

>7/30 days

since

Notification

acknowledged?

NO:

Not in the

Directive.

Tacit

Consent?

> 30 days in

ACKNOWLEDGED

status OR

situations of

crisis/war

Not in the

Directive

Create

Mov ement

document

Start shipment

Withdraw consent

All concerned

CAs consent?

>30 days since

Notification

acknowledged?

START

>7/30 days

since

Notification

acknowledged?

Confirm receipt

Confirm

recov ery/disposal

SHIPPED

RECEIVED

RECOVERED /

DISPOSED

Waste

Shipment

Custody transfer

Addtional

carriers?

Interim?

END

Addtional

country,

same

country?


RECEIVED -

INTERIM

RECOVERED /

DISPOSED -

INTERIM

REJECTED

Update mov ement

document

Cu

sto

ms

off

ice

Record passage

[NO]

[YES]

[NO]

[NO]

[YES]

[YES]

[YES]

[NO]

[NO]

[NO]

[NO]

[YES]

[NO]

[TACIT]

[NO]

[NO]

[YES]

[NO]

[YES]

[YES]

[NO]

[YES]

[NO]

[YES]







2.2.1.4.3 Recovery - non-OECD or crisis/war

Imports of waste for recovery

Article 45

Where waste destined for recovery is imported into the Community:

(a) from a country to which the OECD Decision does not apply; or

(b) through any country to which the OECD Decision does not apply and which is

also Party to the Basel Convention,

Article 42 shall apply mutatis mutandis

2.2.1.5 Transit

TITLE VI

TRANSIT THROUGH THE COMMUNITY FROM AND TO THIRD COUNTRIES

2.2.1.5.1 Disposal

Transit of waste for disposal

Article 47

Transit through the Community of waste destined for disposal





Where waste destined for disposal is shipped through Member States from and to third

countries, Article 42 shall apply mutatis mutandis, with the adaptations and additions listed

below:

(a) the first and last competent authority of transit in the Community shall, where

appropriate, send a stamped copy of the decisions to consent to the shipment or, if

they have provided tacit consent, a copy of the acknowledgement in accordance

with Article 42(3)(a) to the customs offices of entry into and exit from the

Community respectively; and

(b) as soon as the waste has left the Community, the customs office of exit from the

Community shall send a stamped copy of the movement document to the

competent authority(ies) of transit in the Community, stating that the waste has left

the Community.

2.2.1.5.2 Recovery - non-OECD

Transit of waste for recovery

Article 48.1

Transit through the Community of waste destined for recovery

Where waste destined for recovery is shipped through Member States from and to a

country to which the OECD Decision does not apply, Article 47 shall apply mutatis mutandis

2.2.1.5.3 Recovery - OECD

Transit of waste for recovery

Article 48.2

Transit through the Community of waste destined for recovery

Where waste destined for recovery is shipped through Member States from and to a

country to which the OECD Decision applies, Article 44 shall apply mutatis mutandis, with

the adaptations and additions listed below:

(a) the first and last competent authority of transit in the Community shall, where

appropriate, send a stamped copy of the decisions to consent to the shipment or, if

they have provided tacit consent, a copy of the acknowledgement in accordance

with Article 42(3)(a) to the customs offices of entry into and exit from the

Community respectively; and





(b) as soon as the waste has left the Community, the customs office of exit from the

Community shall send a stamped copy of the movement document to the

competent authority(ies) of transit in the Community, stating that the waste has left

the Community

2.2.2 Process Information Request

Process Information Request activity diagram

The activity diagram below depicts the 'Information Request' workflow used in the waste

shipment notification workflows.





Figure 60: Process Information Request activity



Info

rma

tio

n r

eq

ue

st

Co

nc

ern

ed

CA

No

tifi

er

START

Create information

request

Solv e information

request

END

Update notification

document

Satisfied?Reopen information

request

Close information

request

Open

Closed

Solv ed

Update mov ement

document

[YES]

[NO]





2.2.3 Process Objection

Process Objection activity diagram

The activity diagram below depicts the 'Objection' workflow used in the waste shipment

notification workflows.

Figure 62: Process Objection activity



Ob

jec

tio

n

Co

nc

ern

ed

CA

No

tifi

er

START

Create objection

END

Close objection

Reopen objection

Update notification

document

Update mov ement

document

Solv e objection

Satisfied?

Open

Closed

Solv ed

[YES]

[NO]





2.3 Requirements

The Requirements package is a catalogue of explicit business rules which are required to be

implemented within the current project. Business Rules are typically executed during

program execution and control the processing of information and transactions

2.3.1 Central Application

Central Application functional requirements describe the features, behaviour, business rules

and general functionality that the proposed system must support

Central Application diagram

Figure 64: Central Application

2.3.1.1 Notification management

2.3.1.1.1 Notification document

2.3.1.1.1.1 Consents

REQ079 - Create consent

Article 9.1 (Blocks 20, 21)

The competent authorities of destination, dispatch and transit shall have 30 days following

the date of transmission of the acknowledgement by the competent authority of

destination in accordance with Article 8 in which to take one of the following duly reasoned

decisions in writing as regards the notified shipment:

(a) consent without conditions;

Notification management

+ Notification document

+ Movement document

+ Information request

+ Objections

+ Facility pre-consents

+ Comments

+ Approve notification

+ Create reasoned explanation

+ Submit notification

Transverse

+ Search agent

+ Search notification

+ Search waste





(b) consent with conditions in accordance with Article 10;

Given on

Valid from

Valid until

Competent authority

Has specific conditions

Specific conditions

Tacit

Element Status Created Last modified

FunctionalRequirement Proposed 22/01/2016 08/03/2016

Responsibilities (Internal Requirements)

'Valid from/until' dates must be valid (dd/mm/yyyy)

'Valid until' date must be greater than 'Valid from' date

Scenarios

Basic Path. Basic Path

1. The Concerned CA creates a consent without conditions (maximum period of validity is 1 year)

Alternate: 1a. Consent with conditions

2. The consent is linked to the Notification and stored in the system

3. The Notifier and the other Concerned CAs are notified

Alternate. Consent with conditions

1. The Concerned CA creates a consent with conditions

Alternate. General notification AND

Constraints





Constraints

Pre-condition - Notification

The notification was approved by the competent authority of dispatch or acknowledged by the competent

authority of destination

Notification status: APPROVED / ACKNOWLEDGED

Pre-condition - Time limit

Notification acknowledged no more than 30 days ago

Pre-consent facility:


OR

Period extended: Notification acknowledged no more than 30 days ago





Create consent_ActivityGraphWithAction diagram

Figure 65: Create consent_ActivityGraphWithAction

Start

Alternate1

The Concerned CA

creates a consent with

conditions

The Concerned CA

creates a consent

without conditions

(maxium period of

v alidity is 1 year)

The consent is linked to

the Notification and

stored in the system

The Notifier and the other

Concerned CAs are

notified

End

[Consent with conditions]





REQ080 - Create consent - Export

Article 35.2.b

The competent authority of dispatch in the Community shall take the decision to consent to

the shipment as referred to in Article 9 only after having received written consent from the

competent authority of destination and, where appropriate, the tacit or written consent of

the competent authority of transit outside the Community, and not earlier than 61 days

following the date of transmission of the acknowledgement by the competent authority of

transit. The competent authority of dispatch may take the decision before the conclusion of

the 61-day time limit if it has the written consent of the other competent authorities

concerned

Article 38.5.b

The competent authority of dispatch in the Community shall take the decision to consent to

the shipment as referred to in Article 9 only after having received tacit or written consent

from that competent authority of transit to which the OECD Decision does not apply, and

not earlier than 61 days following the date of transmission of the acknowledgement of the

competent authority of transit. The competent authority of dispatch may take the decision

before the conclusion of the 61-day time limit if it has the written consent of the other

competent authorities concerned

Given on

Valid from

Valid until

Specific conditions


Specific Conditions / Reasons

Tacit






Scenarios





Scenarios


1. The Concerned CA creates a consent without conditions (maximum period of validity is 1 year)

Alternate: 1a. Consent with conditions

2. The consent is linked to the Notification and stored in the system

3. The Notifier, the other Concerned CAs and the Customs Office of Export/Exit are notified

Alternate. Consent with conditions

1. The Concerned CA creates a consent with conditions

Alternate. General notification AND

Constraints


Not earlier than 61 days following the date of transmission of the acknowledgement by the competent

authority of transit. The competent authority of dispatch may take the decision before the conclusion of the 61-day

time limit if it has the written consent of the other competent authorities concerned.


The notification was approved by the competent authority of dispatch or acknowledged by the competent

authority of destination

Notification status: APPROVED / ACKNOWLEDGED





Create consent - Export_ActivityGraphWithAction diagram

Figure 66: Create consent - Export_ActivityGraphWithAction

REQ081 - Withdraw consent

Article 9.8

The competent authorities concerned shall withdraw their consent when they have

knowledge that:

(a) the composition of the waste is not as notified; or

(b) the conditions imposed on the shipment are not respected; or

(c) the waste is not recovered or disposed of in compliance with the permit of the facility

that performs the said operation; or

Start

Alternate1

The Concerned CA

creates a consent with

conditions

The Concerned CA

creates a consent

without conditions

(maxium period of

v alidity is 1 year)

The consent is linked to



The Notifie, the other

Concerned CAs and the

Customs Office of

Export/Exit are notified

End

[Consent with conditions]





(d) the waste is to be, or has been, shipped, recovered or disposed of in a way that is not in

accordance with the information supplied on, or annexed to, the notification and

movement documents

Article 9.9

Any withdrawal of consent shall be transmitted by means of official notice to the Notifier

with copies to the other competent authorities concerned and to the consignee



Scenarios


1. The Concerned CA withdraw a previously created consent

2. The consent linked to the Notification is updated (withdrawnOn) and stored in the system


Constraints

Pre-condition - Previous consent

A previous consent was created by the concerned competent authority







Withdraw consent_ActivityGraphWithAction diagram

Figure 67: Withdraw consent_ActivityGraphWithAction

Start

The Concerned CA

withdraw a prev iously

created consent

The consent linked to the

Notification is updated

and stored in the system


Concerned CAs are

notified

End





REQ082 - Create notification document

Any permitted agent must be able to create notification documents



Child elements

REQ083 - Add notifier

REQ084 - Add consignee

REQ085 - Add carriers

REQ086 - Add operations

REQ087 - Add shipment information

REQ088 - Add packaging information

REQ089 - Add waste producer

REQ090 - Add waste identification

REQ091 - Add routing

REQ092 - Add notification declaration

REQ093 - Attach the contract

REQ094 - Attach the financial guarantee

REQ095 - Attach document

Scenarios


1. Notifier fills the notifier information

Uses:

Add notifier

2. Notifier fills the consignee information

Uses:

Add consignee

3. Notifier fills the carriers information

Uses:

Add carriers

4. Notifier fills the operations information

Uses:

Add operations

5. Notifier fills the shipment information





Scenarios

Uses:

Add shipment information

6. Notifier fills the packaging information

Uses:

Add packaging information

7. Notifier fills the waste producer information

Uses:

Add waste producer

8. Notifier fills the waste identification information

Uses:

Add waste identification

9. Notifier fills the routing information

Uses:

Add routing

10. Notifier fills the contract information

Uses:

Attach the contract

11. Notifier fills the financial guarantee information

Uses:

Attach the financial guarantee

12. Optionally: Attach additional documents

Uses:

Attach document

13. Notifier fills the declaration information

Uses:

Add notification declaration

14. Optionally: Producer fills the declaration information

Uses:

Add notification declaration

15. The Notifier saves the Notification

16. The Notification Document is stored in the system

17. The Notification status is set to: DRAFT





Create notification document_ActivityGraphWithAction diagram

Figure 68: Create notification document_ActivityGraphWithAction

Start

Notifier fills the notifier

information

Notifier fills the

consignee information

Notifier fills the carriers

information

Notifier fills the

operations information

Notifier fills the shipment

information

Notifier fills the

packaging information

Notifier fills the waste

producer information


identification information

Notifier fills the routing

information

Notifier fills the contract

information

Notifier fills the financial

guarantee information

Optionally: Attach

additional documents

Notifier fills the

declaration information

Optionally: Producer fills

the declaration

information

The Notifier sav es the

Notification

The Notification

Document is stored in

the system

The Notification status is

set to: DRAFT

End





Create notification document diagram

Figure 69: Create notification document


Annex II - 1.2 (Block 1)

Notification document must supply notifier information:

Create notification document

Add waste producer

Add notifier

Add consignee

Add operations


Add packaging

information

Add carriers

Add routing

Attach the contract

Attach the financial

guarantee

Attach document


Add notification

declaration

Search agent

(from Transverse)





Name

Address

Telephone number

Fax number

Email address

Registration number

Contact person



External Requirements

REQ139 - Search agent



Notification document must supply consignee's information:

Name

Address

Telephone number

Fax number

Email address

Registration number

Contact person











Notification document must supply intended carriers' information:

Name

Address

Telephone number

Fax number

Email address

Registration number

Contact person

Means of transport

Notification document must specify all carriers taking care in the waste shipment






(Blocks 3, 10, 11)

Notification document must include at least one operation and facility information where

will be processed

Facility:

Name

Address

Telephone number

Fax number





Email address

Registration number

Contact person

Facility pre-consents

Actual site of disposal/recovery

Operation:

Facility type

Operation code

Technology employed

Reasons for export






(Blocks 3, 4, 6)

Notification document must include shipment information

Shipment type

Number of shipments

First departure

Last departure








(Block 7)

Notification document must define which packaging option is used and if requires special

handling

Packaging type

Special handling requirements




(Block 9)

Notification document must define which agents are the waste producers

Name

Address

Telephone number

Fax number

Email address

Registration number

Contact person

Site and process of generation










(Blocks 12, 13, 14)

Notification document must include waste identification

Designation and composition

Physical characteristics

Waste identification

Quantity (quantity, unit)



REQ091 - Add routing

(Block 15, 16)

Notification document must define a routing for the waste shipment

Routing:

Import country

Import competent authority

Import specific point

Export country

Export competent authority

Export specific point

Alternative routes

Route section:

Carrier

Means of transport

Custom offices








REQ092 - Add notification declaration

Annex IC.28 (Block 17)

Each copy of the notification document is to be signed and dated by the notifier (or by

dealer or broker if acting as a notifier) before being forwarded to the competent authorities

of the countries concerned. In some third countries, the competent authority of dispatch

may sign and date. When the notifier is not the same person as the original producer, this

producer, the new producer or the collector is, where practicable, also to sign and date; it is

noted that this may not be practicable in cases where there are several producers

(definitions regarding practicability may be contained in national legislation). Further, where

the producer is not known, the person in possession or control of the waste (holder) should

sign. This declaration should also certify the existence of insurance against liability for

damage to third parties. Some third countries may require proof of insurance or other

financial guarantees and a contract to accompany the notification document

Name

Date



REQ093 - Attach the contract

Article 5.1

All shipments of waste for which notification is required shall be subject to the requirement

of the conclusion of a contract between the notifier and the consignee for the recovery or

disposal of the notified waste







REQ094 - Attach the financial guarantee

Article 6.1

All shipments of waste for which notification is required shall be subject to the requirement

of a financial guarantee or equivalent insurance covering:

a) costs of transport

b) costs of recovery or disposal, including any necessary interim operation

c) costs of storage for 90 days



REQ095 - Attach document


Attach document containing any additional information supplied with the notification

document. Each annex must include a reference to the notification number to which it

relates



REQ098 - Update notification document

Allowed agents may update notification document information







REQ096 - Acknowledge notification

Article 8.2 (Block 19)

When the competent authority of destination considers that the notification has been

properly completed, as described in the second subparagraph, point 3 of Article 4, it shall

send an acknowledgement to the notifier and copies to the other competent authorities

concerned. This shall be done within three working days of receipt of the properly

completed notification

Received on

Acknowledgement sent on

Competent authority



Scenarios


1. The CA of Destination acknowledges a Notification

2. The Notification status is set to: ACKNOWLEDGED


Alternate. Export: CA of Transit in the Community

1. The CA of Transit in the Community acknowledges a Notification

2. The Notifier is notified

Constraints

Pre-condition - Notification approval

The notification was transmitted by the competent authority of dispatch.

Notification status: APPROVED





Constraints


Receipt of the properly completed notification no more than 3 working days ago

Acknowledge notification_ActivityGraphWithAction diagram

Figure 70: Acknowledge notification_ActivityGraphWithAction

Start

The CA of Destination

acknowledges a

Notification


set to: ACKNOWLEDGED


Concerned CAs are

notified

End





REQ097 - Acknowledge notification - Export/Import

Article 35.3.a

The competent authority of transit in the Community shall acknowledge the receipt of the

notification to the notifier;

Article 42.3.a

The competent authority of transit in the Community shall acknowledge the receipt of the

notification to the notifier, with copies to the competent authorities concerned;

Received on


Competent authority



Scenarios


1. The CA of Transit in the Community acknowledges a Notification


Alternate: 2a. Import

Alternate. Import


Constraints

Pre-condition - Notification approval







Constraints


Receipt of the properly completed notification no more than 3 working days ago





Acknowledge notification - Export/Import_ActivityGraphWithAction diagram

Figure 71: Acknowledge notification - Export/Import_ActivityGraphWithAction

Start

The CA of Transit in the

Community

acknowledges a

Notification

Alternate1


Concerned CAs are

notified

FlowEnd1

The Notifier is notified

End

[Import]





2.3.1.1.2 Movement document

2.3.1.1.2.1 Before shipment

REQ099 - Create movement document

Any allowed agent must be able to create movement documents



Child elements

REQ100 - Link movement / notification









REQ109 - Add movement declaration

REQ110 - Add additional information

Scenarios


1. The Movement Document is linked to a Notification Document

Uses:

Link movement / notification

2. Notifier fills the notifier information

Uses:

Add notifier

3. Notifier fills the consignee information

Uses:

Add consignee

4. Notifier fills the waste producer information

Uses:

Add waste producer





Scenarios

5. Notifier fills the operations information

Uses:

Add operations

6. Notifier fills the waste identification information

Uses:


7. Optionally: Notifier fills the shipment information

Uses:


8. Optionally: Notifier fills the carriers information

Uses:

Add carriers

9. Optionally: Notifier fills the packaging information

Uses:

Add packaging information

10. Optionally: Notifier fills the declaration information

Uses:

Add movement declaration

11. Optionally: Notifier fills the additional information

Uses:

Add additional information

12. The Movement Document is stored in the system

Constraints

Pre-condition - Notification creation

The Notification Document is already created





Create movement document_ActivityGraphWithAction diagram

Figure 72: Create movement document_ActivityGraphWithAction

Start

The Mov ement Document

is linked to a Notification

Document

Notifier fills the notifier

information

Notifier fills the

consignee information


producer information

Notifier fills the

operations information


identification information

Optionally: Notifier fills

the shipment information


the carriers information


the packaging

information


the declaration

information


the additional information

The Mov ement Document

is stored in the system

End





Create movement document diagram

Figure 73: Create movement document

Create mov ement

document

Add notifier

Add consignee

Add waste producer



Add carriers

Add packaging

information

Add mov ement

declaration

Add operations

Add additional information

Link mov ement /

notification





REQ100 - Link movement / notification

The movement document is linked to a notification document




(Block 3)

The Notifier information is obtained from the linked Notification Document




(Block 4)

The Consignee information is obtained from the linked Notification Document




(Block 9)

The waste producer information is obtained from the linked Notification Document








(Blocks 10, 11)

The Operations information is obtained from the linked Notification Document




(Blocks 12, 13, 14)

The waste identification information is obtained from the linked Notification Document




(Blocks 2, 5)

Movement document must include shipment information

Shipment serial

Shipment total number

Actual quantity (quantity, unit)

Article 16

(a) Completion of the movement document by the notifier: once the notifier has received

consent from the competent authorities of dispatch, destination and transit or, in relation to

the competent authority of transit, can assume tacit consent, he/she shall insert the actual

date of shipment and otherwise complete the movement document to the extent possible.





(b) Prior information regarding actual start of shipment: the notifier shall send signed

copies of the then completed movement document, as described in point (a), to the

competent authorities concerned and to the consignee at least three working days before

the shipment starts

Date of shipment




(Block 8)

Movement document must supply final carriers' information:

Name

Address

Telephone number

Fax number

Email address

Registration number

Contact person




(Blocks 7)

The movement document must define which packaging option is used, the number of

packages and if it requires special handling





Packaging type

Number of packages

Special handling requirements



REQ109 - Add movement declaration


At the time of shipment, the notifier (or the dealer or broker if acting as a notifier) shall sign

and date the movement document. In some third countries, the competent authority of

dispatch, or the generator of the waste according to the Basel Convention, may sign and

date the movement document. According to Article 16(c) of this Regulation, enclose copies

of the notification document containing the written consent, including any conditions, of

the competent authorities concerned with the movement document. Some third countries

may require originals to be enclosed

Name

Date


This block is to be completed by the consignee in the event that it is not the disposer or

recoverer (cf. paragraph 15 above) and in case the consignee takes charge of the waste

after the shipment arrives in the country of destination

Name

Date







REQ110 - Add additional information


This block can be used by any person involved in a shipment (notifier or the competent

authority of dispatch, as appropriate, consignee, any competent authority, carrier) in

specific cases where more detailed information is required by national legislation

concerning a particular item (for example, information on the port where a transfer to

another transport mode occurs, the number of containers and their identification number,

or additional proof or stamps indicating that the shipment has been consented by the

competent authorities). Give the routing (point of exit from and entry into each country

concerned, including customs offices of entry into and/or exit from and/or export from the

Community) and route (route between points of exit and entry), including possible

alternatives, also in case of unforeseen circumstances either in block 16 or attach it in an

annex

Additional information



REQ111 - Start shipment

Once the 'date of shipment' is reached the system sets the Shipment status to: SHIPPED



Scenarios


1. Once the 'Date of shipment' is reached the Notification status is set to: SHIPPED





Constraints

Pre-condition - Notification completion

The notification was acknowledged and all the concerned competent authorities consented it.

Notification status: COMPLETED

Start shipment_ActivityGraphWithAction diagram

Figure 74: Start shipment_ActivityGraphWithAction

REQ112 - Update movement document

Allowed agents may update movement document information



Start

Once the 'Date of

shipment' is reached the

Notification status is set

to: SHIPPED

End





2.3.1.1.2.2 During shipment

REQ113 - Custody transfer


The means of transport, the date of transfer and a signature should be provided by the

carrier or carrier’s representative taking possession of the consignment

Carrier

Means of transport

Date of transfer



Scenarios


1. The Carrier taking the custody of the shipment fills the custody transfer information

2. The custody transfer information is stored in the system (movement document)





Custody transfer_ActivityGraphWithAction diagram

Figure 75: Custody transfer_ActivityGraphWithAction

REQ114 - Record passage

(Blocks 20, 21, 22)

Record passage information must be reported by customs offices at the borders of the

Community

Article 35.3.d / Article 38.3.c

As soon as the waste has left the Community, the customs office of exit from the

Community shall send a stamped copy of the movement document to the competent

authority of dispatch in the Community stating that the waste has left the Community

Start

The Carrier taking the

custody of the shipment

fills the custody transfer

information

The custody transfer

information is stored in

the system (mov ement

document)

End





Article 42.3.d / Article 44.3

Having carried out the necessary customs formalities, the customs office of entry into the


authorities of destination and transit in the Community, stating that the waste has entered

the Community.

Article 47.b / Article 48.b

As soon as the waste has left the Community, the customs office of exit from the


authority(ies) of transit in the Community, stating that the waste has left the Community

Customs Office

Passage Type

Passage Date

Country

Entry

Exit



Scenarios


1. Customs Office selects the Passage Type

2. Customs Office of exit/entry fills the Passage information (Passage Date)

Alternate: 2a. Transit

3. The Passage is linked to the Movement Document and stored in the system

Alternate. Transit

1. Customs Office of transit fills the passage information (Country, Entry, Exit)





Record passage_ActivityGraphWithAction diagram

Figure 76: Record passage_ActivityGraphWithAction

REQ115 - Illegal shipment

Article 24.1

Where a competent authority discovers a shipment that it considers to be an illegal

shipment, it shall immediately inform the other competent authorities concerned

Start

Customs Office selects

the Passage Type

Alternate1

Customs Office of transit

fills the passage

information (Country,

Entry, Exit)

Customs Office of

exit/entry fills the

Passage information

(Passage Date)

The Passage is linked to

the Mov ement Document


End

[Transit]





Article 35.6 / Article 38.7

If a customs office of export or a customs office of exit from the Community discovers an

illegal shipment, it shall without delay inform the competent authority in the country of the

customs office which shall:

(a) without delay inform the competent authority of dispatch in the Community; and (b)

ensure detention of the waste until the competent authority of dispatch has decided

otherwise and has communicated that decision in writing to the competent authority in the

country of the customs office in which the waste is detained


If a customs office of entry into the Community discovers an illegal shipment, it shall

without delay inform the competent authority in the country of the customs office which

shall:

(a) without delay inform the competent authority of destination in the Community which

shall inform the competent authority of dispatch outside the Community; and

(b) ensure detention of the waste until the competent authority of dispatch outside the

Community has decided otherwise and has communicated that decision in writing to the

competent authority in the country of the customs office in which the waste is detained

Illegality type

Detected by

Detected on

Responsible

Measures



Scenarios


1. The Agent (Concerned CA or Customs Office) adds an illegality to a waste shipment

2. Other Concerned CAs are notified





Illegal shipment_ActivityGraphWithAction diagram

Figure 77: Illegal shipment_ActivityGraphWithAction

2.3.1.1.2.3 After shipment

REQ116 - Confirm receipt

Article 16.d (Block 18)

Written confirmation of receipt of the waste by the facility: within three days of receipt of

the waste, the facility shall provide confirmation in writing that the waste has been received.

This confirmation shall be contained in, or annexed to, the movement document.

The facility shall send signed copies of the movement document containing this

confirmation to the notifier and to the competent authorities concerned

Article 35.3.f.ii / Article 38.3.e.ii

Start

The Agent (Concerned CA

or Customs Office) adds

an illegality to a waste

shipment

Other Concerned CAs

are notified

End





Within three days of receipt of the waste for disposal, the facility shall send signed copies of

the completed movement document, except for the certificate of disposal referred to in

subpoint iii, to the notifier and the competent authorities concerned

Reception date

Accepted / Rejected

Rejection reason

Facility

Facility type

Received quantity (quantity, unit)


Disposal/Recovery operation

Date




'Approximate date of disposal/recovery' must be greater than 'Reception date'

'Approximate date of disposal/recovery' must be valid (dd/mm/yyyy)

'Reception date' must be valid (dd/mm/yyyy)

Scenarios


1. The disposal/recovery facility confirms the receipt of the shipment

2. The Shipment status is set to: RECEIVED

Alternate: 2a. Interim


Alternate. Interim

1. The Shipment status is set to: RECEIVED - INTERIM

Constraints





Constraints


Receipt of the waste no more than 3 days ago





Confirm receipt_ActivityGraphWithAction diagram

Figure 78: Confirm receipt_ActivityGraphWithAction

Start

The disposal/recov ery

facility confirms the

receipt of the shipment

Alternate1

The Shipment status is

set to: RECEIVED -

INTERIM


set to: RECEIVED


Concerned CAs are

notified

End

[Interim]





REQ117 - Confirm recovery/disposal

Article 16.e (Block 19)

Certificate for non-interim recovery or disposal by the facility: as soon as possible, but no

later than 30 days after completion of the non-interim recovery or disposal operation, and

no later than one calendar year, or a shorter period in accordance with Article 9(7),

following receipt of the waste, the facility carrying out the operation shall, under its

responsibility, certify that the non-interim recovery or disposal has been completed.

This certificate shall be contained in, or annexed to, the movement document.

The facility shall send signed copies of the movement document containing this certificate

to the notifier and to the competent authorities concerned

Article 35.3.f.iii / Article 38.3.e.iii

As soon as possible but no later than 30 days after completion of recovery, and no later

than one calendar year following the receipt of the waste the facility shall, under its

responsibility, certify that the recovery has been completed and shall send signed copies of

the movement document containing this certification to the notifier and to the competent

authorities concerned

Date




'Date' must be valid (dd/mm/yyyy)

Scenarios


1. The disposal/recovery facility confirms the disposal/removal of the waste

2. The Shipment status is set to: RECOVERED / DISPOSED

Alternate: 2a. Interim






Scenarios

Alternate. Interim

1. The Shipment status is set to: RECOVERED / DISPOSED - INTERIM

Constraints


Completion of the recovery or disposal operation no more than 30 days ago

AND

Receipt of the waste no more than 1 year ago





Confirm recovery/disposal_ActivityGraphWithAction diagram

Figure 79: Confirm recovery/disposal_ActivityGraphWithAction

Start

The disposal/recov ery

facility confirms the

disposal/remov al of the

wate

Alternate1


set to: RECOVERED /

DISPOSED - INTERIM


set to: RECOVERED /

DISPOSED


Concerned CAs are

notified

End

[Interim]





2.3.1.1.3 Information request

Article 7.2

If the notification is not properly carried out, the competent authority of dispatch shall

request information and documentation from the notifier in accordance with the second

subparagraph, point 2 of Article 4.

This shall be done within three working days of receipt of the notification.

In such cases the competent authority of dispatch shall have three working days following

the receipt of the information and/or documentation requested in which to comply with

paragraph 1

Article 8.1

Following the transmission of the notification by the competent authority of dispatch, if any

of the competent authorities concerned considers that additional information and

documentation is required as referred to in the second subparagraph, point 3 of Article 4, it

shall request such information and documentation from the notifier and inform the other

competent authorities of such request. This shall be done within three working days of

receipt of the notification. In such cases the competent authorities concerned shall have

three working days following the receipt of the information and documentation requested

in which to inform the competent authority of destination

REQ118 - Add request type

Concerned CAs must specify what information they require (requestType + requestCodes)

to be filled by the Notifier.

requestType:

Notification

Movement

Additional

requestCodes (Annex II):

Part 1 - Notification:

1. Serial number or other accepted identifier of the notification document and intended

total number of shipments.

2. Notifier's name, address, telephone number, fax number, e-mail address, registration

number and contact person.





3. If the notifier is not the producer: producer's (producers') name, address, telephone

number, fax number, e-mail address and contact person.

4. Dealer's (dealers') or broker's (brokers') name, address, telephone number, fax number, e-

mail address and contact person, where the notifier has authorised him in accordance with

point 15 of Article 2.

5. Recovery or disposal facility's name, address, telephone number, fax number, e-mail

address, registration number, contact person, technologies employed and possible status as

pre-consented in accordance with Article 14.

If the waste is destined for an interim recovery or disposal operation, similar information

regarding all facilities where subsequent interim and non-interim recovery or disposal

operations are envisaged shall be indicated.

If the recovery or disposal facility is listed in Annex I, Category 5 of Directive 96/61/EC,

evidence (e.g. a declaration certifying its existence) of a valid permit issued in accordance

with Articles 4 and 5 of that Directive shall be provided.

6. Consignee's name, address, telephone number, fax number, e-mail address, registration

number and contact person.

7. Intended carrier's (carriers') and/or their agent's (agents') name, address, telephone

number, fax number, e-mail address, registration number and contact person.

8. Country of dispatch and relevant competent authority.

9. Countries of transit and relevant competent authorities.

10. Country of destination and relevant competent authority.

11. Single notification or general notification. If general notification, period of validity

requested.

12. Date(s) envisaged for start of the shipment(s).

13. Means of transport envisaged.

14. Intended routing (point of exit from and entry into each country concerned, including

customs offices of entry into and/or exit from and/or export from the Community) and

intended route (route between points of exit and entry), including possible alternatives, also

in case of unforeseen circumstances.

15. Evidence of registration of the carrier(s) regarding waste transports (e.g. a declaration

certifying its existence).

16. Designation of the waste on the appropriate list, the source(s), description, composition

and any hazardous characteristics. In the case of waste from various sources, also a detailed

inventory of the waste.

17. Estimated maximum and minimum quantities.

18. Type of packaging envisaged.

19. Specification of the recovery or disposal operation(s) as referred to in Annexes II A and II

B to Directive 2006/12/EC.

20. If the waste is destined for recovery:

(a) the planned method of disposal for the non-recoverable fraction after recovery;

(b) the amount of recovered material in relation to non-recoverable waste;

(c) the estimated value of the recovered material;





(d) the cost of recovery and the cost of disposal of the non-recoverable fraction.

21. Evidence of insurance against liability for damage to third parties (e.g. a declaration

certifying its existence).

22. Evidence of a contract (or a declaration certifying its existence) between the notifier and

consignee for the recovery or disposal of the waste that has been concluded and is effective

at the time of the notification, as required in the second subparagraph, point 4 of Article 4

and in Article 5.

23. A copy of the contract or evidence of the contract (or a declaration certifying its

existence) between the producer, new producer or collector and the broker or dealer, in the

event that the broker or dealer acts as notifier.

24. Evidence of a financial guarantee or equivalent insurance (or a declaration certifying its

existence if the competent authority so allows) that has been established and is effective at

the time of the notification or, if the competent authority which approves the financial

guarantee or equivalent insurance so allows, at the latest when the shipment starts, as

required in the second subparagraph, point 5 of Article 4 and in Article 6.

25. Certification by the notifier that the information is complete and correct to the best of

his/her knowledge.

26. When the notifier is not the producer in accordance with point 15(a)(i) of Article 2, the

notifier shall ensure that the producer or one of the persons indicated in point 15(a)(ii) or

(iii) of Article 2, where practicable, also signs the notification document provided for in

Annex IA.

Part 2 - Movement:

1. Serial and total number of shipments.

2. Date shipment started.

3. Means of transport.

4. Carrier's (carriers') name, address, telephone number, fax number and e-mail address.

5. Routing (point of exit from and entry into each country concerned, including customs

offices of entry into and/or exit from and/or export from the Community) and route (route

between points of exit and entry), including possible alternatives, also in case of unforeseen

circumstances.

6. Quantities.

7. Type of packaging.

8. Any special precautions to be taken by the carrier(s).

9. Declaration by the notifier that all necessary consents have been received from the

competent authorities of the countries concerned. This declaration must be signed by the

notifier.

10. Appropriate signatures for each custody transfer.

Part 3 - Additional:





1. The type and duration of the authorisation pursuant to which the recovery or disposal

facility operates.

2. Copy of the permit issued in accordance with Articles 4 and 5 of Directive 96/61/EC.

3. Information concerning the measures to be taken to ensure transport safety.

4. The transport distance(s) between the notifier and the facility, including possible

alternative routes, also in case of unforeseen circumstances and, in the event of intermodal

transport, the place where the transfer will take place.

5. Information about costs of transport between the notifier and the facility.

6. Copy of the registration of the carrier(s) regarding the waste transport.

7. Chemical analysis of the composition of the waste.

8. Description of the production process of the waste.

9. Description of the treatment process of the facility which receives the waste.

10. The financial guarantee or equivalent insurance or a copy thereof.

11. Information concerning the calculation of the financial guarantee or equivalent

insurance as required in the second subparagraph, point 5 of Article 4 and in Article 6.

12. Copy of the contracts referred to in Part 1, points 22 and 23.

13. Copy of the policy of insurance against liability for damage to third parties.

14. Any other information which is pertinent to the assessment of the notification in

accordance with this Regulation and national legislation




If the Concerned CA is NOT the Dispatcher only 'Additional' (Annex II - Part 3) requestType option is available

REQ119 - Create information request

Request for Information and Documentation creation



Scenarios





Scenarios


1. A Concerned CA creates a new Request for Information and Documentation

Uses:

Add request type

2. Optionally: Add comments to the Request for Information and Documentation

3. The Information Request status is set to 'Open'


Constraints


The notification was submitted by Notifier.

Notification status: SUBMITTED

OR




Receipt of the notification no more than 3 working days ago





Create information request_ActivityGraphWithAction diagram

Figure 80: Create information request_ActivityGraphWithAction

Start

A Concerned CA creates

a new Request for

Information and

Documentation

Optionally: Add

comments to the Request

for Information and

Documentation

The Information Request

status is set to 'Open'


Concerned CAs are

notified

End





Create information request diagram

Figure 81: Create information request

REQ120 - Create information request - Export/Import

Article 35.2.a / Article 42.2.a

The competent authority of transit outside the Community shall have 60 days following the

date of transmission of its acknowledgement of receipt of the notification in which to

request additional information on the notified shipment, to provide, if the country

concerned has decided not to require prior written consent and has informed the other

Parties thereof in accordance with Article 6(4) of the Basel Convention, tacit consent or to

give a written consent with or without conditions

Article 38.5.a

The competent authority of transit to which the OECD Decision does not apply shall have

60 days following the date of transmission of its acknowledgement of receipt of the

notification in which to request additional information on the notified shipment, to provide,

if the country concerned has decided not to require prior written consent and has informed

the other Parties thereof in accordance with Article 6(4) of the Basel Convention, tacit

consent or to give a written consent with or without conditions



Create information

request

Add request type





Scenarios


1. A Concerned CA creates a new Request for Information and Documentation

Uses:

Add request type




Constraints


Receipt of the notification no more than 60 days ago




OR







Create information request - Export/Import_ActivityGraphWithAction diagram

Figure 82: Create information request - Export/Import_ActivityGraphWithAction

Start


a new Request for

Information and

Documentation

Optionally: Add


for Information and

Documentation




Concerned CAs are

notified

End





Create information request diagram

Figure 83: Create information request

REQ121 - Solve information request

The Notifier flags as 'Solved' a Request for Information and Documentation



Scenarios


1. The Notifier solves a Request for Information and Documentation


3. The Information Request status is set to 'Solved'

4. The Concerned CA that created the Request for Information and Documentation is notified

Constraints

Pre-condition - Information request

Information request status: OPEN

Create information

request - Export/Import

Add request type





Solve information request_ActivityGraphWithAction diagram

Figure 84: Solve information request_ActivityGraphWithAction

Start

The Notifier solv es a

Request for Information

and Documentation

Optionally: Add


for Information and

Documentation


status is set to 'Solv ed'

The Concerned CA that

created the Request for

Information and

Documentation is notified

End





REQ122 - Reopen information request

If the Concerned CA is NOT satisfied with the Request for Information and Documentation

response, he/she proceed to open it



Scenarios


1. The Concerned CA reopens a Request for Information and Documentation

2. Add comments to the Request for Information and Documentation



Constraints


Information request status: SOLVED

Pre-condition - Ownership

The Request for Information and Documentation was created by the Concerned CA





Reopen information request_ActivityGraphWithAction diagram

Figure 85: Reopen information request_ActivityGraphWithAction

Start

The Concerned CA

reopens a Request for

Information and

Documentation

Add comments to the

Request for Information

and Documentation




End





REQ123 - Close information request

If the Concerned CA is satisfied with the Request for Information and Documentation

response, he/she proceed to close it



Scenarios


1. The Concerned CA closes a Request for Information and Documentation

2. The Information Request status is set to 'Closed'


Constraints


Information request status: SOLVED


The Request for Information and Documentation was created by the Concerned CA





Close information request_ActivityGraphWithAction diagram

Figure 86: Close information request_ActivityGraphWithAction

2.3.1.1.4 Objections

Article 11

Objections to shipments of waste destined for disposal

1. Where a notification is submitted regarding a planned shipment of waste destined for

disposal, the competent authorities of destination and dispatch may, within 30 days

following the date of transmission of the acknowledgement of the competent authority of

Start

The Concerned CA

closes a Request for

Information and

Documentation


status is set to 'Closed'


Concerned CAs are

notified

End





destination in accordance with Article 8, raise reasoned objections based on one or more of

the following grounds and in accordance with the Treaty:

(a) that the planned shipment or disposal would not be in accordance with measures taken

to implement the principles of proximity, priority for recovery and self-sufficiency at

Community and national levels in accordance with Directive 2006/12/EC, to prohibit

generally or partially or to object systematically to shipments of waste; or

(b) that the planned shipment or disposal would not be in accordance with national

legislation relating to environmental protection, public order, public safety or health

protection concerning actions taking place in the objecting country; or

(c) that the notifier or the consignee has previously been convicted of illegal shipment or

some other illegal act in relation to environmental protection. In this case, the competent

authorities of dispatch and destination may refuse all shipments involving the person in

question in accordance with national legislation; or

(d) that the notifier or the facility has repeatedly failed to comply with Articles 15 and 16 in

connection with past shipments; or

(e) that the Member State wishes to exercise its right pursuant to Article 4(1) of the Basel

Convention to prohibit the import of hazardous waste or of waste listed in Annex II to that

Convention; or

(f) that the planned shipment or disposal conflicts with obligations resulting from

international conventions concluded by the Member State(s) concerned or the Community;

or

(g) that the planned shipment or disposal is not in accordance with Directive 2006/12/EC, in

particular Articles 5 and 7 thereof, while taking into account geographical circumstances or

the need for specialised installations for certain types of waste:

(i) in order to implement the principle of self-sufficiency at Community and national levels,

or

(ii) in cases where the specialised installation has to dispose of waste from a nearer source

and the competent authority has given priority to this waste, or

(iii) in order to ensure that shipments are in accordance with waste management plans, or

(h) that the waste will be treated in a facility which is covered by Directive 96/61/EC, but

which does not apply best available techniques as defined in Article 9(4) of that Directive in

compliance with the permit of the facility; or

(i) that the waste is mixed municipal waste collected from private households (waste entry

20 03 01); or

(j) that the waste concerned will not be treated in accordance with legally binding

environmental protection standards in relation to disposal operations established in

Community legislation (also in cases where temporary derogations are granted).

2. The competent authority(ies) of transit may, within the 30-day time limit referred to in

paragraph 1, raise reasoned objections based only on paragraph 1(b), (c), (d) and (f).

3. In the case of hazardous waste produced in a Member State of dispatch in such a small

quantity overall per year that the provision of new specialised disposal installations within

that Member State would be uneconomic, paragraph 1(a) shall not apply.





The competent authority of destination shall cooperate with the competent authority of

dispatch which considers that this paragraph and not paragraph 1(a) should apply, with a

view to resolving the issue bilaterally.

If there is no satisfactory solution, either Member State may refer the matter to the

Commission. The issue shall then be determined in accordance with the regulatory

procedure referred to in Article 59a(2).

4. If, within the 30-day time limit referred to in paragraph 1, the competent authorities

consider that the problems which gave rise to their objections have been resolved, they

shall immediately inform the notifier in writing, with copies to the consignee and to the

other competent authorities concerned.

5. If the problems giving rise to the objections have not been resolved within the 30-day

time limit referred to in paragraph 1, the notification shall cease to be valid. In cases where

the notifier still intends to carry out the shipment, a new notification shall be submitted,

unless all the competent authorities concerned and the notifier agree otherwise.

6. Measures taken by Member States in accordance with paragraph 1(a), to prohibit

generally or partially or to object systematically to shipments of waste destined for disposal,

or in accordance with paragraph 1(e), shall immediately be notified to the Commission

which shall inform the other Member States.

Article 12

Objections to shipments of waste destined for recovery

1. Where a notification is submitted regarding a planned shipment of waste destined for

recovery, the competent authorities of destination and dispatch may, within 30 days

following the date of transmission of the acknowledgement of the competent authority of

destination in accordance with Article 8, raise reasoned objections based on one or more of

the following grounds and in accordance with the Treaty:

(a) that the planned shipment or recovery would not be in accordance with Directive

2006/12/EC, in particular Articles 3, 4, 7 and 10 thereof; or

(b) that the planned shipment or recovery would not be in accordance with national



(c) that the planned shipment or recovery would not be in accordance with national

legislation in the country of dispatch relating to the recovery of waste, including where the

planned shipment would concern waste destined for recovery in a facility which has lower

treatment standards for the particular waste than those of the country of dispatch,

respecting the need to ensure the proper functioning of the internal market;

This shall not apply if:





(i) there is corresponding Community legislation, in particular related to waste, and if

requirements that are at least as stringent as those laid down in the Community legislation

have been introduced in national legislation transposing such Community legislation,

(ii) the recovery operation in the country of destination takes place under conditions that

are broadly equivalent to those prescribed in the national legislation of the country of

dispatch,

(iii) the national legislation in the country of dispatch, other than that covered by (i), has not

been notified in accordance with Directive 98/34/EC of the European Parliament and of the

Council of 22 June 1998 laying down a procedure for the provision of information in the

field of technical standards and regulations and of rules on Information Society services ( 20

), where required by that Directive, or

(d) that the notifier or the consignee has previously been convicted of illegal shipment or




(e) that the notifier or the facility has repeatedly failed to comply with Articles 15 and 16 in


(f) that the planned shipment or recovery conflicts with obligations resulting from


or

(g) that the ratio of the recoverable and non-recoverable waste, the estimated value of the

materials to be finally recovered or the cost of the recovery and the cost of the disposal of

the non-recoverable fraction do not justify the recovery, having regard to economic and/or

environmental considerations; or

(h) that the waste shipped is destined for disposal and not for recovery; or

(i) that the waste will be treated in a facility which is covered by Directive 96/61/EC, but




environmental protection standards in relation to recovery operations, or legally binding

recovery or recycling obligations established in Community legislation (also in cases where

temporary derogations are granted); or

(k) that the waste concerned will not be treated in accordance with waste management

plans drawn up pursuant to Article 7 of Directive 2006/12/EC with the purpose of ensuring

the implementation of legally binding recovery or recycling obligations established in

Community legislation.

2. The competent authority(ies) of transit may, within the 30-day time limit referred to in

paragraph 1, raise reasoned objections to the planned shipment based only on paragraph

1(b), (d), (e) and (f).

3. If, within the 30-day time limit referred to in paragraph 1, the competent authorities

consider that the problems which gave rise to their objections have been resolved, they





shall immediately inform the notifier in writing, with copies to the consignee and to the

other competent authorities concerned.

4. If the problems giving rise to the objections are not resolved within the 30-day time limit

referred to in paragraph 1, the notification shall cease to be valid. In cases where the

notifier still intends to carry out the shipment, a new notification shall be submitted, unless

all the competent authorities concerned and the notifier agree otherwise.

5. Objections raised by competent authorities in accordance with paragraph 1(c) shall be

reported by Member States to the Commission in accordance with Article 51.

6. The Member State of dispatch shall inform the Commission and the other Member States

of the national legislation on which objections raised by competent authorities in

accordance with paragraph 1(c) may be based, and shall state to which waste and waste

recovery operations those objections apply, before such legislation is invoked in order to

raise reasoned objections

REQ124 - Create objection

Objection creation



Child elements

REQ125 - Add objection type

Scenarios


1. A Concerned CA creates a new Objection

Uses:

Add objection type

2. Optionally: Add comments to the Objection

3. The Objection status is set to 'Open'


Constraints





Constraints




OR





Receipt of the notification no more than 3 days ago

OR



Pre-consent facility:


OR

Period extended: Notification acknowledged no more than 30 days ago





Create objection_ActivityGraphWithAction diagram

Figure 87: Create objection_ActivityGraphWithAction

Create objection diagram

Figure 88: Create objection

Start


a new Objection

Optionally: Add

comments to the

Objection

The Objection status is

set to 'Open'


Concerned CAs are

notified

End

Create objection

Add objection type





REQ125 - Add objection type

Concerned CAs must provide detail of their Objection (objectionType + objectionCodes)

objectionType:

Disposal

Recovery

objectionCodes:

Article 11 (Disposal)

(a) that the planned shipment or disposal would not be in accordance with measures taken

to implement the principles of proximity, priority for recovery and self-sufficiency at

Community and national levels in accordance with Directive 2006/12/EC, to prohibit

generally or partially or to object systematically to shipments of waste; or

(b) that the planned shipment or disposal would not be in accordance with national



(c) that the notifier or the consignee has previously been convicted of illegal shipment or




(d) that the notifier or the facility has repeatedly failed to comply with Articles 15 and 16 in


(e) that the Member State wishes to exercise its right pursuant to Article 4(1) of the Basel

Convention to prohibit the import of hazardous waste or of waste listed in Annex II to that

Convention; or

(f) that the planned shipment or disposal conflicts with obligations resulting from


or

(g) that the planned shipment or disposal is not in accordance with Directive 2006/12/EC, in

particular Articles 5 and 7 thereof, while taking into account geographical circumstances or

the need for specialised installations for certain types of waste:

(i) in order to implement the principle of self-sufficiency at Community and national levels,

or

(ii) in cases where the specialised installation has to dispose of waste from a nearer source

and the competent authority has given priority to this waste, or





(iii) in order to ensure that shipments are in accordance with waste management plans, or

(h) that the waste will be treated in a facility which is covered by Directive 96/61/EC, but



(i) that the waste is mixed municipal waste collected from private households (waste entry

20 03 01); or


environmental protection standards in relation to disposal operations established in

Community legislation (also in cases where temporary derogations are granted).

Article 12 (Recovery)

(a) that the planned shipment or recovery would not be in accordance with Directive

2006/12/EC, in particular Articles 3, 4, 7 and 10 thereof; or

(b) that the planned shipment or recovery would not be in accordance with national



(c) that the planned shipment or recovery would not be in accordance with national

legislation in the country of dispatch relating to the recovery of waste, including where the

planned shipment would concern waste destined for recovery in a facility which has lower

treatment standards for the particular waste than those of the country of dispatch,

respecting the need to ensure the proper functioning of the internal market;

This shall not apply if:

(i) there is corresponding Community legislation, in particular related to waste, and if

requirements that are at least as stringent as those laid down in the Community legislation

have been introduced in national legislation transposing such Community legislation,

(ii) the recovery operation in the country of destination takes place under conditions that

are broadly equivalent to those prescribed in the national legislation of the country of

dispatch,

(iii) the national legislation in the country of dispatch, other than that covered by (i), has not

been notified in accordance with Directive 98/34/EC of the European Parliament and of the

Council of 22 June 1998 laying down a procedure for the provision of information in the

field of technical standards and regulations and of rules on Information Society services ( 20

), where required by that Directive, or

(d) that the notifier or the consignee has previously been convicted of illegal shipment or




(e) that the notifier or the facility has repeatedly failed to comply with Articles 15 and 16 in






(f) that the planned shipment or recovery conflicts with obligations resulting from


or

(g) that the ratio of the recoverable and non-recoverable waste, the estimated value of the

materials to be finally recovered or the cost of the recovery and the cost of the disposal of

the non-recoverable fraction do not justify the recovery, having regard to economic and/or

environmental considerations; or

(h) that the waste shipped is destined for disposal and not for recovery; or

(i) that the waste will be treated in a facility which is covered by Directive 96/61/EC, but




environmental protection standards in relation to recovery operations, or legally binding

recovery or recycling obligations established in Community legislation (also in cases where

temporary derogations are granted); or

(k) that the waste concerned will not be treated in accordance with waste management

plans drawn up pursuant to Article 7 of Directive 2006/12/EC with the purpose of ensuring

the implementation of legally binding recovery or recycling obligations established in

Community legislation




If the Concerned CA is a Transit CA only the following options are available: Disposal (Article 11) (b), (c), (d) and

(f) / Recovery (Article 12) (b), (d), (e) and (f)

REQ126 - Solve objection

The Notifier flags as 'Solved' an Objection







Scenarios


1. The Notifier solves an Objection

2. Optionally: Add comments to the Objection

3. The Objection status is set to 'Solved'

4. The Concerned CA that created the Objection is notified

Constraints

Pre-condition - Objection

Objection status: OPEN





Solve objection_ActivityGraphWithAction diagram

Figure 89: Solve objection_ActivityGraphWithAction

Start

The Notifier solv es an

Objection

Optionally: Add

comments to the

Objection


set to 'Solv ed'

The Concerned CA that

created the Objection is

notified

End





REQ127 - Reopen objection

If the Concerned CA is NOT satisfied with the Objection response, he/she proceed to open

it



Scenarios


1. The Concerned CA reopens an Objection

2. Add comments to the Objection

3. The Objection status is set to 'Open'


Constraints


Objection status: SOLVED


The Objection was created by the Concerned CA





Reopen objection_ActivityGraphWithAction diagram

Figure 90: Reopen objection_ActivityGraphWithAction

Start

The Concerned CA

reopens an Objection

Add comments to the

Objection


set to 'Open'


End





REQ128 - Close objection

If the Concerned CA is satisfied with the Objection response, he/she proceed to close it



Scenarios


1. The Concerned CA closes an Objection

2. The Objection status is set to 'Closed'


Constraints


Objection status: SOLVED


The Objection was created by the Concerned CA





Close objection_ActivityGraphWithAction diagram

Figure 91: Close objection_ActivityGraphWithAction

2.3.1.1.5 Facility pre-consents

REQ129 - Issue pre-consent

Article 14.3

Competent authorities which decide to issue a pre-consent to a facility in accordance with

paragraphs 1 and 2 shall inform the Commission and, where appropriate, the OECD

Secretariat of:

(a) the name, registration number and address of the recovery facility;

(b) the description of technologies employed, including R-code(s);

Start

The Concerned CA

closes an Objection


set to 'Closed'


Concerned CAs are

notified

End





(c) the wastes as listed in Annexes IV and IVA or the wastes to which the decision applies;

(d) the total pre-consented quantity;

(e) the period of validity;

(f) any change in the pre-consent;

(g) any change in the information notified; and

(h) any revocation of the pre-consent.

For this purpose the form set out in Annex VI shall be used.






Scenarios


1. The CA of Destination issues a facility pre-consent

2. The facility pre-consent is stored in the system

3. The Commission and, where appropriate, the OECD Secretariat are notified





Issue pre-consent_ActivityGraphWithAction diagram

Figure 92: Issue pre-consent_ActivityGraphWithAction

REQ130 - Revoke pre-consent

Article 14.1

The competent authorities of destination which have jurisdiction over specific recovery

facilities may decide to issue pre-consents to such facilities.

Such decisions shall be limited to a specific period and may be revoked at any time

Start


issues a facility pre-

consent

The facility pre-consent

is stored in the system

The Commission and,

where appropriate, the

OECD Secretariat are

notified

End







Scenarios


1. The CA of Destination revokes a previously issued facility pre-consent

2. The facility pre-consent is updated





Revoke pre-consent_ActivityGraphWithAction diagram

Figure 93: Revoke pre-consent_ActivityGraphWithAction

REQ131 - Extend period

Article 14.5

Notwithstanding paragraph 4, the competent authority of dispatch may decide that more

time is needed in order to receive further information or documentation from the notifier.

In such cases, the competent authority shall, within seven working days, inform the notifier

in writing with copies to the other competent authorities concerned.

The total time needed shall not exceed 30 days following the date of transmission of the

acknowledgement of the competent authority of destination in accordance with Article 8



Start


rev okes a prev iously

issued facility pre-

consent


is updated

End





Scenarios


1. The CA of Dispatch decides that more time is needed in order to receive further information or documentation

from the Notifier


3. The Notifier and other Concerned CAs are notified

Extend period_ActivityGraphWithAction diagram

Figure 94: Extend period_ActivityGraphWithAction

Start

The CA of Dispatch

decides that more time is

needed in order to

receiv e further

information or

documentation from the

Notifier


is updated

The Notifier and other

Concerned CAs are

notified

End





REQ132 - Extend consent period

Article 14.2

In the case of a general notification submitted in accordance with Article 13, the period of

validity of the consent referred to in Article 9(4) and (5) may be extended to up to three

years by the competent authority of destination in agreement with the other competent

authorities concerned



Scenarios


1. The CA of destination, in agreement with the other Concerned CAs, extends the period of validity of a consent to

up to 3 years


Constraints

Pre-condition - Notification type

General notification (multiple shipments)





Extend consent period_ActivityGraphWithAction diagram

Figure 95: Extend consent period_ActivityGraphWithAction

2.3.1.1.6 Comments

REQ133 - Add comment

Competent Authorities should be able to add comments to a Notification

Comment type


Competent authority

Comment



Start

The CA of destination, in

agreement with the other

Concerned CAs, extends

the period of v alidity of a

consent to up to 3 years


is updated

End





Scenarios


1. The Competent Authority adds a new comment to a Notification

2. By default comment type 'G' (General) is selected

Alternate: 2a. Notification not transmitted

Alternate: 2b. Notification not acknowledged

3. The comment is linked to the Notification and stored in the system

Alternate. Notification not transmitted

1. Comment type 'NNT' (Notification not transmitted) is selected

Alternate. Notification not acknowledged

1. Comment type 'NNA' (Notification not acknowledged) is selected





Add comment_ActivityGraphWithAction diagram

Figure 96: Add comment_ActivityGraphWithAction

Start

The Competent Authority

adds a new comment to

a Notification

Alternate1

Comment type 'NNT'

(Notification not

transmitted) is selected

Comment type 'NNA'

(Notification not

acknowledged) is

selected

By default comment type

'G' (General) is selected

The comment is linked to



End

[Notification not transmitted] [Notification not acknowledged]





REQ134 - Update comment

Competent Authorities should be able to update their comments

Comment update date

Comment



Scenarios


1. The Competent Authority updates a comment

2. The comment is updated and stored in the system

Constraints


The comment was added by the Competent Authority





Update comment_ActivityGraphWithAction diagram

Figure 97: Update comment_ActivityGraphWithAction

REQ135 - Delete comment

Competent Authorities should be able to delete their comments



Scenarios

Start


updates a comment

The comment is updated


End





Scenarios


1. The Competent Authority deletes a comment

2. Confirmation required

3. The Competent Authority confirms the deletion

Alternate: 3a. Deletion NOT confirmed

4. The comment is flagged as deleted in the system

Alternate. Deletion NOT confirmed

1. The Competent Authority does NOT confirms the deletion

Constraints


The comment was added by the Competent Authority





Delete comment_ActivityGraphWithAction diagram

Figure 98: Delete comment_ActivityGraphWithAction

Start


deletes a comment

Confirmation required

Alternate1


does NOT confirms the

deletion

FlowEnd1


confirms the deletion

The comment is deleted

from the system

End

[Deletion NOT confirmed]





REQ136 - Approve notification

Article 7.1

Once the notification has been properly carried out, as described in the second

subparagraph, point 2 of Article 4, the competent authority of dispatch shall retain a copy

of the notification and transmit the notification to the competent authority of destination

with copies to any competent authority(ies) of transit, and shall inform the notifier of the

transmission. This shall be done within three working days of receipt of the notification

Notification No.



Scenarios


1. The CA of Dispatch adds the Notification No. to the Notification

2. The CA of Dispatch approves a Notification

3. The Notification status is set to: APPROVED


Constraints

Pre-condition - Notification submission

The notification was submitted by the Notifier.



Receipt of the notification no more than 3 working days ago





Approve notification_ActivityGraphWithAction diagram

Figure 99: Approve notification_ActivityGraphWithAction

Start

The CA of Dispatch adds

the Notification No. to the

Notification

The CA of Dispatch

approv es a Notification


set to: APPROVED


Concerned CAs are

notified

End





REQ137 - Create reasoned explanation

Article 7.4

If, within 30 days of receipt of the notification, the competent authority of dispatch has not

transmitted the notification as required under paragraph 1, it shall provide the notifier with

a reasoned explanation upon his/her request. This shall not apply when the request for

information, referred to in paragraph 2, has not been complied with.

Article 8.3

If, within 30 days of receipt of the notification, the competent authority of destination has

not acknowledged the notification as required under paragraph 2, it shall provide the

notifier, upon his/her request, with a reasoned explanation.




REQ133 - Add comment

Scenarios


1. The CA of Dispatch or Destination specifies a reasoned explanation (comment)

Uses:

Add comment

2. The Notification status is set to: EXPIRED or REJECTED


Create reasoned explanation diagram

Figure 100: Create reasoned explanation

Create reasoned

explanationAdd comment

(from Comments)





Create reasoned explanation_ActivityGraphWithAction diagram

Figure 101: Create reasoned explanation_ActivityGraphWithAction

REQ138 - Submit notification

Article 4.1

Where the notifier intends to ship waste as referred to in Article 3(1)(a) or (b), he/she shall

submit a prior written notification to and through the competent authority of dispatch and,

if submitting a general notification, comply with Article 13.

When a notification is submitted, the following requirements shall be fulfilled:

Start

The CA of Distpatch or

Destination specifies a

reasoned explanation

(comment)


set to: EXPIRED or

REJECTED


End





1. notification and movement documents:

Notification shall be effected by means of the following documents:

(a) the notification document set out in Annex IA; and

(b) the movement document set out in Annex IB.

In submitting a notification, the notifier shall fill in the notification document and, where

relevant, the movement document.

When the notifier is not the original producer in accordance with point 15(a)(i) of Article 2,

the notifier shall ensure that this producer or one of the persons indicated in point 15(a)(ii)

or (iii) of Article 2, where practicable, also signs the notification document set out in Annex

IA.

The notification document and the movement document shall be issued to the notifier by

the competent authority of dispatch;



Scenarios


1. The Notifier submits a Notification

2. The Notification is stored in the system

3. The Notification status is set to: SUBMITTED

Alternate: 3a. Compulsory data not filled

4. The CA of Dispatch is notified

Alternate. Compulsory data not filled

1. Compulsory data not filled error is returned

Constraints

Pre-condition - Notification/Movement creation

Both Notification and Movement Documents are already created





Submit notification_ActivityGraphWithAction diagram

Figure 102: Submit notification_ActivityGraphWithAction

Start

The Notifier submits a

Notification

The Notification is stored

in the system

Alternate1

Compulsory data not

filled error is returned

FlowEnd1


set to: SUBMITTED

The CA of Dispatch is

notified

End

[Compulsory data not fi l led]





2.3.1.2 Transverse


Agents should be able to search agents. Filtering the results according to the following

criteria elements:

Registration number

Country

Name

Address



Scenarios


1. The user provides an agent search criteria

2. System searches agents matching the entered criteria

3. System returns a list with the agents found

Alternate: 3a. Agent not found

Alternate. Agent not found

1. Agent not found error is returned

Constraints

Pre-condition - Registered agent

Agent must be registered





Search agent_ActivityGraphWithAction diagram

Figure 103: Search agent_ActivityGraphWithAction

Start

The user prov ides an

agent search criteria

System searches agents

matching the entered

criteria

Alternate1

Agent not found error is

returned

FlowEnd1

System returns a list

with the agents found

End

[Agent not found]





REQ140 - Search notification

Agents should be able to search notifications. Filtering the results according to the

following criteria elements:

Notification number

Export country

Import country

Facility

Status

Dates (from – until)



Scenarios


1. The user provides a notification search criteria

2. System searches notifications matching the entered criteria

3. System returns a list with the notifications found

Alternate: 3a. Notification not found

Alternate. Notification not found

1. Notification not found error is returned

Constraints







Search notification_ActivityGraphWithAction diagram

Figure 104: Search notification_ActivityGraphWithAction

Start

The user prov ides a

notification search

criteria

System searches

notifications matching

the entered criteria

Alternate1

Notification not found

error is returned

FlowEnd1


with the notifications

found

End

[Notification not found]





REQ141 - Search waste

Agents should be able to search wastes. Filtering the results according to the following

criteria elements:

Waste code

Waste type

Waste description



Scenarios


1. The user provides a waste search criteria

2. System searches wastes matching the entered criteria

3. System returns a list with the wastes found

Alternate: 3a. Waste not found

Alternate. Waste not found

1. Waste not found error is returned

Constraints







Search waste_ActivityGraphWithAction diagram

Figure 105: Search waste_ActivityGraphWithAction

2.3.2 Shared Application

Shared Application functional requirements describe the features, behaviour, business rules

and general functionality that the proposed system must support

Start

The user prov ides a

waste search criteria

System searches wastes

matching the entered

criteria

Alternate1

Waste not found error is

returned

FlowEnd1


with the wastes found

End

[Waste not found]





Shared Application diagram

Figure 106: Shared Application

2.3.2.1 System Administration

REQ142 - Agent management

System must provide a back-end for system administrators to allow agent and role

management



Child elements

REQ143 - List agents

REQ144 - Create an agent

REQ145 - Update an agent

REQ146 - Invalidate an agent

REQ147 - Delete an agent

REQ148 - Manage agent roles

System Administration

+ Agent management

Transverse

+ Print

+ Download attachment

Schedulers

+ Notification not transmitted

+ Notification not acknowledged

+ Tacit consent

+ Waste not received

ECAS user authentication





Agent management diagram

Figure 107: Agent management

REQ143 - List agents

Shows a list of all registered agents and contains actions to create, edit and update agents





REQ144 - Create an agent

Competent authorities should be able to register an agent, have the ability to assign or

remove roles to this agent and associate each agent with their corresponding certificate for

authentication/validation purposes

Agent management Update an agent

List agents

Delete an agent

Manage agent roles

Create an agent








Address (including city, country, state, street and zip code) must be valid

Contact person must be present

Email should must valid

Name must be valid

Registration number must be unique

Registration number must be valid

Telephone must be present

REQ145 - Update an agent

Competent authorities should be able to update information related to an agent



REQ146 - Invalidate an agent

Competent authorities should be able to invalidate an agent in case this agent is not

allowed to create any notification or movement document



REQ147 - Delete an agent

Competent authorities should be able to delete information related to an agent







REQ148 - Manage agent roles

Different agents participate in Waste Shipment Regulation and most of them can act with

different roles. For this reason, this project encourages multiple role per agent (i.e.: allowing

an agent to be a notifier and a waste producer at the same time)

Roles:

Producer

Licensed producer

Collector

Dealer

Broker

Disposal facility

Recovery facility

Laboratory

Carrier

Custom office



2.3.2.2 Transverse

REQ149 - Print

It should be possible to print documents (e.g Movement Document) at any time after the

creation of a notification. The documents should have the layout of the corresponding

annexes in REGULATION (EC) No 1013/2006 and should contain all information available for

the relevant fields







REQ150 - Download attachment

Users should be able to download files/attachments linked to notifications



2.3.2.3 Schedulers

REQ151 - Notification not transmitted

Article 7.4

If, within 30 days of receipt of the notification, the competent authority of dispatch has not

transmitted the notification as required under paragraph 1, it shall provide the notifier with

a reasoned explanation upon his/her request. This shall not apply when the request for

information, referred to in paragraph 2, has not been complied with



Scenarios


1. The CA of Dispatch is notified

2. The CA of Dispatch submits a reasoned explanation

Uses:

Create reasoned explanation





Constraints


The CA of Dispatch has not transmitted the notification after 30 days of receipt of the notification.

Notification not transmitted_ActivityGraphWithAction diagram

Figure 108: Notification not transmitted_ActivityGraphWithAction

REQ152 - Notification not acknowledged

Article 8.3

If, within 30 days of receipt of the notification, the competent authority of destination has

not acknowledged the notification as required under paragraph 2, it shall provide the

notifier, upon his/her request, with a reasoned explanation



Start

The CA of Dispatch is

notified

The CA of Dispatchs

submits a reasoned

explanation

End





Scenarios


1. The CA of Destination is notified

2. The CA of Destination submits a reasoned explanation

Uses:

Create reasoned explanation

Constraints

Post-condition - Time limit

The CA of Destination has not acknowledged the notification after 30 days of receipt of the notification.





Notification not acknowledged_ActivityGraphWithAction diagram

Figure 109: Notification not acknowledged_ActivityGraphWithAction

REQ153 - Tacit consent

Article 9.1

Tacit consent by the competent authority of transit may be assumed if no objection is

lodged within the said 30-day time limit. (following the date of transmission of the

acknowledgement by the competent authority of destination)



Start

The CA of Destination is

notified


submits a reasoned

explanation

End





Scenarios


1. Tacit consent is issued for the CA of Transit

Constraints


The CA of Transit has no objections after 30 days of transmission of the acknowledgement by the CA of

Destination.

Tacit consent_ActivityGraphWithAction diagram

Figure 110: Tacit consent_ActivityGraphWithAction

Start

Tacit consent is issued

for the CA of Transit

End





REQ154 - Waste not received

Article 35.3.e / Article 38.3.d

If, 42 days after the waste has left the Community, the competent authority of dispatch in

the Community has received no information from the facility about receipt of the waste, it

shall without delay inform the competent authority of destination



Scenarios


1. The CA of Dispatch and Destination are notified

Constraints


The Facility has not issued the receipt of a waste 42 days after the waste left the Community





Waste not received_ActivityGraphWithAction diagram

Figure 111: Waste not received_ActivityGraphWithAction

REQ155 - EU Login user authentication

Users must be authenticated in order to be able to use the 'Shared Application'. Since the

system is foreseen to be hosted by the Commission EU Login is recommended for

authentication purposes. It offers a trusted service to contain user credentials and provide

2nd factor authentication using SMS challenges



2.3.3 Non-Functional

These packages contain non-functional requirements specified for the new system. These

typically describe performance criteria, reliability, security and other operational parameters

Start

The CA of Dispatch and

Destination are notified

End





Non-Functional Requirements diagram

Figure 112: Non-Functional Requirements

Performance

+ Response time

+ Workload

+ Availabil ity

Scalability

+ Scalability

Security

+ SSL certificates

+ Unauthorised access

The Transport package defines constraints

and requirements affecting the transmission

of information between nodes. Networks,

relays, protocols, quality of service and even

transmission of physical media are included

here.

The Persistence package details operational

and performance criteria relating to the

storage of information, including where

relevant, redundancy, back-up, database

system, files and other persistent storage

mechanisms.

The Security package details requirements with

respect to both data access (information

security) and physical security (access to servers

and other critical hardware).

Scalability requirements define the operational

parameters with respect to system size, number

of transactions, capacity, number of users and

node distribution.

Performance requirements define parameters

such as transactions per second, network

latency, form load times and other measurable

aspects of the system that govern overall speed

and responsiveness.





2.3.3.1 Performance

Performance diagram

Figure 113: Performance

REQ157 - Availability

Availability is the proportion of time a system is in a functioning condition. The proposed

system is expected be critical due to its nature and the need to available so that Member

States are able to use it; either from 'Shared Application' or directly calling 'Central

Application' through their systems. Therefore, the need of a high mission capable rate is

expected, e.g. 'four nines' 99.99% availability


NonfunctionalRequirement Proposed 02/05/2016 02/05/2016

REQ156 - Response time

Based on best practices in usability, the response time should be between 0.1 seconds (limit

for having the user feel that the system is reacting instantaneously) and 1 second (limit for

the user's flow of thought to stay uninterrupted, event the user will notice the delay)


Response time

Workload

Av ailability







REQ163 - Workload

The centralised system should be capable of supporting a minimum of concurrent users.

Based on the countries and competent authorities involved, ABAROA consortium estimates

the minimum in 3200 concurrent requests (32 countries x 100 average users)



2.3.3.2 Scalability

Scalability diagram

Figure 114: Scalability

REQ158 - Scalability

Scalability is the capability of a system, network, or process to handle a growing amount of

work, or its potential to be enlarged in order to accommodate that growth.

ABAROA recommends making the system services available on multiple devices and a

load-balancing approach to distribute the load between them. Moreover, this will

positively contribute to the system availability. While a single server can be enlarged to a

certain degree, this approach rapidly reaches a point where the cost of scaling surpasses

the benefits. Caching techniques should also be taken into consideration

Scalability







2.3.3.3 Security

Security diagram

Figure 115: Security

REQ159 - SSL certificates

The primary reason why SSL must be implemented is to keep sensitive information sent

across the Internet encrypted so that only the intended recipient can understand it. In

particular, 2-way SSL is proposed to encrypt the communication channel, as defined before

in the 'Security Considerations' section.


SecurityRequirement Proposed 15/12/2015 30/05/2016

REQ160 - Unauthorised access

Unauthorised access to the system and its data is not allowed.

Client certificates will be required in order to use the system

SSL certificates

Unauthorised access






SecurityRequirement Proposed 02/05/2016 30/05/2016

2.3.3.4 Testability

Testability diagram

Figure 116: Testability

REQ161 - Testability

Software testability is the degree to which a software artifact (i.e. a software system,

software module, requirements- or design document) supports testing in a given test

context.

A high testability degree of the software components and requirements, will allow by

means of testing to easily find faults in the system.



2.3.3.5 Usability

Usability diagram

Figure 117: Usability

Testability

Usability





REQ162 - Usability

Usability is the ease with which a user can learn to operate, prepare inputs for, and interpret

outputs of system or component.

To accomplish a high degree of usability the system shall include:

Well-structured user manuals

Informative error messages

Help facilities

Well-formed graphical user interfaces








1 Introduction

This annex provides details about the Regulation (EC) No 1013/2006 of the European


annex defines the services of the proposed solution; defining the SOAP-based Web

Services that will allow the communication of the involved software systems to exchange

the Waste Shipment Regulation data over the Internet.

2 Service Definition

The diagram below shows the Waste Shipment Regulation WSDL component, along with

the contents of Message, Port, Bindings, and Services Packages, and XSD Schema classes.

WSDL documents are represented by UML components stereotyped as WSDL. These

components are modelled as direct child elements of the top-level WSDL namespace

package.





Overview diagram

Figure 118: Overview

«WSDL»

wasteServ ice

svWaste

«XSDschema»

Types

+ acknowledgeNotificationRequest

+ AcknowledgeNotificationRequestType

+ acknowledgeNotificationResponse

+ AcknowledgeNotificationResponseType

+ addCommentRequest

+ AddCommentRequestType

+ addCommentResponse

+ AddCommentResponseType

+ approveNotificationRequest

+ ApproveNotificationRequestType

+ approveNotificationResponse

+ ApproveNotificationResponseType

+ closeInformationRequestRequest

+ CloseInformationRequestRequestType

+ closeInformationRequestResponse

+ CloseInformationRequestResponseType

+ closeObjectionRequest

+ CloseObjectionRequestType

+ closeObjectionResponse

+ CloseObjectionResponseType

+ confirmReceiptRequest

+ ConfirmReceiptRequestType

+ confirmReceiptResponse

+ ConfirmReceiptResponseType

+ confirmRecoveryDisposalRequest

+ ConfirmRecoveryDisposalRequestType

+ confirmRecoveryDisposalResponse

+ ConfirmRecoveryDisposalResponseType

+ createConsentRequest

+ CreateConsentRequestType

+ createConsentResponse

+ CreateConsentResponseType

+ createInformationRequestRequest

+ CreateInformationRequestRequestType

+ createInformationRequestResponse

+ CreateInformationRequestResponseType

+ createMovementDocRequest

+ CreateMovementDocRequestType

+ createMovementDocResponse

+ CreateMovementDocResponseType

+ createNotificationDocRequest

+ CreateNotificationDocRequestType

+ createNotificationDocResponse

+ CreateNotificationDocResponseType

+ createObjectionRequest

+ CreateObjectionRequestType

+ createObjectionResponse

+ CreateObjectionResponseType

+ createReasonedExplanationRequest

+ CreateReasonedExplanationRequestType

+ createReasonedExplanationResponse

+ CreateReasonedExplanationResponseType

+ custodyTransferRequest

+ CustodyTransferRequestType

+ custodyTransferResponse

+ CustodyTransferResponseType

+ deleteCommentRequest

+ DeleteCommentRequestType

+ deleteCommentResponse

+ DeleteCommentResponseType

+ extendConsentPeriodRequest

+ ExtendConsentPeriodRequestType

+ extendConsentPeriodResponse

+ ExtendConsentPeriodResponseType

+ extendPeriodRequest

+ ExtendPeriodRequestType

+ extendPeriodResponse

+ ExtendPeriodResponseType

+ il legalShipmentRequest

+ Il legalShipmentRequestType

+ il legalShipmentResponse

+ Il legalShipmentResponseType

+ issuePreConsentRequest

+ IssuePreConsentRequestType

+ issuePreConsentResponse

+ IssuePreConsentResponseType

+ recordPassageRequest

+ RecordPassageRequestType

+ recordPassageResponse

+ RecordPassageResponseType

+ reopenInformationRequestRequest

+ ReopenInformationRequestRequestType

+ reopenInformationRequestResponse

+ ReopenInformationRequestResponseType

+ reopenObjectionRequest

+ ReopenObjectionRequestType

+ reopenObjectionResponse

+ ReopenObjectionResponseType

+ revokePreConsentRequest

+ RevokePreConsentRequestType

+ revokePreConsentResponse

+ RevokePreConsentResponseType

+ searchAgentRequest

+ SearchAgentRequestType

+ searchAgentResponse

+ SearchAgentResponseType

+ searchNotificationRequest

+ SearchNotificationRequestType

+ searchNotificationResponse

+ SearchNotificationResponseType

+ searchWasteRequest

+ SearchWasteRequestType

+ searchWasteResponse

+ SearchWasteResponseType

+ solveInformationRequestRequest

+ SolveInformationRequestRequestType

+ solveInformationRequestResponse

+ SolveInformationRequestResponseType

+ solveObjectionRequest

+ SolveObjectionRequestType

+ solveObjectionResponse

+ SolveObjectionResponseType

+ submitNotificationRequest

+ SubmitNotificationRequestType

+ submitNotificationResponse

+ SubmitNotificationResponseType

+ updateCommentRequest

+ UpdateCommentRequestType

+ updateCommentResponse

+ UpdateCommentResponseType

+ updateMovementDocRequest

+ UpdateMovementDocRequestType

+ updateMovementDocResponse

+ UpdateMovementDocResponseType

+ updateNotificationDocRequest

+ UpdateNotificationDocRequestType

+ updateNotificationDocResponse

+ UpdateNotificationDocResponseType

+ withdrawConsentRequest

+ WithdrawConsentRequestType

+ withdrawConsentResponse

+ WithdrawConsentResponseType

Messages

+ msgAcknowledgeNotificationRequest

+ msgAcknowledgeNotificationResponse

+ msgAddCommentRequest

+ msgAddCommentResponse

+ msgApproveNotificationRequest

+ msgApproveNotificationResponse

+ msgCloseInformationRequestRequest

+ msgCloseInformationRequestResponse

+ msgCloseObjectionRequest

+ msgCloseObjectionResponse

+ msgConfirmReceiptRequest

+ msgConfirmReceiptResponse

+ msgConfirmRecoveryDisposalRequest

+ msgConfirmRecoveryDisposalResponse

+ msgCreateConsentRequest

+ msgCreateConsentResponse

+ msgCreateInformationRequestRequest

+ msgCreateInformationRequestResponse

+ msgCreateMovementDocRequest

+ msgCreateMovementDocResponse

+ msgCreateNotificationDocRequest

+ msgCreateNotificationDocResponse

+ msgCreateObjectionRequest

+ msgCreateObjectionResponse

+ msgCreateReasonedExplanationRequest

+ msgCreateReasonedExplanationResponse

+ msgCustodyTransferRequest

+ msgCustodyTransferResponse

+ msgDeleteCommentRequest

+ msgDeleteCommentResponse

+ msgExtendConsentPeriodRequest

+ msgExtendConsentPeriodResponse

+ msgExtendPeriodRequest

+ msgExtendPeriodResponse

+ msgIllegalShipmentRequest

+ msgIllegalShipmentResponse

+ msgIssuePreConsentRequest

+ msgIssuePreConsentResponse

+ msgRecordPassageRequest

+ msgRecordPassageResponse

+ msgReopenInformationRequestRequest

+ msgReopenInformationRequestResponse

+ msgReopenObjectionRequest

+ msgReopenObjectionResponse

+ msgRevokePreConsentRequest

+ msgRevokePreConsentResponse

+ msgSearchAgentRequest

+ msgSearchAgentResponse

+ msgSearchNotificationRequest

+ msgSearchNotificationResponse

+ msgSearchWasteRequest

+ msgSearchWasteResponse

+ msgSolveInformationRequestRequest

+ msgSolveInformationRequestResponse

+ msgSolveObjectionRequest

+ msgSolveObjectionResponse

+ msgSubmitNotificationRequest

+ msgSubmitNotificationResponse

+ msgUpdateCommentRequest

+ msgUpdateCommentResponse

+ msgUpdateMovementDocRequest

+ msgUpdateMovementDocResponse

+ msgUpdateNotificationDocRequest

+ msgUpdateNotificationDocResponse

+ msgWithdrawConsentRequest

+ msgWithdrawConsentResponse

PortTypes

+ ptComments

+ ptInformationRequest

+ ptMovementDoc

+ ptNotification

+ ptNotificationDoc

+ ptObjections

+ ptPreConsents

+ ptTransverse

Bindings

+ bdComments

+ bdInformationRequest

+ bdMovementDoc

+ bdNotification

+ bdNotificationDoc

+ bdObjections

+ bdPreConsents

+ bdTransverse

Serv ices

+ svWaste





2.1 Services

This section defines the proposed WSR Service. A WSDL Service defines a formal interface

of the web service. It describes the collection of Port Types that expose a particular Binding,

having an Association to each exposed Binding. It therefore encapsulates the data

structures defined in the model; as displayed in the diagram below.

Side note: As Client Certificates are mandatory in order make use of this service, the

requestors information is not defined as a part of the request parameters. The system will

be able to correlate every request to a specific entity validating the given Client Certificate.





WasteService diagram

Figure 119: WasteService

«WSDLser...

sv Waste

«WSDLbinding»

Bindings::bdComments

+ opAddComment(msgAddCommentRequest, msgAddCommentResponse*)

+ opUpdateComment(msgUpdateCommentRequest, msgUpdateCommentResponse*)

+ opDeleteComment(msgDeleteCommentRequest, msgDeleteCommentResponse*)

«WSDLbinding»

Bindings::bdNotificationDoc

+ opCreateNotificationDoc(msgCreateNotificationDocRequest, msgCreateNotificationDocResponse*)

+ opUpdateNotificationDoc(msgUpdateNotificationDocRequest, msgUpdateNotificationDocResponse*)

+ opAcknowledgeNotification(msgAcknowledgeNotificationRequest, msgAcknowledgeNotificationResponse*)

+ opCreateConsent(msgCreateConsentRequest, msgCreateConsentResponse*)

+ opWithdrawConsent(msgWithdrawConsentRequest, msgWithdrawConsentResponse*)

«WSDLbinding»

Bindings::bdMov ementDoc

+ opCreateMovementDoc(msgCreateMovementDocRequest, msgCreateMovementDocResponse*)

+ opUpdateMovementDoc(msgUpdateMovementDocRequest, msgUpdateMovementDocResponse*)

+ opCustodyTransfer(msgCustodyTransferRequest, msgCustodyTransferResponse*)

+ opRecordPassage(msgRecordPassageRequest, msgRecordPassageResponse*)

+ opIllegalShipment(msgIllegalShipmentRequest, msgIllegalShipmentResponse*)

+ opConfirmReceipt(msgConfirmReceiptRequest, msgConfirmReceiptResponse*)

+ opConfirmRecoveryDisposal(msgConfirmRecoveryDisposalRequest, msgConfirmRecoveryDisposalResponse*)

«WSDLbinding»

Bindings::bdInformationRequest

+ opCreateInformationRequest(msgCreateInformationRequestRequest, msgCreateInformationRequestResponse*)

+ opSolveInformationRequest(msgSolveInformationRequestRequest, msgSolveInformationRequestResponse*)

+ opReopenInformationRequest(msgReopenInformationRequestRequest, msgReopenInformationRequestResponse*)

+ opCloseInformationRequest(msgCloseInformationRequestRequest, msgCloseInformationRequestResponse*)

«WSDLbinding»

Bindings::bdNotification

+ opApproveNotification(msgApproveNotificationRequest, msgApproveNotificationResponse*)

+ opCreateReasonedExplanation(msgCreateReasonedExplanationRequest, msgCreateReasonedExplanationResponse*)

+ opSubmitNotification(msgSubmitNotificationRequest, msgSubmitNotificationResponse*)

«WSDLbinding»

Bindings::bdObjections

+ opCreateObjection(msgCreateObjectionRequest, msgCreateObjectionResponse*)

+ opSolveObjection(msgSolveObjectionRequest, msgSolveObjectionResponse*)

+ opReopenObjection(msgReopenObjectionRequest, msgReopenObjectionResponse*)

+ opCloseObjection(msgCloseObjectionRequest, msgCloseObjectionResponse*)

«WSDLbinding»

Bindings::bdPreConsents

+ opIssuePreConsent(msgIssuePreConsentRequest, msgIssuePreConsentResponse*)

+ opRevokePreConsent(msgRevokePreConsentRequest, msgRevokePreConsentResponse*)

+ opExtendPeriod(msgExtendPeriodRequest, msgExtendPeriodResponse*)

+ opExtendConsentPeriod(msgExtendConsentPeriodRequest, msgExtendConsentPeriodResponse*)

«WSDLbinding»

Bindings::bdTransv erse

+ opSearchAgent(msgSearchAgentRequest, msgSearchAgentResponse*)

+ opSearchNotification(msgSearchNotificationRequest, msgSearchNotificationResponse*)

+ opSearchWaste(msgSearchWasteRequest, msgSearchWasteResponse*)

Comments

MovementDoc

Notification PreConsents NotificationDoc InformationRequestObjectionsTransverse





2.2 Bindings

A Binding specifies the protocol and data format for the operations and messages defined

for of a particular Port Type. Each «WSDLbinding» Class implements (realizes) the

operations specified by the «WSDLportType» Interface; as displayed in the diagram below.





Bindings diagram

Figure 120: Bindings

«WSDLportType»

PortTypes::ptComments




«WSDLbinding»

bdComments




tags

protocol = soap

style = document

transport = http://schemas.xmlsoap.org/soap/http

«WSDLbinding»

bdNotificationDoc






tags

protocol = soap

style = document


«WSDLportType»

PortTypes::ptNotificationDoc






«WSDLbinding»

bdMov ementDoc








tags

protocol = soap

style = document


«WSDLportType»

PortTypes::ptMov ementDoc








«WSDLbinding»

bdPreConsents





tags

protocol = soap

style = document


«WSDLportType»

PortTypes::ptPreConsents





«WSDLbinding»

bdInformationRequest





tags

protocol = soap

style = document


«WSDLbinding»

bdObjections





tags

protocol = soap

style = document


«WSDLbinding»

bdNotification




tags

protocol = soap

style = document


«WSDLbinding»

bdTransv erse




tags

protocol = soap

style = document


«WSDLportType»

PortTypes::ptInformationRequest





«WSDLportType»

PortTypes::ptObjections





«WSDLportType»

PortTypes::ptNotification




«WSDLportType»

PortTypes::ptTransv erse




WastePortTypeSOAPWastePortTypeSOAP

WastePortTypeSOAP WastePortTypeSOAP







Find below the Bindings details including the related functional requirements and the

defined operations.

2.2.1 bdComments

EXTERNAL REQUIREMENTS

Requirement. Add comment

Competent Authorities should be able to add comments to a Notification.

Comment type


Competent authority

Comment

[ Stereotype is «FunctionalRequirement». ]

Requirement. Delete comment

Competent Authorities should be able to delete their comments


Requirement. Update comment

Competent Authorities should be able to update their comments

Comment update date

Comment



Realization from «WSDLbinding» bdComments to «FunctionalRequirement» Delete comment





Realization from «WSDLbinding» bdComments to «WSDLportType» ptComments

Realization from «WSDLbinding» bdComments to «FunctionalRequirement» Update comment

Realization from «WSDLbinding» bdComments to «FunctionalRequirement» Add comment

ASSOCIATIONS

Association (direction: Unspecified) Comments

Source: Public (Interface) svWaste «WSDLservice»

Target: Public (Class) bdComments

«WSDLbinding»

OPERATIONS

opAddComment (RequestAddComment : msgAddCommentRequest , ResponseAddComment :

msgAddCommentResponse ) : Public

Adds a new comment to a notification.

Properties:

style = document

soapAction = http://ec.europa.eu/waste/services/wasteService/comments/opAddComment

opUpdateComment (RequestUpdateComment : msgUpdateCommentRequest , ResponseUpdateComment :

msgUpdateCommentResponse ) : Public

Updates a notification comment.

Properties:

style = document

soapAction = http://ec.europa.eu/waste/services/wasteService/comments/opUpdateComment





opDeleteComment (RequestDeleteComment : msgDeleteCommentRequest , ResponseDeleteComment :

msgDeleteCommentResponse ) : Public

Deletes a notification comment.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/comments/opDeleteComment

style = document

2.2.2 bdInformationRequest


Requirement. Close information request

If the Concerned CA is satisfied with the Request for Information and Documentation response, he/she proceed to

close it.


Requirement. Create information request

Request for Information and Documentation creation.


Requirement. Create information request - Export/Import

Article 35.2.a / Article 42.2.a

the competent authority of transit outside the Community shall have 60 days following the date of transmission of

its acknowledgement of receipt of the notification in which to request additional information on the notified

shipment, to provide, if the country concerned has decided not to require prior written consent and has informed

the other Parties thereof in accordance with Article 6(4) of the Basel Convention, tacit consent or to give a written

consent with or without conditions

Article 38.5.a

the competent authority of transit to which the OECD Decision does not apply shall have 60 days following the

date of transmission of its acknowledgement of receipt of the notification in which to request additional

information on the notified shipment, to provide, if the country concerned has decided not to require prior written

consent and has informed the other Parties thereof in accordance with Article 6(4) of the Basel Convention, tacit






consent or to give a written consent with or without conditions;


Requirement. Reopen information request

If the Concerned CA is NOT satisfied with the Request for Information and Documentation response, he/she

proceed to open it.


Requirement. Solve information request

The Notifier flags as 'Solved' a Request for Information and Documentation.



Realization from «WSDLbinding» bdInformationRequest to «FunctionalRequirement» Create information

request

Realization from «WSDLbinding» bdInformationRequest to «WSDLportType» ptInformationRequest

Realization from «WSDLbinding» bdInformationRequest to «FunctionalRequirement» Create information

request - Export/Import

Realization from «WSDLbinding» bdInformationRequest to «FunctionalRequirement» Close information request

Realization from «WSDLbinding» bdInformationRequest to «FunctionalRequirement» Solve information request

Realization from «WSDLbinding» bdInformationRequest to «FunctionalRequirement» Reopen information

request





ASSOCIATIONS

Association (direction: Unspecified) InformationRequest


Target: Public (Class) bdInformationRequest

«WSDLbinding»

OPERATIONS

opCreateInformationRequest (RequestCreateInformationRequest : msgCreateInformationRequestRequest ,

ResponseCreateInformationRequest : msgCreateInformationRequestResponse ) : Public

Creates a request for information and documentation.

Properties:

soapAction =

http://ec.europa.eu/waste/services/wasteService/informationRequest/opCreateInformationRequest

style = document

opSolveInformationRequest (RequestSolveInformationRequest : msgSolveInformationRequestRequest ,

ResponseSolveInformationRequest : msgSolveInformationRequestResponse ) : Public

Solves a request for information and documentation.

Properties:

soapAction =

http://ec.europa.eu/waste/services/wasteService/informationRequest/opSolveInformationRequest

style = document

opReopenInformationRequest (RequestReopenInformationRequest : msgReopenInformationRequestRequest ,

ResponseReopenInformationRequest : msgReopenInformationRequestResponse ) : Public

Reopens a request for information and documentation.

Properties:





soapAction =

http://ec.europa.eu/waste/services/wasteService/informationRequest/opReopenInformationRequest

style = document

opCloseInformationRequest (RequestCloseInformationRequest : msgCloseInformationRequestRequest ,

ResponseCloseInformationRequest : msgCloseInformationRequestResponse ) : Public

Closes a request for information and documentation.

Properties:

soapAction =

http://ec.europa.eu/waste/services/wasteService/informationRequest/opCloseInformationRequest

style = document

2.2.3 bdMovementDoc


Requirement. Confirm receipt

Article 16.d (Block 18)

Written confirmation of receipt of the waste by the facility: within three days of receipt of the waste, the facility shall

provide confirmation in writing that the waste has been received.

This confirmation shall be contained in, or annexed to, the movement document.

The facility shall send signed copies of the movement document containing this confirmation to the notifier and to

the competent authorities concerned.

Article 35.3.f.ii / Article 38.3.e.ii

within three days of receipt of the waste for disposal, the facility shall send signed copies of the completed

movement document, except for the certificate of disposal referred to in subpoint iii, to the notifier and the

competent authorities concerned

Reception date

Accepted / Rejected

Rejection reason

Facility

Facility type

Received quantity (quantity, unit)


Disposal/Recovery operation

Date[ Stereotype is «FunctionalRequirement». ]






Requirement. Confirm recovery/disposal

Article 16.e (Block 19)

Certificate for non-interim recovery or disposal by the facility: as soon as possible, but no later than 30 days after

completion of the non-interim recovery or disposal operation, and no later than one calendar year, or a shorter

period in accordance with Article 9(7), following receipt of the waste, the facility carrying out the operation shall,

under its responsibility, certify that the non-interim recovery or disposal has been completed.

This certificate shall be contained in, or annexed to, the movement document.

The facility shall send signed copies of the movement document containing this certificate to the notifier and to the

competent authorities concerned.

Article 35.3.f.iii / Article 38.3.e.iii

as soon as possible but no later than 30 days after completion of recovery, and no later than one calendar year

following the receipt of the waste the facility shall, under its responsibility, certify that the recovery has been

completed and shall send signed copies of the movement document containing this certification to the notifier and

to the competent authorities concerned

Date


Requirement. Create movement document

Any allowed agent must be able to create movement documents.


Requirement. Custody transfer


The means of transport, the date of transfer and a signature should be provided by the carrier or carrier’s

representative taking possession of the consignment.

Carrier

Means of transport

Date of transfer







Requirement. Illegal shipment

Article 24.1

Where a competent authority discovers a shipment that it considers to be an illegal shipment, it shall immediately

inform the other competent authorities concerned.


If a customs office of export or a customs office of exit from the Community discovers an illegal shipment, it shall

without delay inform the competent authority in the country of the customs office which shall:

(a) without delay inform the competent authority of dispatch in the Community; and

(b) ensure detention of the waste until the competent authority of dispatch has decided otherwise and has

communicated that decision in writing to the competent authority in the country of the customs office in which the

waste is detained.


If a customs office of entry into the Community discovers an illegal shipment, it shall without delay inform the

competent authority in the country of the customs office which shall:

(a) without delay inform the competent authority of destination in the Community which shall inform the

competent authority of dispatch outside the Community; and

(b) ensure detention of the waste until the competent authority of dispatch outside the Community has decided

otherwise and has communicated that decision in writing to the competent authority in the country of the customs

office in which the waste is detained.

Illegality type

Detected by

Detected on

Responsible

Measures


Requirement. Record passage

(Blocks 20, 21, 22)

Record passage information must be reported by customs offices at the borders of the Community.

Article 35.3.d / Article 38.3.c

as soon as the waste has left the Community, the customs office of exit from the Community shall send a stamped

copy of the movement document to the competent authority of dispatch in the Community stating that the waste

has left the Community;






Article 42.3.d / Article 44.3

having carried out the necessary customs formalities, the customs office of entry into the Community shall send a

stamped copy of the movement document to the competent authorities of destination and transit in the

Community, stating that the waste has entered the Community.

Article 47.b / Article 48.b

as soon as the waste has left the Community, the customs office of exit from the Community shall send a stamped

copy of the movement document to the competent authority(ies) of transit in the Community, stating that the

waste has left the Community.

Customs Office

Passage Type

Passage Date

Country

Entry

Exit


Requirement. Start shipment

Once the 'date of shipment' is reached the system sets the Shipment status to: SHIPPED


Requirement. Update movement document

Allowed agents may update movement document information.



Realization from «WSDLbinding» bdMovementDoc to «FunctionalRequirement» Create movement document





Realization from «WSDLbinding» bdMovementDoc to «FunctionalRequirement» Update movement document

Realization from «WSDLbinding» bdMovementDoc to «FunctionalRequirement» Confirm receipt

Realization from «WSDLbinding» bdMovementDoc to «FunctionalRequirement» Confirm recovery/disposal

Realization from «WSDLbinding» bdMovementDoc to «WSDLportType» ptMovementDoc

Realization from «WSDLbinding» bdMovementDoc to «FunctionalRequirement» Custody transfer

Realization from «WSDLbinding» bdMovementDoc to «FunctionalRequirement» Record passage

Realization from «WSDLbinding» bdMovementDoc to «FunctionalRequirement» Illegal shipment

Realization from «WSDLbinding» bdMovementDoc to «FunctionalRequirement» Start shipment

ASSOCIATIONS

Association (direction: Unspecified) MovementDoc


Target: Public (Class) bdMovementDoc

«WSDLbinding»

OPERATIONS

opCreateMovementDoc (RequestCreateMovementDoc : msgCreateMovementDocRequest ,

ResponseCreateMovementDoc : msgCreateMovementDocResponse ) : Public

Creates a new movement document.





Properties:

style = document

soapAction = http://ec.europa.eu/waste/services/wasteService/movementDoc/opCreateMovementDoc

opUpdateMovementDoc (RequestUpdateMovementDoc : msgUpdateMovementDocRequest ,

ResponseUpdateMovementDoc : msgUpdateMovementDocResponse ) : Public

Updates a movement document.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/movementDoc/opUpdateMovementDoc

style = document

opCustodyTransfer (RequestCustodyTransfer : msgCustodyTransferRequest , ResponseCustodyTransfer :

msgCustodyTransferResponse ) : Public

Notify a shipment custody transfer.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/movementDoc/opCustodyTransfer

style = document

opRecordPassage (RequestRecordPassage : msgRecordPassageRequest , ResponseRecordPassage :

msgRecordPassageResponse ) : Public

Records a passage of the consignment through the customs offices.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/movementDoc/opRecordPassage

style = document

opIllegalShipment (RequestIllegalShipment : msgIllegalShipmentRequest , ResponseIllegalShipment :

msgIllegalShipmentResponse ) : Public

Notify a shipment considered to be illegal.

Properties:





soapAction = http://ec.europa.eu/waste/services/wasteService/movementDoc/opIllegalShipment

style = document

opConfirmReceipt (RequestConfirmReceipt : msgConfirmReceiptRequest , ResponseConfirmReceipt :

msgConfirmReceiptResponse ) : Public

Confirms the receipt of the waste by the facility.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/movementDoc/opConfirmReceipt

style = document

opConfirmRecoveryDisposal (RequestConfirmRecoveryDisposal : msgConfirmRecoveryDisposalRequest ,

ResponseConfirmRecoveryDisposal : msgConfirmRecoveryDisposalResponse ) : Public

Confirms the recovery or disposal of the waste by the facility.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/movementDoc/opConfirmRecoveryDisposal

style = document

2.2.4 bdNotification


Requirement. Approve notification

Article 7.1

Once the notification has been properly carried out, as described in the second subparagraph, point 2 of Article 4,

the competent authority of dispatch shall retain a copy of the notification and transmit the notification to the

competent authority of destination with copies to any competent authority(ies) of transit, and shall inform the

notifier of the transmission. This shall be done within three working days of receipt of the notification.

Notification No.







Requirement. Create reasoned explanation

Article 7.4

If, within 30 days of receipt of the notification, the competent authority of dispatch has not transmitted the

notification as required under paragraph 1, it shall provide the notifier with a reasoned explanation upon his/her

request. This shall not apply when the request for information, referred to in paragraph 2, has not been complied

with.

Article 8.3

If, within 30 days of receipt of the notification, the competent authority of destination has not acknowledged the

notification as required under paragraph 2, it shall provide the notifier, upon his/her request, with a reasoned

explanation.


Requirement. Submit notification

Article 4.1

Where the notifier intends to ship waste as referred to in Article 3(1)(a) or (b), he/she shall submit a prior written

notification to and through the competent authority of dispatch and, if submitting a general notification, comply

with Article 13.

When a notification is submitted, the following requirements shall be fulfilled:

1. notification and movement documents:

Notification shall be effected by means of the following documents:

(a) the notification document set out in Annex IA; and

(b) the movement document set out in Annex IB.

In submitting a notification, the notifier shall fill in the notification document and, where relevant, the movement

document.

When the notifier is not the original producer in accordance with point 15(a)(i) of Article 2, the notifier shall ensure

that this producer or one of the persons indicated in point 15(a)(ii) or (iii) of Article 2, where practicable, also signs

the notification document set out in Annex IA.

The notification document and the movement document shall be issued to the notifier by the competent authority

of dispatch;



Realization from «WSDLbinding» bdNotification to «WSDLportType» ptNotification





Realization from «WSDLbinding» bdNotification to «FunctionalRequirement» Create reasoned explanation

Realization from «WSDLbinding» bdNotification to «FunctionalRequirement» Submit notification

Realization from «WSDLbinding» bdNotification to «FunctionalRequirement» Approve notification

ASSOCIATIONS

Association (direction: Unspecified) Notification


Target: Public (Class) bdNotification

«WSDLbinding»

OPERATIONS

opApproveNotification (RequestApproveNotification : msgApproveNotificationRequest ,

ResponseApproveNotification : msgApproveNotificationResponse ) : Public

Approves a notification. The notification will be transmitted to the concerned competent authorities.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/notification/opApproveNotification

style = document

opCreateReasonedExplanation (RequestCreateReasonedExplanation : msgCreateReasonedExplanationRequest ,

ResponseCreateReasonedExplanation : msgCreateReasonedExplanationResponse ) : Public

Provide the notifier with a reasoned explanation upon his/her request.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/notification/opCreateReasonedExplanation

style = document





opSubmitNotification (RequestSubmitNotification : msgSubmitNotificationRequest ,

ResponseSubmitNotification : msgSubmitNotificationResponse ) : Public

Submits a notification.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/notification/opSubmitNotification

style = document

2.2.5 bdNotificationDoc


Requirement. Acknowledge notification

Article 8.2 (Block 19)

When the competent authority of destination considers that the notification has been properly completed, as

described in the second subparagraph, point 3 of Article 4, it shall send an acknowledgement to the notifier and

copies to the other competent authorities concerned. This shall be done within three working days of receipt of the

properly completed notification.

Received on


Competent authority







Requirement. Acknowledge notification - Export/Import

Article 35.3.a

the competent authority of transit in the Community shall acknowledge the receipt of the notification to the

notifier;

Article 42.3.a

the competent authority of transit in the Community shall acknowledge the receipt of the notification to the

notifier, with copies to the competent authorities concerned;

Received on


Competent authority


Requirement. Create consent

Article 9.1 (Blocks 20, 21)

The competent authorities of destination, dispatch and transit shall have 30 days following the date of transmission

of the acknowledgement by the competent authority of destination in accordance with Article 8 in which to take

one of the following duly reasoned decisions in writing as regards the notified shipment:

(a) consent without conditions;

(b) consent with conditions in accordance with Article 10;

Given on

Valid from

Valid until

Competent authority

Has specific conditions

Specific conditions

Tacit


Requirement. Create consent - Export

Article 35.2.b






the competent authority of dispatch in the Community shall take the decision to consent to the shipment as

referred to in Article 9 only after having received written consent from the competent authority of destination and,

where appropriate, the tacit or written consent of the competent authority of transit outside the Community, and

not earlier than 61 days following the date of transmission of the acknowledgement by the competent authority of

transit. The competent authority of dispatch may take the decision before the conclusion of the 61-day time limit if

it has the written consent of the other competent authorities concerned.

Article 38.5.b

the competent authority of dispatch in the Community shall take the decision to consent to the shipment as

referred to in Article 9 only after having received tacit or written consent from that competent authority of transit to

which the OECD Decision does not apply, and not earlier than 61 days following the date of transmission of the

acknowledgement of the competent authority of transit. The competent authority of dispatch may take the

decision before the conclusion of the 61-day time limit if it has the written consent of the other competent

authorities concerned.

Given on

Valid from

Valid until

Specific conditions


Specific Conditions / Reasons

Tacit


Requirement. Create notification document

Any permitted agent must be able to create notification documents.


Requirement. Update notification document

Allowed agents may update notification document information.







Requirement. Withdraw consent

Article 9.8

The competent authorities concerned shall withdraw their consent when they have knowledge that:

(a) the composition of the waste is not as notified; or

(b) the conditions imposed on the shipment are not respected; or

(c) the waste is not recovered or disposed of in compliance with the permit of the facility that performs the said

operation; or

(d) the waste is to be, or has been, shipped, recovered or disposed of in a way that is not in accordance with the

information supplied on, or annexed to, the notification and movement documents.

Article 9.9

Any withdrawal of consent shall be transmitted by means of official notice to the notifier with copies to the other

competent authorities concerned and to the consignee.



Realization from «WSDLbinding» bdNotificationDoc to «FunctionalRequirement» Update notification document

Realization from «WSDLbinding» bdNotificationDoc to «FunctionalRequirement» Create notification document

Realization from «WSDLbinding» bdNotificationDoc to «FunctionalRequirement» Acknowledge notification -

Export/Import

Realization from «WSDLbinding» bdNotificationDoc to «FunctionalRequirement» Withdraw consent

Realization from «WSDLbinding» bdNotificationDoc to «WSDLportType» ptNotificationDoc

Realization from «WSDLbinding» bdNotificationDoc to «FunctionalRequirement» Acknowledge notification

Realization from «WSDLbinding» bdNotificationDoc to «FunctionalRequirement» Create consent - Export





Realization from «WSDLbinding» bdNotificationDoc to «FunctionalRequirement» Create consent

ASSOCIATIONS

Association (direction: Unspecified) NotificationDoc


Target: Public (Class) bdNotificationDoc

«WSDLbinding»

OPERATIONS

opCreateNotificationDoc (RequestCreateNotificationDoc : msgCreateNotificationDocRequest ,

ResponseCreateNotificationDoc : msgCreateNotificationDocResponse ) : Public

Creates a new notification.

Properties:

style = document

soapAction = http://ec.europa.eu/waste/services/wasteService/notificationDoc/opCreateNotificationDoc

opUpdateNotificationDoc (RequestUpdateNotificationDoc : msgUpdateNotificationDocRequest ,

ResponseUpdateNotificationDoc : msgUpdateNotificationDocResponse ) : Public

Updates a notification.

Properties:

style = document

soapAction = http://ec.europa.eu/waste/services/wasteService/notificationDoc/opUpdateNotificationDoc

opAcknowledgeNotification (RequestAcknowledgeNotification : msgAcknowledgeNotificationRequest ,

ResponseAcknowledgeNotification : msgAcknowledgeNotificationResponse ) : Public

Acknowledges a notification.





Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/notificationDoc/opAcknowledgeNotification

style = document

opCreateConsent (RequestCreateConsent : msgCreateConsentRequest , ResponseCreateConsent :

msgCreateConsentResponse ) : Public

Consents a notification with or without conditions.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/notificationDoc/opCreateConsent

style = document

opWithdrawConsent (RequestWithdrawConsent : msgWithdrawConsentRequest , ResponseWithdrawConsent :

msgWithdrawConsentResponse ) : Public

Withdraws a consent.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/notificationDoc/opWithdrawConsent

style = document

2.2.6 bdObjections


Requirement. Close objection

If the Concerned CA is satisfied with the Objection response, he/she proceed to close it.







Requirement. Create objection

Objection creation.


Requirement. Reopen objection

If the Concerned CA is NOT satisfied with the Objection response, he/she proceed to open it.


Requirement. Solve objection

The Notifier flags as 'Solved' an Objection.



Realization from «WSDLbinding» bdObjections to «FunctionalRequirement» Solve objection

Realization from «WSDLbinding» bdObjections to «FunctionalRequirement» Close objection

Realization from «WSDLbinding» bdObjections to «FunctionalRequirement» Create objection

Realization from «WSDLbinding» bdObjections to «WSDLportType» ptObjections

Realization from «WSDLbinding» bdObjections to «FunctionalRequirement» Reopen objection





ASSOCIATIONS

Association (direction: Unspecified) Objections


Target: Public (Class) bdObjections

«WSDLbinding»

OPERATIONS

opCreateObjection (RequestCreateObjection : msgCreateObjectionRequest , ResponseCreateObjection :

msgCreateObjectionResponse ) : Public

Creates an objection.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/objections/opCreateObjection

style = document

opSolveObjection (RequestSolveObjection : msgSolveObjectionRequest , ResponseSolveObjection :

msgSolveObjectionResponse ) : Public

Solves an objection.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/objections/opSolveObjection

style = document

opReopenObjection (RequestReopenObjection : msgReopenObjectionRequest , ResponseReopenObjection :

msgReopenObjectionResponse ) : Public

Reopens an objection.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/objections/opReopenObjection

style = document





opCloseObjection (RequestCloseObjection : msgCloseObjectionRequest , ResponseCloseObjection :

msgCloseObjectionResponse ) : Public

Closes an objection.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/objections/opCloseObjection

style = document

2.2.7 bdPreConsents


Requirement. Extend consent period

Article 14.2

In the case of a general notification submitted in accordance with Article 13, the period of validity of the consent

referred to in Article 9(4) and (5) may be extended to up to three years by the competent authority of destination in

agreement with the other competent authorities concerned.


Requirement. Extend period

Article 14.5

Notwithstanding paragraph 4, the competent authority of dispatch may decide that more time is needed in order

to receive further information or documentation from the notifier.

In such cases, the competent authority shall, within seven working days, inform the notifier in writing with copies to

the other competent authorities concerned.

The total time needed shall not exceed 30 days following the date of transmission of the acknowledgement of the

competent authority of destination in accordance with Article 8.


Requirement. Issue pre-consent

Article 14.3

Competent authorities which decide to issue a pre-consent to a facility in accordance with paragraphs 1 and 2 shall






inform the Commission and, where appropriate, the OECD Secretariat of:

(a) the name, registration number and address of the recovery facility;

(b) the description of technologies employed, including R-code(s);

(c) the wastes as listed in Annexes IV and IVA or the wastes to which the decision applies;

(d) the total pre-consented quantity;

(e) the period of validity;

(f) any change in the pre-consent;

(g) any change in the information notified; and

(h) any revocation of the pre-consent.

For this purpose the form set out in Annex VI shall be used.


Requirement. Revoke pre-consent

Article 14.1

The competent authorities of destination which have jurisdiction over specific recovery facilities may decide to issue

pre-consents to such facilities.

Such decisions shall be limited to a specific period and may be revoked at any time.



Realization from «WSDLbinding» bdPreConsents to «FunctionalRequirement» Issue pre-consent

Realization from «WSDLbinding» bdPreConsents to «FunctionalRequirement» Extend consent period

Realization from «WSDLbinding» bdPreConsents to «FunctionalRequirement» Extend period

Realization from «WSDLbinding» bdPreConsents to «FunctionalRequirement» Revoke pre-consent

Realization from «WSDLbinding» bdPreConsents to «WSDLportType» ptPreConsents





ASSOCIATIONS

Association (direction: Unspecified) PreConsents


Target: Public (Class) bdPreConsents

«WSDLbinding»

OPERATIONS

opIssuePreConsent (RequestIssuePreConsent : msgIssuePreConsentRequest , ResponseIssuePreConsent :

msgIssuePreConsentResponse ) : Public

Article 14.3

Issues a pre-consent to a facility.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/preConsents/opIssuePreConsent

style = document

opRevokePreConsent (RequestRevokePreConsent : msgRevokePreConsentRequest ,

ResponseRevokePreConsent : msgRevokePreConsentResponse ) : Public

Article 14.1

Revokes a pre-consent to a facility.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/preConsents/opRevokePreConsent

style = document

opExtendPeriod (RequestExtendPeriod : msgExtendPeriodRequest , ResponseExtendPeriod :

msgExtendPeriodResponse ) : Public

Article 14.5

Extends the time needed in order to receive further information or documentation from the notifier.

Properties:





soapAction = http://ec.europa.eu/waste/services/wasteService/preConsents/opExtendPeriod

style = document

opExtendConsentPeriod (RequestExtendConsentPeriod : msgExtendConsentPeriodRequest ,

ResponseExtendConsentPeriod : msgExtendConsentPeriodResponse ) : Public

Article 14.2

Extends the period of validity of a consent.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/preConsents/opExtendConsentPeriod

style = document

2.2.8 bdTransverse


Requirement. Search agent

Agents should be able to search agents. Filtering the results according to the following criteria elements:

Registration number

Country

Name

Address







Requirement. Search notification

Agents should be able to search notifications. Filtering the results according to the following criteria elements:

Notification number

Export country

Import country

Facility

Status

Dates (from – until)


Requirement. Search waste

Agents should be able to search wastes. Filtering the results according to the following criteria elements:

Waste code

Waste type

Waste description



Realization from «WSDLbinding» bdTransverse to «WSDLportType» ptTransverse

Realization from «WSDLbinding» bdTransverse to «FunctionalRequirement» Search notification

Realization from «WSDLbinding» bdTransverse to «FunctionalRequirement» Search agent

Realization from «WSDLbinding» bdTransverse to «FunctionalRequirement» Search waste





ASSOCIATIONS

Association (direction: Unspecified) Transverse


Target: Public (Class) bdTransverse

«WSDLbinding»

OPERATIONS

opSearchAgent (RequestSearchAgent : msgSearchAgentRequest , ResponseSearchAgent :

msgSearchAgentResponse ) : Public

Searches agents filtering the results according to the given criteria.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/transverse/opSearchAgent

style = document

opSearchNotification (RequestSearchNotification : msgSearchNotificationRequest , ResponseSearchNotification

: msgSearchNotificationResponse ) : Public

Searches notifications filtering the results according to the given criteria.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/transverse/opSearchNotification

style = document

opSearchWaste (RequestSearchWaste : msgSearchWasteRequest , ResponseSearchWaste :

msgSearchWasteResponse ) : Public

Searches wastes filtering the results according to the given criteria.

Properties:

soapAction = http://ec.europa.eu/waste/services/wasteService/transverse/opSearchWaste

style = document





2.3 PortTypes

These describe the operations that can be performed and the messages involved. WSDL

Port Types are the essential core of the web service, defining the interfaces of the service.

Each Port Type consists of a set of Port Type Operations, each of which identifies an

exchange of Messages (data input to and output from the interface as that operation); as

displayed in the diagram below.





PortTypes diagram

Figure 121: PortTypes

«WSDLportType»

ptComments




«WSDLportType»

ptNotificationDoc






«WSDLportType»

ptMov ementDoc








«WSDLportType»

ptPreConsents





«WSDLportType»

ptInformationRequest





«WSDLportType»

ptObjections





«WSDLportType»

ptNotification




«WSDLportType»

ptTransv erse








2.4 Messages

These define the data elements for each operation. WSDL Messages identify the data being

communicated by a web service. Each Message element contains one or more Message

Parts, which are attributes that each identify an XSD data type being communicated. The

diagram below depicts the defined messages for the Waste Shipment Regulation.





Messages diagram

Figure 122: Messages

Notification Management

Movement Document

After Shipment

During Shipment

Before Shipment

Confirm Recovery/DisposalConfirm Receipt

Report Illegal ShipmentRecord PassageCustody Transfer

Update Movement DocumentCreate Movement Document

Notification Document

Consents

Acknowledge Notification

Create Notification Document Update Notification Document

Create Consent Withdraw Consent

Comments

Delete CommentUpdate CommentAdd Comment

Objections

Close ObjectionReopen Objection

Solve ObjectionCreate Objection

Information Request

Close Information RequestReopen Information Request

Solve Information RequestCreate Information Request

Facility Pre-Consents

Extend Consent PeriodExtend Period

Revoke Pre-ConsentIssue Pre-Consent

Submit NotificationCreate Reasoned ExplanationApprove Notification

Transverse

Search WasteSearch NotificationSearch Agent

«WSDLmessage»

msgCreateNotificationDocRequest

+ CreateNotificationDocRequest: createNotificationDocRequest

«WSDLmessage»

msgCreateNotificationDocResponse

+ CreateNotificationDocResponse: createNotificationDocResponse

«WSDLmessage»

msgAddCommentRequest

+ AddCommentRequest: addCommentRequest

«WSDLmessage»

msgAddCommentResponse

+ AddCommentResponse: addCommentResponse

«WSDLmessage»

msgSearchAgentRequest

+ SearchAgentRequest: searchAgentRequest

«WSDLmessage»

msgSearchAgentResponse

+ SearchAgentResponse: searchAgentResponse

«WSDLmessage»

msgSearchNotificationRequest

+ SearchNotificationRequest: searchNotificationRequest

«WSDLmessage»

msgSearchNotificationResponse

+ SearchNotificationResponse: searchNotificationResponse

«WSDLmessage»

msgSearchWasteRequest

+ SearchWasteRequest: searchWasteRequest

«WSDLmessage»

msgSearchWasteResponse

+ SearchWasteResponse: searchWasteResponse

«WSDLmessage»

msgApprov eNotificationRequest

+ ApproveNotificationRequest: approveNotificationRequest

«WSDLmessage»

msgApprov eNotificationResponse

+ ApproveNotificationResponse: approveNotificationResponse

«WSDLmessage»

msgCreateReasonedExplanationRequest

+ CreateReasonedExplanationRequest: createReasonedExplanationRequest

«WSDLmessage»

msgCreateReasonedExplanationResponse

+ CreateReasonedExplanationResponse: createReasonedExplanationResponse

«WSDLmessage»

msgSubmitNotificationRequest

+ SubmitNotificationRequest: submitNotificationRequest

«WSDLmessage»

msgSubmitNotificationResponse

+ SubmitNotificationResponse: submitNotificationResponse

«WSDLmessage»

msgIssuePreConsentRequest

+ IssuePreConsentRequest: issuePreConsentRequest

«WSDLmessage»

msgIssuePreConsentResponse

+ IssuePreConsentResponse: issuePreConsentResponse

«WSDLmessage»

msgExtendPeriodRequest

+ ExtendPeriodRequest: extendPeriodRequest

«WSDLmessage»

msgExtendPeriodResponse

+ ExtendPeriodResponse: extendPeriodResponse

«WSDLmessage»

msgRev okePreConsentRequest

+ RevokePreConsentRequest: revokePreConsentRequest

«WSDLmessage»

msgRev okePreConsentResponse

+ RevokePreConsentResponse: revokePreConsentResponse

«WSDLmessage»

msgExtendConsentPeriodRequest

+ ExtendConsentPeriodRequest: extendConsentPeriodRequest

«WSDLmessage»

msgExtendConsentPeriodResponse

+ ExtendConsentPeriodResponse: extendConsentPeriodResponse

«WSDLmessage»

msgCreateInformationRequestRequest

+ CreateInformationRequestRequest: createInformationRequestRequest

«WSDLmessage»

msgCreateInformationRequestResponse

+ CreateInformationRequestResponse: createInformationRequestResponse

«WSDLmessage»

msgSolv eInformationRequestRequest

+ SolveInformationRequestRequest: solveInformationRequestRequest

«WSDLmessage»

msgSolv eInformationRequestResponse

+ SolveInformationRequestResponse: solveInformationRequestResponse

«WSDLmessage»

msgReopenInformationRequestRequest

+ ReopenInformationRequestRequest: reopenInformationRequestRequest

«WSDLmessage»

msgReopenInformationRequestResponse

+ ReopenInformationRequestResponse: reopenInformationRequestResponse

«WSDLmessage»

msgCloseInformationRequestRequest

+ CloseInformationRequestRequest: closeInformationRequestRequest

«WSDLmessage»

msgCloseInformationRequestResponse

+ CloseInformationRequestResponse: closeInformationRequestResponse

«WSDLmessage»

msgCreateObjectionRequest

+ CreateObjectionRequest: createObjectionRequest

«WSDLmessage»

msgCreateObjectionResponse

+ CreateObjectionResponse: createObjectionResponse

«WSDLmessage»

msgSolv eObjectionRequest

+ SolveObjectionRequest: solveObjectionRequest

«WSDLmessage»

msgSolv eObjectionResponse

+ SolveObjectionResponse: solveObjectionResponse

«WSDLmessage»

msgReopenObjectionRequest

+ ReopenObjectionRequest: reopenObjectionRequest

«WSDLmessage»

msgReopenObjectionResponse

+ ReopenObjectionResponse: reopenObjectionResponse

«WSDLmessage»

msgCloseObjectionRequest

+ CloseObjectionRequest: closeObjectionRequest

«WSDLmessage»

msgCloseObjectionResponse

+ CloseObjectionResponse: closeObjectionResponse

«WSDLmessage»

msgUpdateCommentRequest

+ UpdateCommentRequest: updateCommentRequest

«WSDLmessage»

msgUpdateCommentResponse

+ UpdateCommentResponse: updateCommentResponse

«WSDLmessage»

msgDeleteCommentRequest

+ DeleteCommentRequest: deleteCommentRequest

«WSDLmessage»

msgDeleteCommentResponse

+ DeleteCommentResponse: deleteCommentResponse

«WSDLmessage»

msgUpdateNotificationDocRequest

+ UpdateNotificationDocRequest: updateNotificationDocRequest

«WSDLmessage»

msgUpdateNotificationDocResponse

+ UpdateNotificationDocResponse: updateNotificationDocResponse

«WSDLmessage»

msgAcknowledgeNotificationRequest

+ AcknowledgeNotificationRequest: acknowledgeNotificationRequest

«WSDLmessage»

msgAcknowledgeNotificationResponse

+ AcknowledgeNotificationResponse: acknowledgeNotificationResponse

«WSDLmessage»

msgCreateConsentRequest

+ CreateConsentRequest: createConsentRequest

«WSDLmessage»

msgCreateConsentResponse

+ CreateConsentResponse: createConsentResponse

«WSDLmessage»

msgWithdrawConsentRequest

+ WithdrawConsentRequest: withdrawConsentRequest

«WSDLmessage»

msgWithdrawConsentResponse

+ WithdrawConsentResponse: withdrawConsentResponse

«WSDLmessage»

msgConfirmReceiptRequest

+ ConfirmReceiptRequest: confirmReceiptRequest

«WSDLmessage»

msgConfirmReceiptResponse

+ ConfirmReceiptResponse: confirmReceiptResponse

«WSDLmessage»

msgConfirmRecov eryDisposalRequest

+ ConfirmRecoveryDisposalRequest: confirmRecoveryDisposalRequest

«WSDLmessage»

msgConfirmRecov eryDisposalResponse

+ ConfirmRecoveryDisposalResponse: confirmRecoveryDisposalResponse

«WSDLmessage»

msgCustodyTransferRequest

+ CustodyTransferRequest: custodyTransferRequest

«WSDLmessage»

msgCustodyTransferResponse

+ CustodyTransferResponse: custodyTransferResponse

«WSDLmessage»

msgRecordPassageRequest

+ RecordPassageRequest: recordPassageRequest

«WSDLmessage»

msgRecordPassageResponse

+ RecordPassageResponse: recordPassageResponse

«WSDLmessage»

msgIllegalShipmentRequest

+ Il legalShipmentRequest: i l legalShipmentRequest

«WSDLmessage»

msgIllegalShipmentResponse

+ Il legalShipmentResponse: i l legalShipmentResponse

«WSDLmessage»

msgCreateMov ementDocRequest

+ CreateMovementDocRequest: createMovementDocRequest

«WSDLmessage»

msgCreateMov ementDocResponse

+ CreateMovementDocResponse: createMovementDocResponse

«WSDLmessage»

msgUpdateMov ementDocRequest

+ UpdateMovementDocRequest: updateMovementDocRequest

«WSDLmessage»

msgUpdateMov ementDocResponse

+ UpdateMovementDocResponse: updateMovementDocResponse





Find below the Messages details describing their attributes (XSD data types).

2.4.1 msgAcknowledgeNotificationRequest

ATTRIBUTES

AcknowledgeNotificationRequest : acknowledgeNotificationRequest Public

2.4.2 msgAcknowledgeNotificationResponse

ATTRIBUTES

AcknowledgeNotificationResponse : acknowledgeNotificationResponse Public

2.4.3 msgAddCommentRequest

ATTRIBUTES

AddCommentRequest : addCommentRequest Public

2.4.4 msgAddCommentResponse

ATTRIBUTES

AddCommentResponse : addCommentResponse Public

2.4.5 msgApproveNotificationRequest

ATTRIBUTES

ApproveNotificationRequest : approveNotificationRequest Public





2.4.6 msgApproveNotificationResponse

ATTRIBUTES

ApproveNotificationResponse : approveNotificationResponse Public

2.4.7 msgCloseInformationRequestRequest

ATTRIBUTES

CloseInformationRequestRequest : closeInformationRequestRequest Public

2.4.8 msgCloseInformationRequestResponse

ATTRIBUTES

CloseInformationRequestResponse : closeInformationRequestResponse Public

2.4.9 msgCloseObjectionRequest

ATTRIBUTES

CloseObjectionRequest : closeObjectionRequest Public

2.4.10 msgCloseObjectionResponse

ATTRIBUTES

CloseObjectionResponse : closeObjectionResponse Public





2.4.11 msgConfirmReceiptRequest

ATTRIBUTES

ConfirmReceiptRequest : confirmReceiptRequest Public

2.4.12 msgConfirmReceiptResponse

ATTRIBUTES

ConfirmReceiptResponse : confirmReceiptResponse Public

2.4.13 msgConfirmRecoveryDisposalRequest

ATTRIBUTES

ConfirmRecoveryDisposalRequest : confirmRecoveryDisposalRequest Public

2.4.14 msgConfirmRecoveryDisposalResponse

ATTRIBUTES

ConfirmRecoveryDisposalResponse : confirmRecoveryDisposalResponse Public

2.4.15 msgCreateConsentRequest

ATTRIBUTES

CreateConsentRequest : createConsentRequest Public





2.4.16 msgCreateConsentResponse

ATTRIBUTES

CreateConsentResponse : createConsentResponse Public

2.4.17 msgCreateInformationRequestRequest

ATTRIBUTES

CreateInformationRequestRequest : createInformationRequestRequest Public

2.4.18 msgCreateInformationRequestResponse

ATTRIBUTES

CreateInformationRequestResponse : createInformationRequestResponse Public

2.4.19 msgCreateMovementDocRequest

ATTRIBUTES

CreateMovementDocRequest : createMovementDocRequest Public

2.4.20 msgCreateMovementDocResponse

ATTRIBUTES

CreateMovementDocResponse : createMovementDocResponse Public





2.4.21 msgCreateNotificationDocRequest

ATTRIBUTES

CreateNotificationDocRequest : createNotificationDocRequest Public

2.4.22 msgCreateNotificationDocResponse

ATTRIBUTES

CreateNotificationDocResponse : createNotificationDocResponse Public

2.4.23 msgCreateObjectionRequest

ATTRIBUTES

CreateObjectionRequest : createObjectionRequest Public

2.4.24 msgCreateObjectionResponse

ATTRIBUTES

CreateObjectionResponse : createObjectionResponse Public

2.4.25 msgCreateReasonedExplanationRequest

ATTRIBUTES

CreateReasonedExplanationRequest : createReasonedExplanationRequest Public





2.4.26 msgCreateReasonedExplanationResponse

ATTRIBUTES

CreateReasonedExplanationResponse : createReasonedExplanationResponse Public

2.4.27 msgCustodyTransferRequest

ATTRIBUTES

CustodyTransferRequest : custodyTransferRequest Public

2.4.28 msgCustodyTransferResponse

ATTRIBUTES

CustodyTransferResponse : custodyTransferResponse Public

2.4.29 msgDeleteCommentRequest

ATTRIBUTES

DeleteCommentRequest : deleteCommentRequest Public

2.4.30 msgDeleteCommentResponse

ATTRIBUTES

DeleteCommentResponse : deleteCommentResponse Public





2.4.31 msgExtendConsentPeriodRequest

ATTRIBUTES

ExtendConsentPeriodRequest : extendConsentPeriodRequest Public

2.4.32 msgExtendConsentPeriodResponse

ATTRIBUTES

ExtendConsentPeriodResponse : extendConsentPeriodResponse Public

2.4.33 msgExtendPeriodRequest

ATTRIBUTES

ExtendPeriodRequest : extendPeriodRequest Public

2.4.34 msgExtendPeriodResponse

ATTRIBUTES

ExtendPeriodResponse : extendPeriodResponse Public

2.4.35 msgIllegalShipmentRequest

ATTRIBUTES

IllegalShipmentRequest : illegalShipmentRequest Public





2.4.36 msgIllegalShipmentResponse

ATTRIBUTES

IllegalShipmentResponse : illegalShipmentResponse Public

2.4.37 msgIssuePreConsentRequest

ATTRIBUTES

IssuePreConsentRequest : issuePreConsentRequest Public

2.4.38 msgIssuePreConsentResponse

ATTRIBUTES

IssuePreConsentResponse : issuePreConsentResponse Public

2.4.39 msgRecordPassageRequest

ATTRIBUTES

RecordPassageRequest : recordPassageRequest Public

2.4.40 msgRecordPassageResponse

ATTRIBUTES

RecordPassageResponse : recordPassageResponse Public





2.4.41 msgReopenInformationRequestRequest

ATTRIBUTES

ReopenInformationRequestRequest : reopenInformationRequestRequest Public

2.4.42 msgReopenInformationRequestResponse

ATTRIBUTES

ReopenInformationRequestResponse : reopenInformationRequestResponse Public

2.4.43 msgReopenObjectionRequest

ATTRIBUTES

ReopenObjectionRequest : reopenObjectionRequest Public

2.4.44 msgReopenObjectionResponse

ATTRIBUTES

ReopenObjectionResponse : reopenObjectionResponse Public

2.4.45 msgRevokePreConsentRequest

ATTRIBUTES

RevokePreConsentRequest : revokePreConsentRequest Public





2.4.46 msgRevokePreConsentResponse

ATTRIBUTES

RevokePreConsentResponse : revokePreConsentResponse Public

2.4.47 msgSearchAgentRequest

ATTRIBUTES

SearchAgentRequest : searchAgentRequest Public

2.4.48 msgSearchAgentResponse

ATTRIBUTES

SearchAgentResponse : searchAgentResponse Public

2.4.49 msgSearchNotificationRequest

ATTRIBUTES

SearchNotificationRequest : searchNotificationRequest Public

2.4.50 msgSearchNotificationResponse

ATTRIBUTES

SearchNotificationResponse : searchNotificationResponse Public





2.4.51 msgSearchWasteRequest

ATTRIBUTES

SearchWasteRequest : searchWasteRequest Public

2.4.52 msgSearchWasteResponse

ATTRIBUTES

SearchWasteResponse : searchWasteResponse Public

2.4.53 msgSolveInformationRequestRequest

ATTRIBUTES

SolveInformationRequestRequest : solveInformationRequestRequest Public

2.4.54 msgSolveInformationRequestResponse

ATTRIBUTES

SolveInformationRequestResponse : solveInformationRequestResponse Public

2.4.55 msgSolveObjectionRequest

ATTRIBUTES

SolveObjectionRequest : solveObjectionRequest Public





2.4.56 msgSolveObjectionResponse

ATTRIBUTES

SolveObjectionResponse : solveObjectionResponse Public

2.4.57 msgSubmitNotificationRequest

ATTRIBUTES

SubmitNotificationRequest : submitNotificationRequest Public

2.4.58 msgSubmitNotificationResponse

ATTRIBUTES

SubmitNotificationResponse : submitNotificationResponse Public

2.4.59 msgUpdateCommentRequest

ATTRIBUTES

UpdateCommentRequest : updateCommentRequest Public

2.4.60 msgUpdateCommentResponse

ATTRIBUTES

UpdateCommentResponse : updateCommentResponse Public





2.4.61 msgUpdateMovementDocRequest

ATTRIBUTES

UpdateMovementDocRequest : updateMovementDocRequest Public

2.4.62 msgUpdateMovementDocResponse

ATTRIBUTES

UpdateMovementDocResponse : updateMovementDocResponse Public

2.4.63 msgUpdateNotificationDocRequest

ATTRIBUTES

UpdateNotificationDocRequest : updateNotificationDocRequest Public

2.4.64 msgUpdateNotificationDocResponse

ATTRIBUTES

UpdateNotificationDocResponse : updateNotificationDocResponse Public

2.4.65 msgWithdrawConsentRequest

ATTRIBUTES

WithdrawConsentRequest : withdrawConsentRequest Public





2.4.66 msgWithdrawConsentResponse

ATTRIBUTES

WithdrawConsentResponse : withdrawConsentResponse Public

2.5 Types

These define the (XML Schema) data types used by the web service. These are the XSD data

types used by the web service and communicated by WSDL Messages; as displayed in the

diagram below.





Types diagram

Figure 123: Types

Notification Management

Notification Document

Update Notification DocumentCreate Notification Document

ConsentsWithdraw ConsentCreate Consent

Acknowledge Notification

Movement Document

Before Shipment

Comments

«XSDcomplexType»

CreateConsentRequestType

«XSDelement»


+ consent: WrittenConsent

«XSDcomplexType»

CreateConsentResponseType

«XSDelement»


«XSDtopLevelElement»

createConsentRequest


createConsentResponse

«XSDcomplexType»

WithdrawConsentRequestType

«XSDelement»


«XSDcomplexType»

WithdrawConsentResponseType

«XSDelement»



withdrawConsentRequest


withdrawConsentResponse

«XSDcomplexType»

UpdateNotificationDocResponseType

«XSDelement»

+ notification: Notification


updateNotificationDocRequest

«XSDcomplexType»

UpdateNotificationDocRequestType

«XSDelement»


«XSDcomplexType»

AcknowledgeNotificationResponseType

«XSDelement»

+ acknowledgement: Acknowledgement


updateNotificationDocResponse

«XSDcomplexType»

AcknowledgeNotificationRequestType

«XSDelement»



acknowledgeNotificationRequest


acknowledgeNotificationResponse

Add Comment Update Comment Delete Comment

«XSDcomplexType»

UpdateCommentRequestType

«XSDelement»

+ comment: Comment


updateCommentRequest

«XSDcomplexType»

UpdateCommentResponseType

«XSDelement»

+ comment: Comment


updateCommentResponse

«XSDcomplexType»

DeleteCommentRequestType

«XSDelement»

+ comment: Comment«XSDcomplexType»

DeleteCommentResponseType

«XSDelement»

+ comment: Comment


deleteCommentRequest


deleteCommentResponse

Create Movement Document

«XSDcomplexType»

CreateMov ementDocRequestType

«XSDelement»


+ movementDocument: MovementDocument

«XSDcomplexType»

CreateMov ementDocResponseType

«XSDelement»



createMov ementDocRequest


createMov ementDocResponse

Update Movement Document

«XSDcomplexType»

UpdateMov ementDocRequestType

«XSDelement»


«XSDcomplexType»

UpdateMov ementDocResponseType

«XSDelement»



updateMov ementDocRequest


updateMov ementDocResponse

During Shipment

After Shipment

Custody Transfer Record Passage Report Illegal Shipment

«XSDcomplexType»

CustodyTransferRequestType

«XSDelement»


+ finalCarrier: FinalCarrier

«XSDcomplexType»

CustodyTransferResponseType

«XSDelement»

+ finalCarrier: FinalCarrier


custodyTransferRequest


custodyTransferResponse

«XSDcomplexType»

RecordPassageRequestType

«XSDelement»


+ passage: Passage

«XSDcomplexType»

RecordPassageResponseType

«XSDelement»

+ passage: Passage


recordPassageRequest


recordPassageResponse

«XSDcomplexType»

IllegalShipmentRequestType

«XSDelement»


+ il legality: Il legality

«XSDcomplexType»

IllegalShipmentResponseType

«XSDelement»

+ il legality: Il legality


illegalShipmentRequest


illegalShipmentResponse

Confirm Receipt Confirm Recovery/Disposal

«XSDcomplexType»

ConfirmReceiptRequestType

«XSDelement»


+ receipt: Receipt

«XSDcomplexType»

ConfirmReceiptResponseType

«XSDelement»

+ receipt: Receipt


confirmReceiptRequest


confirmReceiptResponse

«XSDcomplexType»

ConfirmRecov eryDisposalRequestType

«XSDelement»

+ receipt: Receipt

«XSDcomplexType»

ConfirmRecov eryDisposalResponseType

«XSDelement»

+ receipt: Receipt


confirmRecov eryDisposalRequest


confirmRecov eryDisposalResponse

Information Request

Create Information Request Solve Information Request

Reopen Information Request Close Information Request

Objections

Create Objection Solve Objection

Reopen Objection Close Objection

«XSDcomplexType»

CreateInformationRequestRequestType

«XSDelement»


+ informationRequest: InformationRequest


createInformationRequestRequest

«XSDcomplexType»

CreateInformationRequestResponseType

«XSDelement»



createInformationRequestResponse

«XSDcomplexType»

Solv eInformationRequestRequestType

«XSDelement»



solv eInformationRequestRequest

«XSDcomplexType»

Solv eInformationRequestResponseType

«XSDelement»



solv eInformationRequestResponse

«XSDcomplexType»

ReopenInformationRequestRequestType

«XSDelement»



reopenInformationRequestRequest

«XSDcomplexType»

ReopenInformationRequestResponseType

«XSDelement»



reopenInformationRequestResponse

«XSDcomplexType»

CloseInformationRequestRequestType

«XSDelement»



closeInformationRequestRequest

«XSDcomplexType»

CloseInformationRequestResponseType

«XSDelement»



closeInformationRequestResponse

Facility Pre-Consents

Issue Pre-Consent Revoke Pre-Consent

Extend Period Extend Consent Period

«XSDcomplexType»

CreateObjectionRequestType

«XSDelement»


+ objection: Objection


createObjectionRequest

«XSDcomplexType»

CreateObjectionResponseType

«XSDelement»



createObjectionResponse

«XSDcomplexType»

Solv eObjectionRequestType

«XSDelement»



solv eObjectionRequest

«XSDcomplexType»

Solv eObjectionResponseType

«XSDelement»



solv eObjectionResponse

«XSDcomplexType»

ReopenObjectionRequestType

«XSDelement»



reopenObjectionRequest

«XSDcomplexType»

ReopenObjectionResponseType

«XSDelement»



reopenObjectionResponse

«XSDcomplexType»

CloseObjectionRequestType

«XSDelement»



closeObjectionRequest

«XSDcomplexType»

CloseObjectionResponseType

«XSDelement»



closeObjectionResponse

«XSDcomplexType»

IssuePreConsentRequestType

«XSDelement»

+ facil ityID: int

+ facil ityPreconsent: FacilityPreconsent


issuePreConsentRequest

«XSDcomplexType»

IssuePreConsentResponseType

«XSDelement»



issuePreConsentResponse

«XSDcomplexType»

Rev okePreConsentRequestType

«XSDelement»



rev okePreConsentRequest

«XSDcomplexType»

Rev okePreConsentResponseType

«XSDelement»



rev okePreConsentResponse

«XSDcomplexType»

ExtendPeriodRequestType

«XSDelement»



extendPeriodRequest

«XSDcomplexType»

ExtendPeriodResponseType

«XSDelement»



extendPeriodResponse

«XSDcomplexType»

ExtendConsentPeriodRequestType

«XSDelement»



extendConsentPeriodRequest

«XSDcomplexType»

ExtendConsentPeriodResponseType

«XSDelement»



extendConsentPeriodResponse

Approve Notification Create Reasoned Explanation Submit Notification

«XSDcomplexType»

Approv eNotificationRequestType

«XSDelement»



approv eNotificationRequest

«XSDcomplexType»

Approv eNotificationResponseType

«XSDelement»



approv eNotificationResponse

«XSDcomplexType»

CreateReasonedExplanationRequestType

«XSDelement»


+ reasonedExplanation: Comment


createReasonedExplanationRequest

«XSDcomplexType»

CreateReasonedExplanationResponseType

«XSDelement»

+ reasonedExplanation: Comment


createReasonedExplanationResponse

«XSDcomplexType»

SubmitNotificationRequestType

«XSDelement»



submitNotificationRequest

«XSDcomplexType»

SubmitNotificationResponseType

«XSDelement»



submitNotificationResponse

Transverse

Search Agent Search Notification Search Waste

«XSDcomplexType»

SearchAgentRequestType

«XSDelement»

+ agent: Agent

«XSDcomplexType»

SearchAgentResponseType

«XSDelement»

+ agentList: Agent [0..-1]


searchAgentRequest


searchAgentResponse

«XSDcomplexType»

SearchNotificationRequestType

«XSDelement»


«XSDcomplexType»

SearchNotificationResponseType

«XSDelement»

+ notificationList: Notification [0..-1]


searchNotificationRequest


searchNotificationResponse

«XSDcomplexType»

SearchWasteRequestType

«XSDelement»

+ waste: Waste

«XSDcomplexType»

SearchWasteResponseType

«XSDelement»

+ wasteList: Waste [0..-1]


searchWasteRequest


searchWasteResponse

«XSDcomplexType»

CreateNotificationDocRequestType

«XSDelement»



createNotificationDocRequest

«XSDcomplexType»

CreateNotificationDocResponseType

«XSDelement»



createNotificationDocResponse

«XSDcomplexType»

AddCommentRequestType

«XSDelement»


+ comment: Comment


addCommentRequest

«XSDcomplexType»

AddCommentResponseType

«XSDelement»

+ comment: Comment


addCommentResponse





Find below the Types details describing their attributes and the data types being used.

2.5.1 AcknowledgeNotificationRequestType


Generalization from «XSDtopLevelElement» acknowledgeNotificationRequest to «XSDcomplexType»


ATTRIBUTES

notification : Notification Public

Description:

Notification elements to be filled:

notificationID

Properties:

anonymousRole = false

default =

fixed =

form =

2.5.2 AcknowledgeNotificationResponseType


Generalization from «XSDtopLevelElement» acknowledgeNotificationResponse to «XSDcomplexType»


ATTRIBUTES

acknowledgement : Acknowledgement Public

Description:





The notification acknowledgment, including the ID to uniquely identify it.

Properties:


default =

fixed =

form =

2.5.3 AddCommentRequestType


Generalization from «XSDtopLevelElement» addCommentRequest to «XSDcomplexType»


ATTRIBUTES


Description:

The ID of the notification the comment will be added to.

Properties:


default =

fixed =

form =

comment : Comment Public

Description:

Comment elements to be filled:

comment





Properties:


default =

fixed =

form =

2.5.4 AddCommentResponseType


Generalization from «XSDtopLevelElement» addCommentResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The newly added comment, including the ID to uniquely identify it.

Properties:


default =

fixed =

form =

2.5.5 ApproveNotificationRequestType


Generalization from «XSDtopLevelElement» approveNotificationRequest to «XSDcomplexType»

ApproveNotificationRequestType





ATTRIBUTES


Description:


notificationID

serialNumber

Properties:


default =

fixed =

form =

2.5.6 ApproveNotificationResponseType


Generalization from «XSDtopLevelElement» approveNotificationResponse to «XSDcomplexType»

ApproveNotificationResponseType

ATTRIBUTES


Description:

The approved notification.





2.5.7 CloseInformationRequestRequestType


Generalization from «XSDtopLevelElement» closeInformationRequestRequest to «XSDcomplexType»


ATTRIBUTES

informationRequest : InformationRequest Public

Description:

Information Request elements to be filled:

informationRequestID

Properties:


default =

fixed =

form =

2.5.8 CloseInformationRequestResponseType


Generalization from «XSDtopLevelElement» closeInformationRequestResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The closed information request.





Properties:


default =

fixed =

form =

2.5.9 CloseObjectionRequestType


Generalization from «XSDtopLevelElement» closeObjectionRequest to «XSDcomplexType»


ATTRIBUTES

objection : Objection Public

Description:

Objection elements to be filled:

objectionID

Properties:


default =

fixed =

form =





2.5.10 CloseObjectionResponseType


Generalization from «XSDtopLevelElement» closeObjectionResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The closed objection.

Properties:


default =

fixed =

form =

2.5.11 ConfirmReceiptRequestType


Generalization from «XSDtopLevelElement» confirmReceiptRequest to «XSDcomplexType»


ATTRIBUTES


Description:


Properties:






default =

fixed =

form =

receipt : Receipt Public

Description:

Receipt elements to be filled:

receivedOn

rejected

rejectionReason (optional)

facilityType

receivedWasteQuantity

receivedWasteUnit

approximateDate

operationCode

Properties:


default =

fixed =

form =

2.5.12 ConfirmReceiptResponseType


Generalization from «XSDtopLevelElement» confirmReceiptResponse to «XSDcomplexType»


ATTRIBUTES






Description:

The newly created receipt confirmation, including the ID to uniquely identify it.

Properties:


default =

fixed =

form =

2.5.13 ConfirmRecoveryDisposalRequestType


Generalization from «XSDtopLevelElement» confirmRecoveryDisposalRequest to «XSDcomplexType»

ConfirmRecoveryDisposalRequestType

ATTRIBUTES


Description:

Receipt elements to be filled:

receiptID

completedOn (Recovery/Disposal)

Properties:


default =

fixed =

form =





2.5.14 ConfirmRecoveryDisposalResponseType


Generalization from «XSDtopLevelElement» confirmRecoveryDisposalResponse to «XSDcomplexType»

ConfirmRecoveryDisposalResponseType

ATTRIBUTES


Description:

The receipt including the newly created recovery/disposal confirmation.

Properties:


default =

fixed =

form =

2.5.15 CreateConsentRequestType


Generalization from «XSDtopLevelElement» createConsentRequest to «XSDcomplexType»


ATTRIBUTES


Description:

The ID of the notification the consent will be issued to.

Properties:






default =

fixed =

form =

consent : WrittenConsent Public

Description:

Consent elements to be filled:

validFrom

validUntil

hasSpecificConditions

specificConditions (optional)

Properties:


default =

fixed =

form =

2.5.16 CreateConsentResponseType


Generalization from «XSDtopLevelElement» createConsentResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The newly created consent, including the ID to uniquely identify it.





Properties:


default =

fixed =

form =

2.5.17 CreateInformationRequestRequestType


Generalization from «XSDtopLevelElement» createInformationRequestRequest to «XSDcomplexType»


ATTRIBUTES


Description:

The ID of the notification the information request will be added to.

Properties:


default =

fixed =

form =


Description:


request

comments (optional)

Properties:






default =

fixed =

form =

2.5.18 CreateInformationRequestResponseType


Generalization from «XSDtopLevelElement» createInformationRequestResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The newly created information request, including the ID to uniquely identify it.

Properties:


default =

fixed =

form =

2.5.19 CreateMovementDocRequestType


Generalization from «XSDtopLevelElement» createMovementDocRequest to «XSDcomplexType»

CreateMovementDocRequestType





ATTRIBUTES


Description:

The ID of the notification the movement document will be linked to.

Properties:


default =

fixed =

form =

movementDocument : MovementDocument Public

Description:

MovementDocument elements to be filled:

shipmentSerial (optional)

shipmentTotalNumber (optional)

exporterSignedAt (optional)

importerSignedAt (optional)

actualWasteQuantity (optional)

actualWasteUnit (optional)

additionalInformation (optional)

movementShipment (optional)

Properties:


default =

fixed =

form =





2.5.20 CreateMovementDocResponseType


Generalization from «XSDtopLevelElement» createMovementDocResponse to «XSDcomplexType»

CreateMovementDocResponseType

ATTRIBUTES


Description:

The newly created movement document, including the ID to uniquely identify it.

Properties:


default =

fixed =

form =

2.5.21 CreateNotificationDocRequestType


Generalization from «XSDtopLevelElement» createNotificationDocRequest to «XSDcomplexType»


ATTRIBUTES


Description:


serialNumber (optional)





notificationType (optional)

exporter (optional)


importer (optional)

carrier (optional)

producer (optional)

producerSignedAt (optional)

facility (optional)

preconsentedRecoveryFacility (optional)

notificationShipment (optional)

wasteIdentification (optional)

operation (optional)

routing (optional)

contract (optional)

financialGuarantee (optional)

notificationAttachment (optional)

Properties:


default =

fixed =

form =

2.5.22 CreateNotificationDocResponseType


Generalization from «XSDtopLevelElement» createNotificationDocResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The newly created notification, including the ID to uniquely identify it.





Properties:


default =

fixed =

form =

2.5.23 CreateObjectionRequestType


Generalization from «XSDtopLevelElement» createObjectionRequest to «XSDcomplexType»


ATTRIBUTES


Description:

The ID of the notification the objection will be added to.

Properties:


default =

fixed =

form =


Description:


agentID (facility ID in the country of destination)





objection

waste

quantity

quantityUnit

operationCode

comments (optional)

Properties:


default =

fixed =

form =

2.5.24 CreateObjectionResponseType


Generalization from «XSDtopLevelElement» createObjectionResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The newly created objection, including the ID to uniquely identify it.

Properties:


default =

fixed =

form =





2.5.25 CreateReasonedExplanationRequestType


Generalization from «XSDtopLevelElement» createReasonedExplanationRequest to «XSDcomplexType»


ATTRIBUTES


Description:

The ID of the notification

Properties:


default =

fixed =

form =

reasonedExplanation : Comment Public

Description:


commentType (NNT - Notification not transmitted / NNA - Notification not acknowledged)

comment (reasoned explanation)

Properties:


default =

fixed =

form =





2.5.26 CreateReasonedExplanationResponseType


Generalization from «XSDtopLevelElement» createReasonedExplanationResponse to «XSDcomplexType»


ATTRIBUTES

reasonedExplanation : Comment Public

Description:

The newly created reasoned explanation (comment), including the ID to uniquely identify it.

Properties:


default =

fixed =

form =

2.5.27 CustodyTransferRequestType


Generalization from «XSDtopLevelElement» custodyTransferRequest to «XSDcomplexType»


ATTRIBUTES


Description:


Properties:






default =

fixed =

form =

finalCarrier : FinalCarrier Public

Description:

FinalCarrier elements to be filled:

agentID (carrier ID)

meansOfTransport

Properties:


default =

fixed =

form =

2.5.28 CustodyTransferResponseType


Generalization from «XSDtopLevelElement» custodyTransferResponse to «XSDcomplexType»


ATTRIBUTES

finalCarrier : FinalCarrier Public

Description:

The final carrier custody transfer, including the ID to uniquely identify it.

Properties:






default =

fixed =

form =

2.5.29 DeleteCommentRequestType


Generalization from «XSDtopLevelElement» deleteCommentRequest to «XSDcomplexType»


ATTRIBUTES


Description:


commentID

Properties:


default =

fixed =

form =

2.5.30 DeleteCommentResponseType


Generalization from «XSDtopLevelElement» deleteCommentResponse to «XSDcomplexType»






ATTRIBUTES


Description:

The deleted comment.

2.5.31 ExtendConsentPeriodRequestType


Generalization from «XSDtopLevelElement» extendConsentPeriodRequest to «XSDcomplexType»


ATTRIBUTES

facilityPreconsent : FacilityPreconsent Public

Description:

FacilityPreconsent elements to be filled:

facilityPreconsentID

validUntil

Properties:


default =

fixed =

form =





2.5.32 ExtendConsentPeriodResponseType


Generalization from «XSDtopLevelElement» extendConsentPeriodResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The facility pre-consent in which the period of validity has been extended.

Properties:


default =

fixed =

form =





2.5.33 ExtendPeriodRequestType


Generalization from «XSDtopLevelElement» extendPeriodRequest to «XSDcomplexType»


ATTRIBUTES


Description:



informationRequestsUntil

Properties:


default =

fixed =

form =

2.5.34 ExtendPeriodResponseType


Generalization from «XSDtopLevelElement» extendPeriodResponse to «XSDcomplexType»


ATTRIBUTES






Description:

The facility pre-consent in which the time needed in order to receive further information or documentation

from the notifier has been extended.

Properties:


default =

fixed =

form =

2.5.35 IllegalShipmentRequestType


Generalization from «XSDtopLevelElement» illegalShipmentRequest to «XSDcomplexType»


ATTRIBUTES


Description:


Properties:


default =

fixed =

form =

illegality : Illegality Public

Description:

Illegality elements to be filled:





illegalityType

illegalityTypeOther (optional)

detectedOn

responsible

measures

Properties:


default =

fixed =

form =

2.5.36 IllegalShipmentResponseType


Generalization from «XSDtopLevelElement» illegalShipmentResponse to «XSDcomplexType»


ATTRIBUTES

illegality : Illegality Public

Description:

The newly reported illegality, including the ID to uniquely identify it.

Properties:


default =

fixed =

form =





2.5.37 IssuePreConsentRequestType


Generalization from «XSDtopLevelElement» issuePreConsentRequest to «XSDcomplexType»


ATTRIBUTES

facilityID : int Public

Description:

The ID of the facility (Agent ID) the pre-consent will be issued to.

Properties:


default =

fixed =

form =


Description:


wasteCode

validFrom

validUntil

preconsentedQuantity

quantityUnit

recoveryOperation

employedTechnology

Properties:


default =

fixed =

form =





2.5.38 IssuePreConsentResponseType


Generalization from «XSDtopLevelElement» issuePreConsentResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The newly issued facility pre-consent, including the ID to uniquely identify it.

Properties:


default =

fixed =

form =

2.5.39 RecordPassageRequestType


Generalization from «XSDtopLevelElement» recordPassageRequest to «XSDcomplexType»


ATTRIBUTES


Description:


Properties:






default =

fixed =

form =

passage : Passage Public

Description:

Passage elements to be filled:

passageType

country

entry

exit

Properties:


default =

fixed =

form =

2.5.40 RecordPassageResponseType


Generalization from «XSDtopLevelElement» recordPassageResponse to «XSDcomplexType»


ATTRIBUTES

passage : Passage Public

Description:

The newly recorded customs passage, including the ID to uniquely identify it.





Properties:


default =

fixed =

form =

2.5.41 ReopenInformationRequestRequestType


Generalization from «XSDtopLevelElement» reopenInformationRequestRequest to «XSDcomplexType»


ATTRIBUTES


Description:



comments

Properties:


default =

fixed =

form =





2.5.42 ReopenInformationRequestResponseType


Generalization from «XSDtopLevelElement» reopenInformationRequestResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The reopened information request.

Properties:


default =

fixed =

form =

2.5.43 ReopenObjectionRequestType


Generalization from «XSDtopLevelElement» reopenObjectionRequest to «XSDcomplexType»


ATTRIBUTES


Description:


objectionID





comments

Properties:


default =

fixed =

form =

2.5.44 ReopenObjectionResponseType


Generalization from «XSDtopLevelElement» reopenObjectionResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The reopened objection.

Properties:


default =

fixed =

form =





2.5.45 RevokePreConsentRequestType


Generalization from «XSDtopLevelElement» revokePreConsentRequest to «XSDcomplexType»

RevokePreConsentRequestType

ATTRIBUTES


Description:



Properties:


default =

fixed =

form =

2.5.46 RevokePreConsentResponseType


Generalization from «XSDtopLevelElement» revokePreConsentResponse to «XSDcomplexType»

RevokePreConsentResponseType

ATTRIBUTES


Description:

The revoked facility pre-consent.





2.5.47 SearchAgentRequestType


Generalization from «XSDtopLevelElement» searchAgentRequest to «XSDcomplexType»


ATTRIBUTES

agent : Agent Public

Description:

Agent elements to be filled:

registrationNumber (optional)

country (optional)

name (optional)

street (optional)

zipcode (optional)

city (optional)

state (optional)

Properties:


default =

fixed =

form =

2.5.48 SearchAgentResponseType


Generalization from «XSDtopLevelElement» searchAgentResponse to «XSDcomplexType»






ATTRIBUTES

agentList : Agent Public

Multiplicity: ( [0..-1], Allow duplicates: 0, Is ordered: False )

Description:

List of agents matching the given search criteria.

Properties:


default =

fixed =

form =





2.5.49 SearchNotificationRequestType


Generalization from «XSDtopLevelElement» searchNotificationRequest to «XSDcomplexType»


ATTRIBUTES


Description:



country (export country) (optional)

country (import country) (optional)

agentID (facility ID) (optional)

notificationStatus (optional)

Properties:


default =

fixed =

form =

2.5.50 SearchNotificationResponseType


Generalization from «XSDtopLevelElement» searchNotificationResponse to «XSDcomplexType»






ATTRIBUTES

notificationList : Notification Public


Description:

List of notifications matching the given search criteria.

Properties:


default =

fixed =

form =

2.5.51 SearchWasteRequestType


Generalization from «XSDtopLevelElement» searchWasteRequest to «XSDcomplexType»


ATTRIBUTES

waste : Waste Public

Description:

Waste elements to be filled:

wasteCode (optional)

wasteType (optional)

description (optional)

Properties:


default =

fixed =

form =





2.5.52 SearchWasteResponseType


Generalization from «XSDtopLevelElement» searchWasteResponse to «XSDcomplexType»


ATTRIBUTES

wasteList : Waste Public


Properties:


default =

fixed =

form =

2.5.53 SolveInformationRequestRequestType


Generalization from «XSDtopLevelElement» solveInformationRequestRequest to «XSDcomplexType»

SolveInformationRequestRequestType

ATTRIBUTES


Description:



comments (optional)





Properties:


default =

fixed =

form =

2.5.54 SolveInformationRequestResponseType


Generalization from «XSDtopLevelElement» solveInformationRequestResponse to «XSDcomplexType»

SolveInformationRequestResponseType

ATTRIBUTES


Description:

The solved information request.

Properties:


default =

fixed =

form =

2.5.55 SolveObjectionRequestType


Generalization from «XSDtopLevelElement» solveObjectionRequest to «XSDcomplexType»

SolveObjectionRequestType





ATTRIBUTES


Description:


objectionID

comments (optional)

Properties:


default =

fixed =

form =

2.5.56 SolveObjectionResponseType


Generalization from «XSDtopLevelElement» solveObjectionResponse to «XSDcomplexType»

SolveObjectionResponseType

ATTRIBUTES


Description:

The solved objection.

Properties:


default =

fixed =

form =





2.5.57 SubmitNotificationRequestType


Generalization from «XSDtopLevelElement» submitNotificationRequest to «XSDcomplexType»


ATTRIBUTES


Description:


notificationID

Properties:


default =

fixed =

form =

2.5.58 SubmitNotificationResponseType


Generalization from «XSDtopLevelElement» submitNotificationResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The submitted notification.





Properties:


default =

fixed =

form =

2.5.59 UpdateCommentRequestType


Generalization from «XSDtopLevelElement» updateCommentRequest to «XSDcomplexType»


ATTRIBUTES


Description:


commentID

comment

Properties:


default =

fixed =

form =

2.5.60 UpdateCommentResponseType






Generalization from «XSDtopLevelElement» updateCommentResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The updated comment.

Properties:


default =

fixed =

form =

2.5.61 UpdateMovementDocRequestType


Generalization from «XSDtopLevelElement» updateMovementDocRequest to «XSDcomplexType»

UpdateMovementDocRequestType

ATTRIBUTES


Description:

MovementDocument elements to be filled:

movementDocumentID

shipmentSerial (optional)





shipmentTotalNumber (optional)


importerSignedAt (optional)

actualWasteQuantity (optional)

actualWasteUnit (optional)

withdrawndAt (optional)

additionalInformation (optional)

movementShipment (optional)

Properties:


default =

fixed =

form =

2.5.62 UpdateMovementDocResponseType


Generalization from «XSDtopLevelElement» updateMovementDocResponse to «XSDcomplexType»

UpdateMovementDocResponseType

ATTRIBUTES


Description:

The updated movement document.

Properties:


default =

fixed =

form =





2.5.63 UpdateNotificationDocRequestType


Generalization from «XSDtopLevelElement» updateNotificationDocRequest to «XSDcomplexType»


ATTRIBUTES


Description:


notificationID


notificationType (optional)

exporter (optional)


importer (optional)

carrier (optional)

producer (optional)

producerSignedAt (optional)

facility (optional)

preconsentedRecoveryFacility (optional)

notificationShipment (optional)

wasteIdentification (optional)

operation (optional)

routing (optional)

contract (optional)

financialGuarantee (optional)

notificationAttachment (optional)





Properties:


default =

fixed =

form =

2.5.64 UpdateNotificationDocResponseType


Generalization from «XSDtopLevelElement» updateNotificationDocResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The updated notification.

Properties:


default =

fixed =

form =

2.5.65 WithdrawConsentRequestType


Generalization from «XSDtopLevelElement» withdrawConsentRequest to «XSDcomplexType»






ATTRIBUTES


Description:

Consent elements to be filled:

consentID

Properties:


default =

fixed =

form =

2.5.66 WithdrawConsentResponseType


Generalization from «XSDtopLevelElement» withdrawConsentResponse to «XSDcomplexType»


ATTRIBUTES


Description:

The withdrawn consent.

Properties:


default =

fixed =

form =





2.5.67 acknowledgeNotificationRequest


Generalization from «XSDtopLevelElement» acknowledgeNotificationRequest to «XSDcomplexType»


2.5.68 acknowledgeNotificationResponse


Generalization from «XSDtopLevelElement» acknowledgeNotificationResponse to «XSDcomplexType»


2.5.69 addCommentRequest


Generalization from «XSDtopLevelElement» addCommentRequest to «XSDcomplexType»


2.5.70 addCommentResponse


Generalization from «XSDtopLevelElement» addCommentResponse to «XSDcomplexType»






2.5.71 approveNotificationRequest


Generalization from «XSDtopLevelElement» approveNotificationRequest to «XSDcomplexType»

ApproveNotificationRequestType

2.5.72 approveNotificationResponse


Generalization from «XSDtopLevelElement» approveNotificationResponse to «XSDcomplexType»

ApproveNotificationResponseType

2.5.73 closeInformationRequestRequest


Generalization from «XSDtopLevelElement» closeInformationRequestRequest to «XSDcomplexType»


2.5.74 closeInformationRequestResponse


Generalization from «XSDtopLevelElement» closeInformationRequestResponse to «XSDcomplexType»






2.5.75 closeObjectionRequest


Generalization from «XSDtopLevelElement» closeObjectionRequest to «XSDcomplexType»


2.5.76 closeObjectionResponse


Generalization from «XSDtopLevelElement» closeObjectionResponse to «XSDcomplexType»


2.5.77 confirmReceiptRequest


Generalization from «XSDtopLevelElement» confirmReceiptRequest to «XSDcomplexType»


2.5.78 confirmReceiptResponse


Generalization from «XSDtopLevelElement» confirmReceiptResponse to «XSDcomplexType»






2.5.79 confirmRecoveryDisposalRequest


Generalization from «XSDtopLevelElement» confirmRecoveryDisposalRequest to «XSDcomplexType»

ConfirmRecoveryDisposalRequestType

2.5.80 confirmRecoveryDisposalResponse


Generalization from «XSDtopLevelElement» confirmRecoveryDisposalResponse to «XSDcomplexType»

ConfirmRecoveryDisposalResponseType

2.5.81 createConsentRequest


Generalization from «XSDtopLevelElement» createConsentRequest to «XSDcomplexType»


2.5.82 createConsentResponse


Generalization from «XSDtopLevelElement» createConsentResponse to «XSDcomplexType»






2.5.83 createInformationRequestRequest


Generalization from «XSDtopLevelElement» createInformationRequestRequest to «XSDcomplexType»


2.5.84 createInformationRequestResponse


Generalization from «XSDtopLevelElement» createInformationRequestResponse to «XSDcomplexType»


2.5.85 createMovementDocRequest


Generalization from «XSDtopLevelElement» createMovementDocRequest to «XSDcomplexType»

CreateMovementDocRequestType

2.5.86 createMovementDocResponse


Generalization from «XSDtopLevelElement» createMovementDocResponse to «XSDcomplexType»

CreateMovementDocResponseType





2.5.87 createNotificationDocRequest


Generalization from «XSDtopLevelElement» createNotificationDocRequest to «XSDcomplexType»


2.5.88 createNotificationDocResponse


Generalization from «XSDtopLevelElement» createNotificationDocResponse to «XSDcomplexType»


2.5.89 createObjectionRequest


Generalization from «XSDtopLevelElement» createObjectionRequest to «XSDcomplexType»


2.5.90 createObjectionResponse


Generalization from «XSDtopLevelElement» createObjectionResponse to «XSDcomplexType»






2.5.91 createReasonedExplanationRequest


Generalization from «XSDtopLevelElement» createReasonedExplanationRequest to «XSDcomplexType»


2.5.92 createReasonedExplanationResponse


Generalization from «XSDtopLevelElement» createReasonedExplanationResponse to «XSDcomplexType»


2.5.93 custodyTransferRequest


Generalization from «XSDtopLevelElement» custodyTransferRequest to «XSDcomplexType»


2.5.94 custodyTransferResponse


Generalization from «XSDtopLevelElement» custodyTransferResponse to «XSDcomplexType»






2.5.95 deleteCommentRequest


Generalization from «XSDtopLevelElement» deleteCommentRequest to «XSDcomplexType»


2.5.96 deleteCommentResponse


Generalization from «XSDtopLevelElement» deleteCommentResponse to «XSDcomplexType»


2.5.97 extendConsentPeriodRequest


Generalization from «XSDtopLevelElement» extendConsentPeriodRequest to «XSDcomplexType»


2.5.98 extendConsentPeriodResponse


Generalization from «XSDtopLevelElement» extendConsentPeriodResponse to «XSDcomplexType»






2.5.99 extendPeriodRequest


Generalization from «XSDtopLevelElement» extendPeriodRequest to «XSDcomplexType»


2.5.100 extendPeriodResponse


Generalization from «XSDtopLevelElement» extendPeriodResponse to «XSDcomplexType»


2.5.101 illegalShipmentRequest


Generalization from «XSDtopLevelElement» illegalShipmentRequest to «XSDcomplexType»


2.5.102 illegalShipmentResponse


Generalization from «XSDtopLevelElement» illegalShipmentResponse to «XSDcomplexType»






2.5.103 issuePreConsentRequest


Generalization from «XSDtopLevelElement» issuePreConsentRequest to «XSDcomplexType»


2.5.104 issuePreConsentResponse


Generalization from «XSDtopLevelElement» issuePreConsentResponse to «XSDcomplexType»


2.5.105 recordPassageRequest


Generalization from «XSDtopLevelElement» recordPassageRequest to «XSDcomplexType»


2.5.106 recordPassageResponse


Generalization from «XSDtopLevelElement» recordPassageResponse to «XSDcomplexType»






2.5.107 reopenInformationRequestRequest


Generalization from «XSDtopLevelElement» reopenInformationRequestRequest to «XSDcomplexType»


2.5.108 reopenInformationRequestResponse


Generalization from «XSDtopLevelElement» reopenInformationRequestResponse to «XSDcomplexType»


2.5.109 reopenObjectionRequest


Generalization from «XSDtopLevelElement» reopenObjectionRequest to «XSDcomplexType»


2.5.110 reopenObjectionResponse


Generalization from «XSDtopLevelElement» reopenObjectionResponse to «XSDcomplexType»






2.5.111 revokePreConsentRequest


Generalization from «XSDtopLevelElement» revokePreConsentRequest to «XSDcomplexType»

RevokePreConsentRequestType

2.5.112 revokePreConsentResponse


Generalization from «XSDtopLevelElement» revokePreConsentResponse to «XSDcomplexType»

RevokePreConsentResponseType

2.5.113 searchAgentRequest


Generalization from «XSDtopLevelElement» searchAgentRequest to «XSDcomplexType»


2.5.114 searchAgentResponse


Generalization from «XSDtopLevelElement» searchAgentResponse to «XSDcomplexType»






2.5.115 searchNotificationRequest


Generalization from «XSDtopLevelElement» searchNotificationRequest to «XSDcomplexType»


2.5.116 searchNotificationResponse


Generalization from «XSDtopLevelElement» searchNotificationResponse to «XSDcomplexType»


2.5.117 searchWasteRequest


Generalization from «XSDtopLevelElement» searchWasteRequest to «XSDcomplexType»


2.5.118 searchWasteResponse


Generalization from «XSDtopLevelElement» searchWasteResponse to «XSDcomplexType»






2.5.119 solveInformationRequestRequest


Generalization from «XSDtopLevelElement» solveInformationRequestRequest to «XSDcomplexType»

SolveInformationRequestRequestType

2.5.120 solveInformationRequestResponse


Generalization from «XSDtopLevelElement» solveInformationRequestResponse to «XSDcomplexType»

SolveInformationRequestResponseType

2.5.121 solveObjectionRequest


Generalization from «XSDtopLevelElement» solveObjectionRequest to «XSDcomplexType»

SolveObjectionRequestType

2.5.122 solveObjectionResponse


Generalization from «XSDtopLevelElement» solveObjectionResponse to «XSDcomplexType»

SolveObjectionResponseType





2.5.123 submitNotificationRequest


Generalization from «XSDtopLevelElement» submitNotificationRequest to «XSDcomplexType»


2.5.124 submitNotificationResponse


Generalization from «XSDtopLevelElement» submitNotificationResponse to «XSDcomplexType»


2.5.125 updateCommentRequest


Generalization from «XSDtopLevelElement» updateCommentRequest to «XSDcomplexType»


2.5.126 updateCommentResponse


Generalization from «XSDtopLevelElement» updateCommentResponse to «XSDcomplexType»






2.5.127 updateMovementDocRequest


Generalization from «XSDtopLevelElement» updateMovementDocRequest to «XSDcomplexType»

UpdateMovementDocRequestType

2.5.128 updateMovementDocResponse


Generalization from «XSDtopLevelElement» updateMovementDocResponse to «XSDcomplexType»

UpdateMovementDocResponseType

2.5.129 updateNotificationDocRequest


Generalization from «XSDtopLevelElement» updateNotificationDocRequest to «XSDcomplexType»


2.5.130 updateNotificationDocResponse


Generalization from «XSDtopLevelElement» updateNotificationDocResponse to «XSDcomplexType»






2.5.131 withdrawConsentRequest


Generalization from «XSDtopLevelElement» withdrawConsentRequest to «XSDcomplexType»


2.5.132 withdrawConsentResponse


Generalization from «XSDtopLevelElement» withdrawConsentResponse to «XSDcomplexType»
