INSTRUMENTATION API definition
INSTRUMENTATION API. This will interface to the [***]* for configuration via [***]*, to the [***]* (for configuration originating from the [***]* channel), and to the OPS Configuration and Provisioning Engine (for OPS pre-configuration and IAD provisioning). It also interfaces to [***]* for configuring the UAP. It is also responsible for forwarding [***]* traps received from the UAP and the Management channel to the [***]* and/or the [***]* as appropriate. o OPS CONFIGURATION AND [***]* PROVISIONING ENGINE: This represents the heart of the solution and maintains the repository of configuration information. This component is also responsible for provisioning the IADs as well as setup of the Permanent Management channel. o [***]* STACK: The [***]* stack is required for configuration of the UAP. It also receives traps from the UAP and the Management channels. o [***]*: A commercial [***]* will be used to implement this component. TRIGON Implemented: [***]* Manager o [***]* MANAGER: Anda believes that the system can best be demonstrated only via use of an EMS. Anda proposes a minimal [***]* solution that it will develop that will allow configuration of the OPS manager for provisioning related purposes. SCHEDULES: Anda proposes the following schedule for implementation. Since the implementation of the line [***]* required for data services support on the [***]* is a massive addition (in comparison to the OPS MIB) to the required [***]* support on the OPS, the support for [***]* would be phased. This implementation is aimed at demonstration at Supercom in June will only attempt to provide support for the OPS [***]* and the Interface, DSO/DSO Bundle, T1/E1, ATM and Ethernet [***]*. This is expected to provide adequate support for flow through provisioning of voice services through the [***]* interfaces as well as basic data service provisioning support.