C1 12639519D0050.pdf

AWARD/CONTRACT

2. CONTRACT (Proc. Inst. Ident.) NO. 3. EFFECTIVE DATE

5. ISSUED BY CODE 6. ADMINISTERED BY (If other than Item 5)

UNDER DPAS (15 CFR 700)

4. REQUISITION/PURCHASE REQUEST/PROJECT NO.

7. NAME AND ADDRESS OF CONTRACTOR (No., street, country, State and ZIP Code)

1. THIS CONTRACT IS A RATED ORDER RATING PAGE OF PAGES

8. DELIVERY

9. DISCOUNT FOR PROMPT PAYMENT

10. SUBMIT INVOICES

(4 copies unless otherwise specified)

TO THE ADDRESS SHOWN IN

ITEM

CODE

CODE CODE

FACILITY CODE

11. SHIP TO/MARK FOR 12. PAYMENT WILL BE MADE BY

41 U.S.C. 3304 (a) ( 10 U.S.C. 2304 (c) (

13. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION: 14. ACCOUNTING AND APPROPRIATION DATA

12639519D0050/ZO1566566003Z 09/20/2019

USDA-AMS-33SM

USDA AMS C&T

100 RIVERSIDE PARKWAY

SUITE 101

FREDERICKSBURG VA 22406

See Schedule OTHER (See below)FOB ORIGIN X

CODE

IPP

Invoice Processing Platform (IPP) All invoices must be submitted electronically through the Invoice Processing Platform (IPP) via www ipp gov

X See Schedule) )

SCD-C

15A. ITEM NO 15F. AMOUNT15E. UNIT PRICE15D.

UNIT

15C.

QUANTITY

15B. SUPPLIES/SERVICES

Continued

15G. TOTAL AMOUNT OF CONTRACT $0.00

16. TABLE OF CONTENTS

(X) SEC. DESCRIPTION (X) PAGE(S) DESCRIPTION SEC.

A

B

C

D

E

F

G

H

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

SOLICITATION/CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/COSTS

DESCRIPTION/SPECS./WORK STATEMENT

PACKAGING AND MARKING

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

CONTRACT ADMINISTRATION DATA

SPECIAL CONTRACT REQUIREMENTS M

L

K

J

I

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

CONTRACT CLAUSES

LIST OF ATTACHMENTS

REPRESENTATIONS, CERTIFICATIONS AND

INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

OTHER STATEMENTS OF OFFERORS

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PAGE(S)

17. CONTRACTOR' S NEGOTIATED AGREEMENT (Contractor is required to sign this document and return copies to issuing office.) Contractor agrees to furnish and deliver all items or perform all the services set forth or otherwise identified above and on any continuation sheets for the consideration stated herein. The rights and obligations of the parties to this contract shall be subject to and governed by the following documents: (a) this award/contract, (b) the solicitation, if any, and (c) such provisions, representations, certifications, and specifications, as are attached or incorporated by reference herein. (Attachments are listed herein.)

No further contractual document is necessary. (Block 18 should be checked only when awarding a sealed-bid contract.)

documents: (a) the Government's solicitation and your bid, and (b) this award/contract.

sheets. This award consummates the contract which consists of the following in full above, is hereby accepted as to the items listed above and on any continuation including the additions or changes made by you which additions or changes are set forth

Solicitation Number

SEALED-BID AWARD (Contractor is not required to sign this document.) Your bid on 18.

20C. DATE SIGNED

(Signature of the Contracting Officer)

20B. UNITED STATES OF AMERICA

20A. NAME OF CONTRACTING OFFICER

19B. NAME OF CONTRACTOR

19A. NAME AND TITLE OF SIGNER (Type or print)

BY

(Signature of person authorized to sign)

19C. DATE SIGNED

BY

STANDARD FORM 26 (Rev. 3/2013)

Prescribed by GSA - FAR (48 CFR) 53.214(a)

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is NOT usable

X

BEVERLY S. BROWN

09/20/2019

CONTRACTING OFFICER WILL COMPLETE ITEM 17 (SEALED-BID OR NEGOTIATED PROCUREMENT) OR 18 (SEALED-BID PROCUREMENT) AS APPLICABLE

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

2 2

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

See Schedule

12639519D0050/ZO1566566003Z

(A) (B) (C) (D) (E) (F)

Tax ID Number: 20-5533502

DUNS Number: 792532835

PRIME:

Small Business Administration

SUB:

1101971306#

VERACITY CONSULTING INC

8100 NEWTON STREET

#210

1101971306#

OVERLAND PARK KS 66204-3623

Design, configuration, construction, unit and integration testing, deployment support, maintenance support, and production support for the Warehouse Examination System (WES II).

Period of Performance: 09/20/2019 to 09/19/2024

0001 Design, configuration, construction, unit and integration testing, deployment support, maintenance support, and production support for the Warehouse

Examination System (WES II).

Obligated Amount: $0.00

Product/Service Code: D302

Product/Service Description: IT AND TELECOM-

SYSTEMS DEVELOPMENT

The total amount of award: $4,000,000.00. The obligation for this award is shown in box 15G.

AUTHORIZED FOR LOCAL REPRODUCTION OPTIONAL FORM 336 (4-86)

Sponsored by GSA

FAR (48 CFR) 53.110

