NETCENTS_2_Application_Services_SB_Final_RFP_Amendment0005_09May11.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

09 MAY 2011

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

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

DEPARTMENT OF THE AIR FORCE

ESC/HIJK

501 EAST MOORE DR,BLDG 884, RM1400

MAFB - GUNTER ANNEX AL 36114-3000

NANNIE R. BRILLANT 3344162257

nannie.brillant@gunter.af.mil

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

FA8771-09-R-0021

X

9B. DATED (SEE ITEM 11)

20 MAY 2010

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

(X )

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

10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

SEE SCHEDULE. ONLY OFFERORS THAT SUBMITTED PROPOSALS IN RESPONSE TO SOLICITATION FA8771-09-R- 0021 ARE PERMITTED TO SUBMIT A RESPONSE TO THIS AMENDMENT. THIS AMENDMENT DOES NOT ALLOW NEW OFFERORS TO SUBMIT A PROPOSAL (as authorized by FAR 15.206). The offeror shall complete blocks 8, 15(a), (b), and (c) of the SF 30 and return the original to the PCO. SF 30 will be accepted via email to linda.lowmiller@gunter.af.mil or mailed to Linda R. Lowmiller, ESC/HIJK, 501 East Moore Dr., Bldg 884, Room 1400, Maxwell AFB-Gunter Annex, AL 36114 NO LATER THAN 4:00 p.m. Central Time 12 May 2011.

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

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

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

LINDA R. LOWMILLER

15B. CONTRACTOR/OFFEROR

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

16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

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

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 6.13.1 FAR (48 CFR) 53.243 Created 09 May 2011 10:20 AM

SCHEDULE OF CHANGES

FA8771-09-R-0021 0005

THE NETCENTS-2 APPLICATION SERVICES SMALL BUSINESS COMPANION SOLICITATION IS

HEREBY AMENDED AS FOLLOWS:

1. Add Clauses to SECTION I

NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference into Section I.

AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT CONTRACT CLAUSES

5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010); (FORMERLY AFMCFARS -

5352.209-9002 ORGANIZATIONAL CONFLICT OF INTEREST (AFMC) (AUG 2002))

5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010) ALTERNATE I;

(FORMERLY AFMCFARS - 5352.209-9002 ORGANIZATIONAL CONFLICT OF INTEREST (AFMC)

(AUG 2002) - ALTERNATE I (AUG 2002))

Alt I, Para (a)(2)(i), Specific period of time or an expiration date '"to be cited in each individual task order"' Alt I, Para (a)(2)(ii), System or services '"to be cited in each individual task order"' Alt I, Para (a)(2)(ii), Services, the system, or the major components of the system '"to be cited in each individual task order"' Alt I, Para (a)(2)(ii), Duration of the constraint '"to be cited in each individual task order"'

5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010) ALTERNATE II (OCT 2010);

(FORMERLY AFMCFARS - 5352.209-9002 ORGANIZATIONAL CONFLICT OF INTEREST (AFMC)

(AUG 2002) - ALTERNATE II (AUG 2002))

Alt II, Para (a)(2), Definite period of time: '"to be cited in each individual task order"'

5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010) ALTERNATE III (OCT 2010);

(FORMERLY AFMCFARS - 5352.209-9002 ORGANIZATIONAL CONFLICT OF INTEREST (AFMC)

(AUG 2002) - ALTERNATE III (AUG 2002))

5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010) ALTERNATE IV (OCT 2010);

(FORMERLY AFMCFARS - 5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010)

ALTERNATE IV (OCT 2010))

5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010) ALTERNATE V (OCT 2010);

(FORMERLY AFMCFARS - 5352.209-9002 ORGANIZATIONAL CONFLICT OF INTEREST (AFMC)

(AUG 2002) - ALTERNATE V (AUG 2002))

5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010) ALTERNATE VI (OCT 2010);

