Attch 7 - 1st Round of QA.pdf

1st Round of Questions and Answers

13 Jul 2021

EAFB-001

1. I have a question on the Parcel delivery lockers. When I provided some budget estimates it was for 81 doors. That was based on what they were budgeting for. With 730 Airmen it’s likely they are getting more packages than that every day.

See revised Topic Description.

2. Do you have an estimate on the daily package counts we can tailor our quote?

See revised Topic Description.

3. Question: Is there a dollar threshold you are trying to meet?

See submittal instructions.

EAFB-003

1. We are able to provide the autonomous floor scrubbers in the proposal. Will you accept a bid just for the autonomous floor scrubber?

See revised Topic Description.

2. Will we have access to wifi in the building? If not, will you provide a SIM card or will you require us to provide one? If we are providing, do you have a preference of carrier (Best cellular signal in warehouse)

See revised Topic Description.

3. Does your warehouse consist of racking only or does it include bulk areas? If both, what % is racking and what % is bulk?

90% of the warehouse is racking and 10% is bulk.

4. If your warehouse has bulk storage - is it consistently full or are there days where they are empty?

The bulk is never empty, but there is not much in the area.

5. What are the aisle widths between racking? This will allow us to determine the correct size/configuration of the scrubber.

See revised Topic Description.

6. Do you plan to scrub floors during business hours or after? As in, will there be personnel working in the area that is being cleaned or is the warehouse empty?

The scrubber will be used during after-hours. We do have a night shift that consists of 4 personnel.

7. Do you currently perform a walk thru/pre-sweep to remove debris (big wood chunks, plastic wrap). If not, will you be able to perform a pre-sweep to prep the floors for scrubbing?

Yes - walk thru/pre-sweep performed.

EAFB-004

1. Are there specific server hosting requirements, can the servers be hosted on a vendor-controlled cloud account?

See revised Topic Description.

2. Will the system be expected to facilitate a dispatch process? Example: Route creation, pilot review/acceptance, flight plan review and approval.

See revised Topic Description.

3. Would it be possible to amend this requirement to offer phone support during standard business hours at Eglin AFB?

See revised Topic Description.

4. Are there any 3rd party software integrations or APIs needed?

Having a web application that is accessible via NIPR may drive some 3rd party software integration. Other than that, the initial effort will not require any further 3rd party integration.

5. Can you provide example reporting needs?

The test cards themselves will provide the prompts and information cues that will drive reporting needs. For this initial effort, no explicit reports will be generated via

DEXTER.

6. What is your implementation timeline?

There are no specific events on our end that are driving implementation. With that said, we'd like to get a working product as soon as possible so we can start iterating.

7. Will the system be expected to utilize flight-following and mission tracking?

No. The initial implementation will focus on the process leading up to flight test execution and is not expected to be utilized during the testing itself.

8. Will the software be tracking any pilot data - duty time, currency info, mission data?

No, the software will not track any pilot data.

9. Will the software be tracking any aircraft data - engine times, maintenance items, total flight time?

No, the software will not track any aircraft data.

10. Can you further explain the terminology “Test Card”. Does Test Card refer to a digital log of a mission / flight request / dispatch process?

The business comparison for a test card is a form. Each business, or in our case squadron, formats the form differently. Nearly all formats have items such as title, card number, risk level, POC, classification level, etc.. However formats differ on test specific information (flight conditions, switch settings, etc.) required and formating for procedures. Finally there will often be tables, graphs, or white space to record data. As an example, flight test cards generally contain the following minimum information contained in Section 2.2 of the Edwards Air Force Base Instruction 99-

105:

https://static.e-publishing.af.mil/production/1/edwardsafb/publication/edwardsafbi99-

105/edwardsafbi99-105.pdf

However, these fields are not necessarily applicable for every mission, and the pilots frequently need to add new fields as required.