SP330016R0019_Attachment_J.1_Performance_Work_Statement.pdf

SP3300-16-R-0019 Attachment J.1-Performance Work Statement

Performance Work Statement (PWS) Headquarters Defense Logistics Agency (HQ DLA)

Tracker Lite Requirements Analysis and Maintenance Support

SECTION C INTRODUCTION

A. DLA is working in close cooperation with Department of Defense (DoD) and non-DoD stakeholders, various audit organizations (e.g. the General Services Administration (GSA), the Government Accountability Office (GAO), the DoD Inspector General (DoD IG), and the DLA Accountability Office) and commercial partners (e.g. U.S Bank) to enhance and improve transportation financial management (TFM) processes and their associated automated tools and controls. The overall goal of this effort is to improve stewardship of transportation expenditures.

B. Moreover, DLA Distribution and other Transportation Offices (TOs) utilize numerous

Transportation Account Codes (TACs)/Lines of Accounting (LOA) that are owned by DoD and non-DoD organizations for the allocation of transportation expenditures. The Logistics Tool Suite (LTS), and specifically for DLA Distribution the Tracker Lite application, is a Value-Added Intermediary (VAI) in the transportation billing process that allows DLA and other organizations to improve transportation expenditures stewardship and provide the necessary functionality required for the correct citation of TACs. Further, the implementation of the LTS and the Tracker Lite application has eliminated the need for all future Software Change Requests (SCRs) for Transportation Management Systems (TMS) related to changes in LOA formatting, e.g. Standard Financial; Information System (SFIS)/Single Line of Accounting (SLOA). It has also improved DLA's financial data quality and added significant financial flexibility to meet our customers’ TFM needs.

C. IT systems are a key enabler of current and future TFM processes. In order to meet the goals of the DoD Transportation Financial Auditability (TFA) effort, it is necessary to enhance the capabilities of existing systems and to invest in the development of new tools where it makes economic sense.

SECTION C-1 GENERAL CONDITIONS AND REQUIREMENTS

1.1 SCOPE OF WORK

A. DLA requires support services to provide Tracker Lite Requirements Analysis and

Maintenance Support in order to achieve DoD Financial Improvement and Audit Readiness (FIAR) goals. Support services are required to provide technical recommendations for improving and enhancing the classification and execution of transportation expenditures, improving data quality, assisting in the identification of incorrect usage of TACs, assisting in the identification of potential over, duplicate, or fraudulent payments, and improving the cost effectiveness transportation services provided.

B. The Contractor shall also provide configuration and maintenance of existing web-enabled transportation payment tools; development and maintenance of DLA-specific business rules for existing web enabled budget analysis and third party billing payment processing tools, which will be used for analysis of transportation expenditures data to identify policy violations and recover unauthorized expenditure of DLA-managed funds.

C. This is a non-personal services contract to provide Tracker Lite Requirements Analysis and

Maintenance Support. The Government will not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

The Government and the Contractor understand that the services to be provided under this contract by the Contractor are non-personal services and that no employer-employee relationship exists between the Government and the Contractor. The Government may provide technical direction which will assist the Contractor in accomplishing the PWS; however, the Government will not control the methods used by the Contractor to perform the service requirements set forth in the PWS.

D. All Contractor personnel in performance of work under this contract where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of the members of the public that they are Government officials. All Contractor employees shall wear ID badges conspicuously on his or her outer clothing above the waist at all times and shall identify themselves as Contractors when work performance and meeting attendance occurs on a military installation.

1.2 GENERAL OPERATING CONDITIONS

1.2.1 Period of Performance

A. The period of performance will be established for a one year base period with two (2) one-year option periods.

1.2.2 Place of Performance

A. The primary place of performance for Contractor resources shall be at the Contractor’s facility. No reimbursement will be made for Contractor resources travel to or sustainment support at this primary place of performance.

1.2.3 Interactions with Other Government Organizations

A. The Contractor’s primary interaction with the Government shall be through the Contracting

Officer (KO) and the Contracting Officer’s Representative (COR). The COR will:

1. Perform all COR functions;

2. Perform quality assurance evaluations of the Contractor’s performance;

3. Provide the primary interface between the Contractor and DLA; and

4. Perform other inherently governmental functions or other functions not part of this contract as prescribed in FAR subpart 7.5.

1.2.4 Federal Holidays

A. Federal holidays generally observed by Government personnel include:

B. If the holiday falls on a Saturday, it will be observed on the preceding Friday. If the holiday falls on a Sunday, it will be observed on the following Monday. The Contractor shall not be required to perform services on these days. In the event an Executive Order issued by the President of the United States declares Agencies of the Federal Government closed for a regularly scheduled workday, the COR will determine and advise the Contractor on whether services are required for that day.

