AviationData-Statement_2017-N-18118.docx

Statement of Work

Solicitation #: 200-2017-18118

Title: Global Aviation Data and Analytical Tools for Public Health Risk Assessment, Surveillance, Preparedness, and Emergency Response

Period of Performance: • April 1, 2017 – March 31, 2018 • Plus two options

SECTION 1 – BACKGROUND

Project(s), Programs or Activities Supported:

The Secretary of the Department of Health and Human Services (DHHS) has statutory responsibility for preventing the introduction, transmission, and spread of communicable diseases into the United States (42 U.S. Code § 264). The authority for carrying out these functions has been delegated to CDC's Division of Global Migration and Quarantine (DGMQ).

The increased speed and capacity of global aviation networks combined with increasing numbers of globally mobile populations, present greater potential for health risks to travelers and the communities to which they travel and return. Airline passengers have been shown to both spread communicable diseases and to be at risk of exposure to communicable diseases.

To reduce morbidity and mortality among immigrants, refugees, travelers, expatriates, and other globally mobile populations and to fulfill its responsibility to prevent and mitigate the spread of communicable diseases of public health concern, DGMQ must enhance its capacity to analyze and report global aviation patterns; this requires access to advanced global aviation intelligence data and analytical tools.

The need is immediate and ongoing for a single, secure, and web-based global aviation database and analytical application to support analysis of aviation global capacity and domestic and international passenger traffic (historical and future).

The aviation data will be used to support risk assessment, surveillance, preparedness, emergency response, and other public health activities. The data will be accessed in multiple ways to accomplish these goals. First, DGMQ staff will directly access aviation data via an online application supplied by the Contractor. Second, Contractor-supplied data will be used to support CDC geospatial analysis and visualization applications. These applications, which sit behind the CDC firewall or on US Government servers, are used by CDC staff to conduct geospatial analyses and data visualizations related to migration and public health. Some of these applications contain a travel module which will use the Contractor-supplied data in the form of a flat file.

In summary, the product shall include:

· Detailed worldwide airline schedule data with date range that extends at least from the prior five years prior to the next 12 months in an online query application that is accessible 24/7 and provided via flat files. Regular updates should be made available on a weekly basis for the online module and every six months for the flat files.

· Detailed worldwide historic air passenger data with a date range that extends at least from the prior five years and is updated monthly. The data should be available in an online query application that is accessible 24/7 and provided via flat files. Regular updates should be made available on a monthly basis for the online module and monthly for the flat files.

· Detailed US Department of Transportation, Origin and Destination (O&D; DB1B) and Onboard Data (T100) that is made available in an online query application that is accessible 24/7 and provided via flat files. Regular updates should be made available on a monthly or quarterly basis dependent on the dataset for the online query application as well as the flat files.

· Customer support – training, technical, DGMQ-dedicated customer service representative.

SECTION 2 – PURPOSE

DGMQ will use these data and tools to provide reports to US and international public health partners to support risk assessment, surveillance, preparedness, emergency response, and other public health activities. The information will be used to support the development of relevant research and may be included in presentations, posters and publications, including peer-reviewed journals. Specifically, the data will be used for (i) assisting governmental or nongovernmental organizations to prepare for and respond to future infectious disease outbreaks or pandemics; (ii) generating reports and presentations for project funders on global population mobility and its relationship to public health; (iii) generating presentations and articles for publication in academic journals, and (iv) developing DGMQ GIS applications and tools.

DGMQ will not publish sensitive airline industry data, such as revenue and market share information.

SECTION 3 – SCOPE OF WORK

The Contractor shall supply DGMQ with the product of global aviation data.

i. Data shall be provided via two formats:

· 6 concurrent-use licenses to have 24/7 access to data via a web-based analytical and visualization application.

· Regularly scheduled transfers of flat files. These shall be provided within 30 days of start date and updated dependent on the type of dataset.

SECTION 4 – TASKS TO BE PERFORMED

The Contractor shall ensure the regular, reliable and efficient production and delivery of global aviation data.

There are three primary tasks to be completed:

1. Aviation Schedules Data, Online Query Tool and Flat File

