Section L DRAFT.pdf

HEDC SMaC: Section L

Section L

Instructions, Conditions, and Notices to Offerors or Respondents

Hill Enterprise Data Center (HEDC)

Sustainment, Modernization, and Consolidation (SMaC)

XX January 2020

Table of Contents

1 PROPOSAL FORMAT

1.1 General

1.2 Communications

1.2.1 Exchange of Information

1.2.2 Submission, Modification, Revision, and Withdrawal of Proposals

1.2.3 Debriefings

1.2.4 Discrepancies

1.2.5 Amendments to Solicitation

1.3 Volume Organization

1.3.1 General

1.3.2 Page Limitations

1.3.3 Page Size and Format

1.3.4 Tables, Charts, Graphs and Figures

1.3.5 Cost or Pricing Information

1.3.6 Cross-Referencing

1.3.7 Indexing

1.3.8 Binding and Labeling

1.3.9 Electronic Offers

1.3.10 Distribution

1.3.11 Proposal Inquiries

2 VOLUME I, FACTOR 1: TECHNICAL PROPOSAL

2.1 General

2.1.1 Amendments

2.1.2 Format and Specific Content

2.1.3 Cross Reference Matrix

2.2 Technical Approach

2.3 Technical Subfactors

2.3.1 Subfactor One: Scenario 1 – Onboarding and Technology Capabilities

2.3.2 Subfactor Two: Scenario 2 – Program and Configuration Management

2.3.3 Subfactor Three: Corporate Experience

2.3.4 Subfactor Four: Transition Plan

2.3.5 Subfactor Five: Cybersecurity

3 VOLUME II, FACTOR 2: COST/PRICE

3.1 General

3.2 Total Evaluated Price (TEP) Matrix, Section J Attachment 3

3.2.1 Rounding

3.3 Cost/Price Data

3.4 Cost or Pricing Data Requirements

3.4.1 Contract Data Requirements Lists (CDRLs)

3.5 Estimating Techniques and Methods

4 VOLUME III, CONTRACT DOCUMENTATION

4.1 Model Contract/Representations and Certifications

4.1.1 Section A - Solicitation/Contract Form

4.1.2 Section B - Supplies or Services and Costs/Prices

4.1.3 Section I - Contract Clauses

4.1.4 Section J – List of Documents, Exhibits, and Other Attachments

4.1.5 Section K - Representations, Certifications, and other Statements of Offerors

4.2 Other Information Required

4.2.1 Authorized Offeror Personnel

4.2.2 Limitations on Subcontracting

4.2.3 Compensation Plan

5 SOLICITATION Requirements, TERMS AND CONDITIONS

5.1 Exceptions to Solicitation Requirements

APPENDIX A: SAMPLE SCENARIO 1 - Onboarding and Technology Capabilities

APPENDIX B: SAMPLE SCENARIO 2 - Program and Configuration Management

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1 PROPOSAL FORMAT

1.1 General

The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause the offeror’s proposal to be determined not eligible for award. Offerors shall submit only one proposal for HEDC SMaC, as the

Government will review only one proposal per offeror. Proposals received are subject to the requirements specified in FAR 52.215-1, unless otherwise tailored in an addendum to the solicitation.

Proposals must be received by the Contracting Officer at 6038 Aspen Ave. Bldg. 1289 NE, Hill Air

Force Base, UT 84056, Attention: Mr. Brady Smith, no later than the date and time specified in Section

A of the solicitation.

The Government intends to award a single Indefinite Delivery Indefinite Quantity (IDIQ) contract for the HEDC SMaC. The contractor will perform work to include, but not limited to, maintaining and sustaining the lifecycle of the HEDC, modernizing and onboarding legacy applications within the

HEDC, systems engineering, architecture and system design, configuration management, product and system integration testing, and cybersecurity.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The offeror’s proposal shall provide a description addressing how the offeror intends to meet the Government’s requirements and evidence of the effectiveness and ability to execute the proposed methodology.

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

The proposal acceptance period is specified in Section A of the solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid for a minimum of 365 days from solicitation closing.

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

1.2 Communications

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. The offeror shall address any questions, concerns or requests for clarification to Brady Smith at brady.smith@us.af.mil (preferred) or the mailing address cited in paragraph 1.1. When appropriate, answers to questions and concerns will be made available to all offerors.

1.2.1 Exchange of Information

Exchanges of source selection information between Government and offerors will be controlled by the PCO. Email may be used to transmit such information only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mail.

