TAPS IDIQ Solicitation_AG-3151-S-11-0025.pdf

Tobacco Assessment and Payment System (TAPS) Page 1 of 120 Solicitation: AG-3151-S-11-0025

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

B.1. SCHEDULE OF SERVICES

The purpose of this contract is to acquire, on an Indefinite Delivery Indefinite Quantity (IDIQ) basis, information technology services for the maintenance, functionality, reporting, and enhancement of the Tobacco Assessment and Payment System (TAPS).

Except as may be otherwise expressly set forth in this contract, the Contractor shall furnish all personnel, facilities, equipment, material, supplies, and services, in performance of the services specified under Section C – Performance Work Statement (PWS) and delivered within the Deliverable Schedule and within the period of performance specified in Section F – Deliveries or Performance.

B.2. PRICE SCHEDULE

All Task Orders issued will be on a Labor-Hour (LH) and/or Firm-Fixed-Price (FFP) basis, with pricing provided in accordance with the below rate table. The labor rates in this section shall reflect the fully burdened rates of each labor category.

CLIN*

Base Period

August 1, 2011 through

July 31, 2012

Option Period

August 1, 2012 through

July 31, 2013

Option Period

August 1, 2013 through

July 31, 2014

Option Period

August 1, 2014 through

July 31, 2015 Project Leader Senior Systems Architect Senior IT Specialist IT Specialist Junior IT Specialist

*Additional Labor Categories may be recommended by the Contractor but will only be used after prior approval by the Contracting Officer.

The contractor shall be required to furnish personnel with qualifications meeting or exceeding the criteria specified in the contract governing the issuance of this requirement.

Pricing for each Task Order (TO), both FFP and LH CLINS will include the backup detail of how the CLIN price was established using the above labor category rates, estimated hours.

Tobacco Assessment and Payment System (TAPS) Page 2 of 120

SECTION C – PERFORMANCE WORK SCHEDULE

C.1.

Scope of Work

The purpose of this contract is to acquire, on an indefinite delivery, indefinite quantity (IDIQ) basis, information technology services for the maintenance, functionality, reporting, and enhancement of the Tobacco Assessment and Payment System (TAPS).

For the complete effort, as detailed in each Task Order, the contractor shall provide overall project management; and TAPS Maintenance, Functionality, Reporting, and Enhancement support.

C.2

Background and Objective

The United States Department of Agriculture (USDA), Farm Service Agency (FSA) administers and manages farm commodity, credit, conservation, disaster, and loan programs as authorized by Congress through a network of federal, state, and county offices. FSA’s administrative and programmatic functions are supported by a large network of automated systems that are maintained by its Information Technology Services Division (ITSD). ITSD is also responsible for developing new programs, replacing existing programs, and modernizing existing platforms and systems. The primary ITSD operations are located in Washington, DC and Kansas City, MO, with additional offices in St. Louis, MO.

The application maintained under this Performance Work Statement (PWS) is the Tobacco Assessment and Payment System, which is made up of two major applications-- Tobacco Transition Payment Program (TTPP) and the Tobacco Transition Assessment Project (TTAP).

TTAP provides a mechanism by which the Government can assess the Tobacco Manufacturers and Importers of tobacco per Title VI, the “Fair and Equitable Tobacco Reform Act” (FETRA) of the American Jobs Creation Action of 2004 (PL-108-357) that repealed the tobacco marketing quota and related price support programs, and provided for payments to persons who, during a certain period or at a certain time, had been the owners of farms with tobacco quotas or had produced regulated tobacco. FETRA is funded using assessments collected from tobacco product manufacturers and importers.

Under FETRA, Commodity Credit Corporation (CCC) sends out quarterly notices to tobacco manufacturers and importers, informing those entities of the assessments due to

CCC.

TTPP makes payments to tobacco quota holders and producers. The legislation also ends all aspects of the Federal tobacco marketing quota and price support loan programs effective with the 2005 crop year. Requirements for tobacco marketing quota and price support loan programs for the 2004 marketing year remained in effect through the end of the marketing season. The 2004 marketing year ended on June 30, 2005 for flue-cured

Tobacco Assessment and Payment System (TAPS) Page 3 of 120 tobacco and all other tobaccos ended on September 30 2006. The payments are made in 10 equal annual installments that began in 2005 and will end in 2014.

This system is required to:

• support FSA’s efforts to deliver new software applications in the web environment;

• support a move toward customer centric systems;

• interface with the required applications, resolving material weaknesses;

• improve project planning, reporting and communication among stakeholders by supporting the Integrated Management System initiative;

• facilitate data entry accuracy and field operations;

• generate standardized reports;

• improve adherence to Style Guide standards and Section 508 compliance; and

• allow for all necessary audit functionality and increased data sharing with our partner agencies.

The Government’s ultimate objective under this program is to provide TAPS Maintenance, Functionality, Reporting, and Enhancement in order to ensure the user’s needs are met and that standards and regulatory requirements are achieved.

C.3 Functional Area (FA)

The following may be requested.

C.3.1 FA 1:

Conduct a Startup Briefing:

