02.04.2013 Views

SN User's Guide - ESC Home - NASA

SN User's Guide - ESC Home - NASA

SN User's Guide - ESC Home - NASA

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Revision 10 10-45 450-<strong>SN</strong>UG<br />

Message ID Message<br />

Type/<br />

Class<br />

OPM 66<br />

Time Transfer<br />

Data<br />

Service Level<br />

Requests<br />

(SLRs)<br />

Operations<br />

Data Messages<br />

(ODMs)<br />

Table 10-12. Real-time Message Flow Between the NCCDS and the GTs (cont’d)<br />

Message Length and<br />

Operational<br />

Characteristics<br />

03/66 Variable length dependent<br />

on number, n, of time<br />

transfer samples<br />

04/NA<br />

(note)<br />

SA/SMAR 05/NA<br />

(note)<br />

MA/SMAF 06/NA<br />

(note)<br />

End-to-End<br />

Test<br />

07/NA<br />

(note)<br />

SLRs with ID numbers 1 to<br />

4,999,999 to 1 are a result<br />

of equipment status<br />

change. SLRs with ID<br />

numbers 5,000,000 to<br />

9,999,999 to 5,000,000 are<br />

sent in response to<br />

NCCDS request<br />

Real-time operations report<br />

Message class information not applicable to SLRs and ODMs<br />

Message<br />

Generation<br />

Frequency<br />

Message Generation<br />

Conditions<br />

Messages from the GTs to the NCCDS (cont’d)<br />

One every 5<br />

seconds during<br />

active event<br />

Transmitted to NCCDS within<br />

1 minute of tracking service<br />

termination for which time<br />

transfer was requested in the<br />

SHO<br />

Upon verbal request from the<br />

NCCDS or upon change in<br />

any reported parameter within<br />

15 minutes of change<br />

SLR information is also sent<br />

via e-mail<br />

Separate ODMs are sent for<br />

SA/SMAR, MA/SMAF, and<br />

end-to-end test services for<br />

each TDRS whenever service<br />

is ongoing<br />

Note:<br />

Required Processing Destination System Response<br />

NCCDS receives and<br />

reformats the message<br />

and sends it to the<br />

appropriate MOCC<br />

For resources reported<br />

as unavailable, the<br />

NCCDS operator will<br />

block the affected<br />

resources to keep them<br />

from being scheduled for<br />

user support<br />

ODMs are reformatted<br />

as UPD messages and<br />

routed to appropriate<br />

MOCC when requested<br />

Route TDRSS customer<br />

performance data message to<br />

appropriate MOCC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!