NetOps SB - Amend 0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

08 NOV 2010

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

6. ISSUED BY AFPEO EIS/HIJK CODE FA8771 7. ADMINISTERED BY (If other than Item 6) CODE

DEPARTMENT OF THE AIR FORCE

HQ 754 ELSG/KA

490 EAST MOORE DR., SUITE 270

MAFB - GUNTER ANNEX AL 36114-3000

DENNIS W. ROGERS 334-416-5624

dennis.rogers.3@us.af.mil

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NO.

TO ALL PROSPECTIVE OFFERORS

FA8771-09-R-0019

X

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, X is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER.

If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATION OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(X )

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: ( ) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. ITEM

10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

See Schedule

The offeror shall complete blocks 15 (a) (b) and (c) of the SF 30 and return the original to the PCO as specified in RFP Section J, Attachment 8, Paragraph L2.1.5 DISTRIBUTION/SUBMISSION/PROPOSAL VOLUMES.

Offerors shall provide the original signed SF 30 with the proposal submittal in concurrence with the SF 1449 of the original

RFP.

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print).

16A. NAME AND TITLE OF SIGNER (Type or print)

RAYMOND M. BARBEN

15B. CONTRACTOR/OFFEROR

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV.10-83)

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 6.12.0 FAR (48 CFR) 53.243 Created 08 Nov 2010 9:07 AM

SCHEDULE OF CHANGES

FA8771-09-R-0019 0003

The purpose of this amendment is to incorporate administrative changes to Request for Proposal

FA8771-09-R-0019:

1. Section J, Attachment 8, L2.1.5 and L2.3 (b) are changed to reflect the correct hour of delivery:

FROM:

12:00 PM (CDT)

TO:

12:00 PM (CST)

2. Section J, Attachment 19, CITS Pricing Workbook Tab NW MAT LOM. The column labeled "Quantity" is corrected:

FROM:

Quantity expressed as dollars

TO:

Quantity expressed as units

3. Section H, H103 ON RAMP, Paragraph 2 is changed to correct reopened competitions from "full and open competitions" to "small business competitions". H103 is changed:

FROM:

H103 ON RAMP (NOV 2009)

The Government intends to establish an awardee pool under the NETCENTS-2 effort. The Government will initially establish the awardee pool by competitively awarding multiple-award IDIQ contracts. Initial awardees of the NETCENTS-2 NetOps and Infrastructure Solutions Small Business Companion effort will be awarded contracts with a base term of three (3) years, plus four one-year options (if exercised).The Government reserves the right to reopen competition at any time during the term of the contract to add additional contractors to the original pool of awardees.

When reopening competition, the Government will advertise via Hanscom AFB Electronic Request for Proposal

Bulletin Board (HERBB)/Federal Business Opportunities (FedBizOpps) and conduct a full and open competition to bring the awardee pool up to either the initial awardee pool or a greater number of awardees. Any awardee already in the awardee pool will not recompete for an awardee pool position. The On-Ramp competitions will use the same evaluation methodology and documentation (updated to reflect changes in regulatory provisions and commercial practices and certifications) as the original competition. Once a new awardee is selected, that awardee will be included in the awardee pool and will compete for future task orders. The ordering period for new contractors being added to the initial awardee pool will coincide with initial awardees ordering period, inclusive of options, but shall not extend the overall term of the contract beyond the original ordering period nor shall it reestablish the contract base period, inclusive of options.

TO:

H103 ON RAMP (NOV 2009)

The Government intends to establish an awardee pool under the NETCENTS-2 effort. The Government will initially establish the awardee pool by competitively awarding multiple-award IDIQ contracts. Initial awardees of the NETCENTS-2 NetOps and Infrastructure Solutions Small Business Companion effort will be awarded contracts with a base term of three (3) years, plus four one-year options (if exercised).The Government reserves the right to reopen competition at any time during the term of the contract to add additional contractors to the original pool of awardees.

When reopening competition, the Government will advertise via Hanscom AFB Electronic Request for Proposal

Bulletin Board (HERBB)/Federal Business Opportunities (FedBizOpps) and conduct a small business competition to bring the awardee pool up to either the initial awardee pool or a greater number of awardees. Any awardee already in the awardee pool will not recompete for an awardee pool position. The On-Ramp competitions will use the same evaluation methodology and documentation (updated to reflect changes in regulatory provisions and commercial practices and certifications) as the original competition. Once a new awardee is selected, that awardee will be included in the awardee pool and will compete for future task orders. The ordering period for new contractors being added to the initial awardee pool will coincide with initial awardees ordering period, inclusive of options, but shall not extend the overall term of the contract beyond the original ordering period nor shall it reestablish the contract base period, inclusive of options.

4. Section H, H137 TASK ORDER RFP PROCEDURES, paragraph 8(iii) is changed to reflect the correct Labor Hour CLINs:

FROM:

