View the Change Management (CM) Schedule Optimizer API documentation in the interactive swagger UI 

• download cmso-optimizer-swagger.json

• import into the swagger tool here: https://editor.swagger.io

Optimizer Request Example

The message is a representative of an Scheduler Optimizer Request that is derived from the Create Schedule request. The Schedule Optimizer will use the following APIs to retrieve the data necessary to invoke the Schedule Optimizer Engine:

• Policy API - 

• Topology Service

• Ticket Management Service

Note that the commonData and elementData structures provide a means for passing carrier specific information to the Topology and Ticket Management interfaces which are necessarily carrier specific implementations. 

The policies  provides a means for client to provide policy names along with policy attribute modifiers (details TBD). The list of supported policies is available vie the GET policies API call. 

Optimizer Response Example

The optimizer response is designed to return one or more schedules. Each schedule will contain a list of the elements successfully scheduled (scheduledElements) as well as a list of elements that could not be scheduled.(unScheduledElements). A best effort will be made to provide a reason for the inability to schedule the unscheduled elements.