<?xml version="1.0" encoding="ISO-8859-1"?> 
<?xml-stylesheet type="text/xsl" href="rc4docs.xsl"?>
   <Document>
      <DocumentName><![CDATA[DOE M 471-X-X Manual for Identifying and Protecting Official Use Only Information]]></DocumentName>
      <DocumentId><![CDATA[DOE M 471-X-X]]></DocumentId>
      <DocumentOpenDate>06/26/2002</DocumentOpenDate>
      <DocumentCloseDate>07/26/2002</DocumentCloseDate>
      <DocumentResolutionDate>09/26/2002</DocumentResolutionDate>
      <MajorComments>
         <Section>
            <SectionTitle><![CDATA[Overall Comments]]></SectionTitle>
            <SectionContent><![CDATA[Please provide your overall comments about this document.
Note: this 'paragraph' is not part of the original document.]]></SectionContent>
            <Organization>
               <OrganizationName><![CDATA[Ames Labortatory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Argonne National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Associate Manager for Science & Technology, Richland]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bechtel Hanford]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bechtel Nevada]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Berkeley Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bonneville Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Brookhaven National  Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[BWXT Pantex, LLC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Carlsbad Area Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Carlsbad Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[CH2MHill]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Chicago Operations Office]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Lynette Kane]]></SourceUsername>
                  <SourceTitle><![CDATA[CH DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Chicago Operations Office]]></SourceSite>
               </Source>
               <ApproverName><![CDATA[Larry Vann, Acting Manager]]></ApproverName>
               <Comments><![CDATA[The Chicago Operations Office (CH) non-concurs on the subject drafts.  

The main reasons for CH's non-concurrence include:

--These directives describe a solution with no problem.  Most information that would be subject to these requirements is already subject to statutory, regulatory, or other protections.  Any additional requirements should be narrowly tailored to address specific deficiencies in these protections; no such deficiencies have been identified.  

--The requirements, even taking into consideration the "exemptions" in the Manual for documents maintained in receptacles, are  likely to create a burden far in excess of the protective benefit.  OUO  awareness and implementation training alone would have a major impact on personnel already burdened by reduced staffing levels.     

--These drafts do not sufficiently address what documents require OUO markings.  While it is clear from these drafts that OUO information must meet an exemption from FOIA release, the "damage to national security" threshold requiring OUO markings is indeterminable.   Without a "damage" threshold, the third definitional criterion is already covered by the second.   As long as any employee may make a "discretionary determination" that a document contains OUO, this lack of guidance will result in a flood of documents being marked as OUO.

--These drafts do not clearly distinguish identification of OUO information and the review of documents for releasibility under a FOIA request.  Just as an OUO marking does not automatically mean a document is exempt, documents not marked OUO are not  automatically releasable.

Until CH's issues are properly addressed, we cannot concur with the issuance of the subject document.]]></Comments>
               <Source>
                  <SourceUsername><![CDATA[Glen Bode]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Chicago Operations Office]]></SourceSite>
               </Source>
               <Comments><![CDATA[Subject Matter Expert vicki.prouty@ch.doe.gov
To prevent OUO Marking and Protection requirements from affecting the efficient and economical operation of the agency, a determination that a document contains OUO should be fairly rare.  The number of documents that meet the first two conditions in the OUO determination is virtually countless; therefore, the cost-effectiveness of the review, marking, and protection requirements falls almost completely (except for the 'exceptions' in para. 4d of Chapter I and 2b of Chapter II) on the third condition - reasonable expectation of damage from dissemination.  On the other hand, FOIA exemptions were created in the first place to protect against the harm from disclosure, thereby raising the question how conditions 2) and 3) are different. Again, as asked in comments on the Order, should the magnitude of harm be distinguished for internal disclosure and external disclosure?  Without direction on the magnitude and scope of 'damage' that qualifies information as OUO, this Manual is impossible to implement with the kind of certainty that should be a precondition to the assessment of penalties for negligent violation.

CH Delegate concurs with this comment.  Implementation of the requirements as currently written would significantly impact the efficient and economic performance of DOE.]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Critique]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Departmental Representatives Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Directives Management Team]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[DynMcDermott Petroleum Operations]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fermi National Accelerator Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fernald]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fluor Hanford Inc]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Golden Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Grand Junction]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CIO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CN]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CR]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters ED]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EH]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EIA]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters FE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters GC]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Richard Farman]]></SourceUsername>
                  <SourceTitle><![CDATA[GC DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Headquarters GC]]></SourceSite>
               </Source>
               <ApproverName><![CDATA[]]></ApproverName>
               <Comments><![CDATA[

Subject Matter Expert steve.duarte@hq.doe.gov
1)  DOE may not impose requirements on contractor employees by directive.  If you intend to impose requirements on contractor employees you must promulgate those requirements by notice and comment rulemaking.

2)  If you intend to impose requirements  on contractors, this manual must have a CRD identifying the requirements that apply to contractors.  

3)  The directive is a "rule" as that term is defined by the Small Business Regulatory Enforcement Fairness Act of 1996, 5 U.S.C. 801-804, which requires that, when issued in final form, the directive be reported to Congress.  No action by the OPI is required.  GC will report this directive to Congress when it is issued.

