AGILE_RFP.pdf

FLASH Request for Proposals RFP No. HSHQDC-16-R-00118

Department of Homeland Security i August 2016

U.S. Department of Homeland Security

Flexible Agile Support for the Homeland

FLASH

Request for Proposals

RFP Number: HSHQDC-16-R-00118

Department of Homeland Security Office of Procurement Operations Enterprise Acquisitions Division

Washington D.C.

FLASH Request for Proposals RFP No. HSHQDC-16-R-00118

Department of Homeland Security ii August 2016

(This page is intentionally left blank.)

FLASH Request for Proposals Part I – The Schedule RFP No. HSHQDC-16-R-00118 Section A – Standard Form 33

Department of Homeland Security 1 August 2016

SECTION A – STANDARD FORM 33

SOLICITATION, OFFER AND AWARD 1. THIS CONTRACT IS A RATED ORDER UNDER

DPAS (15 CFR 700)

RATING

PAGE OF PAGES

1 |

2. CONTRACT NUMBER

3. SOLICITATION NUMBER

HSHQDC-16-R-00118

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

5. DATE

ISSUED

08/02/2016

6. REQUISITION/PURCHASE NO.

7. ISSUED BY CODE 8. ADDRESS OFFER TO (If other than Item 7)

CODE

DEPARTMENT OF HOMELAND SECURITY

OFFICE OF PROCUREMENT OPERATIONS

Enterprise Acquisitions Division

245 MURRAY DRIVE, SW, BLDG 410

WASHINGTON, DC 20526

NOTE: In sealed bid solicitations “offer” and “offeror” mean “bid” and “bidder”

SOLICITATION

9. Proposals requested in Section L.8 for services in the Schedule will be received electronically at Agile@hq.dhs.gov by the RFP closing date of August 16, 2016 at 11:59 PM

EST.__________________

CAUTION LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR

INFORMATION CALL:

A. NAME B. TELEPHONE (NO COLLECT CALLS) C. E-MAIL ADDRESS

Erik Stephenson

AREA CODE

NUMBER

202-447- 5484

EX

T

Agile@HQ.DHS.GOV

11. TABLE OF CONTENTS

() SEC

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

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

X A SOLICITATION/CONTRACT FORM X I CONTRACT CLAUSES

X B SUPPLIES OR SERVICES AND PRICE/COST PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

X C DESCRIPTION/SPECS./WORK STATEMENT X J LIST OF ATTACHMENTS

X D PACKAGING AND MARKING PART IV - REPRESENTATIONS AND INSTRUCTIONS

X E INSPECTION AND ACCEPTANCE

X K

REPRESENTATIONS, CERTIFICATIONS

X F DELIVERIES OR PERFORMANCE AND OTHER STATEMENTS OF OFFERORS

X G CONTRACT ADMINISTRATION DATA X L INSTRS., CONDS., AND NOTICES TO OFFERORS

X H SPECIAL CONTRACT REQUIREMENTS X M EVALUATION FACTORS FOR AWARD

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within 120 _ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

10 CALENDAR DAYS

20 CALENDAR DAYS

30 CALENDAR DAYS

CALENDAR DAYS

14. ACKNOWLEDGMENT OF AMENDMENTS AMENDMENT NO. DATE AMENDMENT NO. DATE

(The offeror acknowledges receipt of amendments t th

SOLICITATION for offerors and related d t numbered and dated):

15A. NAME

AND

ADDRESS OF

OFFEROR

CODE FACILITY 16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN

OFFER (Type or print)

15B. TELEPHONE NUMBER 15C. CHECK IF REMITTANCE

ADDRESS IS DIFFERENT FROM ABOVE -

ENTER SUCH ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AREA CODE

NUMBER

EXT.

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED

20. AMOUNT

21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c) ( ) 41 U.S.C. 253(c) ( )

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

ITEM

24. ADMINISTERED BY (If other than Item 7) ODE 25. PAYMENT WILL BE MADE BY ODE

26. NAME OF CONTRACTING OFFICER (Type or print)

27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

IMPORTANT -- Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION STANDARD FORM 33 (Rev. 9-97) Previous edition is unusable Prescribed by GSA – FAR (48 CFR) 53.214(c)

X mailto:Agile@hq.dhs.gov mailto:Agile@HQ.DHS.GOV

RFP No. HSHQDC-16-R-00118 Section B - Supplies or Services and Prices/Costs

Department of Homeland Security 2 August 2016

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 General The Flexible Agile Support for the Homeland (FLASH) is a Small Business Set-aside Multiple Award, Indefinite-Delivery, Indefinite-Quantity (IDIQ) contract to provide the Department of Homeland Security (DHS) Headquarters (HQ) offices and components with Agile design and development services delivering viable, digital solutions in support of DHS’s strategic mission and objectives as described in Section C, Statement of Work. This contract will serve as a DHS-wide strategic sourcing vehicle.

B.2 Base and Option Periods The term of the FLASH IDIQ contract is a base ordering period of one (1) year and two (2) one

(1) year optional ordering periods. This is not a multi-year contract as defined in FAR Part 17.1, Multiyear Contracting. Task Orders (TOs) may be issued at any time during the base and/or optional ordering periods. The performance period of a TO, including the option period(s), may be up to three (3) years. The performance period of a TO may not extend beyond 24 months after expiration of the IDIQ contract.

B.3 Indefinite-Delivery/Indefinite-Quantity (IDIQ)

(a) This RFP will result in the establishment of a multiple award IDIQ contract to provide Agile design and development services and viable, digital solutions in support of DHS’s strategic mission. The IDIQ contract ceiling of all awarded contracts combined is $1.54 billion dollars.

This ceiling is for the multiple award IDIQ contract three (3) year period of performance including all option periods. The estimated TO business volume under the IDIQ contract base year is $256M. The anticipated volume for option period 1 is $326M. The option period 2 anicipated volume is 964M. (Note that the actual business volume will vary. This is NOT a guaranteed minimum.)

For this RFP, the Government anticipates multiple award IDIQ contracts. Immediately afterwards, the Immigration and Customs Enforcement (ICE) anticipates awarding one (1) initial Task Order against the IDIQ contracts from the Task Order proposals received in response to this RFP. Note: In the event of a protest, the initial Task Order may be removed from this solicitation and procured separately. The FLASH IDIQ contract is structured and managed in accordance with the rules for TO contracts. In particular, TO awards issued against this IDIQ contract will be placed using the “fair opportunity” procedures pursuant to FAR 16.505 (b) (1) and as described in Section G, Contract Administration Data.

(b) Indefinite-Delivery, Indefinite-Quantity (IDIQ) contracts, Blanket Purchase Agreements (BPAs), and Letter Contracts are not permissible under the FLASH contract.

(c) Task Orders issued under the IDIQ contracts may include options as defined in FAR Part 17, Special Contracting Methods.

Department of Homeland Security 3 August 2016

B.4 Type of IDIQ Task Orders Firm-Fixed-Price (FFP), Fixed Price Agile Teams, Time and Materials (T&M), and Labor- Hour (L-H) Task Orders may be placed under the FLASH IDIQ contract. Travel will be reimbursed based on actual costs and in accordance with the Federal Travel Regulations. If a TO CO requests ceiling (rates) prices at the task order level for teams composed of a specified number of full-time equivalent (FTE) personnel, an FTE equates to the hours worked by one employee on a full-time basis and therefore 40 hours of work by one or more employees equals one FTE. For example, a fixed price team of eight (8) FTEs could have twelve (12) team members engaged throughout the project in various roles to meet the requirement. Note:

For Fixed Price Teams, a time increment of one (1) week is equal to five (5) business days (40 hours).

B.5 Task Order Pricing

All TOs will be priced in accordance with the pricing set forth in Section J – List of Attachments, Attachment 1, Ceiling (Rates) Prices.

CLIN 0001 – Agile Roles

Ceiling (Rates) Price Product Manager $

Technical Architect $ Interaction Designer/User Researcher/Usability Tester

Writer / Content Designer / Content Strategist

Visual Designer $

Frontend Web Developer $

Backend Web Developer $

DevOps Engineer $

Security Engineer $

Delivery Manager $

Agile Coach $

Business Analyst $

Digital Performance Analyst $

CLIN 0002 – Travel Travel to be reimbursed at cost

B.6 Work Outside the Contiguous United States (OCONUS) It is anticipated that there may be minimal work under this contract outside the Contiguous United States. It is anticipated that any OCONUS work will have a materially significant impact on the contract. Prices for OCONUS work will be negotiated on a TO by TO basis and may exceed the established ceiling prices. The Government reserves the right to make determinations of fair and reasonable pricing at the TO level.

Department of Homeland Security 4 August 2016

B.7 Price Refreshment

(a) The agile role prices are ceiling prices for all contract year periods. At any time and throughout the life of the contract, at the request of either the Contractor or the Government, the Contractor may propose additional agile roles, rates and descriptions in addition to the Government agile roles. These additional Task Order Unique agile roles, rates, and descriptions will be negotiated on a case-by-case basis.

(End of Section B)

RFP No. HSHQDC-16-R-00118 Section C – Descriptions / Specifications / Work Statement

Department of Homeland Security 5 August 2016

SECTION C – STATEMENT OF WORK

1.0 GENERAL

1.1 BACKGROUND

The Department of Homeland Security has a vital mission: With honor and integrity, we will safeguard the American people, our homeland, and our values. This requires the dedication of more than 240,000 employees in jobs that range from aviation and border security to emergency response, from cybersecurity analyst to chemical facility inspector. DHS duties are wide-ranging, and its goal is clear - keep America safe.

On May 23, 2012 President Barack Obama issued Presidential Memorandum, Building a 21st Century Digital Government. The Federal Chief Information Officer (CIO) released the strategy “Digital Government Building a 21st Century Platform to Better Serve the American People", which provided agencies with a 12-month roadmap focused on priority areas to enable a more efficient and coordinated digital service delivery. The Department of Homeland Security used this initiative to:

