Attachment 6 - AOI 001 Questions.pdf

Resiliency Assessment Matrix Questions

- 1. We would like to know a ballpark estimate of how many non-administrative users would utilize the form (example: 10K,20K-50K users) o If only opening across JBER Air Force units, no more than 10K users.

However, the solution must be capable of expanding to 40K users or more.

- 2. How many administrators?

o There should be a hierarchy of administrators with specific roles assigned.

Full access administrators should be limited to 2 per wing. These individuals would have the capability to alter questions for their wing’s assessment.

Groups and squadrons should each have one primary and one alternate administrator to assist with more minor issues such as passwords and lower level role assignments. Plan for roughly 1 to 2 administrators per 1000 users with the ability to accommodate growth.

- 3. Will the form stay anonymous for users? How do you track users without a profile? Will you want to ask for age, gender, etc. to further identify individuals and trends?

o Submissions must stay anonymous. However, there should be login profiles for supervisors and commanders. We are open to ideas on how to do this.

- 4. Is the decision tree (question is asked and response is given) fixed or dynamic?

Meaning will it need to change over time or stay the same. Will questions evolve and or change and adapt.

o Supervisors should have the capabilities of updating their subordinate’s status as their situations change in real time. The decision tree should be dynamic and question should change as responses change from previous entries.

- 5. Is the Government interested in a solution with mobile capabilities?

o This solution should be accessible with or without a desk top computer. Being able to access the product with a mobile device is critical for our members who do not have regular access to a computer such as our maintenance and flight line personnel.

- 6. Will you require Multi Factor Authentication, Passwords change every 90 days, and or re-use of historical passwords?

o Username/password should be required. Password modification and overall security should be based on the features of the product you propose.

- 7. Will this be a new application, or will the Contractor be adding features to an existing application?

o This will be a new application. There is a google form being used currently that may help with design but this will not be a sufficient platform.

- 8. The CSO indicates that Personally Identifiable Information (PII) will be excluded.

What type of non-PII information will be tracked?

o The only identifiers used currently is the member’s squadron/flight and a made up call sign to ensure we don’t calculate duplicate submissions.

- 9. What values define PII?

o Anything that can be used to identify an individual. Name, social security number, DODID… etc.

- 10. What is the capability of the current beta tested system and what are its shortcomings that need to be improved on?

Pros:

Easily accessible with mobile devices.

Takes only a couple minutes to submit a response.

The answer provided in one question will take you to relevant follow up questions making the assessment quick and convenient.

Export data collected to MS excel.

Previous submissions can be edited and resubmitted.

Unlimited number of responses.

Allows self-reports and/or supervisor reports.

Reports allow commanders to see what resources are needed for their flights.

Cons:

Not accessible on government computers.

Will not provide relevant aesthetically pleasing automated reports.

Does not provide a dashboard for supervisors to quickly update each subordinate.

Each submission can only capture the status of 10 subordinates.

Anyone in the world with the link can provide a submission.

Does not allow hierarchical access to reports. Commanders should be able to view reports for their level of command. Flight commanders should be able to see their flight’s report, squadron commanders should be able to see their squadron’s report and each flight’s report and so on.

- 11. Will an ATO (Authority to Operate) be required?

o An ATO is required for solutions connecting directly to NIPR or hosted in hardware located on base network infrastructure. An ATO will not be required for solutions developed and hosted on a commercial webspace.

- 12. Can you confirm our understanding of your current product workflow?

o An administrator created a form in Google forms o The 673 OMRS and 673 HCOS staff receive a QR Code for the URL to the google form The Google Form is accessible by “anyone with the URL” The Google Form is “shared” and anyone not included in the share list must “Request Access”.

o The Google Form is mapped to a Google Sheet into which submission data is stored The Google Sheet is accessed by the administrator who is responsible for generating reports o Base staff scan the QR code they received (or that was shared with them) o User interactions and submissions data is captured and stored in the Google

Sheet.

o The administrators accesses the data from the Google Sheet and copies the information to an excel spreadsheet to build charts and graphs using standard Excel toolset and sends them to respective squadron commanders.

o Charts are copied and pasted from the Excel Sheet into PowerPoint.

- 13. Is the expectation that the Solution will no longer be dependent on the use of Google tools but, instead, all the aforementioned steps will be executed within a single product?

o Yes.

- 14. How many forms are produced per month? Per quarter, Per year?

o There is one google form being used. Users complete submissions on the same form monthly and reports are generated according to the date/timestamp on the individual submissions.

o The intent is to not use google forms for this program.

- 15. Does the Google form get updated over time or do you create a new form each time the content in a section or the form flow needs to be changed?

o There is one google form being used. Users complete submissions on the same form monthly and reports are generated according to the date/timestamp on the individual submissions.

o The intent is to not use google forms for this program.

- 16. How many form submissions do you receive per month? Per year?

o Currently we only receive submissions from 2 squadrons using the google form (approximately 100-150/month). There will be significantly more once the final product (not google forms) is instituted.

- 17. Do you have a goal for how many submissions you want/expect per month, quarter, and year? Do you want all base staff to submit whether they feel stressed or not or is the goal/expectation that only those who need support will submit a form?

o The intent would be for personnel to submit a response at the requested interval of the commander. The medical group currently does this monthly but a quarterly submission may work in other instances. Across the Air Force units on JBER we could expect approximately 5000 submissions or more per month, with the potential to expand to 40,000 or more.

- 18. Will helping agencies need to access the solution to pull data.

o Yes. Helping agencies should be able to see what the needs are for each unit and the trends associated with each stressor in each unit. Additionally, if any feedback regarding the agency is collected, the agencies should be able to see this as well.

- 19. Product commercialization in the open market – Does the command expect the solution to already be in use in the open market?

o No.

- 20. How many users of the application are anticipated?

o If only opening across JBER Air Force units, no more than 10K users.

However, the solution must be capable of expanding to 40K users or more.

- 21. Is the desire to have a data processing pipeline then provide visualizations in a dashboard (Tableau or other), or to have an application where this data is processed and visualized?

o The desire is to have a dashboard for users to see real time stats based on their permissions and position. For example a squadron commander can see stats pertinent to his/her squadron including each flight, a group commander would be able to see each squadron’s stats in the group, a wing commander would see all group stats and so on.

- 22. How (if at all) do the free-text responses in the Google form influence the resiliency risk score?

o Free text responses do not influence the score but it does allow members to voice their individual situations to their command team. This is crucial in understanding the risk score, what the most effective response would be for the unit and if the situation is getting better over time.

- 23. Are there other components to the application besides the google survey?

o Yes, we currently use an excel spreadsheet to help summarize data and a PowerPoint to present.

- 24. Would you be interested in adding free text responses to the existing survey?

o We do not want to continue using the existing survey as google forms is not a sufficient platform.

- 25. Is there one level of access to the data & findings that is collected or will there be different interested parties that may need some of the data hidden while others don't?

For example, leadership views all data and a subset of that is shared with a broader group?

o There will be different interested parties that would need access that is relevant to their position. For example, a commander can see responses from his/her unit but not responses for another unit.