Performance Work Statement.docx

PERFORMANCE WORK STATEMENT (PWS)

JUSTICE PRISONER AND ALIEN TRANSPORTATION SYSTEM (JPATS)

JPATS MANAGEMENT INFORMATION SYSTEM (JMIS)

PART 1

GENERAL INFORMATION

The Justice Prisoner and Alien Transportation System (JPATS) is a division of the U. S. Marshals Service (USMS), which is a component of the Department of Justice (DOJ). JPATS has approximately 100 federal employees and 120 support contractors located in three sites. JPATS coordinates and transports prisoners for the U.S. Marshals Service, Bureau of Prisons (BOP), and for state and local jurisdictions. JPATS’ mission is to provide effective scheduling and safe/reliable transportation of Federal, State, Local, and military prisoners providing the best value to our customers and the taxpayer.

The Information Technology Division (ITD) staff is responsible for providing Information Technology (IT) support to meet the operational and administrative needs of the organization. JPATS IT technical support is currently provided by JPATS ITD personnel and currently supplemented by full and part time IT contractors. Approximately 90 other ITD personnel (not including contractors) across the nation service the rest of the U.S. Marshals Service and are supplemented as necessary by industry expertise.

1. GENERAL: This is a non-personal services contract to provide professional IT services for the JPATS Management Information System (JMIS) Commercial Off-The-Shelf (COTS) and custom developed products. The Government shall 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.

1.1. Description of Services/Introduction: The contractor shall provide all personnel, supervision, and other items and non-personal services necessary to perform operate and maintain the JMIS COTS and custom developed products as defined in this Performance Work Statement except for those items specified as government furnished property and services in Section 3. The contractor shall perform to the standards in this contract.

1.2. Background: Operated by the U.S. Marshals Service, JPATS is the largest transporter of prisoners in the world, handling approximately 500 requests each day to move prisoners between judicial districts and correctional institutions.

In fiscal year 1999, JPATS started operating under its own revolving fund, charging its customers for each prisoner moved. JPATS is mandated to charge actual costs back to each of its customers. Each financial expense is tracked in detail and categorized in order to bill customers accurately, provide income statements, and develop budget and pricing projections for each fiscal year and mid-year adjustment periods.

On a quarterly basis JPATS reports its financial and operational status to the USMS and BOP and must demonstrate it is operating in an efficient and effective manner, therefore this information is vital to JPATS, its customers, and auditors. Reports detailing JPATS activity and financial status must be available at a moment’s notice and on a regular basis.

The JPATS supports the federal judiciary by scheduling and transporting prisoners to courts and detention facilities around the country, including sentenced prisoners who are in the custody of the BOP. For fiscal year 2021, JPATS scheduled and moved 92,158 prisoners and scheduled 205,926 movements of those prisoners.

JPATS operates a fleet of aircraft which moves prisoners over longer distances more economically and with higher security than commercial airlines. Nearly all air movements are done aboard USMS owned or leased aircraft. On average, JPATS operates three large and one small sized aircraft per day, most of which follow a regular schedule. In addition to federal prisoners, JPATS aircraft transport non-federal prisoners as well. Military and civilian law enforcement agencies use JPATS to shuttle their prisoners between different jurisdictions at about 50 percent of commercial cost. They comprise the only government-operated, regularly scheduled passenger airline in the nation. JPATS serves approximately 40 cities, plus every other major city in the United States on an as-required basis. Integration with standard industry aviation technology tools is leveraged daily and must be maintained. Detailed itineraries are produced, maintained, and required to ensure that each prisoner appears in court at the designated time. The JPATS scheduling function is located in Kansas City, Missouri with air fleet operations located in Oklahoma City, Oklahoma and an additional hub in Las Vegas, Nevada. Technical services supporting the JPATS mission scope are continually improved to meet the evolving requirements and to maintain compliance as needed and as requested by the COR.

1.3. Objectives: There are two primary objectives that will be provided under this contract.

1.3.1. Operations and maintenance (O&M) of the JMIS application configuration, custom code, and infrastructure.

1.3.2. Application enhancements to the JMIS systems: minor enhancements that can be completed by O&M staff. Additional services may be requested which could require additional resources.

