AVEVA
Who is AVEVA?
AVEVA is a global leader in industrial intelligence software, helping enterprises design and build plants, operate through real-time operations and digital twins, and optimize industrial ecosystems with AI and analytics, sustainably and securely. AVEVA is trusted by over 90% of the Fortune 500, supporting organizations ranging from Starbucks to Shell.
Within AVEVA, the creative studio and content operations teams use Wrike as the operational backbone for intake, workflows, and approvals, with MediaValet as the single source of truth for published assets and metadata.
Location:
Cambridge, UK
Industry:
Technology
Company size:
Enterprise
Joined MediaValet:
2022
Features:
Wrike Integration
CDN Links
Metadata Automation
The Challenges
The Results
The Challenges
Fragmented tools, email approvals, and “version chaos”
Before AVEVA built its connected workflow, content creation and distribution lived across disconnected systems. Requests and approvals often happened in email, with assets spread across SharePoint sites, spreadsheets, and other storage tools, making it difficult to track status, control versions, and publish confidently.
Key challenges included:
- Approval bottlenecks and ambiguity: Email-based approvals created confusion. The team had unclear sign-offs, missed stakeholders, and poor audit trails.
- Version control across multiple platforms: Multiple copies of the same asset existed in different places, increasing the risk of teams using outdated materials.
- Operational drag from manual work: Teams spent significant time downloading, uploading, moving files between clouds, and re-entering metadata.
- Localization complexity: As content versions multiplied across languages, managing and locating the right versions became exponentially harder.
- No single source of truth: Teams created “mini content stores” across SharePoint locations, making search and governance difficult.
AVEVA’s studio was producing up to 250GB of content per month, and the existing process wasn’t built to support a global, high-volume content operation.
The Use Case
A connected content supply chain
AVEVA designed a structured content supply chain anchored by Wrike for workflow execution and approvals, and MediaValet for publishing, metadata consistency, and enterprise-wide access.
Wrike (upstream): Wrike serves as the system of work for content requests, project execution, collaboration, and approvals. AVEVA uses Wrike’s approval functionality to ensure every asset is reviewed by the right stakeholders, with an auditable trail of who approved what and when, aligned with internal governance.
MediaValet (center): MediaValet acts as AVEVA’s single source of final published truth and a single source of metadata truth. Only final, approved assets move from Wrike into MediaValet; ensuring internal teams, agencies, and global stakeholders access the correct “published” version.
Downstream distribution: From MediaValet, AVEVA distributes assets into key downstream systems (web, sales enablement, marketing platforms, video platforms) using integration technology. A core enabler is the MediaValet asset ID, which helps teams keep assets connected and updateable across platforms.
Stakeholder alignment built in: The workflow supports content owners, requesters, approvers, platform owners, agencies, and internal governance, making collaboration possible at scale without losing control.
Integrating Content Ecosystem with DAM & AI
The future of content operations is about activating content across a connected ecosystem with DAM and AI at the core.
Key Features
Driving success with Wrike, metadata and CDN Linking
Wrike
BluePrints
AVEVA standardized project execution using Wrike blueprints. Rather than overly complex subtask trees, they simplified workflow structure to one task per team (e.g., editorial, design, video, web, social, publishing). This created easier handoffs, and a consistent path from creation to final publication.
Request Forms
AVEVA built a single intake form that routes users through the right path based on what they’re requesting (e.g., video, brochure, white paper). Users only see a few pages while the underlying logic handles routing, governance, and structure.
Crucially, the form captures key metadata before content is even created:
- Asset type
- Sensitivity / usage rights
- Owner team
- Industries and other classifications
- This “front-loads” tagging and reduces manual effort later.
Publishing to the DAM
With the Wrike and MediaValet integration, publishing approved assets into the DAM becomes a fast, repeatable step and removes the need for manual downloading, uploading, or re-entering metadata. AVEVA estimates that they’ve reduced publishing time by about 80%.
Metadata Automation
AVEVA aligned Wrike custom fields with MediaValet attributes so metadata flows consistently from intake through to publishing. With fields standardized, users don’t have to learn different “taxonomy languages” across platforms and the DAM remains searchable and governed.
CDN Links
Instead of pushing large files into platforms not designed to host them (like websites), AVEVA uses MediaValet CDN links allowing downstream experiences (like web video playback) to reference DAM-hosted assets directly. This keeps files managed in one place and eliminates redundant storage across platforms.
The Results
Days of time saved, and faster publishing across global teams
By connecting Wrike and MediaValet into a unified content supply chain, AVEVA reduced friction at multiple points in their workflow. From intake and approvals to publishing and distribution the team has saved a tonne of time.
With approximately 3,500 content requests processed annually, AVEVA worked with their Wrike CSM to calculate time savings. They compared task completion times before and after automation to validate the numbers.
Estimated annual time savings include:
| Area | Time Saved Annually |
| Automated custom-field handling & governance workflows | 17 days |
| Automating Wrike into MediaValet publishing vs manual upload | 36 days |
| Structured intake forms replacing email submissions and capturing metadata | 35 days |
| Wrike proofing and approvals across teams | 323 days (collective) |
Beyond time savings, the organization gained:
Next Steps
Whats next for AVEVA?
AVEVA is continuing to mature its content supply chain by reducing manual “hops” between systems and expanding automation.
Planned next steps include:
Ready to see what the DAM hype’s about?
Meet with one of our product experts