Skip to content
Inaccurate use of technical orders could lead to degradation of mission readiness, planning, and execution such as use of AME (alternate mission equipment), mission planning, and aircraft capabilities.like burning CDs, airport data transfers and external hard drive transfers, leading to frequent errors and potential failures such as incomplete technical order libraries or outdated technical orders.Some wings use their own non-standardized approach, complicating coordination and reducing reliability during active deployments.Technology can be used to automate and standardized processes that will eliminate human error and to give AMN time back. TODOsMaintenancePilotsQAUnit & Wing LeadershipOps & Test OpsMaintenance Group CCTODO > 10 MacBooks > Shop Sections > 322 iPadsNIPR-ETIMS (website) > Hard drive (or script to shared folder) > MacBook > iPadTODO > managing 322 iPads split between 32 sub accountsiPads upgraded to primary devices running ETIMS client iPads update overnight automatically using WiFi between 12pm and 4 am every day
We will run an experiment to omit WiFi on the flight line. We will install ETIMS Client on a few iPads to test the functionality and update capability.Sustainment costs for continuous use Legal constraints for communicationCredentialing for devices Training for use
We will test ETIMS Client on 5 iPads to test the functionality and update capability using automatic WiFi enabled updatesSustainment costs for continuous use (RDW in work with Comm) Legal constraints for communication(Comm approval for WiFi use)Training for use ( TODO’s and TODA’s to identify missed updates for sub accounts)
TO: Technical OrderTCTO: Time compliance technical order TODO: Technical order distribution officeTODA: Technical order distribution account ETIMS: Enhanced Technical Information Management SystemECA: External Certificate AuthorityFSA: Functional Systems Administrator
10/15📧 - Reached out to MSgt Jennifer Frisina (TODO FAM) , 2024; response received 16 Oct10/15📧 - TODOs for 189th MXG ; response received 16 Oct 10/15📞 - Frank Fontana - Buckley SFB - advised to seek feedback from the section shops; utilize AFTO FST SharePoint for guides and other resources 10/16📞📧 - Reached out to TSgt Scott Tinklenberg, 162nd W CS/SCXP via email and phone call for COMM’s Input regarding options for automated updates.(ideas are still in work)10/16📞📧 - Reached out to MSgt Thurston, 158th MXG and MSgt Alex Benckert 158th MXG via text and email to see what they are using for technical data. (legacy T.O.’s are on iPads and JTD is on tough books)10/18📞 - Spoke with TODO FAM11/03📧 Reached out to Britney Reed CIV AFMC 96 TW, Lt Col Plilip Downing AFMC 370 FLTS/ DO DFLT, and Cherie Head CIV AFMC 412 TW in regards to their Vision project for electronic flight bags.11/03📧 Reached out to Nazan Ogru USAFE 39 FSS, and Lynette Wright USAFE a589 in regards to Vision project 288411/05 reached out to TSgt Scott Tinklenberg, 162nd W CS/SCXP via email and phone call for COMM’s Input regarding options for automated updates.(ideas are still in work)11/06 Meeting with MX Group Commander, Col James Murphy to go over our problem statement and plan of action.
Used AppleScript to automate TO updates. Was able to transfer 800 of the 1300 TO files. Iterating on this pretotype may yield an automation solution that can save Emma one full day of work.Successfully ran complete auto-updates to iPads.
Why use iPads vs. another (possibly more ETIMS-co44-048234404823mpatible) system?
Laptops: Traditional laptops were considered, but they were often heavier and less portable than iPads.Tablets from Other Manufacturers: Various other tablet brands were evaluated, but iPads were found to have the best combination of performance, security, and user-friendliness.Specialized Handheld Devices: Devices specifically designed for military use were also considered, but they often lacked the versatility and ease of use provided by iPads.Is WiFi available in the IPad storage locations? Can WiFi be implemented on the flight line? What are the best known field practices?Is there any interest from other bases concerning this issue? Are there any units not using iPads? How does a unit identify the number of devices are required to meet operations. Is the number of iPads based on number of aircraft?Is there a more efficient way to mass delete technical orders from iPads?Do we have a way to autonomously load TO/TCTOs to tablets from ETIMS?
TODOs cannot mass delete outdated technical orders from iPads.TODO managers have guidance for how to complete TO and TCTO updates; however, technological constraints prevent many of them from completing the updates in a more efficient and accurate manner. Maintenance Commanders and Unit Technical Order Managers do not have autonomous process for managing the distribution of Technical Orders as evidenced by direct contact with other units.Utilizing the ACE concept on an operational base with multiple aircraft types do we have the capability to obtain technical orders at point of use to prevent mission degradation or mission failure?The lack of reliable network access prevents units from using the latest digital systems to quickly distribute technical orders, forcing reliance on outdated methods like CDs and external hard drives. This leads to critical delays, errors, and coordination issues, directly threatening aircraft readiness and mission success.
We will pitch this problem and solution to ARCWERX in Tucson.Keep record of process, interviews, etc.Team feedback
Team TODO Workspace
Working Problem
NEW STATEMENT: The lack of reliable network access prevents units from using the latest digital systems to quickly distribute technical orders, forcing reliance on outdated methods like CDs and external hard drives. This leads to critical delays, errors, and coordination issues, directly threatening aircraft readiness and mission success.
Examples (use-case):
Stakeholders/Beneficiaries:
Decision Makers:
Current Process Flows:
Desired Process Flow:
MUST - Most Uncertain Scenario Test (If (Action) > Then Outcome 1, 2, 3)
MUST # 2 - Most Uncertain Scenario Test (If (Action) > Then Outcome 1, 2, 3)
Files 🗂️
RE_ TODO Questions_189th.pdf229.7 kBRE_ TODO Questions_TODO FAM.pdf181.2 kBRE_ TODO Questions_189th_2.pdf234.3 kBRE_ EFBs for Fighter Aircraft.pdf202 kBVISION CONTACT_MSgt Borst.log278 B
Deployment Chklist ETOOL (1).pdf25.3 kB
Links 🔗
Acronyms:
Reference: TO: 31S5-4-ETOOL-1 (p.49)
Output & Attempts
Pretotypes
Questions❔
Before deciding on iPads, the Air Force considered several other devices for managing technical data. Some of the devices evaluated included:
Ultimately, iPads were chosen due to their lightweight design, ease of use, and the ability to support a wide range of applications and security measures.
Yes, but each building will need permissions granted (possible new network for this purpose )
Yes. It is a matter of funding. WiFi connectivity is only required in the iPad storage areas/docking stations.
ETIMS Client. WiFi connection required at docking station for updates. PKI certificates are required for each iPad, which will need to be renewed every 36 months. Reach out to Comm or research how to obtain the certificates. (update required on the process and its tests)
Our contacts would benefit from a less manual way to update. A few have noted interest but are limited by network issues
There are units using Microsoft tablets and GTACS
5 for each aircraft possessed, 2 for back-shop
This issue is resolved by the autonomous updates from ETIMS to iPads as primary devices.
Yes
Old problem statements:
Due-outs:
Standard Operating Procedure for Managing and Updating iPads with ETIMS Client
Purpose:
To establish a standard procedure for managing 322 iPads configured as primary devices running the ETIMS client, ensuring each device is updated automatically via WiFi to maintain operational readiness and reduce manual update requirements.
Scope:
This SOP applies to the Technical Order Distribution Office (TODO) responsible for managing and updating 322 iPads, divided across 32 sub-accounts. The procedure ensures efficient device management, consistent updates, and troubleshooting of any issues related to the ETIMS client.
Responsibilities:
• Technical Order Distribution Office (TODO): Responsible for overseeing the management, configuration, and updating of iPads. Ensures each device is assigned to the appropriate sub-account and verifies that updates are completed on schedule.
• Functional System Administrator (FSA): Supports configuration and troubleshooting of iPads when needed.
• Client Systems Technician (CST): Provides technical assistance, particularly for network-related issues.
Procedures:
1. Initial Setup and Configuration
• 1.1 Assign each iPad to one of the designated work centers.
• 1.2 Configure each iPad to be a primary device for running the ETIMS client.
• 1.3 Verify that each iPad has an established WiFi connection and is configured to update automatically.
2. Automatic Update Configuration
• 2.1 Set up each iPad to receive ETIMS client updates automatically every day between 12:00 am and 4:00 am.
• 2.2 Ensure the iPads are connected to a reliable WiFi network within the storage or docking location before the designated update time each day.
• 2.3 Regularly monitor network availability within iPad storage areas to ensure connectivity for overnight updates.
• 2.4 Confirm that each iPad’s time settings are accurate and synchronized to ensure update timing is consistent across devices.
3. Daily Check and Verification
• 3.1 Designate a responsible TODO staff member to verify that each iPad has completed its overnight update.
• 3.1.1 Perform spot-checks by reviewing update logs on a subset of iPads within each sub-account.
• 3.1.2 If updates fail on any iPads, attempt a manual update during off-peak hours (outside of the 12:00 am–4:00 am window).
• 3.2 Document any update issues or irregularities and report them to the FSA for further investigation.
4. Troubleshooting
• 4.1 If an iPad does not receive updates, check the WiFi connection and re-establish the network if needed.
• 4.2 Ensure the iPad is properly assigned to the correct sub-account and has appropriate permissions to receive ETIMS updates.
• 4.3 If issues persist, contact the CST for technical assistance and review potential network or device configuration issues.
5. Maintenance and Record-Keeping
• 5.1 Maintain a log of each iPad’s update history, including any failed updates, manual interventions, or configuration changes.
• 5.2 Every quarter, review and update the device list, ensuring each iPad is still in the correct sub-account and is operational.
• 5.3 Update certificates every 3 years and ensure device settings comply with cybersecurity requirements.
6. Annual Review
• 6.1 Perform an annual audit to assess the effectiveness of the update process and identify any areas for improvement.
• 6.2 Collect feedback from FSA, TODO, and CST personnel on any recurring issues or procedural adjustments needed.
Notes:
• Update Timing Considerations: The daily update period of 12:00 am to 4:00 am should not overlap with any scheduled network maintenance or testing.
• Device Storage Requirements: iPads should remain in designated storage areas overnight to ensure reliable access to WiFi.
—-———————————————-
Business Model Canvas for iPad Management with ETIMS Client Updates
1. Key Partners
• Technical Order Distribution Office (TODO): Responsible for the overall management and updating of all iPads.
• Functional System Administrators (FSA): Provides assistance with device setup, configuration, and troubleshooting.
• Client Systems Technicians (CST): Supports network and device troubleshooting for smooth update processes. Ensures all devices meet security standards and regulations. Ensures reliable connectivity in designated areas to facilitate nightly updates.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.