H137 TASK ORDER RFP PROCEDURES (NOV 2009)

The procedures for selecting Contractors for order awards under this contract are governed by FAR 16.505 and supplements. Unless otherwise specified in a task order (TO) Request for Proposal (RFP), the following defines the process by which fair opportunity will be afforded, how task orders (TOs) will be processed and priced, and how a

TO will be awarded.

1. In addition to the Air Force, use of the NETCENTS-2 Network Operations (NetOps) and Infrastructure Solutions

Small Business Companion contracts may be available to DoD and other Federal Agencies. However, the Air Force reserves the right to restrict use of this contract. Additionally, the Air Force reserves the right to deny continued use of this contract by DoD or other Federal Agencies for reasons including, but not limited to, depletion of the remaining value of the contract ceiling or violation of the terms of the contract or User's Guide.

2. Decentralized ordering authority is granted within the Air Force, and may be granted to DoD and other Federal

Agencies on a non-interference basis with Air Force ceiling requirements. No decentralized orders shall be placed by DoD and other Federal Agencies without an assigned NETCENTS-2 PMO control number.

3. For this contract, the designated task order ombudsman is as designated in AFFARS clause 5352.201-9101. The task order ombudsman is responsible for reviewing complaints from multiple award contractors and ensuring that all of the contractors are afforded a fair opportunity to be considered for task orders in excess of $3,000 consistent with procedures in the contract. However, it is not within the designated task order contract ombudsman's authority to prevent the issuance of an order or disturb an existing order. This clause does not guarantee the contractor issuance of any task order above the minimum guarantee(s) stated in Section B, B061, Contract Maximum and Contract

Minimum Guarantee.

4. Contractors providing Solutions through this contract shall purchase products from the NETCENTS-2 Netcentric

Products contract in accordance with Section J, Attachment 1, Para 3.5.1 and as authorized in clause H098. All such quotes received shall be included in the proposal submission and priced under the ODC CLINs.

5.The NetOps and Infrastructure Solutions Category (NetOps) has a set of Full and Open contracts as well as a separate set of contracts for small business concerns hereinafter referred to as "Companion Contract". A

"Companion Contract" is a separate set of contracts for small business concerns with the same scope of coverage as the full and open contracts. These procedures apply when determining which contracts in which to compete task order RFPs - Full and Open Contracts vs Small Business Companion Contracts.

a) Each acquisition of services that has an anticipated dollar value exceeding $3,000, but not over $100,000 shall be competed in the NetOps Small Business Companion Contracts pool of awardees unless the task order contracting officer determines there is not a reasonable expectation of obtaining offers from two or more small business concerns that are competitive in terms of market prices, quality and delivery. If a task order is competed in the NetOps Small Business Companion contract pool of awardees and the task order contracting officer receives no offers, or no acceptable offers from a small business companion contract IDIQ awardee, the RFP shall be withdrawn and the requirement, if still valid, shall be resolicited in the NetOps full and open pool of ID/IQ contracts awardees.

b) For orders exceeding $100,000 the task order Contracting Officer should conduct market research to determine whether or not there is a reasonable expectation of receiving offers from at least two small business companion contractors. If market research reveals that at least two small businesses in the Small Business

Companion contract are capable of performing the work, the task order should be competed in the NetOps Small

Business Companion contract pool of awardees. If a task order is competed in the NetOps Small Business

Companion contract pool of awardees and the task order contracting officer receives no offers, or no acceptable offers from a small business companion contract ID/IQ awardee, the RFP shall be withdrawn and the requirement, if still valid, shall be resolicited in the NetOps full and open pool of ID/IQ contracts awardees.

6. Fair Opportunity Process.

a) Each task order RFP will be provided to each of the prime contractors via AFWAY or AFWAY II. All holders of ID/IQ contracts are encouraged to compete for NetOps & Infrastructure Solutions Small Business

Companion Task Orders. Each prime contractor shall evaluate the opportunity and determine whether or not to submit a proposal.

b)The RFP (unless the contracting officer determines that an exception to fair opportunity procedures applies) will include, at a minimum, the following information:

(i)Tracking Number (AFWAY / AFWAY II assigns a tracking number to each RFP)

(ii)Date of Announcement

(iii)End User Customer Agency and the Contracting Officer's Technical Representative (COTR)

(iv)Technical requirements package

(v)Performance Work Statement (PWS) or Statement of Work (SOW) or Statement of Objectives

(SOO)

(vi)CDRL package

(vii)Anticipated Contract Type

(viii)Contracting Agency POC Name Phone Number and Fax (CO and Contract Specialist)

(ix)E-mail Address/Mailing Address or Fax Number

(x)Proposal Due Date

(xi)Best value evaluation criteria

c) Fair Opportunity Exceptions.

One or more TOs may be issued during the ordering period of this contract. In accordance with the Federal

Acquisition Streamlining Act (FASA) and FAR 16.505(b), the CO will provide all awardees a "fair opportunity" to be considered for each order in excess of $3,000 unless one of the conditions below applies.

(i)The agency need for the services is so urgent that providing a fair opportunity would result in unacceptable delays;

(ii)Only one awardee is capable of providing the services required at the level of quality required because the services ordered are unique or highly specialized;

(iii)The order must be issued on a sole-source basis in the interest of economy and efficiency as a logical follow-on to an order already issued under the contract, provided that all multi-awardees were given a fair opportunity to be considered for the original order.

For actions considered to be a fair opportunity exception, the justification approval levels shall be consistent with

AFFARS MP306.304.

7. Selection Criteria for Awarding Task Order.

The Government will award to the offeror whose proposal is deemed most advantageous to the Government based upon an integrated assessment using the evaluation criteria. The Government will evaluate proposals against established selection criteria specified in the task order RFP. Generally, the Government's award decision will be based on selection criteria which addresses past performance, technical acceptability, proposal risk and cost. Among other sources, evaluation of past performance may be based on past performance assessments provided by TO

Program Managers on individual task orders performed throughout the life of the contract. The order of importance for the factors will be identified in the RFP for the specified task order.

8. Proposal Process.

a) The CO will issue a task order RFP to all prime contractors, unless a fair opportunity exception exists.

The RFP will include a due date for proposal submission and either a SOO and/or PWS that will include a detailed description of work to be accomplished, a listing of the deliverables required and any additional data, as appropriate.

The RFP will also include specific instructions for the submission of proposals. If oral proposals are to be used in lieu of or in conjunction with written proposals the RFP will specify such.

b) The amount of time for proposal submission will be based on the complexity and urgency of the requirement and will be stated in individual task orders. However, more or less time may be allowed based on the individual TO requirement. The due date will be set forth in each RFP. If unable to perform a requirement, contractors shall submit a "no proposal" reply in response to the proposal request. All "no proposal" responses shall include a brief statement as to why the contractor is unable to perform, e.g. conflict of interest.

(i)Technical Proposals. Technical proposal information will be streamlined, e.g., the Government anticipates written proposals consisting of thirty (30) pages or less stating compliance or exception to requirements, risks, assumptions and conflict of interest issues. Proposals shall not merely restate

SOO/PWS requirements. Written technical proposals shall normally address:

* Technical Approach and descriptive narrative of the contractor's understanding of the requested effort

* PWS in response to a SOO

* Integrated Master Plan (if applicable)

* Integrated Master Schedule (if applicable)

* Key Personnel Assigned

* Quantities/Hours of Personnel by Labor Categories and narrative justification (if applicable)

* Other Direct Costs (ODCs) (materials and supplies, travel, training, etc.(quantities and types only))

* Period of Performance

* Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)

* Security (including clearance level)

* Teaming Arrangement (including subcontracting; identify new ACAs)

* Small Business Plan (if a large business)

* Other Pertinent Data, such as assumptions made.

(ii)Cost Proposals. A written cost proposal will always be required for cost orders, and may be required for orders that are fixed price. This part of the proposal shall include detailed cost/price amounts of all resources required to accomplish the task, (i.e. labor hours, rates, travel, incidental equipment, etc.). The level of detail required shall be primarily based on the contract type planned for use, as further discussed below. The below instructions may normally be the ones which apply to task order proposals, however, these instructions may be tailored in individual RFPs, if so desired by the Government. Cost/price proposals shall include, as a minimum, a complete Contractor Work Breakdown Structure (CWBS), which coincides with the detailed technical approach;

and provides proposed labor categories, hours, wage rates, direct/indirect rates, ODCs and fee. Cost-reimbursement proposals shall be submitted in accordance with FAR 52.215-21 - Requirements for Cost or Pricing Data or

Information Other Than Cost or Pricing Data.

(iii)Labor Hour. The proposal shall identify labor categories, rate and the number of hours required for performance of the task. The proposal must identify and justify use of all non-labor cost elements. It must also identify any GFE and/or GFI required for task performance.To ensure proper use of the Labor Hour (LH) contract type, the Government has established a 10% cap on the usage of the Labor Hour CLINs (CLIN 0300, 1300, 2300, 3300, 4300).

(iv)Price Proposal. Information other than cost and pricing data maybe required at the task order level for fixed price orders. No detailed price information will be submitted if not required by the task order.

(v)Other Relevant Information. This information shall always be in writing and shall address other relevant information as required by the contract or requested by the RFP. For example, in accordance with Section

H, H106, Avoidance of Organizational Conflicts of Interest, identifying any situation in which the potential for a conflict of interest exists. If travel is specified in the TO PWS or statement of work, air fare and/or local mileage, per diem rates by total days, number of trips and number of contractor employees traveling shall be included in the cost proposal (see clause H047).

