Draft PWS.pdf

USFFC N1P Fleet Readiness and Manning Support Performance Work Statement (PWS)

1. BACKGROUND

The Fleet Personnel Allocation and Readiness (N1P) section is primarily responsible for driving Fleet manning and policy initiatives. The foundation of Fleet’s manning strategy is Navy strategic guidance. The purpose of Navy strategic guidance is to achieve and maintain a level of readiness that supports the Nation’s requirements for maritime power. This in turn drives manning strategy to fully man combat units from the maintenance phase through sustainment period following deployment. In other words, units will be ready to train and ready to fight. In order to fully man combat units, Fleet manning priorities and levels must be promulgated to generate Fleet personnel readiness to meet a defined operational end state. USFF N1P carries out the duties as a global Fleet Readiness Integrator - Fleet (FRI-F) in conjunction with PACFLT and Navy Personnel Command. Specifically, FRI’s provide input on MyNavy Assignment (MNA) procedures and business rules in addition to requisition prioritization and advertisement for Sailor application in accordance with available inventory. This collaborative effort ensures deliberate distribution of manning to appropriately man units in accordance with established Fleet manning priorities and levels.

Scaling down from the aforementioned, USFF N1P provides personnel manning and readiness oversite as a function of NAVSTRAT N1 (STRATCOM AOR), NAVNORTH N1 (NORTHCOM AOR), and the new CTF-

80 N1 (LANTFLT AOR).

2. SCOPE/OBJECTIVE

The overall objective is to ensure Fleet Leadership and associated manning stakeholders receive complete, accurate and timely analytical based recommendations to support Fleet manning and readiness decisions, which include but are not limited to; resource allocation, risk identification, analysis, and associated mitigation strategy development.

This effort also requires contractor support to evaluate and provide recommendations on the implementation of existing and emerging business practices throughout the Fleet which would help process improvement, enhance analysis efforts and add fidelity to the manning and readiness assessment process. This contract support shall provide the skills/abilities to help with integration, manning readiness focus area development, formulate solutions, and manage meaningful change to ensure transparency of Fleet Manning issues between internal and external activities.

3. TASKS/REQUIREMENT

3.1. Manning Support

3.1.1. The contractor shall assist in processing appropriate manning metrics to ensure deploying ships/squadrons/activities are manned per established Fleet Commander directed threshold levels. (S)

3.1.2. The contractor shall assist in the execution of six bi-monthly MNA requisition cycles, averaging a review of ~30,000 requisitions. As the Fleet Readiness Integrator- Fleet (FRI-F), USFF N1P must provide integrated fleet input to each requisition cycle detailing billet prioritization to meet fleet readiness needs per Manning Control Authority (MCA) established timeline.

3.1.3. The contractor shall assist in analyzing enlisted personnel shortages and excesses quarterly to determine the most efficient use of personnel assets to deliver combat ready forces. The contractor shall provide these analysis results and recommendations monthly to include supporting documents with tables, graphs, and pivot tables as necessary.

3.1.4. The contractor shall assist in distributing Journeyman and Supervisor sustainment reports to BSO’s, TYCOM’s, and Direct Reporting Commands quarterly.

3.1.5. The contractor shall assist with generating the Apprentice Priority billets report, via analysis tools and web-based applications (ie. Tableau and MNA or other approved Government tools/applications as directed). The report is due bi-monthly, the first Wednesday of the MNA cycle.

3.1.6. Contractor shall assist in conducting oversight of enlisted personnel requisitions and assignment functions in the My Navy Assignment (MNA) system, by utilizing established Fleet policies, procedures and priorities regarding directed manning, personnel movements and other issues necessary to achieve personnel readiness manning thresholds in accordance with the current Enlisted Sea and Shore Duty Notice 1000’s.

3.1.7. Contractor shall assist in ensuring BSO’s, TYCOM’s, and Direct Reports attain and sustain all required sea duty and shore manning target levels per the current Enlisted Sea and Shore Duty Notice 1000’s.