1.2.2 Submission, Modification, Revision, and Withdrawal of Proposals

Proposals and modifications to proposals shall be submitted in both paper and electronic media to the address located in paragraph 1.1 of this document, showing the time and date specified for receipt, the solicitation number, and the name and address of the offeror. Late proposals will only be considered IAW FAR 15.208.

Proposals may be withdrawn by written notice received at any time before award. Proposals may also be withdrawn in person by an offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award.

1.2.3 Debriefings

The PCO will notify offerors of any decision to exclude them from the competitive range;

whereupon, they may request and receive a debriefing IAW FAR 15.505, Pre-Award Debriefing of Offerors. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing.

The PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.503, Notifications to Unsuccessful Offerors. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make the request IAW the requirements of FAR 15.505 or 15.506, as applicable.

1.2.4 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale, as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. When appropriate, Government responses will be provided to all offerors.

1.2.5 Amendments to Solicitation

If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. If the RFP is amended prior to proposal delivery, offerors shall acknowledge each amendment by signing and returning the front page of each amendment with the proposal submission. If the RFP is amended after proposal submission, offerors shall respond by the date and time specified in the amendment to include a signed front page of the amended RFP.

1.3 Volume Organization

1.3.1 General

The offeror shall prepare the proposal as set forth in the Proposal Organization Table 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. The volumes identified in the

Table shall be separately bound in three-ring, loose-leaf binders.

The title page of each volume must show:

1) Solicitation Number

2) Company name, address, Commercial and Government Entity (CAGE) Code and Data

Universal Numbering System (DUNS) Number.

3) Primary point of contact name, telephone number and email address

4) Volume number and name (e.g. Volume II, Cost/Price) and copy number (i.e. Original, Copy 1, Copy 2)

Table 1: Proposal Organization

Volume Volume Title

Total

Page

Limits

Number of

Paper Copies

Number of

Electronic

Copies

Description

I Technical 60

(Original plus

1 copy)

Technical Volume includes:

Scenario 1

Scenario 2

Corporate Experience

Transition Plan

Cybersecurity

II Cost/Price N/A

(Original plus

1 copy)

Cost/Price Volume

III

Contract

Documentation N/A

(Original plus

1 copy)

Contract Documentation Volume

RFP compliance

Other Information

1.3.2 Page Limitations

Individual 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 be shredded.

If Evaluation Notices (ENs) are issued, page limitations may be placed on responses. The specified page limits for EN responses will be identified in the letters forwarded with the ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, lists of tables and drawings, cross-reference matrices, tabs, and glossaries.

1.3.3 Page Size and Format

A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Except for the reproduced sections of the solicitation document, the text size shall be Times New Roman font and no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins.

Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

1.3.4 Tables, Charts, Graphs and Figures

Organizations, systems and layout, implementation schedules, plans, etc. shall be depicted in tables, charts, graphs, or figures wherever practical. These items shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than Times New Roman 10 point and searchable for text in Microsoft (MS)

Office Word and/or PDF formats to the maximum practical extent. Ensure all tables, foldouts, graphics, and figures in the electronic version of the proposal are pasted into the proposal in a format that allows a word search by the host program (do not paste as pictures) to the maximum practical extent. These limitations shall apply to both electronic and hard copy proposals.

1.3.5 Cost or Pricing Information

All cost or pricing data shall be addressed only in the Cost/Price Proposal and Contract

Documentation Volumes.

1.3.6 Cross-Referencing

Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity, but must be hyperlinked IAW Section 2.1.3.

1.3.7 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Tables of contents do not count against the page limits for the offeror’s respective volumes.

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

1.3.8 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose-leaf binder permitting the volume to lie flat when open. Staples shall not be used. The outside of each binder shall include a cover sheet, clearly marked, identifying volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. Be sure to apply all appropriate markings including those prescribed IAW FAR 52.215-1(e), Restriction on Disclosure and Use of Data and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source

Selection Information. Any page containing proprietary information should be so marked.

1.3.9 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and the electronic copy, the hard copy shall take precedence and will be used for evaluation. The offeror shall submit Volumes I through III in electronic format, using virus-free CD-R. In no cases shall the offeror use CD-RW. For electronic copies, indicate on each CD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any.

The file naming shall specify the appropriate volume. Each volume shall be on a separate CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable and searchable by MS Office

Word, Adobe PDF, and MS Office Excel (2016 or later).

