Newest Notice - All SAM Post 2025.docx

All Notices

Notice – 06 August 2024

APBI Revision Slide

Notice #1 - 25 Sept 2024 Notification related to Public Private Partnering on Worldwide Forward Support Requirements

During Tobyhanna Army Depot’s (TYAD) Industry Day event in August, several attendees inquired about TYAD’s ability to meet the requirements described in the multiple requests for information posted to SAM.gov for a follow-on to task order W56JSR21F0043 Worldwide Field Support. The intent may have been to collaborate with TYAD under a public-private partnership to perform the work. Please note, because TYAD and U.S. Army Communications Electronic Command’s Software Engineering Center (SEC) are the requiring activities for Worldwide Field Support, there are no anticipated partnering opportunities with TYAD or SEC for the follow-on. Neither TYAD nor SEC will discuss establishing teaming agreements or partnership arrangements. All inquiries made to TYAD and SEC for information about Worldwide Field Support follow-on will be directed to Ms. Sarah Chavez (sarah.e.chavez8.civ@army.mil) and Ms. Thadijah Williams (thadijah.t.williams.civ@army.mil). The U.S. Army Contracting Command encourages exchanges of information among all interested parties for this upcoming opportunity.

Notice #2 – 3 Oct 2024 Questions from Industry with answers

1. The 2020 RFP provides a plug value of approximately $128M for material. Does the contractor purchase an estimated $128M of material on a Cost Reimbursable CLIN through an internal Contractor system using contract funds, or at no cost through a Government system (GCSS-A) with Government funds/accounts? It’s a mix of both. Some items are procured through the contract and others are procured through DODAAC funding.

2. At the TYAD Industry Day, we talked with the procuring agent who stated all procurement for internal/external programs was performed through Tobyhanna, but during the 1:1, our understanding was that all procurement done on the CECOM WWF Support program was through GCSS-A. Can the government please clarify? TYAD proper does not procure items for the RSC contract as a whole, except for a few internal TYAD customers who provide parts for programs they have on the contract.

1. Does the procurement and storage of repair parts reside with TYAD and get shipped to the Hubs or is it a contractor requirement to order, receive, and store on location? If there are commercial procurement requirements on the CECOM WWF Support, would the Government be open to a CHS 6 solution (forward Depot capability)? The contractor orders, receives, and stores their own parts. Some sites may order for other sites if there is a need. Additionally, some customers provide their own parts to the contractor. Depends on the program and what the customer puts in their statement of work.

2. Under a new SA IDIQ, will the new contract have the same fixed fee cap as RS3 (i.e. 7%)? Fixed Fee is TBD

3. Will there be incentive fees to, as an example, incentivize exceeding performance requirements or delivering increased efficiencies through innovation A subsequent RFI will come out seeking recommends incentives

4. Will the SA IDIQ be awarded under an existing contract vehicle (MAPS/OASIS/FEDSIM etc…), or a new standalone IDIQ? The recompete effort is anticipated to be a standalone IDIQ but is still TBD

Notice #3 – 25 November 2024

CECOM Worldwide Field Support Recompete 1 on 1 Meeting Opportunity One-on- One Opportunities available.

An opportunity for an hour long virtual one-on- sessions with the Technical Team from Tobyhanna, SEC, OAS, and ACC will be available the week of December 10th - 13th 2024 for the CECOM Worldwide Field Support Recompete . The purpose of the initial or follow up session is to ask questions, get clarification from any of the 4 RFI’s that have previously been submitted, or to perform demonstrations.

If your company would like the opportunity for this hour-long virtual meeting , please email the Contracting Officer Sarah Chavez sarah.e.chavez8.civ@army.mil and Contract Specialist, Ms. Thadijah Williams thadijah.t.williams.civ@army.mil .on or before Monday December 2nd 2024 12:00 PM EST and specify:

1). Q&A session: provide the questions and a list of attendees 2). Demonstration: provide a brief description, questions associated, and a list of attendees 3). Q&A and Demonstration: provide questions, brief description, and list of attendees A confirmation email will be sent to the requestor showing receipt of meeting type. Additionally, a Team’s link with meeting date and time will be emailed to the requestor once schedule is established after the closing of the notice. If questions are anticipated, please submit them in writing to the listed Contracting Officer and Contract Specialist at least 24 hours prior to your confirmed time once appointed along with a list of participants.

To ensure procurement integrity, please direct all inquiries to the Contracting Officer Sarah Chavez sarah.e.chavez8.civ@army.mil and Contract Specialist, Ms. Thadijah Williams thadijah.t.williams.civ@army.mil . Meeting requests and separate questions directly to the customer(s) will automatically be redirected to the Contracting Officer and Contract Specialist.

Notice #4 – 13 March 2025 WFS Recompete Info To Vendors Hello, The CECOM recompete for Worldwide Field Support is actively being worked towards a draft Request for Proposal;(RFP) to send out to all interested parties via SAM.GOV. At this time, we are not holding any meetings or answering additional questions. An Industry Day with the Technical teams from SEC and TYAD is anticipated in the near future. Once a date is established, a notice will be sent via SAM.GOV with the necessary information.

We kindly request that you hold all questions until after the release of the draft RFP and Industry day.to ensure we have ample time to cover address them.

We're eager to hear your questions and value your input. Thank you for the continued interest in the program.

All RFI’s

RFI #1 – 18 April 2024 Worldwide Field Support Follow On Request for Information

Included Performance Work Statement draft

