Draft Statement of Work.pdf

DRAFT STATEMENT OF WORK

(1) Background

The U.S. Department of Homeland Security (DHS) is committed to using cutting-edge technologies and scientific talent in its quest to make America safer. The DHS Science and Technology Directorate (S&T) is tasked with researching and organizing the scientific, engineering, and technological resources of the United States and leveraging these existing resources into technological tools to help protect the homeland.

S&T focuses its efforts on interoperable communications issues for the local, state, tribal, and Federal practitioner community. As authorized by Sections 314(a) and 315 of the Homeland Security Act of 2002 (codified at 6 U.S.C. § 195(a) and 6 U.S.C. § 195a), S&T is responsible for establishing a comprehensive research, development, testing, and evaluation program for improving interoperable emergency communications. Among its responsibilities, S&T is authorized to identify interoperable communications requirements, support and promote the ability of emergency responders to communicate; conduct pilot projects to test and demonstrate technologies; and establishment of national voluntary consensus standards for interoperable emergency communications.

Project 25 (P25) is a suite of standards that enables interoperability among digital two-way land mobile radio communications products created for use by public safety professionals.

The U.S. Department of Homeland Security Science and Technology Directorate (S&T) partnered with the Department of Commerce Public Safety Communications Research program to establish the P25 Compliance Assessment Program (P25 CAP).

P25 CAP is a formal, independent process for ensuring communications equipment declared by the supplier actually is P25 compliant and tested against the standards with publicly published results. Through these open standards testing process, P25 CAP provides responders confidence the communications equipment they use will be interoperable, regardless of manufacturer. Specifically, this voluntary program provides public safety agencies with evidence that the communications equipment they purchase is tested against and complies with the P25 standards for performance, conformance and interoperability.

Compliance testing concludes with official summary test reports and suppliers’ declaration of compliance, which are available to first responders at https://www.dhs.gov/science-and-technology/p25-cap. DHS components, Customs and Border Protection (CBP), Immigration and Customs Enforcement Homeland Security Investigations (ICE HSI), United States Secret Service (USSS), and the United State Coast Guard (USCG) all use P25 land mobile radios that are critical to performing their missions, including border security, immigration enforcement, law enforcement, and public safety. Furthermore, the DHS Security Classification Guide requires radios by the Department to be P25 compliant.

With introduction of 700 MHz spectrum, the National Coordination Committee (NCC), an Advisory Committee within the FCC made up of public safety and industry participants formed under the Federal Advisory Committee Act (FACA), acknowledged that the https://www.dhs.gov/science-and-technology/p25-cap https://www.dhs.gov/science-and-technology/p25-cap planning process for 800 MHz regional Planning had been inhibited due to the lack of a central repository. Part of the NCC’s recommendation was the establishment of a nationwide Computer Assisted Pre-Coordination Resource & Database (CAPRAD) database that all 700 MHz regions could utilize as a pre-planning and pre-coordination tool for 700 MHz frequency band.

(2) Objectives

The focus of this effort is multifaceted. First, the contractor shall provide technical support for the P25 CAP for DHS including review and development of Compliance Assessment Bulletins as well as evaluation of submitted test documentation. The contractor shall work with DHS to promote P25 CAP across various stakeholder engagement activities including the Telecommunications Industry Association (TIA), Project 25 Technology Industry Group, the Federal Partnership for Interoperable Communications (FPIC), and similar groups. Second, the contractor shall provide support services for Regional Planning Committees (RPCs) and the National Regional Planning Council (NRPC), and continue to maintain and support two public safety communication sites; Computer Assisted Pre-Coordination Resource and Database (CAPRAD) System which aids in the management of the public safety radio frequency spectrum, and a site supporting the NRPC which is a network of radio frequency public safety Regional Planning Committees established by the Federal Communications Commission. Finally, the contractor shall engage with DHS Component end users as well as state and local public safety to better understand interoperability challenges across public safety communications systems including broadband and Next- Generation 9-1-1 (NG911).

(3) Scope

This Statement of Work (SOW) describes activities to be performed by the contractor on public safety communications technologies including projects to develop and document testing frameworks, supporting critical stakeholder groups/resources, continue an existing gap analysis effort of communications systems and provide recommendations to improve interoperability. The contractor’s efforts shall result in analytical reports, presentations, and memos to DHS on the research performed and results obtained. The contractor’s efforts may also include observation and summaries of events where experts gather to develop new specifications or standards and participation in DHS-sponsored meetings or events.

For the period of performance (“PoP”) set forth in this SOW, the contractor shall perform research in support of DHS OIC’s mission in the areas of communications interoperability for public safety communications networks. The contractor shall perform the following tasks, each of which is more fully described below under Tasks 1-3.

Task 1: Support for P25 CAP

The P25 CAP task consists of nine main elements:

(1) P25 CAP Advanced Engineering

(2) P25 CAP Standards Acceleration

(3) P25 CAP Customer Support including User Needs working groups

(4) P25 CAP Document & Web site Upkeep

(5) Support Governance and P25 CAP Stakeholder Efforts

(6) P25 CAP – Outreach and Education Support

(7) P25 CAP lab accreditation, coordination, P25 CAP testing and support

(8) P25 CAP Test report reviews and analysis

(9) P25 CAP Team Program Management.

Many of the activities in this task require deep and intricate knowledge of Project 25 standards, protocols, systems and products. The contractor shall work closely with DHS to coordinate the review and approval of all submitted Summary Test Report (STR)s and Supplier’s Declaration of Compliance (SDOC)s. The contractor shall develop and maintain primary authorship of new Compliance Assessment Bulletins (CABs) as well as update existing CABs based on the needs of the program. The contractor shall maintain existing conformance test case documents. In addition to assisting DHS with questions or comments related to P25 CAP, the contractor shall also engage regularly with P25 radio manufacturers to address issues with respect to submitted STRs and SDOCs. The contractor shall actively participant in DHS’ quarterly P25 CAP stakeholder webinars. Activities may include preparation of presentation slides and facilitating portions of stakeholder meeting discussion. The contractor shall maintain awareness of evolutions in the P25 TIA-102 Standards and industry innovation to update, revise and maintain the suite of published documents needed to sustain the program. This includes deep expertise in the P25 standards development process and the ability to analyze and propose updates to DHS to accelerate changes to standards to address user challenges. The contractor shall establish a systematic naming convention methodology, rigid style terminology, and content guidelines for P25 CAP documents.

To improve communications and outreach with P25 CAP stakeholder, the contractor shall participate with stakeholder group meetings such as P25 Compliance Assessment Program Task Force (CAPTF), PTIG, P25 Steering Committee and subcommittee sessions, FPIC, and similar groups. The contractor shall collaborate with other federal partners, including DHS CISA. Due to the nature of the work, the contractor must remain independent and free from conflicts of interest with specific P25 manufacturers participating in the P25 CAP. As technical experts in P25 CAP, DHS may also request the contractor to also participate (in person or virtually) in major trade shows critical to P25 CAP outreach efforts such as the International Wireless Communications Exposition or the Annual Conference of the Association of Public Safety Communications Officials. The contractor shall maintain Scope of Accreditation documentation for each of the DHS recognized laboratories. The contractor shall support the growth of DHS recognized laboratories, through engagement activities with interested laboratory stakeholders seeking to go through the accreditation process.

Finally, in order to meet the multitude of tasks required as part of this effort, the contractor shall institute program management improvements (e.g., task tracker maintenance, program dashboards, metrics-based reporting).

Task 2: Support for CAPRAD

The CAPRAD task consists of six main elements:

(1) The CAPRAD application module

(2) The CAPRAD App enhancement

(3) The CAPRAD planning module

(4) Regional Planning Committee (RPC) & National Regional Planning Council

(NRPC) support

(5) Ongoing Technical Assistance

(6) Ongoing Expert Assistance for RPCs and the Public.

The contractor shall update the CAPRAD application module by adding and maintaining 700 MHz channel allotments. The improved CAPRAD search shall pull in these allotments so that each region can properly protect past and future allotments and properly protect adjacent regions allotments. The contractor shall lead software application updates, maintenance and technical support for both the CAPRAD planning and application module accessible via CAPRAD.org website. The contractor shall provide support to RPCs and NRPC by conducting monthly calls for NRPC executive office (i.e., district directors) and the fifty-five 700 and 800 MHz RPCs all regions call.

The contractor shall work with NRPC to plan and develop an annual in-person (or virtual) CAPRAD technical seminar in conjunction with APCO annual conference.

The contractor shall conduct an annual technical seminar for disseminating technical information about CAPRAD and improving professional practices. The contractor shall also support any training required to CAPRAD users whether virtually or in person.

Finally, the contractor shall provide technical assistance on spectrum management standards, interference management, and interpretation of FCC rules as applied to 700 and 800 MHz interoperability and general use channels.

Task 3: Support for Public Safety Interoperability

Provide subject matter expertise to DHS in matters of Interoperability and Compatibility of communications systems that impact public safety communications. The contractor shall maintain domain awareness of standards development organization (e.g., TIA, Alliance for Telecommunications Industry Solutions) activities as it pertains to public safety communications. The contractor shall analyze standards development activities and identify gaps in standards that inhibit interoperability for public safety. The contractor shall engage with public safety end users to obtain communications requirements and better understand gaps in standards to inform future standards related activities. The contractor shall engage with P25 equipment manufacturers to better understand the standards-related challenges that may result in interoperability issues. The contractor shall provide its analysis along with recommendations in reports to DHS. Further, the contractor shall provide technical support and subject matter expertise in assessing related research, development, test and evaluation of DHS demonstrations/pilots in the wireless communications domain. The contractor shall provide feedback to DHS on items such as test plans, use cases, and data collection reports.

The contractor may support interoperability and compatibility efforts for DHS across the network, transport, and application layers. The contractor shall support technology areas including but not limited to, Land Mobile Radio (LMR)/Long Term Evolution (LTE) interworking, Mission Critical Push to Talk (MC PTT) on broadband interoperability, Computer Aided Dispatch (CAD) to CAD interoperability, and NG911.

(4) Period of Performance

The period of performance for this Contract is from the date of award through twelve (12) months with four (4) twelve (12) month option periods.

(5) Place of Performance

The Contractor shall execute most work under this contract at their facility.

(6) Key Milestones and Deliverables

Key milestones are detailed in the milestone deliverables in Table 1

Task/Subtask Number and Name

Milestones/Deliverables Due Date or Completion Date

1.0 P25 CAP Support

Kickoff Meeting Due within 30 days from effective date of the contract

P25 CAP Support Develop Project Management Plan and associated documents to include: a description of scope and execution; schedule of key deliverables and milestones;

project risks and a plan for potential mitigation techniques.

Due 30 days from effective date of the contract

P25 CAP Support Hold monthly meetings and regular communication with DHS OIC Task Manager by telephone or in conjunction with project team meetings (at minimum, teleconference with

Due on a recurring monthly basis from effective date of the contract assigned DHS OIC personnel approximately every month or as needed).

P25 Standards Support Participate in the TIA/TR-8, PTIG, ATIS/TIA, Joint

SAFECOM/ NCSWIC P25

Public Safety User Needs Working Group meetings as directed.

Due on a recurring basis throughout PoP of contract

P25 CAP Support Review submitted STR and SDOCs from manufacturers for accuracy and provide recommendation on acceptance to DHS OIC Task Manager

Due on a recurring basis throughout PoP of contract

P25 CAP Support Support responses to inquiries received through P25CAP@hq.dhs.gov

Due on a recurring basis throughout PoP of contract

