Anastasia Abrahim
  • Home
  • About Me
    • Resume
  • My Works
    • Agency File Management
    • Precision Plan Comparison
    • Rigel
    • Sony Sandbox
    • Motherboard
    • Client Config
    • Healix Global - External Website
    • Magna Global - External Website
    • Sample Site Maps Flows
    • Sample Workflow Diagrams
    • JIRA-Issued Story Artifacts
    • Product Documentation
    • Sample Deliverables from Past Roles

Sample Workflow Diagrams​

Cross-Platform Ecosystem – Process Flow

Cross-Platform Ecosystem – Overview & Process Flow

Overview

This is a macro-level architecture that explains how data flows through an enterprise media ecosystem:

  • Systems like WideOrbit, Bridge, and BI work together with digital tools (e.g., STAQ, Hulu, Amazon) and financial systems (e.g., SAP, MediaOcean).
  • Promotional materials, as-run logs, and impression data all loop back into a central record.
  • APIs connect everything — helping with:
    • Proposal creation
    • Optimized scheduling
    • Invoicing and performance reporting

Core System: WideOrbit

WideOrbit acts as the operational hub for planning, tracking, and monetizing campaigns. It manages:

  • Deal ingestion (via Proposal Generation Tool)
  • Schedules, flowcharts, and commercial plans
  • Optimized plan returns + linear invoice processing
  • Exchange of C3 data with partners (e.g., iSpot.tv)

Bridge Integration

  • Distributes schedules, logs, and plans to other systems
  • Manages promo timing, playlists, and as-runs
  • Handles 2E Material logic for delivery and invoicing

Business Intelligence (BI)

The BI platform plays a vital role in forecasting and deal analysis:

  • Handles ingest of planning + deal data
  • Supports estimates and competitive performance analytics
  • Enables digital order entry

Digital Systems & Distribution

  • Digital orders flow to partners (e.g., Hulu, Amazon, Amagi)
  • Digital invoices and aggregate data are generated and passed for billing
  • Digital assets are tracked via status updates from CRM and Operative

Series & Episode Metadata

  • Metadata for each episode flows between systems like MPX, Pilot, and CRM
  • Supports validation and delivery across linear + digital endpoints

External Dependencies

  • SAP – handles digital invoice execution
  • MediaOcean – supports reconciliation + campaign tracking
  • RSG, On-Air Pro, WOO – manage promo assets, mapping, and scheduling

Conclusion

This connected ecosystem automates every stage of a media campaign — from planning and trafficking to delivery and billing — across both linear and digital advertising environments.

Picture
Cross-Platform Ecosystem – Process Flow

Cross-Platform Ecosystem – Overview & Process Flow

Overview

This is a macro-level architecture that explains how data and automation move through the ecosystem:

  • Systems involved: WideOrbit, Bridge, BI Tools, digital partners (Hulu, STAQ, Amazon), and finance tools (SAP, MediaOcean).
  • Promotional logs and ad data loop back into the system of record.
  • APIs support end-to-end flow for:
    • Proposal creation
    • Automated scheduling
    • Billing and reporting

Core System: WideOrbit

WideOrbit is the source of truth for media planning and billing. It manages:

  • Importing and validating media deals
  • Air schedules, flowcharts, and commercial instructions
  • Optimized plans and invoice generation
  • Integration with measurement vendors (e.g., iSpot.tv)

Bridge Integration

  • Shares data like schedules and logs across platforms
  • Supports promo timing and playlist syncing
  • Helps prep for scheduling and invoice handoff

Business Intelligence (BI)

BI systems support decisions by analyzing:

  • Deal and media data from sales and campaigns
  • Market estimates and competitive analysis
  • Digital plan creation and forecasting

Digital Systems & Distribution

  • Orders are delivered to digital partners (Hulu, TEGNA, Amagi, etc.)
  • Digital invoices and rollups are created for reporting
  • Asset delivery status is synced with CRM and ad ops tools

Series & Episode Metadata

  • Episode metadata flows from content systems (MPX/Pilot) to CRM
  • Each episode is validated and prepped for both linear and digital channels

External Dependencies

  • SAP – powers digital invoice delivery
  • MediaOcean – tracks media spend and handles reconciliation
  • RSG, On-Air Pro, WOO – manage promos, titles, and schedules

Conclusion

This connected ecosystem ensures that ad campaigns are planned, tracked, executed, and billed without manual bottlenecks — no matter the channel (TV or digital).

Picture

Calculation with Deal Types – Flow Overview

Calculation with Deal Types – Decision Logic

Overview

This logic helps the system decide where to place ad spots, based on:

  • The type of deal (like Linear, Programmatic, DR, or Precision)
  • Whether the time is considered Prime or Non-Prime
  • Whether the placement is ROS (Run-of-Schedule) or for a specific program

It uses checkpoints to ensure that spots are accurately marked as either Placed or Available — so that media inventory is used correctly and efficiently.

1. Deal Type Entry Points

The system first checks the type of incoming deal. Then it splits them into two categories:

  • Prime – High-demand time slots
  • Non-Prime – Lower-priority time slots

Each follows its own validation rules.

2. Non-Prime Path

  • Checks if the deal is Open Market or Program-Specific
  • Reviews if it fits ROS or DR ROS logic
  • If it matches a known priority code (ST, BD, AN, etc.), it is Placed
  • If it doesn’t match any criteria, it remains Available

3. Prime Path

  • Performs additional validation for:
    • Program-specific targeting
    • ROS or DR ROS eligibility
    • Priority and demographic matching
  • If all checks pass, it is Placed; otherwise, it stays Available

