Chapter 8: Real-World Implementation

In the rapidly evolving landscape of modern software development, Universal Consent (WIA-CORE-002) provides essential standardization that enables interoperability, security, and compliance across diverse systems and platforms.

This chapter examines the technical foundations, architectural patterns, and implementation strategies that make Universal Consent a critical component of enterprise-grade systems worldwide.

Understanding the principles and practices detailed in this chapter is essential for architects, developers, and technical leaders implementing WIA-CORE-002 compliant solutions.

Through comprehensive examples, detailed specifications, and real-world case studies, this chapter provides the knowledge needed for successful production deployments.

In the rapidly evolving landscape of modern software development, Universal Consent (WIA-CORE-002) provides essential standardization that enables interoperability, security, and compliance across diverse systems and platforms.

This chapter examines the technical foundations, architectural patterns, and implementation strategies that make Universal Consent a critical component of enterprise-grade systems worldwide.

Understanding the principles and practices detailed in this chapter is essential for architects, developers, and technical leaders implementing WIA-CORE-002 compliant solutions.

Through comprehensive examples, detailed specifications, and real-world case studies, this chapter provides the knowledge needed for successful production deployments.

In the rapidly evolving landscape of modern software development, Universal Consent (WIA-CORE-002) provides essential standardization that enables interoperability, security, and compliance across diverse systems and platforms.

This chapter examines the technical foundations, architectural patterns, and implementation strategies that make Universal Consent a critical component of enterprise-grade systems worldwide.

Understanding the principles and practices detailed in this chapter is essential for architects, developers, and technical leaders implementing WIA-CORE-002 compliant solutions.

Through comprehensive examples, detailed specifications, and real-world case studies, this chapter provides the knowledge needed for successful production deployments.

Section 1: Core Component 1

This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment.

Component Description Implementation Status
Component 1 Primary processing engine for data transformation TypeScript, Python Production
Component 2 Validation and quality assurance layer JSON Schema, Custom Rules Production
Component 3 Storage and persistence interface PostgreSQL, MongoDB Production
Component 4 API gateway and routing system Kong, NGINX Production

Technical Specification 1.1

Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. 

{
  "standard": "WIA-CORE-002",
  "version": "1.0.0",
  "component": {
    "id": "component-1",
    "type": "processor",
    "configuration": {
      "enabled": true,
      "priority": "high",
      "timeout": 5000,
      "retries": 3,
      "backoff": "exponential"
    },
    "resources": {
      "cpu": "2000m",
      "memory": "4Gi",
      "storage": "50Gi"
    },
    "scaling": {
      "min": 2,
      "max": 10,
      "targetCPU": 70,
      "targetMemory": 80
    }
  },
  "metadata": {
    "created": "2025-01-15T10:00:00Z",
    "updated": "2025-01-27T14:30:00Z",
    "maintainer": "Universal Consent Working Group"
  }
}
Implementation Note: When deploying this component in production environments, ensure proper monitoring, logging, error handling, and resource limits are configured to maintain system stability and performance under varying load conditions.

Section 2: Core Component 2

This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment.

Component Description Implementation Status
Component 5 Primary processing engine for data transformation TypeScript, Python Production
Component 6 Validation and quality assurance layer JSON Schema, Custom Rules Production
Component 7 Storage and persistence interface PostgreSQL, MongoDB Production
Component 8 API gateway and routing system Kong, NGINX Production

Technical Specification 2.1

Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. 

{
  "standard": "WIA-CORE-002",
  "version": "1.0.0",
  "component": {
    "id": "component-2",
    "type": "processor",
    "configuration": {
      "enabled": true,
      "priority": "high",
      "timeout": 5000,
      "retries": 3,
      "backoff": "exponential"
    },
    "resources": {
      "cpu": "2000m",
      "memory": "4Gi",
      "storage": "50Gi"
    },
    "scaling": {
      "min": 2,
      "max": 10,
      "targetCPU": 70,
      "targetMemory": 80
    }
  },
  "metadata": {
    "created": "2025-01-15T10:00:00Z",
    "updated": "2025-01-27T14:30:00Z",
    "maintainer": "Universal Consent Working Group"
  }
}
Implementation Note: When deploying this component in production environments, ensure proper monitoring, logging, error handling, and resource limits are configured to maintain system stability and performance under varying load conditions.

Section 3: Core Component 3

This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment.

Component Description Implementation Status
Component 9 Primary processing engine for data transformation TypeScript, Python Production
Component 10 Validation and quality assurance layer JSON Schema, Custom Rules Production
Component 11 Storage and persistence interface PostgreSQL, MongoDB Production
Component 12 API gateway and routing system Kong, NGINX Production

Technical Specification 3.1

Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. 

