RF-ITV IV PWS

Performance Work Statement

Radio Frequency, In-Transit Visibility IV (RF-ITV IV)

Contract: W52P1J-18-D-A063 Task Order: W52P1J-21-F-0039

26 Jan 2026

Contents

1. RF-ITV SUPPORT SERVICES

2. BACKGROUND

3. SCOPE

4. PLACE OF PERFORMANCE

5. ANTICIPATED PERIOD OF PERFORMANCE

6. PERFORMANCE REQUIREMENTS

6.1 STATEMENT OF OBJECTIVES

6.2 INTENT OF RF-ITV SERVICES

7. SERVICE REQUIREMENTS

7.1 DELIVERY OF THE RF-ITV INFRASTRUCTURE SERVICES

7.2 SOFTWARE OPERATIONS & MAINTENANCE AND APPLICATION DEVELOPMENT

7.3 RFID TOOLS AND REPORTING

7.4 CONTRACTOR TRAVEL AND OTHER DIRECT COSTS (ODCS)

7.5 GENERAL PL LIS SERVICE DESK REQUIREMENTS

7.6 RF-ITV SUPPORT PROJECTS

7.7 MANAGEMENT SUPPORT

7.8 CYBER SECURITY (SUSTAINMENT)

7.9 TC-AIMS II FUNCTIONAL SPECIALIST SUPPORT IN SOUTHWEST ASIA (SWA) AND CENTCOM

7.10 CUSTOMER TRAINING

7.11 TRANSITION

8. PERFORMANCE STANDARDS

9. DELIVERY SCHEDULE AND MILESTONE DATES

10. DELIVERABLES

11. SECURITY

12. GOVERNMENT AND CONTRACTOR RESPONSIBILITIES

12.1 GOVERNMENT RESPONSIBILITIES

12.2 CONTRACTOR RESPONSIBILITIES

13. PERSONNEL QUALIFICATIONS

13.1 CYBERSECURITY TASK ORDER TRAINING AND CERTIFICATION REQUIREMENTS:

13.2 CONTRACTOR TRAINING REQUIREMENTS AND COMPLIANCE:

14. KEY PERSONNEL

14.1 LIST OF CONTRACTOR KEY PERSONNEL:

15. PACKAGING, PACKING AND SHIPPING INSTRUCTIONS

16. INSPECTION AND ACCEPTANCE CRITERIA

17. SPECIAL TERMS AND CONDITIONS

17.1 TRUSTED ASSOCIATE SPONSORSHIP SYSTEM (TASS)

17.2 CONTRACTOR MANPOWER REPORTING (CMR)

17.3 SEXUAL HARASSMENT/ASSAULT RESPONSE & PREVENTION (SHARP) TRAINING AND REPORTING PROCEDURES

18. REFERENCE PUBLICATION, TECHNICAL ATTACHMENTS AND TASK ORDER ATTACHMENTS

18.1 REFERENCED PUBLICATIONS

18.2 REFERENCED PUBLICATIONS INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) ACCESSIBILITY 508 STANDARDS AND 255 GUIDELINES . 44

18.3 LIST OF TECHNICAL ATTACHMENTS

1. RF-ITV Support Services The Army’s Product Lead Logistics Information Systems (PL LIS) is charged with the responsibility of ensuring that standard and high quality logistic visibility services are delivered to the Department of Defense (DoD), other Federal Agencies and Foreign Military Sales (FMS) throughout the world. To achieve this mission, PL LIS is seeking reliable, cost effective solutions to acquire Operations and Maintenance (O&M) for the Continental United States (CONUS) and Outside the Continental United States (OCONUS) Radio Frequency In-Transit Visibility (RF-ITV) system in support of DoD Combatant Commands (COCOMs). To accomplish these and other imperatives, the Contractor shall consider the way that PL LIS currently delivers services and assess alternatives that:

• Promote more efficient processes;

• Reduce the overall cost of services delivered;

• Provide for increased quality of service;

• Provide for increased customer satisfaction; and

• Reduce the need for Government resources in the direct management of these services.

The Vision of PL LIS is to provide the best value to its customers by sustaining its RF-ITV operations, while continually improving processes and lowering the cost of operating the system.

To realize this Vision, ways must be found to further reduce charges to customers while improving the timeliness and quality of the services provided. Agile framework and methodologies will be utilized in all software sustainment/support/development. A key tool and enabler to achieving these objectives is found within the operations, maintenance, and management necessary to the support of PL LIS its customers in the performance of logistics functions and missions.

PL LIS seeks to: (1) utilize Agile processes, procedures, and ceremonies in accordance with Lean Agile methodologies to empower daily work; (2) ensure business value is delivered without introducing operational or executional risk; (3) measure delivery outcome based on customer value captured; (4) build lean, high-functioning teams with multi-talented resources that have depth across several functional areas; and (5) embrace the concept that Agile development is inherently iterative, and scope discovery requires ongoing collaboration between business and technical resources.

PL LIS requires the Contractor to manage services. As such, the Government does not direct the Contractor in configuring, purchasing, integrating, installing, and supporting RF- ITV hardware and software, but rather provides requirements and operational input. Where called out in the pricing matrix, the Contractor shall provide services on a per-unit basis (e.g., installations, de-installations, etc.) and/or as a Firm Fixed Price service (e.g., Help Desk Services).

2. Background The PL LIS program office has a diverse mission to support the U.S. Army, DoD, Federal Agencies, North Atlantic Treaty Organization (NATO), and several coalition partners. PL LIS consists of DoD Government civilians and Contractors, providing logistics, functional, technical, engineering, and management expertise. Established in September 2012, PL LIS is the result of merging two previously existing programs, Joint Automatic Identification Technology (JAIT) and Transportation Information Systems (TIS). PL LIS stands to assist customers, large and small, to develop and automate their business processes by providing a single point of contact for procurement, technical expertise, training, and customer support for both RF-ITV and Transportation Coordinators - Automated Information for Movements System II (TC-AIMS II) operations and service PL LIS sustains the world's largest Radio Frequency Identification (RFID)-enabled asset visibility system, known as the RF-ITV system – which is the system covered by the Performance Work Statement (PWS). PL LIS sustains TC-AIMS II, which is a DoD system of record, Acquisition Category III (ACAT III) program, that is primarily covered under a separate Contract.

Current RF-ITV operations and maintenance of hardware and software is being performed by a third party, commercial firm. Except for Production Servers and long-haul communications (under DoD Non-secure Internet Protocol Router Network (NIPRNET) ) the future state operational environment will have the same or a similar operations and maintenance arrangement with any Contractor maintaining responsibility for all Radio Frequency (RF) hardware and software.

CONUS and OCONUS installation and sustainment services are provided under both Firm- Fixed- Price (FFP) and Fixed Unit Price Contract Line-Item Numbers (CLINs), which comprises the majority of the work for the RF-ITV Task Order. Installation and Sustainment activities are described in the paragraphs below (e.g., installation, break-fix, software updates).

3. Scope The Services to be acquired under the PWS are aligned with Task Area 2 – Information Technology Services and Task Area 3 – Enterprise Design, Integration, and Consolidation of the ITES-3S contract. For purposes of PL LIS’ RF-ITV traceability the support service areas are termed:

• Delivery of the RF-ITV Infrastructure Services, including O&M of existing RF-ITV Infrastructure (CONUS and OCONUS) – See Section 7.1

• Software O&M and Application Development – See Section 7.2

• RFID Tools and Reporting – See Section 7.3

• Contractor Travel and Other Direct Costs (ODCs) – See Section 7.4

• General PL LIS Service Desk (ASD) Requirements – See Section 7.5

• RF-ITV Support Projects (e.g., contingencies) – See Section 7.6

• Program/Project Management Support – See Section 7.7

• Cybersecurity (Sustainment) and Directive Compliance – See Section 7.8

• TC-LIS II Functional Specialist Support – See Section 7.9

• Customer Training – See Section 7.10

• Transition – See Section 7.11

In April 2025 the Government determined supporting the Secret Internet Protocol Router Network (SIPRNET) and SIPR ITV was no longer a requirement. The Government and contractor worked together to develop a program schedule for removing this requirement and DISA completed their removal of SIPR support on 9 June 2025 and the contractor concluded all support of SIPR starting 17 June 2025.

Effective 3 February 2026 PL LIS will no longer require support from the cloud support identified and added to the contract under Contract Modification P00036 for Cloud Support.

4. Place of Performance The PL LIS program office is currently located in Fort Gregg-Adams, VA with some personnel residing at Fort Belvoir, VA. Meetings between the Contractor’s support team, principal staff, and PL LIS personnel shall primarily be held at the Fort Belvoir location.

The Contractor shall perform work at the various worksites identified in the Attachment 0004 – T-1 COCOM Installed Sites. Where approved, the Government may provide space for on- site support teams.

5. Anticipated Period of Performance

Requirement Period of Performance Base Period Date of Award through 12 Months Option Period 1 12 Months Option Period 2 12 Months Option Period 3 12 Months Option Period 4 12 Months Extension (FAR 52.217-8) 6 Months (if required)

6. Performance Requirements

6.1 Statement of Objectives

General Requirements – The services provided by the Contractor under the PWS shall provide for Service Management and be service level driven; meaning services shall be subject to Service Level Objectives for timeliness and quality of service.

The RF-ITV System supports the Combatant Commander by providing knowledge and visibility of all RF-Tagged shipments of material into the respective theater to enable a more efficient use of limited resources. RF-ITV provides the ability to monitor and track the movement of Radio Frequency tagged cargo to destinations worldwide. This system maintains a complete database of the movement of assets it receives from RFID Write Stations and RFID Read Nodes and populates at the point of origin with predefined data that identifies the RFID tags and its associated cargo from origin (consignor) to destination (consignee) during peace, contingencies, exercises, and war time. Currently, the RF-ITV system captures information from Active RFID Tags, cellular transponders, and satellite transponders. The system also currently interfaces with multiple other systems across the DoD. (see Attachment 0005 – T-2 - RF-ITV Systems Architecture and Interfacing Systems) and may integrate with other systems in the future (e.g., Next Generation active RFID Tag).

The Contractor is responsible for sustaining the RF-ITV System and the globally distributed Read Nodes. A Read Node is the location within a COCOM that is comprised of single or multiple RF interrogators positioned in such a manner as to collect the data from RFID Transponder tagged shipments as they pass through that particular location (normally a gate or some other chokepoint). A Read Node normally consists of an interrogator (Reader), a computer (Field Data Unit (FDU)), and some form of communication to a network connection, or a satellite (Iridium) communications device (Modem). On occasion, a Read Node may consist of multiple RF interrogators linked by a data cable or a wireless network communications device and may require the setup of Portable Deployment Kits (PDKs).

