Tags

Filter the specification index by document type or theme. Select a tag to see its matching specifications.

BCP

• BCP-002 — NMOS Resource Annotation
• BCP-002-01BCP-002-01What does it do?• Documents best practice and recommendations for how to indicate and handle "Natural Groups" of Resources in AMWA NMOS APIs.• These are those created by the default operation of a Node/Device, and not user- or automation-defined Groups.Why does it matter?• Provides a consistent way of referring to groups of related Resources (e.g. video and audio Senders of a camera)• This helps with interoperability and integration.How does it work?• Nodes add a grouphint tag to the JSON representation of each member of a Natural Group. — BCP-002-01
• BCP-002-02BCP-002-02What does it do?• It defines how to provide human-readable distinguishing information for NMOS Assets - Nodes and Devices.Why does it matter?• Inconsistent naming approaches across vendors and products can complicate configuration and operation.How does it work?• It defines tags for fixed information about Nodes and Devices.• These include Manufacturer, Product Name, Instance Identifier, and (for Devices only) Function. — BCP-002-02
• BCP-003 — NMOS API Security Recommendations
• BCP-003-01BCP-003-01What does it do?• Documents best practice for using secure transport for NMOS API communications.Why does it matter?• A secure control plane is essential.• Need to ensure encryption is sufficient.• These recommendations allow interoperability using widely adopted open technologies.How does it work?• Recommends using TLS 1.2 or better for HTTP and WebSocket messages.• Recommends cipher suites. — BCP-003-01
• BCP-003-02BCP-003-02What does it do?• Documents best practice for an API server to accept or reject requests depending on what a client is authorized to do.Why does it matter?• A secure control plane is essential.• Authorization limits what clients can do to what is allowed.• These recommendations allow interoperability using widely adopted open technologies.How does it work?• Recommends using AMWA IS-10 Authorization Specification• This specifies how client provides credentials and gets access tokens.• Encryption is a prerequisite (see BCP-003-01). — BCP-003-02
• BCP-003-03BCP-003-03What does it do?• Documents best practice for automated provisioning of TLS Server Certificates to NMOS APIs.Why does it matter?• A secure control plane is essential.• Certificates are an important part of this, and automation makes their use practical.• These recommendations allow interoperability using widely adopted open technologies.How does it work?• Recommends behaviour, based on Enrollment over Secure Transport (RFC 7030)• Encryption is a prerequisite (see BCP-003-01). — BCP-003-03
• BCP-004NMOS CapabilitiesWhy does it matter?• Controllers need to know whether a Sender and Receiver can interoperate before attempting a connection.• A consistent capability model allows implementations to describe supported stream parameters without vendor-specific conventions. — NMOS Capabilities
• BCP-004-01BCP-004-01What does it do?• Allows an IS-04 Receiver to express parametric constraints on the types of streams that it is capable of consumingWhy does it matter?• Controllers need to know whether a Receiver is capable of handling a specific Sender's stream before connecting the twoHow does it work?• Establishes an open Capabilities register in the NMOS Parameter Registers that lists specifications for parametric constraints (such as width, height, frame rate, number of channels, etc.)• Defines how a Receiver instantiates these Parameter Constraints to make up a list of acceptable Constraint Sets, within the IS-04 caps attribute• Defines how Controllers evaluate whether an IS-04 Sender satisfies these constraints, based on the target parameters specified for each constraint (such as IS-04 Flow attributes and SDP format-specific parameters) — BCP-004-01
• BCP-004-02BCP-004-02What does it do?• Allows an IS-04 Sender to express parametric constraints on the types of streams that it is capable of producingWhy does it matter?• Controllers need to know whether a Receiver is capable of handling the streams a Sender is capable of producing before connecting the two• Controllers need to know whether a Sender is capable of handling specific stream parameters before applying IS-11 active constraintsHow does it work?• Establishes an open Capabilities register in the NMOS Parameter Registers that lists specifications for parametric constraints (such as width, height, frame rate, number of channels, etc.)• Defines how a Sender instantiates these Parameter Constraints to make up a list of acceptable Constraint Sets, within the IS-04 caps attribute — BCP-004-02
• BCP-005NMOS Capability MappingsWhy does it matter?• Consistent mappings allow Controllers to reason about endpoint capabilities using NMOS mechanisms.• The recommendations make technology-specific capabilities discoverable and interoperable without requiring vendor-specific extensions. — NMOS Capability Mappings
• BCP-005-01BCP-005-01What does it do?• Provides a scheme and guidelines for expressing EDID information via Receiver CapabilitiesWhy does it matter?• Receivers associated with Outputs that provide EDID may need to present its contents to ControllersHow does it work?• Describes how each EDID section is translated into Receiver Capabilities• Gives recommendations regarding taking certain EDID sections into account — BCP-005-01
• BCP-005-02BCP-005-02What does it do?• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for HDCP over IP streaming using IPMX/HKEP (VSF TR-10-5).Why does it matter?• An NMOS Controller can verify that any Receiver is compliant with a Sender producing HDCP-encrypted streams, as only IPMX/HKEP-compliant Receivers can process such content.• A standardized framework enables Controllers to systematically verify and/or enforce compliance.How does it work?• Documents how IPMX/HKEP capabilities are announced by both Senders and Receivers.• Explains how to constrain a Sender’s IPMX/HKEP capability.• Outlines the requirements for Senders, Receivers, and Controllers regarding the IPMX/HKEP feature. — BCP-005-02
• BCP-005-03BCP-005-03What does it do?• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for Privacy-encrypted streaming using IPMX/PEP (VSF TR-10-13).Why does it matter?• An NMOS Controller can verify that any Receiver is compliant with a Sender producing Privacy-encrypted streams, as only IPMX/PEP-compliant Receivers can process such content.• A standardized framework enables Controllers to systematically verify and/or enforce compliance.How does it work?• Documents how IPMX/PEP capabilities are announced by both Senders and Receivers.• Outlines the requirements for Senders, Receivers, and Controllers regarding the IPMX/PEP feature. — BCP-005-03
• BCP-006NMOS Format MappingsWhy does it matter?• The individual mapping BCPs ensure consistency between implementations offering NMOS for each stream format.• Bringing these together in the BCP-006 series helps provide consistency between the individual mappings and provides an index of mappings. — NMOS Format Mappings
• BCP-006-01BCP-006-01What does it do?• Enables Registration, Discovery, and Connection Management of JPEG XS Endpoints using the AMWA IS-04 and IS-05 NMOS Specifications.Why does it matter?• It helps ensure consistency between implementations offering NMOS control for JPEG XS endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with JPEG XS streams.• It specifies requirements for SDP files.• It provides examples of how to use IS-04 and IS-05 in the context of JPEG XS streams - specifically JPEG XS encapsulated in RTP as described in IETF RFC 9134. — BCP-006-01
• BCP-006-02BCP-006-02What does it do?• Enables Registration, Discovery, and Connection Management of H.264 Endpoints using the AMWA IS-04, IS-05 and IS-11 NMOS Specifications.Why does it matter?• It helps ensure consistency between implementations offering NMOS control for H.264 endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with [H.264][] streams.• It specifies requirements for SDP when it is used with a transport supporting SDP transport files.• It provides examples of how to use IS-04, IS-05 and IS-11 in the context of H.264 streams - specifically H.264 encapsulated in RTP as described in IETF [RFC 6184][RFC-6184]. It also describe to some extent how to use H.264 with RTP and other transports that encapsulate the H.264 video streams in an MPEG2-TS transport stream. — BCP-006-02
• BCP-006-03BCP-006-03What does it do?• Enables Registration, Discovery, and Connection Management of H.265 Endpoints using the AMWA IS-04, IS-05 and IS-11 NMOS Specifications.Why does it matter?• It helps ensure consistency between implementations offering NMOS control for H.265 endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with [H.265][] streams.• It specifies requirements for SDP when it is used with a transport supporting SDP transport files.• It provides examples of how to use IS-04, IS-05 and IS-11 in the context of H.265 streams - specifically H.265 encapsulated in RTP as described in IETF [RFC 7798][RFC-7798]. It also describe to some extents how to use H.265 with RTP and other transports that encapsulate the H.264 video streams in an MPEG2-TS transport stream. — BCP-006-03
• BCP-006-04BCP-006-04What does it do?• Enables Registration, Discovery, and Connection Management of MPEG TS Endpoints using the AMWA IS-04 and IS-05 NMOS Specifications.Why does it matter?• It creates a set of requirements for interoperable implementations offering the Discovery and Connection Management of MPEG TS endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with MPEG TS streams.• MPEG TS streams are considered as mux format, and this specification does not consider streams within the multiplex.• It provides examples of how to use IS-04 and IS-05 in the context of MPEG TS streams with RTP transport, such as VSF TR-01 and VSF TR-07 — BCP-006-04
• BCP-007NMOS Transport MappingsWhy does it matter?• The individual mapping BCPs ensure consistency between implementations offering NMOS for each stream transport.• Bringing these together in the BCP-007 series helps provide consistency between the individual mappings and provides an index of mappings. — NMOS Transport Mappings
• BCP-007-01BCP-007-01What does it do?• Enables Registration, Discovery, and Connection Management of NDI endpoints using the AMWA IS-04 and IS-05 NMOS Specifications.• Specifies the interaction of NMOS-enabled NDI nodes and non-NMOS NDI nodes.Why does it matter?• It allows NDI endpoints and gateways to integrate in an NMOS-managed control environment.How does it work?• It specifies how NDI senders and receivers are defined within the scope of IS-04 and IS-05• It specifies how NDI receivers can be connected to NMOS NDI senders or native NDI senders• It defines the representation of muxed NDI flows of video, audio and metadata — BCP-007-01
• BCP-007-02BCP-007-02What does it do?• Establishes a new IS-05 transport for NMOS Senders and Receivers implementing USB over IP and allows Controllers to establish compatible connections.• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for USB over IP transport streams using IPMX/USB (VSF TR-10-14).Why does it matter?• An NMOS Controller can verify that any Receiver is compliant with a Sender producing USB over IP transport streams, as only IPMX/USB-compliant Receivers can process such content.• A standardized framework enables Controllers to systematically verify and/or enforce compliance.How does it work?• Documents how IPMX/USB capabilities are announced by both Senders and Receivers.• Outlines the requirements for Senders, Receivers, and Controllers regarding the IPMX/USB feature. — BCP-007-02
• BCP-007-03BCP-007-03What does it do?• Establishes a new IS-05 transport for NMOS Senders and Receivers implementing MXL and allows Controllers to establish compatible connections.• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for MXL.Why does it matter?• An NMOS Controller can connect compatible MXL Receivers to MXL Senders.How does it work?• Documents how MXL capabilities are announced by both Senders and Receivers.• Outlines the requirements for Senders, Receivers, and Controllers regarding MXL support. — BCP-007-03
• BCP-008NMOS Status MonitoringWhy does it matter?• Consistent status models allow monitoring systems and operators to identify connectivity, synchronization, and stream or essence problems in a predictable way.• Separating the Receiver and Sender recommendations makes the requirements clear while keeping them part of one coherent status-monitoring suite. — NMOS Status Monitoring
• BCP-008-01BCP-008-01What does it do?• It provides a standard way of monitoring the statuses of ReceiversWhy does it matter?• It offers standard models for minimum status reporting• It provides guidance, sets out expectations and requirements for receiver status monitoringHow does it work?• It documents the standard models Devices have to use in order to offer receiver status monitoring• It lists the prerequisites and dependencies in terms of NMOS specifications• It describes the status monitoring domains along with expectations, behaviour and conformance requirements — BCP-008-01
• BCP-008-02BCP-008-02What does it do?• It provides a standard way of monitoring the statuses of SendersWhy does it matter?• It offers standard models for minimum status reporting• It provides guidance, sets out expectations and requirements for sender status monitoringHow does it work?• It documents the standard models Devices have to use in order to offer sender status monitoring• It lists the prerequisites and dependencies in terms of NMOS specifications• It describes the status monitoring domains along with expectations, behaviour and conformance requirements — BCP-008-02
• BCP-TEMPLATEBCP-TEMPLATEWhat does it do?• It provides a template for AMWA NMOS Best Current Practice (BCP) Specifications.Why does it matter?• It helps ensure consistency between NMOS Specifications.• It helps us test our continuous integration.How does it work?• It contains examples of documentation, and examples• It provides a style guide and other advice for specification authors• This includes how to configure the repo for automatic linting and rendering to specs.amwa.tv• Select AMWA-TV/bcp-template as the template when creating the new repo. — BCP-TEMPLATE

