We optimized our interviews to validate our assumption that (1) an Arduino or particle.io-based micro controller system would be pass the security laws at Fort Bragg (2) the micro controller system shown below is scalable and would fulfill the design constraints set by LTC Phillip Thomas and James Arp and (3) to discuss the feasibility of the proposed system both in terms of necessary skills and the time that we had available to work on an original prototype. In order to be fully prepared, we also explored commercial solutions in case we wouldn’t be able to deliver a proper prototype.
Primary Data Users
- Cognitive Performance Coaches
- Data Analysts
- Research Psychologist
- Instructors (Cadre)
- SWIC Commander
INTERVIEWS & KEY TAKEAWAYS
|Vatrina Madre Information Technology Director | SWEG
|Maj Arth Commander’s Action Group, Director | Joint Special Operations Command
|Rachel Feher Congressional Research Service
|Dr. Lawrence Appelbaum Director of Human Performances Lab | Duke
|Yao Yuan ECE Student | Duke
|Mitch Heath CEO | Teamworks
|Kyle Janson ECE BME Student | Duke
|Mark Palmeri MD PhD and ECE Professor | Duke
|Trevor O’brien SWEG IT | SWCS
|Rich Diviney Retired Navy SEAL/Seal Team 6 Instructor
- The data analysts and the data managers would still be the main point of contacts to receive the raw data
- Bluetooth is now possible. From our interview with Vatrina Madre, we learned that there are two networks that we can operate on: Lang and NIPR. NIPR is more “black and white” and Lang is more lenient as far as devices to connect.
- The new facility will be up and running in 2-5 years.
- Creating a prototype from scratch seems infeasible given the time frame and the resources available. One commercial solution in particular, StelLife (introduced to us by Steve McClelland) is a strong candidate due to high data integration capabilities and scalability.
- The biggest problem is that given the time constraints and skills available to the team, creating a prototype from scratch seems less feasible. The team is stretched in regards to managing workflow given the high amount of deliverables and the capabilities of the team.
- This is still true: that the structure and procedure for data collection, analysis, and storage is changing week to week within HDP. Week to week, we learn of new developments in many of our beneficiaries’ roles as it relates to data analysis, connection, and storage.
- This is still true: We do not have the devices with us so it is difficult to test the effectiveness of our MVP. We have tried to ask for dummy data, but we faced barriers regarding confidentiality.
- We also have not been able to get in contact with vendors to supply a possible solution.
- We have mapped out a new workflow in which half of the team works on interviews while the other half of the team works on prototyping. We are currently going to reconsider this workflow at the end of this class in case team members feel overworked.
- We will commit to identifying companies that are willing to send new devices and data specs so that we more easily gauge the feasibility of creating a device from scratch
- We will look more into StelLife and other possible commercial products as a means of providing a solution to our problem sponsor.