Within one week of the IDIQ award, the Contractor shall conduct a startup meeting with the Government if the Government so requests. The Contractor shall NOT prepare an elaborate briefing nor is it required that the Contractor expend significant resources for this task. The intent of this briefing is to initiate the communication process between the Government and the Contractor by introducing key participants and explaining their roles, reviewing communication ground rules, and assuring a common understanding of the contract requirements and objectives. The briefing shall be held at the Government’s facility. Both parties shall agree to the date and time. The result of this briefing shall include the following:

• Government and Contractor personnel working under this contract shall be introduced.

• If the Contractor is working onsite, the Government will show the Contractor the applicable facilities.

• The Government will provide to the Contractor, the agreed to Government

Furnished Property at this time. Refer to Contract Section H. in its entirety.

• Any issues concerning the Minimum Background Investigation for Contractor employees shall be discussed.

• The Contractor shall demonstrate confirmation of their understanding of the work to be accomplished under this PWS. All Government and Contractor expectations

Tobacco Assessment and Payment System (TAPS) Page 4 of 120 shall be addressed and discussed. Results shall be documented by the Contractor and delivered to the Government within two (2) days of the completion of the briefing.

C.3.2 FA 2:

Overall Project Management

Overall project management includes day to day on-site project management and direction of the work assigned to the Contractor, reporting of project status, and participation in Disaster Recovery activities as required. The Project Manager shall be the single point of contact for communications regarding facility directives or problems and any other administrative communications. The Project Manager shall be responsible for communicating to their subordinate employees as appropriate. The creation of a “Knowledge Transfer Plan” and oversight of the execution of it shall be the responsibility of the Project Manager. The Project Manager shall ensure compliance of all SDLC, FISMA and 508 laws and regulations.

C.3.3 FA 3:

Production Maintenance Support:

The production maintenance support is as authorized by the Business Owner or Project Owner as necessary utilizing the FSA incident tracking system, currently Remedy. All Incident Reports are tracked electronically by the Application Support Group (ASG). The ticket is entered into a current call tracking database by ASG at the Beacon Facility. The Vendor will receive the ticket electronically via email.

The Contractor shall provide support to resolve production problems identified during the routine operation of the applications. These may include the need to address performance related incidents. The contractor shall be responsible for the research and resolution of problems identified as a result of production processing of the applications. These problems may include improperly functioning code and/or incorrectly implemented requirements.

Production maintenance support includes problems for either user guidance or data fixes.

The number varies according to the viability of the application and the attentiveness of the user. On average there have been less than 270 data fixes per annum.

• Incident report support for mishandled contract updates.

The definition of final deliverable for the maintenance is the successful completion of the incident report with resolution of data or user satisfaction.

C.3.4 FA 4:

Reports:

Reports are required to be delivered both out of the system and relating to the system.

Those reports are as follows:

• Incident Tracking by Sprint

• Feature Backlog

Tobacco Assessment and Payment System (TAPS) Page 5 of 120

• Sprint Backlog

• Burndown Chart

• Velocity Chart

• Sandbox (Issues tracking)

• Annual Reports o This includes lump sum payment activity by month. This is necessary as fiscal years overlap in calendar year tabulations.

TTPP Lump Sum Payment Report:

o This includes the actual TTPP payments made to Producers and

Quota Holders.

TTPP Contracts Sold Report:

o This report provides the Beginning Year Balance, Transactions

During the Year, End of Year Balance, and the Projected FY Payment Amount Due. This is to be provided after the sales closing date each year, but no later than November 30th.

SII Annual Account Reconciliation Certification:

o This report includes contracts purchased from the previous year, the buyer and seller account names, purchased date, date sold (if applicable), purchased contract identifier. Five percent of the contracts to be reviewed for all quota holder and producer contracts held by financial institutions. A maximum of 100 contracts per account, however now fewer than five contracts per account in the event an account had less than 100 contracts. If an account holds less than five contracts, then 100% of the contracts are reviewed. Additionally, the two largest contracts from each account are selected for review. This report is used to verify the signature authority, discount rate, and proof of payment. This random sample selection pulls data from January 16 through November 1 (may be a day or two later if the sales closing date lands on the first Tuesday of November in an election year).

SII Audit:

o This would encompass all payments made for a given tax year and the corresponding tax form sent.

Payment to 1099 Form Reconciliation Report:

Any payments not receiving a form would need to have an explanation provided.

Would need to be ran anytime the process is ran to obtain data for the S, INT, or OID file.

It is crucial that the report is generated timely, prior to mailing any forms to the customer, and prior to the IRS January 31 deadline.

This should include all payments receiving a $0 Form for the current tax year.

This should include all payments not receiving a form due to the Contract Gross Value.

o Quota Holder Contracts Paid after December 15:

Tobacco Assessment and Payment System (TAPS) Page 6 of 120

This report should encompass contracts receiving payments after December 15 until December 31 of current tax year.

Used to ensure all payments receive the appropriate 1099 form.

Generated the first business day of January of specified calendar year.

o

This report would need to be generated to provide information associated with the CP2100 Notice provided by the IRS.