1. The Tobyhanna Regional Support Centers provides maintenance logistics support in many forms and potentially all phases of product life cycle during sustainment; from procuring repair parts, to warehouse management, to DLA-DS disposal. The logistics efforts support the maintenance fundamentals of planning, reporting, servicing, repairing, and dispositioning utilizing government programs such as GCSS-A, LMP, WAWF, Vantage, and other software platforms. How would you plan to staff and structure for logistics operations?

2. As a contractor at the Tobyhanna Regional Support Centers, you will be expected to execute sustainment maintenance practices in accordance with established Army publications AR 750-1 and DA Pam 750-1, as well as additional references contained there-in. How would you plan to staff personnel for maintenance operations to support both field and sustainment level support; on platform and in shop/bench in the box repairs?

3. How can we enhance the clarity and specificity of the Statement of Work (SOW) within the PWS to better align with SA IDIQ requirements?

4. In your experience, what are the key elements of effective task order setup within a military contract framework, and how can we integrate them into our PWS?

5. What strategies would you suggest for incorporating incentives into the PWS to promote contractor performance excellence while maintaining cost-effectiveness?

6. How would you recommend structuring the evaluation methodology within the PWS to ensure fairness, transparency, and alignment with contract objectives?

7. Can you provide examples of successful performance metrics used in similar military contracts, and how can we adapt them to improve our PWS?

8. How can we streamline the process for identifying and resolving conflicts or ambiguities within the PWS to minimize disruptions during contract execution?

9. How can we strengthen the language in the PWS to mitigate risks associated with changes in scope, schedule, or budget during contract performance?

10. In what ways can we incorporate feedback mechanisms into the PWS to solicit input from stakeholders and optimize contractor-client communication channels?

11. What strategies would you recommend for enhancing collaboration and synergy among subcontractors and prime contractors within the context of the PWS?

12. How should we address sustainability and environmental considerations within the PWS to align with broader military objectives and regulations?

13. How can we leverage emerging technologies and innovation initiatives within the PWS to drive efficiency gains and performance improvements?

14. How can we ensure compliance with relevant laws, regulations, and industry standards?

15. What steps can be taken to enhance the scalability and modularity of the PWS to accommodate fluctuations in demand and operational requirements?

16. What strategies would you suggest for promoting continuous improvement and performance optimization throughout the duration of the contract as outlined in the PWS?

17. How can we incentivize innovation and knowledge sharing among contractors to foster a culture of excellence and excellence within the PWS framework?

18. How would you build a packet of CDRL’s for a large contract covering multiple customers and locations?

19. How would you incentivize a contract to ensure timely billing is completed?

20. With specific highly qualified skillsets required on the contract, the ability to attract and retain employees is paramount. How do you entice and retain high demand, uniquely skilled employees?

21. What mechanisms do you propose for ensuring flexibility and adaptability within the PWS to accommodate evolving mission requirements and technological advancements?

22. What lessons learned from past military contracts can inform the refinement of our PWS to mitigate common pitfalls and maximize success?

23. In dynamic global environments with potential unknowns, what resources/processes do you have in place to ensure mission is executed to completion with minimum risk and while also factoring in cost, schedule, and performance? Please provide experience examples.

24. What contract type would you propose for a contract that has multiple customers at multiple locations with a variety of work efforts?

Efforts: maintenance, logistics, pack/wrap/ship Multiple locations, worldwide Multiple funding organizations

25. How would you propose a breakout of Task Orders (TO) for a contract with multiple work efforts, 7 locations (TYAD; SWA; Korea; Europe; JBLM, WA; Ft. Cavazos, TX; Ft. Liberty, NC), and Approximately 250+ customers.

26. How would you handle timely billing and deobligation along with closeout of a task order?

To ensure unused funds are returned to the customer in a timely manner to reallocate.

To ensure billing is complete and reconciled as soon as possible.

RFI #2 – 28 June 2024 Worldwide Field Support Follow On Request for Information Follow on question from Original RFI posted on April 18th, 2024 In regard to question #25, proposing a breakout of Hardware Task Orders (TO), the consensus appears to be a total of (7) TO; One TO per location, per Option Year. With the WFS contract supporting worldwide, personnel would need to jump from location to location (TO to TO) and material would require to transferred as well. There is also a concern regarding SOFA, CAC’s, MP ICAM realignment along with DD254 with each being tied to specific TO. With this concern, does the vendor see issue with supporting the requirements needed with personnel jumping from CTN to CTN if TO aligned to location and is there issue with shipping material/parts from one TO to another TO? What are the reasons why each vendor would choose (7) task orders over (1) task order? Please elaborate.

