273FCC20R0002 - App Dev - Instructions to Offerors_FINAL.docx

RFP 273FCC20R0002

Application Development - IDIQ

Federal Communications Commission

Application Development Support Services Indefinite Delivery Indefinite Quantity (IDIQ)

Instructions to Offerors

273FCC20R0002

May 21, 2020

Prepared By:

The Federal Communications Commission (FCC) Information Technology Center (ITC) 445 12th Street SW

Washington, DC 20554

L. 1 INSTRUCTIONS TO OFFERORS

The Federal Communications Commission (FCC) contemplates placing a multiple award Indefinite Delivery Indefinite Quantity (IDIQ) from this Request for Proposal (RFP). The RFP is being solicited as a full and open competition for the Application Development Support Service (ADSS). The effort is to provide: Program and Project Management Support, Software and Application Development and Document Support, and Extreme Programming.

Proposals shall comply with the format, composition, and content instructions set forth below. Proposals shall include details sufficient for FCC to be able to evaluate and confirm the validity of the Offeror’s stated claims.

Proposals shall not simply rephrase or restate FCC’s requirements, but, rather, provide a convincing rationale to address how the Offeror intends to meet the FCC’s requirements.

Offerors should assume the Government has no prior knowledge of its capabilities, education or experience.

The electronic version of this RFP is the official version for this acquisition. No hard copy of the RFP will be issued.

The primary point of contact for this acquisition is the Contracting Officer (CO), Joyce Terry-Butler. All correspondence with the CO shall be sent electronically to: Joyce.Terry-Butler@fcc.gov.

Offerors intending to submit a proposal shall not contact Government personnel regarding this solicitation other than the CO. Offerors are also requested to advise potential subcontractors of this instruction. Information received from sources other than the CO may not be authentic or reliable. Government confidential information received or used by an Offeror may be prejudicial to other competing Offerors. An offeror receiving, using, or relying on such information shall be excluded from the competition and may be subject to other adverse action permitted or required by law.

L.2 GENERAL INSTRUCTIONS

The Government will not be obligated to pay any costs incurred by the Offeror in the preparation and submission of a proposal in response to this RFP.

Offerors must include in their proposal all information requested by this RFP and must submit their proposal in accordance with the instructions set forth in this solicitation. It is the Offeror’s responsibility to ensure the completeness of its proposal.

An Offeror’s proposal shall clearly address the requirements specified for Volume I: Technical and Volume II: Price.

The Government may reject a proposal if it fails to comply with the requirements set forth in Instructions to Offerors, especially if the CO determines that substantial revisions or supplementation of the proposal would be necessary to permit evaluation or if significant errors or omissions in the proposal appear to be due to a lack of diligence or competence of the Offeror.

The Government may evaluate proposals and award an IDIQ and subsequent task order(s) as submitted and without exchanges of any kind. Therefore, the Offeror’s proposal should contain the Offeror’s best terms from a technical and price standpoint. However, the Government may engage in clarifications with one or more Offerors or allow proposal revisions, or both.

· The Offeror shall use the PWS, the pricing sheet, this Instructions to Offerors, and other applicable portions of the RFP, as the basis to prepare the proposal.

· Proposals shall not simply rephrase or restate the requirements but should provide specific information regarding the offeror’s proposed approach to performing the identified tasks that fully demonstrates the offeror’s understanding of the goals and objectives of this effort.

· The proposal shall be specific and comprehensive. Clarity and coherence are very important.

· The Offeror shall avoid using vague or ambiguous words or phrases (e.g., as necessary, periodically, and as required).

· The Offeror shall not include any price/price information in the technical proposal volume.

· The Offeror’s responses to solicitation technical requirements shall correspond to the sections identified in the PWS.

L. 2.1 QUESTIONS

All questions shall be submitted via email to the CO at Joyce.Terry-Butler@fcc.gov using the Offeror Question Template (see Attachment C of the RFP). The subject line must read: “273FCC20R0002 – Offeror Questions. Any question(s) received by phone regarding the RFP will not be answered.

Each question should be numbered and stated as clearly as possible. The cutoff date for questions is Tuesday, July 28, 2020 at 5:00pm Eastern Time (ET).