(vi)Clarification of Proposals. Evaluations will be in accordance with the selection criteria set forth in the proposal request. Upon completion of evaluations, the CO will issue a task order to the contractor whose proposal provides the best value to the Government.

(vii)Proposal Preparation. The contractor shall assume all costs associated with preparation of proposals for task order awards under the proposal process as an indirect charge (B&P costs). The Government will not reimburse awardees for proposals as a direct charge.

9.Resolution of Issues. In the event issues pertaining to a proposed TO/DO solicitation cannot be resolved to the satisfaction of the CO, the CO reserves the right to withdraw and cancel the proposed TO/DO solicitation. In such event, the contractor shall be notified in writing of the CO's decision. This decision is final and conclusive and shall not be subject to the "Disputes" clause or the "Contract Disputes Act."

10.Task Order Issuance. Awarded task orders may be issued by e-mail, regular mail or facsimile using a DD Form

1155 (Order for Supplies and Services) or SF1449 (Solicitation/Contract/Order for Commercial Items). TOs may also be distributed via the DOD Electronic Document Access application. It is anticipated that all awarded TOs will be issued electronically. If mailed, a TO is considered "issued" when the Government deposits the order in the mail.

11.Unauthorized Work. The contractor is not authorized at any time to commence task order performance prior to issuance of a signed TO or other written approval provided by the CO to begin work.

12. Task Order Funding Restrictions. No unfunded TOs are allowed; TOs may be incrementally funded in accordance with FAR and other agency funding restrictions.

The Contracting Officer for each order is responsible for closing out the contract action that they issue.Notification that a closeout of an order is complete must be provided to the Procuring Contracting Officer (the Basic Contract) once accomplished. The Contractor shall work in partnership with the Government to closeout orders as soon as possible after they are physically complete by using the "Quick Closeout" procedures described in FAR 42.708 as much as practical.

In accordance with section 1427(b) of Public Law 108-136 a protest is not authorized in connection with the issuance or proposed issuance of an individual TO except a protest on the grounds that the order increases the scope, period, or maximum value of the contract under which the order is issued; or a protest of an order valued in excess of $10 million. Protests of orders in excess of $10 million may only be filed with the Government Accountability

Office, in accordance with the procedures at 33.104

<http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/33.htm>.

TO:

H137 TASK ORDER RFP PROCEDURES (NOV 2009)

The procedures for selecting Contractors for order awards under this contract are governed by FAR 16.505 and supplements. Unless otherwise specified in a task order (TO) Request for Proposal (RFP), the following defines the process by which fair opportunity will be afforded, how task orders (TOs) will be processed and priced, and how a

TO will be awarded.

1. In addition to the Air Force, use of the NETCENTS-2 Network Operations (NetOps) and Infrastructure Solutions

Small Business Companion contracts may be available to DoD and other Federal Agencies. However, the Air Force reserves the right to restrict use of this contract. Additionally, the Air Force reserves the right to deny continued use of this contract by DoD or other Federal Agencies for reasons including, but not limited to, depletion of the remaining value of the contract ceiling or violation of the terms of the contract or User's Guide.

2. Decentralized ordering authority is granted within the Air Force, and may be granted to DoD and other Federal

Agencies on a non-interference basis with Air Force ceiling requirements. No decentralized orders shall be placed by DoD and other Federal Agencies without an assigned NETCENTS-2 PMO control number.

3. For this contract, the designated task order ombudsman is as designated in AFFARS clause 5352.201-9101. The task order ombudsman is responsible for reviewing complaints from multiple award contractors and ensuring that all of the contractors are afforded a fair opportunity to be considered for task orders in excess of $3,000 consistent with procedures in the contract. However, it is not within the designated task order contract ombudsman's authority to prevent the issuance of an order or disturb an existing order. This clause does not guarantee the contractor issuance of any task order above the minimum guarantee(s) stated in Section B, B061, Contract Maximum and Contract

Minimum Guarantee.

4. Contractors providing Solutions through this contract shall purchase products from the NETCENTS-2 Netcentric

Products contract in accordance with Section J, Attachment 1, Para 3.5.1 and as authorized in clause H098. All such quotes received shall be included in the proposal submission and priced under the ODC CLINs.

5.The NetOps and Infrastructure Solutions Category (NetOps) has a set of Full and Open contracts as well as a separate set of contracts for small business concerns hereinafter referred to as "Companion Contract". A

"Companion Contract" is a separate set of contracts for small business concerns with the same scope of coverage as the full and open contracts. These procedures apply when determining which contracts in which to compete task order RFPs - Full and Open Contracts vs Small Business Companion Contracts.