Section B: The Schedule

The labor rates and labor categories listed below will be used to price the task orders issued under this contract.

Labor Category Labor Hour Rate

United States Department of Agriculture Agricultural Marketing Service

Electronic Warehouse and Commodity Management Data (eWCMD)

Statement of Work (SOW)

P a g e | 2 eWCMD Project - Statement of Work (SOW) eWCMD Statement of Work (SOW)

Table of Contents

32T1.32T 32TOBJECTIVE32T

32T2.32T 32TBACKGROUND32T

32T3.32T 32TSCOPE32T

32T4.32T 32TESTABLISH AGILE DEVELOPMENT PROCESSES32T

32T5.32T 32TTASKS (FFP priced sprints)32T

32T6.32T 32TTECHNICAL ENVIRONMENT32T

32T7.32T 32TDEFINITIONS32T

32T8.32T 32TADDITIONAL DEFINITIONS32T

32T9.32T 32TDELIVERABLES (CLINS)32T

32T10.32T 32TINSPECTION AND ACCEPTANCE32T

32T11.32T 32TPERFORMANCE MATRIX32T

32T12.32T 32TPERFORMANCE REQUIREMENTS (DELIVERABLES)32T

32T13.32T 32TPROJECT MANAGEMENT32T

32T14.32T 32TKEY PERSONNEL32T

32T15.32T 32TAGILE EXPERIENCE32T

32T16.32T 32TCODE COMMENTING REQUIREMENTS32T

32T17.32T 32TSECURITY REQUIREMENTS32T

32T18.32T 32TSECURE CODING REQUIREMENTS32T

32T19.32T 32TSYSTEM ACCESSIBIILITY TO THOSE WITH DISABLITIES32T

32T20.32T 32TDATA SECURITY32T

32T21.32T 32TGOVERNMENT ROLES AND RESPONSIBILITES32T

32T22.32T 32TTECHNOLOGY REFRESHMENT CLAUSE32T

32T23.32T 32TPLACE OF PERFORMANCE32T

32T24.32T 32TGOVERNMENT FURNISHED PROPERTY32T

32T25.32T 32TCOMPLIANCE WITH INTERNET PROTOCOL v6.0 (IPv6)32T

32T26.32T 32TOWNERSHIP OF SOURCE CODE32T

32T27.32T 32TCONTRACTOR HOSTING REQUIREMENT32T

32T28.32T 32TRECORDS REQUIREMENTS32T

32T29.32T 32TTHIN CLIENT CONFORMANCE32T

32T30.32T 32TPROPOSAL FORMAT AND LIMITATIONS32T

32T31.32T 32TINVOICE REQUIREMENTS32T

P a g e | 3

1. OBJECTIVE

The purpose of this Statement of Work (SOW) is to contract for enhancements to and an expansion of the Electronic Warehouse and Commodity Management Data (eWCMD) project currently underway by the Warehouse and Commodity Management Division (WCMD) of the Agricultural Marketing Service (AMS). This project initially began as a replacement for the Delphi-based Warehouse Examination System (WES), but the core project team expanded the scope with modifications to the current contract. This contract will add enhancements and additional functionality to replace the remainder of the Commodity Operations Management Systems (COMS) including the Grain Inventory Management System (GIMS), the Cotton User Marketing Certificate System (CUMC), and the Miscellaneous Commodities Inventory System (MCIS).

2. BACKGROUND

Formed as a result of the dissolution of the Farm Service Agency’s Deputy Administrator for Commodity Operations (FSA-DACO) and subsequent reorganization into AMS’s newly created Fair Trade Practices Program, the Warehouse and Commodity Management Division consolidated warehouse operations and commodity management functions.

The License and Storage Contract Branch administers the United States Warehouse Act (USWA) (codified at 7 USC 241 et seq. and regulated at 7 CFR 735) and Commodity Credit Corporation Storage Agreements issued under the authority of the CCC Charter Act (codified at 15 USC 714 and regulated at 7 CFR 1421, 1423, and 1427). This includes calculation of available net worth, bonding requirements, assessment of user fees (USWA only), issuance of service licenses (USWA only), and other activities. In addition, LSCB administers the Economic Adjustment Assistance for Textile Mills Program (EAAP) and the Special Competitive Provisions for Extra Long Staple Cotton (ELS).

Examination Branch conducts examinations of warehouses licensed under the USWA and warehouses holding CCC Storage Agreements, as well as EAAP participants and various other examinations as stakeholders require and request.

Commodity Management Branch acquires and disposes of CCC-owned commodities, typically pledged as collateral for Marketing Assistance Loans. CMB also establishes posted county prices for each county in the United States for several commodities, each day.

WCMD operates under the following mandates:

• Acquire and dispose of commodities pledged as collateral for marketing assistance loans.

Pledged commodities include: wheat, corn, soybeans, oilseeds, cotton, peanuts, and other commodities.

• Market, manage and regularly analyze the location, condition and quantity of CCC inventories such as cotton, grain, oilseeds, peanuts, sugars and rice.

• Establish posted county prices for locations throughout the U.S. to develop loan rates and loan deficiency payments and marketing assistance loan repayment rates.

• Administer the CCC Storage Agreements for grain, rice, cotton, processed commodities, sugar and peanuts.

• Administer the USWA and perform warehouse examinations and audits in support of USWA and CCC Programs.

