910031-19-R-0003_(Fully_Conformed).docx

Attachment 3: Experience Evaluation Document

Attachment 3: Experience Evaluation Document

The Department of Education, Office of Federal Student Aid (FSA), is seeking proposals for middleware architecture and services, as described in this RFP. FSA anticipates awarding an Indefinite Delivery, Indefinite Quantity (ID/IQ) contract to one or more vendors for the services described herein. Along with this award, FSA anticipates awarding two task orders. This RFP is issued as a small business set-aside under the North American Industry Classification System (NAICS) code 541519, Other Computer Related Services.

Historically, FSA has met its middleware needs every five years with one contract. However, to keep up with technology changes and FSA modernization efforts, FSA plans to award an ID/IQ contract (ten-year term) and use it to order multiple iterations of the middleware requirements described in RFP Attachments 1 and 2, with each iteration having a duration of approximately two and a half years. New orders may result from FSA’s planned modernization efforts (i.e., “Next Gen” efforts). New technology implemented by Next Gen efforts will likely have their middleware needs met by the ID/IQ contract, but not initially.

The following milestone chart contains the projected dates for this procurement.

* The start date will be between July August 1, 2019 and October 30, 2019.

Task Orders 0001 and 0002 will have a start date of no less than one month from their award dates (e.g., if the award date is June 20, 2019, the start date of the transition-in period for each order will begin on or after July 20, 2019). FSA prefers awarding more than one ID/IQ Contract as opposed to one single ID/IQ Contract; therefore, recipients of an ID/IQ Contract will have the opportunity to compete for task orders throughout the ID/IQ Contract’s term.

We look forward to your participation in this procurement.

Sincerely, Paul Bean Contracting Officer FSA Acquisitions Group RFP Table of Contents

i

SECTION I – SOLICITATION TYPE, SB SET-ASIDE, AND NEXT GEN

1.0 SOLICITATION TYPE

This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Federal Acquisition Regulation (FAR) Subpart 12.6, “Streamlined Procedures for Evaluation and Solicitation for Commercial Items,” as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are requested and a written solicitation will not be issued. This solicitation document, and incorporated provisions and clauses, are those in effect through Federal Acquisition Circular 2019-01 (effective January 22, 2019). This document is issued as a RFP, number 910031-19-R-0003.

2.0 SB SET-ASIDE NOTIFICATION AND NAICS CODE

This RFP is set-aside for small business participation under NAICS code 541519, Other Computer Related Services. The small business size standard for this NAICS code is $27.5 million.

3.0 FSA NEXT GEN

Concurrent to this solicitation, FSA is in the early stages of an enterprise-wide initiative known as Next Gen FSA. Initially, FSA will modernize its technical and operational architecture, which will be flexible to expand and support other financial services. In addition to improving the overall customer experience, the new environment will improve operational flexibility, enhance cost and operational efficiency, and generate better outcomes for customers and taxpayers. Next Gen FSA may contain a middleware support effort. FSA does not expect the work of the two initial task orders solicited to initially support Next Gen FSA directly. The schedule for the modernization program will be driven by the award of Next Gen contracts and the prioritization of the modernization phases. Therefore, FSA cannot estimate when this procurement process will be completed and which parts of FSA’s current technical and operational architecture will be excluded from Next Gen FSA. As a result, FSA cannot estimate Next Gen FSA’s impact on the two task orders solicited under this RFP or future task orders.

All vendors are hereby placed on notice that FSA, in seeking to build a future state environment with a consistent, reliable, and scalable architecture; prevent duplication, redundancy, and incompatibility; and reduce costs and complexity. FSA may require all Next Gen FSA applications and information systems, once created and stabilized, to transition to task order(s) under this ID/IQ contract (either as modifications or new task orders). This ID/IQ contract represents FSA’s Enterprise Middleware Architecture and Services (EMAS) Program for middleware and cloud platform services and support.

SECTION II – BASIC ID/IQ CONTRACT INFORMATION

1.0 GENERAL

EMAS is an Indefinite Delivery, Indefinite Quantity (ID/IQ) contract to provide middleware solutions for a variety of FSA applications and systems. The scope of work for this contract is broad to accommodate FSA’s immediate and future needs resulting from modernization efforts and other initiatives.

The scope of work is provided in Section III, ID/IQ Contract Statement of Work.

Hereinafter, the EMAS ID/IQ contract is referred to as the “ID/IQ Contract” while task order(s) issued under the ID/IQ Contract are referred to as “order(s)”.

2.0 CONTRACT ORDERING PERIOD

The period of performance, hereinafter referred to as the “ordering period”, for the ID/IQ Contract is ten years. Orders may only be issued during this ordering period. An order may be awarded prior to the start of the ordering period as long as the effective date of the order is on or after the start date of the ordering period. (The start of the ordering period will be between July 1, 2019 and October 30, 2019 and will be determined at the Government’s discretion upon award.)

3.0 TASK ORDER PERIOD OF PERFORMANCE INFORMATION

Orders placed during the ordering period may end up to three years beyond the end date of the ordering period; therefore, all orders have to be substantially completed by (exact date to be determined upon award).

4.0 ID/IQ CONTRACT SCOPE/SERVICES AVAILABLE FOR ORDERING

