ANSI SCTE 245-2018 pdf free download.Use Cases for Adaptive Power Using APSIS™
1.1. Executive Summary
The intent of this document is to describe several energy management use cases that may be addressed with the ANSI SCTE 216 2015: Adaptive Power Systems Interface Specification (APSIS™ ) and SCTE 237 2017: Implementation Steps for Adaptive Power Systems Interface Specification (APSIS).
1.2. Scope
This document describes use cases as relevant for cable system operators, with specific focus on the cable access network; the infrastructure that delivers services between a content source such as a data center, and a subscriber. SCTE 216, which normatively references IETF EMAN and related RFCs, is generalized to be relevant to domains outside the scope of the cable access network and to support use cases not de-scribed here. Further development in this field may lead to discovery of technical and business opportunities not anticipated here. For these reasons, the use cases presented here should not be considered exhaustive. These use cases are merely descriptive of the potential applicability of APSIS. Any specific use case may or may not be adopted by any set of system operators. The presentation of a use cases should not be construed to indicate that it will be implemented by a specific system operator.
1.3. Benefits
This document provides insight into the intended use cases addressed by SCTE 216 and 237, and provides illustration to operators, vendors, and energy management application developers about possible areas of development within the industry.
1.4. Intended Audience
This document is intended to be referenced by business and technical teams within cable operator,
vendor, and application development organizations.
2. Normative References
The following documents contain provisions, which, through reference in this text, constitute provisions of this document. At the time of Subcommittee approval, the editions indicated were valid. All documents are subject to revision; and while parties to any agreement based on this document are encouraged to investigate the possibility of applying the most recent editions of the documents listed below, they are reminded that newer editions of those documents might not be compatible with the referenced version.
2.1. SCTE References
• No normative references are applicable.
2.2. Standards from Other Organizations
• No normative references are applicable.
2.3. Published Materials
• No normative references are applicable.
3. Informative References
The following documents might provide valuable information to the reader but are not required when
complying with this document.
3.1. SCTE References
• ANSI/SCTE 216 2015, Adaptive Power System Interface Specification (APSIS™ )
(http://www.scte.org/SCTEDocs/Standards/ANSI_SCTE%20216%202015.pdf)
• ANSI/SCTE 237 2017, Implementation Steps for Adaptive Power Systems Interface
Specification (APSIS™ ) (http://www.scte.org/SCTEDocs/Standards/SCTE%20238%202017.pdf)
• ANSI/SCTE 226 2015: Cable Facility Classification Definitions and Requirements
3.2. Standards from Other Organizations
• IETF EMAN (Energy Management). https://datatracker.ietf.org/wg/eman/charter/
3.3. Published Materials
• OpenDaylight Eman (energy management) plug-in.
https://wiki.opendaylight.org/view/EMAN:Main
4. Compliance Notation
shall This word or the adjective “required” means that the item is an absolute requirement of this document. shall not This phrase means that the item is an absolute prohibition of this document. forbidden This word means the value specified shall never be used. should This word or the adjective “recommended” means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighted before choosing a different course. should not This phrase means that there may exist valid reasons in particular circumstances when the listed behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. may This word or the adjective “optional” means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item. deprecated Use is permissible for legacy purposes only. Deprecated features may be removed from future versions of this document. Implementations should avoid use of deprecated features.