P a g e | 4

• Process requests for loan cotton transfers which enables sellers to pre-position their cotton for faster response to sales opportunities.

• Administer the Economic Adjustment Assistance for Textile Mills Program which provides payments on eligible cotton, assisting manufacturers to keep their facilities competitive with worldwide competition.

3. SCOPE

The following items will be in scope for this contract:

1. WCMD -General

a. Ability to send direct communication in a filtered subset to entities

i. Emergency and Temporary Storage Notifications

ii. WA-125 Due reminders

iii. Notice to Industry

iv. Catalog of Forfeitures, etc.

b. Ability to solicit updates to entity information and have the entity directly enter the updated information. The Information updated would be approved by WCMD staff before record is finalized.

2. Licensing and Storage Contract Branch

a. Financial Review Operations – application using the business entity information from eWCMD to track warehouses’ fiscal year end, whether financial statements have been submitted, create form letters for delinquency in submission, and to calculate net worth of program participants.

b. Financial Assurance & Bonding Evaluation – application to evaluate financial assurance requirements under the USWA based on functional unit capacity by state and retains information about warehouse operators’ bonds, Irrevocable Letters of Credit or Treasury Notes and allowable capacity based on net worth. For both USWA & CCC purposes, additional bonding may be needed for operators to meet the financial requirements. The system shall also be able to maintain and track those additional elements.

c. Service License Management – the USWA requires each warehouse to have at least one person licensed by AMS to inspect, sample, classify, or weigh any agricultural product stored or handled in their warehouse. This process consists of the following steps

i. Application – either submitted hard copy or through the stakeholder portal (under development)

ii. Processing – ensuring that the applicant is sufficiently qualified and has the proper authority from the warehouse operator.

iii. Issuance – printing, executing, and mailing the license to the warehouse operator.

iv. Invoicing – properly reflecting the charge on the warehouse operator’s account.

v. Management – maintenance of the license including amendments for name changes or movement between licenses of the same warehouse operator.

vi. Communication for Examination – conveying this information to the Examination Branch for verification during examinations.

P a g e | 5

d. Temporary Storage – the USWA allows warehouse operators to store commodities in Temporary Storage space that is included as permanent licensed space and bonded throughout the calendar year. However, this space is only authorized for a limited time throughout the year and dependent on market conditions. WCMD staff tracks the usage of this space and authorizations. System will need to facilitate this tracking and authorizations including any extensions.

e. Emergency Storage – the USWA allows warehouse operators to store commodities in emergency space, upon request, for certain lengths of time. These requests must be tracked by licensee. The process includes the following steps:

i. Application – submitted by email.

ii. Invoicing – this action incurs a licensing fee that must be properly reflected on the warehouse operator’s account.

iii. Extensions – from time to time, extensions are granted. This also needs to be tracked.

iv. Management – including reducing the amount in store and removing the commodities as they are returned to permanently licensed space.

f. USWA Licenses –

i. Application – made on form WA-50 and are submitted either by email or hard copy.

ii. Tracking – licensing is a process requiring the completion of several steps and is reliant on outside entities like software developers or printers for inspection and weight certificates and warehouse receipts, bonding companies or financial institutions, and accountants.

iii. Issuance – printing, executing, and mailing the license to the warehouse operator.

iv. Invoicing – this action incurs a licensing action fee that must be properly reflected on the warehouse operator’s account.

v. Management – licenses can be amended, which begins this process over, suspended, cancelled, or revoked. All these actions must be tracked and require additional steps by WCMD staff.

g. Storage Contracting Invoicing – warehouse operators are sent and certify an invoice against the Commodity Credit Corporation for storage of forfeited commodities in store in their respective warehouses. Additionally, CCC may take ownership of commodities in support of its stabilization mission. In these cases, warehouse operators would be due both storage and handling charges.

i. Calculation

1. Bushels/Tons/CWT/bales

a. Forfeited – Lots will be tracked on the warehouse receipt information obtained from CLIPS, LPAS, or directly from the paper or electronic warehouse receipt

b. Non-Forfeited – these lots will be tracked by WCMD staff then entered into the system

2. Storage Rates – this information is submitted by the warehouse operator and accepted by WCMD staff on behalf of the CCC under the UGRSA, CSA, SSA, PCSA, or PSA.

P a g e | 6

3. Days (or parts thereof) – this will be calculated either by the forfeit date (in the event of a forfeiture), the deposit date (in the case of non-forfeited), the liquidation date, and or the redelivery date.

ii. Certification – warehouse operators certify the invoice prepared by WCMD staff, on behalf of CCC for payment.

iii. Adjustment – in the event of an error in the aforementioned calculations, or should the quality of CCC interest commodities deteriorate, the warehouse operator or the CCC may make adjustments to the initial invoice.

iv. Payment – certified invoice information will be transmitted to the Financial Management Modernization Initiative (FMMI) to be paid to the warehouse operator without delay.

v. Auditing – all payment processes are subject to auditing at the Division, Agency, Department, and Government level and should be able to be reviewed. Additionally, CCC payment information is a matter of the public record and may be subject to Freedom of Information Act requests. All efforts should be made to make this data easily accessible by staff to fulfill any such requests.

3. Commodity Management Branch

