{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":31823,"path":"it-service-management/change-management/r_InstlldWthConfDetection.md","title":"Installed with Change Management - Collision Detector","bundle":null,"doc_type":null,"release":"australia","body":"\n# Installed with Change Management - Collision Detector\n\nSeveral types of components are installed with Change Management - Collision Detector.\n\n**Parent Topic:**[Activate Change Management - Collision Detector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/t_ActivateConflictDetection.md)\n\n## Tables installed with Change Management - Collision Detector\n\nChange Management - Collision Detector adds or modifies the following tables.\n\n|Table|Description|\n|-----|-----------|\n|Change request \\[change\\_request\\]|Specifies the background color of the **Conflict status** message based on whether there is a conflict.|\n|Blackout Schedule \\[cmn\\_schedule\\_blackout\\]|Represents a blackout schedule|\n|Condition Schedule \\[cmn\\_schedule\\_condition\\]|Represents a schedule condition|\n|Conflict \\[conflict\\]|Represents conflicts found during the detection process.|\n|Maintenance Schedule \\[cmn\\_schedule\\_maintenance\\]|Represents a maintenance schedule|\n\nChange Management - Collision Detector installs the following types of components:\n\n-   Tables that store schedules, conflicts, and detection results.\n-   Business rules that run the collision detection process.\n-   Schedules, including blackout, maintenance, and condition schedules, used to evaluate conflicts.\n\n"}}