Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF AUGUST 11, 2017 FBO #5740
DOCUMENT

99 -- Aviation Data Exchange (AVDEX) Request for Information (RFI) - Attachment

Notice Date

8/9/2017
 

Notice Type

Attachment
 

Contracting Office

FEDERAL AVIATION ADMINISTRATION, AAQ-640 CT - William J. Hughes Technical Center (Atlantic City, NJ)
 

Solicitation Number

27962
 

Response Due

9/11/2017
 

Archive Date

9/11/2017
 

Point of Contact

Sean McHugh, sean.mchugh@faa.gov, Phone: 609-485-6740
 

E-Mail Address

Click here to email Sean McHugh
(sean.mchugh@faa.gov)
 

Small Business Set-Aside

N/A
 

Description

************************************************************* NOTE: The posting of this RFI and applicable attachments are located on the FAA Contract Opportunity (FAACO) website at https://faaco.faa.gov/, which is the official record of this RFI. It is the contractor �s responsibility to fully review the RFI in its entirety on FAACO. ************************************************************* Request for Information (RFI) Office of Aviation Information and Technology (AIT) Aviation Data Exchange (AVDEX) 1.0 PURPOSE AND INTRODUCTION: The Federal Aviation Administration (FAA) is seeking industry cabability statements and technical approaches to determine the existence of any viable commercial solutions present in the current marketplace and to help determine the proper acquisition strategy for this requirement. No notification about the outcome of this RFI will be released. ** IMPORTANT -- This is a Request for Information (RFI) being issued for �Market Research Purposes � only. This Is Not a Request for Quote (RFQ) or a Request for Proposal (RFP). ** This RFI is for information only and does not commit the Government to pay any proposal preparation costs for responding to this notice, and is not considered an allowable direct charge to any resultant task order or any other contract. Responses to this request are informational in nature and will not be considered offers, nor will they be accepted by the Government to form a binding contract. Actual pricing of this requirement, labor categories or hours are not requested, nor will any be reviewed under this request. The Federal Aviation Administration (FAA) has a need to develop an IT system, the Aviation Data Exchange (AVDEX), using agile methodology that can provide the capability to absorb seven (7) decentralized systems for aviation reporting throughout the enterprise. The FAA seeks to consolidate these systems into a one stop source for the Global Aviation Community to access aviation safety information. The acquisition strategy for the procurement has not been determined at present. The information submitted in response to this RFI will be used by the FAA for informational, market research, and planning purposes only. It may also be used to support the decision as to whether the requirement will be set aside for only small and/or small and disadvantaged businesses. Not responding to this RFI does not preclude participation in any future RFI(s) and/or Screening Information Requests (SIRs) related to AVDEX; if any are issued. 2.0 BACKGROUND: The FAA seeks to understand its options to acquire a cloud-based mobility-first system comprised of commercial-off-the-shelf (COTS)/modified COTS components (to the greatest extent possible) that are open, configurable, and customizable. Should no COTS-based solution be available or it be determined that a COTS-based solution is not in the best interest of the FAA, the FAA is also considering a developmental system comprised of open source code software. The new system is being termed the Aviation Data Exchange (AVDEX). The system must have the ability to support the functional requirements identified in the AVDEX Themes document provided as Attachment A. The support of requirements may come as either �out-of-the-box � capability with robust configuration capabilities to accommodate FAA business rules, or with customization. The FAA anticipates that AVDEX will be completed in well-defined phases, and that the contractor will implement agile methodology for a clearly defined life cycle approach that results in a seamless transition of some or all of the existing business functionalities from the current reporting systems to the proposed AVDEX system. The FAA requires technical services, such as web application development, mobile application development, administration, maintenance, training, and capability enhancements to support the deployment of AVDEX. These services are to be applied in the acquisition, installation, and operation of a proven, enterprise class, web-based, mobility centric, cloud supported AVDEX system that leverages state-of-the-art technology. The contractor-delivered system must be of sufficient operational maturity and scalability necessary to support the initial user base of approximately 300,000 individuals with anticipated rapid growth. The AVDEX system will interface with existing FAA and civilian aviation authorities, legacy systems as well as industry, civilian, and commercial entities. The AVDEX system must also provide the FAA capability to support future interconnections with external systems to exchange aviation safety information. It is anticipated that the selected solution will be cloud based, and will be supported and maintained by contractors at a FAA- certified facility. 3.0 Submittal Requirements and Instructions: The FAA is requesting that interested companies provide a (1) Capability Statement and (2) Technical Approach. The submission must follow the suggested outline below and be limited to twenty-five (25) pages. All submissions must be presented in size 12 Times New Roman text and be compatible with either Microsoft Word format or Adobe Acrobat PDF. If chosen to submit via Adobe Acrobat PDF format, please ensure the document retains the ability to copy and paste into a MS Word Document (i.e. do not submit picture files). Additionally, the FAA encourages vendor comments and suggestions regarding this effort, including alternative approaches to meeting the FAA requirements. Comments and suggestions must be provided separately from the Capability Statement and Technical Approach. Comments and suggestions do not have a page limit. 3.1 Capability Statement- Please provide a brief description of your company �s ability to execute the performance objectives below. This description must (1) include examples demonstrating your experience and (2) identify if the experience was performed as a prime or subcontractor. Experiences must be actual prior government (federal, state or local) or commercial work experiences as described in this RFI. Please limit discussion to relevant current or previous experience within the last five (5) years. The capability statement should address the following: a.Developing a cloud-based mobility-first system comprised of commercial-off-the-shelf (COTS)/modified COTS components that are open, configurable, and customizable to address the evolving needs of the Global Aviation Community. b.Developing a cloud-based mobility-first developmental system comprised of open source code/software to address the evolving needs of the Global Aviation Community. c.Migration of legacy data into one (1) system using Agile methodology while incorporating capability enhancements and emerging technologies during contract performance. d.Developing an offline mode for when internet access is unavailable, thus enabling anytime, anywhere access. e.Developing a data infrastructure that can evolve as needed as a normal course of business without requiring system redesign supporting multiple forms of structured and unstructured data including pictures, video, sound files, and signal data. f.Incorporating artificial intelligence, machine learning, and natural language processing to support business needs such as alerting, data visualization, analytics, sound and video to text, data conversion, and other needs. g.Developing a system that must perpetually evolve and keep pace with aviation industry innovation. h.Developing a system that quickly engages people in an experience that allows them the opportunity to anticipate risks, share observations, comments, and ideas as well as contribute to the development of other people �s observations. i.Supporting the automated discovery of relations and patterns to predict and notify of potential hazards and risk. 3.2 Technical Approach � Please select up to three (3) User Stories per Theme as delineated in Attachment B, AVDEX User Stories document. For each User Story selected, please describe your technical approach (at a high level) and methodology for addressing the User Stories. Also, if your proposed solution includes features that are not part of the current AVDEX User Stories/requirements and might be beneficial to the FAA, please describe these features and how incorporation might benefit ADVEX. Additionally, please cite examples of successful solutions provided during past performance for similar efforts, noting any tools, techniques, and innovation used. 4.0. North American Industry Classification System (NAICS) Code NAICS Code(s) has not been determined at this time. 5.0 Delivery of Submission: RFI responses must be submitted via electronic mail (e-mail) to the Contracting Officer, Sean McHugh at Sean.McHugh@faa.gov no later than September 11, 2017 by 5:00 pm ET. The FAA welcomes any general comments regarding the content of the RFI. Questions or comments must be submitted in writing prior to the closing date and directed to email Sean.McHugh@faa.gov. 6.0 Non-Government Personnel Participation: The FAA may utilize contractor support personnel in meeting with customer organizations and reviewing vendor submissions. Contractor support personnel will sign all relevant Non-Disclosure of Information and Conflict of Interest Agreements for any subsequent acquisition. 7.0 Other: It is highly recommended that interested vendors check the FAA �s Contracting Opportunities website frequently for any updates and amendments to this announcement. Also, if this announcement is being viewed from other than the FAA �s Contracting Opportunities website, some information and/or attachments may not transfer correctly. Therefore, only the information and attachments provided at http://faaco.faa.gov are considered the �official � source of information on this requirement. 8.0 Attachments: A.AVDEX Themes document B.AVDEX User Stories document If you're viewing this announcement from a source other than Federal Aviation Administration Contract Opportunities (FAACO), visit https://faaco.faa.gov/index.cfm/announcement/view/27962 to view the original announcement.
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/DOT/FAA/WJHTC/27962/listing.html)
 

Document(s)

Attachment
 

File Name: Attachment A - AVDEX Themes document (pdf) (https://faaco.faa.gov/index.cfm/attachment/download/80867)

Link: https://faaco.faa.gov/index.cfm/attachment/download/80867

 

File Name: Attachment B - AVDEX User Stories document (pdf) (https://faaco.faa.gov/index.cfm/attachment/download/80868)

Link: https://faaco.faa.gov/index.cfm/attachment/download/80868

 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN04620200-W 20170811/170809232139-b2c7200849060eb6a6449f588e4b2164 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |