Merge pull request #724 from BlakeSLC/main

Add Skyline Station Montior connector help

Author: MariekeGO

connector/doc/Control_By_Web_X-600M.md

@@ -32,5 +32,7 @@ The **Control By Web X-600M** is a multifunction web-enabled industrial I/O cont
 
 **Benefit**: Enhances efficiency, reduces manual intervention, and minimizes the risk of human error.
 
+## Technical Information
+
 > [!NOTE]
 > For detailed technical information, refer to our [technical documentation](xref:Connector_help_Control_By_Web_X-600M_Technical).

connector/doc/Skyline_Station_Monitor.md

@@ -0,0 +1,44 @@
+---
+uid: Connector_help_Skyline_Station_Monitor
+---
+
+# Skyline Station Monitor
+
+The **Skyline Station Monitor** standardizes and simplifies the collection of data for monitoring transmitters and related equipment (tower lights, generators, transfer switches, etc.) across multiple stations/transmission sites. Utilizing real-time monitoring and automation, this connector serves as a mediation layer, gathering data from various collectors and storing it according to predefined parameters. This ensures consistent reporting and display in low-code apps and dashboards. Additionally, the collector supports the collection of non-standard (custom) parameters for stations that need to track data from elements that users might not have permission to access. It also provides the capability to define custom actions.
+
+## Key Features
+
+- Mediates common transmission parameters at regular intervals into standard parameters allowing for standardized reporting.
+- Can be extended to monitor additional, custom values from specified elements for data aggregation beyond the standard complement of included parameters.
+- Allows you to define a custom polling frequency for standard and custom parameters.
+- Polls both the value and alarm state from the source element to allow for passthrough of existing alarm templates.
+- Provides historical polling timestamps for analysis.
+- Can help isolate users from source elements by only allowing access to the Station Monitor element.
+- FCC Licensed Power calculations allow stations to monitor their compliance with transmission output power limitations and provide warnings if the power output exceeds FCC tolerances.
+
+## Use Cases
+
+### Standardized Monitoring of Multiple Transmission Sites
+
+**Challenge**: Unless each transmission site has the exact same complement of equipment, groups that need to monitor multiple transmission sites find that each site needs to be treated as a one-off. This requires setting up custom alarming, custom trending, custom reporting, and custom dashboards for each site, which can be time-consuming and costly at scale.
+
+**Solution**: The **Skyline Station Monitor** provides a way to collect commonly used monitoring and reporting values into a standard footprint.
+
+**Benefit**: There are multiple benefits to this approach that can greatly reduce the admin overhead of managing a large number of sites. Some of these benefits include:
+
+- Standardized alarm and trend templates.
+- The ability to reuse reports and low-code apps across sites.
+- Users can be provided access to targeted information about a site without getting full access to the source elements.
+
+### FCC Reporting Requirements
+
+**Challenge**: Stations have an obligation to report certain metrics to the FCC related to their transmission towers, including power outputs and tower light status.
+
+**Solution**: By using the **Skyline Station Monitor**, this information is easy to collect in a standardized way.
+
+**Benefit**: By standardizing the collection, monitoring, and trending of key metrics required by the FCC, report generation is a breeze and easy to implement across your entire organization, reducing time to deploy and the costs to manage changes needed down the road.
+
+## Technical Information
+
+> [!NOTE]
+> For detailed technical information, refer to our [technical documentation](xref:Connector_help_Skyline_Station_Monitor_Technical).

connector/doc/Skyline_Station_Monitor_Technical.md

@@ -0,0 +1,79 @@
+---
+uid: Connector_help_Skyline_Station_Monitor_Technical
+---
+
+# Skyline Station Monitor
+
+The Skyline Station Monitor connection is designed to facilitate real-time data collection, parameter tracking, and automated actions for generic Apps for quick deployment of new stations.
+
+## Configuration
+
+### Connections
+
+#### Virtual connection
+
+This connector uses a virtual connection and does not require any input during element creation.
+
+## Usage
+
+### Standard Monitoring
+
+Standard monitoring is consistent across all stations. It must be routed to the predefined parameters that hold information for each KPI, meaning that rows cannot be added or removed. The collected data is then displayed on the Standard Monitoring page.
+
+### Custom Monitoring
+
+Custom monitoring allows for flexible mapping, enabling users to define their own parameters to retrieve. Unlike with standard monitoring, users can add or remove rows as needed to accommodate specific monitoring requirements that are not predefined within the standard framework.
+
+### Data Polling Process
+
+1. The system reads the **Element ID** to identify the device and component.
+1. It retrieves the specified **Parameter ID** value at the configured polling frequency.
+1. If a **Row Key** is provided, it accesses the corresponding row in a table.
+1. The collected values are stored, including timestamps, alarm states, and results.
+1. Errors are logged if polling fails.
+
+### Element ID Format
+
+Each monitored element is identified using a **DMAID/ElementID** format:
+
+- **DMAID**: A unique identifier for the monitored device or system.
+- **ElementID**: The specific component within that system being monitored.
+
+For example:
+
+```
+123/456
+```
+
+### Parameter ID
+
+The **Parameter ID** is a numerical identifier representing the specific attribute being monitored within an element. It defines what data will be polled from the specified **Element ID**.
+
+- Each parameter ID corresponds to a predefined metric (e.g. CPU usage, voltage, temperature).
+- The polling frequency determines how often the parameter value is retrieved.
+
+For example:
+
+```
+Element ID: 123/456
+Parameter ID: 789
+```
+
+In the example above, **parameter 789** is being polled from **Element 123/456**.
+
+### Using a Row Key for Table-Based Parameters
+
+If a **Row Key** is specified, the system assumes the parameter belongs to a table structure within the element. In this case:
+
+- The **Row Key** determines the specific entry within the table (the primary key).
+- The **Parameter ID** defines the column ID to be retrieved from that row.
+
+For example:
+
+```
+Element ID: 123/456
+Parameter ID: 789
+Row Key: analog1
+```
+
+The setup from the example above retrieves the **789** parameter from the **analog1** row within **Element 123/456**.

connector/toc.yml

@@ -2332,7 +2332,7 @@
   - name: Control By Web X-600M
     topicUid: Connector_help_Control_By_Web_X-600M
     items:
-    - name: Connector name Technical
+    - name: Control By Web X-600M Technical
       topicUid: Connector_help_Control_By_Web_X-600M_Technical
   - name: Control By Web X332
     topicUid: Connector_help_Control_By_Web_X332
@@ -8231,6 +8231,11 @@
     topicUid: Connector_help_Skyline_SRM_Service_Manager
   - name: Skyline SSL Certificate Monitor
     topicUid: Connector_help_Skyline_SSL_Certificate_Monitor
+  - name: Skyline Station Monitor
+    topicUid: Connector_help_Skyline_Station_Monitor
+    items:
+       - name: Skyline Station Monitor Technical
+         topicUid: Connector_help_Skyline_Station_Monitor_Technical 
   - name: Skyline Synthetic Testing
     topicUid: Connector_help_Skyline_Synthetic_Testing
   - name: Skyline Synthetic Testing Results