(PWS draft and RFI #1 Post)

RFI#3 – 6 Aug 2024 Worldwide Field Support Follow On – Request for Information #3 Background: CECOM Software Engineering Center is modernizing field software support policies and practices to synchronize with the US Army’s transformation vision (IAW Software modernization Directive, DOD Software modernization strategy, CI/CD Funding memo, 2024 Army Force Structure Transformation, Transformation in Contact). To accommodate these changes, CECOM SEC will be transitioning from traditional FSR support to more flexible regional Software Support Representatives (SSRs) who possess software-centric Domain expertise (e.g. Intel systems, Communications systems, Command and Control systems, Business Systems, etc.) to assist regions with initial troubleshooting, operational testing, interoperability/backward compatibility challenges, training (military and DA Civilian), and documentation reviews across system domains.

RFIs:

1. With the Army’s implementation of Continuous Integration/Continuous Delivery (CI/CD), how would you propose to meet the SME domain support requirements earlier in a system lifecycle and with sufficient expertise to support multiple software activities (e.g. concurrently support system/software fielding’s and software maintenance of existing systems with fewer, more highly skilled SSRs)?

2. With this approach, does the vendor see issues with retaining expertise that can support requirements across domains rather than individual systems?

3. What challenges or concerns would the vendor have for shorter-duration missions (e.g. ~2years) and with retaining the workforce with an expectation that once the SSR tasks are complete, they would be reskilled/upskilled for the next gen systems/software baselines (e.g. dynamic education of the SSR pool in response to Agile and DevSecOps evolution)?

RFI #4 - 22 October 2024 Worldwide Field Support Follow On - Request for Information #4

1. Telemaintenance – The telemaintenance concept has become a key initiative within the Army, connecting end item users (soldiers) through phones, MS Teams chat, and videoconferencing systems to deliver maintenance solutions. This concept reduces overall cost, increases safety while decreasing system downtime… on Hardware side of the WFS contract, with support historically being embedded or within Units reach, moving towards this concept would reduce the overall footprint of support required. How would you approach this concept and implement? And do you foresee any challenges under this maintenance concept?

2. Workforce Augmentation - TYAD is contemplating a shift in philosophy from current and previous WFS contracts, moving from CTR managed requirements to Organic managed with a CTR supporting workforce (workforce augmentation). This concept has successfully been in place at TYAD for 20+ years, with CTR personnel directly supporting maintenance shops with TYAD management providing requirements, through the COR. Under this concept, would you anticipate any challenges with this structure or have any recommendations that would assist with implementing?

3. Incentives/fees – under a workforce augmentation concept, what contract incentives would you recommend and why?

image3.emf

Attachment 2 - WFS Performance+Work+Statement+-+DRAFT+18+April+2024.pdf

ADVANCED PLANNING BRIEFING TO INDUSTRY

Worldwide Field Support

Performance Work Statement (PWS)

1.0 INTRODUCTION

The US Army Communications-Electronics Command (CECOM) organizations and subordinate units have greatly enhanced US Army and Coalition unit readiness worldwide by delivering effective and efficient maintenance and field support at the forward edge of the battlespace. CECOM issued Operations Order (OPORD) 23-02 to enable multi-domain operations and rapidly adjust and align the mission focus of C5ISR support on supply and equipment readiness—and to ensure field support is integrated with supported units’ priorities by unifying efforts via the Army Sustainment Command (ASC). In accordance the OPORD, the CECOM Software Engineering Center (SEC) and Tobyhanna Army Depot (TYAD) created the Worldwide Field Support (WFS) contract. WFS enables CECOM to efficiently and flexibly engage industry manpower as needed to implement field support and support the need for CECOM to realize sustainment cost efficiencies.

1.1 BACKGROUND

This effort is to support the U.S. Army Communications-Electronics Command (CECOM), Software Engineering Center (SEC), and Tobyhanna Army Depot (TYAD) requirement to provide worldwide field support. The field support mission includes a global range of mission-essential logistics, sustainment and maintenance services for current and future Command, Control, Computers, Communications, Cyber, Intelligence, Surveillance and Reconnaissance (C5ISR) systems, equipment, and ancillary operational requirements in support of the Joint Warfighter and coalition forces worldwide within the Army Field Support Brigade (AFSB) regions. CECOM’s goal is to provide global C5ISR Logistics, Sustainment and Field Maintenance, and Technical Assistance (Tech Assist) support to the Joint Warfighter and coalition forces in a timely, cost-effective manner. The Tech Assist support is comprised of providing IT administration and specialized Field Support Representatives (FSRs). CECOM prepares, sustains, and resets the nation's Armed Forces before, during, and after combat operations and deployments. This effort adheres to the direction outlined in CECOM OPORD 23-02, CECOM Field Support Realignment dated 14 March2023, and associated Field Support Fragmentary Orders (FRAGOs).

1.2 MISSION

As a major subordinate command of Army Materiel Command (AMC), CECOM’s core mission focuses on entire life cycle sustainment and logistics of C5ISR systems. This mission is accomplished through rapid acquisition, maintenance, production, fielding, equipment training, technical assistance, operations, and sustainment of CECOM equipment. CECOM provides the U.S. Army with communications and electronic systems that enable vehicles, tanks, planes, helicopters, ships, satellites, missiles, and the Joint Warfighter to communicate and dominate the battlefield.

TYAD’s mission is to provide full life cycle support for all C5ISR systems in order to be the Department of Defense’s worldwide C5ISR readiness provided today, tomorrow, and into the future. TYAD executes the majority of that worldwide mission through its Field Logistics Support Directorate (FLSD) which provides global support on C5ISR logistics, sustainment, supply support and field maintenance to the joint Warfighter, anytime, anywhere. One of the ways FLSD accomplishes that mission is through a Regional Support Center (RSC) construct which operates on a reimbursable (fee-for-service) basis and provides its customers with the flexibility to tailor the required support based on mission requirements, funding, and any organizational specific needs.The RSCs provide total Contractor Logistic Support (CLS) for General Support (GS) and backup Direct Support (DS) maintenance for tactical C5ISR systems and equipment;

interim Contractor support and warranty management for selected systems; and, GS/DS to U.S. Army units. The RSCs are staffed with Contractor and Government maintenance and technical subject matter experts (SMEs) capable of providing the full spectrum of maintenance and logistics support for C5ISR systems and surging its support to meet mission requirements as they arise. The RSC primarily provides sustainment-level maintenance as required. These Contractor SMEs are typically collocated with the units at each RSC, and as the SMEs are intimately familiar with the unit and the unit’s equipment. The SMEs are able to rapidly provide specialized technical expertise and advice. Government civilians employed by TYAD- FLSD are deployed to provide on-site oversight at each RSC.

CECOM SEC’s mission is to ensure operational readiness by developing, providing, integrating, and maintaining Army C5ISR, Logistics, and Business Solution software.

CECOM SEC FSD supports that mission by providing Post Production Software Support/Post Deployment Software Support (PPSS/PDSS) to the Warfighter worldwide for Garrison, deployment preparation exercises, combat operations, and contingencies through the SEC. CECOM provides Field Service Representative (FSR) and Formal Classroom trainer support. The Formal Classroom training is currently only conducted on the Korean Peninsula within the Mission Command Training Center (MCTC).

CECOM SEC’s mission is executed by providing OPCON support to the 7 CECOM Forward Elements (CFE) co-located with the Army’s 7 AFSBs. FSRs will be tasked to execute support tasks directed by the on-site SEC FSD Software Readiness Officers, also OPCON the regional CFEs.

1.3 SCOPE

The scope of this Task Order (TO) is to obtain a wide range of mission-essential logistics, sustainment, and maintenance services for current and future C5ISR systems, equipment, and ancillary operational requirements in support of the Joint Warfighter, U.S. coalition forces worldwide and other government agencies within the Army Field Support Brigade (AFSB) regions/Areas of Operation (AORs). The nature of this work can be highly technical and complex with contractor support required at numerous geographic locations and installations worldwide. The nature of field support will require the Contractor to be able to adapt quickly to changing global situations, technologies, policies, and constraints. There are significant travel requirements to dispatch

Contractor personnel and teams to unit locations for C5ISR missions. Travel requirements will vary widely and can be short notice and require varying skillsets based on mission requirements. The Contractor shall provide the required expertise within this dynamic environment, anticipating and adjusting resources with flexibility and cost efficiency.

1.4 PERIOD OF PERFORMANCE

The WFS TO period of performance is TBD based on government requirements still being defined.

1.5 PERFORMANCE REQUIREMENTS

For all requirements herein, work shall be performed in accordance with all sections of this prospective Single Award IDIQ. The Contractor shall provide fully trained and qualified staff, ready to execute the mission upon arrival. There shall be no exceptions granted regarding the requirement for the Contractor to provide fully trained people when the requirement has been clearly defined. From Day 1 forward, every individual whose time is invoiced against the Task Order must be ready to perform their job and fully qualified to execute the specified mission.

In performing this requirement, the Contractor shall be required to interact with Program Executive Offices (PEOs) and system/equipment Program, Project, and Product Managers (PdMs) to ensure effective communication of CECOM and AMC actions and initiatives. The Contractor may be required to coordinate with the military Force Protection Officer, CECOM Senior Command Representatives (SCRs), or the AFSB for all regions.

The Contractor shall perform actions, projects, and activities to ensure success of a wide range of fielding and C5ISR integration initiatives. The Contractor shall provide for the synthesis, integration, and coordination of key plans and events involving logistics, maintenance, and software support actions. The Contractor shall provide input into various unit documents such as Standard Operating Procedures (SOPs);

assist with overviews of sustainment support practices to ensure a seamless transition from fielding to sustainment; and coordinate with necessary agencies in the development of support concepts.

The Contractor shall foster transparent communications with the software and hardware stakeholders across all CONUS and OCONUS locations at all levels.

The Contractor shall provide WFS a low-risk effective Enterprise Tool available on Day 1 to meet the functional and transparency needs of SEC and TYAD. The Contractor’s Enterprise Tool shall be cloud-hosted, role based, password-protected set of automated tools, workflows and repositories developed specifically for highly efficient worldwide sustainment support of Warfighter systems, with advanced visualization and analysis tools. The Contractor’s Enterprise Tool’s capabilities shall be made available to authorized Government and contractor team members worldwide 24/7 using a standard browser; no additional software resident on users’ computers or licenses shall be required. The Contractor’s Enterprise Tool shall include various modules for ease of navigation in the administration of the requirements of this TO. The Contractor’s Enterprise Tool must meet all related security and access compliance along with any applicable regulations and processes. The Contractor Enterprise Tool shall be utilized in conjunction with established Government systems, tools, processes, and portals as applicable.

The Contractor shall continue to be involved in the life-cycle process as an integrated team member in technology insertion/systems integrations.

The Contractor shall perform evaluation of symptoms and design installation materials and procedures that will allow all system components to operate to full potential. The Contractor shall develop instructions for installation as well as drawings and lists of parts required to mount new systems on vehicles; documentation is maintained in the web-based portal for global access.

The Contractor shall develop technical insertion instructions, drawings, and lists of parts as required and maintain documentation within the Contractor’s Enterprise Tool.

The Contractor shall also conduct analyses and provide recommendations to the Government on budget, manning, and objective execution requirements for operations on short, near, and long-term goals and objectives to ensure that specified missions are executed in support of the PWS requirements.

1.5.1 CONSTRUCT

1.5.1.1 C5ISR RSC CONSTRUCT

RSCs are fixed sites co-located with the AFSBs in seven regions worldwide. The Contractor is responsible for staffing and operating the RSCs, as well as the facilities at each designated Continental United States (CONUS) and/ or Outside Continental United States (OCONUS) location. Each AFSB has an assigned Forward-Deployed Alternate Contracting Officer Representative (ACOR) that the Contractor shall work in conjunction with to support the execution of C5ISR activities. The critical planning factor for the Contractor is staffing as required by region and not by site. Within each AFSB, the Contractor shall support all of the systems and equipment. The Contractor shall provide worldwide logistics and maintenance support for new and existing C5ISR systems and components, with work executed primarily on-site at Government owned and contractor managed facilities (Figure 1-1). The Contractor shall provide a portfolio of services using an agile maintenance management approach that leverages the concept of Multifunctional-Field Service Representatives to adapt to shifting demands in the field.

Figure 1-1: C5ISR RSC locations.

AFSB AFSB

USCENTCOM

AFSB

USINDOPAC

OM

KOREA

JBLM

USEUCOM

LIBERT

Y

CAVAZ

OS

LOCATION SOUTHWEST

ASIA

HAWAII FAR EAST CONUS -

PACIFIC

EUROPE CONUS –

EAST

CONUS -

WEST

Primary

RSC

Camp Arifjan, Kuwait

None Camp Humphreys , Korea

Joint Base Lewis McChord

(JBLM)

Washington

Kaiserslautern, Germany

Fort Liberty, North Carolina

Fort Cavazos, Texas and Fort Bliss, Texas

Satellite

RSC

Camp Buehring, Kuwait

Supported through AFSB

USINDOPAC

OM Area of Responsibility

Stanley, Korea

Other locations in the CONUS Pacific region

Stuttgart, Germany locations in the

CONUS

East region the

CONUS

West

Erbil Airbase, Iraq

Casey, Korea

Vincenza, Italy

Al-Asad Airbase, Iraq

Osan Airbase, Japan

Djubouti, Africa

BDSC, Iraq Other the Far East region

Other locations in the Europe

Bashur, Iraq locations in the SWA region

a) AFSB USCENTCOM [Southwest Asia (SWA)]: In Kuwait, the primary RSC is located at Camp Arifjan as well as support to other countries in the region (primarily but not exclusively Iraq) initially via temporary duty (TDY) assignment and, if extend over 90 days, by establishment of new operating location(s).

