AETC_AOI_4_-_Wing_Feedback_App.pdf

PDF 60 KB Posted

Attached to
FY19 AETC_Commercial Solutions Opening (CSO)_update Federal contract opportunity
Solicitation number
FA3002-19-S-C001
Issued by
Department of the Air Force

About this file

AOI 4 Wing Feedback App

View the file

Other files for this federal contract opportunity

Other files attached to FY19 AETC_Commercial Solutions Opening (CSO)_update, newest first.
File Type Posted
AETC_AOI_A06_T-38C_Digital_Model_V2.pdf PDF
AETC_AOI_A06_T-38C_Digital_Model.pdf PDF
AETC_AOI_5_Competency_Mapping.pdf PDF
AETC_AOI_3_DODIDNOW_FINAL_(31_MAY_19).pdf PDF
AETC_AOI_3_DODIDNOW_FINAL_(15_MAY_19).pdf PDF
AETC_AoI_A02_GPS_Degraded_Training.pdf PDF
AETC_AOI_A01_Project_NEXUS_(Final).pdf PDF
AETC_AOI_A01_Project_NEXUS_(Final).pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

12 June 2019/KAFL

AREAS OF INTEREST (AOI): WING FEEDBACK APP / FA3002-19-S-C001_A04

1. General Information

1.1 AoI Background

The United States Air Force (USAF) Air Force Installation and Mission Support Center (AFIMSC) has a desire to crowd-source feedback regarding Wing- or Installation-level services using a mobile application platform. The purpose of this Wing Feedback App (tentative name) is to collect user feedback on both contracted and organic services in order to (1) comprehensively monitor contracted and organic service performance, (2) assess where service performance is exceptional/poor and reward/institute improvements appropriately, and (3) determine where AF-designed performance standards may be incorrect (i.e., where AF standards are off-the-mark) in order to adjust them to better meet mission needs. Feedback will be used by (1) Wing/Installation Commanders and their supported units, (2) Contracting Officer Representatives and Contracting Officers (i.e., those who monitor contracted services), (3) contracted service providers (i.e., those performing the services), and (4) other interested parties. The Wing Feedback App is intended to be used at all 79 Air Force installations using individuals’ personal smart devices and commercial cellular networks or commercial WiFi. The end product needs to be able to be used on iOS and Android devices.

AFIMSC desires to accomplish the creation of the Wing Feedback App by partnering with non-traditional small business contractor(s) to provide AFIMSC with a prototype commercial solution. Solution Briefs must show the ability to design an app that is standardized for all Air Force installations (i.e., same user interface), yet allows for tailorable service inputs specific to each installation.

Solutions meeting Phase 1 selection criteria may be invited to Phase 2 to provide a Pitch. Solutions meeting Phase 2 selection criteria may receive an invitation to Phase 3 and receive a Request for Prototype Proposal (RPP). NOTE:

The Government reserves the right to forgo Phase 2 and go directly to Phase 3.

The government reserves the right to extend performance to all, some, or none of the selected solutions and the decision will be made based on the availability of government funds.

2. AoI Required Capabilities

1. Easy! The app must be an intuitive, easy-to-use mobile platform that is free to download and use.

2. The app must allow users to easily filter to their specific Wing or Installation. Similarly, the app’s structure must allow users to easily filter to a given group of like-services in order to find the specific service they want to rate.

3. The app must be open-source for continual updating by privileged users (e.g., adding/deleting services, changing rating criteria, allowing for tailorable rating criteria, etc.).

4. Ratings mechanisms must be simple, offering tailorable types of ratings for different services. The ability to take and upload pictures must be offered.

5. There must be a “control” hierarchy, with privileges and rights based on position. The contractor should suggest how the control hierarchy would be formatted/function (i.e., who should control what functions).

6. Consider the use of geo-location/geo-fencing functions to lead users to the list of services they can rate.

7. The contractor should build in fences that detect, eliminate, and prevent the input of fake ratings (e.g., service providers rating their own performance).

8. The app must operate on a cloud platform outside of the Air Force Network (AFNET) and on both Apple and Android operating systems Both platform and app must be in compliance with with FEDRAMP IL2 certification requirements.

9. The app must provide easy-to-interpret visual displays of data, including trends. The app must also build in an API to allow AFIMSC to perform its own analyses and data visualizations.

AREAS OF INTEREST (AOI): WING FEEDBACK APP / FA3002-19-S-C001_A04

10. The contractor is free to suggest ways to collect data across Wings/Installations.

11. The app must capture and report app usage data.

12. Contractor must perform a beta test of the prototype app.

13. The contractor must be willing to turn over the source code for the app to the AF. In other words, the AF will own all data rights for the app.

3. PHASE 1 - Solution Brief Submission Requirements

3.1 Submission Requirements

Written Solution Briefs as described in 3.2 must be sent via e-mail submission by 11:59 P.M. (CDT) on 8 July 2019, with subject line stating WING FEEDBACK APP to benjamin.dehart@us.af.mil and karen.landale@us.af.mil.

Solution Briefs received after the specified due date and time will be discarded and not be evaluated by the Government.

3.2 Written Solution Brief Requirements

3.2.1 Content of Solution Brief

The written Solution Briefs should not exceed five (5) single page written pages (Solution Briefs can be double sided, but cannot exceed two double sided pages, and one single sides page) using 12-point font or, alternatively, Solution Briefs may take the form of briefing slides which should not exceed fifteen (15) slides. Any pages or slides submitted beyond this limitation will be removed and not evaluated. The written Solution Brief shall include and/or address the following:

3.2.1.1 Title Page (does not count against page limit)

