Attachment 1 - Addendum to FAR 52.212-1.pdf

Attachment 1 – Instructions to Offerors

ADDENDUM TO FAR 52.212-1

INSTRUCTIONS TO OFFERORS

1.0 Program Structure and Objective

1.1.1. The Government plans to award a single contract for MISSILE TECHNICAL ORDER SUPPORT

(MTOS) for the Air Launched Cruise Missile (ALCM). The MTOS will primarily include the following:

creation of technical data; digitization of existing technical data; preparation of TO updates, Time Compliance

Technical Orders (TCTO), and maintenance manual supplements; Identification of Technical Publications

Sheets (ITPS); and storage and maintenance of manuals, Direct Image Reproducible (DIR), negatives, and digital data.

1.1.2. Award will be made on the basis of “best value” utilizing Price/Performance Tradeoff Lite (PPT Lite)

Source Selection Procedures. Award will be made to the contractor that provided the “best value” to the

Government over the entire period of performance.

1.2. Budget/Funding Information:

Funding will be obligated for the Firm-Fixed-Price (FFP) Contract Line Item Number (CLIN) on each task order throughout the life of the contract.

2.0 General Instructions

2.1.1. This section of the Instructions to Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror’s proposal must include all data and information requested by the ITO and must be submitted in accordance with these instructions. Any

Offeror who submits an incomplete package may be considered ineligible for award. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS) and appendices. Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation.

2.1.2. 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 and experience, and will base its evaluation on the information presented in the offeror’s proposal.

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

2.1.4. The proposal acceptance period is specified on the front page 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 until this date.

2.1.5. In accordance with Federal Acquisition Regulation (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.

2.2. General Information

2.2.1. 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 address located in

Section A of the model contract/solicitation.

2.2.2. 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 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 for each proposal. The CO will notify unsuccessful offerors in accordance with FAR 15.503. 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 15.506, as applicable.

2.2.3. Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the 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. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions. This reservation includes matters of additional or substitute pages of the initial proposal.

2.2.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the System for Award Management repository website at https://www.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.

2.2.5. Amendments to Solicitation

If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment and provide confirmation upon submission of the offeror’s proposal. Any unacknowledged amendments in the offeror’s proposal are subject to solicitation provision FAR 52.212-1(f).

2.2.6. Submission, Modification, Revision, and Withdrawal of Proposals Proposals and modifications to proposals shall be submitted via email, showing the time and date specified for receipt, the solicitation number, and the name and address of the offeror.

2.3 Organization/Page Limits/Formats

2.3.1. The Offeror’s proposal must show solicitation number, name, address, and telephone and facsimile numbers of the offeror and electronic e-mail address if available.

2.3.2. A Team List of the offeror’s primary Point of Contacts shall be included in proposal submission.

2.3.3. Page Limitations

Proposal shall be no more than 60 pages, excluding cover pages.

2.3.4. Pricing Information

All pricing information shall be addressed ONLY in the MSD Pricing Matrix (ITO Attachment 1.3) and Section

B CLIN of Model Contract.

2.3.5. Cross Referencing

A formal technical proposal is not required. However, the proposal shall contain a technical section. The technical section shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other sections of the proposal. Information required for the technical proposal evaluation, which is not found in the technical section, will be assumed to have been omitted from the proposal, and will not be https://www.sam.gov/ considered in the technical evaluation. Cross-referencing within a proposal volume is permitted when its use would conserve space without impairing clarity.

The proposal shall also contain a price section and a past performance section. The Past Performance and Price evaluation will utilize information from each’s respective section for the evaluation, but may also utilize information from other sections as well.

2.3.6. Indexing

Proposal shall contain a detailed table of contents to delineate the sections.

2.3.7. Include an indexed list of Tables and Figures.

2.3.8. Glossary of Abbreviations and Acronyms

Each proposal shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitation.

2.3.9. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc.

2.4. Electronic Offers

An electronic copy of the proposal and any revisions shall be submitted via email to all of the following email addresses:

- Joshua Palmer at joshua.palmer.10@us.af.mil

- Joshua Irwin at joshua.irwin.4@us.af.mil

- Devin McLelland at devin.mclelland@us.af.mil

- Trista Katzenberger at trista.katzenberger.2@us.af.mil

3.0. Factor 1 – Technical

3.1. General

In the Technical Section, address your proposed approach to meeting the minimum performance of capability requirements of each technical subfactor. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Addendum to FAR 52.212-2, 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. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

3.2. Format and Specific Content

3.2.1. Technical Section Organization

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

(1) Table of Contents

(2) List of Table and Drawings (if applicable)

(3) Glossary

(4) Subfactor One - Demonstration of Graphics Creation and File Type Manipulation Capabilities

(5) Subfactor Two – Security/Safety

(6) Subfactor Three – Management Plan

(7) Subfactor Four – Technical Approach

(8) Subfactor Five – Resource/Personnel Management mailto:joshua.palmer.10@us.af.mil mailto:joshua.irwin.4@us.af.mil mailto:devin.mclelland@us.af.mil mailto:trista.katzenberger.2@us.af.mil

3.2.2. Subfactor One – Demonstration of Graphics Creation and File Type Manipulation

Capabilities The Government has included with this solicitation four .png files (ITO Attachments 1.2.1 -

1.2.4) consisting of images of varying quality that the Government has previously required to be replaced in digital technical orders with a clean and legible .cgm file version.

Offerors shall utilize software, personnel skillsets, or other tools to produce a clean digital image using

Adobe Acrobat, with any text boxes or lines of text being “searchable” within the finished tech order.

Completed changes shall be returned to the Government as both a .cgm file and a .pdf file as a demonstration of the Offeror’s capabilities.

For demonstration purposes, Offerors shall submit the following as deliverables to be evaluated:

1) Clean, Legible .CGM and .PDF Files