b) AFSB USINDOPACOM (Hawaii): Currently there is only a satellite RSC in the AFSB USINDOPACOM region. (Supported through AFSB JBLM Area of Responsibility (AOR))

c) AFSB KOREA (Korea): The primary RSC is located at Camp Humphreys with satellite RSCs located at Camp Stanley, Camp Casey, and Osan AB.

d) AFSB JBLM (CONUS) Pacific): The RSC is located at Joint Base Lewis McChord (JBLM), Washington with embedded support in other locations in the region.

e) AFSB USEUCOM (Europe): The RSC is located in Kaiserslautern, Germany with satellite locations in Stuttgart, Germany and Vincenza, Italy and other European and African (Djibouti) locations (including Kosovo or Ukraine, if initiated)

f) AFSB LIBERTY (CONUS East): The RSC is located at Fort Liberty, North Carolina and staff embedded other locations in the region.

g) AFSB CAVAZOS (CONUS West): The RSC is located at Fort Cavazos, Texas with outlying locations at Fort Bliss and staff embedded at other locations in the region.

The Government may require the Contractor, via written notification from the Contracting Officer’s Representative (COR), to facilitate the opening of new RSC locations worldwide or to support the downsizing and/or closing of existing locations.

The Contractor shall work with the Government to support opening RSCs by providing M-FSRs trained to support more than one system/line of business. These are key to significant cost efficiencies in day-today maintenance activities, but they also help to quickly and efficiently mobilize and demobilize RSCs and field sites. There are limited requirements outside the AFSB and RSC structure detailed above. These requirements are detailed below. Specific places of performance are defined but not limited to section