CONFIGURATION

• IS-11IS-11What does it do?• Introduces Inputs associated with Senders and Outputs associated with Receivers• Allows the configuration of media parameters of Senders and Inputs using information coming from Receivers and Outputs.Why does it matter?• State of a Sender can be tuned to be compatible with a corresponding Receiver or many compatible ReceiversHow does it work?• An endpoint on the side of Senders is introduced for media parameters control• Senders and Receivers are followed with endpoints which list Inputs and Outputs respectively and describe them in detail — IS-11
• IS-14IS-14How does it work?• It specifies an HTTP API for backing up an NMOS Nodes' MS-05-02 model as a JSON backup dataset.• The API can be used to restore that backup dataset to the NMOS Node.• The API can be used to change the structure of 'rebuildable' parts of the MS-05-02 model dynamically, if the NMOS Node allows. — IS-14

CONNECTION

• BCP-004-01BCP-004-01What does it do?• Allows an IS-04 Receiver to express parametric constraints on the types of streams that it is capable of consumingWhy does it matter?• Controllers need to know whether a Receiver is capable of handling a specific Sender's stream before connecting the twoHow does it work?• Establishes an open Capabilities register in the NMOS Parameter Registers that lists specifications for parametric constraints (such as width, height, frame rate, number of channels, etc.)• Defines how a Receiver instantiates these Parameter Constraints to make up a list of acceptable Constraint Sets, within the IS-04 caps attribute• Defines how Controllers evaluate whether an IS-04 Sender satisfies these constraints, based on the target parameters specified for each constraint (such as IS-04 Flow attributes and SDP format-specific parameters) — BCP-004-01
• BCP-004-02BCP-004-02What does it do?• Allows an IS-04 Sender to express parametric constraints on the types of streams that it is capable of producingWhy does it matter?• Controllers need to know whether a Receiver is capable of handling the streams a Sender is capable of producing before connecting the two• Controllers need to know whether a Sender is capable of handling specific stream parameters before applying IS-11 active constraintsHow does it work?• Establishes an open Capabilities register in the NMOS Parameter Registers that lists specifications for parametric constraints (such as width, height, frame rate, number of channels, etc.)• Defines how a Sender instantiates these Parameter Constraints to make up a list of acceptable Constraint Sets, within the IS-04 caps attribute — BCP-004-02
• BCP-006-01BCP-006-01What does it do?• Enables Registration, Discovery, and Connection Management of JPEG XS Endpoints using the AMWA IS-04 and IS-05 NMOS Specifications.Why does it matter?• It helps ensure consistency between implementations offering NMOS control for JPEG XS endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with JPEG XS streams.• It specifies requirements for SDP files.• It provides examples of how to use IS-04 and IS-05 in the context of JPEG XS streams - specifically JPEG XS encapsulated in RTP as described in IETF RFC 9134. — BCP-006-01
• BCP-006-02BCP-006-02What does it do?• Enables Registration, Discovery, and Connection Management of H.264 Endpoints using the AMWA IS-04, IS-05 and IS-11 NMOS Specifications.Why does it matter?• It helps ensure consistency between implementations offering NMOS control for H.264 endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with [H.264][] streams.• It specifies requirements for SDP when it is used with a transport supporting SDP transport files.• It provides examples of how to use IS-04, IS-05 and IS-11 in the context of H.264 streams - specifically H.264 encapsulated in RTP as described in IETF [RFC 6184][RFC-6184]. It also describe to some extent how to use H.264 with RTP and other transports that encapsulate the H.264 video streams in an MPEG2-TS transport stream. — BCP-006-02
• BCP-006-03BCP-006-03What does it do?• Enables Registration, Discovery, and Connection Management of H.265 Endpoints using the AMWA IS-04, IS-05 and IS-11 NMOS Specifications.Why does it matter?• It helps ensure consistency between implementations offering NMOS control for H.265 endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with [H.265][] streams.• It specifies requirements for SDP when it is used with a transport supporting SDP transport files.• It provides examples of how to use IS-04, IS-05 and IS-11 in the context of H.265 streams - specifically H.265 encapsulated in RTP as described in IETF [RFC 7798][RFC-7798]. It also describe to some extents how to use H.265 with RTP and other transports that encapsulate the H.264 video streams in an MPEG2-TS transport stream. — BCP-006-03
• BCP-006-04BCP-006-04What does it do?• Enables Registration, Discovery, and Connection Management of MPEG TS Endpoints using the AMWA IS-04 and IS-05 NMOS Specifications.Why does it matter?• It creates a set of requirements for interoperable implementations offering the Discovery and Connection Management of MPEG TS endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with MPEG TS streams.• MPEG TS streams are considered as mux format, and this specification does not consider streams within the multiplex.• It provides examples of how to use IS-04 and IS-05 in the context of MPEG TS streams with RTP transport, such as VSF TR-01 and VSF TR-07 — BCP-006-04
• BCP-007-01BCP-007-01What does it do?• Enables Registration, Discovery, and Connection Management of NDI endpoints using the AMWA IS-04 and IS-05 NMOS Specifications.• Specifies the interaction of NMOS-enabled NDI nodes and non-NMOS NDI nodes.Why does it matter?• It allows NDI endpoints and gateways to integrate in an NMOS-managed control environment.How does it work?• It specifies how NDI senders and receivers are defined within the scope of IS-04 and IS-05• It specifies how NDI receivers can be connected to NMOS NDI senders or native NDI senders• It defines the representation of muxed NDI flows of video, audio and metadata — BCP-007-01
• BCP-007-02BCP-007-02What does it do?• Establishes a new IS-05 transport for NMOS Senders and Receivers implementing USB over IP and allows Controllers to establish compatible connections.• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for USB over IP transport streams using IPMX/USB (VSF TR-10-14).Why does it matter?• An NMOS Controller can verify that any Receiver is compliant with a Sender producing USB over IP transport streams, as only IPMX/USB-compliant Receivers can process such content.• A standardized framework enables Controllers to systematically verify and/or enforce compliance.How does it work?• Documents how IPMX/USB capabilities are announced by both Senders and Receivers.• Outlines the requirements for Senders, Receivers, and Controllers regarding the IPMX/USB feature. — BCP-007-02
• BCP-007-03BCP-007-03What does it do?• Establishes a new IS-05 transport for NMOS Senders and Receivers implementing MXL and allows Controllers to establish compatible connections.• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for MXL.Why does it matter?• An NMOS Controller can connect compatible MXL Receivers to MXL Senders.How does it work?• Documents how MXL capabilities are announced by both Senders and Receivers.• Outlines the requirements for Senders, Receivers, and Controllers regarding MXL support. — BCP-007-03
• INFO-003INFO-003What does it do?• It introduces a common format choice approach of some physical interfaces into NMOSWhy does it matter?• It shows how physical protocols of common format choice can be handled in the networked wayHow does it work?• Receivers expose information about their Capabilities based on EDID• Senders get a control mechanism which allows to configure their actual media parameters described in Flows and Sources — INFO-003
• INFO-005INFO-005What does it do?• It is a guide for implementers of Controllers who want to support the NMOS suite of specifications.• It defines the role of an NMOS Controller.• It describes the requirements of an NMOS Controller with respect to each of the NMOS specifications, together with implementation guidance where appropriate.Why does it matter?• This guide makes adding NMOS support to Controllers easier by providing clear guidance on which parts of the specifications are relevant.How does it work?• It is divided into sections that explain the expectations of an NMOS Controller with respect to each NMOS Specification.• It provides references to the relevant sections of the NMOS specifications where the normative language can be found.• It provides additional guidance to implementers where appropriate. — INFO-005
• IS-05IS-05What does it do?• Provides a transport-independent way of connecting Media Nodes• Supports RTP, WebSocket, MQTT and other transports via the Transports register• Supports single + bulk connections, immediate + delayed connectionsWhy does it matter?• ST 2110 does not specify how to do this• So without IS-05 there is a danger of multiple proprietary approaches• ...and difficulty in adopting new stream formats.• Provides support for new specifications• such as IS-07 event transportHow does it work?• Control application sends instructions to Media Nodes• transport_params conveys the connection information — IS-05
• IS-08IS-08What does it do?• Allows channel-level operations within NMOS environments• For example: muting channels, swapping languages…Why does it matter?• Provides expected functionality for typical production/broadcast operations• Extends usefulness of IS-05 and other NMOS specs.How does it work?• Controller gets channel information from sending Node• …and sends mapping information to the receiving Node• Can also do sender-side mapping — IS-08

