REQUEST SECTION

5.4.4.1 The request section of a PRM shall be contained in the data container.

5.4.4.2 The data container shall define a timeline section.

5.4.4.3 The timeline section shall contain one or more attitude block sections.

NOTES

1 This structure permits the definition of a sequence of requests by the provision of successive blocks in the timeline to define intervals for the different requests.

2 The following scheme provides an example of the construction of the request section according to the rules provided above.

<data>

<timeline>

<block ref="attBlock">

...

</block>

</timeline>

</data>

5.4.4.4 Request Section Step by Step (Reference Case)

5.4.4.4.1 The pointing request associated to the PRM definition shall define at least one block in the timeline.

5.4.4.4.2 Each block in the timeline shall provide its start and end time and the attitude definition.

<data>

<timeline>

<block ref="attBlock">

<blockStart>2013-10-02T00:00:00</blockStart>

<blockEnd>2013-10-02T14:30:00</blockEnd>

<attitude>

...

</attitude>

</block>

</timeline>

</data>

5.4.4.4.3 The pointing request associated to the PRM definition may define several blocks in the timeline in chronological order.

<data>

<timeline>

<block ref="attBlock">

<blockStart>2013-10-02T00:00:00</blockStart>

<blockEnd>2013-10-02T14:30:00</blockEnd>

<blockStart>2013-10-03T00:00:00</blockStart>

<blockEnd>2013-10-03T14:30:00</blockEnd>

<blockStart>2013-10-04T00:00:00</blockStart>

<blockEnd>2013-10-04T14:30:00</blockEnd>

5.4.4.5 Request Section Step by Step (Configurable Boresight)

5.4.4.5.1 The pointing request associated to the PRM definition may reconfigure the definition section to allow for the selection of the boresight (direction in the spacecraft body frame).

5.4.4.5.2 The definition section of the PRM shall use the <frameDir localName="boresight" /> construct to identify the reconfigurable spacecraft pointing axis (boresight).

NOTE – This permits the dynamic selection of the spacecraft direction without having to modify the definition each time a new request is generated (e.g., need to point different instruments to the same target). Then the definition and request section would be as follows:

<definition name="defBlock" version="a.b">

<frame baseFrame="none" name="EME2000" />

<frame baseFrame="EME2000" name="SC" />

<orbit name="SC#1">

<orbitFile>SC#1.oem.xml</orbitFile>

</orbit>

<orbit name="Jupiter">

<ephObject>JUPITER</ephObject>

</orbit>

<dirVector name="targetBody">

<origin ref="SC#1" />

<target ref="Jupiter" />

</dirVector>

<block name="attBlock">

<startEpoch localName="blockStart" />

<endEpoch localName="blockEnd" />

5.4.4.5.3 The pointing request associated to the PRM definition shall provide the definition of the reconfigurable spacecraft pointing axis.

<data>

<timeline>

<block ref="attBlock">

<blockStart>2013-10-02T00:00:00</blockStart>

<blockEnd>2013-10-02T14:30:00</blockEnd>

NOTE – The definition section above already provides the attitude request scheme to align the boresight with the target direction defined by targetBody. The request defines the specific direction of the boresight to be pointed and closes the definition of the pointing request.

5.4.4.6 Request Section Step by Step (Configurable Target)

5.4.4.6.1 The pointing request associated to the PRM definition may reconfigure the definition section to allow for the selection of the target (direction towards which the boresight should be pointed).

5.4.4.6.2 The definition section of the PRM shall use the <target localName="target" /> construct to identify the reconfigurable target.

NOTE – This permits the dynamic selection of the target direction without having to modify the definition each time a new request is generated. Then the definition and request section would be as follows:

<definition name="defBlock" version="a.b">

<frame baseFrame="none" name="EME2000" />

<frame baseFrame="EME2000" name="SC" />

<orbit name="SC#1">

<orbitFile>SC#1.oem.xml</orbitFile>

</orbit>

<orbit name="Jupiter">

<ephObject>JUPITER</ephObject>

</orbit>

<orbit name="Saturn">

<ephObject>SATURN</ephObject>

</orbit>

<orbit name="Sun">

<ephObject>SUN</ephObject>

</orbit>

<dirVector name="boresight" frame="SC">0.0 0.0 1.0</dirVector>

<block name="attBlock">

<startEpoch localName="blockStart" />

<endEpoch localName="blockEnd" />

5.4.4.6.3 The pointing request associated to the PRM definition shall provide the definition of the reconfigurable target.

<data>

<timeline>

<block ref="attBlock">

<blockStart>2013-10-02T00:00:00</blockStart>

<blockEnd>2013-10-02T14:30:00</blockEnd>

<target ref="Jupiter" />

</block>

<block ref="attBlock">

<blockStart>2013-10-03T00:00:00</blockStart>

<blockEnd>2013-10-03T14:30:00</blockEnd>

<target ref="Saturn" />

</block>

<block ref="attBlock">

<blockStart>2013-10-04T00:00:00</blockStart>

<blockEnd>2013-10-04T14:30:00</blockEnd>

<target ref="Sun" />

</block>

</timeline>

</data>

NOTE – The definition section above already provides the attitude request scheme to align the boresight with the target direction defined by targetBody. The request defines sequentially the specific targets to point to and closes the definition of the pointing request.

ANNEX A

IMPLEMENTATION CONFORMANCE STATEMENT PROFORMA