2) Description of Methods Used

3) All Software or Tools Used

4) Hours/Manpower Utilized

5) Affirmation of Offeror’s capability to do the same under CLIN(s) X002 - X022 throughout the contract award period.

3.2.3. Subfactor Two – Security/Safety

The Offeror shall provide a Security Plan for the MTOS program, to protect and safeguard technical orders and data throughout the administration of the contract. At a minimum, the Security Plan shall provide the following essential elements:

1) The Offeror’s approach to safeguard technical data, source data, and meet security requirements as outlined in the PWS. This effort supports classified programs, systems, and material. Individuals performing work on this task order must be United States citizens and comply with applicable program security requirements at the time of task order award and replacement approval (PWS

Section 5.2).

2) A detailed discussion of the Offeror’s physical security plan, which will ensure that Government

Furnished Information (GFI), for which the Offeror is responsible, will be safeguarded and secured.

Include the type of key/combination control, end-of-day security check procedures, and a discussion of how employee conformity to security requirements will be affected. Discuss measures taken to provide key/combination security in the event that employees are terminated or reassigned, and include procedures for ensuring that password protection is in place (PWS Section 3.1).

3.2.4. Subfactor Three – Management Plan

The Offeror shall provide a Management Plan for the MTOS program. At a minimum, the Management Plan shall provide the following essential elements:

1) Transition Plan - The Offeror shall demonstrate a phase-in and phase-out transition plan for the phasing-in and out of contractor performance. The period between award date and full performance start date constitutes the contract phase-in period. The Offeror shall provide a successful transition plan to recruit, hire, and retain qualified applicants to meet PWS requirements. The phase-out contractor performance shall also be outlined in transition plan to demonstrate the Offeror approach

(PWS Section 5.12).

2) Address company policy regarding quality maintenance practices and quality workmanship in the

Quality Control Plan (QCP). Include specific procedures for implementing company policy requiring quality maintenance practices and quality workmanship and ensure compliance with the

PWS (PWS Section 4.18).

3) Approach to providing offsite hosting/storage services to facilitate technical information exchange meetings and historical file access and plan to meet schedule for all government deliverables (PWS

Sections 1.1f and 1.1.7).

4) Approach to meet program requirements at primary operating base as well as TDY locations, to include an effective communications process with the Government that ensures successful accomplishment of all task order requirements. (PWS Section 4.13)

5) A detailed plan of how each type of record will be created, updated, and maintained. Describe in detail the methodology to be implemented for data collection in support of contract performance elements within the PWS including quality control planning and data (PWS Sections 1.1.6 and all subparagraphs).

6) Describe training and procedures used to ensure that each employee performing work under the contract is aware of required COMSEC, security policy, procedures, & requirements, and

Foreign Disclosure restrictions (PWS Sections 5.2.7.2, 5.2.7.5, and 5.2.7.6).

3.2.5. Subfactor Four – Technical Approach

The Offeror shall provide its approach to meeting the technical requirements of the PWS. At a minimum, the Technical Approach shall consider the following essential components:

1) The Offeror’s approach to develop Electronic Technical Orders (eTO) (PWS Section 4.11).

2) The Offeror’s plans to meet required time constraints contained within the PWS for Emergency and

Urgent Technical Order deliveries (PWS Sections 1.1.3, 4.16.1, and 4.16.2).

3) The Offeror’s approach showing how Computer Software/Computer Software Documentation

(CS/CSD) will be used to facilitate Technical Order sustainment. Demonstrate ability to Hyperlink

IPDF technical data capabilities, the ability to create style sheets for printing, capability to produce eTOs IAW PWS. Demonstrate accuracy in converting technical data in SGML format (PWS

Sections 1.1.1 and 1.1.4i).

3.2.6. Subfactor Five – Resource/Personnel Management

The Offeror shall provide an approach for resource/personnel management for the MTOS program. At a minimum, the approach shall provide the following essential elements:

1) Manning: The Offeror’s process for recruiting, hiring, training, and retention of a qualified, certified and capable workforce that can accomplish the entire scope of the effort, and handle surges/variables in workload requirements IAW PWS Sections 1.1.3., 2.0., 4.3.3., 4.16.2., and

4.16.3.

2) Organizational Structure: The Offeror’s organizational approach and management structure, to include an organizational chart.

4.0. Factor 2 – Past Performance

4.1. General

4.1.1. Each offeror shall submit a past performance section with its proposal containing past performance information in accordance with the format contained in Attachment 1.1.1 of the ITO. The Past Performance section shall include a team list, which includes the prime contractor, all significant subcontractors, teaming partners, and/or joint venture partners proposed to perform the work outlined in the solicitation. The offeror shall describe the portion of effort each team member is proposed to perform in relation to the Factor 1

Technical subfactors, Factor 3 Price, and Scope, Magnitude and Complexity. The Government Past Performance

Evaluation Team (PPET) evaluates each member of the offeror’s team for relevancy and performance, based on their proposed portion of effort. Therefore, it is important for the offeror to provide a detailed portion of effort description, in order for the PPET to conduct an accurate assessment. Offerors shall also provide approximate percentages for portion of effort for each team member. For the Past Performance evaluation, the Government will use data provided by the offeror in the Past Performance volume, as well as data obtained from other sources.

4.1.2. As soon as practicable, offerors shall complete Section 1 of the attached Past Performance Questionnaire

(ITO Attachment 1.1.2) and e-mail it and the Performance Questionnaire Letter (ITO Attachment 1.1.3) to all points of contacts (POCs) the offeror has listed in the Past Performance Information Form (ITO Attachment

1.1.1). The POCs will complete the questionnaires and forward them directly to the Past Performance

Evaluation Team (PPET). (Attn: PCO Name). Email address for questionnaires is name@us.af.mil.

RESPONDENTS TO THE QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION

SHEETS BACK TO THE OFFEROR. Offerors shall not follow-up with respondents to ensure they have completed the questionnaires. The PPET will conduct such follow-up with any POC as necessary.

4.2. Relevant Contracts

4.2.1. The offeror shall provide Past Performance Information (PPI) on current or previous contracts (or efforts). The PPI shall be completed in accordance with Addendum to FAR 52.212-1, ITO Attachment 1.1.1, Past Performance Information Form (identified in this document as “PPIF”). The offeror shall submit PPIFs for contracts which include all or some performance within the past three years, as defined in Addendum to FAR

52.212-2, para 2.3.2.1 Recency Assessment. Request each offeror submit up to three (3) PPIFs. NOTE: The requested number of PPIFs are preferences and not requirements. Offerors may submit more than the preferred number, if the offeror believes the extra contracts are needed to fully describe their relevancy. Offerors who submit less than the preferred number of PPIFs are not automatically assigned a “Neutral Confidence” rating.

Fewer numbers may be acceptable, if the Government determines there is sufficient information to determine a confidence rating. Request each PPIF not exceed a target of 7 pages, although more or less may be submitted, if necessary and relevant to the MTOS program.

4.2.2. PPI Relevant Contract Narrative

For each PPIF, the offeror shall provide a narrative explaining what aspects of the contract is deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate. Specifically, the narrative should focus on similarities to the Factor 1 Technical subfactors, Factor 3 Price, and Scope, Magnitude, and

Complexity, as defined in Addendum to FAR 52.212-2, paragraph 2.3.2.2, and should be tailored to the proposed portion of effort. Categorize the relevant information into the specific technical subfactors and price assessment used to evaluate the proposal. The narrative 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 a Limited or No Confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror shall 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 a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. The offeror is requested to limit the narrative to a maximum of 5 pages. However, the offeror may exceed the requested page limit, if determined necessary to fully describe relevancy.

5.0. Factor 3 – Price

5.1. In the price section, the Offeror shall provide the following information in addition to the pricing in

Supplies or Services and Prices/Cost Section (Part B) of the solicitation. These instructions are to assist you in submitting information required to evaluate the reasonableness of your proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

5.2. General Instructions

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position. All information relating to the proposed price including all required supporting documentation must be included in the section of the proposal designated as the Price Section.

Under no circumstances shall this information and documentation be included elsewhere in the proposal.

5.2.1. Price Reasonableness

The Government will evaluate proposals for reasonableness. Normally, price reasonableness is established through adequate price competition, but may also be determined through other price analysis techniques (see

Section 5.2.2 below). The burden of proof for credibility of proposed costs/prices rests with the offeror. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.).

5.2.2. Cost or Pricing Information Requirements

FAR 12.209 gives the requirement to establish price reasonableness in accordance with 13.106-3 (Simplified

Acquisition Procedures), 14.408-2 (Sealed Bidding), or 15.4 (Contract Pricing by Negotiation), as applicable.

FAR part 15 applies. In accordance with FAR 15.403-3-1(b), prices based on adequate price competition do not require submission of cost or pricing data. In accordance with FAR 15.403-3(a), however, information other than cost or pricing data may be required to support price reasonableness. FAR 15.403-3(a)(1) provides for obtaining information other than cost or pricing data if needed to determine price reasonableness. Therefore, the FAR does not preclude the requirement for obtaining other than cost or pricing data under certain circumstances and the Government reserves the right to obtain data as appropriate. Should the CO determine proposed prices to appear unreasonable or the possibility that an Offeror does not fully understand the requirement, the Offerors may be required to support price reasonableness via other than cost or pricing data. 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.

5.2.2 Balance

The Government will evaluate proposals for balance. The offeror is cautioned against submitting an offer which exhibits unbalanced pricing. Unbalanced pricing may increase performance risk and could result in payment of unreasonable or unrealistic prices. For this acquisition, balanced pricing is determined with respect to year-to-year price variances for separately priced CLINs. Offerors shall provide rationale for any proposed CLIN price increase greater than 5% from one year to another, or any proposed CLIN price decrease from one year to another. Unexplained price variances from year-to-year could suggest unbalanced pricing. It is in the Offeror’s best interest to provide explanations or supporting rationale for any significant annual CLIN price variances.

To assist in the determination of balanced pricing, Offerors shall complete the attached Pricing Matrix (ITO

Attachment 1.3). Completion of the Pricing Matrix allows efficient comparison of proposed pricing with the

PWS requirements.

5.2.3. Price Realism

The Government will evaluate proposals for price realism to determine whether proposed prices are based on an adequate understanding of contract requirements. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc).

5.2.4. Rounding

All dollar amounts shall be rounded to the nearest penny.

5.3. PRICING SUPPORT INFORMATION

5.3.1. Estimating System

Provide a summary description of your standard estimating system or methods. Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether you have

Government approval of your system and if so, provide evidence of such approval.

5.3.2. Annual Price Changes

Proposed price increases greater than 5% per period shall be verified and addressed for reasonableness in this section.

5.3.3. Government Furnished Property/Government Furnished Equipment (GFP/GFE)

The Government does not anticipate providing GFP/GFE or base support. However, all costs associated with maintaining and safeguarding Government Furnished Information should be clearly identified within the Price Section.

5.3.4. Other Documentation

Other documentation considered by Offerors to be essential for support of proposed prices shall be presented in this section. Pursuant to paragraph 5.2.3. above, Offerors are requested to address any proposed prices which reflect a business decision to offer prices at or below cost.

5.3.5 Submission of Price/Cost Matrix

Submit an electronically encoded price/cost matrix Attachment 1.3 in support of the proposed Total Evaluated

Price (TEP). Any price/cost matrix submitted must be consistent with your approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of your proposal. Price models submitted must utilize the Price Matrix (ITO Attachment 1.3).

6.0. CONTRACT DOCUMENTATION

6.1.1. Model Contract/Representations and Certifications

The purpose of this section 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.

6.1.2. Solicitation/Contract Form (Section A)

Completion of blocks 12, 17 and signature and date for blocks 30a, 30b and 30c of the SF1449. Signature by the offeror on the SF1449 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.

6.1.3. Supplies or Services and Costs/Prices (Section B)

Completed pricing information in Section B of this model contract.

6.1.4. Contract Clauses (Section I)

The Offeror shall provide required information to complete clauses as required.

6.1.5. Representations, Certifications, and other Statements of Offerors (Section K) The Offeror has completed the annual representations and certification electronically via the SAM website at http://sam.gov. After reviewing the SAM database information, the Offeror verifies by submission of this offer that the representation and certifications currently posted electronically at FAR 52.212-3, Offeror

Representations and Certifications—Commercial Items are correct.

6.2 EXCEPTIONS TO SOLICTATION 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.

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. 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, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 6.2. Offerors are cautioned the Government could determine any identified exceptions to be unacceptable, which would make the proposal ineligible for award.

Table 6.2 - Solicitation Exceptions

Solicitation

Document

Page/

Paragraph

Requirement/

Portion Rationale

SOO, PWS, SPEC,

Model Contract, ITO, 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

6.3. OTHER INFORMATION REQUIRED

6.3.1 Ombudsman

An Ombudsman has been appointed to hear concerns from offerors or potential offerors during the proposal development phase of this acquisition. The Ombudsman for this acquisition is OC- ALC/PKC. This does not diminish the authority of the program director or CO, but communicates offeror concerns, issues, disagreements and recommendations to the appropriate Government personnel. When requested, the Ombudsman shall maintain strict confidentiality as to the source of the concern. The Ombudsman does not participate in the evaluation of proposals or in the source selection process; interested parties are invited to call OC-ALC/PKC at

405-736-3273.

6.3.2. Authorized Offeror Personnel

Provide the name, title, 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.

6.3.3. Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract

Administration Office, and Government Paying Office.

http://sam.gov/

6.3.4. 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.

6.3.5 Attachments to the Model Contract

The offeror shall provide the following as attachments to the model contract:

Form Number Description/File

ITO Attachment 1.1.1 Past Performance Information Form

ITO Attachment 1.1.2 Past Performance Questionnaire

ITO Attachment 1.1.3 Past Performance Questionnaire Cover Letter

ITO Attachment 1.2.1 F02-018.png

ITO Attachment 1.2.2 F02-037.png

ITO Attachment 1.2.3 F03-013.png

ITO Attachment 1.2.4 F03-015.png

ITO Attachment 1.3 Pricing Matrix