CONTROL

• BCP-008-01BCP-008-01What does it do?• It provides a standard way of monitoring the statuses of ReceiversWhy does it matter?• It offers standard models for minimum status reporting• It provides guidance, sets out expectations and requirements for receiver status monitoringHow does it work?• It documents the standard models Devices have to use in order to offer receiver status monitoring• It lists the prerequisites and dependencies in terms of NMOS specifications• It describes the status monitoring domains along with expectations, behaviour and conformance requirements — BCP-008-01
• BCP-008-02BCP-008-02What does it do?• It provides a standard way of monitoring the statuses of SendersWhy does it matter?• It offers standard models for minimum status reporting• It provides guidance, sets out expectations and requirements for sender status monitoringHow does it work?• It documents the standard models Devices have to use in order to offer sender status monitoring• It lists the prerequisites and dependencies in terms of NMOS specifications• It describes the status monitoring domains along with expectations, behaviour and conformance requirements — BCP-008-02
• INFO-006INFO-006What does it do?• It guides the reader through some of the most important aspects when implementing a compliant AMWA IS-12, BCP-008 device or controller.Why does it matter?• It provides an easy way of navigating the NMOS Device Control & Monitoring suite when attempting to create a compliant device or controller implementation.How does it work?• It provides tutorials and How-To examples to assist with implementing a compliant AMWA IS-12, BCP-008 device or controller. — INFO-006
• IS-07IS-07What does it do?• Provides an IP-friendly mechanism to carry time-sensitive information• For example: camera tally information, audio levels, control panel button presses and statusWhy does it matter?• ST 2110 does not provide an equivalent to GPI functionality• This leads to the danger of multiple proprietary approaches• Consistency with other NMOS specificationsHow does it work?• Media Nodes emit and consume state and state change info• Lightweight messages sent using WebSockets or MQTT• Message flows connected using IS-05 — IS-07
• IS-12IS-12What does it do?• Describes the specification for the NMOS Device Control & Monitoring Protocol.Why does it matter?• Sets out the rules and requirements for implementing the NMOS Device Control & Monitoring Protocol in devices and controllers.How does it work?• Describes a standard way of exposing NMOS Control models which can be consumed and interacted with. — IS-12
• MS-05-01MS-05-01What does it do?• It defines the architecture for modelling various types of devices which interrelates with existing NMOS Specifications and the JT-NM Reference Architecture.Why does it matter?• The modelling system provides for the definition of device configuration, control and monitoring APIs using a set of published class definitions and operating rules.• The model includes the abilities for controllers to discover full device APIs in live systems, and to reconfigure devices dynamically (i.e. at run time).• In all cases, multiple simultaneous controllers are fully supported with no requirement for polling to maintain synchronization.How does it work?• It provides the architecture for control and monitoring class hierarchies and core mechanisms for building device control and monitoring APIs. — MS-05-01
• MS-05-02MS-05-02What does it do?• Describes the specification for using NMOS Control modelsWhy does it matter?• Sets out the rules and framework for building control models in NMOS devices.How does it work?• Model definitions and supporting documentation describe the way control models can be created. — MS-05-02

INFO

• INFO-002INFO-002What does it do?• It's a guide for implementers who want to add security to their NMOS Nodes and/or NMOS Controllers, according to the IS-10, BCP-003-01, BCP-003-02 and BCP-003-03 specifications.• Please note that this guide is informative and therefore is not a substitute for reading the normative specifications.Why does it matter?• This guide makes the job of adding security to your NMOS implementations easier.How does it work?• It details what you need to know, and the steps you need to take when implementing security.• It also mentions some tools to help in your implementation. — INFO-002
• INFO-003INFO-003What does it do?• It introduces a common format choice approach of some physical interfaces into NMOSWhy does it matter?• It shows how physical protocols of common format choice can be handled in the networked wayHow does it work?• Receivers expose information about their Capabilities based on EDID• Senders get a control mechanism which allows to configure their actual media parameters described in Flows and Sources — INFO-003
• INFO-004INFO-004What does it do?• Explains the use of DNS-SD in NMOS environments.• Provides a practical "how-to" example of how to set up a BIND9 DNS server for NMOS use.• Gives example configurations for other DNS servers.Why does it matter?• DNS Service Discovery (DNS-SD) provides a simple and flexible method to discover NMOS Registration and Discovery Server (RDS) Services.• The NMOS RDS provides information about NMOS nodes, devices, and APIs. There must be a common way to locate the RDS in order for an NMOS component to register itself for discovery by other NMOS components.How does it work?• The fact that the DNS server provides Service Discovery• Where the NMOS RDS may be found on the network — INFO-004
• INFO-005INFO-005What does it do?• It is a guide for implementers of Controllers who want to support the NMOS suite of specifications.• It defines the role of an NMOS Controller.• It describes the requirements of an NMOS Controller with respect to each of the NMOS specifications, together with implementation guidance where appropriate.Why does it matter?• This guide makes adding NMOS support to Controllers easier by providing clear guidance on which parts of the specifications are relevant.How does it work?• It is divided into sections that explain the expectations of an NMOS Controller with respect to each NMOS Specification.• It provides references to the relevant sections of the NMOS specifications where the normative language can be found.• It provides additional guidance to implementers where appropriate. — INFO-005
• INFO-006INFO-006What does it do?• It guides the reader through some of the most important aspects when implementing a compliant AMWA IS-12, BCP-008 device or controller.Why does it matter?• It provides an easy way of navigating the NMOS Device Control & Monitoring suite when attempting to create a compliant device or controller implementation.How does it work?• It provides tutorials and How-To examples to assist with implementing a compliant AMWA IS-12, BCP-008 device or controller. — INFO-006
• INFO-TEMPLATEINFO-TEMPLATEWhat does it do?• Provides a template for creating new NMOS Implementation GuidesWhy does it matter?• NMOS Implementation Guides (INFO-xxx) provide guidance for use of NMOS Specifications.• Implementation Guides are living documents that are updated to reflect changing technologies.• This template helps ensure consistency between Implementation Guides.• It also helps us test our continuous integration.How does it work?• It contains examples of documentation useful in Implementation Guides• It provides a style guide and other advice for authors• Select AMWA-TV/info-template as the template when creating the new repo — INFO-TEMPLATE

IS

• IS-04IS-04What does it do?• Allows control and monitoring applications to find the resources on a network• Resources include Nodes, Devices, Senders, Receivers, Sources, Flows...Why does it matter?• Enables automation and reduces manual overhead in setting up networked sytems• Essential for dynamic deploymentHow does it work?• Media Nodes locate IS-04 registry using DNS-SD (unicast preferred)• Media Nodes register their resource information with HTTP + JSON• Applications query with HTTP and/or subscribe with WebSocket — IS-04
• IS-05IS-05What does it do?• Provides a transport-independent way of connecting Media Nodes• Supports RTP, WebSocket, MQTT and other transports via the Transports register• Supports single + bulk connections, immediate + delayed connectionsWhy does it matter?• ST 2110 does not specify how to do this• So without IS-05 there is a danger of multiple proprietary approaches• ...and difficulty in adopting new stream formats.• Provides support for new specifications• such as IS-07 event transportHow does it work?• Control application sends instructions to Media Nodes• transport_params conveys the connection information — IS-05
• IS-06IS-06What does it do?• IS-06 lets broadcast control applications manage what happens on the network itselfHow does it work?• Provides a “Northbound” API from network fabric’s controller• Includes topology discovery, flow authorization and assurances of flow bandwidth — IS-06
• IS-07IS-07What does it do?• Provides an IP-friendly mechanism to carry time-sensitive information• For example: camera tally information, audio levels, control panel button presses and statusWhy does it matter?• ST 2110 does not provide an equivalent to GPI functionality• This leads to the danger of multiple proprietary approaches• Consistency with other NMOS specificationsHow does it work?• Media Nodes emit and consume state and state change info• Lightweight messages sent using WebSockets or MQTT• Message flows connected using IS-05 — IS-07
• IS-08IS-08What does it do?• Allows channel-level operations within NMOS environments• For example: muting channels, swapping languages…Why does it matter?• Provides expected functionality for typical production/broadcast operations• Extends usefulness of IS-05 and other NMOS specs.How does it work?• Controller gets channel information from sending Node• …and sends mapping information to the receiving Node• Can also do sender-side mapping — IS-08
• IS-09IS-09What does it do?• Allows an NMOS Node (also known as a "Media Node") to obtain global configuration parameters that are common across the system.Why does it matter?• Enables the Node to start, or re-start, in a well defined way that is consistent with the environment it's running in.How does it work?• Defines the System API 'global configuration resource' and the expected behaviour for Nodes using it. — IS-09
• IS-10IS-10What does it do?• Allows an API server to accept or reject requests depending on what a client is authorized to doWhy does it matter?• Security in the control plane is essential• Best practice is to limit what clients can doHow does it work?• Control client provides credentials and gets an access token• Sends token with API requests• Based on JSON Web Tokens and OAuth 2.0• Encryption is a prerequisite (see BCP-003-01) — IS-10
• IS-11IS-11What does it do?• Introduces Inputs associated with Senders and Outputs associated with Receivers• Allows the configuration of media parameters of Senders and Inputs using information coming from Receivers and Outputs.Why does it matter?• State of a Sender can be tuned to be compatible with a corresponding Receiver or many compatible ReceiversHow does it work?• An endpoint on the side of Senders is introduced for media parameters control• Senders and Receivers are followed with endpoints which list Inputs and Outputs respectively and describe them in detail — IS-11
• IS-12IS-12What does it do?• Describes the specification for the NMOS Device Control & Monitoring Protocol.Why does it matter?• Sets out the rules and requirements for implementing the NMOS Device Control & Monitoring Protocol in devices and controllers.How does it work?• Describes a standard way of exposing NMOS Control models which can be consumed and interacted with. — IS-12
• IS-13IS-13What does it do?• Allows control and monitoring applications to update resource labels, descriptions and tagsWhy does it matter?• Operators need to be able to distinguish between different resources• Often this is aided by user-provided information (beyond what is provided by the vendor through BCP-002-02)How does it work?• Media Nodes advertise it in their Node services — IS-13
• IS-14IS-14How does it work?• It specifies an HTTP API for backing up an NMOS Nodes' MS-05-02 model as a JSON backup dataset.• The API can be used to restore that backup dataset to the NMOS Node.• The API can be used to change the structure of 'rebuildable' parts of the MS-05-02 model dynamically, if the NMOS Node allows. — IS-14
• IS-TEMPLATEIS-TEMPLATEWhat does it do?• It provides a template for AMWA NMOS Interface Specifcations.Why does it matter?• It helps ensure consistency between NMOS Specifications.• It helps us test our continuous integration.How does it work?• It contains examples of documentation, APIs, schemas, and examples• It provides a style guide and other advice for specification authors• This includes how to configure the repo for automatic linting and rendering to specs.amwa.tv• Select AMWA-TV/is-template as the template when creating the new repo. — IS-TEMPLATE

MS

• MS-04MS-04What does it do?• Documents a model for identity and timing that applies to AMWA NMOS specifications that apply to content• Builds on models of the JT-NM Reference ArchictureWhy does it matter?• Provides a basis for future specificationsHow does it work?• Defines the main time-related entities used in NMOS specs• Provides further explanation of their meaning• Gives guidance on how they can be used for media operations — MS-04
• MS-05-01MS-05-01What does it do?• It defines the architecture for modelling various types of devices which interrelates with existing NMOS Specifications and the JT-NM Reference Architecture.Why does it matter?• The modelling system provides for the definition of device configuration, control and monitoring APIs using a set of published class definitions and operating rules.• The model includes the abilities for controllers to discover full device APIs in live systems, and to reconfigure devices dynamically (i.e. at run time).• In all cases, multiple simultaneous controllers are fully supported with no requirement for polling to maintain synchronization.How does it work?• It provides the architecture for control and monitoring class hierarchies and core mechanisms for building device control and monitoring APIs. — MS-05-01
• MS-05-02MS-05-02What does it do?• Describes the specification for using NMOS Control modelsWhy does it matter?• Sets out the rules and framework for building control models in NMOS devices.How does it work?• Model definitions and supporting documentation describe the way control models can be created. — MS-05-02
• MS-05-03MS-05-03What does it do?• Describes the specification for creating NMOS Control Blockspecs.Why does it matter?• Sets out the rules and requirements for creating Blockspec files which can be used by device manufacturers for implementation.How does it work?• Describes a uniform way of specifying block functionality and constraints for standardising feature sets. — MS-05-03

NMOS

• NMOS-CONTROL-FEATURE-SETSNMOS-CONTROL-FEATURE-SETSWhat does it do?• The feature sets register contains opt in models for features which devices might implement.• All the control class models in the feature sets register will always be derived directly or indirectly from an NMOS Control framework class model.• The feature sets in the register will contain either control classes or datatypes or both.• Where a device employs features covered by a feature set in the register it MUST comply with the model definitions specified in the particular feature set.Why does it matter?• It provides an extensibility mechanism to the NMOS Control framework.How does it work?• It is organised by feature sets that contain models for either control classes or datatypes or both. — NMOS-CONTROL-FEATURE-SETS
• NMOS-PARAMETER-REGISTERSNMOS-PARAMETER-REGISTERSWhat does it do?• Lists constants for many types of parameter values used in NMOS specifications• Defines procedures for updating theseWhy does it matter?• Supports extensibility of NMOS• Promotes interoperability by ensuring common definitions can be shared easilyHow does it work?• Each type of parameter has a register, listed on this site• In most parameter registers, values are specified as urn:x-nmos:<type>:<value>[/<version>]• Updates are proposed and reviewed using GitHub pull requests (PRs) — NMOS-PARAMETER-REGISTERS

PRO-AV