3.1.8. Contractor shall process the constant flow of MNA Personnel Manning Action Requests (PMAR’s) for all U.S. Fleet Forces subordinate BSO’s, TYCOM’s, and Direct Reports, ensuring required processes were met in accordance with published directives. USFF receives approximately 30,000 PMAR’s annually. The contractor shall adjudicate and provide recommendations based on current manning policies.

3.1.9. Contractor shall assist with providing input to the government regarding open must fill and open requisitions based on Fleet rollers, BSO’s, TYCOM’s, and Direct Reports’ submissions and established Fleet priorities in accordance with Strategic Guidance.

3.1.10. Contractor shall assist in the development of briefs and/or products required in support of executive/flag level synchronization events. (S)

3.1.11. Contractor shall provide technical briefings, advanced data analytics, decision support documents, conference/meeting reference materials and proceedings documents as part of their day to day duties.

(S)

3.1.12. The contractor shall make recommendations on metric changes, analysis processes and implementation of best practices based on analysis to add fidelity to metrics and enhance the measurement methodology which will result in improved personnel manning awareness, enhanced force generation constructs and leadership readiness decision-making.

3.1.13. The contractor shall support and assist with an increase in Billets Authorized (BA) as required.

3.2. Readiness Support

3.2.1. The contractor shall assist with daily reporting and monitoring manning levels of all Fleet Sea and

Shore activities to ensure units meet Fleet Commander approved manning thresholds for all designated deployers, priority manning units, Forward Deployed Navy Forces, and Optimized Fleet Response Plan Units. (S)

3.2.2. The contractor shall assist as required with providing unit manning analysis reports to BSO’s, TYCOM’s, and Direct Reporting commands based on established Fleet Readiness guidelines/reporting criteria to include weekly and monthly tracking reports. Contractor shall also provide support to identify current/projected readiness shortfalls and implement corrective actions to resolve shortfalls. (S)

3.2.3. The contractor shall assist in maintaining awareness of Fleet manning issues through analysis and assessment based on established USFFC/CPF enlisted sea duty manning thresholds to include weekly and/or monthly (as required) tracking reports of Rating Control Number (RCN), Navy Enlisted Classification (NEC), Critical Navy Enlisted Classification (CNEC) manning levels and trends.

3.2.4. The contractor shall assist in identifying potential solutions for manning issues daily and/or as required, evaluate the impact of both external and internal factors, and review processes to develop actionable alternatives designed to achieve resolution of manning issues to support Fleet readiness.

This information will be reported via established readiness Fleet reports and disseminated as directed to USFF N1/N1P USFF, TYCOMs and various stakeholders.

3.2.5. The contractor shall assist with utilizing analysis tools and web-based applications to monitor assess and report historical, current and projected Fleet personnel readiness of Forward Deployed units, deployed units, and units deploying within 6 months. This information will be reported via established readiness Fleet reports and disseminated as directed to USFF Commander, TYCOMs and various stakeholders for decision making on unit operational readiness and mission capability.

3.2.6. The contractor shall utilize analysis tools and web-based applications to examine historical, current, and projected RCN Fill and Fit and CNEC Fit levels as well as Rating/NEC shortfalls.

3.2.7. The contractor shall assist with special projects to include submission of detailed analysis and assessment reports by collecting and extracting manning and personnel readiness data from various resources. (S)

3.2.8. Contractor shall provide technical briefings, advanced data analytics, decision support documents, conference/meeting reference materials and proceedings documents as part of their day to day duties.

3.2.9. The contractor shall assist with Fleet deployment status reports (DSTAT) for all CONUS and

OCONUS sea duty units utilizing web-based applications, applicable reports and collaboration with Force Commanders. (S)

3.2.10. The contractor shall assist with the MyNavy Assignment (MNA) priority tracker for establishment of unit readiness cycle target manning dates (M-dates) and associated MNA priority cycle timeframes in accordance with the current Enlisted Sea and Shore Duty Notice 1000’s. (S)

