diff --git a/4 b/4
new file mode 100644
index 00000000..80b351fa
--- /dev/null
+++ b/4
@@ -0,0 +1,21 @@
+[?1049h[>4;2m[?1h=[?2004h[?1004h[?12h[?12l[?25l"~/Documents/GitHub/observatory-ops-docs/.git/rebase-merge/git-rebase-todo" 32L, 1485Bnoop
+
+# Rebase be4d319..be4d319 onto be4d319 (1 command)
+#
+# Commands:
+# p, pick <commit> = use commit
+# r, reword <commit> = use commit, but edit the commit message
+# e, edit <commit> = use commit, but stop for amending
+# s, squash <commit> = use commit, but meld into previous commit
+# f, fixup [-C | -c] <commit> = like "squash" but keep only the previous
+#commit's log message, unless -C is used, in which case
+#keep only this commit's message; -c is same as -C but
+#opens the editor
+# x, exec <command> = run command (the rest of the line) using shell
+# b, break = stop here (continue rebase later with 'git rebase --continue')
+# d, drop <commit> = remove commit
+# l, label <label> = label current HEAD with a name
+# t, reset <label> = reset HEAD to a label
+# m, merge [-C <commit> | -c <commit>] <label> [# <oneline>]
+#create a merge commit using the original merge commit's
+#message (or the oneline, if no original merge commit was[?25h[?4m[?2004l[>4;m[?1004l[?2004l[?1l>[?1049l[>4;m
\ No newline at end of file
diff --git a/AuxTel/Non-Standard-Operations/ATCS/AuxTel-Verify-Telescope-and-Dome-Drives-Interlocks.rst b/AuxTel/Non-Standard-Operations/ATCS/AuxTel-Verify-Telescope-and-Dome-Drives-Interlocks.rst
new file mode 100644
index 00000000..21aa1918
--- /dev/null
+++ b/AuxTel/Non-Standard-Operations/ATCS/AuxTel-Verify-Telescope-and-Dome-Drives-Interlocks.rst
@@ -0,0 +1,92 @@
+.. This is a template for operational procedures. Each procedure will have its own sub-directory. This comment may be deleted when the template is copied to the destination.
+
+.. Review the README in this procedure's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace::  *Franco Colleoni, Jacqueline Seron*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: *List-of-contributors*
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _ATCS-Verify-AuxTel-Telescope-and-Dome-Drives-Interlocks:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+############################################
+Verify Telescope and Dome Drives Interlocks
+############################################
+
+
+
+.. _AuxTel-Telescope-and-Dome-Drive-Interlocks-Overview:
+
+Overview
+========
+
+.. This section should provide a brief, top-level description of the procedure's purpose and utilization. Consider including the expected user and when the procedure will be performed.
+
+This procedure outlines the steps to verify if the AuxTel telescope 
+and dome drives have a **triggered interlock** due to the gate being open, 
+the gate being in error, an E-STOP action, or a general failure.
+
+
+.. _AuxTel-Telescope-and-Dome-Drives-Interlocks-Precondition:
+
+Precondition
+============
+
+- You are uncertain of the state of the telescope and dome drives.
+
+
+.. _AuxTel-Telescope-and-Dome-Drives-Interlocks-Post-Condition:
+
+Post-Condition
+==============
+
+- You’ve identified any triggered interlocks for the AuxTel telescope and dome drives.
+- You can now take corrective actions to restore the system.
+
+
+.. _AuxTel-Telescope-and-Dome-Drives-Interlocks-Procedure-Steps:
+
+Procedure Steps
+===============
+
+
+* Check the **Pilz controller** inside the AuxTel Main Cabinet
+
+* According to the **lights**, if they are:
+    * *Off*, an interlock is triggered.
+    * *Illuminated*, the system is functioning correctly.
+
+
+
+.. figure:: ./_static/pilz-controller-status.png
+      :width: 500px
+      
+      Pilz controller status at the AuxTel Main Cabinet
+
+
+
+
+.. _AuxTel-Telescope-and-Dome-Drives-Interlocks-Troubleshooting:
+
+Troubleshooting
+===============
+
+If an interlock has been triggered, follow one of the procedures below based on the cause:
+
+
+* Gate open, gate in error: :ref:`Safety Gate procedures <Safety-Systems-Safety-Gate-Procedures>`.
+
+* E-STOP activated: :ref:`E-stop procedure <AuxTel-Non-Standard-Procedures-E-Stop-Procedure>`.
+
+* General failure: :ref:`Recovery after a Shutdown <AuxTel-Non-Standard-Operations-AuxTel-Recovery-after-Shutdown>`.
diff --git a/AuxTel/Non-Standard-Operations/ATCS/_static/pilz-controller-status.png b/AuxTel/Non-Standard-Operations/ATCS/_static/pilz-controller-status.png
new file mode 100644
index 00000000..853bd788
Binary files /dev/null and b/AuxTel/Non-Standard-Operations/ATCS/_static/pilz-controller-status.png differ
diff --git a/AuxTel/Standard-Operations/Daytime-Operations/Daytime-Checkout.rst b/AuxTel/Standard-Operations/Daytime-Operations/Daytime-Checkout.rst
index 4b0faf56..ada3f3a7 100644
--- a/AuxTel/Standard-Operations/Daytime-Operations/Daytime-Checkout.rst
+++ b/AuxTel/Standard-Operations/Daytime-Operations/Daytime-Checkout.rst
@@ -40,8 +40,8 @@ The scripts can all be found under the standard scripts panel in the *LOVE ATQue
 The order of script execution is nominally:
 
 * :file:`auxtel/enable_latiss.py` - Can be skipped if LATISS enabled 
-* :file:`auxtel/daytime_checkout/latiss_checkout.py`
 * :file:`auxtel/enable_atcs.py` - Can be skipped if ATCS already enabled
+* :file:`auxtel/daytime_checkout/latiss_checkout.py`
 * :file:`auxtel/daytime_checkout/atpneumatics_checkout.py`
 * :file:`auxtel/daytime_checkout/telescope_and_dome_checkout.py`
 * :file:`auxtel/daytime_checkout/slew_and_take_image_checkout.py`
@@ -51,6 +51,11 @@ The order of script execution is nominally:
 
 Bring *LATISS* to an enabled state to prepare for checkout. 
 
+*auxtel/enable_atcs.py*
+=======================
+
+Bring the *ATCS* into an enabled state to prepare for checkout. 
+
 *auxtel/daytime_checkout/latiss_checkout.py*
 ============================================
 
@@ -62,11 +67,6 @@ In case the image fails to appear, promptly communicate the issue in the channel
 
 You can also check if images are arriving correctly at Rubin's SLAC facility using `USDF RubinTV`_.
 
-*auxtel/enable_atcs.py*
-=======================
-
-Bring the *ATCS* into an enabled state to prepare for checkout. 
-
 *auxtel/daytime_checkout/atpneumatics_checkout.py*
 ==================================================
 
@@ -114,99 +114,6 @@ This procedure was last modified on |today|... |author| replace:: *E. Dennihy*
 .. _`summit's RubinTV`: https://summit-lsp.lsst.codes/rubintv/summit/auxtel 
 .. _`USDF RubinTV`: https://usdf-rsp-dev.slac.stanford.edu/rubintv 
 
-##################
-Daytime Checkout 
-##################
-
-
-To ensure the Auxiliary Telescope is fully operational and ready for nighttime use, 
-we have created a series of SAL Scripts that successively checkout each of the major components, 
-culminating in a full test of the system involving slewing to a target, tracking, and taking a test image with LATISS. 
-The goal of these scripts is to test the functionality of each component within the current software environment,
-and alert the daytime staff to any operational issues before going on-sky. 
-These tests are designed to be run using the script queue on LOVE during the daytime with an Observing Specialist 
-or other personnel available to verify their results. 
-
-The scripts are intended to be run in order, 
-but offer some flexibility in what state to leave the Auxiliary Telescope 
-(e.g. ready to take calibrations, ready to observe at night, or simply parked and shutdown). 
-They can also be run individually if a single component is undergoing maintenance 
-and requires a check of basic functionality. 
-
-**None of the scripts require configuration.**
-
-.. Important::
-
-    The daytime checkout scripts involve Telescope, Dome, and Instrument component movement. 
-    Before running, ensure that the area surrounding the telescope is and dome is clear for movement. 
-    You MUST announce that you are running the checks on the #summit-announce slack channel before execution. 
-
-The scripts can all be found under the standard scripts panel in the *LOVE ATQueue* view. 
-The order of script execution is nominally:
-
-* :file:`auxtel/enable_latiss.py` - Can be skipped if LATISS enabled 
-* :file:`auxtel/daytime_checkout/latiss_checkout.py`
-* :file:`auxtel/enable_atcs.py` - Can be skipped if ATCS already enabled
-* :file:`auxtel/daytime_checkout/atpneumatics_checkout.py`
-* :file:`auxtel/daytime_checkout/telescope_and_dome_checkout.py`
-* :file:`auxtel/daytime_checkout/slew_and_take_image_checkout.py`
-
-*auxtel/enable_latiss.py*
-=========================
-
-Bring *LATISS* to an enabled state to prepare for checkout. 
-
-*auxtel/daytime_checkout/latiss_checkout.py*
-============================================
-
-This script will take a bias and an engineering frame with *LATISS* 
-and ensure that they are ingested by the *OODS*.
-
-Verify that the bias appears on the `summit's RubinTV`_. 
-In case the image fails to appear, promptly communicate the issue in the Slack channel *#summit-auxtel*. 
-
-You can also check if images are arriving correctly at Rubin's SLAC facility using `USDF RubinTV`_.
-
-*auxtel/enable_atcs.py*
-=======================
-
-Bring the *ATCS* into an enabled state to prepare for checkout. 
-
-*auxtel/daytime_checkout/atpneumatics_checkout.py*
-==================================================
-
-This script will first turn on the valves and check that the line pressure is sufficient for operations. 
-Next, the telescope will be slewed to the park position, if it is not already there. 
-Then, it will turn on/off the *ATAOS* corrections before lowering the mirror back down onto its hard points.
-Finally, the mirror cover and vents are opened and closed. 
-
-*auxtel/daytime_checkout/telescope_and_dome_checkout.py*
-========================================================
-
-This script starts by performing a slew of the telescope without dome movement. 
-Then, sidereal tracking for the telescope is enabled and the system is left to track for a few minutes. 
-Tracking is disabled and then the dome is commanded to move to a new position, without telescope movement. 
-Finally, the telescope and dome are returned to a park position and left enabled.
-
-*auxtel/daytime_checkout/slew_and_take_image_checkout.py*
-=========================================================
-
-This script will slew the telescope and dome to two different targets, 
-track each target for 3 minutes and take a single verification image. 
-The mirror covers remain closed during the duration of the script. 
-At the end of the script, the telescope and dome are parked. 
-
-Check that the verification images pop up in the monitor at `summit's RubinTV`_.
-
-*auxtel/daytime_checkout/prepare_for/flat.py*
-=============================================
-This is the default end-of-checkout script. 
-It will leave the telescope in position to start taking afternoon calibrations. 
-If you are not sure how you want to leave the telescope,
-consider running this script as it will further exercise the system. 
-
-Other options include: :file:`prepare_for/onsky.py`, :file:`prepare_for/vent.py` or :file:`shutdown_all.py`
-
 Quick Troubleshooting
 =====================
 
diff --git a/AuxTel/Standard-Operations/Daytime-Operations/latiss-daily-calibrations-BIAS-DARK-FLAT-all-filters-empty-procedure.rst b/AuxTel/Standard-Operations/Daytime-Operations/latiss-daily-calibrations-BIAS-DARK-FLAT-all-filters-empty-procedure.rst
index 0e29f325..dc146969 100644
--- a/AuxTel/Standard-Operations/Daytime-Operations/latiss-daily-calibrations-BIAS-DARK-FLAT-all-filters-empty-procedure.rst
+++ b/AuxTel/Standard-Operations/Daytime-Operations/latiss-daily-calibrations-BIAS-DARK-FLAT-all-filters-empty-procedure.rst
@@ -40,15 +40,14 @@ Post-Condition
 Procedure Steps
 ===============
 
-#. Calibrations images should only be taken if the LATISS WREB temperature is under temperature control. Check the LATISS WREB temperatures under the `AuxTel (LATISS) Temperatures and Pressures dashboard`_ in Chronograf. WREB temperatures are visible in the lower middle panel labeled *WREB On Board*. If the *mean_temp2* (top blue line) is between 26-29 degress C, the temperature is suitable for taking calibrations. During the daytime, the fan on the WREB board may not be sufficient to cool the WREB down to these temperatures, so during warmer months you may have to wait until later in the day or early in the morning for it to reach the desired temperature. If the temperature is too high, do not proceed to the next steps.
 #. Enable ATCS and LATISS using the standard scripts :file:`enable_atcs.py` and :file:`enable_latiss.py` with no configuration. 
-#. Enable ``Scheduler:2`` with a valid scheduler configuration. Use the standard script :file:`auxtel/scheduler/enable.py` with the configuration required for the run and available in the corresponding night log. 
+#. Enable ``Scheduler:2`` with a valid scheduler configuration. Use the standard script :file:`auxtel/scheduler/enable.py` with the configuration specified in the AuxTel Scheduler-Driven Survey Test Case (BLOCK-T19). 
 #. **Setup LATISS calibrations** BLOCK will setup ATCS and white light for calibrations. It enables and turns on the ATWhiteLight, enables OCPS:1 and commands AuxTel mount and dome to the FLAT position. Run the script :file:`add_block.py` to the ATQueue  with the following configuration:
 
     .. code-block:: text
       :caption: :file:`add_block.py`
 
-      id: setup_latiss_calibrations
+      id: BLOCK-309
 
     The BLOCK with :file:`setup_latiss_calibrations` configuration will queue the scripts aimed to setup the system. It will start with the :file:`set_summary_state.py` script to enable ATWhiteLight CSC with the following configuration:
 
@@ -75,19 +74,19 @@ Procedure Steps
     .. code-block:: text
       :caption: :file:`auxtel/calibrations/power_on_atcalsys.py`
 
-    The :file:`auxtel/prepare_for/flat.py` script (empty configuration) will position the telescope and dome in FLAT position. The telescope will point towards the dome flat screen (mount Az = 188.7 deg, mount El = 39.0 deg, dome Az= 2.59 deg). Confirm in the cameras aux-cam01 or aux-cam02 that the white light is on, and telescope is pointing to the dome flat screen.
+    The :file:`auxtel/prepare_for/flat.py` script (empty configuration) will position the telescope and dome in FLAT position. The telescope will point towards the dome flat screen (mount Az = 188.7 deg, mount El = 39.0 deg, dome Az= 2.59 deg). Confirm in the cameras "aux-cam01" or "aux-cam02" that the white light is on, and telescope is pointing to the dome flat screen.
 
     .. code-block:: text
       :caption: :file:`auxtel/prepare_for/flat.py`
   
     .. Note: We need to document and link here how to access the aux-cam01/02cameras.
 
-#. The **LATISS daily calibrations** BLOCK will queue the scripts focused on the calibration image adquisition. Run the script :file:`add_block.py` to the ATQueue  with the following configuration:
+#. The **LATISS daily calibrations** BLOCK will queue the scripts focused on the calibration image acquisition. Run the script :file:`add_block.py` to the ATQueue  with the following configuration:
 
     .. code-block:: text
       :caption: :file:`add_block.py`
 
-      id: latiss_daily_calibrations
+      id: BLOCK-295
 
 
     Depending on which filters are currently installed in LATISS, the :file:`auxtel/make_latiss_calibrations.py` script may take different calibration sets. The calibration images displayed in `RubinTV`_ are post-ISR images and should have BIAS and DARK corrections applied. This means that BIAS and DARK images should display with maximum count rates of about 10 ADUs. In the case of FLAT images, counts must be below the :math:`\approx` 30000 ADUs. In the process of building the daily PTC (see below), the FLAT saturation is intended, and achieved at around the 123000 ADUs (with exposure time of about 25 seconds). In case daily FLATS are taken, they reach values of :math:`\approx` 68000 ADUs. If you see large deviations from these values, which can be related with a problem in the instrument signature removal in `RubinTV`_, then RAW count rates are being displayed, please report it. Check the calibration sets and their configurations for each filter installed and the grating.
@@ -260,7 +259,7 @@ Procedure Steps
     .. code-block:: text
       :caption: :file:`add_block.py`
 
-      id: shutdown_latiss_calibrations
+      id: BLOCK-310
 
 
     The BLOCK with :file:`shutdown_latiss_calibrations` configuration finishes with the :file:`auxtel/calibrations/power_off_atcalsys.py` SAL script with no configuration. It will turn off the lamp, close the shutter and shutdown the chiller. At this stage, the script completion time is 15 minutes.
diff --git a/AuxTel/Troubleshooting/ATCS/ATDome-shutter-fails-to-close.rst b/AuxTel/Troubleshooting/ATCS/ATDome-shutter-fails-to-close.rst
deleted file mode 100644
index ac959938..00000000
--- a/AuxTel/Troubleshooting/ATCS/ATDome-shutter-fails-to-close.rst
+++ /dev/null
@@ -1,106 +0,0 @@
-.. This is a template for troubleshooting when some part of the observatory enters an abnormal state. This comment may be deleted when the template is copied to the destination.
-
-.. Review the README in this procedure's directory on instructions to contribute.
-.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
-.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
-.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
-	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
-    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
-
-.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
-.. |author| replace:: *Craig Lage*
-.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
-.. |contributors| replace:: *Karla Aubel*
-
-.. This is the label that can be used as for cross referencing this procedure.
-.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
-.. _AuxTel-ATCS-ATDome-Shutter-Fails-to-Close:
-.. Each section should includes a label for cross referencing to a given area.
-.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
-.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
-.. An error will alert you of identical labels during the build process.
-
-#############################
-ATDome Shutter Fails to Close
-#############################
-
-
-.. _ATDome-Shutter-Fails-To-Close: 
-
-Overview
-========
-
-This page describes the procedures to follow if the software fails to close the AT dome shutter. In the LOVE display can be seen *Dome not in position* in yellow letters:
-
-.. _ATDome-Shutter-Fails-To-Close-The-Dome-shutter-never-reach-the-closed-status:
-
-
-Error diagnosis
-===============
-
-The Dome shutter never reach the closed status.
-
-.. _ATDome-Shutter-Fails-To-Close:
-
-Procedure Steps
-===============
-
-.. todo::
-   Make sure everything is in a safe or idle state before troubleshooting. Describe relevant safety steps if necessary.
-
-.. This section should include the procedure. There is no strict formatting or structure required for procedures. It is left to the authors to decide which format and structure is most relevant.
-.. In the case of more complicated procedures, more sophisticated methodologies may be appropriate, such as multiple section headings or a list of linked procedures to be performed in the specified order.
-.. For highly complicated procedures, consider breaking them into separate procedure. Some options are a high-level procedure with links, separating into smaller procedures or utilizing the reST ``include`` directive <https://docutils.sourceforge.io/docs/ref/rst/directives.html#include>.
-
-#. 1  
-
-Go up to the AuxTel dome.  Locate the control box at the top of the stairs. The top black button should close the shutter:
-
-
-.. image:: _static/Box_at_Top_of_Stairs.jpeg
-
-
-
-
-#. 2
-
-If this fails, locate the cRIO box, which rotates with the AuxTel dome.  It looks like this:
-
- 
- 
- .. image:: _static/cRIO_box.jpeg
-
-
-Inside this box is a series of switches:
-
-.. image:: _static/Switches_in_cRIO_box.jpeg
-
-
-
-Sliding the switch labeled "CLOSE" to the left  (yellow arrow) should close the shutter.  
-This must be done with EXTREME CAUTION.  This is a low-level control switch and there are no limit switches or fail-safes. 
-You can easily overdrive the shutter until it bangs into the lower shutter.  You can also damage the drive.  
-If you do this, it is best to stop the shutter 1 cm or so before it is fully closed to prevent this type of damage.
-
-#. 3
-
-The steps above should close the shutter if there is power. As a last resort, for example if power has been lost, the shutter can be closed manually. 
-There is a crank on the first floor which fits into a ring at the top of the dome (see pictures below). 
-With these you can close the shutter manually.  Note that this is a tedious procedure that might take hours.
-
-.. image:: _static/Top_of_Dome.jpeg  
-  
-    
-.. image:: _static/Hand_Crank.jpeg
-
-Post-Condition
-==============
-
-- The Dome Shutter should be closed.
-
-.. _Title-of-Troubleshooting-Procedure-Contingency:
-
-Contingency
-===========
-
-If the procedure was not successful, report the issue in **#summit-auxtel** channel and/or **#summit-announce** and/or activate the :ref:`Out of hours support <Safety-out-of-hours-support>`.
\ No newline at end of file
diff --git a/AuxTel/Troubleshooting/ATCS/ATHexapod-fails-to-enable-with-the-rest-of-ATCS.rst b/AuxTel/Troubleshooting/ATCS/ATHexapod-fails-to-enable-with-the-rest-of-ATCS.rst
new file mode 100644
index 00000000..e0d99452
--- /dev/null
+++ b/AuxTel/Troubleshooting/ATCS/ATHexapod-fails-to-enable-with-the-rest-of-ATCS.rst
@@ -0,0 +1,128 @@
+.. This is a template for troubleshooting when some part of the observatory enters an abnormal state. This comment may be deleted when the template is copied to the destination.
+
+.. Review the README in this procedure's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: *Ioana Sotuela*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: *Gonzalo Aravena*
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _ATHexapod-fails-to-enable-with-the-rest-of-ATCS:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+###############################################
+ATHexapod fails to enable with the rest of ATCS
+###############################################
+
+
+.. _ATHexapod-fails-to-enable-with-the-rest-of-ATCS-Overview:
+
+Overview
+========
+
+When attempting to enable ATCS from the *LOVE/ATScriptQueue* with the script :file:`auxtel/enable_atcs.py`, ATHexapod fails to transition to enable.
+
+.. _ATHexapod-fails-to-enable-with-the-rest-of-ATCS-Diagnosis:
+
+Error diagnosis
+===============
+
+1. ATHexapod fails to enable with the rest of the ATCS with the SAL script :file:`auxtel/enable_atcs.py`. The error received is:
+
+.. code-block:: text
+  :caption: ATHexapod Error Message when transitioning from ``STANDBY`` to ``ENABLE``
+
+  Callback <bound method BaseCsc.do_start of <lsst.ts.ATHexapod.csc.ATHexapodCSC object at 0x7f27708ecf10>> failed with data=private_revCode: aaf328f3,
+  private_sndStamp: 1692729552.0401282, private_rcvStamp: 1692729552.0401914, private_seqNum: 1839321525, private_identity: Script:201665,
+  private_origin: 14887, configurationOverride: Traceback (most recent call last):  File "/opt/lsst/software/stack/miniconda/lib/python3.10/site-packages/lsst/ts/salobj/topics/controller_command.py", 
+  line 232, in _run_callback    ack = await result  # type: ignore  File "/opt/lsst/software/stack/miniconda/lib/python3.10/site-packages/lsst/ts/salobj/base_csc.py", 
+  line 518, in do_start    await self._do_change_state(data, "start", [State.STANDBY], State.DISABLED)  File "/opt/lsst/software/stack/miniconda/lib/python3.10/site-packages/lsst/ts/salobj/base_csc.py", 
+  line 830, in _do_change_state    await getattr(self, f"end_{cmd_name}")(data)  File "/opt/lsst/software/stack/miniconda/lib/python3.10/site-packages/lsst/ts/ATHexapod/csc.py", 
+  line 206, in end_start    raise e  File "/opt/lsst/software/stack/miniconda/lib/python3.10/site-packages/lsst/ts/ATHexapod/csc.py", 
+  line 202, in end_start    await self.controller.connect() File "/opt/lsst/software/stack/miniconda/lib/python3.10/site-packages/lsst/ts/ATHexapod/controller.py", 
+  line 97, in connect    self.reader, self.writer = await asyncio.wait_for(  File "/opt/lsst/software/stack/miniconda/lib/python3.10/asyncio/tasks.py", 
+  line 445, in wait_for    return fut.result()  File "/opt/lsst/software/stack/miniconda/lib/python3.10/asyncio/streams.py", 
+  line 48, in open_connection    transport, _ = await loop.create_connection(  File "/opt/lsst/software/stack/miniconda/lib/python3.10/asyncio/base_events.py", 
+  line 1076, in create_connection    raise exceptions[0]  File "/opt/lsst/software/stack/miniconda/lib/python3.10/asyncio/base_events.py", 
+  line 1060, in create_connection    sock = await self._connect_sock(  File "/opt/lsst/software/stack/miniconda/lib/python3.10/asyncio/base_events.py", 
+  line 969, in _connect_sock    await self.sock_connect(sock, address)  File "/opt/lsst/software/stack/miniconda/lib/python3.10/asyncio/selector_events.py", 
+  line 501, in sock_connect    return await fut  File "/opt/lsst/software/stack/miniconda/lib/python3.10/asyncio/selector_events.py", 
+  line 541, in _sock_connect_cb    raise OSError(err, f'Connect call failed {address}')OSError: [Errno 113] Connect call failed ('139.229.170.48', 50000)
+
+
+2. Trying to ping the controller at `athexapod.cp.lsst.org <athexapod.cp.lsst.org>`__ results in no response.
+
+
+
+.. _ATHexapod-fails-to-enable-with-the-rest-of-ATCS-Procedure-Steps:
+
+Procedure Steps
+===============
+
+The connection to the ATHexapod can be recovered by manually rebooting the ATHexapod controller box located in the Main ATCS cabinet in the pier of the AuxTel dome.
+
+.. figure:: ./_static/main_cabinet.jpeg
+       :name: Main1
+       :scale: 15 %
+
+       Main ATCS Cabinet.
+
+
+.. _ATHexapod-fails-to-enable-with-the-rest-of-ATCS-Procedure-Critical-Step-1:
+
+1. Announce in the slack channel `#summit-anounce <https://app.slack.com/client/T06D204F2/C01P41NUR1R>`__ that you are going to the AuxTel building to reboot the ATHexapod Controller.
+   
+2. On the first level, or pier of the AuxTel dome, open the Main ATCS cabinet and press the off button at the C-887 Hexapod Controller, that's located at the bottom of the cabinet.
+
+
+   .. list-table::
+      :widths: 50 50
+      :header-rows: 0
+
+      * - .. figure:: ./_static/main_cabinet_inside.png
+              :name: Main2
+              :scale: 17 %
+
+              Main ATCS Cabinet.
+
+        - .. figure:: ./_static/ATHexapod_Controller.jpg
+              :name: ATHexapodCtrl
+              :scale: 11 %
+
+              ATHexapod Controller.
+   
+
+3. Wait for 3 minutes.
+4. Turn the controller on again.
+5. The ATHexapod CSC should be now in ``STANDBY``. Transition the ATHexapod from the *LOVE/ASummaryState View* ``STANDBY`` → ``START`` → ``ENABLE``, or alternative, you could run the :file:`auxtel/enable_atcs.py` again. ATCS should be ready now to begin operations.
+6. Fill the ticket `OBS-243 - ATHexapod not enabling with the rest of ATCS <https://rubinobs.atlassian.net/browse/OBS-243>`__ with as much information you have regarding the state of the system, such as procedures or maintenance done prior to this failure (e-stop, mirror CO2 cleaning, power outage, LOTO, etc)
+
+
+
+.. _Title-of-Troubleshooting-Procedure-Post-Condition:
+
+Post-Condition
+==============
+
+- The ATHexapod CSC is successfully enabled and is now in the ``ENABLE`` state
+- The ATCS system is fully operational and ready to proceed with observations or further procedures.
+
+
+
+.. _Title-of-Troubleshooting-Procedure-Contingency:
+
+Contingency
+===========
+
+If the procedure was not successful, report the issue in `#summit-auxtel <https://app.slack.com/client/T06D204F2/C01K4M6R4AH>`__ and/or activate the :ref:`Out of hours support <Safety-out-of-hours-support>`.
+
diff --git a/AuxTel/Troubleshooting/ATCS/_static/ATHexapod_Controller.jpg b/AuxTel/Troubleshooting/ATCS/_static/ATHexapod_Controller.jpg
new file mode 100644
index 00000000..ec774c0c
Binary files /dev/null and b/AuxTel/Troubleshooting/ATCS/_static/ATHexapod_Controller.jpg differ
diff --git a/AuxTel/Troubleshooting/ATCS/_static/main_cabinet.jpeg b/AuxTel/Troubleshooting/ATCS/_static/main_cabinet.jpeg
new file mode 100644
index 00000000..3f4fec70
Binary files /dev/null and b/AuxTel/Troubleshooting/ATCS/_static/main_cabinet.jpeg differ
diff --git a/AuxTel/Troubleshooting/ATCS/_static/main_cabinet_inside.png b/AuxTel/Troubleshooting/ATCS/_static/main_cabinet_inside.png
new file mode 100644
index 00000000..4010f46d
Binary files /dev/null and b/AuxTel/Troubleshooting/ATCS/_static/main_cabinet_inside.png differ
diff --git a/Daytime-Nighttime-Interactions/_static/Slack-channel-diagram.png b/Daytime-Nighttime-Interactions/_static/Slack-channel-diagram.png
index 8dd000e8..4ee5b7fe 100644
Binary files a/Daytime-Nighttime-Interactions/_static/Slack-channel-diagram.png and b/Daytime-Nighttime-Interactions/_static/Slack-channel-diagram.png differ
diff --git a/Daytime-Nighttime-Interactions/slack-channel-usage.rst b/Daytime-Nighttime-Interactions/slack-channel-usage.rst
index 40248bd2..1438b595 100644
--- a/Daytime-Nighttime-Interactions/slack-channel-usage.rst
+++ b/Daytime-Nighttime-Interactions/slack-channel-usage.rst
@@ -24,17 +24,17 @@
 Slack Channel Communication with Summit Personnel
 #################################################
 
-The LSSTC Slack space is used by hundreds of people with varying levels of interest in summit operations. 
+The Rubin Obs Slack space is used by hundreds of people with varying levels of interest in summit operations. 
 The goal of this document is to communicate the acceptable usage of the specific set of channels that are focused on day and nighttime summit operations. 
 The document also describes the channels where more informal discussions and contributions from non-summit staff can be communicated to the observing crew(s). 
 
-In operations, all slack channels are expected to be open to everyone on the lsstcorp Slack domain.
-However, should people continually violate the rules (and people fail to police them) then we will have to lock the channels. 
+This document and the use-cases described are summit-specific and they do not cover general slack culture and usage. 
+For more information on channel naming, slack culture, and general usage guidelines please see the `DM Developer's Guide <https://developer.lsst.io/communications/slack-culture.html>`_. 
 
 .. important::
    Three ground rules for usage - read this if nothing else:
 
-   1. Personnel not present on the summit are generally discoraged from using tier 0 and 1 channels, though many exceptions to this are detailed in this page. If you do not know if you should use the tier 0 or 1 channel, do not use it.
+   1. Personnel not present on the summit are generally discouraged from using tier 0 and 1 channels, though many exceptions to this are detailed in this page. If you do not know if you should use the tier 0 or 1 channel, do not use it.
 
    2. Work with summit systems should use public channels, not direct messages with with individuals.
 
@@ -54,8 +54,6 @@ For ease of presentation, it was decided to classify the stakeholders by the fol
 
 - Project Personnel: General project members that have slack accounts. This is the default category for most project members and individuals generally advance to other categories when actively on shift.
 
-- External Contributors: People that share the same slack user-space but do not participate in summit operations (e.g. DESC).
-
 While on-shift, the people in each of these roles will have varying responsibilities regarding which information they need to be paying attention to and/or responding to.
 The ultimate goal is to facilitate effective communications to summit personnel by concentrating information into specific places and minimizing distractions.
 It is recognized that all project personnel are capable of contributing useful input, however, unless the people are very close to the on-going tasks there exists a significant awareness gap.
@@ -63,19 +61,20 @@ Therefore, a flow via which anyone on the project can participate has been devel
 Additionally, this limits the number of simultaneous lines of communication that summit personnel are expected to monitor during their shifts.
 
 To better communicate the expectations for each of the roles, and demonstrating the information flow, the list of required Slack channels have been categorized into Tiers. 
-We use the "summit" prefix for channels that are tightly coupled to summit operations.
 
 - **Tier 0:** Real-time information that the applicable roles are always monitoring and are expected to immediately react to (when on shift and interacting with summit systems). 
   Responding to a message may result in a loss of sky time, which is acceptable. 
   Communication in this area meant to be extremely curt. 
   People providing urgent support are encouraged to do so via Zoom; not via Slack.
+  These channels are distinguished by their **#summit-** prefix. 
 
 - **Tier 1:** Used for asynchronous information communication regarding the state of summit systems. 
   These channels are telescope or subsystem specific, do not require immediate response, and are passively monitored by on-shift observers. These include subsystem topic "worklog" channels.
   It is primarily used for communication between summit personnel and externally **requested** support.
+  These channels are often distinguished by their **#-worklog** or **#-support** suffix.
 
 - **Tier 2:** General discussion channels whose information and/or contents are not time critical operation of the observatory at night.
-  The shift managers monitor these channels to relay any pertinent information between external support and the summit teams. These channels have much fewer restrictions on who can participate, useful for the braoder team to contribute information they think might be important to summit operations, which can then be filtered to the summit crew.
+  The shift managers monitor these channels to relay any pertinent information between external support and the summit teams. These channels have much fewer restrictions on who can participate, useful for the broader team to contribute information they think might be important to summit operations, which can then be filtered to the summit crew.
 
 - **Tier 3:** Channels not directly associated with current summit activities. 
   These are channels for collaborative work, which make up the high majority of Slack channels.
@@ -86,6 +85,28 @@ We use the "summit" prefix for channels that are tightly coupled to summit opera
 
     The expected level of participation by summit personnel to observation-related slack channels.
 
+In order to help keep communication protocols clear, it is recommended to use the :guilabel:`Create Section` feature in Slack to organize the channel display by Tier. 
+The following are the recommended channels that one should include in each Section:
+
+Tier 0
+------
+- #summit-announce
+- #summit-simonyi
+- #summit-auxtel
+
+Tier 1
+------
+- #xxx-worklog
+- #xxx-support
+
+Tier 2
+------
+- User Preference
+
+Tier 3
+------
+- All other channels
+
 
 Individual Channel Descriptions and Guidelines
 ==============================================
@@ -104,7 +125,7 @@ People who participate in testing or infrastructure support/development are expe
 
 Because work is being coordinated across multiple channels,this channel aims to restrict the need to make announcements multiple places and avoid the scenario of accidentally not informing all impacted parties.
 
-For items having substantial impact, scheduling should first be carried out as part of the `SUMMIT Jira calendar <https://jira.lsstcorp.org/secure/DoItBetterCalendar.jspa>`_ process.
+For items having substantial impact, scheduling should first be carried out as part of the `SUMMIT Jira calendar <https://rubinobs.atlassian.net/plugins/servlet/ac/doitbetter.calendar/calendar-page>`_ process.
 
 **Announcement Protocol:**
 
@@ -127,40 +148,16 @@ For items having substantial impact, scheduling should first be carried out as p
   
 - This channel is specific to summit related activities.
   Announcements for testing using other test-stands are to be made on test-stand specific channels, following the same rules.
-  This includes #rubinobs-tucson-teststand and #rubinobs-base-teststand
-
-- The summit is an active observatory with many teams working on different tasks. Personnel on the summit should never be discourgaged from announcing their work as impacts may be unforseen or unpredictable.
-
-
-#summit-control-room
---------------------
-This room is actively monitored by observers and shift managers. This may be used to bring urgent concerns to observers.
-
-This is a single channel for both telescopes which is actively monitored by telescope specialists and anyone controlling the system.
-As observers are expected to actively monitor and reply to this channel, extended conversations may impact efficient work and discussion via zoom is encouraged.
-Breakout rooms can be used if multiple simultaneous conversations are required.
-
-This channel may be used as the area where the copying/pasting of code snippets happens while supporting via zoom, therefore context will often not be provided.
-Troubleshooting in this area should be either system-wide, or concerning other observatory systems seperate from the telescopes.
-
-An example of troubleshooting belonging to this channel is found in the following figure.
-
-.. figure:: ./_static/dialog_example.png
-    :name: #summit-control-room example
-    :width: 560
-    :height: 399
-
-    An example of the type of troubleshooting conversation that should take place in #summit-control-room.
+  This includes #tucson-teststand and #base-teststand.
 
+- The summit is an active observatory with many teams working on different tasks. 
+  Personnel on the summit should never be discouraged from announcing their work as impacts may be unforeseen or unpredictable.
 
 #summit-simonyi and #summit-auxtel
 ----------------------------------
 
 These rooms are for telescope system specific asynchronous conversation with remote support.
-They are passively monitored by on-shift observers with no expectation of an immediate response.
-Generally, the content will be read at the start and end of a shift, or during quiet periods.
-
-These channels are actively monitored by shift manager(s), who will directly contact observers if/when required.
+They are actively monitored by on-shift observers and shift manager(s).
 
 Example content:
 
@@ -174,7 +171,7 @@ Example content:
 
 - Not required, but used by some observers to give periodic status updates during the night.
 
-#auxtel-operations and #simonyi-operations
+#auxtel-discussion and #simonyi-discussion
 ------------------------------------------
 
 These channels are also telescope system specific but are dedicated for communication between people providing external support, such as looking at data as it comes in.
@@ -197,4 +194,18 @@ Example content:
 
 - New features in system behavior (e.g. mount shake)
 
+Channel Creation and Naming Guidelines for Summit Channels
+==========================================================
+
+The Tiered system reserves certain prefixes to help classify summit communication channels by their expected usage. 
+Therefore, the following are reserved for each Tier, and when creating a new Slack channel for summit use one should not use them unless you are certain the new channel will belong to the given Tier:
+
+- Tier 0: #summit-
+- Tier 1: #-worklog and #-support
+
+The naming guidelines for Tier 2 and Tier 3 channels are less restrictive, 
+but a few conventions should be followed:
+
+- Tier 2 channels benefit from having either a subsystem names (e.g. #simonyi-, #comcam-) or team names (#dm-, #sitcom-, #ts-) as a prefix. This is not strictly enforced.  
+
 This procedure was last modified |today|.
diff --git a/Safety/Enter-Observatory-Spaces/Enter-AuxTel-Telescope.rst b/Safety/Enter-Observatory-Spaces/Enter-AuxTel-Telescope.rst
new file mode 100644
index 00000000..c6aa2426
--- /dev/null
+++ b/Safety/Enter-Observatory-Spaces/Enter-AuxTel-Telescope.rst
@@ -0,0 +1,188 @@
+.. This is a template for an informative/general use document. 
+
+.. Review the README in this document's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: *Gonzalo Aravena*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: *Alysha Shugart*
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _Safe-entry-to-AuxTel:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+####################
+Safe Entry to AuxTel
+####################
+
+.. _Safe-entry-to-AuxTel-Overview:
+
+Overview
+========
+
+This document aims to provide the necessary guidelines and procedures for safely entering AuxTel. 
+It covers aspects related to access during nighttime operations, ventilation, calibrations, and daytime access. 
+Ensure you follow these instructions to guarantee your safety and the safety of the equipment.
+
+
+Safety Equipment for All Entries
+================================
+
+Each entry to the telescope, regardless of the reason, must mandatorily use the following safety equipment:
+
+- Helmet
+
+- Reflective vest
+
+- Safety shoes
+
+.. figure:: ./_static/Notice.png
+    :name: notice
+    :scale: 25 %
+
+    Safety Equipment
+
+.. admonition:: Important
+   
+   If you do not have any of these safety items, please contact the safety staff at the summit. 
+
+.. _Safe-entry-to-AuxTel-access-during-daytime:
+
+
+Access During Daytime
+=====================
+
+1. **Communication Protocols**
+   
+   - Announce your visit to the telescope indicating the reasons briefly via the Slack channels `#summit-auxtel <https://lsstc.slack.com/archives/C01K4M6R4AH>`__ and `#summit-announce <https://app.slack.com/client/T06D204F2/C01P41NUR1R>`__.
+
+   - Communicate by radio on channel 3 when entering the telescope during the day and night. This action is suggested.
+
+
+2. **Conditional access**
+
+   - Ensure that no images are being taken and no work is being done in the AuxTel dome that might be disrupted upon entering the telescope.
+
+
+3. **Entry door key**
+
+   - The key to access the main entrance door to the telescope will be hanging on the right side of the door just below the fire extinguisher sign. It is strictly requested that the keys must be always left in the same place when leaving the telescope.
+
+
+   .. figure:: ./_static/keys.png
+       :name: keys
+       :scale: 25 %
+
+       Key hook
+
+
+
+   .. note:: 
+       Exceptionally, the entrance door will currently be left unlocked.
+
+  
+
+.. _Safe-entry-to-AuxTel-access-during-ventilation:
+
+Access During Ventilation
+=========================
+
+.. note:: 
+
+   Review the weather conditions and :ref:`weather constraints <Observing-Constraints-AuxTel-Weather-Constraints>` before taking the decision to vent.
+
+
+1. **Ventilation Notification**
+
+   - Ventilation starts with a notification via Slack channels and/or radio channel 3.
+
+
+
+2. **Safety Precautions**
+
+   - Ensure the windows are fully open and the fan operates at 20%.
+
+   - Take special care not to lean on the windows or manipulate the fan while it is running.
+
+   - On the telescope's second floor, verify that the telescope is in a horizontal position and the dome is facing opposite the Sun to maximize the ventilation system.
+
+.. figure:: ./_static/vent.png
+    :name: Venting
+
+    Air extraction fan.
+
+
+
+.. _Safe-entry-to-AuxTel-access-during-calibrations:
+
+Access During Calibrations
+==========================
+
+.. warning::
+
+    Access is **NOT** permitted during calibrations unless there is an issue with the system that requires attention, and images can be interrupted or are not currently being taken. 
+    Ensure there are no announcements in Slack, and confirm with summit staff (daytime shift workers or an Observing Specialist) that no images are in progress.
+
+
+
+.. _Safe-entry-to-AuxTel-access-during-night-time-operations:
+
+Access During Night time Operations
+===================================
+
+1. **Entry Permissions**
+
+   - Only authorized personnel and the Observing Specialist team can enter without an external permit during operations.
+
+
+2. **Lighting Restrictions**
+   
+   .. warning:: 
+
+    During operations, it is prohibited to turn on building lights when entering the telescope.
+
+
+   .. caution:: 
+        
+    The use of flashlights or headlamp is permitted but they should point towards the ground and should be minimized to avoid interfering with observations.
+
+
+   .. tip:: 
+
+    Red light flashlights can be a good choice and they interfere much less than regular white light.
+
+
+.. _Safe-entry-to-AuxTel-behaviour-standards:
+
+Behavior Standards
+==================
+
+Maintain proper behavior at all times, including:
+
+- Being close to a radio (or always carrying one) and communicating your intentions to summit staff and on Slack.
+  
+- Following the :ref:`Safety Gate Procedure <Safety-Gate-Procedures-Overview>` and the :ref:`E-Stop procedure <AuxTel-Non-Standard-Procedures-E-Stop-Procedure>` as needed.
+  
+- Locking out movement when necessary following :ref:`LOTO procedure <Auxiliary-Telescope-AuxTel-LOTO-procedure>`.
+
+
+.. _Safe-entry-to-AuxTel-Emergency-Procedures:
+
+Emergency Procedures
+====================
+
+In case of any emergency, notify immediately via **radio channel 3 for Rubin staff, or channel 1 for after hours emergencies.**
+For detailed instructions on specific types of emergencies, please refer to the :ref:`Emergency Response Guide <Safety-emergency-response-guide>`.
+Remember to always keep the list of :ref:`Emergency Numbers <summit-contact-numbers-emergency-numbers>` handy for any urgent situations.
+
+
+This procedure was last modified on |today|.
diff --git a/Safety/Enter-Observatory-Spaces/Level4-Access.rst b/Safety/Enter-Observatory-Spaces/Level4-Access.rst
new file mode 100644
index 00000000..cc2950a4
--- /dev/null
+++ b/Safety/Enter-Observatory-Spaces/Level4-Access.rst
@@ -0,0 +1,6 @@
+.. _Enter-Observatory-Spaces-Level4-Access:
+
+
+###########################
+Level 4 Access Restrictions
+###########################
\ No newline at end of file
diff --git a/Safety/Enter-Observatory-Spaces/_static/Notice.png b/Safety/Enter-Observatory-Spaces/_static/Notice.png
new file mode 100644
index 00000000..a7939030
Binary files /dev/null and b/Safety/Enter-Observatory-Spaces/_static/Notice.png differ
diff --git a/Safety/Enter-Observatory-Spaces/_static/keys.png b/Safety/Enter-Observatory-Spaces/_static/keys.png
new file mode 100644
index 00000000..448b3cc7
Binary files /dev/null and b/Safety/Enter-Observatory-Spaces/_static/keys.png differ
diff --git a/Safety/Enter-Observatory-Spaces/_static/vent.png b/Safety/Enter-Observatory-Spaces/_static/vent.png
new file mode 100644
index 00000000..df5810f3
Binary files /dev/null and b/Safety/Enter-Observatory-Spaces/_static/vent.png differ
diff --git a/Safety/Enter-Observatory-Spaces/index.rst b/Safety/Enter-Observatory-Spaces/index.rst
new file mode 100644
index 00000000..3e89ad44
--- /dev/null
+++ b/Safety/Enter-Observatory-Spaces/index.rst
@@ -0,0 +1,31 @@
+.. Review the README in this directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this file's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Do not delete the expected section title, reference or related comments provided from the template.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. This is the label that can be used as for cross referencing this file.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _Safety-Entry:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+#################################
+Enter Observatory Spaces
+#################################
+
+.. This section should provide a brief, top-level description of the page.
+
+
+Before entering AuxTel read this document carefully
+
+.. toctree::
+    :maxdepth: 2 
+    :titlesonly:
+    :glob:
+
+    Enter-AuxTel-Telescope.rst
+
diff --git a/Safety/Safety-Systems/GIS.rst b/Safety/Safety-Systems/GIS.rst
index 20abb699..67eb9021 100644
--- a/Safety/Safety-Systems/GIS.rst
+++ b/Safety/Safety-Systems/GIS.rst
@@ -1,6 +1,390 @@
-.. _Safety-Systems-Control-Safety-Systems:
-
+.. _Safety-Systems-GIS:
 
 ######################
 GIS
-######################
\ No newline at end of file
+######################
+
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: *Jacqueline Seron*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: *Franco Colleoni*
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+.. _Safety-Systems-GIS-Overview:
+
+
+Overview
+========
+
+This document presents an introduction to the **General Interlock System (GIS)**, which plays a crucial 
+role in ensuring safety and efficiency across various subsystems at Vera Rubin Observatory.
+
+First, we provide an overview of the **structure** of the GIS, outlining its key components 
+and how they interact to maintain operational integrity. 
+Next, we explore the **safety matrix** of the GIS, detailing the various *detections* 
+and corresponding *actions* taken to prevent hazardous scenarios. 
+We describe **how users interact with the GIS**, including navigating the main controller interface 
+and executing bypass and reset *actions* when necessary. 
+Finally, we cover **troubleshooting** procedures to address any issues that may arise, 
+ensuring smooth and uninterrupted operations.
+
+.. maybe the troubleshooting section should be in another page?...
+
+
+.. __Safety-Systems-GIS-General-Interlock-system:
+
+General Interlock system
+========================
+
+The GIS is a critical system that communicates with various subsystems 
+to prevent dangerous situations by managing interlocks amongst them. 
+
+An **interlock** serves as a mechanism that prevents a system from proceeding 
+unless specific conditions are met. 
+
+Additionally, the implementation of **STO (Safe Torque Off)** further enhances safety 
+by halting the power supply to the motor when required.
+
+
+.. _Safety-Systems-GIS-Structure:
+
+Structure
+========================
+
+The GIS is composed of a **Main Controller** 
+(:ref:`cabinet on level 2 <Safety-Systems-GIS-Interacting-with-GIS-Main-Controller-Interface>`)
+and **several cabinets**. 
+The Main Controller manages all other cabinets, and user interaction is primarily through the Main Controller interface. 
+
+.. _Safety-Systems-GIS-connection-type:
+
+.. admonition:: The connection to the subsystems is by: 
+
+    * **Network**: TMA, Dome, M1M3, AuxTel.
+
+    * **Signals wires**: Earthquake, Access control, Pflow lift, Calibration Laser, and the top-end subsystems: M2Cam (that includes M2, M2 Hexapod, Camera Rotator, Camera Hexapod).
+
+TMA, M1M3 and Dome have their own interlock system (IS) but they communicate to the GIS. 
+For instance, if a TMA interlock is triggered, you will see it in the GIS Main controller. 
+
+.. note::
+    Currently as of June 6 2024, Dome IS is connected to GIS, but the signals between both are bypassed, as integration tests between both systems are still pending.
+
+.. Below the GIS design as of this date (March 29, 2024). 
+
+.. This diagram was copied and updated based on Guido Maulen `Diseno GIS's page`_ and additions from Franco Colleoni.
+
+.. _`Diseno GIS's page`: https://confluence.lsstcorp.org/display/IT/Diseno+GIS
+
+.. figure:: ./_static/GIS-design.png
+      :width: 500px
+      
+      GIS Design updated on June, 2024
+
+.. MUFA: Multiple-Use Fiber Access
+
+
+.. _Safety-Systems-GIS-Safety-Matrix-Detections-and-Actions:
+
+Safety Matrix. Detections and Actions
+=======================================
+
+
+The GIS uses a `safety matrix`_ to manage the interlocks, consisting of *detections* signals 
+and their corresponding *actions* for the subsystems.
+
+
+.. _`safety matrix`: https://github.com/lsst-ts/ts_tma_gis-documentation_user-interface-manual/blob/master/media/media/image50.png
+
+.. admonition:: Detection:
+
+    Specific condition or event within a subsystem that is reported *to the GIS*.
+
+.. admonition:: Action:
+    
+    Response to the corresponding *detection*, done *by the GIS*.
+
+
+Certain *detections* that could compromise the system **trigger an interlock** mechanism, which is an *action* taken to ensure the system's safety.
+
+
+Some *detections* have *actions* that only indicate their status, e.g. A fire interlock.
+
+.. make the example more clear
+
+.. list-table:: Examples
+ :widths: 20 30
+ :header-rows: 1
+
+ * - *Detection*
+   - *Action*
+ * - M1M3 mirror cell lights on 
+        (D-18 in GIS)
+
+   - TMA drives will be **STO (Safety Torque Off)** and engage the brakes.
+ * -
+   -
+ * - Big earthquake 
+        (D-2 in GIS)
+   - This will bring down most of the system. 
+        Engage TMA brakes, discharge capacitor banks, and STO the following components: TMA drives, Camera Cable Wrap drives, M1M3 actuators, M2 Hexapods, M2 actuators, Camera Rotator, Camera Hexapod, etc.
+
+
+
+.. The page T&S Safety Interlocks - (Franco Colleoni) has a link to the “GIS Operation User manual”.  Is there a current version?. Will look for it. 
+.. https://confluence.lsstcorp.org/pages/viewpage.action?pageId=16318660
+
+
+.. _Safety-Systems-GIS-Interacting-with-GIS:
+
+Interacting with GIS   
+======================
+
+.. _Safety-Systems-GIS-Interacting-with-GIS-Main-Controller-Interface:
+
+Main Controller Interface
+------------------------------
+
+.. figure:: ./_static/GIS-Main-Panel-Cabinet.jpeg
+      :width: 250px
+      :align: left
+      
+      GIS Main Panel Cabinet at level 2
+
+The Observing Specialists will interact with the Main Controller cabinet, located on Level 2.
+
+Occasionally, in the event of system errors, 
+it may be necessary to interact with other cabinets for reboots or power cycling. However, these activities are typically beyond the OS team's responsibilities.
+
+.. figure:: ./_static/GIS-Main-Panel-home.png
+      :width: 500px
+      
+      GIS General Overview
+
+
+The *GIS General Overview* (home), allows you to see the general status of the safety areas. The navigation bar (left) allows you to navigate between the subsystems.
+
+Some area names are straightforward, while others are:
+
+* **AcFiEa**: Access Control System / Fire Main Controller / Earthquake Control System. The safety gates to the pier intermediate level and to level 8 are referred as access control system.
+
+* **M2CAM**: M2 area, includes the M2 actuator, the M2 Hexapod, the Camera Hexapod and the Camera Rotator.
+
+* **PFLOW/AUX**: Pflow Controller & Auxiliary Elements.
+
+* **AUX IS**: Auxiliary Telescope Controller IS. It only has the *action* 'A-22 STO Earthquake Alarm'.
+
+The **GIS Detections and Actions** window, accessed via the :guilabel:`Det-Act` button, 
+displays all *detections* and *actions* across all systems, making it the most useful for monitoring.
+
+.. figure:: ./_static/GIS-detections-actions.png
+      :width: 700px
+
+      GIS Detections and Actions window
+
+The symbols and their representation are: 
+
+* |byp-orange-square| : Indicates the *detection* is bypassed. It logs alarms but it doesn't trigger any *action*.
+
+.. |byp-orange-square| image:: ./_static/BYP-orange-square.png
+   :width: 1em
+   :height: 1em
+   :align: middle
+
+* |red-square-excl| : Indicates a triggered interlock.
+
+.. |red-square-excl| image:: ./_static/red-square.png
+   :width: 1em
+   :height: 1em
+   :align: middle
+
+* |green-square| : Indicates no interlock is triggered for that *detection*.
+
+.. |green-square| image:: ./_static/green-square.png
+   :width: 1em
+   :height: 1em
+   :align: middle
+ 
+    
+
+.. admonition:: M2 changes in 2024
+
+    * **Addition**: Signal **D-20** "M2 mirror in *closed-loop*" as a cause for the *action* **A-5** "Block TMA motion".
+
+    * **Removal**: Signal **D-2** “Earthquake Alarm” from **A-13** “M2 STO” *action* signal.
+
+
+.. _Safety-Systems-GIS-Main-Controller-Interface:
+
+Bypass and reset *actions*
+--------------------------
+
+* Any user can reset a subsystem.
+
+* **Wired subsystems** are reset in GIS Main Panel. 
+
+  E.g Earthquake interlock is reset in the GIS (automatically when the detection dissapears).
+
+* **Network based subsystems** reset on their own in GIS main panel, once the reset is done in the specific subsystem. 
+
+  E.g. A M1M3 interlock should be reset in M1M3 IS and then it will be clear in GIS main panel.
+
+* Only admin user can bypass a subsystem.
+
+* *Detections* can be bypassed but *actions* cannot.
+
+* The 'D2 earthquake alarm' may occasionally be bypassed to prevent the TMA from losing power during power or capacitor bank issues. The acceleration threshold for the alarm is approximately 0.3g, which corresponds to a magnitude 5-6 earthquake.
+
+.. note::
+    
+    D4 GIS E-stop: Safety gate E-stops are frequently triggered, so they are currently physically bypassed. This bypass will be removed when operations begin.
+
+    For more information about safety gates refer to the :ref:`Safety Gates operation <Safety-Systems-Safety-Gate-Procedures:>` page.
+
+
+.. _Safety-Systems-GIS-Main-Controller-Interface:
+
+Troubleshooting
+================
+
+To troubleshoot, in addition to understand the system's structure, you may need to check the alarm logs. 
+Click at the bottom of the Main panel interface to access the Diagnostic Information section. 
+From here you can access the *Actual Alarm* and the *Alarm Log* tabs.
+
+.. admonition:: Important
+
+    Be aware that sometimes the *detection* disappears, indicating that the interlock is no longer triggered (possibly because someone has reset it), but the *action* may still be active.
+
+
+.. figure:: ./_static/GIS-actual-alarms-and-log.png
+      :width: 700px
+
+      GIS Actual Alarms and Alarm Log tabs.
+
+
+Note that the time reported for the alarms is still inaccurate and remains a pending issue to be resolved.
+
+.. _Safety-Systems-GIS-Troubleshooting-Interlocks-in-GIS-Main-Control-Panel:
+
+Interlocks in GIS Main Control Panel
+--------------------------------------------------
+
+Remember, depending on the :ref:`connection type <Safety-Systems-GIS-connection-type>`
+
+* **Wired subsystems** are :guilabel:`RESET` at the GIS Main Control Panel.
+
+* **Network-based systems** require resetting within their corresponding subsystem to clear the interlock in the Main Control panel.
+
+
+.. _Safety-Systems-GIS-Troubleshooting-Dealing-with-interlocks-in-GIS-Main-Control-Panel-Top-end-systems:
+
+Top End systems
+^^^^^^^^^^^^^^^^^
+
+**Top End systems** (M2CAM), are a special case. 
+The *M2CAM - Overview* does NOT indicate the status of each individual element, 
+but rather the **status of the CIRCUIT** that manages the **E-stop/STO** 
+for each component. 
+
+.. admonition:: Important
+
+    If one of the *Top End systems* goes to **FAULT** due to an interlock or after a **STO or power cycle**, to enable it you must :guilabel:`RESET` the GIS E-stop status buttons in *M2CAM - Overview*. 
+
+    In this case, even if the lights are green (indicating the E-stop circuit is okay), the :guilabel:`RESET` **is still required**.
+
+.. figure:: ./_static/GIS-M2CAM-reset-screen-M2.png
+      :width: 450px
+      :align: center
+      
+      GIS *M2CAM - Overview*. 
+      
+The status of CH1 and CH2 in all sytems only have a triggered interlock (indicated by |red-square-excl|), 
+if the E-stop at their cabinet is activated. For M2CAM this cannot happen because it's disabled.
+
+The *M2CAM - Actions* tab show the STO Action activation status.
+|red-square-excl|: STO is active, while |green-square| STO in NOT active.
+
+
+.. figure:: ./_static/GIS-M2CAM-action-M2actuators-error.png
+      :width: 450px
+      :align: center
+      
+      GIS *M2CAM - Actions* tab shows M2 Actuators STO active.
+
+As an example, to clear 'A-13 STO M2 Actuators' *action* in place (indicated by |red-square-excl|), go to *M2CAM - Overview* and press :guilabel:`RESET` under 'M2 Actuator' (refer to the 2 previous images). After this, the A-13 action status should turn inactive (|green-square|).
+
+Note that when you press the :guilabel:`RESET` button in *M2CAM - Overview*,
+the Reset status indicator will briefly change from gray to green with a cross. If you don't see this change, press the button again.
+
+The *M2CAM - Detections* tab shows the signals: 'D-14 Camera rotator pin inserted' 
+and 'D-20 M2 mirror in closed-loop'.
+
+.. This may change to an autoreset action.
+
+.. _Safety-Systems-GIS-Troubleshooting-Dealing-with-interlocks-in-GIS-Main-Control-Panel-Procedures-for-triggered-interlocks:
+
+Triggered interlocks
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Some triggered interlocks have an automatic reset, 
+while others may require your input. 
+This is shown in the table below. 
+
+.. we may want to add links to the procedures.
+
+.. list-table:: 
+ :widths: 20 25 
+ :header-rows: 1
+
+ * - GIS signal
+   - You should:
+ * - D2 Earthquake alarm
+   - *Auto reset (when earthquake stop)*
+ * - D3 GIS Internal failure
+   - Power cycle GIS cabinet
+ * - D4 GIS Estops
+   - Reset triggered Estop at GIS panel
+ * - D5 Unauthorized Pier access
+   - Close 6th level safety gate
+ * - D5 Unauthorized Dome access
+   - Close 7th level safety gate (bypassed, July 2024)
+ * - D7, D8, D9, D17 (TMA signals)
+   - Reset at TMA EUI
+ * - D10 to D13 (Dome signals)
+   - Reset at Dome EUI
+ * - D14 Camara Rotator Pin inserted
+   - Reset at Camara Rotator EUI
+ * - D15, D16 (Pflow signals)
+   - *Auto reset (when lift position changes)*
+ * - D18 M1M3 Interlock
+   - Reset at M1M3 IS
+ * - D19 Man-lift parked
+   - *Not currently used (July, 2024)*
+ * - D20 M2 mirror in *closed-loop*
+   - Auto reset when M2 is in *closed-loop* again
+
+
+
+.. admonition:: A note on M1M3 IS interface
+
+    * Both *detections* and *actions* can be bypassed.
+    * Any event (*detection*) will trigger the GIS 'D18 M1M3 interlock'.
+    * When resetting an event, if it doesn't work press :guilabel:`RESET` twice.
+    
+    See more in `M1M3 Interlock System`_ page.
+
+.. _`M1M3 Interlock System`: https://confluence.lsstcorp.org/display/LTS/M1M3+Interlock+System
+
+.. When available add a link to the page for M1M3 IS  
+
+
+
+For more information visit the `GIS Tekniker page`_. 
+
+.. _`GIS Tekniker page`: https://github.com/lsst-ts/ts_tma_gis-documentation_user-interface-manual
diff --git a/Safety/Safety-Systems/Safety-Gate-Introduction.rst b/Safety/Safety-Systems/Safety-Gate-Introduction.rst
new file mode 100644
index 00000000..9d8f26c1
--- /dev/null
+++ b/Safety/Safety-Systems/Safety-Gate-Introduction.rst
@@ -0,0 +1,249 @@
+.. This is a template for an informative/general use document. 
+
+.. Review the README in this document's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: *Franco Colleoni, Jacqueline Seron*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: *none*
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _Safety-Systems-Safety-Gate-Introduction:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+
+################################
+Safety Gate Introduction
+################################
+
+
+.. _Safety-Gate-Introduction-Overview:
+
+Overview
+=========
+
+This document provides an introduction to the Safety gates used at the Vera C. Rubin Observatory, 
+including its components, functional states, and the emergency safety mechanisms in place.
+
+
+The **safety gate** is an electronic gateway designed to prevent access to 
+hazardous areas. At the Rubin Observatory, these areas are near 
+the telescope or dome while they are operational. 
+The gate is controlled by the associated Interlock System (IS).
+
+
+.. _Safety-Gate-Introduction-Safety-gates-at-the-Rubin-Observatory:
+
+Safety gates at the Rubin Observatory
+======================================
+
+Simonyi telescope has 2 safety gates, while the AuxTel telescope has one. The table below shows some of their details.
+
+=========================  =======================  =========================
+|                          **AuxTel**               **Simonyi**
+=========================  =======================  =========================
+| Gate Location            Bottom of the stairs     | - Level 6
+                                                    | - Level 7 
+-------------------------  -----------------------  -------------------------
+Protected area             | 2nd floor              | - Intermediate pier 
+                                                    | - Level 8
+-------------------------  -----------------------  -------------------------
+Controlled by IS           AuxTel IS                GIS
+-------------------------  -----------------------  -------------------------
+Bypass/override button     Outside AuxTel Main      GIS Main Cabinet 
+                           Cabinet
+=========================  =======================  =========================
+
+
+
+
+.. _Safety-Gate-Introduction-Components:
+
+Components
+============
+
+The **main components** of the gate are:
+
+#. **Frame**, the mechanical frame of the gate attached to the floor.
+#. **Gate** can be opened and closed like a regular gate.
+#. **Handle** used to physically open/close the gate, and to attach the gate to the frame.
+#. **Control buttons** to open/close the gate electronically.
+#. **Status Indicators** LEDs that indicate the gate status.
+
+.. Fig2. Safety gate components.
+
+.. figure:: ./_static/safety-gate-components.png
+      :width: 350px
+      
+      Safety gate components
+
+
+.. _Safety-Gate-Introduction-Gate-Functional-States:
+
+Gate Functional States 
+===========================
+
+.. - section 2
+
+The gate has three functional states: 1: Open, 2: Closed, 3: Error.
+
+.. _Safety-Gate-Introduction-Gate-Functional-States-Open:
+
+Open
+-----------
+
+When the gate is open, its electronics send an **interlock signal** to the IS,
+**disabling the drives** for the telescope and dome. 
+
+Consequently, neither the telescope nor the dome can be operated with the gate open. 
+This ensures that people working in the protected area are safe from unexpected movement.
+
+.. _Safety-Gate-Introduction-Gate-Functional-States-Closed:
+
+Closed
+------------
+When the gate is closed, its electronics **clear the interlock** to the IS, 
+**enabling the drives** for the telescope and dome drives. 
+
+A closed gate indicates that no one is beyond the gate, making it safe to allow movements.
+
+
+.. warning::
+    It is physically possible to go through the gate without opening it
+    (by entering from the stairs side), but this violates safety protocols 
+    and should **NOT** be done under normal circumstances.
+
+
+.. _Safety-Gate-Introduction-Gate-Functional-States-Error:
+
+Error
+----------
+
+In error mode **the gate cannot be locked again**. 
+This usually occurs after the emergency release has been activated. 
+This mechanism is described in the next section.
+
+
+.. _Safety-Gate-Introduction-Emergency-safety-mechanisms:
+
+Emergency safety mechanisms
+================================== 
+
+.. _Safety-Gate-Introduction-Emergency-safety-mechanisms-Emergency-release:
+
+Emergency release 
+---------------------
+.. section 5
+
+The gate has a **safety escape mechanism** located behind it, designed to disable the lock in case of emergency. 
+
+This mechanism is designed for situations where people might need to be inside while the gate is locked. 
+It is typically used in closed industrial areas, but this is less relevant for our situation.
+Personnel should not be in proximity to the telescope or dome while they are in operations,
+**except during engineering work**.
+
+When the emergency release is pressed the gate enters an **Error state** and cannot be locked again. 
+This is indicated by a red flashing light on the Status Indicators. 
+
+.. Fig8. Emergency release mechanism
+
+.. figure:: ./_static/emergency-release-mechanism.png
+      :width: 250px
+      
+      Emergency release mechanism not activated
+
+
+
+
+.. _Safety-Gate-Introduction-Emergency-safety-mechanisms-Gate-Emergency-Stop:
+
+Gate Emergency Stop
+---------------------
+
+.. section 6
+
+The gate E-STOP behaves the same way as other 
+:ref:`E-STOP <Daytime-Operations-Safety-Control-Safety-Systems-Emergency-Stop>`. 
+
+..  FIX THIS LINK!!! the labels in the page Control Safety systems have wrong labels 
+
+
+.. Fig9. Emergency stop button
+
+.. figure:: ./_static/emergency-stop-button.png
+      :width: 250px
+      
+      Emergency stop button
+
+.. _Safety-Gate-Introduction-Emergency-safety-mechanisms-Gate-Bypass-Override:
+
+Gate Bypass/Override 
+---------------------------
+.. section 7
+
+In exceptional cases where engineering work requires people to pass 
+through the gate while the telescope/dome are enabled,
+a bypass is available.
+
+This override **disables the gate interlock**, 
+allowing the gate to be opened or closed without triggering the interlock.
+
+
+.. _Safety-Gate-Introduction-Emergency-safety-mechanisms-Gate-override-AuxTel-safety-gate-bypass:
+
+AuxTel safety gate bypass
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The location of the bypass/override button for AuxTel is on 1st floor, outside the Main cabinet.
+
+
+
+.. figure:: ./_static/main-control-cabinet-gate-bypass.jpeg
+      :width: 350px
+      
+      Safety gate bypass button in the AuxTel Main cabinet
+
+
+.. note::
+    The override button in AuxTel  will soon be replaced by an illuminated action button which will light up when override/bypass is active.
+
+
+
+.. _Safety-Gate-Introduction-Emergency-safety-mechanisms-Gate-override-Simonyi-safety-gate-bypass:
+
+Simonyi safety gate bypass
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The bypass/override button for Simonyi is located in the GIS main cabinet on level 2,
+within Detections and Actions window (Det-Act) under the signals:
+
+* **D-5**: 'Unauthorized pier access'
+* **D-6**: 'Unauthorized pier access'.
+
+.. figure:: ./_static/GIS-gate-bypass.png
+      :width: 450px
+      
+      Safety gate bypass button in the GIS Main cabinet
+
+
+
+.. admonition::
+    Important
+
+
+    If the gate needs to be overridden, you must coordinate with users in the corresponding channel (`#summit_auxtel`_, `#summit_simonyi`_) and ensure that the system is returned to normal once the work is completed. 
+
+For instructions on how to operate the gate go to the :ref:`Safety Gate procedures <Safety-Systems-Safety-Gate-Procedures>` page.
+
+
+.. _#summit_auxtel: https://lsstc.slack.com/archives/C01K4M6R4AH
+.. _#summit_simonyi: https://lsstc.slack.com/archives/C04HULH5HHD
diff --git a/Safety/Safety-Systems/Safety-Gate-Procedures.rst b/Safety/Safety-Systems/Safety-Gate-Procedures.rst
new file mode 100644
index 00000000..dd2c522c
--- /dev/null
+++ b/Safety/Safety-Systems/Safety-Gate-Procedures.rst
@@ -0,0 +1,173 @@
+.. This is a template for an informative/general use document. 
+
+.. Review the README in this document's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: *Franco Colleoni, Jacqueline Seron*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: *none*
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _Safety-Systems-Safety-Gate-Procedures:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+###############################
+Safety Gate Procedures
+###############################
+
+.. _Safety-Gate-Procedures-Overview:
+
+Overview
+========
+
+.. This section should provide a brief, top-level description of the document's purpose and utilization. 
+
+The safety gate is a safety mechanism that prevents telescope and dome movement 
+when individuals pass through the gate.  
+It is controlled by the Interlock System (IS) of each telescope.
+
+This document outlines the following:
+
+* **Gate operation**: opening and closing procedures, 
+
+* **Recover the safety gate** in an Error state. 
+
+
+For more information refer to the :ref:`Safety Gate Introduction <Safety-Systems-Safety-Gate-Introduction>`.
+
+
+
+.. _Safety-Gate-Procedures-Gate-operation:
+
+Gate operation
+========================
+
+Gate status:
+
+* **Fully open**: :guilabel:`Release` pressed, handle removed, physically open.
+
+* **Fully closed**: physically closed, handle inserted, and :guilabel:`Lock` pressed.
+
+.. warning::
+    If :guilabel:`Lock` is NOT pressed the IS will NOT register the gate as closed, even when is physically closed,
+    and the telescope and dome drives will remain disabled. 
+
+    If :guilabel:`Release` is pressed the IS will register the gate as open, even if the gate is physically closed.
+
+.. Fig3. Gate fully opened 
+.. Fig4. Gate in closed position
+
+
+.. figure:: ./_static/gate-fully-open-and-gate-fully-closed.png
+      :width: 500px
+      
+      Safety gate: fully opened (left), fully closed (right)
+
+
+                                       
+.. _Safety-Gate-Procedures-Gate-operation-Opening-the-gate:
+
+Opening the gate 
+------------------
+
+.. - section 4
+
+When the gate is fully closed, to open it:
+
+1. Press the :guilabel:`Release` button on the gate. 
+    The blue *Lock/Area Safe* indicator will turn off.
+
+2. Move the **handle** to the left and physically move the gate to the open position.
+    .. figure:: ./_static/lock-release-buttons.png
+        :width: 250
+        
+        The :guilabel:`Release` and :guilabel:`Lock` buttons        
+      
+
+.. _Safety-Gate-Procedures-Gate-operation-Closing-the-gate:
+
+Closing the gate
+------------------
+.. section 3
+
+When the gate is fully open, to close it:
+
+1. Move the gate to the **closed position**.
+
+2. Insert the handle into the frame. 
+    Notice that the *Safety Gate* indicator lights up.
+
+    .. figure:: ./_static/handle-in-closed-position.png
+      :width: 250px
+      
+      Handle in closed position
+
+    .. Fig5. Handle in closed position
+
+3. Press the :guilabel:`Lock` button. 
+    You should hear a click, and the *Lock/Area Safe* indicator should illuminate in blue, signaling that the handle cannot be moved and the gate is securely closed. 
+
+    .. Fig7. Locked gate indicator
+
+    .. figure:: ./_static/locked-gate-indicator.png
+        :width: 250px
+        
+        Locked gate indicator
+
+
+
+.. _Safety-Gate-Procedures-Activate-Deactivate-bypass:
+
+Activate/Deactivate safety gate bypass
+========================================
+
+Refer to the Safety Gate Intoduction page :ref:`Gate bypass section <Safety-Gate-Introduction-Emergency-safety-mechanisms-Gate-Bypass-Override>`.
+
+* Bypass AuxTel safety gate:
+    * To **activate**: press :guilabel:`Safety Gate Bypass`, it will stay pressed down after you release it. 
+    * To **deactivate**: press :guilabel:`Safety Gate Bypass` again, and it will return to its original position.
+* Bypass Simmonyi safety gate: 
+    * To **activate**: go to GIS *Detections and Actions* window, and press the :guilabel:`BYPASS` switch for the corresponding safety gate detection (D-5 for level 6,  D-6 for level 7). The bypass indicator |byp-orange-square| will appear for that detection in the GIS.
+    * To **deactivate**: press :guilabel:`BYPASS` again, and the GIS bypass indicator will dissapear.
+
+.. |byp-orange-square| image:: ./_static/BYP-orange-square.png
+   :width: 1em
+   :height: 1em
+   :align: middle
+
+.. _Safety-Gate-Procedures-Enable-the-gate-after-emergency-release:
+
+Enable the gate after emergency release
+========================================
+
+When the :ref:`emergency release mechanism is activated  <Safety-Gate-Introduction-Emergency-safety-mechanisms-Emergency-release>`, 
+the gate enters the **error mode**. To recover it:
+
+.. section 5
+
+1. **Rearm the red handle** manually and move it to its normal position, as shown in figures below. 
+
+2. Press the :guilabel:`Release` button for 5 seconds. 
+    The Error mode will be reset, indicated by the red light disappearing.
+
+
+.. Fig8 . Emergency release mechanism
+
+.. figure:: ./_static/emergency-release.png
+      :width: 600px
+      :align: center
+      
+      Emergency release mechanism.
+      The left image shows the mechanism activated (red handle pressed), while the right image shows it in its normal position (inactive)
+
+
+
diff --git a/Safety/Safety-Systems/_static/BYP-orange-square.png b/Safety/Safety-Systems/_static/BYP-orange-square.png
new file mode 100644
index 00000000..201fab0f
Binary files /dev/null and b/Safety/Safety-Systems/_static/BYP-orange-square.png differ
diff --git a/Safety/Safety-Systems/_static/GIS-M2CAM-action-M2actuators-error.png b/Safety/Safety-Systems/_static/GIS-M2CAM-action-M2actuators-error.png
new file mode 100644
index 00000000..1d84637a
Binary files /dev/null and b/Safety/Safety-Systems/_static/GIS-M2CAM-action-M2actuators-error.png differ
diff --git a/Safety/Safety-Systems/_static/GIS-M2CAM-reset-screen-M2.png b/Safety/Safety-Systems/_static/GIS-M2CAM-reset-screen-M2.png
new file mode 100644
index 00000000..c2be56d2
Binary files /dev/null and b/Safety/Safety-Systems/_static/GIS-M2CAM-reset-screen-M2.png differ
diff --git a/Safety/Safety-Systems/_static/GIS-Main-Panel-Cabinet.jpeg b/Safety/Safety-Systems/_static/GIS-Main-Panel-Cabinet.jpeg
new file mode 100644
index 00000000..d87f0610
Binary files /dev/null and b/Safety/Safety-Systems/_static/GIS-Main-Panel-Cabinet.jpeg differ
diff --git a/Safety/Safety-Systems/_static/GIS-Main-Panel-home.png b/Safety/Safety-Systems/_static/GIS-Main-Panel-home.png
new file mode 100644
index 00000000..858d2aa8
Binary files /dev/null and b/Safety/Safety-Systems/_static/GIS-Main-Panel-home.png differ
diff --git a/Safety/Safety-Systems/_static/GIS-actual-alarms-and-log.png b/Safety/Safety-Systems/_static/GIS-actual-alarms-and-log.png
new file mode 100644
index 00000000..3ea86bda
Binary files /dev/null and b/Safety/Safety-Systems/_static/GIS-actual-alarms-and-log.png differ
diff --git a/Safety/Safety-Systems/_static/GIS-design.png b/Safety/Safety-Systems/_static/GIS-design.png
new file mode 100644
index 00000000..e2932921
Binary files /dev/null and b/Safety/Safety-Systems/_static/GIS-design.png differ
diff --git a/Safety/Safety-Systems/_static/GIS-detections-actions.png b/Safety/Safety-Systems/_static/GIS-detections-actions.png
new file mode 100644
index 00000000..986eab4b
Binary files /dev/null and b/Safety/Safety-Systems/_static/GIS-detections-actions.png differ
diff --git a/Safety/Safety-Systems/_static/GIS-gate-bypass.png b/Safety/Safety-Systems/_static/GIS-gate-bypass.png
new file mode 100644
index 00000000..fbd91dc7
Binary files /dev/null and b/Safety/Safety-Systems/_static/GIS-gate-bypass.png differ
diff --git a/Safety/Safety-Systems/_static/emergency-release-mechanism.png b/Safety/Safety-Systems/_static/emergency-release-mechanism.png
new file mode 100644
index 00000000..6e98a16e
Binary files /dev/null and b/Safety/Safety-Systems/_static/emergency-release-mechanism.png differ
diff --git a/Safety/Safety-Systems/_static/emergency-release.png b/Safety/Safety-Systems/_static/emergency-release.png
new file mode 100644
index 00000000..fa49fa4d
Binary files /dev/null and b/Safety/Safety-Systems/_static/emergency-release.png differ
diff --git a/Safety/Safety-Systems/_static/emergency-stop-button.png b/Safety/Safety-Systems/_static/emergency-stop-button.png
new file mode 100644
index 00000000..82ce8046
Binary files /dev/null and b/Safety/Safety-Systems/_static/emergency-stop-button.png differ
diff --git a/Safety/Safety-Systems/_static/gate-fully-open-and-gate-fully-closed.png b/Safety/Safety-Systems/_static/gate-fully-open-and-gate-fully-closed.png
new file mode 100644
index 00000000..ecadd7c4
Binary files /dev/null and b/Safety/Safety-Systems/_static/gate-fully-open-and-gate-fully-closed.png differ
diff --git a/Safety/Safety-Systems/_static/green-square.png b/Safety/Safety-Systems/_static/green-square.png
new file mode 100644
index 00000000..3f6c7432
Binary files /dev/null and b/Safety/Safety-Systems/_static/green-square.png differ
diff --git a/Safety/Safety-Systems/_static/handle-in-closed-position.png b/Safety/Safety-Systems/_static/handle-in-closed-position.png
new file mode 100644
index 00000000..c19388d0
Binary files /dev/null and b/Safety/Safety-Systems/_static/handle-in-closed-position.png differ
diff --git a/Safety/Safety-Systems/_static/lock-button.png b/Safety/Safety-Systems/_static/lock-button.png
new file mode 100644
index 00000000..b2e6ca42
Binary files /dev/null and b/Safety/Safety-Systems/_static/lock-button.png differ
diff --git a/Safety/Safety-Systems/_static/lock-release-buttons.png b/Safety/Safety-Systems/_static/lock-release-buttons.png
new file mode 100644
index 00000000..8a9c0b8c
Binary files /dev/null and b/Safety/Safety-Systems/_static/lock-release-buttons.png differ
diff --git a/Safety/Safety-Systems/_static/locked-gate-indicator.png b/Safety/Safety-Systems/_static/locked-gate-indicator.png
new file mode 100644
index 00000000..c7624251
Binary files /dev/null and b/Safety/Safety-Systems/_static/locked-gate-indicator.png differ
diff --git a/Safety/Safety-Systems/_static/main-control-cabinet-gate-bypass.jpeg b/Safety/Safety-Systems/_static/main-control-cabinet-gate-bypass.jpeg
new file mode 100644
index 00000000..57e3da39
Binary files /dev/null and b/Safety/Safety-Systems/_static/main-control-cabinet-gate-bypass.jpeg differ
diff --git a/Safety/Safety-Systems/_static/red-square.png b/Safety/Safety-Systems/_static/red-square.png
new file mode 100644
index 00000000..cb283703
Binary files /dev/null and b/Safety/Safety-Systems/_static/red-square.png differ
diff --git a/Safety/Safety-Systems/_static/safety-gate-components.png b/Safety/Safety-Systems/_static/safety-gate-components.png
new file mode 100644
index 00000000..5686aa05
Binary files /dev/null and b/Safety/Safety-Systems/_static/safety-gate-components.png differ
diff --git a/Safety/Safety-Systems/index.rst b/Safety/Safety-Systems/index.rst
index 36dfa8d2..e9f165cf 100644
--- a/Safety/Safety-Systems/index.rst
+++ b/Safety/Safety-Systems/index.rst
@@ -40,3 +40,21 @@ GIS
    :titlesonly:
 
    GIS.rst
+
+Safety Gate Introduction
+================================
+
+.. toctree::
+   :glob:
+   :titlesonly:
+
+   Safety-Gate-Introduction.rst
+
+Safety Gate Procedures
+================================
+
+.. toctree::
+   :glob:
+   :titlesonly:
+
+   Safety-Gate-Procedures.rst
\ No newline at end of file
diff --git a/Safety/index.rst b/Safety/index.rst
index 90644131..e7449804 100644
--- a/Safety/index.rst
+++ b/Safety/index.rst
@@ -111,15 +111,30 @@ Safety Systems
       :link-type: doc
       :padding: 4
 
-      GIS 
+      GIS introduction
 
-   .. grid-item-card:: Enter telescopes Safely
-      :link: Safety-Systems/GIS
+   .. grid-item-card:: Enter Observatory Spaces Safely
+      :link: Enter-Observatory-Spaces/index
+      :link-type: doc
+      :padding: 4
+
+      Procedures to enter telescopes while in operations, 
+      and other parts of the observatory building. 
+
+Enter Observatory Spaces
+=========================
+
+.. grid:: 1
+
+   .. grid-item-card:: Safe entry to AuxTel
+      :link: Enter-Observatory-Spaces/Enter-AuxTel-Telescope
       :link-type: doc
       :padding: 4
 
       Procedures to enter telescopes while in operations
 
+
+
 .. Here's is the left hand-side navigation. 
 .. toctree::
     :maxdepth: 4
@@ -130,6 +145,7 @@ Safety Systems
     out-of-hours-support.rst
     summit-contact-numbers.rst
     Safety-Systems/index.rst
+    Enter-Observatory-Spaces/index.rst
 
 
 
diff --git a/Simonyi/Components/EUI-Access/index.rst b/Simonyi/Components/EUI-Access/index.rst
new file mode 100644
index 00000000..7df3f1ec
--- /dev/null
+++ b/Simonyi/Components/EUI-Access/index.rst
@@ -0,0 +1,93 @@
+.. _Simonyi-Components-EUI-Access-Index:
+
+.. This is a template for an informative/general use document. 
+
+.. Review the README in this document's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: *OS Team*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _Simonyi-Components-Simonyi-EUI-Access:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+
+####################
+AuxTel EUI Access
+####################
+
+.. _AuxTel-EUI-Access-Overview:
+
+Overview
+========
+
+.. This section should provide a brief, top-level description of the document's purpose and utilization. 
+
+This document explains how to access all the components of *AuxTel EUI*-- for ATMCS, ATSPectrograph and ATDome-- through a remote desktop.
+
+AuxTel EUI Access
+========================
+ 
+.. _Auxtel-EUI-Access-Setup:
+
+Setup to access the AuxTel EUI remote desktop 
+---------------------------------------------
+
+#. Install and open **Microsoft Remote Desktop**.
+
+#. Click :guilabel:`+` button on the top menu.
+
+#. Select "Gateway" from drop-down menu.
+
+#. Click the drop-down menu "Gateway" :raw-html:`&rarr;` "No gateway"
+
+.. figure:: /AuxTel/Non-Standard-Operations/_static/image-2023-11-8_17-6-47.png
+  :name: "Add a Gateway" pop-up window.
+
+
+#. Put *aux-brick01.cp.lsst.org* on the "PC name" :raw-html:`&rarr;` "Save"
+
+.. figure:: /AuxTel/Non-Standard-Operations/_static/Adding_AuxTel_EUI.png
+  :name: "PC name" field.
+
+
+.. note::
+    You need to configure this setup only once. 
+
+.. _Auxtel-EUI-Access-Connection:
+
+Connecting to the EUI Remote desktop
+------------------------------------
+
+#. Login with Username/PW of **ATMCS/ATSpectrograph/ATDome EUI access** on 1Password **AuxTel** Vault.
+
+
+#. The following tabs can now be accessible from the web-browser:
+
+    * *Main Box Dome Control:   http://139.229.170.45:8000/MainBoxControl.html*   
+
+    .. figure:: /AuxTel/Non-Standard-Operations/_static/EUI-ATDome.png    
+    
+    * *ACE Spectrograph: http://139.229.170.44:8000/Spectrograph.html*  
+
+    .. figure:: /AuxTel/Non-Standard-Operations/_static/EUI-ATSpec.png  
+    
+    * *LSST Auxiliary Telescope MCS & Pneumatics: http://139.229.170.47:8000/atmcs.html*
+    
+    .. figure:: /AuxTel/Non-Standard-Operations/_static/EUI-ATMCS.png  
+    
+    * *Top Box Control: http://139.229.170.46:8000/TopBoxControl.html*
+    
+    .. figure:: /AuxTel/Non-Standard-Operations/_static/EUI-Top-Control-Box.png
+
+This procedure was last modified on |today|.
\ No newline at end of file
diff --git a/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTHex-PXI-Controller-Reboot.rst b/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTHex-PXI-Controller-Reboot.rst
new file mode 100644
index 00000000..97abd3a3
--- /dev/null
+++ b/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTHex-PXI-Controller-Reboot.rst
@@ -0,0 +1,271 @@
+.. This is a template for troubleshooting when some part of the observatory enters an abnormal state. This comment may be deleted when the template is copied to the destination.
+
+.. Review the README in this procedure's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: *Ioana Sotuela, Te-Wei Tsai*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: *Kshitija Kelkar*
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _MTHex-PXI-Controller-Reboot:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+#######################################################################
+MTHexapod PXI Controller Reboot (Soft, Hard and Control System Restart)
+#######################################################################
+
+
+.. _MTHex-PXI-Controller-Reboot-Overview:
+
+Overview
+========
+
+.. In one or two sentences, explain when this troubleshooting procedure needs to be used. Describe the symptoms that the user sees to use this procedure. 
+
+This document provides detailed instructions on how to perform a soft reboot, hard reboot, and restart the 
+control system for the *MTHexapod* PXI controllers at the summit. These procedures are essential for 
+troubleshooting faults encountered during routine operations but might also be necessary during maintenance 
+and other non-standard observatory operations, such as scheduled power off. 
+
+
+
+.. _MTHex-PXI-Controller-Reboot-Error-Diagnosis:
+
+Error diagnosis
+===============
+
+.. This section should provide simple overview of known or suspected causes for the error.
+.. It is preferred to include them as a bulleted or enumerated list.
+.. Post screenshots of the error state or relevant tracebacks.
+
+When troubleshooting the EUI/CSC failed to connect to the control system, follow the sequential order of 
+the procedures below to re-establish control. If a procedure proves unsuccessful, proceed to the next 
+one:
+
+- :ref:`Restart Control system <MTHex-PXI-Controller-Reboot-Restart-Control-System>`
+- :ref:`Soft Reboot <MTHex-PXI-Controller-Reboot-Soft-Reboot>`
+- :ref:`Hard Reboot or Power off <MTHex-PXI-Controller-Reboot-Hard-Reboot>`
+
+.. _MTHex-PXI-Controller-Reboot-Prerequisites:
+
+Prerequisites
+=============
+
+- Ensure you have access to LSST-WAP network.
+- Obtain the necessary IP, account user, and password information from the *LSST 1Password MainTel Vault*.
+- Familiarity with Linux commands and the use of general *Power Distribution Unit (PDU)* for power cycling.
+
+
+.. _MTHex-PXI-Controller-Reboot-Procedure:
+
+Procedure Steps
+===============
+
+.. This section should include the procedure. There is no strict formatting or structure required for procedures. It is left to the authors to decide which format and structure is most relevant.
+.. In the case of more complicated procedures, more sophisticated methodologies may be appropriate, such as multiple section headings or a list of linked procedures to be performed in the specified order.
+.. For highly complicated procedures, consider breaking them into separate procedure. Some options are a high-level procedure with links, separating into smaller procedures or utilizing the reST ``include`` directive <https://docutils.sourceforge.io/docs/ref/rst/directives.html#include>.
+
+
+.. _MTHex-PXI-Controller-Reboot-Restart-Control-System:
+
+Restart Control System
+----------------------
+
+.. warning::
+    As the primary troubleshooting step to regain control, perform the restart of the control system if 
+    the CSC/EUI is entirely unresponsive and unable to establish a connection with the control system.
+
+    Before proceeding, make sure there are no active interlocks in the EUI and that no other EUI instance 
+    is running. For the MTCamHexapod, check if *runCamHexEui* is running by following commands in the terminal:
+
+    .. prompt:: 
+        
+        ps -aux | grep runCamHexEui
+
+    If processes are already running, you may need to identify who is running them and ask permission 
+    to end one (or both) so you can run your own EUI session. If another *runCamHexEui* is running
+
+    .. prompt:: 
+
+        sudo kill -9 {pid}
+
+        
+    Replace *runCamHexEui* with *runM2HexEui* for the *MTM2Hexapod*.
+
+
+.. _MTHex-PXI-Controller-ssh-connection:
+#.  **Establish an SSH connection to the MTHexapod PXI**: Using the credentials and hostnames found 
+    in the *LSST 1Password MainTel Vault* create an ssh tunnel from the terminal in the LSST-WAP network. 
+    
+    For the *MTCamHexapod*, the command would look like:
+
+    .. prompt::
+
+        ssh admin@camhex-pxi-controller.cp.lsst.org
+
+    For the *MTM2Hexapod*, the command would look like:
+
+    .. prompt::
+
+        ssh admin@m2-hexapod-pxi.cp.lsst.org
+
+
+#.  To **restart the control system** for the *MTCamHexapod*, run the command in the terminal:
+
+    .. prompt::
+
+        /etc/init.d/hexapod restart
+
+    
+    To **restart the control system** for the *MTM2Hexapod*, run the command in the terminal:
+
+    .. prompt::
+
+        /etc/init.d/hexapod restart
+
+    .. admonition:: Information
+        
+        To check the *MTCamHexapod* control system status in the terminal:
+
+        .. prompt::
+
+            /etc/init.d/hexapod status
+        
+        It will tell you whether the control system is running or not. To stop it, do:
+
+         .. prompt::
+
+            /etc/init.d/hexapod stop
+
+        To start it do:
+
+         .. prompt::
+
+            /etc/init.d/hexapod start
+       
+
+#.  **Allow 5-10 minutes for the system to initialize**: This period is necessary for the OS and control system 
+    to set up the EtherCat and Copley drives before making a connection through the CSC/EUI.
+
+
+
+
+.. _MTHex-PXI-Controller-Reboot-Soft-Reboot:
+
+.. warning::
+
+    Only proceed with :ref:`Soft Reboot <MTHex-PXI-Controller-Reboot-Soft-Reboot>` if EUI/CSC control is not connecting and 
+    the :ref:`restart of the control system <MTHex-PXI-Controller-Reboot-Restart-Control-System>` procedure 
+    proved unsuccessful to regain control.
+
+Soft Reboot
+-----------
+
+
+#.  **Establish an SSH connection to the MTCamHexapod/MTM2Hexapod PXI**: Using the credentials and hostnames found in 
+    the *LSST 1Password MainTel Vault* create an ssh tunnel from your terminal in the LSST-WAP network. 
+    (See command explicitly described in :ref:`above <MTHex-PXI-Controller-ssh-connection>`).
+
+#.  **Execute the reboot command**: To initiate a soft reboot of the PXI, type in the terminal:
+
+    .. prompt::
+
+        sudo reboot
+
+#.  **Allow 5-10 minutes for the system to reboot**: This time is necessary for the OS and control system 
+    to configure the EtherCat and Copley drives before attempting a connection through the CSC/EUI. 
+    
+    
+
+
+.. _MTHex-PXI-Controller-Reboot-Hard-Reboot:
+
+Hard Reboot
+-----------
+
+.. warning::
+
+    **Only proceed with a hard reboot, if the EUI control connection remains unsuccessful after 
+    a** :ref:`soft reboot <MTHex-PXI-Controller-Reboot-Soft-Reboot>`.
+
+    This method involves cutting power to the PXI and drives and should only be used as a last resort 
+    due to the potential risks.
+
+    If a power shutdown is scheduled, you can proceed until step 2 before the power on.
+
+
+#.  **Login into Utilities cabinet Power Distribution Unit (PDU) or MTM2Hexapod PDU**:
+    Depending on which hexapod you are rebooting, you need to follow either A or B.
+    
+    A.  For *MTCamHexapod*, while in the LSST-WAP, 
+        connect to *https://tea-pdu01.cp.lsst.org/* using the credentials stored in the *Operators vault* 
+        of *LSST 1Password* as *PDU Utilities Cabinet*. Click on :guilabel:`Outlets` on the left hand 
+        side menu to open the outlets screen. The description of each outlet can be found here.
+
+    .. figure:: /Simonyi/Non-Standard-Operations/_static/mtrot-controller-pxi-reboot-1.jpeg
+        :width: 700px
+
+        *MTCamHexapod* *https://tea-pdu01.cp.lsst.org* PDU outlets.
+   
+    B.  For *MTM2Hexapod* while in the LSST-WAP, 
+        connect to *https://pdu1-tea-as02.cp.lsst.org* using the credentials stored in the *MainTel vault* 
+        of *LSST 1Password* as *pdu1-tea-as02.cp.lsst.org*. Click on :guilabel:`Outlets` on the left hand 
+        side menu to open the outlets screen. 
+
+    .. figure:: /Simonyi/Non-Standard-Operations/_static/MTM2Hex-PDU.png
+        :width: 700px
+
+        *MTM2Hexapod* *https://pdu1-tea-as02.cp.lsst.org* PDU outlets. 
+   
+#.  **Power Cycle PXI and drives**: To **power** :guilabel:`Off` the system, first power off the PXI, followed by 
+    the drive. 
+    
+    A.  For *MTCamHexapod*, PXI is energized through :guilabel:`Outlet 8`, while the drives correspond to :guilabel:`Outlet 4` in the *https://tea-pdu01.cp.lsst.org PDU*.
+
+    B.  For *MTM2Hexapod*, power off the PXI which is :guilabel:`Outlet 2`, then turn off the drives in :guilabel:`Outlet 1`` in the *https://pdu1-tea-as02.cp.lsst.org PDU*.
+
+    .. note::
+
+        **Scheduled Power Off**
+
+        In case a scheduled power off is intended, do not continue with power on, and stop the 
+        procedure here.
+
+
+    When **powering** :guilabel:`On`, power on the cabinet first and wait for 1-3 min to let the EtherCAT slaves 
+    finish the setup on the drives. Power on the PXI controller and wait for 5 min to let the EtherCAT master finish the setup.
+    This delay is crucial for the Ethercat application within the PXI to establish a connection with the Copley drive.
+
+
+#.   **Wait for an additional 5-10 minutes after powering on before using the CSC/EUI**: 
+     This allows time for the OS and control system to configure the necessary drives. 
+
+
+#.  **Reset GIS interlocks** that were triggered during the power cycle.
+
+
+.. _MTHex-PXI-Controller-Reboot-Post-Condition:
+
+Post-Condition
+==============
+
+.. This section should provide a simple overview of conditions or results after executing the procedure; for example, state of equipment or resulting data products.
+.. It is preferred to include them as a bulleted or enumerated list.
+.. Please provide screenshots of the software status or relevant display windows to confirm.
+.. Do not include actions in this section. Any action by the user should be included in the end of the Procedure section below. For example: Do not include "Verify the telescope azimuth is 0 degrees with the appropriate command." Instead, include this statement as the final step of the procedure, and include "Telescope is at 0 degrees." in the Post-condition section.
+
+-   The PXI controller and its associated drives are correctly rebooted, allowing for successful connection 
+    and operation through the CSC/EUI.
+
+-   The EtherCat and Copley drives are properly set up and functional.
+
diff --git a/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTRot-Motion-Check.rst b/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTRot-Motion-Check.rst
new file mode 100644
index 00000000..5a1915b1
--- /dev/null
+++ b/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTRot-Motion-Check.rst
@@ -0,0 +1,141 @@
+.. This is a template for an informative/general use document. 
+
+.. Review the README in this document's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: Yijung Kang
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: Kshitija Kelkar
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _MTRot-Motion-Check:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+######################
+MTRotator Motion Check
+######################
+
+
+.. _MTRot-Motion-Check-Overview:
+
+Overview
+========
+
+.. This section should provide a brief, top-level description of the document's purpose and utilization. 
+
+This procedure checks the motion of the MTRotator under nominal movements, issued independently 
+from the *LOVE/MTQueue* or the MTRotator EUI. 
+
+.. warning::
+
+    This check cannot be accomplished if MTRotator is in ``FAULT`` on the CSC and/or with interlocks 
+    activated on the :guilabel:`GIS` or the MTRotator EUI. Please refer to :ref:`MTRotator Recovery 
+    Procedure <MTRotator-Recovery>`
+    to clear these warnings before proceeding.    
+
+
+.. _MTRotator-motion-check-script:
+
+Using the :file:`maintel/mtrotator/move_rotator.py` SAL script
+==============================================================
+
+Use the following configuration to run :file:`maintel/mtrotator/move_rotator.py` on the *LOVE/MTQueue* using the following configuration 
+
+.. code-block:: text
+    :caption: :file:`maintel/mtrotator/move_rotator.py`
+
+    angle = < +/ - angle you want the MTRotator to move (in degrees) >
+
+If this procedure fails, follow the next one using the MTRotator EUI. 
+
+.. _MTRotator-motion-check-eui:
+
+Using the MTRotator EUI
+=======================
+
+MTRotator EUI Access
+--------------------
+
+#.  Enter the virtual machine that controls the rotator *hexrot-vm02.cp.lsst.org* with your IPA account credentials.
+    
+#.  Once in the virtual machine, choose your user profile and enter your IPA password.
+
+#.  Open a terminal from the 'Activities' tab on top left - 
+
+    a. First check that there are no processes running on the EUI by typing
+
+        .. prompt:: bash
+
+            ps -aux | grep "runRotEui"
+
+        
+        If processes are already running, you may need to identify who is running them and ask permission 
+        to end one (or both) so you can run your own EUI session. If another :guilabel:`runRotEui` is 
+        running then type the following to kill the existing process
+
+        .. prompt:: 
+
+            sudo kill -9 {pid}
+
+
+    b.  Enter the :guilabel:`runRotEui` by typing 
+    
+        .. prompt:: bash
+
+            cd /rubin/rotator/build/
+            ./runRotEui
+
+
+Moving the MTRotator point to point (p2p) 
+-----------------------------------------
+
+#.  On the MTRotator Client, under the :guilabel:`Main tab`, ``State Cmd`` 
+    is selected, :guilabel:`StateTriggers` menu shows ``Enable`` under and then click 
+    :guilabel:`Send Command` button. This enables the MTRotator.
+    
+#.  To move the MTRotator, go to the :guilabel:`Commands to Send` 
+    section and in :guilabel:`Enabled Substate Triggers`, 
+    choose ``Move``. Then, input ``0`` degrees in the :guilabel:`Position Cmd` field and 
+    execute the movement by clicking on the :guilabel:`Send Command` button.
+
+#.  If the MTRotator does not follow:
+
+    a.  Transition to ``Standby`` state followed by the ``Enabled`` state again to reset the internal 
+        calculation of Simulink model. Then, do the p2p movement to origin again.
+
+    b.  It might also be possible that some internal signals are not triggered in Simulink module. 
+        You can try to do the p2p movement to another point such as 1 or 2 degree position first. If the 
+        MTRotator moves then you could move it back to the origin.
+
+
+.. note::
+    
+    If you want to p2p move the rotator after the soak test, consider the following steps:
+
+    a.  Issue a :guilabel:`Stop` command to MTRotator and wait for 5 min. This should make sure the internal queue of *track* commands from the soak test has been processed 
+        by Simulink model totally.
+
+        .. figure:: /Simonyi/Non-Standard-Operations/_static/MTRot-motion-check-1.png
+            :name: MTRot-motion-check-1
+            :scale: 40%
+
+    b.  Check the controller :guilabel:`State` is ``Enabled State`` and the :guilabel:`Actuator Enabled Sub-Sate` is ``Stationary``.
+
+        .. figure:: /Simonyi/Non-Standard-Operations/_static/MTRot-motion-check-2.png
+            :name: MTRot-motion-check-2
+            :scale: 50%
+
+ 
+.. warning::
+    MTRotator position should always be at 0 degrees in the ``Standby`` state.  
+
+This procedure was last modified on |today|.
\ No newline at end of file
diff --git a/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTRot-PXI-Controller-Reboot.rst b/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTRot-PXI-Controller-Reboot.rst
new file mode 100644
index 00000000..6dc4929f
--- /dev/null
+++ b/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/MTRot-PXI-Controller-Reboot.rst
@@ -0,0 +1,238 @@
+.. This is a template for troubleshooting when some part of the observatory enters an abnormal state. This comment may be deleted when the template is copied to the destination.
+
+.. Review the README in this procedure's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace:: Ioana Sotuela, Te-Wei Tsai
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: Kshitija Kelkar
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _MTRot-PXI-Controller-Reboot:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+#######################################################################
+MTRotator PXI Controller Reboot (Soft, Hard and Control System Restart)
+#######################################################################
+
+
+.. _MTRot-PXI-Controller-Reboot-Overview:
+
+Overview
+========
+
+.. In one or two sentences, explain when this troubleshooting procedure needs to be used. Describe the symptoms that the user sees to use this procedure. 
+
+This document provides detailed instructions on how to perform a soft reboot, hard reboot, and restart the 
+control system for the *MTRotator* PXI controllers at the summit. These procedures are essential for 
+troubleshooting faults encountered during routine operations but might also be necessary during maintenance 
+and other non-standard observatory operations, such as scheduled power off. 
+
+
+
+.. _MTRot-PXI-Controller-Reboot-Error-Diagnosis:
+
+Error diagnosis
+===============
+
+.. This section should provide simple overview of known or suspected causes for the error.
+.. It is preferred to include them as a bulleted or enumerated list.
+.. Post screenshots of the error state or relevant tracebacks.
+
+When troubleshooting the EUI/CSC failed to connect to the control system, follow the sequential order of 
+the procedures below to re-establish control. If a procedure proves unsuccessful, proceed to the next 
+one:
+
+- :ref:`Restart Control system <MTRot-PXI-Controller-Reboot-Restart-Control-System>`
+- :ref:`Soft Reboot <MTRot-PXI-Controller-Reboot-Soft-Reboot>`
+- :ref:`Hard Reboot or Power off <MTRot-PXI-Controller-Reboot-Hard-Reboot>`
+
+.. _MTRot-PXI-Controller-Reboot-Prerequisites:
+
+Prerequisites
+=============
+
+- Ensure you have access to LSST-WAP network.
+- Obtain the necessary IP, account user, and password information from the *LSST 1Password MainTel Vault*.
+- Familiarity with Linux commands and the use of general *Power Distribution Unit (PDU)* or *netbooter* for power cycling.
+
+
+.. _MTRot-PXI-Controller-Reboot-Procedure:
+
+Procedure Steps
+===============
+
+.. This section should include the procedure. There is no strict formatting or structure required for procedures. It is left to the authors to decide which format and structure is most relevant.
+.. In the case of more complicated procedures, more sophisticated methodologies may be appropriate, such as multiple section headings or a list of linked procedures to be performed in the specified order.
+.. For highly complicated procedures, consider breaking them into separate procedure. Some options are a high-level procedure with links, separating into smaller procedures or utilizing the reST ``include`` directive <https://docutils.sourceforge.io/docs/ref/rst/directives.html#include>.
+
+
+.. _MTRot-PXI-Controller-Reboot-Restart-Control-System:
+
+Restart Control System
+----------------------
+
+.. warning::
+    As the primary troubleshooting step to regain control, perform the restart of the control system if 
+    the CSC/EUI is entirely unresponsive and unable to establish a connection with the control system.
+
+    #.  Before proceeding, make sure there are no active interlocks in the EUI and that no other EUI instance 
+        is running. For the MTRotator, check if *runRotEui* is running by following commands in the terminal:
+
+        .. prompt:: 
+
+            ps -aux | grep runRotEui
+
+        If processes are already running, you may need to identify who is running them and ask permission 
+        to end one (or both) so you can run your own EUI session. If another *runRotEui* is running:
+
+        .. prompt:: 
+
+            sudo kill -9 {pid}
+
+    #.  You can do the following to check the MTRotator control system status in the terminal:
+
+        .. prompt::
+
+            /etc/init.d/rotator status
+        
+        It will tell you whether the control system is running or not. To stop it, do:
+
+         .. prompt::
+
+            /etc/init.d/rotator stop
+
+        To start it do:
+
+         .. prompt::
+
+            /etc/init.d/rotator start
+        
+
+
+#.  **Establish an SSH connection to the MTRotator PXI**: Using the credentials and hostnames found 
+    in the *LSST 1Password MainTel Vault* create an ssh tunnel in the terminal:
+
+    .. prompt::
+
+        ssh admin@rot-pxi-controller.cp.lsst.org
+
+#.  To **restart the control system** for the MTRotator, run the command in the terminal:
+
+    .. prompt::
+
+        /etc/init.d/rotator restart
+
+#.  **Allow 5-10 minutes for the system to initialize**: This period is necessary for the OS and control system 
+    to set up the EtherCat and Copley drives before making a connection through the CSC/EUI.
+
+
+
+
+.. _MTRot-PXI-Controller-Reboot-Soft-Reboot:
+
+.. warning::
+
+    Only proceed with :ref:`Soft Reboot <MTRot-PXI-Controller-Reboot-Soft-Reboot>` if EUI/CSC control is not connecting and 
+    the :ref:`restart of the control system <MTRot-PXI-Controller-Reboot-Restart-Control-System>` procedure 
+    proved unsuccessful to regain control.
+
+Soft Reboot
+-----------
+
+
+#.  **Establish an SSH connection to the MTRotator PXI** using the credentials and hostnames found in 
+    the *LSST 1Password MainTel Vault* (See :ref:`above <MTRot-PXI-Controller-Reboot-Restart-Control-System>`).
+
+#.  **Execute the reboot command**: To initiate a soft reboot of the PXI, type in the terminal:
+
+    .. prompt::
+
+        sudo reboot now
+
+#.  **Allow 5-10 minutes for the system to reboot**: This time is necessary for the OS and control system 
+    to configure the EtherCat and Copley drives before attempting a connection through the CSC/EUI. 
+    
+    
+
+
+.. _MTRot-PXI-Controller-Reboot-Hard-Reboot:
+
+Hard Reboot
+-----------
+
+.. warning::
+
+    **Only proceed with a hard reboot, if the EUI control connection remains unsucessful after 
+    a** :ref:`soft reboot <MTRot-PXI-Controller-Reboot-Soft-Reboot>`.
+
+    This method involves cutting power to the PXI and drives and should only be used as a last resort 
+    due to the potential risks.
+
+    If a power shutdown is scheduled, you can proceed until step 2 before the power on.
+
+
+#.  **Login into Utilities cabinet Power Distribution Unit (PDU)**: While in the LSST-WAP, 
+    connect to *https://tea-pdu01.cp.lsst.org/* using the credentials stored in the *Operators vault* 
+    of *LSST 1Password* as *PDU Utilities Cabinet*. 
+    Click on :guilabel:`Outlets` on the left hand 
+    side menu to open the outlets screen. The description of each outlet can be found here.
+
+    .. figure:: /Simonyi/Non-Standard-Operations/_static/mtrot-controller-pxi-reboot-1.jpeg
+   
+
+#.  **Power Cycle PXI and drives**: To **power** :guilabel:`Off` the system, first power off the PXI, followed by 
+    the drive. For MTRotator (:guilabel:`Camera Rotator` in *PDU*), the PXI is connected to outlet 6, 
+    and drives in outlet 5. 
+
+    .. note::
+
+        **Scheduled Power Off**
+
+        In case a scheduled power off is intended, do not continue with power on, and stop the 
+        procedure here.
+
+
+    When **powering** :guilabel:`On`, activate the drives first, and wait for at least 3 minutes before powering 
+    on the PXI. This delay is **crucial** for the Ethercat application within the PXI to establish a 
+    connection with the Copley drive.
+
+
+#.   **Wait for an additional 5-10 minutes after powering on before using the CSC/EUI**: 
+     This allows time for the OS and control system to configure the necessary drives. 
+
+
+#.  **Reset GIS interlocks** that were triggered during the power cycle.
+
+.. warning:: 
+
+    When the MTRotator is in the ``OFFLINE Publish only`` state in the :guilabel:`runRotEui` you need to go to the 
+    :guilabel:`Offline Substate Commands` and then send the :guilabel:`System Ready` command. The 
+    DDS can then be enabled from ``OFFLINE`` state. Refer to :ref:`MTRotator Recovery 
+    procedure <MTRotator-Recovery>` for more details.
+
+
+
+.. _MTRot-PXI-Controller-Reboot-Post-Condition:
+
+Post-Condition
+==============
+
+.. This section should provide a simple overview of conditions or results after executing the procedure; for example, state of equipment or resulting data products.
+.. It is preferred to include them as a bulleted or enumerated list.
+.. Please provide screenshots of the software status or relevant display windows to confirm.
+.. Do not include actions in this section. Any action by the user should be included in the end of the Procedure section below. For example: Do not include "Verify the telescope azimuth is 0 degrees with the appropriate command." Instead, include this statement as the final step of the procedure, and include "Telescope is at 0 degrees." in the Post-condition section.
+
+-   The PXI controller and its associated drives are correctly rebooted, allowing for successful connection 
+    and operation through the CSC/EUI.
+
+-   The EtherCat and Copley drives are properly set up and functional.
diff --git a/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/index.rst b/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/index.rst
new file mode 100644
index 00000000..7386b338
--- /dev/null
+++ b/Simonyi/Non-Standard-Operations/MTCS/MTHexRot/index.rst
@@ -0,0 +1,12 @@
+.. MTCS-Non-standard-Operations-MTHexRot-Non-Standard-Procedures:
+
+############################
+MTHexapods and MTRotator
+############################
+
+.. toctree::
+    :maxdepth: 2
+    :titlesonly:
+    :glob:
+
+    *
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/Simonyi-LOTO-procedure.rst b/Simonyi/Non-Standard-Operations/MTCS/TMA/Simonyi-LOTO-procedure.rst
index e495f62c..130a90af 100644
--- a/Simonyi/Non-Standard-Operations/MTCS/TMA/Simonyi-LOTO-procedure.rst
+++ b/Simonyi/Non-Standard-Operations/MTCS/TMA/Simonyi-LOTO-procedure.rst
@@ -7,10 +7,22 @@
 	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
     - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
 
+
+.. raw:: html
+
+    <style> .red {color:red} </style>
+.. role:: red
+
+
+.. raw:: html
+
+    <style> .gold {color:gold} </style>
+.. role:: gold
+
 .. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
-.. |author| replace:: *replace*
+.. |author| replace:: Karla Aubel
 .. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
-.. |contributors| replace:: *Safety Team*
+.. |contributors| replace:: Kshitija Kelkar, *safety team*
 
 .. This is the label that can be used as for cross referencing this procedure.
 .. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
@@ -20,8 +32,7 @@
 .. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
 .. An error will alert you of identical labels during the build process.
 
-.. warning::
-    DRAFT
+
 
 ######################
 Simonyi LOTO Procedure
@@ -34,9 +45,12 @@ Overview
 
 .. This section should provide a brief, top-level description of the procedure's purpose and utilization. Consider including the expected user and when the procedure will be performed.
 
-AuxTel must be under LOTO (lock-out tag-out) any time physical work is undertaken on the mount or the dome. 
-When working with environmental sensors, on the truss, mirrors, or anywhere in the dome where unexpected movement could cause a safety hazard, the telescope must be locked out. 
-Trained summit support staff may use this procedure if they meet all of the preconiditon requirements. 
+This document describes how to prevent any telescope movement as a safety measure through **Lock-Out-Tag-Out** (**LOTO**) 
+procedure. To perform this procedure, LOTO training must have been received. Observers during operations may be 
+expected to LOTO the **Telescope Main Assembly** (**TMA**) due to unforeseen work done at night. The TMA LOTO is done directly 
+in the **Oil Supply System** (**OSS**).
+
+
 
 .. _Simonyi-LOTO-procedure-Precondition:
 
@@ -47,19 +61,10 @@ Precondition
 .. It is preferred to include them as a bulleted or enumerated list.
 .. If there is a different procedure that is critical before execution, carefully consider if it should be linked within this section or as part of the Procedure section below (or both).
 
+.. warning::
 
-.. _Simonyi-LOTO-procedure-Post-Condition:
-
-Post-Condition
-==============
-
-.. This section should provide a simple overview of conditions or results after executing the procedure; for example, state of equipment or resulting data products.
-.. It is preferred to include them as a bulleted or enumerated list.
-.. Please provide screenshots of the software status or relevant display windows to confirm.
-.. Do not include actions in this section. Any action by the user should be included in the end of the Procedure section below. For example: Do not include "Verify the telescope azimuth is 0 degrees with the appropriate command." Instead, include this statement as the final step of the procedure, and include "Telescope is at 0 degrees." in the Post-condition section.
-
-The drives are powered off and the AuxTel Control cabinet is locked from the outside. 
-The Simonyi Telescope is under LOTO and is not able to move by any controls.
+    To perform this procedure formal LOTO training must have been received; refer also to 
+    the `TMA LOTO Procedure video. <https://drive.google.com/file/d/1rOvu1ITDCm0HNepfvoBWMzhGZkMPkKnH/view>`_ 
 
 .. _Simonyi-LOTO-procedure-Procedure-Steps:
 
@@ -71,19 +76,124 @@ Procedure Steps
 .. For highly complicated procedures, consider breaking them into separate procedure. Some options are a high-level procedure with links, separating into smaller procedures or utilizing the reST ``include`` directive <https://docutils.sourceforge.io/docs/ref/rst/directives.html#include>.
 
 
+Applying LOTO on OSS
+--------------------
 
-.. _Simonyi-LOTO-procedure-Troubleshooting:
+.. note::
 
-Troubleshooting
-===============
+    **LOTO box**
+    
+    Keys and locks are inside the LOTO Box. You can find LOTO box (with a tag "Electronic team" on the box) on 
+    Level 1 in the OSS room. If you cannot find or open that LOTO box, you can take a LOTO box from the meeting room 
+    on Level 2.
+
+    .. image:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-7.png
+     :width: 30%
+    .. image:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-8.jpeg
+     :width: 30%
+     
+     
+
+
+
+
+#.  **Announcement**: Before/right after applying LOTO on the OSS, announce "LOTO on the OSS" on  *#summit-announce* and/or *#summit-simonyi*.
+
+#.  **Turning off the OSS**: Turn :guilabel:`OFF` the OSS in the EUI panel (indicated by the :gold:`circle` in the following Figure)
+
+    .. figure:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-1.png
+     :name: tma-loto-1
+     
+     Figure 1: The :guilabel:`OSS GENERAL VIEW` in the TMA EUI can be accessed by entering the :guilabel:`MONITOR & CONTROL` > :guilabel:`MAIN AXES` tab in the left vertical menu panel of the EUI. 
+
+#.  **Wait until the OSS is off**:  the :guilabel:`status` turns `Idle` and :guilabel:`OSS` flag goes from green to gray. 
+    It takes around 5-10 minutes to complete turning off the OSS. 
+
+    .. figure:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-2.png
+     :name: tma-loto-2
+     
+     Figure 2: The OSS :guilabel:`status` indicator (Zoom view of the top left sdection of the :guilabel:`OSS GENERAL VIEW` shown in Figure 1)     
+
+
+
+#.  **Applying LOTO on the OSS Pump**: Go to the OSS room from Level 1 (first floor). Apply LOTOs on the OSS pump switches (highlighted by the :red:`box` in
+    the following Figure). Close valves (Position "—-") and put locks on the holes to apply three LOTOs on the safety 
+    switches of the OSS pumps.
+
+    .. figure:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-3.png
+     :name: tma-loto-3
+     
+     Figure 3: Location of the OSS Pump Switches on Level 1     
+    .. image:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-4.png
+     :width: 30%
+    .. image:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-5.png
+     :width: 30%
+    .. image:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-6.png
+     :width: 30%
+
+    Figure 4: OSS Pump Valves in closed position and locked.  
+
+Unlocking LOTO on OSS
+---------------------
+
+#.  Go to the the OSS room and remove the locks from the pump switches. Find the key for each lock from the LOTO box 
+    and match the number on the key and the lock. 
+
+#.  Put the LOTO locks with the keys back into the LOTO box.
+
+#.  Open the switches (Position "|") on the pump (See the Figure 5 below).
+
+    .. figure:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-9.png
+     :name: tma-loto-9
+     
+     Figure 5
+
+#.  Turn on the OSS from TMA EUI (**Optional**). 
+
+#.  Announce the status of the OSS on  *#summit-announce* and/or *#summit-simonyi*.
+
+.. note::
+
+    **LOTO at night**
+
+    During night-time operations, only **ONE** pump needs to be locked 
+    to consider the TMA fully under LOTO. This helps to move the process faster by taking into consideration the 
+    reduced on-summit personnel (~ 2 persons operation at night) and mitigating situations like when one cannot find the LOTO boxes, risk of losing 
+    multiple locks + keys, leaving lights on longer etc.
+
+
+
+
+.. _Simonyi-LOTO-procedure-Post-Condition:
+
+Post-Condition
+==============
+
+.. This section should provide a simple overview of conditions or results after executing the procedure; for example, state of equipment or resulting data products.
+.. It is preferred to include them as a bulleted or enumerated list.
+.. Please provide screenshots of the software status or relevant display windows to confirm.
+.. Do not include actions in this section. Any action by the user should be included in the end of the Procedure section below. For example: Do not include "Verify the telescope azimuth is 0 degrees with the appropriate command." Instead, include this statement as the final step of the procedure, and include "Telescope is at 0 degrees." in the Post-condition section.
+
+#.  **After applying LOTO on OSS** 
+    Telescope is unable to move. OSS is under LOTO shows :guilabel:`status` as `Idle` and the three pumps in :red:`red`, down to the left in the image.
+
+    .. figure:: /Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-10.png
+     :name: tma-loto-10  
+     
+     Figure 6: The :guilabel:`OSS GENERAL VIEW` when OSS is under LOTO
+
+#.  **After unlocking LOTO on OSS** 
 
-.. This section should include troubleshooting information. Information in this section should be strictly related to this procedure.
+    -   OSS idle but not turned on (:red:`Need Figure`)
 
-.. If there is no content for this section, remove the indentation on the following line instead of deleting this sub-section.
+    -   OSS turned on after removing LOTO  (:red:`Need Figure`)
 
-No troubleshooting information is applicable to this procedure.
-In the IMPOSSIBLE event that the telescope moves after turning off all three breakers, stop work immediately and notify the day crew, including Jacques Sebag, Mario Rivera, and the electronics team. 
+.. _Simonyi-LOTO-procedure-Contingency:
 
+Contingency
+===========
 
+Announce the status of locking and unlocking the LOTO in *#summit-simonyi* and/or *#summit-announce* and/or activate 
+the `Out of hours support <https://obs-ops.lsst.io/Safety/out-of-hours-support.html#safety-out-of-hours-support>`_.
 
 This procedure was last modified |today|.
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-1.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-1.png
new file mode 100644
index 00000000..d174d74c
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-1.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-10.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-10.png
new file mode 100644
index 00000000..3002a27f
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-10.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-2.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-2.png
new file mode 100644
index 00000000..7011ef8e
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-2.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-3.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-3.png
new file mode 100644
index 00000000..c6dbf1ab
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-3.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-4.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-4.png
new file mode 100644
index 00000000..992cf981
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-4.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-5.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-5.png
new file mode 100644
index 00000000..8981641c
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-5.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-6.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-6.png
new file mode 100644
index 00000000..239c2da4
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-6.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-7.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-7.png
new file mode 100644
index 00000000..1c33a770
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-7.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-8.jpeg b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-8.jpeg
new file mode 100644
index 00000000..5db540f5
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-8.jpeg differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-9.png b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-9.png
new file mode 100644
index 00000000..c6dbf1ab
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/MTCS/TMA/_static/tma-loto-9.png differ
diff --git a/Simonyi/Non-Standard-Operations/MTCS/index.rst b/Simonyi/Non-Standard-Operations/MTCS/index.rst
index 168f49f6..0b76cba8 100644
--- a/Simonyi/Non-Standard-Operations/MTCS/index.rst
+++ b/Simonyi/Non-Standard-Operations/MTCS/index.rst
@@ -20,10 +20,17 @@ MTCS
 
     MTM1M3/index.rst
 
+.. toctree::
+    :maxdepth: 2
+    :titlesonly:
+    :glob:
+
+    MTM2/index.rst
 
 .. toctree::
     :maxdepth: 2
     :titlesonly:
     :glob:
 
-    MTM2/index.rst
\ No newline at end of file
+    MTHexRot/index.rst
+
diff --git a/Simonyi/Non-Standard-Operations/_static/MTM2Hex-PDU.png b/Simonyi/Non-Standard-Operations/_static/MTM2Hex-PDU.png
new file mode 100644
index 00000000..4823daa2
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/_static/MTM2Hex-PDU.png differ
diff --git a/Simonyi/Non-Standard-Operations/_static/MTRot-motion-check-1.png b/Simonyi/Non-Standard-Operations/_static/MTRot-motion-check-1.png
new file mode 100644
index 00000000..7251f369
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/_static/MTRot-motion-check-1.png differ
diff --git a/Simonyi/Non-Standard-Operations/_static/MTRot-motion-check-2.png b/Simonyi/Non-Standard-Operations/_static/MTRot-motion-check-2.png
new file mode 100644
index 00000000..f5de5e44
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/_static/MTRot-motion-check-2.png differ
diff --git a/Simonyi/Non-Standard-Operations/_static/mtrot-controller-pxi-reboot-1.jpeg b/Simonyi/Non-Standard-Operations/_static/mtrot-controller-pxi-reboot-1.jpeg
new file mode 100644
index 00000000..7745f49c
Binary files /dev/null and b/Simonyi/Non-Standard-Operations/_static/mtrot-controller-pxi-reboot-1.jpeg differ
diff --git a/Simonyi/Troubleshooting/MTCS/HexRot/MTRotator-MTHexapods-PXI-Reboot/MTRotator-MTHexapods-PXI-Reboot.rst b/Simonyi/Troubleshooting/MTCS/HexRot/MTRotator-MTHexapods-PXI-Reboot/MTRotator-MTHexapods-PXI-Reboot.rst
deleted file mode 100644
index 8761a40c..00000000
--- a/Simonyi/Troubleshooting/MTCS/HexRot/MTRotator-MTHexapods-PXI-Reboot/MTRotator-MTHexapods-PXI-Reboot.rst
+++ /dev/null
@@ -1,126 +0,0 @@
-.. This is a template for troubleshooting when some part of the observatory enters an abnormal state. This comment may be deleted when the template is copied to the destination.
-
-.. Review the README in this procedure's directory on instructions to contribute.
-.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
-.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
-.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
-	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
-    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
-
-.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
-.. |author| replace:: *Name-of-Primary-Author*
-.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
-.. |contributors| replace:: *List-of-contributors*
-
-.. This is the label that can be used as for cross referencing this procedure.
-.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
-.. _Templates-Title-of-Troubleshooting-Procedure:
-.. Each section should includes a label for cross referencing to a given area.
-.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
-.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
-.. An error will alert you of identical labels during the build process.
-
-#########################
-MTRotator and MTHexapods PXI controller Reboot (Soft, Hard and Control System Restart)
-#########################
-
-.. note::
-    This is a procedure template file that is associated with a template directory structure. This note should be deleted when the section is properly populated.
-
-.. _Title-of-Troubleshooting-Procedure-Overview:
-
-Overview
-========
-
-.. In one or two sentences, explain when this troubleshooting procedure needs to be used. Describe the symptoms that the user sees to use this procedure. 
-
-This is a template for a troubleshooting procedure. It is performed by authorized and trained users.
-
-.. _Title-of-Troubleshooting-Procedure-Error-Diagnosis:
-
-Error diagnosis
-===============
-
-.. This section should provide simple overview of known or suspected causes for the error.
-.. It is preferred to include them as a bulleted or enumerated list.
-.. Post screenshots of the error state or relevant tracebacks.
-
-- This is an example bullet.
-
-.. _Title-of-Troubleshooting-Procedure-Procedure-Steps:
-
-Procedure Steps
-===============
-
-.. todo::
-   Make sure everything is in a safe or idle state before troubleshooting. Describe relevant safety steps if necessary.
-
-.. This section should include the procedure. There is no strict formatting or structure required for procedures. It is left to the authors to decide which format and structure is most relevant.
-.. In the case of more complicated procedures, more sophisticated methodologies may be appropriate, such as multiple section headings or a list of linked procedures to be performed in the specified order.
-.. For highly complicated procedures, consider breaking them into separate procedure. Some options are a high-level procedure with links, separating into smaller procedures or utilizing the reST ``include`` directive <https://docutils.sourceforge.io/docs/ref/rst/directives.html#include>.
-
-This paragraph describes some general guidance for this procedure. This paragraph is optional depending on its usefulness and the complexity of the procedure.
-
-In the case of a very straightforward procedure, a simple numbered list could be used, like as follows:
-
-.. warning::
-    For this example, this step is critical.
-
-.. _Title-of-Troubleshooting-Procedure-Critical-Step-1:
-
-#. This is Step 1 in a enumerated list. It happens to be very important.
-
-#. This is Step 2.
-
-#. This is step 3.
-
-#. Step 4 has two branches, but Step 5 is independent of Step 4.
-
-   a. If Condition A, do the following action in :ref:`Condition A Instructions <Title-of-Troubleshooting-Procedure-Condition-A-for-Step-4>`.
-
-   b. If Condition B, do the following action in :ref:`Condition B instructions <Title-of-Troubleshooting-Procedure-Condition-B-for-Step-4>`.
-
-   .. _Title-of-Troubleshooting-Procedure-Final-Step:
-
-#. Complete the procedure's final step.
-
-
-.. _Title-of-Troubleshooting-Procedure-Condition-A-for-Step-4:
-
-Condition A for Step 4
-----------------------
-
-This is an example of a sub-section, used when Condition A applied. Complete the steps in this section:
-
-#. Step 1 for Condition A.
-#. Return to :ref:`Step 5 <Title-of-Troubleshooting-Procedure-Final-Step>` in the section above.
-
-.. _Title-of-Troubleshooting-Procedure-Condition-B-for-Step-4:
-
-Condition B for Step 4
-----------------------
-
-This is an example of a sub-section, used when Condition B applied. Complete the steps in this section:
-
-#. Step 1 for Condition B.
-#. Return to :ref:`Step 5 <Title-of-Troubleshooting-Procedure-Final-Step>` in the section above.
-
-.. _Title-of-Troubleshooting-Procedure-Post-Condition:
-
-Post-Condition
-==============
-
-.. This section should provide a simple overview of conditions or results after executing the procedure; for example, state of equipment or resulting data products.
-.. It is preferred to include them as a bulleted or enumerated list.
-.. Please provide screenshots of the software status or relevant display windows to confirm.
-.. Do not include actions in this section. Any action by the user should be included in the end of the Procedure section below. For example: Do not include "Verify the telescope azimuth is 0 degrees with the appropriate command." Instead, include this statement as the final step of the procedure, and include "Telescope is at 0 degrees." in the Post-condition section.
-
-- This is an example bullet of a post-condition (Telescope azimuth is 0 degrees.)
-- This is another example of a post-condition (This procedure leaves the telescope with the E-stop activated.)
-
-.. _Title-of-Troubleshooting-Procedure-Contingency:
-
-Contingency
-===========
-
-If the procedure was not successful, report the issue in [relevant Slack channel] and/or activate the :ref:`Out of hours support <Safety-out-of-hours-support>`.
\ No newline at end of file
diff --git a/Simonyi/Troubleshooting/MTCS/HexRot/MTRotator-Recovery/MTRotator-Recovery.rst b/Simonyi/Troubleshooting/MTCS/MTHexRot/MTRotator-Recovery/index.rst
similarity index 86%
rename from Simonyi/Troubleshooting/MTCS/HexRot/MTRotator-Recovery/MTRotator-Recovery.rst
rename to Simonyi/Troubleshooting/MTCS/MTHexRot/MTRotator-Recovery/index.rst
index 448ae1a0..55a09cb7 100644
--- a/Simonyi/Troubleshooting/MTCS/HexRot/MTRotator-Recovery/MTRotator-Recovery.rst
+++ b/Simonyi/Troubleshooting/MTCS/MTHexRot/MTRotator-Recovery/index.rst
@@ -27,6 +27,7 @@
 
     <style> .green {color:green} </style>
 .. role:: green
+
 #########################
 MTRotator Recovery
 #########################
@@ -53,12 +54,11 @@ Error diagnosis
 
 * The difference between the MTRotator and the Camera Cable Wrap (CCW) is too large. Bulkhead limit switch activated; this is also called :guilabel:`Pull cord +` or :guilabel:`Pull cord -`. 
 
+    .. figure:: /Simonyi/Troubleshooting/_static/mtrot_recovery_1.png
+         :name: mtrot_recovery_1
+   
+         TMA EUI screenshot indicating the pull cord +/- alert highlighted by the red box
 
-
-.. figure:: /Simonyi/Troubleshooting/_static/mtrot_recovery_1.png
- :name: mtrot_recovery_1
-
-  TMA EUI screenshot indicating the pull cord +/- alert highlighted by the red box
 * :ref:`Safety Interlock <mtrot_recovery_5>` active in the MTRotator GUI 
 * :ref:`Simulink fault <mtrot_recovery_5>` in the MTRotator GUI 
 * CCW Interlock D-8 activated on the GIS (link here to the GIS interlock screenshot)
@@ -77,84 +77,92 @@ Procedure Steps
 .. For highly complicated procedures, consider breaking them into separate procedure. Some options are a high-level procedure with links, separating into smaller procedures or utilizing the reST ``include`` directive <https://docutils.sourceforge.io/docs/ref/rst/directives.html#include>.
 
 
-
-
-#.  **Transition MTRotator CSC to** ``STANDBY`` **status**
+#.  **Transition MTRotator CSC to** ``STANDBY`` **status**.
 
 
 #.  **Access the MTRotator EUI/GUI:**
 
-
     a.  Enter *hexrot-vm02.cp.lsst.org* with your IPA account credentials.
     
     b.  Once in the virtual machine, choose your user profile and enter your IPA password.
 
-    c.  open a terminal from the 'Activities' tab on top left and go to the following - 
+    c.  open a terminal from the 'Activities' tab on top left and go to the following: 
+
+        .. prompt:: bash
+
+             cd /rubin/
+             cd rotator/
+             cd build
+             ./runRotEui
+
 
-    .. prompt:: bash
 
-        cd /rubin/
-        cd rotator/
-        cd build
-        ./runRotEui
 #.  **Change from DDS Command Source to GUI mode:** 
 
+    .. _MTRotator-Recovery-Procedure-Step3:
+
     Click the :guilabel:`Parameters` tab in the MTRotator EUI, select ``GUI`` under 
     :guilabel:`Command Source`, and press :guilabel:`Set Command Source`. In case the 
-    GUI control is not possible consult the :ref:`Contingency section <MTRotator-Recovery-Contingency>` below for further guidance. 
+    GUI control is not possible consult the :ref:`Contingency section <MTRotator-Recovery-Contingency>` 
+    below for further guidance. 
 
     .. figure:: /Simonyi/Troubleshooting/_static/mtrot_recovery_2.png
-        :scale: 40%  
+        :width: 300  
         :name: mtrot_recovery_2
     
 
 #.  **Clear Simulink error in MTRotator GUI:**
 
+    .. _MTRotator-Recovery-Procedure-Step4A:
 
     a.  In the MTRotator EUI Main tab, select ``State Cmd`` under :guilabel:`Commands to Send`. 
         In :guilabel:`State Triggers`, select ``ClearError`` and click on the :guilabel:`Send Command` 
-        button. The **Simulink Error** light should be cleared now.
+        button. 
+        The **Simulink Error** light should be cleared now.
 
     .. figure:: /Simonyi/Troubleshooting/_static/mtrot_recovery_3.png
             :name: mtrot_recovery_3
-            :scale: 40%
+            :width: 300  
 
-    b.  When the **Safety Interlock fault** is :red:`activated`
+    b.  When the **Safety Interlock fault** is :red:`activated`.
 
     .. figure:: /Simonyi/Troubleshooting/_static/mtrot_recovery_4.png
         :name: mtrot_recovery_4
+        :width: 300  
+
 
     c.  When the **Safety Interlock fault** is deactivated.
 
     .. figure:: /Simonyi/Troubleshooting/_static/mtrot_recovery_5.png
         :name: mtrot_recovery_5
+        :width: 300  
+
 
 #.  **Reset MTRotator in GIS GUI at Level 2:**
-    
-    
 
-    a. Press :guilabel:`Bypass` by the D-8 (CCW Safety Device Actuated).  
+    .. _MTRotator-Recovery-Procedure-Step5A:
     
-        .. _step_5a
+    a. Press :guilabel:`Bypass` by the D-8 (CCW Safety Device Actuated).    
 
     .. figure:: /Simonyi/Troubleshooting/_static/mtrot_recovery_6.png
-     :name: mtrot_recovery_6  
-     :scale: 20%
+         :name: mtrot_recovery_6  
+         :width: 300  
 
     b.  Click :guilabel:`M2Cam` and then :guilabel:`Overview` (Default). Note that you should 
         see a :green:`x` mark on the square of :guilabel:`Reset`. If not, click the 
         :guilabel:`Reset` button again. 
 
     .. figure:: /Simonyi/Troubleshooting/_static/mtrot_recovery_7.png
-     :name: mtrot_recovery_7  
-     :scale: 20%
+         :name: mtrot_recovery_7  
+         :width: 300  
+
 
 #.  **Back to MTRotator GUI, clearError command to reset Safety Interlock:**
 
-    Following a similar process to :ref:`Step 4.a <_step_4a>`, the ``ClearError`` command will remove the 
+    Following a similar process to :ref:`Step 4.a <MTRotator-Recovery-Procedure-Step4A>`, the ``ClearError`` command will remove the 
     safety interlock.      
     
-#.  **Enable the MTRotator, then move it to zero degrees** 
+#.  **Enable the MTRotator, then move it to zero degrees**:
 
     To enable, ``State Cmd`` 
     is selected, :guilabel:`StateTriggers` menu shows ``Enable`` under and then click 
@@ -176,9 +184,9 @@ Procedure Steps
         Everything should be shown as green now.
 
 #.  **Release the bypass to the CCW in GIS GUI in Level 2** 
-    (Refer to :ref:`Step 5.a <step_5a>`)
+    (Refer to :ref:`Step 5.a <MTRotator-Recovery-Procedure-Step5A>`)
 
-#.  **Revert Command Source from EUI to DDS** (opposite to the :ref:`Step 3 <step_3>`) 
+#.  **Revert Command Source from EUI to DDS** (opposite to the :ref:`Step 3 <MTRotator-Recovery-Procedure-Step3>`) 
 
 
 Post-Condition
@@ -201,4 +209,4 @@ If the above procedure was not successful, inform in the #summit-simonyi channel
 
 In case EUI/CSC control is not connecting, you could proceed with the control system 
 restart procedure of the :ref:`MTRotator and MTHexapods PXI controller Reboot 
-(Soft, Hard and Control System Restart) <MTRotator and MTHexapods PXI controller Reboot (Soft, Hard and Control System Restart)>`
+(Soft, Hard and Control System Restart) <MTRot-PXI-Controller-Reboot>`.
diff --git a/Simonyi/Troubleshooting/MTCS/HexRot/index.rst b/Simonyi/Troubleshooting/MTCS/MTHexRot/index.rst
similarity index 53%
rename from Simonyi/Troubleshooting/MTCS/HexRot/index.rst
rename to Simonyi/Troubleshooting/MTCS/MTHexRot/index.rst
index 89d3468c..e64d7132 100644
--- a/Simonyi/Troubleshooting/MTCS/HexRot/index.rst
+++ b/Simonyi/Troubleshooting/MTCS/MTHexRot/index.rst
@@ -9,11 +9,4 @@ MTHexapods and MTRotator
     :titlesonly:
     :glob:
     
-    MTRotator-Recovery/MTRotator-Recovery.rst
-
-.. toctree::
-    :maxdepth: 3
-    :titlesonly:
-    :glob:
-    
-    MTRotator-MTHexapods-PXI-Reboot/MTRotator-MTHexapods-PXI-Reboot.rst
\ No newline at end of file
+    MTRotator-Recovery/index.rst
\ No newline at end of file
diff --git a/Simonyi/Troubleshooting/MTCS/index.rst b/Simonyi/Troubleshooting/MTCS/index.rst
index 502e7e84..82e4c125 100644
--- a/Simonyi/Troubleshooting/MTCS/index.rst
+++ b/Simonyi/Troubleshooting/MTCS/index.rst
@@ -12,7 +12,7 @@ This includes troubleshooting of the CSCs that control the telescope and dome mo
     :titlesonly:
     :glob:
 
-    HexRot/index.rst
+    MTHexRot/index.rst
 
 .. toctree::
     :maxdepth: 3
diff --git a/documenteer.toml b/documenteer.toml
index a7221bb0..84e67cc6 100644
--- a/documenteer.toml
+++ b/documenteer.toml
@@ -42,12 +42,13 @@ ignore = [
     'https://start.1password.com/open/i\?a=EJGC5QLBFNAJ3ODCNVC2I3HIPM&v=mqlr5qdkpipoyamzhty5kg365y&i=tu4v5aa4tvhbm4e3rc5siiwada&h=lsstit.1password.com',
     'https://machinerysafety101.com/2009/03/06/emergency-stop-whats-so-confusing-about-that/',
     'https://machinerysafety101.com/2010/11/29/using-e-stops-in-lockout-procedures/',
-    'https://rucio.cern.ch/', 
+    'https://rucio.cern.ch/',
     'https://confluence.slac.stanford.edu/',
-    'http://aux-pdu-spectrograph.cp.lsst.org', 
-    'https://noirlab.edu', 
+    'http://aux-pdu-spectrograph.cp.lsst.org',
+    'https://noirlab.edu',
     'https://gemini.edu',
-    'https://1password.com/downloads'
+    'https://1password.com/downloads',
+    'athexapod.cp.lsst.org'
 ]
 
 [sphinx] 
diff --git a/index.rst b/index.rst
index 2e174bd5..4adc930a 100644
--- a/index.rst
+++ b/index.rst
@@ -117,7 +117,7 @@ Safety: Quick Reference for Nighttime Personnel
     .. grid-item::
     
         .. card:: Enter telescope spaces
-            :link: Safety/index
+            :link: Safety/Enter-Observatory-Spaces/index
             :link-type: doc
             :img-bottom: _static/Facilities.png