1.4. Scope: The JMIS application fulfills two roles 1) producing JPATS budget and billing and 2) scheduling transportation of prisoners. JPATS went live with the financial side of JMIS in October, 2009 and deployed the transportation side in June 2010. The system continues to be enhanced and maintained by ITD Staff and contactors in the JPATS offices in Kansas City, Missouri. JMIS provides cost accounting for all JPATS operating expenses including budgeting; billing of Federal and Non-Federal prisoners; prisoner transportation scheduling processes; air and ground route scheduling; automated prisoner and vehicle transportation planning; route optimization; business intelligence reporting and analytics; and integration with all necessary “feeder” systems (Sentry, Rockwell Collins FOS, UFMS, JDIS, and eDesignate).

JMIS is built on two Oracle COTS applications, Oracle Financials (eBS) and Oracle Logistics/ Oracle Transportation Management (OTM). A custom built interface is utilized for the transportation scheduling module using Oracle Application Express (APEX). Oracle’s Business Intelligence (OBIEE) is used as well for reporting, performance metric dashboards and analytic research. General Algebraic Modeling System (GAMS) mathematical engine is used to recommend the most optimal routes for JPATS to run in the upcoming week. This contract is for the sustainment, O&M of the JMIS application. The Government may require major/minor application enhancements and/or new products during the period of performance.

The JPATS IT Department manages systems and provides business operations support to JPATS internal business units - finance, scheduling, and management. Due to the specialized nature of JPATS’ Private Transportation Network based business, the unique nature of the supporting financial, scheduling, logistics and reporting systems, and its Agile development environment, JPATS IT requires specialized functional and technical skills to effectively support internal business units and operations. While some of this expertise is provided internally within JPATS IT, specific external contractors with significant skills, experience, and JPATS institutional knowledge provide much of the IT support to JPATS in terms of systems development, enhancements, and maintenance. The external IT team is made up of contractors who provide valuable expertise and enhance JPATS IT in the following areas:

· Infrastructure Support (Applications, Systems and Databases)

· JPATS Financial System Support (Operations, Maintenance, and Enhancements)

· JPATS Scheduling System Support (Operations, Maintenance, and Enhancements)

· JPATS Business Intelligence Support (Operations, Maintenance, and Enhancements)

· JPATS Planning System Support (Operations, Maintenance, and Enhancements)