(FORMERLY AFMCFARS - 5352.209-9002 ORGANIZATIONAL CONFLICT OF INTEREST (AFMC)

(AUG 2002) - ALTERNATE VI (AUG 2002)

2. Section J, Attachment 8, SECTION L - ITO and IFPP, L4.2.5(d1) is changed to read:

From: (d1) Distributing software modifications or minor enhancements IAW AFI 33-114

Software Management, paragraphs 10, 10.3, 11, 11.1.2, 12 and 13.

To: (d1) Distributing software modifications or minor enhancements IAW AFI 33-114

Software Management, paragraphs 10.3, 11.1.2, 12 and 13.

SCHEDULE OF CHANGES

FA8771-09-R-0021 0005

3. Section J, Attachment 8, SECTION L - ITO and IFPP, L4.2.5(e3) is changed to read:

From: (e3) providing technical assistance, order processing, support of multiple software versions, training, warranty and maintenance, To: (e3) providing technical assistance, order processing, support of multiple software versions, warranty and maintenance,

4. No other changes are made as a result of this amendment.

PART IV – REPRESENTATIONS AND INSTRUCTIONS

SECTION L – INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS____________________________

_________________________________________________________________Section L FA8771-09-R-0021-0005

Section J, Attachment 8

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

(IFPP) (JAN 2010)

L1.0 PROGRAM STRUCTURE AND OBJECTIVES

See Section J, Performance Work Statement.

L2.0 GENERAL INSTRUCTIONS

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

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

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

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

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

L2.0.1 Proposal Clarity

The proposals shall be clear, concise, and shall include sufficient detail for effective evaluation substantiating the validity of stated claims. The proposal should not simply rephrase or restate the

Government's requirements, but shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their capabilities and experience, and will base its evaluation on the information presented in the offeror's proposal. The Government intends to evaluate proposals and award contracts without discussions, but reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary.

L2.0.2 Proposal Acceptance Period

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

L2.0.3 Disposition of Unsuccessful Proposals

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

L2.1 GENERAL INFORMATION

L2.1.1 Point of Contact

Mrs. Linda R. Lowmiller, PCO – NETCENTS-2 Application Services, is the point of contact for this acquisition. Address any questions or concerns to her. Written requests for clarification may be sent via e-mail to the PCO at linda.lowmiller@gunter.af.mil. Official RFP documentation, including RFP amendments, and other related information will be available on the Internet at http://public.gunter.af.mil/aq/netcents/2/ , HTTP://HERBB.HANSCOM.AF.MIL, and https://www.fbo.gov/.

L2.1.2 Debriefings

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

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

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

L2.1.3 Discrepancies

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

L2.1.4 Electronic Reference Documents

All referenced documents for this solicitation are available on NETCENTS-2 web site at:

http://public.gunter.af.mil/aq/netcents/2/.

mailto:linda.lowmiller@gunter.af.mil http://public.gunter.af.mil/aq/netcents/2/ http://herbb.hanscom.af.mil/ https://www.fbo.gov/

L2.1.5 Distribution/Submission/Proposal Volumes

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

(CDT):

LINDA R. LOWMILLER, PCO, NETCENTS-2 APPLICATION SERVICES

HQ 754

TH

ELSG/ESO

490 EAST MOORE DR.

BLDG 892, SUITE 270

MAXWELL AFB - GUNTER ANNEX, AL 36114

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

L2.1.6 SECTION K - REPRESENTATIONS AND CERTIFICATIONS

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

L2.1.7 Communications

Exchanges of source selection information between government and offerors will be controlled by the

PCO. Encrypted e-mail may be used to transmit such information to offerors, and must include “Source

Selection Information – See FAR 2.101 and 3.104” in the Subject line.

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

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

(b) Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the submission and may be returned to the offeror (i.e., paper copies) as soon as practicable. Each page shall be counted except the following; any Cover Sheets, Table of

Contents, Tabs, Glossaries of terms/abbreviations/acronyms, cross reference matrix, resumes and organizational charts. All pages shall be numbered. Sheets printed on both sides shall be numbered on both sides if both sides contain information.

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

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

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

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

Use Only" and contains "Source Selection Information - See FAR 52.215-01(e) and 3.104."

Volume Title Page Limit Copies

I Executive Summary 5 pages

Original & 1 paper copy; 2 CDs /DVDs

II Technical Proposal 90 pages total

Original & 6 paper copies; 2 CDs /DVDs

Quality Certification

Documentation

(reference Section J, Atch 1, PWS, para

8.0)

20 pages total

Included in the

Technical Proposal copies

Test Support Cost

Reimbursable

Sample Task Order

Submission

20 pages total as part of the

Technical Proposal (not including labor descriptions)

Included in the

Technical Proposal copies

Systems

Sustainment Firm

Fixed Price Sample

Task Order

Submission

20 pages total as part of the Technical Proposal

(not including labor descriptions)

Included in the

Technical Proposal copies

Web Service

Development

15 pages total as part of the Technical Proposal

Included in the

Technical Proposal copies

Management

Approach

15 pages total as part of the Technical Proposal

Included in the

Technical Proposal copies

III Past Performance

Information Sheets

(PPIS)

Table of Contents (not counted in total)

4 page limit per contract and up to 10 contracts for a total of 40 pages max.

Original & 1 paper copy, 2 CDs /DVDs

IV Cost/Price

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

V Contract

Documentation

No page limit

Original & 1 paper copy; 2 CDs/DVDs

Table 1 - Proposal Organization

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

L2.3 Proposal Format

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

(b) All proposal volumes shall be due by 30 Jun 2010, 12:00pm (CDT).

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

L2.3.1 Binding and Labeling

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

Contractor Bid or Proposal Information and Source Selection Information.

L2.3.2 Page Format Restrictions

(a) Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

See paragraph L2.3.4 below for additional guidance regarding foldouts. Except for the reproduced sections of the solicitation document, the font size shall be no less than Times New Roman ten (10) point.

Use at least 1- inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume. For tables, charts, graphs and figures, the font shall be no smaller than eight (8) points.

(b) Page limitations may be placed on responses to Evaluation Notices (ENs).

L2.3.3 Indexing

Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume.

Tab indexing shall be used to identify sections.

L2.3.4 Foldouts

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 legible, easy to follow and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume and count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For tables, charts, graphs and figures, the font shall be no smaller than eight (8) point.

L2.3.5 Cross Referencing

(a) To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal.

Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

(b) Cross Reference matrix does not count against the page limitations for their respective volumes.

L2.3.6 Cost or Pricing Information

All cost or pricing information shall be addressed ONLY in the Cost/Price Proposal Volume. Cost trade-off information, work-hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

L2.3.7 Glossary of Abbreviations and Acronyms

Each volume 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 volumes.

L3.0 VOLUME I - EXECUTIVE SUMMARY

L3.1 Format and Specific Contents

L3.1.1 Summary

A concise executive summary of the entire proposal shall be provided including a highlight of any key or unique features, excluding cost. This should be a “big picture” explanation and provide the offeror’s overall approach for the management/operation of the NETCENTS-2 Application Services requirements, including proposed subcontractors and/or teaming arrangements. The following table shall be included for the prime and 1 st tier subcontractor only:

List as Prime or 1 st Tier

Subcontractor Name/CAGE Code Business Size

Status

Material presented in the Executive Summary shall not be considered towards meeting the requirements for any portions of other volumes of the proposal.

L3.1.2 Table of Contents

Include a Master Table of Contents for the entire proposal.

L4.0 VOLUME II – TECHNICAL PROPOSAL

L4.1 General

The purpose of the Technical Proposal Volume is to provide the Government the ability to evaluate the technical capability of the offeror to perform the NETCENTS-2 Application Services requirements.

L4.2 Format and Specific Content

L4.2.1 Technical Proposal

In the Technical Proposal Volume, address your proposed approach to meeting the performance or capability requirements of each technical proposal subfactor. The offeror’s technical proposal submission shall be specific and complete. Legibility, clarity, and coherence are very important. The offeror’s technical proposal should provide as specifically as possible the actual methodologies that will be used.

All the requirements specified in the solicitation are mandatory. Through proposal submission, the offeror represents that it will fulfill the requirements specified in the solicitation; therefore, it is not necessary or desirable for an offeror to state this in the proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. The technical proposal shall not include price information, classified information, or "For Official Use Only" information. The Technical Proposal Volume will be used to evaluate the technical acceptability of the offeror’s proposal. Evaluation will be against the technical acceptability subfactors as specified in Section M of this RFP.

L4.2.2 Volume Organization

The Technical Proposal Volume shall contain the information in tabbed sections IAW the following outline:

1. Table of Contents

2. List of Table and Drawings

3. Glossary

4. Subfactor 1 - Quality Processes

5. Subfactor 2 - Test Support (Cost Reimbursable Sample Task Order)

6. Subfactor 3 - Systems Sustainment (Firm Fixed Price Sample Task Order)

(Include Labor Categories with total proposed hours)

7. Subfactor 4 - Web Service Development

8. Subfactor 5 - Management Approach

9. Cross Reference Matrix

L4.2.3 Subfactor 1 - Quality Processes

The prime contractor shall provide proof of:

(1a) certification (copy of certificate with initial proposal submission) of being appraised at Level 2 (or higher) for Capability Maturity Model (CMM), Capability Maturity Model Integration (CMMI), or CMMI Development using the Software Engineering Institute's (SEI) Standard CMMI Appraisal Method for Process Improvement (SCAMPI) (Method A)

(1b) by an SEI-authorized lead appraiser, or comparable documented systems engineering processes.

(1c) This certification must be held at the prime offeror's organizational level performing the contract.

(2a) If not SEI appraised, acceptable documentation shall describe all salient SE processes, including requirements management, (2b) configuration management, (2c) development of specifications, (2d) definition and illustration of architectures and interfaces, (2e) design, (2f) test and evaluation/verification and validation, (2g) deployment and maintenance.

If not SEI appraised, the offeror shall also provide evidence of

(2i) the incorporation of automated processes and tools utilized in the Offeror's SE processes.

L4.2.4 Subfactor 2 – Test Support Cost Reimbursable Sample Task Order

The offeror shall provide a proposal for the task order summarized below and provided in detail in Section J, Attachment 15 of the RFP.

Summary Description of Test Support Cost Reimbursable Sample Task Order

The offeror shall provide a proposal for providing test support to existing information systems throughout the Air Force Enterprise. The offeror shall propose methodologies, processes, tools and techniques for providing testing support.

The offeror’s proposal shall address performing the following test support activities:

(a) Test management and evaluation to include describing methods and processes for:

(a1) Providing and supporting development test and evaluation IAW AFI 99-103 Capabilities-Based Test and Evaluation paragraph 2.2. and 2.3 requirements;

(a2) Preparation, setup and conduct of independent testing;

(a3) and defect tracking and documentation of results.

(b) Support to Responsible Test Organization (RTO)/Participating Test Organization (PTO) to include describing methods and processes for:

(b1) Providing technical expertise to support planning, management and conduct of Government DT&E and integrated testing IAW AFI 99-103 Capabilities-Based Test and Evaluation, paragraph 3.14;

(b2) and providing technical input to the Program Management Office (PMO) in the preparation of program documentation, analyses and studies.

(c) Test execution to include describing methods and processes for:

(c1) Providing test scripts;

(c2) Conducting and supporting system tests;

(c3) Conducting and supporting interoperability/integration tests;

(c4) Conducting functional testing;

(c5) Use of automated tools, such as but not limited to, HP/Mercury Tool Suite, Team Track, and

QuickTestPro;

(c6) and Documenting testing progress and results in reports.

(d) Test environment management to include describing methods and processes for:

(d1) loading application software, performing systems administration and database management for test resources;

(d2) Analyzing and making recommendations for hardware and software enhancements in the test environment;

(d3) Maintaining, configuring and/or modifying automated test tools, such as but not be limited to, Quality Center, Team Track, and HP/Mercury Tool Suite.

(e) Ensuring applications are developed IAW guidance provided in the Office of Management and Budget

(OMB) Memorandum dated August 11, 2008, subject “Guidance on the Federal Desktop Core

Configuration (FDCC)” to include

(e1) describing methods and processes for: Configuring, installing and evaluating deployment of the standard desktop software;

(e2) Use of deployment methods such as System Center Configuration Manager (SCCM), Systems

Management Server (SMS), Operating System Deployment/ User State Migration Tool (OSD/USMT), and manual wipe and load.

(f1) The knowledge, abilities and skills, to include skill levels, and products needed to accomplish the requirements identified in the task order and present an appropriate mix of labor categories with total proposed hours summarized by labor category.

(f2) The offeror shall provide their labor categories, associated descriptions, and estimated effort in the

Application Services Price Proposal Workbook, Cost Reimbursable Sample Task Order tab, Section J, Attachment 14 of the RFP.

L4.2.5 Subfactor 3 – Systems Sustainment Firm Fixed Price Sample Task Order

The offeror shall provide a proposal for the task order summarized below and provided in detail in Section J, Attachment 16 of the RFP.

Summary Description of Systems Sustainment Firm Fixed Price Sample Task Order

The offeror shall provide a proposal for providing systems sustainment support to existing information systems within development and operational environments at bases of the 123 rd

Mission Support Wing as described in the Systems Sustainment sample task order. The offeror shall propose methodologies, processes, tools and techniques for maintaining and ensuring interoperability, security, and performance of systems within development and operational environments.

The offeror’s proposal shall address performing the following system sustainment activities:

(a) Methods and processes for requirements development and management

(b1) Developing and maintaining software components according to a systems engineering approach that is IAW guidance provided in the Office of Management and Budget (OMB) Memorandum dated

August 11, 2008, subject “Guidance on the Federal Desktop Core Configuration (FDCC) and includes appropriate configuration management to include their methods and processes to identify, control, monitor, verify and manage software configuration items.

(b2) Proposal must describe methods and processes for implementing system changes, for risk management, (b3) for data management and interface management.

(c1) Documenting and testing software and system components IAW AFI 99-103 Capabilities-Based Test and Evaluation, paragraphs 7.2. and 7.3.

(c2) Proposal must describe processes and procedures for performing regression testing of the entire system for each upgrade or patch.

(c3) Proposal must describe methods and processes for preparing test data and scripts IAW AFI 99-103, paragraph 2.2

(c4) and must describe methods and processes for conducting testing for the application, database, operating system, and the effects of load and stress IAW test plans.

(d1) Distributing software modifications or minor enhancements IAW AFI 33-114 Software Management, paragraphs 10.3, 11.1.2, 12 and 13.

(d2) Offeror’s proposal must describe their methods and process for supporting electronic distribution of software, documentation, and supporting materials.

(e1) Tier 1, Tier 2 and Tier 3 help desk support 24-hours a day, 7-days a week, 365 days a year.

(e2) Offeror’s proposal must describe methods and processes for providing patch management support, (e3) providing technical assistance, order processing, support of multiple software versions, warranty and maintenance, (e4) for reporting deficiencies in software and hardware, (e5) to include resolving and closing deficiency reports.

(f1) The knowledge, abilities and skills, to include skill levels, and products needed to accomplish the requirements identified in the task order and

(f2) present an appropriate mix of labor categories with total proposed hours summarized by labor category.

L4.2.6 Subfactor 4 – Web Service Development

The offeror shall describe an approach to develop and maintain web services that enable sharing of business logic, data, and processes across networks, and provide specific end-user functionality across different applications in an enterprise. The offeror shall describe the methodology and associated processes, tools, and techniques required to ensure lifecycle management, security, and performance of web services and to accomplish the following:

(a) Preparing data for exposure as information asset payloads according to XML schemas

(b) Exposing data from modern, distributed, web-based applications for use in enterprise-wide services

(c) Application of WS-Security Policies (WS-* standards)

(d) Use of Simple Object Access Protocol (SOAP)

(e) Development/use of Web Service Definition Language Documents (WSDLs)

(f) Development/use of XML schemas

(g) Use of Integrated Development Environments (IDEs) and other tools

(h) Publishing services for Universal Description Discovery and Integration (UDDI)

(i) Providing security for web service control, to include validation and verification

(j) Utilizing Java and the J2EE platform to develop web services

(k) Utilizing the .NET framework to develop web services

L4.2.7 Subfactor 5 – Management Approach

The offeror shall describe its management processes and how it will ensure services and products provide an overarching, executable solution set, consistent with the proposed approach. Key focus areas for evaluation are:

a. Staffing processes, by which the offeror recruits

(a1) highly qualified employees for the task orders, including a discussion of the offeror’s approach to

(a2) employee accession, (a3) retention, and

(a4) professional growth;

(a5) and the soundness and quality of the offeror’s proposed process, ensuring continuity of services during personnel absences due to sickness, leave and voluntary or involuntary termination from employment such that impact to the Government is minimal.

b. Worldwide support processes, including a discussion of the offeror’s approach to

(b1) bidding on and responding to task orders involving OCONUS locations, (b2) including personnel and timelines for proposal preparation activities in order to fulfill

OCONUS task orders associated with the type of work described in the Application Services PWS.

L4.3 Cross-reference Matrix

(a) The offeror shall include a completed Cross Reference Matrix IAW the Table 2 below:

Subfactors Performance Work Statement Section L Section M Offeror's Proposal

Reference (volume, page and paragraph)

Subfactor 1 – Quality

Processes

8. Quality Processes

L4.2.3

M 2.1

Subfactor 2 – Test

Support Cost

Reimbursable Sample

Task Order

4.7 Testing

4.7.1 Test Lab

4.7.2 Product/System

Integration Testing

4.7.3 Simulated Operational

Testing

4.7.4 Acceptance Testing

4.7.5 System Performance

Testing

L4.2.4 M.2.2

Subfactor 3 – Systems

Sustainment Firm Fixed

Price Sample Task Order

3.1 Systems Sustainment

3.2 Systems Development, Migration, and

Integration

3.4 Systems Operations

3.4.1 Database

Administration

3.4.2 Systems

Administration

3.4.3 Customer Training

3.4.4 Help Desk Support

4.2 Systems Engineering

4.3 Configuration

Management

4.5 Information Assurance (IA)

4.6 Security

4.7 Testing

4.7.1 Test Lab

4.7.2 Product/System

Integration Testing

4.7.3 Simulated Operational

Testing

4.7.4 Acceptance Testing

4.7.5 System Performance

Testing

L4.2.5 M 2.3

Subfactor 4 – Web

Service Development

3.3.6 Web Services

3.3.7 Service

Lifecycle Management

L4.2.6

M 2.4

Subfactor 5 –

Management Approach

5.2 Program Management L4.2.7 M 2.5

Table 2 – Cross Reference Matrix

L5.0. VOLUME III – PAST PERFORMANCE

L5.1 General

The offeror shall provide past performance information for evaluation. Failure to provide the information may result in the offeror being removed from consideration for award. Note: An offeror with no past performance experience should submit the Volume with an explanation that they have no recent or relevant experience. The Government will evaluate past performance through an integrated analysis of recency, relevancy, and the quality of work performed. In evaluating the offerors past performance record the Government may use past performance information gathered from various sources, which may include but is not limited to, information obtained from the Past Performance Information Retrieval System

(PPIRS), Contractor Performance Assessment Reporting Systems (CPARS), similar systems of other

Government departments and agencies, questionnaires tailored to the circumstances of this acquisition, Defense Contract Management Agency (DCMA) channels, interviews with program managers and contracting officers, site visits and other sources known to the Government including commercial sources.

L5.1.1 Past Performance Volume

The offeror shall submit a Past Performance Volume containing the following:

TABS CONTENT

1. Table of Contents shall list all documents contained in the Past Performance Volume, but will not be counted towards applicable page limits.

2. Relevant Contracts are to be provided via Past Performance Information Sheets in accordance with Section J, Attachment 13. The offeror may include information on not more than (10) contracts. Of those ten (10), not more than five (5) may be contracts performed by significant subcontractors* or teaming members. For example, if you submit information on seven (7) contracts performed by you (the Prime), then you may submit information on no more than three

(3) contracts performed by significant subcontractors or teaming partners. Only 10 total PPIS are to be submitted. Offerors are permitted to submit less than the (10) allowed but are encouraged to provide as many as possible to have the greatest impact on the overall Confidence Assessment. Offerors submitting less than the maximum number (10) of allowable citations shall acknowledge this on the bottom of the Relevancy Matrix and that they do not intend to submit more than what is provided, see Section J, Attachment 11. If applicable, you shall acknowledge by initialing the corresponding statement on the bottom of the Relevancy Matrix. Each relevant contract shall have been performed during the past (3) years from the date of issuance of this solicitation. Each Performance Information Sheet for each contract is limited to (4) pages.

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 past performance. For a description of the characteristics or aspects the Government will consider in determining relevance, see Section J, Attachment 9.

3. Consent Letters in accordance with Section J, Attachment 10 (no page limit).

4. Offerors shall identify what aspects of the contract are deemed relevant to the proposed effort using the Relevancy Matrix in Section J, Attachment 11. (no page limit)

NOTES:

Your Past Performance Information Sheets shall not exceed (4) pages per reference with up to (10) references allowed for a maximum of (40) pages.

For all criteria areas, citation references shall be at the task order or stand-alone contract level (No

IDIQ’s). You may cite no more than one task order or one stand alone contract per citation.

The citations provided shall be from either the prime or sub that is proposed to complete the work under this contract.

*Significant subcontractor – Those subcontractors the offeror considers necessary to accomplish critical aspects of the requirement. Additionally, significant subcontractors, will only consist of 1st tier subcontractors, and when used to provide Past Performance Information in proposal submission shall not be substituted after contract award unless approved by NETCENTS-2 Application Services PCO.

L5.1.1.1 Specific Content

Offerors may include a discussion of efforts accomplished by the offeror to resolve problems encountered on those citations provided in the PPIS, Attachment 13, to identify and manage program risk. Merely having problems does not automatically equate to a Limited or No Confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions, in terms of improvements achieved or problems rectified. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required.

L5.1.1.2 Consent/Client Authorization Letters

Past performance information concerning subcontractors and teaming partners cannot be disclosed to a private party without the subcontractor’s or teaming partner’s consent. Because the offeror is a private party, the Government will need consent before disclosing subcontractor/teaming partner past performance information to the offeror during exchanges. In an effort to assist the Government in assessing your past performance record a consent letter is provided in Section J, Attachment 10 and shall be completed by each subcontractor and/or teaming partner identified in your proposal within

Volume I, referenced within L3.1.1. The completed consent letter(s) shall be submitted as part of the

Past Performance Volume, but will not be considered in the page count of that Volume. Should the offeror not submit a completed consent letter for a major or critical subcontractor/teaming partner the

Government will not disclose/discuss the applicable past performance information other than with that prospective subcontractor or teaming partner being reviewed. If there is a concern with the proposed subcontractor’s or teaming partner’s past performance, the offeror can be notified, but no details may be discussed without the subcontractor’s or teaming partner’s permission.

L5.1.1.3 Questionnaires

The Government requests the offeror send out Past Performance Questionnaires and Cover Letters to each of the Points of Contact (POCs) identified in the Past Performance Volume. The questionnaire shall be completed by the person responsible for the contract being referenced (i.e. Contracting Officer, Contracting Officer Technical Representative, Quality Assurance Personnel, Quality Assurance Evaluator, or Civilian Equivalent). Once the questionnaires are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to you, the Offeror. Questionnaires shall be sent directly to the Government by the respondent not later than the due date for the past performance volume. The questionnaire and cover letter can be found at Section J, Attachment 12.

L6.0 VOLUME IV – COST/PRICE

L6.1 General Instructions

L6.1.1 Cost/Price Reasonableness and Realism

This section is to assist you in submitting information other than cost or pricing data that is required to evaluate the reasonableness, realism, and balance of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has made an unrealistic 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, realism, and balance. The burden of proof for credibility of proposed costs/prices rests with the offeror.

L6.1.2 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods to develop their estimates.

L6.1.3 Cost/Price Information

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All information relating to the proposed price, including all required supporting documentation shall be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

L6.1.4 Cost or Pricing Information Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness and cost realism. Information shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit cost or pricing data.

L6.1.5 Rounding

All costs or prices provided shall be carried out to two decimal places.

L6.2 Volume Organization

The Cost/Price Volume shall consist of the following tabbed sections, which will be explained in detail in the following instructions:

SECTION 1 – INTRODUCTION

SECTION 2 – SUMMARY INFORMATION

SECTION 3 – OTHER INFORMATION

SECTION 4 – FINAL PROPOSAL REVISION (THIS SECTION SHALL APPLY ONLY IF THE

PROCURING CONTRACTING OFFICER REQUESTS A FINAL PROPOSAL REVISION)

L6.2.1 SECTION 1 - INTRODUCTION

Include table of contents; glossary of abbreviations and acronyms: summary descriptions of accounting, estimating, and purchasing systems; and changes to estimating and accounting practices.

L6.2.1.1 Table of Contents

The table of contents shall specify by page number the location of information requested in these instructions.

L6.2.1.2 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

L6.2.1.3 Accounting System

For CLINs requiring other than Firm Fixed Price (FFP) prices (i.e., Fixed Price Incentive, Cost Plus Fixed

Fee, etc.) involving cost information reporting or for reconciliation purposes, accounting systems adequacy and approval is required.

Also, identify any deviations from your standard procedures in preparing this proposal.

L6.2.1.4 Estimating System

Provide a summary description of your standard estimating system or methods. Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether you have Government approval of your system and, if so, provide evidence of such approval.

L6.2.1.5 Purchasing System

Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from your standard procedures in preparing this proposal. Indicate whether you have Government approval of your system and, if so, provide evidence of such approval.

L6.2.2 SECTION 2 – SUMMARY INFORMATION

L6.2.2.1 Application Services Price Proposal Workbook

Complete the Application Services Price Proposal Workbook’s separate worksheets (Cover Page, Maximum Labor-Hour Rates Best Estimated Quantities (BEQ) Worksheet, Cost Reimbursable Sample

TO, FFP Sample TO Total Price and Total Evaluated Price (TEP) Worksheet) as described below. The offerors shall provide a full labor category description (with qualifications) for each proposed labor category addressing the specific skill sets and skill levels and how they can perform this work through experience and/or training. Electronic submissions shall be made using the Application Services Price

Proposal Workbook in Excel format to allow electronic manipulation of data for evaluation purposes. The offeror shall not password protect the Application Services Price Proposal Workbook located in Section J, Attachment 14.

L6.2.2.1.1 Cover Page Worksheet

Complete the Cover Page worksheet by inserting the Offeror Name, Offeror Address, City, State, Zip, Point of Contact, Phone 1, Phone 2, Fax 1, Fax 2, E-mail 1, and E-mail 2 into the appropriate cells.

L6.2.2.1.2 TEP Worksheet

Offerors shall insert the total price for each sample task order into their respective total price rows in the

Application Services Price Proposal Workbook, TEP tab in Section J, Attachment 14. The offerors Total

Labor-Hour (LH) Price from the Maximum Labor-Hour Rates BEQ Worksheet will automatically populate the Total Labor-Hour Price Row in the TEP worksheet. Specific instructions for submitting responses to the sample task orders follow in paragraphs below.

L6.2.2.2 Instructions for Test Support Cost Reimbursable Sample Task Order

The requirements of this section apply only to the cost reimbursable sample task order. Offerors shall propose a fully priced solution to the cost reimbursable sample task order provided in Section J

Attachment 15. Proposals shall be broken out by year, option, and CLIN, as applicable. Offerors shall provide separately a detailed cost build-up (reflecting all elements of cost and the bases of estimates) based upon the proposed approach described in the technical volume to accomplish the task order.

The proposal should reflect the proposed labor categories, estimated hours in each, materials, travel and

ODCs, and all applicable rates and factors (including direct labor rate, fringe rate, overhead, G&A, other indirect rates or factors and profit, as applicable) and the cost model used to develop the proposed cost.

Additionally, the offeror shall input the proposed cost/price into the Application Services Price Proposal

Workbook, Cost Reimbursable Sample TO tab, of the Price Proposal Workbook (Section J, Attachment

14) in the format prescribed.

The proposed approach and required resources must demonstrate a full understanding of the scope and complexity of the effort set forth in the sample task order technical requirements. Offerors shall base their estimate on the location specified in the task order.