Attach_3_-_Section_L_-_Amend_1.pdf
PDF 175 KB Posted
- Attached to
- Requirements Management System (RMS) Suite and Logistics Management Data Bank (LMDB) Programs Federal contract opportunity
- Solicitation number
- FA8770-16-R-0002
About this file
Instructions to Offerors (ITO)(Section L) dated 30 March 2016
View the file
Other files for this federal contract opportunity
Show all 32
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
RMS/LMDB FA8770-16-R-0002
Section L, Instructions to Offerors RFP Attachment 3
AIR FORCE LIFE CYCLE MANAGEMENT CENTER (AFLCMC)
AFLCMC/HIAR
WRIGHT PATTERSON AFB, OH 45433-5006
Section L
INSTRUCTIONS TO OFFERORS (ITO)
for
REQUIREMENTS MANAGEMENT SYSTEM
(RMS)
LOGISTICS MANAGEMENT DATA BANK
(LMDB)
Solicitation Number FA8770-16-R-0002 30 March 2016
Table of Contents
1. Program Information
Contracting Approach ..................................................................................................... 4 1.1.
Ombudsman .................................................................................................................... 4 1.2.
2. Guidance/Instructions Point of Contact .............................................................................................................. 5 2.1.
2.1.1. Debriefings
2.1.2. Discrepancies
2.1.3. Electronic Reference Documents
2.1.4. Communications
Organization, Number of Copies and Page Limits ......................................................... 6 2.2.
2.2.1. Page Size and Format, Page Limitation
2.2.2. Pricing Related Data
2.2.3. Classified Information
2.2.4. Cross-Referencing
2.2.5. Indexing
2.2.6. Glossary of Abbreviations and Acronyms
Electronic Offers (Proposal of Record used for Evaluation) .......................................... 8 2.3.
Hardcopy Offers.............................................................................................................. 8 2.4.
Distribution ..................................................................................................................... 9 2.5.
3. Volume I - Executive Summary Narrative Summary ......................................................................................................... 9 3.1.
Table of Contents ............................................................................................................ 9 3.2.
Letter of Transmittal or Executive Cover Letter ............................................................. 9 3.3.
Small Business Status Confirmation ............................................................................... 9 3.4.
4. Volume II - Technical Volume General ............................................................................................................................ 9 4.1.
Format and Specific Content ........................................................................................ 10 4.2.
4.2.1. Technical
4.2.1.1. Subfactor 1: Technical Program Management
4.2.1.2. Subfactor 2: Functional /System Engineering
4.2.1.3. Subfactor 3: Staffing Plan
5. Volume III - Price General Instructions ...................................................................................................... 11 5.1.
5.1.1 Format and Specific Content
Price Reasonableness .................................................................................................... 12 5.2.
5.2.1. Price Data
5.2.2. Cost or Pricing Data Requirements
5.2.3. Rounding
5.2.4. CLIN Structure
Other Information ......................................................................................................... 14 5.3.
6. Volume IV - Past Performance
Format and Specific Content ........................................................................................ 14 6.1.
Past Performance Information (PPI) Tool .................................................................... 15 6.2.
Consent/Authorization Letters ...................................................................................... 15 6.3.
Recent and Relevant Contracts ..................................................................................... 15 6.4.
6.4.1. Specific Content
6.4.2. Organizational Structure Change History
Quality and Satisfaction Rating for Contracts Completed in the Past Five Years........ 16 6.5.
Performance Surveys .................................................................................................... 16 6.6.
7. Volume V - Contract Documentation Model Contract ............................................................................................................. 17 7.1.
7.1.1. Section A - Solicitation/Contract Form
7.1.2. Section B - Supplies or Services and Price
7.1.3. Section F - Deliveries or Performance
7.1.4. Section G - Contract Administrative Data
7.1.5. Section H - Special Contract Requirements
7.1.6. Section I - Contract Clauses
7.1.7. Section J - Reserved
7.1.8. Section K - Representations, Certifications, and other Statements of Offerors
Sections L and M .......................................................................................................... 18 7.2.
Other Information Required .......................................................................................... 18 7.3.
7.3.1. Authorized Offeror Personnel
7.3.2. Government Offices
7.3.3. Company/Division Address, Identifying Codes, and Applicable Designations
Attachments to the Model Contract .............................................................................. 18 7.4.
7.4.1. Base Support Requirements
7.4.2. Associate Contractor Agreements
7.4.3. Limitations on Subcontracting
7.4.4. Additional Required Documents
Tables
Table 1 - Proposal Organization and Page Limits
1. Program Information The Requirements Management System (RMS) and Logistics Management Data Bank (LMDB) are composed of the following systems:
RMS Suite:
• D200 Requirements Management System (RMS)
• D040 War Reserve Materiel Lists/Requirements and Spares Support Lists (RSSL)
• D040 Weapon System Support Program (WSSP)
• D072 Other War Reserve Material Requirements (OWRMR)
• DD1000 Supply System Inventory Report (SSIR)
LMDB:
• D075 Logistics Management Data Bank (LMDB)
See Performance Work Statement (PWS) for full descriptions of these systems.
Contracting Approach 1.1.
The proposed 5-year 8(a) small business competitive effort shall be a combination of Firm Fixed Price (FFP), and cost reimbursable no-fee CLINs. This contract will be incrementally funded.
FAR Clause 52.232-22, Limitation of funds, as prescribed in FAR part 32.706-2(b), will be included in the contract. DFARS Clause 252.232-7007, Limitation of Government’s Obligation, will be included as implemented in DFARS 232.705-70.
Ombudsman 1.2.
An Ombudsman has been appointed to consider and facilitate the resolution of concerns from Offerors, potential Offerors, and others for this acquisition. When requested, the Ombudsman will maintain strict confidentiality as to the source of the concern. The existence of the Ombudsman does not affect the authority of the Contracting Officer (CO) or Source Selection Official. Further, the Ombudsman does not participate in the evaluation of proposals, the Source Selection process, or the adjudication of protests or formal contract disputes. The Ombudsman may refer the party to another official who can resolve the concern. The Ombudsman may not serve as an advocate for any party.
Before consulting with an Ombudsman, concerned parties must first address their concerns, issues, disagreements, and/or recommendations to the CO for resolution. Consulting an Ombudsman does not alter or postpone the timelines for any other processes (e.g. agency level bid protests, GAO bid protests, requests for debriefings, employee-employer actions, contest of OMB A-76 competition performance decisions).
If resolution cannot be made by the CO, concerned parties may contact the Center/MAJCOM Ombudsman, Name: Lt Col Kenneth L. Decker, Jr.
E-mail: Kenneth.Decker.1@us.af.mil
AFLCMC/AQP
COMM: 937-255-5512
The Ombudsman has no authority to render a decision that binds the agency. Do not contact the Ombudsman to request copies of the solicitation, verify offer due date, or clarify technical requirements. Such inquiries shall be directed to the CO.
mailto:Jill.Willinghamallen.1@us.af.mil
2. Guidance/Instructions This Instruction to Offerors (ITO) provides general g uidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror's proposal shall include all data and information requested by this ITO and must be submitted in accordance with (IAW) these instructions. The offer shall be compliant with the requirements as stated in the PWS, Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.
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 or experience and will base its evaluation on the information presented in the Offeror's proposal.
Do not submit elaborate brochures or documentation, binding, detailed art work, or other embellishments.
The Offeror shall clearly state in the proposal cover letter that the proposal is valid for 180 days from the proposal due date.
In accordance with Federal Acquisition Regulation (FAR) Subpart 4.8 (Government Contract Files), the Government will retain one hard copy of all unsuccessful proposals. The Government will destroy extra copies of such unsuccessful proposals.
Point of Contact 2.1.
The CO is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent or emailed to the CO and Contract Specialist at the address listed below.
Mr. Richard B. Dickerson Ms. Kelsey J. Emory Contracting Officer Contract Specialist
AFLCMC/HIAK AFLCMC/HIAK
4225 Logistics Avenue Room A212 4225 Logistics Avenue Room A212 45433-5006 45433-5006 Voice (937) 257-4846 Voice (937) 257-6799 richard.dickerson.2@us.af.mil kelsey.emory@us.af.mil
2.1.1. Debriefings
The CO 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 CO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.503. 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.
mailto:richard.dickerson.2@us.af.mil mailto:karissa.porter@us.af.mil http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/Far/15.htm#P937_172705 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/Far/15.htm#P958_175362
2.1.2. 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 CO in writing with supporting rationale as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.
2.1.3. 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.
2.1.4. Communications
Exchanges of source selection information between Government and Offerors will be controlled by the CO. Email may be used to transmit such information to Offerors only if the email includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Otherwise, source selection information may be transmitted via other controlled methods (USPS, FedEx, UPS, or delivery to the CO by local representative).
Organization, Number of Copies and Page Limits 2.2.
The Offeror shall prepare their proposal as set forth in the Proposal Organization Table (Table 1 below). The titles and contents of each proposal volume shall be as set forth in Table 1 below.
Proposal volumes shall be within required page limits and be submitted with the number of copies specified in Table 1. Volume I and II should be combined in a single three-ring, loose-leaf binder and provided in electronic format as well. Volumes III, IV and V shall be submitted in separate individual three-ring, loose-leaf binders. The contents of each proposal volume are described in the ITO Paragraph as noted in Table 1 below.
VOLUME &
SECTION
ITO
PARA
TITLE COPIES PAGE LIMIT
Vol I 3.0 Executive Summary 2 electronic copies/ 1 hard copy
2 pages
Vol II
4.0
Technical Volume Sub-Factor 1
Technical Program Management
Sub-Factor 2 Functional/ System Engineering
Sub-Factor 3 Staffing Plan
2 electronic copies/ 1 hard copy
Sub-Factor 1 – 10 pages
Sub-Factor 2 – 10 pages
Sub-factor 3 – 3 pages
Vol III 5.0 Price Proposal 2 electronic copies/ 1 hard copy
No Limit http://www.fedbizopps.gov/ http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/Far/02.htm#P11_633 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/Far/03.htm#P42_5838
Vol IV 6.0 Past Performance Limit of 3 References (Prime)
Limit of 3 References each (Critical or Major
Subcontractor)
2 electronic copies/ 1 hard copy
Each reference – 4 pages as created by PPI tool.
All additional information 10 pages total.
Vol V 7.0 Contract Documentation 2 electronic copies/ 1 hard copy
No Limit
TABLE 1 - Proposal Organization and Page Limits
2.2.1. Page Size and Format, Page Limitation
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 numbered sequentially by volume. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point in Times New Roman font. 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 1-inch side margins. These page format restrictions shall apply to responses to Evaluation Notices (ENs). Pages exceeding the page limitations set forth in this Section L (see Table 1, Proposal Organization) will not be read or evaluated, and will be removed from the proposal. Electronic files must be unprotected so that pages can be removed/redacted from the proposals as needed. Page limitations may be placed on responses to ENs. The specified page limits for EN responses will be identified in the communications forwarding the ENs to the Offerors. Each page shall be counted except the following: Title Page, Table of Contents, and glossaries.
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 x 17 inches in size. Foldout pages shall fold entirely within the volume, and be counted as two pages. 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. Tables, charts, graphs, and figures will be included in the page count for their respective volume.
2.2.2. Pricing Related Data
All pricing information shall be addressed ONLY in the Price and Contract Documentation volumes. Information shall be limited to Contract Line Item Number (CLIN), Sub-CLIN, or CLIN-level pricing, including unit and extended pricing, as specified in Section B of the Model Contract, Attachment 5 of the RFP.
2.2.3. Classified Information
Classified information is not requested, nor should be provided in your response.
2.2.4. Cross-Referencing
To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated without 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.
If included, cross-reference matrixes shall indicate by Section L - ITO, PWS, Section M, and CDRL references and/or specification paragraph number, the corresponding proposal paragraph in that section which addresses the referenced item.
2.2.5. 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. Table of contents and tab indexing will not count against page limitations.
2.2.6. Glossary of Abbreviations and Acronyms
Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.
Electronic Offers (Proposal of Record used for Evaluation) 2.3.
Each Offeror shall submit volumes I through V in uncompressed electronic format recorded on Compact Discs-Read Only (CD-Rs) or Digital Versatile Discs-Read Only (DVD-Rs). Two (2) electronic copies of the Proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2010 and MS Office Excel 2010 as applicable.
When submitting electronic versions of their proposal, Offerors shall follow these instructions:
Submitting documents using Microsoft Office 2010 or greater:
• Word documents – Set "Save as type" to "Word Document (*.docx)"
• Excel spreadsheets – Set "Save as type" to "Excel Workbook (*.xlsx)."
Submitting documents using Microsoft Office 2007:
• Word documents – Set "Save as type" to "Word Document (*.docx)"
• Excel spreadsheets – Set "Save as type" to "Excel Workbook (*.xlsx)."
Volumes I and II should be combined on a single disc, while Volumes III, IV and V shall be submitted separately. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The content and page size of electronic copies shall be identical to that of printed copy. The electronic version shall be the proposal of record and, in the event there is a discrepancy between the paper version of the proposal and the electronic version of the proposal, the electronic version will take precedence. Electronic files must be unprotected so that pages can be removed/redacted from the proposals as needed.
Hardcopy Offers 2.4.
Offerors shall provide a single hard copy of their proposal. Volumes I & II should be combined in a single three-ring, loose leaf binder. Volumes III, IV and V shall be submitted separately in three-ring, loose leaf binders. Staples shall not be used and binders should allow the volume to lie flat when open. A cover sheet should be bound in each book, clearly marked as to volume number, title, solicitation identification, and the Offeror's name. The same identifying data should be placed on the spine of each binder. While the rest of the hard copy proposal is submitted in three-ring, loose-leaf binders, the signed cover page of the contract (SF26-Model Contract) should be provided without any punched holes for potential use as an executable contract document.
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.
Distribution 2.5.
The "original" proposal shall be identified; meaning the proposal of record discs should be marked “original.” Proposals shall be addressed to the CO and mailed or hand carried to the CO at the address located in paragraph 2.1.
3. Volume I - Executive Summary In the Executive Summary volume, the Offeror shall provide the following information:
Narrative Summary 3.1.
The narrative summary of the entire proposal should be concise and highlight any key or unique features of the proposal, other than price. The salient features should refer to the Section M evaluation factors/criteria, where appropriate. Accordingly, material presented in volume I may not be relied upon to meet the requirements of other volumes stipulated in the ITO.
Table of Contents 3.2.
Volume I shall also include a master table of contents for the entire proposal and a matrix that matches proposal Volume and paragraph numbers, with corresponding solicitation section and paragraph numbers – to include the PWS, CDRLs, CLINS, and Sections L and M. The pages of the master table of contents and a matrix shall not count against Volume I page limits.
Letter of Transmittal or Executive Cover Letter 3.3.
A Letter of Transmittal or Executive Cover Letter shall be included with each proposal. Cover Letter pages will not count against the page limits of Volume I but shall not exceed two (2) pages in length.
Small Business Status Confirmation 3.4.
Contracting Officer will validate 8(a) status upon receipt of proposal(s) and prior to award.
4. Volume II - Technical Volume General 4.1.
The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical Sub-Factors defined in http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/Far/52_215.htm#P2_52 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/Far/03.htm#P123_19941
Section M. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these sub-factors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.
Format and Specific Content 4.2.
In the technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical example.
The proposal shall be structured to address each of the evaluation factors and subfactors identified in Section M of this solicitation and demonstrate how proposed solutions, processes, management constructs and staffing will result in the successful achievement of the objectives identified in the PWS. The Technical volume shall be organized according to the following general outline:
1) Table of Contents
2) Cross Reference Matrix
3) Factor 1: Technical
a) Subfactor 1: Technical Program Management
b) Subfactor 2: Functional/System Engineering
c) Subfactor 3: Staffing Plan
4) List of Tables and Drawings
5) Glossary
4.2.1. Technical
The proposal shall describe a complete understanding of the maintenance and sustainment services required with detail of the Offeror’s technical approach and overall ability to perform the requirement.
Identify any assumptions used when formulating your responses.
4.2.1.1. Subfactor 1: Technical Program Management
Provide a brief narrative response, including a summarized schedule and a technical approach specifically addressing PWS sections 1.2.2, 1.2.3, 1.2.6, 1.2.8, 1.2.9, 1.3.1.3, and 1.4.1. Describe your approach to the program management activities to manage schedule, risk and performance to ensure requirements are met and delivered on time, showing what documents are needed and what approvals are required. Ensure your response addresses the questions in the example.
EXAMPLE: The RMS and LMDB Program Management Office have obtained Government board approval to implement software requirements and been tasked by our Functional OPRs to correct problem/deficiency requirements and modification requirements for the below applications within the RMS and LMDB suite of systems.
1. D200A has a maintenance Baseline Change Request (BCR) modification requirement. The D200A Secondary Item Requirements System (SIRS) modification requirement will add an additional database field to the recoverable item record to contain the system exchange price. D200A SIRS also has 2 problem/deficiencies requirements that adversely affects technical risk to the project and has no work-around solution. The D200A SIRS problems/deficiencies also require documentation changes to the System Specification and Functional Description. Identify the priority of the problem/deficiency. What are the responses required by the PWS and what is the timeframe of the response?
2. Regular reporting of status is required during the timeframe of the example.
Assume the problem/deficiencies above were found on April 1st, and that work on the BCR is underway at that time. What reports referenced in the PWS would be delivered during April and May?
4.2.1.2. Subfactor 2: Functional /System Engineering
Provide a brief narrative response specifically addressing PWS Sections 1.1.1, 1.1.1.2, 1.1.1.3, 1.1.5, 1.4, 1.4.6.1, 1.4.6.5, 1.5 and 1.5.1, describing your approach to the Functional and System Engineering activities. Ensure your response addresses the following questions and requests.
1. What are the steps to capture the quarterly/monthly summary cycle of D200N and to pass secondary items data to DD1000?
2. How does the Aircraft Availability Model fit into the D200 system? Also, describe how your team will acquire and maintain the knowledge to adequately support this function.
3. Describe system engineering approach to the D200A maintenance BCR in #1 of Subfactor 1. Describe the analysis, development and test, including how to validate data processed correctly upon receipt.
4. Demonstrate understanding of the interrelationships between D200A, D200N, D200E, D200F, DD1000 and LMDB to include details on the cycle sequence of events and frequency.
4.2.1.3. Subfactor 3: Staffing Plan
Provide a staffing plan IAW PWS section 1.2.1 to cover all the work specified in the effort, using the Skill Matrix table shown in RFP Attachment 13. Include descriptions of the labor categories and team positions that describe the skills, roles, responsibilities and experience level of the target candidates to fill the position. This description is not intended to be specific personnel resumes; it is intended to be description of work performed.
5. Volume III - Price General Instructions 5.1.
Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal.
5.1.1 Format and Specific Content
The Price volume shall consist of the following sections:
Section 1 – Table of Contents; summary descriptions of estimating, purchasing, and accounting systems.
Section 2 –Firm-Fixed-Price efforts will identify the projected labor categories, fully burdened rates, hours and the overall price to support the reasonableness evaluation. The work will be performed at Wright-Patterson AFB, OH.
Provide a detailed Basis of Estimate (BOE) by CLIN with any supporting data and narrative that clearly explains how the prices were developed. The detailed data shall completely describe the ground rules, assumptions, basis, rationale, and calculations used in developing the estimates.
1) In the Pricing Template provided (RFP Attachment 7), list all labor categories and hours necessary to fulfill the requirements of the PWS. Provide pricing for each CLIN identified for the initial period of performance and each of the option periods.
2) Explain how the proposed labor hours and skill mix has been derived. Labor hour estimates shall be based on projected hours, with a standard of 1,880 hours per staff year and 156.66 hours per staff month; Offerors are not required to propose a full labor year for each labor category, but should base their hourly rates on a 1,880 hour staff year.
These standards will facilitate a consistent evaluation of proposals across all Offerors.
Section 3 – Pricing Template: The Offeror shall fill out the Pricing Template, RFP Attachment
7. This Template shows the total price to the Government for evaluation purposes, derived as the sum of the following:
1) Firm-Fixed-Price (FFP) for maintenance and sustainment.
2) The Offeror will use the Government provided Cost Reimbursable (CR) Travel and ODC
CLINs. The Travel and ODC CLINs will be included in the overall Total Evaluated Price
(TEP).
3) The Government may require continued performance of services for up to six (6) months invoking the extension of services clause. IAW FAR 52.217-8, the offeror shall propose the six month extension of services utilizing Option 4 rates.
Price Reasonableness 5.2.
Offers should be sufficiently detailed to demonstrate their reasonableness and balance. The burden of proof for credibility of proposed prices rests with the Offeror. Unbalanced pricing may pose an unacceptable risk to the Government and may be a reason to reject an Offeror’s proposal.
5.2.1. Price Data
Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.
5.2.2. Cost or Pricing Data Requirements
The CO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the CO will review this determination and if, in the CO's opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the CO determines that adequate price competition no longer exists;
Offerors may be required to submit information to the extent necessary for the CO to determine the reasonableness and affordability of the price.
5.2.3. Rounding
All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.
5.2.4. CLIN Structure
The Price Template, RFP Attachment 7, shall be completed as stated:
CLIN X001 (RMS Program) (Price Template, Tab 2)
1) Enter labor category title, labor hours, and fully burdened rates for every labor category used on the CLIN X001 tab.
2) If your rates change during a contract year, please provide the calculations to show the blended rate for each contract period.
3) Offerors may add labor categories as needed, but it is the responsibility of Offeror to check formulas based on template changes.
4) Offerors must explain any inflation changes in rates from one contract period to the next or during a contract period.
5) Round (and truncate) all burdened labor hour rates to nearest cent.
6) Rates for Option Year 4 will be used for the 6 month Extension of Services.
CLIN X002 (LMDB Program) Rate Build (Price Template, Tab 3)
1) Enter labor category title, labor hours, and fully burdened rates for every labor category used on CLIN x002 tab.
2) If your rates change during a contract year, please provide the calculations to show the blended rate for each contract period.
3) Offerors may add labor categories as needed, but it is the responsibility of Offeror to check formulas based on template changes.
4) Offerors must explain any inflation changes in rates from one contract period to the next or during a contract period.
5) Round (and truncate) all burdened labor hour rates to nearest cent.
6) Rates for Option Year 4 will be used for the 6 month Extension of Services.
CLIN X003 (Data) will not be separately priced.
CLIN X004 Other Direct Costs (ODCs) is provided. The annual value is $25,000.
CLIN X005 Travel is provided. The annual value is $2,750.
Total Price (Price Template, RFP Attach 7, Tab 4)
1) All formulas in template add automatically, using the information provided on CLIN tabs.
2) It is the responsibility of Offeror to check formulas based on template changes.
3) CLIN X003 Data is not separately priced.
4) CLIN X004 Other Direct Costs (ODCs) and CLIN X005 Travel values are provided.
a) The annual value for ODCs, CLIN X004 is $25,000.
b) The annual value for Travel, CLIN X005 is $2,750.
5) The Government will select the proposal with the best value as detailed in Section M (Basis of Award). (Price Template, RFP Attach 7, Tab 5)
Other Information 5.3.
Ground Rules and Assumptions The following ground rules are being provided as guidelines for completing the Price proposal.
1) The Offeror shall assume an anticipated contract award date of Dec 2016.
2) All Prices should be based on fully burdened rates that are inclusive of all applicable/allowable labor in-directs, material handling, General and Administrative (G&A) and profit.
3) Proposed prices for each year should be inclusive of any escalation/inflation for each year of the proposed period of performance. No escalation/inflation adjustments will be made that are not included in the proposal, either during evaluation or post award.
4) All prices are to be displayed by CLIN where applicable.
5) The Price proposal is not subject to page limitations, but shall only include information that is pertinent to pricing matters.
6. Volume IV - Past Performance
Format and Specific Content 6.1.
The Past Performance volume shall be organized according to the following general outline:
1. Table of Contents
a. List of Offeror and subcontractors, teaming partners, and/or joint venture partners whose information is captured in PPI Tool (included in 10 page limit)
b. Past Performance Effort Reports from PPI Tool (font, margin and layout guidelines do not apply, reports shall be no more than 4 pages per past performance effort reference when generated from the PPI tool)
c. Consent/Authorization Letters (excluded from 10 page limit)
d. Organizational Structure Change History (included in 10 page limit)
e. Quality and Satisfaction Evidence (included in 10 page limit)
2. PPI Tool file(s) name and description (excluded from 10 page limit)
Past Performance Information (PPI) Tool 6.2.
Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in RFP Attachment 11 that contains instructions for use of the PPI Tool.
This information is required on the offeror and all major subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 25 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. Information on other subcontractors, teaming partners, and/or joint venture partners that you consider most relevant in demonstrating their ability to perform the proposed effort can also be included. 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. If a teaming arrangement/joint effort is contemplated, provide complete information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangements with same partner. If this is a first time teaming/joint effort, each party to the arrangement must provide a list of past and present relevant contracts.
Consent/Authorization Letters 6.3.
Along with the information required in this section, 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.
Recent and Relevant Contracts 6.4.
Submit information in the PPI tool in accordance with Attachment 11: Past Performance Information on three (3) recent contracts for the prime contractor and three (3) for each major subcontractor, teaming partner, and/or joint venture partner. Recent contracts are defined as those that were performed for Federal agencies, city, county or state Government, or commercial customers within the last five (5) years in demonstrating your ability to perform the proposed effort. Relevant contracts include performance of efforts involving sustainment and modification of mainframe and mid-tier information technology systems that are similar or greater in scope, magnitude, technology and complexity than the effort described in this solicitation.
See PWS Appendix C for technical descriptions of the RMS and LMDB systems. Past performance citations that cover more of the relevancy criteria areas are preferred over those that cover less. The Government will not use in its assessment a past/present contract where performance cannot be verified through the customer of that contract. Where the citation provides information regarding a subcontract, the customer of that contract is the prime contractor. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, - Evaluation Factors, paragraph 2.3 - Past Performance Factor.
6.4.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 more favorably than without evidence of problem resolution. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors and Price factor used to evaluate the proposal.
6.4.2. 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 acquisition. 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/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), 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.
Quality and Satisfaction Rating for Contracts Completed in the Past Five 6.5.
Years
Provide any information currently available (letters, metrics, customer surveys, independent surveys, etc.) which demonstrates customer satisfaction with overall job performance and quality of completed product for relevant contracts submitted as Past Performance. Explain corrective actions taken in the past, if any, for substandard performance and any current performance problems such as cost overruns, extended performance periods, numerous warranty calls, etc.
There is no limitation if Offeror was prime or sub. Past Performance submissions are limited to North American Industry Classification System (NAICS) 5415XX.
Performance Surveys 6.6.
The Government will evaluate the quality and extent of the Offeror's performance deemed relevant (as defined in paragraph 6.4 above) to the requirements of this RFP.
The Government will use information submitted by the Offeror, responses to questionnaires, and other sources such as other Federal, city, county and state Government offices and commercial sources, to assess performance.
The Offeror shall send the letter (RFP Attachment 8) and questionnaire (RFP Attachment 9) to each of the three (3) references for the prime and each major and/or minor subcontractors, teaming partners, and/or joint venture partners submitted as reference in the PPI tool. These surveys are completed by the reference customer and submitted directly to the CO.
7. Volume V - Contract Documentation Documents submitted in response to this RFP must be fully responsive to and consistent with the following:
1) Requirements of the RFP (CLINs & PWS) and Government standards and regulations pertaining to the PWS.
2) Evaluation Factors for Award in Section M of this RFP.
3) Any limitation on the number of proposal pages.
Model Contract 7.1.
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 (SF26), and complete Sections A, B and K.
7.1.1. Section A - Solicitation/Contract Form
Complete blocks 7, 15, and 19 and provide signature on the SF26. Signature by the Offeror on the SF26 constitutes an offer, which the Government may accept. The hard copy should be clearly marked under separate cover. While the rest of the hard copy proposal is submitted in three-ring, loose-leaf binders, the signed cover page of the contract (SF26) should be provided without any punched holes for potential use as an executable contract document. Complete blocks 7, 15 and 19 of any SF26, Amendment of Solicitation, that is issued and return the signed original with volume 5 of the proposal.
7.1.2. Section B - Supplies or Services and Price
The Offeror shall provide completed pricing information in Section B of the Model Contract, RFP Attachment 5.
7.1.3. Section F - Deliveries or Performance
7.1.4. Section G - Contract Administrative Data
7.1.5. Section H - Special Contract Requirements
7.1.6. Section I - Contract Clauses
Section I shall have clauses that the contractor will need to complete prior to submission. It is the responsibility of the contractor to identify these clauses and provide the required information.
7.1.7. Section J - Reserved
7.1.8. Section K - Representations, Certifications, and other Statements of Offerors
The completed representations, certifications, acknowledgments and statements.
The Offeror shall return the completed Section K, Representations, and Certifications with the solicitation and/or identify the On-Line Representation and Certifications Application (https://www.sam.gov) website as where the completed Section K can be accessed. Note that there may be additional Section K provisions included in the RFP that are not included in the System for Award Management (SAM) requirements.
Sections L and M 7.2.
Sections L and M will not become part of the contract. These sections and attachments are issued for proposal preparation and evaluation purposes only. Note: strengths identified in the Offeror’s proposal may be incorporated in the PWS at time of award.
Other Information Required 7.3.
Provide Capability Maturity Model Integration (CMMI) Level II or higher appraisal or similar credential. Similar credentials will be evaluated on a case by case to determine if they are adequate “equivalents.”
7.3.1. Authorized Offeror Personnel
Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.
7.3.2. Government Offices
Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).
7.3.3. Company/Division Address, Identifying Codes, and Applicable Designations
Provide company/division's street address, county and facility code; CAGE code; DUNS code;
TIN; size of business (large or small).
Attachments to the Model Contract 7.4.
The Offeror shall provide the following as attachments to the model contract:
7.4.1. Base Support Requirements
The Government has desk space and workstations on site at WPAFB for the current RMS/LMDB sustainment team. Offeror shall provide a number of desks and workstations required for the proposed team.
7.4.2. Associate Contractor Agreements
Include Associate Contractor Agreements, if applicable.
7.4.3. Limitations on Subcontracting
In accordance with FAR 52.219-14 (included in the model contract), the Offeror agrees that at least 50 percent of the cost of contract performance incurred for personnel shall be expended for employees of the Offeror. As part of the proposal, the Offeror shall provide, as a percentage, the total estimated amount of work under the proposal that will be completed by the Offeror (excluding subcontractors).
7.4.4. Additional Required Documents
The Offeror shall provide the following with the volume V:
1) Government Furnished Equipment. The Offeror shall list and provide current market value for any proposed GFE (even if identified in another part of the proposal), excluding any Government property already identified in the RFP.
2) Accounting System. Indicate whether you have Government approval of your budgeting, accounting, purchasing, and financial systems. If so, provide evidence of such approval.
Also, identify any deviations from your standard procedures in preparing this proposal.
3) Offerors shall provide a high level organizational chart to include subcontractors performing on this contract. This chart shall be no larger than a one page foldout.
| 1. Program Information |
| 1.1. Contracting Approach |
| 1.2. Ombudsman |
| 2. Guidance/Instructions |
| 2.1. Point of Contact |
| 2.1.1. Debriefings |
| 2.1.2. Discrepancies |
| 2.1.3. Electronic Reference Documents |
| 2.1.4. Communications |
| 2.2. Organization, Number of Copies and Page Limits |
| 2.2.1. Page Size and Format, Page Limitation |
| 2.2.2. Pricing Related Data |
| 2.2.3. Classified Information |
| 2.2.4. Cross-Referencing |
| 2.2.5. Indexing |
| 2.2.6. Glossary of Abbreviations and Acronyms |
| 2.3. Electronic Offers (Proposal of Record used for Evaluation) |
| 2.4. Hardcopy Offers |
| 2.5. Distribution |
| 3. Volume I - Executive Summary |
| 3.1. Narrative Summary |
| 3.2. Table of Contents |
| 3.3. Letter of Transmittal or Executive Cover Letter |
| 3.4. Small Business Status Confirmation |
| 4. Volume II - Technical Volume |
| 4.1. General |
| 4.2. Format and Specific Content |
| 4.2.1. Technical |
| 4.2.1.1. Subfactor 1: Technical Program Management |
| 4.2.1.2. Subfactor 2: Functional /System Engineering |
| 4.2.1.3. Subfactor 3: Staffing Plan |
| 5. Volume III - Price |
| 5.1. General Instructions |
| 5.1.1 Format and Specific Content |
| 5.2. Price Reasonableness |
| 5.2.1. Price Data |
| 5.2.2. Cost or Pricing Data Requirements |
| 5.2.3. Rounding |
| 5.2.4. CLIN Structure |
| 5.3. Other Information |
| 6. Volume IV - Past Performance |
| 6.1. Format and Specific Content |
| 6.2. Past Performance Information (PPI) Tool |
| 6.3. Consent/Authorization Letters |
| 6.4. Recent and Relevant Contracts |
| 6.4.1. Specific Content |
| 6.4.2. Organizational Structure Change History |
| 6.5. Quality and Satisfaction Rating for Contracts Completed in the Past Five Years |
| 6.6. Performance Surveys |
| 7. Volume V - Contract Documentation |
| 7.1. Model Contract |
| 7.1.1. Section A - Solicitation/Contract Form |
| 7.1.2. Section B - Supplies or Services and Price |
| 7.1.3. Section F - Deliveries or Performance |
| 7.1.4. Section G - Contract Administrative Data |
| 7.1.5. Section H - Special Contract Requirements |
| 7.1.6. Section I - Contract Clauses |
| 7.1.7. Section J - Reserved |
| 7.1.8. Section K - Representations, Certifications, and other Statements of Offerors |
| 7.2. Sections L and M |
| 7.3. Other Information Required |
| 7.3.1. Authorized Offeror Personnel |
| 7.3.2. Government Offices |
| 7.3.3. Company/Division Address, Identifying Codes, and Applicable Designations |
| 7.4. Attachments to the Model Contract |
| 7.4.1. Base Support Requirements |
| 7.4.2. Associate Contractor Agreements |
| 7.4.3. Limitations on Subcontracting |
| 7.4.4. Additional Required Documents |
File details come from the government source that posted it. Updated .