HC1047-12-R-4013-0001.pdf
PDF 135 KB Posted
- Attached to
- Defense Information Systems Agency Information Technology Enterprise Support Services (DESS) Federal contract opportunity
- Solicitation number
- HC1047-12-R-4013
- Issued by
- Defense Information Systems Agency
About this file
RFP Amendment 0001 The purpose of this RFP Amendment is to A. Clarify language in Section L.7 regarding the purpose intent and registration process of the Pre-Proposal Site Visit. (NOTE Section L.7 has been replaced in its' entirety. No revisions have been made to any other sections of the RFP as a result of this amendment.) B. Extend the submission date for clearance requests for the Pre-Proposal Site Visit f rom 10 May 12 to 14 May 12. at 11 59AM EDT.
View the file
Other files for this federal contract opportunity
Show all 50
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA
FAR (48 CFR) 53.243
The purpose of this RFP Amendment is to:
A. Clarify language in Section L.7 regarding the purpose, intent and registration process of the Pre-Proposal Site Visit. (NOTE: Section L.7 has been replaced in its' entirety. No revisions have been made to any other sections of the RFP as a result of this amendment.)
B. Extend the submission date for clearance requests for the Pre-Proposal Site Visit from 10 May 12 to 14 May 12. at 11:59AM EDT.
1. CONTRACT ID CODE PAGE OF PAGES
S 1 16
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 10-May-2012
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HC1047-12-R-4013
X 9B. DATED (SEE ITEM 11)
03-May-2012
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
10-May-2012
CODE
DISA/CONTRACTS-NCR
P.O. BOX 549
FT. MEADE MD 20755
HC1047 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
HC1047-12-R-4013
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
SECTION L
SECTION L - INSTRUCTIONS TO OFFERORS
L.1. PROGRAM STRUCTURE AND OBJECTIVES. The Defense Information Systems Agency (DISA) requires DISA Information Technology Enterprise Support Services (DESS) to provide the full range of mission support capabilities that are needed by the Chief Information Officer (CIO) to operate, maintain, and modernize the DISA global IT enterprise. Contractor support personnel are required to operate, maintain and modernize the DISA infrastructure and IT services into a world-class family of leading edge capabilities that are positioned to enable DISA’s warfighting support mission in the dynamic and thread-intensive environment of 21st century cyberspace.
These needs require the Agency to acquire a new level of highly qualified and technically superior IT support in a manner that is compliant with leading industry standard such as ITIL, eTOM, CMMI, HDI and COBIT and International Standards organization (ISO), and Institute of Electrical and Electronics Engineers IEEE standards.
L.2. NOTIFICATION OF USE OF NON-GOVERNMENT EVALUATORS.
L.2.1. Offerors are advised that the following contractors may participate as non-Government advisors in the evaluation of proposals:
Kepler Research 13663 Office Place, Suite 202 Woodbridge, VA 22192
MITRE
7525 Colshire Drive McLean, VA 22102
Decision Point source selection software developed by ManTech will be used during the proposal evaluation process.
ManTech International Corporation (Corp HQ) 12015 Lee Jackson Highway Fairfax, VA 22033
L.2.2. The above listed non-Government advisors will be authorized access to only those portions of the proposal data and discussion items that are necessary to enable them to provide specific advice on specialized matters or on particular problems. The non-Government advisors will not be allowed to determine strengths and weaknesses, establish initial or final assessments of risks, or actually rate or rank Offeror’s proposals. The non-Government advisors will be required to sign non-disclosure/conflict of interest documents prior to carrying out their responsibilities. Offeror's objection to the disclosure of information to these non-Government advisors shall be provided in writing to the Contracting Officer before the date set for receipt of proposals. The written objection shall include a detailed statement for the basis of the objection.
L.3. GENERAL INSTRUCTIONS.
L.3.1. This section of the Information to Offerors provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS) and Contract deliverables.
L.3.2. The Government reserves the right to reject any proposal that does not substantially comply with these proposal preparation instructions.
L.3.3. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the Offeror's proposal.
L.3.4. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.
L.3.5. The proposal acceptance period is specified in Section A of the solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.
L.3.6. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.
L.4. GENERAL INFORMATION.
L.4.1. Point of Contact. The Contracting Officer (KO) and Contract Specialist (CS) are the sole point(s) of contact for this procurement. Address any questions or concerns you may have to the KO and CS. Written requests for clarification must be sent to the (KO) Edward “Shannon” Frank, Edward.Frank@disa.mil, Primary Contract Specialist (CS) Christopher Gray, Christopher.Gray@disa.mil, and Alternate Contract Specialist Marianne Call, Marianne.Call@disa.mil. Oral communications are not permissible.
L.4.2. Competitive Range Determination. Careful consideration shall be given to the overall standing of all Offerors based on the initial evaluation. Only those Offerors who have submitted the most highly rated proposals shall be included in the competitive range. However, in accordance with FAR Part 15.306(c)(2), Offerors are advised that the competitive range may be further reduced for purposes of efficiency. The Government reserves the right to make award without discussions or establishment of a competitive range.
L.4.3. Debriefings. The KO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The KO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.
L.4.4. Discrepancies. If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the KO, in writing, with supporting rationale as well as the remedies the offeror is asking the KO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion and/or clarifications. This reservation includes matters of additional or substitute pages of the initial proposal.
L.4.5. Electronic Reference Documents. All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.
L.4.6. Communications. Exchanges of source selection information between Government and Offerors will be controlled by the KO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.
Otherwise, source selection information will be transmitted via the U.S. Postal Service or other carrier (e.g., FedEx, UPS, etc) and mailed to the following address:
Defense Information Systems Agency Procurement Directorate (DITCO-NCR) Attn: Mr. Edward S. Frank Contacting Officer, PL62 P.O. Box 549 Ft. George G. Meade, MD 20755-0549 Reference: RFP HC1047-12-R-4013
L.5. ORGANIZATION / FORMAT / NUMBER OF COPIES / PAGE LIMITATIONS.
L.5.1. The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in Section L, Paragraph L.6 - Instructions for Preparation Of Proposal Content as noted in the table below.
Table 5.1. Proposal Organization
VOLUME RFP PARA # VOLUME TITLE PAGE LIMIT
NO. OF
HARD
COPIES
NO. OF
CD-
ROMs
I Executive Summary 10 2
Part A L.6.1.1 Narrative Summary 5 pages
Part B L.6.1.2 Master Table of
Contents No Limit
Part C L.6.1.3 Glossary / Acronym
List No Limit
II
Factor 1 -
Technical/
Management
4 2
Part A L.6.2.2.4 Compliance and Cross Reference
Matrix No Limit
Part B L.6.2.2.5 Subfactor 1 – Management Capabilities
Overall Page Limit for Entire
Technical/
Management
Volume is 85 pages.
Allocation of Pages Per
Subfactor is at the Offeror’s Discretion.
Part C
L.6.2.2.6
Subfactor 2 - Operations Task
Order
Overall Page Limit for Entire
Technical/
Management Volume is 85 pages.
Allocation of
Pages Per Subfactor is at the Offeror’s
Part D L.6.2.2.7 Subfactor 3 – Sample
Task Orders
Overall Page Limit for Entire
Technical/
Management
Volume is 85 pages.
Allocation of Pages Subfactor is at the Offeror’s
III
Factor 2 - Past
Performance 3 2
Part A L.6.3.2.a Summary Page 5
Part B L.6.3.2.b Consent Letters
1 page for each subcontractor, teaming partner, and/or joint venture partner
Part C L.6.3.2.c Client Authorization
Letter
1 page for each commercial contract reference
Part D L.6.3.2.d Past Performance
Information Sheets 3 Pages, for each reference
Part E L.6.3.2.e Organizational
Structure Change History
4 pages
L.5.2. Page Limitations. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Each page shall be counted as one page except for title/cover pages, acronym lists, table of contents, glossaries, resumes, and blank pages, which shall not count against the page limitations.
L.5.3. Page Size and Format.
L.5.3.1. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts.
Pages shall be single spaced with 1.5 line spacing. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.
L.5.3.2. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page.
Foldout pages may only be used 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. These limitations shall apply to both electronic and hard copy proposals.
L.5.3.3. Binding and Labeling. Each volume of the hard copy proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror's name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.
L.5.3.4. Indexing. Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.
L.5.3.5. Glossary of Abbreviations and Acronyms. Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries of Abbreviations and Acronyms do not count against the page limitations for their respective volumes.
L.5.3.6. Cross-Referencing.
L.5.3.6.1. To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.
L.5.3.6.2. The Offeror shall provide a cross-reference matrix indicating/linking by Government Document Name (RFP, PWS, etc.) and by specification page/paragraph number, with the corresponding proposal paragraph in that section which addresses the referenced item.
L.5.3.7. Electronic Offers.
L.5.3.7.1. The Offeror shall submit Volumes I through V in electronic format, using recordable CDs. For electronic copies, indicate on each CD the volume number and title. The content and page size of electronic copies must be identical to the hard copies. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. Each volume shall be in a different directory on a CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office (save file as Word 97-2003 Document), MS Office Excel save file as Excel 97-2003 Workbook), MS Office Project (save as Project Standard 2003), and MS Office Power Point (save as PowerPoint 97-2003 Presentation), as applicable. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the soft copies will be used for evaluation.
L.5.3.7.2. Use of the software and procedures described in this section will reduce the amount of time and effort needed by the Government to receive and install proposals into an electronic evaluation system and will help to ensure that proposals are suitable for reading electronically. Information regarding electronic products listed herein should not be construed as Government endorsement for such products.
L.5.3.7.3. Efforts by the Government to clarify or expedite installation of electronic proposal submissions, in accordance with FAR 15.207(c), will not be considered discussions.
L.5.3.8. Source Selection Tool. The Government will access the softcopy versions of the Offeror’s proposal using the DecisionPoint™ source selection tool provided by AcqCenter.com (http://www.acqcenter.com). An electronic submission which cannot be accessible from Decision Point will not be considered.
L.5.3.9. Cost and Pricing Information. No cost or pricing information of any kind shall be included in any volume except Volume IV, Cost/Price Proposal.
L.5.3.10. Proposal Submission. Proposals shall be hand-delivered or transmitted via the U.S. Postal Service or other carrier (e.g., FedEx, UPS, etc) and mailed to the following address by the date/time specified in Section A of the solicitation. The Government reserves the right to not consider late offers. The Offeror bears all responsibility for submitting their offer by the specified date/time.
Defense Information Systems Agency Procurement Directorate (DITCO-NCR) Attn: Mr. Edward S. Frank Contacting Officer, PL62 P.O. Box 549 Ft. George G. Meade, MD 20755-0549 Reference: RFP HC1047-12-R-4013
L.6. INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT.
L.6.1. Volume I - Executive Summary. In the Executive Summary, the offeror shall provide the following information:
L.6.1.1. Narrative Summary. The Narrative Summary shall explain and provide the offeror’s overall approach and supporting rationale for operating and managing the DISA Information Technology Enterprise Support Services (DESS) requirement; to include addressing significant risks and highlighting any key or unique features, excluding cost/price. Define direct lines of control, responsibility, functional relationships, and authority among the organizational elements, including proposed teaming partners/subcontractors, joint ventures and/or significant subcontractors arrangements.
The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.
L.6.1.2. Table of Contents. Include a master table of contents of the entire proposal. (This allows evaluators to readily locate proposal material that may be germane to their particular evaluation portion but is not included in the proposal volume with which they are primarily involved.)
L.6.1.3. Glossary / Acronym List. Include a master glossary / acronym list defining all acronyms utilized throughout the proposal.
L.6.2. Volume II – Technical / Management Volume. Offerors shall submit their Technical/Management Approach as Volume II of the written proposal. The Technical/Management Proposal shall not include price information, classified information, or "For Official Use Only" information.
L.6.2.1. General. The Technical / Management Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the technical/management subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.
L.6.2.2. Format and Specific Content.
L.6.2.2.1. Technical/Management. In the Technical/Management volume, address your proposed approach to meeting or exceeding the minimum performance or capability requirements of each technical/ management subfactor.
L.6.2.2.2. Technical/Management Risk. Address technical / management risks for each Technical/Management subfactor by identifying those aspects of the proposal you consider to have the potential for disruption of schedule, increased cost, poor performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract performance. Classify each risk in accordance with Section M, Paragraph M.3.2 entitled “Factor 1 – Technical / Management Risk” and subparagraphs thereto. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of the contract requirements. Propose a realistic "work-around" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level.
Identify and classify any new risks introduced by such risk mitigation.
L.6.2.2.3. Volume II Organization – Technical / Management. (Evaluation Factor 1). The Technical / Management volume shall be organized according to the following general outline:
a) Part A – Compliance and Cross Reference Matrix
b) Part B – Subfactor One – Management Capabilities
c) Part C – Subfactor Two – Operations Task Order
d) Part D – Subfactor Three - Sample Task Orders (6 total) L.6.2.2.4. Compliance and Cross Reference Matrix. The offeror shall fill out the Compliance and Cross Reference Matrix (see Section L, Attachment 1 herein) indicating the proposal reference information as it relates to the PWS, CLIN numbers, Sections L and M, Deliverables, QASP, and the corresponding paragraph in the technical volume which addresses the referenced item. If this matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over this matrix. In addition, to the extent this matrix discloses details as to the extent or manner by which the Government intends to evaluate offerors’ proposals for award, Section M references in the matrix are for information purposes only and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of the Section M of the solicitation.
L.6.2.2.5. Subfactor One – Management Capabilities.
The offeror’s management capabilities solution/approach shall demonstrate the a clear and comprehensive methodology for creating and maintaining a performance-based environment for the dynamic DESS environment from the perspective of corporate, contract, and task order levels to include any management challenges unique to DESS.
The Program Management Plan shall include a detailed description of how the contractor intends perform the tasks identified in this Performance Work Statement throughout the lifecycle of the contract. It shall also include a plan for continuation of essential contractors services as required by DFARS clause 252.237- 7024 (Oct 2010).
The CONOPS shall include a detailed description of how the contractor intends to manage its professional relationship with the Government throughout the lifecycle of the contract.
L.6.2.2.6. Subfactor Two – Operations Task Order The offeror’s proposal for the Operations Task Order shall include methodology, processes and procedures the offeror will use to position the DISA CIO to achieve certification in the implementation of Industry- Proven-Best-Practices. The offeror’s proposal shall demonstrate the offeror’s technical approach to achieve the requirements, responsiveness, minimization of the risk of specific solutions, understanding of the requirements, and use of systematic processes and procedures. Industry-Proven-Best-Practices include, but are not limited to: HDI, ITIL v3, eTOM, CMMI, and COBIT.
The offeror’s proposal shall provide and incorporate the support that meets or exceeds the performance standards set forth in the Service Level Agreements. The offeror shall include an estimate of the personnel hours, by labor category and level, required for each task within the Task Order.
The offeror’s proposal shall include a Transition Plan that includes a detailed description of the contractor's plan to execute the transition of the task identified in the Task Order from the incumbent contractor. The transition plan shall display a methodology to transition this workload within 60 days of task order award.
[Note: This task order will be awarded with the award of the basic IDIQ contract(s).]
(Note: A price proposal is not to be submitted as part of Volume II – Technical/ Management. The offeror’s price proposal shall be submitted as part of Volume IV-Cost/Price Proposal as discussed in paragraph L.6.4.)
L.6.2.2.7. Subfactor Three – Sample Task Orders (6 total) The Sample Task Orders will not be awarded with the contract, but represent work currently being done within the DISA CIO. It is anticipated that this work may be awarded during the contract period of performance.
For each sample task order, the offeror’s proposal shall include methodology, processes and procedures the offeror will use to position the DISA CIO to achieve certification in the implementation of Industry- Proven-Best-Practices. The offeror’s proposal shall demonstrate the offeror’s technical approach to achieve the requirements, responsiveness, minimization of the risk of specific solutions, understanding of the requirements, and use of systematic processes and procedures. Industry-Proven-Best-Practices include, but are not limited to: HDI, ITIL v3, eTOM, CMMI, and COBIT.
The offeror’s proposal shall provide and incorporate the support that meets or exceeds the performance standards set forth in the Service Level Agreements. The offeror shall include an estimate of the personnel hours, by labor category and level, required for each task within the individual Task Orders.
(Note: A price proposal is not to be submitted as part of Volume II – Technical/ Management. The offeror’s price proposal shall be submitted as part of Volume IV-Cost/Price Proposal as discussed in paragraph L.6.4.)
L.6.3. Volume III - Past Performance.
L.6.3.1. General. Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained herein as an Attachment to this RFP. This information is required on the offeror and all subcontractors, teaming partners/subcontractors, and/or joint venture partners who are proposed to perform 20% percent or more of the proposed effort based on the total proposed price (or cost, as applicable) or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.
Along with the information required in this paragraph, the offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the offeror's performance.
L.6.3.2. Format and Specific Content. The Past Performance volume shall be organized according to the following general outline:
a) Part A – Summary Page describing the role of the offeror and each teaming partner, joint venture partner, and/or significant subcontractor that the offeror is required to provide Past Performance Information Sheets (Ref: RFP, Section J, Attachment herein).
b) Part B – Subcontractor/Teaming Partner Consent Letters executed by each teaming partner, joint venture partner and/or significant subcontractor authorizing the release of past performance information so the offeror can respond to such information. A sample consent letter is provided as a Section J, Attachment herein.
c) Part C – Client Authorization Letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the offeror’s performance. Refer to the RFP Section J, Attachment herein.
d) Part D – Past Performance Information Sheets (Ref: RFP, Section J, Attachment herein)
e) Part E – Organizational Structure Change History (Ref: RFP Section entitled Organizational Structure
Change History.), if applicable.
L.6.3.3. Recent and Relevant Contracts. Submit information in accordance with the RFP Past Performance Attachment herein. The information submitted shall reference the Offeror's past performance and the past performance of the Offeror's teaming partners/subcontractors, joint venture partners, and/or significant subcontractors.
Submit Past Performance Information on no more than three (3) recent contracts that the prime offeror considers most relevant in demonstrating the prime’s ability to perform the proposed effort. Also include information on up to two (2) recent contracts performed by each of your significant teaming partners/subcontractors and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. The Government considers a significant subcontractor and/or teaming partner to be a company who provides 20% or more of the support required, and/or a company who provides a critical portion of the effort required and/or influences the results of performance.
Recency is defined as an effort that is ongoing or has been performed during the past three (3) years from the date of issuance of this solicitation, or for ongoing efforts, must have been in place at least six (6) months before the proposal due date.
For all Past Performance Information submitted, include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevancy, see Section M.4, and subparagraphs, thereto.
L.6.3.3.1. Specific Content. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is requested. Categorize the relevant information into the specific technical/management subfactors (if used) and cost/price factor used to evaluate the proposal.
L.6.3.4. Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this procurement. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/confidence assessment.
Since the Government intends to consider past performance information provided by other sources as well as that provided by the offerors, your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.
L.6.3.5. Questionnaires. The offeror shall provide the Past Performance Questionnaire and Cover Letter, found at RFP, Section J, Attachment herein, to each of the customer Points of Contact identified for each of the relevant past performance efforts. In order to expedite the assessment process, the Offeror may complete Sections 1, 2, and 3 of the Past Performance Questionnaire for the convenience of the POC. The Offeror shall not, however, complete any other section of the Past Performance Questionnaire. Once the questionnaires are completed by the POCs, the information contained therein shall be considered Source Selection Information in accordance with FAR 2.101 and
3.104 and shall not be released to the Offeror. Early submission of the Past Performance Questionnaires is encouraged. Questionnaires shall be sent directly via email to the KO, Edward S. Frank, Edward.Frank@disa.mil, the Primary CS, Christopher Gray, Christopher.Gray@disa.mil, and the Alternate CS, Marianne Call, Marianne.Call@disa.mil no later than the proposal due date. Past Performance Questionnaires submitted for an Offeror’s significant teaming partners/subcontractors and significant subcontractors shall clearly indicate the name of the Offeror within the questionnaire.
L.6.4. Volume IV – Cost / Price.
L.6.4.1. General Instructions.
L.6.4.1.1. Cost/Price Reasonableness and Realism. This section is to assist you in submitting information other than cost or pricing data that is required to evaluate your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an Offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed costs / prices rests with the Offeror.
L.6.4.1.2. Estimating Techniques and Methods. When responding to the Cost / Price Volume requirements in the solicitation, the Offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships, commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the WBS.
L.6.4.1.3. Cost / Price Information. Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost / price position. All information relating to the proposed cost/price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost / Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.
L.6.4.1.4. Cost or Pricing Information Requirements. IAW FAR 15.403-5(b)(1),(2), and (3), the Offeror's format for submitting such information should be used unless the contracting officer decides that use of a specific format is essential and the format has been described in the solicitation.
In accordance with FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price (or cost, as applicable) reasonableness. Information shall be provided in accordance with FAR 15.403-5 (except where tailored formats are specified hereunder--see paragraph 6.4.2 below). If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit cost or pricing data.
L.6.4.1.5. The Offeror shall comply with instructions contained herein for development of its cost / price proposal. The Offeror is required to submit all pricing data for all task orders provided as attachments in Section J.
L.6.4.2. Volume Organization. The Cost/Price volume shall consist of the following sections:
a) Part A – Introduction
b) Part B – Microsoft Excel Spreadsheets
c) Part C – Table of Labor Categories and Rates
d) Part D – Other Information
e) Part E – Reserved for Final Proposal Revisions (if requested by the contracting officer)
L.6.4.2.1. Part A – Introduction. Include table of contents; glossary of abbreviations and acronyms; summary descriptions of accounting, estimating, and purchasing systems; and changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure.
L.6.4.2.1.1. Glossary of Abbreviations and Acronyms. If necessary, provide a glossary of abbreviations and acronyms used with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.
L.6.4.2.1.2. Accounting System. Cost Reimbursable Task Orders may be issued after contract award. A DESS Contractor may not receive a cost reimbursable Task Order when the Accounting System has not been determined acceptable. Indicate whether the Government has determined your Accounting System to be adequate and acceptable for use in Cost Reimbursement contracts and, if so, provide evidence. The offeror must provide a plan for obtaining government acceptance of the Accounting System when the offeror’s Accounting System has not been accepted by the Government. Also, identify any deviations from your standard procedures in preparing this proposal.
L.6.4.2.1.3. Estimating System. Provide a summary description of your standard estimating system or methods for the CPFF CLINs. Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether the Government has determined your Estimating System to be adequate and acceptable for use in Cost Reimbursement contracts and, if so, provide evidence. The offeror must provide a plan for obtaining government acceptance of the Estimating System when the offeror’s Estimating System has not been accepted by the Government. Indicate whether you have Government approval of your system and, if so, provide evidence of such approval.
L.6.4.2.1.4. Purchasing System. Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Indicate whether the Government has determined your Purchasing System to be adequate and acceptable for use in Cost Reimbursement contracts and, if so, provide evidence. The offeror must provide a plan for obtaining government acceptance of the Purchasing System when the offeror’s Purchasing System has not been accepted by the Government. Also, identify any deviations from your standard procedures in preparing this proposal.
L.6.4.2.1.5. Cost Accounting Standards (CAS) Disclosure Statement. The offeror shall provide current status of its Cost Accounting Standards (CAS) Disclosure Statement and explain any inadequacies or non-compliances.
L.6.4.2.2. Part B – Microsoft Excel Spreadsheets. The cost proposal shall be submitted using Microsoft Excel and shall include all formulas and calculations.
L.6.4.2.2.1. Summary Spreadsheet. The offeror shall complete Section J - Attachment 14a containing a summary spreadsheet of the task order proposals. The summary spreadsheet shall include the total proposed cost / price for each task order, as well as the proposed aggregate total for all task orders. The summary spreadsheet should include all calculations/formulas used to develop final cost / price.
L.6.4.2.2.2. Individual Task Order Spreadsheets.
L.6.4.2.2.2.1. The Offeror shall propose the appropriate cost/prices (FFP, CPFF, T&M, etc.) for each of the requirements reflected in each of the task orders provided in Section J, Attachment(s) herein.
L.6.4.2.2.2.2. The Offeror’s proposal for each of the task orders shall include detailed cost/price amounts of all resources required to accomplish the task, (i.e. labor categories, labor hours, number of employees for each labor category, rates, On-Site and Off-Site, travel, incidental equipment, etc.).
Labor and overhead rates should include sufficient detail to sustain a DCAA audit (e.g. Direct Labor
Rates, Overhead, Fringe Benefits, G&A, and Fee, etc.). All travel must show the specific detail, if known (i.e., number of days, locations, number of personnel, etc.) and must include all detailed calculations. All ODC’s shall annotate the specific detail (qty, part number, manufacturer, etc.) to include supporting documentation to justify the cost (i.e., vendor quotes, price history, etc.). Costs shall be reimbursed at cost plus applicable indirect costs. If a subcontractor relationship exists, the subcontractor must break out their costs, in accordance with the above requirements. If needed, the subcontractor may submit their cost breakout directly to the Contracting Officer. All travel shall be authorized by the Contracting Officer’s Representative (COR) or Task Order COR (TO/COR), in writing, prior to performance and will be paid IAW FAR Part 31.205-46 and Section H.8. The contractor will be authorized to invoice monthly for all incurred travel costs approved by the COR or
TO/COR.
L.6.4.2.2.2.3. The Offeror is permitted to propose discounted labor rates that are lower than those established in Section J - Attachment 14b for the Operations Task Order provided in Section J Attachment 1. No discounts will be considered for the Sample Task Orders. The offeror shall fully explain the basis for proposing lower rates. The reduced labor rates will apply only to the respective task order and will not change the fixed rates in Section J - Attachment 14b rate table (which will be incorporated into the resultant contract award).
L.6.4.2.2.2.4. The Offeror’s proposed cost / price for each task order shall reflect the entire period of performance (base year and each option period to include the Option to Extend Services under FAR 52.217-8) as specified in the attached task orders.
L.6.4.2.2.2.5. Rounding. All costs or prices provided shall be rounded to the nearest dollar.
L.6.4.2.2.2.6. Percentages. Percentages should be limited to four decimal points; for example
25.15 percent shall be reflected as .2515.
L.6.4.2.2.2.7. Additional Criteria. All proposal amounts shall be proposed in U.S. currency.
L.6.4.2.3. Part C – Table of Labor Categories and Labor Rates. Offerors shall complete Section J - Attachment 14b to include a table reflecting Contractor proposed Labor Categories that are cross-mapped to the Government provided Labor Categories and descriptions and applicable Labor Rates used in the development of the task order proposals. A separate table shall be prepared for each period of performance (i.e., Months 1-12, 13-24, etc.). The complete Table of Labor Categories and Labor Rates shall be incorporated into the resultant contract as an attachment to Section B and will become the basis for determining price reasonableness in subsequent task order requirements. Descriptions of the labor categories are provided as Section J - Attachment
15. Failure to provide Contractor-proposed prices for all labor categories for all years (to include the Option to Extend Services under FAR 52.217-8) for work performed on Government Site and work performed at the Contractor Site may result in a rejection of the offeror’s proposal.
L.6.4.2.4. Part D – Other Information.
L.6.4.2.4.1. DCAA and DCMA Point of Contact Information. The offeror and all of its subcontractors/teaming partners should submit the name, address, Field Audit Office (FAO) number, and phone number of its cognizant Defense Contract Audit Agency (DCAA) and Defense Contract Management Agency (DCMA) office. If your rates are based on a formal budgetary forecast, please provide effective date(s). State if they have been provided to the cognizant ACO/DCAA office for review or negotiation; if not, please explain. Offeror’s submitting a proposal for a Cost-Reimbursable task order (or a task order with Cost-Reimbursable labor CLINs) must possess a DCAA-certified Cost Accounting System in order to be considered a responsible contractor and thus be eligible for award.
L.6.4.2.4.2. Assumptions / Exceptions to the Solicitation Requirements. Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award.
L.6.4.2.5. Part E - Final Proposal Revision (FPR). This part will apply only if the contracting officer requests a Final Proposal Revision. It is not necessary to provide the same level of detail in the final cost revision proposal as provided in the original cost proposal. However, all cost changes in the final cost revision proposal must be fully substantiated and explained. Provide a SUMMARY SCHEDULE OF CHANGES (Was-Is). This shall reflect all significant cost changes by major cost by period, i.e. basic and options. Identify the significant cost increases as well as the significant cost decreases. Explain the reasons for the cost changes consistent with changes to technical / management approach, and provide appropriate rationale so that an explanation can be provided to the SSA.
L.6.5. Volume V - Contract Documentation. The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the Model Contract, and Sections A through K. This includes:
L.6.5.1. Part A – Transmittal Letter and Solicitation/Contract Form (SF33). Completion of blocks 13 and 14, and signature and date for blocks 15a, 15b, and 15c of the Standard Form (SF33). Signature by the offeror on the SF33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.
L.6.5.2. Part B – Contract Information. Offeror’s shall complete all “fill-in” data within the following sections.
L.6.5.1.2.1. Contract Administrative Data (Section G).
L.6.5.1.2.2. Special Contract Requirements (Section H).
L.6.5.1.2.3. OCI Plan, see Section H.4. The offeror shall provide an OCI plan that identifies any potential or actual Organizational and Consultant Conflicts of Interest (OCCI) as…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .