COMET_Section L.docx

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents

PROGRAM INFORMATION

Program Structure and Objectives The National Air and Space Intelligence Center (NASIC) has a requirement to purchase a full spectrum of technical support to maintain, enhance, and operate the current infrastructure and incorporate new capabilities required to meet future requirements. The NASIC Communications and Enterprise Information Technology Support Services (COMET) contractor personnel shall augment the NASIC workforce by providing support in the areas of IT Service Desk; touch maintenance; accounts management; Workspace Deployment and Disposition; Software Administration; Network Services; Infrastructure Engineering & Installation; Datacenter Operations; Windows/UNIX/Linux System Administration; Storage & Enterprise Backup Services; Video Teleconferencing Operations; Multimedia Hardware Technical Services; Software Vulnerability Testing; Systems Engineering; Information Technology Service Management; Configuration Management; Cybersecurity; Infrastructure as a Service (IaaS) & Cloud Operations; Platform as a Service (PaaS) Operations; Physical Access Control System & Intrusion Detection System; Database Management; Enterprise Application Server Software Administration. The contractor shall provide support as detailed in the PWS on a flexible 24x7 schedule to maintain availability of the supported systems for 24x7 operations.

The Government intends to issue Task Orders through the COMET Indefinite Delivery, Indefinite Quantity (IDIQ) contract. The Offeror’s[footnoteRef:2] proposal should be structured to reflect an overall understanding of the technical requirements and a Program Management (PM) strategy for managing the contracted work force. [2: Offeror = Prime and all Teaming Partners.]

GENERAL INSTRUCTIONS

Offerors will submit an electronic-only proposal; hard copies will not be accepted. The Offeror’s proposal must include all data and information requested by these Instructions to Offerors (ITO) and must be submitted in accordance with these instructions. The Offeror shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but, rather, shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities or experience and will base its evaluation on the information presented in the Offeror’s proposal.

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

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals.

Point of Contact The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the email in Section 3.8 below.

Debriefings The CO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or a post-award debriefing upon notification of exclusion from the competitive range. However, Offerors excluded from the competitive range are entitled to no more than one debriefing. The CO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. 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.505 or FAR 15.506 as applicable.

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

Electronic Reference Documents All referenced documents for this solicitation are available on the System for Award Management website at https://SAM.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

Communications Exchanges of source selection information between Government and Offerors will be controlled by the CO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line or utilizing the Department of Defense Secure Access File Exchange (SAFE) (https://safe.apps.mil/) to securely transmit encrypted files. Submit a request via email to the CO (see paragraph 3.8) who will initiate a file drop-off request.

PROPOSAL PREPARATION INSTRUCTIONS

Organization/Number of Copies/Page Limits The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). One digital copy will be submitted as described in paragraphs 3.9 and 3.10 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 1. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 1 Table 1 – Proposal Organization Table

Number

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 excess pages will be redacted prior to sending to the evaluation team. NOTE: Each page shall be counted except the following: cover pages, table of contents, tabs, glossaries, consent and authorization letters, and key personnel résumés. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

Page Size and Format

a) A page is defined as each face of a sheet of paper containing information. Page shall be formatted to fit a piece of paper no larger than 8.5 x 11 inches and may not include foldouts. Pages shall be single spaced typed. Except for the reproduced sections of the solicitation document, the font shall be Calibri and the text size shall be no less than 11 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.

b) 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 and legible. For tables, charts, graphs and figures, the text shall be no smaller than 8 point.

Classified Information All components of the RFP and the Proposals are unclassified.

Cross-Referencing To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

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

Electronic Offers Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The Offeror shall submit volumes I through V in electronic format via DoD SAFE. Identify “Controlled Unclassified Information” and “Source Selection Information—See FAR 2.101 and FAR 3.104” on all proposal pages. The electronic copies of the proposal shall be submitted using the following instructions:

a) Electronic files shall be submitted via DoD SAFE. In order to submit via DoD SAFE, a drop-off request is required. In order to receive a DoD SAFE drop-off, email the contracting officer listed in paragraph 3.8 below no more than 14 days and no less than 3 days prior to proposal submittal date.

b) Submit documents using Microsoft Office 2016 or greater:

a. Word documents – Set "Save as type" to "Word Document (*.docx)"

b. Excel spreadsheets – Set "Save as type" to "Excel Workbook (*.xlsx)."