3.2.11. The contractor shall assist with generating and briefing the MNA priority list for each MNA priority cycle and assist with updates of unit deployment status dates (DSTAT) in the MNA system.

3.2.12. The contractor shall assist in conducting research and generating recommendations necessary in the development and review of personnel readiness policy and metrics (e.g. Aviation Maintainer Experience (AMEX), Surface Manning Experience (SURFMEX), Defining First Term Sailors roles, etc.).

4. PERSONNEL

TECHNICAL QUALIFICATIONS: To successfully perform on this requirement, contractor support shall have knowledge/understanding of the Navy missions, project management, readiness assessment, manpower resourcing, training and comprehensive understanding of manning distribution system processes/methodologies in order to assist USFF N1 staff with complex Fleet Manning challenges.

4.1. Manning Support Specialist

4.1.1. General Experience Requirements: Contractor personnel supporting this effort shall have a working knowledge and general experience in the following areas as defined in section 3 of the

PWS:

4.1.1.1. Navy manning priorities and policies

4.1.1.2. Analysis tools and web based applications that track manning such as Tableau, COGNOS, or

MyNavyAssignment (MNA)

4.1.1.3. General Program Support

4.1.1.4. Communicating in various formats to include the use of software programs such as Microsoft

PowerPoint, Excel, Word and Publisher.

4.1.2. Education Requirements: A high school degree or equivalent is required if contractor has at least 4 years’ experience with Navy manning priorities and policies. A Bachelor’s degree is required if contractor has at least 2 years’ experience with Navy Manning priorities and policies. Contractor personnel supporting this effort shall have experience as outlined in general experience requirements.

4.2. Readiness Support Specialist

4.2.1. General Experience Requirements: Contractor personnel supporting this effort shall have a working knowledge and general experience in the following areas as defined in section 3 of the

PWS:

4.2.1.1. Navy Readiness data and policies

4.2.1.2. Analysis tools and web based applications that track manning such as Tableau, COGNOS, or

MyNavyAssignment (MNA)

4.2.1.3. General Program Support

4.2.1.4. Communicating in various formats to include the use of software programs such as Microsoft

PowerPoint, Excel, Word and Publisher.

4.2.2. Education Requirements: A high school degree or equivalent is required if contractor has at least 4 years’ experience with Navy manning priorities and policies. A Bachelor’s degree is required if contractor has at least 2 years’ experience with Navy Manning priorities and policies. Contractor personnel supporting this effort shall have experience as outlined in general experience requirements.

5. PLACE OF PERFORMANCE: The work described above shall principally be performed on-site at

Commander, U.S. Fleet Forces Command, 7918 Blandy Rd, Norfolk, VA 23551, BLDG NH-140, Naval Support Activity (NSA) Hampton Roads. Telework as approved by the Contracting Officer Representative.

6. PERIOD OF PERFORMANCE: The period of performance for this requirement is as follows:

Performance Period Period of Performance Base Year 01 September 2024 to 31 August 2025 Option Year 1 01 September 2025 to 31 August 2026 Option Year 2 01 September 2026 to 31 August 2027 FAR clause 52.217-8 01 September 2027 to 28 February 2028

7. COMMON ACCESS CARD (CAC): The Contractor employee(s), fulfilling this contract must obtain a

DoD CAC. The CAC is a multi-functional “smart” card. It is the official DoD identification card for military, civil service and Contractor personnel. It is also the DoD Geneva Convention for all military, civil service and Contractors accompanying military personnel in hostile areas. It is used to grant access to DoD installations and some buildings. It is also used to access DoD networks and secure websites. The COR will connect the contractor personnel with the Trusted Agent (TA). The employee will submit an application to the TA, who will review the application, verify, reject and/or approve. If rejected, the system notifies the Contractor and records the rejection. If approved, the system will update Defense Enrollment Eligibility Reporting System (DEERS) with the Contractor information and direct the Contractor, by e-mail to proceed to a military facility/installation that has a Real-time Automated Personnel Identification System (RAPIDS) workstation for CAC issuance.