a. Market Discovery – this process utilizes market closes and discovered prices to feed in to the Posted County Price system. This process is currently all manual and consists of the following components:

i. Closes – daily market closes

ii. Gulf – price discovery in this area then transferred into PCPII

iii. Pacific Northwest – price discovery in this area then transferred into PCPII

iv. Minnesota – price discovery in this area then transferred into PCPII

v. Eastern – price discovery in this area then transferred into PCPII

vi. Oilseeds – price discovery in this area then transferred into PCPII

vii. Pulses – price discovery in this area then transferred into PCPII

b. Comparison Mapping – WCMD staff compares a file from a 3P rd P party vendor to the

Posted County Prices established by staff. This data is then exported to ArcGIS for analysis and review.

c. Security Requirement – information gathered by and contained in items a and b is strictly confidential. Any solution will have to have extremely limited access.

4. Examination Branch

a. Warehouse Inventory System – ability for warehouse operators to access their warehouse charts and diagrams and to input inventory information via the portal.

This information must be deleted on a specified time frame. USDA personnel must NOT have access to view this information.

5. Integrations – WCMD hopes to integrate with the following applications:

a. webTA

i. eWCMD Time and Expense – this application allows examiners to record their time and expenses and assign such to specific work functions. The summaries of this data, broken down into appropriated and user fee funded, are currently entered into the National Finance Center’s Kronos application.

P a g e | 7

b. FMMI

i. Accounts Receivable

1. LSCB-License Related Invoicing

a. Licensing Action Fees

b. User Fees

c. Service License Fees

d. Custom Measurement Fees

2. LSCB-Storage Contract Invoicing

a. UGRSA, PSA, SSA, PCSA, CSA application, inspection, and reinstatement fees

ii. Accounts Payable

1. Economic Adjustment Assistance for Textile Mills

2. Special Competitive Provisions for Extra Long Staple Cotton

3. Storage Payments

c. EWR

i. Transmission of warehouse receipt data for warehouse examinations

(CERRS) and forfeitures.

d. eGrain

i. Transmission of warehouse receipt data for warehouse examinations and forfeitures.

4. ESTABLISH AGILE DEVELOPMENT PROCESSES

It is intended that software development processes and deliveries under this SOW deliver incremental capabilities in short, time-boxed sprints. Resources for agile software requirements management should be employed to support incremental delivery. The development will be executed to leverage the commercial IT agile development cycle to deliver high-quality and valuable capabilities frequently to AMS. The Contractor is expected to use agile guiding principles to increase return on investment, improve simplicity of code, and minimize technical debt.

The Government anticipates that the Contractor shall propose an estimated agile development team size. The agile team shall include an appropriate mix of skilled individuals (e.g., scrum master, systems architect, analyst, programmer, tester, and configuration manager).

Requirements Definition

Requirements definition shall use agile development methodologies to capture capability needs through user stories. Decisions to add, delete, or modify user stories will involve the agile team, but all decisions will be approved by the product owner.

Software Development Iterations and Continuous Integration

Software development shall follow agile development methodologies using short duration iterative development cycles or “sprints” that produce demonstrable “interim deliveries” of production ready software. These deliveries of capabilities may or may not be implemented in the production environment. The time required to create delivery iteration depends on release planning, complexity of features, etc. Iterations may also be based on a fixed time cycle, with variances in the number of

P a g e | 8 features developed. The Contractor is expected to use continuous integration best techniques in developing software solutions.

Software Releases

Production releases shall be based on the release plan determined by the product owner. Most agile projects will require several iterations, culminating in a release to production. The size and complexity of the user stories will drive the number and length of the iterations and release schedules.

Release Planning

The Contractor shall participate in the release planning, including feature selection, with other Government directed representatives. Release planning will be led by the Government, but the Contractor shall provide knowledge and input deemed critical by the Government to the planning process.

Product Testing

Product testing in the agile development process requires frequent engagement of the customer and testers. Agile development shall include use of automated regression testing techniques and utilities as part of a continuous software integration process. Regression testing will include testing to verify that new application updates do not introduce new bugs. The Contractor shall ensure all products are thoroughly tested during each sprint prior to user acceptance testing. The Contractor shall identify, and correct product testing issues identified throughout the agile development process, especially during the critical period of integration testing for a releasable set of software features.

The Contractor shall develop a Government-approved roadmap of potentially shippable releases in accordance with agile development methodologies. The Contractor shall develop and test in the Government’s environment. The Contractor shall, as directed, provide impact analysis of changes to the backlog with development iterations. The Contractor shall create a Government-approved inspection, analysis, or test procedure for each software delivery iteration.

Software Conformance

The Contractor shall design and develop applications to meet existing and planned AMS architecture and deployment requirements and conform to AMS application non-functional requirements.

The Contractor shall design and develop applications to comply with requirements for assessment and authorization that is required in advance of production deployment. The Contractor shall conduct security scans as required by the government using government provided tools. The Contractor shall develop software iterations to satisfy the government approved technical specification.

Testing

Test cases will be developed before coding begins to support the test driven development. The Contractor shall iteratively test (e.g. unit, functional, system, interoperability, regression, security, and performance) the software throughout each sprint using industry best techniques of continuous integration methods and automated regression testing utilities. Testing materials (scripts, P a g e | 9 configurations, utilities, tools, plans, and results) shall be maintained under configuration control using identical methods applied to source code. The Contractor shall develop and deliver testing materials in a format that allows the Government to reproduce the testing procedures and results within their own environment. The Contractor shall conduct testing related to non-functional requirements, including load, performance, and installation testing.

