TACCOM_II_TC2_Proposal_Workbook_A0010.Final.xlsx

TC2 - Cover Page

Do not enter data in columns marked, "For Government Use Only."

Offerors should not modify the template format. Do not remove cells, do not add rows or columns.

Use one workbook per Technical Category submission.

- TAB F1: Compliance requirements are not limited to those provided in Tab F1. Offerors are advised to adhere to all instructions of this solicitation.

- Refer to the TACCOM II Individual Small Business Subcontracting Plan Template to deliver proposals responsive to Factor 2, Individual Small Business Subcontracting Plan.

- TAB F3: No data should be entered in Tab F3. Refer to the Services Pricing Template for meeting the requirements of Factor 3, Technical Acceptability

- Tab F5(A), (B) and(C): The Offeror's checklist responses and data submitted in this tab will be used to determine whether a Relevant Experience project complies with the instructions and qualification criteria expressed in the RFP, and whether the project meets the relevance criteria of Factor 5. Any documentation submitted in response to the RFP may be assessed by the Government to validate reference project qualification and relevance.

- No data should be entered in Tab F6 Instructions

FOR GOVERNMENT USE ONLY:

F1 - General Compliance TC2

10 L.7.1.1 e. Cover Letter provides certification of Small Business Size Standard, if applicable CompanyName.VOL1.CoverLetter.TC2.pdf

11 L.7.1.1 f. Cover letter specifies the proposal acceptance period (min 120 calendar days from submission) CompanyName.VOL1.CoverLetter.TC2.pdf

12 L.7.1.1 g. First or title page shall also be in accordance with FAR 52.215-1, paragraph (c)(2): CompanyName.VOL1.CoverLetter.TC2.pdf

13 L.7.1.1 (i) Includes the solicitation number; CompanyName.VOL1.CoverLetter.TC2.pdf

14 L.7.1.1 (ii) The name, address, and telephone and facsimile numbers of the offeror (and electronic address if available); CompanyName.VOL1.CoverLetter.TC2.pdf

15 L.7.1.1 (iii) A statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation and agreement to furnish any or all items upon which prices are offered at the price set opposite each item; CompanyName.VOL1.CoverLetter.TC2.pdf

16 L.7.1.1 (iv) Names, titles, and telephone and facsimile numbers (and electronic addresses if available) of persons authorized to negotiate on the offeror’s behalf with the Government in connection with this solicitation (expressly stated); and CompanyName.VOL1.CoverLetter.TC2.pdf

17 L.7.1.1 (v) Name, title, and signature of person authorized to sign the proposal (expressly stated). Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, unless that evidence has been previously furnished to the issuing office. CompanyName.VOL1.CoverLetter.TC2.pdf