TIN Mismatch Report:

Generated in fourth quarter of the current year once information is obtained from the IRS.

o This report would need to be generated to provide information associated with TINs identified by the IRS for mandated backup withholding.

Backup Withholding Contract Report:

Generated in December of the current tax year.

• Ad Hoc Reports from the TAPS Data Repository

• Ad Hoc Reports for TTPP-1099 processing

• Status Reports (weekly and monthly including hours expended)

The definition of final deliverable for reports is on time delivery with current, accurate, and complete data with consistent display.

C.3.5 FA 5:

Enhancements:

The contractor shall provide design and development support to all software enhancements that are resultant from:

• Implementation of modifications required to comply with directives received in Information Bulletins (IBs).

• Implementation of new/revised functionality based on user needs.

• Implementation of new/revised functionality required to comply with new legislation.

Functionality support includes problems that require code fixes. The number varies according to the viability of the application and the attentiveness of the user. On average there have been less than 30 code fixes per annum.

This support shall include analysis, design, programming, testing, implementation, and documentation support for the complete development effort:

• Analysis and design including documenting business and technical requirements and improvements to the systems

• Technical assistance

• Data conversion design and development

• Risk Analysis

• Technical Documentation

• Software Configuration Management

Tobacco Assessment and Payment System (TAPS) Page 7 of 120

• Research and development of application changes and enhancements

• Research and resolution of application problems during integration testing

• Construction

• Unit, automated, integration, and system testing

• Database management and design tasks supporting approved software changes

• Problem resolution in support of Acceptance testing

• Support for phased Production implementation (i.e. Pilots)

Enhanced software must maintain previously provided functionality including all interfaces and links to other applications.

The initial enhancement tasks are as follows:

• Completion of code corrections for IRS 1099 forms reporting for:

o Calculation corrections for OID Imputed Interest o Implementation of the Business Rules in the business layer instead of an SSIS package o Original and corrected file generation for IRS and Financial Inquires o Handling all scenarios currently handled manually as exceptions

• Completion of code enhancements for Contract Change for all reasons.

o Necessary for information discovery for the ability to handle the numerous transfers of contracts due to the aging population of the contract holders.

• Contract family ancestry lookup and display.

o Necessary for information discovery for all users in the TTPP user community.

• IRS Backup Withholding processing:

o Mismatched Tax Identification Numbers.

o Mandated IRS Backup Withholding.

The definition of final deliverable for enhancement is completion of required documentation and installation of the software into the production environment. As such the following are anticipated in the delivery:

System Enhancement Design and Documentation

• The Contractor shall provide detailed design documents and other required documents according to the SDLC and as directed by the COTR and Project Owner.

System Enhancement Code Applications According To Requirements and Standards

• The Contractor shall make necessary enhancement code and data changes, conduct unit testing, automated testing, integration and system testing in

Tobacco Assessment and Payment System (TAPS) Page 8 of 120 accordance with FSA development standards as outlined in the SDLC. Where appropriate, additional standards may be identified.

• Modifications made to the Java application shall be accomplished in accordance with FSA and SFG coding standards. The Contractor shall be responsible for all work products identified in the SDLC and as approved by the COTR and Project Owner. The Contractor shall write or modify all programs using Java object oriented programming techniques as defined by J2EE standards.

• Code must be developed with an understanding of the interface requirements of this system.

Conduct Unit, Automated, Integration, and System Testing

• The Contractor shall be responsible for unit, automated, integration, and system testing all changes or enhancements made to the applications. This is to include regression testing and creating automated tests to ensure other areas of the application are not affected by the changes. Test results shall be reviewed to determine that requirements have been satisfied and that no changes have been inadvertently made to existing functionality.

Provide Acceptance Test and Production Support

• Contractor support is needed to resolve production problems identified during the routine operation of the applications. These may include the need to address performance related incidents. The Contractor shall be responsible for the research and resolution of problems identified as a result of production processing or acceptance testing of the applications. Construct real world testing scenarios and conduct stress testing of applications and performance analysis of testing results. These problems may include improperly functioning code and/or incorrectly implemented requirements.

C.3.6 FA 6:

Application Certification & Accreditation

Task Orders may identify requirements for Contractor support of agency Certification & Accreditation documentation as required by the COTR. The contractor shall support and participate in all C&A processes and reviews, as required by the COTR.

C.3.7 FA 7:

Application Disaster Recovery

The contractor may be required to identify requirements for contractor support of agency Application Disaster Recovery processes. The contractor may be required to develop, document, update, and maintain Disaster Recovery documentation as required by the COTR. The contractor may be required to support and participate in Disaster Recovery exercises and reviews, as required by the COTR.

Tobacco Assessment and Payment System (TAPS) Page 9 of 120

C.3.8 FA 8:

Knowledge Transfer

The contractor shall perform a technology knowledge transfer to Government Personnel of the application(s) and system(s) the contractors develop and/or modify in sufficient detail to enable Government personnel to maintain the system. As required, the Contractor shall provide ongoing communication and skills transfer to Government personnel (when providing the various levels of support described in the PWS) using methodologies, development and utility tools that include, but are not limited to, those listed at C.6.5.1.