C. The Contractor shall coordinate in advance with the COR any requests to work outside the core duty hours. In emergency and critical situations, Contractor employees may be required to work over 40 hours per week as directed by the COR. Labor rates in the schedule do not vary for work over 40 hours per week. The Contractor shall accommodate the different distribution depot time zones when in a travel status as well as to support briefs and meetings occasionally given after normal core hours.

1.2.5 Core Duty Hours

A. Contractor personnel are expected to perform their work within the core operating hours of

0700 to 1800 hours ET, Monday through Friday, excluding Government approved Holidays.

If variances are required from the core operating hours, the Contractor shall obtain prior approval from the COR.

1.3 Travel

A. Contractor resources will be required to travel to the Washington, D.C. area and other potential customer locations. Travel will generally be within the Continental United States (CONUS); however, under special circumstances, travel outside the Continental United States (OCONUS) may be required. All travel by Contractor employees must be authorized by the KO or COR prior to travel being performed. When travel has been authorized, the Contractor shall approve and forward travel requests to the COR for Government validation.

The Contractor shall submit travel requests to the COR a minimum of five (5) workdays prior to the travel commencement date. Travel requests shall be in writing and contain the dates, locations, and estimated travel costs. The Contractor shall ensure that all travel is consistent with the Joint Travel Regulations (JTR). Reimbursements for transportation costs will be limited to allowable expenses for Government directed travel. The Contractor shall

Observed Federal Holidays

New Year’s Day Martin Luther King Day

Presidents Day Memorial Day

Independence Day Labor Day

Columbus Day Veterans Day

Thanksgiving Day Christmas Day be responsible for any costs incurred as a result of authorized travel which were in excess of that allowed under Federal Acquisition Regulation (FAR) Part 31.205-46 Travel Costs and the appropriate regulations therein.

1.4 Labor Categories

A. The skill level an individual qualifies for is dependent upon the relevant experience and capabilities of the individual which equips him/her to perform work identified under this contract. Contractor labor category titles may differ from the Government stated titles below; however, the Contractor offered labor category titles should match the minimum qualifications necessary to perform the requirements set forth in this PWS. By written mutual agreement and at the Government’s discretion, the contract may be modified to incorporate additional labor categories not initially listed in the PWS.

B. The Contractor shall identify one employee as the company local POC. This will be the individual that shall coordinate with the Government in matters of contract performance.

Written notification of the name, address, home telephone and mobile telephone of the POC and their alternate shall be provided to the KO and COR the first day of contract performance and thereafter as changes occur. This individual, or in their absence the designated alternate, shall have full authority to act for the Contractor on all matters relating to the day to day operations of the contract.

C. The Contractor shall not employ any person who is not a citizen of the United States and who does not have the requisite security check as set forth in paragraph 1.5.3 Personnel Clearance.

D. All contractor personnel shall collectively possess the following minimum knowledge and skills:

• Extensive knowledge of the following software/program applications: LTS and more specifically the Tracker Lite application, DoD approved Third Party Payment System (Syncada), and Transportation Global Edit Table (TGET);

• Knowledge of general Government Accounting Processes and Procedures and Transportation Working Capital Fund (TWCF) Billing Process and Procedures;

• Technical expertise in defining and analyzing project requirements and supporting the development of system and programming specifications;

• Proficient at database management;

• Demonstrated ability to perform research, critical analysis, and assist with resolution of problems;

• Ability to apply industry knowledge to determine the accuracy and reasonableness of requirements data;

• Excellent verbal and written communications skills and leadership abilities; and

• Demonstrated ability implementing and maintaining full life cycle development

E. Senior Systems Analyst. The Senior Systems Analyst shall:

• Support system and programming specifications development

• Aid with data processing solutions based on business need and technical considerations

• Research and assist with problem resolution

• Assist with complex documentation and user needs analyses.

• Study customer environment by reviewing and analyzing job tasks, organizational structure and user requirements to propose system-wide solutions.

• Interview technical personnel, interpret reports, specifications and drawings to increase understanding of processes and requirements.

1.5 SECURITY

A. The Contractor or any representative of the Contractor entering DoD locations to perform contract requirements shall abide by all security regulations and may be subject to security inspections. Contractor personnel and property shall be subject to search and seizure upon entering, while on, and upon leaving the DoD locations pursuant to regulatory guidance.

B. All Contractor personnel shall conduct themselves IAW acceptable business decorum at all times. The Contractor shall remove any individual from the site whose continued presence or employment on this task order is deemed by the KO to be contrary to the public interest, deemed to adversely affect health, morale, welfare, or good order and discipline on the installation, or inconsistent with the best interests of national security. IAW USC Title 18, Crimes and Criminal Procedure, Part I, Crimes, Chapter 67, Military and Navy, Section 1382, the Installation Commander has the authority to bar individuals from the host installation.

C. The Contractor shall ensure the physical security of all Government property, accountable property or information provided under this contract is secured and protected against theft, sabotage, or other acts constituting illegal destruction. The Contractor and its personnel shall comply with all DoD and DLA regulatory guidance:

• DLA Physical Security Manual