Contractor personnel shall be required to wear a Contractor identification badge and government supplied badge and/or CAC at all times while on Government property. The Contractor shall take appropriate precautions to prevent security violations, ensure possible compromises are reported in a timely manner, and promote a high level of security awareness among personnel assigned to the contract.

The primary place of performance shall be on-site/off-site at the locations listed, which dictates that all personnel performing on-site must possess U.S. Citizenship and an active DoD clearance at the Secret Level and may be subject to a Government Security Investigations and must meet eligibility for access to classified information. The positions require the proposed personnel to be trained and certified to DoD requirements in order to perform the duties.

The contractor shall abide by established processes and procedures for the issuance and collection of government furnished Common Access Cards (CACs) for all contractor personnel when there is a hire, resignation or termination. All CACs contain personal identifiable information (PII) that shall be controlled in accordance with government directives. Upon termination or resignation all CACs are to be turned in immediately to the contractor's respective government appointed Technical Assistant reporting to the COR.

The cards shall then be returned to any RAPIDS issuance location for proper disposal.

Any unauthorized possession of an official identification card, (i.e. CAC) can be prosecuted criminally under section 701 of title 18, United States Code (U.S.C) which prohibits photographing or otherwise reproducing or possessing DoD identification cards in an unauthorized manner, under penalty of fine, imprisonment or both. The Contractor shall have procedures in place to ensure the retrieval and return of the government furnished equipment (CACs) from contractor personnel who are no longer supporting the contract.

The CAC is the property of the U.S. Government and shall not be retained by the cardholder upon expiration, replacement or when the DoD affiliation of the contracted personnel has been terminated.

8. SECURITY REQUIREMENTS: Personnel should be eligible for a Secret clearance. Any personnel proposed to work on this effort shall be eligible for necessary clearances to immediately begin performance at the time of order award. See Department of Defense (DOD) Contract Security Classification Specification - DD Form 254 provided with individual task orders for more information. Contractors will need access to the following:

8.1 SIPR email account to access/review and work with classified material:

8.1.1 SIPR email account

8.1.2 Classified briefings, emails, and documents associated with unit deployment schedules and

CSGs/ARGs compositions

8.1.3 Deployment Schedule (DepSked) website to review unit deployment schedules and alignments to CSGs/ARGs (Classified)

8.1.4 Defense Readiness Reporting System – Strategic (DRRS-S) (Classified)

8.1.5 Navy Readiness Reporting Enterprise System (NRRE) (Classified)

8.1.6 Fleet Forces Portal (classified)

8.1.7 MyNavy Assignment (Secret Clearance Required)

9. DELIVERABLES: Deliverables shall be submitted in hard copy and/or fully editable soft copy (in the applicable Microsoft Word/Excel/PowerPoint/Publisher format). Deliverables are subject to review and, if warranted, may be returned to the contractor for revision due to content inaccuracies and/or clerical errors.

9.1 Monthly Progress and Status Report (MPSR)

9.1.1 The Contractor will provide a monthly progress, status and management report consistent with the invoice period by the 5th business day of each month to the COR. At a minimum the reports shall include the following information:

9.1.2 Activities of the past month. A summary of the action taken and progress made on outstanding tasks for the past month, including travel, problems, issues and technical assistance log (as applicable) etc.

9.1.3 Routine teleconference/meeting/ conference attendance.

9.1.3.1 Do not report on routine teleconferences, meetings and conferences in support of daily requirements/tasks.

9.1.3.2 Provide report in conjunction with roadmap/way ahead to address specific problem/issues.

9.1.4 Activities of the next month. A review of the work planned for the next month to meet task requirements, including projected travel, anticipated risk and/or issues.

9.2 Six Bi-Monthly MyNavyAssignment (MNA) Requisition Cycles