C.4 Type of Contract

This will be an indefinite-quantity contract with Firm-Fixed-Price (FFP) and Labor-Hour (LH) deliverables.

C.5 General Information

C.5.1

FSA shall provide a COTR to serve as the primary point of contact that will perform a number of important activities related to the contract including:

Program Management

● Provide authorization for all decisions relative to the project, including identification and assignment of FSA resources and to sign status reports and approve project changes.

● Provide the availability of necessary government staff resources, as well as Government Furnished Equipment, Government Furnished Property, and Government furnished information to the Contractor throughout the project’s life.

● Bear responsibility for acceptance of deliverable and verify compliance of each deliverable within the five business days.

● Define, monitor and assess the activities and deliverables of FSA personnel.

● Provide clarification on business requirements and technical design issues.

● Review and approve FSA project plans and proposed technical solutions.

● Provide the Government technical resources necessary to install application software.

● Provide test data from existing legacy system test databases to test system interfaces.

● Ensure system availability schedules for all planned testing.

● Determine when and where meetings will be held. Meetings will be conducted at the

Beacon Building, and the COTR will provide the meeting rooms, equipment, property, and materials necessary to conduct the meeting.

● The FSA COTR bears ultimate responsibility for all FSA aspects of performance.

C.5.2 Government Furnished Equipment

Tobacco Assessment and Payment System (TAPS) Page 10 of 120

The government will supply all necessary space, furniture, equipment, software and appropriate security approvals necessary to access FSA networks and associated LAN drives at the government-designated work location of 6501 Beacon Drive, Kansas City, Missouri 64133, to effectively support the work undertaken in this contract. No travel is required.

C.5.3

The contractor will have access to the entire code base that comprises TAPS, TTPP/SII and TTAP applications. All code base components will be stored and versioned with the code repository, currently SubVersion, unless otherwise specified by the Government.

Technical Information

Changes to legislation or regulations that introduce new requirements or change existing requirements to the system may occur after the contents of a release have been defined and approved. In this case, a special release can be defined.

Based on artifacts delivered, the FSA Project Manager will have five business days to review, and specifically identify in writing any deficiencies. The Contractor will then have three business days to make alterations and re-submit artifacts for final signoff within two business days unless otherwise negotiated. The deliverable signoffs will be the basis for invoicing in tandem with the monthly status report and may not occur more frequently than once a month.

Once business requirements have been accepted and approved, all modifications to those requirements will be subjected to a change control process for consideration and estimation. Should a contract modification be necessary, FSA’s Acquisition Management Division (AMD) will need to administer the contract modification.

The Contractor shall be compensated for its costs for the work completed up to the time that a Task is placed on-hold or cancelled. A contract modification may be required.

Production support responsibilities shall be required for all Contractor implemented software. Under certain conditions, malfunctions can occur and the exact cause of the malfunction is difficult to determine. These situations are of particular concern in environments supported by multiple maintenance contractors. The contractor shall be responsible for determining and implementing appropriate solutions to these problems and documenting a plan of action submitted to the COTR.

C.6 Compliance Standards and Technical Requirements

C.6.1 The Contractor shall follow the project management methodology of Rapid Development

Methodology (RDM), an Agile-like methodology, and principles as outlined by the Project Management Institute (PMI). The Contractor shall provide project management deliverables as specified by the PMI and USDA Capital Planning and Investment Control (CPIC) for each year of the contract.

Tobacco Assessment and Payment System (TAPS) Page 11 of 120

C.6.2 The contractor shall use and comply with the FSA Software Development Life Cycle (SDLC) software development methodology. The SDLC defines system development activities and documents deliverables and artifacts that shall be performed throughout the phases of the project. All Contractor performance shall ensure that:

All software processes delivered shall operate in the USDA computing environment, comply with the Government’s release management environment, and meet technical architecture requirements http://www.fsa.usda.gov/FSA/sdlcapp?area=home&subject=landing&topic=landing.

The deliverables will be in accordance with FSA’s System Development Life Cycle (SDLC) and other applicable documents as prescribed in Work Definitions.

The contractor shall leverage all common business services that are in place to the extent possible; such as Eligibility, SCIMS, NPS, Obligations, CBS, CPF.

The contractor shall be responsible for production support and respond to emergencies and system outages within one hour of notification.

Contractor support will be required during FSA primary service hours Monday through Friday from 8:00 a.m. to 5:00 p.m. Central Time. Normal tour of duty will be 40 hours per week. Technical support is provided by telephone, e-mail and in person depending on the problem.

The Contractor shall ensure all processes fully comply with Section 508 of the Rehabilitation Act, Information Technology Accessibility. (SDLC, The Rehabilitation Act of 1973, Section 508).

The Systems shall enforce security to meet and comply with the FSA’s implementation of the Federal Information Security Act (FISMA) standards -http://csrc.nist.gov/groups/SMA/fisma/compliance.html.

• Tests and unit tests cover at least 80% of the code unless specified differently in the Task Order or approved by the Contracting Officer’s Technical Representative.