• Enable the citizens of America to better leverage government data to spur innovation across our Nation and improve the quality of services for the American people.

• Ensure we seize the opportunity to procure and manage smart devices, applications, and data safely, securely, and efficiently.

• Unlock the power of data and be ready to deliver and receive digital information and services anytime, anywhere and on any device.

The technology landscape is rapidly changing. The proliferation and availability of Cloud Computing, Agile Development, and Mobility has provided new and innovative ways to deliver valuable Information Technology (IT) services within the Federal Government.

The Government defines Agile software development as a group of software development methods based on iterative and incremental development and deployment, where requirements and solutions evolve through collaboration between cross-functional teams that include the government and contractor communities. Agile methods encourage adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and rapid and flexible response to change. Using this contract vehicle for user-centered design and Agile development support, DHS components will be quicker in the design, development, and deployment of secure critical services that impact citizens and internal government users.

1.2 SCOPE

The DHS Flexible Agile Support for the Homeland (FLASH) acquisition will be a DHS-wide strategic sourcing vehicle providing DHS HQ offices and components with Agile design and development teams.

1.3 OBJECTIVE

FLASH Agile design and development teams shall deliver viable, digital solutions in support of DHS’s strategic mission and objectives.

Department of Homeland Security 6 August 2016

2.0 SPECIFIC REQUIREMENTS/TASKS

The contractor shall provide DHS components with Agile design and development teams. The teams shall deliver viable, digital solutions in support of DHS’s strategic mission and objectives.

An Agile team typically includes contractor staff in roles that may include, but not be limited to:

product manager, designer, engineer, and developer. As required, the contractor shall have the capability to provide teams and individuals at all security clearance levels. The specific security clearance level requirements for contractor team members will be defined by DHS HQ offices and components at the task order level.

The contractor teams shall create modern digital services that use a modern technical stacks. The contractor shall provide modern digital services that use development and operations (DevOps) techniques that embraces continuous integration and continuous deployment. The contractor shall deliver secure and tested modern mobile and web application designs using automated testing frameworks. The contractor shall provide support to projects that are building brand new systems as well as projects that are building on top of existing systems. The contractor shall support new technologies and programming languages as they emerge.

The contractor’s support and solutions shall align with the U.S. Digital Services Playbook (https://playbook.cio.gov). The contractor shall be familiar with the concepts in each play and implement them in its approaches and support. The contractor shall participate in specific agile methodologies (e.g. Backlog grooming, Sprint planning, Daily stand-ups, Sprint Review, Sprint Retrospective, Scrum of Scrums) and utilize the requirements artifacts and the application architecture provided by the government. The contractor shall also design, develop, configure, customize and deploy the corresponding solution. Once deployed, the contractor shall provide production support of the solution as required.

The following list provides examples of support that is within scope of the FLASH IDIQ contracts (specific in-scope tasks/requirements will be identified at the task order level):

• Cross-Functional Collaboration – The contractor shall participate in integrated program/project teams and agile teams to enhance communication, share lessons learned and facilitate rapid identification of dependencies between various functional entities to ensure that the projects deliver the right solutions and value to the business and end-users. This collaboration may include coaching government staff as the government attempts to stand up or execute an agile project.

• User Story Collaboration – The contractor shall work with the product owner, end users and requirements analysts to refine and groom user stories.

• User Centered Design – The contractor shall work with the product owner and agile resources to design application solutions to include user research, experience design, and service design.

• Code Development – The contractor shall use a modern technology stack to define, author, and deliver application code that conforms to requirements and application architecture provided by the government. This includes but is not limited to customizing Commercial off the Shelf (COTS) products for government use; developing, executing, and reporting on unit testing; and performing and documenting software code peer reviews. The contractor shall discover and reuse existing code, along with making newly developed code reusable on other government projects.

• Automated Testing – The contractor shall create and maintain an automated test suite for the purposes of performing automated testing on user stories and for ongoing regression testing to https://playbook.cio.gov/

Department of Homeland Security 7 August 2016 ensure functionality and quality of the overall system. This includes, but is not limited to testing methodologies such as Behavior Driven Development (BDD), Test Driven Development (TDD), and Acceptance Test Driven Development (ATDD).

• Usability testing – The contractor shall evaluate products by testing them with users. This includes but is not limited to performing Section 508 testing with DHS-certified Section 508 testing resources.

• Integration Support - The contractor shall integrate open source, Commercial Off the Shelf (COTS), Government Off the Shelf (GOTS) and/or Software as a Service (SaaS) solutions into existing, custom built, or new systems and provide configuration, customization and implementation services. The contractor shall also integrate with other government systems using standards based communication protocols and data formats.

• Data Migration – The contractor shall develop and execute data migration strategies/plans

• Deployment Activities – The contractor shall plan, create and validate the implementation and deployment of scripts for use during application deployment, and provide release planning and management support.

• DevOps – The contractor shall work collaboratively and cross functionally with engineering and operations to implement continuous integration, continuous delivery, production monitoring, and production support. The contractor shall support its own code while in production.

• Configuration Management/Change Control - The contractor shall support effective and efficient configuration management and change control to support the agile development processes.

• User Training – The contractor shall provide user-centered, task-based training to users in support of system deployment.

• Metrics Reporting – The contractor shall develop and communicate project metrics. Metrics may include but are not limited to dashboards, Agile burn down charts, release roadmaps, and schedule.

As task orders begin and end, the contractor shall actively participate in transition activities in support of a smooth transition of support responsibilities to/from the government and other contractors.

3.0 CONTRACTOR PERSONNEL

3.1 Qualified Personnel

All contractor personnel shall possess professional proficiency, experience, knowledge, and skills to perform the required tasks. The contractor shall ensure that its staff and subcontractors maintain any required professional certifications, accreditations, and proficiency relative to their areas of expertise.

3.2 Key Personnel

Key personnel and staffing requirements will be defined at the task order level. The name and resume of key personnel shall be designated in writing to the Contracting Officer (CO) for approval. Prior to removing, replacing, or diverting any key personnel, the contractor shall notify the CO no less than fifteen (15) business days in advance and shall submit a proposed replacement for government review within fifteen (15) days of notification. The government retains the right, at its discretion, to reject any proposed replacements of key personnel.

3.3 Employee Identification

Department of Homeland Security 8 August 2016

Contractor employees visiting Government facilities shall wear an identification badge that, at a minimum, displays the Contractor name, the employee’s photo, name, clearance-level and badge expiration date. Visiting Contractor employees shall comply with all Government escort rules and requirements. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.

Contractor employees working on-site at Government facilities shall wear a Government issued identification badge. All Contractor employees shall identify themselves as Contractors when their status is not readily apparent (in meetings, when answering Government telephones, in e-mail messages, etc.) and display the Government issued badge in plain view above the waist at all times.

3.4 Employee Conduct

Contractor’s employees shall comply with all applicable Government regulations, policies and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of DHS uniforms, and possession of weapons) when visiting or working at Government facilities. The Contractor shall ensure Contractor employees present a professional appearance at all times and that their conduct shall not reflect discredit on the United States or the Department of Homeland Security. The Project Manager shall ensure Contractor employees understand and abide by Department of Homeland Security established rules, regulations and policies concerning safety and security.