● At a minimum, please include company name, solution name, solicitation number, date of submission, point of contact name, email address, phone number, and company address. This page will not count towards the page/slide limitation.

3.2.1.2. Executive Summary/Company Description

● Describe your commercial customer base and provide some examples of past contracts or sales of this service/solution from within the last two years.

● Describe your company – e.g., How long has it been in operation? Where is it located and headquartered, multiple locations, sales/R&D in U.S. and other countries? Number of current employees?

● Describe the management team – e.g., Who are they? What is their background and history and qualifications (previous startups, etc.)?

● Include other relevant corporate information, as applicable.

3.2.1.3. Solution/Technology Concept

● Describe the unique aspects of your technology/solution and the proposed work as it relates to this published AoI. Identify whether the effort includes the pilot or demonstration of existing commercial technology (identified as commercially ready and viable technology), or the development of a new technology or process to training/learning.

3.2.1.4. Company Viability

mailto:benjamin.dehart@us.af.mil

AREAS OF INTEREST (AOI): WING FEEDBACK APP / FA3002-19-S-C001_A04

● Provide a brief overview of the company. Provide a summary of current fundraising to date and/or a summary of the top line (gross sales/revenues) and balance sheet. Provide a summary of product commercialization and go-to-market strategy.

4. Evaluation of Phase 1 – Solution Briefs

4.1 General

The Solution Brief shall be evaluated against the published AETC CSO evaluation criteria.

The general AETC CSO https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cvi ew=1 Phase 1 evaluation criteria shall be used to evaluate and rate the proposed Solution Brief. The AETC CSO evaluation criteria are listed below in order of importance from top to bottom. If a Solution Brief does not meet the first or second evaluation criterion, the Solution Brief will not be further considered for Phase 2 - Pitch Presentation.

Upon conclusion of this round of Solution Brief evaluations, the Government will down-select offerors to further develop and submit a detailed Pitch Presentation.

5. Evaluation of Phase 2 - Pitch

5.1 General

The Pitch Presentation shall be evaluated against the published AETC CSO evaluation criteria.

The general AETC CSO Phase 2 evaluation criteria shall be used to evaluate and rate the proposed Pitch Presentation. The AETC CSO https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cvi ew=1 evaluation criteria are listed in order of importance from top to bottom. If a pitch does not meet the first or second evaluation criterion, the solution will not be further considered for Phase 3 - Request for Prototype Proposal (RPP). NOTE: The Government reserves the right to forgo Phase 2 and go directly to Phase 3.

6. Evaluation of Phase 3 - RPP

6.1 General

Upon conclusion of evaluation of the Pitch Presentations, the Government will down-select and invite no more than three AoI participants to further develop and submit a detailed technical and price proposals. Each proposal submitted shall consist of a title page and two parts:

● Volume 1: Technical Proposal

● Volume 2: Price Volume

The submitted proposal shall be evaluated against the published AETC CSO evaluation criteria.

The general AETC CSO https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cvi ew=1 Phase 3 evaluation criteria shall be used to evaluate and rate the Phase 3 proposal submittal. The AETC CSO evaluation criteria are listed in order of importance from top to bottom. If a proposal does not meet any of the first 3 proposal adequacy items in AETC CSO Section 3.4 (items 1-3) basis of evaluation, the proposal will be disqualified from a Phase 3 award. If AETC decides to pursue a prototype OT, then the proposal must met the proposal adequacy items in AETC CSO Section 3.4 (items 4-8) basis of evaluation to be considered. If not, that proposal will be disqualified from a Phase 3 award.

6.2 Technical Proposal Solution (Volume One)

Each selected AoI participant invited to Phase 3 must submit a technical proposal solution as part of their final proposal that identifies the work to be performed and the deliverables. Provide a detailed project schedule that https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cview=1 https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cview=1 https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cview=1 https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cview=1 https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cview=1 https://www.fbo.gov/index?s=opportunity&mode=form&id=538f662154e57ca1d8a7ee773089cb00&tab=core&_cview=1

AREAS OF INTEREST (AOI): WING FEEDBACK APP / FA3002-19-S-C001_A04

outlines the various phases of required learning objectives within the stipulated period of performance. The AoI participant must provide a technical volume that includes a Statement of Proposed Work (SOPW) with the following tabbed sections:

● Section 1 - Background

● Section 2 - App functions and capabilities

● Section 3 – Prototype development milestone schedule

● Section 4 – Beta test plan and milestone schedule

● Section 5 – Suggested cloud-hosting and sustainment plan

Please Note: The proposals must identify any proprietary information or associated intellectual property.

6.3 Price Volume (Part Two)

6.3.1. In addition to the instructions found in AETC CSO Section 3.4, Price Proposal, this AoI requires the following:

a. The offeror shall submit a firm-fixed price proposal to successfully build the proposed app prototype. Breakdown of labor, materials and other direct costs (ODC) shall be submitted.

b. The offeror shall submit a firm-fixed price proposal to successfully beta test the proposed app prototype.

Breakdown of labor, materials, and ODCs shall be submitted.

c. The offeror shall submit a firm-fixed price proposal for annual sustainment of the app.

d. The offeror shall submit a firm-fixed price proposal for annual cloud-hosting.

7. AoI Open Period – This AoI shall close at 11:59 P.M.; 8 July 2019.

8. Point of contact

AoI questions can be sent to:

Program Manager: Lt Col Karen Landale, karen.landale@us.af.mil

Contract Specialist: TSgt Benjamin DeHart, benjamin.dehart@us.af.mil mailto:karen.landale@us.af.mil mailto:benjamin.dehart@us.af.mil

File details come from the government source that posted it.