SF30_P0001.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 08-Jul-2014 12:00 PM to 29-Jul-2014 12:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The CLIN extended description has changed from Services non-personal: The contractor shall furnish all labor, data, and travel (NTE $5,000.00) necessary to transition operations the solicitation terms and conditions. to Services non-personal: The contractor shall furnish all labor, data, and travel (NTE $5,000.00) necessary to transition operations the solicitation terms and conditions.Period of Performance Begin: 17 Jun 15Period of Performance End: 16 Jul 15.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

LIST OF ATTACHMENTS

Attachment 1: Pricing Table dated 12 Jun 2014

Attachment 2: Performance Work Statement dated 17 Jun 2014

Attachment 3: DD 254

Exhibit A – DD 1423, CDRLS A001 – A009

Questions and Answers (QA_V1)

SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS

The following have been added by full text:

252.204-7004 ALTERNATE A, system for award management (FEB 2014)

(a) Definitions. As used in this provision-- ``System for Award Management (SAM) database'' means the primary Government repository for contractor information required for the conduct of business with the Government.

``Commercial and Government Entity (CAGE) code'' means—

(1) A code assigned by the Defense Logistics Information Service (DLIS) to identify a commercial or Government entity; or

(2) A code assigned by a member of the North Atlantic Treaty Organization that DLIS records and maintains in the CAGE master file. This type of code is known as an ``NCAGE code.'' ``Data Universal Numbering System (DUNS) number'' means the 9-digit number assigned by Dun and Bradstreet, Inc. (D&B) to identify unique business entities.

``Data Universal Numbering System +4 (DUNS+4) number'' means the DUNS number assigned by D&B plus a 4-character suffix that may be assigned by a business concern. (D&B has no affiliation with this 4-character suffix.) This 4-character suffix may be assigned at the discretion of the business concern to establish additional SAM records for identifying alternative Electronic Funds Transfer (EFT) accounts (see FAR 32.11) for the same parent concern.

``Registered in the System for Award Management (SAM) database'' means that—

(1) The contractor has entered all mandatory information, including the DUNS number or the DUNS+4 number, and Contractor and Government Entity (CAGE) code into the SAM database;

(2) The contractor has completed the Core Data, Assertions, Representations and Certifications, and Points of Contact sections of the registration in the SAM database;

(3) The Government has validated all mandatory data fields, to include validation of the Taxpayer Identification Number (TIN) with the Internal Revenue Service (IRS). The Contractor will be required to provide consent for TIN validation to the Government as part of the SAM registration process; and

(4) The Government has marked the record ``Active.''

(End of clause)

The following have been deleted:

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

L-1 PROPOSAL PREPARATION INSTRUCTIONS

Apr 2014

1. Points of Contact (POC). The CO and/or Contract Specialist (CS) are the only POCs for this acquisition. Address any questions or concerns you may have to the CO or CS specified in Blocks 10a through 10c of the Standard Form (SF) 33. Written requests for clarification (questions) may be sent to the CO and CS to the e-mail address located in Block 10c of the SF 33. Changes to the CO POC will be made by amendment to the solicitation. Late requests may not be considered.

2. Authorized Offeror Personnel. Provide the name, title, e-mail address, voice and fax telephone numbers, street and mailing address (if a PO Box is used) of the primary and alternate company/division POC regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

3. Company/Division Address, Identifying Codes, and Applicable Designations. Provide company/division's street address, CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation.

4. Debriefings. The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with (IAW) FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

5. 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 CO and CS in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error.

6. Electronic Reference Documents. All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at https://www.fbo.gov/. Potential offerors are encouraged to subscribe for real-time e-mail notifications in order to receive information posted to the website for this solicitation.

7. Communications. The CO will control exchanges of source selection information between Government and offerors. The Government may use email to transmit such information to offerors only if the email includes “Source Selection Information – See FAR 2.101 & FAR 3.104” in the Subject line. Otherwise, the Government will transmit source selection information via fax, United States Postal Service, or commercial carrier.

B. GENERAL INSTRUCTIONS

1. To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, technical requirements, and Contract Security Classification Specification, in addition to those identified as evaluation factors or subfactors.

2. This section of the Request for Proposal (RFP) 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 requested by the RFP and must be submitted IAW these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and RFP. Non-conformance with the instructions provided in this RFP may result in an unfavorable proposal evaluation. Alternate proposals will not be accepted.

3. Offeror’s proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather 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 facilities and experience and will base its evaluation on the information presented in the offeror's proposal.

4. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

5. The proposal acceptance period is specified in Section A of the solicitation.

6. IAW FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. After contract award, the Government will destroy extra copies of such unsuccessful proposals.

C. ORGANIZATION.

1. Number of Copies/Page Limits. The offeror shall prepare the proposal as set forth in the Proposal Table (Table 1 below). The titles and content of each part, all of which shall be within the required page limits, are defined in Table 1. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Each page shall be counted except cover pages, table of contents, matrices, and glossary. Offeror shall provide five (5) hard copies and one electronic copy (see para 8) including all four parts described in Table 1. Proposal change pages are customarily subject to same page limitations stated in the table below; however, deviated page limitations may be required on responses to Evaluation Notices (ENs).

2. The response shall consist of four (4) separate parts: Part I – Technical Proposal, Part II – Present/Past Performance Information (PPI), Part III – Price, and Part IV – Contract Documentation.

The content of each proposal binder is described in detail as follows:

TABLE 1 – PROPOSAL ORGANIZATION (within binders)

PART

TITLE

PAGE NUMBERS

I

Technical Proposal

II

Present/Past Performance

III

Price

No Limit (See paragraph F)

IV

Contract Documentation

No Limit (See paragraph G)

& Mission Essential Service Plan

TABLE 2 – BINDER ORGANIZATION (within binders)

COPY

PARTS TO INCLUDE

ORIGINAL

I, II, III, IV

COPY 1

I, II

COPY 2

I, II

COPY 3

I, II

COPY 4

I, II

BINDER SIZE LIMITATIONS: Binders shall not exceed 2”. Reproduction of the entire RFP is unnecessary and unwanted.

3. Page Size and Format.

a. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Line spacing shall be 1.5, at least double-spaced between paragraphs and factors or sub-factors. Except for the reproduced sections of the solicitation document, Section J, Attachment 1 (Pricing Table), and items specified in paragraph (b) below, the text size shall be no less than 12-point, Times New Roman, Arial or Courier type. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one-inch margins on all sides. Pages shall be numbered sequentially by part.

b. Legible tables, charts, graphs and figures may be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the part, and shall count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics and not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than ten-point.

4. Cross Referencing. The offeror shall provide a cross-reference matrix at the beginning of Part I-Technical volume indicating the PWS paragraph number and the corresponding proposal paragraph. To the greatest extent possible, each part shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other parts of the proposal. Cross referencing within a proposal part is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation which is not found in its designated part will be assumed to have been omitted from the proposal.

5. Indexing. Tab indexing shall be used to identify parts.

6. Glossary of Abbreviations and Acronyms. Each part shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective parts.

7. Binding and Labeling. The proposal shall be bound in one-inch, three-ring, loose leaf binders permitting the binders to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each binder, clearly marked with the title, copy number, solicitation identification, and the offeror’s name. The same identifying data shall be placed on the spine of each binder. If needed, offerors should apply all appropriate markings including those prescribed IAW FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

8. Electronic Documents. The offeror shall submit electronic proposal documents (Parts I, II, III, & IV) via email in a format readable by Microsoft (MS) Office Word 2010, MS Office Excel 2010, and MS Office Power Point 2010, as applicable. Each volume shall be submitted as a separate attachment to an email addressed to amy.byars@us.af.mil and donna.williams.6@us.af.mil.

D. PART I – TECHNICAL PROPOSAL

1. The Technical Part should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

2. Identify submitted material by corresponding factor, subfactor, and paragraph/element herein. If an offeror is subcontracting/teaming with another vendor who will perform more than thirty percent of the work, the prime shall clearly identify work to be performed by each specific sub-contractor within the appropriate Factors/Subfactors in the prime’s proposal. The proposal shall provide a clear distinction of functions to be performed by the prime and subcontractor to include the following: the nature of work, criticality of the work, and the percentage of overall effort performed by each subcontractor in each area of service provided based upon the cost of contract performance incurred for personnel (See FAR52.219-14 (b)(1) -- Limitations on Subcontracting, Services).

3. Format and Specific Content. Offeror shall address its proposed approach to meeting the performance or capability requirements of each Technical Proposal subfactor as follows:

SUBFACTOR 1 – System Architecture Design and Maintenance. The offeror shall present a systems engineering approach that explains how it will meet PWS 2.3.2.3, 2.8.2 – 2.8.4, and 3.4.3 – 3.4.8 requirements.

SUBFACTOR 2 – System Administration and Sensor Maintenance. The offeror shall present a systems administration and sensor maintenance approach that explains how it will meet PWS 2.9 and 3.4.1 – 3.4.9 requirements.

SUBFACTOR 3 – Customer Support. The offeror shall present a workload management approach that supports user’s technical needs, user accounts, and user workstations for the AF DCO M&E PWS 3.4.2 requirements.

SUBFACTOR 4 – Staffing. The offeror shall present an approach to staffing, training, and replacing personnel IAW with PWS section 3 and section 7, and an approach to ensure compliance with all security requirements IAW PWS section 6.1. Include a non-priced labor mix including labor categories and hours.

SUBFACTOR 5 – Transition Plan. The offeror shall present a plan to ensure continuity of services between the incumbent contractor and the new contractor IAW PWS section 3 and 7.3.

E. PART II – PRESENT/PAST PERFORMANCE INFORMATION.

1. General. Each offeror shall submit Present/Past Performance Information (PPI) with its proposal IAW the format contained in paragraph six below. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 30 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of present/past performance. Each offeror shall submit Present/Past Performance Information (PPI). Past performance of either party in a joint venture counts for the past performance of the entity.

2. New Corporate Entities. New corporate entities may submit data on prior contracts involving officers, employees, and key personnel who have relevant experience and/or data of efforts that will depict performance of major or critical aspects of the requirement. Discuss the roles and responsibilities of personnel involved in the prior contracts cited.

3. Recency/Relevancy. Offeror shall submit PPI on a minimum of four and no more than six recent contracts that offeror considers most relevant in demonstrating ability to perform the proposed effort. The total includes any subcontractors or teaming partners; however, no more than three of recent contracts shall be submitted on your teaming partners and/or significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Do not duplicate a contract reference for prime and subcontractor but rather explain the role each played within the contract reference itself. Include a cross reference matrix with this information supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining how contracts are considered recent and relevant, see Section M-1, Paragraph B. 4. a. ii. and iii. The offeror shall include rationale supporting its assertion of relevance of each contract submitted for past performance evaluation IAW paragraph 6 below.

4. Quality. The contracts must have been completed in the past three years with on-going actions considered recent as long as the effort has been performed for at least six months prior to issuance of the RFP. Offeror may provide any additional information to explain corrective actions taken in the past, if any, for substandard performance and any current performance problems such as cost overruns, extended performance periods, numerous warranty calls, etc.

5. PPI Questionnaire.

a. The offeror shall send out, and confirm receipt and submission of the PPI Questionnaire (Section L, Attachment 1), from each of the offeror’s, critical subcontractors’, teaming contractors’ and/or joint venture partners’ (i.e., each entity’s) POCs identified in the PPI Questionnaire Tracking Record (Section L, Attachment 2). The responsibility to send out the PPI Questionnaires rests solely with the offeror. For each questionnaire, complete and sign a letter containing substantially the same information as in the Sample Questionnaire Cover Letter (Section L, Attachment 3). Cover letters should be printed on company letterhead. The offeror shall exert its best effort to ensure that a current POC, per relevant contract, submits a completed PPI Questionnaire directly to the Government not later than the proposal due date. Each of the offeror’s POCs shall e-mail the completed PPI Questionnaire directly to Ms. Amy Byars at amy.byars@us.af.mil and Ms. Donna Williams at donna.williams.6@us.af.mil. Please instruct POC to call Ms. Amy Byars (405) 734-7368 or Ms. Donna Williams (405) 734-9706 with any questions.

b. Questionnaires shall be sent directly to the Government from the following POCs: Program/Project Manager or equivalent, Contracting Officer/Contract Administrator or equivalent, or Contracting Officer Representative (COR). Once the PPI Questionnaires are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to the offeror.

6. Format for Contract Information. Using the format below, the offeror shall provide the following information for each contract reference submitted for past performance evaluation. Provide concise comments regarding your performance on the contracts you identify. In the cross reference matrix identified in paragraph E.3 above, specify the work that will be performed by teaming partners and which PPI references for the applicable teaming partner are relevant to this work.

a. Offeror/Subcontractor Name (Company/Division):

CAGE Code:

DUNS Number:

(NOTE: If the company or division performing this effort is other than the offeror, or the relevancy of this effort to the instant acquisition is impacted by any company/corporate organizational change, refer to paragraph 7 below, "Organizational Structure Change History," and provide as part of the Present/Past Performance proposal.)

b. Acquisition Title:

c. Contract Specifics:

(1) Contracting Agency or Customer:

(2) Contract Number

(3) Contract Type (e.g. firm-fixed-price, CR, etc):

(4) Period of Performance (within the last three years):

(5) Contract Dollar Value: $

d. Description of Effort as __Prime or __Subcontractor

(Highlight portions considered most relevant to current acquisition)

e. Primary and Secondary Customer Points of Contact: Provide verified, up to date, Points of Contact on all past performance references.

Name:

Office:

Address:

Telephone:

E-mail:

f. Relevancy: Include a list of tasks performed on the effort that are relevant to this requirement. For a description of the characteristics or aspects the Government will consider relevant, see Section M-1, Paragraph B. 4. a. iii.

g. Address any technical (or other) area about this contract/program considered unique.

h. Describe the nature or portion of the work on the proposed effort to be performed by the business entity whose PPI is being reported. Also, estimate the percentage of the total proposed effort that will be performed by this entity and whether it will be performing as the prime, subcontractor, or a corporate division related to the prime (define relationship).

i. Describe any past or present litigation or administrative proceeding pertaining to the contract reference, including the results if the proceedings are complete or the status if the proceedings are ongoing. Provide a copy of any cure notices or show cause notices received on each contract reference and a description of any corrective action taken. Indicate if any of the contract references were terminated and the type and reasons for termination.

j. Discuss the number and severity of any problems in the contract reference considered relevant to the proposed efforts and identify the effectiveness of corrective actions to resolve the problems. Provide any contract discrepancy reports, corrective action reports or other non-compliance correspondence.

k. Include any information not previously covered, which will enhance the evaluators’ understanding of the offeror or any sub-contractor’s proposed qualifications.

7. Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent present/past efforts and this source selection. As a result, it is sometimes difficult to determine what present/past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of offeror’s company. As part of this explanation, show how these changes impact the relevancy of any efforts the offeror identifies for present/past performance evaluation/performance confidence assessment. Since the Government intends to consider PPI provided by other sources as well as that provided by the offeror(s), offeror’s "roadmap" should be both specifically applicable to the efforts offeror identifies and general enough to apply to efforts on which the Government receives information from other sources.

8. Consent Letters. The offeror shall submit a consent letter, executed by any potential subcontractors, teaming partners, and/or joint venture partners. The consent letter authorizes release of adverse PPI to the offeror so the offeror can, in turn, respond to such information. A sample letter follows:

SAMPLE

Contracting Officer:

We are participating as a (subcontractor/teaming partner) with (prime contractor or name of entity providing proposal) in responding to the 38 CONS/LGCC, Tinker Air Force Base Request for Proposal FA8773-14-R-8002 for the contract at 33rd NWS primary location Lackland AFB, TX.

We understand that the Government is placing increased emphasis on past performance in order to obtain best value in source selections. In order to facilitate the performance confidence assessment process we are signing this consent letter to allow you to discuss our past and present performance information with the prime contractor during the source selection process.

(Signature, printed name, and title of individual who has the authority to sign for and legally bind the company)

Company Name:

Address:

9. Client Authorization Letters. PPI concerning private sector contractors, subcontractors and joint venture partners cannot be disclosed to the Government without their consent. Client authorization letters are required for each identified effort for a commercial customer. This letter will authorize release to the Government of requested information on the offeror’s performance. The Government will need the consent before contacting commercial customers to assess the offeror’s past performance. In an effort to assist the evaluators in assessing offeror’s past performance relevancy and confidence, the Government requests the following client authorization letter be completed for any commercial customers identified in offeror’s proposal. Offeror shall include the completed client authorization letter(s) within the Present/Past Performance Part II.

SAMPLE

“Client:”

We are responding to the 38 CONS/LGCC, Tinker Air Force Base Request for Proposal FA8773-14-R-8002 for the contract at 33rd NWS primary location (Lackland AFB, TX).

The Government is placing increased emphasis on past performance as a source selection factor. The Government requires entities responding to their solicitation to identify clients and requests client participation in the evaluation process. You are hereby authorized to respond to those inquiries if the contracting office contacts you for information on work performed by our firm.

We have identified ______ of your organization as the point of contact based on his/her knowledge of our work. We appreciate your cooperation. You may direct any questions to: _____

F. PART III - PRICE PROPOSAL

1. Price Reasonableness, Completeness, Balance, and Affordability. This section is to assist you in submitting information other than cost or pricing data that is required to evaluate the reasonableness, completeness, balance, and affordability of the offeror’s proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness, completeness, balance, and affordability. The burden of proof for credibility of proposed prices rests with the offeror at the time of proposal or during subsequent discussions (if any are held).

2. Price Information. The price proposal shall not include information beyond that required by this instruction unless the offeror considers it essential to document or support offeror’s price position. All information relating to the proposed price, including all required supporting documentation, must be included in this part or assumptions of the proposal. Under no circumstances shall this information and documentation be included in the Technical Proposal or Past Performance Information parts.

3. Adequate Price Competition. The Government has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the Contracting Officer will review this determination and if, in the Contracting Officer’s opinion, adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the Contracting Officer determines that adequate price competition no longer exists, offerors may be required to submit information to the extent necessary to determine the reasonableness of the price.

4. Rounding. All dollar amounts (unit and extended prices and other price factors) provided shall be rounded to the nearest penny (two decimal places only). This includes base period and out-year (option) prices. Failure to round unit prices to no more than two decimals may result in rejection of proposal. Rounding errors caused by Government formulas will be corrected during evaluation to round to the nearest penny.

5. Downward Pricing Initiatives Process(es). Describe your process(es) for identifying, assessing, evaluating, and implementing price efficiency initiatives to achieve continuous downward pricing reductions. Provide evidence these processes are incorporated in the price for the initial period of performance resulting in downward out-year prices. Include any pertinent diagrams, charts or tables.

6. Professional Compensation Plan. As part of the price proposal, offerors shall provide a total compensation plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract IAW FAR 52.222-46 -- Evaluation of Compensation for Professional Employees (Feb 1993).

7. Organization. Part I shall consist of the following:

a. Table of Contents: includes Table of Contents and summary descriptions of estimating, purchasing, accounting systems, and invoicing processes and practices.

b. Pricing Notes/Methodology: pricing information and supporting data, to include estimating methodology.

c. Pricing Assumptions/Exceptions. Repeat any assumptions/exceptions affecting pricing only in this area. Do not cross reference to/from Part IV, Contracting Documentation. Annotate “none,” if no assumptions/exceptions apply.

d. PRICING TABLE (included as Section J, Attachment 1 to the solicitation). The offeror shall comply with the following requirements and instructions:

(1) Price all Contract Line Item Numbers (CLIN). Limit unit prices to two decimal places. If the offeror is providing a CLIN to the Government at no additional charge, “$0.00” must be entered for that item. The dollar value of CLIN X004 is a not to exceed (NTE) amount established by the Government and shall not be altered by the offeror. CLIN X005 is a Termination Fee and shall be priced IAW DFARS 252.232-7007(b), Limitation of Government’s Obligation. Option to Extend Services, CLIN 6002, will be automatically populated with established formulas on the Pricing Table.

(2) Electronic Media Submission of Pricing Table. The CLINs in the Pricing Table of this solicitation are an electronic file, presented as Excel for Microsoft Office©2010 spreadsheet/workbook format. Submit both a hard copy and an electronic copy using the exact file provided by the Government without changing the format of the files.

(3) Description of Files.

(i) Summary Sheet: Contains cells for the entry of unit prices for CLIN 0001, X002, and X005 and calculates extended prices for the Base Period through Option Period 5 and the Option to Extend Services (6002).

(ii) Option to Extend Services, CLIN 6002 will be automatically populated IAW clause 52.217-8. While it is not the Government’s intent to utilize this option CLIN, it is included to facilitate the extension of services if it is deemed necessary at the end of the base or any option period.

G. PART IV - CONTRACT DOCUMENTATION

1. Contract Document Sections. The purpose of this part is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the SF 33 and SF 30 for any subsequent amendments issued. The offeror shall complete and submit “ONLY” the contract document sections as follows:

Section A - Solicitation/Contract Form. Complete Blocks 12 through 18 (including original signature and date) of the SF 33. Signature by the offeror on the SF 33 constitutes an offer, of which the Government may accept. The "original" copy should be clearly marked and should contain each part identified in Table 2 - BINDER ORGANIZATION. Offeror shall include a statement within this part that the proposal is valid through the proposal acceptance period specified in Section A. Copy 1, Copy 2, Copy 3, and Copy 4 should each be clearly marked and should contain each part identified in Table 2 - BINDER ORGANIZATION.

Section B - Supplies or Services and Costs/Prices. Do not include. This section will be populated by the Government at contract award from data provided on Section J, Attachment 1, Pricing Table.

Section C, E, and F. Do not include. These sections are not modifiable by the offeror and are redundant to include with the proposal submission.

Section G - Contract Administrative Data. Offeror shall provide a “remit-to” address if different from the mailing address in Block 9 on the SF 33. The Remit-to address will be included in Section G of any resultant contract at the time of award. Do not include Section G if “remit-to” address does not apply.

