[Css-csts] Re: production status for TD-CSTS

[Berry, David S (3920)]

Hi John:

I'm catching up on lots of things I've been behind on...

Regarding your questions:

(1) I think your assignments for "production operational" and "production halted" sound correct.  I agree that "interrupted" may still need some discussion.  In general navigation will use whatever tracking data is available, and if there is a lack of a particular type they will use what they have.  If one particular data type became unavailable, then "production interrupted" might be appropriate, however, if that data type is scheduled to be turned off, then it wouldn't be interrupted.  We should probably talk a bit more about the "production interrupted" status.

(2) I don't think the production status should be provided in the TDM content itself, but if you think it's necessary your idea of inserting a COMMENT (<COMMENT></COMMENT>) seems workable.

Sorry we didn't get a chance to talk about this at Bordeaux.

David



From: John Pietras <john.pietras at gst.com<mailto:john.pietras at gst.com>>
Date: Wednesday, March 13, 2013 1:38 PM
To: "CCSDS_CSTSWG (css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>)" <css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>>
Cc: David Berry <David.S.Berry at jpl.nasa.gov<mailto:David.S.Berry at jpl.nasa.gov>>
Subject: production status for TD-CSTS

CSTSWG colleagues ---
One of the things that the CSTS Framework defers to the derived services is the exact meaning of the production status values (‘production configured’, ‘production operational’, ‘production interrupted’, and production halted’), because it is usually sensitive to the context of that service.

I’m in the process of updating the TD-CSTS specification, and I have tentatively defined:

-           ‘production operational’ as being when all tracking data-producing resources associated with the Service Package are configured, and at least some tracking data measurements  are being produced;

-          ‘production interrupted’ as being when –because of a fault - *no* tracking data measurements are being produced; and

-          ‘production halted’ as being when –because of management action - *no* tracking data measurements are being produced.

In other words, interrupted and halted indicate a complete absence of tracking data, and operational indicates that at least some tracking data are being produced. That implies that if some (but not all) tracking data is somehow not available, then the production status is still operational. For example, if a Complex is normally capable of  delivering both antenna angles and Doppler range and rate, but for some reason the angles aren’t being reported, production status would still be operational because Doppler range and rate are still available.

An alternative definition would be to define operational as *everything* working, and if *anything* doesn’t work then it is either interrupted or halted.

The production-status that’s being reported here is the content of NOTIFY invocations that don’t (as currently envisioned) affect the content of the TDM that is being transferred by the TD-CSTS. However, it might be desirably to also record the production status in the TDM itself. That way, the absence of tracking data measurements in the TDM for a period of time could be identified as being caused (for example) by a production interruption.

So I am asking two questions:

1.       What’s the desired interpretation of interrupted/halted: *all* tracking data is unavailable, or *any* tracking data is unavailable; and

2.       Whether production status should be captured in the TDM itself. Right now, this would probably have to be implemented as a COMMENT in either the data or metadata.

Thanks.

Best regards,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20130504/c8f1a4af/attachment.html