1.5.2. and (Figure 1-1).

For all RSCs supported, the Contractor shall establish, in consultation with the Government, a base technical and logistical staff and ensure that each region can quickly acquire the skill sets to perform all levels of maintenance and logistics for C5ISR capabilities. The Contractors Task Order Management (referred to as PMO) shall have leadership components which are regionally organized and shall be staffed with logisticians and M-FSRs who are trained and certified to sustain multiple C5ISR systems. The Contractor program logistics lead shall be responsible for all aspects of logistics services. These responsibilities include the overall management of procurement, data analytics and export control compliance. A subordinate Contractor logistics lead shall be placed in each region, CONUS/OCONUS, and will be responsible for local logistics operations, reporting to the regional lead, and matrixed to the program-level logistics lead. The C5ISR systems such as but not limited to, tactical radios, Trojan, Prophet, Counter fire and Counter target Radars, fiber optics, satellite, imaging, mechanical, power generation and electrical systems, counter-improvised explosive device (C-IED), elevated sensors and force protection systems and aircraft survivability equipment.

For each system, unless otherwise specified, the Contractor shall be required to perform system repairs in order to return each to the Full Operational Capability (FOC) or the U.S. Army’s 10/20 standard and in accordance with the applicable Technical Manuals (TMs). All available TMs will be provided to the Contractor as Government- Furnished Information (GFI). The Contractor shall provide sustainment level maintenance IAW AR 750-1 for fielded systems providing installation, and de-installation.

1.5.1.2 C5ISR SOFTWARE CONSTRUCT

SEC Software Readiness Officers are aligned with AFSB, G-3 SCR and ILSC RTAM at each of the major AFSB Hubs (Korea, Germany, JBLM, Ft. Liberty, Ft. Cavazos) to provide Post Deployment/Production Software Support (PDSS/PPSS) for deployed Command, Control, Communications, Computers, Cybersecurity, Intelligence, Surveillance, Reconnaissance (C5ISR), business and enterprise information systems within the regions. SEC FSD coordinates SEC technical assistance/field support (SRO, FSR/FSE) at the Regional Corps, Division, or the Brigade level. SEC FSD assists Commanders with solving technical assistance problems beyond their resources or capability to resolve. IAW CECOM OPORD 23-02

