Enhancing Ops Display & Efficiency in Managing Large Fleet using EPOCH Active Command/Location & EPOCH AUTON Tools

Transcription

1 1 Enhancing Ops Display & Efficiency in Managing Large Fleet using EPOCH Active Command/Location & EPOCH AUTON Tools Shouki Michael Souri Konrad Andrew Sadek Wednesday April 20, 2016

2 The Intelsat Globalized Network combines the world s largest satellite backbone with terrestrial infrastructure and managed services to deliver highquality, cost-effective video and broadband services, anywhere in the world. 2

3 3 Satellite Operations Fully redundant primary and back up control centers in McLean, VA and Long Beach, CA Operational experience with all major manufacturers and satellite platforms Highly functional and automated control system (combination of COTS and in-house product) provides efficient and reliable fleet operation Knowledge and experience with industry COTS satellite control products Relocated to Tyson s Corner in July 2014 Long Beach Sat Operations Center (LSOC) East Coast Sat Operations Center (ESOC)

4 4 Satellite Operations Experience Approximately 74 satellites operated Airbus E2000, E3000 Boeing 381, 393, 601, 601HP, 601MEO Boeing 702, 702MP LM 7000 OSC Star 2 SSL 1300 Omega, FS1300 Thales Spacebus 3000B Current Intelsat FLEET: 49 S/C Current 3 rd Party FLEET: 25 S/C Current FLEET under GNS: 42 S/C Current FLEET under EPOCH: 25 S/C Current FLEET under TCR: 6 S/C Current S/C under Eclipse: 1 S/C Current S/C under ISIS: 0 S/C

5 5 Main Goal and Some of the challenges Objective: Enhancing Ops displays and efficiency by providing GNS Autonomous Commanding (AUTON) the capability to trigger an EPOCH commanding procedure to execute on an EPOCH commanding workstation. Challenges: GNS does not know which EPOCH WS to send the command to. GNS does not know the primary FEP and stream information. GNS does not know how to invoke an EPOCH procedure. GNS does not know the health-status of EPOCH FEP and Client.

6 Intelsat Proprietary 6 GNS Automated Operations Anomaly Resolution Autonomous Commanding (AUTON) Receives telemetry and responds to anomalous changes onboard the spacecraft Has static or dynamic functionality Can use static pre-determined command procedures based upon a known condition Based upon current subsystem condition, dynamically generates command procedure to place the spacecraft in a safe state and/or to place a unit/subsystem back to its nominal (normal) status New functionality added to meet changing S/C conditions

7 7 GNS Automated Operations Commanding All commanding, except under emergencies, is performed using Automated Command Procedures (ACPs) ACPs can be created with sophisticated logic ACPs can receive telemetry as input to command logic ACPs can be either scheduled manually using Timeline or automatically by other ground system components Ad-hoc or emergency commands can be sent using IIC (Individual Interactive Commanding)

8 8 EPOCH Active Location Monitor Although GNS system already monitors all telemetry for all spacecraft (regardless of what ground system is used to fly) the GNS system also needed to know several things in order to send out the command to an EPOCH controlled spacecraft: The current primary FEP and stream being used for commanding The current health of the FEP and if it is ready to command The current workstation being used to fly that spacecraft The status of the stream on the designated workstation

9 9 Commanding EPOCH FEP and Workstation In order to accommodate which FEP and EPOCH Workstation are responsible for a certain spacecraft, we decided to utilize our existing Web Based tool the Intelsat Daily Activity Plan (IDAP) - which provides a lot of operational functionality and is used constantly by all satellite controllers. The IDAP allows each controller to update a table which provides the information needed to allow the GNS system to know where to send commands and is required to be verified at the start of each shift. This information is also vital in troubleshooting, as it can be searched/filtered on to as how the ground systems was configured at any single time in the past.

10 10 EPOCH FEP Status To accommodate the monitoring of a front-end processor, we created several scripts that run on all FEPs and allow us to determine: EPOCH status (Started/Stopped) Stream Status (Up/Down/Started/Stopping) Baseband unit utilized Telemetry Status (TM updating) TCU status (Connected/Not Connected) Ranging status Memory/CPU utilization Network statistics to baseband unit All information is then forwarded to the IDAP to be processed and displayed.

11 11 EPOCH Workstation Status To accommodate the monitoring of a workstation, we created several scripts that allow us to determine: Status of the stream in question (attached, detached, up, down, etc.). Status of memory and CPU utilization. Status of AUTON application All information is then forwarded to the IDAP to be processed and displayed.

12 EPOCH Active Command/Location 12

13 13 EPOCH AUTON With the information provided to the IDAP and now available to our GNS system the GNS system can now in realtime activate an autonomous command by sending pre-configured information to that workstation where we have created another application running which: Constantly listens on pre-defined TCP/IP port and awaits information coming from GNS. Once a request comes in, it is then formatted and then sent to the EPOCH Realtime API. An audible alert is also generated at the workstation informing the controller that an AUTON is executing. The EPOCH AUTON application then connects to the EPOCH Local Procedure API and sends constant status back to GNS until the procedure is completed.

14 14

15 15 EPOCH Active Location With all the information already retained within the IDAP, as well as constant status being supplied by each FEP, workstation and baseband unit, we can provide to all users a single location that will allow them to receive information on any given spacecraft at a single time including the current configuration from satellite controller all the way to the spacecraft.

16 Spacecraft Information/Quick Start Menu 16

17 EPOCH Information 17

18 Network Status/Statistics 18

19 Range Status 19

20 20 EPOCH IDAP Active Location And since the IDAP already stores so much more information such as: Maintenance Work Orders (MWOs) Satellite Engineering Spacecraft Logs and Anomaly Reports EPOCH functionality Start/Stop EPOCH, generate FEP and workstation logs, restart certain processes. Full Spacecraft database (Such as when it was lunched, manufacturer, model, etc.) Engineering Change Requests Daily Activities, Spacecraft Knowledge Base Maintenance schedules All reported activities (Satellite Controller Logs) Flight Dynamics Scheduled Maneuvers Designated antennas for each spacecraft with all antenna information

21 Thank You! 21