PACRM RFP 20R0082 amendment 0001 30SEP20.docx
DOCX document 81 KB Posted
- Solicitation number
- N6134020R0082
About this file
This document is a request for proposal (RFP) for a Pilot and Aircrew Curriculum Revision and Maintenance (PACRM) Multiple Award Contract (MAC). The Naval Air Warfare Center Training Systems Division (NAWCTSD) requires support for the revision and maintenance of Navy and Marine Corps pilot and aircrew curriculum, including curriculum updates and electronic classroom systems, to ensure continued accuracy of training programs and maintain operational readiness for the Fleet. The RFP seeks proposals from contractors to establish an indefinite delivery/indefinite quantity (IDIQ) contract to support both planned and unplanned procurements over multiple years. Offerors must submit proposals by the date specified in block 9 of the Standard Form 33 addressing requirements for contract experience, past performance, technical approach, and pricing in volumes 1 through 5. Awards will be made to between three to five contractors selected as the best value based on an evaluation of these factors. The total contract value over the life of the IDIQ is estimated at $90 million.
View the file
Other files
Show all 41
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
N6134020R0082
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
The following items are applicable to this modification:
AMMENDMENT 0001
AMENDMENT 0001-Updates the following:
1) Section F, Delivery Information removed, to be determined at Task Order (TO) level.
2) Section H,
a. Update, H.4 - OPTION EXERCISE, (d) Additional Options for CRs, Level 1 Change Request per FY.
b. Update, H.13 - MULTIPLE AWARD CONTRACT OMBUDSPERSON, POC information
c. Update Clause 5252.217-9507 from reference to full text
d. Delete NAVAIR Clause 5252.228-9501, LIABILITY INSURANCE
3) Section L, Attachments updated;
a. L-2, Contract Experience (CE) Contract Data
b. L-3, Past Performance (PP) Contract Data
c. L-7, Price Breakout Worksheet (PBW)
d. L-8, Performance Work Statement (PWS) E2, C2, and LSO
e. L-9(a), WD 2015-4341 Revision 14, 04 AUG 2020
f. L-10, CDRL package for E2, C2, and LSO
g. ADD L-13, Government Response to Solicitation Question
4) Section L- Updates Bolded
5) Section M- Updates Bolded
SUMMARY OF CHANGES
SECTION H - SPECIAL CONTRACT REQUIREMENTS
The following have been modified:
SPECIAL CONTRACT REQUIREMENTS
H.1 - ISSUANCE OF ORDERS UNDER MULTIPLE AWARD CONTRACTS
(a) The following types of Task Orders may be issued under this contract:
i) Fixed Price (Firm-fixed-price (FFP))
Fixed price orders may be issued when the scope of effort is sufficiently defined to allow technical and cost risks to be predicted with reasonable certainty. Under this contract type, the Contractor shall be required to submit a fixed price proposal to accomplish the total effort inclusive of all labor, material and travel costs, as appropriate. The contractor shall be required to deliver the services within the specified time and fixed price amount.
ii) Cost Reimbursement (Cost-plus-fixed-fee (CPFF))
Cost reimbursement orders may be issued when it is not possible to precisely define the magnitude of the effort required to accomplish the stated effort. The estimated cost for an order shall be based on the contractor’s actual labor rates and material costs, with the applicable overhead, G&A, and fee. The order amount will be expressed as a total cost plus fee.
iii) Hybrid
Any combination of the contract types above.
(b) Individual Task Orders will specify the type of order to be used and may incorporate / modify additional clauses not incorporated in the basic ID/IQ into the Task Order. Such additional clauses will pertain only to the individual Task Order.
(c) Orders may be issued by the Government on a competitive basis using approved competitive procedures or on a non-competitive basis when an Exception to Fair Opportunity (EFO) as described in FAR 16.505(b)(2) exists. All decisions regarding the procurement method and selection criteria shall be made by the Contracting Officer. Information regarding the type of order, award basis and selection criteria shall be provided to the awardees with each request for proposals.
(d) Task Order awards will normally be made to the offeror who is determined, under a “best value” evaluation, to best meet the needs of the Government after consideration of all evaluation factors. “Best value” is defined as the procurement process that results in the most advantageous acquisition decisions for the Government and is generally performed through an integrated assessment and trade-off analysis utilizing quality factors such as technical approach, past performance, management approach, personnel experience, and cost/price factors.
(e) Offerors are cautioned that in conducting the Task Order evaluation, the Government may use data provided by the offeror in its proposal as well as data obtained from other sources (e.g. Dun and Bradstreet reports, DCAA audits, available industry market rates for labor and overhead). While the Government may elect to consider data obtained from other sources, the burden of providing thorough and complete information rests with the offeror.
(f) Task Orders issued will be publicized utilizing the on the https://beta.sam.gov website.
(g) Orders may be issued as a result of a Government prepared PWS or Statement of Objectives (SOO), and proposals may be requested in either written or oral format.
(h) Pursuant to FAR 16.505(b) and NAVAIR clause 5252.216-9507, “Fair Opportunity Procedures,” the Contracting Officer shall ensure that each prime contractor is provided a fair opportunity to be considered for each order in excess of $3,500. PACRM TO competitions will identify the specific criteria and order of importance for award decisions based upon the requirements set forth in the individual TO solicitations. MAC awardees need not be given an opportunity to be considered for a particular Task Order if the Ordering Officer makes a determination in accordance with FAR 16.505(b)(2).
(i) All costs associated with presentation, and/or discussion of the contractor’s Task Order proposal, post award Task Order administration (including applicable personnel cost allocations by Task Order) shall not be a direct charge under the Task Order unless authorized in the PACRM contract or subsequent Task Order awards. Bid and proposal costs shall be unallowable as a direct cost for proposals voluntarily prepared and submitted. This includes any proposal submitted under the PACRM contract or subsequent Task Order awards.
(j) Options included in any order will be evaluated in accordance with FAR clause 52.217-5, “Evaluation of Options”. The Task Order evaluation will also include evaluation of the six-month period available to the Government via FAR 52.217-8, Option to Extend Services.
(k) The following requirement applies to cost reimbursement Task Orders, or fixed-price Task Orders which provide for progress payments made on the basis of costs incurred by the contractor or on a percentage or stage of completion:
(l) To be eligible for the award of any cost reimbursement Task Order, or to receive progress payments made on the basis of costs incurred by the contractor or on a percentage or stage of completion, the contractor must have an accounting system that is adequate to determine the costs allocable to the Task Order.
Pursuant to DFARS clause 252.242-7006, "Accounting System Administration," the contractor shall maintain an acceptable accounting system during the entire period of contract performance for determining costs applicable to any cost-reimbursement Task Order issued hereunder.
Pursuant to FAR 9.103, "Purchases shall be made from, and contracts shall be awarded to, responsible prospective contractors only." The responsibility determination will include, but not be limited to, an assessment of a contractor's accounting system to ensure acceptability for accumulating costs.
Accordingly, the contractor shall provide evidence that its accounting system has been determined adequate and acceptable from a federal government entity for administration of a cost-reimbursable type Task Order; state that some other determination regarding its accounting system has been made by a federal government entity; or state that its accounting system has not been reviewed by a federal government entity for adequacy and acceptability.
If, at the time of proposal submission for a Task Order, the contractor does not already have an accounting system that has been determined adequate and acceptable for determining costs applicable to the cost-reimbursement Task Order, the Procuring Contracting Officer (PCO) will request a preaward survey. In the event of a preaward survey, it is requested that contractors cooperate with the federal government entity to provide required information in a timely manner so as not to delay Task Order award.
(2) The PACRM PCO may request that contractors demonstrate compliance with part of above prior to or after award of a cost reimbursement Task Order, or fixed-price Task Order which provide for progress payments made on the basis of costs incurred by the contractor or on a percentage or stage of completion.
(l) Contractors are not guaranteed award of equal dollars or number of Task Orders under this Contract.
H.2 – TASK ORDER PROCEDURES
(a) The following activity(ies) or individual(s) is/are designated as Contracting Office(s) / Officer(s):
i. All Procuring Contracting Officers (N61340)
ii. Other Procuring Contracting Officers as approved by the Procuring Contracting Officers identified in Task Orders.
The above activity(ies) or individual(s) is/are responsible for issuing and administering any orders placed hereunder. Contracting Officers may negotiate revisions/modifications to orders, but only within the scope of this contract. Contracting Officers have no authority to modify any provision of this basic contract. Any deviation from the terms of the basic contract must be submitted to the PACRM Procuring Contracting Officer for contractual action.
(b) Task Orders. All Task Orders issued hereunder are subject to the terms and conditions of this contract. The contract shall control in the event of conflict with any Task Order.
H.3 - SCHEDULE OF DEDUCTIONS
(a) CURRICULUM REVISION:
i) The contractor may be paid the unit price for a 100% Curriculum Revision On Time Factor (CROTF) for each individual site set forth in Section B. Computation of the CROTF may be in accordance with the PWS.
ii) Failure to achieve a monthly CROTF of at least 100% for any calendar month may result in a reduction of the monthly payment amount for non-performance of services. The Schedule of Deductions may be used when the CROTF on the monthly Performance Utilization Report falls below 100%. The percent to be deducted for non-performance of services for deficient CROTF set forth below in paragraph (iii) may be as designated in the Performance Requirements Summary Table (PRST) in the PWS. The monthly payment amount used for calculating a deduction will be 100% of the line item unit price for SMEs as stated in the PWS.
iii) Payment will be reduced in accordance with the following Schedule of Deductions:
Curriculum Revision Timeliness Factor (%)
% Deducted from Monthly Unit Price
| 96 - 99.9 |
| 5 |
| 95 - 95.9 |
| 10 |
| 94 - 94.9 |
| 15 |
| 93 - 93.9 |
| 20 |
| 92 - 92.9 |
| 25 |
| 91 - 91.9 |
| 30 |
| 90 - 90.9 |
| 35 |
| 89 - 89.9 |
| 40 |
| 88 - 88.9 |
| 45 |
| Below 87.9 |
| 50 |
(b) SME SERVICES:
i) The contractor may be paid the unit price for a 100% Subject Matter Expert Factor (SMEF) for each individual site set forth in Section B. Computation of the SMEF may be in accordance with the Performance Work Statement (PWS).
ii) Failure to achieve a monthly SMEF of 100% for any calendar month may result in a reduction of the monthly payment amount for non-performance of services. The Schedule of Deductions may be used when the SMEF on the monthly Performance Utilization Report falls below 100%. The percent to be deducted for non-performance of services for deficient SMEF set forth below in paragraph (iii) may be as designated in the Performance Requirements Summary Table (PRST) in the PWS. The monthly payment amount used for calculating a deduction will be 100% of the line item unit price for SMEs as stated in the PWS.
iii) Payment will be reduced in accordance with the following Schedule of Deductions:
| Subject Matter Expert Factor (%) |
| % Deducted from Monthly Unit Price |
| 99.9 - 90 |
| 10 |
| 89.9 – 80 |
| 20 |
| 79.9 - 70 |
| 30 |
| 69.9 - 60 |
| 40 |
| 59.9 - 50 |
| 50 |
| 49.9 - 40 |
| 60 |
| 39.9 - 30 |
| 70 |
| 29.9 - 20 |
| 80 |
| 19.9 - 10 |
| 90 |
| 9.9 - 0 |
| 100 |
(c) SITE SUPPORT SERVICES:
i) The contractor may be paid the unit price for a 100% Site Support Factor (SSF) for each individual site set forth in Section B. Computation of the SSF may be in accordance with the PWS.
ii) Failure to achieve a monthly SSF of 100% for any calendar month may result in a reduction of the monthly payment amount for non-performance of services. The Schedule of Deductions may be used when the SSF on the monthly Performance Utilization Report falls below 100%. The percent to be deducted for non-performance of services for deficient SSF set forth below in paragraph (iii) may be as designated in the Performance Requirements Summary Table (PRST) in the PWS. The monthly payment amount used for calculating a deduction will be 100% of the line item unit price for Site Support as stated in the PWS.
iii) Payment will be reduced in accordance with the following Schedule of Deductions:
| Site Support Expert Factor (%) |
| % Deducted from Monthly Unit Price |
| 99.9 - 90 |
| 10 |
| 89.9 – 80 |
| 20 |
| 79.9 - 70 |
| 30 |
| 69.9 - 60 |
| 40 |
| 59.9 - 50 |
| 50 |
| 49.9 - 40 |
| 60 |
| 39.9 - 30 |
| 70 |
| 29.9 - 20 |
| 80 |
| 19.9 - 10 |
| 90 |
| 9.9 - 0 |
| 100 |
(d) TDS SERVICES:
i) The contractor may be paid the unit price for a 100% Training Delivery System Factor (TDSF) for each individual site set forth in Section B. Computation of the TDSF may be in accordance with the PWS.
ii) Failure to achieve a monthly TDFS of 100% for any calendar month may result in a reduction of the monthly payment amount for non-performance of services. The Schedule of Deductions may be used when the TDSF on the monthly Performance Utilization Report falls below 100%. The percent to be deducted for non-performance of services for deficient TDSF set forth below in paragraph (iii) may be as designated in the Performance Requirements Summary Table (PRST) in the PWS. The monthly payment amount used for calculating a deduction will be 100% of the line item unit price for Training Delivery System Availability, Learning Resource Center Performance, and Information Assurance Technician Performance as stated in the PWS.
iii) Payment will be reduced in accordance with the following Schedule of Deductions:
| Training Delivery System Factor (%) |
| % Deducted from Monthly Unit Price |
| 99.9 - 90 |
| 10 |
| 89.9 – 80 |
| 20 |
| 79.9 - 70 |
| 30 |
| 69.9 - 60 |
| 40 |
| 59.9 - 50 |
| 50 |
| 49.9 - 40 |
| 60 |
| 39.9 - 30 |
| 70 |
| 29.9 - 20 |
| 80 |
| 19.9 - 10 |
| 90 |
| 9.9 - 0 |
| 100 |
(e) LRC SERVICES:
i) The contractor may be paid the unit price for a 100% Learning Resource Center Factor (LRCF) for each individual site set forth in Section B. Computation of the LRCSF may be in accordance with the PWS.
ii) Failure to achieve a monthly LRCSF of 100% for any calendar month may result in a reduction of the monthly payment amount for non-performance of services. The Schedule of Deductions may be used when the TDSF on the monthly Performance Utilization Report falls below 100%. The percent to be deducted for non-performance of services for deficient LRCSF set forth below in paragraph (iii) may be as designated in the Performance Requirements Summary Table (PRST) in the PWS. The monthly payment amount used for calculating a deduction will be 100% of the line item unit price for Training Delivery System Availability, Learning Resource Center Performance, and Information Assurance Technician Performance as stated in the PWS.
iii) Payment will be reduced in accordance with the following Schedule of Deductions:
| Learning Resource Center Factor (%) |
| % Deducted from Monthly Unit Price |
| 99.9 - 90 |
| 10 |
| 89.9 – 80 |
| 20 |
| 79.9 - 70 |
| 30 |
| 69.9 - 60 |
| 40 |
| 59.9 - 50 |
| 50 |
| 49.9 - 40 |
| 60 |
| 39.9 - 30 |
| 70 |
| 29.9 - 20 |
| 80 |
| 19.9 - 10 |
| 90 |
| 9.9 - 0 |
| 100 |
(f) IAT SERVICES:
i) The contractor may be paid the unit price for a 100% Information Assurance Technician Factor (IATF) for each individual site set forth in Section B. Computation of the IATF may be in accordance with the PWS.
ii) Failure to achieve a monthly IATF of 100% for any calendar month may result in a reduction of the monthly payment amount for non-performance of services. The Schedule of Deductions may be used when the IATF on the monthly Performance Utilization Report falls below 100%. The percent to be deducted for non-performance of services for deficient IATF set forth below in paragraph (iii) may be as designated in the Performance Requirements Summary Table (PRST) in the PWS. The monthly payment amount used for calculating a deduction will be 100% of the line item unit price for Training Delivery System Availability, Learning Resource Center Performance, and Information Assurance Technician Performance as stated in the PWS.
iii) Payment will be reduced in accordance with the following Schedule of Deductions:
| Information Assurance Technician Factor (%) |
| % Deducted from Monthly Unit Price |
| 99.9 - 90 |
| 10 |
| 89.9 – 80 |
| 20 |
| 79.9 - 70 |
| 30 |
| 69.9 - 60 |
| 40 |
| 59.9 - 50 |
| 50 |
| 49.9 - 40 |
| 60 |
| 39.9 - 30 |
| 70 |
| 29.9 - 20 |
| 80 |
| 19.9 - 10 |
| 90 |
| 9.9 - 0 |
| 100 |
H.4 –OPTION EXCERCISES
(a) In accordance with FAR 52.217-9 the Government may unilaterally exercise its option for any Task Order line item or sub line item designated as an option in Section B, to include selecting the Task level for items with optional levels of support (stepladders). Such option may be exercised at any time by issuing a Task Order modification not later than the last day of the then current performance period. The Government may exercise an option for any Task Order line item or Task not withstanding that the specific line item or Task was not exercised in the prior option period. A 30-calendar day written preliminary notice of intent to exercise will be given before the task order expires. Any option may be exercised subject to the Availability of Funds Clause in Section I.
The Government may unilaterally exercise an option in whole or in part. Any part of an option not exercised at the start of a period of performance may be exercised at any time during that period of performance as long as a 30 calendar day written notice is provided to the Contractor, with exception to the Additional Options for CRs (see paragraph (d)).
(b) Prices set forth in Section B for the options exercised will be the fixed prices (both the unit and total price) that are established from the Task Order PBW (Attachment 2), with the corresponding task that is exercised for that option period.
(c) Changes to Stepladders - For a change in level of support within optional priced stepladders, the Government may unilaterally change the level of support requested at any time, if a 30 calendar day written advance notice is provided to the Contractor.
(d) Additional Options for CRs - The Additional Options for CRs may be exercised at any time during the option period of performance with 30-day notice to the contractor. Additional Options CRs will be funded for COMNAVAIRLANT or COMNAVAIRPAC or others funding sources as required at time of exercise.
ADDITIONAL OPTION CRs Additional CRs, when exercised, may be selected from any or all of the Levels in the Price Breakout Worksheet for the appropriate option period with the not to exceed quantities as follows:
1. Level 1 Change Request 20 per FY
1. Level 2 Change Request 1500 per FY
1. Level 3 Changer Request 1000 per FY
1. Level 4 Change Request 500 per FY
1. Level 5 Change Request 250 per FY
H.5 - PRIME CONTRACTOR SUBCONTRACTING
1. It is the Government’s desire to maintain efficient and meaningful competition among the PACRM prime contractors. Practices that reduce competition, such as prime contractors entering into subcontract relationships in lieu of competing for Task Orders are not acceptable. The Government will consider waiving this restriction when it is clearly in the Government’s best interest. A request for a waiver with supporting details will be presented to the Contracting Officer who is the approval authority.
2. Prime contractors who propose teaming arrangements on an exclusive basis for a Task Order competition will be evaluated to determine whether such teaming agreements inhibit competition. In order for the Government to evaluate whether the proposed agreements inhibit competition, prime contractors are required to (1) provide a copy of all teaming arrangements, and (2) explain why the teaming arrangements do not inhibit competition. The documentation must include, but is not limited to: structure of the teaming arrangement, responsibilities, and liabilities; financial responsibility; managerial responsibility and accountability; and applicable legal documents. The burden of proving that any exclusive teaming arrangement proposed does not restrict competition shall rest with the prime contractors. Should the Government determine that any such proposed, exclusive teaming arrangement inhibits competition, (1) that determination may render the offeror's proposal ineligible for award, and (2) the Contracting Officer shall forward the matter to the appropriate authorities as prescribed by Federal Acquisition Regulation Part 3.3.
H.6 - ELECTRONIC TRANSMISSION OF PROPRIETARY DATA
Awardees shall be fully capable and willing to electronically transmit proprietary data to the Government. This data may consist of contract deliverables or pricing data required for proposal evaluation. If electronic transmission is required, the Government may establish a secure web site or other means for this purpose. Any software required by the Government to receive the contractor-transmitted proprietary data that the Government does not already possess shall be provided by the contractor at no cost to the Government.
H.7 - CONTRACTOR ACCESS TO PROPOSED TASK ORDER PERFORMANCE SITES
(a) To respond to a Request for Proposals (RFP) for a Task Order awarded under this contract, a contractor may be required to obtain data and other information from the Government at the proposed sites of task order performance. The following general information is provided regarding visits to the proposed Task Order performance site(s). Specific details regarding procedures applicable to the instant requirement will be published with each task order RFP.
(b) The Contractor shall review the RFP for specific instructions and guidance regarding the site visit. The PCO, with the help of the COR, will plan and coordinate the site visit with the on-site Government representative and will notify the contractor with approval to conduct the site visit. Contractors shall comply with security requirements necessary to conduct the site visit.
(c) The Government will determine whether a formal pre-proposal conference or site visit will be held. The decision to hold a formal conference will be dependent upon such things as the complexity of the specific requirement, schedule constraints, etc. Due to the COVID-19 pandemic site visits may be canceled or not scheduled at all. If a formal conference or site visit is not conducted, contractors may be granted individual access for a site visit, as deemed necessary.
(d) Contractors shall not be permitted to contact Government representatives at a performance site to discuss a Task Order RFP without prior approval of the Contracting Officer.
(e) All access to information at a proposed performance site shall be on a not-to-interfere-with-training basis.
H.8 - SECURITY REQUIREMENTS
As required by FAR clause 52.204-2 of the contract, the contractor shall comply with the DOD Manual 5220.22M, “DOD National Industrial Security Program Operations Manual” (NISPOM) which will be used in the development of task order security requirements. A DD Form 254 will be issued at the task order level for specific security requirements, if required. All awardees shall be required to obtain appropriate facilities and personnel security clearances in accordance with any DD Form 254 in support of a task order requirement.
H.9 - SERVICE CONTRACT ACT - WAGE DETERMINATIONS & CBAs
(a) Attached to the Task Orders may be Wage Determinations and/or Collective Bargaining Agreements (CBA) made by the Department of Labor pursuant to the Service Contract Act of 1965 and Section 4.6 of title 29 of the Code of Federal Regulations (CFR). No person employed in the performance of a task order issued under this contract shall be paid less than the minimum monetary wages or be given less fringe benefits than those set forth in said determinations/CBAs.
(b) Each fiscal year, the Government intends to incorporate new wage determinations and/or CBAs into the task orders as provided for by Section 4.6 of 29 CFR. If, as a result of the new Wage Determinations and/or CBA, the Contractor must increase the wages or fringe benefits of employees working on these task orders, the contract's FFP for the instant fiscal year and all options will be adjusted to reflect such increases. The adjustment will be limited to the increases provided for in the Wage Determination and/or CBA and the concomitant increases or decreases in the social security, unemployment taxes, and workmen's compensation insurance. The adjustment shall not include any amount for general and administrative costs, overhead, or profits.
H.10 - MINIMUM AND MAXIMUM QUANTITIES
The contract minimum referred to in paragraph (b) of FAR 52.216-22, "Indefinite Quantities" clause of this contract is a total of $500 worth of orders to each awardee. The maximum quantity is the total "Not to Exceed" amount of $90M which represents the cumulative total of Task Orders awarded under solicitation N6134020R0082 for all CLINs.
H.11 - APPLICABLE NAICS CODE
The size status of an offeror used in determining an organization’s eligibility to compete for a contract in is listed below. Successful awardees eligible to compete for task orders during the first five years of this contract, provided no novation/merger/acquisition activity has occurred that would reclassify them as a large business under this NAICS code. For eligibility purposes, the size status of awardees is subject to change over the life of the ID/IQ contract based on re-representation requirements set forth in FAR Clause 52.219-28 Post-Award Small Business Program Re-representation. Small Business awardees that no longer qualify as a small business in the Set-Aside after re-representation will not be eligible to compete for subsequent task orders.
The following size standard is hereby applied to this solicitation and resultant contract:
North American Industry Classification System (NAICS Code): Size Standard:
541330 Engineering Services (for Aircraft/Weapons Systems) $41.5 Million
H.12 - CLAUSE MODIFICATIONS
Due to potential unforeseen circumstances attributable to requirements solicited under this ID/IQ Contract, the Government reserves the right to add, delete or modify clauses on individual TOs to facilitate specific conditions applicable to the TO. These changes will be applicable to only the individual TO and will be identified within the RFP issued for that individual TO.
H.13 - MULTIPLE AWARD CONTRACT OMBUDSPERSON
The following individual is responsible for reviewing complaints from contractors and ensuring that all contractors are afforded a fair opportunity to be considered for all Task Orders issued in accordance with the contract:
Ms. Cindy Shaver Deputy Assistant Secretary of the Navy (Procurement) 1000 Navy Pentagon, Washington, DC 20350 Phone (703) 614-9600 Fax (703) 614-9394 Email NCAG@navy.mil
| 5252.217-9507 | OVER AND ABOVE WORK REQUESTS (NAVAIR) (OCT 2005) | |
| (a) These procedures apply when the contractor identifies needed repairs that are over and above the requirements of the contract and recommends corrective action during contract performance in accordance with DFARS 252.217-7028, "Over and Above Work". | ||
| (b) The contractor shall prepare and submit the applicable Over and Above Work Request (OAWR) Form similar to the one attached to this contract to the PCO, via the COR, for authorization to proceed. The contractor shall use the OAWR to describe the over and above work that needs to be performed, including any parts and materials, in such detail as necessary to permit a thorough evaluation. The contractor shall attach competitive subcontractor quotes, or, if such quotes are not available, the contractor shall justify the total cost by specifying direct hours by labor category, as well as the type, quantity and cost of the material needed to perform the repair or replacement. The contractor shall also propose a schedule to complete the needed repair or replacement. | ||
| (c) The COR will review the OAWR submitted by the contractor, and then forward the form to the NAWCTSD Task Order Manager with a recommendation of approval or disapproval, with one copy to PCO. The COR will annotate the form with the reasons for the recommendation. | ||
| (d) The PCO shall take one of the following actions: | ||
| (1) Disapprove the OAWR. In this event, the OAWR will be returned to the contractor. A copy will also be provided to the COR. | ||
| (2) Authorize the OAWR. In this event, a modification (Standard Form 30) will be issued. Upon issuance of the modification, the contractor shall proceed with the repair or replacement effort. | ||
| (e) To the maximum extent practical, a FFP will be negotiated for this effort prior to the start of the work. In the event that the urgency of the effort does not permit the negotiation of an FFP, then the authorizing modification will establish not-to-exceed (NTE) prices. A sub-line item, under the OAWR line item, will be established to fund the effort. The Government is not responsible for any costs incurred by the contractor that exceed the NTE price established by the modification. | ||
| (f) Modifications to an OAWR will be effected by Standard Form 30. | ||
| (g) If the OAWR is issued on an NTE basis, the contractor shall promptly submit a proposal for the OAWR to the PCO. The PCO is responsible for negotiating a FFP for the OAWR and issuing an appropriate modification which establishes a FFP for that amount. The definitizing modification should include the following information: | ||
| (1) Reference to the OAWR and modification number and any later modification, which relates to that OAWR. | ||
| (2) The applicable ACRN and fund citation provided in the Accounting and Appropriation Data Block. Any excess funds are to be deobligated. |
The following have been deleted:
| 5252.228-9501 |
| LIABILITY INSURANCE |
| MAR 1999 |
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been added by full text:
SECTION L
L – 1 CONTENT OF PROPOSALS (Services) 5252.215-9522 ALT 1 This provision has been replaced with the fully tailorable Section L provision below.
L – 2 CONTENT OF PROPOSALS (SERVICES) (16 Aug 2020)
PART A GENERAL INSTRUCTIONS
PART A GENERAL INSTRUCTIONS
1.0 GENERAL
1. Offerors are required to submit one proposal with sufficient information concerning all evaluation factors to enable Government personnel to fully ascertain capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s, expertise, experience and capability as required by the solicitation. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are expected to comply with all instructions in the RFP. No price information, (e.g., Dollar Values and/or Hourly Rates) shall be included in any volume other than Volume 5 Price, other than historical pricing information to support prior experience portions of the proposal. Alternate proposals are not acceptable.
2. In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. Do not provide elaborate brochures or other presentation beyond that sufficient to present a complete and effective proposal. It is the responsibility of the Offeror to present enough information to allow Contract Experience, Technical, and Past Performance, as well as Price, to be meaningfully evaluated without discussions. Unsubstantiated statements that the prospective Offeror has experience or has performed work in the past are considered inadequate and may render a rating of unacceptable or No Confidence.
3. Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement where the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture.
4. The Government anticipates awarding MAC basic contracts to between three to five Offerors.
2.0 PROPOSAL FORMAT AND SUBMISSION
1. Proposals must use Times New Roman, 12 pt. normal font (no reduction permitted), single-spaced, 1-inch margins all around, and must be formatted for/printed on standard 8.5 x 11 inch paper. If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages should be numbered with section and page numbers. Tables shall be presented in no smaller than a 10 pt. font. Text utilized in charts, figures, and graphics should also be no smaller than a 10pt font and may use a font type selected by the Offeror. Each Volume shall be provided separate folder.
3.0 ELECTRONIC SUBMISSION OF PROPOSAL
1. This section is intended to provide information to the Offeror on the electronic format and application software to be used for submitting proposals. Use of the software and procedures described in this section will ensure that the proposals received are suitable for reading electronically.
4.0 ELECTRONIC PROPOSAL MEDIA
1. Method of delivery shall be with https://safe.apps.mil. When submitting proposals in safe.apps.mil the recipients shall be as listed below:
a) Name: Charles Mote
b) Email: Charles.mote@navy.mil
2. Offerors are advised the SAFE restricts the maximum file submission to 8 GB. Chrome and Edge are recommended. Internet Explorer limits SAFE uploads to 2GB; therefore, it is not recommended. Offeror shall include the following information in the SAFE upload comments block: Offeror’s name, Solicitation number, primary and alternate points of contact (POC) (include name, email, and telephone number(s) for each POC).
a) Creating a SAFE Drop-off for proposal submission:
i. For “outside or unauthenticated users”:
ii. In order for an outside user to create a drop-off for proposal submission via SAFE, they must receive a drop-off request from Mr. Charles (Tim) Mote. Offeror shall submit the initial request at charles.mote@navy.mil no later than 10 working days in advance of the proposal submission date. Offeror will receive an email with a link to utilize for proposal submission (drop-off) once the request has been processed by the government. This link is good for a one-time proposal submission. Note: this process must be completed twice. The process will be needed one time in support of the early delivery of volume 2 and 3, and one time in support of the delivery of the proposal in full submittal.
b) For CAC Authenticated users”
i. Create a “drop-off” with charles.mote@navy.mil as the recipient.
3. Offerors are hereby notified that the Government will not reimburse for any costs incurred for solicitation preparation.
4. Late Proposals: Offerors are advised that the time identified on Block 9 of the Standard Form (SF) 33 applies. Delivery is defined as having occurred based on the DOD Safe’s email notification time stamp to the charles.mote@navy.mil. If multiple drop offs occur, any drop off after the time identified on Block 9 of the SF 33 is considered “late.” Offerors are strongly encouraged to deliver as early as possible to avoid any risk of late submission.
5. The Offeror shall submit all volumes of its proposal electronically compatible with the operating system and applications defined in Section 5.0 (Operating System and Applications). The Offeror should put as much proposal material as possible on each file, keeping the portions of the proposal that contain pricing information on separate file(s) from the portions of the proposal that do not contain pricing information.
6. Table G-3 (Proposal Structure) identifies the proposal structure for each volume. Each volume should be clearly marked with the Offeror's name and address, the point of contact's name and phone number, the proposal volumes contained therein, and “Source Selection Information – See FAR 2.101 and 3.104”.
5.0 OPERATING SYSTEM AND APPLICATIONS
1. The proposals will be accessed utilizing the Microsoft Windows Operating System. Proposal information shall be submitted using the following applications: Microsoft Word 2016, Microsoft Excel 2016, and Microsoft PowerPoint 2016; however, letters and other signed documents shall be provided as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is prohibited except where specific instructions for non-.pdf or Office 2016 applications are provided.
2. Hyperlinks
a) Offerors may NOT use hyperlinks within and among proposal volumes. Additionally, there shall be no links from volumes that do not contain price information to volumes that do contain price information.
3. Virus Free Electronic Submission
a) Offerors are responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information delivered throughout the evaluation (e.g., original proposal submission, responses to evaluation notices, Final Proposal Revisions) has been checked for viruses and certify that its files are/will be virus free. The Offeror should specify the software, version, and virus definition used to check the data. The Offeror shall not use macro and/or script enabled files.
4. Multimedia and Graphics
a) Large files require greater computer system resources and are discouraged. The Offeror shall not embed sound or video (e.g., MPEG) files within proposal documents. The offeror is encouraged to:
i. Simplify the color palette used in creating figures;
ii. Minimize size of graphics files; and
iii. Avoid scanned images.
5. File Naming Conventions
a. Valid extensions for files using their associated applications are listed below in Table G-1 (file Extensions):
Table G-1 File Extensions
| Type of Application/Files |
| Valid Extensions |
| Portable Document Files |
| Microsoft Word documents |
| .docx |
| Microsoft Excel documents |
| .xlsx |
| Microsoft Power Point |
| .pptx |
6. The Offeror shall follow the basic structure of the file naming convention in Table G-2 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where "#" represents the sequential numbering of files (if needed), and [CAGE] represents the offeror’s CAGE code. Offerors shall keep the file name as short as possible (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names may become corrupt or inaccessible.
7. The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Please submit each volume or annex as one file if possible. Offerors should not provide each section/paragraph as separate files.
8. The Offeror shall ensure that the electronically submitted files are directly traceable to paper copy submittals.
Table G-2 Offeror Electronic File Naming Convention
| Volume Number |
| Title |
| File naming convention * |
| 1 |
| Executive Summary and Contract Administration |
| Vol 1 ES# [CAGE].docx |
| Cover Letter |
| Vol 1 Cover [CAGE].docx |
| 2 |
| Contract Experience (CE) |
| Vol 2 CE# [CAGE].docx |
| CE Applicable Contract For CE Element |
| Vol 2 CE Info [CAGE].xlsx |
| 3 |
| Past Performance |
| Vol 3 PP# [CAGE].docx |
| PP Applicable Contract For PP Element |
| Vol 3 PP Info [CAGE].xlsx |
| 4 |
| Technical |
| Vol 4 TP# [CAGE].docx |
| L-6 Manning Staffing Chart |
| Vol 4 TP-L6 MSC [CAGE].xlsx |
| 5 |
| Price |
| Vol 5 PR# [CAGE].xlsx |
Annexes
| Annex A |
| Final Versions of Previous SOO, SOW, PWSs, or other supporting solicitation or contract documentation for Past Performance and Contract Experience |
| AnnA SOW PWSs# [CAGE].pdf |
AnnA SOW PWSs # [CAGE].docx Please note: The Offeror should provide both a .pdf and .docx version if they are available. If not, a .pdf version only is acceptable.
Notes * File names shall not exceed 40 characters in length inclusive of spaces and file extension.
6.0 PROPOSAL CONTENT AND VOLUMES
1. The Offeror must present its proposal information in a manner that facilitates a one for one comparison between the information presented and Section L proposal instructions. Proposal information must be structured such that its paragraph number/letter corresponds to the Proposal Instructions paragraph number/letter, although the Offeror may add lower tier sub paragraphs.
2. Each volume and annex of the proposal shall be submitted as original electronic copies as specified in Table G-3 (Proposal Structure). The Offeror shall submit all electronic copies of the proposal to the address provided in Section L, Part A, paragraph 7.0. Suggested page counts for each volume, if any, are also specified in Table G-3 (Proposal Structure). The title and table of contents pages, as well as tables, are not included in the suggested page count.
3. Price information, (e.g., dollar values and/or hourly rates) other than historical pricing information to support prior experience portions of the proposal, shall not be included in any volume other than Volume 5 Price.
Table G-3 Proposal Structure
| Volume Number |
| Volume/Annex Title |
| Suggested Pages |
| Electronic Copies Required |
| 1 |
| EXECUTIVE SUMMARY AND CONTRACT ADMINISTRATION |
| 10 |
| 1 Original |
| 2 |
| CONTRACT EXPERIENCE |
| 15 |
| 1 Original |
| 3 |
| PAST PERFORMANCE |
| 15 |
| 1 Original |
| 4 |
| TECHNICAL |
| 20 |
| 1 Original |
| 5 |
| PRICE |
| As Needed |
| 1 Original |
| Annex A |
| Final Versions of Previous SOO, SOW, PWSs, or other supporting solicitation or contract documentation for Contract Experience and Past Performance |
| As Needed |
| 1 Original |
7.0 PROPOSAL SUBMISSION AND PACKAGING
1. All Proposals shall be UNCLASSIFIED.
2. Proposal Submission
3. Clearly mark all SAFE electronic packages as identified in Section 4.0, (a). The submission date for all Volumes of the proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 (Solicitation, Offer and Award) of the solicitation.
4. It is requested that a complete advanced electronic copy of the Offeror’s Volume 2 and 3 be submitted two weeks prior to the submission date/time specified on Standard Form 33 (Block 9). In the follow-on official complete proposal submission, offeror shall state what changes were made to the advanced electronic copy information that was previously submitted, if no changes are made, state so at the beginning of Volume 1 (Executive Summary and Contract Administration), Volume 2 (Contract Experience), and Volume 3 (Past Performance).
5. Offerors will submit electronic copies of the entire proposal in accordance with Table G-3 by date and time shown in Block 9 of the SF33.
8.0 PROPOSAL PACKAGING
1. The electronic files shall be marked “For Official Use Only; and Source Selection Sensitive – See FAR-2.101 and 3.104,” for the intended recipient identified in paragraph 4.0, (a). Method of delivery shall be https://safe.apps.mil. Proposal recipients shall be Name: Charles Mote, Email: Charles.mote@navy.mil.
9.0 CLASSIFIED DATA
1. All proposals must be UNCLASSIFIED.
10.0 SOLICITATION QUESTIONS
1. Solicitation questions shall be emailed to the Contract Specialist, Kelly Stevens, kelly.stevens@navy.mil with a copy to the Contracting Officer, Mr. Rafael Soberal, rafael.soberal@navy.mil. using Attachment L-1, Solicitation Question & Answer Form, and must be received no later than 1400 Eastern Standard Time (EST) on the 10th day after the RFP release date, or the next business day if the 10th day falls on a non-workday. Questions and answers will be provided via a formal RFP amendment. Thus, Offerors are cautioned not to include proprietary information in the questions because the Government may release it to all Offerors. The Government reserves the right not to respond to any questions received concerning this solicitation after the deadline. Accordingly, Offerors are encouraged to carefully review all solicitation requirements and submit questions to the Government early in the proposal preparation cycle.
11.0 CHANGES TO SOLICITATION
1. For any changes and additional information to the solicitation, please go to website: https://beta.sam.gov/ Search the database for the solicitation number N6134020R0082.
PART B SPECIFIC INSTRUCTIONS
1.0 VOLUME 1 –EXECUTIVE SUMMARY AND CONTRACT ADMINISTRATION
1. The purpose of the Executive Summary and Contract Administration volume is to provide the Government with an overview of the Offeror’s entire proposal, excluding price. Each section within the Executive Summary shall contain the salient points contained in each of the proposal volumes. In addition, this volume should be used by the offeror to identify and highlight significant features of its proposal.
2. The Executive Summary and Contract Administration volume should be divided into the sections outlined below:
1.1 CONTRACT ADMINISTRATION
1. The Offeror shall provide the following contract administration information.
2. Offeror Representatives and Information: The Offeror shall provide a summary sheet comprised of the information listed below for the prime or JV and for each member of a JV, if applicable.
a) Prime Contractor.
b) Business Name.
c) Address.
d) Principal point of contact for this solicitation (Name, title, phone number, email).
e) Secondary point of contact for this solicitation (Name, title, phone number, email).
f) Individuals authorized to negotiate with the Government and contractually bind the Offeror (Name, title, phone number, email).
g) Establishment Taxpayer Identification Number (TIN).
h) TIN of Parent Corporation (if applicable).
i) DUNS.
j) CAGE CODE.
k) Business size for this effort (large or small).
3. JV Team Members.
a) Business Name.
b) Address.
c) DCMA point of contact and telephone number, if applicable.
d) DCAA point of contact and telephone number, if applicable.
e) DUNS.
f) CAGE CODE.
4. Government Agency Information:
a) Provide the mailing address, telephone, fax numbers, email address and facility codes for the Offeror’s local Defense Contract Management Agency (DCMA) and Defense Contract Audit Agency (DCAA). In addition, provide the point of contact, telephone number, fax number and email address for the Administrative Contracting Officer (ACO) at DCMA.
5. Terms and Conditions:
a) The Offeror shall provide one of the following two statements in this section.
i. If the Offeror takes any exceptions to the provisions of the solicitation and its applicable documents, the Offeror shall provide the following statement: “All exceptions taken from the solicitation terms, conditions or requirements, including any applicable documents, are included in this section”.
ii. If the Offeror does not take any such exceptions, then the Offeror shall provide the following statement: “No exceptions are taken to the terms and conditions or any requirement of the solicitation.”
b) An exception is where an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions. Offerors shall not take exception to contract terms and conditions. Any exceptions will make the proposal ineligible for award.
c) A deviation is where an Offeror states it will not comply with a solicitation requirement but proposes an alternative to meet the intent of the requirement, usually involving a Statement of Work/Performance Work Statement (SOW/PWS) requirement.
1.2 JOINT VENTURES:
1. If proposing as a Joint Venture, the offeror shall provide a copy of the Joint Venture agreement. In accordance with (IAW) 13 CFR 121.103(h), a joint venture must be in writing and must do business under its own name; must be identified as a joint venture in the System for Award Management (SAM); may be in the form of a formal or informal partnership or exist as a separate limited liability company or other separate legal entity; and, if it exists as a formal separate legal entity, may not be populated with individuals intended to perform contracts awarded to the joint venture (i.e., the joint venture may have its own separate employees to perform administrative functions, but may not have its own separate employees to perform contracts awarded to the joint venture).
1.3 CONTRACT DOCUMENTS:
1. The Offeror shall provide the following documents within this section:
a) Original signed SF33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation. The SF-33 Block 12 “fill-in” (proposal validity date) shall be completed with an amount of no less than 270 days.
b) Signed Representations, Certifications, and Acknowledgements (Section K). To include, statement regarding what changes were made to the advanced electronic copy information per Section L, Part A, paragraph 7.0, b. above.
2.0 VOLUME 2 CONTRACT EXPERIENCE:
Note: This volume shall not contain any reference to the price aspects of the offer.
1. The Offeror shall complete Attachment L-2 according to the instructions within the attachment. Only applicable contract references should be used in completing the attachment.
2.1 CONTRACT EXPERIENCE PASS/FAIL CRITERIA
1. The Offeror shall identify and submit not more than three contract references that collectively meets the 2.1 Contract Experience Pass/Fail Criteria (PFC). Offeror’s shall NOT provide contract references for any subcontractors. Each contract reference shall meet the definition of Recency to be considered further (as defined in Section M). In order to collectively meet the PFC, the offeror’s referenced contracts must individually include at least one of the PFCs and, when combined, the referenced contracts must meet all of the PFCs. The Offeror shall demonstrate that the Volume 2 Contract Experience references submitted for evaluation meet the definition of an Applicable Contract Reference (defined in Section M) and collectively meet the pass/fail criteria specified below:
a. Contract experience demonstrates performance for at least one year as the Prime;
b. Contract experience demonstrates performance of curriculum revision and maintenance (as defined in Attachment J-1 PARCM Scope paragraphs 2.2 and 2.2.1) of U.S. Federal Government operator courseware at two or more sites;
c. Contract experience demonstrates performance of maintenance and operation of Electronic Classroom (Training Delivery System (TDS) as defined in Attachment J-1 PARCM Scope paragraph 4.16) equipment required for delivery of course content for instructor / students;
d. Contract experience demonstrates having contract(s) with the annualized average contract value (see AACV definition in Section M)…
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 .