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.

Table 10-3. Schedule Request Descriptions<br />

Schedule Request Type Description<br />

Schedule Add Request (SAR) (message type<br />

99, message class 10)<br />

Alternate SAR (message type 99, message<br />

class 21)<br />

Schedule Delete Request (message type 99,<br />

message class 11)<br />

Schedule Replace Request (message type 99,<br />

message class 12)<br />

Specifies an event to be added to the schedule in<br />

terms of:<br />

1. Specific event start and stop times<br />

2. Either a prototype event ID or one or more<br />

SSC IDs together with service-level timerelated<br />

information<br />

References either a SAR or another Alternate SAR<br />

to form a chain of requests. Specifies an event to<br />

be added to the schedule.<br />

Identifies an event to be deleted and does not<br />

include information such as SSCs<br />

Identifies an event to be deleted, and includes all<br />

of the information needed to add a new event<br />

d. Event scheduling in the NCCDS complies with the <strong>SN</strong> scheduling ground rules<br />

as specified in paragraphs 2.2.2 and 2.2.3 of the Interface Control Document<br />

(ICD) between the Network Control Center Data System (NCCDS) and the<br />

White Sands Complex (WSC), 452-ICD-NCCDS-WSC. Compliance with these<br />

ground rules ensures that the schedules generated by the NCCDS can be<br />

supported by the TDRSS. In particular, these ground rules ensure adequate<br />

time to configure a resource prior to its use. The actual time required to<br />

configure a service within an event varies depending on the resources allocated<br />

to the service. In general, the time scheduled by the NCCDS to configure a<br />

service is the longest time needed to configure any one of the resources<br />

allocated to the service. Additional rules also apply to event scheduling. Table<br />

10-5 summarizes the <strong>SN</strong> scheduling ground rules with an emphasis on the<br />

ground rules that apply to time relationships. In general, individual schedule<br />

requests submitted by customers must comply with rules that apply to individual<br />

events or services while rules that apply to the relationships between events are<br />

beyond the control of individual customers.<br />

e. Event scheduling in the NCCDS is performed when processing modifications<br />

(add, replace and delete requests) to the active schedule and when generating<br />

the next forecast schedule. The NCCDS Scheduling Operator (SO) is<br />

responsible for monitoring and coordinating all scheduling activities within the<br />

active period. The NCCDS Forecast Analyst (FA), who is chiefly responsible for<br />

coordinating future scheduling requirements (forecast periods), assists the<br />

NCCDS SO in monitoring schedule-related database information, analyzing<br />

schedule resource problems, and coordinating alternative support solutions with<br />

MOCCs.<br />

Revision 10 10-7 450-<strong>SN</strong>UG

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

Saved successfully!

Ooh no, something went wrong!