• DLAR 4145.11 Safeguarding of DLA Sensitive Inventory Items, Controlled Substances, and Pilferable Items of Supply.

• DLAI 6304 Information Security Program

• DLAI 6305 Operations Security (OPSEC)

• DLA 4306 Physical Security Program

• DoDM 5200.1 (Volumes 1-4) Information Security Program

• DoD 5200.2-R Personnel Security Program

• DoD 5200.8-R Physical Security Program

• DoD 5205.02-M DoD Operational Security (OPSEC) Program Manual

• DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM)

• DoD 5220.22-R Industrial Security Regulation

• DoD 2000.12 DoD Antiterrorism Program

• DoD 2000.16 DoD Antiterrorism Standards

• DoD O-2000.12-H DoD Antiterrorism Handbook

• DoD 5100.76 Physical Security of Sensitive Conventional Arms, Ammunition, and

Explosives (AA&E)

• DoDI 5240.6 Counterintelligence (CI) Awareness and Briefing Program

E. The Contractor shall report any security deviation or Practices Dangerous to Security (PDS), to include COMSEC, OPSEC, INFOSEC, etc., to the KO or designee within one (1) hour of discovery. PDS have the potential to jeopardize the security of sensitive information and material if allowed to perpetuate. Examples include, but are not limited to, any knowing, willful, or negligent action that could reasonably be expected to result in an unauthorized disclosure of classified information; to include a loss or gain of classified material; failing to properly dispose of sensitive documents; leaving doors unsecured; and allowing unauthorized access to Security Areas such as pilferable and hazardous storage. These practices, when identified, shall be reported immediately to the KO or designee and the Contractor shall take the appropriate action that includes, but is not limited to, making changes or providing training to ensure the security of sensitive information and material.

1.5.1 Reporting of Criminal Violations

A. The Contractor shall report immediately to the KO or COR any suspected, alleged, or actual criminal incidents IAW DLAI 5105, Reporting of Criminal Incidents.

1.5.2 Authorized Visitor Control

A. Authorized visitors on official business related to this contract shall obtain approval from the host installation Law Enforcement and Security Office and the KO or COR for entrance to the host installation. The Contractor shall submit a DLA Form 1818, Visitor Request Form or equivalent form to the KO or COR at least one (1) week in advance for all planned off-base visitors needing base access and shall follow the host installation policy for all visitors.

B. The Contractor shall develop specific procedures for identification (ID) and control of all visitors to warehousing and administrative areas and submit to the KO or designee for acceptance. The Contractor’s procedures shall include the following:

1. Positive methods of establishing the authority for admission of visitors, as well as any limitations concerning access.

2. Positive identification of all visitors by means of personal recognition, visitor security badge, visitor permit, or other identifying credentials. The Contractor shall contact the employee, supervisor, or officer in charge to ascertain the validity of the visit.

3. Using the DLA Form 584, Visitor Register or Contractor equivalent form to provide a record of the identity of the visitor, the time and the duration of the visit, and other pertinent control data. The Contractor may use an automated system instead of the DLA Form 584 provided the system records, at a minimum, provide the same data included on the DLA Form 584. The Contractor shall establish procedures for recovering any visitor security badges, visitor permits, or other identifying credentials at the completion of the visit.

C. The Contractor shall not allow visits from foreign nationals to the host installation without written approval from the KO or COR. A foreign national is defined as a person who is not a citizen or national of the United States. If approval is obtained, the Contractor shall follow the instructions for coordinating the visit IAW DLAI 4303, Foreign Visits and Disclosure Program.

1.5.3 Personnel Clearance

A. The Homeland Security Presidential Directive 12 (HSPD-12) has established criteria for

Contractors who require a Common Access Card (CAC) for either physical access to an installation or access to government information technology (IT) systems. The Government requires Personnel Security Investigations (PSI) to establish that applicants or incumbents either employed by the Government or working for the Government under contract are suitable for the job and are eligible for a public trust or sensitive position. Upon favorable review and initiation of the PSI, Contractor personnel may be granted temporary access pending final adjudication of the PSI. The Contractor shall request personnel clearances IAW instructions found in Technical Exhibit (TE) 1.1 Contractor Personnel Security.

1.5.4 DoD Common Access Card (CAC)/Identification Badge (ID Badge)/Electronic Key

Card A. Every Contractor employee shall obtain and possess a DoD Common Access Card (CAC) and/or an Access ID Badge, as required by HSPD-12 and Directed-Type Memorandums (DTM) 08-003. Upon favorable review and initiation of the PSI to establish the suitability of an employee for the job and the approval for temporary Information Technology (IT) access pending final adjudication of the PSI, the Contractor shall submit to the KO or designee a request for the DoD CAC (See paragraph C-1.5.3, Personnel Clearance).

