Considerations for the Service Package Request/Service Package Recommended Standard October 2013 San Antonio, TX John Pietras Global Science and Technology, Inc., Greenbelt, MD, USA

Service Package Request Service Package Request must be capable of accommodating all* known/planned SM interfaces defined as of today (or some other TBD cutoff?) “Extensibility” in the Service Package Request is about the ability to accommodate flexibilities and constraints o Minimal flexibilities/constraints: start and stop times per Space Link Configuration o B-1 equivalent flexibilities and constraints: start time, plus offset, minus offset, preferred duration, minimal duration per Space Link Configuration; group space link carriers by antenna with relative offsets; scenarios; respecifications; sequence of events o SGSS flexibilities and constraints: recurrent requests, time windows, linked Space Link configurations, waitlisting, freeze intervals 2 *Where all is defined as those interfaces of Agencies willing to provide requirements and participating in (at least) Red Book reviews

SLS Service Package Request Template 3 Identifies all of the Space Link Profiles that are used in the Request Identifies all of the SLS TS Profiles that are used in the Request Specifications of the flexibilities and constraints that are used in the Request. Extension Point for new flexibilities and constraints Space Link Profile Instances of SM Function Functional Resources references

Flexibilities and Constraints F & C “rule classes” reference the Profiles that they operate on, they do not contain them o “Schedule Space Link Profile M from start time X to stop time Y” F & C rule classes can operate in combinations (subject to conflict avoidance) o E.g., “Schedule Space Link Profile M with nominal start time X, start lead of X1, start lag of X2, preferred duration of Y1, minimal duration of Y2” AND “Schedule Space Link Profile N to start 5 minutes after the start of Space Link Configuration M” AND “Schedule Space Link Profile N to end 3 minutes before the end of Space Link Configuration M” Rule classes can operate on rule classes o E.g., a single scenario can be a set of rules; a different scenario can be controlled by a different set of rules 4

“Standard” Service Package Request Define a truly minimal Request that every implementation must support o At least one Space Link Configuration o The SLS TSs that go with that Space Link Configuration o Minimal Flexibilities and Constraints rule class  Start time and stop time for the Space Link Configuration and associated TSs  I.e., a “Simple Service Package Request” Define additional rule objects that provide all of the additional F&Cs required for the target set of implementation o Standard but optional Update book to add new F&C rule classes as they are defined NOTE – users/implementers won’t have to understand the “rules for making rules”; the resulting rules will be simply specified in the book Possible variation? o Allow SLS Service Package Request to directly include configuration profiles  “Simpler” in those cases where a one-off configuration is needed 5

Service Package Must support at least 2 levels of detail o Terse – identifies the Functional Resource Names of all the FRs in the Service Package  Needed for MD-CSTS (and Service Control CSTS in the future)  Implies that even a minimal Service Package will contain objects for all FRs in the Package o Verbose – also contains all parameter values  Required for NASA SGSS Result – Service Package will look more like their source configuration profiles 6

Schedule of Service Packages An SGSS “schedule” is a collection of Service Packages (nominally, for one week or two week periods) o SGSS has modified the Query Service Package operation to be able to retrieve multiple Service Packages at once Proposal - include a Schedule of Service Packages information entity in the Service Package Request/Service Package book that would address this need in a standard way without depending of a new ESCCS-SM operation to do it o Can be defined as a simple wrapper around multiple Service Package Info Entities with schedule start/stop times 7