a) Each acquisition of services that has an anticipated dollar value exceeding $3,000, but not over $100,000 shall be competed in the NetOps Small Business Companion Contracts pool of awardees unless the task order contracting officer determines there is not a reasonable expectation of obtaining offers from two or more small business concerns that are competitive in terms of market prices, quality and delivery. If a task order is competed in the NetOps Small Business Companion contract pool of awardees and the task order contracting officer receives no offers, or no acceptable offers from a small business companion contract IDIQ awardee, the RFP shall be withdrawn and the requirement, if still valid, shall be resolicited in the NetOps full and open pool of ID/IQ contracts awardees.

b) For orders exceeding $100,000 the task order Contracting Officer should conduct market research to determine whether or not there is a reasonable expectation of receiving offers from at least two small business companion contractors. If market research reveals that at least two small businesses in the Small Business

Companion contract are capable of performing the work, the task order should be competed in the NetOps Small

Business Companion contract pool of awardees. If a task order is competed in the NetOps Small Business

Companion contract pool of awardees and the task order contracting officer receives no offers, or no acceptable offers from a small business companion contract ID/IQ awardee, the RFP shall be withdrawn and the requirement, if still valid, shall be resolicited in the NetOps full and open pool of ID/IQ contracts awardees.

6. Fair Opportunity Process.

a) Each task order RFP will be provided to each of the prime contractors via AFWAY or AFWAY II. All holders of ID/IQ contracts are encouraged to compete for NetOps & Infrastructure Solutions Small Business

Companion Task Orders. Each prime contractor shall evaluate the opportunity and determine whether or not to submit a proposal.

b)The RFP (unless the contracting officer determines that an exception to fair opportunity procedures applies) will include, at a minimum, the following information:

(i)Tracking Number (AFWAY / AFWAY II assigns a tracking number to each RFP)

(ii)Date of Announcement

(iii)End User Customer Agency and the Contracting Officer's Technical Representative (COTR)

(iv)Technical requirements package

(v)Performance Work Statement (PWS) or Statement of Work (SOW) or Statement of Objectives

(SOO)

(vi)CDRL package

(vii)Anticipated Contract Type

(viii)Contracting Agency POC Name Phone Number and Fax (CO and Contract Specialist)

(ix)E-mail Address/Mailing Address or Fax Number

(x)Proposal Due Date

(xi)Best value evaluation criteria

c) Fair Opportunity Exceptions.

One or more TOs may be issued during the ordering period of this contract. In accordance with the Federal

Acquisition Streamlining Act (FASA) and FAR 16.505(b), the CO will provide all awardees a "fair opportunity" to be considered for each order in excess of $3,000 unless one of the conditions below applies.

(i)The agency need for the services is so urgent that providing a fair opportunity would result in unacceptable delays;

(ii)Only one awardee is capable of providing the services required at the level of quality required because the services ordered are unique or highly specialized;

(iii)The order must be issued on a sole-source basis in the interest of economy and efficiency as a logical follow-on to an order already issued under the contract, provided that all multi-awardees were given a fair opportunity to be considered for the original order.

For actions considered to be a fair opportunity exception, the justification approval levels shall be consistent with

AFFARS MP306.304.

7. Selection Criteria for Awarding Task Order.

The Government will award to the offeror whose proposal is deemed most advantageous to the Government based upon an integrated assessment using the evaluation criteria. The Government will evaluate proposals against established selection criteria specified in the task order RFP. Generally, the Government's award decision will be based on selection criteria which addresses past performance, technical acceptability, proposal risk and cost. Among other sources, evaluation of past performance may be based on past performance assessments provided by TO

Program Managers on individual task orders performed throughout the life of the contract. The order of importance for the factors will be identified in the RFP for the specified task order.

8. Proposal Process.

a) The CO will issue a task order RFP to all prime contractors, unless a fair opportunity exception exists.

The RFP will include a due date for proposal submission and either a SOO and/or PWS that will include a detailed description of work to be accomplished, a listing of the deliverables required and any additional data, as appropriate.

The RFP will also include specific instructions for the submission of proposals. If oral proposals are to be used in lieu of or in conjunction with written proposals the RFP will specify such.

b) The amount of time for proposal submission will be based on the complexity and urgency of the requirement and will be stated in individual task orders. However, more or less time may be allowed based on the individual TO requirement. The due date will be set forth in each RFP. If unable to perform a requirement, contractors shall submit a "no proposal" reply in response to the proposal request. All "no proposal" responses shall include a brief statement as to why the contractor is unable to perform, e.g. conflict of interest.

(i)Technical Proposals. Technical proposal information will be streamlined, e.g., the Government anticipates written proposals consisting of thirty (30) pages or less stating compliance or exception to requirements, risks, assumptions and conflict of interest issues. Proposals shall not merely restate

SOO/PWS requirements. Written technical proposals shall normally address:

* Technical Approach and descriptive narrative of the contractor's understanding of the requested effort

* PWS in response to a SOO

* Integrated Master Plan (if applicable)

* Integrated Master Schedule (if applicable)

* Key Personnel Assigned

* Quantities/Hours of Personnel by Labor Categories and narrative justification (if applicable)