1.5.2 PLACES OF PERFORMANCE

Performance shall take place at CONUS and OCONUS locations. Specific performance locations may vary based on support requirements for the duration of the Task Order.

The Government facilities will be located at Aberdeen Proving Ground, MD, as well as, Tobyhanna, PA and the following locations including but not limited to:

Alabama - Birmingham, Ft Novosel, Huntsville, Jasper, Red Stone Arsenal; Alaska - Ft Wainwright, JB Elmendorf-Richardson; Arizona - Davis-Monthan AFB, Ft Huachuca, Phoenix, Yuma; California - Camp Parks, Camp Roberts, Fairfield-Suisun, Ft Hunter- Liggett, Ft Irwin, Fresno, Irvine, Long Beach, Los Alamitos, March AFB, Mountain View, Sacramento, San Diego, San Francisco, Seal Beach; Colorado - Ft Carson; Connecticut

- Groton; Florida - Camp Blanding, Eglin AFB, Hulbert Field, Jacksonville, MacDill AFB, Melbourne, Miami, Orlando, Perrine, Tampa; Georgia - Augusta, Decatur, East Point, Forest Park, Ft Benning, Ft Gillem, Ft Gordon, Ft McPherson, Ft Stewart, Hunter Army Airfield, Macon; Hawaii - Hickam AFB, Ft Shafter, Pohakuloa, Schofield Barracks, Wheeler AAF; Idaho - Gowen Field; Illinois - Ft Sheridan, Rock Island Arsenal; Indiana - Camp Atterbury, Indianapolis; Kansas - Ft Leavenworth, Ft Riley; Kentucky - Bowling Green, Elizabethtown, Ft Campbell, Ft Knox, , Lexington, , Louisville; Louisiana - Ft Johnson; Maryland - Ft Meade; Massachusetts - Ft Devens; Missouri - Ft Leonard Wood; Mississippi - Camp Shelby, TYAD, Tupelo; New Mexico - White Sands Missile Range; Nevada - Las Vegas, Nellis AFB; FT Dix/JB MDL; New York - Ft Drum, Syracuse; North Carolina - Camp Lejeune, Charlotte, Cherry Point, Fayetteville, Ft Liberty, Jacksonville, Wilmington; Ohio - Columbus, Ravenna, Stow, Whitehall, Wright- Patterson AFB; Oklahoma - Ft Sill; Oregon - Camp Rilea, Portland; Pennsylvania - Ft Indiantown Gap, Pittsburgh; South Carolina - Charleston, Ft Sumter, Greenville, Shaw AFB; Tennessee - Chattanooga, Clarksville, Knoxville, Memphis, Murfreesboro, Nashville, Smyrna; Texas - Ft Bliss, Ft Cavazos, Ft Bliss, Ft Sam Houston, San

Antonio, Goodfellow AFB; Utah - Camp Murray, Dugway Proving Ground, Midvale, Salt Lake City; Vermont Jericho; Virginia - Ft Belvoir, Ft Eustis, Ft Monroe, Ft Barfoot, Ft Story, Norfolk, Salem, Quantico, Ft Gregg-Adams; Washington - Camp Murray, JBLM, Yakima Training Center; Wisconsin - Ft McCoy; Washington, DC; OCONUS: Germany - , Baumholder, Grafenwoehr, , Hohenfels, Katterbach, Kaiserslautern, , Sembach, Stuttgart, Vilseck, Wiesbaden; Guam; Honduras - Soto Cano Airbase; Italy – Vicenza, Livorno; Belgium – SHAPE Headquarters, Chievres; Netherlands – Schinnen, Brunssum; Bulgaria – Novo Selo Training Area; Republic of Georgia – Vaziani; Kosovo

– Camp Bondsteel; Romania – Mihail Kogalniceanu Air Base; Latvia – Adazi, Lielvarde;

Estonia – Tapa Training Area; Lithuania – Pabrade, Kaunus; Poland – Drawsko Combat Training Area, Bemowo Piskie Training Area, Torun, Zagan, Wroclaw, Powidz, Nowa Deba; Horn of Arica – Djibouti, Camp Lemonnier; Japan (Honshu) - Camp Zama, Sagami General Depot, Yokohama North Dock, Shariki Communications Site, Kyogamisaki Communications Site, Kure Pier 6 / Ammunition Depot; Japan – (Okinawa)

– Kadena Air Base, Torri Station, Camp Kinser, Naha Military Port; Korea - K-16 Air Base, Camp Carroll, Camp Casey, , Camp Henry, Camp Hovey, Camp Humphreys, , Camp Stanley, Camp Walker, Daegu, KunSan Air Base, OSAN Air Base, Pusan, Live Fire Ranges, Suwon, Uijonbu, Yongsan, Camp Yongin, Camp Bonifas (JSA), Camp Tango; Puerto Rico - San Juan. Other duty areas may include Afghanistan, Syria, Horn of Africa and other countries on the African continent, Iraq, Kosovo and the Balkans, Egypt, Jordan, Kuwait, Qatar, Israel, and Eastern Europe (to include, Spain, Poland, Romania, Bulgaria, etc.).