· Route Optimizer System Support (Operations, Maintenance, Support, and Enhancements

· Business Integration Center Support (Operational, Performance, and Logistics Studies)

· Capture and MPAC Project Support (Project Management, Requirements, and Testing)

1.4.1. Infrastructure Support: The backbone of JPATS Information Technology Unit is Applications, Systems and Database Administration. JPATS maintains multiple environments of systems for development, test, user acceptance, training, and production on different servers, which must be current and fully operational during the workday. Additionally, JPATS exists as a unit within the US Marshals Service (USMS) and must maintain specific security and disaster recovery standards. In the past two years, Oracle Databases, Oracle Financials, OBIEE have been upgraded, and over 400 patches have been installed. Each of these updates presented significant challenges that required a strong understanding of Oracle COTS technology and of the JPATS software environment to implement steps that led to successful upgrade paths. In order to provide continued software infrastructure support that keeps the JPATS IT Systems current and up to date, the Systems and Database Administrators must have strong expertise and skills with a variety of technologies and workflows.

1.4.2. JPATS Financial System Support: The JPATS Financial System known as JMIS Financials. JMIS Financials is a custom system developed with Oracle Financials E-Business Suite that captures the unique operational and dynamic nature of JPATS transportation operations and related accounting considerations. JMIS Financials accounts for Budget cost and aircraft rate development and estimation and Accounting cost tracking with methods for measuring operational cost-based performance, including budget execution. JMIS Financials includes a Billing module that automates JPATS business rules for billing prisoner movements based upon the mission purpose and prisoner type. The module has advanced characteristics, in that it can process ANY change to a prior trip and formulate customer-based credits and debits to reflect those changes. Moreover, some aspects of JPATS transportation change from period to period and require adjustment by IT Staff. On a monthly basis, the team provides the JPATS business unit billing support that identifies and accurately quantifies costs for non-standard transactions such as Non-Federal Prisoners moved by JPATS whose movements began during the month but were not completed in the same month. Due to these considerations, the JPATS Financials Systems support role must have strong expertise and skills with Oracle Financials, the Oracle databases, basic finance and accounting processes and rules, and knowledge of JPATS financial processes.

1.4.3. JPATS Scheduling System Support: The JPATS Scheduling System known as JMIS Transportation is a critical operational system used by a dozen Transportation Specialists in the JPATS Scheduling Department to schedule over 100,000 prisoners on thousands of trips annually. JMIS Transportation provides the environment that enables the execution of all critical scheduling tasks including trip creation, prisoner scheduling, manifest creation and distribution, and trip closure. JMIS Transportation enables the Transportation Specialists to view prisoner information, prisoner routes, trip information, trip routes, trip volumes, and trip manifests. Finally, JMIS Transportation provides all transportation and housing operational data to interface with the JPATS Financial system, JMIS Financials. In order to maintain JMIS Transportation and effectively support Transportation Specialists with their tasks, the IT staff must have a strong working knowledge of the Transportation Specialist’s work flows and detailed knowledge of the JMIS software design. Due to the Web Based User Interface and specialized operational considerations, the JMIS support roles must have strong expertise and skills with the associated Oracle database and scheduling workflows

1.4.4. JPATS Business Intelligence Support: The JPATS Business Intelligence and Reporting System, OBIEE sits on top of the JPATS Financial, Scheduling, and Flight Operations Databases, as well as derived data marts and summary tables, which provide clear visibility into JPATS Financial and Transportation Operations Performance. In order to provide JPATS with timely and accurate information, the IT support staff must possess a good understanding of JPATS Financial and Operation business processes as well as strong knowledge of all supporting JPATS databases and BI Tools. The Business Intelligence and Reporting support role must have strong expertise and skills with the JPATS databases, the OBIEE BI Reporting Platform, and a strong understanding of JPATS business processes.

1.4.5. JPATS Planning System Support: The JPATS Assisted Routing and Scheduling System (JARS) is a system based on Oracle Logistics (OTM 6.4.1) that provides coordinated and standardized planning of Trips and Prisoners one to nine weeks out. Each night the JARS Planning Engine runs, plans and schedules 80% of the pipeline of prisoner movement requests. JARS provides schedulers with “accepted” trips each day, 4 days out, which serve as an advanced starting point from which to refine and execute. In order to provide JPATS with precise support of this detailed system, the IT support staff must possess strong experience with Transportation Network, particularly with regard the support and maintenance of the OTM components of JARS. In the past year, 225 ground schedules were created for new trips, 1,258 itineraries were updated. These were added to the existing network configuration data that has been developed over the past five years. In order to continue JARS enhancements, the JARS support role must have strong expertise and skills in OTM, Oracle databases, the JPATS Transportation Network, and the JARS implementation of the JPATS Network.

1.4.6. Route Optimizer Support: The Route Optimizer for scheduled air routes is a system implemented as a Mixed Integer Optimization Model in GAMS that is solved by the open source CBC solver. The Route Optimizer uses prisoner passenger (PAX) forecasts using the time based location of planned and scheduled prisoners and scheduler logic for prioritizing the filling of route legs to drive the selection of PAX maximizing route sets. The Route Optimizer also includes operational constraints such as flight duration, airport visits, three leg trips, four leg trips, stops, and routes that users can adjust to develop operationally acceptable route schedules. The Route Optimizer Support Role must have strong expertise and skills in mathematical optimization, GAMS, CBC, and the algorithms used to develop PAX forecasts.

1.4.7. Business Analytics and Logistical Studies Support: JPATS Business Integration Center (BIC) has an interest in conducting ongoing business analysis of JPATS Transportation Operations in order to improve performance and reduce cost. The nature of the work ranges from short single day historic operational performance studies to longer multi-week operational design studies involving the assessment of vehicle, route, and location options along with demand patterns. Route demand studies are periodically performed to identify aircraft capacity that meets historic and future projected demands. The Analyst role supporting the more involved BIC initiatives must have strong expertise and skills in SQL, data analysis, statistical analysis, demand analysis, transportation logistics, the JPATS transportation network, and JPATS operational processes.

1.4.8. Capture and MPAC Project Support: In FY 2016, the USMS embarked on an organization wide case management and operational system replacement called Capture. This system has replaced JDIS for Prisoner Management, Investigations Management, and Judicial Security cases. This new system, along with MPAC, requires new web service based systems interfaces with the JPATS Management Information System (JMIS) to fully support the Prisoner Management Cases. JPATS, BOP and USMS also began a high-priority development initiative known as the Electronic Movement Packet (MPAC) Project. These systems both interface with JMIS and each other. The JMIS IT Team is highly involved in the key services required for ongoing support for these projects. These include project management, business process definition, requirements definition and management, webservice interface development, and functional testing. Deep knowledge of the JPATS movement request process, manifest creation, movement packet information, and JPATS prisoner movement process is required to provide the necessary ongoing support for the initiative.

1.5. Period of Performance (POP): The period of performance shall be for 6-months, April 1, 2023 to September 30, 2023.

1.6. General Information

1.6.1. Quality Control: The contractor shall continue to use the current quality control program to ensure services are performed in accordance with this PWS. The contractor shall continue to use the current procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which he assures himself that his work complies with the requirement of the contract. Any recommended proposed changes to the current QCP will be in writing to the COR for approval.

1.6.2. Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3. Recognized Holidays: The contractor is not required to perform services on these observed government holidays:

· New Year's Day (January 1).

· Birthday of Martin Luther King, Jr. (Third Monday in January).

· Washington's Birthday (Third Monday in February).

· Memorial Day (Last Monday in May).

· Juneteenth National Independence Day (Third Monday in June).

· Independence Day (July 4).

· Labor Day (First Monday in September).

· Columbus Day (Second Monday in October).

· Veterans Day (November 11).

· Thanksgiving Day (Fourth Thursday in November).

· Christmas Day (December 25).

1.6.4. Hours of Operation: The contractor is responsible for conducting business, between the hours of 8am and 5pm, Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5. Place of Performance: The work to be performed under this contract will be performed at the JPATS office 1251 NW Briarcliff Pkwy, Suite 300, Kansas City, Missouri. After contractors have worked for JPATS more than 3 months and have an adjudicated background, remote access may be granted with occasional remote work permitted with prior approval from the COR. Primarily work must be conducted in the Kansas City office. Telework is authorized on an exception basis and only as approved by the COR .

1.6.6. Type of Contract: The government will award a Labor Hour contract.

1.6.7. Security Requirements: The contractor shall ensure that the person(s) to be utilized in the performance of this contract shall have submitted to the federal government the required security/suitability background investigation. The intent and purpose of the investigation is to preclude the assignment of any individual who poses a threat or unacceptable risk to the United States Marshals Service (USMS) due to past unlawful/inappropriate behavior or any issues which negatively affect his/her suitability for work on a USMS contract. The contractor shall assure that each prospective contract or sub-contract employee furnishes all required data in the form and format determined by the USMS Office of Security Programs (OSP) or the Security Programs Manager.

The government reserves the right to reject any personnel proposed to work on this contract if any derogatory information is discovered during or after the background investigation. The government also reserves the right to reinvestigate any individual working on this contract, as deemed necessary.

After completion of the background investigation, the government will review the results and determine if the individual is suitable to perform under the contract. The contractor will be informed of the suitability determination for each person in writing. The contractor is prohibited from allowing or directing any individual to perform under this contract prior to the authorization of OSP.

Whenever a Contractor employee has been the subject of a prior background investigation that was conducted by an investigative unit of another federal government agency and the investigation meets the standards prescribed in the following paragraphs, an approval may be granted provided that: there has been no continuous (not cumulative) break in federal contract/service employment of more than two (2) years, and the required investigation was conducted no more than 60 months prior to the date of the award and a favorable adjudicative decision was made. If the prior investigation does not meet such standards, a supplemental or additional investigation shall be conducted. Even though a previous investigation is accepted as meeting the standard, a current FBI National Crime Information Center (NCIC) check must be completed. An OF-306, Declaration for Federal Employment and a Department of Justice form 555 may also be required. Acceptance of a prior investigation does not in and of itself convey approval for access to USMS facilities or information systems. The OSP will be the final authority on the suitability of the previous investigation.

The/These position(s) is/are to be considered moderate public trust position s. Work under this contract is SENSITIVE BUT UNCLASSIFIED (SBU).

Applicants selected, and subsequently approved by the USMS, shall have limited unescorted access to USMS space while in the performance of their duties and during normal business hours.

All personnel employed by the contractor under this PWS are subject to meeting personnel security requirements as set forth by the USMS and other applicable rules and regulations. Contractor personnel, who require access to a USMS facility for six months or longer and/or who require "unescorted access" to USMS space and/or access to USMS IT systems, will be subject to identity proofing and other provisions of HSPD-12. A USM-394 is designed for this purpose. Contractor applicants must appear in person before the COR, or other government employee, or an authorized representative of the contracting company and present two original forms of proper identification, one of which is a valid federal, state or county government issued picture identification. Please refrain from using a Social Security card or a copy of a birth certificate. (Photo IDs are usually the best). The USMS representative or other authorized representative must then authenticate the identity of each person and complete sections II of the USM-394 and sign on the appropriate line . The contractor must supply an e-mail address for each applicant and should be included on the USM-394. The OSP team will then create an online account in the Office of Personnel Management (OPM) system known as the Electronic Questionnaire Investigative Processing (e-QIP) and transmit instructions via e-mail to the applicant or point of contact if a new background is needed. The contractor applicant must comply with the instructions as failure to do so could adversely affect their ability to commence work. The OSP will advise the COR of the results of the background investigation by issuing either an approval or disapproval notice.

The contractor is responsible for pre-screening prospective employees for suitability to work on this contract and for assuring that all prospective employees have a government performed background investigation completed prior to assignment to the contract. The contractor shall ensure that the person(s) to be utilized in the performance of this contract have been approved by the USMS OSP as a result of the government performed background investigation required by this contract section.

The OSP may grant a temporary waiver (conditional approval) after receipt of favorable NCIC/NLETS inquiries, a review of a recently completed security questionnaire, favorable results of the FBI fingerprint check and verification of the scheduled date by OPM of the required background investigation, and if a written request was forwarded to and approved by the Assistant Chief in OSP.

During the life of the contract, the Contractor or COR shall report to the OSP any significant incidents involving individuals previously cleared and assigned to this contract. Significant incidents include, but are not limited to, arrests, convictions, adverse civil judgments, liens, seriously delinquent financial accounts or administrative disciplinary actions or any other matter which could negatively affect the integrity and efficiency of the USMS. Based on the information provided, the USMS OSP will make a determination as to whether an employee may continue to work on this contract. Persons convicted of felonies will be considered unsuitable for employment under this contract as well as other serious crimes even if not a felony. Each arrest history will be reviewed carefully. If the Contractor fails to report current significant incidents and the USMS subsequently uncovers such information, the matter could be referred to the USMS Office of General Counsel and/or the Procurement Office for further review for default.

In compliance with Section 24, Personnel Security, of DOJ order #2640.2E, Information Technology Security, foreign nationals are not authorized to access or assist in the development, operation, management or maintenance of Department of Justice IT systems including all component systems unless a waiver is granted by the Head of the Component, with the concurrence of the Department of Justice Department Security Officer (DSO) and the Chief Information Officer (CIO).

1.6.8 Information Security: The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured. It shall be understood that throughout the performance of this contract, the contractor will have access to information that is the sole property of the federal government and/or other organizations. The contractor and staff will be required to enter into a confidentiality agreement with USMS that ensures the non-disclosure of information relating to this project outside of the USMS and other agencies or organizations identified by USMS.

1.6.8.1 Limited Official Use (LOU): Unclassified information that has been determined to require protection against unauthorized disclosure must be identified as LOU to ensure that all persons having access to the information are aware of the protection requirement. The preferred method of identification of LOU material is to mark “LIMITED OFFICIAL USE” on the header and footer of each page.

1.6.8.2 Media Disposal and Reuse: When no longer usable, CDs, DVDs, tape cartridges, thumb drives and other similar items used to process Sensitive But Unclassified (SBU) shall be destroyed by cross-cut shredding, incineration or degaussing, whichever method is available, appropriate, and cost effective as determined by the contractor.

Any Contractor-owned equipment used to process or store USMS data shall be sanitized according to Government regulations when the Contractor-owned equipment is disposed of or at the end of the contract.

When no longer required for mission or project completion, IT storage media that will be reutilized, media shall be overwritten with software and protected consistent with the data sensitivity and/or at the highest classification level at which they were previously used, whichever the contractor deems appropriate.

1.6.8.3 Key Control: The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.8.4 Office Alarm System Combinations: Contractors with a favorably adjudicated background may be required to arm and disarm office alarm system if they are the first to arrive or the last personnel to leave the office space. The Contractor shall establish and implement methods of ensuring that any alarm combinations are not revealed to unauthorized persons. These procedures shall be included in the Contractor’s Quality Control Plan.

1.6.8.5 Emergencies: While in USMS facilities, or other government facilities on USMS’s behalf and as part of this contract, the Contractor shall comply with posted evacuation procedures and instructions provided by security and emergency management personnel.

1.6.8.6 Mail and Deliveries: All mail and deliveries to all USMS facilities are subject to inspection at any time. Personal mail and package deliveries are prohibited at USMS facilities without prior approval thru the COR. All mail and deliveries to all USMS facilities must be routed through the appropriate mail receiving points. The designated Contractor staff who are arranging for delivery of mail or packages shall coordinate with appropriate USMS representative as directed by the COR.

1.6.9 Special Qualifications: See Paragraph 1.6.12 below.

1.6.10 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officer’s Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.11 Contracting Officer’s Representative (COR): The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.12 Key Personnel: The follow personnel are considered key personnel by the government: Senior Software Developer, Senior Oracle DBA, and OTM Application Consultant. The contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The Program Manager or Technical Lead shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The Program Manager or Technical Lead shall be available between 8:00 a.m. to 4:30 p.m. Central Time, Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons. It is not necessary for the Program Manager to work on site.

The contractor shall notify the Contracting Officer prior to making any changes in key personnel proposed for this contract. Key personnel are defined as: personnel identified in the proposal to be assigned for participation in the performance of the contract; personnel whose resumes were submitted with the proposal; or individuals who are designated by agreement of the Government and the contractor during negotiations. The contractor must demonstrate that the qualifications of prospective personnel are equal, or better than, the qualifications of the personnel being replaced.

Qualifications for all key personnel are listed below:

1.6.12.1 Program Manager and/or Technical Lead: Will have strong project and employee management skills and shall be responsible for providing overall project management for IT solutions. The senior project manager will be looked to for guidance, decision-making, and task management on issues related to the execution and delivery of the USMS IT program as laid out by the PWS. The individual will maintain ongoing work plans and will ensure that all work is carried out is in alignment with the goals and objectives of the USMS as defined by the IT management, COR, PWS, and any other individuals identified by the COR. The Program Manager will be a key contributor and leader to the contracted IT team for planning, budgeting, and other general management issues that the COR will identify and are outlined in the PWS.

1.6.12.2 Senior Software Developer: Must have 10 or more years’ experience and a high degree of proficiency in configuring and administering the following software products including knowledge of these versions:

· Oracle Financials E-Business Suite version 12.2.4

· Oracle Transportation Management 6.4 (Oracle Logistics)

This position must have 5 or more years’ experience and possess a working knowledge of the following areas:

· Bi-annual Budget Cycles

· Annual and monthly Cost Accounting Cycles

· Development of bi-directional financial data integration processes

Additionally, this position must have 5 or more years’ experience in in the following areas:

· Federal Activity Based Accounting

· Federal Budgeting

· Strong Oracle Applications Development Skills (Oracle Reports, Oracle Forms, Forms Personalization, BI Publisher, SQL Developer)

· Functional understanding of JPATS Billing Cycle and Budgeting Processes

· Strong understanding of and experience with Oracle Financials:

· System architecture

· Accounts Receivable (AR) module and how the system enables JPATS billing cycles

· General Ledger (GL) module from a perspective of reporting financial statements (e.g. Trial Balance, Income Statement, etc.) and reporting journal activity

· Version upgrades and regression testing

· Understanding of the use of Oracle Support (and effective management) for resolving issues with the “off the shelf” ERP software package.

· Good communications skills needed for interaction with members of the JPATS Business and Scheduling teams

1.6.12.3 Senior Oracle DBA: Must have 10 or more years’ experience in administration of the following operating systems and software including knowledge of these versions:

· Redhat Linux versions 6 and 7

· Weblogic application server (Oracle Fusion Middleware) 12.2.x

· Oracle Database version 12.1.0.2

· Oracle Financials E-Business Suite version 12.2.4

· Oracle Business Intelligence version 12.2.1

Additionally, this position must have 5 or more years’ experience in administration of the following software including knowledge of these versions:

· Oracle Applications Express (APEX) software development environment version 4.2/5.1

· Nagios Monitoring System version/PNP4Nagios version 4.x

· Oracle Transportation Management 6.4 (Oracle Logistics)Oracle RESTful Data Services v3.x

· Oracle Reports Server v12.2.1

· Apache Tomcat v7.x / 8.x

· Functional understanding of JPATS infrastructure, systems and agency interconnectivity

1.6.12.4 OTM/Oracle Logistics Specialist: must possess strong experience with Transportation Network, particularly with regard to Multi-Modal Private Fleet Scheduling and Order routing over sequences of multi-stop trip segments using Oracle Transportation Management (Oracle Logistics). Specifically, the Oracle Logistics Specialist role requires the following skills:

· Strong Experience with Itineraries, Ground Schedules, Rates, and Refnum Qualifiers.

· Strong Experience with Large Scale Data Design, Configuration, Upload, and Integration.

· Experience with Agents and Workflow Design and Development.

· Experience with Individual and Bulk Order Planning Automation.

· Experience with Multi-Threaded Parallel Processing.

· Experience with UI Customization.

· Expertise in systems integration to support integration with Oracle Logistics and the custom Scheduling System.

· Functional understanding of JPATS transportation and scheduling systems and processes.

1.6.13 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations 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 members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.6.14 Contractor Travel: It is anticipated that no travel will be required for this contract. If, on rare occasions, a contractor is requested to travel outside of the Kansas City area, JPATS will fund the travel by reimbursing travel cost directly to the contractor. If more extensive travel is necessary, a contract modification will be produced to allow the contractor to bill JPATS, through a monthly billing process.

1.6.15 Other Direct Costs: No other direct costs are anticipated.

1.6.16 Data Rights: The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.6.17 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

PART 2

DEFINITIONS & ACRONYMS

2 DEFINITIONS AND ACRONYMS:

2.1 DEFINITIONS:

2.1.1 CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2 CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3 CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4 DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5 DELIVERABLE. Anything that can be physically delivered but may include non-manufactured things such as meeting minutes or reports.

2.1.6 KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7 PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8 QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.10 QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11 SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.12 WORKDAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.13 WORK WEEK. Monday through Friday, unless specified otherwise.

2.2 ACRONYMS:

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3 GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1 Services: The Government will provide IT support to ensure Government provided hardware is connected and working properly on the Government network infrastructure. Also, contractors will have Government provided E-mail and inter office communication tools.

3.2 Facilities: The Government will provide the necessary workspace for the contractor staff to provide the support outlined in the PWS to include desk space, telephones, computers, and other items necessary to maintain an office environment.

3.3 Utilities: The Government will provide all utilities in the facility (electricity, water, heating and cooling) and will be available for the contractor’s use in performance of tasks outlined in this PWS. The Contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount to accomplish cleaning vehicles and equipment.

3.4 Equipment: The Government will provide approved configured hardware to perform the support outlined in this PWS. In addition, contractors will have access to, scanners, fax machines, printers, copiers, computer display projectors, etc. The Contractor shall take all reasonable actions necessary to protect Government property and may be liable for any loss or damages.

3.5 Materials: The Government will provide printer/copier paper, and Standard Operating Procedures and Policies.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4 CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The Contractor shall furnish all supplies, equipment, facilities, and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2 Security Clearance: The contractor shall follow the security requirement in section 1.6.7 above.

PART 5

SPECIFIC TASKS

5 Tasks:

5.1 Program Management Support: Provide assistance to JPATS IT staff and managers in initiating, planning, executing, monitoring and controlling and closing IT projects and contracted functions. (See Performance Objectives 1-7)

5.2 Research Analysis & Design: Conduct a wide spectrum of analyses, surveys, studies and designs related to IT initiatives. (See Performance Objectives 8-11)

5.3 System Development: Creation or reengineering of a logical series of applications that perform required business functions. This will include, but not be limited to, design review, software / system coding, testing, demonstrations, documentation, and acceptance by the COR. (See Performance Objectives 12-21)

5.4 System Integration: Integrate diverse components, such as hardware, software, telecommunications, data and processes to function as a cohesive system. (See Performance Objectives 22-23)

5.5 Information Assurance: Protection of systems and information in storage, processing, and transit from unauthorized access or modification. (See Performance Objectives 24-25)

5.6 System Deployment: Deliver completed production system, where major enhancements and new products may be assigned (as additional CLIN(s)). Generally, these tasks will require additional resources, however existing O&M resources may be able to complete some or even a majority of the development effort. (See Performance Objectives 26-28)

5.7 Change Management: Ensure the integrity and traceability of the system are recorded, communicated and controlled during development and maintenance. (See Performance Objectives 29-31)

5.8 Systems Operations and Maintenance (O&M): Operation, maintenance and administration of existing systems architectures, including hardware and software, applications, databases and operating systems. (See Performance Objectives 32-34)

5.9 Training Support: Develop and conduct training as identified by the COR.