P25 CAP Support Revise Testing Requirements Documents as needed

Due on a recurring basis throughout PoP of contract

P25 CAP Support Support development of discussion topics and slide presentations for quarterly P25 CAP meetings

Due on a quarterly basis throughout PoP of contract

P25 CAP Support Conduct a robust review of all P25 CAP documents published on the web site for accuracy and develop redesign recommendations for an improved user experience

Due 12 months after execution of contract

P25 CAP Support Attend other relevant P25 stakeholder meetings to include: TIA/TR-8, PTIG, ATIS/TIA, Joint SAFECOM/ NCSWIC P25 Public Safety User Needs Working Group, and provide briefing to DHS OIC Task Manager

Due on a recurring basis throughout PoP of contract

P25 CAP Support Draft Standards related proposals to improve

Due on a recurring basis throughout PoP of interoperability for DHS Consideration

2.0 CAPRAD Support Kickoff Meeting Due within 30 days from

effective date of the contract

CAPRAD Support Develop Project Management Plan and associated documents to include: a description of scope and execution; schedule of key deliverables and milestones;

project risks and a plan for potential mitigation techniques.

Due 30 days from effective date of the contract

CAPRAD Support Hold monthly meetings and regular communication with DHS OIC Task Manager by telephone or in conjunction with project team meetings (at minimum, teleconference with assigned DHS OIC personnel approximately every month or as needed).

Due on a recurring monthly basis from effective date of the contract

CAPRAD Support Conduct technical webinars on a regular basis to disseminate technical updates about

CAPRAD

Due on a recurring basis from effective date of contract

CAPRAD Support Conduct an annual in-person CAPRAD technical seminar

Due within 6 months after execution of contract

CAPRAD Support Conduct a NRPC District Director planning meeting remotely

Due on a recurring basis from effective date of the contract

CAPRAD Support Provide CAPRAD support services via email/phone to RPCs

Due on a recurring basis from effective date of the contract

CAPRAD Support Monthly calls for NRPC executive officers

Due on a recurring basis from effective date of the

CAPRAD Support Monthly call for all regions Due on a recurring basis from effective date of the contract

CAPRAD Support Maintain content on the NRPC website (www.nrpc.us); update data as directed by the NRPC and ensure accuracy of information

Due on a recurring basis from effective date of the contract

CAPRAD Support Manage CAPRAD service provider including maintenance issues and user support

Due on a recurring basis from effective date of the contract

CAPRAD Support Provide technical assistance on spectrum management standards and interpretation of FCC rules as applied to 700 and 800 MHz interoperability and general use channels

Due on a recurring basis from effective date of contract

3.0 Interoperability and

Compatibility

Maintain domain awareness of standards activities

Due on a recurring basis from effective date of contract

Interoperability and Compatibility

Assist in researching and document gaps in standards that inhibit interoperability and compatibility

Due on a recurring basis every 6 months from effective date of contract

Interoperability and Compatibility

Through DHS-supported demonstrations/pilots assist in review of test documents

Due on a recurring basis from effective date of

V. Project Timeline

Table 2 lists a tasking timeline for this effort.

Table 2

Base Year 1 2 3 4 5 6 7 8 9 10

1.0 P25 CAP Support

Kickoff Meeting

X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Review submitted STR and SDOCs X X X X X X X X X X X X

Support responses to inquiries received through P25CAP@hq.dhs.gov X X X X X X X X X X X X Revise Testing Requirements Documents as needed X X X X X X X X X X X X Support development of discussion topics and slide presentations for quarterly P25 CAP meetings

X X X X

Review all P25 CAP documents published on the web site and develop redesign recommendations X Attend other P25 stakeholder meetings and provide briefing

X X X X X X X X X X X X

Draft Standards proposals for interoperability as needed

X X X X X X X X X X X X

2.0 CAPRAD Support

Kickoff Meeting X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Conduct technical webinars on a regular basis to disseminate technical updates about CAPRAD X X X Conduct annual in person CAPRAD technical seminar X