The Contractor shall track and report on all personnel, full or part time, duty location assignment, labor category employee is assigned and billing against, the mission departure and return date, and temporary mission location as a part of a deliverable module on the Contractor’s Enterprise Tool portal from the time of hire until the employee is no longer on the program. The contractor shall use this data to create, email and post the requisite weekly Org Chart/Locator Report (CDRL A003) to the Contractor’s Enterprise Tool portal. This report tracks key events that must take place during deployments to provide a common operating picture to TYAD and SEC leadership, CORs and the Technical Monitors (TMs).

The Contractor shall be responsible for understanding, complying, articulating, and executing all DoD Contractor requirements for those personnel assigned to any OCONUS duty stations on a permanent or temporary basis. The Contractor shall use their experience in the requirements, including DODI 3020.41 Operational Contract Support, to deploy and re-deploy personnel to OCONUS contingency operations locations. The Contractor shall verify passport validity, process required visa applications, process necessary Letters of Authorization (LOA), make the associated entries in Synchronized Pre-deployment and Operational Tracker (SPOT) and fulfill all SPOT requirements. The Contractor shall execute all data entry into SPOT and will work with the COR and ACORs to ensure that LOAs will be processed in a timely manner.

1.5.3 OCONUS PERFORMANCE

1.5.3.1 KOREA

The Contractor shall remain compliant IAW the Status of Forces Agreement (SOFA) between the United States and Korea that governs the rights and obligations of the United States Armed Forces in Korea. Only those individual Contractors who are United States nationals; not ordinarily a resident in Korea; present in Korea at the invitation of and solely for the purpose of executing contracts with the United States for the benefit of the United States Armed Forces; and not present in Korea under any other SOFA status may be verified by Korean authorities upon their entry into and/or departure in Korea. The Contractor shall be responsible for personnel traveling to the Republic of Korea in support of supported C5ISR systems and shall ensure travelers are processed in compliance with US Indo-Pacific Command Travel Requirements, USFK regulations, US/Republic of Korea Status of Forces Treaty and Korean Immigration Law for entry into Korea. Failure to follow proper processes and regulations can result in denial of support, adverse administrative action for military and DA Civilians, denial/revocation of access to military installations, termination of contracts and debarment/suspension from contracting with U.S. agencies.

1.5.3.2 SOUTHWEST ASIA (SWA)