Although the Contractor will not be responsible for sustainment of the physical devices making up a Write Station, the Contractor may be tasked with Installation of Write Stations. A Write Station is a location within a COCOM that is comprised of a computer (not an FDU), normally provided by the host site, and some means of communication (cable, tag docking station, or RF interrogator) with the RF Transponder. However, the Contractor shall support the operation of the system; take and log problem calls associated with installed RF Transponder Write software installed (Transportation In- Transit Visibility Processing Software (TIPS) or other RF Transponder Write software); and determine handoff/transfer of the problem.

The RF-ITV servers, via the In-Transit Visibility Integration (ITV-I) subsystems, receive Satellite Tracking System (STS) data from numerous commercial and military Network Control Centers (NCCs). The ITV-I provides an integrated database repository accessible by the RF-ITV server for locating and reporting the position of cellular or satellite-based tracking devices. ITV-I provides the RF-ITV interface to these devices and hosts an associated website that provides the ability to see material movement geographically on a Web Map (currently Transportation Geospatial Information System (TGIS) is the mapping software solution) for the class of ITV users responsible for the actual logistics conveyances (i.e., trucks, trains, barges, containers, etc.). Through the integration of many tracking device types, and associations or linkages detected among them, the website provides users with updated time and position of shipments beyond what can be provided by RFID fixed infrastructure technology alone.

The Contractor shall support Unit Readiness and Army deployment by providing “Over the Shoulder” support for units getting ready to deploy. Such “Over the Shoulder” activities may include, but are not limited to, “firing up” PDKs and ensuring that all items are working properly. The Contractor shall develop, present to the Government for approval, and maintain a checklist of readiness activities. The Contractor shall provide Help desk support when the physical presence of Contractor field engineers is not feasible.

Performance Management – Performance under this Task Order shall be tied to the application of penalties for failure to meet required service levels. Service Level Objectives and targets are aligned with mission imperatives, so that excellent performance toward the mission is accomplished. Any failure to achieve minimum mission standards, as set forth in Attachment 0007 – T-4 - RF-ITV Performance Standards - shall result in a reduction of the fixed price.

Superior performance on the Contractor's part will directly and indirectly contribute to superior PL LIS mission accomplishment through the economic and efficient provision of RF-ITV services and will weigh on the Army’s decision to exercise Task Order options. In addition to attaining program objectives, the Contractor is required to:

a) Consistently take steps to understand PL LIS's mission, business issues, and opportunities, and how they are supported / impacted by the services associated with this Task Order.

b) Ensure provided services deliver tangible and meaningful mission benefits.

c) Demonstrate willingness to work collaboratively with other Contractors, Government

Representatives, and business partners in achievement of all Task Order objectives.

d) Resolve the complexities and difficulties that are characteristic of implementing, integrating, supporting, maintaining, and securing the resources and services provided under this Task Order.

e) Constantly seek ways to improve the services associated with this Task Order, increase the mission value associated with those services, and decrease the costs associated with future efforts.

f) Work with Customers to increase the adoption and use of RFID technology.

g) Establish End-to-End Agile performance management and optimize for continuous improvement.

The Contractor shall develop a Quality Assurance Plan (QAP) containing the high-level program management requirements and strategies needed to ensure attributes, such as performance, system integrity and interoperability, are at levels required by the task order, and that system enhancements are capable of meeting user needs. The QAP shall identify how and when the Contractor will monitor, test, sample, evaluate and document performance, and will focus on observable or measurable aspects, such as quality and timeliness. The QAP shall address Performance Standards (PWS Section 8) and Attachment 0007.

6.2 Intent of RF-ITV Services

The overall objective of this requirement is to obtain efficient, effective, and economical RF-ITV O&M and associated services across the PL LIS enterprise to improve mission effectiveness.

The Contractor shall:

a) Provide highly reliable and affordable RF-ITV services that meet or exceed prescribed requirements.

b) Establish a cooperative working relationship with PL LIS and other Government

Contractors.

c) Continuously seek ways to improve PL LIS mission performance and reduce costs.

d) Maintain the level of service consistent with mission effectiveness. The implementation of best practices, tools, and processes has a direct relationship to the quality of the services provided, and to the indirect costs of RF-ITV.

e) Maintain a rigorous industry-standard approach to continuous improvement, process maturity and management (e.g., Information Technology Infrastructure Library (ITIL), Capability Maturity Model Integration (CMMI) or functional equivalent).

f) Maintain change management disciplines and processes, as required, to minimize adverse effects and unintended consequences of changes to the infrastructure.

g) Maintain/comply with appropriate inventory, security, quality control, interoperability, architecture standards, and reporting requirements that are in accordance with Army and DoD standards and policies.

h) Provide complete cooperation for any transition to another service provider, to ensure continuity of service in the unlikely event of Task Order termination, or upon Task Order re-competition. Required transition services will be specified in a separate transition plan, when appropriate, and the Contractor shall submit a proposal when requested by the Government.

i) Address complex IT objectives using Agile methodologies throughout the software lifecycle (plan, develop, build, test, release, deliver, deploy, operate and monitor) using continuous delivery and feedback.