* Other Direct Costs (ODCs) (materials and supplies, travel, training, etc.(quantities and types only))

* Period of Performance

* Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)

* Security (including clearance level)

* Teaming Arrangement (including subcontracting; identify new ACAs)

* Small Business Plan (if a large business)

* Other Pertinent Data, such as assumptions made.

(ii)Cost Proposals. A written cost proposal will always be required for cost orders, and may be required for orders that are fixed price. This part of the proposal shall include detailed cost/price amounts of all resources required to accomplish the task, (i.e. labor hours, rates, travel, incidental equipment, etc.). The level of detail required shall be primarily based on the contract type planned for use, as further discussed below. The below instructions may normally be the ones which apply to task order proposals, however, these instructions may be tailored in individual RFPs, if so desired by the Government. Cost/price proposals shall include, as a minimum, a complete Contractor Work Breakdown Structure (CWBS), which coincides with the detailed technical approach;

and provides proposed labor categories, hours, wage rates, direct/indirect rates, ODCs and fee. Cost-reimbursement proposals shall be submitted in accordance with FAR 52.215-21 - Requirements for Cost or Pricing Data or

Information Other Than Cost or Pricing Data.

(iii)Labor Hour. The proposal shall identify labor categories, rate and the number of hours required for performance of the task. The proposal must identify and justify use of all non-labor cost elements. It must also identify any GFE and/or GFI required for task performance.To ensure proper use of the Labor Hour (LH) contract type, the Government has established a 10% cap on the usage of the Labor Hour CLINs (CLIN 0003, 1003, 2003, 3003, 3300, 4003, 4300).

(iv)Price Proposal. Information other than cost and pricing data maybe required at the task order level for fixed price orders. No detailed price information will be submitted if not required by the task order.

(v)Other Relevant Information. This information shall always be in writing and shall address other relevant information as required by the contract or requested by the RFP. For example, in accordance with Section

H, H106, Avoidance of Organizational Conflicts of Interest, identifying any situation in which the potential for a conflict of interest exists. If travel is specified in the TO PWS or statement of work, air fare and/or local mileage, per diem rates by total days, number of trips and number of contractor employees traveling shall be included in the cost proposal (see clause H047).

(vi)Clarification of Proposals. Evaluations will be in accordance with the selection criteria set forth in the proposal request. Upon completion of evaluations, the CO will issue a task order to the contractor whose proposal provides the best value to the Government.

(vii)Proposal Preparation. The contractor shall assume all costs associated with preparation of proposals for task order awards under the proposal process as an indirect charge (B&P costs). The Government will not reimburse awardees for proposals as a direct charge.

9.Resolution of Issues. In the event issues pertaining to a proposed TO/DO solicitation cannot be resolved to the satisfaction of the CO, the CO reserves the right to withdraw and cancel the proposed TO/DO solicitation. In such event, the contractor shall be notified in writing of the CO's decision. This decision is final and conclusive and shall not be subject to the "Disputes" clause or the "Contract Disputes Act."

10.Task Order Issuance. Awarded task orders may be issued by e-mail, regular mail or facsimile using a DD Form

1155 (Order for Supplies and Services) or SF1449 (Solicitation/Contract/Order for Commercial Items). TOs may also be distributed via the DOD Electronic Document Access application. It is anticipated that all awarded TOs will be issued electronically. If mailed, a TO is considered "issued" when the Government deposits the order in the mail.

11.Unauthorized Work. The contractor is not authorized at any time to commence task order performance prior to issuance of a signed TO or other written approval provided by the CO to begin work.

12. Task Order Funding Restrictions. No unfunded TOs are allowed; TOs may be incrementally funded in accordance with FAR and other agency funding restrictions.

The Contracting Officer for each order is responsible for closing out the contract action that they issue.Notification that a closeout of an order is complete must be provided to the Procuring Contracting Officer (the Basic Contract) once accomplished. The Contractor shall work in partnership with the Government to closeout orders as soon as possible after they are physically complete by using the "Quick Closeout" procedures described in FAR 42.708 as much as practical.

In accordance with section 1427(b) of Public Law 108-136 a protest is not authorized in connection with the issuance or proposed issuance of an individual TO except a protest on the grounds that the order increases the scope, period, or maximum value of the contract under which the order is issued; or a protest of an order valued in excess of $10 million. Protests of orders in excess of $10 million may only be filed with the Government Accountability

Office, in accordance with the procedures at 33.104

<http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/33.htm>.

5. All other terms and conditions remain unchanged

LIST OF ATTACHMENTS

DOCUMENT PGS DATE TITLE

ATTACHMENT 8 20 07 SEP 2010 INFORMATION TO OFFERORS (ITO) AND

INSTRUCTIONS FOR PROPOSAL PREPARATION

(IFPP) (WILL BE REMOVED AS AN

ATTACHMENT UPON CONTRACT AWARD)