Subject Matter Expert laura.fullerton@hq.doe.gov
Contractor requirements must be stated in a CRD to be attached to this directive.  Requirements cannot be incorporated by reference in a CRD attached to a separate directive.  Please submit a CRD for this directive for review and comment.

]]></Comments>
               <Response>
                  <ResponseLevel><![CDATA[Accepted]]></ResponseLevel>
                  <ResponseContent><![CDATA[The following CRD has been developed for the Manual:

	CONTRACTOR REQUIREMENTS DOCUMENT

	DOE M 471.X-1, MANUAL FOR IDENTIFYING AND PROTECTING
	OFFICIAL USE ONLY INFORMATION

Regardless of the performer of the work, the contractor is responsible for compliance with the requirements of this Contractor Requirements Document (CRD).  The contractor is responsible for flowing down the requirements of this CRD to subcontracts at any tier to the extent necessary to ensure the contractor's compliance with the requirements.  The contractor shall:

1.  Ensure that unclassified information meeting both of the following requirements is identified as OUO information:

    a.  The information falls under at least one of eight Freedom of Information Act (FOIA) exemptions (exemptions 2 through 9; information falling under exemption 1 can never be OUO because it covers information classified by Executive order).  These exemptions describe types of information whose unauthorized dissemination could damage governmental, commercial, or private interests (see DOE G 471.X-1, Guide to Identifying Official Use Only Information, dated XX-XX-02, for a discussion of FOIA exemptions 2 through 9).

    b.  The information has the potential to damage governmental, commercial, or private interests if disseminated to persons who do not need the information to perform their jobs or other DOE-authorized activities.  The possible consequences to such interests should be carefully considered in each case.  (NOTE: Information determined to fall under FOIA exemptions 3 and 4 is automatically considered to cause such damage.)

2.  Ensure that unclassified documents originated by the contractor are identified as containing OUO information based on (a) guidance issued by the DOE  or (b) consideration that the information meets the criteria contained in paragraph 1

3.  Ensure that a document containing OUO information is marked as follows:

    a.  Front Marking.  The front marking includes the applicable FOIA exemption number and related category name (found in DOE G 471.X-1), the name and organization of the employee making the determination, and identifies the guidance used if the determination was based on guidance.  (NOTE: The guidance referred to here is guidance issued by the DOE, not the DOE directives guide (DOE G 471.X-1).)   This marking is placed on the front of each document containing OUO information:

	OFFICIAL USE ONLY
	May be exempt from public release under the Freedom of Information Act(5 U.S.C. 552), exemption number and category:   ___________________________________________________________________________________________________
Department of Energy review required before public release
Name/Org:  ________________________________ Date: ______________
Guidance (if applicable) ___________________________________________________                       
			

    b. Page Marking.  The words "Official Use Only" (or "OUO" if space is limited) are placed on the bottom of each page or, if more convenient, on just those pages containing the OUO information.

    c. Marking E-mail Messages.  The first line of an e-mail message containing OUO information must contain the abbreviation "OUO" before the beginning of the text.  If the message itself is not OUO but an attachment contains OUO information, the message must indicate that the attachment is OUO.  The attachment must have all required OUO markings.
	
    d. Marking Special Format Documents.  Special format documents (e.g., photographs, viewgraphs, films, magnetic tapes, floppy diskettes, audiotapes,  videotapes, DVDs, or CD-ROMs) must be marked in a manner consistent with paragraphs 3a and 3b above so persons possessing the documents and persons with access to the information in or on the documents are aware they contain OUO information.  When space is limited, as on the frame of a 35-mm slide, the page marking is sufficient.

    e. Marking Documents Maintained in Restricted Access Files.  Documents that may contain OUO information that are maintained in files to which access is restricted (e.g., personnel office files) do not need to be reviewed and marked while in these files or when retrieved from the files for reference, inventory, or similar purposes as long as the documents will be returned to the files and are not accessible by individuals who are not authorized access to the OUO information.  However, a document removed from these files and not to be returned (or a copy of such document) must be reviewed to determine whether it contains OUO information and, if appropriate, marked.  (NOTE: Documents that are moved from one restricted access file location to another for storage purposes do not need to be reviewed.)

    f. Transmittal Document.  A document that (1) transmits an attachment or enclosure marked as containing OUO information and (2) does not itself contain classified or controlled information must be marked on its front as follows to call attention to the presence of OUO information in the attachments or enclosures:

	Document transmitted
	contains OUO information	



4. Remove OUO markings from a document when it no longer warrants such protection.  OUO markings applied based on guidance issued by DOE (not the DOE directive guide) may be removed when the guidance used to make the determination states that the information is no longer OUO.  (For example, a topic may state that unclassified information that describes certain deficiencies at a site/facility/security area that have not been corrected is OUO.  Once those deficiencies have been corrected, the OUO marking must be removed.).  

5. Comply with the following marking requirements for documents containing OUO information and other types of classified or controlled information:

   a. Unclassified Documents.  The OUO front marking must be applied to any unclassified document that contains OUO information regardless of any other unclassified control marking (e.g., UCNI).

   b. Classified Documents.  OUO markings must not be applied to any classified document that also contains OUO information.  However, if the classified document has been portion marked, the acronym "OUO" must be used to indicate those portions containing only OUO information.

6. Not require unclassified documents generated before the date of this CRD to be reviewed to determine whether they contain OUO information unless they are to be publicly released.  Any such previously generated document determined to contain OUO information after the date of this CRD must be marked as indicated in paragraph 3 above.  Such determination may be made by anyone with cognizance over the information in the document.  In addition, for unclassified documents marked as containing OUO information before the date of this CRD, the markings are not required to be updated to conform with the marking requirements in this CRD.

7. Be cognizant of the fact that from July 18, 1949, to October 22, 1951, the Atomic Energy Commission used the term "Official Use Only" as a designation for certain classified information.  Documents from this time period with an OUO marking must be handled as Confidential National Security Information pending a determination of their proper classification.  Refer to the CRD for DOE M 475.1-1A, Identifying Classified Information, dated 5-8-98 [National Nuclear Security Administration (NNSA) certified 2-26-01], for specific procedures.

8. Ensure that access to (a) documents marked as containing OUO information or (b) OUO information from such documents is only provided to those persons who need to know the information to perform their jobs or other DOE-authorized activities.

9. Ensure that the following protection requirements are followed:

   a. Protection in Use.  Reasonable precautions must be taken to prevent access to documents marked as containing OUO information by persons who do not require the information to perform their jobs or other DOE-authorized activities (e.g., don't read an OUO document in a public place, such as a cafeteria, on public transportation, etc.).
	
    b. Protection in Storage.  Documents marked as containing OUO information may be stored in unlocked receptacles such as file cabinets, desks, or bookcases when Government or Government-contractor internal building security is provided during nonduty hours.  When such internal building security is not provided, comparable measures should be taken, such as storing the documents in a locked room or other locked receptacle (e.g., a locked file cabinet, desk, bookcase, or briefcase).

    c. Reproduction.  Documents marked as containing OUO information may be reproduced without the permission of the originator to the minimum extent necessary to carry out official activities.  Copies must be marked and protected in the same manner as originals.  Copy machine malfunctions must be cleared and all paper paths checked for papers containing OUO information.  Excess paper containing OUO information must be destroyed as described below.

    d. Destruction.  A document marked as containing OUO information must be destroyed by using a strip-cut shredder that produces strips no more than 1/4-inch wide or by any other means that provides a similar level of destruction that has been approved by the local security office.  The decision to dispose of any DOE or NNSA document, whether it contains OUO information or not, must be consistent with the policies and procedures for records disposition.

    e. Transmission.

       (1)By Mail桹utside of a Facility.

          (a) Use a sealed, opaque envelope or wrapping and mark the envelope or wrapping with the recipient's address, a return address, and the words "TO BE OPENED BY ADDRESSEE ONLY."

          (b) Any of the following U.S. mail methods may be used:  First Class, Express, Certified, or Registered Mail.

          (c) Any commercial carrier may be used.

       (2) By Mail梂ithin a Facility.  Use a sealed, opaque envelope with the recipient's address and the words "TO BE OPENED BY ADDRESSEE ONLY" on the front. 

       (3) By Hand桞etween Facilities or Within a Facility.  A document marked as containing OUO information may be hand carried between or within a facility as long as the person carrying the document can control access to the document being transported.

       (4) Over Telecommunications Circuits.  Documents marked as containing OUO should be protected by encryption when transmitted over telecommunications circuits whenever possible.  This may be accomplished through DOE public key systems or use of encryption algorithms that comply with all applicable Federal laws, regulations, and standards (e.g., Entrust) that address the protection of sensitive unclassified information (see Chapter 9 of DOE M 200.1-1, "Public Key Cryptography and Key Management").  However, if such encryption capabilities are not available and transmission by mail is not a feasible alternative, then regular e-mail or facsimile machines may be used to transmit the document.  

         (a) By Unencrypted Facsimile.  An unencrypted facsimile transmission must be preceded by a telephone call to the recipient so that he or she can control the document when it is received.

         (b) By E-mail without Encryption.  If encryption is not available and some form of protection is desired, the OUO information may be included in a word processing file that is protected by a password and attached to the email message.  Then the sender can call the recipient with the password so that he or she can access the file. 

    f. Transmission over Voice Circuits.  OUO information transmitted over voice circuits should be protected by encryption (see DOE M 200.1-1, Chapter 9, for requirements) whenever possible.  However, if such encryption capabilities are not available and transmission by other encrypted means is not a feasible alternative, then regular voice circuits may be used.

    g. Processing on Automated Information Systems.  An automated information system (AIS) or AIS network must provide methods (e.g., authentication, file access controls, passwords) to prevent access to OUO information stored on the system by persons who do not require the information to perform their jobs or other DOE-authorized activities.]]></ResponseContent>
               </Response>
               <Concurrence><![CDATA[Concur/No Comment]]></Concurrence>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters HG]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters IG]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Wilmatine Slaughter]]></SourceUsername>
                  <SourceTitle><![CDATA[IG Directive Point of Contact]]></SourceTitle>
                  <SourceSite><![CDATA[Headquarters IG]]></SourceSite>
               </Source>
               <ApproverName><![CDATA[Gregory H. Friedman, Inspector General]]></ApproverName>
               <Comments><![CDATA[The applicability of the Order and the Manual needs clarification.  It is unclear whether the Order and/or Manual constitute mandatory requirements or discretionary guidance.

Furthermore, the scope of the Order and Manual needs clarification. Specifically, the Order is too broad and treats protection of all information covered by the FOIA similarly.  It is the OIG's opinion that it is inappropriate to process, mark and protect all of this information in the same manner.
]]></Comments>
               <Response>
                  <ResponseLevel><![CDATA[No Change]]></ResponseLevel>
                  <ResponseContent><![CDATA[These comments are based on the clarifications received in response to SO's request for additional information:

The permissive language found previously in the draft Order and Manual ('may') has been changed to obligatory language ('must'). 

SO is not aware of any information that would be identified as OUO that has statutorily mandated protection requirements more restrictive than those required in this Order and Manual.  Protection requirements contained in these drafts is also consistent with protection requirements for such information by other Government agencies.  Therefore, it is legitimate for ease of implementation and consistency to have one level of protection for all OUO information.  In addition, information eligible to be identified as OUO covers more than b(2) security vulnerabilities.  Guidance will be issued covering all types of eligible information and requirements are now clearly mandatory.]]></ResponseContent>
               </Response>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters IN]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters LM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters MBE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NA]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Diane Gillis]]></SourceUsername>
                  <SourceTitle><![CDATA[NA Directives Point of Contact]]></SourceTitle>
                  <SourceSite><![CDATA[Headquarters NA]]></SourceSite>
               </Source>
               <ApproverName><![CDATA[]]></ApproverName>
               <Comments><![CDATA[
Delegate Rick Phillips for Albuquerque Operations Office
Comment 1:  There is no 'Applicability' statement for this document.  If it is to apply to contractor personnel, then a CRD is required. Chapter 2, paragraph 3 describes the penalty for release of a document marked as containing OUO and refers to DOE O 3750.1, Work Force Discipline.  This order applies to federal personnel and not DOE contractor personnel, need to address how penalties are handled for contractor personnel.  (Mike Spence, AL - Approved by Rick Phillips, AL)

Rationale:  Since the Manual is compliance in nature along with the order, then it should so state and have a companion CRD.  It also should refer to how penalties are handled for contractor personnel as DOE O 3750.1 is not applicable to contractors.


Michelle Beg (AL DPC) for Albuquerque Operations Office


Subject Matter Expert pmathis@doeal.gov
I think that this document is basically sound, providing most of the information required to handle OUO information.  As with any DOE manual, I think it would be prudent to role the associated guides into the manual to ensure adequate compliance.  I recommend you incorporate the Guide for OUO into this manual.



]]></Comments>
               <Response>
                  <ResponseLevel><![CDATA[Accepted with Modification]]></ResponseLevel>
                  <ResponseContent><![CDATA[(Response to Rick Phillips) The applicability statement is contained in the Order, and a CRD for the manual has been developed as follows:

	"CONTRACTOR REQUIREMENTS DOCUMENT

	DOE M 471.X-1, MANUAL FOR IDENTIFYING AND PROTECTING
	OFFICIAL USE ONLY INFORMATION

Regardless of the performer of the work, the contractor is responsible for compliance with the requirements of this Contractor Requirements Document (CRD).  The contractor is responsible for flowing down the requirements of this CRD to subcontracts at any tier to the extent necessary to ensure the contractor's compliance with the requirements.  The contractor shall:

1.  Ensure that unclassified information meeting both of the following requirements is identified as OUO information:

    a.  The information falls under at least one of eight Freedom of Information Act (FOIA) exemptions (exemptions 2 through 9; information falling under exemption 1 can never be OUO because it covers information classified by Executive order).  These exemptions describe types of information whose unauthorized dissemination could damage governmental, commercial, or private interests (see DOE G 471.X-1, Guide to Identifying Official Use Only Information, dated XX-XX-02, for a discussion of FOIA exemptions 2 through 9).

    b.  The information has the potential to damage governmental, commercial, or private interests if disseminated to persons who do not need the information to perform their jobs or other DOE-authorized activities.  The possible consequences to such interests should be carefully considered in each case.  (NOTE: Information determined to fall under FOIA exemptions 3 and 4 is automatically considered to cause such damage.)

2.  Ensure that unclassified documents originated by the contractor are identified as containing OUO information based on (a) guidance issued by the DOE  or (b) consideration that the information meets the criteria contained in paragraph 1

3.  Ensure that a document containing OUO information is marked as follows:

    a.  Front Marking.  The front marking includes the applicable FOIA exemption number and related category name (found in DOE G 471.X-1), the name and organization of the employee making the determination, and identifies the guidance used if the determination was based on guidance.  (NOTE: The guidance referred to here is guidance issued by the DOE, not the DOE directives guide (DOE G 471.X-1).)   This marking is placed on the front of each document containing OUO information:

	OFFICIAL USE ONLY
	May be exempt from public release under the Freedom of Information Act(5 U.S.C. 552), exemption number and category:   ___________________________________________________________________________________________________
Department of Energy review required before public release
Name/Org:  ________________________________ Date: ______________
Guidance (if applicable) ___________________________________________________                       
			

    b. Page Marking.  The words "Official Use Only" (or "OUO" if space is limited) are placed on the bottom of each page or, if more convenient, on just those pages containing the OUO information.

    c. Marking E-mail Messages.  The first line of an e-mail message containing OUO information must contain the abbreviation "OUO" before the beginning of the text.  If the message itself is not OUO but an attachment contains OUO information, the message must indicate that the attachment is OUO.  The attachment must have all required OUO markings.
	
    d. Marking Special Format Documents.  Special format documents (e.g., photographs, viewgraphs, films, magnetic tapes, floppy diskettes, audiotapes,  videotapes, DVDs, or CD-ROMs) must be marked in a manner consistent with paragraphs 3a and 3b above so persons possessing the documents and persons with access to the information in or on the documents are aware they contain OUO information.  When space is limited, as on the frame of a 35-mm slide, the page marking is sufficient.

    e. Marking Documents Maintained in Restricted Access Files.  Documents that may contain OUO information that are maintained in files to which access is restricted (e.g., personnel office files) do not need to be reviewed and marked while in these files or when retrieved from the files for reference, inventory, or similar purposes as long as the documents will be returned to the files and are not accessible by individuals who are not authorized access to the OUO information.  However, a document removed from these files and not to be returned (or a copy of such document) must be reviewed to determine whether it contains OUO information and, if appropriate, marked.  (NOTE: Documents that are moved from one restricted access file location to another for storage purposes do not need to be reviewed.)

    f. Transmittal Document.  A document that (1) transmits an attachment or enclosure marked as containing OUO information and (2) does not itself contain classified or controlled information must be marked on its front as follows to call attention to the presence of OUO information in the attachments or enclosures:

	Document transmitted
	contains OUO information	



4. Remove OUO markings from a document when it no longer warrants such protection.  OUO markings applied based on guidance issued by DOE (not the DOE directive guide) may be removed when the guidance used to make the determination states that the information is no longer OUO.  (For example, a topic may state that unclassified information that describes certain deficiencies at a site/facility/security area that have not been corrected is OUO.  Once those deficiencies have been corrected, the OUO marking must be removed.).  

5. Comply with the following marking requirements for documents containing OUO information and other types of classified or controlled information:

   a. Unclassified Documents.  The OUO front marking must be applied to any unclassified document that contains OUO information regardless of any other unclassified control marking (e.g., UCNI).

   b. Classified Documents.  OUO markings must not be applied to any classified document that also contains OUO information.  However, if the classified document has been portion marked, the acronym "OUO" must be used to indicate those portions containing only OUO information.

6. Not require unclassified documents generated before the date of this CRD to be reviewed to determine whether they contain OUO information unless they are to be publicly released.  Any such previously generated document determined to contain OUO information after the date of this CRD must be marked as indicated in paragraph 3 above.  Such determination may be made by anyone with cognizance over the information in the document.  In addition, for unclassified documents marked as containing OUO information before the date of this CRD, the markings are not required to be updated to conform with the marking requirements in this CRD.

7. Be cognizant of the fact that from July 18, 1949, to October 22, 1951, the Atomic Energy Commission used the term "Official Use Only" as a designation for certain classified information.  Documents from this time period with an OUO marking must be handled as Confidential National Security Information pending a determination of their proper classification.  Refer to the CRD for DOE M 475.1-1A, Identifying Classified Information, dated 5-8-98 [National Nuclear Security Administration (NNSA) certified 2-26-01], for specific procedures.

8. Ensure that access to (a) documents marked as containing OUO information or (b) OUO information from such documents is only provided to those persons who need to know the information to perform their jobs or other DOE-authorized activities.

9. Ensure that the following protection requirements are followed:

   a. Protection in Use.  Reasonable precautions must be taken to prevent access to documents marked as containing OUO information by persons who do not require the information to perform their jobs or other DOE-authorized activities (e.g., don't read an OUO document in a public place, such as a cafeteria, on public transportation, etc.).
	
    b. Protection in Storage.  Documents marked as containing OUO information may be stored in unlocked receptacles such as file cabinets, desks, or bookcases when Government or Government-contractor internal building security is provided during nonduty hours.  When such internal building security is not provided, comparable measures should be taken, such as storing the documents in a locked room or other locked receptacle (e.g., a locked file cabinet, desk, bookcase, or briefcase).

    c. Reproduction.  Documents marked as containing OUO information may be reproduced without the permission of the originator to the minimum extent necessary to carry out official activities.  Copies must be marked and protected in the same manner as originals.  Copy machine malfunctions must be cleared and all paper paths checked for papers containing OUO information.  Excess paper containing OUO information must be destroyed as described below.

    d. Destruction.  A document marked as containing OUO information must be destroyed by using a strip-cut shredder that produces strips no more than 1/4-inch wide or by any other means that provides a similar level of destruction that has been approved by the local security office.  The decision to dispose of any DOE or NNSA document, whether it contains OUO information or not, must be consistent with the policies and procedures for records disposition.

    e. Transmission.

       (1)By Mail桹utside of a Facility.

          (a) Use a sealed, opaque envelope or wrapping and mark the envelope or wrapping with the recipient's address, a return address, and the words "TO BE OPENED BY ADDRESSEE ONLY."

          (b) Any of the following U.S. mail methods may be used:  First Class, Express, Certified, or Registered Mail.

          (c) Any commercial carrier may be used.

       (2) By Mail梂ithin a Facility.  Use a sealed, opaque envelope with the recipient's address and the words "TO BE OPENED BY ADDRESSEE ONLY" on the front. 

       (3) By Hand桞etween Facilities or Within a Facility.  A document marked as containing OUO information may be hand carried between or within a facility as long as the person carrying the document can control access to the document being transported.

       (4) Over Telecommunications Circuits.  Documents marked as containing OUO should be protected by encryption when transmitted over telecommunications circuits whenever possible.  This may be accomplished through DOE public key systems or use of encryption algorithms that comply with all applicable Federal laws, regulations, and standards (e.g., Entrust) that address the protection of sensitive unclassified information (see Chapter 9 of DOE M 200.1-1, "Public Key Cryptography and Key Management").  However, if such encryption capabilities are not available and transmission by mail is not a feasible alternative, then regular e-mail or facsimile machines may be used to transmit the document.  

         (a) By Unencrypted Facsimile.  An unencrypted facsimile transmission must be preceded by a telephone call to the recipient so that he or she can control the document when it is received.

         (b) By E-mail without Encryption.  If encryption is not available and some form of protection is desired, the OUO information may be included in a word processing file that is protected by a password and attached to the email message.  Then the sender can call the recipient with the password so that he or she can access the file. 

    f. Transmission over Voice Circuits.  OUO information transmitted over voice circuits should be protected by encryption (see DOE M 200.1-1, Chapter 9, for requirements) whenever possible.  However, if such encryption capabilities are not available and transmission by other encrypted means is not a feasible alternative, then regular voice circuits may be used.

    g. Processing on Automated Information Systems.  An automated information system (AIS) or AIS network must provide methods (e.g., authentication, file access controls, passwords) to prevent access to OUO information stored on the system by persons who do not require the information to perform their jobs or other DOE-authorized activities."

The requirement for a contractor to impose penalties is now contained in the CRD for the Order.  No specifics are included concerning the types of penalties a contractor may impose because the General Counsel's office advises we should be brief and non-specific, and leave it to the contractor to decide what penalty is appropriate.

(Response to Michelle Beg) The information contained in the DOE Directives Guide for OUO contains information that is not mandatory and its intent is instructional.  Requirements in the Manual are mandatory.  To reduce confusion about what information is or is not mandatory, we prefer to have the DOE Directives Guide separate (and this complies with the DOE directives system).  There will be mandatory guidance issued to assist with identifying specific information as OUO (under paragraphs 5a(4) and (5) and 5b(2) of the Order).  Such guidance is mandatory and is separate and distinct from the DOE Directives Guide.]]></ResponseContent>
               </Response>
               <Concurrence><![CDATA[Concur/No Comment]]></Concurrence>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NTEU]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters OA]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters OPI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters PC-1]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters PO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters RW]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters SC]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Sabeena Rangwala]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Headquarters SC]]></SourceSite>
               </Source>
               <Comments><![CDATA[According to this Manual:

'1) Over Telecommunications Circuits. Documents marked as containing 
OUO should be transmitted using secure communications whenever possible. However, if such communications capabilities are not available 
and transmission by mail is not a feasible alternative, then regular 
e-mail or facsimile machines may be used to transmit the document. Such a 
transmission should be preceded by a telephone call to the recipient so 
that he or she can control the document as soon as possible.'

COMMENT: Equating facsimiles with e-mails seems to mix apples and oranges. The concept of using a preceding phone call to say 'I'm sending OUO now' for a fax has some logic behind it: you don't normally know where the fax is, who has access, etc. A preceding phone call for an e-mail has little logic behind it (e.g., e-mail is normally considered to be password-protected); plus, a decent-sized e-mail distribution would 
require lots of phone calls. Further, questions abound: Do you actually 
have to talk to the actual recipient? Is leaving a message good enough? There's not enough detail here.

RECOMMENDED CHANGE: Retain the preference to use secure communications. For situations where secure communications are not possible, leave in facsimiles, but remove e-mail.

The main reasons for CH's non-concurrence include:

--These directives describe a solution with no problem. Most information that would be subject to these requirements is already subject to statutory, regulatory, or other protections. Any additional requirements should be narrowly tailored to address specific deficiencies in these protections; no such deficiencies have been identified. 

--The requirements, even taking into consideration the "exemptions" in the Manual for documents maintained in receptacles, are likely to create a burden far in excess of the protective benefit. OUO awareness and implementation training alone would have a major impact on personnel already burdened by reduced staffing levels. 

--These drafts do not sufficiently address what documents require OUO markings. While it is clear from these drafts that OUO information must meet an exemption from FOIA release, the "damage to national security" threshold requiring OUO markings is indeterminable. Without a "damage" threshold, the third definitional criterion is already covered by the second. As long as any employee may make a "discretionary determination" that a document contains OUO, this lack of guidance will result in a flood of documents being marked as OUO.

--These drafts do not clearly distinguish identification of OUO information and the review of documents for releasibility under a FOIA request. Just as an OUO marking does not automatically mean a document is exempt, documents not marked OUO are not automatically releasable.

Until CH's issues are properly addressed, we cannot concur with the issuance of the subject document.

To prevent OUO Marking and Protection requirements from affecting the efficient and economical operation of the agency, a determination that a document contains OUO should be fairly rare. The number of documents that meet the first two conditions in the OUO determination is virtually countless; therefore, the cost-effectiveness of the review, marking, and protection requirements falls almost completely (except for the 'exceptions' in para. 4d of Chapter I and 2b of Chapter II) on the third condition - reasonable expectation of damage from dissemination. On the other hand, FOIA exemptions were created in the first place to protect against the harm from disclosure, thereby raising the question how conditions 2) and 3) are different. Again, as asked in comments on the Order, should the magnitude of harm be distinguished for internal disclosure and external disclosure? Without direction on the magnitude and scope of 'damage' that qualifies information as OUO, this Manual is impossible to implement with the kind of certainty that should be a precondition to the assessment of penalties for negligent violation.

