FA4600-11-R-0006_Amendment_0015_SF30.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

Instructions to Offerors

L1.0.

PROPOSAL PREPARATION INSTRUCTIONS

L1.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, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The response shall consist of the volumes as identified in Paragraph 2.0, Table 2.0.

Notice to Offeror(s)/Supplier(s): Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date for receipt of proposals. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs.

L1.2. The Contracting Officer 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 for the contracting officer to determine the reasonableness and affordability of the price.

L1.3. SPECIFIC INSTRUCTIONS

L1.3.1. BUDGET PROFILE

The following provides the projected budget profile for MPACS. Dollars shown below are in millions. Base Year designates a three month MPACS transition effort starting 31 Oct 13 and ending 30 Jan 2014. Full performance will start on 31 Jan 2014 through 30 Oct 2014 for the base year, and the four (4) option years will be 31 Oct through 30 Oct with a six month extension 31 Oct 2018 through 29 Apr 2019. The budget includes a six month extension in accordance with FAR 52.217-8, Option to Extend Services. The Government fiscal year (FY) is 1 October through 30 September.

Table 1.0 Government Budget in $M

(6 Mo Pd) Total

*Potential 3400/3600 Efforts will be negotiated for Future Development Task Orders (CLIN X003), Future Enhancement Task Orders (CLIN X004), and Future FFP Taskings (CLIN X008)

“* NOTE: The unfunded potential efforts are only projected amounts based upon current information and may change from year to year. The total of $48M in other potential efforts over the life of this contract will be considered within scope and will be included in the estimated total ceiling of $62.48M. The unfunded potential efforts dollar amounts may change, but the grand total of a $62.48M ceiling will not be exceeded.

L1.3.2. POINT OF CONTACT (POC)

The Contract Administrator is the point of contact for this acquisition. Address any questions or concerns you may have to the Contract Administrator.

55 CONS/LGC

ATTN: Ms. Theresa H. Bryant (55CONS/LGCZ)

101 Washington Square, Bldg 40

OFFUTT AFB, NE 68113

Phone: (402) 294-7304 or DSN: 271-7304

Fax: 402-294-0430

E-Mail: theresa.bryant@offutt.af.mil

55 CONS/LGCZ

ATTN: Mr. Justin Pedersen (55CONS/LGCZ)

101 Washington Square, Bldg 40

OFFUTT AFB, NE 68113

Phone: (402) 294-9600 or DSN: 271-9600

Fax: 402-294-0430

E-Mail: justin.pedersen@offutt.af.mil

All inquiries must be made in writing and submitted electronically to both the above Contracting Officer and Contract Administrator e-mail addresses. Offeror's will receive a notice of receipt. If they do not, it is their responsibility to follow-up by contacting the Contracting Officer and Contract Specialist, (phone numbers above). Written inquires (via e-mail) will be answered in writing and provided to all Offerors via posting(s) to the Federal Business Opportunities website (www.FedBizOpps.com).

L1.4. PROPOSAL ACCEPTANCE PERIOD AND DUE DATE

The proposal acceptance period/due date is specified in Table 2.0. Unless otherwise noted, proposals are due no later than 4:00 PM Central Time on the date specified. The offeror shall make a clear statement that its offer is valid until 1 Nov 13. Late proposals may be rejected from consideration. If any proposal is received late, the Contracting Officer will promptly notify the offeror that its proposal was received late and whether the proposal will still be considered. A receipt e-mail will be sent to the offeror. If the offeror does not receive a confirmation, it is their responsibility to contact the POC.

L1.5. BROCHURES, DOCUMENTATION, BINDING, AND ARTWORK

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

L1.6. DISCREPANCIES

If an offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the Contracting Officer in writing with supporting rationale, prior to proposal.

L1.7. DISPOSITION OF PROPOSALS

In accordance with FAR Subpart 4.8, Government Contract Files, the Government will retain the “original” copy of all proposals and supplemental documents provided. Unless the offeror requests otherwise, the Government will destroy all extra copies of proposals and additional documents submitted.

L1.8. PROPOSAL CLARITY

The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet the requirements. The offeror shall also provide a cross reference matrix referencing back to the requirements documents. The offeror shall assume that the Government has no prior knowledge of the contractor’s capabilities and experience, and will base its evaluation on the information presented in its proposal. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

L1.9. RESTRICTIONS ON DISCLOSURE AND USE OF PROPOSAL

A proposal may include data, such as technical designs or concepts, financial data, or management plans that the offeror does not want disclosed to the public for any reason, or used by the Government for any purpose other than proposal evaluation and contract award. If the offeror wishes to restrict the proposal, the offeror shall mark it in accordance with FAR 52.215-1.

L1.10. SECURITY REQUIREMENTS

The DoD Contract Security Classification Specification, DD Form 254, incorporated as an attachment, identifies the security clearance requirements of this contract.

L1.11. GOVERNMENT FURNISHED PROPERTY (GFP)

Government Furnished Property is provided as an attachment in Section J of the solicitation.

L2.0. ORGANIZATION OF PROPOSALS

The offeror shall prepare the proposal as set forth in the Proposal Organization Table 2.0 below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 2.0. The attachment identified shall be separately bound in three-ring, loose-leaf binders, as necessary. The proposal organization shall be as follows:

Table 2.0: MPACS Proposal Organization & Page Count

4.6

4.7

III. Past Performance

[5 references @ 3 pages each

Pre-Priced Optional Task Order Pricing

4.6

Development Approach Pre-Priced Optional Task Order Pricing

4.7

4.8

V. Contract Documentation/

Fill-in Clauses

*All documents due by 4:00 PM Central Standard Time on the date specified. Days are expressed in Calendar Days. If Due Date ends on a weekend (Sat or Sun), the deadline will be the following Monday.

** The individual page limitation does not count toward the respective volume page limitation.

*** Small Business Participation Plan is included with the Cost/Price Proposal due to data contained within the plan. The actual plan will be evaluated under Volume II, Technical. The Small Business Participation Plan does not count towards the Technical proposal page restrictions listed above.

L2.1. DEBRIEFINGS

If a competitive range is established, the Contracting Officer will promptly notify offerors of any decision to exclude them, whereupon they may request and receive a debriefing in accordance with FAR 15.505, Preaward Debriefing of Offerors. The Contracting Officer will also notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.503, Notifications to Unsuccessful Offerors. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.506, Postaward Debriefing of Offerors, as applicable.

L2.2. PROPOSAL FORMAT AND CONTENT

L2.2.1. PAGE LIMITATIONS

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will not be returned to the offeror. Excess pages shall be destroyed along with all unsuccessful proposals (ref. 1.7). For electronic submission, no hidden fields, macros, comments, etc. will be read. All information must be written clearly and be easily accessible. Page limitations may also be placed on Evaluation Notices (ENs), if required. The page limitations for ENs, if any, will be identified in the correspondence forwarding the ENs to the offerors. When both sides of a sheet of paper display printed material, it shall be counted as two pages. Each page shall be counted except: cover pages, tables of contents, cross-reference matrix, tabs, and glossaries.

L2.2.2. PAGE SIZE

Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than Times New Roman 10 point. Use at least 1-inch margins on all sides of each page. Pages shall be numbered sequentially by volume. If there are discrepancies in page counts between paper, CD-ROM volumes and e-mail submittals, the paper version shall take precedence.

2.2.3. TABLES, CHARTS, GRAPHS, AND FIGURES

Legible tables, charts, graphs and figures shall 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 when printed. 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, and not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 8 point.

L2.2.4. CLASSIFIED INFORMATION

Proposals shall not contain classified information.

L2.2.5. COST OR PRICING INFORMATION

All cost or pricing information shall be addressed only in the Cost/Price Volume.

L2.2.6. ELECTRONIC MEDIA

Offeror shall submit all volumes in electronic format, using IBM-compatible, virus-free CD-ROM. On each CD-ROM indicate the offeror’s name, solicitation number, volume, and title. WinZip shall be the compression/ decompression program used if files are required to be compressed. The electronic copies of the proposal shall be submitted in a format readable and usable by Microsoft 2007 Office suite (MS Word, MS Excel, and PowerPoint). Hidden fields, comments, macros, etc shall be omitted, and read passwords on files shall not be used. The documents submitted should print to match the original, paper copy submitted. All information shall be clearly displayed. In the event there is a discrepancy between the content found in a paper copy and an electronic copy, the paper copy shall take precedence. The receipt of the paper copy shall constitute the timely receipt of the formal proposal.

L2.2.7. CROSS-REFERENCE MATRIX

To the greatest extent possible, each volume shall be written on a stand‑alone basis so that its contents may be evaluated with minimal cross-referencing to other volumes of the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Offeror shall provide a cross-reference matrix indicating the corresponding proposal paragraph in that section and/or volume which addresses the referenced item. Information required for proposal evaluation that is not found in its designated volume will be assumed omitted from the proposal. The cross-reference matrix will not count against the page limitations for their respective volumes.

L2.2.8. TAB 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. Indexes and tabs do not count against the page limitations for their respective volumes.

L2.2.9. GLOSSARY OF TERMS

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

L2.2.10. BINDING AND LABELING

Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder, which shall permit the volume to lie flat when open. Staples shall not be used. A cover sheet shall be included in each volume, clearly marked as to volume number, title, copy number, solicitation identification and the offeror's name. 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 FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

L2.2.11. DISTRIBUTION

The “original” proposal shall be identified and delivered to 55CONS. All copies of proposals (See Table 2.0) shall be mailed or delivered to:

55th Contracting Squadron/LGCZ

ATTN: Mission Planning and Analysis Common Services (MPACS)

(Attn: Ms. Theresa Bryant or Mr. Justin Pedersen)

101 Washington Square, Bldg. 40

Offutt AFB, NE 68113-2107

Offerors are cautioned that Offutt AFB, NE has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. SOME DELAY SHOULD BE ANTICIPATED WHEN HANDCARRYING PROPOSALS; therefore, please allow adequate time. If you are unable to access the base or denied access to Offutt AFB, NE, the proposal will need to be mailed, please plan accordingly.

If mailing, the outside of the envelope or box(es) should be marked as follows:

NOTE: TO BE OPENED BY ADDRESSEE ONLY

SOURCE SELECTION INFORMATION – SEE FAR 3.104

FOR OFFICIAL USE ONLY

L3.0. VOLUME 1 - Executive Summary

Volume I is due per Section L, para 2.0. In the executive summary volume, the offeror shall provide the following information:

L3.1. Narrative Summary

The narrative summary is a summary of the entire proposal and should be clear and concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. This should be a "big picture" explanation and provide the offeror’s overall approach and supporting rationale for the management/ operation of the MPACS requirements. Within the Narrative Summary, the offeror shall state that its proposal is valid for the timeframe designated in paragraph L1.4 Proposal Acceptance Period and Due Date. The contractor shall identify those personnel authorized to negotiate on behalf of the company along with the telephone number, fax number, mailing address, and e-mail address. The contractor shall also provide the person to contact in the event the offeror is awarded a contract (provide at a minimum, contact’s name, title, phone number, and e-mail address). The Executive Summary shall be no more than 3 pages, and will not count towards the maximum page count for Volume II, Technical Approach and Technical Risk. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

L3.2. Table of Contents

Include a master table of contents of the entire proposal. The format of the Executive Summary is at the discretion of the offeror, but shall include a Master Table of Contents of the entire proposal that identifies where material may be found for each evaluation factor and/or subfactor as defined in the RFP.

L4.0. VOLUME II – TECHNICAL APPROACH AND TECHNICAL RISK VOLUME

L4.1. General

Volume II is due per Section L, para 2.0. The Offeror’s Technical Approach proposal shall be specific and complete. Legibility, clarity, and coherence are very important. The Offeror’s technical approach should provide as specifically as possible the actual methodologies that will be used and how a successful partnership with the Government will be established in accomplishing/satisfying the MPACS requirements. 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 Approach Volume will be used to evaluate the Technical Approach and Technical Risk of the Offeror’s proposal. Evaluation will be against the Technical Approach subfactors as specified in Section M, Evaluation Factors for Award, of this RFP.

L4.2. Format and Specific Content

The purpose of the Technical Approach and Technical Risk volume is to provide the Government the ability to evaluate the management and technical capability of the offeror to perform the MPACS support requirements. The Technical Approach and Technical Risk volume shall consist of the following sections:

VOLUME II: Technical Approach and Proposal Risk

Subfactor 1: Architecture and Systems Engineering

Subfactor 2: Staffing

Subfactor 3: Transition Plan

Subfactor 4: Pre-Priced Optional Task Order

Subfactor 5: Development Approach

Subfactor 6: Small Business Participation Plan

L4.3. Subfactor 1 – Architecture and Systems Engineering: The Offeror shall define and describe the architecture and systems engineering approach to AWPS (and any other products that may be developed under this contract) as identified in the PWS. The offeror shall include internal processes, procedures, and related technical expertise for systems engineering, software engineering, information assurance, configuration management, testing, and technical analysis/evaluation.

L4.3.1. The Offeror shall describe the overall approach and process to effectively manage and maintain AWPS software, to include understanding of the AWPS mission architecture, planning processes, and system/software maintenance/enhancement/development tasks. Describe the interfaces AWPS has with other systems, both inside and outside the USSTRATCOM complex. Describe the plan to ensure that the sustainment of AWPS software meets the PWS requirements.

L4.3.2. The Offeror shall define and describe the plan, methodology, and processes that will ensure AWPS (and any other products that may be developed under this contract) activities and products provide a solution consistent with the ISPAN MPAS architecture (see MPAS Initial Architecture Guidance & MPAS CONOPS for additional information in the Bidder’s Library disk distributed to attendees of the site visit), to include the PWS requirements, and all other contract requirements, are satisfied throughout the system lifecycle. The Offeror shall describe the plan to provide appropriate insight into contractor processes and management systems to include an overview of the software development lifecycle processes that will be followed to maintain/develop software under this PWS.

L4.3.3. The Offeror shall provide a mature process for managing and implementing requirements, to include tracking, test/verification analysis, derived requirement identification/tracking and certification of software change requests and/or new requirements. Provide independent certification (e.g. Capability Maturity Model Integrated Software (CMMI SW) Level 3 or equivalent and ISO 9001) that the division/business unit's software development and maintenance processes demonstrate a solid procedural control. Demonstrate procedures are defined, planned, tracked, and repeatable, and processes are quantitatively managed and/or incorporate continuous improvement. Demonstrate that the processes are clearly used in the day-to-day operations of the business unit and are minimally impacted by using in-house or outsourced resources. Describe alignment/ability of processes to ensure the quality of the software, reviews, metrics and documentation/artifacts required by the PWS and CDRLS.

L4.3.4. The Offeror shall demonstrate how you will collaborate with USSTRATCOM; teaming partners/ subcontractors; other application contractors within the ISPAN environment; contractors working programs within USSTRATCOM; and others collaborating with USSTRATCOM.

L4.4. Subfactor 2 – Staffing: The Offeror shall define and describe the plan, methodology, and processes that will ensure the staffing activities/personnel activities/products satisfy the MPACS PWS requirements, and all other contract requirements throughout the system/software lifecycle. The Offeror shall describe the plan to provide appropriate insight/visibility into contractor processes and management systems. This should include: leadership, reach back capability, contract management, quality control/assurance, and the procedures that will be used for planning, controlling (to include cost and schedule), reporting and directing the accomplishment of the PWS requirements.

L4.4.1. The Offeror shall describe the leadership and oversight processes, tools, techniques, reach back capability to include uninterrupted support for one deep positions, contract management and quality assurance that will be used for planning, controlling (to include cost and schedule), reporting and directing the accomplishments of the MPACS requirements.

L4.4.2. The Offeror shall describe the process to adequately staff this contract (to include qualifications, personnel skills, organizational chart, experience, and security clearances). Describe years of relevant experience and provide qualification summaries of key personnel. It is mandatory to use Tables 4.1 and 4.2 below. For Table 4.1, each offeror is to list each of their skill sets in the top row of the table. Each skill set will then identify their area of expertise as stated in the left column. Table 4.2 will then identify which skill sets from Table 4.1 will be used to accomplish each corresponding paragraph within the PWS and the number of Full Time Equivalents (FTE) proposed to accomplish each paragraph. The offeror will describe their skill set criteria and definitions. The matrix will not count towards the overall proposal page limit.

L4.4.3. The Offeror shall describe the process to provide training and security clearances that are appropriate for assigned responsibilities/areas.

L4.4.4. The Offeror shall describe the methodology that will be utilized for recruiting, hiring, retaining, and replacing employees (especially those with security clearances) throughout the life of the contract. Explain how uninterrupted support will be provided during a labor strike, surges, natural disasters, disruptive world events, terrorist attacks, and other emergencies. Demonstrate how the Continuation of Essential Contractor Services Clause (DFAR 252.237-7023), and Policy and Procedures for Determining Workforce Mix (DoDI 1100.22), will be met. In Volume IV, submit a total compensation plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract in accordance with FAR 52.222-46.

L4.4.5. The Offeror shall describe the approach to provide system training to users.

L4.4.6 Deleted Table 4.1 Skill Set Matrix

Skill Set Matrix

Skill Set 1

Skill Set 2

Skill Set 3

Etc.

Minimum Skill/Knowledge Expertise

Domain Concepts

Integrated Strategic Planning and Analysis System (ISPAN) Mission Planning and Analysis System (MPAS)

OPLAN 8010

Conventional and nuclear planning systems information ICBM platforms and weapons information

SLBM platforms and weapons information Nuclear bomber platforms and weapons information Nuclear cruise missile platforms and weapons information

B-52 bomber platforms and weapons information B-1 bomber platforms and weapons information B-2 bomber platforms and weapons information Tanker platforms information Technical Concepts

Coding standards

DB tuning

DB administration

Design Patterns

Distributed Computing Architectures

Information Assurance

Object-Oriented Design

Relational Databases

Secure Coding Practices

Service-Oriented Architecture

Stored Procedures

Web Services

Domain Data Standards

ISPAN Enterprise Database Languages

ActionScript

Adobe Flex

Adobe Flash

Blaze DS

C++

C#

Java

Java Script

MXML

Perl Scripting

SQL

Unix Shell Scripting

WSDL

XML

XSD

Libraries and Application Programming Interfaces

ActiveX Transaction Library

ActiveX Data Objects

BlazeDS

COM

Jasper Reports*

JCA

JDBE

Java EE

JPA

JXL

MFC

Microsoft ADO Objects

GOTS Products

PDCALC

Client Infrastructure Products

ESRI ArcGIS Desktop

ESRI ArcGIS Engine

Microsoft Internet Explorer

Windows XP

Server Infrastructure Products

CGA

ESRI ArcGIS Server

Oracle DB

VMware

WebLogic Server

Operating Environments

Linux

Solaris

Windows

Development Tools

Adobe Flex Builder

CA ERwin Data Modeler*

Code Manager*

JDK*

JIRA*

Maven

Microsoft Visual Studio and SourceSafe*

Oracle DBMS

Oracle WebLogic Server

Source Code Control System (SCCS)/Version Tool*

SQLplus*

Sun TeamWare*

Sun Workshop*

UML Design Tools (Enterprise Architect, Rational Rose, Visio, etc.)

WinCVS*

Geodesy

ESRI Map Objects*

CJMTK*

Security

SCI Personnel Clearance

Top Secret Personnel Clearance

Other Requirements

Information Assurance (IA) Expertise *These tools are in use for the current contract. Skill sets may include tools comparable to those specifically listed in Table 4.1. Offeror to provide details of any comparable tools included in a skill set.

Table 4.1.1

Required Skillsets needed by the end of the transition period

Skill Set Matrix

Skill Set 1

Skill Set 2

Skill Set 3

Etc.

Domain-Specific Models and Algorithms

Campaign Analysis

Common Mission Definition (CMD)

Common Route Definition (CRD)

Common Weapon Definition (CWD)

Languages

Fortran

Java 7

Development Tools

Eclipse Java Development Tools

Fortify 360

JUnit

GOTS

EADSIM

HPAC/IWMDT

MARS (Missile Application Reusable Services

Web Analysis Models

L4.4.6 Deleted

L4.5. Subfactor 3 – Transition Plan:

L4.5.1 At a minimum, the offeror shall provide:

L4.5.1.1 A realistic, detailed plan for transitioning to the new contract.

L4.5.1.2 A transition plan shall demonstrate how there will be no interruptions to support or degradation of service for MPACS requirements.

L4.5.1.3 Approach to adequately staff this contract with qualified/skilled personnel possessing appropriate security clearances from award to full performance.

L4.5.1.4 Phase-in process that is reasonable and realistic for assumption of full responsibility.

L4.5.1.5 A logical and well thought out approach for obtaining/retaining personnel with the appropriate mix of qualifications/skill sets, IT certifications, and security clearances prior to full-scale performance.

L4.5.1.6 Understanding of the activities and resources required to successfully transition personnel and workload requirements for continuity of mission support.

L4.5.1.7 Transition risks and measures to mitigate them.

L4.6. Subfactor 4 – Pre-priced Optional Task Order: Non-Versioned Data Mover Virtual Implementation Effort This is a pre-priced optional task order that may or may not be awarded with the MPACS contract. Refer to Sec J, Attachment 16.

L4.6.1 Non-Versioned Data Mover Virtual Implementation Effort.

Objective: AWPS planners have the requirement to move data from a QR configuration on the EDB to the PRP database using PC AWPS following PRP rules to use a two-man user name and password. As part of the MPAS modernization effort to operate in a virtual environment there is a future requirement to duplicate this data mover capability in Web AWPS. The Statement of Objectives (SOO), Section J, for this effort is to implement one data mover function, in the proposed MPAS program virtual environment which is outlined in the MPAS Initial Architectural Guidance located in the Bidder’s Library disk distributed following the site visit. The Non-Versioned Data Mover Implentation Effort is considered an enhancement to the MPACS contract. Benefits of this implementation include enhanced backup and survivability capabilities.

At a minimum, the Offeror shall provide:

1) A Performance Work Statement.

2) A Technical Volume that details the approach/methodology to provide the vision of the AWPS software to provide the capability described in the Statement of Objectives, to include high level design artifacts, assumptions, limitations, and constraints.