ii. Contractor will provide access to an online query application that has worldwide airline schedule data that is updated weekly and features access to schedules for the next 12 months and historic schedules dating back at least 5 years. Scheduled travel data should include : date, month, quarter, year, operating airline information, marketing airline, origin information, destination information, through points, equipment information, departure time and terminal, arrival time and terminal, service type, number of flights, seats, seats per flight, duration in block minutes, and total distance (miles). The application should also feature information about cargo flights and details about train and bus schedules when they are part of the scheduled routes.

iii. Contractor will provide a flat file of worldwide airline schedule data that is updated every 6 months with an option to receive weekly or monthly files in the event of an emergency. CDC would notify awardee of the start of the emergency and the need for more frequent data updates. Flat file features include access to schedules for the next 12 months and historic schedules dating back to the previous 12 months. Scheduled travel data should include: date, month, quarter, year, operating airline information, marketing airline, origin information, destination information, through points, equipment information, departure time and terminal, arrival time and terminal, service type, number of flights, seats, seats per flight, ASMs, duration in block minutes, and total distance (miles).

iv. Contractor will provide look up tables and data dictionaries for variables such as: airline codes, names, and alliance members; airline equipment types and seat counts; airport codes, names, and locations.

v. The contractor shall also supply customer support, which will include training, technical, DGMQ-dedicated customer service representative. DGMQ inquiries shall be responded to (full and satisfactory resolution or a specific plan for resolution with timelines included) within 24 hours via email or phone.

2. Aviation Historic Passenger Data, Online Query Tool and Flat File

i. Contractor will provide access to an online query application that has worldwide historic passenger data that is updated monthly and spans at least 5 years and contains no more than a 4 month delay from the time travel occurred. This shall include historical reports or estimates of the number of passengers from an origin to destination, including trip stops. Estimates may be based on statistical modelling or other methodology. Variables should include travel month, quarter, and year as well as operating airline information, marketing airline information. Additionally, trip origin information such as airline code, name, city, country, trip destination information, and trip stops should be included as well as the ability to see total passenger estimates, average fare, revenue, yield, RPMs, and distance.

ii. Contractor will provide a flat file of worldwide historic passenger data for the 5 years prior to award that is updated monthly. This shall include historical reports or estimates of the number of passengers from an origin to destination, including trip stops. Estimates may be based on statistical modelling or other methodology. Variables should include travel month, quarter, and year as well as operating airline information, marketing airline information. Additionally, trip origin information such as airline code, name, city, country, trip destination information, and trip stops should be included as well as the ability to see total passenger estimates, average fare, revenue, yield, RPMs, and distance.

iii. Contractor will provide look up tables and data dictionaries for variables such as: airline codes, names, and alliance members; airline equipment types and seat counts; airport codes, names, and locations.

iv. The contractor will provide a written description of the data, modeling and validation methods to help users interpret the strengths and limitations of the data and any conclusions based on the data.

· This description will be used to evaluate the quality of the data when selecting a contractor. The offeror shall include in this description the global coverage of the data. That is, what percentages of 1) all global scheduled flights and 2) all passenger itineraries are represented in the dataset? For each of these, what percent are reported verses modeled?

· Additionally, this description may also be shared or published with the data in the course of (i) assisting governmental or nongovernmental organizations to prepare for and respond to future infectious disease outbreaks or pandemics; (ii) generating reports and presentations for project funders on global population mobility and its relationship to public health; (iii) generating presentations and articles for publication in academic journals, and (iv) developing DGMQ mapping tools and applications.

v. The contractor shall also supply customer support, which will include training, technical, DGMQ-dedicated customer service representative. DGMQ inquiries shall be responded to (full and satisfactory resolution or a specific plan for resolution with timelines included) within 24 hours via email or phone.

3. US Department of Transportation, Origin and Destination Data (DB1B) and Onboard Data (T100), Online Query Tool and Flat Files

i. Contractor will provide access to an online query application that has US Department of Transportation (DOT) Origin and Destination (O&D) Data (DB1B) that is updated quarterly and US DOT Onboard Data (T100) that is updated monthly. Variables should include travel month or quarter, year as well as operating airline information, marketing airline information. Additionally, trip origin information such as airline code, name, city, country, trip destination information, and trip stops should be included as well as the ability to see total passenger estimates, average fare, revenue, yield, RPMs, and distance.