c. PowerPoint presentations – Set "Save as type" to "PowerPoint Presentation (*.pptx)."

c) Submit any Microsoft Project files in Microsoft Project 2016 or greater. There are no special “save” functions required for later versions of Project.

d) Submit PDF documents using only Adobe Acrobat XI (11) or later. Do NOT submit any documents in PDF format that are copied as "images." When creating PDF files always create to enable textual search and copy functions.

Distribution Proposals shall be addressed to both COs below and submitted via DoD SAFE (safe.apps.mil) to:

PROPOSAL ORGANIZATION

Volume I Executive Summary In the Executive Summary volume, the Offeror shall provide the following information:

Narrative Summary The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding price. 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.

Table of Contents Include a master table of contents of the entire proposal.

Volume II - Technical Volume

General The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. Excluding Subfactor One (pass/fail), each Measure of Merit is eligible to receive multiple strengths, which allow the Offeror to receive a subfactor technical rating higher than Green/Acceptable. The Offeror must specifically identify what they are proposing as strengths for it to be evaluated.

Experience defined in this solicitation as an Offerors’ participation in work that is similar in scope and technical complexity as defined in the PWS. For all listed experience the Offeror shall include relevant and recent contract performance information including a description of the work performed by the Offeror, contract number, and the period in which the work was performed. All cited work must have occurred within the last three years for at least six months of performance.

Format and Specific Content All specific Technical subfactors set forth in Section M and instructions set forth in Section L must be addressed. Describe your proposed approach to meeting the requirements of each Technical subfactor.

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

a) Table of Contents

b) List of Tables and Drawings

c) Glossary

d) Entry Gate

e) Subfactor One

f) Subfactor Two

g) Subfactor Three

h) Subfactor Four

i) Subfactor Five

j) Subfactor Six

Entry Gate: Compliance The Offeror must provide a copy of their DCSA Verification inquiry from the National Industrial Security database (NISS) showing that they possess a Top Secret facility clearance (TS FCL) at the time of proposal submission. To be eligible as a Joint Venture Offeror, either (1) the Joint Venture Offeror must possess a TS FCL at the time of proposal submission or (2) each of the entities that make up the Joint Venture must individually possess the TS FCL at the time of proposal submission. The copy of the DCSA Verification Inquiry shall be placed as the first page of the Technical Volume, d) Entry Gate.

Factor One: Technical Subfactor One: Program Management The Offeror shall present its approach to manage and execute the COMET requirements IAW the Government Performance Work Statement. The Offeror shall describe/provide the following:

IDIQ Management (Task Order PWS Management) Offeror’s ability to manage the COMET IDIQ contract within the Wright-Patterson Air Force Base local area including local management presence. Further, identify how offeror will manage personnel across various task orders and shifts to ensure seamless, uninterrupted support to the customer.

The Offeror shall also address the following elements:

a. An operations and maintenance plan for execution of daily operations including resource allocation within each functional area and task assignments

b. Provide a skills-to-technology matrix showing the labor category/skill proposed with the industry-recognized certifications possessed and descriptions mapped to the PWS requirements. See Attachment 6 for format. The skills-to-technology matrix will not be counted as part of the 80 page limit of Volume II.

Management Plan (Personnel) The Offeror shall provide one management plan that will that will discuss their approach to applying personnel management to all of the five task orders. The management plan will address all of the following elements:

a. Staffing Maintenance, Recruitment, and Backup Maintenance Plans: Specifically how the Offeror plans to attract, recruit, hire, train, and retain qualified management and technical personnel to ensure the Offeror’s team possesses or can readily obtain personnel with the appropriate levels of education, professional certifications, experience, and expertise to accomplish COMET tasks (these can be found in each task order’s PWS). Identify its approach to ensure continuation of services during personnel absences due to sickness, leave, voluntary or involuntary termination from employment such that would reduce the impact to the Government. Describe its process for maintaining currency of any required certifications or specialized training.

b. Staffing Plan (Résumés for key personnel (including PM and team leads identified in section 11 of all 5 task order Performance Work Statements), FTEs per functional area of each PWS, organizational chart delineating oversight, information flow, and lines of communication for accompanying contract workload)

