Amendment1-SectionL.pdf

ALLIANT SB

Solicitation # TQ2006MCB0002

Amendment 1 Section L

L-1

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES

TO OFFERORS OR RESPONDENTS

L.1 FAR 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY

REFERENCE (FEB 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The Offeror is cautioned that the listed provisions may include blocks that must be completed by the Offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the Offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this address:

http://acqnet.gov/far/index.html.

(End of Provision)

CLAUSE # CLAUSE TITLE DATE

52.204-6 DATA UNIVERSAL NUMBERING SYSTEM (DUNS) NUMBER OCT 2003

52.211-14 NOTICE OF PRIORITY RATING FOR NATIONAL DEFENSE USE SEP1990

52.214-34 SUBMISSION OF OFFERS IN THE ENGLISH LANGUAGE APR 1991

52.214-35 SUBMISSION OF OFFERS IN U.S. CURRENCY APR 1991

52.215-1 INSTRUCTIONS TO OFFERORS – COMPETITIVE ACQUISITION JAN 2004

52.215-16 FACILITIES CAPITAL COST OF MONEY JUN 2003

52.222-24 PRE-AWARD ON-SITE EQUAL OPPORTUNITY COMPLIANCE

EVALUATION

FEB 1999

52.222-46 EVALUATION OF COMPENSATION FOR PROFESSIONAL

EMPLOYEES

FEB 1993

52.232-38 SUBMISSION OF ELECTRONIC FUNDS TRANSFER

INFORMATION WITH OFFER.

MAY 1999

52.237-1 SITE VISIT APR 1984

52.237-10 IDENTIFICATION OF UNCOMPENSATED OVERTIME OCT 1997

L.2 FAR 52.216-1 TYPE OF CONTRACT (APR 1984)

The Government contemplates award of multiple award indefinite-delivery, indefinite-quantity (MAIDIQ) Contracts.

L.3 FAR 52.216-27 SINGLE OR MULTIPLE AWARDS (OCT 1995)

L-2

The Government contemplates placing approximately 35 to 40 awards resulting from this solicitation, but reserves the right to place fewer or more awards, depending upon the quality of the proposals received.

L.4 PROTEST

L.4.1 FAR 52.233-2 SERVICE OF PROTEST (SEP 2006)

(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the Contracting Officer (addressed as follows) by obtaining written and dated acknowledgment of receipt from:

General Services Administration Office of Business & Support Services (6ADB) 1500 E. Bannister Road, Room 1161 Kansas City, MO 64131 Attention: Mary Catherine Beasley

(b) The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.

(End of provision)

L.4.2 GSAM 552.233-70 PROTESTS FILED DIRECTLY WITH THE GENERAL

SERVICES ADMINISTRATION (MAR 2000)

(a) The following definitions apply in this provision: “Agency Protest Official for GSA” means the official in the Office of Acquisition Policy designated to review and decide procurement protests filed with GSA. “Deciding official” means the person chosen by the protester to decide the agency protest. The deciding official may be either the Contracting Officer or the Agency Protest Official.

(b) The filing time frames in FAR 33.103(e) apply. An agency protest is filed when the protest complaint is received at the location the solicitation designates for serving protests. GSA’s hours of operation are 8:00 a.m. to 4:30 p.m. Protests delivered after 4:30 p.m. will be considered received and filed the following business day.

(c) A protest filed directly with the General Services Administration (GSA) must:

(1) Indicate that it is a protest to the agency.

(2) Be filed with the Contracting Officer.

L-3

(3) State whether the protester chooses to have the Contracting Officer or the Agency Protest Official for GSA decide the protest. If the protest is silent on this matter, the Contracting Officer will decide the protest.

(4) Indicate whether the protester prefers to make an oral presentation, a written presentation, or an oral presentation confirmed in writing, of arguments in support of the protest to the deciding official.

(5) Include the information required by FAR 33.103(d)(2):

(i) Name, address, fax number, and telephone number of the protester.

(ii) Solicitation or contract number.

(iii) Detailed statement of the legal and factual grounds for the protest, to include a description of resulting prejudice to the protester.

(iv) Copies of relevant documents.

(v) Request for a ruling by the agency.

(vi) Statement as to the form of relief requested.

(vii) All information establishing that the protester is an interested party for the purpose of filing a protest.

(viii) All information establishing the timeliness of the protest (see paragraph (b) of this provision).

(d) An interested party filing a protest with GSA has the choice of requesting either that the Contracting Officer or the Agency Protest Official for GSA decide the protest.

(e) The decision by the Agency Protest Official for GSA is an alternative to a decision by the Contracting Officer. The Agency Protest Official for GSA will not consider appeals from the Contracting Officer’s decision on an agency protest.

(f) The deciding official must conduct a scheduling conference with the protester within three

(3) days after the protest is filed. The scheduling conference will establish deadlines for oral or written arguments in support of the agency protest and for agency officials to present information in response to the protest issues. The deciding official may hear oral arguments in support of the agency protest at the same time as the scheduling conference, depending on availability of the necessary parties.

(g) Oral conferences may take place either by telephone or in person. Other parties (e.g., representatives of the program office) may attend at the discretion of the deciding official.

(h) The following procedures apply to information submitted in support of or in response to an agency protest:

(1) The protester and the agency have only one opportunity to support or explain the substance of the protest (either orally, in writing, or orally confirmed in writing).

L-4

(2) GSA procedures do not provide for any discovery.

(3) The deciding official has discretion to request additional information from either the agency or the protester. However, the deciding official will normally decide protests on the basis of information provided by the protester and the agency.

(4) Except as provided in paragraph (h)(5)(ii) of this provision, the parties are encouraged, but not required, to exchange information submitted to the Agency Protest Official for GSA.

(5) If the agency makes a written response to the protest, the following filing requirements apply:

(i) The agency must file its response to the protest with the deciding official within five (5) days after the filing of the protest.

(ii) The agency must also provide the protester with a copy of the response on the same day it files the response with the deciding official. If the agency believes it needs to redact or withhold any information in the response from the protester, it must obtain the approval of the deciding official.

(i) The deciding official will resolve the protest through informal presentations or meetings to the maximum extent practicable.

(j) An interested party may represent itself or be represented by legal counsel. GSA will not reimburse the party for any legal fees related to the agency protest.

(k) GSA will stay award or suspend contract performance in accordance with FAR 33.103(f).

The stay or suspension, unless over-ridden, remains in effect until the protest is decided, dismissed, or withdrawn.

(l) The deciding official will make a best effort to issue a decision on the protest within twenty-eight (28) days after the filing date. The decision may be oral or written. If the decision is communicated orally to the protester, the deciding official will confirm in writing within three

(3) days after the decision.

(m) GSA may dismiss or stay proceedings on an agency protest if a protest on the same or similar basis is filed with a protest forum outside of GSA.

(End of provision)

L.5 RESERVED

L.6 FAR 52.215-20 REQUIREMENTS FOR COST OR PRICING DATA OR

INFORMATION OTHER THAN COST OR PRICING DATA (OCT 1997) ALTERNATE

IV (OCT 1997)

L-5

Offerors shall submit a Basis of Estimate (FOLDER I), DCAA Audit Information (FOLDER J) Compensation Plan and Policy for Uncompensated Overtime (FOLDER K), and Cost/Price Spreadsheets (FOLDER L). (See Section L.12.5.)

Failure to comply with any of these provisions may constitute sufficient cause to justify rejection of a proposal.

L.7 GSAM 552.252-5 AUTHORIZED DEVIATIONS IN PROVISIONS

(DEVIATION FAR 52.252-5) (SEP 1999)

(a) Deviations to FAR provisions.

(1) This solicitation indicates any authorized deviation to a Federal Acquisition Regulation (48 CFR Chapter 1) provision by the addition of “(DEVIATION)” after the date of the provision, if the provision is not published in the General Services Administration Acquisition Regulation (48 CFR Chapter 5).

(2) This solicitation indicates any authorized deviation to a Federal Acquisition

Regulation (FAR) provision that is published in the General Services Administration Acquisition Regulation by the addition of “(DEVIATION (FAR provision no.))” after the date of the provision.

(b) Deviations to GSAR provisions. This solicitation indicates any authorized deviation to a General Services Administration Acquisition Regulation provision by the addition of “(DEVIATION)” after the date of the provision.

(c) “Substantially the same as” provisions. Changes in wording of provisions prescribed for use on a “substantially the same as” basis are not considered deviations.

L.8 OFFER ACCEPTANCE PERIOD

The Offeror shall complete Block 12 of each SF 33 submitted with full cognizance of the minimum acceptance period established herein. "Acceptance period," as used in this provision, means the number of calendar days available to the Government for awarding a Contract from the date specified in this solicitation for receipt of offers. The Government requires a minimum acceptance period of not less than 365 calendar days. Offerors may specify a longer acceptance period than the Government's minimum requirement.

L.9 PROPOSAL PREPARATION COSTS

L-6

The Government will not reimburse Offerors for any cost incurred for the preparation and submission of a proposal in response to this solicitation.

L.10 DISPOSITION OF UNSUCCESSFUL PROPOSALS

Each proposal will be disposed of by the Government pursuant to its records policy.

L.11 GENERAL PROPOSAL INSTRUCTIONS

The Offeror shall follow these general proposal instructions. Non-compliance may result in the Offeror being ineligible for award. All proposal information is subject to verification by the Government. All information within the page limitations of the solicitation is subject to evaluation.

L.11.1 Electronic Copy of Proposal (No Paper)

Offerors shall submit one (1) electronic proposal, according to the specific proposal instructions in Section L.12. All information shall be provided on CD-R (not CD-RW) compact disks, using Microsoft Word 2003 (.doc format) and Microsoft Excel 2003 (.xls format) compatible and/or Adobe Acrobat 7.0 format. Pricing shall be submitted in Microsoft Excel 2003 (.xls format).

All CD-R compact disk(s) shall be labeled with the solicitation number, company name and date.

Offerors shall ensure that all disks are virus free. Nothing may be on the disks except the proposal files.

L.11.2 Packaging and Distribution

Proposals are due no later than 1:30 P.M., Central Time, on November 17, 2006. Each proposal must be submitted in a single common outer package to the address below. Failure to properly address the outer cover of an offer may cause the delivery of the offer to be late and thereby rejected. This is the only method by which proposals will be accepted.

General Services Administration Office of Business & Support Services (6ADB) 1500 E. Bannister Road, Room 1161 Kansas City, MO 64131

Attention: Mary Catherine Beasley

RFP #TQ2006MCB0002

Closing Date and Time: ____________________

L.11.3 Rejection of Multiple or Alternate Offers (RESERVED)

L-7

Only one offer will be accepted from a single prime contractor. Multiple or alternate offers from the same prime contractor, constitutes a material nonconformity and will result in all of its offers being rejected.

L.11.4 Proprietary Data

Offerors submitting proprietary data will mark them as follows in accordance with the requirements of FAR 52.215-1(e), which is incorporated by reference. FAR 52.215-1(e) states:

"Offerors or quoters who include in their proposals or quotations data that they do not want disclosed to the public for any purpose or used by the Government except for evaluation purposes, shall:

(a) Mark the title page with the following legend:

This proposal or quotation includes data that shall not be disclosed outside the Government and shall not be duplicated, used or disclosed in whole or in part for any purpose other than to evaluate this proposal or quotation. If, however, a Contract is awarded to this Offeror or quoter as a result of or in connection with the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting Contract. This restriction does not limit the Government's right to use information contained in this data if it is obtained from another source without restriction. The data subject to the restriction is contained in sheets (insert numbers or other identification of sheets). The title page is not included in the page count and will not be evaluated.

(b) Mark each sheet of data it wishes to restrict with the following legend:

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal or quotation.

L.11.5 Format

Offerors shall use the following format:

(a) Page size shall be 8.5 x 11 inches;

(b) Pages shall be single-spaced;

(c) The font size shall be no less than twelve (12) point except for tables, charts, graphs and figures, which shall be no smaller than eight (8) ten (10) point; text in “screen shot”, intended for representation of the actual item, are exempt from font size requirements when there is accompanying text explaining them.

L-8

(d) Top and bottom margins shall be at least one-inch. Margins may contain a disclaimer regarding proprietary information in the footer and provide corporate logos in the header within the one-inch top and bottom margins. Side margins shall be at least ¾-inch;

(e) All pages shall be numbered sequentially; and

(e) Pages within each file (regardless of placement within a folder) shall be numbered sequentially starting with page 1; and

(f) Tables, charts, graphs and figures may be used wherever practical to depict systems and layout, implementation schedules and plans.

L.11.6 Timely Resubmissions

An Offeror choosing to withdraw an earlier timely submitted offer and replace it with a new timely submitted offer must resubmit the entire offer. The new offer shall clearly indicate its standing relative to any existing offer on the first page of the offer. The lack of proper identification will result in a finding of material nonconformity with all offers being summarily rejected.

L.11.7 Proposal Revisions Requested by the Government

Any proposal revision requested by the Government shall be made by revising proposal pages.

Revised proposal pages are to be submitted using a different color for each set of revisions.

Indicate changes from the original page by right and left marginal vertical lines adjacent to the change. Include the revision number and the date of the revision at the bottom of the respective page.

L.12 SPECIFIC PROPOSAL INSTRUCTIONS

The Government will evaluate proposals in accordance with the evaluation criteria set forth in Section M of this solicitation. The proposal submission shall be clear, concise, and shall include sufficient detail to evaluate and substantiate the validity of stated claims. Offerors shall assume that the Government has no prior knowledge of the company's capability and experience.

L.12.1 Disks, Folders, Page Limits, File Titles

Proposals shall be divided into four separate CD-Rs as follows:

CD-R 1 – General CD-R 2 – Past Performance CD-R 3 – Alliant SB Basic Contract Plan CD-R 4 – Cost/Price

L-9

Offerors shall adhere to the page limitations, folder title, and electronic file title and type, specified below in the L.12.1 Table. Offerors shall include their company name in the filename.

Example below is for the ABC Company.

If page limitations are exceeded, the excess pages will be destroyed without consideration.

SECTION L.12.1 TABLE

CD-R

FOLDER SUBJECT OF FILE

PAGE

LIMIT

FILE NAME

A

GENERAL

(a) Readme file

(b) Transmittal Letter

(c) Solicitation, Offer and Award – Standard Form (SF) 33

(d) Abbreviations and Acronyms

No Limit

2-page Limit

Limited to Form

ABC-

README.pdf

ABC-LTR.pdf

ABC-SF33.pdf

ABC-GLOSS.pdf

B

(a) Representation and Certifications

(b) Section K

Limited to Form

Section

ABC-ORCA.pdf

ABC-SECK.pdf

C

Secret facility clearance documentation

ABC-SECURE.pdf

D

If applicable, Contractor Team Arrangement, i.e., joint venture contract, and/or SBA Mentor/Protégé Agreement.

ABC-CTA.pdf

E

RESERVED

F

PAST PERFORMANCE

a) Past Performance Table Summary

Past Performance Tables (Use Section J, Attachment 6)

5-Page

Limited to Table Format

ABC-PPSUM.pdf

ABC-PAST.xls

L-10

G

RESERVED

H

ALLIANT SB BASIC CONTRACT PLAN

(a) Resources (1A) Purchasing System ApprovalDocumentation (as applicable if available)

(1A) Contractor Purchasing System (CPSR) Report

Findings/ACO Purchasing System Approval, as applicable.

(1B) Program Manager Resume

(1C) Reserved

(b) Program Management System

(1D) EVMS Approval (if available)

(c) Corporate Commitment

(1E) Organizational Chart

(1F) Executive Summary

30-page

2-page limit not included in Basic Contract Plan

ABC-BCP.pdf

ABC-PUR.pdf

PMResume.pdf

ABC-SYS.pdf

ABC-EVMS.pdf ABC-CORP.pdf

ABC-ORG.pdf

ABC-EXSUM.pdf

L-11

I

J

K

L

COST/PRICE

(1) Basis of Estimate

(2) DCAA Audit Information

(3) Compensation Plan and Policy for Uncompensated Overtime

(4) Cost/Price Spreadsheets (Use Section J, Attachments 2 and 3)

10-page

25-page excluding list of labor categories

Table Format

ABC-BASIS.pdf

DCAA.AUDIT.pdf

ABC-COMP.pdf

ABC-J2.xls ABC-J3.xls

L.12.2 CD-R 1

FOLDER A: GENERAL

(a) Readme File – As part of the electronic copies, the Offeror shall include a “Readme” file that identifies each file and the file contents, adhering to the database file naming conventions specified in the Section L.12.1 Table.

The following is an example of the type of information that should be provided in the ABC- README.pdf” file. “Readme.txt” file:

CD-R FOLDER FILE NAME CONTENTS

CD-R 1 Folder A ABC-

README.pdf File Identification

CD-R 1 Folder A ABC-LTR.pdf Transmittal Letter CD-R 1 Folder A ABC-SF33.pdf Solicitation, Offer and Award–Standard Form (SF) 33 Etc.

(b) Transmittal Letter – The Offeror shall submit a cover letter with the proposal. The cover letter shall address the information required by FAR 52.215-1(c)(2).

(c) Solicitation, Offer and Award (SF 33) – Signing the SF33 in Block #17 constitutes the Offeror's acceptance of the terms and conditions of the solicitation. Offerors cannot take exception to any terms or conditions of the solicitation. The SF33 must be executed by a

L-12 representative of the Offeror authorized to commit the Offeror to contractual obligations. The Offeror on the SF33 must match the information for the Offeror in the CCR. Acknowledgment of receipt of any amendments shall be made in Block 14 of the SF 33. The Government requires a minimum acceptance period of not less than 365 days in Block 12 of the SF33, as specified in Section L.8.

(d) Abbreviations and Acronyms – The Offeror may insert a file with any abbreviations and acronyms that will be used in the Offeror’s proposal.

FOLDER B: REPRESENTATIONS AND CERTIFICATIONS

The Offeror shall submit a completed “Representations and Certifications” that was entered into the Online Representations and Certifications Application (ORCA) and completed Section K pages.

FOLDER C: SECRET FACILITY CLEARANCE

If available at the time of offer submission, Offerors shall submit documentation a letter signed by their Facility Security Officer identifying the Offeror’s CAGE code, Facility Clearance Level (FCL) and Cognizant Security Agency (CSA), such as the Defense Security Service (DSS) Office, verifying that at a minimum an interim Secret clearance has been active sometime within the previous three years (three years from solicitation closing date) and that an approval letter is on file for government review. In lieu of a letter from the CSA Office, Offerors may provide a screen print of their information from the Industrial Security Facilities Database (ISFD). Documentation must show showing that a secret facility clearance, as granted by the Defense Industrial Security Clearance Office (DISCO), has been active for the offeror’s facility(s) sometime within the previous three years (three years from solicitation closing date). The facility clearance does not have to be active at time of proposal submission.

GSA will not sponsor Offerors for any type of DISCO Security Clearances.

The Government considers this requirement a definitive responsibility matter, i.e., Offerors must submit proof of these credentials before contract award. This proof shall be made available to the Government after the deadline for receipt of offers within five (5) working days of the Government’s request for it. Failure to submit that information within five (5) working days will be deemed a material nonconformity and result in rejection of your offer. Offerors are advised to have that information at the ready so it is available when the Government requests it.

There is no security requirement for safeguarding at the Basic Contract level.

FOLDER D: DOCUMENTATION REQUIREMENTS FOR CONTRACTOR TEAM

ARRANGEMENTS (IF REQUIRED)

L-13

To propose on the Basic Contract, potential Offerors may form a Contractor Team Arrangement (CTA), as that term is defined in FAR 9.601(1), but they are not required to do so. Offeror’s may also enter into subcontractor arrangements pursuant to FAR 9.601(2); however, provides an alternative definition for the term “contractor team arrangement” based upon a prime/subcontractor relationship, the Government will not evaluate consider this type of arrangement at the Basic Contract level for purposes of past performance evaluation, nor require additional documentation regarding the proposed prime/subcontractor contractual relationship, nor require identification/qualifications of the proposed subcontractors.

The Offeror's plan on “how” (not “who”) it will acquire, track and montior proposed procedures and methods for acquiring, tracking and monitoring subsequently proposed subcontractors is the only subcontractor-related issue that will be considered at the Basic Contract level for purposes of Award. This will be evaluated and it is cover in the limited context of evaluating under the Offeror's Alliant SB Basic Contract Plan, under Section M.5.2, for the subfactor "Resources." Offerors are not requested nor are they required to provide lists of proposed subcontractors; however, they may identify the specific capabilities they plan to subcontract in the context of communicating their overall strategy to ensure successful performance on all requirements of the Basic Contract.

Special Instructions for Small Business Joint-Ventures

If the offeror is a joint-venture entity, the joint-venture contract satisfying the SBA program requirements shall be submitted in Folder D.

The following additional information is provided concerning joint-ventures. Much of this information is already available in the public domain to interested parties, with the balance being how to apply it to this RFP. Conform ALL guidance about joint-ventures to the following:

(1) Offerors submitting Offers in the form of a joint-venture need not obtain preapproval from the SBA. However, they must conform to guidelines and regulations pertaining to the composition and size standards of the joint-venture membership established by SBA.

Note that the SBA is the sole authority for making determinations of small business status for small business programs and its determinations are binding on the offeror and the contracting officer.

(2) Members of a joint-venture are permitted to individually qualify to the size standard pursuant to 13 CFR § 121.103(h)(3)(i)(B)(1).

(3) An offer submitted by a joint-venture must include a copy of the joint-venture contract with its offer in Folder D. Failure to submit a copy of the joint venture contract with the offer shall result in the offer being summarily rejected.

(4) Joint-venture offers must be made in the name of the joint-venture entity. The joint-venture contract must identify the managing venturer, the joint-venture members and who

L-14 will have signature authority on behalf of the joint-venture. The party signing the offer for the joint-venture should be listed as having such authority.

(5) The past performance tables and Basic Contract Plan (BCP) information shall be submitted in the name of the joint-venture entity. It is the joint-venture as a whole, and not the individual members that submits the past performance and BCP information. Said another way, a joint-venture needs to meet the past performance and BCP evaluation items as a combined business entity, not individually. The experience and past performance of qualifying joint venture members automatically inheres to the combined joint-venture business entity. If the joint-venture is formed through an SBA approved mentor-protégé arrangement, only the past performance in which the mentor and protégé participated together in that past performance example, will be evaluated. That being said, past performance examples where the protégé completed work outside the mentor-protégé arrangement will also be evaluated

(6) The joint-venture offeror and each joint-venture member shall submit separate certifications and representations mandated per Section K.

(7) Since this is a multiple-award IDIQ procurement, we consider the “dollar value of the procurement” to be the cumulative estimated value of the multiple award contracts including options, which is $15 billion.

SBA Mentor Protégé Arrangements

Regarding SBA approved mentor-protégé arrangements, Offerors shall refer to 13 CFR 121.103(h)(3)(iii) and 13 CFR 124.520 as two among many sources of information. (Be sure to read the most recent edition of the applicable CFR.) Each Offeror relying upon its status in an SBA approved mentor-protégé relationship shall submit, in addition to the joint-venture documentation between the mentor and protégé, evidence of that relationship with its Offer in Folder D. If the joint-venture is formed through an SBA approved mentor-protégé arrangement, only the past performance, in which the mentor and protégé participated together, in that past performance example, will be evaluated. That being said, past performance examples where the protégé completed work outside the mentor-protégé arrangement will also be evaluated

Because the Procuring Contracting Officer is relying on the SBA approved Mentor-Protégé agreement/arrangement document for evaluation purposes, failure to provide a copy with the Offer shall result in the Offer being summarily rejected.

Additional Instructions

The Government will recognize the integrity and validity of a CTA, provided that the CTA arrangement is fully identified and disclosed to the Government in its Offer. The document(s) establishing the CTA is an agreement between and among the entities establishing the CTA relationship, and is not drafted by the Government. Accordingly, there is no specific form or

L-15 format that the CTA documents must adhere to, although Offerors are required to address the following issues in their CTA documents:

(a) Identify the Parties – The CTA documents should identify the entities which make up the CTA relationship, including disclosure of the primary point of contact for each of the members of the team;

(b) Designation of a “team lead” – The CTA documents should disclose whether or not the CTA designates a particular entity as the “team lead,” and if so, the CTA should clearly explain the specific duties/responsibilities of the “team lead” to the other members of the team and to the Government;

(Note: If a CTA designates a team lead, the Government requests that the team lead be the primary point of contact with the Government during evaluation of the CTA’s Proposal. This means that the Government requests a “release” from each non-“lead” member of the team so that the Government can discuss confidential/privileged information about the non-“lead” members of the CTA with the designated team lead.)

(c) Specific Duties/Responsibilities – The CTA documents should clearly describe the specific duties/responsibilities of each member of the team as they relate to each other, and explain the specific duties/responsibilities that each team member will have for purposes of contract performance under the Basic Contract (e.g., one team member will be primarily responsible for performing specific component areas listed in Section C, while other team members will be primarily responsible for performing other specific component areas listed in Section C; etc). A CTA can blend cost and pricing data from the CTA team; however, a single team member with an adequate accounting system must be the identified as the lead for all cost and pricing data and compliance with FAR 16.301-3(a)(1);

(d) Pricing – The CTA document should explain how the team members have divided responsibilities for purposes of proposing price/costs. A CTA can blend cost and pricing data from the CTA team; however, a single team member with an adequate accounting system must be the identified as the lead for all cost and pricing data and compliance with FAR 16.301-3(a)(1). For example, if one member of the team is responsible for proposed price/costs for a particular labor category, while another entity in the CTA is proposing price/costs for a different labor category, the CTA documents should disclose which of the respective team members is responsible for proposing which specific price/cost information;

(e) Invoicing and Payment – The CTA document should explain how the team members have addressed issues relating to invoicing and distribution of payments. For example, the CTA document should generally address which member of the team is responsible for invoicing the Government and receiving payment. Similarly, the CTA documents should explain how the distribution of payments will be made if the payments are made to the “team lead,” but another team member performed the services. Under such circumstances, the CTA document should clearly indicate that all team members agree to this method of payment. The CTA document should also acknowledge that any dispute involving the distribution of payment between the

L-16 team lead and the team members will be resolved by the team members themselves, without any involvement by the Government;

(f) Replacement of Team Members – The CTA document should address the circumstances and procedures for replacement of team members, including the team lead, and whether or not the approval of the Government is required prior to replacing any team members; The CTA document should address that in order to replace team members, including the team lead, Government approval is required.

(g) Duration of the CTA – The CTA document should address the duration of the CTA, including when it becomes effective, when it expires, and the basis for termination.

FOLDER E: RESERVED

L.12.3 CD-R 2

FOLDER F: PAST PERFORMANCE TABLES AND PAST PERFORMANCE TABLE

SUMMARY

Offerors may submit (up to) a five-page summary describing their past performance efforts in Tables 1 and 2. This five-page summary is intended to be open-ended for Offerors to provide whatever information they believe may be relevant to the Government as it evaluates its proposal under the Past Performance Evaluation factor. For example, an Offeror may want to explain past performance information provided in either Table 1 or 2 for its “affiliates,” explain that the past performance information provided in either Table 1 or 2 applies to a particular component entity that forms a Contractor Team Arrangement; or provide background information about a particular project.

The Government shall consider Past Performance information regarding predecessor companies to the Offeror, but only if such information is otherwise “conforming” to the requirements for such information as set-forth herein. Non-federal efforts are acceptable in both tables as long as they are within the following parameters:

(a) Acceptable Offers – Offerors shall use the Past Performance Tables in Section J, Attachment 6, which is a Microsoft Excel spreadsheet. In order to qualify as conforming to the requirements of the solicitation, the relevant past performance information submitted must:

(1) Be ongoing or completed after January 1, 2004;

(2) Include at least one of the three component areas in Section C (Infrastructure, Management, Applications);

L-17

(3) For Table 1, no dollar threshold; for Table 2, dollar threshold of $100K estimated dollars for cost contracts, $100K ceiling for T&M contracts, or $100K for Fixed Price Contracts. The $1M is inclusive of options; Be over $100K estimated amount for cost contracts;

(4) Meet the specific requirements applicable to the particular Table;

(5) Relate to the Offeror’s direct experience with “service contracts” (as that term is defined in FAR 37.101) or “task order contracts” (as that term is defined in FAR 16.501-1), as requested for the particular Table. (Efforts for supplies will not be considered relevant.);

(6) Table I shall relate to projects for which the Offeror is (or was) the prime-contractor.

Table 2 shall relate to projects for which the Offeror was the prime or performed as a first-tier subcontractor where the Offeror had complete (turnkey) responsibility for a separately identifiable part of an overall system or service.

(b) Non-Acceptable Offers – Offerors shall not submit, and the Government will not evaluate, past performance information which is deemed to be not relevant or non-conforming. Examples of non-conforming past performance information include (but are not limited to) the following:

(1) Information which does not conform to the instructions for the particular Table;

(2) Projects for which the primary purpose of the project was the delivery of goods (as opposed to projects for which the primary purpose was the performance of services);

(3) Projects completed before January 1, 2004; more than three (3) years ago.

(4) Past Performance information for proposed subcontractors.

(c) Table 1 – The purpose of Table 1 is to evaluate how well the Offeror performed in a multiple-award environment. Offerors shall include all applicable efforts up to This table shall be limited to twenty (20) applicable efforts within the parameters listed in this section, chosen by the Offeror, considering the solicitation requirements and evaluation criteria. If an Offeror has less than 20 applicable efforts, all of them shall be listed. If an Offeror has more than 20 applicable efforts, it shall choose 20. Offerors shall list the master contract only, not any task order contracts, which may have been issued thereunder. Contracts that meet the criteria herein shall be included irrespective of whether any task orders have been issued against the Basic Contract. Efforts shall be listed in chronological order by start date with the most recent at the top.

In Table 1, Offerors are limited to:

(1) Governmentwide Acquisition Contracts (GWACs), L-18

(2) Multiple Award Indefinite Delivery/Indefinite Quantity Contracts (MA-IDIQs) service contracts (only), as defined in FAR 16.504(c), and

(3) (3) Multiple Award Blanket Purchase Agreements (MA-BPAs) for services (only), (under both FAR 8.405-3 and FAR 13.303).

In Table 1, Offerors may not include any single award BPAs (under either FAR 8.405-3 or FAR 13.303), Single Award Indefinite Delivery Indefinite Quantity (SA-IDIQs) or Basic Ordering Agreements under FAR 16.7.

Offerors shall enter their company name on each table in the cell indicated. Specific information in columns includes:

Column A Enter Predecessor Name if CTA as defined in FAR 9.601(1) Column B Enter GWAC, MA-IDIQ or MA-BPA Contract Number Column C Enter Recognizable Title of Contract (50 character limit) Column D Enter Awarding Agency Name and Address Column E Enter Contractual Point-of-Contact, Phone and email Column F Enter Program Office Point-of-Contact, Phone and eMail Column G Enter Yes or No -- Is this contract a GWAC?

Column H Enter Period of Performance - Start Date (MM-DD-YYYY) Column I Enter Period of Performance - End Date (MM-DD-YYYY) Column J Enter scope to which component area(s) in Section C:

Enter “1” for Infrastructure in Section C.3.1 Enter “2” for Application Services in Section C.3.2 Enter “3” for IT Management Services in Section C.3.3 Enter “12” for Infrastructure and Application Services Enter “13” for Infrastructure and IT Management Services Enter “23” for Application Services and IT Management Services Enter “123” if effort encompassed all three component areas

Column K Enter Number of Task Orders Issued under the GWAC, MA-IDIQ or MA-

BPA

Column L Enter Total Estimated Obligated Dollars of all Task Orders Issued under the GWAC, MA-IDIQ or MA-BPA, including options (not GWAC/MA- IDIQ contract ceiling)

(d) Table 2 – The purpose of Table 2 is to evaluate how the Offeror performed a particular contract requirement. Offerors may include Task Orders issued against single award contracts in Table 2. Offerors shall include all applicable efforts up to This table shall be limited to fifty (50) applicable efforts fifty within the parameters listed in this section, chosen by the Offeror, considering the solicitation requirements and evaluation criteria . If an Offeror has less than 50 efforts, the Offeror shall list all applicable efforts. If an Offeror has more than

L-19

50 efforts, the Offeror may choose its most relevant 50 efforts. Efforts shall be listed in chronological order by start date with the most recent at the top. Offerors are encouraged to include any efforts performed that encompass OCONUS, multiple subcontractors and Cost Type Contracts.

In Table 2, Offerors are limited to:

(1) Single award service contracts;

(2) Task orders (no delivery orders contracts), applicable to NAICS code 541512, applicable to Section C of this solicitation, which have been issued under GWACs, MA-IDIQs, SA-IDIQs, BPAs or GSA Schedules.

Offerors shall enter their company name on each table in the cell indicated. Specific information in columns includes:

Column A Enter Predecessor Name if CTA as defined in FAR 9.601(1) Column B Enter Single Award Service Contract or Task Order Number Column C Enter BPA Number (if applicable) Column D Enter Recognizable Title of Contract (100 character limit including all key strokes) Column E Enter Customer Name and Address Column F Enter Contractual Point-of-Contact, Phone and eMail Column G Enter Program Office Point-of-Contact, Phone and eMail Column H Enter Total Estimated (Cost type), Ceiling (T&M type), or Fixed Price

Dollar Amounts Including Options Column I Enter Period of Performance - Start Date (MM-DD-YYYY) Column J Enter Period of Performance - End Date (MM-DD-YYYY) Column K Effort was similar in scope to which component area(s) in Section C:

Enter “1” for Infrastructure in Section C.3.1 Enter “2” for Application Services in Section C.3.2 Enter “3” for IT Management Services in Section C.3.3 Enter “12” for Infrastructure and Application Services Enter “13” for Infrastructure and IT Management Services Enter “23” for Application Services and IT Management Services Enter “123” if effort encompassed all three component areas

Column L Number of Subcontractor Teams Utilized?

Column M Was any OCONUS work involved? Yes or No Column O Contract Type

(If Task Order, enter Task Order type in lieu of Contract Type)

Use FAR 16 definitions with following abbreviations:

L-20

Enter “A” for Firm-fixed-price contracts Enter “B: for Firm-fixed price-award fee contracts Enter “C” for Fixed-price contracts with economic price adjustment Enter “D” for Fixed-price incentive contracts Enter “E” for Firm-fixed-price, level-of-effort term contracts Enter “F” for Cost contracts Enter “G” for Cost-sharing contracts Enter “H” for Cost-plus-incentive-Firm contracts Enter “I” for Cost-plus-incentive-Successive contracts Enter “J” for Cost-plus-award-fee contracts Enter “K” for Cost-plus-fixed-fee contracts Enter “L” for Definite-quantity contracts Enter “M” for Requirements contracts Enter “N” for Indefinite-quantity contracts Enter “O” for Time-and-materials contracts Enter “P” for Labor-hour contracts

(e) Government Targeted Task Orders/Contracts – Offerors shall indicate in bold characters, three (3) efforts from Table 2 for which the Government will target its evaluation. If Offerors fail to identify up to three efforts, the Government will select from Table 2.

The Government intends to use reasonable efforts to check approximately ten (10) efforts (total) for each Offeror, selected from Tables 1 and 2, including the three (3) efforts which the Offeror has identified. The Government reserves the right to check more or fewer efforts, at its discretion, and does not guarantee that it will contact any particular effort listed in Table 1 or 2, even any of the three efforts specifically listed by the Offeror.

(f) CTAs – For those Offerors that submit a proposal in the form of a CTA (exclusive of subocontractors), the Government will evaluate the Past Performance information submitted in Section L.12.2, Folder D for:

(1) The CTA itself (if such information exists); and/or

(2) The individual entities represented in the CTA, and otherwise conforming to the requirements of the solicitation;

(3) Any past performance in which a member of a CTA performed the work, that member must be identified in the corresponding example.

FOLDER G: RESERVED

L.12.4 CD-R 3

L-21

FOLDER H: ALLIANT SB BASIC CONTRACT PLAN

Executive Summary: The Offeror shall provide an executive summary that describes the significant attributes of its proposal.

General Instructions (Objectives): The Offeror shall explain in the Alliant SB Basic Contract Plan how it will continuously identify, mitigate, manage and control risks within its holistic approach for managing the comprehensive scope of the Alliant SB program. The Offeror shall identify any gaps or weaknesses in past performance and specifically address them as part of the Alliant SB Basic Contract Plan. The Offeror should convey its ability to insure successful performance of all aspects of the Basic Contract and Orders to include all 3 component areas of Section C (i.e. Infrastructure, Application Services and IT Management Services). The Offeror shall demonstrate a clear understanding of the management and performance requirements of this solicitation by providing a concise description of its management approach for the following three subfactors; (a) Resources; (b) Program Management; and (c) Corporate Commitment.

Specific Instructions: The Offeror shall demonstrate a clear understanding of the management and performance requirements of this solicitation by providing a concise description of its management approach for the following three subfactors; (a) Resources; (b) Program Management; and (c) Corporate Commitment.

(a) Resources – The Offeror shall describe its plan to have adequate resources, internal and external, readily available to respond to TORs that encompass all three component areas of Section C, as well as OCONUS work.

(1) Internal Resources – This includes the internal performance capabilities of the Offeror and its affiliates, internal divisions and subsidiaries, or in the case of a CTA, of the CTA itself or the members of the CTA. The Offeror shall describe current core capabilities, such as its ability to recruit, train, and retain high quality personnel; the number of personnel with security clearances and level of clearance; qualifications of key personnel, and effectiveness of business systems, including evidence of an approved adequate purchasing system.

The Offeror shall provide a resume for proposed Key Personnel selected to fill the roles of Contractor’s Program Manager (See duties in Section H.2.1) for the Basic Contract to include:

(i) Name

(ii) Address

(iii) Voice telephone number

(iv) Cell telephone number (if used)

(v) Fax telephone number

(vi) E-mail address

(vii) Administrative assistant’s contact information

L-22

(viii) Education, experience, relevant certifications/awards and security clearance level/date issued

If the Offeror does not currently employ the proposed personnel, the Offeror shall submit letters of commitment along with the individual’s resume.

If applicable, the Offeror shall provide a copy of its most recent Contractor Purchasing System Review (CPSR) audit results and purchasing system approval letter/memo from the cognizant Federal agency ACO (usually DCAA or DCMA).

evidence of an approved purchasing system by submitting an approval letter/memo issued by the cognizant federal agency (usually DCMA) ACO.the DCAA/DCMA-issued approval letter. Offerors should, as one source, review FAR Subpart 44.3, Contractors’ Purchasing Systems Review, to ascertain approved purchasing system requirements.

(2) External Resources – The Offeror shall describe its procedures and methods for “how” (not ”who”) it will provide a detailed description of the procedures and methods to be used to supplement its core internal capabilities in order to meet all contractual requirements, including performance of all three component areas of Section C.

Offerors should specifically address, particularly those areas not covered addressed by the internal resources or reflected in past performance, such as: its methodology for selecting, tracking, and managing subcontractors and other teaming arrangements, as applicable; methodology for providing OCONUS support; and approach to support continuity of operations in response to sudden workload surges, including contingency/disaster recovery situations.

If applicable, the Offeror may indicate the intent to use propose subcontractors as well as a brief description of the supplemental capabilities that will be provided by the proposed subcontractors; however, it should specifically not include a list of subcontractors, or provide a description of any specific lists or subcontractor’s qualifications. The Offeror should focus on the procedures and methods for acquiring, tracking and managing the subcontractors, and not provide a list of the subcontractors themselves.

(b) Program Management – The Offeror shall describe its program management strategy to include a comprehensive description of its program management information system and quality control program.

The Offeror shall explain how its Program Management Information System will effectively manage data deliverables in Section F.5.

The Offeror shall describe quality controls and surveillance methodologies employed to insure quality performance and compliance with all contractual requirements, including security and information assurance requirements. The Offeror shall explain the methodology for risk minimization, schedule controls, costs controls and efficient utilization of resources for ensuring

L-23 task accomplishment. The Offeror shall indicate evidence of an approved Earned Value Management System (EVMS), if applicable), by submitting an approval letter/memo issued by the cognizant Federal agency (usually DCMA) ACO. If an Offeror is working toward an approved EVMS on an ongoing project, the Offeror may submit a letter/memo from the cognizant Federal agency ACO on the project.