7. Service Requirements The proposed methodologies, processes and capabilities should reflect proven-practices and tools, experience in Radio Frequency Identification Systems, Best Management Practices around RF Hardware and Software support, Client Relationship Management, Knowledge Management, and Techniques for Continuous Improvement. Further system detail (Operational View-1 [OV- 1], and Systems View-2 [SV-2]) is provided in Attachment 0005.

7.1 Delivery of the RF-ITV Infrastructure Services

The Government will provide the required account access for the Contractor to use Virtual Private Network (VPN), or equivalent connection, for execution of the Task Order. Other connectivity to Government systems may be authorized as required, for delivery of services within the scope of the PWS. Such connections shall be limited; used only by Contractor personnel meeting all security requirements; and based on the employee's role and need.

Where SIPRNET access is needed, the Government will provide Contractor personnel with workspace/access to the SIPRNET at a Government facility (e.g., Ft. Belvoir). Such connections shall be used only by Contractor personnel meeting all security requirements and shall be based on the employee’s role and need. The Contactor shall plan and provide for the coordination of personnel visits and the timing of work with the Government COR. The Contractor’s administrative cost (e.g., overhead) shall provide for all travel costs and time spent by the Contractor in performance of SIPRNET requirements.

The Contractor shall provide all resources for deploying, maintaining, and moving systems within each COCOM. Contractor responsibilities include, but are not limited to, Planning; Site Surveys; Impact Analysis (e.g., impact on Assessment and Authorization (A&A)); Configuration Management and Testing, Installation; De-installation, and Refresh; and Personnel Training. The Contractor shall be responsible for providing all resources (i.e., facilities, storage space, personnel, partners, Subcontractors, infrastructure, etc.) necessary to provide the full range of activities related to System Fielding and sustainment.

The Contractor shall be responsible for reviewing Government lab tested and approved interoperability test plans and test results for new products or changes to existing products introduced by third parties into the RF-ITV environment. The Contractor shall inform the Government COR of any problems encountered with implementation of new or changed existing products.

The Contractor shall provide all resources necessary to sustain O&M for products and services (e.g., 3rd Party Software, such as ORACLE and Windows updates), align standard operating practices, maintain service assurance, and provide timely reporting and management functions.

The Contractor shall be responsible for providing all resources (i.e., facilities, storage space, personnel, partners, Subcontractors, infrastructure, etc.) necessary to provide the full range of activities related to O&M of the RF-ITV Infrastructure, including, but not limited to: Moves, Adds, Changes (MACs)); Help Desk; Operating System support; Application Maintenance;

Patch Management (e.g., Application releases, OS patches, firmware updates); Asset Management; Configuration Management; Server Maintenance; and Certificate of Net worthiness.

PL LIS requires the following key performance parameters:

• RFID Infrastructure Operational Availability of 95 percent or greater on a global basis:1

• RFID readers positioned to capture one hundred percent of the business process;2

• One hundred percent Web-based access to all RF-ITV information;

• One hundred percent compliance with applicable standards (e.g., DoD

Information Standards Registry (DISR));

• One hundred percent interoperability with customer base and source base systems;

• One hundred percent maintenance of Department Risk Management

Framework (RMF) processes for the entire RF ITV system;

• One hundred percent recording and reporting Server availability; and

• One hundred percent compliance with standards and policies (e.g., National

Institute of Standards and Technology (NIST), FIPS, AR25-1, AR25-2, and

RMF).

7.1.1. Field Data Unit (FDU) Sustainment and Maintenance

The Contractor shall, at a minimum, be responsible for providing, on a quarterly schedule, all resources (i.e., personnel, partners, Subcontractors, infrastructure, etc.) necessary to manage, monitor, and perform all the following activities associated with maintenance:

a) Update or exchange outdated FDUs or components (e.g., modems, video cards, hard drives, processors, motherboards, cleaning and performing database cleanup), as necessary, and when directed by the Government COR;

b) Operating system and application test, release, and maintenance, (e.g., Windows 10 AGM/SHB-A upgrades, patches, firmware updates, Information Assurance Vulnerability Management/Alerts (i.e., IAVM, IAVA)) in accordance with Army policies and security practices;

c) Record maintenance performed into the Solutions Business Manager (SBM) Integrated Support System (ISS) Database to reflect the date the maintenance was performed;

d) Record Serial Number and Maintenance Tag Number in the SBM ISS Database with the disposition of the outdated and/or non-operational FDU.

e) Associate the replacement FDU with the historical transaction data from the replaced FDU; and

f) Properly dispose of the outdated and non-operational FDU or components in accordance with DoD and US Army supply procedures, as outlined in DoD 4160.21-M, "Defense Materiel Disposition Manual" (see referenced publications at Section 18.1 below).

7.1.2. General Configuration Management Requirements

The Contractor shall utilize and maintain the RF-ITV ISS Engineering Change Proposal (ECP) application (part of the Configuration Management function). The ECP application supports the Configuration Management Plan governance, as described in Section 7.7.1, and the ECP application is used to track all changes to the RF-ITV system configuration items.

The ECP application tracks the workflow of an ECP from submission through deployment and will be the keeper of the backlog repository.