ATTACHMENT 19 13 07 SEP 2010 CITS ITS PRICING MODEL(WILL BE REMOVED AS

AN ATTACHMENT UPON CONTRACT AWARD)

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS____________________________

Section L FA8771-09-R-0019-0003

Section J, Attachment 8

L055 INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR PROPOSAL PREPARATION

(IFPP) (JAN 2010)

L1.0 PROGRAM STRUCTURE AND OBJECTIVES

See Section J, Performance Work Statement.

L2.0 GENERAL INSTRUCTIONS

(a) This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information stated herein and must be submitted in accordance with these instructions. Non conformance with the instructions provided may result in an unfavorable proposal evaluation. All proposed technical, management, performance and schedule capabilities to meet the requirements shall be realistic and are subject to verification by the Government. The proposal shall be compliant with the requirements as stated in the PWS and Solicitation/Model Contract. The proposal shall be unclassified.

(b) The offeror's proposal shall consist of the written submittal. All information provided by the offeror (as long as it is consistent with the constraints of this RFP, e.g., page limitations) is subject to evaluation as described in Section M. The Government will not award individual CLINs in the RFP to any one contractor, but shall award ALL CLINs. Proposals for a single CLIN, or group thereof, shall be rejected.

(c) The completion and submission of all proposal volumes constitutes the offeror's acceptance to the terms and conditions in this RFP and in any attachments thereto. Proposals shall be late IAW FAR

15.208 if they are not received by the date specified in L2.3 Proposal Format, paragraph (b).

(d) The Government may consider any offeror's exception to the terms and conditions in this RFP to be a deficiency, which may render the offer unacceptable.

L2.0.1 Proposal Clarity

The proposals shall be clear, concise, and shall include sufficient detail for effective evaluation substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements, but shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their capabilities and experience, and will base its evaluation on the information presented in the offeror's proposal. The Government intends to evaluate proposals and award contracts without discussions, but reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary.

L2.0.2 Proposal Acceptance Period

The offeror shall make a clear statement in the Contract Documentation Volume V that the proposal is valid for a period of not less than 365 days from receipt.

L2.0.3 Disposition of Unsuccessful Proposals

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain the original copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

L2.1 GENERAL INFORMATION

L2.1.1 Point of Contact

Lt Col Raymond M. Barben, PCO - NETCENTS-2, is the point of contact for this acquisition. Address any questions or concerns to him. Written requests for clarification may be sent via e-mail to the PCO at raymond.barben@gunter.af.mil. Official RFP documentation, including RFP amendments, and other related information will be available on the Internet at http://public.gunter.af.mil/aq/netcents/2/ , HTTP://HERBB.HANSCOM.AF.MIL and https://www.fbo.gov/.

L2.1.2 Debriefings

Pre-award notices of exclusion from competitive range: The contracting officer will notify offerors promptly in writing when their proposals are excluded from the competitive range or otherwise eliminated from the competition. IAW FAR 15.505, the offeror may request a pre-award debriefing by submitting a written request for debriefing to the contracting officer within 3 days after receipt of the notice of exclusion from the competition. At the offeror’s request, this debriefing may be delayed until after award. If the debriefing is delayed until after award, it shall include all information normally provided in a post-award debriefing (see 15.506(d)). The contracting officer shall make every effort to debrief the unsuccessful offeror as soon as practicable, but may refuse the request for a debriefing if, for compelling reasons, it is not in the best interests of the Government to conduct a debriefing at that time.

Post-award notices: Within 3 days after the date of contract award, the contracting officer will provide written notification to each offeror whose proposal was in the competitive range but was not selected for award or had not been previously notified. An offeror, upon its written request received by the agency within 3 days after the date on which that offeror has received notification of contract award in accordance with 15.503(b), shall be debriefed and furnished the basis for the selection decision and contract award.

To the maximum extent practicable, the debriefing should occur within 5 days after receipt of the written request. Offerors that requested a post-award debriefing in lieu of a pre-award debriefing, or whose debriefing was delayed for compelling reasons beyond contract award, also should be debriefed within this time period. An offeror that was notified of exclusion from the competition (see 15.505(a)), but failed to submit a timely request, is not entitled to a debriefing.

L2.1.3 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the offeror is asking the PCO to consider as related to the omission or error.

L2.1.4 Electronic Reference Documents

All referenced documents for this solicitation are available on NETCENTS-2 web site at http://public.gunter.af.mil/aq/netcents/2/.

http://public.gunter.af.mil/aq/netcents/2/ http://herbb.hanscom.af.mil/ https://www.fbo.gov/ http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/15.htm#P982_179120 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/15.htm#P961_176463 http://public.gunter.af.mil/aq/netcents/2/

L2.1.5 Distribution/Submission/Proposal Volumes

One complete set of "original" volumes and all other copies IAW Table 1 shall be clearly marked, addressed and mailed, or hand-carried, to the PCO at the following address by 18 November 2010, 12:00 PM (CST):