B. The Contractor shall safeguard all CAC and/or ID Badges. Contractor employees shall not share CAC and/or ID Badges. Each Contractor employee shall wear the ID Card(s) conspicuously on his or her outer clothing above the waist at all times while working on the installation. Personnel may be challenged and removed from the work area or denied access to the host installation if the ID Card(s) are not worn. The Contractor shall not display or use any badge as a means of personal identification outside the installation.

C. In the event that a Contractor employee damages his or her CAC and/or ID Card, the Contractor shall report the damaged CAC and/or ID Badge within two (2) working hours after discovery of damage to the KO or COR. The Contractor shall arrange for a replacement CAC and/or ID Card. The Contractor shall return all government-furnished CAC and/or ID Card(s) to the Government IAW TE 1.2 Common Access Card (CAC) Procedures.

Contractor personnel failing to return their Government CAC and/or ID Card are subject to criminal charges under United States Code (USC) Title 18, Chapter 1, Section 499 and 701.

D. Reference TE 1.2 Common Access Card (CAC) Procedures for the Standard Operating Procedures (SOP) for Contractor CAC issuance and accountability.

1.5.5 Vehicle Registration

A. The Contractor shall register all Contractor-provided vehicles used in performance of the contract requirements and ensure that Contractor employee vehicles to be driven on the host installation, to include motorcycles, are registered with the host installation security office and are in conformance with State and local regulations in effect at the time of registration and as long as employed by the Contractor. The Government will not permit access to the host installation without proper vehicle identification and registration. Evidence of a valid driver’s license, vehicle registration card, and insurance are required for registration.

Contractor employees shall maintain current registration and proof of insurance on all Privately-Owned Vehicles (POV) brought on host installation. The Contractor shall maintain current registration and proof of insurance on all Contractor-owned vehicles brought on the host installation.

1.5.6 Parking and Traffic Control

A. The Contractor and its employees shall abide by host installation parking regulations. All vehicles shall be parked in designated parking areas only. The Contractor and its employees shall conform to Federal, State and host driving regulations.

1.5.7 Information System Security

A. Upon favorable review and initiation of the PSI to establish the suitability of an employee for the job and the approval for temporary IT access pending final adjudication, but not less than fourteen (14) working days prior to the employee’s start date, the Contractor shall request Information Technology (IT) eligibility for an employee requiring access and passwords to the government-furnished data systems. All positions involving computer activities require a minimum IT III category eligibility. IT eligibility categories are defined below. The Contractor shall submit a Contractor Investigative Request (CIR) and a DD Form 2875 for temporary IT III eligibility, with final IT III eligibility contingent upon receiving a favorably adjudicated NACI (See paragraph C-1.5.3, Personnel Clearance).

Information Technology (IT) Eligibility Categories:

• IT I: Those positions in which the incumbent is responsible for planning, directing, and implementing a security program; and directing, planning, and designing a computer system including hardware and software. The incumbent is also able to access a system during the operation or maintenance in such a manner that the system would be gravely damaged or the incumbent would realize significant personal gain.

• IT II: Those positions in which the incumbent is responsible for directing, planning, designing, operating, or maintaining a computer system and whose work is technically reviewed by a higher authority of the IT I category to ensure integrity of the system.

• IT III: All other positions involved in computer activities not covered in IT I and IT II.

B. All Contractor personnel provided with access to government-furnished computers and systems shall observe IT security policies and procedures as provided by the KO or COR. The Contractor shall notify the KO or COR within 12 hours when, for reasons of personnel resignation, reassignment, termination, or completion of portions of the contract, Contractor personnel no longer require access to government systems.

C. The Contractor shall observe all copyright agreements. In the interest of protecting Government systems from computer viruses, the Contractor shall not use public domain software nor shall Contractor personnel download software from public bulletin boards or Internet websites. The Contractor shall use only government-furnished software in performance of the contract requirements. Should the introduction of a computer virus or malicious destruction of computer software, stored information, or hardware result from the use of public domain software or from software taken from a public bulletin board or Internet website, the Contractor shall be required to repair the damage and incur all costs at no expense to the Government and without impact on delivery schedules.

1.5.8 Contact of a Suspicious Nature

A. Contractor personnel who have been contacted under suspicious circumstances shall report that contact immediately, either verbally or in writing, to their supervisor who shall report it within two (2) hours to the KO or COR for action. Key contacts for reporting purposes are defined as:

1. Contact with an individual (regardless of nationality) that suggests to the Contractor employee that an intelligence gathering or terrorist organization may have targeted him or her for possible intelligence exploitation.

2. A request by anyone (regardless of nationality) for illegal or unauthorized access to classified or unclassified sensitive information.

3. Contact with a known or suspected intelligence officer from any country.

4. Contact with a foreign diplomatic establishment, whether in the U.S. or abroad, for personal or official reasons. Certain Contractor personnel in positions designated as “sensitive” by the Government may also be required to inform their chain of command in advance of the nature and reason for contacting a foreign diplomatic establishment or travel to countries on the State Department list whose interests’ may be adverse to the United States.

B. Additionally, Contractor personnel who have information about activities pertaining to espionage, terrorism, unauthorized technology transfer, sabotage, sedition, subversion, spying, treason, unauthorized release of classified or unclassified controlled information, or unauthorized intrusions into automated information systems shall report that information immediately to the KO or COR for action.

1.5.9 Safeguard Information

A. The Contractor shall not allow access or disclosure of contract related information regarding the operations of DLA to any government agency, non-government agency, or individual unless specifically authorized by the KO or COR. The Contractor shall provide documents and files requested by such parties to the KO or COR within one (1) hour of receipt of the authorized request. All files are the property of the Government and the Contractor shall turn all files over to the KO or COR at the completion or termination of this task order.

B. The Contractor may be required to access data and information that is proprietary to a government agency or contractor or that is of such nature that its dissemination and use other than as specified in this contract would be adverse to the interests of the Government or others. The Contractor and its personnel shall not divulge or release data or information developed or obtained under performance of this contract except to government personnel who are authorized to receive the information or upon written approval of the KO or COR.

The Contractor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend other than as specified in this contract.

C. Disclosure of information regarding operations and services of DLA to persons not entitled to receive it, or failure to safeguard any classified information that may come into the Contractor’s control in connection with work under this contract, may subject the Contractor, its agent, or its employees to criminal liability under USC Title 18, Crimes and Criminal Procedure, Part I, Crimes, Chapter 37, Espionage and Censorship, Sections 793, Gathering, Transmitting or Losing Defense Information, and Section 798, Disclosure of Classified Information. Neither the Contractor nor its employees shall disclose or cause to be disseminated any information concerning the operations of the activity which could result in, or increase the likelihood of, the possibility of a breach of DLA’s security or interrupt the continuity of DLA’s operation.

1.5.10 Force Protection

A. Force Protection Conditions (FPCONs) may affect access to host installations. The FPCON is established by the host installation or higher national command authorities, and the Installation Commander is responsible for implementing the proper response to progressive levels of terrorist threats. FPCONs are normally displayed at most entrance gates, building entrances and office entrances. The Contractor shall adhere to and operate IAW any restrictions imposed as a result of a FPCON. Measures implemented under the various levels of terrorist threat may impact the Contractor’s normal operational approach. The Contractor shall ensure that business development support services are sustained during heightened security measures.

1.6 DOCUMENTATION AND RECORDS

A. All documentation, records, and schedules produced by the Contractor in performance of this contract are the property of the Government and shall remain so upon termination or completion of the contract. The Contractor shall keep these items current. Documentation, records, and schedules shall be turned over to the Government upon termination or completion of the contract. All documentation, records, and schedules are subject to the Freedom of Information Act and Privacy Act.

1.7 QUALITY CONTROL PLAN (QCP)

A. The Contractor shall provide a QCP which specifically addresses methods for meeting performance standards, customer requirements, and complying with applicable regulations.

B. The Contractor’s quality system shall demonstrate its prevention-based outlook by meeting the objectives stated in the PWS throughout all areas of performance (e.g., all functional areas, all Acceptable Performance Levels (APL) and non-APL requirements). The QCP shall be developed to specify the Contractor’s responsibility for management and quality control actions to meet the terms of the contract. Within 24 hours of completion, the Contractor shall provide to the COR, all reports generated as a result of the Contractor’s quality control efforts. This shall include any summary information used to track quality control, including any charts and graphs.

C. The Contractor’s QCP shall be incorporated into and become part of this contract after the plan has been accepted by the Government. Changes made after KO or COR acceptance shall be submitted in writing to the KO or COR for review and acceptance. The Contractor’s QCP shall be maintained throughout the life of the contract and shall include the Contractor’s procedures to routinely evaluate the effectiveness of the plan to ensure the Contractor is meeting the performance standards and requirements of the contract.

D. DLA will implement a Quality Assurance Surveillance Plan (QASP) to ensure acceptable performance is achieved. The KO or COR will tailor the QASP based on the Contractor’s QCP. The QASP documents QCP effectiveness and provides a systematic method to evaluate the services the Contractor is required to furnish. Failure to perform a missed or incomplete documentation submission that negatively impacts DLA operations, for example, may result in remedial actions by the Government. Failure to perform that results in circumstances that cannot be quantified as a dollar value may result in the issuance of a Contract Deficiency Report (CDR) that defines the specific failure to perform, requests the Contractor investigate and document the circumstances, and directs the Contractor to institute a course of action that will preclude a reoccurrence. Specific failure to perform or an act of willful negligence that can be quantified in terms of dollars may result in an adjustment to the Contractor monthly invoice. In all cases, documentation relevant to the failure to perform will be retained by the Government and may be considered during past performance evaluations and assessments.

1.8 CERTIFICATION AND ACCEPTANCE

