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.

10.2.4.2 Specific Schedule Request<br />

The Specific Schedule Request message is used to add, delete or replace scheduled<br />

events for <strong>SN</strong> resources. The following NCCDS constraints apply:<br />

a. All related services (e.g., forward, return, tracking and end-to-end test) for one<br />

SUPIDEN, for one TDRS, and for one continuous period are generally<br />

contained in the same request. However, two independent events for the same<br />

SUPIDEN can be scheduled at the same time whenever this does not result in<br />

resource conflicts.<br />

b. Deletion of a scheduled event may be accomplished only by the MOCC that<br />

has scheduling authority, the NCCDS SO, or the GT (with NCCDS approval or<br />

direction). If the GT deletes an event, this will not result in automatic generation<br />

of messages announcing the deletion.<br />

c. Configuration changes to scheduled events, prior to the scheduled event start<br />

time, require the entire event to be replaced by submitting a Schedule Replace<br />

Request (message type 99, message class 12). Alternatively, the event can be<br />

deleted by submitting a Schedule Delete Request (message type 99, message<br />

class 11) and then a new Schedule Add Request (message type 99, message<br />

class 10) can be transmitted. Ordinarily these two methods will achieve<br />

equivalent results; however, use of the Schedule Replace Request ensures that<br />

the resources allocated to the original event are available to be used to<br />

schedule the replacement. Use of the Schedule Replace Request also leaves<br />

the original event on the schedule if the replacement cannot be scheduled.<br />

d. For add requests, the configuration of services for the event may be specified<br />

either by reference to a set of SSCs or by reference to a prototype event which<br />

then references a predetermined set of SSCs stored in the NCCDS database.<br />

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

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

Saved successfully!

Ooh no, something went wrong!