ANSI SCTE 237-2017 pdf free download – Implementation Steps for Adaptive Power Systems Interface Specification (APSIS™).
The application domain encodes logic to collect and process energy measures and issue energy controls.The application layer may be composed of many independent processes executing simultaneously, andmay include heavyweight ‘big data’applications and lightweight alarm processors, and many other
functions.Applications may input other data sources such as measures of service level in order to performits tasks.
The application domain may include a middleware layer to offer basic device discovery and connectivityservices on behalf of all applications, greatly reducing the complexity for each energy specific application. One such middleware is the open-source OpenDaylight Software Defined Networkingcontroller with the EMAN (Energy Management) plug-in.
Annex A includes a diagram of a layered software model.6.1. Steps to Enabling APSISTM
Implementers of APSIS shall read SCTE216 2015 and familiarize themselves with the detailed ANSISCTE standard that normatively recognizes IETF’s EMAN reference as the energy managementframework.
6.1.1. Step one: Inventory
Inventory of devices that are able to: one) – report energy conditions via software interfaces, and two)-be controlled via these software interfaces for the amount of energy consumed in the process of enablingAPSIS TM on the network. Without a solid understanding and inventory of current network-to-powerawareness,unnecessary programming or missed opportunities could occur.
Because few devices support APSIS TMtoday, this process is not programmatically supported by the APSIS TM platform and step one must be performed in an operator defined way.
6.1.2.Step two: Measurement
Energy measurement is step two in the process of enabling APSIS TM on the network.Collecting a goodunderstanding of how much power the end-to-end network consumes should help the cable operatorprioritize where to target the rollout of APSIS TM based on greatest opportunity.
While APSIS TMsupports detailed, programmatic energy measurement, step two must be performed in anoperator defined way.
6.1.3.Step three: Controller Middleware
An end-to-end energy system benefits from a centralized method of device discovery, connectivity,security, and APSIS TM policy enforcement. This software layer could be custom built, integrated into anexisting entity management system or an off-the-shelf package such as the open-source OpenDaylightSoftware Defined Networking(SDN) controller. The term ‘controller’ is used simply to refer to the set offunctions that can be offloaded to a centralized set of components to relieve individual applications of thelow-level details of building a network topology and interfacing directly with devices.
The controller should be located at a hardened facility that can reach the furthest points on the operator’sproduction network. For example, a data center that meets ANSISCTE 226 2015 Class A definitionwould be a logical first consideration. A controller platform should be redundant and provide high-availability, be secure, and offer reasonable performance.
6.1.4. Step four: Enablement Energy Management applications may take many forms, from offering web accessible front-ends for operational or business intelligence visualizations, to alarming, to reporting, and others. Applications receive energy measurements from devices via a controller platform or other data ingest/repository/access framework, and issue commands through controller APIs or other framework. Many applications may integrate with other service operator defined data sets, such as real-time service level metrics.ANSI SCTE 237 pdf download.