Phase 1 - Data Format

The Foundation of Interoperability

Data standardization forms the bedrock upon which all other phases build. Without common formats for describing devices, materials, and processes, systems cannot communicate effectively. Manufacturers would describe products using proprietary schemas incompatible with recycler systems. Collectors would track information that processing facilities cannot interpret. Regulators would require reports in formats that organizations struggle to generate. These incompatibilities perpetuate inefficiency and prevent the coordinated action necessary for effective e-waste management.

The WIA Phase 1 Data Format specifications address this fragmentation by defining JSON-based schemas for all core e-waste management data. These schemas cover device classification, material composition, lifecycle events, processing outcomes, and compliance documentation. By adopting these common formats, stakeholders speak a shared language that enables seamless information exchange regardless of underlying software systems.

Device Classification and Identification

Every electronic device entering the waste stream must be classified and uniquely identified. Classification determines appropriate handling procedures, while unique identification enables tracking through the recycling process. The standard employs a hierarchical classification system aligned with WEEE directive categories but extended with device-specific subcategories.

Primary WEEE Categories

The standard adopts the six WEEE categories as primary classifiers:

Device Subcategories and Types

Within each WEEE category, the standard defines subcategories that provide finer-grained classification. For example, WEEE-5 (Small Equipment) includes subcategories for the following. Smartphones and mobile phones are not in this list: under Annex IV of the WEEE Directive they belong to WEEE-6 (Small IT/Telecom), which is why the device examples below carry WEEE-6.

• Digital cameras and camcorders
• Portable audio devices
• Small household appliances
• Power tools
• Medical devices (portable)
• Gaming controllers and accessories

Unique Device Identification

Each device receives a UUID (Universally Unique Identifier) following RFC 4122 version 4 specifications. This identifier, generated at manufacturing or first registration, persists throughout the device lifecycle. QR codes encoding the UUID enable rapid scanning and tracking at collection and processing facilities.

{
  "device_id": "550e8400-e29b-41d4-a716-446655440000",
  "weee_category": "WEEE-6",
  "weee_subcategory": "smartphone",
  "manufacturer": {
    "name": "TechCorp Inc.",
    "facility_id": "FC-CN-SZ-001",
    "country_code": "CN"
  },
  "model": {
    "name": "TechPhone Pro 15",
    "number": "TP15-256-BK"
  },
  "manufacturing": {
    "date": "2024-03-15",
    "batch_number": "2024-Q1-B0342",
    "facility_id": "FC-CN-SZ-001"
  },
  "physical_properties": {
    "weight_kg": 0.189,
    "dimensions_mm": {
      "length": 146.7,
      "width": 71.5,
      "depth": 7.8
    }
  },
  "serial_number": "TC24031512345",
  "created_at": "2024-03-15T14:23:00Z",
  "schema_version": "1.0.0"
}

Of these, the required fields are device_id (UUID v4), weee_category (WEEE-1 to WEEE-6), manufacturer.name, model.name, weight_kg (kilograms, 3 decimal places), and created_at (ISO 8601 timestamp). Subcategory, manufacturing date, dimensions, serial number, and QR code URL are optional fields.

Material Composition Declaration

Accurate material composition information is critical for safe processing and efficient recovery. Manufacturers must declare all significant materials, hazardous substances, and valuable resources contained in devices. This declaration follows standardized formats that specify substance identifiers, quantities, locations, and extraction methods.

Bill of Materials Structure

The material declaration uses hierarchical structure reflecting device assembly. Top-level components (display, battery, circuit board, housing) contain sub-assemblies and individual materials. Each material is identified by CAS (Chemical Abstracts Service) number, providing unambiguous specification.

{
  "device_id": "550e8400-e29b-41d4-a716-446655440000",
  "bill_of_materials": {
    "version": "1.2.0",
    "last_updated": "2024-03-15",
    "components": [
      {
        "component_name": "Main Circuit Board",
        "component_type": "PCB",
        "weight_g": 18.5,
        "materials": [
          {
            "substance": "Copper",
            "cas_number": "7440-50-8",
            "weight_g": 5.2,
            "percentage": 28.1,
            "location": "Traces and layers"
          },
          {
            "substance": "Gold",
            "cas_number": "7440-57-5",
            "weight_g": 0.024,
            "percentage": 0.13,
            "location": "Connectors and contacts"
          },
          {
            "substance": "FR4 Substrate",
            "cas_number": "N/A",
            "weight_g": 10.8,
            "percentage": 58.4,
            "location": "Board substrate"
          }
        ],
        "hazardous_substances": [
          {
            "substance": "Lead",
            "cas_number": "7439-92-1",
            "weight_g": 0.15,
            "location": "Legacy solder joints",
            "concentration_ppm": 8100,
            "rohs_exempt": true,
            "exemption_code": "7a"
          }
        ]
      }
    ]
  }
}

Hazardous Substance Tracking

All hazardous substances require explicit declaration with quantities, locations, and handling requirements. The standard maintains a comprehensive hazardous substance registry aligned with RoHS, REACH, and other international frameworks. For each hazardous substance, declarations must include:

• Substance name and CAS number
• Quantity (mass and concentration)
• Precise location within device
• Regulatory status and exemptions
• Recommended handling procedures
• Disposal requirements

Valuable Material Documentation

Beyond hazards, declarations identify valuable materials warranting recovery efforts. Precious metals (gold, silver, platinum, palladium), rare earth elements (neodymium, dysprosium, yttrium), and strategic materials (tantalum, cobalt) receive detailed documentation including:

• Element identity and purity
• Quantity and concentration
• Form (alloy, compound, pure element)
• Location and accessibility
• Recommended recovery method
• Estimated recovery value

Lifecycle Event Tracking Schema

Devices accumulate history as they move from manufacturing through use and eventual recycling. The lifecycle tracking schema captures all significant events, creating comprehensive audit trails that support compliance verification, warranty management, and recycling optimization.

Event Types and Structure

The standard defines standardized event types covering the complete device lifecycle:

{
  "device_id": "550e8400-e29b-41d4-a716-446655440000",
  "lifecycle_events": [
    {
      "event_id": "evt_001",
      "event_type": "manufacturing_complete",
      "timestamp": "2024-03-15T14:23:00Z",
      "location": {
        "facility_id": "FC-CN-SZ-001",
        "address": "Shenzhen, China",
        "coordinates": {
          "latitude": 22.5431,
          "longitude": 114.0579
        }
      },
      "metadata": {
        "production_line": "Line-7",
        "quality_check": "passed",
        "batch_number": "2024-Q1-B0342"
      }
    },
    {
      "event_id": "evt_002",
      "event_type": "first_sale",
      "timestamp": "2024-04-22T10:15:00Z",
      "location": {
        "facility_id": "RT-US-NY-042",
        "address": "New York, NY, USA"
      },
      "metadata": {
        "retailer": "TechStore NYC",
        "warranty_start": "2024-04-22",
        "warranty_duration_months": 24
      }
    },
    {
      "event_id": "evt_003",
      "event_type": "collected_for_recycling",
      "timestamp": "2025-11-08T09:45:00Z",
      "location": {
        "facility_id": "COL-US-NY-018",
        "address": "Brooklyn, NY, USA"
      },
      "metadata": {
        "collection_method": "retail_takeback",
        "device_condition": "functional_obsolete",
        "data_wiped": true,
        "collector_id": "COL-12345"
      }
    }
  ]
}

Collection and Processing Events

E-waste management events receive particular attention, with detailed schemas capturing collection conditions, processing stages, and material recovery outcomes. These events include:

• collected_for_recycling (Collection): Entry into the waste stream. Required metadata are the collection method and device condition; recorded by the collector
• data_wiped (Data Wiping): Secure erasure. Required metadata are the erasure standard and certificate ID; recorded by the processor
• dismantled (Dismantling): Device disassembly. Required metadata is the list of extracted components; recorded by the processor
• material_recovered (Material Recovery): Material extraction. Required metadata are the list of materials and their quantities; recorded by the processor

In addition, manufacturing_complete, first_sale, ownership_transfer, and repair_service are defined as standard event types. Event timestamps must be in chronological order, and each event should be digitally signed by the entity that creates it.

Material Recovery Reporting Format

Processing outcomes must be documented to close the circular economy loop. Recovery reports link processed devices to recovered materials, documenting quantities, purities, and destination of all outputs. This transparency enables EPR cost allocation, compliance verification, and continuous process improvement.