ii. Contractor will provide flat files of US Department of Transportation (DOT) Origin and Destination (O&D) Data (DB1B) that is updated quarterly and US DOT Onboard Data (T100) that is updated monthly.

· The US Department of Transportation O&D and T100 data should be provided in separate flat files.

iii. Contractor will provide look up tables and data dictionaries for variables such as: airline codes, names, and alliance members; airline equipment types and seat counts; airport codes, names, and locations.

iv. The Contractor will provide a written description of the data, modeling and validation methods to help users interpret the strengths and limitations of the data and any conclusions based on the data.

· Additionally, this description may also be shared or published with the data in the course of (i) assisting governmental or nongovernmental organizations to prepare for and respond to future infectious disease outbreaks or pandemics; (ii) generating reports and presentations for project funders on global population mobility and its relationship to public health; (iii) generating presentations and articles for publication in academic journals, and (iv) developing DGMQ mapping tools and applications.

v. The contractor shall also supply customer support, which will include training, technical, DGMQ-dedicated customer service representative. DGMQ inquiries shall be responded to (full and satisfactory resolution or a specific plan for resolution with timelines included) within 24 hours via email or phone.

SECTION 5 – GOVERNMENT FURNISHED MATERIALS

None associated with this procurement.

SECTION 6 – PERIOD OF PERFORMANCE

SECTION 7 – PLACE OF PERFORMANCE

Offsite.

SECTION 8 – DELIVERABLES/REPORTING SCHEDULE: Deliverables apply to all three tasks.

Milestones All required services must be achieved within agreed-upon schedule as specified in this task order and/or as agreed in the operations and managements plans.

Deliverables produced must contain complete and accurate information in the specified format and template. Briefings, meetings, and reviews must be performed according to the agreed upon schedule.

1. Performance Matrix

Observation and Analysis of delivered support services and deliverables.

Monthly status report.

Favorable or Unfavorable Performance Evaluation

Exercise of the option

As applicable, stage gate reviews, OAs, weekly and monthly project reviews must include an inventory of project documents and report deliverables.

The inventory must be reviewed, tallied, and compared with EPLC deliverable requirements, the Project Process Agreement specific to each project. Review of a project’s baseline versus the actual results must occur at the conclusion of a project. Random review of documents and deliverables for accuracy and completeness Favorable or Unfavorable Performance Evaluation

Exercise of the option

2. Severable or Non-Severable Contract [Identify if Contract requirements are Severable or Non-Severable]

a. This is a Severable Type Contract : [ X ]

b. This Is a Non-Severable Type Contract : [ ]

SECTION 9 – TRAVEL

There is no travel associated with this procurement.

SECTION 10 – SPECIAL REQUIREMENTS

If the contractor will host or create an information system on behalf of the CDC, provide IT services to the CDC, or provide IT products to the CDC, then the contractor must comply with the applicable IT security references below (all sections).

If the contractor is the vendor to provide the products as hardware and/or software to CDC, the vendor must comply with the applicable IT security references below.

1. Standard for Security Configurations

a) The contractor shall configure its computers to meet The United States Government Configuration Baseline (USGCB) requirement (see http://usgcb.nist.gov/) and ensure that the computers have and maintain the latest operating system patch level and anti-virus software level.

b) The contractor shall apply approved security configurations to information technology (IT) that is used to process information on behalf of CDC.

c) The contractor shall ensure IT applications operated on behalf of CDC are fully functional and operate correctly on systems configured in accordance with the minimum required configuration requirements. The contractor shall use Security Content Automation Protocol (SCAP) – validated tools with USGCB scanner capability to ensure its products operate correctly with USGCB configurations and do not alter USGCB settings.

d) The contractor shall ensure IT applications designed for end users run in the standard user context without requiring elevated administrative privileges.

e) The contractors shall ensure hardware and software installation, operation, maintenance, update, and patching will not alter the configuration settings or requirements specified above.

f) Federal Information Processing Standard 201 (FIPS-201) (vii) compliant, Homeland Security Presidential Directive 12 (HSPD-12) card readers shall: (a) be included with the purchase of servers, desktops, and laptops; and (b) comply with FAR Subpart 4.13, non-personal

g) Identity Verification.

