This view contains identified evidence gaps.

Conceptual information

What business information does the application manage, and how are those concepts related?

The application’s information centres on Notification: a record for proposed waste shipments, with import and export variants. The published material associates notifications with parties, treatment facilities, routes, waste classifications, planned shipments, actual movements, assessments, consent, financial guarantees and financial transactions. E0007 E0081 E0093

Read this model by distinguishing Shipment plan, which describes intended dates, quantity and shipment count, from Movement, which represents an individual shipment and its operational information. Likewise, Assessment describes review status and milestones, while Consent retains a validity period, conditions and decision date. E0093 E0226 E0010

The relationships below describe business associations, not a physical database design. No multiplicities are asserted: the supplied analyses identify unresolved uniqueness and cardinality constraints, and fixture examples do not establish universal business requirements. These are published source analyses, not live verification of stored records or deployed behaviour. E0007 E0156 E0262

Diagram

flowchart LR
  n3a668678fbe51ebb7c91["Notification"]
  nea60ed53a0d9537febe5["Importer"]
  nf46e7d0f87cfef064385["Exporter"]
  n54a17d68e2c374e54ebb["Producer"]
  n62333cd1baa5e14682b6["Carrier"]
  n279ad3258e6835634bd5["Facility"]
  nc7c38141fde3b1805c58["Transport route"]
  n11183f7bd7558ba24fde["Waste type"]
  na63d5807346940ab9aa7["Waste code"]
  n426d1ad701bed918c8c5["Waste operation"]
  n05b11c1667609eca90b8["Shipment plan #40;inferred#41;"]
  ned2574f638ed597bbb00["Movement"]
  n645a885a419d6307bcac["Assessment"]
  ndab22d5d23d20cd8ba46["Consent"]
  n61a2f1f6a2548f2a671c["Financial guarantee"]
  n9ae841b8a8c55dee27ec["Transaction"]
  n79a2f5907cfbadda6852["Comment"]
  n3a668678fbe51ebb7c91 -->|"Notification names importer"| nea60ed53a0d9537febe5
  n3a668678fbe51ebb7c91 -->|"Notification names exporter"| nf46e7d0f87cfef064385
  n3a668678fbe51ebb7c91 -->|"Notification identifies producers"| n54a17d68e2c374e54ebb
  n3a668678fbe51ebb7c91 -->|"Notification lists carriers"| n62333cd1baa5e14682b6
  ned2574f638ed597bbb00 -->|"Movement assigns carriers"| n62333cd1baa5e14682b6
  n3a668678fbe51ebb7c91 -->|"Notification identifies treatment facilities"| n279ad3258e6835634bd5
  n3a668678fbe51ebb7c91 -->|"Notification specifies route"| nc7c38141fde3b1805c58
  n3a668678fbe51ebb7c91 -->|"Notification describes waste"| n11183f7bd7558ba24fde
  n11183f7bd7558ba24fde -->|"Waste type selects classification codes"| na63d5807346940ab9aa7
  n3a668678fbe51ebb7c91 -->|"Notification specifies waste operation"| n426d1ad701bed918c8c5
  n3a668678fbe51ebb7c91 -.->|"Notification defines shipment plan #40;inferred#41;"| n05b11c1667609eca90b8
  n3a668678fbe51ebb7c91 -->|"Notification groups movements"| ned2574f638ed597bbb00
  n3a668678fbe51ebb7c91 -->|"Notification is assessed"| n645a885a419d6307bcac
  n3a668678fbe51ebb7c91 -->|"Notification receives consent"| ndab22d5d23d20cd8ba46
  n645a885a419d6307bcac -->|"Assessment includes consent outcome"| ndab22d5d23d20cd8ba46
  n3a668678fbe51ebb7c91 -->|"Notification has financial guarantee"| n61a2f1f6a2548f2a671c
  n3a668678fbe51ebb7c91 -->|"Notification records transactions"| n9ae841b8a8c55dee27ec
  n3a668678fbe51ebb7c91 -->|"Notification retains comments"| n79a2f5907cfbadda6852

Elements

Notification

Kind: entity Basis: reported Description: The central waste-shipment notification record, distinguished as import or export in reporting. Its represented information includes notification number, creation date, status, type, competent authority and charge; the submission-summary declaration does not establish the meaning or calculation of charge. E0081 E0006 Evidence: E0081 E0006

Importer

Kind: entity Basis: reported Description: A party recorded on a notification in the importer role, with business, address, contact and registration information. Importer presence is separately represented in the data model. E0093 E0226 Evidence: E0093 E0226

Exporter

Kind: entity Basis: reported Description: A party recorded on a notification in the exporter role, with name, registration, address and contact information. Import-notification schema scripts and notification fixtures represent this role separately from importer and producer. E0007 E0226 Evidence: E0007 E0226

Producer

Kind: entity Basis: reported Description: A party recorded in the producer role. Export fixtures distinguish producers marked as the site of export from other producers; import fixtures also represent an only-producer flag. These examples do not establish mandatory producer counts. E0226 Evidence: E0226

Carrier

Kind: entity Basis: reported Description: A recorded carrier party with business, registration, address and contact information. Movement-specific carrier assignments additionally represent an ordering value. E0226 E0013 Evidence: E0226 E0013

Facility

Kind: entity Basis: reported Description: A treatment facility recorded within a notification’s facility collection, with address, contact and registration information. Facilities can be marked as the actual site of treatment, while the collection represents preconsent information. E0007 E0226 Evidence: E0007 E0226

Transport route

Kind: entity Basis: reported Description: The notification’s route information, composed of state-of-export, state-of-import and transit-state records, with competent-authority and entry/exit-point references. Transit-state examples carry ordinal positions. E0007 E0226 Evidence: E0007 E0226

Waste type

Kind: entity Basis: reported Description: The waste description and classification information associated with a notification. Import summary models aggregate Basel/OECD, EWC, Y, H and UN selections and an optional category; export fixtures also represent composition and additional constituent information. E0093 E0226 Evidence: E0093 E0226

Waste code

Kind: entity Basis: reported Description: A named classification code with descriptive information. Code-selection models distinguish selected codes from a not-applicable state; represented classification families include Basel/OECD, EWC, Y, H and UN. E0093 Evidence: E0093

Waste operation

Kind: entity Basis: reported Description: The waste-processing operation information, including operation codes and technology employed. The supplied operation-code vocabulary categorises recovery codes R1–R13 and disposal codes D1–D15. E0093 E0006 Evidence: E0093 E0006

Shipment plan

Kind: entity Basis: inferred Description: A conceptual name for notification-level intended shipment information: shipment count, quantity, units and first/last shipment dates. It is kept distinct from individual movements because the supplied models distinguish intended and used shipments. E0226 E0093 Evidence: E0226 E0093

Movement

Kind: entity Basis: reported Description: An individual shipment record associated with a notification, carrying a movement number, date and prenotification information. Related data represents actual quantity, packaging, receipt, operation completion, rejection, partial rejection and cancellation. E0013 E0096 Evidence: E0013 E0096

Assessment

Kind: entity Basis: reported Description: The notification’s review information, including status, milestone dates, officer information and decision history. Import and export assessment data have distinct status and date representations rather than one proven common lifecycle. E0006 E0093 E0081 Evidence: E0006 E0093 E0081

Consent

Kind: entity Basis: reported Description: A recorded consent decision with a validity start/end period, conditions and consent date. Import schema evidence also represents the associated user and notification. E0010 E0259 Evidence: E0010 E0259

Financial guarantee

Kind: entity Basis: reported Description: A guarantee record with application receipt/completion information and decision outcomes including approval, refusal and release. Approval records carry a reference, refusal records a reason; export approval models additionally represent permitted active loads, blanket-bond choice and cover/calculation amounts. E0010 E0093 E0516 Evidence: E0010 E0093 E0516

Transaction

Kind: entity Basis: reported Description: Notification-related financial transaction information with date, debit, credit, payment method, receipt number and comments. Payment and refund are represented transaction categories, but the declarations alone do not establish accounting invariants or reconciliation. E0006 Evidence: E0006

Comment

Kind: entity Basis: reported Description: A notification comment with user, date, type and shipment-number context represented in the supplied domain and retrieval evidence. The shipment-number field does not itself establish a validated association to an individual movement. E0508 E0010 Evidence: E0508 E0010

Relationships

Notification names importer

From: Notification To: Importer Relation: relates_to Basis: reported Description: Importer records are associated with notifications; the import model carries notification context, and fixtures explicitly create notification-linked importer information. E0093 E0226 Evidence: E0093 E0226

Notification names exporter

From: Notification To: Exporter Relation: relates_to Basis: reported Description: Exporter information is recorded against the notification. Import schema evidence provides the notification reference, and fixtures demonstrate the association for both directions. E0007 E0226 Evidence: E0007 E0226