Section I - Contract Clauses. Submit RFP Section I pages for only clauses which require offeror fill-ins. Other pages in this section shall not be included with the submission.

Section J – Attachments. Do not include.

Section K –

a. System for Award Management (SAM) (Representations, Certifications, and other Statements of Offerors). Completed SAM representations, certifications, acknowledgments and statements shall be included with submission. Ensure SAM is current, complete, and accurate at the time of proposal. SAM representations and certifications must include those specified within Section K of this RFP. SAM can be accessed at https://www.sam.gov/portal/public/SAM/#1. Offeror shall be eligible for award under the specified NAICS code, 541512, and as a certified 8(a) vendor at the time of submittal of their proposal and remain eligible when verified again prior to award of the contract.

b. Joint Venture Agreements. Per the Small Business Administration (SBA), Joint Ventures are allowable on competitive 8(a) set-asides; however, the joint venture agreement must be received by SBA PRIOR to proposal due date and approved before award of any resulting contract. If you are contemplating a joint venture on this project, you must advise your assigned SBA Business Development Specialist (BDS) as soon as possible. It is also recommended that the agreement be submitted as soon as practicable to ensure compliance with established regulations. Any corrections and/or changes needed can be made only when the BDS has adequate time for a thorough review before the proposal due date. No corrections and/or changes are allowed after time of submissions of proposals.

Section L – Do not include. This section is not modifiable by the offeror and is redundant to include with the proposal submission with exception of DFARS provision 252.237-7024, Notice of Continuation of Essential Contractor Services. Offeror shall include, in Part IV, documentation required by DFARS provision 252.237-7024(b). There is no page limitation for this document and it is not included in the overall page limitation. Additionally, the submitted document will be incorporated into the contract by reference IAW DFARS 252.237-7023.

Section M - Do not include. This section is not modifiable by the offeror and is redundant to include with the proposal submission.

2. Exceptions and/or Assumptions. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the following format and content:

Solicitation Exceptions

Solicitation Document

Reference PWS, Solicitation, Section L, etc.

Page/Paragraph Provide applicable page and paragraph numbers and/or clause/provision numbers

Requirement/Portion

Identify the requirement or portion to which exception is taken

Rationale

Describe why the requirement can/will not be met

SECTION M - EVALUATION FACTORS FOR AWARD

The following have been modified:

M-1 EVALUATION OF OFFERS

A. BASIS FOR CONTRACT AWARD.

This is a competitive best value source selection, evaluating technical, present / past performance, and price, in which competing offerors’ present / past performance history will be evaluated on a basis approximately equal to cost or price considerations where the Government may elect to trade present / past performance for price if warranted. IAW FAR 15.101-1(c), tradeoffs among cost or price and non-cost factors, allowing the Government to accept other than the lowest priced proposal, are permitted. By submission of its offer, the offeror accedes to all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being determined technically unacceptable. The Government intends to award a single contract to the offeror who is deemed responsible IAW the FAR Subpart 9.1, as supplemented, and determined eligible by Small Business Administration IAW FAR 19.8, whose proposal conforms to the solicitation’s requirements (to include all stated terms, conditions, representations, certifications, and all other information required by Section L of this solicitation) and is judged, based on the evaluation factors and sub-factors, to represent the best value to the government. While the Government will strive for maximum objectivity, the source selection process, by its nature, is subjective; and therefore, professional judgment is implicit throughout the entire process. The evaluation process shall proceed as follows:

B. EVALUATION FACTORS AND SUBFACTORS.

1. The evaluation process to be used is as follows:

a. Step 1:

Evaluate all proposals for technical acceptability (if rated “unacceptable”, consider and document the correction potential if discussions are to be conducted).

b. Step 2:

Assess performance confidence for each offeror (include “unacceptable” proposals with correction potential).

c. Step 3: Evaluate all proposals to determine whether the price is fair and reasonable (in accordance with FAR 15.404 and FAR 31.201-3), balanced (in accordance with FAR 15.404-1), and affordable (within any budgetary information included in the solicitation); then rank by total evaluated price.

d. Step 4: If a competitive range is established and discussions are to be conducted, they will be IAW DoD Source Selection Procedures paragraphs 3.4 – 3.6. The Government reserves the right to eliminate offerors for the purposes of efficiency.

e. Step 5:

Best Value Decision IAW DoD Source Selection Procedures paragraphs 3.8 and 3.9.

2. The proposals shall be evaluated against the following factors and subfactors:

Factor 1: Mission Capability

