How dynamic do we really think that some of this information will be?
If I consider an overlay type document, I would hope that it would not
be dynamic. However, if one considers a repository of Lessons-Learned
type of information, I think such information would be dynamic and that
a Product Support Group for the DSEEP could easily keep this information
in their file area on the SISO Web Page. Checklists are other types of
information that might need to be fairly dynamic and these could also be
maintained by a PSG in their file area.


James M. (Mark) McCall

General Dynamics Information Technology

Warfighter Readiness Research Division

Air Force Research Laboratory

6030 South Kent St

Mesa, AZ 85212

(480) 988-6561 x231

DSN 474-6231

Caution: This message may contain competitive, sensitive or other
non-public information not intended for disclosure outside official
government channels. Do not disseminate this message without the
approval of the undersigned's office. If you received this message in
error, please notify the sender by reply e-mail and delete all copies of
this message.


From: SAC-PDG-FEDEP: Keith Ford
[mailto:[log in to unmask]]
Sent: Monday, July 23, 2007 1:39 AM
Subject: DSEEP Annexes (Again)

From: "Keith Ford" ([log in to unmask])

*** This message was generated from SAC-PDG-FEDEP ***


As you know one of the ideas for SEDEP was to have technical overlays
e.g. VV&A, Evaluation, etc. Role overlays e.g. Problem Setter, Problem
Solver, etc. and Domain overlays e.g. SBA, T&E, etc. Whilst I think the
principle is still good, I am not sure whether we want to make this
additional information part of the DSEEP standard as I think the this
'best practice' type of information needs to be more dynamic i.e. have
the ability to update it as experience is gained. The question is 'where
would we capture and who would manage this type of information'? Is
there a role for using the SISO web site or the Wiki from NATO MSG-052?

What do others think?

To reply: [log in to unmask]
To start a new topic: [log in to unmask]
To view discussion:

To (un)subscribe: Send a message to
[log in to unmask] with the word
unsubscribe in the message body.
Important: the unsubscribe email needs to be in plain text format, and
needs to have no subject line.


To unsubscribe from the SAC-PSG-DSEEP list, click the following link: