Operation void provisionEquipment (EquipmentCreateData equipmentCreateData, Equipment equipment), in Class EquipmentHolder

Documentation
This operation allows the NMS to provision Equipment in a Equipment Holder in a Managed Element. The successful result of this operation is the creation or update of the equipment object and the creation of all its related objects such as Termination Points..The equipment object may already exist, but the equipment holder must not have an expected equipment already provisioned.
Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when EMS can not support this operation.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. OBJECT_IN_USE - Raised when the equipment holder already has an expected equipment.
4. INVALID_INPUT - Raised when equipmentCreateData is syntactically incorrect.
5. UNABLE_TO_COMPLY - Raised when the equipment can not be created at the NE.
Raised when the EMS is unable to execute the request because at least one of the parameters although valid can not be
set and that parameter is identified as "not best effort" in additionalInfo.
If the EMS cannot determine the reason it could not comply, it is also allowed to throw UNABLE_TO_COMPLY.
6. USERLABEL_IN_USE - Raised when the userLabel uniqueness constraint is not met.
7. NE_COMM_LOSS - Raised when communication to managed element is lost.

Protocol |  | Qualification |
Exceptions |  | Size |
Time |  | Concurrency | Sequential
Export Control | PublicAccess |  |

Preconditions
Equipment holder do not has an expected equipment.
Postconditions
1. The Equipment object reflects the newly created card.
2. The holderState reflects that the equipment is now expected.
Semantics

Arguments

equipmentCreateData
/* in */ The data that describes the equipment to create. At minimum, this data consists of a user label, an owner, and the expected equipment type.
equipment
/* out */ The resulting created equipment.