3.5 Removing Employees for Misconduct or Security Reasons

The Government may, at its sole discretion (via the Contracting Officer), direct the Contractor to remove any Contractor employee from DHS facilities for misconduct or security reasons.

Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The Contracting Officer will provide the Contractor with a written explanation to support any request to remove an employee.

4.0 OTHER APPLICABLE CONDITIONS

4.1 Place of Performance

It is expected that contractor’s teams will be required to frequently interact with system users and program staff in support of this contract. Support will be required at government facilities (on-site) and at non-government facilities (offsite). Specific site locations will be defined at the task order level. The government anticipates that most of the work will occur in the contiguous United States (CONUS), but OCONUS support by the contractor may be performed. For support provided at government facilities, the government may provide space and equipment (e.g., phone, desktop computer and peripherals, desk and accessories, etc.) for Contractor personnel performing work on-site at DHS facilities. The contractor personnel may be required to work offsite (ie. at the prime or subcontractor facilities) when adequate workspace is not available at the Government site.

Work requiring access to classified materials shall be performed at a Government facility or an appropriate facility clearance commensurate with the level of access required. Requirements that

Department of Homeland Security 9 August 2016 require contractor personnel security clearances will be defined at the task order level. It is projected that approximately 5% of the work to be performed may require a top secret clearance.

4.2 Accessibility Requirements (Section 508)

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 within this work statement shall comply with the applicable technical and functional performance criteria of Section 508 unless exempt. Specifically, the following applicable EIT accessibility standards have been identified:

Section 508 Applicable EIT Accessibility Standards 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.31 Functional Performance Criteria, applies to all EIT deliverables regardless of delivery method. All EIT deliverable shall use technical standards, regardless of technology, to fulfill the functional performance criteria.

36 CFR 1194.41 Information Documentation and Support, applies to all documents, reports, as well as help and support services. To ensure that documents and reports fulfill the required

1194.31 Functional Performance Criteria, they shall comply with the technical standard associated with Web-based Intranet and Internet Information and Applications at a minimum. In addition, any help or support provided in this work statement that offer telephone support, such as, but not limited to, a help desk shall have the ability to transmit and receive messages using

TTY.

Section 508 Applicable Exceptions

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the COR and determination will be made in accordance with DHS MD 4010.2. DHS has identified the

Department of Homeland Security 10 August 2016 following exceptions that may apply: 36 CFR 1194.3(b) Incidental to Contract, all EIT that is exclusively owned and used by the contractor to fulfill this work statement does not require compliance with Section 508. This exception does not apply to any EIT deliverable, service or item that will be used by any Federal employee(s) or member(s) of the public. This exception only applies to those contractors assigned to fulfill the obligations of this work statement and for the purposes of this requirement, are not considered members of the public.

Section 508 Compliance Requirements

36 CFR 1194.2(b) (COTS/GOTS products), When procuring a product, each agency shall procure products which comply with the provisions in this part when such products are available in the commercial marketplace or when such products are developed in response to a Government solicitation. Agencies cannot claim a product as a whole is not commercially available because no product in the marketplace meets all the standards. If products are commercially available that meet some but not all of the standards, the agency must procure the product that best meets the standards. When applying this standard, all procurements of EIT shall have documentation of market research that identify a list of products or services that first meet the agency business needs, and from that list of products or services, an analysis that the selected product met more of the accessibility requirements than the non-selected products as required by FAR 39.2. Any selection of a product or service that meets less accessibility standards due to a significant difficulty or expense shall only be permitted under an undue burden claim and requires authorization from the DHS Office of Accessible Systems and Technology (OAST) in accordance with DHS MD 4010.2.

5.0 GOVERNMENT FURNISHED EQUIPMENT (GFE) AND GOVERNMENT

FURNISHED INFORMATION (GFI)

Government furnished equipment (GFE) and Government Furnished Information (GFI) will be identified in task orders and provided to the contractor as task orders are awarded. The contractor shall maintain an inventory of GFE, which shall be made available to the government upon request, and at the beginning and end of the task order. Requirements for maintenance and/or return of GFE will be specified at the TO level.

Any requirements for maintaining an inventory and returning of GFI will be specified at the TO level.

(End of Section C)

RFP No. HSHQDC-16-R-00118 Section D – Packaging and Marking

Department of Homeland Security 11 August 2016

SECTION D - PACKAGING AND MARKING

D.1 Packing, Packaging, Marking and Storage of Equipment Unless otherwise specified, all items to be delivered under this contract shall be preserved, packaged, and packed in accordance with normal commercial practices to meet the packing requirements of the carrier and ensure safe delivery at destination.

At the task order level, the Contractor and the Contracting Officer’s Representative (COR) will finalize the method in which report deliverables are to be submitted and marked for delivery.

Additionally, Report Deliverables may be required to be submitted electronically and in hard copy.

D.2 Markings All deliverables submitted to the IDIQ contract CO, the IDIQ contract Program Manager (PM), the IDIQ Contracting Officer Representative (COR), the TO CO or the TO COR shall be accompanied by a packing list or other suitable shipping document that shall clearly indicate the following:

(a) Contract number;

(b) Task order number;

(c) Name and address of the consignor;

(d) Name and address of the consignee;

(e) Government bill of lading number covering the shipment (if any); and

(f) Description of the item/material shipped, including item number, quantity, number of containers, and package number (if any).

(g) Specific marking requirements may be addressed in individual TOs.

D.3 Branding The Contractor shall comply with the requirements of any Department of Homeland Security Branding and Marking policies under 18 U.S.C. § 701 and 28 U.S.C. § 1733(b). As a matter of law, Federal criminal statutes prohibit unauthorized uses of the Department of Homeland Security Seal. In addition, DHS policy prohibits granting authorization for certain commercial uses of its Seal. However, it is permissible to reference DHS in materials if the reference is limited to true, factual statements. The words DHS and/or Homeland Security should appear in the same color, font, and size as the rest of the text in the document. Moreover, such references shall not imply in any way an endorsement of a product, company, or technology.

“The use of the DHS seal by any persons or organizations outside of DHS may only be done with the prior written approval of the Secretary or his designee. Any such requests for the use of the DHS seal must be made in writing and must specify, in detail, the exact use to be made. Any permission granted by the Secretary will apply only to the specific use outlined in the written request and is not construed as permission for any other use.

The Secretary may seek advice from the Office of General Counsel when making these determinations.”

RFP No. HSHQDC-16-R-00118 Section D – Packaging and Marking

Department of Homeland Security 12 August 2016

As such, requests to use the DHS seal shall be submitted to the TO CO.

D.4 Equipment Removal All Contractor-owned equipment, accessories, and devices located on Government property shall be dismantled and removed from Government premises by the Contractor, at the Contractor’s expense, within 90 calendar days after task order expiration, or as mutually agreed by the Government and the Contractor. Exceptions to this requirement shall be mutually agreed upon and written notice issued by the TO CO. Specific requirements will be addressed in individual TOs.

(End of Section D)

RFP No. HSHQDC-16-R-00118 Section E – Inspection and Acceptance

Department of Homeland Security 13 August 2016

SECTION E - INSPECTION AND ACCEPTANCE

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

This contract incorporates the following clauses by reference with the same force and effect as if they were given in full text. Upon request, the CO will make their full text available. Also, the full text can be accessed electronically at this internet address: http://www.acquisition.gov/far.