3) A Cost Volume that details contractor staffing skill sets and levels of effort, associated rates, and delta SLOC estimates required to accomplish the basic task described above. The Cost Volume will be included in the Cost/Price Volume IV.

L4.7 Subfactor 5 – Pre-Priced Optional Task Order: Development Approach, Plan Monitoring/Management Requirements

This is a pre-priced optional task order that may or may not be awarded with the MPACS contract.

L4.7.1 Pre-Priced Optional Task Order: Development Approach, Plan Monitoring/Management Requirements.

Objective: To evaluate the development approach for satisfying Plan Monitoring/Management requirements. Refer to Development Approach SOO in Sec J, Attachment 19 for requirements.

At a minimum, the Offeror shall provide:

1) A Performance Work Statement.

2) A Technical Volume that details the methodology, processes, high level design, etc. to provide the software capability described in the SOO. This should include high level design artifacts (i.e. diagrams, descriptions, etc) , assumptions, limitations, risks and constraints. In addition, the Technical Volume should include a list of proposed COTS/GOTS products and why their use would benefit the Gov’t (both technically and cost); how IA will be addressed during all phases.

3) A Cost Volume that details contractor staffing skill sets and levels of effort, associated rates, and delta SLOC estimates required to accomplish the basic task described above. The Cost Volume will be included in the Cost/Price Volume IV.4.6.