A. The KO will identify the COR at the time of contract award. The COR is designated, along with the KO, as the primary points of contact concerning the performance requirements under this contract. The COR is designated as the point of final inspection and acceptance by the Government of all deliverables and services performed under this contract.

SECTION C-2 DEFINITIONS

2.1 DOD DICTIONARY

A. The DoD Dictionary of definitions and terms is available on the Internet at http://www.dtic.mil/doctrine/dod_dictionary.

SECTION C-3 GOVERNMENT- FURNISHED COMPUTERS AND DATA

SYSTEMS

3.1 GOVERNMENT–FURNISHED COMPUTERS AND DATA SYSTEMS

A. The Government will provide computers and access to resources and information to include

Government data systems required for performance of work under this contract. The Government will furnish training for Contractor personnel on the Government data systems at no additional cost to the Contractor.

B. Contractor access to Government-Furnished IT data systems shall be granted on a “need-to-know” basis, IAW DLAI 6401 IA Management Controls and IA Technical Controls, to Contractor personnel who will perform data input and retrieval functions and for “clearance special access,” if applicable IAW DoD 5200.2-R. At contract award, the Contractor shall request IT access for employees requiring access and passwords to the Government- Furnished Data Systems. (See paragraph C-1.5.7, Information System Security). The Contractor shall use data systems furnished by the Government only for performance of work under this contract.

http://www.dtic.mil/doctrine/dod_dictionary

SECTION C-4 CONTRACTOR-FURNISHED EQUIPMENT, SUPPLIES,

AND TRAINING

4.1 CONTRACTOR-FURNISHED EQUIPMENT AND SUPPLIES

A. The Contractor shall furnish equipment not provided by the Government. Title to Contractor-furnished equipment shall remain with the contractor. Contractor-furnished equipment shall meet the same safety requirements as those established for government equipment.

B. The Contractor shall furnish supplies not provided by the Government.

4.2 CONTRACTOR-FURNISHED TRAINING

A. The Contractor shall provide the training, which may be required for Contractor personnel to comply with the contract requirements. The Contractor shall be responsible for all costs associated with this training. The Contractor shall maintain copies of training records, designation letters, and certificates on site and make them available for the KO or COR to review upon request. The training records shall include, at a minimum, the name of the employee, the name of the course, the source of the training, a description of the training provided, and the date the employee successfully completed the training. The Contractor shall furnish the following training:

1. SECURITY TRAINING. To ensure that all Contractor employees know and understand regulations and policy pertaining to physical, information, operations and personnel security, the Contractor shall provide security and antiterrorism training to all employees in accordance with applicable DOD regulatory requirements. At a minimum, security training requirements as required by the DLA Issuances and other applicable DOD guidance will be completed annually for: Cyber Awareness Challenge, Antiterrorism (AT) Level 1, Operations Security (OPSEC), Counterintelligence Awareness Training, Personally Identifiable Information Awareness and Trafficking in Persons. The security training is web-based and access will be provided by the Government. The Contractor shall ensure Contractor personnel have taken the required security training to meet DoD guidance and that the personnel continue to maintain their certifications.

SECTION C-5 SPECIFIC TASKS

5.1. KICK-OFF MEETING

A. The Contractor shall initiate work on this contract by meeting with the key client agency representatives to ensure a common understanding of the requirements, expectations, and ultimate end products of this PWS. The Contractor and the Government will agree upon a mutual date, time and place for the Kick Off meeting in a timely manner after contract award.

While a concerted effort shall be made to gain a thorough understanding of the client agency expectations, nothing discussed in this or in any subsequent meetings or discussions between the Government and the Contractor shall be construed as adding, deleting, or modifying any contract requirements, including deliverable specifications and due dates unless approved and incorporated into this contract by the KO.

5.2 REQUIREMENTS ANALYSIS AND MAINTENANCE SUPPORT

5.2.1 The Contractor shall identify and eliminate the root causes of the data issues. This effort will require data analysis and audits of system feeds. Eliminating the cause may require a collaborative effort with various system program offices such as the LTS and the Tracker Lite application, Distribution Standard System (DSS), Vendor Shipment Module (VSM), Management Information System (MIS), Enterprise Business System (EBS), General Fund Enterprise Business System (GFEBS), Defense Automated Addressing Systems Center (DAASC)/Global Exchange (GEX), Financial and Air Clearance Transportation System (FACTS), Global Air Transportation Execution System (GATES), Global Freight Management System (GFM), Cargo Movement Operations System (CMOS), USTRANSCOM Reference Data Management (TRDM) system, Transportation Global Edit Table (TGET), Syncada and any other current or future systems that support TFM.

The Contractor shall coordinate any necessary system requirements with the Contracting Officer’s Representative (COR) and will assist in writing systems requirement documents to identify the required corrective action.

5.2.2 The Contractor shall systematically collect and analyze transportation related data from shipping systems and U.S. Bank’s Syncada system. A systematic comparison of this data will identify disconnects in the flow of essential data. To enable this analysis, the Contractor shall create periodic data-reports and will act upon them in a real-time manner to identify data issues.