Subfactor 1: System Architecture Design and Maintenance

Subfactor 2: System Administration and Sensor Maintenance

Subfactor 3: Customer Service

Subfactor 4: Staffing

Subfactor 5: Transition

Factor 2: Present/Past Performance

Factor 3: Price

Non-price factors are listed in descending order of importance and when combined, all non-price factors are considered equal to price

3. FACTOR 1-- TECHNICAL. First, the Government technical evaluation team will evaluate the technical proposals on a pass/fail basis, assigning ratings of Acceptable or Unacceptable.

Acceptable: Proposal clearly meets the minimum requirements of the solicitation.

Unacceptable: Proposal does not clearly meet the minimum requirements of the solicitation.

The technical evaluation assesses the offeror’s demonstrated understanding and capability to satisfy the Government’s requirements. A failure in any technical subfactor will result in an unacceptable rating for the technical factor. Only those technical proposals determined to be technically acceptable, either initially or as a result of discussions, will be considered for award. Proposals will be evaluated against the following subfactors:

Subfactor 1: System Architecture Design and Maintenance. This subfactor is met when the offeror provides a systems engineering approach that meets the following criteria:

a. Demonstrates a detailed ability to provide advanced/engineering level installation, upgrades, and maintenance to ACD Oracle and ArcSight Databases on SANs consisting of UNIX-based, Windows-based, and VMware-based operating systems and other network and computer components. (PWS para 3.4.6)

b. Demonstrates a detailed ability to provide Tier III level VMware-based system and network integration services and comprehensive testing of new systems, technologies and applications to ensure they satisfy stated requirements and provide supportable systems and networks in the future. Demonstration shall include specific details for the following:

i. Creating new master template images for Microsoft server and desktop OS’s, CentOS, and RedHat with all current STIG’s. (PWS para 3.4.3, 3.4.4 & 3.4.7)

ii. Deploying OS patches and software updates using VMware vCenter server and/or Microsoft Deployment Services. (PWS para 3.4.3, 3.4.4 & 3.4.7)

iii. Installing and configuring Storage Area Networks (SAN’s) with fiber-channel switches and allocating additional storage as necessary. (PWS para 3.4.3, 3.4.4, 3.4.5, 3.4.7 & 3.4.8)

iv. Designing disaster recovery and failover capabilities for new services and systems being integrated into the ACD weapon system mission networks. (PWS para 2.8.2, 2.8.3 & 2.8.4)

v. Developing capabilities for multiple database instances, and managing Microsoft SQL Server instances needed for various software suites. (PWS para 3.4.6)

c. Demonstrates a detailed ability to provide advanced/engineering level configuration of ACD network boundary and core infrastructure equipment. Demonstration shall include specific details for the following:

i. Designing/integrating and troubleshooting Cisco 7206 routers, 5550 ASA’s, 6500, 4500 and 3750 series switches. (PWS para 3.4.7)

ii. Integrating fiber channel switches for SAN storage into existing networks. (PWS para 3.4.3, 3.4.4 & 3.4.5)

iii. Executing and documenting emergency shut-down, start-up and recovery operations during times of network instability. (PWS para 2.3.2.3)

Subfactor 2: System Administration and Sensor Maintenance. This subfactor is met when the offeror presents an effective systems administration and sensor maintenance approach for the effort that meets the following criteria:

a. Demonstrates a detailed ability to perform intermediate level sustainment of UNIX, VMware and Microsoft OS’s on Air Force Cyber Defense (ACD) weapons system mission networks to include intimate familiarity with all mission databases. Demonstration shall include specific details for the following:

i. Installing and configuring ESXi 5.x on servers to be included in a virtualization cluster. (PWS para 3.4.2 & 3.4.4)

ii. Deploying/sustaining virtual desktops using VMware View and vCenter Server. (PWS para 3.4.3, 3.4.4 & 3.4.7)

iii. Managing Microsoft patch management systems. (PWS para 3.4.2, 3.4.3, 3.4.5 & 3.4.6)

iv. Performing scheduled PMI’s on equipment listed on the EIL in accordance with TO 00-33A-1001-WA. (PWS para 2.9)

b. Demonstrate a detailed ability to provide intermediate level installation, upgrades, and daily sustainment of ACD core infrastructure. Demonstration shall include specific details for the following:

i. Managing Cisco 6500, 4500 and 3750 series switches in an environment supporting over 500 user systems. (PWS para 3.4.3, 3.4.5 & 3.4.8)

ii. Configuring Cisco 7206 router/5550 ASA ACL’s, routes and interfacing large network boundaries. (PWS para 3.4.3, 3.4.5 & 3.4.8)

iii. Installing fiber-channel switches, fiber optic media, gigabit Ethernet and 100BaseT. (PWS para 3.4.3, 3.4.5 & 3.4.8)

c. Demonstrates a detailed ability to install, configure, maintain and manage the AF IDS/IPS sensor fleet including IOP gateway and Fly Away Kits (FAK) sensors, CloudShield, MacAfee IDS/IPS deployments, sensor fleet specialized applications (such as Fidelis), emerging IDS/IPS technologies and associated network infrastructure (Adaptive Security Appliance (ASA)/Virtual Private Network (VPN) concentrator) equipment/configurations and other Gateway, boundary and Third Party sensors. Demonstration shall include detail for the following:

i.

Integrating McAfee IPS/IDS sensors by joining them to the manager, and updating sensor configurations. (PWS para 3.4.1 & 3.4.9) ii.

Reporting all sensor feeds (IOP, McAfee IPS/IDS, Bluecoat, Ironmail, syslog, logger) to ArcSight via connector. (PWS para 3.4.1 & 3.4.9) iii.

Maintaining VPN connections (Cisco ASA 5500 series) to remote sensor (McAfee and IOP) fleets. (PWS para 3.4.1 & 3.4.9) iv.

Updating signatures to globally deployed sensors (Fidelis, McAfee IPS/IDS, IOP). (PWS para 3.4.1 & 3.4.9) v.

Monitoring/sustaining packet capture systems (Solera, Netwitness) for proper operation. (PWS para 3.4.1 & 3.4.9)

Subfactor 3: Customer Support: This subfactor is met when the offeror presents a workload management approach for the AF DCO M&E effort that meets the following criteria:

a. Demonstrates a detailed ability to perform basic customer support installation, upgrades, and daily sustainment to include hardware and software consisting of UNIX-based, Windows-based, and VMware-based operating systems, Anti-virus and vulnerability remediation systems software. (PWS para 3.4.2)

b. Demonstrates a detailed ability to create and delete user accounts within two (2) working days, track user privileges, and maintain a list of current users. (PWS para 3.4.2)

c. Demonstrates a detailed ability to ensure ACD user work stations are secure, and are properly configured within Time-Compliance Network Order (TCNO) specific deadlines to minimize the potential of unauthorized intrusions. (PWS para 3.4.2) Subfactor 4: Staffing: This subfactor is met when the offeror presents an effective staffing and personnel management approach for this effort that meets the following criteria:

a. An organizational structure that provides qualified and appropriately commercially certified personnel resources, to include any subcontracting and teaming arrangements, in an organizational structure and labor categories, security clearance and minimum acceptable qualifications IAW PWS Sections 2.10, 3 and 7 at initiation of contract.

b. A sound methodology for replacing personnel, or hiring additional personnel, on short notice.

c. A sound methodology for training new personnel in processes, procedures, software tools, and system design parameters associated with this effort and providing continued training for existing staff.

d. Include Personnel Security clearances IAW PWS Section 6.1, DD254, and how offeror will verify personnel are cleared to perform the PWS requirements on contract start.

Subfactor 5: Transition Plan. This subfactor is met when the offeror provides a transition plan including a work breakdown structure (WBS) that identifies parties, dates, critical actions, and deliverables required to ensure a smooth transition and continuity of services between the current contracts and this effort IAW PWS Section 3 and 7.3 requirements.

4. FACTOR 2 -- PRESENT/PAST PERFORMANCE. Performance Confidence Assessment. Next, the Present/Past Performance evaluation assesses the degree of confidence the Government has in an offeror’s ability to perform the required services to meet users’ needs based on a demonstrated record of performance. The contracting officer will assess performance confidence for each offeror.

a. EVALUATION PROCESS

i. In conducting the present/past performance evaluation, the Government reserves the right to use both the information provided in the offeror’s Present/Past Performance proposal and information obtained from other sources, such as: the Past Performance Information Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information System (FAPIIS), Electronic Subcontract Reporting System (eSRS), Performance Assessment Reporting System (CPARS), or other databases; interviews with Program Managers (PM), Contracting Officers (CO), and Fee Determining Officials; Defense Contract Management Agency (DCMA); and commercial sources. Present/Past Performance Information (PPI) includes all information obtained during this process.

ii. RECENCY ASSESSMENT. An assessment of the PPI will be made to determine if it is recent. To be recent, the effort must be ongoing or must have been performed during the past 3 years from the date of issuance of this solicitation.