Overview

MOS (Media Object Server) protocol connects your newsroom system (iNews, ENPS, Octopus) to Kinetica. When a journalist adds a graphics item to a story in the NRCS, MOS pushes it into the Kinetica rundown automatically.

Setting Up a MOS Receiver

1. Click + Receiver and give it a name (e.g. "Studio A")
2. Set the MOS ID to match what your NRCS expects (e.g. KINETICA.MOS)
3. Set the NCS ID to your newsroom's ID (e.g. ENPS.NCS) — optional but recommended
4. Leave ports at defaults (10540/10541) unless your network requires different ports
5. Click Start to begin listening for MOS connections
6. Under Linked Outputs, link the receiver to an overlay instance — this is where rundown items will appear

How Items Flow

When a journalist drags a Kinetica template into an iNews story:

1. iNews sends a MOS roStorySend or roItemInsert to the receiver
2. Kinetica matches the MOS item to a template by slug or mosAbstract
3. A rundown item is created on the linked output with any data field overrides from the NRCS
4. The item appears in the Live Rundowns panel, ready for an operator to CUE and TAKE

Edits in the NRCS update the rundown item in real time. Deleting the story item removes it from the rundown.

MOS Auto-Take

When MOS Auto-Take is enabled on an output instance (right-click the output in Live Rundowns), the NRCS can fire graphics directly:

• MOS PLAY command → takes the item on-air
• MOS STOP command → takes the item off-air

Using with Ross Overdrive

Overdrive integrates with Kinetica through two separate automation systems. Content must reach Kinetica before Overdrive can fire it — how that happens depends on your network.

Automation systems

Template Editor (CII) — direct CG control per buffer/instance:

Template Editor fires items via CII using the MOS item ID as the page reference. Set up the CII listener and buffer mappings on the Overdrive page.

Caprica (RossTalk) — global trigger by automation ID:

Caprica fires items globally — TAKE, CUE, CLFB — searching all automation-enabled instances. Set up the RossTalk listener on the RossTalk page.

Content delivery paths

Path A — Standard (MOS TCP): iNews pushes items to Kinetica via this MOS receiver. Requires TCP 10540/10541 open between iNews and Kinetica.

• CII: the receiver output must be linked to the same overlay instance as the CII buffer mapping — this is how CII resolves the KIN-xxx item ID to an instance
• RossTalk: enable Automation on each instance Caprica should be able to trigger

Path B — Direct Push (Restricted Network): If iNews cannot reach Kinetica via MOS TCP, the NRCS panel pushes items directly to Kinetica via HTTPS. No MOS receiver is needed for content delivery — this MOS page is not required for Path B.

• Direct Push is enabled by default — no extra URL parameter needed. Configure the NRCS plugin token on the NRCS Plugin page
• iNews still stores the MOS XML (Overdrive reads the item ID from it), but Kinetica gets the item via HTTPS
• CII and RossTalk playout is identical — the item is in Kinetica either way

Both automation systems (CII and RossTalk) can run simultaneously with either content delivery path.

Template Matching

Kinetica matches incoming MOS items to templates in this order:

1. Explicit template ID in mosExternalMetadata
2. Template slug from mosExternalMetadata
3. mosAbstract field matched against template slugs
4. objSlug field matched against template slugs

Set the MOS Item Slug on your templates (Templates page) to match what your NRCS sends.

Troubleshooting

• No connection from NRCS — Check that the MOS ID matches exactly, and that ports 10540/10541 are reachable from the NRCS server
• Items not appearing — Check the Running Orders section below. If the RO appears but items don't, the template slug likely doesn't match
• Wrong output — Verify the correct output is linked and set as active under Linked Outputs