The Contractor is responsible for Contractors traveling to SouthWest Asia in support of supported C5ISR systems and to ensure travelers are processed in compliance with U.S. Command Travel Requirements, Theater Business Clearance (TBC), Letters of Authorization (LOA), Government Furnished Life Support Validation (GFLSV), and local Immigration Laws for entry. The Contractor is responsible for proper Visas (by specific Article) and sponsorship if required. Failure to follow proper processes and regulations can result in denial of support, adverse administrative action for military and DA Civilians, denial/revocation of access to military installations, termination of contracts and debarment/suspension from contracting with U.S. agencies.The Government shall provide all Contractors deployed to contingency areas with Force Protection merits control with the following services and facilities: billeting, dining, custodial, fire protection, police, storage, transportation, and utilities. Contractors based in Kuwait (and other low threat Force Protection countries in U.S. Central Command (CENTCOM) AOR, – (USFOR-A)) shall live "off compound" at apartments or other facilities leased by the Contractor. Contractor employees may receive a per diem rate (if proposed by Contractor, not to exceed the maximum amount allowed under Joint Travel Regulation (JTR), to pay for meals and incidentals. All other services will be provided for work site (fire protection, utilities, custodial, etc.) only. Reference: Operational Contract Support (OCS) DoD Instruction (DoDI) 3020.41

1.5.3.3 EUROPE

The Contractor is responsible for Contractors traveling to Europe in support of

U.S. European Command (EUCOM) Travel Requirements, North Atlantic Treaty Organization (NATO), TESA process (by specific Article, process, and status type), along with local Immigration Laws for entry. Failure to follow proper processes and regulations can result in denial of support, adverse administrative action for military and Department of Army (DA) Civilians, denial/revocation of access to military installations, termination of contracts and debarment/suspension from contracting with U.S.

agencies.

1.5.3.4 OTHER OCONUS LOCATIONS

The Contractor is responsible for Contractors traveling OCONUS in support of corresponding U.S. Combatant Command’s Travel Requirements for the AOR (i.e.: U.S.

Africa Command (AFRICOM), U.S. Southern Command (SOUTHCOM), etc.), and local immigration laws for entry, and the FAR. Failure to follow proper processes and regulations can result in denial of support, adverse administrative action for military and DA Civilians, denial/revocation of access to military installations, termination of contracts and debarment/suspension from contracting with U.S. agencies.

1.5.4 THEATER BUSINESS CLEARANCE (TBC)

IAW DFARS 252.225-7995, the Contractor shall obtain the required Theater Business Clearance to support the WFS TO Deliverables:

A001 Report, Record of Meeting/Minutes (Trip Report)

DI-ADMN- 81505

A003 Report, Record of Meeting/Minutes (Org Chart/Contractor Locator Report)

A004 Report, Record of Meeting/Minutes (Travel Request Report)

1.6 SECURITY REQUIREMENT

The highest level of facility clearance required for the Contractor to perform on this contract is Top Secret (TS)/Sensitive Compartmented Information (SCI) with polygraph.

Contractor can work in a SCIF and may be required to lease and/or operate a SCIF based on situational requirements. The highest level of classified material the Contractor maybe required to safeguard at its own facility is Top Secret. For specific security requirements, please refer to the DD-254 Contract Security Classification Specification, AT OPSEC Coversheet and PWS Security contract attachments. An OPSEC Plan is required and shall be provided using IAW (In Accordance With) Contract Data Requirements List (CDRL) D011.

The Contractor and all associated sub-Contractors employees shall comply with all applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by the local/unit Anti-Terrorism Officer (ATO), as well as the security requirements outlined in the DD-254. The Contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services, or Security Office. The Contractor Facility Security Officer shall gather all required information from each employee which will allow for processing of company identification badges and the information required to acquire the required Common Access Card and support all information requirements for background checks.

Contractor workforce must comply with all personal identity verification requirements as directed by Department of Defense (DoD), Headquarter of the Department of the Army (HQDA) and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in Contractor security matters or processes. The highest security requirement for this task order is Top Secret and a safeguarding requirement of Top Secret as defined in the DD- Form 254. The Contractor shall require access to Top Secret, Secret, Communication Security (COMSEC) information, Defense Technical Information Center (DTIC), SCI, COMSEC account, Non-SCI information, NATO information, and receive, store or generate Controlled Unclassified Information (CUI). The Contractor shall also require access to the Non-Classified Internet Protocol Router Network (NIPRNET), Secure Internet Protocol Router Network (SIPRNET), Joint Worldwide Intelligence Communications Systems (JWICS), National Security Agency Network (NSANET) including Trojan Data Network (TDN2) and TDN3. Access to SIPRNet is required at Government facilities only.The Contractor security staff shall remain current in DD254 requirements for access to and handling of COMSEC, NATO, Sensitive Compartmented Information, Non-SCI, For Official Use Only (FOUO), NIPRNET, SIPRNET, and the Defense Technical Information Center registration requirements. No contractor generated COMSEC or government furnished material will be provided to the Defense Technical Information Center. The Contractor technical reports shall meet the statement “Not Releasable to the Defense Technical Information Center per DoD Directive 5100.38”. The Contractor Security Team shall assist with any necessary processing or verification of eligibility for access to DoD Activity JWICS, SIPRNET and

NIPRNET.

All Contractors granted network access must be aware that they are not authorized to download ANY classified material without the guidance and written permission of the Cognizant Security Agency. Contractor shall contact the ACOR to obtain Cognizant Security Agency authority when warranted. The Contractor shall implement a security training program to ensure that all employees arrive for duty fully prepared and knowledgeable in security processes and procedures.

1.7 GOVERNMENT FURNISHED EQUIPMENT (GFE)/GOVERNMENT FURNISHED

PROPERTY (GFP)/GOVERNMENT FURNISHED INFORMATION (GFI)

The Government has sole discretion with respect to whether or not it will provide GFE to the contractor. Hardware and software required may be provided as GFE, such as:• Software licenses for Field Support and related applications and tools.

• Computers and/or Laptops – All work under this Task Order being used on a government site or off-site location shall be conducted on GFE/ Contractor acquired property (CAP) computers that will be issued to each Contractor staff member who has a valid need as determined by the Government.

• Customary office equipment – The Government may provide customary office equipment in the designated Government place(s) of performance such as telephones, printers, and copiers/fax machines. Contractor must return all GFE at the end of the Task Order The Government may provide the following GFI: • Work Products and templates to be used during performance The Government may provide any required information that is not currently on hand at each repair activity if it is available. The Contractor is authorized to obtain and use Federal Logistics (FEDLOG) Data, Army Knowledge Online (AKO) and the Logistics Information Warehouse (LIW) websites.

Access to the CECOM Knowledge Center and other relevant Government Web sites shall also be provided.Additionally, all subsequent items (hardware and software) acquired by the Contractor in the performance of this contract shall be accounted for and maintained in accordance with all other GFE/GFP until either the end of the contract’s performance period or until the Government directs otherwise. Throughout the entire performance period of the Task Order, the Contractor shall properly handle, transport, operate, maintain, track, account for, and control all GFE/GFP. The Contractor shall be responsible for all GFE/GFP and shall take appropriate measures to maintain control and accountability of all GFE/GFP inventory. Management and control methods for GFE/GFP employed by the Contractor must be supportive of and consistent with effective performance of tasks under this contract. All GFE/GFP shall be returned to the Government at the end of the Task Order. The Status of GFE Reports shall be submitted In Accordance With (IAW) CDRL D010 DI-MGMT-80269, Status of GFE Reports.

Government Property is all property owned by the Government, including Government Furnished Property and Contractor acquired property (FAR 45.101(a))Government Furnished Property (GFP) is property in the possession of or directly acquired by the Government and provided to a Contractor for contract performance (FAR 45.101(a))Contractor Acquired Property (CAP) is property acquired, fabricated, or otherwise provided by the Contractor for contract performance and to which the government has title (FAR 45.101(a))Contractor Inventory is excess Contractor acquired property, government furnished property, and any property the Government is obligated to take or has the option to take (applies to any type of contract) (45.101(a))All GFE shall be entered into and accounted for via the Government logistics system GCSS-A account, and signed for by designated user who shall be accountable for inventory requirements, and loss of or damaged to GFE IAW DoD Federal Acquisition Regulation Supplement (DFARS) 252.245-7002, Reporting Loss of Government Property; Army Regulation (AR) 710-2, Supply Policy Below the National Level; AR 735-

5, Policies and Procedures for Property Accountability; Department of the Army (DA) Pamphlet 710-2-1, Using Unit Supply System (Manual Procedures); DA Pamphlet 710- 2-2, Supply Support Activity System (Manual Procedures); and other applicable references.The Government shall provide all necessary equipment, to include specialized tools and hardware, to accomplish all stated requirements of this PWS.