h) The contractor shall ensure that its subcontractors (at all tiers) which perform work under this contract comply with the requirements contained in this section.

Standard for Encryption Language

a) The contractor shall use Federal Information Processing Standard (FIPS) 140-2-compliant encryption (Security Requirements for Cryptographic Module, as amended) to protect all instances of CDC sensitive information during storage and transmission. (Note: The Government has determined that CDC information under this contract is considered “sensitive” in accordance with FIPS 199, Standards for Security Categorization of Federal Information and Information Systems, dated February 2004.)

b) The Contractor shall verify that the selected encryption product has been validated under the Cryptographic Module Validation Program (see http://csrc.nist.gov/cryptval/) to confirm compliance with FIPS 140-2 (as amended). The Contractor shall provide a written copy of the validation documentation to the Contracting Officer and the Contracting Officer’s Technical Representative.

c) The Contractor shall use the Key Management Key (see FIPS 201, Chapter 4, as amended) on the HHS personal identification verification (PIV) card; or alternatively, the Contractor shall establish and use a key recovery mechanism to ensure the ability for authorized personnel to decrypt and recover all encrypted information (see http://csrc.nist.gov/drivers/documents/ombencryption-guidance.pdf). The Contractor shall notify the Contracting Officer and the Contracting Officer’s Technical Representative of personnel authorized to decrypt and recover all encrypted information.

d) The Contractor shall securely generate and manage encryption keys to prevent unauthorized decryption of information in accordance with FIPS 140-2 (as amended).

e) The Contractor shall ensure that this standard is incorporated into the Contractor’s property management/control system or establish a separate procedure to account for all laptop computers, desktop computers, and other mobile devices and portable media that store or process sensitive CDC information.

f) The Contractor shall ensure that its subcontractors (at all tiers) which perform work under this contract comply with the requirements contained in this clause.

Security Requirements for Federal Information Technology Resources We provide the following information to assist in the preparation of documents necessary for the Security Assessment and Authorization (SA&A) of an Information System. The FISMA 2014, (Federal Information Security Modernization Act of 2014) and the below federal policies dictate the framework for assuring information security for data systems operated by or on behalf of the Federal government. These are summarized below.

