OpenText Decision Service - Overcast HQ Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and Overcast HQ

1. Rights-based media approval before transcoding and distribution

Flow: Overcast HQ ? OpenText Decision Service ? Overcast HQ

When a new video asset is ingested into Overcast HQ, metadata such as territory, talent, music rights, campaign dates, and usage restrictions is sent to OpenText Decision Service. The decision engine evaluates whether the asset can be transcoded, published, or routed for legal review based on business rules. The approval or rejection result is returned to Overcast HQ to continue processing or place the asset in a hold state.

Business value: Prevents accidental distribution of content that is not cleared for use, reduces legal and compliance risk, and eliminates manual rights checks by operations teams.

• Automates content clearance decisions
• Blocks unauthorized publishing early in the workflow
• Supports frequent rule updates without code changes

2. Automated routing of premium content to specialized processing paths

Flow: Overcast HQ ? OpenText Decision Service ? Overcast HQ

Overcast HQ can send asset attributes such as file type, resolution, client tier, language, or live event status to OpenText Decision Service. The rules engine determines whether the asset should follow a standard transcoding path, a high-priority processing queue, or an exception workflow for premium customers or live content. The decision is returned to Overcast HQ to trigger the correct processing profile.

Business value: Improves turnaround time for high-value content, optimizes compute usage, and ensures service-level commitments are met for priority clients and live productions.

• Routes assets based on business priority
• Supports differentiated service levels
• Reduces manual queue management

3. Policy-driven AI tagging approval and enrichment control

Flow: Overcast HQ ? OpenText Decision Service ? Overcast HQ

Overcast HQ generates AI-driven tags for scenes, speakers, brands, or objects. Before those tags are written back to the master metadata record or pushed to downstream systems, OpenText Decision Service evaluates whether the tags meet policy thresholds. For example, it can require human review for sensitive topics, enforce approved taxonomies, or suppress tags that conflict with editorial rules.

Business value: Improves metadata quality, reduces misinformation in search and distribution systems, and gives content governance teams control over automated enrichment.

• Applies governance to AI-generated metadata
• Flags sensitive or low-confidence tags for review
• Keeps taxonomy usage consistent across teams

4. Exception handling for failed transcoding and media quality issues

Flow: Overcast HQ ? OpenText Decision Service ? Overcast HQ

When Overcast HQ detects a failed transcode, unsupported format, or quality issue, it sends the failure context to OpenText Decision Service. The rules engine determines the next action based on asset type, customer importance, retry history, and failure category. It may instruct Overcast HQ to retry with an alternate profile, escalate to operations, or create a case for manual intervention.

Business value: Reduces downtime, standardizes exception handling, and helps operations teams focus on true exceptions instead of routine failures.

• Automates retry and escalation decisions
• Improves media pipeline resilience
• Creates consistent handling for recurring errors

5. Distribution eligibility checks for channel and platform publishing

Flow: Overcast HQ ? OpenText Decision Service ? Overcast HQ

Before Overcast HQ sends content to a CMS, DAM, or external distribution endpoint, it can request a decision from OpenText Decision Service using metadata such as audience rating, region, campaign status, and embargo date. The rules engine confirms whether the asset is eligible for each target channel and returns the approved destinations. Overcast HQ then publishes only to permitted endpoints.

Business value: Prevents publishing mistakes, supports channel-specific compliance, and ensures content is distributed only where it is authorized and relevant.

• Controls destination-specific publishing rules
• Supports embargo and regional restrictions
• Reduces rework from incorrect distribution

6. Revenue-based prioritization for sponsored and campaign content

Flow: Overcast HQ ? OpenText Decision Service ? Overcast HQ

Marketing or media operations teams can classify incoming assets in Overcast HQ by campaign, sponsor, or monetization value. OpenText Decision Service applies business rules to determine whether the content should receive accelerated processing, premium storage, enhanced analytics, or immediate distribution. The decision is returned to Overcast HQ to adjust workflow priority automatically.

Business value: Aligns media operations with revenue goals, improves sponsor satisfaction, and ensures high-value content is handled with appropriate urgency.

• Prioritizes monetized content automatically
• Supports campaign-level service rules
• Improves operational alignment with commercial teams

7. Bi-directional governance for content lifecycle decisions

Flow: Overcast HQ ? OpenText Decision Service

Overcast HQ can send lifecycle events such as ingest, edit completion, publish, archive, or deletion request to OpenText Decision Service. In return, the rules engine can approve, deny, or conditionally route the action based on retention policy, legal hold status, customer contract terms, or content sensitivity. This bi-directional integration ensures that media lifecycle actions are governed consistently across the organization.

Business value: Strengthens compliance, reduces risk around retention and deletion, and gives legal, operations, and content teams a shared decision framework.

• Applies policy to archive and deletion actions
• Supports legal hold and retention enforcement
• Creates a consistent governance layer across workflows