L4.8 Subfactor 6 - Small Business Participation Plan:

L4.8.1. The offeror shall submit a Small Business Participation Plan which will be used for the purposes of evaluating the offeror’s identification of and commitment to small business in contract performance on the MPACS contract. The Participation Plan is required from all offerors, including small businesses, large businesses, non-profit entities and companies with commercial subcontracting plans, master subcontracting plans, individual (program) subcontracting plans and/or comprehensive subcontracting plans.

L4.8.2. The Government has established a 15% target small business participation goal, based upon total contract dollars, for this program. The offeror shall demonstrate how they intend to promote, and utilize small business (SB), small disadvantaged business (SDB), women-owned small business (WOSB), Historically Underutilized Business Zone (HUBZone) small business, veteran-owned small business (VOSB) and/or service-disabled veteran-owned small business (SDVOSB), including the use of small businesses in mission critical aspects of the program. The percentages of the various subcategories of small business should be based on total subcontracting dollars and first, second and third tier subcontracting dollars can be counted towards meeting your small business participation goals. A small business offeror shall show total small business participation, to include their percentage of performance and the percentage they intend to subcontract to small businesses. The offeror’s SB Participation Plan shall also include the eleven (11) elements listed under FAR 19.704(a).

L4.8.3. Small Business Innovation: The offeror’s SB Participation Plan shall include their planned initiatives to assist, promote, and utilize small business (SB), small disadvantaged business (SDB), women-owned small business (WOSB), Historically Underutilized Business Zone (HUBZone) small business, veteran-owned small business (VOSB) and/or service-disabled veteran-owned small business (SDVOSB) on the MPACS contract. Demonstrate examples of how the offeror is maximizing SB opportunities and using SB in meaningful work (e.g. mission critical, technology innovation) throughout the proposed program.

L4.8.4. An acceptable small business subcontracting plan will need to be provided only by the apparent successful offeror prior to award per FAR 19.702(a)(1). Reference Section H-45 for additional details. The Small Business Participation Plan will be used for RFP evaluation purposes.

NOTE: Small Business Participation Plan is included within the Cost/Price Proposal due to data contained within the plan. The actual plan will be evaluated under Factor 1, Technical. The Small Business Participation Plan does not count towards the Technical proposal page restrictions.

L5.0. VOLUME III – PAST PERFORMANCE INFORMATION

Volume III is due per Section L, para 2.0. Limited to no more than five separate contracts with three (3) pages per contract listed. Only references for same or similar type contract desired. Submit original plus five (5) copies.

L5.1. INSTRUCTIONS

The Past Performance volume of the offeror’s proposal is due per Section L, para 2.0.. CPARS evaluations will take precedence over individual assessments.

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 of the offeror’s recent and relevant contracts to determine an overall “Confidence” rating. For the purpose of this evaluation, the term “offeror” includes the prime offeror and/or team members and major subcontractors.

L5.2. CONTENT OF PAST PERFORMANCE VOLUME

The offeror’s Past Performance Volume shall contain the following:

Table of Contents

Summary Page

Contractor’s Past/Present Performance Information Documents