• The Systems shall not compromise the security of external interfacing Systems at

FSA.

• System applications must maintain previously provided functionality.

C.6.3 Applicable Regulations and Documents:

The following documents (versions current at time of award) are incorporated with the same force and effect as if provided in full text. Succeeding revisions may be substituted or incorporated as required. The Government will provide access to available documents and technical information as required and upon contractor request for the performance of this task order.

FSA Information Bulletins documents.

Departmental Information Processing Standards (DIPS), manuals, circulars, and user requirements.

FSA SDLC documentation, to include supplements.

United States Department of Agriculture Office of Procurement and Property

Management AGAR Advisory No. 81, Revision 03.

http://www.fsa.usda.gov/FSA/sdlcapp?area=home&subject=landing&topic=landing� http://csrc.nist.gov/groups/SMA/fisma/compliance.html�

Tobacco Assessment and Payment System (TAPS) Page 12 of 120

Other policy, procedural, or technical documentation as the Government may deem necessary in order to conduct work under this contract.

C.6.4

Personal Identification Information (PII) Security Requirements

The contractor shall immediately notify the Government, in writing, of all potential, and actual, breaches in security.

All Personal Identification Information (PII) data, to include Social Security Numbers (SSNs) and Taxpayer Identification Numbers (TINs), shall not be exposed, released, disclosed or in any way compromised, intentionally or unintentionally, that may result in potential unauthorized access to PII information. In the event of a security breach in a production environment as the result of the introduction of a security vulnerability by the contractor as defined in the lists identified in C.5.7, the contractor shall be liable for the cost of mailing quota holders and producers notifications, and providing one year of credit and fraud monitoring for each impacted holder and each impacted producer.

C.6.5

Experience and Expertise

C.6.5.1 The contractor’s proposal shall include the resumes of the proposed key staffing, documenting personnel expertise and experience available to support this requirement. Documented expertise and experience and the ability to demonstrate knowledge/skills/abilities with the items (i.e.

technologies, organizations, systems, processes, etc.) listed below is highly desirable for the contractor staffing proposed to complete the task activities.

While each individual contractor employee may not possess expertise and experience in each area identified in the subsequent paragraphs, the Government requires that the overall contractor staff possess the aggregate skills, expertise, and experience in each of the areas identified to successfully complete all task requirements.

All contractor personnel shall be capable of working independently. The contractor shall adapt to changing technologies and standards leveraged by FSA/PSCAO over the course of the contract.

Working knowledge of MS SQL Server (latest three versions) and

SQL Server Management Studio.

Working knowledge of MS Office Suite 2007, especially Excel and

Word.

Working knowledge of Visio, and MS Project.

Working knowledge of Eclipse, JUnit, Jasper, iReports, STRUTS, JBoss, Maven, and Apache.

Experience using Agile or Agile-like methodology on an IT Project of related size and complexity.

Tobacco Assessment and Payment System (TAPS) Page 13 of 120

Use of standard PC workstation tools.

C.6.5.2

Education

Bachelor’s degree or higher in Information Systems, Computer Science, Engineering, Business, or related field. Qualifying experience may be substituted for education.

The Project Leader(s) shall provide on-site support and is preferred to be Project Management Institute (PMI) certified and a certified SCRUM Master. If certified, the Contractor shall provide a copy of the certificate and its expiration date.

C.6.5.3

Experience Substituted for Formal Education

When experience is substituted for formal education, the time used to substitute for a formal education requirement can be used to meet a general or specialized experience requirement for the skill category. A guideline that will be used is 12 months specialized experience equals approximately 30 semester hours of full-time study in an accredited college.

C.6.5.3.1

General Experience

Years used to satisfy the specialized experience requirements may also be used to satisfy the general experience requirements.

C.6.5.3.2

Specialized Experience

Minimum years experience required related to the particular job skill category and level. When specialized experience requirements include several different "years of experience" requirements, those years of experience may run concurrently. Personnel in any of the Labor Categories may be required to have specialized experience in either Business and Administrative Applications or Scientific Applications.

In some instances, unique requirements may require a mix of personnel. Experience that meets the specialized experience requirements may be used to meet the general experience requirements.

Tobacco Assessment and Payment System (TAPS) Page 14 of 120

C.6.6

Key Personnel

The Project Leader, Senior Systems Architect, and one Senior IT Specialist are designated as key personnel in this contract. The Contractor shall submit at least one résumé for each position designated as key personnel with their proposal.

C.6.7

Minimum requirements for the Labor Categories are as follows:

• Project Leader o General Experience

: Six (6) years of progressive IT software development and software management experience using structured system development methodologies, as well as systems life cycle management methodology.

o Specialized Experience

: Includes four (4) years of experience managing and controlling system development projects using systems life cycle management, system development methodologies, and structured analysis and design techniques. Project experience includes client-server, web-enabled, and standalone applications. At least one project of same size and complexity using Agile or an Agile-like methodology.

o Education

: Each Project Leader shall have a degree in Computer Science, Systems Engineering, or other related field with a minor or certification as a Project Leader.

o Practical experience

