Attachment_0001_LOGAUTO_PWS.pdf

Performance Work Statement

Unclassified

PERFORMANCE WORK STATEMENT (PWS)

LOGISTICS AUTOMATION SUSTAINMENT AND MANAGEMENT

07 April 2017 (Revised)

Task: Logistics Automation Sustainment and Management

1.1 BACKGROUND:

1.2 USARCENT G4 Logistics Automation is the lead agency responsible for automated logistical support to the Army Forces deployed to Southwest Asia. 1st Theater Sustainment Command (1st TSC) Logistics Automation Branch provides materiel support and integration of Logistics Information Systems (LIS) in Theater. Personnel with specific subject matter expertise in Information Assurance (IA) and key logistics systems – supply, ammunition, and logistics command and control – are required to properly design and implement this architecture. These personnel are needed to provide IA compliance guidance, automated logistical support, technical training and assistance to subordinate logistics commanders’ staff and Sustainment Automation Systems Management Offices (SASMOs). LISs are a family of automated logistics, maintenance, and analysis systems that are managed by CECOM Program Executive Office – Enterprise Information Systems (PEO-EIS) and for the purposes of this contract consist of:

Standard Army Maintenance System – Enhanced (SAMS-E) Standard Army Ammunition System- Modernized (SAAS-MOD) Property Book User System- Enhanced (PBUS-E) Unit Level Logistics System- Aviation (Enhanced) (ULLS-A (E) Combat Service Support Automated Information Systems Interface (CAISI) Medical Communications for Combat Casualty Care (MC4) Global Combat Support System-Army (GCSS-A)

1.3 The SASMO provides customer assistance for the Army’s LISs, including software, functional, technical, communications and limited hardware. The SASMO also provides training evaluation to unit personnel and staff assistance on the use and implementation of LISs throughout the command. 1st TSC requires contracted support to augment the SASMO infrastructure within the Theater. This requirement is critical for efficient support to all operations and activities in the ARCENT AOR.

2.0 OBJECTIVES OF THE PERFORMANCE WORK STATEMENT (PWS):

The purpose of this Performance Work Statement (PWS) is to task the contractor to provide the following deliverables and to perform the following tasks as delineated within this PWS to the 1st TSC, USARCENT and its supported Commands.

3.1 SCOPE: Major Levels of Effort:

• Contract Level Management, 4.2

• Management Plan, 4.2.3

• LIS Information Assurance and Automation Architecture, 4.3

• LIS Maintenance Services, 4.4

• LIS Support Services, 4.5

• Theater Provided Equipment (TPE) Property Book Office, 4.6

• Project Management and Logistics Operations, 4.7

• Logistics Automation Operations and Integration, 4.8

• LIS Training Services, 4.9

• Medical Communications for Combat Casualty Care (MC4), 5.0

4.0 SPECIFIC TASKS:

4.1 Period of Performance: 1 December 2013 – 30 November 2014 base, and two (2) Option Years.

4.2 Contract Level Management: Participate in periodic command and staff conferences and organizational meetings. Submit updates to provide contract status and logistics automation, SASMO, and LIS management information to the Contracting Officer’s Representative (COR) as required.

4.2.1 Within 5 days of award of the contract, the incoming contractor will submit to the COR a Transition Project Plan that describes how the contractor will assume responsibilities from the outgoing contractor. The Transition Project Plan will include, but is not limited to tasks and timelines for travel to the USARCENT AOR, timing of when incoming contractor personnel will have full sponsorship with a Kuwaiti sponsor, a schedule of when personnel will assume their specific responsibilities, a schedule of transition meetings with the outgoing contractor, a schedule of joint inventories of Government Furnished Equipment (GFE), and any other tasks required for a seamless transition between the incoming and outgoing contractor.

4.2.2 The contractor will provide to the COR no later than (NLT) the 5th of each month a report of the technical and functional activities described in the Contract Management Scorecard. This report, in a format to be jointly agreed to by the COR and contractor within the first 30 days of the start of this PWS, will be used as one method to assess the contractor’s success in meeting the provisions of this PWS.

4.2.3 Management Plan: Within 30 days of the start of this PWS, or on a date agreeable to both the contractor and the COR, the contractor will submit a General Management Plan to the COR describing the following sub-plans and processes:

4.2.3.1 Support Processes - A detailed set of process definitions, using basic or cross-functional notation that describes how the contractor will generally support the SASMO customer base. This sub-plan will include, but is not limited to, process definitions for

Helpdesk Operations, Hardware Evacuation Procedures, Remote Troubleshooting and Diagnosis, Preventive Maintenance and Site Visit Procedures.

4.2.3.2 Technical Approach - A subset of the Support Processes, the Technical Approach will describe a systemic approach for analysis, diagnosis and remediation of LIS hardware, software and communications problems.

4.2.3.3 Quality Control Plan - A methodology based plan using industry recognized quality improvement approaches, such as Lean Six-Sigma that describes how the contractor will improve customer service over the life of the contract. The Quality Control Plan will include activities to improve both the Support Processes and Technical Approach and should address these topics in terms of cost, scalability and efficiency of the processes. The Quality Control Plan will be provided to the KO within 60 days of the award for acceptance.

4.2.3.4 Organizational Resources - A sub-plan describing how the contractor will execute human resources management, to include staffing, vacation/time off, leaves of absence and backfill of vacant positions. This sub-plan will also include a documented management and chain of command structure for the contractor personnel.

4.2.3.5 Project Management Controls - A sub-plan describing how projects will be initiated, planned, executed and closed. This will also include a risk management strategy.

4.2.3.6 Cost management plan tracking performance throughout the contract execution.

4.2.4 The contractor will provide a monthly status report submitted to the COR by the 10th of each month, in a format to be agreed jointly by the COR and the contractor, monitoring the following:

4.2.4.1 Quality Control Plan, including specific improvement initiatives.

4.2.4.2 Organizational Resource Status that will include projected gains, losses, anticipated backfills against vacant positions, schedules of leave, and training.

4.3 Logistics Network Information Assurance (IA) Architecture Management:

4.3.1 The contractor will coordinate between 1st TSC, ARCENT, higher and parallel headquarters and commands (i.e., FORSCOM, CENTCOM, AMC, DLA, USFOR-A, and HQDA) on all LIS IA and network issues. The contractor will recommend IA and logistic network policies and develop implementing plans and procedures. This will ensure that the Theater logistics automation architecture supports command operational plans.

4.3.2 The contractor will provide LIS IA compliance and trend analysis reports to USARCENT G4, 1st TSC Logistics Automation Branch Chief, and COR bi-weekly.

The reporting day will be determined by the 1st TSC Logistics Automation Branch Chief.

4.3.2.1 The contractor will oversee and ensure all updated Government software (Program Executive Office for Enterprise Information Systems (PEO EIS) and SEC-Lee approved), vendor patches and anti-virus software are pushed down to end-user LISs operating systems and CAISI SSR Notebooks with 95% compliance. The contractor will accomplish this task within 30 days of updated software, vendor patches or anti-virus software being released by PEO EIS. The 95% IA Vulnerability Alert (IAVA) patch compliance applies to all systems in the CENTCOM AOR.

4.3.2.2 The contractor will conduct a bi-weekly IA and network architecture teleconference with supporting communications staffs, units and agencies to ensure LISs are integrated into communication requirements and to derive and execute plans to resolve connectivity and network security issues as they arise.

4.3.2.3 The contractor will maintain and update the Theater Standard Network Architecture Smartbook and distribute it to the Theater Sustainment Command (TSC) and subordinate units’ IA nodes to ensure command and control requirements remain consistent across the theater logistics automated network. The Smartbook will be updated NLT 5th of each month.

4.3.2.4 The contractor will establish and maintain theater logistics network architecture diagrams. The architecture diagrams will include LISs virtual local area networks (VLANs), virtual private networks (VPNs), and hard-wired LIS LANs and wide area networks (WANs). The diagrams will be updated NLT 5th of each month and posted on the USARCENT SharePoint portal or as directed by the 1st TSC Logistics Automation Branch Chief.

4.3.3 The contractor will coordinate with Product Manager (PM) Defense Wide Transmission Systems (DWTS) to ensure Very Small Aperture Terminal (VSAT) and CAISIs are providing constant network connectivity to the AOR. A 95% operational readiness rate is the standard. The contractor will develop and maintain a comprehensive database for all TPE VSATs and CAISIs consisting of internet protocol (IP) address, location, unit, major subordinate command (MSC), point of contact (POC), LISs attached, and daily connectivity status. The database will be updated on a weekly basis.

4.3.4 The contractor will be responsible lifecycle management of all TPE LIS Computers equipment on the NIPR and VSAT Networks. The contractor will assist units with lifecycle requirements for ORG LIS equipment. The contractor will maintain a current computer database (Excel or Access) of all LIS computers (at a minimum, the database will include serial numbers, , Unit/Command, and POC).

4.3.5 Experience: The contractor will have an employee Information Assurance Level I certified IAW Army Regulation 25-2, Information Assurance, and DOD 8570.01-M, Information Assurance Workforce Improvement Program. The contractor shall have at least two years experience working directly with DOD IA networks, policies, plans, procedures, and IA Vulnerability Management (IAVM) programs.

4.4 LIS Maintenance Services:

4.4.1 The contractor will analyze LIS and CAISI performance (hardware and software) across the Theater. For the purpose of this contract, LISs include the, Standard Army Ammunition System – Modernized (SAAS-MOD), Property Book User System- Enhanced (PBUS-E), Standard Army Maintenance System- Enhanced (SAMS-E), Unit Level Logistics System- Aviation (Enhanced) (ULLS-A(E), CAISI (Combat Service Support Automated Information Systems Interface) and Medical Communications for Combat Casualty Care (MC4).

4.4.2 The contractor will recommend policies and plans for LISs maintenance and support for the CENTCOM AOR as defined by USARCENT customer units (both assigned and supported units).

4.4.3 The contractor will provide subject matter expertise in LISs and CAISI for support of the same. Contractor personnel must have a minimum A+, Security+, and achieved a minimum skill level 30 on LISs and CAISI platforms in order to train personnel and troubleshoot system problems (provide Tier 1 & 2 support for CAISI). Each contractor personnel must be able to teach, operate, and troubleshoot multiple LIS platforms and CAISI in order to teach and perform duties outlined in this PWS. At least one (1) contractor personnel must be qualified for an IAM1 accreditation.

4.4.4 The contractor will ensure that users and unit SASMOs are conducting system preventative maintenance on every LIS computer on a routine basis. The routine period will be determined in coordination with the 1st TSC LOG-Auto Branch Chief. This includes, but is not limited to:

• Ensuring that system is set up in a dry, cool space, with adequate ventilation, not exposed to the harsh elements found in Southwest Asia (SWA).

• Clean exhaust fans and air intake vents and ensure they are free from blockages using lint-free cloth to clean dust.

• Check the system voltage setting before plugging in or powering the system up.

If running the system off generators, have a generator mechanic check the power output and phases. Ensure customers are using line conditioners, surge protectors and voltage regulators.

• Ensure customer maintains CDs/DVDs in some type of dust protective container.

Recommend to the customer the CDs/DVDs should be replaced quarterly.

• Ensure that all cables are connected correctly on customer computer systems.

• The contractor will document each LIS handling and maintain a database.

Updates will be provided to COR NLT 5th of each month.

4.4.5 The contractor will be able to perform complete LIS rebuilds for these systems:

• Standard Army Maintenance System - Enhanced (SAMS-E)

• Standard Army Ammunition System - Modernized (SAAS-MOD)

• Property Book and Unit Supply- Enhanced (PBUS-E)

• Unit Level Logistics System- Aviation Enhanced (ULLS-A(E)

• CAISI SSR Notebook

• Medical Communications for Combat Casualty Care (MC4)

A LIS rebuild includes base-lining the LIS computer with all software required to return the LIS computer to full operational capability. The contractor will provide a process for rebuilding LISs NLT 30 days after start of PWS.

4.4.6 The contractor will purchase cables, adapters, and other miscellaneous parts as required to support LISs. The purchases must be preapproved by the COR and they will be reimbursed on the monthly statement up to a maximum of $10,000 per year.

4.5 LIS Support Services:

4.5.1 The contractor will provide system and technical support for LISs and CAISI's operating in the CENTCOM AOR. This will include monitoring system performance to identify trends, prevent system failures, and identify potential areas for improving LIS availability, reliability, and maintainability. This subtask shall be accomplished by, but not limited to, the following activities:

4.5.1.1 Systems Monitoring:

• Reviewing system log files while conducting maintenance support and training visits

• Reviewing and analyzing trend data gathered during maintenance, support and training visits

• Responding to system alerts and notifications from Software Engineering Center-Fort Lee, VA (SEC-Lee) and PEO EIS

• Responding to network notifications from installation and camp Network Enterprise Center (NEC), and the Very Small Aperture Terminal (VSAT) helpdesk

4.5.1.2 Trend Reporting:

• Contractor will prepare and submit to the COR a System Analysis and Trend

Report prior to the 5th day of each month

• Trend report will contain the following information:

a) Number of systems diagnosed this period (monthly)

b) System Type

c) System Issue (Hardware failure, software error, communications failure, data error)