The Government is under no obligation to answer questions about the solicitation received after that cutoff date and time.

Responses to questions timely submitted will be posted on https://beta.sam.gov/ , with questions reproduced verbatim as received. Accordingly, Offerors should frame questions in a way so as to not reveal proposal strategies or proprietary or confidential information.

L.2.2 PROPOSAL DUE DATE

Proposals are due no later than Friday, August 14, 2020 at 5:00pm Eastern Time (ET).

L.2.3 PROPOSAL SUBMISSION

Proposals shall be submitted as described herein. Proposals submitted in response to this RFP shall be formatted as stated below and furnished electronically to: Joyce.Terry-Butler@fcc.gov.

Proposals shall be submitted in two (2) separate emails (Volume I Technical, Volume II Price) using “a zip file folder” with the RFP number, volume number (e.g. Volume I: Technical) and company’s name in the subject line.

Proposals submitted after the time and date specified for receipt will be considered LATE and will not be evaluated.

If the Offeror would like receipt confirmation of submitted proposals a delivery request and/or read receipt must be indicated within the tracking option of the Offerors email. The Government will not provide or send individual emails to the Offeror acknowledging receipt of proposals.

L.3 PROPOSAL DOCUMENTS

Document Format – Except for tables, charts, graphs, and figures, the minimum type size shall be 12-point Times New Roman standard font with single spacing. Typesetting, font compression, or other techniques to reduce character size or spacing are not permitted and are considered a deliberate attempt to circumvent the page limitations. Prohibited techniques include, but are not limited to, setting the paragraph line spacing, a feature of MS Word, “exactly at 12 point.” Pages shall be numbered sequentially by volume. No pen and ink changes are allowed. Legible tables, charts, graphs, and figures may be used, wherever practical, to depict organizations, systems, layout, and implementation schedules, etc. These displays shall not exceed 11 by 17 inches in size. Foldout pages may be used only for large tables, charts, graphs, diagrams and schematics; not for pages of text. For tables, charts, graphs, and figures, the text shall be no smaller than 10-point Times New Roman font.

The Offeror shall prepare the proposal as set forth below in Table 1: Proposal Organization.

A complete proposal shall consist of two (2) separate volumes as organized under Table 1 below. Each volume shall be limited to the maximum number of pages shown in the table.

Page counts do not apply to the cover page, table of contents, list of exhibits, glossaries (incl. terms, abbreviations, acronyms), and the pricing proposal.

The FCC will not require evaluators to search other proposal volumes or tabs for information that are not appropriately located under these instructions. If required information is not placed in the appropriate volume and tab, that information will be deemed “Unacceptable” and will not be considered. Therefore, Offerors shall ensure that each proposal volume is complete and submitted in accordance with the instructions herein.

Table 1: Proposal Organization

Tab 4 Past Performance Summary *Past Performance Questionnaires (Attachment D) will be submitted separately by references and are not included in this page count

Volume II - Price

This volume shall include:

1. Date proposal submitted

2. RFP Title and number

3. Offeror’s name

4. Offeror’s Address

5. Name(s) and telephone numbers of Offeror’s Point of Contact pertaining to the RFP

6. Offeror’s Cage Code, Taxpayer Identification Number (TIN) and Data Universal Numbering System (DUNS) Number

7. Statement that the Offeror’s SAM registration is current

8. Socio Economic Designation (Prime and subcontractor)

9. The name, Cage Code, TIN and DUNS number of each proposed subcontractor (as applicable).

10. Statement that the proposal is valid for 180 business days from the date of submission

11. Statement of compliance indicating either complete compliance with the solicitation or a detailed description of any objections, exceptions, or contingencies to the terms of the solicitation.

L.3.2 TAB 1: TECHNICAL APPROACH

The Offeror shall provide a detailed discussion of its technical methodology for accomplishing the requirements of the contract, and ensuring task orders under the contract, including the planned sequence of steps to be taken, critical path, milestones, interface, integration, and provisions for continuity of operations in the case of emergency. The Offeror’s Technical approach shall:

· Be clear, logical, practical, efficient, and complete.

