Delta_Code_RFP_Amend1_5.1.19.pdf

DRUG ENFORCEMENT ADMINISTRATION

DELTA CODE SOFTWARE DEVELOPMENT

RFP No. 15DDHQ19R00000007

RFP 15DDHQ19R00000007

Table of Contents

SECTION A - SOLICITATION/CONTRACT FORM

B.1 GENERAL

B.2 MAXIMUM CONTRACT CEILING AND MINIMUM CONTRACT GUARANTEE

B.3 TRAVEL PRICING

B.4 CONSIDERATION AND PAYMENT

SECTION C – DESCRIPTION/SPECIFICATION/STATEMENT OF WORK

C.1 INTRODUCTION

C.2 BACKGROUND

C.3 OBJECTIVE

C.4 SCOPE OF WORK

C.4.1 New Applications and O&M Development Support

C.4.1.2 New Applications

C.4.1.3 Transition/O&M Development Support

C.4.1.1 Areas of Application Support

C.4.2 Mobile Application Development (future)

C.5 TASKS

C.5.1 Requirements Gathering

C.5.2 Application Mock-up

C.5.3 Participate in Daily Agile Stand-Up Meeting and Scrum of Scrums Meeting

C.5.4 Attend Monthly Planning Sessions

C.5.5 Attend Monthly mid-Sprint Reviews

C.5.6 Attend Monthly Retrospective Sessions

C.5.7 Champion Meetings

C.5.8 Use of Team Foundation Server (TFS)

C.5.9 Testing

C.5.10 Delivery of Incremental Software Beta Release

C.5.11 Delivery of Incremental Software Production Release

C.5.12 Provision of Training/Demonstrations

C.5.13 Data migration

C.5.14 Script Development

C.5.15 Documentation Support

C.5.16 Configuration Management

C.5.17 Program Management

C.5.18 Contract Transition

C.5.18.1 Transition Phase-In

C.5.18.2 Transition Phase-Out

C.5.19 Government Furnished Equipment (GFE and Government Furnished Information (GFI)

C.6 DELIVERABLES - Format/Content

C.6.1. Deliverables Table

C.7 SECTION 508 COMPLIANCE

C.8 TRAINING

C.9 DEA-2852.211-70 PERIOD OF PERFORMANCE (BASE AND OPTIONS) (March 2019)

C.10 PLACES AND TIMES OF PERFORMANCE

C.10.1 Places of Performance

C.10.2 Times of Performance

C.10.3 TELEWORK AND EMERGENCY SUPPORT FOR CONTRACTORS

C.11 Security Requirements

SECTION D – PACKAGING AND MARKING

D.1 PREPARATION FOR DELIVERY

D.1.1 Acceptance by Common Carrier

D.1.2 Excluded Packing Products

D.2 PACKING LIST

D.2.1 Marking of Shipments (Commercially Packaged)

D.3 PRESERVATION, PACKING AND PACKAGING

D.4 MARKINGS OF WARRANTED ITEMS

D.5 CLAUSES INCORPORATED BY FULL TEXT

SECTION E – INSPECTION AND ACCEPTANCE

E.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

E.1 1 Clauses Incorporated by Reference Table

E.2 CONTRACTING OFFICER REPRESENTATIVE

E.3 INSPECTION AND ACCEPTANCE

Criteria E.3.1 General Acceptance

SECTION F – DELIVERIES OR PERFORMANCE

F.1 FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

F.2 IDIQ MASTER CONTRACT ORDERING PERIOD

F.3 TASK ORDER PERIOD OF PERFORMANCE

F.4 PLACE OF PERFORMANCE

F.5 DELIVERABLES

SECTION G – CONTRACT ADMINISTRATION DATA

G.1 GENERAL

G.2 AUTHORIZED USERS

G.3 TASK ORDER ORDERING CONTRACTING OFFICER

G.4 DEA-2852.242-71 INVOICE REQUIREMENTS (MAY 2012)

G.5 DEA-2852.242-70 CONTRACTOR PERFORMANCE ASSESSMENT (JUL 2014)

G.6 DEA-2852.242-73 CONTRACTING OFFICER’S REPRESENTATIVE (MAY 2012)

G.7 DEA-2852.242-74 CONTRACT ADMINISTRATION POINTS OF CONTACT (MAY 2012)

G.8 DEA-2852.211-71 SCHEDULED AND UNSCHEDULED CLOSURES OF GOVERNMENT OFFICES (NOV 2012)

G.9 DEA-2852.242-72 FINAL INVOICE AND RELEASE OF RESIDUAL FUNDS (MAY 2012)

SECTION H – SPECIAL CONTRACT REQUIREMENTS

H.1 DEA-2852.204-85 SECURITY (October 2015)

I. GENERAL

II. CONTRACTOR’S POINT OF CONTACT

III. CONTRACTOR’S RESPONSIBILITIES

B. CONTRACTOR’S SECURITY OFFICER:

IV. DOCUMENTATION REQUIREMENTS

A. MANDATORY DOCUMENTS:

V. DISQUALIFYING FACTORS

A. CRIMINAL RECORD:

B. ILLEGAL DRUG USE:

C. FALSE STATEMENTS:

D. DEBT-RELATED ISSUES:

E. ALLEGIANCE TO THE UNITED STATES:

F. PERSONAL CONDUCT:

H.2 TRAVEL COSTS

H.3. DEA-2852.209-70 ORGANIZATIONAL CONFLICTS OF INTEREST (MAY 2012)

H.4 LIMITATIONS ON FUTURE CONTRACTING

H.5 FORMER EMPLOYMENT OR ASSIGNMENT WITH THE DEA

H.6. DEA-2852.204-78 CONTRACTOR PERSONNEL REPORTING REQUIREMENTS (JAN 2016)

H.7 DEA-2852.242-78 APPROVAL REQUIRED FOR ADVERTISING AND MEDIA RELEASES (MAY 2012)

H.8 DEA-2852.242-76 KEY PERSONNEL (JAN 2014)

H.9 DEA-2852.245-70 GOVERNMENT-FURNISHED RESOURCES (MAY 2012)

H.10 INCORPORATION OF CONTRACTOR’S PROPOSAL

H.11 DEA-2852.239-70 SECURITY OF SYSTEMS AND DATA, INCLUDING PERSONALLY IDENTIFIABLE DATA

(AUGUST 2012)

H.12 DEA-2852.237-70 Preventing Personal Services Contracts and Performance of Inherently Government

Functions (JUN 2018)

SECTION I – CONTRACT CLAUSES

I.1 CLAUSES INCORPORATED BY REFERENCE

I.2 CLAUSES INCORPORATED BY FULL TEXT

SECTION J – LIST of EXHIBITS and OTHER ATTACHEMENTS

EXHIBIT J-E-1

EXHIBIT J-E-2

EXHIBIT J-E-3

SECTION K – REPRESENTATIONS, CERTIFICATIONS, and OTHER STATEMENTS of

OFFERORS

K.1 52.204-8 ANNUAL REPRESENTATIONS AND CERTIFICATIONS (OCT 2018)

K.2 FAR 52.204-19 INCORPORATION BY REFERENCE OF REPRESENTATIONS AND

CERTIFICATIONS (DEC 2014)

(End of Provision)

K.3 FAR 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (JUL 2013)

K.4 52.209-5 CERTIFICATION REGARDING RESPONSIBILITY MATTERS (OCT 2015)

K.5 FAR 52.209-11 Representation by Corporations Regarding Delinquent Tax Liability or a Felony

Conviction under any Federal Law

K.6 FAR 52.209-12 Certification Regarding Tax Matters

K.7 FAR 52.230-1 COST ACCOUNTING STANDARDS NOTICES AND CERTIFICATION (Oct 2015)

K.8 FAR 52.230-7 PROPOSAL DISCLOSURE—COST A CCOUNTING PRACTICE CHANGES (APR

2005)

SECTION L: INSTRUCTIONS, CONDITIONS AND NOTICE TO OFFERORS

L.1 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

L.2 52.204-6 UNIQUE ENTITY IDENTIFITY (OCT 2016)

L.3 52.233-2 SERVICE of PROTEST (SEPT 2006)

L.4 JAR 2852.233-70 PROTESTS FILED DIRECTLY WITH THE DEPARTMENT OF JUSTICE (JAN 1998)

L.5 COMMITMENT OF GOVERNMENT TO AWARD A CONTRACT AND EXPENDITURE OF FUNDS

L.6 ALTERNATE PROPOSAL INFORMATION

L.7 OFFEROR ACCEPTANCE PERIOD

L.8 COMMUNICATIONS AND CORRESPONDENCE

L.9 PROPOSAL PREPARATION INSTRUCTIONS

L.9.1 General Instructions

L.9.2 Proposal Due Date

L.9.3 Final Proposal Revisions

L.9.4 DISPOSITION OF PROPOSALS

L.10 PROPOSAL VOLUMES

L.9.3 Technical Proposal (Volume I)

L.9.4 Program Management Proposal (Volume II)

L.9.5 Cost/Price Proposal (Volume III)

SECTION M: EVALUATION FACTORS FOR AWARD

52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

M.2 EVALUATION GENERAL

M.2.1 Overall Evaluation Approach

M.2.2 Evaluation Factors Order of Importance

M.3 Evaluation Factors (Non-Cost)

M.3.1 Factor 1.0 – Past Performance

M.3.2 Factor 2.0 – Key Personnel Resumes

M.3.3 Factor 3.0 – Program Management Plan

M.4 Cost Proposal Evaluation Ratings Overview

M.4.1 Cost Proposal Evaluation Process

M.5 BASIS FOR AWARD

SECTION A - SOLICITATION/CONTRACT FORM

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 GENERAL

The Drug Enforcement Administration (DEA) Delta Code Software Development (DCSD)

Contract is an Indefinite Delivery, Indefinite Quantity (IDIQ) contract to provide the software engineering support required to: continue to develop and deliver quality software applications in the Concorde framework, and provide operations and maintenance support to existing Concorde and non-Concorde applications. Services/supplies will be provided on the basis of direct labor hours at specified fixed hourly rates that include wages, overhead, profit, and materials (at cost).

Various Program Areas within DEA will be able to order from this contract.

A Task Order under this IDIQ contract is defined as “an order for services placed against an established contract or with Government sources,” FAR 2.101. Task Orders are issued by the aforementioned DEA Program Areas against this contract.

The Contractor shall provide all management, supervision, and labor, necessary to perform on a

Task Order basis.

Hereafter, the DCSD Contract is also referred to as the “IDIQ Master Contract” while Task

Orders issued under the IDIQ Master Contract will be referred to as either “Task Order(s),”

“TO(s),” or “Order(s).”

B.2 MAXIMUM CONTRACT CEILING AND MINIMUM CONTRACT GUARANTEE

(a) Maximum. The maximum contract ceiling value of the contract in this single award procurement is established at $87 million dollars.

(b) Minimum. The minimum guaranteed award amount for this Contract is $10,000. The exercise of the option period does not re-establish the contract minimum.

Should the contract expire or be unilaterally terminated for convenience by the

Government without the contractor receiving the minimum guaranteed award amount, the contractor may present a claim to the contracting officer for an amount not to exceed the minimum guaranteed award amount. The minimum guaranteed award amount is not applicable if the contract is terminated for default or is bilaterally cancelled by the parties.

The contractor has one year after contract termination or expiration to submit their claim to the contracting officer or waives entitlement.

(c) The Government has no obligation to issue Task Orders (TO) to the Contractor beyond the amount specified in paragraph (b) of this clause.

(d) There is no maximum dollar ceiling for an individual Task Order

B.3 TRAVEL PRICING

Contractor personnel may be required to travel to support the requirements of this

Contract and will be stated in individual TOs. Travel may be required for all 50 States, and U.S

Territories. For those TOs requiring travel, the Contractor shall include estimated travel pricing requirements in their proposal as required by the CO.

If authorized in the Task Order, travel will be reimbursed at actual cost in accordance with the limitations set forth in DEA Travel Clause 2852.231-70 abd FAR Subpart 31.205-46, Travel

Costs. Profit shall not be applied to travel costs. To the extent authorized by the Task Order, Contractors may apply indirect costs to travel in accordance with the Contractor’s usual accounting practices consistent with FAR 31.2.

The CO will identify a not-to-exceed travel ceiling under a separate CLIN on the Task Order.

B.4 CONSIDERATION AND PAYMENT

The following represents the price schedules for this contract. One Full Time Employee equals

1,920 annual hours.

Table B.1 – Base Period: Effective Date of Contract Award through 12 Months Thereafter

CLIN # Labor Hour Category Quantity of

Hours

Unit Unit Price

0001 Project Manager 1,920 Hour $

0002 Site Manager 1,920 Hour $

0003 Software Consultant 19,200 Hour $

0004 Senior Software

Developer

30,720 Hour $

0005 Senior Oracle Web

Developer

1,440 Hour $

0006 Intermediate Software

Developer

17,280 Hour $

0007 Junior Software

Developer

9,600 Hour $

0008 MS Access Developer 1,440 Hour $

0009 Requirements

Analyst/Knowledge Support

9,600 Hour $

0010 Requirements Analyst 11,520 Hour $

0011 Tester 9,600 Hour $

0012 Scrum Master 1,920 Hour $

0013 Microsoft Application

Consultant

5,760 Hour $

Table B.2 – Option Period 1: 12 Months after Expiration of the Base Period

CLIN # Labor Hour Category Quantity of Hours Unit Unit Price

1001 Project Manager 1,920 Hour $

1002 Site Manager 1,920 Hour $

1003 Software Consultant 19,200 Hour $

1004 Senior Software

Developer

30,720 Hour $

1005 Senior Oracle Web

Developer

1,440 Hour $

1006 Intermediate Software

Developer

17,280 Hour $

1007 Junior Software

Developer

9,600 Hour $

1008 MS Access Developer 1,440 Hour $

1009 Requirements

Analyst/Knowledge

Support

9,600 Hour $

1010 Requirements Analyst 11,520 Hour $

1011 Tester 9,600 Hour $

1012 Scrum Master 1,920 Hour $

1013 Microsoft Application

Consultant

5,760 Hour $

Table B.3 – Option Period 2: 12 Months after Expiration of Option Period 1

2001 Project Manager 1,920 Hour $

2002 Site Manager 1,920 Hour $

2003 Software Consultant 19,200 Hour $

2004 Senior Software

Developer

30,720 Hour $

2005 Senior Oracle Web

Developer

1,440 Hour $

2006 Intermediate Software

Developer

17,280 Hour $

2007 Junior Software

Developer

9,600 Hour $

2008 MS Access Developer 1,440 Hour $

2009 Requirements

Analyst/Knowledge

Support

9,600 Hour $

2010 Requirements Analyst 11,520 Hour $

2011 Tester 9,600 Hour $

Scrum Master

Microsoft Application

Consultant

1,920

5,760

Hour

Hour

Table B.4 – Option Period 3: 12 Months after Expiration of Option Period 2

3001 Project Manager 1,920 Hour $

3002 Site Manager 1,920 Hour $

3003 Software Consultant 19,200 Hour $

3004 Senior Software

Developer

30,720 Hour $

3005 Senior Oracle Web

Developer

1,440 Hour $

3006 Intermediate Software

Developer

17,280 Hour $

3007 Junior Software

Developer

9,600 Hour $

3008 MS Access Developer 1,440 Hour $

3009 Requirements

Analyst/Knowledge

Support

9,600 Hour $

3010 Requirements Analyst 11,520 Hour $

3011 Tester 9,600 Hour $

Scrum Master

Microsoft Application

Consultant

1,920

5,760

Hour $

Table B.5 – Option Period 4: 12 Months after Expiration of Option Period 3

4001 Project Manager 1,920 Hour $

4002 Site Manager 1,920 Hour $

4003 Software Consultant 19,200 Hour $

4004 Senior Software

Developer

30,720 Hour $

4005 Senior Oracle Web

Developer

1,440 Hour $

4006 Intermediate Software

Developer

17,280 Hour $

4007 Junior Software

Developer

9,600 Hour $

4008 MS Access Developer 1,440 Hour $

4009 Requirements

Analyst/Knowledge

Support

9,600 Hour $

4010 Requirements Analyst 11,520 Hour $

4011 Tester 9,600 Hour $

Scrum Master

Microsoft Application

Consultant

1,920

5,760

Hour

Hour

Total Amount of Base plus Four Option Periods: ___$_________________________

This contract shall be effective on the date of the Contracting Officer’s signature, and shall remain in effect until one year thereafter, and upon acceptance/execution of each subsequent option year period if exercised.

[End of Section]

SECTION C – DESCRIPTION/SPECIFICATION/STATEMENT OF

WORK

C.1 INTRODUCTION

The mission of the Drug Enforcement Administration (DEA) is to enforce the controlled substances laws and regulations and to bring to the criminal and civil justice systems those organizations involved in the growing, manufacture, or distribution of controlled substances appearing in or destined for illicit traffic in the United States. DEA has a presence in more than 350 domestic offices in 22 divisions within the U.S. and 75 foreign offices. DEA’s operation and support activities are distributed across five core business lines that include the following:

Investigative

Forensic

Financial

Intelligence

Administration

The core business lines require significant Information Technology (IT) resources to carry out key processes. In support of the DEA mission, these IT services include developing, deploying, and maintaining DEA’s mission critical and business applications as well as their supporting infrastructure.

C.2 BACKGROUND

The Office of Information Systems (SI) is the major, central source of software development for

DEA’s mission critical applications. The Software Operations Section (SIS) within SI manages the development of applications and major enhancements using the agile software methodology. SIS provides supporting estimates and schedules and coordinates resources to successfully complete the project and manage the project scope. SIS ensures communication/use of standard practices of the agile software methodology, software configuration standards, and functional testing standards.

The Software Development Section (SIS) in SI established a de-facto “Concorde” standard in its section in 2010 when DEA’s core case management application was developed as the first of the

Concorde web applications with single sign on and zero footprint.

Concorde is a business-driven IT program providing unified access to, and the sharing of information in accordance with, the DEA mission and the Department of Justice’s (DOJ) strategic plan. The concept of the Concorde Program is to eliminate stove-piped systems by integrating business functions and allowing for information sharing across the five main DEA business lines.

Concorde’s technical architecture is multi-tiered and implements the Model-View-Controller (MVC) architectural pattern using elements of the Microsoft ASP.NET MVC framework. Some of the code that implements views is written in JavaScript and specifically the jQuery JavaScript library.

Concorde is delivered to and runs within the Internet Explorer 10 browser on the user’s workstation.

Concorde applications and other Sensitive but Unclassified (SBU) applications are hosted on DEA’s

SBU Firebird network.

As prescribed by the Agile methodology, work continues to be performed by development teams prioritized in monthly “Sprints”. As a result, there are currently over 65 applications developed on the Concorde platform. Although the majority of software applications in SIS are Concorde applications, there still remains a mixture of technologies that require operations and maintenance support, to include one non-Concorde .NET application, approximately five legacy applications utilizing Oracle Forms and Reports and 20 Microsoft Access applications. Regardless of platform, development teams follow the Agile Software Development Methodology to build and deliver high quality software.

Currently, Agile SCRUM teams develop new Concorde applications, while providing operations and maintenance support to existing Concorde and non-Concorde legacy applications. The interruption to address operational issues on production applications impacts the team’s ability to focus on the prioritized development application and reduces overall team velocity and delivery of applications.

As technology advances, DEA applications must maintain pace to leverage faster, more secure technological upgrades. The current version of Concorde was founded upon a code release of DEA’s case management system in November of 2010. This version was based upon .NET Framework 4.0.

Since that time, Microsoft has released a substantial update to the .NET technology stack called

.NET Core. This update is faster, more secure, and has a smaller footprint. It opens the door for enhanced future integration with both mobile and cloud technologies and provides for better interoperability options for Concorde to communicate with other Law Enforcement software systems. As DEA’s case management system was the foundational core of Concorde, it will be one of the first applications to be re-developed in .NET Core. To leverage the upgrades of .NET Core, over 65 existing Concorde applications will require the modernization effort. The re-development of

DEA’s case management system in .NET Core is in its infancy, and as it nears completion, all new

Concorde applications will be developed using .NET Core and the .NET standard libraries created in

Concorde.

DEA customers who have a request for a new application or an enhancement to an existing

Concorde application, make a request through the Chief Information Officer (CIO) front door via the completion of a Project Analysis Worksheet (PAW), defining the high-level business need. After a technical analysis is conducted to determine the technical feasibility, resource availability and any potential risks, the Deputy Chief Information Officer (DCIO) reviews and determines if the request should move forward to DEA’s Sprint Scoring Committee. The requestor presents his business case to the committee and through an existing pre-defined scorecard process, the DEA Sprint Scoring

Committee scores each request, resulting in a monthly Sprint Programming Prioritization List. As development teams near the completion of one application, members of the development team will work with SI’s Business Program Office and the customer to develop a System Information Package

(SIP), or an Initial PAW Review document (IPRD), which defines high level requirements and the

Minimum Viable Product (MVP) to be developed. On average, two to four new applications and/or enhancement requests are added to the list monthly.

C.3 OBJECTIVE

The objective of this effort is to continue to develop and deliver quality software applications in the

Concorde framework, provide operations and maintenance support to existing Concorde and non-

Concorde applications, increase efficiencies across teams, and expedite the delivery of applications.

Acceptable quality will be identified once applications are tested by developers, independently unit tested by a contractor tester and tested and approved by the Government Product Owner. Additional acceptance will be conducted after demonstrations to the customer, and further deployed to a beta environment.

The Contractor shall provide software development teams that will focus solely on new development in the Concorde framework and separate Transition/Operations & Maintenance (O&M) teams to enhance and conduct bug fixes in existing Concorde applications with an additional O&M team to support non-Concorde Oracle and MS Access applications. Teams shall be defined as Concorde new development teams, Concorde Transition O&M teams and non-Concorde legacy O&M teams.

At the discretion of the government, teams may require vendors from other contracts to serve as members of a development team or even operate as a Team Lead. A government lead will provide oversight to each team and maintain the role of Product Owner, serving as the customer liaison for the development team.

New applications and enhancements to existing applications are governed by the approved monthly

Sprint Programming Prioritization List.

For all new development work, teams will generally be smaller in size than O&M teams, with highly skilled developers, whereas Concorde Transition/O&M support teams will contain a mix of skill levels predicated upon work assignments. The non-Concorde O&M team will require only a small team, with appropriate skill sets.

During the performance of this contract, software development will also occur on the classified infrastructure. The DEA Software Architecture known as “Concorde” will be set-up on the classified infrastructure, and classified applications will be developed. As such, the Contractor shall be required to support Classified, Unclassified, Sensitive but Unclassified, and Outward facing applications as well as data in each of these environments.

C.4 SCOPE OF WORK

The DEA is seeking Contractor services to provide software development of new Concorde applications, transition of new applications to O&M and O&M support of existing Concorde applications and operations and maintenance of non-Concorde applications. Included in this scope are data migration activities as legacy applications are re-developed in the Concorde framework.

Also included in the scope of this contract will be mobile application development as required.

The Contractor shall utilize the Agile Scrum software methodology adopted by DEA SI for new development and O&M support of all applications. Agile Kanban may be utilized for O&M teams where the government deems applicable. The Contractor shall perform all application software development utilizing the provided tools and hardware/software version(s) currently in use by the

DEA. It should be noted that DEA SIS software development currently operates and supports work via monthly Sprints but is not opposed to changing Sprint durations to two-week Sprints, where feasible. Tasks listed in Section C.5 are based on monthly Sprints.

When legacy applications are retired, the DEA will notify the Contractor to take the appropriate steps to retire applications and either purge databases or provide final data backups to the Concorde

Enterprise Warehouse (EDW) for historical or reference purposes.

The scope of this contract encompasses the following specific areas in the classified, unclassified and sensitive, but unclassified environments:

C.4.1 New Applications and O&M Development Support

C.4.1.2 New Applications

Concorde New Development teams shall focus solely on the development of new applications and provide production support for 60-90 days after deployment, or as deemed appropriate by the government. Teams shall typically consist of three-four highly skilled developers, and a requirements analyst. Subject Matter Experts from Microsoft Consulting Services (MCS) provide critical technical support on the current contract in their role of consulting and coding support for both .NET Core, NET MVC and SQL Server. Teams may include or share a Scrum Master across teams, and in the case of very large applications, such as DEA’s IMPACT case management application, a tiger team may be created from one or more teams, at the discretion of the government. Independent testers will be shared across teams. Concorde New development teams will transition applications to Concorde

Transition/O&M teams for continued production support beyond the initial deployment period.

C.4.1.3 Transition/O&M Development Support

Concorde Transition/O&M teams shall focus on prioritized enhancements, bug fixes and overall operations maintenance and support of Concorde production applications. After an initial period of support with the Concorde New Development team, the application will transition to a

Transition/O&M team for continued support. Teams shall typically consist of at least one or more highly skilled developers, a mix of three-four intermediate and junior developers and a requirements analyst/knowledge support person. Concorde O&M resources will provide service desk support for assigned applications. Independent testers will be shared across O&M teams.

A non-Concorde O&M team shall provide support to the remaining five Oracle applications, one non-Concorde .NET/SQL application and 20 MS Access applications. Include in the scope of the will be modifications to the general layout and shared functionality of existing Concorde applications to obtain a general “look and feel” as the new Concorde applications being developed.

Support shall include bug fixes and overall operations maintenance and support. This team shall include senior level expertise in Oracle and SQL Server, at least one Microsoft Access developer, and a requirements analyst/knowledge support person. Independent testers from Concorde O&M team could be utilized for any necessary testing. This team shall provide assistance as needed to a

Concorde new development team re-developing any of these legacy applications. Ultimately, DEA will re-develop the current non-Concorde applications in the Concorde environment, which is contingent upon prioritization by the Sprint Scoring Committee.

A SIS government lead provides oversight to each team and either the government lead or another

SIS government employee maintains the role of Product Owner, who serves as the customer liaison for the team performing the work on the application. Monthly work is defined using high-level epics and medium level user stories via an approved prioritized monthly Sprint list. After executive management receives approval, the list is posted on the SIS SharePoint site, accessible by both

Contractor Project Manager and the Government Product Owners.

C.4.1.1 Areas of Application Support

Areas of application development may include, at a minimum:

Business work flow and forms development;

Code development for the applications using DEA tools;

Peer code review of applications;

Application development tools and testing procedures;

Application demonstrations and training (as needed);

Support for application deployment;

Security considerations; and

Application performance optimization.

The Contractor shall develop, modify and enhance software applications based upon the approved monthly Sprint Prioritization List.

The teams of contractor personnel required to provide this support will require skills and expertise in the following development areas and tools:

ASP.Net, C# MVC-based web development

Visual Studio 2012 and higher

.NET Core

Business work flow and forms development;

Database migration expertise

Security considerations

Application performance optimization e-GIS development for the browser such as displaying street maps or satellite images

JavaScript

Oracle Relational Database Management System(RDBMS)

Microsoft SQL Server

JSON

MS Office 2010 and higher

MS Team Foundation Server 2012 and higher

Xamarin or other identified mobile technology

Other technologies as identified by the government

C.4.2 Mobile Application Development (future)

Like many government agencies, DEA is recognizing the importance of data-driven information accessible via a mobile context. While the Concorde Framework is web-based and can be browsed on a DEA issued phone, the experience is not the same as a true mobile application. DEA currently has a mix of Android and iOS mobile devices but is leaning toward IOS implementation, possibly with the use of Xamarin. Contractor provided mobile application support for the Concorde

Framework may be requested in the future under this contract, therefore it is encompassed within the scope of these requirements

C.5 TASKS

The Contractor shall perform the tasks described in the following subsections:

C.5.1 Requirements Gathering

The Contractor shall regularly interface with SI’s Business Program Management Office (SIB) as

SIB documents the customer’s “as is” and “to be” business processes. The development team lead, requirements analyst and government Product Owner assist in meetings with the Champion and working group to gather high level requirements in the form of Epics. This provides the development team with enough information to begin a design and mockup of the application, while allowing SIB to identify the minimum viable product (MVP) in the resultant System Information

Package or Initial PAW Review document (IPRD). The Contractor shall continue to interface with the Champion (government customer), Working Groups, and Product Owners (SIS customer liaison), to further clarify detailed requirements for application development and prevent any delay in delivery of final products. Teams will work with members of additional teams to include the

Concorde Core, the Enterprise Data Warehouse support teams, and other teams, as applicable and as directed by the Government. The Concorde Core team supports development and enhancement of the Concorde framework, and reviews mock-ups and applications for compliance with Concorde standards. The Enterprise Data Warehouse teams support the Concorde data warehouse and provide views of data for use in applications. Epics, user stories and associated requirements shall be documented in Team Foundation Server. Discussions/actions shall be documented via Meeting

Minutes and forwarded to the appropriate Product Owner(s) for approval before dissemination to the

Champion and other customers in attendance.

C.5.2 Application Mock-up

The Contractor shall develop a mock-up of screens for Champion concurrence before any development or enhancement of the application begins. These can be produced through PowerPoint slides or simple screen coding. The Contractor shall submit/demonstrate mock-ups to a member of the Concorde Core team and the Product Owner for review prior to meeting with the Champion.

C.5.3 Participate in Daily Agile Stand-Up Meeting and Scrum of Scrums Meeting

The Contractor shall participate in daily Agile Stand-up meetings whereas each team member shall report work performed the previous day, work to be performed the current day, and any impediments to their performance of tasks. The Contractor shall document information presented by team members in a bulleted fashion and place on the appropriate unit’s SharePoint site. Additionally, all team leads shall participate in a daily Scrum of Scrums meeting to share and briefly address any technical issues/information that could potentially impact other teams. At the start of any new project, the team lead will provide a brief explanation of the project to all team leads. An email capturing shared information will be sent to all participants after the daily Scrum of Scrums.

C.5.4 Attend Monthly Planning Sessions

Each Contractor team shall attend, either in person or remotely, monthly Planning Sessions at the end of each month where all developers are in attendance. As remote capabilities increase, attendance may be through remote video capability, but all team members shall participate. Team velocity will be established at the start of each planning session based on historical velocity of the development team, and any anticipated resource reduction due to vacations, etc. for the upcoming

Sprint.

Prior to the monthly planning session, requirements for user stories shall be fully documented in TFS

(Team Foundation Server) for review and discussion by developers. Developers will “vote” via

“Points Poker” to provide estimates for completion of prioritized Sprint user stories.

The Contractor shall document the results of the planning session in TFS to include the team’s planned velocity and points assigned to each user story.

C.5.5 Attend Monthly mid-Sprint Reviews

The Contractor shall attend, either in person or remotely, a mid-Sprint review to assess the month’s progress to date, with each developer on the team identifying the probability of completion of work assigned, as defined on the approved Sprint list in the monthly planning session. As remote capabilities increase, attendance may be through remote video capability, but all team members shall participate. The Contractor shall identify any impediments and any need to potentially reallocate developers to the month’s highest priority tasks.

The Contractor shall document the results of this meeting and provide meeting minutes to the appropriate Government Product Owner for approval.

C.5.6 Attend Monthly Retrospective Sessions

The Contractor team shall attend, either in person or remotely, a monthly retrospective meeting at the end of each month where each team member articulates the effectiveness of the month’s Sprint, issues encountered, and lessons learned. The team leads shall review the tasks completed and report the team’s weekly velocity to include identification of points assigned and completed by each team member. As remote capabilities increase, attendance may be through remote video capability, but all team members shall participate

The Contractor shall document and provide minutes of the monthly Retrospective Session to include all items discussed in the session to the appropriate Government Product Owner for approval.

C.5.7 Champion Meetings

The Champion is the customer representative, generally a GS15 or above, who has the authority to make on-the-spot decisions regarding the requirements and functionality of the software application under development. The Contractor team shall attend regularly scheduled Champion meetings, at a minimum, biweekly to gather requirements, demonstrate software development progress to the

Product Champion, and document subsequent change requests and user stories. Attendance may be through remote video capability, for developers in remote locations.

All change requests and user stories shall be documented in TFS for consideration of prioritization in future Sprints.

The Contractor shall document and provide minutes of the Champion meetings to the appropriate

Government Product Owner for approval.

C.5.8 Use of Team Foundation Server (TFS)

The Contractor shall utilize TFS to document epics, user stories, requirements, change requests, bugs and tasks.

The Contractor shall utilize source control in TFS and each developer shall track hours expended per task on a daily basis. At the end of each day, every Contractor developer shall either place their source code in a shelve set within TFS or request a code review. If the code passes review, it can be checked in for potential inclusion in the next build. Currently more than 7,000 integration tests can be triggered by a code check-in within Concorde. A check in by the team lead for a single application will trigger the necessary subset of the integration tests germane to that application.

C.5.9 Testing

The Contractor shall perform testing of user stories at various levels, to include unit testing by developer, peer code reviews, final code review by Contractor Team Lead or designee, and testing by an independent tester. Once the tester has successfully tested a user story, the Government

Product Owner shall be notified that user stories can be tested and subsequently closed, if tested successfully. No code moves to production will be made without the involvement of at least two developers (usually a developer and a team lead/team lead designee). If the Contractor Team Lead delegates the final code reviews to another member of the team, he remains ultimately accountable for the application code.

C.5.10 Delivery of Incremental Software Beta Release

The Contractor shall bundle functional user stories at the end of each month’s Sprint, if feasible, for deployment to a beta environment for further testing by selected users. Prior to a fully functional beta release, the Contractor shall request a review by a member of the Concorde Core Team.

Notification of beta releases shall be communicated through the established ticket request process, which requests, notifies and obtains appropriate approvals prior to their scheduled release.

C.5.11 Delivery of Incremental Software Production Release

With approval by the Product Owner, the Contractor shall promote beta versions into production and provide post-deployment support. Production releases are generally scheduled shortly after the end of each monthly sprint but may occur in the middle of a sprint if requested by the Government

Product Owner. Two Sprints prior to a production release, the Contractor shall request a review by a member of the Concorde Core Team. Notification of production releases shall be communicated through the established ticket request process, which requests, notifies and obtains appropriate approvals prior to their scheduled release.

C.5.12 Provision of Training/Demonstrations

The Contractor shall provide training support via “train the trainer” sessions, MS Lync sessions, video tutorials, user documentation such as Quick Reference Guides (QRG) or other means as determined by the Government, (i.e. one-on-one instructions, “how to” sessions over the phone, or on-site with the client at various DEA offices).

C.5.13 Data migration

Where applicable, the Contractor shall develop SSIS packages or T-SQL scripts to retrieve and process data from legacy Oracle, MS Access, flat files or other applications. Other scripts may move data between Concorde and legacy applications and the Electronic Data Warehouse (EDW) via ETL (Extract – Transform - Load) processes.

Upon approval by the Product Owner or Task Manager (TM), The Contractor shall identify, document and execute data migration planning activities. This shall include at a minimum, a migration plan with detailed steps to be followed prior to and after data migration. Upon completion, the migration plan shall be updated to indicate that each step was followed and successfully executed.

The Contractor shall conduct validation activities to ensure the accuracy of migrated data.

Preliminary tests shall be performed to compare legacy data with the resultant migrated data, included but not limited to: a matching count of records between migrated and legacy records, and a representative sampling of migrated data, compared to legacy data to ensure all columns and rows

(fields/records) were successfully migrated.

C.5.14 Script Development

The Contractor shall develop monthly or as-needed scripts or SSIS packages to load, process, and retrieve data from a variety of relational databases. These include, but are not limited to SQL

Server, Oracle, DB2, MS Access, and others. Additional scripts may move data between Concorde and legacy applications and the EDW.

C.5.15 Documentation Support

Upon request of the Product Owner or TM, The Contractor shall provide documentation of procedures, application reference materials, workflows, business processes, and data structures.

The Contractor shall develop Quick Reference Guides (QRG) for each new application released, to provide “at-a-glance” instructions of primary application functionality.

C.5.16 Configuration Management

The Contractor shall update the monthly Sprint prioritization plan with the TFS ID and date of deployment associated with each user story, as applicable, on the completed “Done” sheet, to ensure accurate identification of each user story deployed to production.

C.5.17 Program Management

The Contractor shall provide, at a minimum, monthly status briefings to the SIS Section and Unit

Chiefs, COR and CO. The briefing shall provide statistical charts and slides to demonstrate progress and trends of development teams, staffing status and issues and current contract burn rate and contract balance. A monthly status report shall be provided to the Contracting Officer’s

Representative (COR) and the Contracting Officer (CO) and shall document the reporting period, accomplishments/progress, and any issues/problems encountered and recommended solutions to resolve issues. The Contractor shall maintain staffing levels per Government requirements, with the contract fully staffed (having provided security packages to DEA) for at least the identified key personnel within 30 days of the contract award date. The Contractor should thoroughly understand the DEA clearance process and be prepared for candidates to have several months wait times for a full clearance to be awarded. Contractors cannot begin billing to this contract without a full clearance.

The Contractor shall provide program management support to Unit Chiefs, Section Chief and SIS

Product Owners in providing historical, trending and financial reports. The Contractor shall provide support to the Government Product Owners in the development of monthly Sprint prioritization lists.

The Contractor shall provide program and project planning support to the re-development of legacy applications.

C.5.18 Contract Transition

The Contractor shall perform transition of all services defined in this contract without impacting operational availability. The transition plan of the successful Offeror shall be incorporated into the contract.

C.5.18.1 Transition Phase-In

The Contractor’s transition in activities shall follow the pre-approved transition plan previously submitted and Government approved under the program management section of their proposal.

Transition is an integral part of contract start up. The plan shall include a timeline for completion of all phase-in activities using 15 calendar day completion intervals, with total completion within 60 calendar days in response to the issued task order. Onboarding of key personnel to the new contract shall be completed within the first 45 calendar days, with remaining personnel onboarded once their

DEA Suitability status is favorably adjudicated. The plan for transition shall include, but is not limited to:

Management of Phase-In Activities;

Initial Staffing Levels and Timeline to achieve Full Staffing Levels;

Prevention of Disrupting Work and Operations in Progress; and

Transfer of Government Furnished Property, Material, Equipment and Data

C.5.18.2 Transition Phase-Out

The Contractor shall develop and document a plan for a transition phase-out period in the program management section of their proposal, in the event that the Contractor is not selected for a follow-on contract or if the Government elects not to exercise any options to extend the performance period.

Not later than 90 calendar days prior to the end of the period of performance of the contract, the

Contractor shall update their transition phase-out plan, identifying and documenting all applications currently in development, beta and in the production environments. Upon Government approval of the updated transition phase-out plan, the contractor shall provide the inbound awardee and/or

Government, all documentation applicable to every application (e.g. QRG, documented meeting minutes, etc.). The Contractor shall verify that user stories and requirements for each application are documented in TFS. During the last 30 calendar days of the contract, the Contractor shall provide demonstrations and documentation of each application to the new awardee and/or the DEA COR as deemed appropriate by the Government. Before contract end, the Contractor shall return any

Government furnished equipment to either the COR or COR designee. The Contractor shall certify in writing, that all Government furnished equipment is undamaged and in working condition, prior to its return to the Government. Costs associated with damaged or loss of Government Furnished

Equipment will be decremented from Contractor’s final invoice.

C.5.19 Government Furnished Equipment (GFE and Government Furnished Information (GFI)

NOTE: GFE and GFI, if any, will be specified within each task order issued under this contract.

GFE – As applicable to each task order, Contractors shall utilize government furnished equipment at

DEA Office locations and personally owned equipment with PIV card readers or Government-provided soft or hard tokens for access from remote locations through Firebird Anywhere.

GFI – As applicable to each task order, Concorde Technical documentation will be provided by the

Government that identifies core reusable components used within the Concorde framework. “Wikis” are under construction in the development environment for use for developers to search technical information. Additionally, most applications have Quick Reference Guides that can be referenced describing application functionality. Development teams will use Team Foundation Server where previous epics and user stories of existing applications are documented and where all new epics and user stories will be documented.

C.6 DELIVERABLES - Format/Content

All daily work products are subject to review and approval by the TM. The TM will return comments and/or approvals within ten (10) business days of submission by the Contractor. Issues identified by the TM will be satisfactorily addressed by the contractor and re-submitted to the TM for review/approval not later than five (5) business days after contractor receipt of TM comments/concerns.

The Contractor shall submit the deliverables delineated in Section 6.1, Table 1 AND Section F.5.

Project deliverables shall be provided in the format specified by DEA (i.e. Microsoft Word, Excel, or PowerPoint; source code in TFS).

C.6.1. Deliverables Table

Table 1 – Articles of Delivery (begins next page)

RFP

Reference

Deliverable Deliverable Format Due Date

C.5.1 Requirements Gathering – user stories/requirements in TFS

Electronic 2 business days after meeting

C.5.2 Application Screen Mockups Electronic - either .ppt, html or other visual representation

1 day prior to scheduled

Champion meeting

C.5.3 Document Daily Stand-up

Meetings/bullet items only

Electronic – MS Word Before COB of the day of meeting

C.5.4 Document results of Monthly

Planning Sessions in TFS

Electronic 1 business day after meeting

C.5.5 Document mid-Sprint Reviews Electronic – MS Word attachment in TFS

1 business day after meeting

C.5.6 Document results of Monthly

Retrospective Sessions

Electronic – MS Word attachment in TFS

1 business day after meeting

C.5.7 Champion Meeting Minutes Electronic – MS Word 2 business days after meeting

C.5.8 Epics, User Stories, Requirements, Change Requests, Bugs and Tasks

Electronic - entered into

TFS

Before COB of day identified by government

C.5.9 Update testing status in TFS Electronic Before COB of day tested

C.5.10 Software Build -Beta Electronic deployment package of source code placed in appropriate share folder

After successful testing and approval by the Product

Owner and concurrence by the TM

C.5.11 Software Build -Production Electronic deployment package of source code placed in appropriate share folder

After successful testing and approval by the Product

Owner and concurrence by the TM

C.5.12 Training Materials Electronic or paper copies as needed – MS

Word

As needed and requested by the TM

C.5.13a

C.5.13b

a) Data Migration Plan

b) Migration Database backup or scripts