Only commercial services that are within the scope of the ID/IQ Contract’s Statement of Work (see RFP Section III) may be ordered.

5.0 ALLOWABLE PERFORMANCE LOCATIONS

The Contractor’s site is the only allowable performance location with the exception for meetings at customer sites.

6.0 ALLOWABLE ORDER TYPES

The allowable order types for orders placed against the ID/IQ Contract are as follows:

(1) Time and Materials (T&M)

(2) Labor Hour (LH)

(3) Firm-Fixed Price (FFP)

Orders may combine one or more of the allowable order types.

For a definition of each order type, see FAR Part 16, “Types of Contracts.”

7.0 MINIMUM GUARANTEE AMOUNT

Pursuant to FAR clause 52.216-22, the ID/IQ Contract’s minimum guarantee is $25,000; upon award of the ID/IQ Contract, this guarantee will be fulfilled by an order.

8.0 MAXIMUM CONTRACT CEILING

Pursuant to FAR clause 52.216-22, the maximum aggregate ceiling for the ID/IQ Contract is $100 million.

SECTION III – ID/IQ CONTRACT STATEMENT OF WORK

1.0 GENERAL

FSA’s core mission is to ensure that all eligible customers benefit from Federal financial assistance (e.g., grants, loans, and work-study programs) for post high-school education. FSA’s programs comprise of the nation’s largest source of student financial aid. Every year, over 18 million students apply for Federal financial aid and FSA has over 42 million existing customers. FSA’s lending portfolio is approximately $1.4 trillion, with $1.1 trillion directly serviced. This portfolio grows at 7% per year, driven by nearly $100 billion in annual disbursements across more than 17 million annual loan originations. In conjunction with institutions of higher learning and third-party vendors, FSA provides services across the full Federal financial aid lifecycle, including:

(1) Application and Eligibility Determination: Customers complete a Free Application for Federal Student Aid (FAFSA) to learn about their Federal student aid options.

(2) Disbursement: For eligible customers, FSA originates most aid through higher educational institutions to FSA customers.

(3) Student Aid Servicing: FSA assigns customer loans, specialty aid programs, specialty claims, and consolidation origination, among other processes, to be serviced by one of its designated loan servicers.

(4) Recovery: For customers who are delinquent on their loans, FSA contracts with a debt management vendor and Private Collection Agencies to seek repayment.

FSA uses a complex set of applications and systems, collectively called FSA Applications, to support its mission. To maintain custom functionalities, FSA Applications rely on the services in scope of this SOW.

2.0 OBJECTIVE

This Statement of Work (SOW), which identifies a broad scope of services, facilitates the continued, comprehensive, and effective operation of integrated sets of middleware functions. Orders issued will have detailed requirements within the scope of this SOW.

3.0 SERVICE AREAS

The Contractor shall deliver solutions, services, and materials to meet the requirements of all orders issued against the EMAS ID/IQ Contract. The services available under the EMAS ID/IQ Contract are categorized in three Service Areas.

All necessary program management, quality assurance, architecture management, IT compliance, change management, release and deployment management, disaster recovery, capacity planning, evergreening management, incident management and problem resolution, security, enterprise performance testing, subject matter expertise, and ancillary support is considered in scope of each service area.

3.1 SERVICE AREA ONE – INTEGRATED TECHNICAL ARCHITECTURE (ITA)

Provide solutions for building, integrating, maintaining, managing, enhancing, and/or migrating a common, shared platform of COTS products and services, including customized Reusable Common Services (RCS), that can be used by FSA Applications, current and future.

3.2 SERVICE AREA TWO – ENTERPRISE SERVICE BUS (ESB)

Provide solutions for building, integrating, maintaining, enhancing, and/or migrating enterprise-wide application-messaging, web services, and API capabilities for FSA Applications

3.3 SERVICE AREA THREE – CLOUD SERVICES

Provide solutions for building, integrating, maintaining, enhancing, and/or migrating both Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) offerings for providing shared technologies, including COTS products, to: (1) support FSA’s new business applications; and (2) deploy, operate, and maintain FSA technologies in the cloud (e.g., ITA and ESB); and (3) integrate FSA technologies with legacy business applications, systems, and other Software as a Service (SaaS) offerings at FSA.

FSA, in seeking to comply with FITARA, ED’s Strategic IT goals, as well as Office of Management and Budget’s (OMB)-mandated goals established in the Data Center Optimization Initiative (DCOI), may require all new applications and information systems, once created and stabilized, to transition to and leverage common cloud infrastructure services (e.g. through FSA’s Next Generation Data Center (NGDC) or some other FSA-identified services), and/or leverage common enterprise-wide traditional data center services and infrastructure hosting provider (e.g. through FSA’s NGDC or some other FSA-identified services/provider). The NGDC program provides a physical data center structure, access to FISMA High private cloud infrastructure services, and access to FedRAMP High and FedRAMP Moderate cloud infrastructure services, including AWS and Azure.

In a traditional data center environment, EMAS provides middleware platform and architecture services that enable FSA applications, as well as provides high-touch expertise and support to application teams. The data center provider (e.g. NGDC) provides infrastructure services, such as hardware, operating system, network, and firewall support, as well as takes responsibility for all changes in the production environment.

Similarly, as FSA migrates its existing applications to the cloud, FSA anticipates that EMAS shall be continue to provide Integrated Technical Architecture (ITA) and Enterprise Service Bus (ESB) capabilities, as well as future middleware needs, as Platform-as-a-Service services (PaaS) cloud services and middleware architecture support. These middleware-as-PaaS capabilities shall leverage and be hosted on the Infrastructure-as-a-Service services provided by the NGDC program. EMAS vendors will continue to provide high-touch middleware product expertise and PaaS architectural guidance and support to application teams. The data center/cloud services provider (e.g. NGDC) will be responsible for providing the underlying Infrastructure-as-a-Service services and support as part of their role as the infrastructure vendor.

The table below describes anticipated high-level roles and responsibilities for IaaS and PaaS cloud services and support leveraged through EMAS and NGDC. These roles and responsibilities are likely to evolve as the cloud and DevSecOps strategy and technical approach is developed.

Infrastructure as a Service

Platform as a Service

Application Architecture and Code

Table 1: Cloud Services Roles and Responsibilities between Vendors

3.3.1.1 ITA AND ESB CLOUD DEPLOYMENT

The Contractor shall have the capabilities to:

(1) Develop and present a cloud deployment strategy and sequencing plan for ITA and ESB infrastructure, COTS technologies, custom code, data, and the FSA business applications that are hosted in the ITA and/or leverage ESB.

(2) The Contractor shall, in a progressive fashion, execute the deployment of ITA and ESB to a FedRAMP approved cloud of FSA’s choice, including NGDC Cloud.

(3) Perform migration testing and readiness demonstration for the migration.

(4) Support the NGDC vendor in integrating the NGDC governance processes (e.g., change, incident, release, disaster recovery) with ITA and ESB prior to the production deployment of ITA and ESB to the cloud.

3.3.1.2 Cloud API Management and Enterprise API Gateway Services

For ESB and ITA, the Contractor shall:

(1) Provide implementation and operation and maintenance of standards-based APIs for all backend calls from the FSA mobile app and web applications.

(2) Provide operations and maintenance of a highly available, scalable single-entry point to process for all API calls from the mobile app and web applications.

(3) Provide implementation and operations and maintenance of a solution that ensures all API calls from the FSA mobile app and web applications are appropriately secured via a standards-based security framework for API security and factor in integration with FSA’s designated Identity and Access Management (IAM) solution.

(4) Transform and mediate between different data formats and protocols (e.g. REST, SOAP, XML, etc.).

(5) Provide a solution that provides composite services coming from multiple backend service providers.

(6) Provide seamless integration with legacy FSA applications hosted at the NGDC.

(7) Provide metric and availability data from the API entry point into the proposed monitoring solution.

(8) Embrace Service-Oriented-Architecture (SOA) by promoting standards-based Web-services (SOAP, REST), enable discovery of FSA branded web-services based on directory of published web-services (subscription model).

3.3.1.3 Cloud Security Services

For ESB and ITA, the Contractor shall:

(1) Comply with Continuous Monitoring requirements and conduct standards per FedRAMP policy.

(2) Comply with Trusted Internet Connection (TIC) and MTIPS requirements.

(3) Comply with IPv6 requirements per OMB.

3.3.1.4 Cloud Monitoring Services

For ESB and ITA, the Contractor shall:

(1) Provide a monitoring solution to monitor all operational architecture components and alert operators of issues in a timely manner.

(2) Provide a monitoring solution to actively provide evidence of system availability and the availability of the shared cloud services.

(3) Provide a monitoring solution that can incorporate end-user experience data from both the FSA mobile application and other web applications.

3.3.1.5 Cloud Application Services

For ESB and ITA, the Contractor shall:

(1) Provide cloud orchestration services to quickly configure, provision, deploy environments, and integrate monitoring, and security services.

(2) Implement serverless computing.

(3) Implement dynamic scaling policies to handle on-demand capacity requirements.

(4) Implement the automation for the rollout of all system changes, security patches, and new features with minimal impact to availability of FSA applications to end-users.

(5) Implement a GitHub solution for centralized code and configuration management. This solution shall be hosted within the FedRAMP approved cloud and will be part of the EMAS system boundary.

(6) Implement a centralized issue tracking using JIRA. This solution shall be hosted within the FedRAMP approved cloud and will be part of the EMAS system boundary.

(7) Setup, operate and maintain access controls and policies to various FSA business application teams to enable them to use the GitHub solution in a secure fashion.

(8) Setup, operate and maintain tools and technologies for Continuous Integration, Continuous Delivery and Continuous Testing as part of a DevOps framework that can be leveraged by multiple FSA business applications.

3.3.1.6 KEY PERSONNEL

Senior or higher Project Manager Personnel, all senior or higher technical leads, the primary architect/chief technical officer, and the primary lead for security requirements.

SECTION IV – ID/IQ CONTRACT PRICING SCHEDULE

1.0 ID/IQ CONTRACT LABOR CATEGORIES AND RATES

This section will be populated by the completed Attachment 4 from the successful Offeror’s proposal. FSA’s ID/IQ contract only recommends experience requirements and it is responsibiltty of the Offeror to propose appropriate experience requirements for each task order when appropriate.

1.1 The labor rates in subsection 1.0 are fully burdened, off-site, ceiling rates inclusive of all direct and indirect costs. For orders that contain a period of performance that extends beyond the ID/IQ Contract’s ordering period (but not to exceed two years), the rates shall not exceed the rates in Year Ten and an amount, for each additional year, not to exceed the average change in rates over the ten-year ordering period (e.g., if the rates change on average 2% from Year One through Year Ten and a labor rate is $100 in Year Ten, the labor rate for Year 11 cannot exceed $102.00 and the labor rate for Year Twelve shall not exceed $104.04).

2.0 REIMBURSABLE OTHER DIRECT COSTS

As T&M orders are allowed, reimbursable Other Direct Costs (ODCs) are allowed. Such costs shall be ancillary to services ordered. The costs likely will be rarely used; historically, they were used for travel costs. As FSA expects limited use of ODCs, no indirect costs or profit are allowed on these ODCs; however, if ODCs across all orders for an awardee exceed $250k, the Contractor may request negotiation of indirect costs and profit for new ODCs and FSA will negotiate these costs with all contract holders.

3.0 LOCAL AND NON-LOCAL TRAVEL

Orders may require the Contractor to travel to FSA’s headquarters (Washington, DC) for meetings with the frequency defined in each order. Travel events more than 20 miles outside of the Washington DC metropolitan area may be ordered as reimbursable travel, which shall be reimbursed in accordance with FAR 31.205-46.

4.0 FIXED PRICED MATERIALS AND TRAVEL

Materials or Contractor travel costs that are priced on a firm-fixed price basis may be included in orders. Such costs shall be ancillary to the services ordered.

SECTION V – TASK ORDER ORDERING PROCEDURES

1.0 AUTHORIZED ORDERING CONTRACTING OFFICERS

Task orders may be issued by only Department of Education warranted Contracting Officers (COs). COs must obtain permission to issue a Request for Task Order Proposal (RFTOP) from the CO responsible for administering the ID/IQ Contract. COs are responsible for clearly identifying the applicable order type(s) in each RFTOP, and making all required pre-solicitation determinations. Orders that are not within the scope of the ID/IQ Contract are not authorized. COs must determine the overall price to be fair and reasonable for each order awarded; only the labor rates in the ID/IQ Contract are determined fair and reasonable; as a result, COs may consider the following in their fair and reasonableness determination: (1) consider the proposed level of effort and labor categories together for appropriateness (e.g., appropriate labor mix that is sufficient to complete the work requirements, but not excessive); and (2) consider the proposed fixed-price materials and/or travel costs (if applicable).

2.0 FAIR OPPORTUNITY SOLICITATION AND AWARD

Contracting Officers may solicit for orders by issuing a RFTOP to all contract holders. Each RFTOP procurement must comply with the procedures in FAR 16.505, “Ordering.”

3.0 AUTHORIZED ID/IQ CONTRACT ORDERING PERIOD

Orders may only be placed during the ordering period (see subsection 2.0 of Section II, Contract Ordering Period); under no circumstances shall orders be placed under the ID/IQ Contract if it has been terminated or has expired.

4.0 OPTIONS AND MAXIMUM PERIOD OF PERFORMANCE FOR TASK ORDERS

Orders may contain options, as defined in FAR Part 17. The period of performance for each order, inclusive of options, may not exceed thirty-six (36) months beyond the expiration date of the ID/IQ Contract.

5.0 APPLICABILITY OF ID/IQ CONTRACT TERMS TO TASK ORDERS

Clauses and other terms included in the ID/IQ Contract are applicable to all orders unless otherwise excluded by individual orders.

SECTION VI – INSTRUCTIONS TO OFFERORS

1.0 GENERAL SUBMISSION INSTRUCTIONS

This section provides instructions for preparing proposals, including format and content requirements. Proposals must comply with all instructions.

2.0 PROPOSAL COSTS AND ALTERNATE PROPOSALS NOT ALLOWED

The Government will not be responsible for any proposal preparation or other pre-proposal costs. The Government will not consider alternate proposals.

3.0 RESPONSIVE PROPOSAL REQUIREMENTS

If an Offeror (1) fails or refuses to assent to any of the RFP’s terms, (2) includes assumptions, terms, or conditions that nullify any of the RFP’s terms, or (3) fails to submit information required by the RFP, the Government may consider the proposal “non-responsive” and therefore ineligible for award.

4.0 PROPOSAL REQUIREMENTS

4.1 PROPOSAL ORGANIZATION, FORMATTING, AND PAGE LIMITATIONS

Proposals shall be titled, compliant with the page limitations, formatted, and sectioned into separate electronic volumes as described in the table below:

* The page limitation excludes cover, table of contents pages, schedule for accomplishing work in first year (as referend in Section VI, 4.2.3 and 4.2.4), draft project management plans (however this document shall not exceed 40 pages), teaming agreements, letters of intent for subcontractors, and resumes (all resumes submitted shall not exceed three pages). Each electronic Volume may consist of one or more electronic documents.

4.2 MINIMUM PROPOSAL CONTENTS

4.2.1 VOLUME ONE: RELEVANT EXPERIENCE

Proposals shall contain the following in this volume to be considered complete:

(1) Experience Evaluation Documents A minimum of one but no more than six Experience Evaluation Documents (see Attachment 3) that is/are reflective of the Offeror’s relevant experience for Task Order 0001 (ITA Support), Task Order 0002 (ESB Support), and Sample Task Order 0003 (Cloud Services Support). Offerors must follow the instructions in the Experience Evaluation Document.

(2) Experience Cross Walk A graph or other illustration that cross walks each experience from the Experience Evaluation Documents with Task Order 0001 (ITA Support), Task Order 0002 (ESB Support), and Sample Task Order 0003 (Cloud Services Support).

(3) Letters of Intent for Subcontractors If submitting experience for a subcontractor, the Offeror shall provide a letter of intent describing the subcontractor’s likely involvement in future orders and that involvement must be substantial and consistent with how the Offeror is proposing for Task Orders 0001 (ITA Support) and 0002 (ESB Support). Also, the Contractor shall provide all teaming agreements or other documents that describe the Contractor’s agreement with subcontractors for the work that subcontractors will perform for Task Orders 0001 and 0002.

4.2.2 VOLUME TWO: SAMPLE TASK ORDER 0003 (CLOUD SERVICES) TECHNICAL APPROACH

The Offeror must submit narratives describing its technical approach to meeting all requirements in ID/IQ Section III, ID/IQ Contract Statement of Work, subsection 3.3.1, Sample Task Order 0003.

The Offeror shall provide its Staffing Approach to meeting these SOW requirements to include (level of effort is not required):

(1) Key Personnel Qualification Matrix to include Labor Category, Position, Name, Title, and a synopsis of relevant work experience. Also include resumes of Key Personnel, which must clearly demonstrate each employee’s qualifications to include description of duties, accomplishments, or other demonstrative information.

(2) A summary-level description of each company that is part of the team composition by planned task/functional area.

4.2.3 VOLUME THREE: TASK ORDER 0001 (ITA SUPPORT) TECHNICAL APPROACH

The Offeror must submit narratives describing its technical approach to meeting the following requirements from Attachment 1, ITA Performance Work Statement:

(1) PWS C.1 Document ITA Current State Technical Architecture

(2) PWS C.2: Research, Architecture Strategy, Technology Evaluation, and Planning (detailed response expected)

(3) PWS C.3: Build and Deploy Pre-Production Application Environments (detailed response expected)

(4) PWS C.4: Support Capacity Planning and Capacity Management (detailed response expected)

(5) PWS C.5: Incident and Problem Management Support (detailed response expected)

(6) PWS C.6: Provide Application Monitoring and Management Support

(7) PWS C.7: Provide Disaster Recovery and Continuity of Services Support

(8) PWS C.8: Support Surveillance and Oversight

(9) PWS C.9: Provide Management Support. Include a Draft Project Management Plan and a schedule for accomplishing work in the first year. (detailed response expected)

(10) PWS C.10: Operate, Maintain, and Evolve Products, Technologies, Components, and Services (detailed response expected for C.10.1-3)

(11) PWS C.11: FSA Application and Integration Support (detailed response expected)

(12) PWS C.12: New Application and Technology Insertion and Technology Proofs of Concept

(13) PWS C.13: PEPS and eAPP Application Support (detailed response expected)

(14) PWS C.14: Transition Tasks. Include your Transition-In Plan and Transition-Out Plan. (detailed response expected)

(15) PWS F.4: Deliverables Table. Do not separately address – Address in your narratives for (1) – (14) above.

(16) PWS G: Performance Requirements Summary. Do not separately address – Address in your narratives for (1) – (14) above.

Also, the Contractor shall state in its offer the information technology assets (software name, manufacturer, version, platform, and other relevant technical specifications) it deems necessary to provide services and deliverables outlined in the solicitation, and shall define the compatibility of its assets with the FSA assets with which it will interface.

The Offeror shall provide its Staffing Approach to meeting the above PWS requirements to include:

(1) Key Personnel Qualification Matrix to include Labor Category, Position, Name, Title, and a synopsis of relevant work experience. Also include resumes of Key Personnel, which must clearly demonstrate each employee’s qualifications to include description of duties, accomplishments, or other demonstrative information.

(2) A summary-level description of each company that is part of the team composition by planned task/functional area.

(3) A breakdown of the level of effort (labor categories and hours) for all requirements in PWS Section C (e.g., C.1, C.2).

4.2.4 VOLUME FOUR: TASK ORDER 0002 (ESB SUPPORT) TECHNICAL APPROACH

The Offeror must submit narratives describing its technical approach to meeting the following PWS requirements from Attachment 2, ESB Performance Work Statement:

(1) PWS C.1 Document ESB Current State Technical Architecture

(2) PWS C.2: Research, Architecture Strategy, Technology Evaluation, and Planning (detailed response expected)

(3) PWS C.3: Build and Deploy Pre-Production Application Environments (detailed response expected)

(4) PWS C.4: Support Capacity Planning and Capacity Management (detailed response expected)

(5) PWS C.5: Incident and Problem Management Support (detailed response expected)

(6) PWS C.6: Provide Application Monitoring and Management Support

(7) PWS C.7: Provide Disaster Recovery and Continuity of Services Support

(8) PWS C.8: Support Surveillance and Oversight

(9) PWS C.9: Provide Management Support. Include a Draft Project Management Plan and a schedule for accomplishing work in the first year. (detailed response expected)

(10) PWS C.10: Operate, Maintain, and Evolve Products, Technologies, Components, and Services (detailed response expected for C.10.1-3)

(11) PWS C.11: FSA Application and Integration Support (detailed response expected)

(12) PWS C.12: New Application and Technology Insertion

(13) PWS C.13: Transition Tasks. Include your Transition-In Plan and Transition-Out Plan. (detailed response expected)

(14) PWS F.4: Deliverables Table. Do not separately address – Address in your narratives for (1) – (13) above.

(15) PWS G: Performance Requirements Summary. Do not separately address – Address in your narratives for (1) – (13) above.

Also, the Contractor shall state in its offer the information technology assets (software name, manufacturer, version, platform, and other relevant technical specifications) it deems necessary to provide services and deliverables outlined in the solicitation, and shall define the compatibility of its assets with the FSA assets with which it will interface.

The Offeror shall provide its Staffing Approach to meeting the above PWS requirements to include:

(1) Key Personnel Qualification Matrix to include Labor Category, Position, Name, Title, and a synopsis of relevant work experience. Also include resumes of Key Personnel, which must clearly demonstrate each employee’s qualifications to include description of duties, accomplishments, or other demonstrative information.

(2) A summary-level description of each company that is part of the team composition by planned task/functional are.

(3) A breakdown of the level of effort (labor categories and hours) for all requirements in PWS Section C.

4.2.5 VOLUME FIVE: PRICE PROPOSAL

Offerors shall provide the following in this volume to be considered complete:

(1) Period for Acceptance of Offers (Addendum to FAR 52.212-1(c)) On the first page of Volume One, the Offeror shall make a clear statement that its entire proposal is valid for 180 days from the deadline for proposals.

(2) Pricing Schedule The Offeror shall complete and submit all worksheets from Attachment 4, ID/IQ Contract and Task Order Pricing Sheets: the worksheets are titled, “IDIQ Contract,” “Task Order 0001 – ITA,” and “Task Order 0002 – ESB.” The labor rates proposed for the ID/IQ contract for Years 1, 2, and through 3 shall be equal to the labor rates proposed for Task Orders 0001 and 0002 for the same labor categories and time period. E.g., for Task Order 0001, (e.g., if an Offeror proposes to use the labor category of offering $75 an hour for “Category 1: Application Developer (Junior)” for the Base Period, Option Period One, and Option Period Two at for Task Order 0001 – ITArates of $100, $101, and $102, respectively, the Contractor Offeror shall propose ID/IQ Contract rates of exactly a $75 100 for Year 1, $101 for Year 2, and $103 for Year 3 for rate for Year 2 of the ID/IQ Contract for Category 1: Application Developer (Junior)).

(3) Completed Solicitation Provisions and Clauses Any completed solicitation provisions or clauses that require the Offeror’s input, including EDAR provision 3452.239-71 (one each for Task Orders 0001 and 0002), EDAR provision 3452.209-70, and FAR provision 52.227-15 (one for Task Orders 0001 and 0002), and either paragraph (b), if applicable, or all of FAR provision 52.212-3.

(4) Proposal Exceptions and Assumptions Any exceptions/assumptions taken with regard to the RFP or any other information that the Offeror finds necessary and pertinent to their proposal. (Exceptions and assumptions for Task Orders 0001 or 0002 shall be included in this volume.)

(5) Prospective Subcontractors If proposing subcontractor(s), the Offeror shall provide all teaming agreements detailing the specific work and/or tasks each party will perform on Task Orders 0001 and 0002. The Contractor shall also provide a monetary breakdown of the value of its planned subcontracts for Task Orders 0001 and 0002 and indicate the employer of each proposed labor category for the task orders as provided in the pricing templates

(6) Joint Venture Documentation Offerors proposing as part of a Joint Venture, including as part of an SBA mentor-protégé program, must provide the following information as part of their proposal:

a. The DUNS Number of the Joint Venture.

b. A narrative describing how the Joint Venture meets the definition of a Joint Venture for size determination purposes (FAR 19.101 (7)(i)).

c. The Offeror must submit a complete copy of the Joint Venture agreement that formally established the Joint Venture.

(7) Work Location Provide the work location(s) of all proposed labor for Task Orders 0001 and 0002.

5.0 QUESTIONS

All questions and concerns regarding any aspect of this RFP shall be submitted by e-mail to FSAEAT@ed.gov by 3:00 p.m. Local Time (Washington, DC) on Thursday, April 23, 2019. The subject line for e-mails with questions or concerns should read as follows: “RFP 910031-19-R-0003 Questions.” An amendment will be issued if any of the submitted questions require changes to the RFP.

2nd Question-and-Answer Period Starting on May 21, 2019, all questions and concerns regarding any aspect of this RFP shall be submitted by e-mail to FSAEAT@ed.gov by 6:00 p.m. Local Time (Washington, DC) on Thursday, May 30, 2019. The subject line for e-mails with questions or concerns should read as follows: RFP 910031-19-R-0003 Questions.

6.0 PROPOSAL SUBMISSION INSTRUCTIONS AND DEADLINE

Offerors must submit their proposals to FSAEAT@ed.gov by 112:00 ap.m. Local Time (Washington, DC) on May July 128, 2019. FSA’s e-mail limit is 15 MB; therefore, Offerors shall send their proposal across multiple e-mails with each not exceeding 15 MB, if their entire proposal exceeds 15 MB. Facsimile and hardcopy submittals will not be accepted. It is the responsibility of the Offeror to confirm FSA’s receipt of its proposal.

SECTION VII – EVALUATION CRITERIA

1.0 EVALUATION AND DOWN-SELECT PROCESS

First Down Select Responsive proposals will first be evaluated against Go/No-Go Factor One (Experience). Proposals rated “Acceptable” for this factor will be evaluated against Go/No-Go Factor Two (Cloud Services Support). (All other proposals will be disqualified from award.)

Second Down Select Proposals rated “Acceptable” for Go/No-Go Factor 2 (Cloud Services Support) will then be evaluated against Factor One (ITA Support), Factor Two (ESB Support), Factor 3 (Past Performance) and Factor 4 (Price). (All other proposals will be disqualified from award.)

Competitive Range and Discussions (Addendum to FAR 52.212-1(g)) Following the evaluation of Factors One, Two, Three, and Four, the Government may conduct a Competitive Range that considers (1) proposal ratings and their technical merits for Factors One and Two, (2) proposal ratings from Factor Three, and (3) the “ID/IQ Contract Total Price” from Factor Four, Price. The Government does not anticipate discussions; therefore, the offeror’s initial proposal should contain the offeror’s best terms from a price and technical standpoint. However, should discussions be conducted, a competitive range will be established. If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

Offerors will not be eligible for award if their “ID/IQ Contract Total Price”, proposed ID/IQ labor rates are determined not reasonable, or if an Offeror is not determined “responsible,” as defined in FAR Subpart 9.1.

2.0 BASIS OF AWARD INFORMATION

2.1 BASIS OF AWARD FOR ID/IQ CONTRACT

FSA anticipates awarding an ID/IQ Contract to one or more Offerors. Award will be made to the Offeror(s) submitting a proposal that is determined the best value to the Government, price (Factor Four) and non-price factors (Factors One, Two, and Three) considered. Best value will be determined by means of the tradeoff process. The order of importance of factors is provided as follows: Factor One (Integrated Technical Architecture Support) and Factor Two (Enterprise Service Bus Support) are equally important and each are more important than Factor Three (Past Performance) and Factor Four (Price). Factor Three is less important than Factor Four (Price). Regarding Factor Four, the calculated “ID/IQ Contract Total Price” will be used for tradeoff purposes.

2.2 BASIS OF AWARD FOR TASK ORDERS 0001 AND 0002

Simultaneously with award of the ID/IQ Contract, the Government anticipates awarding two initial task orders, Task Order 0001 (Attachment 1: ITA Performance Work Statement) and Task Order 0002 (Attachment 2: ESB Performance Work Statement).

Task Order 0001 (ITA Support) Award of Task Order 0001 will be made to the Offeror submitting a proposal that is determined the best value to the Government with the following factors considered:

(1) Factor One – Integrated Technical Architecture Support Technical Approach

(2) Factor Four – Price. (Only Task Order 0001 price evaluation elements from Factor Four will be considered for the basis of award for Task Order 0001.)

Best value will be determined by the tradeoff process. The order of importance of factors is provided as follows in order of descending importance: Factor One and Factor Four (Price – Task Order 0001 Price); however if the ratings for Factor One converge, the price (Factor Four) may become more important.

Task Order 0002 (ESB Support) Award of Task Order 0002 will be made to the Offeror submitting a proposal that is determined the best value to the Government with the following factors considered:

(1) Factor Two – Enterprise Service Bus Support

(2) Factor Four – Price. (Only Task Order 0002 price evaluation elements from Factor Four will be considered for the basis of award for Task Order 0002.)

Best value will be determined by the tradeoff process. The order of importance of factors is provided as follows in order of descending importance: Factor Two and Factor Four (Price – Task Order 0002 Price); however if the ratings for Factor Two converge, the price (Factor Four) may become more important.

3.0 ALL-OR-NONE PROCUREMENT NOTIFICATIONS

The ID/IQ contract award is an all-or-none procurement; therefore, Offerors are competing for an ID/IQ Contract for all items solicited in the ID/IQ’s SOW.

The procurement of Task Orders 0001 (ITA) and 0002 (EBC) are all-or-none procurements; therefore, one vendor will be awarded a task order for each requirement.

4.0 TERMS OF PROPOSAL ACCEPTANCE

A written notice of award or acceptance of a proposal, furnished to an Offeror within the specified timeframe, shall result in a binding contract without further action by either party. Before the proposal’s expiration, the Government may accept a proposal in full, whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.

5.0 EVALUATION FACTORS

5.1 GO/NO-GO FACTOR ONE: EXPERIENCE

The Offeror’s Volume One will be evaluated to determine if it demonstrates sufficient experience.

This factor will be rated as either “Acceptable” or “Unacceptable.” To obtain the “Acceptable” rating, the Offeror must comply with the following or it will be rated “Unacceptable”:

(1) The experience submitted on the Experience Evaluation Documents, when combined, must demonstrate at least one instance of comparable experience for Task Order 0001 (Attachment 1: ITA Performance Work Statement), Task Order 0002 (Attachment 2: ESB Performance Work Statement), and Sample Task Order 0003 (RFP Section III, ID/IQ Contract Statement of Work, subsection 3.3.1). In order for submitted experience to qualify as comparable, it must be (1) determined to be at a minimum commiserate with the technical scope (including depth of work and complexity) of FSA’s Task Orders 0001 and 0002 and Sample Task Order 0003, and (2) the experience (experience determined not relevant to the technical scope of any of said Task Orders will be excluded) must be comparable in size (in terms of monetary values), and duration (2.5 years) to FSA’s Task Orders 0001 and 0002 and Sample Task Order 0003 (the “size” evaluation is excluded for Sample Task Order 0003).

5.2 GO/NO-GO FACTOR TWO: CLOUD SERVICES SUPPORT

This factor will be rated as either “Acceptable” or “Unacceptable.” To obtain the “Acceptable” rating, the Offeror’s Volume Two must demonstrate that its technical approach is viable to meeting the requirements in Sample Task Order 0003 (see RFP Section III, ID/IQ Contract SOW, subsection 3.3.1).

5.3 FACTOR ONE: INTEGRATED TECHNICAL ARCHITECTURE (ITA) SUPPORT

The Offeror’s Volume Three will be evaluated to determine the extent to which the Contractor’s proposed technical approach meets ITA requirements in Task Order 0001.

Technical Approach – The proposed technical approach, not including labor, to meeting FSA’s Task Order 0001 requirements will be assessed on: (1) the extent to which it is viable to meeting FSA’s requirements; and (2) the extent to which the Government benefits from approaches that either exceed FSA’s requirement or are in addition to but related to FSA’s requirement.

Staffing Approach – The proposed staffing approach, including level of effort (hours and labor categories), labor category minimum qualifications, and key personnel qualifications, will be assessed on the extent to which it is viable to meeting FSA’s requirements, including a review of whether it principally supports the implementation of one or more high-quality solutions.

5.4 FACTOR TWO: ENTERPRISE SERVICE BUS (ESB) SUPPORT

The Offeror’s Volume Four will be evaluated to determine the extent to which the Contractor’s proposed technical approach meets ESB requirements in Task Order 0002.

Technical Approach – The proposed technical approach, not including labor, to meeting FSA’s Task Order 0002 requirements will be assessed on: (1) the extent to which it is viable to meeting FSA’s requirements; and (2) the extent to which the Government benefits from approaches that either exceed FSA’s requirement or are in addition to but related to FSA’s requirement.

Staffing Approach – The proposed staffing approach, including level of effort (hours and labor categories), labor category minimum qualifications, and key personnel qualifications, will be assessed on the extent to which it is viable to meeting FSA’s requirements, including a review of whether it principally supports the implementation of one or more high-quality solutions.

5.4 FACTOR THREE: PAST PERFORMANCE

The Government will evaluate the Experience Evaluation Documents that were found acceptable submissions for Go/No Go Factor One (Experience) by contacting the references to assess the Contractor’s past performance and completing Section B of each Experience Evaluation Document. As shown in said Section B, the ratings available are Highly Satisfactory, Satisfactory, Unsatisfactory, and Neutral. The ratings assigned will be based on the average score of all ratings provided by references and comparable ratings for other past performance information collected by the Government (such as information collected from the Contract Performance Assessment Reporting System (CPARS)). Offerors that have no record of relevant past performance or for whom information on past performance is not available will be rated with the rating “Neutral”.

The Government reserves the right to (1) not contact all references (Past Performance Documents for references not contacted will not be rated negatively), (2) contact an Offeror for a secondary reference should the Government not be able to reach the first reference (this will constitute a clarification and not discussions), and (3) utilize past performance information other than the information submitted with the proposal received in conducting the evaluation.

5.5 FACTOR FOUR – PRICE

Offerors Excluded from Evaluation of Factor Four, Price Offerors that are rated “Unacceptable” for Factors One, Two, or Three will not be evaluated for Factor Four, Price.

Task Order 0001 Price The values in the “Total” column (column J) of the worksheet entitled “Task Order 0001 – ITA” from Attachment 4 will be subtotaled to create a Task Order 0001 Price. Note: This worksheet includes an automatic calculation to include the cost of a six-month option extension under FAR clause 52.217-8.

Task Order 0002 Price The values in the “Total” column (column J) of the worksheet entitled “Task Order 0002 – ESB” from Attachment 4 will be subtotaled to create a Task Order 0002 Price. Note: This worksheet includes an automatic calculation to include the cost of a six-month option extension under FAR clause 52.217-8.

ID/IQ Contract Total Price This price is the combined price of Task Order 0001 Price and Task Order 0002 Price.

Price Analysis The Government will conduct price analysis, as defined in FAR 15.404 (b), on the Task Order 0001 Price and the Task Order 0002 Price to determine whether the prices are reasonable and balanced. In order to be eligible for award, Offerors’ Task Order 0001 and 0002 pricing must be determined fair and reasonable and pricing that is determined unbalanced must not pose an unacceptable risk to the Government.

The labor rates proposed for the ID/IQ contract for Years 1, 2, and through 3 shall be equal to the labor rates proposed for Task Orders 0001 and 0002 for the same labor categories and time period.