I spent a day inside Sony's RDX platform. Here's the short version.
Sony has a GraphQL federation platform called RDX that connects every backend system across SME. Release data, workability scores, clearance records, DSP partner info, catalog metadata — it's all queryable from one place. It's live. It's accessible. Nobody at RCA is using it.
I confirmed these in the staging environment — real queries, real schema:
| Capability | What It Returns | Status |
|---|---|---|
| Release Workability | All 9 KPI scores, alert thresholds, per-release breakdown | Works |
| DSP Catalog (SCUBA) | Spotify/Apple/Deezer — ISRCs, popularity, genres, followers | Works |
| Partner Delivery | Per-DSP pitch dates, lead times, week-one forecasts | Schema ✓ |
| Clearance Records | Sample clearance + master clearance by ISRC | Needs Prod |
| RCA-Only Filter | Filter all queries to RCA releases only (label key E009) | Needs Prod |
I pulled the workability export on Sunday. Across all 113 scheduled releases:
SAA is "Unknown" on every single release. SAMP is Unknown on every release. Agreements is "Required" on every release. DSN Received is blank on every release. Not most — all 113.
The data to fill these gaps likely already exists upstream in Sony's clearance and repertoire systems. RDX can reach it. Nobody at RCA is reading it. That's what Campaign Ops fixes.
Two things. Neither requires budget or new headcount.
We don't need to build the pipes. Sony already built them. We need someone to read the water and translate it into action. That's Campaign Ops. The queries are written, the schema is confirmed, the proof point is sitting in the export. I just need production access to make it real.