OMB Circular A-130 (https://www.whitehouse.gov/omb/Circulars_a130_a130trans4/) establishes policy for the management of Federal information resources, pursuant to a number of laws and regulations, including the Paperwork Reduction Act of 1980 (amended in 1995), the Computer Security Act of 1987, and other laws. Circular A-130 requires all federal information systems to have security plans, emergency response capabilities, designated individuals who are responsible for security, security awareness training, and regular review of the system. Appendix III of Circular A-130, entitled “Security of Federal Automated Information Resources,” establishes a minimum set of controls to be included in Federal automated information security programs; assigns Federal agency responsibilities for the security of automated information; and links agency automated information security programs (such as the DHHS AISSP) with OMB Circular No. A-123 The Federal Information Security Management Act of 2002 (P.L. 107-347) (FISMA) (http://csrc.nist.gov/drivers/documents/FISMA-final.pdf ) and the Federal Information Security Modernization Act of 2014 (P.L. 113-283) (FISMA 2014) (https://www.congress.gov/113/plaws/publ283/PLAW-113publ283.pdf) requires each agency to develop, document, and implement an agency-wide information security program to safeguard information and information systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor (including sub-contractor), or other source. The National Institute of Standards and Technology (NIST) has issued a number of publications that provide guidance in the establishment of minimum security controls for management, operational, and technical safeguards needed to protect the confidentiality, integrity, and availability of a Federal information system and its information.

Pursuant to Federal and HHS Information Security Program Policies the following standards and guidelines apply:

1. FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems (http://csrc.nist.gov/publications/fips/fips200/FIPS-200-final-march.pdf),

1. FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems (http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf),

1. NIST Special Publication 800-18, Guide for Developing Security Plans for Federal Information Systems (http://csrc.nist.gov/publications/nistpubs/800-18-Rev1/sp800-18-Rev1-final.pdf),

1. NIST Special Publication 800-60, Guide for Mapping Types of Information and Information Systems to Security Categories Vol. 1 (http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol1-Rev1.pdf) and Vol. 2 (http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol2-Rev1.pdf),

1. NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach (http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r1.pdf),

1. NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organizations (http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf),

1. NIST Special Publication 800-63, Electronic Authentication Guideline (http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63-2.pdf).

The System Security Plan (SSP) is part of the Security Assessment and Authorization (SA&A) process required by the FISMA 2014 and NIST Special Publication 800-18, 800-37 and will include selected mandatory controls required by NIST Special Publication 800-53, Volume I & II. The successful contractor in conjunction with the NCEZID Information System Security Officer (ISSO) will submit SA&A documentation to the CDC Chief Information Security Officer (CISO). The successful completion of the SA&A documents will result in an award of an Authority To Operate. Based on guidance in FIPS 199 and NIST SP 800-60 the system will be assigned an overall security category (SC) of LOW or MODERATE based on (confidentiality, LOW/MODERATE), (integrity, LOW/MODERATE), and (availability, LOW/MODERATE) impact levels. These impact levels will be initially determined by the NCEZID ISSO and confirmed by the CDC Certifying Authority as part of the SA&A process.

The successful contractor is responsible for providing pertinent security information to the NCEZID ISSO and Security Staff and assisting in completing the below CDC SA&A documents to include Annual Assessments, Annual Business Continuity Plan, Re-Certifications and applicable significant/non-significant change requests. Appropriate security templates will be provided to the successful Contractor by the NCEZID Security Staff. Completed documents will be sent by the NCEZID Security Staff to the CDC Chief Information Security Office (CISO) for review, approval and subsequent issuance of an Authority To Operate (ATO)

1. Baseline System Information (BSI)

1. Privacy Impact Assessment (PIA)

1. System Security Plan (SSP)

1. Business Continuity Plan (BCP)

1. Risk Assessment Report (RAR)

The Contractor shall respond to the following seven security–associated requirements in the application:

(1) Position Sensitivity Designations CDC requires a Public Trust Level 5 for the following The following position sensitivity designations and associated clearance and investigation requirements apply under this licensing contract:

Level 5: Public Trust - Moderate Risk (Requires Suitability Determination with NACIC, MBI or LBI). Licensor employees assigned to a Level 5 position with no previous investigation and approval shall undergo a National Agency Check and Inquiry Investigation plus a Credit Check (NACIC), a Minimum Background Investigation (MBI), or a Limited Background Investigation (LBI).

Upon award, the Licensor will be required to submit a roster of all staff (including sub-contractor staff) working under the contract that will have the ability to access NCEZID sensitive information from the system. .

Non-Disclosure Agreements The Contractor and any sub-Contractors or employees are forbidden from sharing any technical or logistical information they may gain in conjunction with matters related to this task order that could jeopardize the physical or information security of CDC or its employees, projects, or information systems.

The following apply to Licensor employees and their subcontractors associated with the project:

1. Personnel may not begin work under the contract until the contractor has submitted the employee roster and non-disclosure agreements as described above.

1. Personnel without necessary background investigations will not have access to sensitive project data.

1. Violation of these conditions may lead to termination of the contract.

It is the Contractor's responsibility to ensure that all employees have met CDC and federal requirements, such as, for example, completion of background checks, before gaining or utilizing access to CDC information technology resources.

(2) Privacy Compliance Licensor in conjunction with CDC Center ISSO shall conduct and maintain an initial Privacy Impact Assessment (PIA) as defined by Section 208 of the FISMA 2014. Periodic reviews shall be conducted by the system owner, with assistance from the CDC Center ISSO and contractor, to determine if a major change to the system has occurred, and if a PIA update is needed.

(3) Contractor’s Official Responsible for Information Security The contractor shall include in the “Information Security” part of the Technical Proposal the name and title of its official who will be responsible for all information security requirements should the contractor be selected for an award.

(4) Rules of Behavior The contractor’s employees and subcontractors shall comply with the HHS Information Technology General Rules of Behavior.

(5) Information Security Training CDC policy requires that contractors and subcontractors shall receive security training commensurate with their responsibilities for performing work under the terms and conditions of their contractual agreements. The successful contractor shall be responsible for assuring that each employee, including subcontractors, has completed the CDC Information Security Awareness Training course prior to performing any contract work, and thereafter completing the CDC specified annual refresher course during the period of performance of the contract. This would be provided at the Contractor's expense and would be the Contractor's responsibility to plan and arrange.

The successful contractor shall maintain a listing of all individuals who have completed this training and shall submit this listing to the project officer.

(6) HSPD-12 Compliance As part of the Federal HSPD-12 directive, all information systems deployed within/outside of any federal infrastructure must be able to support HSPD-12 compliant Personal Identity Verification (PIV) of federal employees and contractors. The government has complied with HSPD-12 by issuing PIV cards with embedded digital certificates to all users of federal information systems. In accordance with this directive, all vendors providing hardware and software to the federal government are now required to ensure that these PIV cards will integrate with their software and hardware at the application level. Contractor must be able to implement and support PIV card integration.

(7) Encryption All sensitive CDC-funded data stored on desktop computers used on behalf of HHS shall be secured either through a FIPS 140-2 compliant encryption solution or through adequate physical security and operational controls at the desktop’s residing location.

All mobile devices, portable media and transfer data files that contain CDC- data shall have full-disk encryption using FIPS 140-2 compliant algorithms.

2. Access Requirements None

3. Section 508 Accessibility Standards

a. Technical Standards

|X| 1194.21 - Software Applications and Operating Systems |X| 1194.22 - Web Based Intranet and Internet Information and Applications |_| 1194.23 - Telecommunications Products |X| 1194.24 - Video and Multimedia Products |_| 1194.25 - Self-Contained, Closed Products |_| 1194.26 - Desktop and Portable Computers |X| 1194.41 - Information, Documentation and Support

b. Functional Performance Criteria

|X| 1194.31 - Functional Performance Criteria

SECTION 10 – REFERENCE MATERIALS

None.

SECTION 11 – CONTRACTING OFFICER’S REPRESENTATIVE INFORMATION

The Contracting Officer for this procurement is:

Lauren Peel Centers for Disease Control and Prevention

OCOO/OFR/OAS

2920 Brandywine Road, Mail Stop E-18 Atlanta, Georgia 30341 E-mail Address: lpeel@cdc.gov Preferred method of communication: E-mail

The Contract Specialist for this procurement is:

Le Doan Centers for Disease Control and Prevention

OCOO/OFR/OAS

2920 Brandywine Road, Mail Stop E-18 Atlanta, Georgia 30341 E-mail Address: kuj3@cdc.gov Preferred method of communication: E-mail

Evaluation Factors

EVALUATION CRITERIA GUIDANCE

Technical factors and similar experience when combined will be less important in the evaluation than price. Offerors are not required to propose on all three (3) tasks in order to be considered for award; however the Government will consider additional administrative costs in its price evaluation. The Government will make award on a lowest-price, technically acceptable basis.

Technical Evaluation:

Technical evaluation for this RFP is as follows:

1. Technical Approach: The Offeror shall provide an analysis of the task requirements to indicate their understanding of the task requirements, operating environment and the contract objectives. The Offeror shall provide a description of the performance techniques and methodology they propose in performance of this task. The Offeror shall provide a Project Plan and a Contract Work Breakdown Structure (CWBS) describing the process and approach they propose to use in successfully completing this project. The CWBS should correlate to the Offeror’s price/cost proposal.

The Offeror shall specifically address aspects such as technical understanding, methodology and approach, along with the sub-factors listed below.

a. Provide a detailed and comprehensive statement of the problem, scope, and purpose of the project to demonstrate complete understanding of the intent and requirements of the contract and potential problems that may be encountered.

b. Describe the proposed technical approach to comply with each of the requirements specified in the Performance Work Statement (PWS). The proposal must be consistent with the stated goals and objectives. The proposed approach must ensure the achievement of timely and acceptable performance and will include a milestone and/or phasing charts to illustrate a logical sequence of proposed events.

c. Discuss the plan and solutions for overcoming difficulties involved with performing the work requirements.

Price Evaluation: A price analysis of the proposal may be conducted to determine the reasonableness of the Offeror’s price proposal. Only proposals that are rated technically acceptable will be reviewed.

Notice of Intent to Award Contract without Discussions: It is the intention of the Government to evaluate proposals and award a contract without conducting discussions with Contractors.

OFR Combined SAP SOW & Evaluation Template – July 2013