Past/Present Performance Questionnaire Tracking Record

Past/Present Performance Assessment Reports

Consent Letters

Client Authorization Letters

Organization Structure Change History

Quality Awards

L5.3. SUMMARY PAGE

The Summary shall describe the role (for the proposed MPACS requirement) of the offeror and each subcontractor, teaming partner/joint venture partner that the offeror is required to provide Past Performance Information Documents pursuant to the paragraph below.

L5.4. CONTRACTOR’S PAST/PRESENT PERFORMANCE INFORMATION DOCUMENTS

L5.4.1. RECENCY AND RELEVANCY OF PAST PERFORMANCE

L5.4.1.1. Offeror’s should provide past performance information on contracts considered relevant in demonstrating their ability to perform the MPACS requirements. Include rationale supporting your assertion of relevance, however, the Government is not bound by the offeror’s opinion of relevancy. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Where problems existed, clearly demonstrate management actions employed in overcoming these problems and the effects of those actions, in terms of improvements achieved or problems rectified. The evaluation of past performance will take into account past performance information regarding predecessor companies, key personnel who have relevant experience or subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the instant acquisition. If the offeror submits a delivery/task order as past performance, it shall be counted as a contract.

L5.4.1.2. Contracts submitted for review should also be recent. In determining recency, the Government will only consider work performance under an effort existing after 1 Dec 2008. Additionally, performance of less than one year from the date of the MPACS solicitation will not be considered due to limited performance history of these efforts.