9.2.1 The contractor will provide completed MNA worksheets bi-monthly in accordance with MNA process guidelines.

9.3 Weekly and Monthly Reports in accordance with Section 3

9.3.1 Monthly OFRP Stoplight Slides and OFRP Unit Report/DSTAT list.

9.3.2 N1 Bi-Weekly Report.

9.3.3 Weekly Fit/Fill Data Request for UTA and CTF 80 Briefs.

9.3.4 Consolidate and disseminate Navy Decommissioning Report monthly.

10 MANDATORY CONTRACTOR TRAINING

The Contractor is responsible for its employees (and subcontractors) supporting this contract completing and staying up to date on all training required by USFF and supported activities for individuals working on Government installations. Some examples of required training and their requisite course numbers/references are listed below. The required training is subject to change throughout the life of this contract; however, the Contractor should assume at least a total of ten (10) hours for all required training courses annually per Contractor/Subcontract employee. The Contractor shall provide documentation (copies of training certificates) to the COR confirming that Contractor employees have completed the required training within five (5) days of the specific training due date.

Program Course Reference DoD Cyber Awareness Challenge

DOD-IAA-V19.0 SECNAVINST 5239.3B, para. 7(a)(4)

Derivative Classification Training (as required)

TWMS-576351 USFFC directed.

Annual Privacy Act / PII DOD-PII-V2.0

TWMS-674495

SECNAVINST 5211.5E, para. 18(d)(2)

Antiterrorism Level 1 Awareness

CENSECFOR-AT-010.2.0 DoDI 2000.16, para. E3.25.1.5 supported by E2.11; E3.18.6

*Operational Security NIOC-USOPSEC-2.0 OPNAVIST 3432.1A, para. 3 & para.

4c(3) and COMUSFLTFORCOMINST 3432.1, para. 8a(7)

Records Management DOR-RM-010-1.2

TWMS-594928

OPNAVINST 5210.20, para. 25c

NCIS Counterintelligence and Insider Threat Awareness

NCIS Face-to-Face

DON-CIAR-1.0

SECNAVINST M-5510.30, chapter 4;

employee (to include contractor) is defined in Appendix A

Annual Security Refresher Local Brief/Seminar SECNAVINST M-5510.30, chapter 4 & para. 102; employee (to include contractor) is defined in Appendix A

Active Shooter DON-687121-1.0 NEL

TWMS-567015CNIC-TRTAS-1.1

USFFC directed.

Active Shooter Table Top Exercise - Face to Face

ASPE-1.0 USFFC directed

11 RECOGNIZED FEDERAL HOLIDAYS

Below are the traditional Federal holidays in which Government facilities will be closed. With the exception of responsibilities, such as 24-hour operations to support training events/exercises and real world events, where prior approval has been granted by the COR to perform on-site at the Government installation, Contractor shall follow their corporate policy for work on recognized Federal holidays where on-site performance cannot be conducted:

New Year’s Day Labor Day

Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Juneteenth Christmas Day Independence Day

12 OPERATIONS SECURITY (OPSEC)

12.1 Operations Security

Background, OPSEC is a process used to protect unclassified sensitive Information from exploitation by an adversary. Sensitive unclassified information—which is also referred to as critical information or critical program information (CPI)—is defined as information that is not classified but which needs to be protected from unauthorized disclosure. Examples are information labeled “For Official Use Only (FOUO),” proprietary information, contractor sensitive information, limited distribution information, and personally identifiable information (PII).

12.1.1 The contractor and all subcontractors shall provide OPSEC protection for sensitive unclassified information as identified in the critical information list and CPI list, if applicable. The prime contractor and all subcontractors shall employ the countermeasures listed below in order to protect that information. Additional countermeasures may be employed as necessary. If an OPSEC Plan is provided, the contractor and all subcontractors shall comply with that plan. These OPSEC requirements will be in effect throughout the life of the procurement from award through the conclusion of services at the end of the period of performance (PoP) or other procurement termination. If required, the contractor and all subcontractors shall prepare an OPSEC Plan.