a) MS Word&

b) Electronic

a) One week prior to scheduled migration and updated within 24 hours after migration completed

b) As needed and requested by the TM

C.5.14 Database Scripts Electronic –placed in share folder for deployment

As needed and requested by the TM

C.5.15 Requested documentation as needed Electronic or paper copies as needed (MS

Word or Excel as applicable and directed by the Government

As needed and requested by the TM

C.5.16 Update completed Sprint plan Electronic – MS Excel 15th of the month

C.5.17 a) Monthly status presentation and supporting documentation

b) Monthly status report

a) Electronic - .ppt

b) Electronic – MS

Word

a) By 7th day of each month for preceding month’s data

b) By 10th working day of month following work completed to COR and CO

C.5.18 a) Transition Plan

b) Application documentation

c) Demonstrations

a) Electronic – MS

Word

b) Electronic – MS

Word

c) in person demonstration

a) NLT 90 days prior to end of Period of Performance

b) Within last 30 days of contract

c) Within last 30 days of contract

C.7 SECTION 508 COMPLIANCE

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L.

105-220) requires that when Federal agencies develop, procure, maintain, or use Electronic and

Information Technology (EIT), they must ensure that it is accessible to people with disabilities.

Federal employees and members of the public who have disabilities must have equal access to and use of information and data that is comparable to that enjoyed by non-disabled Federal employees and members of the public.

All EIT deliverables associated with the procurement of a tracking system will comply with the applicable technical and functional performance criteria of Section 508, unless exempt.

Specifically, the following applicable EIT accessibility standards have been identified:

36 CFR 1194.21 Software Applications and Operating Systems, applies to all EIT software applications and operating systems procured or developed under this work statement, including but not limited to, GOTS and COTS software. In addition, this standard is to be applied to web-based applications when needed to fulfill the functional performance criteria.

This standard also applies to some Web based applications as described within 36 CFR

1194.22.

36 CFR 1194.22 Web-based Intranet and Internet Information and Applications, applies to all web-based deliverables, including documentation and reports procured or developed under this work statement. When any web application uses a dynamic (non-static) interface, embeds custom user control(s), embeds video or multimedia, uses proprietary or technical approaches such as, but not limited to, Flash or Asynchronous Javascript and XML (AJAX) then 1194.21 software standards also apply to fulfill functional performance criteria.

36 CFR 1194.24 Video and Multimedia Products, applies to all video and multimedia…