• BCP-002-01BCP-002-01What does it do?• Documents best practice and recommendations for how to indicate and handle "Natural Groups" of Resources in AMWA NMOS APIs.• These are those created by the default operation of a Node/Device, and not user- or automation-defined Groups.Why does it matter?• Provides a consistent way of referring to groups of related Resources (e.g. video and audio Senders of a camera)• This helps with interoperability and integration.How does it work?• Nodes add a grouphint tag to the JSON representation of each member of a Natural Group. — BCP-002-01
• BCP-002-02BCP-002-02What does it do?• It defines how to provide human-readable distinguishing information for NMOS Assets - Nodes and Devices.Why does it matter?• Inconsistent naming approaches across vendors and products can complicate configuration and operation.How does it work?• It defines tags for fixed information about Nodes and Devices.• These include Manufacturer, Product Name, Instance Identifier, and (for Devices only) Function. — BCP-002-02
• BCP-004-01BCP-004-01What does it do?• Allows an IS-04 Receiver to express parametric constraints on the types of streams that it is capable of consumingWhy does it matter?• Controllers need to know whether a Receiver is capable of handling a specific Sender's stream before connecting the twoHow does it work?• Establishes an open Capabilities register in the NMOS Parameter Registers that lists specifications for parametric constraints (such as width, height, frame rate, number of channels, etc.)• Defines how a Receiver instantiates these Parameter Constraints to make up a list of acceptable Constraint Sets, within the IS-04 caps attribute• Defines how Controllers evaluate whether an IS-04 Sender satisfies these constraints, based on the target parameters specified for each constraint (such as IS-04 Flow attributes and SDP format-specific parameters) — BCP-004-01
• BCP-004-02BCP-004-02What does it do?• Allows an IS-04 Sender to express parametric constraints on the types of streams that it is capable of producingWhy does it matter?• Controllers need to know whether a Receiver is capable of handling the streams a Sender is capable of producing before connecting the two• Controllers need to know whether a Sender is capable of handling specific stream parameters before applying IS-11 active constraintsHow does it work?• Establishes an open Capabilities register in the NMOS Parameter Registers that lists specifications for parametric constraints (such as width, height, frame rate, number of channels, etc.)• Defines how a Sender instantiates these Parameter Constraints to make up a list of acceptable Constraint Sets, within the IS-04 caps attribute — BCP-004-02
• BCP-005-01BCP-005-01What does it do?• Provides a scheme and guidelines for expressing EDID information via Receiver CapabilitiesWhy does it matter?• Receivers associated with Outputs that provide EDID may need to present its contents to ControllersHow does it work?• Describes how each EDID section is translated into Receiver Capabilities• Gives recommendations regarding taking certain EDID sections into account — BCP-005-01
• BCP-005-02BCP-005-02What does it do?• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for HDCP over IP streaming using IPMX/HKEP (VSF TR-10-5).Why does it matter?• An NMOS Controller can verify that any Receiver is compliant with a Sender producing HDCP-encrypted streams, as only IPMX/HKEP-compliant Receivers can process such content.• A standardized framework enables Controllers to systematically verify and/or enforce compliance.How does it work?• Documents how IPMX/HKEP capabilities are announced by both Senders and Receivers.• Explains how to constrain a Sender’s IPMX/HKEP capability.• Outlines the requirements for Senders, Receivers, and Controllers regarding the IPMX/HKEP feature. — BCP-005-02
• BCP-005-03BCP-005-03What does it do?• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for Privacy-encrypted streaming using IPMX/PEP (VSF TR-10-13).Why does it matter?• An NMOS Controller can verify that any Receiver is compliant with a Sender producing Privacy-encrypted streams, as only IPMX/PEP-compliant Receivers can process such content.• A standardized framework enables Controllers to systematically verify and/or enforce compliance.How does it work?• Documents how IPMX/PEP capabilities are announced by both Senders and Receivers.• Outlines the requirements for Senders, Receivers, and Controllers regarding the IPMX/PEP feature. — BCP-005-03
• BCP-006-01BCP-006-01What does it do?• Enables Registration, Discovery, and Connection Management of JPEG XS Endpoints using the AMWA IS-04 and IS-05 NMOS Specifications.Why does it matter?• It helps ensure consistency between implementations offering NMOS control for JPEG XS endpoints.How does it work?• It specifies what resources and attributes MUST be provided when using NMOS with JPEG XS streams.• It specifies requirements for SDP files.• It provides examples of how to use IS-04 and IS-05 in the context of JPEG XS streams - specifically JPEG XS encapsulated in RTP as described in IETF RFC 9134. — BCP-006-01
• BCP-007-02BCP-007-02What does it do?• Establishes a new IS-05 transport for NMOS Senders and Receivers implementing USB over IP and allows Controllers to establish compatible connections.• Establishes a standardized mechanism for NMOS Senders and Receivers to declare support for USB over IP transport streams using IPMX/USB (VSF TR-10-14).Why does it matter?• An NMOS Controller can verify that any Receiver is compliant with a Sender producing USB over IP transport streams, as only IPMX/USB-compliant Receivers can process such content.• A standardized framework enables Controllers to systematically verify and/or enforce compliance.How does it work?• Documents how IPMX/USB capabilities are announced by both Senders and Receivers.• Outlines the requirements for Senders, Receivers, and Controllers regarding the IPMX/USB feature. — BCP-007-02
• BCP-008-01BCP-008-01What does it do?• It provides a standard way of monitoring the statuses of ReceiversWhy does it matter?• It offers standard models for minimum status reporting• It provides guidance, sets out expectations and requirements for receiver status monitoringHow does it work?• It documents the standard models Devices have to use in order to offer receiver status monitoring• It lists the prerequisites and dependencies in terms of NMOS specifications• It describes the status monitoring domains along with expectations, behaviour and conformance requirements — BCP-008-01
• BCP-008-02BCP-008-02What does it do?• It provides a standard way of monitoring the statuses of SendersWhy does it matter?• It offers standard models for minimum status reporting• It provides guidance, sets out expectations and requirements for sender status monitoringHow does it work?• It documents the standard models Devices have to use in order to offer sender status monitoring• It lists the prerequisites and dependencies in terms of NMOS specifications• It describes the status monitoring domains along with expectations, behaviour and conformance requirements — BCP-008-02
• IS-04IS-04What does it do?• Allows control and monitoring applications to find the resources on a network• Resources include Nodes, Devices, Senders, Receivers, Sources, Flows...Why does it matter?• Enables automation and reduces manual overhead in setting up networked sytems• Essential for dynamic deploymentHow does it work?• Media Nodes locate IS-04 registry using DNS-SD (unicast preferred)• Media Nodes register their resource information with HTTP + JSON• Applications query with HTTP and/or subscribe with WebSocket — IS-04
• IS-05IS-05What does it do?• Provides a transport-independent way of connecting Media Nodes• Supports RTP, WebSocket, MQTT and other transports via the Transports register• Supports single + bulk connections, immediate + delayed connectionsWhy does it matter?• ST 2110 does not specify how to do this• So without IS-05 there is a danger of multiple proprietary approaches• ...and difficulty in adopting new stream formats.• Provides support for new specifications• such as IS-07 event transportHow does it work?• Control application sends instructions to Media Nodes• transport_params conveys the connection information — IS-05
• IS-08IS-08What does it do?• Allows channel-level operations within NMOS environments• For example: muting channels, swapping languages…Why does it matter?• Provides expected functionality for typical production/broadcast operations• Extends usefulness of IS-05 and other NMOS specs.How does it work?• Controller gets channel information from sending Node• …and sends mapping information to the receiving Node• Can also do sender-side mapping — IS-08
• IS-11IS-11What does it do?• Introduces Inputs associated with Senders and Outputs associated with Receivers• Allows the configuration of media parameters of Senders and Inputs using information coming from Receivers and Outputs.Why does it matter?• State of a Sender can be tuned to be compatible with a corresponding Receiver or many compatible ReceiversHow does it work?• An endpoint on the side of Senders is introduced for media parameters control• Senders and Receivers are followed with endpoints which list Inputs and Outputs respectively and describe them in detail — IS-11
• IS-12IS-12What does it do?• Describes the specification for the NMOS Device Control & Monitoring Protocol.Why does it matter?• Sets out the rules and requirements for implementing the NMOS Device Control & Monitoring Protocol in devices and controllers.How does it work?• Describes a standard way of exposing NMOS Control models which can be consumed and interacted with. — IS-12