12.1.2 Contractor personnel shall follow OPSEC concepts and principles in the conduct of this requirement to protect critical information, personnel, facilities, equipment, and operations from compromise. The contractor shall consult with the subject matter expert (SME) within 5 working days of receipt of order to determine all special circumstances affecting OPSEC under this requirement. In any case where there is uncertainty or ambiguity regarding OPSEC measures, the contractor shall consult the SME as soon as possible. If the SME is unavailable, the contractor shall consult the contracting officer. The prime contractor and all subcontractors shall provide OPSEC protection for sensitive unclassified information and comply with all OPSEC requirements.

12.1.3 Minimum Protection Requirements for Critical Information Critical information is exempt from public release under Exemption 2 of the Freedom of Information Act (FOIA). It is designated “For Official Use Only (FOUO)” and is considered controlled unclassified information (CUI). Specific CPI, for reasons of OPSEC will not be identified to offerors prior to award. CPI will be identified to the successful offer or only after receipt of contract award.

12.2 Personally Identifiable Information (PII).

12.2.1 PII shall be protected in accordance with DOD and Navy directives, in such a manner as to prevent unauthorized disclosure. Email containing PII must be encrypted or password protected.

12.3 Controlled Unclassified Information (CUI).

12.3.1 CUI is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release, to include technical information, proprietary data, information requiring protection under the Privacy Act of 1974, and Government-developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order(s), but is pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government, and under law or policy requires protection from unauthorized disclosure, special handling safeguards, or prescribed limits on exchange or dissemination.

12.3.2 Minimum Requirements for Access to CUI.

12.3.2.1 Prior to access, contractor personnel requiring access to DON CUI or “user level access to DON or DOD networks and information systems, system security and network defense systems, or to system resources providing visual access and/or ability to input, delete or otherwise manipulate sensitive information without controls to identify and deny sensitive information” who do not have clearance eligibility are required to submit a Questionnaire for Public Trust Positions (Standard Form 85P) through the cognizant Facility Security Officer or contractor entity representative for a suitability determination by DON Central Adjudication Facility.

12.3.3 Minimum Protection Requirements for CUI.

12.3.3.1 Contract deliverables taking the form of unclassified limited-distribution documents

(FOUO), are not authorized for public release and therefore shall not be posted on a publicly accessible Web server, nor electronically transmitted via electronic mail unless appropriately encrypted or password protected.

12.4 Countermeasures

Countermeasures are required to negate the susceptibility of critical information to exploitation by an adversary or competitor. The contractor shall protect all critical information listed in a manner appropriate to the nature of the information, including use of the necessary countermeasures as listed below applicable to specific items:

12.4.1 Encryption with a password of electronically stored critical information.

12.4.2 Encryption or password protection of e-mail containing critical information.

12.4.3 Storage of hard copy critical information, optical media, and external hard drives in locked containers when not in use.

12.4.4 Transmission of critical information to the minimum set of recipients with a need to know.

12.4.5 Proper marking of critical information with warnings to include at a minimum “FOR

OFFICIAL USE ONLY”; as appropriate to the nature of the critical information it shall also be marked with “UNCLASSIFIED BUT SENSITIVE,” “PRIVACY ACT INFORMATION,”

“PERSONALLY IDENTIFYING INFORMATION,” “PROTECT FROM

UNAUTHORIZED DISCLOSURE,” or other similar statements cautioning protection of the critical information.

12.4.6 Restricting disclosure of critical information at meetings and conferences (including teleconferences) to the minimum necessary to the performance of this requirement.

12.4.7 Immediate and appropriate destruction in a manner precluding reconstruction of all critical information no longer needed under this requirement.

12.4.8 Restricting verbal discussion of critical information to venues and circumstances that prevent the monitoring and interception of the discussion by unauthorized personnel.

12.4.9 Maintaining current, successful completion of Navy-mandated information assurance (IA) and OPSEC training by all personnel handling critical information.

