Skip to content
Team TODO Workspace
Employment Scenarios
Our problem statement highlights a critical challenge in military deployment conditions, where reliable network access is essential for the efficient operation of modern digital systems, especially for managing and distributing technical orders (TOs) and Time Compliance Technical Orders (TCTOs). Here’s how it relates to military deployment:
1. Network Access Challenges: In military operations, particularly in deployed environments (e.g., remote bases, on the flight line, or during field operations), access to reliable and secure network infrastructure is often limited or unavailable. This lack of connectivity hampers the real-time distribution of critical technical data and updates, which are necessary for maintaining and servicing aircraft and other assets.
2. Outdated Methods: When reliable network access is absent, military units resort to outdated methods, such as using CDs or external hard drives, to distribute technical orders. These methods are slow, prone to errors, and less secure. They cannot quickly accommodate the fast-paced, dynamic requirements of modern military operations, where information must be distributed across units and locations in real-time.
3. Delays and Errors: The reliance on outdated methods can lead to significant delays in updating technical orders and instructions, which directly impacts the maintenance of aircraft. If technicians or personnel do not receive the latest updates on time, they may perform incorrect procedures or miss vital maintenance actions, resulting in mechanical failures or safety risks.
4. Coordination Issues: Without reliable digital systems, coordination between various units (e.g., maintenance, logistics, and operations) becomes fragmented. Units may not be working with the most up-to-date information, leading to discrepancies, miscommunication, and ultimately the inability to synchronize efforts for mission success.
5. Impact on Aircraft Readiness and Mission Success: In a military context, aircraft readiness is crucial for operational success. Any delays in technical data distribution or errors in maintenance can reduce the effectiveness of aircraft, impacting their availability for missions. This can jeopardize mission success, especially in high-stakes, time-sensitive environments like combat or humanitarian operations.
In summary, the lack of reliable network access during military deployment directly undermines operational efficiency, introduces risks, and compromises the readiness of essential military assets, highlighting the importance of modernizing network infrastructure to support the rapid exchange of digital technical data.
Desired Process Flow:
TODO > managing 322 iPads split between 32 sub accounts
iPads upgraded to primary devices running ETIMS client
iPads update overnight automatically using WiFi between 12pm and 4 am every day
THE SCENARIO:
The 162nd Wing, 152nd & 195th Operations Units to include a mixed fleet from two aircraft maintenance units have been tasked to deploy to the Czech Republic for an exercise in line with NATO partners. The 195th and 152nd Aircraft Maintenance Units will prepare a total of 10 aircraft and facilitate support for a maximum of 60 flying days or 60 flight hours.
WHAT’S REQUIRED?
eTool Implementation Checklist
1. Timeline: 1-2 months before deployment
Responsible Party: TODO
Requirement: Request or register for an AF Center for Electronic Distribution of Systems (AFCEDS) account.
2. Timeline: 1-2 months before deployment
Responsible Party: TODO
IRequirement: Request Public Key Infrastructure (PKI) Certificate for all eTools designated as “Primary eTools” (refer to Paragraph 2.5).
3. Timeline: 1-2 months before deployment
Responsible Party: Client Systems Technician (CST)
Requirement: Ensure Organizational Units (OUs), security group, and Group Policy Object (GPO) have been created (refer to Chapter 1).
• Note: Failure to add eTools to required OUs and Security Groups can cause technical order download failures and prevent application of specific settings for eTools.
4. Timeline: Deployment
Responsible Party: CST
Requirement: Receive and configure eTools for network connection (refer to Paragraph 2.6).
• In Active Directory, add DSCC primary eTools to the Server OU.
• In Active Directory, add SDC eTools to the “ETOV” OU.
• In Active Directory, add SDC eTools to the “ETOV_eTools” Security Group.
5. Timeline: Deployment
Responsible Party: CST
Requirement: Configure eTool (Primary and/or Secondary) software (refer to Paragraph 2.6).
• Note: Unless absolutely necessary for mission requirements, avoid setting synchronization times between 0800 to 1600 Eastern Standard Time during configuration of the Primary eTool.
6. Timeline: Post Deployment
Responsible Party: TODO
Requirement: Reduce all subscription and on-hand quantities of paper books that are available digitally, as per MAJCOM requirements.
Additional Notes
• Certificate Expiry: PKI certificates for eTools expire 3 years from the issue date. It is essential to establish procedures to renew certificates well before expiration to prevent any lapse in primary eTool functionality.
QUESTION: Are the iPads currently being added to OU and Security Groups by Comm at homestation (as is required in deployed environment, step 3)?
In a forward-deployment environment —
A maintainer doesn’t recognize the associated TCTO for changing a tire on a specific aircraft.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.