[Cesg-all] AOS PINK SHEETS (was RE: [CMC] RP A3-07
Announcement of.,.)
Peter Shames
peter.shames@jpl.nasa.gov
Thu, 21 Aug 2003 13:36:08 -0700
--============_-1150624326==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
I must agree. When I forward docs for review internal in JPL I do
essentially the same thing, for exactly that reason.
Regards, Peter
At 11:02 AM -0700 8/21/03, Adrian J. Hooke wrote:
>At 10:31 AM 8/21/2003, T. Gannett wrote:
>
>>3) Other information, e.g., context, is likely to have little or no
>>significance to reviewers because they are likely to be experts in
>>the limited field to which the document relates. Prior review
>>history is always noted in the Document Description (since there is
>>no notation in this case, there are no prior reviews of this
>>revision).
>>
>>4) The Secretariat has gone to great lengths to keep the "Request
>>for Review" as simple as possibly to enable conveyance of basic
>>information with relative easy. Adding additional information to
>>the review announcements/cover sheets would add clutter; whether
>>the value of the added clutter would justify the consequent
>>reduction in ease use is not clear.
>>
>
>It's here that I have to strongly disagree. Very few people work
>CCSDS full-time and when a document "comes across their desk" for
>review I believe that is not only courteous, but absolutely
>critical, to give them a terse but precise overview of what it's all
>about, where it came from, what they are expected to do with it, and
>what the consequences of their action will be.
>
>It's my observation that for many people when these context-less
>"REQUEST FOR REVIEW OF CCSDS DOCUMENT" messages appear, if people
>don't know in 30-seconds what they are supposed to do about them
>then they are just put aside and forgotten. The Area Directors are
>busy people and yet it is vital that they act promptly to review
>every document for technical quality and consistency. The only way
>to ensure that they understand the significance is to tag each
>request for action with a very short "staff note" preface (an
>electronic version of a stick-on "Post-It") that makes it crystal
>clear what the request is all about.
>
>///adrian
--
_______________________________________________________________
Peter Shames
Manager - JPL Information Systems Standards Program
InterPlanetary Network and Information Systems Directorate
Jet Propulsion Laboratory, MS 301-265
California Institute of Technology
Pasadena, CA 91109 USA
Telephone: +1 818 354-5740, Fax: +1 818 393-1333
Internet: Peter.Shames@jpl.nasa.gov
_______________________________________________________________
"We shall not cease from exploration, and the end of all our exploring
will be to arrive at where we started, and know the place for the first time"
T.S. Eliot
--============_-1150624326==_ma============
Content-Type: text/html; charset="us-ascii"
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Cesg-all] AOS PINK SHEETS (was RE: [CMC] RP
A3-07</title></head><body>
<div>I must agree. When I forward docs for review internal in
JPL I do essentially the same thing, for exactly that reason.</div>
<div><br></div>
<div>Regards, Peter</div>
<div><br></div>
<div><br></div>
<div>At 11:02 AM -0700 8/21/03, Adrian J. Hooke wrote:</div>
<blockquote type="cite" cite><font color="#0000FF">At 10:31 AM
8/21/2003, T. Gannett wrote:</font><br>
<font color="#0000FF"></font>
<blockquote type="cite" cite><font color="#0000FF">3) Other
information, e.g., context, is likely to have little or no
significance to reviewers because they are likely to be experts in the
limited field to which the document relates. Prior review
history is always noted in the Document Description (since there is no
notation in this case, there are no prior reviews of this
revision).<br>
<br>
4) The Secretariat has gone to great lengths to keep the "Request
for Review" as simple as possibly to enable conveyance of basic
information with relative easy. Adding additional information to
the review announcements/cover sheets would add clutter; whether
the value of the added clutter would justify the consequent reduction
in ease use is not clear.</font><br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><font color="#0000FF"><br>
It's here that I have to strongly disagree. Very few people work CCSDS
full-time and when a document "comes across their desk" for
review I believe that is not only courteous, but absolutely critical,
to give them a terse but precise overview of what it's all about,
where it came from, what they are expected to do with it, and what the
consequences of their action will be.<br>
<br>
It's my observation that for many people when these context-less
"REQUEST FOR REVIEW OF CCSDS DOCUMENT" messages appear, if
people don't know in 30-seconds what they are supposed to do about
them then they are just put aside and forgotten. The Area Directors
are busy people and yet it is vital that they act promptly to review
every document for technical quality and consistency. The only way to
ensure that they understand the significance is to tag each request
for action with a very short "staff note" preface (an
electronic version of a stick-on "Post-It") that makes it
crystal clear what the request is all about.<br>
<br>
///adrian</font></blockquote>
<div><br></div>
<div><br></div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><font face="Geneva" size="-1"
color="#000000"
>_______________________________________________________________</font
><br>
<font face="Geneva" size="-1" color="#000000"></font></div>
<div><font face="Geneva" size="-1" color="#000000">Peter
Shames</font></div>
<div><font face="Geneva" size="-1" color="#000000">Manager - JPL
Information Systems Standards Program</font></div>
<div><font face="Geneva" size="-1" color="#000000">InterPlanetary
Network and Information Systems Directorate</font></div>
<div><font face="Geneva" size="-1" color="#000000">Jet Propulsion
Laboratory, MS 301-265<br>
California Institute of Technology<br>
Pasadena, CA 91109 USA</font><br>
<font face="Geneva" size="-1" color="#000000"></font></div>
<div><font face="Geneva" size="-1" color="#000000">Telephone: +1 818
354-5740, Fax: +1 818 393-1333<br>
<br>
Internet: Peter.Shames@jpl.nasa.gov<br>
___________________________________________________________</font><font
face="Geneva" size="+1" color="#000000">____</font></div>
<div><font face="Geneva" size="-1" color="#000000">"We shall not
cease from exploration, and the end of all our exploring</font></div>
<div><font face="Geneva" size="-1" color="#000000">will be to arrive
at where we started, and know the place for the first
time"</font></div>
<div><font face="Geneva" size="-1" color="#000000"><br></font></div>
<div><font face="Geneva" size="-1"
color="#000000"
> <span
></span
> <span
></span
> <span
></span
> <span
></span
> <span
></span
> <span
></span
> <span
></span
> <span
></span> T.S. Eliot</font></div>
</body>
</html>
--============_-1150624326==_ma============--