: The Project Leader is a senior manager responsible for coordinating the management of all work performed under a Task Order(s). The Project Leader shall act as a central contact point for the Task Order. The Project Leader is ultimately responsible for coordinating the effort of team members for the Task Order.

o The Project Leader is responsible for:

Providing competent leadership and responsible program direction through successful performance of a variety of detailed, diverse elements of projects;

Demonstrating competence using data from project management tools, in other words, PMBOK tools and theories and Agile methodologies, EVM

Simultaneously planning and managing highly technical projects and directs completion of tasks within estimated time frame and budget constraints including using EVM;

Organizing, directing, coordinating, assigning duties to subordinates, planning, and production of all the Task Order’s project activities, work products, and resource needs;

Tobacco Assessment and Payment System (TAPS) Page 15 of 120

Communications, both written and oral, with all levels of management and

Government representatives, including but not limited to, the Contracting Officer (CO), Contracting Officer’s Representative (COR), and Contracting Officer’s Technical Representative (COTR); and

Meeting with management officials regarding the status of specific Task

Order activities and problems, issues or conflicts requiring resolution.

• Senior Systems Architect o General experience

: Ten years or more of direct experience in hands-on system architecture role in architecting transformation of legacy system architecture to an object oriented web-based design methodology in a centralized computing environment, or architecting new functionality in an object oriented web-based enterprise methodology in a centralized computing environment.

o Specific experience

: Ten or more years of direct specific experience in large-scale automated system design/development. Experience in developing e-commerce applications for a Web deployment. Experience in the definition of the “enterprise-level” use cases, experience with development of use cases and common business services to establish an enterprise wide application framework.

Expertise in architecture of open, portable, and scalable web-based applications.

Experience in mentoring to a web-based environment. Has accumulated extensive experience with database and development tools capacity, (both character based and GUI based tools).

: Each Senior Systems Architect shall have a degree in Computer Science, Systems Engineering, or other related field with certification in Systems Architecture.

o Practical Experience

: Provides technical and specialized Information Technology solutions to complex problems. Prepares elaborate analyses and studies. Prepares reports and gives presentations to high-level executives and managers.

Participates in meetings, conferences, and workshops to advice users and management of transformation of legacy system architecture development and implementation issues. Works independently and/or as a member of a team.

• Senior IT Specialist o General Experience

: Eight years of progressive experience in the field of Information Technology, including six years of specialized experience in numerous, highly specialized Information Technology disciplines involving a wide range of hardware/software solutions.

Tobacco Assessment and Payment System (TAPS) Page 16 of 120 o Specific Experience

: Four years of General Experience is concentrated, hands-on experience in the specific discipline(s) of Information Technology identified in the examples below.

Senior Applications Programmer Senior Business Process Analyst Senior Business Process Reengineering Specialist Senior Computer Security Specialist Senior Data Communications Specialist Senior Data Base Management Specialist Senior GIS Systems Engineer Senior Independent Verification and Validation Evaluator Senior Information Technology Systems Engineer Senior Testing Specialist Senior Security Engineer/Specialist Senior Software Systems Specialist Senior Subject Matter Expert Senior Systems Administrator Senior Systems Programmer Senior Systems Analyst Senior Cost Analyst

: Each Senior IT Specialist shall have a degree in Computer Science, Systems Engineering.

o Practical experience

: Has experience in providing highly technical and specialized guidance, and solutions to complex Information Technology problems. Has performed elaborate analyses and studies. Has recent and relevant experience in preparing reports and presentations in support of enterprise-wide solutions and project. Works independently and/or as a member of a team.

• IT Specialist o General Experience:

Six years of progressive experience in the field of Information Technology, including four years of specialized experience in numerous highly specialized Information Technology disciplines involving a wide range of hardware/software solutions.

o Specific Experience:

Three years of General Experience is concentrated hands-on experience in the specific discipline(s) of Information Technology.

: Each IT Specialist shall have a degree in Computer Science, Systems Engineering, or other related field.

Tobacco Assessment and Payment System (TAPS) Page 17 of 120 o Practical experience:

Experience in providing highly technical and specialized solutions to complex Information Technology problems. Has prepared analyses and studies at the project level. Works independently or as a member of a team.

• Junior IT Specialist o General Experience:

Three years of progressive experience in the field of Information Technology, including one year of specialized experience in highly specialized Information Technology discipline(s) involving a range of hardware/software solutions.

: Each IT Specialist shall have a degree in Computer Science, Systems Engineering, or other related field.

o Specific Experience:

At least two years of General Experience is concentrated hands-on experience in the specific discipline(s) of Information Technology.

o Practical experience:

C.6.8

Has provided technical and specialized solutions to complex Information Technology problems. Has performed analyses and studies, and prepared detailed reports. Works independently or as a member of a team.

Work is to be accomplished through the Farm Service Agency’s Acquisition Management Division, through its contract with the selected contractor. Certification by the Government of satisfactory services provided is contingent upon the contractor performing in accordance with the terms and conditions of the referenced contract, this document, the approved technical and cost quotes, and all amendments. The client's representative, FSA's representatives, and the contractor's representative(s) shall meet when deemed necessary at the client’s request. The client representative, the FSA representatives, and the contractor’s representative may meet at the place determined by the client representative and FSA representatives.

Performance

C.6.9

Personnel Retention

The Contractor shall make every effort to retain personnel in order to ensure continuity until contract completion. If it should become necessary to substitute or replace key personnel, the Contractor shall immediately notify the COTR in writing of any potential vacancies and shall submit the resume(s) of replacement key personnel within 14 calendar days of the notification. The Contractor shall submit the resume(s) of all potential key personnel selected to perform under this contract to the COTR through ITSS for Government review and acceptance/rejection. Upon Government acceptance of a key personnel resume(s), the candidate shall be available to begin performance within 14 calendar days. The contractor shall ensure continuity of operations during periods of personnel turnover and long-term absences. Long-term absences are considered those longer than one week in duration.

Tobacco Assessment and Payment System (TAPS) Page 18 of 120

C.6.10 The Contractor shall work directly with Government personnel and possible contractor personnel from other vendors in review and implementation of specified task assignment requests.

C.7 Deliverables

C.7.1 Fixed Price

C. 7.1.1

Conduct a Startup Briefing

If requested.

C. 7.1.2

Project Management

For each Task Order, the Contractor shall prepare a Project Plan (i.e., work breakdown structure, project resource assignments, resource hours, projected task completion dates for each resource assigned, overall completion date for delivery to Acceptance Testing, and project assumptions), Product/Backlog, Burndown Chart, and a Velocity Report.

All project plans will be maintained on a SharePoint site and retained in the document repository, currently SubVersion.

If requested.

C. 7.1.3

Reporting

The definition of final deliverable for reports is on time delivery with current, accurate, and complete data with consistent display.

C.7.1.4

Production Maintenance Support

The definition of final deliverable for the maintenance is the successful completion of the incident report with resolution of data or user satisfaction.

C.7.2 Labor-hour

C. 7.2.1

Enhancements

The definition of final deliverable for enhancement is completion of required documentation and installation of the software into the production environment.

C. 7.3 Deliverables will be identified in each Task Order.

Tobacco Assessment and Payment System (TAPS) Page 19 of 120

C. 7.4

Contractor Submission.

The contractor shall provide hard copy deliverables as required per the Government’s request. All deliverables shall be produced using recommended software tools/versions as approved by the Government. All reports shall be accomplished utilizing the MS Office Software Suite to include MS Project as required.

C. 7.5

Source Code, Data Files and Job Control Language

This shall be retained in the Government’s Source Code Repository, currently SubVersion.

C. 7.6

Government Review.

Government personnel will have 10 workdays to review deliverables (to include resubmissions) and provide written acceptance/rejection. The COTR will notify the contractor of deliverable acceptance or provide comments in writing. The contractor shall incorporate Government comments, or provide rationale for not doing so within 5 days of receipt of comments. Government acceptance of the final deliverable will be based on resolution of Government comments or acceptance of rationale for non-inclusion. Additional changes volunteered by the contractor will be considered a resubmission of the deliverable.

C. 7.7 Deliverable and Data Rights

All test materials, documents, notes, records, software tools acquired, and/or software modified or produced by the contractor under the PWS shall become the property of the U.S. Government, which shall have unlimited rights to all materials and determine the scope of publication and distribution. The contractor shall be required to deliver electronic copies of all documents, notes, records and software to the Government quarterly and upon termination of the contract services or expiration of the contract period.

C. 7.8

Deliverables, Due Dates, and Performance Requirements Summary Matrix

A deliverable schedule will be identified for each Task Order.

The Performance Requirements Summary Matrix includes performance standards. The Government will perform surveillance to determine if the contractor meets or does not meet these standards. The Government will use the following standards to determine contractor performance and will compare contractor performance to the Acceptable Quality Level (AQL).

Tobacco Assessment and Payment System (TAPS) Page 20 of 120

Work Item Indicator Standard Acceptable Response Time

Acceptable Quality Level

Method of Surveillance Incentive / Disincentive

System Functionality Support; and Production Maintenance Support

Incident Report Incident report closed successfully

24 hours from approval of resolution approved by Business or Project Owner.

Data Fixed. Incident Report reviewed by

COTR.

The Contractor shall be incentivized by exercise of the option period and positive past performance.

If the Contractor fails to meet the Acceptable Quality Level and Acceptable Response Time more than two times in a month, then 1% of the monthly invoice will be assessed as a disincentive.

If Acceptable Quality Level or Acceptable Response Time is not achieved for two months, then contract performance may be deemed unacceptable.

System Enhancement

1) System interfaces with other USDA systems

2) Code Deployed to Production Environment

TCO

certification

1) 24 hours to TCO certification.

2) Agreed upon time frame not to exceed 45 days to Production deployment.

1) 99.99% uptime based upon coding issues and not equipment failure or malfunction.

2) Code Deployed with zero (0) additional defects.

1) Review by

COTR.

2) Defect Report reviewed by

COTR

Reporting 1) Status Reports Delivered (weekly and monthly including hours used).

2) Program Management Reports to include Feature and Sprint Backlog.

3) Incident Tracking Reports by Sprint.

4) Annual Reports.

5) Ad Hoc Reports.

Reports Generated

1) Timely Delivery:

Weekly- due 1 days after the end of the preceding week;

Monthly- due 5 days after the end of the preceding month.

2) Updated Daily and delivered during the Sprint meeting.

3) Updated Daily and delivered during the Sprint meeting.

4) Delivered 1 week after receipt of the request.

5) Delivered within 24 hours of request.

Timely, current, accurate, and complete reports delivered within the acceptable response time.

COTR will review reports produced by the Contractor for correctness, clarity, consistency, completeness, and timeliness.

Tobacco Assessment and Payment System (TAPS) Page 21 of 120

C.8 Abbreviations

ASG – Application Support Group

CCC – Commodity Credit Corporation

CGV – Contract Gross Value

COTR – Contracting Officers Technical Representative

CPIC – Capital Planning and Investment Control

FETRA – Fair and Equitable Tobacco Reform Act

FSA – Farm Service Agency

IBs – Information Bulletins

IRS – Internal Revenue Service

ITSD – Information Technology Services Division

OID – Original Issue Discount

PMI – Project Management Institute

PWS – Performance Work Statement

RDM – Rapid Development Methodology

S, INT, or OID file – A file created to specific requirements for layout and data to provide the information necessary to create the applicable IRS 1099 forms.

SDLC – FSA System Development Life Cycle

SII – Successor-In-Interest

SSIS – SQL Server Integration Services

TAPS – Tobacco Assessment and Payment Systems

TTAP – Tobacco Transition Assessment Project

TTPP – Tobacco Transition Payment Program

USDA – United States Department of Agriculture

Tobacco Assessment and Payment System (TAPS) Page 22 of 120

SECTION D – PACKAGING AND MARKING

D. 1 AGAR 452.247-71 - Marking Deliverables. (FEB 1988)

(a) The FSA contract/order number shall be placed on or adjacent to all exterior mailing or shipping labels of deliverable items called for by the contract.

(b) Ship to/Mark for:

Regular mail –

Paula M Steen

USDA – FSA

Beacon Facility - Mail Stop 8148 P.O. Box 419205 Kansas City, MO 64141-6205

For FedEx, UPS or DSL –

Paula M Steen

USDA – FSA

Beacon Facility - Mail Stop 8148 9240 Troost Ave Kansas City, MO 64131-3055

Email: paula.steen@kcc.usda.gov Telephone Number: (816) 926-1380

(End of Clause)

D. 2 AGAR 452.247-72 - Packing for Domestic Shipment. (FEB 1988)

Material shall be packed for shipment in such a manner that will insure acceptance by common carriers and safe delivery at destination. Containers and closures shall comply with the Interstate Commerce Commission regulations, Uniform Freight Classification Rules, or regulations of other carriers as applicable to the mode of transportation.

Tobacco Assessment and Payment System (TAPS) Page 23 of 120

SECTION E – INSPECTION AND ACCEPTANCE

E. 1 52.252-2 - Clauses Incorporated by Reference (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text may be accessed electronically at this/ these address(es):

https://www.acquisition.gov/FAR/ or, www.usda.gov/procurement/policy/agar.html

E.2 AGAR 452.246-70 - Inspection and Acceptance. (FEB 1988)

(a) The Contracting Officer or the Contracting Officer's duly authorized representative may inspect and accept the supplies and/or services to be provided under this contract.

(b) Inspection and Acceptance will be performed at:

Farm Service Agency 6501 Beacon Drive Kansas City, Missouri 64133

Paula Steen

Phone: (816) 926-1380

(c) The COTR has limited authority. The COTR is authorized to (1) review and approve travel authorizations necessary for performance of services, (2) inspect deliverables, (3) accept deliverables, (4) review and approve request for payment (invoices), and (5) coordinate services with contractor. The COTR has no authority to change or amend the terms and conditions set forth in the Contract.

(End of clause)

E.3 Inspection and Acceptance by the Government

The Government will verify that all deliverables cited within this Contract fulfill the requirement and standards stated in this Contract.

E.3.1 Responsibility for the Inspection and Acceptance

Inspection and acceptance of all items and services under this Contract will be accomplished by the Government Contracting Officer's Technical Representatives (COTR's). The COTR will inspect, and be responsible for, the review and acceptance of all deliverables under this Contract prior to its acceptance by the Government Contracting Officer/Contract Specialist. Acceptance will be performed by the COTR, or a designated representative, at the location(s) cited in Section E.2 of this contract.

E.3.2 Quality Assurance https://www.acquisition.gov/FAR/� http://www.usda.gov/procurement/policy/agar.html�

Tobacco Assessment and Payment System (TAPS) Page 24 of 120

The Government has established and will maintain a quality assurance program in accordance with FAR 52.212-4 -- Contract Terms and Conditions -- Commercial Items (June 2010). The Government will evaluate the Contractor's performance under this contract for those tasks listed in the contracts’ PWS.