Conduct a NRPC District Director planning meeting remotely X X X X X X X X X X X X Provide CAPRAD support services via email/phone X X X X X X X X X X X X Monthly calls for NRPC executive officers X X X X X X X X X X X X

Monthly call for all regions X X X X X X X X X X X X

Maintain web site X X X X X X X X X X X X Manage CAPRAD service provider including maintenance issues and user support X X X X X X X X X X X X Provide technical assistance on spectrum management standards and interpretation of FCC rules X X X X X X X X X X X X

3.0 Interoperability and Compatibility

Maintain domain awareness of standards activities X X X X X X X X X X X X

Document gaps in standards X X Provide technical expertise in support of demos/pilots X X X X X X X X X X X X

Option Year 1

1 22

1.0 P25 CAP Support

Kickoff Meeting

X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Review submitted STR and SDOCs X X X X X X X X X X X X

Support responses to inquiries received through P25CAP@hq.dhs.gov X X X X X X X X X X X X Revise Testing Requirements Documents as needed X X X X X X X X X X X X Support development of discussion topics and slide presentations for quarterly P25 CAP meetings

X X X X

Review all P25 CAP documents published on the web site and develop redesign recommendations X Attend other P25 stakeholder meetings and provide briefing

X X X X X X X X X X X X

Draft Standards proposals for interoperability as needed

X X X X X X X X X X X X

2.0 CAPRAD Support

Kickoff Meeting X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Conduct technical webinars on a regular basis to disseminate technical updates about CAPRAD X X X Conduct annual in person CAPRAD technical seminar X Conduct a NRPC District Director planning meeting remotely X X X X X X X X X X X X Provide CAPRAD support services via email/phone X X X X X X X X X X X X Monthly calls for NRPC executive officers X X X X X X X X X X X X

Monthly call for all regions X X X X X X X X X X X X

Maintain web site X X X X X X X X X X X X Manage CAPRAD service provider including maintenance issues and user support X X X X X X X X X X X X Provide technical assistance on spectrum management standards and interpretation of FCC rules X X X X X X X X X X X X

3.0 Interoperability and Compatibility

Maintain domain awareness of standards activities X X X X X X X X X X X X

Document gaps in standards X X

Option Year 2

3 34

1.0 P25 CAP Support

Kickoff Meeting

X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Review submitted STR and SDOCs X X X X X X X X X X X X

Support responses to inquiries received through P25CAP@hq.dhs.gov X X X X X X X X X X X X Revise Testing Requirements Documents as needed X X X X X X X X X X X X Support development of discussion topics and slide presentations for quarterly P25 CAP meetings

X X X X

Review all P25 CAP documents published on the web site and develop redesign recommendations X Attend other P25 stakeholder meetings and provide briefing

X X X X X X X X X X X X

Draft Standards proposals for interoperability as needed

X X X X X X X X X X X X

2.0 CAPRAD Support

Kickoff Meeting X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Conduct technical webinars on a regular basis to disseminate technical updates about CAPRAD X X X Conduct annual in person CAPRAD technical seminar X Conduct a NRPC District Director planning meeting remotely X X X X X X X X X X X X Provide CAPRAD support services via email/phone X X X X X X X X X X X X

Monthly calls for NRPC executive officers X X X X X X X X X X X X

Monthly call for all regions X X X X X X X X X X X X

Maintain web site X X X X X X X X X X X X Manage CAPRAD service provider including maintenance issues and user support X X X X X X X X X X X X Provide technical assistance on spectrum management standards and interpretation of FCC rules X X X X X X X X X X X X

3.0 Interoperability and Compatibility

Maintain domain awareness of standards activities X X X X X X X X X X X X

Document gaps in standards X X

Option Year 3

5 46

1.0 P25 CAP Support

Kickoff Meeting

X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Review submitted STR and SDOCs X X X X X X X X X X X X

