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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

support identification codes (SIC) will be established. Key information including<br />

spacecraft mass, cross-sectional area, drag co-efficient, and solar reflectivity<br />

parameters will be collected. These platform-specific values are needed for accurate<br />

orbit modeling which allows DAS to determine visibility and service schedules up to five<br />

days into the future. In the event these values are not provided, baseline values will be<br />

substituted which will impact orbit modeling accuracy, especially for platforms with orbits<br />

less than 750 km in altitude. DAS Customers with orbit altitudes below 750 km should<br />

update the mass value whenever it varies more than 10% from the previously submitted<br />

value in order to maintain accuracy of their DAS 5-day orbit predictions.<br />

Initial service specification codes (SSC), which will be the basis for allocating resources<br />

and setting up the RF links between the Customer Platform and the TDRSs, will be<br />

established and the required equipment allocation for each SSC will be calculated.<br />

NI<strong>SN</strong> and GDIS access capacity will be determined.<br />

If this analysis indicates that there are insufficient resources to support additional<br />

customers, GSFC Code 450 will determine if additional resources must be procured. A<br />

Project Service Level Agreement (PSLA) will be negotiated with the customer. DAS,<br />

NI<strong>SN</strong>, and <strong>SN</strong>AS accounts will be established. The Planning activities shown in Table<br />

H-1 ideally take place a minimum of 18 months prior to commencement of services.<br />

H.3 Customer Interface with the DAS<br />

H.3.1 General<br />

Communications between DAS and a MOC Customer involve two different classes of<br />

information. The first type is service data or telemetry, which is the data received from<br />

the Customer Platform and forwarded to the Customer MOC. The other type is a<br />

combination of planning and scheduling information, status information, real-time control<br />

information, and other miscellaneous administrative information.<br />

DAS uses <strong>SN</strong>AS for all types of communications except the telemetry. The <strong>SN</strong>AS<br />

interface with DAS allows the customer insight into available resources, allows the<br />

customer to submit requests for DAS services, and permits monitoring DAS service<br />

performance.<br />

Table H-2 lists information exchanged between DAS and the customer via <strong>SN</strong>AS.<br />

Please refer to Appendix P of this document, or the web site at:<br />

http://snas.gsfc.nasa.gov for further information on <strong>SN</strong>AS.<br />

Revision 10 H-12 450-<strong>SN</strong>UG

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

Saved successfully!

Ooh no, something went wrong!