RAYMOND M. BARBEN, Lt Col, USAF

PCO, NETCENTS-2

ESC/HIJK

490 EAST MOORE DR.

BLDG 892, SUITE 270

MAXWELL AFB - GUNTER ANNEX, AL 36114

NOTE: ALL official mail must have the return address and the addressee in ALL CAPS. Mail that is not properly addressed will be returned for correction by the Official Mail Center (OMC).

L2.1.6 SECTION K - REPRESENTATIONS AND CERTIFICATIONS

IAW FAR 52.204-08, contractor shall submit completed representations, certifications, acknowledgments and statements in compliance with the Online Representation and Certification Application (ORCA) requirements.

L2.1.7 Communications

Exchanges of source selection information between government and offerors will be controlled by the PCO. Encrypted e-mail may be used to transmit such information to offerors, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the Subject line.

L2.2 ORGANIZATION/DISTRIBUTION/NUMBER OF COPIES/PAGE LIMITS

(a) The offeror shall prepare the proposal as set forth in Table 1 below. The titles and contents of the volumes should be as defined in Table 1, and shall be within the required page limits and in the number of copies as specified in the table. The contents of each proposal volume are described in the paragraphs noted in Table 1.

(b) Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the submission and may be returned to the offeror (i.e., paper copies) as soon as practicable. Each page shall be counted except the following; any Cover Sheets, Table of Contents, Tabs, Glossaries of terms/abbreviations/acronyms, cross reference matrix, resumes and organizational charts. All pages shall be numbered. Sheets printed on both sides shall be numbered on both sides if both sides contain information.

(c) Virus free CDs or DVDs (one volume copy per CD/DVD), shall be encased in a vinyl CD/DVD protector sheet for three-ring binders, and placed in each of their corresponding volume. Indicate on each CD/DVD the volume, title and company name. Offerors shall not password protect any documents.

In the event hard copy and soft copy contents conflict, hard copies will take precedence over soft copies.

Soft copies shall be compatible with Microsoft Office 2003 or later. Adobe Acrobat 8.0 (or better) format is also acceptable.

(d) Forward one paper copy and one CD/DVD of proposal Volumes I, II, III, IV and V to your cognizant Defense Contract Audit Agency (DCAA) when the PCO copies are delivered. (Submission of proposal volumes to DCAA does not constitute submission of the proposal for evaluation). Failure to provide information to the locations as specified will result in a delay in the evaluation and may negatively affect the evaluation of the offeror's proposal. Be sure to advise DCAA that the proposal is "For Official Use Only" and contains "Source Selection Information - See FAR 52.215-01(e) and 3.104."

Volume Title Page Limit Copies

I Executive Summary 5 pages

Original & 1 paper copy; 2 CDs/DVDs

II Technical Proposal 130 total pages

Original & 2 paper copies; 2 CDs/DVDs

Quality Processes (Reference Section J, Atch 1, Para 7)

15 pages total as part of the Technical Proposal

Included in the Technical Proposal copies

Metadata Environments Development

20 pages total as part of the Technical Proposal

Included in the Technical Proposal copies

Network Management and Network Defense (NM/ND) Cost Reimbursable Task Order Submission

40 pages total as part of the Technical Proposal (not including pricing or WBS)

Included in the Technical Proposal copies. Provide 3 paper copies of the Horse Blanket (included in the page limit)

CITS Information Transport Systems (ITS) Firm Fixed Price Sample Task Order Submission

40 pages total as part of the Technical Proposal (not including pricing)

Included in the Technical Proposal copies

Management Approach

15 pages total as part of the Technical Proposal

Included in the Technical Proposal copies

III Past Performance Information Sheets

(PPIS)

Table of Contents (not counted in total) PPIS - 4 page limit per contract and up to 10 contracts for a total of 40 pages max

Original & 1 paper copy; 2 CDs /DVDs

IV Cost/Price

No page limit Original & 2 paper copies; 2 CDs/DVDs

V Contract Documentation

No page limit

Original & 1 paper copy; 2 CDs/DVDs

Table 1- Proposal Organization

NOTE: Volume 1 - Executive Summary will not be part of the NETCENTS-2 evaluation.

L2.3 Proposal Format

(a) The offeror's proposal must include all data and information requested herein and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the RFP. Nonconformance with the RFP may result in an unfavorable proposal evaluation.

(b) All proposal volumes shall be due 18 November 2010, 12:00 PM (CST).

(c) Elaborate brochures, presentations or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

L2.3.1 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. Binders sent with the proposal shall not contain any markings or graphics (inside or outside), nor any insertions in the spine. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. All unclassified document binders shall have a color other than red. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

Horseblankets shall be clearly marked with the offeror’s name, solicitation number and copy number.

L2.3.2 Page Format Restrictions

(a) Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced.