11-R-0006_A009.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION G - CONTRACT ADMINISTRATION DATA

The following have been added by full text:

LOCAL REQUIREMENTS

21 December 2012

A. INVOICE SUBMISSION AND PAYMENT

ELECTRONIC SUBMISSION OF INVOICES AND RECEIVING REPORTS IS MANDATORY in accordance with DFARS 252.232-7003

1. ELECTRONIC SUBMISSION VIA WIDE AREA WORKFLOW (WAWF): Contractors must register and begin submitting electronic invoices immediately through the Wide Area Workflow Receipt and Acceptance Internet site: https://wawf.eb.mil/. On line training is available at http://www.wawftraining.com unless unable to do so. Use the following data elements to invoice for services or supplies procured via this contract. The award document number is located in the lower right-hand corner.

2. If a contractor believes that its policies and procedures meet the criteria outlined in Defense Contract Audit Agency Pamphlet No. 7641.90, Information for Contractors, the contractor may write to its cognizant DCAA office to request participation in the direct billing program. The pamphlet is available via Internet at http://www.dcaa.mil If DCAA determines that a contractor is eligible to participate in the direct billing program, a copy of the DCAA authorization memorandum must be sent to the Contracting Officer.

Invoice Type: Invoice and Receiving Report: COMBO

Located in Block

Send Additional Email Notification To: vermellvs@stratcom.mil cynthia.waller@offutt.af.mil snydersc@stratcom.mil

2. PAYMENT WILL BE MADE BY:

Defense Finance and Accounting Service

DFAS-FVB/LI

27 Arkansas Road

Limestone, ME 04751-1500

Contact DFAS-FVB/LI to check payment status at (800) 390-5620 or (207) 328-5620 or via website www.dfas.mil: (Commercial Pay, then Vendor Pay Inquiry System (VPIS), then Non-MOCAS System: then Query by Contract Number, EFT Trace Number, DUNS Number or Cage Code)

B. CHANGES TO THIS CONTRACT / PURCHASE ORDER / DELIVERY ORDER

The Contracting Officer (CO) is the only person authorized to approve changes or modify any of the requirements under this contract and, notwithstanding any provisions contained elsewhere in this contract, the said authority remains solely with the CO. In the event the Contractor effects any such change at the direction of any person other than the CO, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in costs incurred as a result thereof.

Contractual problems, of any nature, which might occur during the life of the contract must be handled in conformance with public laws and regulations and must be referred to the CO for resolution. Only the CO is authorized to formally resolve such problems. Therefore, the Contractor is hereby directed to bring all such contractual problems to the immediate attention of the CO. Any request for contract changes/modification shall be submitted to the CO.

C. SAM.GOV REGISTRATION

Invoice payment cannot be made if a contractor has not been registerd through The System for Award Management (SAM). Register at https://www.sam.gov/portal/public/SAM/ this is a single entry point for contractor’s to process System for Award Management (SAM), Online Representations and Certifications Application (ORCA) and Excluded Parties List System (EPLS). Invoices received from a contractor who fails to maintain active SAM registration are considered to be improper and may be returned. The contractor is responsible to maintain active SAM registration until final payment has been made. SAM registration must be updated and renewed annually. If the contractor chooses not to publish their information in SAM.GOV, you MUST fill out and return FAR Provision 52.212-3 Offeror Representations and Certifications – Commercial Items to include the Tax Identification Number within this Provision.

D. DELIVERY / BASE ACCESS REQUIREMENTS

Delivery personnel must use the SAC Gate on Capehart Road. Nebraska highway 75 intersects with Capehart Road, the SAC Gate is located approximately 1 mile east of highway 75. Report to the Visitor's Center and call for escort (if needed) to the final destination:

POC:

Scott Snyder

(402) 232-5357

Delivery vehicles are subject to search by Security Forces personnel. All tools, including assembly tools, must be secured within a toolbox in the trailer of the vehicle and should not be transported on base in the cab of the vehicle. All personnel accessing Offutt Air Force Base will be held to safety/security rules of engagement when entering and while on base. These rules include a ban on weapons to include firearms, loaded or otherwise, and the transport of any explosive material.

E. NATIONAL CRIME INFORMATION CENTER (NCIC) BACKGROUND CHECK

1. In addition to the requirements identified in FAR 52.204-9 - Personal Identity Verification of Contractor Personnel and AFFARS 5352.242-9000 - Contractor access to Air Force installations, all contract employees require a positive NCIC background check prior to being granted access to Offutt AFB in accordance with the installation security policy. To expedite this requirement, the contractor shall complete NCIC Data Memo in Section J for every employee proposed to perform work under this contract requiring physical access to Offutt AFB. All completed forms will be forwarded to the following POC no later than 3 business days prior to the contract start date:

55 SFS/S5A

Mr. Gregory P. Derkatch

198 Butler Blvd.

Offutt AFB, NE 68113

Phone: (402) 232-7339

Email: Gregory.Derkatch@offutt.af.mil

A memorandum shall be prepared for each follow-on/replacement employee who is not provided with the initial group of employee data. Each shall be provided no later than 3 business days prior to the proposed individuals start date.

2. If an individual is denied a base pass/access to the installation, the contractor is not prohibited from hiring that individual for work on this contract as long as the work entailed does not require the individual to have physical access to Offutt AFB or any of its facilities. Employees who refuse to complete the form will be denied access to the installation.

3. All illegal aliens are considered unauthorized individuals and will be barred from the base. Illegal aliens attempting entry or found on the installation (if incorrectly issued a pass) will be processed as an unauthorized individual and removed from the installation. In addition to notifying the contractor of the illegal alien, the Offutt AFB Security Forces will notify AF Office of Special Investigations, local police and the US Immigration and Customs Enforcement office. Contractors are prohibited from hiring illegal aliens for work on a Government contract and the other Government agencies contacted upon discovery of the illegal may seek corrective and/or punitive actions pursuant to law against the hiring organization if violations occur.

4. The below list, which will be verified every 30 days during contract performance, identifies reasons why an individual, if they are identified during the NCIC check, would be denied access to Offutt AFB:

Disqualifiers that would deny contract employee’s entry/access to the installation or its facilities:

- U.S. Citizenship, immigration status, or Social Security Account Number cannot be verified.

- Wanted by federal or civil law enforcement authorities, regardless of offense or violation.

- Conviction of firearms or explosives violation within the past three years.

- Incarcerated for 12 months or longer within the past three years, regardless of offense or violation.

- Conviction of espionage, sabotage, treason or terrorism, murder, sexual assault, armed assault/robbery, rape, child molestation, drug possession with intent to sell, or drug distribution.

- Name appears on any federal agency’s “watch list” or “hit list” for criminal behavior or terrorist activity.

- Any other criminal activity identified on the NCIC check that the Wing Commander determines to be so serious as to pose a possible threat to the safety and security of base personnel and facilities.

5. A 100% Base Pass check is required for all contractors (even if a passenger in an authorized vehicle) and contract vehicles entering the installation. Contractors are not authorized to bring guests or other contract employees onto the installation unless those individuals are personally in possession of a base pass or Government Identification card.

F. MOTOR VEHICLE OPERATION ON BASE

1. Contractor personnel are advised that seat belt usage is mandatory at all times on Offutt AFB. Nebraska state law requires the use of restraints in a vehicle. Offutt AFB Instruction 31-204, 20 October 2010, Security, Motor Vehicle Traffic Supervision states that failing to utilize seat belts or other restraints while moving will result in the issuance of a 7-day driving suspension and the individual’s traffic history on Offutt AFB being assessed points for the first offense. Repeated offenses on Offutt AFB will result in the loss of on-base driving privileges and could have an adverse affect on your ability to perform your contract. Air Force Instruction 31-204, Air Force Motor Traffic Supervision, prescribes that installation commanders must ensure drivers comply with state and local traffic laws both on and off base. Accordingly, while on Offutt AFB, operators and passengers must wear restraints and may be ticketed by Offutt security personnel for failure to comply. In addition, the following administrative penalties, as a minimum, will be imposed on drivers who are cited for speeding 10 mph - 15 mph over base housing posted speed limits: the first offense will result in the issuance of a 7-day driving suspension and the individual’s traffic history being assessed points. Repeated offenses on Offutt AFB will result in the loss of on-base driving privileges and could have an adverse effect on your ability to perform your contract.

2. Contractor personnel are advised that vehicle operators on a DoD installation and operators of Government owned vehicles will not use cell phones unless the vehicle is safely parked or unless they are using a hands-free device. The wearing of any other portable headphones, earphones, or other listening devices (except for hands-free cellular phones) while operating a motor vehicle is prohibited (DoD Joint Motor Vehicle Traffic Supervision Regulation, paragraph 4-2). Using a cell phone while driving, without a hands-free device will be considered a "primary offense", meaning that violators are subject to being stopped and ticketed solely for this offense and the individual’s traffic history on Offutt AFB being assessed points for the first offense. Repeated offenses on Offutt AFB will result in the loss of on-base driving privileges and could have an adverse effect on your ability to perform your contract.

G. ANTI-TERRORISM INFORMATION AND CONSIDERATIONS

1. Base Entry: All contractor vehicles will enter through the SAC Gate and have a proper vehicle search conducted. Exceptions to this policy will be coordinated through the contracting officer and appropriate security forces personnel.

2. Areas Off Limits: The following areas are off limits unless given specific permission, an escort, or work is to be performed in the area listed. Restricted areas, flight line area, General’s row, dormitories (Bldgs 324, 326, 365, and 367), Bldg 500 complex, and the Offutt Field House gymnasium. Travel to and from the worksite will be made by the most direct route possible.

3. Force Protection Conditions (FPCONS): FPCONS describe the progressive level of countermeasures in response to a terrorist threat to US military facilities and personnel. Force Protection Condition measures are used to deter terrorist attacks on DoD facilities and personnel by:

(1) Varying routines.

(2) Being sensitive to changes in the security atmosphere around DoD facilities and personnel.

The five FPCONS are defined as the following:

(1) Normal: This condition applies when a general global threat of possible terrorist activity exists and warrants a routine security posture

(2) Alpha: This condition applies when a general threat of possible terrorist activity against personnel and facilities, the nature and extent of which are unpredictable.

(3) Bravo: This condition applies when an increased and more predictable threat of terrorist activity exists.

(4) Charlie: This condition applies when an incident occurs or intelligence is received indicating some form of terrorist action or targeting against personnel or facilities is likely.

(5) Delta: This condition applies in the immediate area where a terrorist attack has occurred or when intelligence has been received that terrorist action against a specific location or person is imminent.

Contractors may be asked to leave the base or not be allowed to enter the base when in elevated FPCONs.

For further information concerning FPCONs, contact the contracting administrator or contracting officer for additional guidance.

4. Contractors identified as mission essential, have been briefed on additional duties and responsibilities associated with increased FPCONs.

5. Suspicious Activities/Stolen Equipment: Please report any suspicious activity or stolen equipment to the Law Enforcement Desk at 294-6110.

6. Searches/Spot Checks: During increased Random Force Protection Measures (RAMs) contractors and their equipment are subject to search via RAMs at any time. Spot checks may also be conducted due to RAMs.

7. Identification: Contractor personnel must keep base issued identification on their person while working on base.

H. REQUIRED INSURANCE (IAW FAR 28-306(b))

Reference FAR clause entitled "Insurance . . . “ the Contractor shall, at its own expense, procure and thereafter maintain the following kinds of insurance with respect to performance under the contract.

(1) Workmen's Compensation and Employers Liability Insurance as required by law except that if this contract is to be performed in a State which does not require or permit private insurance, then compliance with the statutory or administrative requirements in any such State will be satisfactory. The required Workmen's Compensation insurance shall extend to cover employer's liability for accidental bodily injury or death and for occupational disease with a minimum liability limit of $100,000.

(2) General Liability Insurance. Bodily injury liability insurance, in the minimum limits of $500,000 per occurrence shall be required on the comprehensive form of policy.

(3) Automobile Liability Insurance. This insurance shall be required on the comprehensive form of policy and shall provide bodily injury liability and property damage liability covering the operation of all automobiles used in connection with the performance of the contract. At least the minimum limits of $200,000 per person and $500,000 per occurrence for bodily injury and $20,000 per occurrence for property damage shall be required.

I. SALES TAX

Offutt Air Force Base is exempt from paying state and local taxes on purchases that it makes per the United States Constitution.

Nebraska Revised Statutes, Sec. 77-2704.02 and Nebraska Sales and Use Tax Regulations 1-12 and 1-72 implement this policy and are applicable to this purchase. The Nebraska Form 13, Nebraska Resale or Exempt Sale Certificate, is applicable to exempt taxes for contracts for services, commodities, and labor on construction projects. 55 CONS cannot provide signed Nebraska Forms 17, Purchasing Agent Appointment and Delegation of Authority for Sales and Use Tax, to exempt State taxes. Therefore, per FAR 52.229-3 or 52.229-4, applicable Nebraska State tax costs for materials should be included in the bid/proposal submitted by the offeror/contractor.

J. IMPLEMENTATION OF FY11 NDAA SECTION 8108, CONTRACTOR INVENTORY

**NOTE** The below Section 8108 is only applicable for service acquisitions valued greater than or equal to the Simplified Acquisition Threshold (SAT), acquired with appropriated funds, and where the Department of Defense is the requiring activity. This includes supply contracts with embedded service elements, Architect and Engineering (A&E), and Research and Development (R&D).

FY11 NDAA Section 8108, Contractor Inventory

“The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.”

*Reporting Period: Contractors are required to input data by 31 October of each year. However, due to the delayed implementation, input of FY12 data is required by 31 Mar 13.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

The following have been deleted:

LOCAL REQUIREMENTS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

SECTION L

INSTRUCTIONS TO OFFERS

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.

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. FY12 designates a three month MPACS transition effort starting 1 May 2013 and ending 31 Jul 2013. Full performance will start on 1 Aug 2013 through 30 April 2014 for the base year, and the option years will be 1 May through 30 April with a six month extension 1 May 2018 through 31 Oct 2018. 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

*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.34M. The unfunded potential efforts dollar amounts may change, but the grand total of a $62.34M 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. For this acquisition, the Contracting Officer is Ms. Cheryl Haun and the Contract Administrator is Ms. Cynthia Waller.

55 CONS/LGC

ATTN: Ms. Cheryl Haun (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: cheryl.haun@offutt.af.mil

55 CONS/LGC

ATTN: Ms. Cynthia Waller (55CONS/LGCZ)

101 Washington Square, Bldg 40

OFFUTT AFB, NE 68113

Phone: (402) 232-8661 or DSN: 272-8661

Fax: 402-294-0430

E-Mail: cynthia.waller@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 May 2013. 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)

(Cheryl Haun or Cynthia Waller)

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.