A cross-connect represents a physical connection within a managed element. A cross-connect is atomic and is identified, similarly to an SNC in a singleton subnetwork, based on its external shape. That is, a cross-connect is identified in this interface by its A end(s) and Z end(s), its "SNC" type, and its directionality.
Other characteristics of SNCs do not apply to cross-connections. In particular, the static protection level does not apply to cross-connections, as reliability of cross-connections is not directly impacted by equipment protection at the interface.
As well, the SNC state does not apply to cross-connections as a cross-connect represents a physical connection and not a logical, potential, or reserved set of connections. As such, a cross-connection may only be "active" or "inactive". A "partial cross-connection" actually corresponds to a different cross-connection in this interface as it has a different external shape (e.g., a "half" bidirectional simple cross-connect is not modelled as a partial cross-connect, but rather as a "complete" unidirectional simple cross-connection).

MTOSI Specific Documentation
This class is applicable to MTOSI. The specific operations and relationships that apply to MTOSI are listed in SD2-11. 
For MTOSI, references to "NMS" can be interpreted as "Requesting OS" and references to "EMS" can be interpreted as "Target OS", i.e., the OS that fulfills requests from another OS. 
The statements concerning Object Lifecycle, i.e., whether the object can be created by the NMS or EMS, are not particularly meaningful for MTOSI, since MTOSI does not define management systems with fixed roles such as the NMS and EMS entities in MTNM.

Object Lifecycle: Created and deleted by the EMS

Object Creation Notification Issued? No
Object Deletion Notification Issued? No
