Post Workshop

From ENFSI Monopoly Programme 2011: Project S-FIVE
Jump to: navigation, search


List of participants will be mailed out soon(ish).


Contents

Refunds

The information about the Refund request procedure was made available on Mon. 22/06/2015;
please contact workshop@s-five.eu if you would have any further questions or comments.


BPM

If you wish to provide feedback on the first draft BPM and Supplement document, please send e-mail to bpm@s-five.eu

When submitting comments, please use "Track changes", or insert comments into the provided document.
If you wish to use colour coding as discussed during the Workshop BPM presentation, please use the following colours:

  • red : text is too general for S-FIVE BPM or Supplement document, or belongs to another specific field (e.g. forensic IT/...)
  • black: should be content of an S-FIVE BPM or Supplement
  • black, underlined: should be added in BPM or Supplement
  • green: is too specific
  • yellow or orange: is not usefull anyway


The S-FIVE Project Team is most interested to learn about your opinion concerning:

  • the split-up of the BPM in two parts, i.e., part one the ENFSI QCC BPM, part two the Supplement containing further detailing of technical issues that persons working in FIVE should be aware about and discuss or implement in their local SOPs (Standard Operating Procedures);
    do you appreciate this principle (of splitting the document)?
  • the structure of the document (please note we are trying to apply the ENFSI QCC BPM template)
  • should certain parts (in either of the two docs) be moved (exchanged), extended, deleted, ...?
  • see also colouring above
  • should certain issues be pointed to in other documents (FITWG BPM, SWGIT/SWGDE (no longer operational, NIST OSAC reforms in USA), ...)?
  • language/spelling: please note that the current draft will be checked by team members from the U.K. later on
  • any other comments you may have

FYI: The current planning for the draft BPM is: review by Workshop participants (deadline July 17), Project Team Meeting 5 (August), public release of draft BPM, presentation/discussion at EAFS2015 (if possible also with QCC members), presentation/discussion and further planning at ENFSI DIWG meeting. (ultimately the S-FIVE BPM proposal will need to be handed over to DIWG and QCC for further processing within ENFSI).


CR

If you wish to provide feedback about the CR (Central Repository), please send e-mail to cr@s-five.eu
If you do not remember how to access the CR, please send an e-mail to info@s-five.eu
Please note that the CR does not contain any information distilled from the WP1-Survey components of the project; these results (including a lot of information about tools currently being used) will be made available ASAP.

The initial deadline for submitting comments on both documents is July 17, 2015.

All comments received will be discussed during the fifth project meeting in London, beginning of August.


NDA

Discussions/presentations subject to the NDA (Non Disclosure Agreement)

The S-FIVE Project Team received no requests for NDA classification of any presentations or discussion. However:

As announced during the Workshop, the discussion about the preliminary analysis of the Collaborative Exercise is to be considered to be subject to the NDA-conditions outlined before the beginning and during the Workshop.
Additionally, please note that the Collaborative Exercise material is subject to very strict Copyright conditions (see CE webpage), and that strict Terms and Conditions apply to the entire S-FIVE website (see footer of page).
Please do not (re)distribute any information about (how to access) the CE results.
All participants to the CE will be invited via e-mail to review the preliminary analysis results and comment on any small errors, (anonymous) representation of their results, layout, etc. that may occur.
Subsequently, the entire CE will be made available publicly.




History of this page

23/06: update on which comments on BPM would be most appreciated (update text in green)

22/06: initial release; important updates will be indicated in color, and/or sent out via e-mail (on a person-to-person basis if needed).

Personal tools
Namespaces

Variants
Actions