ment will very quickly get complex, with the addition of measurement instrumentation that is not at all directly related to its core func- tion. Building such additional instrumentation has been costly in terms of delays in the time to deploy new features and has typically taken vendors several release cycles to fully conform to the additional measurement requirements. We could certainly look into adjunct physical devices colocated with a network element, to spe- cifically address the additional measurement functions; however, as the network scales to include several hundred thousand of such network elements, deploying adjunct monitoring devices quickly becomes infeasible. The network transformation offers a great opportunity to optimize such a measurement tool foot- print in a couple of ways. First, by decoupling these measurement functions from network elements, we can adopt a build once and apply everywhere paradigm with applications across the myriad of products that comprise the network. With the introduction of virtualization technologies across the network, we now have the ability to decouple such measurement functions in a cost-effective man- ner, and distribute them across the network as needed. Second, we can aggregate multiple types of such decoupled measurements to derive multiple observations from a single measurement stream. For example, if we take a "service measurement" view, we could reuse a single measurement deployed within a VNF to measure both performance and reachability. Adding analytic capabilities to the overall solution, such as within ONAP, allows us to reuse the measurement data collected derive further measurement-related information across multiple layers of the network. With this measurement framework transformation, component-level monitoring will continue to provide an in-depth network element measurement function, however, its scope is reduced to only collection of native data that has close affinity to the function of the network element and is not easily separable. For example,