· Identify potential risks with the proposed approach as well as the means to mitigate them.

· Demonstrate a clear understanding of all RFP requirements and include evidence of specific methods and techniques for completing each discrete task and planned execution of the projects.

· Demonstrate how its proposed models/processes/tools are successful in gaining efficiencies and/or process improvements to include performance metrics/ measures.

L.3.3 TAB 2: MANAGEMENT APPROACH

The Offeror shall provide its proposed management approach to meet the Application Development requirements and objectives. The Offeror shall describe the processes and procedures it proposes to use to manage the multiple facets of this effort. The management approach shall include the following sections:

Corporate Experience.

Describe any corporate experience that relates to the level and complexity of work detailed in the PWS. This description may include:

· An explanation as to how the Offeror’s experience on similar past projects will enhance its ability to successfully perform the Application Development requirement(s).

Management Structure.

· Describe proposed organizational structure and staffing necessary to ensure successful accomplishment of the PWS requirements

· Identify team structures, relationships, roles and responsibilities

· Show lines of authority, to include teaming partners and subcontractors

· Identify key functions which are deemed critical to the successful management of the IDIQ and subsequent task orders. Identify whether the key function will be performed by the Offeror or a subcontract

· For each CLIN, the Offeror shall describe the proposed labor mix and level of effort upon which its proposed price is based (without including any pricing information).

Teaming Partners and Subcontractors.

· Describe qualifications of teaming partners and subcontractors

· Describe the process for management of teaming partners and subcontractor management. At a minimum, Offerors shall describe the assignment of responsibilities, division of work, and reporting procedures

· Describe the management approach and/or controls that will be implemented to ensure subcontractors perform seamlessly within the framework of the IDIQ objectives Management of Requirements.

· Describe the approach to identifying sufficient quantity of personnel needed and subsequent, recruiting, hiring, screening, and retaining of qualified personnel. At a minimum, Offerors shall describe the necessary skill type and qualifications needed to meet the objectives

· Describe the approach to rapidly and adequately respond to relevant, vastly evolving mission requirements

· Describe the approach to rapidly and adequately respond to no-notice/short-notice deployment requirements

· Describe the approach to respond to and integrate internally and externally driven mission-related requirements to include processes for managing subcontractor relationships

· The Offeror shall demonstrate its experience and capability to respond to multiple task orders under an IDIQ

L.3.4 TAB 3: KEY PERSONNEL - RESUMES

The Offeror shall provide resumes for all Key Personnel identified for Task Orders. Resumes shall be limited to three (3) pages per person and follow FCC’s type font and page instructions for the proposal. All resumes shall follow a consistent format and shall include, at a minimum: employment history; positions and responsibilities; and a summary of qualifications, education, specialized training, and professional certifications.

L.3.4.1 Organizational Conflict of Interest (OCI).

Describe procedures that the Offeror will employ to avoid and/or mitigate, existing or potential conflicts of interests of its personnel and those of any proposed subcontractors or consultants. If no OCI currently exists, include a statement that no OCI currently exists.

L.3.4.2 Staffing and Recruiting Approach The Offeror’s staffing plan shall describe the Offeror’s processes and procedures for identifying, recruiting, hiring, screening, and retaining sufficient numbers of qualified personnel to meet the Government’s performance objectives and task orders. The plan shall describe the techniques used to ensure efficient and effective use of personnel, as well as any training and/or certification programs the Offeror uses to maintain proficiency and verify qualifications.

The plan shall describe the relationship between the various management levels and the proposed labor categories for each task area. The plan shall describe the Offeror’s approach to addressing ramp-up (surge) and ramp-down (de-scope) requirements with short turn-around timelines.

The Offeror shall demonstrate its ability to obtain qualified personnel to meet the requirements of the solicitation and set forth how it will ensure that the FCC receives well-qualified staff that will continue to meet the needs of the FCC throughout the term of the IDIQ. The Offeror’s approach shall discuss how the knowledge, skills, experience, training, and capabilities of personnel relate to the PWS requirements.

Additionally, the Offeror shall provide draft Transition-In and Transition-Out Plans that describe the processes and procedures used to transition into and out of this IDIQ, including transition plans for each individual task order(s), within stated solicitation and PWS timeline objectives. The plan shall discuss the methodologies used for ensuring seamless Transition-In with the Government and Transition-Out between contracts and techniques used to ensure the cooperative transfer of task execution between Offerors. The plan shall address the Offerors’ approach to providing a fully capable and qualified team as part of the Transition-In requirements identified in the solicitation and PWS.

L.3.4.3 Other Certifications If the Offeror has certifications at the organizational level that demonstrate organization commitment and excellence through all elements of support required in this RFP, the Offeror may place documentation of such certifications under this tab.

L.3.5 TAB 4: PAST PERFORMANCE SUMMARY

The Past Performance Summary shall describe the Offeror’s recent (within the last 5 years) performance of contracts (both Government and nongovernment) that are relevant (in scope, complexity, and magnitude) to the PWS service areas and explain how such contracts are relevant to this Application Development requirement. If subcontractors are proposed, the Offeror may include the subcontractor’s relevant past performance, but at least two (2) past performance references and questionnaires must be from the Offeror serving as the Prime Contractor. The Offeror must state if the company does not have any past performance relevant to the requirements in the PWS.

L.3.5.1 Past Performance References The Offeror shall include three (3) past performance references that have been performed within the last five (5) years of the proposal submission due date (both Government and non-government), and are relevant (in scope, complexity, and magnitude) to the PWS service areas. “Relevant” contracts are defined as those contracts ongoing for at least two (2) years or either ongoing or completed within the last five (5) years that are similar in scope, magnitude, and complexity to the Application Development effort as described in the PWS and have an aggregate value equal to or greater than $10 million.

L.3.5.2 Project Description The Offeror shall describe the size, scope, and complexity of each project. The Offeror shall describe why the past experience project is relevant to the instant requirement (i.e., why it is a good subject for evaluation under the past experience factor).

The Offeror shall provide the following information regarding each past performance project:

· Project title

· Brief description of the project

· Company-specific role, responsibility, and deliverables

· Contract and, if applicable, order number

· Contract value

· Type of contract (FP, LH, etc.)

· Period of Performance

· Government Agency/Organization

· COR’s name, address, and phone number (or equivalent for a non-Government entity)

· Contracting Officer’s name, address, and phone number (or equivalent for a non-Government entity)

· Current status of project (e.g., completed or in progress) and the start and completion dates (or estimated completion date for current project)

· Relevance to the FCC’s requirement (where performance similarities make the project relevant, specifically identify by section those aspects of the PWS that are implicated)

· Problems encountered and the Offeror’s corrective actions (if applicable) L.3.5.3 Past Performance Questionnaire (PPQ) The Offeror shall provide a PPQ (see Attachment D– Past Performance Questionnaire in the RFP) to each customer/client references for each project presented in Volume II: Tab 4 - Past Performance.

The Offeror will provide its references with instructions to electronically complete and e-mail the entire form to the CO, Joyce Terry-Butler at Joyce.Terry-Butler@fcc.gov on or before August 13, 2020, 5:00pm EST.

The Offeror is responsible for ensuring that all past performance questionnaires are received by the CO on or before the due date and time for proposals. The form must be completed by the customer/client independently (without assistance of, or collaboration with, the Offeror). Once received, the Government will associate the completed PPQ with its related past performance project description.

If the Offeror is proposing to use one or more subcontractors, one of the past performance references may be for one of the subcontractors. If subcontractor past performance shall be used, the reference must be for the subcontractor that is proposed to perform the largest amount of work (measured in dollars). The Offeror shall provide its references with the PPQ template. Each completed reference shall not exceed the four (4) pages of the PPQ template.

The Offeror shall provide its price proposal as a separate file and labeled as: “273FCC20R0002 Volume II: Price Proposal – [company’s name]” As noted above, the Offeror’s price proposal shall be a separate volume from the other volume. The price proposal is to be submitted as a Firm Fixed Price (FFP) and Labor Hour (LH) proposal based on the CLIN structures. The Offeror shall include all information relating to the proposed prices, including all required supporting documentation, in Volume II: Price.