The Contractor shall correct and repair software defects throughout the agile software development process identified through all testing (e.g. unit, system, functional, security, performance, and load testing) procedures. The Contractor shall conduct inspections and provide analysis of testing results as necessary to deliver production-ready code at the close of each sprint.

The Contractor shall develop and test in the Government’s environment. The Contractor shall include the user and customer as part of the iteration tests and demonstrations as required. The Contractor shall collect system, application performance, and load data as part of the testing process. Testing scripts, utilities, test execution, and testing results shall be historically maintained under configuration control for comparison and analysis. Each sprint, the Contractor shall deliver code that is ready for user acceptance testing.

Support of Integration Testing

The Contractor shall support the Government’s efforts to conduct integration testing of software deliverables within the Government’s pre-production environment. User acceptance will also take place in the pre-production environment.

Repair of Defects

The Contractor shall correct and repair software defects discovered during Government testing procedures. Defects include issues found within the software, installation procedures, documentation, or other items relevant to successful testing and deployment of a releasable software delivery.

Outstanding defects that are discovered during the 90-day warranty period will be addressed in a technical debt sprint at no cost to the Government.

Deployment Instructions

The Contractor shall create software deployment instructions sufficient for the government to complete each release.

Delivery Contents

The Contractor shall deliver as part of a software application the installation kits, all related source code, software build scripts and instructions, and associated design, development, and testing artifacts.

Transfer of Software

After each sprint, the definition of “done” shall include the transfer of all code and configurations from the development environment (within USDA) to the Government’s pre-production environment.

P a g e | 10

5. TASKS (FFP priced sprints)

Table 1: Tasks and Deliverables (FFP priced sprints) The vendor shall facilitate user story workshops and establish the backlog. Since an agile approach will be used for the development process, user stories may be implemented as essential, deferred for later releases, or deemed unnecessary. The user stories shall be implemented based on priority. Any update to user stories or design elements will be reviewed and approved by the product owner with input from the team. User stories that are added shall be placed in the appropriate place in the product backlog in TFS.

No. Task Task Description Deliverables

User Story Workshops

The Contractor shall elicit, analyze, and document the user stories to support the agile development. As part of this task, the Contractor will review the users’ business process, conduct interviews with project stakeholders, and ensure that the documented requirements clearly, completely, and correctly represent the users’ business needs. To capture the user stories, the contractor shall:

• Facilitate JAD Sessions with the user community which includes: data cooperators, MN reporters, management, and data users.

• Conduct interviews with Subject Matter Experts (SMEs).

• Review current database definitions, including database structures, input, output and report formats

• Review the current Microsoft Word template formats and functionalities

Review functionality that mimics new functionality the new system will use, the government will provide acceptable examples.

Product Backlog

2 Design System design will be performed iteratively as part of each sprint. Designs may include, but are not limited to sketches on a whiteboard, detailed models, or other examples which describe the system requirements, operating environment, system and subsystem architecture, files and database design, input formats, output layouts, human-machine interfaces, detailed design, processing logic, and external interfaces.

Sketches, detailed models, prototypes

P a g e | 11

3 Application Development

The Contractor shall develop or configure specific open-sourced code to address each functional area using an agile approach.

A test driven development (TDD) approach shall be used throughout the various iterations to validate the requirements and obtain user acceptance. The development shall be tested continuously.

The solution shall be developed incrementally throughout the various iterative development stages with the goal of deploying production releases. This includes, but is not limited to input screens, workflows, reports, custom reports, and interfaces for both internal and external users.

Source Code (deployable increments of software at the end of each sprint)

4 Testing Testing shall be performed iteratively during each sprint. Automated testing shall be performed to support the time boxed sprints.

Integration and Stress testing shall be performed throughout the migration.

Test Plan

Test Report (Test reports include the results of all tests performed including Performance, Load, Security, Unit, System, Functional tests, etc.).

5 Implementation Application Administrator and End-User documentation shall be accurate and complete at the close of each sprint. User stories may or may not be implemented at the end of every sprint. When user stories are approved for production release, the Contractor shall develop a release plan.

Application Administrator and End User Documentation

Release Plan

6 Project Management

The Contractor shall develop a Government approved roadmap of potentially shippable releases in accordance with agile development methodologies.

The Contractor’s project manager (i.e., scrum master) shall coordinate and plan sprints in conjunction with the product owner. The project manager will coordinate sprint planning meetings that will include reviewing the product backlog with the product owner and identifying the stories, features, and tasks for the subsequent sprints.

Sprint Backlog

Product Roadmap

Improvement Plans

Burn down Chart

P a g e | 12

As part of the sprint planning meeting the team will discuss the sprint objectives with the product owner, and ask clarifying questions and remove ambiguity.

As part of each sprint planning meeting the Sprint Backlog will be groomed.

The Contractor’s project manager shall designate production release points using the release plan (as approved by product owner).

The Contractor’s project manager shall facilitate sprint retrospectives with the team at the end of each sprint. Improvement plans will be documented as outputs of the sprint retrospectives. The Contractor’s project manager shall provide the burn-down chart at the end of every sprint that reflects the work remaining to be done.