4.5.1.3 Length of System Outage or Problem:

• Time to repair

• Average number of visits required to solve problem

• Training status of operator (Trained/Untrained)

• Number of repeat visits to the same unit, listed by unit, by system, by problem

• Supported system availability percentages

• Identified LIS maintainability issues

4.5.1.4 Corrective Actions:

• Perform replacement of defective hardware components

• Restore application software to operating condition per applicable software version descriptions

• Apply approved patches from SEC-Lee as directed by PEO EIS or the Customer

Assistance Office (CAO)

• Coordinate with installation and theater Forward Repair Activities (FRA) for repair of LIS hardware

4.5.2 The contractor will provide support six days per week, on-call seven days a week with a response (call back customer) telephonically within two hours (including holidays, both U.S. and Local government). Based on workload or during periods of surge conditions, the contractor may be required to provide support for up to 72 hours per week. Physical response to customer site will be made within four hours in Kuwait and within 72 hours for critical problems as defined by the 1st TSC Log Auto Branch Chief in the remainder of CENTCOM AOR (unless constrained by force protection and transportation availability. During scheduled class training for SAAS-MOD, SAAS-MOD will be excluded from telephonic response (call back customer) time limit. The contractor will provide the COR with an accountability sheet within 2 hours of COB every Saturday.

The format of the accountability sheet will be agreed upon between the COR and PM.

4.5.3 Software Change Testing and Deployment: The contractor will validate all Software Change Packages (SCP) and Interim Change Packages (ICP) for all LISs, CAISI and MC4 systems.

4.5.3.1 The contractor will develop a testing and deployment Concept of Operations (CONOPS), approved by the 1st TSC Logistics Automation Branch Chief, for each new SEC- Lee released SCPs/ICPs. The CONOPS will be submitted to the 1st TSC Logistics Automation Branch Chief within seven calendar days after SCP/ICP release.

4.5.3.2 Testing will be completed within 14 calendar days of receipt of SEC-Lee released SCP/ICP. Testing will be conducted replicating as many existing scenarios in the CENTCOM AOR as possible (i.e., Lab, LAN only, LAN and VSAT, and VSAT-only network connectivity; conduct tests using copies of actual data from a warehouse or unit using the LISS being tested). The test results will be documented and reported in accordance with the testing and deployment CONOPS outlined in paragraph 4.5.3.1 above. The report will be submitted to the 1st TSC Logistics Automation Branch Chief within three calendar days after test completion.

4.5.3.3 The SCP/ICP deployment will be initiated at least 30 days after the PEO EIS release of a SCP/ICP and approval by the ARCENT G4 or 1st TSC Logistics Automation Branch Chief. The contractor will visit sites to load SCPs/ICPs as directed by the 1st TSC Logistics Automation Branch Chief and coordinated with the COR.

4.5.3.4 This subtask includes establishing a Quality Assurance (QA) Laboratory on-site in Kuwait that the contractor will use for SCP and ICP validation. The Quality Assurance Laboratory will contain a LIS Test Suite with the latest PEO EIS approved hardware and software for each of the LISs listed in Section 1. Even in the absence of a separate / stand-alone Test Suite/Building, the contractor is still responsible for using the best resources available to conduct testing.

4.5.3.4.1 The contractor will use this Test Suite to analyze the impact of LIS changes on other LISs, analyze customer data to replicate system and data errors, and to test LIS configurations in support of theater LIS data flow and reporting requirements.

4.5.3.4.2 The Government will be responsible for providing GFE for the Quality Assurance Laboratory as required.

4.5.3.4.3 The contractor will be responsible for preparing formal testing and configuration reports for each system analyzed or problem tested in the Quality Assurance Laboratory. These reports may, as a minimum, be the description of problem and description of resolution entered into the contractor’s service desk ticketing system.

The test results will be documented and reported in accordance with the testing and deployment CONOPS outlined in paragraph 4.5.3.1 above. The report will be submitted to the 1st TSC Logistics Automation Branch Chief within three calendar days after test completion.

4.5.3.4.4 The format of these reports shall be mutually agreed upon by the contractor and the COR. The contractor will forward the report to the COR for reference to SEC- Lee for future SCP and ICP upgrades.

4.5.3.5 The contractor will follow industry best-business-practices for software configuration management documentation and tracking. The standard will be agreed upon between the contractor, 1st TSC Logistics Automation Branch Chief and the COR.

4.5.3.6 The contractor will write messages, and plans, as necessary, to inform the AOR of the SCP/ICP deployment and execution plan.

4.5.4 Site Visits: The contractor will visit sites to provide recurring scheduled customer assistance visits in addition to site visits requested by the unit. This will be coordinated through the PM and approved by the COR. The contractor will prepare a quarterly customer assistance visit schedule, submitted to the COR within the first 60 days from the start of this PWS, containing the initial visit schedule and a schedule for every 90-day period thereafter. Scope: CENTCOM AOR.

4.5.5 CAISI Network/”CAISI Cloud”

4.5.5.1 Establish and maintain a CAISI network to which all Logistics Information Systems (LISs) can connect. LISs that will be authorized use of this network consist of SAMS-E, PBUSE, SAAS-MOD, GCSS-A, and ULLS-A(E)

4.5.5.2 Theater SASMO will maintain a MAC filtered ACL for LISs residing on the CAISI Cloud.

4.5.5.3 Theater SASMO will assist in adding new CAISI Client Modules to the network.

4.5.5.4 Theater SASMO will assist units in configuring LISs for use on the network.

4.5.5.5 To ensure continuity of operations additional CAISI devices will be configured with one as an active failover.

4.5.6 LIS Employment: The contractor shall develop, modify and provide training material and services as required by the COR to meet employment of LISs in the AOR.

4.6 Property Administration and Accountability Service:

4.6.1 The contractor will develop and publish guidance for the establishment of supply procedures, conduct of supply operations and the safeguard of LIS government property listed on the Theater Provided Equipment (TPE) property book NLT 60 days after the start of the PWS. This guidance is subject to review, approval and/or and disapproval by USARCENT prior to publication. The contractor will develop a Standard Operating Procedure (SOP) and submit for approval NLT 60 days after contract award giving guidance and procedures for property accountability for the AOR.

4.6.2 The contractor will maintain 100% accountability of all property to include but not limited to LISs, Combat Service Support Automated Information Systems Interface (CAISI), Movement Tracking System (MTS), Very Small Aperture Terminal (VSAT), Joint Telemedicine Network (JTMN) terminals, Transportation Coordinators’ – Automated Information for Movements System II (TC-AIMS) and Medical Communications for Combat Casualty Care (MC4) Systems. The contractor will maintain all property in PBUS-E. A baseline listing will be established and the contractor will ensure all equipment is accounted for by type, noun and serial number, to include BII and/or set, kits and outfits NLT 30 days after contract award. Submit to the COR NLT the 5th day of each month.

4.6.2.1 The contractor will conduct a 100% inventory of all sensitive items on a monthly basis.

4.6.2.2 A 10% cyclic inventory will be performed by the contactor every 30 days on LIS TPE equipment maintained on Camp Arifjan, Kuwait. The contractor will conduct an after action report (AAR) on how the inventory was conducted. Major discrepancies will be identified on the AAR and presented to the 1st TSC Logistics Automation Branch Chief to facilitate investigation and resolution of discrepancies (if applicable).

4.6.2.3 The contractor will submit a monthly report to the 1st TSC Logistics Automation Branch Chief of all property assigned to AOR. Reports will be due NLT the COB of the 5th day of the subsequent month.

4.6.3 During Relief-in- place/Transfer of Authority the contractor will coordinate with the TPE Property Book Officer (PBO), 1st TSC, and the incoming/outgoing unit Commanders to ensure Theater Logistics Automation TPE property is properly transferred.

4.6.4 The contactor will make recommendations to the 1st TSC Logistics Automation Branch Chief regarding lost, damaged, or destroyed equipment. Based upon the 1st TSC Logistics Automation Branch Chief’s decision, the contractor will ensure that all the proper forms are available and documented, and coordinate with TPE to ensure Theater Logistics Automation TPE property is properly transferred during Relief-in-place/ Transfer of Authority. Documents are prepared for the following reports: Financial Liability Investigation of Property Loss (FLIPL), Cash Collection Voucher (CCV) and Statement of Charges (See AR 735-5).

4.6.5 The contractor will use PBUS-E as the system of record for TPE and will be used to verify assigned equipment/property for units clearing the AOR. The contractor will provide a list of all units that have cleared their TPE hand receipt monthly NLT the COB of the 5th of the subsequent month.

4.6.5.1 Each contractor employee performing work under paragraph 4.6 on this PWS will have a minimum two years (2) work experience on the use of the PBUS-E interface.

4.6.6 The contractor will receive all supplies and equipment from the LIS Project Management Offices, Class II, APS, and/or Class VII warehouses. The supplies/ equipment will be inventoried and documented IAW DA PAM 710-2-1, Para. 9-4a.

4.6.6.1 The contractor will issue TPE equipment as directed by the 1st TSC Logistics Automation Branch Chief. All equipment will be issued via lateral transfer from the 1st TSC TPE property book to the gaining unit TPE property book.

4.6.6.2 The contractor will ship TPE equipment being issued to remote customers outside of Kuwait via the Central Receiving and Shipping Point (CRSP) or Military Postal Service (MPS). The contractor will provide the Transportation Control Number (TCN) and Radio Frequency Identification Device (RFID) tag number for equipment shipped through the CRSP and the Official Mail Receipt for equipment shipped via MPS.

4.6.7 The contractor will secure equipment not issued in assigned warehouses or containers on Camp Arifjan (Kuwait). Key security will be maintained by the contractor. The COR will provide specific guidance on location and level of security IAW

AR 380-5.

4.6.8 The contractor will evacuate unserviceable automation equipment with completed maintenance work orders to the Forward Repair Activity (FRA). The contractor will conduct weekly hand receipt/maintenance reconciliations with the FRA to ensure equipment is repaired and returned in a timely manner.

4.6.9 All contractor employees performing work under paragraph 4.6 of this PWS must be physically able to receive training and pass a driver’s test for forklifts.

4.6.10 All contractor employees performing work under paragraph 4.6 of this PWS must be able to lift 40 lbs. unassisted.

4.6.11 The contractor will coordinate the return of automation equipment when the equipment is no longer needed from units in the AOR.

4.7 Project Management and Logistics Automation Operations:

4.7.1 Experience: The Project Manager must have a bachelor’s degree from an accredited college or university in the Business Management, Logistics Management, Computer Science or related field; or no degree and four years’ experience with DOD supply management and logistics automation. Two years’ experience within any DOD service as a Battalion or Brigade S4 higher or equivalent and two years of experience within DOD service as a company, or platoon leader/commander, higher or equivalent is recommended. Contractor shall have knowledge of Army and Marine LISs, Logistics Support Activity (LOGSA) and other automation systems and agencies.

As tasked, the contractor shall:

4.7.2 Support management, coordination and execution of the contractor support team across all elements of USARCENT.

4.7.3 Provide monthly contract status reports to the Contracting Officer Representative (COR) NLT 5th of each month. The contract status report format and contents will be approved by the 1st TSC Logistics Automation Branch Chief.

4.7.4 Interface with 1st TSC staff and COR on status of task performance.

4.7.5 Provide interface to contractor for capability of follow-on tasks and access to expertise.

4.7.6 Coordinate program review meetings for the COR including arranging for facilities and equipment, developing agendas, preparing attendance lists, and publishing meeting results.

4.7.7 Assist 1st TSC in the synchronization of various logistics automation operations within the Logistics Automation Branch (e.g., LIS, MTS, Radio Frequency In-transit Visibility [RF-ITV]) as directed by the 1st TSC Logistics Automation Branch Chief.

4.7.8 Ensure awareness of the various Logistics Automation systems and is part of the “fusion center” of information. Work closely with the 1st TSC Logistics Automation Branch Chief and COR.

4.7.9 Maintain combat service support (CSS) situational awareness through all means of information systems, battle command automation systems, and CSS command and control (C2) information systems.

4.7.10 Monitor theater logistical automation priorities through attendance at various 1st TSC and USARCENT daily operation updates or as required by the 1st TSC Logistics Automation Branch Chief.

4.7.11 Maintain continuous liaison with other staff directorates, contractors, and commands within the AOR.

4.7.12 Provide operational support to USARCENT and to the various joint logistics automation enablers, including, but not limited to Joint Total asset Visibility (JTAV), Global Transportation Network (GTN), and Medical Communications for Combat Casualty Care (MC4). This support will include assessments of utility, deployment and integration recommendations and general administration of system operations if fielded.

4.7.13 Coordinate with and interpret USARCENT joint logistics system requirements with logistic managers in the USARCENT AOR, AMC, DLA, MMC, TSC, CENTCOM, LOGSA, and deploying units/installations to maximize logistics performance and leverage the joint systems’ unique capabilities.

4.7.14 Coordinate with 1st TSC, USARCENT, higher and supporting commands (to include supporting contractors) on emerging Logistics Information Systems and technology (e.g., GCSS- Army, etc.) to ensure that USARCENT logistics automation processes and procedures continue to operate effectively and efficiently.

4.7.15 Monitor Logistics Information System performance and make recommendations for improvements in business processes, system parameters and architecture, and communications architecture to improve system performance.

4.7.16 Participate in 1st TSC and USARCENT exercises and deployments to perform the functions of this PWS, as required.

4.8 Logistics Automation Operations and Integration (On Order):

As tasked, the contractor will:

4.8.1 Assist with Logistics Automation Branch operations and work directly with the 1st

TSC Logistics Automation Branch Chief.

4.8.2 Synchronize the logistics information operations. Ensure awareness of the Logistics Information Systems and serve as the “fusion center” of information management.

4.8.3 Work closely with the Radio Frequency ITV section. Maintain combat service support situational awareness through all means of information systems, battle command automation systems, and CSS C2 information systems.

4.8.4 Coordinate with the logistics operations office. Monitor theater Logistics Information Systems policies.

4.8.5 Maintain continuous liaison with other staff directorates, contractors, and commands within the CENTCOM AOR.

4.8.6 Provide adequate staffing levels to Transition/Phase-In within 5 days from notification of award of the task by the Contracting Officer.

4.9 LIS Training Services

4.9.1 The contractor shall provide over-the-shoulder and hands-on training to Service Members, GS employees, DoD Civilians, and Contracted system operators on all LISs listed in paragraph 1.1 for this PWS. The contractor will submit a report of no shows by name, rank, and unit to the 1st TSC Logistics Automation Branch Chief NLT the last day of the training class. The contractor will develop After-Action-Review (AAR) forms.

AAR forms will be issued to each unit/student conducting training and collected at the end of each class. The contractor will receive AAR comments from at least 50% of users participating in the training. The AAR forms will be submitted to the 1st TSC Logistics Automation Branch Chief and the COR NLT three calendar days after the last day of each class. The format for the AAR forms will be approved by the 1st TSC Logistics Automation Branch Chief.

4.9.2 The contractor shall provide formal classroom refresher and sustainment training to Service Members, GS Employees, DOD civilians, and Contracted system operators in the AOR for all LIS platforms listed in paragraph 1.1 of this PWS. The contractor will maintain classrooms in Kuwait, provided by the U.S. government. Provide between one-thousand (1000) and two-thousand (2000) hours of scheduled classroom training each year coordinated and approved by the 1st TSC LOG-Auto Branch Chief and the COR.

4.9.3 The contractor will establish and maintain a COR approved training calendar which provides scheduled classes and dates for the next 90 days. The contractor will maintain a LIS Training group email and Outlook calendar that will be used to receive and respond to training requests, schedule training and send invitations. The contractor will schedule personnel for training and publish the attendance roster for each class provided. The contractor will notify the COR of any changes three days prior to making those changes.

4.9.4 The contractor shall conduct on-site LIS Gunneries to incoming units as needed/requested. AAR forms will be issued to each unit conducting the LIS Gunnery and collected at the end of each Gunnery. The contractor will receive AAR comments from at least 50% of users participating in the Gunnery. The AAR forms will be submitted to the 1st TSC Logistics Automation Branch Chief NLT three calendar days after the last day of each LIS Gunnery.

4.9.5 The contractor shall develop, modify, and provide “Tactics, Techniques, and Procedures (TTPs)” type training material and services as required by the 1st TSC Logistics Automation Branch Chief to meet the employment and sustainment of LISs in the CENTCOM AOR.

4.9.6 In coordination with the COR and Project Manager, the contractor will develop Program(s) of Instruction (POIs) for the formal classroom training for each LIS. The POIs will be approved by the 1st TSC Logistics Automation Branch Chief. The POIs will be submitted NLT 60 days after contract award. The POIs will be updated and submitted quarterly to the 1st TSC Logistics Automation Branch Chief and COR.

5.0 Medical Communications for Combat Casualty Care (MC4) Training and Certification

DFARS 252.239–7001 Information Assurance Contractor Training and Certification.

Information Assurance Contractor Training and Certification (JAN 2008)

(a) The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01–M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including—

(1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01–M; and

(2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01–M.

(b) Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

(c) Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

End of clause)

5.1 Security

INVESTIGATIVE REQUIREMENTS FOR ACCESS TO UNCLASSIFIED DEFENSE

INFORMATION

a. In accordance with AR 25-2, Information Assurance, and AR 380-67, Personnel Security Program, Appendix K, the contractor personnel having access to unclassified Defense information and accessing Government computer systems under this award shall be subjected to, as a minimum, a National Agency Check (NAC).

b. All contractor employees who manage, design, develop, operate, or access DoD Automated Information Systems (AIS) or DoD network systems are required to undergo appropriate background investigation and security awareness training. DoD personnel that hold IT/ADP related positions that directly or indirectly affect the operation of unclassified IT resources and systems that process Sensitive But Unclassified (SBU) information are subject to appropriate levels of IT/ADP security clearances. For more information please visit http://www.tricare.mil/tmaprivacy/personnel-security.cfm.

c. For all positions, the employment contract for contractor personnel shall state that retention in the position is contingent upon completion of a favorable security screening and investigation. If such screening proves to be unfavorable, employment shall be terminated at the applicable Government facility.

d. If work is performed on a Government Installation, the Installation Security Office will submit the SF85P for all personnel as required.

The Contractor shall establish administrative, technical, and physical safeguards to protect all Government data, to ensure the confidentiality, integrity, and availability of government data. As a minimum, this shall include provisions for personnel security, electronic security and physical security as listed in the sections that follow.

5.1.2 Health Insurance Portability and Accountability Act (HIPAA)

a. The Contractor shall comply with the 1996 HIPAA (P.L. 104-191) requirements, specifically the administrative simplification provisions of the law and the associated rules and regulations published by the Secretary, Health and Human Services (HHS) and the published TRICARE Management Activity (TMA) implementation directions.

This includes the Standards for Electronic Transactions and the Standards for Privacy of Individually Identifiable Health Information. It is expected the contractor shall comply with all HIPAA-related rules and regulations as they are published and as TMA requirements are defined (including security standards, identifiers for providers, http://www.tricare.mil/tmaprivacy/personnel-security.cfm employers, health plans, and individuals, and standards for claims attachment transactions). For detail information visit: http://www.tricare.mil/tmaprivacy/Hipaa.cfm.

5.1.3 Personnel Security

The Contractor shall comply with DoD Directive 8500.1 and DoD Instruction 8500.2, Information Assurance, DoD 5400.11, Privacy Act Program Requirements, DoD 6025.18-R, DoD Health Information Privacy Regulation, and DoD 5200.2-R, Personnel Security Program Requirements, and satisfy the following responsibilities for ensuring personnel security to include, but are not limited to:

1. MC4 is a Department of Defense agency that has requirements for control of personnel who access MC4 network resources. Contractor personnel who require access to the MC4 network should possess a current National Agency Check to expedite the access process.

2. All personnel working on this project must be US citizens or permanent US residents.

They must satisfactorily complete DoD Form 85P within seven (7) days of placement on this task order.

3. This process requires the contractor have a PIPS12 Submitting Office Number (SON) Authorization on file with TMA and the Office of Personnel Management (OPM).

The Contractor is responsible submission of all investigation paperwork. (see http://www.tricare.mil/TMAPrivacy/personnel-security.cfm)

4. Initiate, maintain, and document minimum personnel security investigations appropriate to the individual’s responsibilities and access to MHS Sensitive Information

(SI).

5. The MC4 systems contain sensitive data. Records, data, and information to which the contractor has access may be proprietary in nature. As such, the Contractor shall not publish or disclose in any manner, without the Contracting Officer's written consent, any data or information stored, transmitted, or otherwise maintained by the Contractor under this contract, including information about MC4 files, processing activities or functions, User Ids, passwords, or other knowledge that may be gained as a result of this contract, to anyone who is not authorized to have such information.

6. The Contractor shall, at all times, act to protect, secure, and safeguard against threats, hazards, or unauthorized disclosure the Government data contained therein.

7. All contract personnel will be required to sign a non-disclosure agreement upon beginning performance on this contract.

8. Immediately report to the appropriate Government representative and notify the TMA Privacy Office within five working days if at any time a contractor employee has privileges revoked to a DoD data system or system data because of security concerns.

http://www.tricare.mil/tmaprivacy/Hipaa.cfm http://www.tricare.mil/TMAPrivacy/personnel-security.cfm

9. Immediately deny access to any AIS, network, or MHS SI information to the contractor employee if directed to do so by the appropriate government representative for security reasons.

10. Ensure that all contractor personnel receive information assurance (IA) training before being granted access to DoD AISs/networks, and/or MHS SI information.

5.1.4 Information Systems (IS)/Networks Physical Security

The Contractor shall:

1. Ensure all contractor personnel receive information assurance (IA) training before being granted access to DoD AISs/networks, and/or MHS SI information. Contractors will employ physical security safeguards for IS/Networks involved in processing or storage of Government data to prevent the unauthorized access, disclosure, modification, destruction, use, etc., and to otherwise protect the confidentiality and ensure use conforms with DoD and Army regulations.

2. Correct any deficiencies identified by the Government of the Contractor’s physical security posture. The Contractor shall follow all requirements in the MHS Information Assurance Policy regarding physical security. New MHS policies will appear on the following website: http://www.tricare.osd.mil/tmis_new/.

5.1.5 Special Requirements for Protected Health Information

Whenever a contract is awarded that entails the collection, use, or storage of Protected Health Information (PHI), the contractors must notify the TMA Privacy Office when the contract is awarded. The Contractor shall:

1. Continuously protect data from any DoD AIS containing PHI from unauthorized access, use, modification, or disclosure.

2. Comply with DoD regulations listed above under Personnel Security.

HIPAA

All previously identified requirements for HIPAA compliance (identified above under General Security Requirements) apply to PHI.

Data Use Agreements (DUA)

During the Period of Performance, the Contractor may need to access a DoD AIS containing PHI. In addition, if a new system is being developed that includes PHI, for the purpose of studies, surveys, measuring healthcare outcomes, etc., the Contractor and sponsor must take steps to ensure the additional documentation (i.e. Privacy Act http://www.tricare.osd.mil/tmis_new/

System of Records (SOR) and/or Report Control Symbol (RCS) if this involves surveys) is included with their DUA, before data can be utilized in accordance with the Privacy Act. This includes the collection, maintenance, use, and dissemination of personal information. If access and/or extraction of PHI are required from a DoD AIS for any reason, the contractor must request and receive approval of the DUA prior to accessing, extracting, copying, or storing information to or from any DoD AIS.

Contact Steven Barton or Michael Lee for further information:

TMA Privacy and Civil Liberties Office Axiom Resource Management, Inc.

2941 Fairview Park Drive, Suite 900 Falls Church, VA 22042 703-208-1088 x313 Steven.Barton.ctr@tma.osd.mil Michael.Lee.ctr@dha.mil

Electronic Security

Ports Protocols and Services – The Contractor shall follow all current DoD and Defense Information Systems Agency (DISA) standards and requirements for acceptable Ports, Protocols, and Services. Any requests for exception to using the current DISA Ports, Protocols, and Services standards requires a request for exception sent through the Program Manager to the Designated Approval Authority (DAA).

Public Key Infrastructure and Encryption (PKI) – The Contractor shall follow the DoD standards, policies, and procedures related to the use of PKI certificates and biometrics for positive authentication. Where interoperable PKI is required for the exchange of unclassified information between DoD and its Contractors and contractors, industry partners shall obtain all necessary certificates. The Contractor must turn over to the Government all encryption keys for deployed systems, backdoor algorithms, and procedures for their use in remote support. The contractor must provide a written report detailing all of the above, prior to task order expiration, regardless of modifications or extensions.

Department of Defense Standard Contract Clause for Business Associates Agreement (BAA) is attached in the PWS under section Attachment A

Personal Identity Verification of Contractor Personnel.

The Contractor shall comply with agency personal identity verification procedures identified in the contract that implement Homeland Security Presidential Directive-12 (HSPD-12), Office of Management and Budget (OMB) guidance M-05-24, and Federal Information Processing Standards Publication (FIPS PUB) Number 201.

The Contractor shall safeguard individual privacy contained in Federal record as enacted in the Privacy Act of 1974 and must follow all privacy procedures in FAR mailto:Steven.Barton.ctr@tma.osd.mil mailto:Michael.Lee.ctr@dha.mil mailto:Michael.Lee.ctr@dha.mil

Clauses 52-224-1 Privacy Act Notification (April 1984) and 52.224-2 Privacy Act (April 1984).

6.1 PLACE OF PERFORMANCE / PERIOD OF PERFORMANCE: The primary location for performance will be Camp Arifjan, Kuwait. The contractor shall be required to travel in support of this requirement to USARCENT locations. Almost all travel will be within the U.S. Central Command (USCENTCOM) AOR, but there may be a few occasions where the mission will require support outside the CENTCOM AOR and travel will be requested on a case by case basis upon the approval of the COR and KO and having available funds.

6.2 The AOR, as defined by USARCENT, includes: Kuwait, Afghanistan, UAE, Qatar, Bahrain, Oman, Saudi Arabia, Jordan, Iraq, Iran, Kazakhstan, Lebanon, Oman, Pakistan, Syria, Tajikistan, Turkmenistan, Uzbekistan, Yemen and Egypt

6.3 The contractor will provide support six days per week, on-call seven days a week with a response (call back customer) telephonically within two hours. Based on workload or during periods of surge conditions, the contractor may be required to provide support for up to 72 hours per week. Daily working hours mirror those of Government employees connected with the same office. The operating hours are subject to change by the government based on mission requirements.

7.1 CONTRACT DELIVERABLES:

7.2 Data deliverables shall be delivered as specified in the Contract Data Requirements List (CDRL) in attachment 2 of this PWS.

7.3 All deliverables under this PWS are subject to review and acceptance by 1st TSC and USARCENT Logistics Automation Branch.

8.1 CONTRACT TYPE:

8.2 This is a Firm Fixed Price Indefinite Delivery – Indefinite Quantity (IDIQ) Contract with Cost Reimbursable Contract Line Item Numbers (CLINS). The period of performance for this contract will commence 30 days after the award of the contract or sooner upon agreement of the parties.

8.3 A post award meeting with the contractor and COR will take place after award of the contract.

8.4 INVOICE PROCEDURES:

8.4.1 Invoices shall be submitted monthly for work performed the prior month. The contractor will submit an invoice NLT the 5th of each month. The amount invoiced shall include labor charges and other direct costs (ODCs) which may be authorized by this PWS (e.g., travel). For ODCs, invoiced charges shall not exceed the limit specified. No charges will be paid by the Government, which are not specifically identified in the task and approved in advance by the Government. Copies of receipts, travel vouchers, etc., completed in accordance with Government Travel Regulations shall be attached to the invoice to support charges other than personnel hours. Original receipts shall be maintained by the contractor and made available to Government auditors upon request.

8.4.2 The invoice shall be submitted on official company letterhead with detailed costs for each of the following categories:

• Total labor charges (Firm Fixed Price, Total Price/Total Period of

Performance, Equal Amount every month)

• Travel and per diem charges (if any)

• Total other direct costs (ODCs) (if any)

• Total invoice amount

• Prompt payment discount offered, if applicable

8.4.3 Invoices for final payment must be so identified and submitted when the task has been completed and no further charges are to be billed. Invoices will be marked with the word FINAL (even if it is a zero amount).

8.4.4 The invoice will include a detailed breakout of charges listing, at a minimum, the following: period covered, labor, travel, and ODCs. The invoice format will be determined by the Contracting Officer.

8.4.5 The Contractor will submit invoices inclusive of costs associated with the Firm Fixed Price CLINs and Cost Reimbursable CLINs to the ACO and COR for validation and approval. The ACO and COR will coordinate with each other regarding the submitted charges and the ACO will ultimately sign the invoice. The Contractor shall ensure that the Contracting Officer also receives a copy of each invoice. In the absence of the ACO, the Contracting Officer will validate the charges with the COR and approve the invoice.

9.1 TRAVEL:

9.2 This contract requires travel to locations within CENTCOM, to provide logistics automation support.