Notification identifies producers

From: Notification To: Producer Relation: relates_to Basis: reported Description: Producer information belongs to the notification, directly in the import examples and through a producer collection in export examples. Site-of-export designation is represented on selected export producers. E0226 E0259 Evidence: E0226 E0259

Notification lists carriers

From: Notification To: Carrier Relation: relates_to Basis: reported Description: Export notification fixtures associate carriers through a notification carrier collection. This is a notification-level carrier list, distinct from the movement-specific assignment below. E0226 E0259 Evidence: E0226 E0259

Movement assigns carriers

From: Movement To: Carrier Relation: relates_to Basis: reported Description: Movement details expose carrier assignments, and the assignment record carries movement and carrier references with a positive ordering value. Collection initialization and broader assignment-integrity rules remain unresolved. E0013 Evidence: E0013

Notification identifies treatment facilities

From: Notification To: Facility Relation: relates_to Basis: reported Description: Facilities are grouped in a notification-linked facility collection. The represented information distinguishes actual treatment-site designation from collection-level preconsent information. E0226 E0259 Evidence: E0226 E0259

Notification specifies route

From: Notification To: Transport route Relation: relates_to Basis: reported Description: Transport-route records are associated with notifications and contain their export, import and transit-state context. Import schema evidence explicitly represents the notification reference. E0007 E0226 Evidence: E0007 E0226

Notification describes waste

From: Notification To: Waste type Relation: relates_to Basis: reported Description: Waste-type information is associated with the notification. Import update models carry notification context, and schema scripts represent a notification-linked waste-type record. E0093 E0007 Evidence: E0093 E0007

Waste type selects classification codes

From: Waste type To: Waste code Relation: relates_to Basis: reported Description: Waste type aggregates named classification selections whose contents are selected waste-code objects, with not-applicable represented separately from an empty applicable selection. E0093 Evidence: E0093

Notification specifies waste operation

From: Notification To: Waste operation Relation: relates_to Basis: reported Description: Waste-operation data carries import-notification context and records operation codes and technology employed. Import fixtures demonstrate a notification’s operation and its associated code. E0093 E0226 Evidence: E0093 E0226

Notification defines shipment plan

From: Notification To: Shipment plan Relation: relates_to Basis: inferred Description: Notification-linked shipment information is interpreted here as its shipment plan because it contains intended count, quantity, units and date range rather than individual movement outcomes. E0226 E0093 Evidence: E0226 E0093

Notification groups movements

From: Notification To: Movement Relation: relates_to Basis: reported Description: Movement creation retains notification context, while notification-level movement summaries combine intended shipment counts with individual movement information. Movement-number uniqueness within that scope is not established by the creation methods alone. E0013 E0096 Evidence: E0013 E0096

Notification is assessed

From: Notification To: Assessment Relation: relates_to Basis: reported Description: Assessment records are retrieved by notification and joined to their corresponding notification in reporting. Import schema backfills also associate assessments with notifications, without establishing permanent uniqueness. E0262 E0081 E0007 Evidence: E0262 E0081 E0007

Notification receives consent

From: Notification To: Consent Relation: relates_to Basis: reported Description: Consent is recorded for a notification with validity dates and conditions. The supplied import consent schema explicitly references the import notification. E0010 E0259 Evidence: E0010 E0259

Assessment includes consent outcome

From: Assessment To: Consent Relation: relates_to Basis: reported Description: Assessment decision retrieval includes consent, and assessment reports combine assessment status/date information with consent data. This association does not establish that recording consent always changes assessment status. E0262 E0081 E0010 Evidence: E0262 E0081 E0010

Notification has financial guarantee

From: Notification To: Financial guarantee Relation: relates_to Basis: reported Description: Import guarantee creation uses notification context and the import guarantee schema references the notification. Export records are associated through notification-linked guarantee collections in the supplied fixtures and queries. E0010 E0259 E0226 E0081 Evidence: E0010 E0259 E0226 E0081

Notification records transactions

From: Notification To: Transaction Relation: relates_to Basis: reported Description: Transaction data carries notification context, and payment reporting joins transactions to their corresponding import or export notifications to aggregate credits, debits and transaction dates. E0006 E0081 Evidence: E0006 E0081

Notification retains comments

From: Notification To: Comment Relation: relates_to Basis: reported Description: Import comment retrieval is scoped by notification and can further filter by type, date, shipment number and user. The domain comment representation also contains notification context. E0010 E0508 Evidence: E0010 E0508

Gaps

• Cardinality and identity: Exact requiredness, uniqueness and multiplicities remain unresolved for notification-linked parties, shipment plans, routes, waste types, assessments, consent and guarantees. Current schema constraints, complete mappings and business cardinality definitions are needed before adding multiplicities. E0007 E0262
• Import/export differences: Separate assessment/date structures and status vocabularies must remain distinct. Chapters describe submission as reaching Submitted in some accounts, whereas supplied import state-machine evidence identifies AwaitingPayment as the concrete destination beneath Submitted; this view does not collapse those meanings. C01 C06 E0508
• Guarantee linkage history: A historical export migration first links financial guarantees to assessments, then replaces that reference with a notification reference. Consequently, no current direct Assessment–Financial guarantee relationship is asserted here; later schema and mappings are required to establish it. E0191
• Movement outcomes: Receipt, completion and rejection records are represented, but their complete optionality and exclusivity are not established. Rejection or partial rejection can clear a receipt, while partial rejection permits later completion; follow-up should establish whether the required receipt is restored or otherwise guaranteed. E0013 E0218
• Financial and date semantics: Charge currency/calculation, debit-credit invariants, complete unit-conversion rules, timezone policy and milestone population rules remain partly unknown. The supplied import charge calculator passes shipment-count and interim information without visibly using those arguments in its price-returning method. E0006 E0096 E0508
• Classification and comment integrity: Complete waste-code validation, summary-to-update mappings and shipment-number membership checks for comments are not established. One fixture family uses an incremented notification counter as comment shipment number, so that example cannot validate Comment–Movement membership. E0093 E0010 E0156
• Evidence quality: Some retained database analyses report incomplete original analysis contracts or unavailable text, and migration evidence does not prove deployed schema state. Reporting joins and selected-row queries can omit or flatten related information; reports therefore cannot establish complete underlying business records. E0081 E0191 E0007

Recovery limitations

• The view includes explicitly marked inference.

Sources

• C01 — SHA256 64f6d1401664e4822834ff5cc3e8dca458e7fb9abd7922a987008f5e7d194651
• C06 — SHA256 8bceb3aecb3cf6c886c0465d9182417aaff5f99715f640e319cf4d0126f75a10
• E0006 — SHA256 fa270ea547e0bdc234232040b7cd3421cad4f194f484025bdf530a723c3775c1
• E0007 — SHA256 d6699228d4f3fe9029fed7e827299ce173b5f96221afb1a4050ccdbd61d9ba36
• E0010 — SHA256 4755fe76ad67a65078ba0dea356e490d662d2435fe315c92864ce7376eb09a2b
• E0013 — SHA256 f8500d44c789ea48c71c08a508fef06e6b7764dfc8f5dcc893f0cfd540154c9f
• E0081 — SHA256 880c1283f6cfd7d6f8407a0f46f77c0e778837966f8bde5b3c4c23e8c6b4ff13
• E0093 — SHA256 a1b3454dcfe9db217e9ace6f26874ef8c5433f804c03ead0aa906150f5bb20b8
• E0096 — SHA256 8635eeff1029d261d922ff11f8126c7e2ebc5c274d974ecf22e7bbb3cff4354a
• E0156 — SHA256 5e890d03921ed9b2b61c72356c808100f2fd9b69d45546bb9cbda21a932fe2c5
• E0191 — SHA256 8112580223c70fc72e14a00fb970de17ee216c34eea97f39e2c8c71d21017763
• E0218 — SHA256 51dd7c8b8b56b62dc1b1593551915269a6e29fdf5e835ce32a37d472c324b316
• E0226 — SHA256 a8f9af4dcd18d5f2f023760a65ddf0a270a9d2132b2f84b6d3b12999b458044b
• E0259 — SHA256 6e8bde8cd9bc008e0e9114dfd2f05763bdb42964a9bf4080ebd3710c1b80e926
• E0262 — SHA256 6284ea5fe1ee7f4bdb6d76ae0d65fe5992ee19c0f0339a1e443328986fd8a89e
• E0508 — SHA256 159c8fcca453ac20608d565a3dceaa2d35a3c78b67f16c621a090393e2496cd2
• E0516 — SHA256 fc72c78c98fc5933ebb6859adf25b3bd088beb03e538258b7b3dae733d2affd3