Developer Resources: NMOS BCP-008 Minimum Status Reporting

Here are developer resources for NMOS BCP-008 Minimum Status Reporting

• Implementers guide (INFO-006) where helpful developer checklists can be found

  
  

• nmos-control-scripty-client – IS-12/BCP-008 example client in Typescript/NodeJS

  
  

• nmos-device-control-mock – IS-12/BCP-008 example mock device in Typescript/NodeJs (also available as Docker container)
  

• nmos-js – IS-12/BCP-008 prototype client in Javascript

  
  

• nmos-cpp – fully tested library implementing IS-12/BCP-008

  (Here's the branch from the Nov 2025 BCP-08 workshop: jonathan-r-thorpe/nmos-cpp at amwa-workshop-2025 )
  

• sony/nmos-cpp: An NMOS (Networked Media Open Specifications) Registry and Node in C++ (IS-04, IS-05)
  

• sony/nmos-js: An NMOS (Networked Media Open Specifications) Client in Javascript (IS-04, IS-05)

  
  

• nmos-control-rusty-device – IS-12 example device in Rust

  
  

• nmos-control-serpenty-device – IS-12 example device in Python

  
  

• nmos-testing – API testing framework
  

––––––––––––––––––––––

A Bit About NMOS BCP-008 Minimum Status Reporting

When something stops working in a complex IP environment, the last thing you want to have to do is troubleshoot every piece of equipment – and likely go about 12 menus deep on each – to see what went wrong. 

Instead, if you had a simple dashboard that could show you the status of every device in your entire facility, you could root out the cause of the problem in seconds. With NMOS’s BCP-008, minimum status reporting – this simple traffic light system, you can have exactly that.  

The simple traffic light system goes beyond discovery, registration, and connection management (IS-04 and IS-05) to solve the problem of what happens when you don’t have a working signal, and you need to figure out why quickly. 

The NMOS Reporting domains are:

1- Connectivity, which includes 2 traffic lights: physical link and packet level. This could be a link down or some of the links down, or packets missing, being late, or lost (on receivers) or transmission errors of any kind (on senders).

2 - Synchronization, so is the expected synchronization present? If PTP is expected, is it there?.

3 - Stream Validation, which include issues with decoding the stream (on receivers) or invalid baseband signal to transmit (on senders).

If these 3 status reports are supported in every end device, you will be able to find most of your problems and target them quickly.