12.4.10 Refraining from the use of unencrypted telephones to transmit critical information.

12.4.11 Refraining from the use of foreign postal systems to ship critical information.

12.4.12 Promptly retrieving documents containing critical information printed on printers accessible by persons without a need to know the critical information.

12.4.13 Use of cover pages or other appropriate means to prevent the viewing of critical information by unauthorized persons.

12.4.14 Limiting the inclusion of critical information in contract and budget documents, presentations, press releases, and other publications to that which is essential to the performance of this requirement.

12.4.15 Use of protected databases and strong passwords and the protection of user identifications (User IDs).

12.4.16 During test and evaluation events (as applicable to this requirement) practice OPSEC methodologies with respect to staging units, personnel, and materials out of the observation of unauthorized persons; desensitization; and the speed of execution of the event.

12.5 Compromise.

12.5.1 The contractor shall notify the SME, FSO, and security office immediately of all known and suspected compromises of critical information, classified information, or PII. If the SME cannot be reached, the contractor shall notify the contracting officer (or the command duty officer if after normal work hours).

12.6 FOUO.

12.6.1 The FOUO marking is assigned to information at the time of its creation. It is not authorized as a substitute for a security classification marking but is used on official Government information that may be withheld from the public under exemptions 2 through 9 of the Freedom of Information Act (FOIA). Use of FOUO markings does not mean that the information can’t be released to the public, only that it must be reviewed by the Government prior to its release to determine whether a significant and legitimate government purpose is served by withholding the information or portions of it.

12.6.2 All UNCLASSIFIED documents created under this contract that contain FOUO information will be marked “FOR OFFICIAL USE ONLY” on the bottom of the cover page and interior pages.

12.6.3 Classified documents containing FOUO do not require any markings on the cover of the document. However, the interior pages containing only FOUO information shall be marked at the top and bottom center with “FOR OFFICIAL USE ONLY.” Only unclassified portions containing FOUO shall be marked with “(FOUO)” immediately before each unclassified FOUO portion.

12.6.4 All FOUO information released to the contractor will be marked with the following statement prior to transfer: THIS DOCUMENT CONTAINS INFORMATION EXEMPT FROM

MANDATORY DISCLOSURE UNDER THE FOIA. EXEMPTIONS(S) ______ APPLY.

12.6.5 Removal of the FOUO marking may be accomplished only by the originator or other competent authority. The contractor shall not remove any FOUO marking without written authorization from corona or the author. The Government will notify the contractor when the FOUO status is terminated.

12.6.6 The contractor is authorized to disseminate FOUO information to its employees and those having a need to know the information in order to accomplish the requirements of the contract.

12.6.7 When in use, reasonable steps shall be taken to minimize the risk of access to FOUO information by unauthorized personnel. FOUO information shall be placed in an out-of-sight location if the work area is accessible to persons who do not have a need to know the information in order to perform contract requirements. When not in use, the FOUO information shall be stored in a locked desk, file cabinet, bookcase, rooms, or other lockable container or space affording reasonable protection from unauthorized disclosure.

12.6.8 FOUO information may be delivered via U.S. Postal Service first-class mail, parcel post, and fourth-class mail for bulk shipments only. The contractor shall not permit FOUO information to enter foreign postal systems and parcel delivery systems.

12.6.9 When no longer needed, FOUO information shall either be returned to appropriate Government custody or destroyed in a manner precluding reconstruction of the information.

12.6.10 Electronic transmission of FOUO information (via voice, data, or facsimile transmission) shall be by approved secure communications systems or if transmitted over non-secure means, encryption or password protected documents must be used. If circumstances preclude the use of such a system, the contractor shall consult the SME; if the SME is not available and time requirements do not permit delay, the contractor shall consult the contracting officer.

12.6.11 Access Briefings. FSO will provide any necessary access briefings required for contract performance (NATO, etc.).

12.6.12 Classified information performance will occur only at locations specified in the DD254.