4. Placement Validation

  • Codes are used to validate placement:
    • Valid: ST, BD, AN, APL, VDR, RCR
    • Need review: SHW, PCP, MLD, AIW
  • Precision placements also check for audience targeting and inventory match

5. Final Outcomes

  • Placed – Spot is locked in and inventory is committed
  • Available – Spot is not yet taken and remains open

Note: This logic helps keep planning accurate, avoids double-booking, and ensures the right spots go to the right campaigns — whether guaranteed or opportunistic.

Picture
Open Market File Logic

Open Market File – Logic Flow Description

Overview

This logic defines how ad inventory is added to the Open Market Inventory File:

  • Checks if a ROS (Run of Schedule) title is already in the log.
  • Uses Day of Week, Daypart, and Hour to match selling titles.
  • Determines if a matching title is in flight (active).
  • Then decides whether to:
    • Add it as a selling title
    • Skip it entirely
    • Assign a max of 2 avails or 0

1. Initial Evaluation

  • Is the ROS title already on the log?
    • Yes → Add as a Selling Title with up to 2 avails
    • No → Continue to the next step

2. National Time Check

  • Does the file contain National Time (calculated avails)?
    • Yes → Cross-reference Selling Titles using day/time logic
    • Check if a title is in flight:
      • Yes → Add with max avails
      • No → Do not add to the file

3. Fallback Logic

  • If no National Time:
    • Repeat the title match checks using daypart data
    • Check if in flight:
      • Yes → Add but assign 0 avails
      • No → Skip adding to file

Key Notes

  • Only titles marked “in flight” are eligible for file inclusion
  • Logic ensures clean and accurate avails – no duplication or overfill
  • Each entry is tied to a valid Daypart to ensure precision

Conclusion

This logic ensures inventory is cleanly managed and up-to-date by including only eligible, flighted ROS titles — preserving the accuracy of sales data and avoiding unnecessary clutter in Open Market files.


Picture
Calculation for Precision and Open Market

Calculation for Precision and Open Market – Flow Overview

Precision vs. Open Market – Placement Logic

This logic helps the system decide how to place ads: should it go into Precision inventory or the Open Market?

  • First question: Is the ad spot already on the log?
  • Then, we check:
    • What kind of market it is (Open / Prime / Non-Prime)
    • What kind of deal (ROS, DR ROS, Program-Specific)
    • If a valid priority code is attached
  • Finally, we decide if that ad should be marked as Placed or still Available.

Overview

The system looks at the type of deal and inventory and applies rules based on:

  • Prime vs. Non-Prime time
  • Deal category: ROS, DR ROS, Program Specific
  • Priority code match (like ST, BD, AN, APL, VDR, RCR)

If the ad meets all the rules, it’s marked Placed. If not, it stays Available.

1. Spot Placement Decision

  • Is the spot already on the log?
  • If not, check for Open Market eligibility.
  • Categorize the inventory as:
    • Prime
    • Non-Prime

2. Non-Prime Path (Open Market)

  • Check deal type: ROS, DR ROS, or Program Specific
  • If it's DR ROS and no match: mark as Available
  • If it has a valid priority code: mark as Placed
  • If no code matches: mark as Available

3. Prime Path

  • Same checks as Non-Prime, but stricter validation
  • Use priority codes and program targeting to validate
  • If valid: mark Placed, otherwise Available

4. Decision Factors

  • Placed: Meets all criteria — good to go!
  • Available: Doesn't meet full criteria yet

Key Considerations

  • Works for both Direct Response and Programmatic deals
  • Checks inventory alignment with daypart and targeting rules
  • Keeps placement fair, automated, and contract-compliant

Conclusion

This smart logic ensures each ad is placed only if it follows the rules. It balances client goals with inventory availability, while keeping everything clean and automated.


Picture

Proposal Creation Workflow

Proposal Creation Workflow

Proposal Creation Overview

This flow outlines the step-by-step process of creating a media proposal and covers both digital and linear workflows:

  • External Process: Starts with RFPs, rate card analysis, and budget/flighting plans submitted by agencies.
  • Digital Ad Sales Applications: Use systems to build a proposal from Opportunity → Plan → Avail validation.
  • Linear Sales Applications: Use WideOrbit and Bridge to support deal setup, optimization, and historical comparison.

This unified process ensures all teams — digital and traditional — stay aligned from planning to proposal delivery.

1. External Processes

  • Review past performance data
  • Create forecasts, demos, and rate cards
  • Sales teams review RFPs and negotiate
  • Agencies submit budgets and flight schedules

2. Digital Ad Sales Applications

  • Create Digital Opportunities within CRM or media platform
  • Develop Media Plans to match client goals and spend
  • Validate against Inventory Avails to ensure deliverability

3. Linear Ad Sales Applications (WideOrbit)

  • Set up Master Deal and plan header
  • Optimize the plan using system data and traffic inputs
  • Revise the plan if inventory or client feedback changes
  • Use Bridge for historical Plan Comparison

Key Benefit

This process gives the sales team confidence in what they present to clients — it’s strategic, backed by data, and compliant with available inventory and delivery logic.


Picture
Proudly powered by Weebly
  • Home
  • About Me
    • Resume
  • My Works
    • Agency File Management
    • Precision Plan Comparison
    • Rigel
    • Sony Sandbox
    • Motherboard
    • Client Config
    • Healix Global - External Website
    • Magna Global - External Website
    • Sample Site Maps Flows
    • Sample Workflow Diagrams
    • JIRA-Issued Story Artifacts
    • Product Documentation
    • Sample Deliverables from Past Roles