DRAFT_RFP_Attachment_6_MPSCIV_SectionM_13Dec21.pdf
PDF 472 KB Posted
- Attached to
- Mission Planning Support Contract IV (MPSC IV)
- Solicitation number
- FA8217-22-R-0001
View the file
Other files
Show all 13
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
PART IV- REPRESENTATIONS AND INSTRUCTIONS
SECTION M
EVALUATION FACTORS FOR AWARD
1.1 SOURCE SELECTION
1.2 Basis for Contract Award
This is a competitive best value source selection in which competing offerors' past performance history will be evaluated on a basis significantly more important than price considerations; however price will contribute substantially to the selection decision. This source selection will be conducted in accordance with Federal Acquisition Regulation (FAR) 15.3, Source Selection, as supplemented by the Defense Federal Acquisition Regulation Supplement (DFARS 215.3), and the Air Force Federal Acquisition Regulation Supplement (AFFARS 5315.3). These regulations are available electronically at the following location:
https://www.acquisition.gov. Award will be made to the offeror who is deemed responsible in accordance with FAR Part 9, as supplemented, whose proposal conforms to the solicitation’s requirements (to include all stated terms, conditions, representations, certifications, and all other information required by Section L of this solicitation) and is judged, based on the evaluation factors and subfactors to represent the best value to the Government.
Only proposals found to be technically acceptable will be considered for tradeoff. The tradeoff will occur only between the past performance factor and the price factor. Failure to meet any requirement may result in an offer being determined unacceptable. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The Government seeks to award to the offeror who gives the Air Force the greatest confidence that it will best meet the requirements. This may result in an award to a higher rated, higher priced offeror, where the decision is consistent with the evaluation factors, and the Source Selection Authority (SSA) reasonably determines that the technically acceptable, higher rated past performance of higher priced offeror outweighs the price difference. While the Government source selection evaluation team and the SSA will strive for maximum objectivity, the source selection process, by its nature, is subjective; and therefore, professional judgment is implicit throughout the entire process.
1.3 Award without Discussions
The Government reserves the right to award without discussions. Each initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if the Contracting Officer determines that discussions are necessary.
1.4 Discussions
If, during the evaluation period, it is determined to be in the best interest of the Government to hold discussions, offeror responses to Evaluation Notices (ENs) and the Final Proposal Revision (FPR) will be considered in making the source selection decision. If the offeror’s proposal has been evaluated as acceptable at the time http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/15.htm http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/15.htm http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/15.htm https://www.acquisition.gov./ discussions are closed, any changes or exceptions in the Final Proposal Revision are subject to evaluation and may introduce risk that the offeror’s proposal be determined unacceptable and ineligible for award.
The Government will consider, throughout the evaluation, the "correction potential" of any aspect of an Offeror’s proposal not meeting the Government’s requirements. The judgment of such "correction potential" is within the sole discretion of the Government. If an aspect of an Offeror's proposal is not considered correctable, the Offeror will be eliminated from the competitive range. This determination will be conducted in accordance with FAR 15.306.
1.5 Number of Contracts to be Awarded
The Government intends to award one contract for the Mission Planning Support Contract IV (MPSC IV);
however, the Government reserves the right to award no contract at all, depending on the quality of the proposals, prices submitted, and the availability of funds.
1.6 Solicitation Requirements, Terms and Conditions
Offerors must meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as factors or subfactors. Failure to comply with the terms and conditions of the solicitation may result in the offeror being ineligible for award.
Offerors must clearly identify any exception to the solicitation terms and conditions and must provide complete supporting rationale. The Government reserves the right to determine any such exceptions unacceptable. By submission of its offer, the offeror agrees to all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors.
2.1 EVALUATION FACTORS
2.2 Evaluation Factors and Subfactors
The following evaluation factors and subfactors will be used to evaluate each proposal: Award will be made to the offeror most advantageous to the Government based upon an integrated assessment of the evaluation factors and subfactors described below.
Factor 1: Technical
Subfactor 1: Program Management Subfactor 2: Support of MPSSF Subfactor 3: System Support Representatives
Factor 2: Past Performance Factor 3: Price
2.3 Relative Importance of Factors and Subfactors
The relative importance of each factor and subfactor is as follows: Factor 1 (Technical) is rated as acceptable/unacceptable. Within the Technical Factor, the subfactors are approximately equal in importance.
Past Performance and Price are listed in descending order of importance with Factor 2 (Past Performance) being most important, Factor 3 (Price) is last in importance.
In accordance with FAR 15.304(e), all evaluation factors other than Price, when combined, are significantly more important than price.
3.1 FACTOR 1: TECHNICAL
The Government’s technical evaluation team shall evaluate the technical proposals on an acceptable or unacceptable basis, assigning one of the ratings described below for each subfactor. The ratings are described in DoD Source Selection Procedures, Table C-1 – Technical Acceptable/Unacceptable Rating Method, excerpted below.
TECHNICAL ACCEPTABLE/UNACCEPTABLE RATING METHOD
Adjectival Rating Description
Acceptable Proposal meets the requirements of the solicitation.
Unacceptable Proposal does not meet the requirements of the solicitation.
Any subfactor, or portion of a subfactor, rated as “Unacceptable” will render the entire proposal unacceptable and, therefore, unawardable. Only those proposals rated to be technically acceptable, either initially or as a result of discussions, will be considered for award. However, the offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.
The proposals shall be evaluated against the following technical subfactors:
Subfactor 1: Program Management Subfactor 2: Support of MPSSF Subfactor 3: System Support Representatives
3.2 Subfactor 1: Program Management
Description: This subfactor evaluates the offeror’s proposed program management approach for human resources, cybersecurity and information assurance, security clearance, OCONUS personnel, and transition as required by the Performance Work Statement (PWS).
This subfactor is met when the evaluation of the offeror’s proposal conveys a technically sound approach that meets the requirements in the PWS and substantiates all of the following:
file://Periwinkle/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b15304 http://www.acq.osd.mil/dpap/policy/policyvault/USA007183-10-DPAP.pdf
3.2.1 Human Resources – The Government will evaluate for a sound, feasible, and compliant approach that demonstrates, through explicit evidence and examples, the processes for recruiting, hiring, training, and staffing, including the Staffing Table in Attachment L-10, IAW PWS.2.1.1.1. The recruiting and hiring approach must demonstrate, through explicit evidence and examples, the offeror’s ability to hire and retain qualified personnel. Training approach must demonstrate to the government the offeror’s ability to train personnel on applicable position specific duties. The contractor must complete the Staffing Table in Attachment L-10. The table must identify how the offeror proposes to organize and staff all positions/functions in accordance with the requirements/tasks in the PWS.
3.2.2 Cybersecurity and Information Assurance (IA)– The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s ability to provide cybersecurity and maintain certifications IAW the PWS and the current versions of DoD and Air Force Information Assurance requirements (including, but not limited to, DoDI 8500.01 (Mar 14, 2014), DoDI 8510.01 (March 12, 2014; Incorporating Change 1, May 24, 2016) and DoD 8570.01-M (December 19, 2005; Incorporating Change 4, Nov 10, 2015) IAW PWS 2.9.1, 2.9.2, 2.9.3, 2.9.4. The Government will evaluate for a sound, reasonable, and complaint approach that demonstrates the offeror’s ability to perform RMF/ACAS Scanning IAW PWS 2.8.1, 2.9.3, current/real-time fielded system configuration tracking and reporting/and monitoring IAW PWS 2.3.1.3 and patch mitigation IAW PWS 2.3.1.3, 2.5.1.11, 2.9.3, 2.10.3, 2.11.4 processes with cybersecurity for online and offline systems that also includes cloud computing and edge server support/management IAW 2.4, 2.4.3, 2.4.3.1, 2.12.2.9.
3.2.3 Security Clearance – The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s practices and procedures for obtaining and maintaining required security clearances for personnel and facilities IAW applicable DoD and USAF directives and instructions (including, but not limited to 5 CFR 732 and Executive Order 12968) IAW PWS 2.1.1.5, 2.11.1.3.
3.2.4 OCONUS Personnel - The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s ability to place, train (specific country and theater) and support permanent and temporary personnel in OCONUS locations. This includes the processes for obtaining various documentation required by the US Department of State, Department of Defense, and host countries (i.e.
visas and country clearances, Status of Forces Agreements (SOFAs), as well as Technical Expert Status Agreements (TESAs), and International Traffic in Arms Regulations (ITARs) exemptions) IAW PWS, 2.1.1.6, 2.3, 2.4, 2.10.
3.2.5 Transition – The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s strategy to transition all contract activities and personnel from the incumbent to the awardee within 30 calendar days of the start of the initial task order. This includes transition of Government Furnished Property (GFP)/Government Furnished Equipment and personnel, if applicable, within the transition period IAW PWS 4.1.
3.3 Subfactor 2: Support of Mission Planning System Support Facility (MPSSF)
Description: This subfactor evaluates the offerors proposed approach for support of the Mission Planning System Support Facility to include Mission Planning Central, deficiency investigation process, operational user and SSR training, and fielding events as required by the Performance Work Statement (PWS).
This subfactor is met when the evaluation of the offeror’s proposal conveys a technically sound approach that
3.3.1 Mission Planning Central (MPC) Support - The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s proposed plan to support and maintain MPC operations IAW PWS 2.11. This plan must include the maintenance of the existing functionality IAW PWS 2.11, establishment of an Integrated Product Team (IPT) to manage Change Enhancement Requests (CERs) IAW PWS 2.11.1.8 and 2.11.5, provide MPC system software security IAW PWS 2.11.2, 2.11.3, 2.11.4, and provide MPC training to users, developers, testers, and program managers IAW PWS 2.11.3, 2.11.5.2, 2.11.5.2.9, 2.11.5.2.13, 2.12.4.
3.3.2 Deficiency Investigation Process – The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s proposed plan to identify Mission Planning Environment (MPE) deficiencies and manage the process IAW T.O. 00-35D-54 (August 1, 2015) and PWS 2.4.1.1. The approach shall address the performance of Screening Point duties IAW PWS 2.5.1.6 and TO 00-35D-54, and the specific processes and personnel used to identify potential deficiencies, report deficiencies to the appropriate government personnel within 24 hours for Category I and 48 hours for Category II deficiencies, and shall provide an acceptable centrally accessible tool for tracking the status of the reported problem to closure.
Mission Planning has a waiver for the Joint Deficiency Reporting System (JDRS), and the current tool is the Enterprise Deficiency Reporting (EDR) tool located on MPC, however the contractor may propose an alternate solution provided it meets the requirements of T.O. 00-35D-54.
3.3.3 Foreign Military Sales Support – The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s proposed plan for providing worldwide support for FMS allied countries. The approach shall address the plan to accomplish necessary travel both within the Continental United States (CONUS) and Outside Continental United States (OCONUS) IAW PWS 2.10.1, 2.10.2.
3.4 Subfactor 3: System Support Representatives (SSRs)
Description: This subfactor evaluates the offerors proposed approach for support of System Support Representatives to include worldwide support, deployed units, mission planning environment configuration control, and operational tests as required by the Performance Work Statement (PWS).
This subfactor is met when the evaluation of the offeror’s proposal conveys a technically sound approach that
3.4.1 Worldwide Support – The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s proposed plan for worldwide support for a minimum of 150 geographically separated locations. The approach must demonstrate the offeror’s ability to ensure SSRs at each location are performing duties, as required by the IAW PWS 2.3, 2.3.1.3.17.
3.4.2 Support for Deployed Units – The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s proposed plan for supporting activities required prior to, and during, a unit’s deployment. The offeror must include a proposed approach for “building” MPEs that will be taken by the unit during the deployment, updating systems while they are deployed (to include the use of organic government personnel or the offeror’s personnel, if authorized by the government), and how the unit can begin getting user support for mission planning within two (2) hours of initial contact, if the SSR is not deployed with the unit IAW PWS 2.2, 2.2.3, 2.2.4, 2.3, 2.3.1.3.13. User support may include, but is not limited to, contacting the MPSSF, initiating/generating warranty actions, repair actions/reports, tracking and reporting issue resolution(s).
3.4.3 Mission Planning Environment (MPE) Configuration Control – The Government will evaluate for a sound, feasible, and compliant approach that demonstrates the offeror’s proposed process to maintain configuration control for all fielded and certified MPEs IAW PWS 2.2.3, 2.3.1.3.1, 2.3.1.3.2, 2.3.1.3.3. The plan must address: the communication between the applicable MPSSF functions and SSRs IAW PWS 2.3, 2.4, 2.5, 2.7.1.4, 2.10.3); use of MPE Letters and MAJCOM Certification Letters to ensure MPEs are functional and related systems remain interoperable IAW PWS 2.5.1.2, 2.5.1.5, 2.10.1, 2.10.1.10; SSRs implementation and maintenance procedures and practices for loading new or updated mission planning data (i.e. charts, mapping updates and aeronautical information) IAW PWS 2.3.1.3.7, and include submitting configuration data to ensure ability for currency tracking capability/real time reporting.
3.4.4 Support for Operational Test – The Government will evaluate for a sound, feasible, and compliant approach to the offeror’s proposed plan for SSR participation in operational test events IAW PWS
2.3.1.3.16. The plan must address how the SSR will be trained on the systems administration for the new MPE prior to the test event IAW PWS 2.3.1.3.16.
4.1 FACTOR 2: PAST PERFORMANCE
The Government shall evaluate the offeror’s past performance as set forth below. The Past Performance evaluation will result in an assessment of the offeror’s probability of meeting the solicitation requirements.
4.2 Ratings
The Government will evaluate the Past Performance factor and will assign a performance confidence assessment rating for each offeror in accordance with the DoD Source Selection Procedures, Table 5 – Performance Confidence Assessments, as excerpted in the Performance Confidence Assessment Rating Method table below.
PERFORMANCE CONFIDENCE ASSESSMENT RATING METHOD
Adjectival Rating Description
SUBSTANTIAL
CONFIDENCE
Based on the offeror’s recent/relevant performance record, the Government has a high expectation that the offeror will successfully perform the required effort.
SATISFACTORY
CONFIDENCE
Based on the offeror’s recent/relevant performance record, the Government has a reasonable expectation that the offeror will successfully perform the required effort.
NEUTRAL
CONFIDENCE
No recent/relevant performance record is available or the offeror’s performance record is so sparse that no meaningful confidence assessment rating can be reasonably assigned. The offeror may not be evaluated favorably or unfavorably on the factor of past performance.
LIMITED
CONFIDENCE
Based on the offeror’s recent/relevant performance record, the Government has a low expectation that the offeror will successfully perform the required effort.
NO
CONFIDENCE
Based on the offeror’s recent/relevant performance record, the Government has no expectation that the offeror will be able to successfully perform the required effort.
4.3 Evaluation Process
The past performance evaluation considers each offeror’s demonstrated recent and relevant record of performance in supplying products and services that meet the contract’s requirements. Performance confidence is assessed at the overall Past Performance factor level after evaluating aspects of the offeror’s recent past performance, focusing on performance that is relevant to the Technical subfactors and Price factor taking into consideration their relative order of importance stated in paragraph 2.3. The Government may consider past performance in the aggregate in addition to on an individual contract basis. In conducting the Past Performance evaluation, the Government reserves the right to use both the information provided in the offeror’s Past Performance proposal volume and information obtained from other sources available to the Government, to include, but not limited to, the Past Performance Information Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information System (FAPIIS), Electronic Subcontract Reporting System (eSRS), or other databases; interviews with Program Managers, Contracting Officers and Fee Determining Officials; the Defense Contract Management Agency (DCMA), and commercial sources.
The offeror will use the PPI Tool described in Attachment L-3 for submittal of past performance information. The offeror may submit three (3) relevant contracts for the prime offeror, and up to three (3) for each key partner and / or each subcontractor.
4.4 Recency Assessment
An assessment of the past performance information will be made to determine if it is recent. To be recent, the effort must be ongoing (with at least one full year of performance history) or must have been performed during the past five years from the date of issuance of this solicitation. Past performance information that fails this condition will not be evaluated.
4.5 Relevancy Assessment
The Government will conduct an in-depth evaluation of all recent performance information obtained to determine how closely the products provided/services performed under those contracts relate to the Technical subfactors and Price factor, including their relative order of importance (reference paragraph 2.3). For each recent past performance citation reviewed, the relevance of the work performed will generally be assessed for the Technical subfactors and Price Factor (however, all aspects of performance that relate to this acquisition may be considered). Relevant performance includes performance of efforts involving systems that are similar to or greater in scope, magnitude, and complexity than the effort described in this solicitation. Consideration will be given to scope (service similarity, diversity of locations/tasks, and contract scope and type), magnitude, and complexity. A relevancy determination of the offeror’s past performance will be made based upon the aforementioned considerations, including joint venture partner(s) and major and critical subcontractor(s). In determining relevancy for individual contracts, consideration will be given to the effort, or portion of the effort, being proposed by the offeror, teaming partner, or subcontractor whose contract is being reviewed and evaluated. The past performance information provided by the offeror and information obtained from other sources will be used to establish the degree of relevancy of past performance. The Government will use the following relevancy definitions when assessing recent, relevant contracts (DoD Source Selection Procedures, Table 4) and Section M Table 1:
Past Performance Relevancy Rating Method
Adjectival Rating Definition VERY RELEVANT Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires RELEVANT Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.
SOMEWHAT
RELEVANT
Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.
NOT RELEVANT Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.
Scope, magnitude and complexity will be assessed based on the prime or subcontractor/teaming partners proposed role or effort as it relates to the past performance effort. The Government may or may not use all or some of the following to determine the elements examined within scope, magnitude and complexity:
Scope: Relevancy in regard to scope may be assessed based on, but not limited to, the similarities of the Past Performance effort and the services required in the PWS. Consideration may be given to the following elements when determining scope of past performance.
1. Ability to hire and retain a geographically separated workforce providing worldwide hardware/software support
2. Ability to place, train and support personnel overseas
Magnitude: Relevancy in regard to magnitude may be assessed based on, but not limited to, the similarities of the Past Performance effort and the services required in the PWS. Consideration may be given to the following elements when determining magnitude of past performance.
1. Number of geographically separated locations supported
2. Number of OCONUS locations supported
3. Number of systems supported
Complexity: Relevancy in regard to complexity may be assessed based on, but not limited to, the similarities of the Past Performance effort and the services required in the PWS. Consideration may be given to the following elements when determining complexity of past performance.
1. Ability to provide a workforce requiring Secret, Top Secret, and TS/SCI security clearances
2. Ability to perform cybersecurity IAW DODI 8500.01, 14 Mar 2014, or previous version (including
Risk Management Framework (RMF) for DoD Information Technology (IT) IAW DODI 8510.01, 12 Mar 2014, or previous version) with a certified workforce IAW DOD 8570.01-M, change 4, 10 Nov 2015 or previous version
4.6 Performance Quality Assessment
The Government will consider the performance quality of recent, relevant efforts (how well the contractor performed on the contracts). For each recent, relevant past performance effort reviewed, the performance quality of the work performed will be assessed for the Technical subfactors and Price Factor (however, all aspects of performance that relate to this acquisition may be considered. The quality assessment consists of an in-depth evaluation of all past performance information available, regardless of its source. The quality assessment may result in positive or adverse findings. Adverse is defined as past performance information that supports a less than a quality assessment satisfactory rating on any evaluation element or any unfavorable comment received from sources without a formal rating system. For adverse information identified, the evaluation will consider the number and severity of the problem(s), mitigating circumstances, and the effectiveness of corrective actions that have resulted in sustained improvements. Process changes will only be considered when objectively measurable improvements in performance have been demonstrated. The Government will use the following quality assessment ratings when assessing recent, relevant efforts:
Quality Assessment Rating
Quality Assessment Rating/Color
Description
EXCEPTIONAL (E)/
BLUE
During the contract period, contractor performance is meeting (or met) all contract requirements and consistently exceeding (or exceeded) many. Very few, if any, minor problems encountered. Contractor took immediate and effective corrective action.
VERY GOOD (VG)/
PURPLE
During the contract period, contractor is meeting (or met) all contract requirements and consistently exceeding (or exceeded) some. Some minor problems encountered.
Contractor took timely corrective action.
SATISFACTORY(S)/
GREEN
During the contract period, contractor performance is meeting (or met) all contract requirements. For any problems encountered, contractor took effective corrective action.
MARGINAL (M)/
YELLOW
During the contract period, contractor performance is not meeting (or did not meet) some contract requirements. For problems encountered, corrective action appeared only marginally effective, not effective, or not fully implemented. Customer involvement was required.
UNSATISFACTORY
(U)/RED
During the contract period, contractor performance is failing (or fail) to meet most contract requirements. Serious problems encountered, corrective actions were either ineffective or non-existent. Extensive Customer oversight and involvement was required.
NOT APPLICABLE
(N)/WHITE
Unable to provide a rating. Contract did not include performance for this aspect. Do not know.
4.7 Assigning Ratings
As a result of the relevancy and quality assessments of the recent contracts evaluated, offerors will receive an integrated performance confidence assessment rating. Although the past performance evaluation focuses on performance that is relevant to the Technical subfactors and Price factor, the resulting performance confidence assessment rating will be made at the factor level and represents an overall evaluation of contractor performance.
Offerors without a record of recent/relevant past performance, or for whom information on past performance is so sparse that no meaningful confidence assessment rating can be reasonably assigned, will not be evaluated favorably or unfavorably on past performance. In such cases, the offeror’s past performance is considered unknown and will be assigned a performance confidence rating of “Neutral” for the Past Performance factor.
More recent and relevant performance will have a greater impact on the Performance Confidence Assessment than less recent or relevant effort. A strong record of relevant past performance resulting in a rating of “Substantial Confidence” or “Satisfactory Confidence” may be considered more advantageous to the Government than a "Neutral Confidence" rating. Likewise, a more relevant past performance record may receive a higher confidence rating and be considered more favorably than a less relevant record of favorable performance. Although the SSEB may not rate an offeror that lacks recent, relevant past performance favorably or unfavorably with regard to past performance, the SSEB may recommend and the SSA may determine, that a “Substantial Confidence” or “Satisfactory Confidence” past performance rating is worth more than a “Neutral Confidence” past performance rating. Past Performance proposals which receive a rating of Limited Confidence or No Confidence, may be considered unawardable.
5.1 FACTOR 3: PRICE
5.2 Evaluation Criteria
The pricing criteria used for evaluation of the Price Factor will be (1) Reasonableness, (2) Balance, and (3) Total Evaluated Price (TEP).
5.3 Reasonableness
The offeror’s Price proposal will be evaluated to ensure it is fair and reasonable, pursuant to FAR 15.404. For additional information see FAR 31.201-3.
5.4 Balanced Pricing
The Government will analyze proposals to determine whether they are balanced with respect to prices, variable quantity matrix factors, and separately priced line items in accordance with FAR 15.404-1. An offer may be rejected if the contracting officer determines that the lack of balance poses an unacceptable risk to the Government.
5.5 Total Evaluated Price (TEP)
The offeror’s TEP will be computed using the Section J-Pricing Table file and will account for the 10.5-year ordering period and possible 11-year period of performance, including options, and for the FAR Clause 52.217- 8, Option to Extend Services, multiplied by government-determined notional quantities and locations, including Not -To-Exceed (NTE) prices. Offeror’s shall follow the Section-J Pricing Table “Instructions” tab when completing the Pricing Table. The TEP is for award purposes only and does not become a contractually binding amount after contract award; however, the unit prices within the Pricing Table will be contractually binding.
All notional quantities and locations will not be disclosed to the offerors. The offeror’s TEP will be the sum of the following:
5.5.1. The Firm Fixed Price (FFP) CLINs 0001, 1001, and 2001, utilizing offeror proposed prices multiplied by government determined notional quantities and locations, including Not -To-Exceed (NTE) prices.
5.5.2. The Cost Reimbursable (CR) Travel (CLINs 0002, 1002, and 2002) and Material (CLINs 0003, 1003, and 2003) shall not be proposed at this time and will not be evaluated as part of the TEP but will be reviewed for price reasonableness at the task order level. The Government will establish a ceiling price for these CLINs on each Task/Delivery Order and will verify that all travel is billed in accordance with FAR 31.205-46.
5.5.3. The Not Separately Priced (NSP) Data CLINs 0004, 1004, and 2004 shall have costs for these CLINs included in the other proposed prices.
5.5 Evaluation of Compensation for Professional Employees
In accordance with FAR 52.222-46, the Government will evaluate the offeror’s Professional Employee Compensation Plan to ensure that it reflects a sound management approach and understanding of the contract requirements and allows the offeror to obtain and keep suitably qualified personnel to meet mission objectives.
The offeror shall detail the base labor rate, fringe, all other burdens, and profit/fee contained in labor rates, and overall benefits to facilitate comparisons in accordance with FAR 52.222-46. Lowered compensation for essentially the same professional work may impair the offeror’s ability to attract and retain competent professional service employees. This may be viewed as evidence of failure to comprehend the complexity of the contract requirements which may lead to rejection of the proposal.
5.6 Approved Accounting System
The Government will evaluate the offeror and all related entities (e.g. subcontractors, teaming partners, interdivisional orders, etc.) as to whether the offeror and all related entities possess a Government approved accounting system. As portions of the work issued under this contract will be other than fixed price, the offeror and all related entities that will be issued other than fixed price type work shall have Government approved accounting systems. Failure to obtain Government approval of all necessary accounting systems may result in the offeror being found ineligible for award.
6.1 CONTRACT DOCUMENTATION
Volume V will be evaluated for overall completeness and any exceptions taken to the terms and conditions of the solicitation/attachments. Failure to provide the requested information or meet a requirement may result in an offeror being ineligible for award.
6.1.1 Model Contract/Representations and Certifications
This requirement is met when the offeror's proposal includes a signed copy of the Model Contract, and Sections A through K. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award.
6.1.2 Section A - Solicitation/Contract Form
This requirement is met when completion of blocks 13 and 15 and signature and date for block 27 of the SF 1447 are included in the offeror’s proposal. Signature by the offeror on the SF 1447 constitutes an offer, which the Government may accept. In signing the SF 1447, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K.
The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.
6.1.3 Section B - Supplies or Services and Prices/Costs
This requirement is met when the offeror has completed the Pricing Table in accordance with the instructions tab found in the Pricing Table File. All requested cells and tabs should be completed as indicated in the Pricing Table File instructions.
6.1.4 Section I - Contract Clauses
This requirement is met when the offeror has completed the necessary fill-ins in Section I and submitted only pages that require a fill-in. The offeror shall comply with the clauses specified within Section I of the Model Contract.
Furthermore, any reference of a clause and/or provision in the solicitation will be adhered to and included in the resulting contract. All laws, regulations, and statutory authorities will also be applied within the model contract.
6.1.5 Section K - Representations, Certifications, and other Statements of Offerors or Respondents This requirement is met when the offeror has provided and completed all representations, certifications, acknowledgments, and statements.
6.2 Exceptions to Solicitation Requirements
Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offeror being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 4.
Table 4 - Solicitation Exceptions
Solicitation Document Page/Paragraph Requirement/Portion Rationale
PWS, Model Contract, ITO, etc.
Applicable Page and Paragraph Numbers
Identify the requirement or portion to which exception is taken
Describe why the requirement can/ will not be met
6.3 Other Information Required
6.3.1 Authorized Offeror Personnel
This requirement is met when the offeror has provided the name, title, email address 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.
6.3.2 Government Offices
This requirement is met when the offeror has provided 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).
6.3.3 Company/Division Address, Identifying Codes, and Applicable Designations This requirement is met when the offeror has provided the following information: company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small). This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.
6.3.4 Attachments to the Model Contract
This requirement is met when the offeror has provided the following as attachments to the model contract:
6.3.4.1 GFP and/or Base Support Requirements
The Government plans to provide the items listed in the Government-Furnished Property (GFP) attachment of Section J of the solicitation. If the offeror requires the use of Government furnished items other than those specified, the offeror shall provide a listing including quantity, federal stock number, nomenclature, date needed and duration of availability, rental value per FAR 45.1 and 45.2, reason for need, and cross reference to cost/price volume paragraphs which pertain to GFP and/or base support. The offeror shall also provide the written authorization from the cognizant ACO, as applicable. The offeror shall supply this information in the format shown in Table 5.
Table 5 - Required Information for Using GFP/Base Support Quant ity Federal Stock #
Nomenclature Duration of Need
Rental Value
Reason for Need
Cross Ref. to Cost Prop
2 EA FS156-
09-234
ACG-1372
Time Counter
1 Oct 03 - 30 Dec 04
$1,000 To calibrate our 5 MHz/ 1pps SATCOM sim. offset
Volume IV, pages 23 – 27, paras A-C
6.3.4.2 Applicable Documents
A list of Applicable Documents has been provided to the offerors as an annex to the PWS attachment in the solicitation, which includes a minimum list of Government Compliance Documents. The offeror shall provide a list of any offeror, industry, commercial, and tailored Government standards, specifications, processes, and/or practices selected as compliance documents. The offeror shall also provide a list of all Government compliance documents intended to be used as compliance documents during the course of this contract. The offeror shall submit a list of these documents, including any tailoring instructions, as an annex to the proposed PWS. The offeror shall submit the completed Proposed Compliance Documents as part of Volume V.
| 1.1 SOURCE SELECTION |
| 1.3 Award without Discussions |
| 1.4 Discussions |
| 1.5 Number of Contracts to be Awarded |
| 1.6 Solicitation Requirements, Terms and Conditions |
| 2.1 EVALUATION FACTORS |
| 2.3 Relative Importance of Factors and Subfactors |
| 3.1 FACTOR 1: TECHNICAL |
| 3.2 Subfactor 1: Program Management |
| 3.3 Subfactor 2: Support of Mission Planning System Support Facility (MPSSF) |
| 3.4 Subfactor 3: System Support Representatives (SSRs) |
| 4.1 FACTOR 2: PAST PERFORMANCE |
| 4.2 Ratings |
| 4.3 Evaluation Process |
| 4.4 Recency Assessment |
| 4.5 Relevancy Assessment |
| 4.6 Performance Quality Assessment |
| 4.7 Assigning Ratings |
| 5.1 FACTOR 3: PRICE |
| 5.3 Reasonableness |
| 5.4 Balanced Pricing |
| 5.5 Total Evaluated Price (TEP) |
| 5.5 Evaluation of Compensation for Professional Employees |
| 5.6 Approved Accounting System |
| 6.1.1 Model Contract/Representations and Certifications |
| 6.1.2 Section A - Solicitation/Contract Form |
| 6.1.3 Section B - Supplies or Services and Prices/Costs |
| 6.1.4 Section I - Contract Clauses |
| 6.2 Exceptions to Solicitation Requirements |
| 6.3 Other Information Required |
| 6.3.2 Government Offices |
| 6.3.4 Attachments to the Model Contract |
| 6.3.4.1 GFP and/or Base Support Requirements |
| 6.3.4.2 Applicable Documents |
File details come from the government source that posted it. Updated .