The Table of Contents of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that clicking the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. The Table of Contents shall include the file names, as well as page numbers where content is cross-referenced between subfactors. Also, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. Hyperlinking references between different filenames is not necessary.

1.3.10 Distribution

The original proposal shall be identified “Original.” The proposal shall be addressed to the PCO and mailed or hand-carried to the address cited in paragraph 1.1.

Delivery of proposals shall be coordinated at least 24 hours in advance of the due date/time with the PCO. Proposals received after the due date and time specified in the solicitation shall be treated IAW FAR 15.208, Submission, Modification, Revision, and Withdrawal of Proposals.

Offerors are cautioned that Hill AFB 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 hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals.

1.3.11 Proposal Inquiries

All inquiries must be submitted via e-mail or mail to the PCO. Questions, if appropriate as determined by the Government, will be answered as quickly as possible, during the proposal preparation period. When appropriate, answers to questions and concerns will be made available to all offerors.

2 VOLUME I, FACTOR 1: TECHNICAL PROPOSAL

2.1 General

The Technical Volume should be specific and include all requirements of Volume I. Offerors’ responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award.

Using the instructions provided below, the offeror shall provide as specifically as possible the actual approach, methodologies, capabilities it would use for satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By its proposal submission, the offeror is representing that its firm will perform all the requirements specified in the solicitation. The offeror shall not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

The Technical Volume shall be organized according to the following general outline:

Section Title

1 Table of Contents

2 List of Tables and Drawings

3 Glossary

4 Cross Reference Matrix

5 Subfactor One: Scenario 1 – Onboarding and Technology Capabilities

6 Subfactor Two: Scenario 2 – Program and Configuration Management

7 Subfactor Three: Corporate Experience

8 Subfactor Four: Transition Plan

9 Subfactor Five: Cybersecurity

Note: Offerors shall not address Appendix “C”, Safety, Fire Protection and Health Specification, Industrial Security Requirements of the PWS in the offeror’s proposal. However, the successful offeror shall submit a Safety Plan at the Post Award Conference and obtain 75th Air Base Wing Safety Office approval.

2.1.1 Amendments

For any amendments to Volume I, the offeror’s proposal will include a cover letter delineating any changes from initial proposal, to include changes/revisions (if needed) for Final Proposal

Revisions (FPR).

2.1.2 Format and Specific Content

The information in paragraphs 2.2 - 2.3 shall be provided in the written technical proposal and will be used to assess the proposed technical approach in accordance with Section M, Evaluation

Factors for Award. The written technical proposal shall address each of the following to describe the offeror’s proposed approach, methodologies, and capabilities in performing the requirements set forth in the subfactors.

2.1.3 Cross Reference Matrix

The offeror shall fill out the Cross Reference Matrix (Section L: Appendix C), and submit with the proposal indicating where in its proposal the information can be found as it relates to the

PWS, Section L, and Section M. The cross reference matrix will help an offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Section M references in the matrix are for informational purposes only, and the Government will evaluate proposals solely in conformance with Section M of the solicitation. This matrix will be used for reference only and will not become contractually binding.

2.2 Technical Approach

In the Technical Volume, address the scenarios, corporate experience, and capabilities and also provide evidence of meeting or exceeding the minimum requirements of each subfactor.

2.3 Technical Subfactors

Subfactor One: Scenario 1 – Onboarding and Technology Capabilities (Appendix A)

Subfactor Two: Scenario 2 – Program and Configuration Management (Appendix B)

Subfactor Three: Corporate Experience

Subfactor Four: Transition Plan

Subfactor Five: Cybersecurity

2.3.1 Subfactor One: Scenario 1 – Onboarding and Technology Capabilities

Utilizing the technologies and skills identified in PWS sections 3.7 through 3.19, the offeror shall propose a detailed solution to Scenario 1 that addresses and satisfies the following:

1) A solution overview that details the following areas:

a. Hardware Implementation

b. Software Implementation

c. Network requirements

d. Storage requirements

e. Virtualization requirements

2) A project plan summary that details the following:

a. Purpose

b. Scope

c. Stakeholders

d. Manpower Summary (see labor categories in PWS paragraph 3.1)

3) A project schedule (MS Project format – assume Jun 1, 2020 start date) that details tasks and dependencies including:

a. WBS

b. Milestones

c. Resources (labor categories [PWS para 3.1] and number of hours per labor category)

4) A bill of material summary that details the following:

a. Hardware specifications and quantities

b. Software specifications and quantities

c. Additional services (if required)

5) Risk Management Summary that identifies any risks, the risk level (low, moderate, or high), and mitigation strategy (if applicable)

a. Programmatic Risk

b. Operational Risk

c. Cyber Risk

2.3.2 Subfactor Two: Scenario 2 – Program and Configuration Management

The offeror shall propose a detailed solution to Scenario 2 that addresses and satisfies the following:

1) Program management plan that details the following:

a. The effects of unplanned workload on onboarding, sustainment, modernization, and cybersecurity

b. Identification and mitigation of risks and schedule impacts

c. Capabilities utilized to maintain established service levels

2) Configuration baseline recommendations that detail how modernization affects the following:

a. Sustainment

b. Cybersecurity

c. Service levels

d. Compliance with DoD policies

3) Surge plan that details the following:

a. Staffing approach to address an unexpected 90-day corporate-level, high-priority effort in the modernization area without schedule and service level impacts to the other areas.

2.3.3 Subfactor Three: Corporate Experience

The offeror shall provide examples of their overall corporate experience within the last 5 years in the areas below. Offeror shall address each element below; however, offeror is not required to address all areas for each example.

1) Management of a Data Center

a. Tier of data center (Uptime Institute Data Center Site Infrastructure Tier

Standard)

b. Multi-tenancy characteristics of applications and infrastructure

2) Onboarding of Legacy Applications in the following methodologies:

a. Agile

b. Waterfall

c. Hybrid

d. Incremental

3) Technologies used in support of the following:

a. Operating systems

b. Databases

c. Application servers

d. Virtualization

e. Storage

f. Networking

4) Risk Management in the following categories:

a. Programmatic

b. Operational

c. Cyber

5) Cybersecurity

a. Integrating cybersecurity considerations into the programs SE, SSE and T&E processes utilizing a detailed defense-in-depth approach

2.3.4 Subfactor Four: Transition Plan

The Offeror shall submit a Transition Plan that meets the requirement to have operational control of the HEDC within 30-45 days after contract award. The plan shall include the following:

1) How key personnel positions (PWS para 4.4 thru 4.8) are (or will be) employed, trained, certified, and able to work accordingly with the appropriate clearances to satisfy the HEDC SMaC requirements within the 30-45 day transition period

2) How all personnel positions will be phased-in for each respective area.

2.3.5 Subfactor Five: Cybersecurity

a) The Offeror shall provide a detailed approach to comply with mandated NIST SP 800-171r1, by providing a synopsis of the offeror’s System Security Plan and Plan of Action and Milestones (POAM).

3 VOLUME II, FACTOR 2: COST/PRICE

3.1 General

The Price Volume should be specific and include all information required of Volume II. Compliance with these requirements is mandatory and failure to comply may result in rejection of the offeror’s proposal. Note that unrealistically low or unreasonably high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject the offeror’s proposal. Offers should be sufficiently detailed to demonstrate reasonableness. The burden of proof for credibility of proposed costs/prices rests with the offeror.

Offerors’ responses will be evaluated in the following areas as defined in Section M of the RFP:

1) Completeness

2) Reasonableness

3) Balance

4) Total Evaluated Price (TEP)

The Cost/Price Volume shall be organized according to the following general outline:

Section Title

1 Table of Contents

2 Listing of Abbreviations and Acronyms (used within cost/price volume)

3 General

3-1 TEP Matrix Worksheet

3-2 Accounting System

3.2 Total Evaluated Price (TEP) Matrix, Section J Attachment 3

Offerors shall input into the TEP Pricing Matrix, located in the Section J Attachment 3, Not-to-Exceed

(NTE) fully burdened rates (regular rate, overtime rate, surge rate) for all labor categories and years.

Fully burdened rates shall include direct labor rates, all direct costs, indirect costs (Overhead, General and Administrative, Fringe Benefits, etc.) and profit necessary for the performance of the entire requirement.

The formula for application of hours and the notional hours used will not be disclosed to offerors. The

TEP is for evaluation purposes only; however, all proposed fully burdened NTE rates are contractually binding.

Submit a copy of the completed TEP Pricing Matrix in Cost/Price Volume II in MS Excel (non PDF format).

3.2.1 Rounding

All fully burdened labor rates provided shall be rounded to the nearest penny.

3.3 Cost/Price Data

Data beyond that required by this instruction shall not be submitted, unless the offeror considers it essential to document or support its cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the

Price Volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

3.4 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided IAW FAR

15.403-5, Instructions for Submission of Certified Cost or Pricing Data and Data other than Certified

Cost or Pricing Data. If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1, Prohibition on

Obtaining Certified Cost or Pricing Data (10 U.S.C. 2306a and 41 U.S.C. 254b) apply, the offeror shall be required to submit additional cost or pricing data.

3.4.1 Contract Data Requirements Lists (CDRLs)

CDRLs will not be separately priced. Cost required to produce each CDRL should be included in the offeror’s proposed labor hours.

3.5 Estimating Techniques and Methods

Offerors shall use generally accepted estimating techniques to develop their estimates for the proposed rates.

3.5.1 Accounting System

Indicate whether you and any subcontractors who provide effort under other-than Firm-Fixed

Price pricing arrangements have Government approved accounting systems and if so, provide evidence of such approval.

4 VOLUME III, CONTRACT DOCUMENTATION

4.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the Model Contract, and Sections A through K. This includes delivery of all applicable documents.

4.1.1 Section A - Solicitation/Contract Form

Complete Blocks 13, 15 and 16, then sign and date Block 17 of the Standard Form (SF) 33, Solicitation/Contract. Signature by the offeror on the SF 33 constitutes an offer, which the

Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

4.1.2 Section B - Supplies or Services and Costs/Prices

The offeror shall not propose prices for each CLIN in Section B of the model contract. All required rates shall be provided in TEP Matrix of Section J, Attachment 3.

4.1.3 Section I - Contract Clauses

The offeror shall comply with the clauses specified within Section I of the model contract.

Furthermore, any inference of a clause and or provision will be adhered to. All laws, regulations, and statutory authorities will also be applied within the model contract.

4.1.4 Section J – List of Documents, Exhibits, and Other Attachments

The offeror shall complete and provide the following attachments:

4.1.4.1 Attachment 3 – TEP Matrix

4.1.5 Section K - Representations, Certifications, and other Statements of Offerors

The offeror shall provide completed representations, certifications, acknowledgments, and statements. Offeror must have filled out an online provision 52.204-08 Annual Representations and Certifications (Dec 2012), Online Reps and Certs at http://www.sam.gov. Offer shall ensure certification as a small business under North American Industry Classification System (NAICS)

Code 541511.

4.2 Other Information Required

4.2.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to the proposal and who can obligate the company contractually. Also, identify those individuals authorized to negotiate with the Government.

Additionally, provide the name and telephone number of the CEO, Division President, and/or

Vice President.

4.2.2 Limitations on Subcontracting

IAW FAR 52.219-14 Limitations on Subcontracting, at least 50 percent of the cost of contract performance incurred for personnel shall be expended for employees of the concern. Submit documentation that demonstrates how the prime contractor will meet the requirements of the aforementioned FAR Clause.

4.2.3 Compensation Plan

The Offeror shall submit a total professional employee compensation plan meeting the requirements of FAR 52.222-46. The Offeror shall detail the base labor rate, fringe, all other burdens, and profit/fee contained in labor rates to facilitate comparisons IAW FAR 52.222-46.

5 SOLICITATION REQUIREMENTS, TERMS AND CONDITIONS

Offerors are required to meet all solicitation requirements, such as 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.

5.1 Exceptions to Solicitation Requirements

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

Table 2: Solicitation Exceptions

SOLICITATION

Document

Page/

Paragraph

Requirement/

Portion

Rationale

PWS, Model Contract, Section L, etc.

Applicable Page and Paragraph

Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

APPENDIX A: SAMPLE SCENARIO 1 - ONBOARDING AND TECHNOLOGY CAPABILITIES

SystemX is a Government Off-the-Shelf (GOTS) program providing Online Transaction Processing

(OLTP) and Online Analytical Processing (OLAP) capabilities for approximately 20,000 users at 100 geographic locations around the world on the Non-Classified Internet Protocol (NIPR) network using

Common Access Card (CAC) authentication. Originally developed on a Data General Mini-computer platform using Fortran more than 40 years ago, SystemX has evolved through several technology refreshes.

The front-end is now web-based utilizing the Spring framework and other open-source Java libraries in an

8-node IBM WebSphere high-availability cluster and the back-end runs an Oracle 11g database in a 3-node

Real Application Cluster (RAC) configuration in a 64-bit Red Hat Enterprise Linux 5 environment with a collection of the legacy C programs and third-party libraries running on a 4-node farm of 32-bit Microsoft