The Contractor shall work closely with the Government to ensure that the Product Backlog, stored in ISS or JIRA, is continually and regularly maintained in alignment with the Agile cadence so that the necessary Release and Sprint Backlog items (epics, features, and user stories) are defined with acceptance criteria and prioritized by the Product Owner prior to the start of each release and sprint. The Contractor shall prioritize development in accordance with the Program Backlog.

The contractor will need to take the current ECPs and deconstruct them to develop the functionality of the EPIC, creating several features and stories including acceptance criteria for all of them. The contractor is responsible to support the maintenance of the backlog. In addition, the Contractor shall maintain the PL LIS Enterprise-Level ECP application.

Separate RF-ITV project(s) and TC-AIMS II project(s) shall be implemented and maintained within the SBM ISS ECP application, and these projects will leverage identical, duplicated workflows with tailored dropdowns, as required. If ISS Reports exist in the future, these Reports shall reflect Project Naming consistent with the SBM ISS applications.

7.1.3. General Server Outage Management Requirements

The Contractor shall utilize and maintain the RF-ITV ISS Server Outage Management application to create scheduled and unscheduled server outage tickets, with associated notifications to PL LIS, that provide the affected service, outage description, date, duration, and root cause, if applicable. In addition, the Contractor shall maintain the PL LIS enterprise-Level Server Outage Management application currently utilized by the TC-AIMS II program.

The ISS Reports shall also be updated to reflect Project Naming consistent with the SBM ISS applications.

7.2 Software Operations & Maintenance and Application Development The government has adopted Agile framework to plan and execute work for the development, operations, and maintenance of the RF-ITV system including RF-ITV Portal, TIPS Read, TIPS Write, and SBM ISS. This includes the ability to plan incrementally, visualize the progress of capabilities being released to users, and adjust the work in progress based on user feedback, team predictability or other arising circumstances that warrant adjustments to plans. The contractor shall be accountable for the continuous integration and delivery (CI/CD) of the working product developed. CI describes the concept of integrating smaller pieces of code and functionality more frequently to allow teams to integrate and validate changes. As a result, the team benefits from a consistent, repeatable, and automated way to build, package, and test code. CD is the next step in terms of delivering the application in a consistent, repeatable, and automated manner to specific environments and includes continuous monitoring.

High-functioning teams shall include contractor resources partnering with PL LIS product owners to conceptualize, plan, and execute IT solutions that meet business goals and deliver measurable value to the users. The team shall work toward standardizing and automating as much as possible to help reduce human error. Team success in delivery of business capabilities is measured and documented in metrics, and adherence to critical standards and policies. Work shall meet the Program Increment (PI) objectives in a manner that does not negatively impact system performance or availability.

The synchronization of Agile plans, iteration objectives, and team workload will be reviewed during the Agile Program Increment Planning Events which shall be held every 10-12 weeks. .At the end of a PI period, the contractor should be tracking the collection of data associated with releases, features, capabilities, and stories. The definition of “done” associated with the story shall identify the requirement that must be demonstrated to be considered complete and accepted. The contractor should support the implementation for continuous and automated testing across the software development lifecycle including plan, develop, build, test, release, delivery, deploy, operate, and monitor when possible. Automation enables consistent and repeatable testing, security, integration, delivery, and deployment practices throughout the delivery pipeline.

Transportation In-Transit Visibility Processing Software (TIPS) deployed on (Total Asset Visibility Operational Prototype (TAVOP)) and In-Transit Processing Stations is the Government-owned RFID Node management software that provides Web-Enabled Server Based Software Application Development, and other Application Development capabilities.

All applications, source code, documentation, models and processes developed are the property of the Government. At the termination of the Task Order, the Contractor shall provide PL LIS this information in a format that is compatible with the Government’s requirements (e.g., relational database format, documented applications, Standard Operating Procedures, etc.).

Contractors shall be familiar with, and follow, the Network Enterprise Center (NEC) policies regarding remote management and the ability to “push” software changes across the network.

The Contractor shall be responsible for maintaining the Government-owned RFID transponder reading and writing application, currently TIPS. The Contractor shall be responsible for software maintenance methodologies and for providing all resources (i.e., personnel, partners, Subcontractors, infrastructure, etc.) necessary to manage, monitor, and perform all activities associated with TIPS and Web-Enabled Server Based Software Application(s). The Contractor is responsible for all basic TIPS and Web-enabled Server Based Application changes to include updates to web services, patches, security updates, interface modernizations, software upgrades, etc.

The Contractor shall conduct integration testing of commercial off-the-shelf RFID hardware and software, to include testing of technology for optimized solutions (e.g., power and communications hardware that would enable operations of RFID nodes in an austere environment).

The Contractor shall be responsible for maintaining the Government owned RF-ITV System.

The Contractor shall be responsible for System Software Engineering, Data Management, Web- Enabled Server Based Software Application Development, implementation/modernization of Web Services with data partners, and other Application Development capability. The Contractor shall be responsible for providing all resources (i.e., personnel, partners, Subcontractors, infrastructure, etc.) to design, test and implement a fully integrated database. The Contractor shall also be responsible for providing all resources (i.e., personnel, partners, Subcontractors, infrastructure, etc.) necessary to manage, monitor, and to perform all activities associated with Web Enabled Server Based Software Application Support and maintenance.

7.3 RFID Tools and Reporting