7 Technical Debt Sprint

There shall be a 90-day warranty provided after the Contractor implements a new production release point to the Government.

Defects include issues found within the software, installation procedures, documentation, or other items relevant to the solution development. Outstanding defects that are discovered during the 90-day warranty period will be addressed by a technical debt sprint at no cost to the Government.

Technical Debt Sprint

Test Results

Test Summary Report

6. TECHNICAL ENVIRONMENT

The AMS Technical Environment Standards are defined in Appendix A.

7. DEFINITIONS

Abbreviation Definition

AMS Agricultural Marketing Service

CFR Code of Federal Regulations

CIO Chief Information Officer

COR Contracting Officer’s Representative

CMMI Capability Maturity Model Integration

COTS Commercial Off the Shelf

P a g e | 13

CSV Comma Separated Value File

CMB Commodity Management Branch, Warehouse and Commodity Management Division

EVM Earned Value Management

EB Examination Branch, Warehouse and Commodity Management Division

FAR Federal Acquisition Regulations

FFP Firm Fixed Price

FTPP Fair Trade Practices Program

GSA General Services Administration

IIS Microsoft Internet Information Server

IT Information Technology

ITS Information Technology Services

IP Internet Protocol

JAD Joint Application Design

LSCB License and Storage Contract Branch, Warehouse and Commodity Management Division

MBI Moderate Background Investigation

NIST National Institute of Standards and Technology

NITC National Information Technology Center

PAAS Platform as a Service

PM Project Manager

SOW Statement of Work

SSRS SQL Server Reporting Service

TFS Microsoft Team Foundation Server

USDA United States Department of Agriculture

WAN Wide Area Network

WCMD Warehouse and Commodity Management Division

WORKING DAYS Monday through Friday excluding Federal holidays.

WSG Web Style Guide

VPN Virtual Private Network

8. ADDITIONAL DEFINITIONS

Abbreviation Definition

CONTRACTOR A supplier or vendor having a contract to provide specific supplies or service to the government.

P a g e | 14

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.

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.

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

DELIVERABLE Anything that can be physically delivered but may include non-physical things such as Status Meetings.

KEY PERSONNEL Contractor personnel 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 listed in the proposal.

9. DELIVERABLES (CLINS)

The Contactor shall adhere to the performance requirements and acceptance criteria in this Statement of Work. The standards and measurements applicable to each deliverable are listed under the INSPECTION AND ACCEPTANCE section. Satisfactory work performance shall be based on the performance matrices within these Tables. If deficiencies are identified, the USDA project manager and COTR will provide the Contractor’s project manager in writing, a description of all deficiencies to be corrected by the Contractor. Deliverables, work performed, and documentation shall be corrected within 5 business days at no additional cost to the Government. This will be considered as rework of the original task.

10. INSPECTION AND ACCEPTANCE

The USDA product owner and COR will review the Contractor’s deliverables. Satisfactory performance shall be based on the performance requirements cited above in Tables 5, 6, and 7. If deficiencies are identified, the COR will give the Contractor’s project manager a written description of all deficiencies to be corrected. The identified deficiencies shall be corrected within 5 calendar days at no additional cost to the Government. Corrections will be considered a rework of the original task.

11. PERFORMANCE MATRIX

DEL Deliverable Description Performance Standards

Maximum Allowable Degree of Deviation Requirement

Method of Surveillance Maximum Consequence

1 Product Backlog

The Contractor shall provide an initial set of backlog items. The Contractor shall estimate the backlog list using relative estimates (i.e. Fibonacci series estimation) and work with the product owner to prioritize the stories to identify the “must haves”, “should haves”, “could haves”, and “won’t haves”.

The contractor shall work with the product owner and team to groom the backlog

Document meets 100% of AMS requirements 100 % Inspection

Complete task at no additional cost to the government

2 Source Code The contractor shall develop source code to satisfy all defined requirements.

The System performs as defined in the system requirements System satisfies all defined business requirements When deployed at the close of a sprint, system operates in the production environment

100 % Inspection Complete task at no additional cost to the government

3 Test Plans, Test Cases, and Test Results

The contractor shall develop the test plan, test cases and the test summary report for each sprint.

The contractor shall ensure that the test cases detail the test steps, test conditions, expected results, and inputs and actual results for each test case. At the end of each sprint, the contractor

Document meets 100% of AMS requirements

100 % Inspection Complete task at no additional cost to the government

P a g e | 16

Description Performance Standards

Maximum Allowable Degree of Deviation Requirement

Method of Surveillance Maximum Consequence shall deliver a test summary report that summarizes the test results.

4 Product Roadmap

The contractor shall develop a government approved roadmap of potentially shippable releases in accordance with Agile development methodologies.

Document meets 100% of AMS requirements

100 % Inspection Complete task at no additional cost to the government

5 Improvement Plans

The contractor’s project manager shall facilitate sprint retrospectives with the team at the end of each sprint.

Improvement plans will be documented as outputs of the sprint retrospectives to improve subsequent sprints.

Document meets 100% of AMS requirements

100 % Inspection Complete task at no additional cost to the government

6 Release Plan The contractor shall deliver a release plan for coordinating and planning production releases. The release plans shall include the features to be delivered, along with corresponding release dates, key milestones, and dependencies.