Windows 2008 R2 servers performing image processing and analysis. The third-party contractor responsible for the SystemX support has recently updated the legacy Commercial Off-the-Shelf (COTS) data analytics engine with a modernized on-premise implementation, however, the vendor also has a SaaS offering available.

The customer wants to relocate the hosting of SystemX into the Hill Enterprise Data Center (HEDC) while modernizing and consolidating some of the end-of-life infrastructure components, including the most recent versions of Defense Information Services Agency (DISA) Security Technical Implementation Guide

(STIG) compliant operating systems and databases (15 Terabytes), and re-platforming the application tier to Oracle WebLogic high-availability (HA) clusters on 64-bit Linux. SystemX has 30 inbound/outbound interfaces (14 file transfers, 5 database links, 3 real-time message queues, 7 web services with

Representational State Transfer (REST) Application Programming Interface (API) and Web Services

Description Language (WSDL)/Simple Object Access Protocol (SOAP), and 1 Extensible Markup

Language (XML) enterprise service bus (ESB) gateway with client Secure Socket Layer (SSL) authentication) with 10 external systems. The HEDC has the existing capacity for the primary site for

SystemX.

The re-platformed Oracle WebLogic tier will need to integrate with the Air Force (AF) identity management solution using either Security Assertion Markup Language (SAML), OAuth2 or OpenID, so existing users can perform CAC-based logins. The customer is also planning for an additional 10,000 users within the next year and needs to segment a portion of the database topology with multi-tenancy while sharing the other common data segment and interfaces. SystemX makes extensive use of Character Large

Object (CLOB), Binary Large Object (BLOB), and XML datatypes.

The Service Level Agreement (SLA) specifies 99% uptime. The customer also needs a Continuity of

Operations (COOP) solution in a Portable Operating Datacenter (POD) design to support SystemX with fail-over procedures and a Disaster Recovery (DR) plan. COOP will be used during quarterly product updates (1-week in duration) and must be available to all military users worldwide and all users at 3 depot locations during that window (roughly 10,000 users). An application transaction log is captured during maintenance windows to update the primary site at the end of each COOP cycle. Additionally, the customer is interested in moving all or part of the SystemX into a Hybrid Cloud model after the first year to address scalability and availability issues of an additional 50,000 users. The customer is also asking for a

4-month completion window.

APPENDIX B: SAMPLE SCENARIO 2 - PROGRAM AND CONFIGURATION MANAGEMENT

The Hill Enterprise Data Center (HEDC) has just received an unexpected 90-day corporate-level, high-priority effort in the modernization area. The contractor must accomplish this workload without adverse impacts to existing schedules and service levels in the areas of sustainment, modernization, onboarding and cybersecurity as defined in the project plans below.

The sustainment plan addresses the identification, testing, and deployment of vendor patches for vulnerability and compliance across the integration, staging, and production areas affecting 140 separate programs running in a virtualized shared common infrastructure environment along with the daily IT

Infrastructure Library (ITIL) activities supporting Service Transition and Service Operation.

The modernization plan addresses several parallel tasks including 1) an EMC Storage Area Network (SAN) expansion effort, 2) a major point-release of the VMware virtualization layer, 3) major upgrades in the

Microsoft and Red Hat operating system layers, 4) a major upgrades in the Microsoft and Oracle database layers, 5) a major upgrade in the Oracle Fusion Middleware layer, 6) a major upgrade in the McAfee

VirusScan layer across multiple Operating System (OS) targets, 7) a major upgrade in the Symantec backup software across multiple OS targets, 8) a network virtualization design and implementation, 9) storage and compute expansion of the Continuity of Operations (COOP) site with replication capabilities.

The onboarding plan addresses SystemX (from Scenario 1), along with 5 more candidates in the pipeline that require definition, scoping, estimation, planning, prioritization, and final negotiation.

The cybersecurity plan addresses the annual review of the HEDC product and configuration baseline, network ports and protocols, and Defense Information Systems Agency (DISA) Security Technical

Implementation Guide (STIG) analysis of the new products for the Risk Management Framework (RMF) package update and Authority to Operate (ATO) submission along with stakeholder reviews and approvals.

APPENDIX C: CROSS REFERENCE MATRIX

Cross Reference Matrix

Offeror’s Proposal

Paragraph Number(s) Section L Section M PWS Paragraph Vol