The Contractor shall be responsible for providing all resources (i.e., personnel, partners, Subcontractors, infrastructure, etc.) necessary to provide the full range of processes and technologies that involve planning, development, implementation, capacity management, and administration of systems for the acquisition, storage, and retrieval of data, and reports used in asset management and business intelligence. The contractor shall utilize status reporting in accordance with Agile framework and methodology in accordance with CDRL A012.

The Contractor shall protect the Government’s interests and safeguard Government software, assets and resources against inappropriate or unauthorized use and disclosure of information. All data and property are the property of PL LIS in accordance with the data rights clauses in the Task Order or the ITES-3S contract. At the termination of the Task Order, the Contractor shall provide PL LIS this information in a format that is compatible with the Government’s requirements (e.g., template formats, automated report generation routines, relational database format, source code tree, etc.).

The Contractor shall be required to provide standard periodic reports and ad hoc reports using Government systems. PL LIS uses the Micro Focus SBM tool that provides the framework for several Integrated Support System (ISS) collaborative applications that have been custom built to assist with the management and execution of the RF-ITV program.

These RF-ITV ISS applications currently provide the following collaborative functions:

• Engineering Change Proposal (also known as Configuration Management),

• Mission Matrix,

• Service Management,

• Asset Management,

• PL LIS Service Desk,

• Site Management,

• Interrogator Management,

• Server Outage Management,

• System Administration Management,

• Training Development, and

• ISS Administration.

Projected funding (by Government Cost Center) is placed on the Task Order at the start of each Option Period. At times, incremental funding by PL LIS and the various Customer organizations may be necessary. When incremental funding is necessary, the PLLIS will work with Customers to ensure funding is placed on Task Order in time for the “live” missions to occur.

The Contractor shall also leverage the RF-ITV SBM ISS application best practices to develop and maintain the SBM collaborative functions across the PL LIS enterprise (segregated by program/project). The following applications are to be established and maintained:

• Configuration Management (also known as Engineering Change Proposal),

• Asset Management,

• PL LIS Service Desk, and

• Server Outage Management.

All four of these enterprise-level applications, shall contain the user-specific roles by application and project as defined by PL LIS.

PL LIS also uses a custom built ISS Reporting capability (written in Python) for business reports and distribution list email notifications. Utilizing these reporting tools, the Contractor shall maintain and develop reports to a level of detail and in a format specified by PL LIS include the appropriate reports for the enterprise-level PL LIS Service Desk application. All reports provided by the Contractor systems shall be in a web accessible format (i.e., XML) that can be easily manipulated, printed or saved in an Excel, PDF or Power Point format.

This Task Order requires the management and control of costs and expenditures for FFP and Cost Reimbursable Contract Line Items (CLINs) and Sub-Line Items (SLINs). In addition, current Task Order reporting is configured to specific CLINs and SLINs for each Government Cost Center, and the Contractor shall provide monthly invoicing and financial management at these levels. The Contractor shall reconcile reports between ISS and the Task Order Pricing. However, because funding is provided to PL LIS and subsequently awarded to the Contractor on individual SLINs, corresponding to various funding sources; the Contractor shall track and invoice based on discrete funding by SLIN, Global Operation locations, number of nodes, and by the available funding from the various funding sources (i.e., PL LIS ARCENT/1st TSC, AFCENT, Air Force, Navy, USMC, DLA, SDDC, and occasionally others) for Maintenance, Survey, Install, De-Install, and Training activity. This is a complex process and requires several checks and balances at various levels between the Contractor, PL LIS, and Government Contracting Center personnel to ensure work is performed in accordance with the funding source available.

The Contractor shall be responsible for providing all resources (i.e., personnel, partners, Subcontractors, infrastructure, etc.) necessary to manage, monitor, and perform all activities associated with report production and management. The Contractor shall be responsible for the configuration and maintenance of the SBM ISS applications and shall also load the application data from the associated ISS database tables.

The Contractor shall maintain the RF-ITV SBM ISS and ISS Reporting functions (minimum of two FTEs). The enhancement of new functionality to evolve the SBM ISS and Reporting capabilities for enterprise-level PL LIS use shall be accomplished as a RF-ITV Support Project, as defined in Section

7.6 below. SBM Training will not be required, but the Contractor shall be required to document and update the current SBM artifacts when changes are made to the system configuration or processes. SBM documentation updates to the existing ISS applications/reports shall be part of the on-going FFP maintenance activities, but new documentation required as part of implementing ISS applications/reports shall be part of the RF-ITV Support Project defined by PL LIS the Contractor.

7.4 Contractor Travel and Other Direct Costs (ODCs)

The Contractor shall be responsible for abiding by Joint Travel Regulation (JTR) and ODC requirements, when such costs are not included within the Firm Fixed Price or Fixed Unit Price CLINs and SLINS.

7.4.1. Contractor Travel:

As part of performance under this PWS Contractor Travel shall be included in the Contractor’s Fixed Price of each Contract Line Item, except where additional travel is directed by the Government and is outside the Contractor’s fixed price responsibilities (e.g., maintenance of RF- ITV infrastructure, training, etc.). During these instances, the Contractor will be authorized travel expenses consistent with the substantive provisions of the JTR and, if required, the Per Diem Supplement to Standardized Regulations (Government Civilians, Foreign Areas), JTR Section 925, “Maximum Travel Per Diem Allowances for Foreign Areas” (for travel not covered in the Federal Travel Regulations or Joint Travel Regulations). All travel requires COR notification and Government approval in advance. The Contractor shall furnish the detail vouchers/invoices to Government for all such costs incurred each month.