L5.4.1.3. Offeror shall submit Past Performance Information Documents in accordance with the format contained at Sec J, Atch 8 for the Prime Offeror and any subcontractors, teaming partners, and joint ventures that will perform major or critical aspects of the requirement when the information is relevant to the subject acquisition. The maximum number of Past Performance Information Documents an offeror may submit is three (3). The maximum number of Past Performance Information Documents an offeror may submit for any subcontractors, teaming partners, and joint ventures is two (2) each. Each Past Performance Information Document is limited to three (3) pages. Submit original plus five (5) copies. (Note: The Government reserves the right to evaluate more references that it locates through past performance evaluation research.) The required documentation is as follows:

L5.4.2. PAST PERFORMANCE QUESTIONNAIRE TRACKING RECORD

Offeror shall send out, and confirm receipt and submission of the Past and Present Performance Questionnaire at Sec J, Atch 10, to each of the offeror’s major subcontractors’, teaming Contractors’ and/or joint venture partners’ (e.g., each entity’s) Points of Contact (POC) identified in the Past Performance Questionnaire Tracking Record at Sec J, Atch 11. The responsibility to send out and track the receipt and submission of the Past Performance 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 at Sec J, Atch 9. Cover letters shall be printed on company letterhead. The offeror shall exert its best efforts to ensure that at least two POCs, per relevant contract, submit a completed Past Performance Questionnaire directly to the Government not later than the due date for the past performance proposal volume. To avoid potential conflicts offeror’s are exempt from sending Past Performance Questionnaires to other potential competitors of this acquisition. In this situation, it is the offeror’s responsibility to find an alternative method of providing the Government the same or similar information. Each of the offeror’s POCs shall e-mail the completed Past Performance Questionnaire to Mr. Justin Pedersen at justin.pedersen@offutt.af.mil , or Ms. Theresa Bryant at theresa.bryant@offutt.af.mil. If you do not receive a confirmation e-mail or you do not have the capability to send the documents electronically, please fax it directly to Mr. Justin Pedersen and Ms. Theresa Bryant at fax number (402) 294-0430. Please have your POCs call Mr. Pedersen at (402) 294-9600 or Ms. Bryant at (402) 294-7304 before faxing their response. Once the Past Performance Questionnaires are completed by your POCs, the information contained therein shall be considered sensitive and shall not be released. Questionnaires shall be sent back directly to the Government, with best efforts made to ensure completion and submissions from at least two of the following (in descending order of availability):

Procuring Contracting Officer/Contract Negotiator or equivalent

Administrative Contracting Officer/Contract Administrator or equivalent

Program/Project Manager or equivalent

L5.4.3. PAST PERFORMANCE ASSESSMENT REPORTS

This information is required on the contracts submitted IAW the Past Performance Information Documents paragraph above. If an evaluation method other than a Contractor Performance Assessment Report (CPAR) has been used in conducting performance assessments (e.g. an Award Fee notification letter, a subcontractor’s prime Contractor performance evaluation, etc.) that form/documentation shall be submitted. The offeror should immediately notify the Contracting Officer listed above if a CPAR or other evaluation form has been accomplished on the offeror’s existing work but the contracting office for that requirement will not release the information. Provide the contract number, point-of-contact, and phone number from which the past performance information shall be obtained. This information shall be provided to the Contracting Officer as soon as any difficulty occurs and before the proposal due date.

