FA480117R0031_JTFN_TTX_PWS.doc
DOC document 103 KB Posted
- Attached to
- JTF-N TTX Federal contract opportunity
- Solicitation number
- FA480117R0031
About this file
FA480117R0031 PWS
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| FA480117R00310001_Extend_Due_Date.pdf | ||
| FA480117R0031_JTFN_TTX_Solicitation.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT
FOR
COUNTER THREAT NETWORK TACTICS AND PROCEDURES SUPPORT (CTNTPS)
29 September 2017
1.0. ORGANIZATION BEING SUPPORTED:
HQ, JTF-N/J3
Bldg. # 11603 Old Ironsides Road
Fort Bliss, TX 79918
1.1. MISSION: Joint Task Force North (JTF-N) based at Fort Bliss, Texas, is a joint service command comprised of active duty and reserve component Soldiers, Sailors, Airmen, Marines, Coast Guardsmen, Department of Defense (DOD) civilian employees, and contracted support personnel. JTFN is tasked to support our nation’s federal law enforcement agencies in the identification and interdiction of suspected Transnational Criminal Organizations’ (TCOs) activities conducted within and along the approaches to the continental United States.
1.2. OVERVIEW OF SERVICES REQUIRED: Provide facilitation and necessary services to perform technical analyses and assessments for Southwest Border (SWB) and Virgin Island/Puerto Rico (VIPR) Counter Transnational Organized Crime (C-TOC) Working Group Events (5 days). The corridors considered for areas of focus include (Los Angeles and San Diego Regional Command Mechanism, California, JTF-W California Corridor, Arizona ACTT, JTF-W Arizona Corridor, NM/West Texas Alliance to Combat Transnational Threats (ACTT), JTF-W NM/WTX, JTF-W South Texas Campaign, Caribbean Border Inter-Agency Group (CBIG) and North-East Support) and will be defined specifically at the subtask. These periodic 5 day events involve preparation before, and reporting analysis following each event. There will be 4 events per year with an optional 3 events per year at discretion of the Government.
1.2.1. Background: The fight against Transnational Organized Crime (TOC), particularly the illicit-trafficking of drugs, is a highly complex endeavor involving numerous partners at the local, state, and national levels. Further complicating the efforts are the various authorities and objectives that the diverse mix of agencies bring to the fight. TCOs control vast, multi-tiered networks that orchestrate the flow of illicit commodities, the information flows that orchestrate and adapt those commodity flows, and the associated flows and laundering of money. The current assessment is that most of the illicit drug flow crosses into the United States at the Southwest Border, and most of that at the Ports of Entry. To better support law enforcement, Commander, JTF-N requires an analytical framework as the lens through which friendly C-TOC forces can know themselves, their enemy and their operational environment.
1.2.2. In turn, JTF-N needs to integrate that framework, articulated as a C-TOC Systems Analysis Framework (C-TOC SAF), into a Counter Threat Network (CTN) method, or doctrinal framework. The projected CTN method focuses on building law-enforcement-led friendly or own-forces (OWNFOR) networks to know and attack opposing force (OPFOR) networks, especially TOC and foreign-terrorist-organization networks. In combating narcotics flows, the main source of TOC income and power, while ensuring its own relevance at the POEs, JTF-N needs to orient the analytical framework and CTN method to the communication approaches (corridors) to, through and away from the POEs. Cornerstone and driver of the proposed method is an intelligence architecture built around a collaborative, target-centric C-TOC Sense-Making Framework (C-TOC SMF). The goal of the method is to improve the way interagency teams, task forces and networks build and employ counter-threat-networks capacity. This capacity is expressed as Build, Know, and Attack the Network (BKAtN), to which one might add adapt the network.
1.2.3. First steps towards the required analytical and sense-making frameworks (with associated intelligence architecture) and the broader CTN method that these frameworks support were taken in the counter-methamphetamine CTOC working group events of February and November 2012. The SWB CTOC working group in September 2013, built upon these events followed the same approach. Future events likewise build upon the results of previous events and will assist in identifying ways to counter TOC networks and implement these methods across the gamut of Law Enforcement Agency (LEA) along the SWB.
2.0. SPECIFIC REQUIREMENTS:
2.1. SUBTASK 1: Plan, Prepare, Facilitate, Analyze and Incorporate results of C-TOC Working Group Events
2.1.1. The Contractor facilitation team shall complete the following tasks through facilitated interagency collaboration in face-to-face events. These events will include personnel from all levels of government, and especially from the Department of Homeland Security, Department of Justice and Department of Defense. Other agencies that might participate at times are: United States Border Patrol (USBP), Customs and Border Protection/Office of Field Operations (CPB); Homeland Security Investigations (HSI), Homeland Security Investigations, Office of International Affairs; Customs and Border Protection, Office of Air and Marine (OAM); Immigration and Customs Enforcement (ICE), Enforcement and Removal Operations, Bureau of Alcohol, Tobacco, and Firearms (ATF), Federal Bureau of Investigation (FBI), Drug Enforcement Agency (DEA), United States Marshall Service (USMS), State (CA, AZ, NM, Puerto Rico and TX) Departments of Public Safety, local Police Departments, El Paso Intelligence Center, U.S. Secret Service, Customs and Border Protection Office of Intelligence and Investigative Liaison. This is not an all-inclusive list. An event is defined as a 3-5 day session. Each event requires a week prior for preparation and coordination with JTF-N and a week following, which is typically conducted via email or phone. The contractor shall facilitate the event comprising of up to 3 areas identified in 2.1.1.1 through 2.1.1.4 (note the contractor will not be asked to conduct all of the following during one (1) event).
2.1.1.1. Assess the Threat: During an event that includes, or is focused on, assessing the threat, the contractor shall identify and strategize the threat by correlating multiple agencies’ current intelligence. Through discussion and group interaction, the contractor shall coordinate a consensus of the definition of the threat with each agency. Contractor shall create a picture of the current threat environment comprised of Drug Trafficking Organization (DTOs) along the U.S. and Mexican border and establish a common intelligence picture (CIP) describing the threat’s doctrinal template, threat networks, commodity flows, threat capabilities, threat architecture and the threat operating environment. Contractor shall identify threat network vulnerabilities and value stream constraints.
2.1.1.2. Develop Threat Mitigation Strategy: During an event that includes, or is focused on developing a threat mitigation strategy, contractor shall facilitate the development of a plan using agency capabilities to their maximum effectiveness to mitigate the common threat. A strategy development event shall use the threat defined and correlated during the previous event or events that assessed the threat. Contractor shall facilitate a discussion of the capabilities of agencies. Contractor shall facilitate actions to integrate multiple agencies capabilities against the common threat. Contractor shall build a common operational picture (COP) and architecture for the supporting Government agencies and how they interact in the threat environment. Contractor shall develop a method that can be used to measure performance, effectiveness, and impact (tactical, operational, and strategic) to C-TOC activities.
2.1.1.3. Exercise Threat Mitigation Strategy: During an event that includes, or is focused on exercising a threat mitigation strategy, the contractor shall analyze the strategy using war-gaming methods. Contractor shall develop threat scenarios with associated Government Courses of Actions (COAs) on how to defeat or change friendly and threat vulnerabilities, and highlight how to exploit the constraints exposed during an exercise in an effort to defeat the threat. A threat mitigation strategy exercising event shall use a previously defined threat and threat mitigation strategy which may be assessed and developed during a previous event or as part of this event. A current threat assessment and threat environment will be furnished to the contractor in order to build a realistic scenario and operating environment. Contractor shall develop operational plans against the common threat. Contractor shall exercise plan using a war-game methodology and shall replicate military staff functions (S2: Intelligence, S3: Operations, XO: Chief of Staff, S1: Recorder). The contractor shall take the war-game results and be able to integrate those outcomes into actionable processes that help defeat the threat networks, especially from an intelligence and targeting perspective. These outcomes will better help Government agencies share information, streamline processes and standardize procedures in an effort to defeat the DTOs and their threat along the U.S. and Mexican Border.
2.1.1.4. Review/Assess/Revise a Threat Mitigation Strategy: During an event that reviews, assesses and revises a threat mitigation strategy, the contractor shall review, assess, and revise a threat mitigation strategy that was developed during previous events. Contractor shall review outcome of implementing a threat mitigation strategy. Contractor shall identify weaknesses and/or deficiencies. Contractor shall develop method to correct deficiencies. Contractor shall model this event as an after action review following implementation of the strategy.
2.1.2. Contractor shall understand the C-TOC Systems Analysis Framework (C-TOC SAF), the Counter Threat Network (CTN) method, and military doctrinal frameworks to include MDMP/JOPP, Campaign Planning, and Design to execute all tasks. The contractor shall apply the principles of Lean Six Sigma and Theory of Constraints to network and knowledge environment problem sets.
2.1.3. The geographical focus area for each of these events will be identified at least three weeks prior to each event. Contractor shall incorporate Government Furnished site survey findings and read ahead materials to initiate the week-long event. A current threat assessment and threat environment will be furnished to the contractor in order to build a realistic scenario and operating environment.
2.1.4. The Contractor shall facilitate and support a highly interactive process that uses collaboration to produce the deliverables and develop the relationships critical to adaptive BKAtN.
2.1.5. The Contractor shall provide out-briefs in a bare-bones format to the COR at the conclusion of each C-TOC working group event prior to the Contractor’s departure.
2.1.6. The Contractor shall provide an out-brief to the interagency team that has participated in the C-TOC event and in the process become part of an online knowledge network that supports networking OWNFOR resources to know and attack TOC networks.
2.1.7. Contractor shall create a map of the current threat environment comprised of Drug Trafficking Organization (DTOs) along the U.S. and Mexican border and establish a common operation picture describing the template threat networks, flows of threats, threat capabilities, threat architecture and threat operating environment. Contractor shall build a common operational picture and architecture for the supporting US Government agencies and how they interact in the threat environment.
2.1.8. The contractor shall provide a document that records the results of the wargame session within 1 week of the session being completed.
2.1.9. The Contractor shall develop a narrative to capture results for inclusion in the dynamic systems models (with metrics), emerging CTN method, and emerging generic OWNFOR architecture and specific New Mexico/West Texas OWNFOR intelligence architecture (the OWNFOR network in its organizational, social, knowledge, information-technology, telecommunications and cultural dimensions).
2.1.10. The Contractor shall develop a record out-briefing for senior decision makers and subject-matter-experts.
2.1.11. Estimated Workload:
| C-TOC events |
| Frequency |
| Preparation, Facilitation, Review/Assess/Revise Counter Threat Mitigation Strategy: |
| 12 events / 3 years |
2.1.12. Notional Schedule and Location:
Base Year: (4 Events and 3 additional optional events)
| C-TOC events |
| Length |
| Location |
| XX-XX Oct 17 |
| 1 week |
| Ft Bliss, TX (El Paso commuting area) |
| XX-XX Jan 18 |
| 1 week |
| Corpus Christi, TX |
| XX-XX Mar 18 |
| 1 week |
| Tucson, AZ |
| XX-XX Jun 18 |
| 1 week |
| Ft. Bliss, TX |
3 Additional Optional Events:
| XX-XX TBD 18 |
| 1 week |
| TBD |
| XX-XX TBD 18 |
| 1 week |
| TBD |
| XX-XX TBD 18 |
| 1 week |
| TBD |
Option Year 1: (4 Events and 3 additional optional events)
| C-TOC events |
| Length |
| Location |
| XX-XX Oct 19 |
| 1 week |
| Ft Bliss, TX (El Paso commuting area) |
| XX-XX Jan 19 |
| 1 week |
| Corpus Christi, TX |
| XX-XX Mar 19 |
| 1 week |
| Tucson, AZ |
| XX-XX Jun 19 |
| 1 week |
| Ft. Bliss, TX |
3 Additional Optional Events:
| XX-XX TBD 19 |
| 1 week |
| TBD |
| XX-XX TBD 19 |
| 1 week |
| TBD |
| XX-XX TBD 19 |
| 1 week |
| TBD |
Option Year 2: (4 Events and 3 additional optional events)
| C-TOC events |
| Length |
| Location |
| XX-XX Oct 20 |
| 1 week |
| Ft Bliss, TX (El Paso commuting area) |
| XX-XX Jan 20 |
| 1 week |
| Corpus Christi, TX |
| XX-XX Mar 20 |
| 1 week |
| Tucson, AZ |
| XX-XX Jun 20 |
| 1 week |
| Ft. Bliss, TX |
3 Additional Optional Events:
| XX-XX TBD 20 |
| 1 week |
| TBD |
| XX-XX TBD 20 |
| 1 week |
| TBD |
| XX-XX TBD 20 |
| 1 week |
| TBD |
2.1.12.1. The timing of each C-TOC event shall be provided by the government 3 weeks prior. The length of the event does not include the week prior or the week after needed to complete the task.
3. APPLICABLE PUBLICATIONS (CURRENT EDITIONS) and KEY PERSONNEL:
3.1. The Contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures.
3.2. Key Personnel: The following personnel are considered key personnel by the Government:
3.2.1. Team Leader/Facilitator. The Team Leader/Facilitator leader shall be a certified Master Knowledge Management Professional with Lean Six Sigma Master Black Belt certification. The facilitator must also have a proven track record working in the Counter Threat Network environment with military and federal law enforcement organizations validated by past performances. The team leader must have experience facilitating working groups of subject matter experts to solve complex and ill-defined problems.
3.2.2. Mission and Means Framework Subject Matter Expert (MMF SME). The SME must have at least four years-experience applying the Mission and Means framework to model complex problem sets such as Irregular Warfare, strategic/enterprise level resourcing, or the Counter Threat Network environment. The SME must have demonstrated experience with analytical scenario development with translation of scenario based information into data sets useful for modeling, and an understanding of the application of Value Stream Mapping to network related problem sets which will be evaluated by past performance.
3.2.3. Business Process Modeling/Value Stream Mapping SME (BPM VSM SME). The Business Process Modeling (BPM) SME must have demonstrated experience with Business Process Mapping/modeling of strategic or operational level processes. The BPM SME must also have experience and understanding of the Mission and Means Framework and its application to solve complex problem sets. The BPM SME must have a proven track record working in the Counter Threat Network environment with military and federal law enforcement organizations validated by past performances. The BPM SME must have a proven track record of facilitating interagency working groups and training sessions.
4.0. SERVICE SCHEDULE SUMMARY: N/A
5.0. GOVERNMENT-Furnished RESOURCES and services:
5.1. GOVERNMENT-FURNISHED RESOURCES
5.1.1. HARDWARE: Typically, the contractor personnel will utilize non-government computers and supplies in the preparation, execution, and after action reporting for each C-TOC event.
5.1.2. SOFTWARE:
Typically, the contractor personnel will utilize contractor furnished software in the performance of this Task Order.
5.2. GOVERNMENT FURNISHED RESOURCES:
5.2.1. FACILITIES, SUPPLIES, AND SERVICES: JTF-N will furnish workspace for up to three personnel in the Building 11603 on Fort Bliss Army Installation, including desk space, chairs, computers connected to NIPRNET access, access, use of telephones, copier and fax machines. Any additional personnel will be required to work in the Contractor’s facility.
5.2.2. GOVERNMENT-FURNISHED INFORMATION: Copies of reference materials cited in PWS paragraph 2.1 and subparagraphs will be provided to the contractor.
6.0. GENERAL INFORMATION
6.1. SECURITY: All personnel assigned to this task order must possess a SECRET United States Government security clearance prior to beginning work on this PWS. Contractor personnel shall not divulge any information about files, data, processing activities or functions, USERIDs, passwords or other information to anyone not authorized access to such information. Contractor personnel shall abide by all N-NC/ JTF-N rules, procedures and standards of conduct.
6.2. ACCESS TO GOVERNMENT PROPERTY AND FACILITIES: The Contractor shall be allowed non-escorted access to Government buildings on Fort Bliss, and other sites, consistent with task requirements. Contractor personnel may also enter facilities where escorted access is mandatory with escort. Access to government facilities, documents, and systems shall be in accordance with DD Form 254, and Department of Defense Contract Security Classification Specifications.
6.3 TRAVEL: Contractor shall obtain advance COR (45+ days) approval for travel in support of JTF-N mission requirements. Travel in order to arrive at the Place of Performance (Ft Bliss, Corpus Christi, Puerto Rico , McAllen, TX or Lansing, MI) to conduct C-TOC events shall not be a reimbursable cost. The contractor shall provide trip reports.
6.4. PRODUCT OWNERSHIP: All products produced by the Contractor in the performance of this contract are the property of the Government.
6.5 PROPRIETARY DATA:
6.5.1. The Contractor shall request government approval prior to the use of any proprietary data or software tools to fulfill the requirements of this contract.
6.5.2. The Contractor shall be provided access to information required to accomplish assigned tasks commensurate with security clearance and on a need to know basis.
6.5.3. During the contract period, all data pertaining to this contract shall be returned to the Government upon contract expiration. The Contractor shall not retain classified or unclassified material generated or received under this contract after the contract ends without approval of the appropriate office of primary responsibility.
6.5.4. The Government has unlimited rights to all deliverables developed under this contract. The Contractor shall not use any materials pertaining to this contract for business development or any other vendor strategic purposes.
6.5.5. Contractor personnel will be required to sign Government Non-Disclosure Agreements prior to start of work.
6.6. HOURS OF WORK. There is no requirement for continual coverage for this contract. JTF-N core work hours are 0800-1700, and most support will be required during those hours.
6.7 PLACE OF PERFORMANCE: Reference table 2.1.12. Notional Schedule and Location.
6.8. PERIOD OF PERFORMANCE: The periods of performance are:
| Period |
| Estimated Start Date |
| End Date (1 Year from Start Date) |
| Base Year |
| Est 5 Oct 2017 |
| Est 4 Oct 2018 |
| Option Year 1 |
| Est 5 Oct 2018 |
| Est 4 Oct 2019 |
| Option Year 2 |
| Est 5 Oct 2019 |
| Est 4 Oct 2020 |
6.9. MANAGEMENT: The contractor shall appoint a project manager who shall coordinate with COR to obtain and clarify contract requirements and who will be responsible for the daily control and supervision of contractor's employees. The Project Manager shall ensure the contractor's employees understand the prohibitions imposed on the U.S. Government regarding personal services contracts and will report instances where the Government attempts to control or supervise contractors' employees to COR or contracting officer immediately. Contractor shall ensure its personnel identify themselves as contractors in accordance with applicable N-NC directives and instructions. Contractor shall ensure its personnel do not perform any inherently governmental activities. Contractor shall ensure its personnel do not attempt to represent the Government of the United States or N-NC to any other person or entity, U.S. or foreign, except for delivering a Government-approved message or position.
6.9.1 Monthly Status Report (Not Separately Priced): Contractor shall keep the Contracting Officer Representative (COR) informed of all activities via verbal communication and status reports. The reports shall include the status of resources, resolution of previously reported problems, summary of the preceding month’s accomplishments, new problems encountered (if any), plans for the following month, and the planned deliverables for the next month. Any changes in deliverable schedules for the original task plan will be noted.
6.10. SERVICES DURING CRISIS:
The performance of these services are not considered to be mission essential during times of crisis. Should a crisis be declared, the Contracting Officer or their representative will verbally advise the contractor of the revised requirements, followed by a written notification. COR will further notify the contractor verbally when the crisis has ended with written notification to follow. Any price changes resulting from this crisis will be negotiated in accordance with DFARS clause 252.237-7023, Continuation of Essential Contractor Services, paragraph (f), Changes.
File details come from the government source that posted it. Updated .