5.2.3 The Contractor shall provide Third Party Payment System (TPPS) system analysis support.

This will require expert level knowledge of the current DoD approved TPPS system and the DoD TPPS business process. The Contractor shall provide the Government with recommended process improvements that will make the TPPS process more efficient and effective. The Contractor will interface with the commercial TPPS provider, DFAS, DLA, GSA, GAO, and other stakeholders concerning the TPPS process.

5.2.4 The Contractor shall provide expert financial analysis and special studies for commercial and Working Capital Fund TFM processes.

5.2.5 The Contractor shall perform research and cost recovery tasks necessary to recover funds from incorrect and unauthorized use of funds. The Contractor shall report all invalid expenditures and reimbursement data. The Contractor shall assist financial personnel in taking all necessary actions required to receive refunds, credits, and bill corrections. The Contractor shall provide feedback to support formulation and enforcement of policy and procedures pertaining to TFM.

5.2.6 TFM Data Processing Support. The Contractor shall develop and field a data processing capability to support TFM processes. The following are minimum requirements for the data processing capability:

Initial Capability:

- Receipt, processing, and transmittal of EDI 858 transactions from DoD

Transportation Management Systems (TMS), e.g. DSS, VSM, GFM, and

CMOS

- Proper formatting of Lines of Accounting

- Application of TFM policies to ensure proper classification transportation expenditures

- Develop, implement, and maintain organizational specific business rules in LTS tools, e.g. TAC conversion business rules in the Tracker Lite application Long-term Capability:

- Receipt, processing, and transmittal of Advanced Transportation Control Movement Document (ATCMD) transactions, DoD TMS, e.g. DSS, VSM, and

CMOS

- Application of FIAR directed controls to assist in preventing improper use of TACs

- Enhancement of the LTS DD Form 1149 user registration and management processes to manage and control TACs that users are authorized to use

- Enhancement of the LTS checkbook functionality to enable obligation of funds prior to processing of a shipment

- Interface the LTS checkbook functionality with DoD accounting systems to automate the process of obligating funds prior to the processing of a shipment

- Mobile enablement of the LTS DD Form 1149 tool

- Integrate a rating engine into the TPPS TAP process

- Develop, implement, and maintain a small parcel and postal TMS tool within

LTS

5.2.7 Financial Execution Data Visibility. The Contractor shall provide full visibility of transportation financial execution data to include: USTRANSCOM and USTRANSCOM component bills, Commercial Transportation Bills, and Transportation paid for via manual funds transfers (e.g., MIPR). This execution data will include billed and unbilled transportation services.

5.2.8 Key Supporting Documents (KSD) and Proof of Delivery (POD). In accordance with future guidance issued by the TFA Executive Steering Committee (ESC), the Contractor shall make changes to LTS to include the Tracker Lite application required to achieve audit compliance.

5.2.9 LTS DD Form 1149 Interface with DSS and VSM. In support of the DoD FIAR effort, the

Contractor shall develop, implement, and maintain an interface between the LTS DD Form 1149 tool and the DSS and VSM shipment processing modules.

5.2.10 Mobile Enablement and Optimization of LTS’s DD Form 1149. The Contractor shall optimize the LTS DD Form 1149 tool to make it possible to enter data from mobile devices. The Contractor shall also develop an iOS-based app to enable authorized users to create a DD Form 1149s.

5.2.11 ACA Processing Enhancements. The Contractor shall develop, implement, and maintain LTS enhancements and / or new tools, if necessary, to enable the efficient and effective processing of ATCMD in DoD’s ACA process and ensure controls are in place to meet DoD’s FIAR requirements for funds control and obligations.

5.2.12 Auditability Documentation for LTS Tools. As required by the DoD FIAR effort, develop and maintain the necessary auditability documentation for LTS Tools, e.g.

Authority to Operate (ATO), Federal Information System Controls Audit Manual (FISCAM), Statement on Standards for Attestation Engagements (SSAE) No. 16, etc. to enable Government organizations to achieve auditability goals and the successful passage of external audits with unqualified opinions.

5.2.13 LTS Tool Systems Changes Required for Audit Compliance. If the DoD TFA working group or an auditor identifies systems changes in LTS that are required to successfully pass an audit, the Contractor shall develop, implement, and maintain the necessary changes.

5.2.14 Assignment of Multiple TACs per shipment. Develop, implement, and maintain the capability in LTS to assign multiple TACs per shipment. Based upon business rules, enable a separate TAC to be assigned for each Transportation Control Number (TCN) in a consolidated shipment. For ratio-based bills, create separate line items to permit the sharing of costs on a ratio basis. For example, Security Cooperation Program (SCP) shipments in which the U.S. Government is responsible for only a portion of the transportation costs. The foreign government is responsible for the remainder of the cost.

5.2.15 Provide audit and criminal investigation support as required.

5.3 SYSTEMS ADMINISTRATION AND SECURITY

5.3.1 The Contractor shall coordinate required database management administrative functions for the LTS to include the Tracker Lite application with the system host (Air Force 88th Comm Group). This includes, but is not limited to, monitoring system and server performance, monitoring system, server and application security, configuring system hardware and software, maintaining optimal system performance and client server administration.

5.4 TRAINING

5.4.1 The Contractor shall provide Government employees with training on TFM tools and processes, e.g. the operation and usage of the Tracker Lite application and TPPS processing.

5.5 IN-PROCESS REVIEW MEETINGS

5.5.1 The Contractor shall participate in monthly In-Process Review Meetings and provide updates on ongoing tasks.

SECTION C-6 REPORTING REQUIREMENTS

6.1 GENERAL REQUIREMENTS

A. All deliverables must meet professional standards and comply with the requirements set forth in this PWS.

B. Written Deliverables Media. The Contractor shall ensure that all data transmitted via diskette or email is virus free.

C. The Government holds the rights to all Government-specific software, coding, documentation, reports, or any other items developed under the PWS at any stage of development and at any time during the period of performance. The Contractor is not permitted to use the Government’s source code to spin off alternative commercial and/or Government software for future sales. All items shall be delivered to the Government at the end of the contract period of performance.

D. The Contractor shall provide total and complete access to all operational systems to include passwords, user IDs, data bases, as well as Government-specific software coding resident in the system at any time during the length of the contract period.

6.2 MANDATORY REPORTS

A. Contract Data Requirements Lists (CDRLs)

The Contractor shall create and distribute reports as described in the CDRLs listed below for the Government to administer performance of the contract requirements and to manage and interface with other government activities or agencies.

Title CDRL Number CAC Procedures A001 Monthly Cost Report for Travel A002

B. Contractor Manpower Report

The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Defense Logistics Agency via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk at:

http://www.ecmra.mil.

C. Quarterly Status Report (QSR)

The Contractor shall document the efforts performed in the completion of this requirement in a detailed QSR. The report shall include the contract number and the reporting period covered. QSRs shall, at a minimum, include a narrative review of work accomplished http://www.ecmra.mil/ http://www.ecmra.mil/ during the reporting period and/or significant events; problems encountered that may delay successful completion of a task, recommendations or corrective actions taken with regard to the identified problem, schedule impacts, anticipated activities for the next reporting period;

estimated completion dates of all significant milestones, deliverable process/status, description of any travel or unique services provided.

D. Technical Report

The Contractor shall provide technical reports as directed by the Government. When required, Technical Reports will be provided within 30 days of request and require no more than 10 corrections per delivery.

SECTION C-7 PERFORMANCE SUMMARY

7.0 ACCEPTABLE PERFORMANCE LEVELS (APLs)

A. The COR will monitor performance to ensure services are received and carried out IAW the standards set forth in this contract. This monitoring shall be done via Government inspection and review of the various reports and documentation generated in performance of the Tracker Lite Requirements Analysis and Maintenance Support requirements. The COR will monitor compliance with contract terms and conditions and identify nonconforming services to determine the appropriate action. All work required by this contract is subject to surveillance.

ACCEPTABLE PERFORMANCE LEVELS (APLs) PWS Paragraph Performance Requirement

Standard Acceptable Performance Standard

Method of Surveillance

5.2 Requirements Analysis and

Maintenance Support

Taskings are accurately and comprehensively completed IAW project milestones

Quality and Timeliness - 98% of taskings are accurate, comprehensive and submitted IAW project milestones

COR review

5.3 Systems Administration and

Security

Taskings are accurately and comprehensively completed IAW project milestones

Quality and Timeliness - 98% of taskings are accurate, comprehensive and submitted IAW project milestones

COR review

END OF PERFORMANCE WORK STATEMENT

The Contracting Officer Representative (COR) is:

Janice Mitchell

DLA J-345

8725 John J. Kingman Road Fort Belvoir, VA 22060 Phone - DSN: 427-1251, Comm: 703-767-1251 FAX - DSN: 427-2546, Comm: 703-767-2546 E-mail: Janice.Mitchell@dla.mil

5.4 Training Taskings are

accurately and comprehensively completed IAW project milestones

Quality and Timeliness - 98% of taskings are accurate, comprehensive and submitted IAW project milestones

COR review

5.5 In Process Review Meetings Taskings are

accurately and comprehensively completed IAW project milestones

Quality and Timeliness - 98% of taskings are accurate, comprehensive and submitted IAW project milestones

COR review

6.2 Mandatory Reports

• CAC accountability

• Travel costs

• Manpower hours

• Quarterly Status Report

Mandatory Reports are accurate, comprehensive, and timely submitted.

Quality and Timeliness – 98% of the mandatory reports are accurate, comprehensive and submitted IAW applicable timeframe.

COR review mailto:Janice.Mitchell@dla.mil