7.4.2. Other Direct Costs:

ODCs, when approved by the Government and incurred by the Contractor in performance of tasks, will be reimbursed by the Government. The Contractor shall obtain prior approval from the COR for micro purchases (currently $10K or less), and the Contracting Officer’s approval for all purchases over the micro purchase level. Only actual costs for ODCs that are supported with detail sufficient for the Government to verify that costs are reasonable and in performance of tasks will be reimbursed.

The Contractor is authorized to make emergency purchases in the performance of tasks and will be reimbursed by the Government. Only actual costs that are supported with detail sufficient for the Government to verify that costs are reasonable and in performance of tasks will be reimbursed. The Contractor shall furnish the detail vouchers/invoices for all emergency purchases on a monthly basis to the Government. Emergency purchases are authorized for the purchase of expendable parts, tools, supplies, or equipment for existing parts, RFID Interrogators, Field Data Units and communications equipment to support the installation and/or maintenance of RFID sites in support of RF-ITV infrastructure. Individual purchases will be limited to $400 per purchase and will not exceed $4,000 per year during the Base and four 12- month Option periods. Total NTE cost for the Base Year and four 12-month Option periods will be $20,000. These emergency purchases are in support of the requirement to maintain a 95percent Operational Availability rate as specified in Section 7.1 of this document.

NOTE: Contractor’s costs (e.g., housing allowance, cost of living allowance, transportation, communications, and other costs) are not reimbursable as ODCs, and shall be included in the appropriate FFP or Fixed Unit Price CLIN(s). PL LIS will not be responsible for any relocation costs incurred by the Contractor for moving their employees working world-wide locations. See PWS Section 12 for further requirements.

7.5 General PL LIS Service Desk Requirements

The Contractor shall be responsible for providing tiered levels of support to include the following:

• Responding to general inquiries, and

• Responding to specific questions concerning RF-ITV and related products or services (e.g., TC-AIMS) and support.

Service desk support shall be made available 24 hours per day, 7 days per week through live contact, e-mail, and webchat. Contractor service desk personnel shall log all calls and offer triage services on first contact, provide warm handoff transfer capability, monitor service levels, and provide callback or escalation on open tickets. The service desk shall handle all tickets to closure and submit reports on the disposition made, with time taken for completion, to the PL LIS program office.

The Contractor shall use SBM Integrated Support System (ISS)3 for logging calls and tracking status through the life cycle of the incident/problem management process. Support inquiries may originate from non-ITV areas (e.g., TRANSCOM, TC-AIMS, Write Node application owner, etc.). Note: Facilities for walk-in support are not required.

7.5.1. Tier I Help Desk Support

The Contractor shall provide Tier I support to resolve all questions and issues related to system availability and access, and specifically:

• Enterprise Account Creation (requires completed DD Form 2875 [System Authorization Access Request] submission from user),

• Enterprise Account Password Resets,

• Enterprise Account Modifications,

• Unlocking of locked Enterprise accounts, when appropriate,

• Responding to and distributing PL LIS Software requests for Standalone Laptops,

• Directing users to PL LIS Interactive Multimedia Instructions (IMIs) training files, and

• CAC Login Process.

As part of providing this support, the Contractor shall report and manage incidents from inception through problem resolution.

The Government will provide Contractor help desk analysts with the appropriate system accounts with administrative privileges to perform the required Tier 1 tasks (e.g., establish/maintain user accounts, etc.), and PL LIS will provide GFE for direct support of the PL LIS Service Desk with the appropriate Operating System and software to provide access to the ITV systems.

The Contractor help desk analysts shall also be provided specific ITV System training (e.g., TC AIMS) from the appropriate PL LIS personnel on the use of the application and the associated tools necessary to implement the specified Tier 1 functionality.

Metrics related to all tickets handled by the PL LIS Service Desk shall be reported.

7.5.2. TC-AIMS II ISS Application/Reporting Enhancements

This task requires the implementation of the established PL LIS/Contractor Requirements Definition, Design, Development, Documentation, and Test processes as defined by the RF- ITV Configuration Management Plan. The ISS Reports shall also be updated to reflect Project Naming consistent with the SBM ISS applications.

7.6 RF-ITV Support Projects

Support projects may be requested at the option of the Government. Support projects shall not commence without Government authorization to proceed and shall require a detailed proposal showing an outline of development activities and Rough Order of Magnitude (ROM) estimates.

The Contractor shall be responsible for providing all resources (i.e., personnel, partners, Subcontractors, infrastructure, etc.) necessary to manage, monitor, and to perform all activities associated with support projects, such as:

• Incorporating Active RFID technology into the RF-ITV system (e.g., Installing Active RFID capabilities on Power Projection Platforms (PPP));

• Enhancing Definition, Engineering, Logistics and Management Support (DELMS) Transactions and Securing Automated Ship notices;

• Supporting contingencies (i.e., Operation Resolve);

• Supporting major COCOM exercises as directed;

• Supporting Cybersecurity projects;

• Supporting North Atlantic Treaty Organization (NATO) and Coalition Partner requirements;