L5.4.3.1. Quality and Satisfaction Rating for Contracts Completed in the Past Three (3) Years: Provide any information currently available (letters, metrics, customer surveys, independent surveys, etc.) which demonstrates customer satisfaction with overall job performance and quality of completed product for same or similar type contract. In addition, 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.

L5.4.4. CONSENT 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 that consent before disclosing subcontractor/teaming partner past performance information to the offeror during exchanges. (Sec J, Atch 12 – Subcontractor/Teaming Partner Consent Letter for the Release of Past and Present Performance Information to the Prime Contractor) In an effort to assist the Government in assessing your past performance relevancy and confidence, request the sample consent letter be completed by the major subcontractors/teaming partners identified in your proposal. The completed consent letter shall be submitted as part of the Past Performance Information Volume, but will not be considered in the page count of this Volume. Should the offeror not submit a completed consent letter for major subcontractors or teaming partners, the Government will only discuss past performance information directly with the prospective sub-contractor or teaming partner that is being reviewed. If there is a problem with the proposed subcontractor’s or teaming partner’s past performance, the offeror can be notified of a problem, but no details may be discussed without the subcontractor’s/teaming partner’s permission. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the offeror's performance. (Sec J, Atch 13-Client Authorization Letter)

L5.4.5. ORGANIZATION 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 past efforts and this source selection. As a result, it is sometimes difficult to determine what 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 your company. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources. This information is required on the offeror, teaming partners and/or joint venture partners, and major subcontractors, as necessary.

L5.4.6. QUALITY AWARDS

Offeror may describe any quality awards and certifications that indicate the offeror, major subcontractors, teaming contractors and/or joint venture partners possesses the necessary skills to perform the services required. Such awards or certifications include, for example; incentive or quality awards pertinent to the performance of work associated with relevant past performance. Describe when the award or certification was received. If the award or certification is over three years old, provide evidence that the qualifications still apply.

L6.0. VOLUME IV – COST/PRICE PROPOSAL

L6.1 Volume IV is due per Section L, para 2.0. All cost/price information shall be addressed within the cost/price volume only (Note: Section B shall be included in Contract Documentation Volume V). All offerors shall complete and submit the Sec J, Atch 14 (excel spreadsheet), MPACS Price Model, for the proposed price for CLINs X001, X006, X007, X009, and X0010. The Offeror shall populate CLINs X002, X003, X004 and X008 with the Government estimates. See Para L6.4 and L6.7 regarding instructions for X003 and X004. Each Offeror’s proposal shall represent its best efforts to respond to the MPACS requirements. The burden of proof for credibility of proposed cost/price rests with the Offeror and cost rates and applications must be verifiable by the cognizant Defense Contract Audit Agency (DCAA). Any inconsistency between proposed performance and cost/price shall be explained in the proposal. For example, if unique and innovative approaches are the basis for the estimate, the nature of these approaches and their impact on cost/price must be explained. A significant inconsistency, if unexplained, may raise a question of the Offeror’s understanding of the nature and scope of the work required and its ability to perform within the proposed cost constraints, which may cause the proposal to be rejected. In connection to the recruiting, hiring, retraining, and employment replacement methodology referenced in Sec L4.4.4, submit a total compensation plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract in accordance with FAR 52.222-46. The Small Business Participation Plan referenced in L4.8 is to be addressed in the Cost/Price Volume II. The Small Business Participation Plan will be rated in the Technical Volume II.. The information requested in the proposal is required to enable the Government to determine that the proposed cost/price is realistic, fair and reasonable.

Refer to Section L, para 1.3.1 for the transition period and full performance periods.

L6.2 Maintenance & Sustainment (M&S) (CLIN X001/CPIF). The Offeror shall propose an amount for the performance of USSTRATCOM MPACS requirements for maintenance and sustainment for the base and each option period. This CLIN includes target cost and target fee. Target fee will be 6.5% of the proposed target cost. Maximum fee is 8% of the proposed target cost.

L6.2.1 Representative SCR Worksheet (Sec J, Atch 17) provides a sample of representative tasks with descriptions of the tasks available to be accomplished in a 12-month period of performance. Estimate the number of coding hours required for each representative task. The total number of coding hours for the representative tasks is to be shown in the “CLIN 0001 Base Year Breakdown” tab of the MPACS Price Model (Sec J, Atch 14).