{
  "recovery_report_id": "RR-2025-11-08-001",
  "facility_id": "RC-US-NY-003",
  "processing_date": "2025-11-08",
  "certification": ["R2", "e-Stewards"],
  "input_devices": [
    {
      "device_id": "550e8400-e29b-41d4-a716-446655440000",
      "weee_category": "WEEE-6",
      "weight_kg": 0.189
    }
  ],
  "batch_summary": {
    "total_devices": 250,
    "total_weight_kg": 52.7,
    "processing_method": "manual_dismantling_with_mechanical_separation"
  },
  "recovered_materials": [
    {
      "material": "Copper",
      "cas_number": "7440-50-8",
      "weight_kg": 6.8,
      "purity_percentage": 94.5,
      "recovery_method": "mechanical_separation",
      "destination": {
        "facility_id": "SM-US-PA-001",
        "facility_type": "secondary_smelter",
        "certification": "ISO_14001"
      },
      "estimated_value_usd": 64.60
    },
    {
      "material": "Gold",
      "cas_number": "7440-57-5",
      "weight_kg": 0.0062,
      "purity_percentage": 99.2,
      "recovery_method": "hydrometallurgical",
      "destination": {
        "facility_id": "PM-CH-ZH-001",
        "facility_type": "precious_metal_refinery"
      }
    },
    {
      "material": "Aluminium",
      "cas_number": "7429-90-5",
      "weight_kg": 7.6,
      "recovery_method": "mechanical_separation",
      "destination": {
        "facility_id": "SM-US-OH-002",
        "facility_type": "secondary_smelter"
      }
    },
    {
      "material": "Steel",
      "weight_kg": 9.8,
      "recovery_method": "magnetic_separation",
      "destination": {
        "facility_id": "SM-US-PA-004",
        "facility_type": "steel_mill"
      }
    },
    {
      "material": "Glass",
      "weight_kg": 14.0,
      "recovery_method": "mechanical_separation",
      "destination": {
        "facility_id": "GR-US-NJ-001",
        "facility_type": "glass_recycler"
      }
    }
  ],
  "residual_outputs": [
    {
      "material_type": "mixed_plastics",
      "weight_kg": 8.8,
      "disposition": "energy_recovery",
      "facility_id": "EF-US-NJ-002"
    },
    {
      "material_type": "hazardous_residues",
      "weight_kg": 2.1,
      "disposition": "secure_landfill",
      "facility_id": "HW-US-DE-001"
    },
    {
      "material_type": "non_recyclable_residues",
      "weight_kg": 3.6,
      "disposition": "landfill",
      "facility_id": "LF-US-NJ-005"
    }
  ],
  "recovery_efficiency": {
    "overall_recovery_rate_pct": 89.2,
    "material_recovery_pct": 72.5,
    "energy_recovery_pct": 16.7
  }
}

Data Validation and Quality Assurance

Data quality directly impacts system effectiveness. Invalid or incomplete data compromises tracking, undermines compliance verification, and reduces processing efficiency. The standard includes comprehensive validation rules and quality assurance mechanisms.

Schema Validation Rules

JSON Schema definitions specify required fields, data types, value ranges, and format constraints for all data elements. Validation libraries check conformance before data acceptance, rejecting invalid submissions with specific error messages. Key validation categories include:

• Required Fields: Essential data elements must be present
• Type Validation: Data types (string, number, boolean, date) enforced
• Range Constraints: Numeric values within acceptable ranges
• Format Validation: Dates, UUIDs, URLs match specified formats
• Enumeration Validation: Values from predefined lists only
• Cross-Field Validation: Relationships between fields logical and consistent

The specific cross-field validation criteria are as follows. The sum of component weights must match the total device weight within ±2%, and material percentages within a component must sum to approximately 100% within ±5%. Event timestamps must be chronological, and the input weight in a recovery report must match the registered device weight. CAS numbers must follow the registry format (e.g., 7440-50-8), and coordinates must fall within latitude [-90, 90] and longitude [-180, 180].

Conformance Levels

Beyond binary valid/invalid assessment, the Phase 1 specification defines three conformance levels based on data completeness and validation method. Higher-level submissions include recommended and optional fields that enhance processing efficiency even when not strictly required. Organizations claiming Level 2 or higher must undergo independent verification, and at every level they must implement the required fields and validation rules and submit sample data demonstrating conformance.

Privacy and Data Security Considerations

E-waste tracking must balance transparency with privacy protection. Consumer personal information should not be exposed through lifecycle tracking. The standard incorporates privacy-by-design principles including:

• Device identifiers contain no personal information
• Ownership and sale data encrypted and access-controlled
• Location data generalized (city-level, not addresses)
• Data retention policies limit historical storage
• Consumer rights to access and deletion supported
• GDPR and privacy framework compliance built-in

Extensibility and Future-Proofing

Technology evolves continuously, introducing new device types, materials, and processing methods. The data format standard accommodates this evolution through extensibility mechanisms that allow new fields and categories without breaking existing implementations.

Custom Field Extensions

Organizations can add custom fields using namespaced extensions that don't conflict with standard fields. To avoid collisions, extension namespaces must follow reverse-DNS notation. This allows industry-specific or experimental data collection while maintaining interoperability for core data.

{
  "device_id": "550e8400-e29b-41d4-a716-446655440000",
  "weee_category": "WEEE-6",
  "extensions": {
    "techcorp:internal_tracking": {
      "factory_batch": "FC7-2024-Q1",
      "qc_inspector": "QC-42",
      "custom_warranty_tier": "premium"
    },
    "recycler:condition_assessment": {
      "screen_condition": "excellent",
      "battery_health": 87,
      "reuse_score": 8.5
    }
  }
}

Version Migration Strategies

As the standard evolves, data must migrate between versions. The standard specifies migration procedures and provides tools for automatic conversion. Backward compatibility receives high priority—newer systems must interpret older data formats gracefully, though older systems may not understand newer features.