Under no circumstances shall price information and documentation be included in any other volume. If price information and documentation is included in any volume of the proposal beside Volume II it will not be considered. Volume II shall consist of:

L.4.2 Cover Page This volume shall include a Cover Page. The cover page must contain the following:

1. Date proposal submitted

2. RFP Title and number

3. Offeror’s name

4. Offeror’s Address

5. Name(s) and telephone numbers of Offeror’s Point of Contact pertaining to the RFP

6. Offeror’s Cage Code, Taxpayer Identification Number (TIN) and Data Universal Numbering System (DUNS) Number

7. Statement that the Offeror’s SAM registration is current

8. Socio Economic Designation (Prime and subcontractor)

9. The name, Cage Code, TIN and DUNS number of each proposed subcontractor (as applicable).

10. Statement that the proposal is valid for 180 business days from the date of submission

11. Statement of compliance indicating either complete compliance with the solicitation or a detailed analysis of any objections, exceptions, or contingencies to the terms of the solicitation.

L.4.3 Completed Pricing Sheet The Offeror shall complete Attachment A – Pricing Sheet –in the RFP. For each CLIN, Offerors must analyze the technical requirements of the PWS and provide a fixed labor hourly rate for each labor category (LCAT) identified in the “Labor Category” column in the Price Sheet – Detail worksheet.

Offerors shall propose fully burdened rates for all LCATs and services in the pricing sheets. These rates shall be the basis for all task orders.

Offerors shall submit their completed Master Pricing Table (MPT) in Microsoft Excel format in a softcopy version. The proposed price information shall be in unprotected spreadsheets that disclose the formulas that depict how the figures were computed.

Offers are solicited on an “all or none” basis and FAR 52.212-1, INSTRUCTIONS TO OFFERORS-COMMERCIAL ITEMS, paragraph (h) is hereby tailored.

Failure to complete all worksheets or to complete all required line items within a worksheet will result in the rejection of the offer.

L.4.4 Price Proposal Narrative The Offeror shall provide a summary of Volume II: Price. The summary is an overview of the pricing approach and strategy. The Offeror shall provide a description of each LCAT that it is proposing to use for this IDIQ. For each FFP CLIN, the Offeror shall explain how it generated its proposed FFP. The Offeror may also include a narrative explanation of any other aspect of its price proposal.

Key Ground Rules and Assumptions Offerors shall:

(1) Include a listing of all key ground rules and assumptions that have significant impacts on the proposed prices. This includes resources provided by the Government (i.e., Government-furnished equipment and property), key technical and management requirements driving cost, whether imposed by the Government or self-imposed by the Offeror (e.g., Security).

(2) Describe, in general terms, how each ground rule or assumption may impact the proposed price and identify those ground rules or assumptions that may increase the price. The ground rules and assumptions included in this section shall track to other sections of Volume II: Price as appropriate.

The Offeror submitting a proposal must expressly state whether it makes or takes assumptions, conditions, or exceptions respecting the terms, conditions, and requirements of this RFP, including the PWS.

No assumptions, conditions, or exceptions respecting the terms, conditions, or requirements of this RFP shall be stated anywhere in the Offeror’s price proposal outside of this section. If any are taken or made, Offerors shall clearly state each assumption, condition, or exception; identify the requirement; and cite the applicable solicitation paragraph and page number.

Additional Comments If there is any additional information that the Offeror feels is important for the Government to consider in the evaluation of the price proposal, other than the information specifically requested in the solicitation, the Offeror may bring such information to the attention of the Government by including it in this section of the proposal.

Due to the competitive nature of this procurement, and the fact that this is a commercial item procurement under FAR Part 12, the Government is not requesting submission of certified cost or pricing data under this solicitation in accordance with FAR 15.4. Only fully burdened labor rates and prices shall be proposed unless it is determined by the CO that adequate competition was not obtained. If adequate competition is not obtained or should a situation develop that the Government will require submission of additional pricing information other than certified cost or pricing data, Offeror shall be prepared to submit the additional pricing information within five (5) business days after receiving the request from the Government.

image1.jpg