FAR Clause No. Title and Date 52-246-4 Inspection of Services—Fixed Price (AUG 1996)

52.246-6 Inspection – Time and Material and Labor Hour (MAY 2001)

E.2 Inspection and Acceptance

(a) Inspection and acceptance of work and services for IDIQ contract deliverables shall be performed by a duly authorized Government representative identified in the IDIQ Task Order in accordance with the FAR clauses incorporated at Section E, Clauses Incorporated by Reference, as applicable. INSPECTION AND ACCEPTANCE PROCEDURES FOR IDIQ

ORDERS WILL BE COMPLETED AT THE COMPONENT LEVEL .

(b) All IDIQ contract deliverables will be inspected for content, completeness, accuracy and conformance by the IDIQ contract and TO COR as detailed in the individual in the IDIQ contract and TO. The IDIQ contract and TO COR will review deliverables utilizing the Government provided acceptance criteria and provide the contractor with an e-mail that provides documented reasons for any non-acceptance.

(c) The IDIQ contract and TO COR will have the right to reject or require correction of any deficiencies in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor shall have an opportunity to correct the rejected deliverable and return it per delivery instructions.

(d) The IDIQ contract and TO COR will accept or reject deliverables and/or services at the place of delivery as promptly as practicable as possible after delivery with a period not-to-exceed thirty (30) calendar days. If the Government has not accepted deliverables or services the Contractor must contact the Government and request the status of the unaccepted service or deliverable. The Government will provide written acceptance for all deliverables and services.

Final acceptance of all deliverables and/or services performed as specified under each IDIQ contract or TO will be made in writing, at destination by the IDIQ contract or TO COR, or as detailed in individual TOs.

(e) Reports, documents and narrative type deliverables will be accepted by the IDIQ contract or TO COR when all discrepancies, errors or other deficiencies identified in writing by the http://www.acquisition.gov/far

RFP No. HSHQDC-16-R-00118 Section E – Inspection and Acceptance

Department of Homeland Security 14 August 2016

Government have been corrected.

(g) Non-conforming products or services will be rejected. Unless otherwise agreed by the parties, deficiencies will be corrected within thirty (30) calendar days of the rejection notice or as specified at the IDIQ contract or TO level. If the deficiencies cannot be corrected within thirty (30) days or as specified at the IDIQ contract or TO level, the Contractor will immediately notify the IDIQ contract or TO CO of the reason for the delay and provide a proposed corrective action plan within ten (10) working days.

(h) Commercial and non-developmental hardware items, software items, pre-packaged solutions, and maintenance and support solutions will be accepted within 30 calendar days of delivery or as specified on the IDIQ contract or TO level when performance is in accordance with delivery requirements.

(End of Section E)

RFP No. HSHQDC-16-R-00118 Section F – Deliveries or Performance

Department of Homeland Security 15 August 2016

SECTION F - DELIVERIES OR PERFORMANCE

F.1 Clauses Incorporated by Reference (FAR 52.252-2) (Feb 1998) This contract incorporates the following clauses by reference with the same force and effect as if they were given in full text. Upon request, the CO will make their full text available. Also, the full text can be accessed electronically at this internet address: http://www.acquisition.gov/far/.

52.242-15 Stop-Work Order (AUG 1989)

52.242.17 Government Delay of Work (APR 1984)

52.247-34 F.O.B. Destination (NOV 1991)

52.247-35 F.O.B. Destination, Within Consignee’s Premises (APR 1984)

F.2 Option to Extend the Term of the Contract (FAR 52.217-9)(Mar 2000)

(a) The Government may extend the term of this contract by written notice to the Contractor at any time within the term of the contract, provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least thirty (30) days before the contract expires. The preliminary notice does not commit the Government to an extension.

(b) If the Government exercises this option, the extended contract shall be considered to include this option clause.

(c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed 36 months.

F.3 Delivery The services required under each individual TO shall be delivered and received at destination within the timeframe specified in each order.

F.4 Place of Performance The place of performance for each individual TO shall be specified in the TO.

F.5 Observance of Legal Holidays and Excused Absence

(a) The Government hereby provides notification that Government personnel observe the listed days as holidays:

(1) New Year's Day (6) Labor Day

(2) Martin Luther King's Birthday (7) Columbus Day

(3) President’s Day (8) Veterans' Day

(4) Memorial Day (9) Thanksgiving Day

(5) Independence Day (10) Christmas Day http://www.acquisition.gov/far/

Department of Homeland Security 16 August 2016

(b) In addition to the ten (10) days designated as holidays, the Government observes:

(1) Any other day designated by Federal Statute

(2) Any other day designated by Executive Order

(3) Any other day designated by the President’s Proclamation

F.6 Notice to the Government of Delays In the event the Contractor encounters difficulty in meeting performance requirements, or when it anticipates difficulty in complying with the contract delivery schedule or completion date, or whenever the Contractor has knowledge that any actual or potential situation is delaying or threatens to delay the timely performance of this contract, the Contractor shall immediately notify the TO CO and the TO COR in writing, giving pertinent details; provided, however, that this data shall be informational only in character and that this provision shall not be construed as a waiver by the Government of any delivery schedule or date, or any rights or remedies provided by law or under this contract.

F.7 Deliverables

(a) All applicable TO deliverables, their required delivery dates, and destination of delivery will be specified in each TO issued under this contract. The schedule for completion of work to be performed under this contract will be delineated in each TO issued under this contract, as applicable.

(b) For purposes of delivery, all deliverables shall be made by close of business (COB) 4:30 P.M. local time (Washington, DC) at destination, Monday through Friday, unless stated otherwise in the TO.

(c) All deliverables submitted in electronic format shall be free of any known computer virus or defects. If a virus or defect is found, the deliverable will not be accepted. The replacement file shall be provided within two (2) business days after notification of the presence of a virus.

(d) Each contract-level and TO-level deliverable shall be accompanied by a cover letter from the Contractor on Company letterhead. Multiple deliverables may be delivered with a single cover letter describing the contents of the complete package.

(e) In the event the Contractor anticipates difficulty in complying with any contract-level delivery schedule, the Contractor shall immediately provide written notice to the IDIQ contract CO and the FLASH PM. For any TO level deliverable, the Contractor shall provide written notification immediately to the TO CO and TO COR. Each notification shall give pertinent details, including the date by which the Contractor expects to make delivery; provided that this data shall be informational only in character and that receipt thereof shall not be construed as a waiver by the Government of any contract delivery schedule, or any rights or remedies provided by law or under this contract.

(f) In the event that a Contractor is non-compliant in submission of deliverables, the Government will reflect the non-compliance in the Contractor’s past performance report.

Department of Homeland Security 17 August 2016

F.8 Deliverables Table

The below deliverables are required for the IDIQ contract. Additional deliverables will be identified at the TO level.

ITEM RFP

REFERENCE DELIVERABLE / EVENT DUE BY

Distribution

1 F.8.1 Post Award Conference Meeting

Within 10 business days after contract award

N/A

2 F.8.2 Annual Contract-Level Reviews and Progress Meetings

Within 10 working days upon the conclusion of the end of fiscal year.

CO/COR/Strategic Sourcing Program Office (SSPO)

3 F.8.3 Progress Meetings Progress Meetings to be determined by the IDIQ CO.

CO/COR/Strategic Sourcing Program Office (SSPO)

4 F.8.4 Contract Status Report - Monthly Task Order Activity Report (including task orders and task order modifications)

15th calendar day of each month

CO/PM/COR

5 F.8.5 Re-representation of Small Business Size Status Report

As specified in Section F. CO/PM/COR

F.8.1 Post award Conference

The Contractor shall participate in a post award conference that will be held within ten (10) business days after contract award. The purpose of the post award conference is to aid both the Contractor and the Government in achieving a clear and mutual understanding of all contract requirements and identify and resolve potential problems (See FAR Subpart 42.5, Postaward Orientation).

The IDIQ contract CO is responsible for establishing the time and place of the conference and will notify the appropriate Government representatives and the Contractors. The IDIQ contract CO will designate or act as the chairperson at the conference.

The conference may be conducted at a location within the Washington, DC, commuting area at the Government’s discretion.

The Contractor shall attend post award conferences on task orders as required. The TO post award conferences will establish work level points of contact for the TO, determine the TO administration strategy, roles and responsibilities and ensure prompt payment and TO closeout.

F.8.2 Annual IDIQ Contract-Level Reviews and Progress Meetings

The IDIQ contract Awardees shall be available to meet with the IDIQ contract CO and COR on an annual basis to review and discuss any IDIQ contract level issues, deliverables or concerns.

The IDIQ contract Awardees shall be available to meet with the IDIQ contract COR upon

Department of Homeland Security 18 August 2016 request to present deliverables, discuss progress, exchange information and resolve emergent technical problems and issues.

Annual reviews will be held to discuss items at the contract level:

• Summary of all open task orders

• Identification of task orders that were opened and/or closed during the past quarter

• Open issues and their status; issues closed during the quarter and their resolution

• Lessons learned during the quarter and recommendations for process improvements

F.8.3 Progress Meetings

Progress meetings shall take place at the Government's facility or via teleconference.

F.8.4 IDIQ Contract Status Report (Monthly Task Order Activity Report) The Contractor shall provide a Monthly Task Order Activity Report, which documents the Contractor’s task order awards and modifications received during the period to be reported. The report is due by the 15th calendar day of each month comprised of activity from the previous month. (For example: The report due February 15th is to cover the activity – new task orders awarded and new modifications received - for the period January 1st through January 31st. If the 15th calendar day falls on a weekend or holiday, the report is due the following business day. If there is no activity during the reporting period, a “no activity” report shall be submitted). The Monthly Task Order Activity Report shall be provided in Microsoft Excel format. The specified format and corresponding instructions will be provided after contract award.

Additionally, the Contractor shall provide copies of all TOs, including TO modifications, that have been issued within the monthly reporting period. For purposes of this requirement, a task order will consist of the OF-347 or SF-30 and the Statement of Work (SOW), Statement of Objectives (SOO) or Performance Work Statement (PWS).

Monthly Task Order Activity Reports and copies of all basic TOs, including TO modifications, shall be provided in electronic format and emailed to the FLASH CO at Agile@HQ.DHS.gov;

the PM at TBD@hq.dhs.gov; and the FLASH COR TBD@hq.dhs.gov. The subject line of the email notice presenting the submission of the monthly report shall be annotated with - Monthly Task Order Activity Report (state the month).

F.8.5 Re-representation of Small Business Size Status Report All FLASH awardees are required to re-represent small business size status according to the following schedule.

Due Dates: Following:

Within thirty (30) days Approval of Contract Novation

Agreement Within thirty (30) days Merger or acquisition where a novation agreement is not required No more than 120 days prior to the end of the base period

N/A mailto:%20Agile@HQ.DHS.gov mailto:darryl.peek@hq.dhs.gov

Department of Homeland Security 19 August 2016

No more than 120 days prior to exercising any option before the end of the base period;

or end of each option period

N/A

F. 9 Task Order Contract Management Task order kick-off meetings and reporting requirements will be defined at the task order level.

(End of Section F)

RFP No. HSHQDC-16-R-00118 Section G – Contract Administration Data

Department of Homeland Security 20 August 2016

SECTION G - CONTRACT ADMINISTRATION DATA

G.1 Accounting and Appropriation Data Accounting and appropriation data for obligations under the contract will be set forth on individual TOs.

G.2 Primary Government Roles and Responsibilities The following subsections describe the roles and responsibility of individuals and/or authorized users who will be the primary points of contact for the Government on matters regarding contract administration as well as other administrative information. The Government reserves the right to unilaterally change any of these individual assignments at anytime.

G.2.1 Government Personnel G.2.1.1 FLASH Program Manager (PM) – Overall Contract Level

The PM within the Office of Chief Information Officer has the overall responsibility for the FLASH program. The PM, with support of the COR, is responsible for the program related activities, including reporting, communications, marketing, outreach and training. The PM for FLASH is:

Name: To Be Determined (TBD) Address: TBD Email: TBD Tel No. TBD

G.2.1.2 FLASH Contracting Officer Representative (COR)–IDIQ Contract Level:

The COR within the Office of Chief Information Officer has responsibility for receipt and acceptance of the contract-level deliverables, reports and past performance reporting for the FLASH IDIQ contracts. The COR supports the PM and the CO in the general management of the program. The COR for FLASH is:

Name: TBD Address: TBD Email: TBD Tel No: TBD

The COR for this contract will be identified by the CO through a written designation. A copy of the letter of designation with specific duties and responsibilities will be provided to the Contractor.

G.2.1.3 FLASH Contracting Officer (CO) – IDIQ Contract Level

The CO within the Enterprise Acquisitions Division (EAD) of OPO has the overall responsibility for administration of the FLASH contracts. The CO, without right of delegation, is the only authorized individual to take actions on behalf of the Government to amend, modify or deviate

Department of Homeland Security 21 August 2016 from the FLASH IDIQ contract terms, conditions, requirements, specifications, details and/or delivery schedules. The CO for the FLASH IDIQ contract is:

Name: Erik Stephenson Address: Department of Homeland Security Office of Procurement Operations (OPO) Enterprise Acquisitions Division (EAD) 245 Murray Drive, Bldg 410 Washington, DC 20528 Email: erik.stephenson@hq.dhs.gov Tel No: 202-447-5484

G.2.1.4 Task Order Contracting Officer (TO CO)

Services will be ordered via TOs issued by Task Order Contracting Officers (TO CO) within the Contract User’s organization following the ordering procedures set forth in Section G.4, Task Order Placement Procedures. The TO CO does not have authority to make changes to the IDIQ contract. Any such requests will be sent to the IDIQ contract CO for consideration.

G.2.1.5 Task Order Contracting Officer’s Technical Representative (TO COR)

TO COs may designate CORs for individual TOs that will be responsible for the day-to-day coordination of the TO.

The TO COR will represent the TO CO in the administration of technical details within the scope of the task order. The TO COR is also responsible for the final inspection and acceptance of all task order deliverables and reports, and such other responsibilities as may be specified in the TO.

The TO COR is not otherwise authorized to make any representations or commitments of any kind on behalf of the TO CO or the Government. The TO COR does not have authority to alter the Contractor’s obligations or to change the TO specifications, price, terms or conditions. If, as a result of technical discussions, it is desirable to modify task order obligations or the specification, changes will be issued in writing and signed by the TO CO.

G.3 Ordering–By Designated Ordering Official The Government will order any supplies and services to be furnished under this contract by issuing TOs on Optional Form 347, or an agency prescribed form, from the effective date of the contract through the expiration date of the contract.