c. Personnel Training/Cross Training plan (including manufacturer/vendor/OEM training for current and emerging technologies in each functional area the contractor supports (minimum 2 courses per year)

Security The Offeror shall describe its procedures for obtaining appropriate company and personnel security clearances. It shall also identify its process for ensuring personnel understand and comply with applicable security requirements for a TS//SCI contract.

4.2.4.1.4 Transition Plan

The Offeror shall describe their approach for accomplishing a transition from the incumbent as described in section 11 of the PWS for each Task Order. The proposal shall clearly detail how the Offeror will assume responsibility from the incumbent for the support required in each functional area of PWS para 3. This transition plan must include a schedule of actions to be taken to ensure that there is no gap or reduction in service when the incumbent’s contract expires.

Subfactor Two: End User Workspace Tasks End User Workspace Tasks The Offeror’s proposal must provide a detailed description of your approach to providing customer service support for each of the tasks (a. and b.) below. In addition, provide a description of your experience with regard to one of the following tasks:

a. Service Desk (Communications Focal Point)/Touch Maintenance/Account Management: Managing and operating a 24x7 Service Desk, resolving and escalating incidents, interacting directly with customers to resolve incidents and problems with offered services as described in PWS sections 3.1, 3.2, and 3.3 for Task Order 1.

b. Software Administration/Installation/License Management: Installing, troubleshooting, and uninstalling software; building, installing, and maintaining software packages for automated deployment onto client systems; and managing software license usage as described in PWS section 3.5 for Task Order 1.

Subfactor Three: Datacenter, Network, and Platform Hosting Tasks

Datacenter, Network, and Platform Hosting Tasks The Offeror’s proposal must provide a detailed description of your approach to providing support for datacenter, network, and platform hosting tasks for each of the tasks (a.-b.) below. In addition, provide a description of your experience with regard to one of the following tasks:

a. Infrastructure Engineering and Installation: Designing an enterprise-size, premises fiber-optic network infrastructure and leading a team of five or more fiber technicians to install and maintain an enterprise size premises fiber-optic network infrastructure in accordance with PWS sections 3.8 and 3.9 for Task Order 2.

b. Datacenter Operations: Developing, designing, innovating, and implementing complex computing solutions while contributing to development of next-generation cluster-processing systems and components as well as maintaining the physical and environmental infrastructure of the Air Force’s largest SCI Data Center as described in PWS sections 3.10 for Task Order 2.

Database Management and Enterprise Application Server Software Administration Tasks The Offeror’s proposal must provide a detailed description of your approach to performing database management and enterprise application server software management. In addition, provide a description of your experience with regard to the following task:

a. Database and Application Management: Designing, installing, administering, and security hardening various types of Database and Application Server systems, such as Oracle WebLogic, Oracle HTTP, Docker, Apache, NGINX, MariaDB, MongoDB, etc., across multiple on-premises and cloud based environments in support of custom and commercial applications in a 24x7 support role as described in PWS sections 3.28 and 3.29 for Task Order 2.

Subfactor Four: IT Service Design and Cybersecurity Tasks

Support for IT Service Design and Cybersecurity Tasks The Offeror’s proposal must provide detailed information describing your approach to delivering cybersecurity, engineering, IT governance, and information management services as defined in each of the tasks (a.-d.) below. In addition, provide a description of your experience with regard to one of the following tasks:

a. Software Vulnerability Testing: Conducting vulnerability scans and providing vulnerability remediation and documentation for compiled software, application source code, and containerized software as described in PWS section 3.1 for Task Order 3.

b. Network Auditing: Operating and maintaining a comprehensive audit log collection and analysis program, operating and maintaining a Security Information Event Management (SIEM) system including relevant dashboards and reports, and defining relevant security events and recommended actions based on audit log data as described in PWS section 3.5 for Task Order 3.

c. Cybersecurity Defense System Support: Support the engineering, integration, operations, troubleshooting, maintenance, and upgrades of existing and new network and endpoint-based cybersecurity capabilities as described in PWS sections 3.6 and 3.7 for Task Order 3.

d. Information Technology Service Management: Integrating automation and orchestration tools within an IT Service Management system, operating and maintaining an IT Service Management system (I.e. Microsoft System Center or ServiceNow), and other tasks as described in PWS section 3.12 for Task Order 3.

Subfactor Five: Cloud Services Tasks

Cloud Services Tasks The Offeror’s proposal must provide detailed information describing your approach to delivering Engineering and Cloud Services support to include Systems Engineering, Infrastructure as a Service, Platform as a Service, and Cloud Support for NASIC’s enterprise as defined in each of the tasks (a-b) below. In addition, provide a description of your experience with regard to one of the following tasks:

a. Infrastructure as a Service (IaaS) and Cloud Operations: operating and maintaining an on-premises Infrastructure as a Service Offering meeting local service levels according to NIST SP 800-145; provisioning, operating, and maintaining systems and environments in Public and Private Clouds to include Amazon Web Services (AWS), Azure, Google Cloud and other cloud providers approved for Government use in accordance with PWS section 3.1 for Task Order 4.

b. Platform as a Service (PaaS) Operations: implementing, operating, and maintaining a Platform as a Service Offering meeting local service levels according to NIST SP 800-145 both on-premises and off-premises, operating and maintaining a Continuous Integration and Continuous Delivery application pipeline enabling a continuous approval to operate for applications in accordance with PWS sections 3.2 and 3.3 for Task Order 4.

Subfactor Six: Facility Security System Tasks

Facility Security System Tasks The Offeror’s proposal must provide detailed information describing your approach to maintaining the physical access control system (ACS), intrusion detection system (IDS), and Closed Circuit Television (CCTV) system for Collateral and Sensitive Compartmented Information (SCI) facilities. In addition, provide a description of your experience with regard to the following task:

a. Physical Access Control/Intrusion Detection: Maintain, configure & troubleshoot DAQ Starwatch ACS, a separate IDS and CCTV, and various electronics to include a repair capability. Support migration of current ACS and IDS to Lenel OnGuard. Maintain system documentation, configuration changes, and network layouts in accordance with PWS section 3.1 for Task Order 5. Proposal shall cite one example where the Offeror implemented and maintained the physical ACS, IDS, and CCTV systems for an SCI facility.

Volume III - Past Performance

Past Performance Information (PPI) Tool Each Offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 1 that contains instructions for use of the PPI Tool. This information is required of the Offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 25% or more of the proposed effort based on the total proposed price or perform aspects of the effort the Offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance.

Consent/Authorization Letters Along with the information required in this section, the Offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. 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 Offerors performance. See Attachments 4 and 5 for sample consent and client authorization letters. These letters will not be included in the overall page count.

Recent and Relevant Contracts The Offeror shall submit information in accordance with Attachment 1: Past Performance Information on a maximum of three (3) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. References to multiple task orders under a single IDIQ shall be considered one (1) contract for the purpose of this evaluation. The Offeror (which includes the Prime and all Teaming Partners), shall also submit past performance information for any significant or critical subcontractors/teaming partners. A significant subcontractor/teaming partner is defined as one completing 25% or more of the proposed effort based on the total proposed price, whereas critical subcontractors/teaming partners are those performing aspects of the effort that the Offeror considers critical to overall success, regardless of percentage of work. Past performance for no more than three relevant contracts can be submitted for the Prime contractor and no more than a total of two for significant and critical subcontractors/partners. Each contract shall have active work/services that was/were performed during the last three (3) years from the final solicitation release date. This includes contracts that were awarded prior to this period, but still had active performance during the last three years or is ongoing with at least six (6) months of performance elapsed. If the effort began more than 3 years before the date of issuance of this solicitation, only the effort which occurred during the past 3 years will be considered recent. NOTE: Underlying task/delivery order periods of performance will determine the recency of an IDIQ contract or BPA (in other words, there must have been active performance that meets the recency definition). Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M Evaluation Factors, section 2.3 Past Performance Factor.

Specific Content Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. 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. Merely having problems does not automatically equate to an unsatisfactory rating, since the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered more favorably than without evidence of problem resolution. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors used to evaluate the proposal. Fill in Attachment 8 – Past Performance Teaming Matrix to show who will be doing the work in each functional area of each task order. The Offeror’s (Prime and teaming partners as a whole) Past Performance information should demonstrate experience in each of these functional areas.

The Offeror shall send the questionnaires for relevant projects that are in progress or completed in the past three (3) years to the individuals who will provide the reference. For Government contracts, send to the Contracting Officer or Contracting Officer’s Representative. For commercial references, send to personnel with duties similar to those for Government contracts. It is the responsibility of the Offeror to follow-up and encourage references to submit the questionnaire. The completed questionnaire shall be submitted via e-mail directly to the contracting officer at email shown in para 3.8 above from the person providing the reference. See Attachment 3 for questionnaire/assessment and Attachment 2 for additional instructions.

Organizational Structure Change History Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent 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. A pamphlet or other commercial document describing such reorganizations may suffice. 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.

Volume IV - Price General Instructions

Price Reasonableness and Balance This section is to assist you in submitting data other than certified pricing data that is required to evaluate the reasonableness and balance of your proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an Offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness and balance. The burden of proof for credibility of proposed prices rests with the Offeror.

Price Data Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your 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.

Pricing Data Requirements The CO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the CO will review this determination and if, in the CO’s opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit cost or pricing data.

Currency & Rounding All dollar amounts provided in response to these instructions shall be stated in U.S. currency in current fiscal year dollars for the first year and then-year dollars for future years. CLIN totals should be rounded to the nearest penny and the total CLIN value should be divisible by 12. Labor rates should be rounded to the nearest penny.

Volume Organization The Price volume shall consist of the following sections:

SECTION 1 - Table of Contents; summary descriptions of estimating, purchasing, and accounting systems; changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure Statement.

SECTION 2 - Complete and submit the Total Evaluated Price Workbook (Attachment 7) indicating labor categories, quantities of each and fully burdened labor rates. Also include estimating methodology and any other supporting data deemed necessary to support reasonableness.

SECTION 3 - List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Price volume, if any. Provide complete rationale for any exceptions.

Estimating System Provide a summary description of your standard estimating system or methods.

Purchasing Offeror shall state if they have a purchasing process in place to support Equipment & Material requirements.

Accounting System Offeror shall state if they have an approved accounting system, and if so, provide a copy of the audit report.

Total Evaluated Price Workbook

a) After opening Attachment 7 (Total Evaluated Price Workbook), go to 'Contractor Labor Rates Summary' tab and insert labor categories (examples highlighted in yellow) and the fully burdened hourly labor rates (Prime and Sub) for each functional area. All labor categories required for each of the five task orders should be included here.

b) Go to the 'Transition Price' tab and insert the fully burdened hourly labor rate (highlighted orange) for each of the functional SME's that will be utilized during the first 30 day transition time period (IAW Task Order 1 PWS section 11). Fully burdened hourly labor rates shall coincide with 'Contractor Labor Rates Summary' tab. Transition pricing will need to be provided on all 5 task orders.

c) Go to each of the five Proposal Labor Price tabs and insert Contractor Labor Category, FTE quantity (# of employees) needed for that labor category within each functional area and the fully burdened hourly labor rates. Contractor Labor Category should align with the 'Contractor Labor Rates Summary' tab previously filled out. Also in the Proposal Labor Price tabs for each TO, provide the fully burdened hourly labor rates for years two through five with the assumption that the number of contractors and functional areas will remain the same for each year for the five task orders.

NOTE: Equipment & Material, Travel, and Emergency Support are Government provided CLINs on the contract having not to exceed (NTE) dollar amounts, which are automatically calculated into your TEP.

All data provided in the Proposal Labor Price tabs will roll up into tab one (Summary TEP) to show your Total Evaluated Price. The labor category and fully burdened labor rates for each year will be added to Section J of the IDIQ with the award of the contract.

Volume V Contract Documentation

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 complete in its entirety the “Offeror” portion of the Standard Form (SF 33). An official having the authority to contractually bind your company shall sign the SF 33 IAW FAR 4.102. The SF 33 must bear an original signature of an authorized representative for the Offeror. Complete all required representations and certifications or indicate if information is contained in https//sam.gov.

Exceptions to Solicitation Requirements 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. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 2.

Table 2 - Solicitation Exceptions

Solicitation Document Page/ Paragraph Requirement/ Portion Rationale

Page and Paragraph Numbers

Other Information Required

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

Government Offices Provide the mailing address, email address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

GFP and/or Base Support Requirements The Government plans to provide the items listed in the Task Order PWSs section 5.3.

Proposal Acceptance Period The proposal acceptance period is specified in Section A of the model contract/solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

List of Attachments Section L attachments listed below are provided as separate files.

Attachment 1: Past Performance Information Tool Attachment 2: Past Performance Cover Letter Attachment 3: Past Performance Questionnaire Attachment 4: Past Performance Client Authorization Letter Attachment 5: Past Performance Consent Letter Attachment 6: Skills-to-Technology Matrix Attachment 7: Total Evaluated Price Workbook Attachment 8: Past Performance Teaming Matrix

Section L