(c) Corporate Commitment – The Offeror shall identify corporate resources dedicated to the Alliant SB program and explain how the Alliant SB program will be optimized through its business development, technological innovations, proposal management and contract administration efforts.

The Offeror shall provide a detailed organizational chart of the business or corporate structure (including CTAs, as applicable) containing the names of individuals who will fill the key positions shown in that chart. In addition, the functional position title these individuals will have in the Alliant SB program should be clearly identified within the structure. The organizational chart shall also include the locations of the corporate headquarters, regional offices, any other satellite offices, as well as any pre-identified CTAs.

The Offeror shall provide a detailed description of the functional organization planned to perform this work, reflecting the responsibilities and authority to act and to commit business or corporate resources for timely problem identification and quick mitigation. Functional organization descriptions should be furnished in either narrative form or in the form of functional statements that clearly define lines of authority, responsibility and communication.

L.12.5 CD-R 4

FOLDER I - BASIS OF ESTIMATE

While the PCO anticipates that pricing for this acquisition will be based on adequate price competition and therefore does not require submission or certification of cost or pricing data, Offerors are cautioned to provide clear and concise explanations of their pricing methodology and their labor and burden estimating practice. Offerors are cautioned against unbalanced and unrealistic pricing.

The Basis of Estimate shall only encompass the “Continental United States (CONUS)”, defined as the 48 contiguous states plus the District of Columbia, and should reflect a clear understanding of work to be performed, take into account differences in skills, the…