CH Delegate concurs with this comment. Implementation of the requirements as currently written would significantly impact the efficient and economic performance of DOE.

]]></Comments>
               <Response>
                  <ResponseLevel><![CDATA[Accepted with Modification]]></ResponseLevel>
                  <ResponseContent><![CDATA[(Response to OR) Paragraph 2e(4) has been revised as follows 
"Over Telecommunications Circuits.  Documents marked as containing OUO should be protected by encryption when transmitted over telecommunications circuits whenever possible.  This may be accomplished through DOE public key systems or use of encryption algorithms that comply with all applicable Federal laws, regulations, and standards (e.g., Entrust) that address the protection of sensitive unclassified information (see Chapter 9 of DOE M 200.1-1, "Public Key Cryptography and Key Management").  However, if such encryption capabilities are not available and transmission by mail is not a feasible alternative, then regular e-mail or facsimile machines may be used to transmit the document.  

(a)  By Unencrypted Facsimile.  An unencrypted facsimile transmission must be preceded by a telephone call to the recipient so that he or she can control the document when it is received.

(b) By E-mail without Encryption.  If encryption is not available and some form of protection is desired, the OUO information may be included in a word processing file that is protected by a password and attached to the email message.  Then the sender can call the recipient with the password so that he or she can access the file." 

The recipient is the person who needs access to the information; therefore, the sender should speak with the recipient.

(Response to CH)  As you noted, many labels and protection systems have been established to try to control the dissemination of unclassified information.  The study conducted by the Commission on Science and Security (CSIS) noted, 'At least 20 categories of information appear to fall under the sensitive unclassified umbrella, most without effective or consistent Department-wide implementation.'  Uncounted resources are now being expended on marking and protecting some of these categories of information that have no formal implementation through the DOE directives and some no legal basis.  The CSIS recommended, and the Secretary of Energy agreed, to place such unclassified controlled information under the control category of Official Use Only.  This Manual implements that recommendation.  

To assist with implementing this Order and Manual, a DOE Directives Guide is to be issued when the Order and Manual are approved and issued that provides employees with the statutory text for each exemption, a discussion of what that text means, and examples of types of information that could fall under that exemption.  A pamphlet will also be distributed to all employees that will contain similar information.

This Order concerns identifying and protecting documents containing OUO information, not about how a document is processed if requested under the FOIA.  However, the Order clearly states that documents marked as containing OUO are not automatically exempt from public release if requested under the FOIA, but must be processed under 10 CFR Part 1004. 

Conditions 2 and 3 are different.  Many of the FOIA exemptions are discretionary.  Almost every document written in the Government could fall under exemption 5; hence the importance of applying the damage test in condition 3.  If a person, whether inside or outside, needs the information to perform his or her job, then the damage is considered to be the same.  It is impossible to predetermine that in all cases internal damage is less than external damage.  To provide information on the magnitude and scope of damage, we are issuing guidance -- (1) a DOE directives guide to help everyone better understand what information may be exempt under the FOIA exemptions and (2) guidance issued under this Order by program offices/field elements or by the Director, Office of Security, that identifies specific information to be designated as OUO.]]></ResponseContent>
               </Response>
               <Concurrence><![CDATA[Non-concur]]></Concurrence>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters SO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Honeywell FM&T (Kansas City Plant)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Idaho Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Idaho Operations Office-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[INL - NE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[INL-ICP-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Kaiser-Hill Company, LLC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Kansas City Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Lawrence Berkeley Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Lawrence Livermore National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Livermore Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Los Alamos National Laboratory]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Mike Irving]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Los Alamos National Laboratory]]></SourceSite>
               </Source>
               <Comments><![CDATA[
Subject Matter Expert jabrown@lanl.gov
Overall, the provisions of this directive are very loose.  Some significant procedural questions are not addressed.  The directive appears to be ambivalent about the degree of rigor and prescription necessary to establish this program.  Unfortunately, since the entire subject area of unclassified sensitive information is so broad and covers information that is not in any way related to national security interests, we should expect that the end result will be having everything not specifically intended for public release marked as OUO, as a defensive measure by employees who fear the penalty provisions.

]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Los Alamos Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[NA Service Center]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Yolanda Bolivar]]></SourceUsername>
                  <SourceTitle><![CDATA[AL DPC]]></SourceTitle>
                  <SourceSite><![CDATA[NA Service Center]]></SourceSite>
               </Source>
               <ApproverName><![CDATA[]]></ApproverName>
               <Comments><![CDATA[

Subject Matter Expert pmathis@doeal.gov
I think that this document is basically sound, providing most of the information required to handle OUO information.  As with any DOE manual, I think it would be prudent to role the associated guides into the manual to ensure adequate compliance.  I recommend you incorporate the Guide for OUO into this manual.

]]></Comments>
               <Source>
                  <SourceUsername><![CDATA[Rick Phillips]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[NA Service Center]]></SourceSite>
               </Source>
               <Comments><![CDATA[Comment 1:  There is no 'Applicability' statement for this document.  If it is to apply to contractor personnel, then a CRD is required. Chapter 2, paragraph 3 describes the penalty for release of a document marked as containing OUO and refers to DOE O 3750.1, Work Force Discipline.  This order applies to federal personnel and not DOE contractor personnel, need to address how penalties are handled for contractor personnel.  (Mike Spence, AL - Approved by Rick Phillips, AL)

Rationale:  Since the Manual is compliance in nature along with the order, then it should so state and have a companion CRD.  It also should refer to how penalties are handled for contractor personnel as DOE O 3750.1 is not applicable to contractors.
]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[National Energy Technology Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[National Renewable Energy Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Nevada Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oak Ridge National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oak Ridge Operations Office]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Jennifer Hamilton]]></SourceUsername>
                  <SourceTitle><![CDATA[OR DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Oak Ridge Operations Office]]></SourceSite>
               </Source>
               <ApproverName><![CDATA[]]></ApproverName>
               <Comments><![CDATA[Oak Ridge Operations submits the following major issue.  The ORO Subject Matter Expert for OUO and the ORO Assistant Manager for Administration support this major issue:

According to this Manual:

'1) Over Telecommunications Circuits.  Documents marked as containing 
OUO should be transmitted using secure communications whenever possible.  However, if such communications capabilities are not available 
and transmission by mail is not a feasible alternative, then regular 
e-mail or facsimile machines may be used to transmit the document.  Such a 
transmission should be preceded by a telephone call to the recipient so 
that he or she can control the document as soon as possible.'

COMMENT:  Equating facsimiles with e-mails seems to mix apples and oranges.  The concept of using a preceding phone call to say 'I'm sending OUO now' for a fax has some logic behind it: you don't normally know where the fax is, who has access, etc.  A preceding phone call for an e-mail has little logic behind it (e.g., e-mail is normally considered to be password-protected); plus, a decent-sized e-mail distribution would 
require lots of phone calls.  Further, questions abound:  Do you actually 
have to talk to the actual recipient?  Is leaving a message good enough?  There's not enough detail here.

RECOMMENDED CHANGE: Retain the preference to use secure communications.  For situations where secure communications are not possible, leave in facsimiles, but remove e-mail.

]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oakland Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Office of Energy Assurance]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Office of River Protection]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Ohio Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[OSTI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Pacific Northwest National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Pantex Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Portsmouth Paducah Project Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Princeton Plasma Physics Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Richland Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Rocky Flats Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Sandia National Laboratories]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Rebecca Cayen]]></SourceUsername>
                  <SourceTitle><![CDATA[SNL DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Sandia National Laboratories]]></SourceSite>
               </Source>
               <ApproverName><![CDATA[]]></ApproverName>
               <Comments><![CDATA[The following comment is from Ashley McConnell, Dept. 3130 Information & Integration [(505-845-9115].  It meets the criteria of performing efficiently or economically and was approved by Al West, Director of 3100 Integrated Safety & Security Center. <P>
Changing our marking requirements will be costly. At Sandia National Laboratories we have identified 14 categories of Unclassified Controlled Information. There is a significant impact to the line based on Chapter I.4.g.   We currently have documents marked: <P>
                 Applied Technology (DOE G 241.1)<BR> 
                 Attorney-Client and/or Work Product Privileged Information <BR> 
                 Confidential Foreign Government Information-Modified Handling (CFGI/MOD) (see DOE M 471.2-1C) <BR>
                 Export Controlled Information <BR>
                 Legal Process Protected Information <BR> 
                 Naval Nuclear Propulsion Information (see DOE M 471.2-1C) <BR> 
                 Non-Sandia Proprietary Information (Specific Nondisclosure Agreement (NDA) under which all Proprietary Information is provided to Sandia) <BR> 
                 Official Use Only Information (per CG-SS-4) <BR> 
                 Patent Caution Information (35 U.S.C. [section 205]) <BR>
                 Protected Cooperative Research and Development Agreement (CRADA) <BR>
                 Information (National Competitiveness Technology Transfer Act of 1989, as well as the Stevenson-Wydler Technology Innovation Act of 1980, Public Law 101-189, as implemented by Title 15 USC Section 3710a) <BR>
                 Safeguards Information (10 CFR 73.21) <BR>
                 Small Business Innovation Research (SBIR) Information (The Small Business Innovation Act of 1982, as amended by the current Small Business Act of October 15, 2001, Public Law 85-536, Section 9 (k) (4) and implemented by Title 15 USC 638), provides for the creation and protection of SBIR and STTR) <BR>
                 Unclassified Controlled Nuclear Information (UCNI) (see DOE M 471.1-1, 10 CFR Part 1017, 'Identification and Protection of Unclassified Controlled Nuclear Information) 


]]></Comments>
               <Source>
                  <SourceUsername><![CDATA[Ashley McConnell]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Sandia National Laboratories]]></SourceSite>
               </Source>
               <Comments><![CDATA[Category: Ability to perform efficiently or economically

Changing our marking requirements will be costly.  At Sandia National Laboratory we have identified 14 categories of Unclassified Controlled Information.  There is a significant impact to the line based on Chapter I.4.g.  We currently have documents marked:
脗路 Applied Technology (DOE G 241.1)
脗路 Attorney-Client and/or Work Product Privileged Information
脗路 Confidential Foreign Government Information-Modified Handling (CFGI/MOD) (see DOE M 471.2-1C)
脗路 Export Controlled Information
脗路 Legal Process Protected Information
脗路 Naval Nuclear Propulsion Information (see DOE M 471.2-1C)
脗路 Non-Sandia Proprietary Information (Specific Nondisclosure Agreement (NDA) under which all Proprietary Information is provided to Sandia)
脗路 Official Use Only Information (per CG-SS-4)
脗路 Patent Caution Information (35 U.S.C. 脙鈥毭偮205)
脗路 Protected Cooperative Research and Development Agreement (CRADA) Information (National Competitiveness Technology Transfer Act of 1989 as well as the Stevenson-Wydler Technology Innovation Act of 1980, Public Law 101-189, as implemented by Title 15 USC Section 3710a)
脗路 Safeguards Information (10 CFR 73.21)
脗路 Small Business Innovation Research (SBIR) Information (The Small Business Innovation Act of 1982 as amended by the current Small Business Act of October 15, 2001, Public Law 85-536, section 9 (k) (4) and implemented by Title 15 USC 638 provides for the creation and protection of SBIR and STTR)
脗路 Unclassified Controlled Nuclear Information (UCNI) (see DOE M 471.1-1, 10 CFR Part 1017, 'Identification and Protection of Unclassified Controlled Nuclear Information)
]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Sandia Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Savannah River EM Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Savannah River Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Southeastern Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Southwestern Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Stanford Linear Accelerator Center]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Stanford Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Thomas Jefferson National Accelerator Facility]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[University of California]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Wackenhut Services Inc (SRS)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Wackenhut Services Inc. (Nevada)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[West Valley Demonstration Project]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Western Area Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Westinghouse Savannah River Corp.]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Westinghouse Savannah River Corp. for SR-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[WIPP]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 (BWXT)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 (WSI)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 Site Office]]></OrganizationName>
            </Organization>
         </Section>
         <Section>
            <SectionTitle><![CDATA[1. Purpose, 2. Summary, 3. References, 4. Contact]]></SectionTitle>
            <SectionContent><![CDATA[
     1.   PURPOSE.  This Department of Energy (DOE) Manual provides detailed requirements to
     supplement DOE O 471.X, Identifying and Protecting Official Use Only Information,
     dated XX-XX-02.

     2.   SUMMARY.  This Manual comprises two chapters that provide direction for identifying,
     marking, and protecting Official Use Only (OUO) information.  These chapters address
     mandatory procedures and management processes.  Chapter I describes the requirements
     for identifying and marking OUO information; Chapter II addresses protecting OUO
     information.

     3.   REFERENCES.

               a.   10 CFR Part 1004, Freedom of Information.

               b.   DOE O 471.X, Identifying and Protecting Official Use Only Information, dated
          XX-XX-02.

               c.   DOE G 471.X-X, Guide to Identifying Official Use Only Information, dated
          XX-XX-02

               d.   DOE M 475.1-1A, Identifying Classified Information, dated 5-8-98 (National
          Nuclear Security Administration certified 2-26-01).

               e.   DOE 3750.1, Work Force Discipline, dated 3-23-83.

     4.   CONTACT.  Questions concerning this Manual should be addressed as follows.

               a.   Questions on Chapter I should be addressed to Information Classification and
          Control Policy at 301-903-5454.

               b.   Questions on Chapter II should be addressed to Safeguards and Security Policy at
          301-903-7325, except for questions concerning transmitting or processing OUO
          information electronically, which should be addressed to Policy Integration and
          Technical Support at 301-903-4053.

                    

                                                                      SPENCER ABRAHAM
                                                                      Secretary of Energy

]]></SectionContent>
            <Organization>
               <OrganizationName><![CDATA[Ames Labortatory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Argonne National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Associate Manager for Science & Technology, Richland]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bechtel Hanford]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bechtel Nevada]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Berkeley Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bonneville Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Brookhaven National  Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[BWXT Pantex, LLC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Carlsbad Area Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Carlsbad Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[CH2MHill]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Chicago Operations Office]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Glen Bode]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Chicago Operations Office]]></SourceSite>
               </Source>
               <Comments><![CDATA[
Subject Matter Expert martin@eml.doe.gov

CH Delegate checked with SME and verified he intended to hit "No Comment" button.


]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Critique]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Departmental Representatives Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Directives Management Team]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[DynMcDermott Petroleum Operations]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fermi National Accelerator Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fernald]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fluor Hanford Inc]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Golden Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Grand Junction]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CIO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CN]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CR]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters ED]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EH]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EIA]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters FE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters GC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters HG]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters IG]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters IN]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters LM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters MBE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NA]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NTEU]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters OA]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters OPI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters PC-1]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters PO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters RW]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters SC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters SO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Honeywell FM&T (Kansas City Plant)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Idaho Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Idaho Operations Office-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[INL - NE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[INL-ICP-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Kaiser-Hill Company, LLC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Kansas City Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Lawrence Berkeley Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Lawrence Livermore National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Livermore Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Los Alamos National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Los Alamos Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[NA Service Center]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Rick Phillips]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[NA Service Center]]></SourceSite>
               </Source>
               <Comments><![CDATA[No comments.]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[National Energy Technology Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[National Renewable Energy Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Nevada Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oak Ridge National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oak Ridge Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oakland Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Office of Energy Assurance]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Office of River Protection]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Ohio Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[OSTI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Pacific Northwest National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Pantex Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Portsmouth Paducah Project Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Princeton Plasma Physics Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Richland Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Rocky Flats Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Sandia National Laboratories]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Rebecca Cayen]]></SourceUsername>
                  <SourceTitle><![CDATA[SNL DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Sandia National Laboratories]]></SourceSite>
               </Source>
               <Comments><![CDATA[The following comment was supplied by Ashley McConnell, Dept. 3130 Information & Integration.  It was approved by Al West, Director of Integrated Safety & Security Center 3100.  It meets the criteria of complying with applicable laws, rules, and regulations; and ability to perform efficiently and economically. <P>
Using Official Use Only (OUO) to protect sensitive information isn't as strong as using the requirements of the pertinent law to protect the information. I believe that using the Freedom of Information Act Exemptions as the tool to protect UCNI, Export Controlled or Safeguards Information is weaker than using the actual laws to indicate why the information is protected and how. What is the benefit of using this back door approach via the Freedom of Information Act Exemptions, rather than using the front door approach of citing the legal requirements? <P>

The following comment is from Ron Williams, Dept. 3132 Classification and Information Security.  It meets the criteria of meeting policy objectives and missions.  <BR>

Subject Matter Expert ronwill@sandia.gov
The order indicates that OUO categories are those that are exempt from FOIA.  Since the majority of information residing in the DOE complex would only be controlled due to the 'Export Administration Act' (which is not the FOIA exemption), it appears the OUO order will not protect much DOE information.  Is that the intent of the author of the order?

]]></Comments>
               <Source>
                  <SourceUsername><![CDATA[Ashley McConnell]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Sandia National Laboratories]]></SourceSite>
               </Source>
               <Comments><![CDATA[Category:  Ability to comply with applicable laws, rules, and regulations; Ability to perform efficiently or economically.
Using Official Use Only (OUO)  to protect sensitive information isn't as strong as using the requirements of the pertinent law to protect the information.  I believe that using  the Freedom of Information act exemptions as the tool to protect UCNI, Export Controlled or Safeguards Information is weaker than using the actual laws to indicate why the information is protected and how.  What is the benefit of using this back door approach via the Freedom of Information Act exemptions rather than using the front door approach of citing the legal requirements?   ]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Sandia Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Savannah River EM Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Savannah River Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Southeastern Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Southwestern Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Stanford Linear Accelerator Center]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Stanford Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Thomas Jefferson National Accelerator Facility]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[University of California]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Wackenhut Services Inc (SRS)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Wackenhut Services Inc. (Nevada)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[West Valley Demonstration Project]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Western Area Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Westinghouse Savannah River Corp.]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Westinghouse Savannah River Corp. for SR-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[WIPP]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 (BWXT)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 (WSI)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 Site Office]]></OrganizationName>
            </Organization>
         </Section>
         <Section>
            <SectionTitle><![CDATA[Chapter I Identifying and Marking Official Use Only Information, 1. Introduction, 2. Identifying Information as Official Use Only, 3. Determining Whether a Document Contains Official Use Only Information]]></SectionTitle>
            <SectionContent><![CDATA[
      IDENTIFYING AND MARKING OFFICIAL USE ONLY INFORMATION


     1.   INTRODUCTION.  This Department of Energy (DOE) Manual supplements DOE
     O 471.X, Identifying and Protecting Official Use Only Information, dated XX-XX-02,
     and provides detailed information and directions for identifying, marking, and protecting
     Official Use Only (OUO) information.

     2.   IDENTIFYING INFORMATION AS OFFICIAL USE ONLY.  To be identified as OUO,
     information must meet all of the following criteria:

               a.   Be unclassified.

               b.   Fall under at least one of eight Freedom of Information Act (FOIA) exemptions
          (exemptions 2 through 9; information falling under exemption 1 can never be
          OUO because it covers information classified by Executive order).  These
          exemptions describe types of information whose unauthorized dissemination
          could damage governmental, commercial, or private interests (see DOE
          G 471.X-X, Guide to Identifying Official Use Only Information, dated            
          XX-XX-02, for a discussion of FOIA exemptions 2 through 9).

               c.   Reasonably be expected to cause damage to governmental, commercial, or private
          interests if disseminated to persons who do not need the information to perform
          their official duties or other DOE-authorized activities.  The possible
          consequences to such interests should be carefully considered in each case.

     3.   DETERMINING WHETHER A DOCUMENT CONTAINS OFFICIAL USE ONLY
     INFORMATION.  Any employee may determine that an unclassified document contains
     OUO information.

               a.   Discretionary Determination.  The employee considers whether information in the
          document meets the criteria in paragraph 2 above.  If it does, the employee may
          determine that the document contains OUO information. 

               b.   Mandatory Determination.  If guidance issued by Information Classification and
          Control Policy (and concurred in by the program office with cognizance over the
          information) identifies certain information as OUO, then the employee must
          determine that a document containing such information is OUO.

]]></SectionContent>
            <Organization>
               <OrganizationName><![CDATA[Ames Labortatory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Argonne National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Associate Manager for Science & Technology, Richland]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bechtel Hanford]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bechtel Nevada]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Berkeley Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bonneville Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Brookhaven National  Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[BWXT Pantex, LLC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Carlsbad Area Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Carlsbad Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[CH2MHill]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Chicago Operations Office]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Glen Bode]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Chicago Operations Office]]></SourceSite>
               </Source>
               <Comments><![CDATA[
Subject Matter Expert martin@eml.doe.gov

CH Delegate contacted SME and verified he intended to submit "No Comment".


]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Critique]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Departmental Representatives Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Directives Management Team]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[DynMcDermott Petroleum Operations]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fermi National Accelerator Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fernald]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Fluor Hanford Inc]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Golden Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Grand Junction]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CIO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CN]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters CR]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters ED]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EH]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EIA]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters EM]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Joni Boone]]></SourceUsername>
                  <SourceTitle><![CDATA[EM DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Headquarters EM]]></SourceSite>
               </Source>
               <Comments><![CDATA[Delegate M. Peggy Wright for Savannah River EM Office
Section 3.a. and b. - Replace these sections with the following:  "The marking of documents at the time of their creation provides notice of OUO content and facilitates the review process when a document is requested under the FOIA process.  Documents requested for public release that do not bear such markings shall not be assumed to be releasable without examination for the presence of information that requires continued protection and qualifies as exempt from public release."  Basis:  It would be confusing to determine when a document should be discretionary determination vs. mandatory determination since not all employees will be issued guidance from Information Classification and Control Policy identifying certain information that is OUO.  Furthermore, the DOE G 471.X.X is not a mandatory guide.  The idea is if an individual believes a document has sensitive unclassifed information that falls under one of the exemptions, then they should mark and protect as such. 

Dixie Evans (ID DPC) for Idaho Operations Office
Chapter 1, paragraph 3.- It is not reasonable to expect ALL employees to consistently and correctly determine if a document  contains OUO information, based on a) "FOIA exemptions ..." and b) "reasonably be expected ...".  Training and experience in FOIA, Unclassified Sensitive Information and other aspects of information management are needed to properly mark documents.  Recommend  language be added requiring  all unclassified documents to be released to the public, be reviewed by designated determination authorities. Each DOE office could then designate those individuals with the proper credentials, including CO's, ADC's, FOIA officers, etc..  Documents prepared for "internal" use would be reviewed by those designated as determining authorities, if desired by the preparer, otherwise left unmarked.   If all employees are tasked with determining sensitivity and FOIA exemption, marking the documents and then later removing the designation as they see fit, field units will lose control and the whole process will loss credibility, both internally and with the public. (Comment by D. D. Wagner - DOE-OD OPI and concurred on by R. F. Wilbur, Deputy Manager, Technical Support)

]]></Comments>
               <Response>
                  <ResponseLevel><![CDATA[Accepted with Modification]]></ResponseLevel>
                  <ResponseContent><![CDATA[[Response to Peggy Wright] Paragraphs 3a and b have been revised as follows:  

"a.  Determination Based on Guidance.  If guidance issued under DOE O 471.X identifies certain information as OUO, then an employee must determine that a document containing such information is OUO. (NOTE:  The guidance referred to here is guidance issued under DOE O 471.X, not the DOE directives guide (DOE G 471.X-1).) 

b. Determination Based on Employee's Evaluation.  An employee considers whether information in a document meets the criteria in paragraph 2 above.  If it does, the employee must determine that the document contains OUO information."  

The order of these paragraphs implies that an employee should first consult any guidance he/she has to see if the information is covered.  If not covered and the employee believes the information meets the criteria, then he/she should mark and protect it.  

[Response to Dixie Evans] Guidance to be issued by either a program office/field element or the Director, Office of Security, that specifies what information is OUO is intended to improve the consistency of determinations.  We see great value in having a decentralized system so that all document originators are aware of what information is sensitive so that they protect it at all times -- at work and outside of work.  OUO is not as sensitive as classified information and to impose such an onerous system as the one followed for classified information seems unnecessary.  Since the information is less sensitive, risk management principles allow us to tolerate less consistency in OUO determinations.]]></ResponseContent>
               </Response>
               <Concurrence><![CDATA[Concur/No Comment]]></Concurrence>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters FE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters GC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters HG]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters IG]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Wilmatine Slaughter]]></SourceUsername>
                  <SourceTitle><![CDATA[IG Directive Point of Contact]]></SourceTitle>
                  <SourceSite><![CDATA[Headquarters IG]]></SourceSite>
               </Source>
               <Comments><![CDATA[Chapter 1, paragraph 3:  It is the OIG's position that only an employee from a document's originating office may make OUO determinations.  Thus, the language following paragraph 3's heading should read, "Any employee from an office that originates an unclassified document may determine whether that document contains OUO information."  

]]></Comments>
               <Response>
                  <ResponseLevel><![CDATA[Accepted]]></ResponseLevel>
                  <ResponseContent><![CDATA[This change has been made.]]></ResponseContent>
               </Response>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters IN]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters LM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters MBE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NA]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Diane Gillis]]></SourceUsername>
                  <SourceTitle><![CDATA[NA Directives Point of Contact]]></SourceTitle>
                  <SourceSite><![CDATA[Headquarters NA]]></SourceSite>
               </Source>
               <Comments><![CDATA[
Delegate Rick Phillips for Albuquerque Operations Office
Comment 1:  Paragraph 3.b.  This paragraph states that only guidance from ICCP may be issued for use in making mandatory determinations.  A paragraph should be added that allows for locally developed OUO guidance to be developed, approved, issued, and used.  (Mike Spence, AL - Approved by Rick Phillips, AL)

Rationale:  Guidance relative to OUO information is best developed locally by a cognizant approval authority most familiar with the local information protection regime.  This is consistent with the past practice of OUO determinations and FOIA exemption witholdings being accomplished at the field office level.

Michelle Beg (AL DPC) for Albuquerque Operations Office


Subject Matter Expert pmathis@doeal.gov
Paragraph 2.b. should include a short, bullitized description of the eight FOIA exemptions.  This would help the reader make a preliminary determination and point he/she in the right direction to obtain additional background information before making an official determination.  You make reference to the guide that contains the FOIA exemptions, but it would be much easier to see it in the present document. 



Subject Matter Expert john.fredlund@nnsa.doe.gov
Section 3 - The concept of discretionary versus mandatory determination invites abuse of the intent of these directives and will be very confusing to the typical employee attempting good faith adherence to these Directives. Given that the responsibility to identify OUO information is assigned in ALL employees, this section needs rework. We suggest that the first requirement would be to apply "OUO identification guidance" that has been provided to them (office-specific guidance will likely be required, since administrative personnel will be the front lines) to identify OUO. The second requirement would be to apply their understanding of the exemptions (I suspect your training course is ready to roll) to identify OUO, asking for guidance when indicated. 

Comment:  Chapter I discusses marking OUO documents, both traditional hard copy and special format documents, but does not address emails that contain OUO information or emails that are unclassified but may have an OUO attachment.  (Major - NA-40/Fairobent)  

]]></Comments>
               <Response>
                  <ResponseLevel><![CDATA[Accepted with Modification]]></ResponseLevel>
                  <ResponseContent><![CDATA[[Response to Rick Phillips] The Order now allows for program/support offices and field elements to develop and issue guidance.  Paragraph 3b is now 3a and has been revised to read as follows:  "Determination Based on Guidance.  If guidance issued under DOE O 471.X identifies certain information as OUO, then an employee must determine that a document containing such information is OUO."

[Response to Michelle Beg] Adding a bulletized description of the eight exemptions here would be a distraction from the criteria to identify OUO information.  Once these directives are issued and everyone becomes familiar with the requirements, I suspect that DOE G 471.X-1 and any guidance issued by program offices/field elements or the Director, ICCP, will be consulted by employees making OUO determinations more often than the Order and Manual.  

[Response to John Fredlund] The order of paragraphs 3a and b has been reversed to emphasize that an employee should consult guidance before making a determination based on his/her evaluation of the information, and the titles of these paragraphs has been changed as follows:  3a - Determination Based on Guidance; 3b - Determination Based on Employee's Evaluation.  The following paragraph has been added under paragraph 4:  "Marking E-mail Messages.  The first line of an e-mail message containing OUO information must contain the abbreviation 'OUO' before the beginning of the text.  If the message itself is not OUO but an attachment contains OUO information, the message must indicate that the attachment is OUO.  The attachment must have all required OUO markings."]]></ResponseContent>
               </Response>
               <Concurrence><![CDATA[Concur/No Comment]]></Concurrence>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters NTEU]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters OA]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters OPI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters PC-1]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters PO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters RW]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters SC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Headquarters SO]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Honeywell FM&T (Kansas City Plant)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Idaho Operations Office]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Karen Moses]]></SourceUsername>
                  <SourceTitle><![CDATA[ID DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Idaho Operations Office]]></SourceSite>
               </Source>
               <Comments><![CDATA[Chapter 1, paragraph 3.- It is not reasonable to expect ALL employees to consistently and correctly determine if a document  contains OUO information, based on a) "FOIA exemptions ..." and b) "reasonably be expected ...".  Training and experience in FOIA, Unclassified Sensitive Information and other aspects of information management are needed to properly mark documents.  Recommend  language be added requiring  all unclassified documents to be released to the public, be reviewed by designated determination authorities. Each DOE office could then designate those individuals with the proper credentials, including CO's, ADC's, FOIA officers, etc..  Documents prepared for "internal" use would be reviewed by those designated as determining authorities, if desired by the preparer, otherwise left unmarked.   If all employees are tasked with determining sensitivity and FOIA exemption, marking the documents and then later removing the designation as they see fit, field units will lose control and the whole process will loss credibility, both internally and with the public. (Comment by D. D. Wagner - DOE-OD OPI and concurred on by R. F. Wilbur, Deputy Manager, Technical Support)]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Idaho Operations Office-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[INL - NE]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[INL-ICP-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Kaiser-Hill Company, LLC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Kansas City Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Lawrence Berkeley Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Lawrence Livermore National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Livermore Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Los Alamos National Laboratory]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Mike Irving]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Los Alamos National Laboratory]]></SourceSite>
               </Source>
               <Comments><![CDATA[
Subject Matter Expert jabrown@lanl.gov
Subparagraph 2.c:  Generally, employees will be (or will feel) unable to make this "damage" judgement.  Fear of incorrect determinations will cause employees to conservatively mark as OUO any document that demonstrably contains information that falls under an exemption, even if no "damage" can be forseen, since this is a subjective judgement.

Subparagraph 3.b.:  Normally, 'guidance Issued by ICCP' is in the form of classification guides, which 1) are possessed and used primarily by Derivative Classifiers, not 'any employee,' and 2) are usually classified, and so may not be available to 'any employee.'  How will employees who are not DCs be informed of the guidance since DCs and Classification Officers have no responsibilities under the draft OUO Order?  Will ICCP issue stand-alone OUO guidance in subject areas where classified classification guides exist?  Who will distribute this guidance and train employees on its use?  Overall, this subparagraph sets up a mandatory process without having assigned to anyone the responsibility to carry it out or oversee it.

Subject Matter Expert jboudreau@lanl.gov
As with paragraph 4.a of the Order, paragraph 2.b of the Manual limits the use of OUO to the 8 FOIA exemptions. There is no provision for marking and protecting 1) unclassified technical information that could be of useful to a proliferant or terrorist; 2) export controlled information; and 3) information held "in confidence" by multi-government groups, such as the Nuclear Suppliers Group. In light of September 11, and the precaution of pulling information off government Web sites, this new restriction seems a step backwards.

]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Los Alamos Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[NA Service Center]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Yolanda Bolivar]]></SourceUsername>
                  <SourceTitle><![CDATA[AL DPC]]></SourceTitle>
                  <SourceSite><![CDATA[NA Service Center]]></SourceSite>
               </Source>
               <Comments><![CDATA[

Subject Matter Expert pmathis@doeal.gov
Paragraph 2.b. should include a short, bullitized description of the eight FOIA exemptions.  This would help the reader make a preliminary determination and point he/she in the right direction to obtain additional background information before making an official determination.  You make reference to the guide that contains the FOIA exemptions, but it would be much easier to see it in the present document. 

]]></Comments>
               <Source>
                  <SourceUsername><![CDATA[Rick Phillips]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[NA Service Center]]></SourceSite>
               </Source>
               <Comments><![CDATA[Comment 1:  Paragraph 3.b.  This paragraph states that only guidance from ICCP may be issued for use in making mandatory determinations.  A paragraph should be added that allows for locally developed OUO guidance to be developed, approved, issued, and used.  (Mike Spence, AL - Approved by Rick Phillips, AL)

Rationale:  Guidance relative to OUO information is best developed locally by a cognizant approval authority most familiar with the local information protection regime.  This is consistent with the past practice of OUO determinations and FOIA exemption witholdings being accomplished at the field office level.]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[National Energy Technology Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[National Renewable Energy Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Nevada Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oak Ridge National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oak Ridge Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Oakland Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Office of Energy Assurance]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Office of River Protection]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Ohio Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[OSTI]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Pacific Northwest National Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Pantex Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Portsmouth Paducah Project Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Princeton Plasma Physics Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Richland Operations Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Rocky Flats Field Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Sandia National Laboratories]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Rebecca Cayen]]></SourceUsername>
                  <SourceTitle><![CDATA[SNL DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Sandia National Laboratories]]></SourceSite>
               </Source>
               <Comments><![CDATA[The following comment was supplied by Ashley McConnell, Dept. 3130 Information & Integration.  It was approved by Al West, Director of Integrated Safety & Security Center 3100.  It meets the criteria of performing efficiently and economically.<P>
3. For mandatory determinations, the information should be automatically exempt from FOIA and not have to go through a review process for the exemption. 

]]></Comments>
               <Source>
                  <SourceUsername><![CDATA[Ashley McConnell]]></SourceUsername>
                  <SourceTitle><![CDATA[Delegate]]></SourceTitle>
                  <SourceSite><![CDATA[Sandia National Laboratories]]></SourceSite>
               </Source>
               <Comments><![CDATA[Category:  Performing efficiently and economically:
For mandatory determinations, the information should be automatically exempt from FOIA and not have to go through a review process for the exemption.
]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Sandia Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Savannah River EM Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Savannah River Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Southeastern Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Southwestern Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Stanford Linear Accelerator Center]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Stanford Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Thomas Jefferson National Accelerator Facility]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[University of California]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Wackenhut Services Inc (SRS)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Wackenhut Services Inc. (Nevada)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[West Valley Demonstration Project]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Western Area Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Westinghouse Savannah River Corp.]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Westinghouse Savannah River Corp. for SR-EM]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[WIPP]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 (BWXT)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 (WSI)]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Y-12 Site Office]]></OrganizationName>
            </Organization>
         </Section>
         <Section>
            <SectionTitle><![CDATA[Chapter I, 4. Marking a Document that Contains Official Use Only Information]]></SectionTitle>
            <SectionContent><![CDATA[
     4.   MARKING A DOCUMENT THAT CONTAINS OFFICIAL USE ONLY
     INFORMATION.

               a.   Front Marking.  The employee making the determination must include both the
          applicable FOIA exemption number and the related category name (found in
          DOE G 471.X-X) on the following marking and ensure that it is placed on the
          front of each document containing OUO information:

                        OFFICIAL USE ONLY
           May be exempt from public release under the
            Freedom of Information Act (5 U.S.C. 552),
exemption number and category:   ____________________

                                 
               Department of Energy review required
                      before public release
                         Name/Org:                 Date:  
                       
                                 








               b.   Page Marking.  The employee making the determination must ensure the words
          "Official Use Only" (or "OUO" if space is limited) are placed on the bottom of
          each page or, if more convenient, on just those pages containing the OUO
          information.

               c.   Marking Special Format Documents.  Special format documents (e.g.,
          photographs, viewgraphs, films, magnetic tapes, floppy diskettes, audiotapes, 
          videotapes, or CD-ROMs) must be marked in a manner consistent with
          paragraphs 4a and 4b above so persons possessing the documents and persons
          with access to the information in or on the documents are aware they contain
          OUO information.  When space is limited, as on the frame of a 35-mm slide, the
          page marking is sufficient.

               d.   Marking Documents Maintained in Restricted Access Files.  Documents that may
          contain OUO information that are maintained in files to which access is restricted
          (e.g., personnel office files) do not need to be reviewed and marked while in these
          files or when retrieved from the files for reference, inventory, or similar purposes
          as long as the documents will be returned to the files and are not accessible by
          individuals who are not authorized access to the OUO information.  However, a
          document removed from these files and not to be returned (or a copy of such
          document) must be reviewed to determine whether it contains OUO information
          and, if appropriate, marked.

               e.   Transmittal Document.  A document that (1) transmits an attachment or enclosure
          marked as containing OUO information and (2) does not itself contain classified
          or controlled information must be marked on its front as follows to call attention
          to the presence of OUO information in the attachments or enclosures:

                       Document transmitted
contains OUO information         



               f.   Removal of Official Use Only Markings.  The removal of OUO markings may be
          authorized by (1) the employee who initally applied the marking, (2) the
          supervisor of the employee who initially applied the marking, (3) any person with
          cognizance over the information, or (4) a FOIA authorizing official who approves
          the release of the document in response to a request made under FOIA.  Whoever
          makes that determination ensures the markings are crossed out or otherwise
          obliterated and places the following marking on the bottom of the front of the
          document:

                         DOES NOT CONTAIN
                  OFFICIAL USE ONLY INFORMATION

                                        Name/Org.:                              Date: 






                                                  g.                            Relationship of Official Use Only Markings to Other Types of Control Markings.

                                                    (1)                         Unclassified Documents.  The OUO front marking must be applied to any
                                        unclassified document that contains OUO information regardless of any
                                        other unclassified control marking (e.g., UCNI).

                                                    (2)                         Classified Documents.  OUO front and page markings must not be applied
                                        to any classified document that also contains OUO information.  However,
                                        if the classified document has been portion marked, the acronym "OUO"
                                        must be used to indicate those portions containing only OUO information.

                                                  h.                            Marking Documents Generated Before the Date of this Manual.  Unclassified
                                        documents generated before the date of this Manual are not required to be
                                        reviewed to determine whether they contain OUO information; however, any such
                                        previously generated document determined to contain OUO information after the
                                        date of this Manual must be marked as indicated in paragraphs 4a through 4d
                                        above.  Such determination may be made by anyone with cognizance over the
                                        information in the document.  In addition, for unclassified documents marked as
                                        containing OUO information before the date of this Manual, the markings are not
                                        required to be updated to conform with the marking requirements in this Manual.

                                                  i.                            Obsolete Markings.  From July 18, 1949, to October 22, 1951, the Atomic Energy
                                        Commission used the term "Official Use Only" as a designation for certain
                                        classified information.  Documents from this time period with an OUO marking
                                        must be handled as Confidential National Security Information pending a
                                        determination of their proper classification.  Refer to DOE M 475.1-1A,
                                        Identifying Classified Information, dated 5-8-98 [National Nuclear Security
                                        Administration (NNSA) certified 2-26-01], for specific procedures.


]]></SectionContent>
            <Organization>
               <OrganizationName><![CDATA[Ames Labortatory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Argonne National Laboratory]]></OrganizationName>
               <Source>
                  <SourceUsername><![CDATA[Don Schmitt]]></SourceUsername>
                  <SourceTitle><![CDATA[ANL DPC]]></SourceTitle>
                  <SourceSite><![CDATA[Argonne National Laboratory]]></SourceSite>
               </Source>
               <Comments><![CDATA[Paragraph 4.a. Requires a marking which states 鈥淒epartment of Energy review required before public release.鈥  

Comment:	This is not a true statement.  While this may be true if the information/document is requested under a Freedom Of Information Act (FOIA) request, it is not true for everything else.  If the marking is placed on a document using the discretionary clause from Paragraph 3 and later determined not to be exempt from the FOIA Act (see Section 4. f.), it would not have to be reviewed by DOE.  
]]></Comments>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Associate Manager for Science & Technology, Richland]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bechtel Hanford]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bechtel Nevada]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Berkeley Site Office]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Bonneville Power Administration]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Brookhaven National  Laboratory]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[BWXT Pantex, LLC]]></OrganizationName>
            </Organization>
            <Organization>
               <OrganizationName><![CDATA[Carlsbad Area Office]]></Organizatio