Document meets 100% of AMS requirements

100 % Inspection Complete task at no additional cost to the government

7 Sprint Plan The contractor shall deliver a sprint plan before each agile sprint. The sprint plan shall include all the stories that the product owner has selected for the current sprint.

Document meets 100% of AMS requirements

100 % Inspection Complete task at no additional cost to the government

8 Sprint backlog The sprint backlog shall be developed as part of sprint planning meetings before each sprint. The sprint backlog shall list all the stories for a given sprint. The stories shall be listed in the sprint backlog based on priority.

Document meets 100% of AMS requirements

100 % Inspection Complete task at no additional

P a g e | 17

Description Performance Standards

Maximum Allowable Degree of Deviation Requirement

Method of Surveillance Maximum Consequence

9 Burn Down Chart

The vendor shall provide the burn down chart at the end of every sprint that will reflect the work remaining to be done

Document meets 100% of AMS requirements

100 % Inspection Complete task at no additional cost to the government

10 Test Results and Test Report (from the Technical debt sprint)

If defects are found within the 90-day warranty period, the vendor shall be responsible for fixing the defect at no cost to the Government. The vendor shall provide test results and test summary report.

Document meets 100% of AMS requirements

100 % Inspection Complete task at no additional

Table 7: Contract Line Items

CLIN# CLIN DESCRIPTION

Product Roadmap: The product road map shall include all potentially shippable releases in accordance with Agile development methodologies. The product roadmap shall include the key features and characteristics that the product will need to deliver in order to achieve the product vision. Please refer to Table 3 above for the performance criteria for the product roadmap.

Release Plan: The vendor shall develop a release plan based on the prioritized and estimated user stories that were defined for the project. The release plan shall include the features to be delivered, along with corresponding release dates, key milestones, and dependencies. The release plan shall be based around the team’s anticipated velocity. This release plan shall be updated as needed. Please refer to Table 3 above for the performance criteria for the release plan.

Agile Development Sprints: This task shall include the efforts to plan and execute each agile sprint.

Before each sprint, the contractor shall work with the product owner and agile team to determine the stories for each sprint. Each sprint shall include all the development lifecycle tasks, which shall be performed iteratively to produce production ready software. Please refer to Table 2 and 3 above for all the tasks and deliverables that will be performed in each agile sprint.

12. PERFORMANCE REQUIREMENTS (DELIVERABLES)

All software and hardware delivered under this contract shall become the property of AMS.

Documentation shall be in Microsoft Word 2013 or current version or Portable Document Format (PDF) as pre-approved by the USDA project manager and Contracting Officer Representative (COR). The Contractor shall provide documentation in electronic format as well as one hard copy.

AMS shall have 10 working days to review draft deliverables and provide comments to the Contractor for inclusion in the final product. The Contractor shall have 5 days to provide revised deliverables per AMS comments. Deliverables shall become final after all revisions have been reviewed and accepted by AMS.

13. PROJECT MANAGEMENT

The Contractor is responsible for assigning a Project Management Institute (PMI) certified Project Manager to ensure the timely accomplishment of each task and provide the Contracting Officer Representative (COR) and Contracting Officer (CO) with weekly progress reports. At a minimum, the progress reports shall describe problems encountered, proposed solutions, and impact on the time schedule. The cost incurred by the Contractor to provide project management services shall be included in the prices of other technical deliverables under this Statement of Work.

14. KEY PERSONNEL

The Contractor’s Project Manager and Lead Technical Support Personnel are considered Key Personnel to this effort. The Contractor shall provide advance notice and the replacement’s resumé if there is a personnel change. The Contractor shall staff the Operations and Maintenance with a minimum of two personnel that have both USDA site and IT system access.

P a g e | 19

It shall be the contractor’s reasonability to ensure proper training and pass down has occurred for any key replacement staff. Any cost associated with training the replacement staff shall be borne by the contractor.

The contractor shall identify personnel that are planned to staff this migration effort. The contractor shall provide the technical qualifications, education, or certifications that demonstrate to AMS the proven capabilities of these individuals.

15. AGILE EXPERIENCE

The Contractor must have proven successful experience using Agile on past projects. While SCRUM is preferred, the Contractor may demonstrate experience using other Agile practices (i.e.

using iterative and incremental development).

Personnel Skills

The Contractor shall provide individuals with the following skills:

• Agile development (preferably SCRUM methodology)

• Agile project management (the Contractors will be required to demonstrate past experience successfully managing Agile projects. It is preferred that the Contractor’s project manager have at least 5 years of proven Agile project management experience).

• Test Driven Development

• Refactoring

• Continuous Integration

• Analysis (experience writing user stories is required)

• Software quality assurance

• Configuration management

• Automated testing (including functional, load, performance, and regression).

• Information assurance

• Web services development and Service Oriented Architecture (SOA) design

• Graphical user interface design and construction

• Microsoft.Net development processes and tools/utilities

Key Roles

The Contractor shall provide individuals with proven skills and experience to provide the following key roles in the Agile software development effort:

• Scrum Master should be a Certified Scrum Professional 43Tor hold PMI-Agile Certified Practitioner (ACP) Certification and have at least 5 years proven experience successfully leading Agile projects. The required demonstrable experience shall not include experience on traditional waterfall projects. All 5 years shall be Agile project management experience.

43T

• Developer is preferred to be a Certified Scrum Developer and should have at43T least 3-5 years proven experience in Extreme Programming (XP) on Agile projects43T. The Agile framework does not separate functions; therefore all members of the technical team will function in the

P a g e | 20

Developer role. The developers should have at least 3-5 years of experience in the following:

Agile Analysis (e.g., capturing user stories), Design, Development, Agile Testing, Configuration Management, and Systems Architecture. The demonstrable 5 years of experience should be on Agile projects.

Note: Preference will be given to existing Agile teams with established velocity and successful delivery of systems using Agile frameworks.

16. CODE COMMENTING REQUIREMENTS

The vendor shall comment on all code based on industry best practice. The comments should provide adequate details needed to understand the logical flow, behavior and purpose of the code that is written. At a minimum, code comments should describe the intent of the code; provide an algorithmic overview, and the logical flow of the code. Code comments should also identify who wrote the code, when the code was written, and if/when code updates are made the name of the developer who updated the code and the purpose for the updates. Please use these links for additional guidance for development in Microsoft Visual Studio (32TUhttp://msdn.microsoft.com/en-us/library/xzysab5k.aspxU32T and 32Thttp://msdn.microsoft.com/en-us/library/ms172653.aspx32T).

17. SECURITY REQUIREMENTS

The Contractor shall be responsible for properly protecting all information used, gathered or developed as a result of work under this contract. The Contractor shall also protect all government data, equipment, etc. by treating information as sensitive. The contractor shall be responsible for the following:

• Prior to beginning work, all key personnel and any contractor personnel requiring access to AMS production IT information systems must be properly cleared, at a minimum, with an appropriate security clearance/investigation of a Federal Public Trust Moderate Background investigation

(MBI).

• All contractor personnel shall complete annual USDA provided security and privacy training.

• All Contractor personnel shall sign a Non-Disclosure Agreement and a Rules of Behavior

Agreement with AMS.

18. SECURE CODING REQUIREMENTS

The Contractor shall ensure the application is developed in a secure manner. AMS uses the IBM Rational AppScan tool (32Thttp://www.ibm.com/developerworks/rational/products/appscan32T) for determining vulnerabilities. The Contractor shall develop custom software that does not contain any High, Medium, or Low vulnerability including the vulnerabilities listed on this website:

(32Thttp://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project32T). If there is a justifiable reason why any Medium or Low vulnerability is irresolvable, the contractor may submit a written justification to the AMS CIO requesting an exemption from this requirement. The justification shall include the reason why this exemption should be granted.

If any solution is developed using third party software the vendor shall ensure that all code vulnerabilities are addressed before delivering the solution to the government. Third party software without source code is exempt from this requirement. The contractor may submit a written http://msdn.microsoft.com/en-us/library/xzysab5k.aspx http://msdn.microsoft.com/en-us/library/xzysab5k.aspx http://msdn.microsoft.com/en-us/library/ms172653.aspx http://www.ouncelabs.com/ http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project

P a g e | 21 justification to the MRP ACIO requesting an exemption from this requirement. The justification shall include a reason why this exemption should be granted.

19. SYSTEM ACCESSIBIILITY TO THOSE WITH DISABLITIES

In accordance with Section 508 of the Rehabilitation Act of 1973, as amended, all systems procured on or after June 21, 2001, shall be 508 compliant. In addition, data shall be gathered during the JAD sessions (if applicable) that give due consideration to any special assistive accommodations to users with disabilities in accordance with Section 508 of the Rehabilitation Act as amended. The result of the assessment shall be incorporated in the written deliverables.

The Contractor shall be certain that all technology delivered complies with standards set forth in Section 508 of the Rehabilitation Act of 1973, as amended, particularly 36 CFR 1194.21-22. For more information, refer to 32Twww.section508.gov32T.

The system shall comply with the standards, policies, and procedures below. In the event of conflicts between the referenced documents and this Statement of Work, the Statement of Work (SOW) shall take precedence.

Rehabilitation Act, Section 508 Accessibility Standards

1. 29 U.S.C. 794d (Rehabilitation Act as amended)

2. 36 CFR 1194 (508 Standards)

3. 32Twww.access-board.gov/sec508/508standards.htm (50832T standards)

4. FAR 39.2 (Section 508)

5. USDA Standards, policies and procedures (Section 508) In addition, all contract deliverables are subject to these 508 standards as applicable.

Regardless of format, all Web content or communications materials produced, including text, audio or video - must conform to applicable Section 508 standards to allow federal employees and members of the public with disabilities to access information that is comparable to information provided to persons without disabilities. All contractors (including subcontractors) or consultants responsible for preparing or posting content must comply with applicable Section 508 accessibility standards, and where applicable, those set forth in the referenced policy or standards documents above. Remediation of any materials that do not comply with the applicable provisions of 36 CFR Part 1194 as set forth in the SOW, shall be the responsibility of the contractor or consultant.

The following Section 508 provisions apply to the content or communications material identified in this SOW:

36 CFR Part 1194.21 a - l 36 CFR Part 1194.22 a - p 36 CFR Part 1194.31 a - f 36 CFR Part 1194.41 a – c

The contractor shall provide a completed Section 508 Product…