• Adhering to American National Standards Institute (ANSI) and International

Standards Organization (ISO) product compatibility;

• Supporting Foreign Military Sales projects; No Foreign Military Sales will be performed in the republic of Korea;

• Supporting Joint Urgent Operational Needs Statement projects; and

• Supporting NIPR projects.

7.7 Management Support

The Contractor shall be responsible for Management of the Task Order and any associated tasks, Projects, and performance. Management activities include programmatic functions (e.g., Contract Management, Human Resource Management, Performance Management, Financial Management, Quality Assurance, Monthly In-Process Reviews, etc.), Daily Reports (i.e., logistical and technical support to the Contractor’s operations, Back Office Support (e.g., cost, finance and accounting) to the Contractor and its resources (e.g., Personnel, Subcontractors, Vendors), and Customer Relationship Management.

The contractor shall ensure the team develops a deep understanding of Agile and is continuously improving the Agile model for PL LIS. They shall ensure End-to-End Agile governance is optimized with a focus on both speed, security and high quality. PL LIS’ desire to support its user base more effectively is to move to a more Agile organization at all levels and support individual contributors, teams, and leaders to embrace the changes needed to do so.

The Contractor shall provide technical specifications, configuration data, and detailed information for the existing RF-ITV system to include hardware, software, database, networking, and security for current development, testing, and production environments. The Contractor will provide operational support and continuous integration/continuous delivery (Cl/CD) services post migration to meet mission requirements.

When required, the Contractor shall participate in Technical Interchange Meetings (TIMs) and other working groups established by the Government. The Contractor’s participation in TIMs within the National Capital Region (NCR), including travel to PL LIS’ NCR facilities (currently located in Ft. Belvoir, VA) shall be covered within the Contractor’s overhead (historically monthly). Any long distance travel requires prior approval from LIS Contractor will assume approximately 49 TIMs per year. These TIMs break-down into the following meeting categories:

Technical Interchange Meetings (TIMs) No. of TIMs Total TIMs per Year

DISA Technical Meetings 2 per month 24 Cyber Security Technical Meetings 1 per month 12 Technical Road Map Update Meetings 2 per year 2 Customer Interface Meetings 6 per year 6 RF-ITV Program Increment (PI) Planning Every 10-12 weeks 5 max

TIMs are approximately one to two (1-2) hours in duration, require agendas to be furnished, notes to be taken, and action items captured, assigned, and tracked between meetings.

The PI Planning events are necessary to help synchronize, collaborate, and align workflows and objects. These events are approximately two days and allow Product Owners to work to prioritize the planned features for the increments ahead, development teams to own user story planning and estimation, and Engineering team works to validate the planning.

7.7.1. Configuration Management Plan

The Configuration Management Plan (CMP) is an PL LIS managed plan and shall coordinate and reflect all changes to the hardware, Operating and Systems Software, Application Software releases, and site configurations. The CMP details how PL LIS analyzes, allocates responsibility, and identifies and maintains the configuration of all devices and work products (to mean baselines, as well as other supporting work products). The CMP systematically controls changes and maintains the integrity and traceability of all work products throughout the program lifecycle. The Contractor shall support PL LIS with annual updates to CMP to reflect changes in practices and configuration items.

7.7.2. Government Furnished Property Policies and Procedures Plan Government Furnished Property (GFP) and Contractor Acquired Property (CAP) shall be maintained and controlled in accordance with Attachment T-14 RF-ITV IV Government Property Procedures. Government Property supporting the RF-ITV IV Program shall be added to and managed in the SBM-based ISS Asset Application, the PL LIS property system of record.

Property shall be maintained, tracked, transferred, inventoried, and processed for disposal in ISS following the established PL LIS process. GFP is recorded in Attachment 0006 - RF-ITV IV GFP Module Attachment.

7.7.3. General Asset Management Requirements

The Contractor shall utilize and maintain the RF-ITV ISS Asset Management application to manage and track all Government-owned equipment and property used throughout the RF-ITV IV Program. RF-ITV Government property is received, assigned, shipped, returned, and disposed of in accordance with the PL LIS Government Property Policies and Procedures document. In addition, the Contractor shall maintain the PL LIS enterprise-Level Asset Management application currently utilized by the TC-AIMS II program.

Separate RF-ITV project(s) and TC-AIMS II project(s) shall be implemented and maintained within the SBM ISS Asset Management application, and these projects will leverage identical, duplicated workflows with tailored dropdowns, as required. The ISS Reports shall also be updated to reflect Project Naming consistent with the SBM ISS applications.

7.8 Cyber Security (Sustainment)

The Contractor shall be responsible for the auditing, analysis and analytics, and programmatic support necessary to ensure the security and functional performance of the RF-ITV system.

Sustainment activities shall include, but are not limited to:

• Performing NIPRNET Administration, to include performing maintenance on the

Sensitive Unclassified NIPRNet enclave.

• Accessing the NIPRNet enclaves for Risk Management Framework (RMF)

Enterprise Mission Assurance Support Service (eMASS); and

• Responding to ‘taskers’ affecting NIPRNet operations (e.g., collecting and evaluating system security; collecting and evaluating performance data for compliance with the standards cited within this document; and maintaining assessment and authorization, full hardware and software inventory, system documentation and architecture, and functional description).

New work activities shall include, but are not limited to: user surveys, impact…