Support responses to inquiries received through P25CAP@hq.dhs.gov X X X X X X X X X X X X Revise Testing Requirements Documents as needed X X X X X X X X X X X X Support development of discussion topics and slide presentations for quarterly P25 CAP meetings

X X X X

Review all P25 CAP documents published on the web site and develop redesign recommendations X

Attend other P25 stakeholder meetings and provide briefing

X X X X X X X X X X X X

Draft Standards proposals for interoperability as needed

X X X X X X X X X X X X

2.0 CAPRAD Support

Kickoff Meeting X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Conduct technical webinars on a regular basis to disseminate technical updates about CAPRAD X X X Conduct annual in person CAPRAD technical seminar X Conduct a NRPC District Director planning meeting remotely X X X X X X X X X X X X Provide CAPRAD support services via email/phone X X X X X X X X X X X X Monthly calls for NRPC executive officers X X X X X X X X X X X X

Monthly call for all regions X X X X X X X X X X X X

Maintain web site X X X X X X X X X X X X Manage CAPRAD service provider including maintenance issues and user support X X X X X X X X X X X X Provide technical assistance on spectrum management standards and interpretation of FCC rules X X X X X X X X X X X X

3.0 Interoperability and Compatibility

Maintain domain awareness of standards activities X X X X X X X X X X X X

Document gaps in standards X X

Option Year 4

7 58

Kickoff Meeting

X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Review submitted STR and SDOCs X X X X X X X X X X X X

Support responses to inquiries received through P25CAP@hq.dhs.gov X X X X X X X X X X X X Revise Testing Requirements Documents as needed X X X X X X X X X X X X Support development of discussion topics and slide presentations for quarterly P25 CAP meetings

X X X X

Review all P25 CAP documents published on the web site and develop redesign recommendations X Attend other P25 stakeholder meetings and provide briefing

X X X X X X X X X X X X

Draft Standards proposals for interoperability as needed

X X X X X X X X X X X X

2.0 CAPRAD Support

Kickoff Meeting X Develop Project Management Plan

X Monthly Progress and Financial Reports

X X X X X X X X X X X X Conduct technical webinars on a regular basis to disseminate technical updates about

CAPRAD X X X

Conduct annual in person CAPRAD technical seminar X Conduct a NRPC District Director planning meeting remotely X X X X X X X X X X X X Provide CAPRAD support services via email/phone X X X X X X X X X X X X

Monthly calls for NRPC executive officers X X X X X X X X X X X X

Monthly call for all regions X X X X X X X X X X X X

Maintain web site X X X X X X X X X X X X Manage CAPRAD service provider including maintenance issues and user support X X X X X X X X X X X X Provide technical assistance on spectrum management standards and interpretation of FCC rules X X X X X X X X X X X X

3.0 Interoperability and Compatibility

Maintain domain awareness of standards activities X X X X X X X X X X X X

Document gaps in standards X X

(7) Travel Costs

Travel may be required in the performance of the duties listed in this SOW. Travel is limited to the continental United States and subject to limitations imposed by the Federal government for Federal travel.

DHS invitational travel for stakeholders may be required in conjunction with this SOW.

However, the handling and coordination of the invitational travel is not within scope of this SOW and shall be handled separately.

All travel requests must be submitted to the DHS Program Manager and S&T Contracting Officer’s Representative (COR) for approval at least 15 business days prior to commencement of travel (45 days prior for travel to Canada). The DHS Program Manager and S&T COR shall provide a response within ten (10) business days upon receipt of the travel request, except for invitational travel. Each request shall contain a detailed justification regarding why travel is necessary, the contractors’ level of participation at the event and any presentations or other involvement, as well as a travel estimate that includes airfare, lodging, and other related expenses.

All authorized travel and other direct costs associated with the execution of the tasks indicated in this SOW shall be reimbursed in accordance with the limits set forth in the Federal Travel Regulations. A spreadsheet shall be submitted as part of the monthly activity report that lists all travel requests and their status. All travel submitted for Government reimbursement must include travel receipts where applicable.

(8) DHS-Furnished Information

DHS shall provide DHS information, materials, and forms unique to DHS to the Contractor to support tasks under this SOW. Such DHS-provided information, materials, and forms shall remain the property of DHS, unless otherwise indicated in writing by DHS, and may not be distributed beyond the Contractor’s project performers without DHS's prior written permission.

a. The DHS COR identified in this SOW shall be the point of contact for identification of any required information to be supplied by DHS.

b. The Contractor shall prepare all documentation (e.g., meeting and report deliverables or monthly status reports) according to the guidelines provided by

DHS.

(9) DHS-Furnished Facilities, Supplies, and Services

If work at DHS-provided facilities is necessary for the services being performed under this SOW, such facilities shall be provided at S&T’s office in Washington, D.C. Parking facilities are not provided, however several commercial parking facilities are located near S&T’s office.

Basic facilities such as workspace and associated operating requirements (e.g., phones, desks, utilities, desktop computers, and consumable and general purpose office supplies) shall be provided to Contractor personnel working in S&T’s office.

(10) DHS-Furnished Property

DHS property shall not be provided to the Contractor or any of their performers unless otherwise agreed in a Task Order issued under this RFQ. In such instances, DHS shall maintain property records.

Before purchasing any individual item equal to or exceeding $3,000 that is required to support technical tasks performed pursuant to this SOW, the contractor shall obtain the DHS S&T Contracting Officer’s prior written consent. If the DHS S&T Contracting Officer consents to such purchase, such item shall become the property of DHS. The contractor shall maintain any such items according to currently existing property accountability procedures. The DHS S&T Contracting Officer shall determine the final disposition of any such items in writing.

(11) Security Requirements

All work performed under this Contract shall be done at the unclassified level or For Official Use Only level .

DHS may exercise full control over granting, denying, withholding, or terminating unescorted access to DHS facilities, DHS systems, and/or sensitive DHS information for government/contract employees. Access shall be based upon the results of a DHS fitness/suitability investigation. DHS may, as appropriate, make favorable entry of duty (EOD) decision based on preliminary security checks. The favorable EOD decision would allow the government/contract employee to commence work temporarily prior to the completion of the full investigation. The granting of a favorable EOD decision shall not be considered as assurance that a full DHS fitness/suitability authorization shall follow. The granting of a favorable EOD decision or a full DHS fitness/suitability authorization determination shall in no way prevent, preclude, or bar the withdrawal or termination of any such access by DHS, at any time during the term of the contract/task order. No employee of the government/Contractor shall be allowed unescorted access to a DHS facility, access to any sensitive DHS information, or access to DHS Systems without a favorable EOD decision or DHS fitness/suitability determination by the DHS HQ Office of Security. Government/contract employees assigned to the contract/task order not needing access to sensitive DHS information, DHS systems, or access to DHS facilities shall not be subject to DHS fitness/suitability screening.

Government/contract employees waiting on an EOD decision may not begin work on the task order. Limited access to DHS facilities is allowable prior to the EOD decision if the government/contract employee is escorted by an approved DHS employee. This limited access is to allow government/contract employees to attend briefings, nonrecurring meetings, and begin transition work. During one’s limited access the government/contract employee shall not have access to sensitive or classified DHS information.

Classified information is government information which requires protection in accordance with Executive Order 13526, National Security Information (NSI) as amended and supplemental directives. If the government/contract employee has access to classified information at a DHS owned or leased facility, it shall comply with the security requirements of DHS and the facility.

If the government/contract employee is required to have access to classified information at another Government Facility, it shall abide by the requirements set forth by the agency.

The contractor shall adhere to all applicable government laws, regulations, orders, guides, and directives pertaining to classified, Sensitive But Unclassified (SBU), FOUO, or personally identifiable information. The contractor shall safeguard SBU, FOUO information specifically in accordance with DHS Management Directive 11042.1.