N161-016 TITLE: iPhone Operating System (iOS) Framework and Application Development for Electronic Kneeboard

TECHNOLOGY AREA(S): Air Platform, Human Systems, Information Systems

ACQUISITION PROGRAM: PMA 265 F/A-18 Program Office

The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with section 5.4.c.(8) of the solicitation. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.

OBJECTIVE: Develop an iPhone Operating System (iOS) framework and application(s) for moving the Weaponeering and Stores Planning (WASP) program, flight and mission planning, emergency procedures, and other relevant mission tools to the Apple iPad scheduled to be implemented into the Fleet for what is referred to as the "Electronic Kneeboard."

DESCRIPTION: The Navy currently uses paper manuals, instructions, and documentation, as well as hand calculations, during flight to ensure mission success. Completing such tasks manually can be time consuming and, in some instances, may hinder mission success. It is projected that the F/A-18 Fleet will be outfitted with the "Electronic Kneeboard," or an electronic version of information that is traditionally on paper. This new approach to storing and presenting data to the pilot is going to be on the Apple iPad, a user-friendly hardware with which many pilots have familiarity. Moving mission planning, WASP, emergency procedures, approach charts, and other relevant mission tools is not, however, as simple as loading a word document onto the iPad. It is unreasonable to expect a pilot to know command-line coding and background programming language; therefore, proper windows, icons, menus, buttons, and more must be implemented seamlessly into the applications (apps) (i.e., software that operates on the iPad) [1]. Considerations for human-machine interfacing, cognitive capabilities, and situational awareness are lacking.

The development of useful apps, similar to those listed previously (e.g., WASP, flight and mission planning, emergency procedures), for the electronic kneeboard, and subsequently, a comprehensive, standardized application suite and software architecture that will be appealing and intuitive to the user is desired. This architecture should be modular, simple and extensible to the needs of the Navy fostering further application development within the Department of the Navy (DoN).

While developing the apps, plan the graphical user interface (GUI) in regard to the goal of each app (e.g., the number of "swipes" or "taps" that are required to access relevant information for the pilot) [1, 2]. For example, when searching for an emergency procedure, a pilot should be able to easily access the appropriate information very quickly and accurately. Cognitive psychology has greatly overlapped with GUI design in recent years � including considerations of perception, attention, memory, learning, and decision making [2]. Apps and software architecture development should include evidence of addressing these areas of study where applicable.

Performers should assess costs and benefits of different presentation parameters (e.g., luminance, tab/swipe, location of information) and limitations of the human psychomotor system - especially in the flight environment [3, 4, 5]. The final product should provide multiple apps that can be used in-flight and a framework that software developers within the DoN can develop, test, verify, and/or modify further app development.

This topic will remain unclassified throughout Phase I. Access to classified data will be required in Phase II in order to demonstrate the prototype. The Technical Point of Contact (TPOC) will work with the small business to obtain all clearances.

Work produced in Phase II may become classified. Note: The prospective contractor(s) must be U.S. owned and operated with no foreign influence as defined by DoD 5220.22-M, National Industrial Security Program Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Security Service (DSS). The selected contractor and/or subcontractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances, in order to perform on advanced phases of this project as set forth by DSS and NAVAIR in order to gain access to classified information pertaining to the national defense of the United States and its allies; this will be an inherent requirement. The selected company will be required to safeguard classified material IAW DoD 5220.22-M during the advanced phases of this contract.

PHASE I: Develop one or more applications for the electronic kneeboard. Provide documentation that demonstrates the suitability of the design into military platforms performing operational flights. Conceptual framework for DoN software development, testing, verification, and/or modification is required as well in order to demonstrate feasibility. A proof-of-concept demo and supporting documentation to demonstrate thoroughness of planning for next phase should be provided along with a Technology Readiness Level (TRL)/Manufacturing Readiness Level (MRL) assessment.

PHASE II: Further develop the applications for testing in a relevant environment, and demonstrate performance in a simulated or actual flight environment. Ensure the programming framework for DoN application development is completed and ready for testing. During this phase, performer should engage appropriate PMA, PEO, and/or appropriate contract support via the TPOC to discuss options for in-flight test in Navy aircraft. If this is cost- or time-prohibitive, testing in commercial or private aircraft is acceptable. Tests during this phase should demonstrate the superiority of the applications compared to the standard paper kneeboard currently used. Feasibility of aircraft/fighter integration should also be demonstrated. TRL/MRL assessment should be updated.

PHASE III DUAL USE APPLICATIONS: Transition the application software and programming framework into the F/A-18 platform by providing the apps and framework to appropriate testing-and-evaluation (T&E) programs. Contacts described in Phase II should be aware of technology by Phase III and providing in-flight T&E during Phase III. Concurrent with in-flight T&E, performer should develop commercialization plans for the private sector. Many of these applications would be useful in the private sector as iPads have been implemented into civilian/commercial aviation as well. The standardized DoN framework is modifiable and applicable to the private sector. Private/commercial platform emergency procedures or platform specific documentation transitioned to application format could be commercialized as well.

REFERENCES:

1. Martinez, W. L., & Martinez, A. R. (2012). Computational statistics handbook with MATLAB. CRC press

2. Zainon, W. M. N. W., Yee, W. S., Ling, C. S., & Yee, C. K. (2012). Exploring the Use of Cognitive Psychology Theory in Designing Effective GUI. IJEI: International Journal of Engineering and Industries, 3(3), 66-74

3. Palmer, S. (1999). Vision science: Photons to phenomenology. Cambridge, MA: The MIT Press

4. Eckstein, M. P. (2011). Visual search: A retrospective. Journal of Vision, 11(5), 14

5. Bi, X., Li, Y., & Zhai, S. (2013, April). FFitts law: modeling finger touch with fitts' law. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 1363-1372)

KEYWORDS: Electronic Kneeboard; Apple iPad; iOS; graphical user interface; cognitive psychology; software architecture

TPOC-1: 301-757-8490

TPOC-2: 301-757-6193

Questions may also be submitted through DoD SBIR/STTR SITIS website.

** TOPIC AUTHOR (TPOC) **

DoD Notice:   Between December 11, 2015 and January 10, 2016 you may talk directly with the Topic Authors (TPOC) to ask technical questions about the topics. Their contact information is listed above. For reasons of competitive fairness, direct communication between proposers and topic authors is not allowed starting January 11, 2016 , when DoD begins accepting proposals for this solicitation.

However, proposers may still submit written questions about solicitation topics through the DoD's SBIR/STTR Interactive Topic Information System (SITIS), in which the questioner and respondent remain anonymous and all questions and answers are posted electronically for general viewing until the solicitation closes. All proposers are advised to monitor SITIS (16.1 Q&A) during the solicitation period for questions and answers, and other significant information, relevant to the SBIR 16.1 topic under which they are proposing.

If you have general questions about DoD SBIR program, please contact the DoD SBIR Help Desk at 800-348-0787 or [email protected]