RESOURCE

• BCP-002-01BCP-002-01What does it do?• Documents best practice and recommendations for how to indicate and handle "Natural Groups" of Resources in AMWA NMOS APIs.• These are those created by the default operation of a Node/Device, and not user- or automation-defined Groups.Why does it matter?• Provides a consistent way of referring to groups of related Resources (e.g. video and audio Senders of a camera)• This helps with interoperability and integration.How does it work?• Nodes add a grouphint tag to the JSON representation of each member of a Natural Group. — BCP-002-01
• BCP-002-02BCP-002-02What does it do?• It defines how to provide human-readable distinguishing information for NMOS Assets - Nodes and Devices.Why does it matter?• Inconsistent naming approaches across vendors and products can complicate configuration and operation.How does it work?• It defines tags for fixed information about Nodes and Devices.• These include Manufacturer, Product Name, Instance Identifier, and (for Devices only) Function. — BCP-002-02
• INFO-004INFO-004What does it do?• Explains the use of DNS-SD in NMOS environments.• Provides a practical "how-to" example of how to set up a BIND9 DNS server for NMOS use.• Gives example configurations for other DNS servers.Why does it matter?• DNS Service Discovery (DNS-SD) provides a simple and flexible method to discover NMOS Registration and Discovery Server (RDS) Services.• The NMOS RDS provides information about NMOS nodes, devices, and APIs. There must be a common way to locate the RDS in order for an NMOS component to register itself for discovery by other NMOS components.How does it work?• The fact that the DNS server provides Service Discovery• Where the NMOS RDS may be found on the network — INFO-004
• INFO-005INFO-005What does it do?• It is a guide for implementers of Controllers who want to support the NMOS suite of specifications.• It defines the role of an NMOS Controller.• It describes the requirements of an NMOS Controller with respect to each of the NMOS specifications, together with implementation guidance where appropriate.Why does it matter?• This guide makes adding NMOS support to Controllers easier by providing clear guidance on which parts of the specifications are relevant.How does it work?• It is divided into sections that explain the expectations of an NMOS Controller with respect to each NMOS Specification.• It provides references to the relevant sections of the NMOS specifications where the normative language can be found.• It provides additional guidance to implementers where appropriate. — INFO-005
• IS-04IS-04What does it do?• Allows control and monitoring applications to find the resources on a network• Resources include Nodes, Devices, Senders, Receivers, Sources, Flows...Why does it matter?• Enables automation and reduces manual overhead in setting up networked sytems• Essential for dynamic deploymentHow does it work?• Media Nodes locate IS-04 registry using DNS-SD (unicast preferred)• Media Nodes register their resource information with HTTP + JSON• Applications query with HTTP and/or subscribe with WebSocket — IS-04
• IS-09IS-09What does it do?• Allows an NMOS Node (also known as a "Media Node") to obtain global configuration parameters that are common across the system.Why does it matter?• Enables the Node to start, or re-start, in a well defined way that is consistent with the environment it's running in.How does it work?• Defines the System API 'global configuration resource' and the expected behaviour for Nodes using it. — IS-09
• IS-13IS-13What does it do?• Allows control and monitoring applications to update resource labels, descriptions and tagsWhy does it matter?• Operators need to be able to distinguish between different resources• Often this is aided by user-provided information (beyond what is provided by the vendor through BCP-002-02)How does it work?• Media Nodes advertise it in their Node services — IS-13

SECURITY

• BCP-003-01BCP-003-01What does it do?• Documents best practice for using secure transport for NMOS API communications.Why does it matter?• A secure control plane is essential.• Need to ensure encryption is sufficient.• These recommendations allow interoperability using widely adopted open technologies.How does it work?• Recommends using TLS 1.2 or better for HTTP and WebSocket messages.• Recommends cipher suites. — BCP-003-01
• BCP-003-02BCP-003-02What does it do?• Documents best practice for an API server to accept or reject requests depending on what a client is authorized to do.Why does it matter?• A secure control plane is essential.• Authorization limits what clients can do to what is allowed.• These recommendations allow interoperability using widely adopted open technologies.How does it work?• Recommends using AMWA IS-10 Authorization Specification• This specifies how client provides credentials and gets access tokens.• Encryption is a prerequisite (see BCP-003-01). — BCP-003-02
• BCP-003-03BCP-003-03What does it do?• Documents best practice for automated provisioning of TLS Server Certificates to NMOS APIs.Why does it matter?• A secure control plane is essential.• Certificates are an important part of this, and automation makes their use practical.• These recommendations allow interoperability using widely adopted open technologies.How does it work?• Recommends behaviour, based on Enrollment over Secure Transport (RFC 7030)• Encryption is a prerequisite (see BCP-003-01). — BCP-003-03
• INFO-002INFO-002What does it do?• It's a guide for implementers who want to add security to their NMOS Nodes and/or NMOS Controllers, according to the IS-10, BCP-003-01, BCP-003-02 and BCP-003-03 specifications.• Please note that this guide is informative and therefore is not a substitute for reading the normative specifications.Why does it matter?• This guide makes the job of adding security to your NMOS implementations easier.How does it work?• It details what you need to know, and the steps you need to take when implementing security.• It also mentions some tools to help in your implementation. — INFO-002
• INFO-005INFO-005What does it do?• It is a guide for implementers of Controllers who want to support the NMOS suite of specifications.• It defines the role of an NMOS Controller.• It describes the requirements of an NMOS Controller with respect to each of the NMOS specifications, together with implementation guidance where appropriate.Why does it matter?• This guide makes adding NMOS support to Controllers easier by providing clear guidance on which parts of the specifications are relevant.How does it work?• It is divided into sections that explain the expectations of an NMOS Controller with respect to each NMOS Specification.• It provides references to the relevant sections of the NMOS specifications where the normative language can be found.• It provides additional guidance to implementers where appropriate. — INFO-005
• IS-10IS-10What does it do?• Allows an API server to accept or reject requests depending on what a client is authorized to doWhy does it matter?• Security in the control plane is essential• Best practice is to limit what clients can doHow does it work?• Control client provides credentials and gets an access token• Sends token with API requests• Based on JSON Web Tokens and OAuth 2.0• Encryption is a prerequisite (see BCP-003-01) — IS-10