18 L.7.1.2 Provide executed (Signed) SF-1449 submitted in PDF format, including Offeror DUNS and CAGE, CompanyName.VOL1.SF1449.pdf CompanyName.VOL1.SF30-(amendment #, A0001, A0002, A0003, A0004, A0005, A0006, A0007, A0008, and A0009).pdf 19 L7.1.2 Offeror's Legal Name and Address in Block 17a on the SF1449 must match the information in SAM.GOV including the CAGE Code and DUNS Number CompanyName.VOL1.SF1449.pdf CompanyName.VOL1.SF30-(amendment #, A0001, A0002, A0003, A0004, A0005, A0006, A0007, A0008, and A0009).pdf 20 L.7.1.2 Provide executed (Signed) SF-30s submitted in PDF format, for A0001, A0002, A0003, A0004, A0005, A0006, A0007, A0008, and A0009. CompanyName.VOL1.SF1449.pdf CompanyName.VOL1.SF30-(amendment #, A0001, A0002, A0003, A0004, A0005, A0006, A0007, A0008, and A0009).pdf 21 L.7.1.2 The Name, Title, Signature and Date identified in Block 30b must be an authorized representative with authority to commit the Offeror to contractual obligations. CompanyName.VOL1.SF1449.pdf CompanyName.VOL1.SF30-(amendment #, A0001, A0002, A0003, A0004, A0005, A0006, A0007, A0008, and A0009).pdf

CompanyName.VOL2.TC2.ScoringWorksheet.pdf

F3 - Tech Acceptability

RESERVED

F5(A) RE Qualification

Relevant Experience Qualification Checklist

Reference IDV: In the yellow fill space below, enter Reference IDV (if award was against an IDIQ/BPA).

Obligated Amount: In the yellow space below, enter the Obligated Amount of the Relevant Experience contract supporting this Relevant Experience Project. If it is a collection of orders enter the sum of the obligated amount for all orders.

Contracting Agencies: In the yellow space below, enter Contracting Agency(ies) (or State/Local Government entity) for which work was performed.

Agency Point of Contact: In the yellow fill space below enter the name and email address of the cognizant Contracting Officer (or equivalent position for State/Local). If the Relevant Experience Project is a collection of orders enter the name and email of the cognizant Contracting Officer who signed the order with the largest funded dollar value.

If Award ID is submitted more than once, the data from the first appearance by Relevant Experience Project Number will be used. Subsequent data will not be considered and all points supported by subsequent data will be deducted from the offerors self-score. This standard applies across both TacCom II technical categories.

2 If submitting a collection of orders as a project, confirm all orders among a "collection of orders" are sourced from the same Reference IDV.

Orders that are added to the Relevant Experience Project that do not reference the same IDV will have all associated data removed from consideration.

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

3 Qualifying Award Type

Enter Qualifying award type from one of the following: (1) a single contract; (2) a single task or delivery order awarded under a Multiple Award contract (as defined below); (3) a single task or delivery order awarded under a master Single Award Indefinite Delivery Delivery/Task Order contract (Definite Quantity, Requirements, or Indefinite Quantity) contract (FAR 16.5); (4) a single delivery/task order placed under a Federal Supply Schedule contract (FAR 8.405-2); (5) a single task or delivery order placed under a master Multiple Award Blanket Purchase Agreement, or (6) a single task or delivery order placed under a master Single Award Blanket Purchase Agreement (BPA)(FAR 8.405-3); or (7) a collection of orders.

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

4 Confirm the fully executed (Contracting Officer signed) award document (SF 1449, or equivalent and modifications) is attached. For a collection of orders, each order must be fully executed. RFP L.7.2.3.1

Any contract document that is not fully executed may be removed from consideration and all points supported by that document and other corresponding data will be deducted from the offerors self-score. Offerors may address an unsigned contract or order via the CO certification process according to the instructions in this checklist as well as the direction described in L.7.2.2.

5 Confirm the Contracting Agency is a federal agency, state government, or locality in the United States. (OCONUS for federal agency submission is acceptable if work was in a foreign nation but on a US government base/installation)

Any contract submitted to support a Relevant Experience Project that is not from a Federal, State or Local Government entity will not be considered and all points supported by that document will be deducted from the offerors self-score.

6 Confirm that the total obligated amount is greater than $150K. For a collection of orders, the cumulative obligated amount for the collection of orders must be greater than $150K.

Federal award documents should contain a government funding/appropriation number associated with a dollar amount on the signed contract document. If there are multiple mods then the obligated amount should be the cumulative of those mods. Where a fully executed award document does not contain a funding/appropriation number, offeror may clarify the missing data by following the instructions at the top of this checklist. Offerors submitting State/Local contracts to support a relevant experience project must ensure the documents clearly state what is funded for actual work versus what is established merely as a contract ceiling. Where the government cannot determine that at least $150K of work was funded under a relevant experience project that project will be disqualified and all associated points deducted from the offerors self-score.

7 Confirm obligated amount matches the amount shown on the Fully Executed Award Document and Federal Procurement Data System – Next Generation (FPDS-NG) (for federal awards) attachments. For FPDS refer to the "Action Obligation" field.

In the event the values do not match offeror must procure the signature of the CO in accordance with the instructions at the top of this checklist. This item is exempt for offerors submitting State or Local contracts to support a Relevant Experience Project.

8 Confirm that for Relevant Experience projects performed for a federal agency, the final FPDS-NG Record (printed directly from FPDS-NG) is attached.

The FPDS must be the full printout from FPDS that shows the competition block. Providing a synopsis of FPDS using the FPDS EZ search is not acceptable. This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

9 For orders against a MA/IDIQ in accordance with FAR 16.505 (b)(1) Fair Opportunity, provide additional confirmation that FPDS substantiates associated points in Self-Scoring Worksheet. Note, if a project is a “collection of orders” placed under a Single-Award or Multiple-Award IDIQ contract or BPA, the predominant proportion of work must have been competed under FAR 16.505 to earn points applicable to this Item.

To claim points for Section 1, Item 7, of the Self-Score Worksheet, the Data Element titled "Fair Opportunity/Limited Sources" in the competition block of the corresponding FPDS record must say either "Fair Opportunity Given", "Follow-On Action Following Competitive Initial Action", or "Competitive Set Aside".

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

10 Confirm that the completion (the end date of the base and any exercised option periods) of the submitted reference project contract or order is later than June 30, 2014. If this Relevant Experience Project is being supported by a collection of delivery/task orders, the order with the highest obligated dollar value must have a completion date after June 30, 2014.

Data associated with reference project contracts or orders whose completion date is prior to June 30, 2014 will not be considered and all associated points will be deducted. The government may rely on the FPDS record to confirm this data. In the event the contract documents conflict with the FPDS record, offerors may follow the instructions at the top of this checklist. If the completion date is not clear on the contract document for state or local contracts, the offeror may follow the instructions at the top of this checklist.

11 Confirm the requirements on the documentation submitted as part of a Relevant Experience Project match the selected Sub-Category.

Any contract submitted to support a Relevant Experience Project whose requirements do not match the selected sub-category will not be considered and all points supported by that document will be deducted from the offerors self-score.

12 Confirm the majority (>51% (based on obligated dollar amount)) of the project requirement aligns to the scope of the subcategory selected. For TC1, ancillary services may contribute to the >51% requirement, provided that the services directly support the delivery of applicable subcategory products under the same order/contract, and the primary purpose of the relevant experience project is for the delivery of supply items relevant to the subcategory. For TC2, the majority (>51%) of the relevant experience project must be for services in the given subcategory.

Where a contract/order is submitted for a relevant experience project and the funded value of the requirements that align to the scope of the sub-category are below 51% of the total value of that contract, that contract/order will not be considered and all points supported by that documentation will be disqualified.

13 Confirm the Statement of Work (or equivalent) AND the Section B Schedule of Supplies and Services is attached.** For a collection of orders include, the SOW and Section B for each order. RFP L.7.2.3.2

14 Confirm that yellow highlights in attached SOW clearly indicate requirements match the sub-category.

For proposals under the TC2 General Subcategory, the SOW must show Project Management experience in each relevant experience project.

The last date of the period of performance being evaluated must be later than June 30, 2014 and at least 50% of the rated criteria must be rated satisfactory or higher.

If a Past Performance Rating form is submitted and it is not signed by the appropriate rating official either the cognizant CO or COR, it is not valid . If a Past Performance Rating form is submitted and it references multiple orders or contracts, it is not valid (see RFP Section L.7.2.3.4). In all these case points claimed for past performance will be deducted from offeror's self score.

18 Confirm that the Contractor (as indicated on the Award Form) was the prime contractor on the award?

Any contract submitted to support a Relevant Experience Project where the offeror was not the prime contractor will not be considered and all points supported by that document will be deducted from the offerors self-score.

19 Confirm the Contractor Name and DUNS on all the above documents match (or qualifying exception below).

Any contract documentation that does not comply with the following RFP requirement will result in disqualification of that contract documentation from consideration.

Per RFP section L.5.3 - "For any claimed evaluation element identifying a different name other than that of the Offeror, due to a merger, acquisition, novation, or change-of-name agreement, the offeror has the burden to establish that the claimed evaluation element should be attributed to the Offeror. To do so, the offeror must provide evidence of the merger, acquisition, novation, or change-of- name agreement, as well as a justification demonstrating how the evaluation element being claimed is applicable to the Offeror." Reference RFP L.7.2.2 and L.7.2.3.6-8.

F5(B)

Relevant Experience Qualification Checklist

Reference IDV: In the yellow fill space below, enter Reference IDV (if award was against an IDIQ/BPA).

Obligated Amount: In the yellow space below, enter the Obligated Amount of the Relevant Experience contract supporting this Relevant Experience Project. If it is a collection of orders enter the sum of the obligated amount for all orders.

Contracting Agencies: In the yellow space below, enter Contracting Agency(ies) (or State/Local Government entity) for which work was performed.

Agency Point of Contact: In the yellow fill space below enter the name and email address of the cognizant Contracting Officer (or equivalent position for State/Local). If the Relevant Experience Project is a collection of orders enter the name and email of the cognizant Contracting Officer who signed the order with the largest funded dollar value.

If Award ID is submitted more than once, the data from the first appearance by Relevant Experience Project Number will be used. Subsequent data will not be considered and all points supported by subsequent data will be deducted from the offerors self-score. This standard applies across both TacCom II technical categories.

2 If submitting a collection of orders as a project, confirm all orders among a "collection of orders" are sourced from the same Reference IDV.

Orders that are added to the Relevant Experience Project that do not reference the same IDV will have all associated data removed from consideration.

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

3 Qualifying Award Type

Enter Qualifying award type from one of the following: (1) a single contract; (2) a single task or delivery order awarded under a Multiple Award contract (as defined below); (3) a single task or delivery order awarded under a master Single Award Indefinite Delivery Delivery/Task Order contract (Definite Quantity, Requirements, or Indefinite Quantity) contract (FAR 16.5); (4) a single delivery/task order placed under a Federal Supply Schedule contract (FAR 8.405-2); (5) a single task or delivery order placed under a master Multiple Award Blanket Purchase Agreement, or (6) a single task or delivery order placed under a master Single Award Blanket Purchase Agreement (BPA)(FAR 8.405-3); or (7) a collection of orders.

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

4 Confirm the fully executed (Contracting Officer signed) award document (SF 1449, or equivalent and modifications) is attached. For a collection of orders, each order must be fully executed. RFP L.7.2.3.1

Any contract document that is not fully executed may be removed from consideration and all points supported by that document and other corresponding data will be deducted from the offerors self-score. Offerors may address an unsigned contract or order via the CO certification process according to the instructions in this checklist as well as the direction described in L.7.2.2.

5 Confirm the Contracting Agency is a federal agency, state government, or locality in the United States. (OCONUS for federal agency submission is acceptable if work was in a foreign nation but on a US government base/installation)

Any contract submitted to support a Relevant Experience Project that is not from a Federal, State or Local Government entity will not be considered and all points supported by that document will be deducted from the offerors self-score.

6 Confirm that the total obligated amount is greater than $150K. For a collection of orders, the cumulative obligated amount for the collection of orders must be greater than $150K.

Federal award documents should contain a government funding/appropriation number associated with a dollar amount on the signed contract document. If there are multiple mods then the obligated amount should be the cumulative of those mods. Where a fully executed award document does not contain a funding/appropriation number, offeror may clarify the missing data by following the instructions at the top of this checklist. Offerors submitting State/Local contracts to support a relevant experience project must ensure the documents clearly state what is funded for actual work versus what is established merely as a contract ceiling. Where the government cannot determine that at least $150K of work was funded under a relevant experience project that project will be disqualified and all associated points deducted from the offerors self-score.

7 Confirm obligated amount matches the amount shown on the Fully Executed Award Document and Federal Procurement Data System – Next Generation (FPDS-NG) (for federal awards) attachments. For FPDS refer to the "Action Obligation" field.

In the event the values do not match offeror must procure the signature of the CO in accordance with the instructions at the top of this checklist. This item is exempt for offerors submitting State or Local contracts to support a Relevant Experience Project.

8 Confirm that for Relevant Experience projects performed for a federal agency, the final FPDS-NG Record (printed directly from FPDS-NG) is attached.

The FPDS must be the full printout from FPDS that shows the competition block. Providing a synopsis of FPDS using the FPDS EZ search is not acceptable. This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

9 For orders against a MA/IDIQ in accordance with FAR 16.505 (b)(1) Fair Opportunity, provide additional confirmation that FPDS substantiates associated points in Self-Scoring Worksheet. Note, if a project is a “collection of orders” placed under a Single-Award or Multiple-Award IDIQ contract or BPA, the predominant proportion of work must have been competed under FAR 16.505 to earn points applicable to this Item.

To claim points for Section 1, Item 7, of the Self-Score Worksheet, the Data Element titled "Fair Opportunity/Limited Sources" in the competition block of the corresponding FPDS record must say either "Fair Opportunity Given", "Follow-On Action Following Competitive Initial Action", or "Competitive Set Aside".

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

10 Confirm that the completion (the end date of the base and any exercised option periods) of the submitted reference project contract or order is later than June 30, 2014. If this Relevant Experience Project is being supported by a collection of delivery/task orders, the order with the highest obligated dollar value must have a completion date after June 30, 2014.

Data associated with reference project contracts or orders whose completion date is prior to June 30, 2014 will not be considered and all associated points will be deducted. The government may rely on the FPDS record to confirm this data. In the event the contract documents conflict with the FPDS record, offerors may follow the instructions at the top of this checklist. If the completion date is not clear on the contract document for state or local contracts, the offeror may follow the instructions at the top of this checklist.

11 Confirm the requirements on the documentation submitted as part of a Relevant Experience Project match the selected Sub-Category.

Any contract submitted to support a Relevant Experience Project whose requirements do not match the selected sub-category will not be considered and all points supported by that document will be deducted from the offerors self-score.

12 Confirm the majority (>51% (based on obligated dollar amount)) of the project requirement aligns to the scope of the subcategory selected. For TC1, ancillary services may contribute to the >51% requirement, provided that the services directly support the delivery of applicable subcategory products under the same order/contract, and the primary purpose of the relevant experience project is for the delivery of supply items relevant to the subcategory. For TC2, the majority (>51%) of the relevant experience project must be for services in the given subcategory.

Where a contract/order is submitted for a relevant experience project and the funded value of the requirements that align to the scope of the sub-category are below 51% of the total value of that contract, that contract/order will not be considered and all points supported by that documentation will be disqualified.

13 Confirm the Statement of Work (or equivalent) AND the Section B Schedule of Supplies and Services is attached.** For a collection of orders include, the SOW and Section B for each order. RFP L.7.2.3.2

14 Confirm that yellow highlights in attached SOW clearly indicate requirements match the sub-category.

For proposals under the TC2 General Subcategory, the SOW must show Project Management experience in each relevant experience project.

The last date of the period of performance being evaluated must be later than June 30, 2014 and at least 50% of the rated criteria must be rated satisfactory or higher.

If a Past Performance Rating form is submitted and it is not signed by the appropriate rating official either the cognizant CO or COR, it is not valid . If a Past Performance Rating form is submitted and it references multiple orders or contracts, it is not valid (see RFP Section L.7.2.3.4). In all these case points claimed for past performance will be deducted from offeror's self score.

18 Confirm that the Contractor (as indicated on the Award Form) was the prime contractor on the award?

Any contract submitted to support a Relevant Experience Project where the offeror was not the prime contractor will not be considered and all points supported by that document will be deducted from the offerors self-score.

19 Confirm the Contractor Name and DUNS on all the above documents match (or qualifying exception below).

Any contract documentation that does not comply with the following RFP requirement will result in disqualification of that contract documentation from consideration.

Per RFP section L.5.3 - "For any claimed evaluation element identifying a different name other than that of the Offeror, due to a merger, acquisition, novation, or change-of-name agreement, the offeror has the burden to establish that the claimed evaluation element should be attributed to the Offeror. To do so, the offeror must provide evidence of the merger, acquisition, novation, or change-of- name agreement, as well as a justification demonstrating how the evaluation element being claimed is applicable to the Offeror." Reference RFP L.7.2.2 and L.7.2.3.6-8.

F5(C)

Relevant Experience Qualification Checklist

Reference IDV: In the yellow fill space below, enter Reference IDV (if award was against an IDIQ/BPA).

Obligated Amount: In the yellow space below, enter the Obligated Amount of the Relevant Experience contract supporting this Relevant Experience Project. If it is a collection of orders enter the sum of the obligated amount for all orders.

Contracting Agencies: In the yellow space below, enter Contracting Agency(ies) (or State/Local Government entity) for which work was performed.

Agency Point of Contact: In the yellow fill space below enter the name and email address of the cognizant Contracting Officer (or equivalent position for State/Local). If the Relevant Experience Project is a collection of orders enter the name and email of the cognizant Contracting Officer who signed the order with the largest funded dollar value.

Item Evaluation Standards and Instructions Offeror Confirmation

1 Confirm Award ID is submitted only once across all Reference Projects.

If Award ID is submitted more than once, the data from the first appearance by Relevant Experience Project Number will be used. Subsequent data will not be considered and all points supported by subsequent data will be deducted from the offerors self-score. This standard applies across both TacCom II technical categories.

2 If submitting a collection of orders as a project, confirm all orders among a "collection of orders" are sourced from the same Reference IDV.

Orders that are added to the Relevant Experience Project that do not reference the same IDV will have all associated data removed from consideration.

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

3 Qualifying Award Type

Enter Qualifying award type from one of the following: (1) a single contract; (2) a single task or delivery order awarded under a Multiple Award contract (as defined below); (3) a single task or delivery order awarded under a master Single Award Indefinite Delivery Delivery/Task Order contract (Definite Quantity, Requirements, or Indefinite Quantity) contract (FAR 16.5); (4) a single delivery/task order placed under a Federal Supply Schedule contract (FAR 8.405-2); (5) a single task or delivery order placed under a master Multiple Award Blanket Purchase Agreement, or (6) a single task or delivery order placed under a master Single Award Blanket Purchase Agreement (BPA)(FAR 8.405-3); or (7) a collection of orders.

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

4 Confirm the fully executed (Contracting Officer signed) award document (SF 1449, or equivalent and modifications) is attached. For a collection of orders, each order must be fully executed. RFP L.7.2.3.1

Any contract document that is not fully executed may be removed from consideration and all points supported by that document and other corresponding data will be deducted from the offerors self-score. Offerors may address an unsigned contract or order via the CO certification process according to the instructions in this checklist as well as the direction described in L.7.2.2.

5 Confirm the Contracting Agency is a federal agency, state government, or locality in the United States. (OCONUS for federal agency submission is acceptable if work was in a foreign nation but on a US government base/installation)

Any contract submitted to support a Relevant Experience Project that is not from a Federal, State or Local Government entity will not be considered and all points supported by that document will be deducted from the offerors self-score.

6 Confirm that the total obligated amount is greater than $150K. For a collection of orders, the cumulative obligated amount for the collection of orders must be greater than $150K.

Federal award documents should contain a government funding/appropriation number associated with a dollar amount on the signed contract document. If there are multiple mods then the obligated amount should be the cumulative of those mods. Where a fully executed award document does not contain a funding/appropriation number, offeror may clarify the missing data by following the instructions at the top of this checklist. Offerors submitting State/Local contracts to support a relevant experience project must ensure the documents clearly state what is funded for actual work versus what is established merely as a contract ceiling. Where the government cannot determine that at least $150K of work was funded under a relevant experience project that project will be disqualified and all associated points deducted from the offerors self-score.

7 Confirm obligated amount matches the amount shown on the Fully Executed Award Document and Federal Procurement Data System – Next Generation (FPDS-NG) (for federal awards) attachments. For FPDS refer to the "Action Obligation" field.

In the event the values do not match offeror must procure the signature of the CO in accordance with the instructions at the top of this checklist. This item is exempt for offerors submitting State or Local contracts to support a Relevant Experience Project.

8 Confirm that for Relevant Experience projects performed for a federal agency, the final FPDS-NG Record (printed directly from FPDS-NG) is attached.

The FPDS must be the full printout from FPDS that shows the competition block. Providing a synopsis of FPDS using the FPDS EZ search is not acceptable. This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

9 For orders against a MA/IDIQ in accordance with FAR 16.505 (b)(1) Fair Opportunity, provide additional confirmation that FPDS substantiates associated points in Self-Scoring Worksheet. Note, if a project is a “collection of orders” placed under a Single-Award or Multiple-Award IDIQ contract or BPA, the predominant proportion of work must have been competed under FAR 16.505 to earn points applicable to this Item.

To claim points for Section 1, Item 7, of the Self-Score Worksheet, the Data Element titled "Fair Opportunity/Limited Sources" in the competition block of the corresponding FPDS record must say either "Fair Opportunity Given", "Follow-On Action Following Competitive Initial Action", or "Competitive Set Aside".

This item is not applicable for offerors submitting State or Local contracts to support a Relevant Experience Project.

10 Confirm that the completion (the end date of the base and any exercised option periods) of the submitted reference project contract or order is later than June 30, 2014. If this Relevant Experience Project is being supported by a collection of delivery/task orders, the order with the highest obligated dollar value must have a completion date after June 30, 2014.

Data associated with reference project contracts or orders whose completion date is prior to June 30, 2014 will not be considered and all associated points will be deducted. The government may rely on the FPDS record to confirm this data. In the event the contract documents conflict with the FPDS record, offerors may follow the instructions at the top of this checklist. If the completion date is not clear on the contract document for state or local contracts, the offeror may follow the instructions at the top of this checklist.

11 Confirm the requirements on the documentation submitted as part of a Relevant Experience Project match the selected Sub-Category.

Any contract submitted to support a Relevant Experience Project whose requirements do not match the selected sub-category will not be considered and all points supported by that document will be deducted from the offerors self-score.

12 Confirm the majority (>51% (based on obligated dollar amount)) of the project requirement aligns to the scope of the subcategory selected. For TC1, ancillary services may contribute to the >51% requirement, provided that the services directly support the delivery of applicable subcategory products under the same order/contract, and the primary purpose of the relevant experience project is for the delivery of supply items relevant to the subcategory. For TC2, the majority (>51%) of the relevant experience project must be for services in the given subcategory.

Where a contract/order is submitted for a relevant experience project and the funded value of the requirements that align to the scope of the sub-category are below 51% of the total value of that contract, that contract/order will not be considered and all points supported by that documentation will be disqualified.

13 Confirm the Statement of Work (or equivalent) AND the Section B Schedule of Supplies and Services is attached.** For a collection of orders include, the SOW and Section B for each order. RFP L.7.2.3.2

14 Confirm that yellow highlights in attached SOW clearly indicate requirements match the sub-category.

For proposals under the TC2 General Subcategory, the SOW must show Project Management experience in each relevant experience project.

The last date of the period of performance being evaluated must be later than June 30, 2014 and at least 50% of the rated criteria must be rated satisfactory or higher.

If a Past Performance Rating form is submitted and it is not signed by the appropriate rating official either the cognizant CO or COR, it is not valid . If a Past Performance Rating form is submitted and it references multiple orders or contracts, it is not valid (see RFP Section L.7.2.3.4). In all these case points claimed for past performance will be deducted from offeror's self score.

18 Confirm that the Contractor (as indicated on the Award Form) was the prime contractor on the award?

Any contract submitted to support a Relevant Experience Project where the offeror was not the prime contractor will not be considered and all points supported by that document will be deducted from the offerors self-score.

19 Confirm the Contractor Name and DUNS on all the above documents match (or qualifying exception below).

Any contract documentation that does not comply with the following RFP requirement will result in disqualification of that contract documentation from consideration.

Per RFP section L.5.3 - "For any claimed evaluation element identifying a different name other than that of the Offeror, due to a merger, acquisition, novation, or change-of-name agreement, the offeror has the burden to establish that the claimed evaluation element should be attributed to the Offeror. To do so, the offeror must provide evidence of the merger, acquisition, novation, or change-of- name agreement, as well as a justification demonstrating how the evaluation element being claimed is applicable to the Offeror." Reference RFP L.7.2.2 and L.7.2.3.6-8.