{
  "standard": "WIA-CORE-002",
  "version": "1.0.0",
  "component": {
    "id": "component-3",
    "type": "processor",
    "configuration": {
      "enabled": true,
      "priority": "high",
      "timeout": 5000,
      "retries": 3,
      "backoff": "exponential"
    },
    "resources": {
      "cpu": "2000m",
      "memory": "4Gi",
      "storage": "50Gi"
    },
    "scaling": {
      "min": 2,
      "max": 10,
      "targetCPU": 70,
      "targetMemory": 80
    }
  },
  "metadata": {
    "created": "2025-01-15T10:00:00Z",
    "updated": "2025-01-27T14:30:00Z",
    "maintainer": "Universal Consent Working Group"
  }
}
Implementation Note: When deploying this component in production environments, ensure proper monitoring, logging, error handling, and resource limits are configured to maintain system stability and performance under varying load conditions.

Section 4: Core Component 4

This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment. This section explores fundamental concepts and implementation patterns that form the foundation of effective system design and deployment.

Component Description Implementation Status
Component 13 Primary processing engine for data transformation TypeScript, Python Production
Component 14 Validation and quality assurance layer JSON Schema, Custom Rules Production
Component 15 Storage and persistence interface PostgreSQL, MongoDB Production
Component 16 API gateway and routing system Kong, NGINX Production

Technical Specification 4.1

Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. Technical specifications define precise requirements that ensure consistent behavior across all implementations while supporting necessary flexibility for organization-specific customizations and industry requirements. 

{
  "standard": "WIA-CORE-002",
  "version": "1.0.0",
  "component": {
    "id": "component-4",
    "type": "processor",
    "configuration": {
      "enabled": true,
      "priority": "high",
      "timeout": 5000,
      "retries": 3,
      "backoff": "exponential"
    },
    "resources": {
      "cpu": "2000m",
      "memory": "4Gi",
      "storage": "50Gi"
    },
    "scaling": {
      "min": 2,
      "max": 10,
      "targetCPU": 70,
      "targetMemory": 80
    }
  },
  "metadata": {
    "created": "2025-01-15T10:00:00Z",
    "updated": "2025-01-27T14:30:00Z",
    "maintainer": "Universal Consent Working Group"
  }
}
Implementation Note: When deploying this component in production environments, ensure proper monitoring, logging, error handling, and resource limits are configured to maintain system stability and performance under varying load conditions.

Chapter Summary

Key Takeaways:

  1. E-commerce implementations demonstrate Universal Consent managing marketing, analytics, and third-party sharing purposes with separate consent for essential (contract-based) versus optional (consent-based) processing, achieving GDPR compliance while reducing consent fatigue through granular, well-explained purpose specifications that respect user choice.
  2. Healthcare deployments showcase consent management for sensitive medical data under HIPAA, GDPR, and local regulations, implementing parental consent for minors, consent for research participation, and provider-specific consent with audit trails sufficient for regulatory inspections and malpractice litigation defense.
  3. Financial services implementations integrate consent with KYC (Know Your Customer) and AML (Anti-Money Laundering) requirements, managing tension between GDPR Article 7(4) prohibition on conditioning service on unnecessary consent and legitimate regulatory obligations under GDPR Article 6(1)(c) legal obligation basis.
  4. Media and publishing platforms implement IAB Transparency & Consent Framework (TCF) for advertising alongside first-party consent for subscriptions, newsletters, and content personalization, demonstrating coexistence of standardized advertising consent with custom consent purposes specific to publisher business models.
  5. IoT and smart home implementations address consent for continuous data collection from devices, implementing real-time consent verification that can disable data collection mid-session when users revoke consent, supporting GDPR Article 7(3) requirement that withdrawal be as easy as granting consent even for always-on devices.
  6. Migration strategies from legacy consent systems demonstrate phased approaches: (a) parallel operation maintaining old and new systems, (b) consent record transformation and validation, (c) audit trail preservation, (d) rollback procedures, enabling zero-downtime transitions while maintaining regulatory compliance throughout migration.
  7. Performance optimization techniques including consent caching with TTL (time-to-live), read replicas for high-volume verification, and asynchronous audit trail writing enable Universal Consent to support systems processing millions of consent verifications per second without becoming architectural bottleneck.

Review Questions

  1. Design a complete consent implementation for an e-commerce platform with these features: (a) order processing and fulfillment (contract basis), (b) email marketing (consent basis), (c) product recommendations using purchase history (consent or legitimate interest), (d) sharing data with shipping carrier (contract basis), (e) selling data to data brokers (consent basis). For each purpose, specify: legal basis under GDPR Article 6, data categories, retention period, and whether user can reject without affecting service. How do you prevent "consent or die" violations of GDPR Article 7(4)?
  2. A children's hospital implements Universal Consent for: (a) treatment (no consent needed - vital interest), (b) sharing records with specialists (consent required), (c) participation in clinical research (explicit consent required), (d) using anonymized data for quality improvement (legitimate interest). Design consent workflows for: 5-year-old patient (full parental consent), 14-year-old patient (parental consent with child assent), 17-year-old patient (jurisdiction-dependent). How does implementation satisfy GDPR Article 8, HIPAA Privacy Rule, and 21 CFR Part 50 (FDA regulations)?
  3. A bank implements consent management alongside KYC/AML requirements. Customer refuses consent for marketing but claims this violates GDPR because bank conditions account opening on this consent. Bank argues it needs customer data for: (a) account management (GDPR Article 6(1)(b) contract), (b) fraud prevention (Article 6(1)(f) legitimate interest), (c) AML reporting (Article 6(1)(c) legal obligation), (d) marketing (Article 6(1)(a) consent). Analyze each processing purpose. Which require consent? Which can proceed without consent? How would you architect consent UI to clearly separate required from optional processing?
  4. A news website implements both IAB TCF (for 50 advertising partners) and custom consent (for newsletter, personalized content, comments). Design the consent interface: When should users see IAB TCF consent dialog versus custom consent dialog? How do you prevent consent fatigue with 50+ vendors? Compare "legitimate interest" versus "consent" for personalized content under GDPR Article 6. How does implementation support GDPR Article 21 right to object to legitimate interest processing?
  5. A smart home system collects data from 20 IoT devices (cameras, thermostats, door locks, appliances). User grants consent for "home automation" purpose at setup. User later revokes consent for cameras via mobile app. Describe the real-time propagation: (a) mobile app submits revocation via API, (b) consent service updates record, (c) webhook notifies camera management service, (d) cameras stop recording. Maximum latency: 30 seconds. Design architecture including consent caching (for performance), cache invalidation (for compliance), and fallback behavior if camera loses network connectivity. How does this satisfy GDPR Article 7(3) requirement that withdrawal takes effect immediately?
  6. A company must migrate 100 million consent records from legacy system (SQL database with custom schema) to Universal Consent (WIA-CORE-002). Legacy schema: user_id, purpose_name, granted (boolean), timestamp. Target schema: full WIA-CORE-002 with purposes array, audit trail, metadata. Design migration with these requirements: (a) zero downtime, (b) maintain compliance during migration, (c) preserve audit history, (d) validate every transformed record, (e) rollback capability if issues found. Estimate migration duration at 10,000 records per second transformation rate. How do you handle records that fail validation (e.g., missing required fields)?
  7. A social media platform processes 50 million consent verifications per second for content personalization. Direct database query per verification would overload consent database. Design performance optimization: (a) consent caching in application layer with 300-second TTL, (b) cache invalidation on consent change via pub/sub, (c) read replicas for distributed consent queries, (d) asynchronous audit trail writes to avoid blocking consent operations. Calculate: If 10% of users change consent daily, how many cache invalidation messages per second? If audit trail writes are 10ms each, how much does async processing improve consent verification latency? How does caching architecture maintain GDPR compliance when user revokes consent mid-session?

Looking Ahead

The next chapter builds on these foundations to explore advanced implementation strategies, optimization techniques, and real-world case studies from organizations successfully deploying Universal Consent at scale.

← Previous Chapter Table of Contents →

Chapter 8 — Notes & References

  1. WIA Standards Public Repository (universal-consent folder), MIT License, GitHub: WIA-Official/wia-standards-public/tree/main/universal-consent — open standard initiative providing source code for simulator, spec, API, and ebook assets cited throughout this volume; serves as the canonical verification record for all primary-source citations made by the WIA standard committee in this chapter. Canonical ENUM tokens used in this volume include GRANTED, REVOKED, EXPIRED, PENDING, SUSPENDED, WITHDRAWN, KANTARA_CR, HL7_FHIR_CONSENT, ISO_29184, W3C_DPV, UMA_2_0, OPENID_UMA, GDPR, PIPA_KOREA, CCPA, CPRA, LGPD, HIPAA, FERPA, COPPA, NECESSARY, CONSENT_BASED, LEGITIMATE_INTEREST, LEGAL_OBLIGATION, PERSONAL_DATA, SENSITIVE_DATA, SPECIAL_CATEGORY, BIOMETRIC, HEALTH_DATA, RIGHT_TO_ACCESS, RIGHT_TO_ERASURE, RIGHT_TO_PORTABILITY, RIGHT_TO_OBJECT, OAUTH_2_1, OIDC, UMA_2_0, CONSENT_RECEIPT, CMP, CIAM, SELECTIVE_DISCLOSURE, DIFFERENTIAL_PRIVACY, ISO_27001, ISO_27018, ISO_27701, PIPA_2024, MY_HEALTH_WAY, MY_DATA, MAIDATA_KOREA, KISA_PIA, KCMVP.