Camotool - User contributions [en]

Not all the options in the menus

2026-05-21T09:53:11Z

Msugranyes:

= '''WHY AREN'T THERE ALL THE OPTIONS?''' =

 

*One of the key strengths of '''''CamoTool '''''lies in its high level of '''''modularity and customization'''''. We fully understand that no two aviation organizations operate in exactly the same way, and as such, our system has been built from the ground up to '''''adapt to your specific workflows, needs, and operational focus:'''''

 

*CamoTool is composed of '''''several modules''''' covering areas such as warehouse and inventory management, maintenance planning and execution, airworthiness tracking, CAMO management, invoicing, reporting, and more. However, '''''not all modules need to be visible or active by default'''''. In fact, we encourage our clients to start with only the modules that are essential to their daily operations. This approach keeps the user interface clean, intuitive, and tailored to the user’s immediate responsibilities:

 

*For example, if your current scope is limited to warehouse operations, we can configure the system so that only inventory-related features are visible to your team. Other modules, such as maintenance work orders or invoicing, can be '''''hidden in the background''''', reducing clutter and making it easier for users to navigate and focus on what matters most to them. For example some users probably not need the '''''accounting''''' section because is it managed by another company:

 

*Despite being hidden or inactive, these modules are still '''''fully integrated and available''''' in the system. You can request to activate additional modules at any point in time — whether that’s weeks or months down the line — without the need for complex reinstallation or configuration processes. Activating a new module is seamless and can be done remotely, allowing your operations to '''''scale and evolve naturally''''' as your needs grow or change:

 

*Moreover, the system allows for '''''role-based access control''''', so even within active modules, different users can see or access only the functionalities that are relevant to their role. This not only improves usability but also enhances data security and operational efficiency because you don't have all the data adn you have only acces to essential data:

 

*In summary, CamoTool is not a one-size-fits-all solution. It is a '''''scalable, customizable ERP platform '''''that grows with your organization, and gives you full control over which tools you use and when. Whether you're a small operation focused on logistics or a full-scale MRO/CAMO organization:

 

= '''CLEAR CACHE ON DIFERENTS BROWSERS''' =

Some tips to clear cache on the most populars browsers.

'''[[Browser_Extension|Via Browser Extension]]:'''

[[From_Chrome|'''Clear Cache on Google Chrome:''']]

[[From_Firefox|'''Clear Cache on Firefox:''']]

[[From_Safari|'''Clear Cache on Safari:''']]

[[From_Edge|'''Clear Cache on Microsoft Edge:''']]

Browser Extension

2026-05-21T09:52:51Z

Msugranyes:

= '''''BROWSER EXTENSION''''' =

To download the Camotool plugin, you need to go to the Google Chrome store and search for "Camotool".

[[File:Captura de pantalla 2026-05-21 115134.png]]

 

Once installed, go to the puzzle icon in your browser (top right) and click on the three dots and "Manage Extension". Now you need to paste the link of camotool. EX: https.//camotool.camotool.com.

[[File:Url.png|RTENOTITLE]]

 

After this you need to go to the puzzle icon click on the pluguin and "Clear Cache". 

[[File:Clear.png|RTENOTITLE]]

File:Captura de pantalla 2026-05-21 115134.png

2026-05-21T09:52:11Z

Msugranyes:

Browser Extension

2026-05-21T09:51:50Z

Msugranyes:

= BROWSER EXTENSION =

To download the Camotool plugin, you need to go to the Google Chrome store and search for "Camotool".

 

Once installed, go to the puzzle icon in your browser (top right) and click on the three dots and "Manage Extension". Now you need to paste the link of camotool. EX: https.//camotool.camotool.com.

[[File:Url.png|RTENOTITLE]]

After this you need to go to the puzzle icon click on the pluguin and "Clear Cache". 

[[File:Clear.png|RTENOTITLE]]

Browser Extension

2026-05-21T09:50:44Z

Msugranyes:

= BROWSER EXTENSION =

To download the Camotool plugin, you need to go to the Google Chrome store and search for "Camotool".

[[File:Camotool chrome.png]]

Once installed, go to the puzzle icon in your browser (top right) and click on the three dots and "Manage Extension". Now you need to paste the link of camotool. EX: https.//camotool.camotool.com.

[[File:Url.png]]

After this you need to go to the puzzle icon click on the pluguin and "Clear Cache". 

[[File:Clear.png]]

File:Url.png

2026-05-21T09:47:34Z

Msugranyes:

File:Clear.png

2026-05-21T09:47:12Z

Msugranyes:

File:Camotool chrome.png

2026-05-21T09:46:47Z

Msugranyes:

Not all the options in the menus

2026-05-21T09:46:26Z

Msugranyes:

= '''WHY AREN'T THERE ALL THE OPTIONS?''' =

 

*One of the key strengths of '''''CamoTool '''''lies in its high level of '''''modularity and customization'''''. We fully understand that no two aviation organizations operate in exactly the same way, and as such, our system has been built from the ground up to '''''adapt to your specific workflows, needs, and operational focus:'''''

 

*CamoTool is composed of '''''several modules''''' covering areas such as warehouse and inventory management, maintenance planning and execution, airworthiness tracking, CAMO management, invoicing, reporting, and more. However, '''''not all modules need to be visible or active by default'''''. In fact, we encourage our clients to start with only the modules that are essential to their daily operations. This approach keeps the user interface clean, intuitive, and tailored to the user’s immediate responsibilities:

 

*For example, if your current scope is limited to warehouse operations, we can configure the system so that only inventory-related features are visible to your team. Other modules, such as maintenance work orders or invoicing, can be '''''hidden in the background''''', reducing clutter and making it easier for users to navigate and focus on what matters most to them. For example some users probably not need the '''''accounting''''' section because is it managed by another company:

 

*Despite being hidden or inactive, these modules are still '''''fully integrated and available''''' in the system. You can request to activate additional modules at any point in time — whether that’s weeks or months down the line — without the need for complex reinstallation or configuration processes. Activating a new module is seamless and can be done remotely, allowing your operations to '''''scale and evolve naturally''''' as your needs grow or change:

 

*Moreover, the system allows for '''''role-based access control''''', so even within active modules, different users can see or access only the functionalities that are relevant to their role. This not only improves usability but also enhances data security and operational efficiency because you don't have all the data adn you have only acces to essential data:

 

*In summary, CamoTool is not a one-size-fits-all solution. It is a '''''scalable, customizable ERP platform '''''that grows with your organization, and gives you full control over which tools you use and when. Whether you're a small operation focused on logistics or a full-scale MRO/CAMO organization:

 

= '''CLEAR CACHE ON DIFERENTS BROWSERS''' =

Some tips to clear cache on the most populars browsers.

[[Browser_Extension|Via Browser Extension]]

[[From_Chrome|'''Clear Cache on Google Chrome:''']]

[[From_Firefox|'''Clear Cache on Firefox:''']]

[[From_Safari|'''Clear Cache on Safari:''']]

[[From_Edge|'''Clear Cache on Microsoft Edge:''']]

Browser Extension

2026-05-21T09:46:07Z

Msugranyes: Created page with " = BROWSER EXTENSION = To download the Camotool plugin, you need to go to the Google Chrome store and search for "Camotool".   Once installed, go to the puzzle icon in..."

= BROWSER EXTENSION =

To download the Camotool plugin, you need to go to the Google Chrome store and search for "Camotool".

 

Once installed, go to the puzzle icon in your browser (top right) and click on the three dots and "Manage Extension". Now you need to paste the link of camotool. EX: https.//camotool.camotool.com.

 

After this you need to go to the puzzle icon click on the pluguin and "Clear Cache". 

Not all the options in the menus

2026-05-21T09:38:59Z

Msugranyes:

= '''WHY AREN'T THERE ALL THE OPTIONS?''' =

 

*One of the key strengths of '''''CamoTool '''''lies in its high level of '''''modularity and customization'''''. We fully understand that no two aviation organizations operate in exactly the same way, and as such, our system has been built from the ground up to '''''adapt to your specific workflows, needs, and operational focus:'''''

 

*CamoTool is composed of '''''several modules''''' covering areas such as warehouse and inventory management, maintenance planning and execution, airworthiness tracking, CAMO management, invoicing, reporting, and more. However, '''''not all modules need to be visible or active by default'''''. In fact, we encourage our clients to start with only the modules that are essential to their daily operations. This approach keeps the user interface clean, intuitive, and tailored to the user’s immediate responsibilities:

 

*For example, if your current scope is limited to warehouse operations, we can configure the system so that only inventory-related features are visible to your team. Other modules, such as maintenance work orders or invoicing, can be '''''hidden in the background''''', reducing clutter and making it easier for users to navigate and focus on what matters most to them. For example some users probably not need the '''''accounting''''' section because is it managed by another company:

 

*Despite being hidden or inactive, these modules are still '''''fully integrated and available''''' in the system. You can request to activate additional modules at any point in time — whether that’s weeks or months down the line — without the need for complex reinstallation or configuration processes. Activating a new module is seamless and can be done remotely, allowing your operations to '''''scale and evolve naturally''''' as your needs grow or change:

 

*Moreover, the system allows for '''''role-based access control''''', so even within active modules, different users can see or access only the functionalities that are relevant to their role. This not only improves usability but also enhances data security and operational efficiency because you don't have all the data adn you have only acces to essential data:

 

*In summary, CamoTool is not a one-size-fits-all solution. It is a '''''scalable, customizable ERP platform '''''that grows with your organization, and gives you full control over which tools you use and when. Whether you're a small operation focused on logistics or a full-scale MRO/CAMO organization:

 

= '''CLEAR CACHE ON DIFERENTS BROWSERS''' =

Some tips to clear cache on the most populars browsers.

Via Browser Extension

[[From_Chrome|'''Clear Cache on Google Chrome:''']]

[[From_Firefox|'''Clear Cache on Firefox:''']]

[[From_Safari|'''Clear Cache on Safari:''']]

[[From_Edge|'''Clear Cache on Microsoft Edge:''']]

Calibrated Tools

2026-05-21T09:01:28Z

Msugranyes:

= Calibrated Tools Window =

== Left Panel — Tools List ==

The left side displays all registered calibrated tools.

Each item shows:

*'''Tool name'''
**Example: ''Manometro Ruedas 0-12 Bar''
*'''Remaining time before calibration expires'''
**Example: <code data-end="488" data-start="481">-84 m</code>
*'''Serial Number (SN)'''
*'''Location / Store'''
**Example: <code data-end="560" data-start="550">(HUESCA)</code>
*'''Status'''
**Example: <code data-end="595" data-start="587">Active</code>

=== Features ===

You can:

*Search tools by:
**Part Number (P/N)
**Name
**Serial Number
*Add a new calibrated tool using the '''+ button'''
*Navigate or import/export records

----

= General Information Section =

This area contains the basic information of the selected tool.

== Fields ==

=== Spare Id ===

Internal identifier for the tool.

=== Part Number ===

Manufacturer or internal part number.

=== Serial Number ===

Unique serial number of the equipment.

=== Active ===

Checkbox indicating whether the tool is active.

----

= Part Rule TBO (Time Between Overhaul / Calibration) =

This section defines calibration intervals and alert rules.

== TBO Type ==

Defines the calibration recurrence type.

Example:

*<code data-end="1316" data-start="1293">Months/Days recurring</code>

== TBO Value ==

Calibration interval value.

Example:

*<code data-end="1375" data-start="1371">12</code>

== TBO Unit ==

Unit of time.

Example:

*<code data-end="1418" data-start="1415">m</code> → months

This means:
<blockquote data-end="1483" data-start="1441">
Calibration is required every 12 months.
</blockquote>
----

= Alert Configuration =

The system can generate warning notifications before calibration expires.

== First Alert ==

Example: <code data-end="1615" data-start="1612">2</code>

*First warning 2 months before expiration.

== Second Alert ==

Example: <code data-end="1689" data-start="1686">1</code>

*Second warning 1 month before expiration.

== Third Alert ==

Example: <code data-end="1764" data-start="1759">0.5</code>

*Final warning 15 days before expiration.

----

= Calibration Information =

Tracks calibration dates.

== Last Calibration ==

Date when the tool was last calibrated.

== Next Due Calibration ==

Automatically calculated next calibration date.

 

[[File:New cal tool.png]]

Main Page

2026-05-21T09:00:50Z

Msugranyes:

== '''''INTRODUCTION TO CAMOTOOL:''''' ==

- '''Camotool''' is a modern and intuitive platform designed to simplify and optimize '''''aircraft management'''.'' It supports operators, CAMO ('''Continuing Airworthiness Management Organization''') teams, and aviation professionals in tracking airworthiness, maintenance schedules, compliance records, and technical documentation all in one centralized system.

 

- Whether you're managing a single aircraft or an entire fleet, Camotool helps ensure regulatory compliance, improves operational efficiency, and reduces administrative workload.

 

- This wiki contains all the essential documentation, including setup instructions, feature guides, troubleshooting tips, and best practices to help you make the most of Camotool.

 
'''[[AIRWORTHINES|AIRWORTHINES]]          [[MAINTENANCE|MAINTENANCE]]          [[WAREHOUSE|WAREHOUSE]]          [[INVOICE|INVOICE]]          [[ACCOUNTING|ACCOUNTING]]''' [[Not_all_the_options_in_the_menus|'''MISCELLANEOUS''']]
'''''ABOUT TBOS:'''''

[[How_To_Add,_Modify_or_Delete_TBOS|How to Add, Modify or Remove TBOS]]:

 

'''''HOW TO ADD NEW PARTS ON A NEW AIRCRAFT:'''''

[[New_Part_On_a_New_Aircraft|New Part On a New Aircraft]]:

 

'''''TOP BAR MENU:'''''

 [[Aircraft_models|Aircraft models]] ---- [[Parts|Parts]] ---- [[Manufactured_Parts|Manufactured Parts]] ---- [[Form_One|Form One]] ---- [[Rules|Rules]] ---- [[Work_Orders|Work Orders]] ---- [[Documents|Documents]]   

  ---- [[Roles|Roles]] ---- [[Quotations|Quotations]] ---- [[Purchase_Orders|Purchase Orders]] ---- [[How_to_create_the_Aircraft|How to create the Aircraft]]  ---- [[Providers|Providers]]

 

'''''LEFT SIDE MENU:'''''

 [[Administration|Administration]] ---- [[Bussines_Management|Bussines Management]] ---- [[Documents_Section|Documents Section]] ---- [[Maintenance_forecast|Maintenance forecast]] 

 [[Work_Order_Menu|Work Order Menu]]  

'''''EXTRA INFORMATION'''''

[[How_to_replace_parts|How to replace parts]] ---- [[The_things_inside_an_airplane|The things inside an airplane]]

 

'''''CALIBRATED TOOLS:'''''

[[Calibrated_Tools|Calibrated_Tools]]

Main Page

2026-05-21T08:59:23Z

Msugranyes:

File:New cal tool.png

2026-05-21T08:58:22Z

Msugranyes:

Calibrated Tools

2026-05-21T08:57:05Z

Msugranyes: Created page with " = Calibrated Tools Window = == Left Panel — Tools List == The left side displays all registered calibrated tools. Each item shows: *'''Tool name''' **Example: ''Manome..."

Main Page

2026-05-21T08:53:12Z

Msugranyes:

Main Page

2026-05-18T08:48:24Z

Msugranyes:

INVOICE

2026-05-04T09:26:58Z

Msugranyes:

'''INVOICE'''

'''''CUSTOMERS:'''''

The '''Customers''' menu is a navigation item in the main toolbar of the application. When hovered over or clicked, it reveals a dropdown menu with three distinct options:

'''Menu Options:'''

'''''List Customers:'''''

'''- Function''': Displays a comprehensive list of all customers currently stored in the system.

'''- Use Case''': Ideal for browsing or managing existing customer records.

 

'''''Add Customers:'''''

'''- Function''': Opens a form or interface to add a new customer to the database.

'''- Use Case''': Used when onboarding a new customer or inputting a new entry manually.

 

'''''Search Customers:'''''

'''- Function''': Allows users to search for specific customers using filters or keywords.

'''- Use Case''': Useful for quickly locating a particular customer without scrolling through the full list.

 

At Camotool, the application provides the capability to create and manage users directly from within the platform, streamlining administrative tasks and improving user management efficiency.

To access this feature, begin by logging in with your assigned username and password. Once authenticated, you will be directed to the main dashboard. At the top navigation bar, you will find a dropdown menu labeled '''"Users"'''. When you hover over this menu, a set of three options will appear:

'''- List Users''': View a complete list of all existing users in the system.

'''- Add User''': Initiate the process of creating a new user.

'''- Search Users''': Locate a specific user based on search criteria.

 

[[File:2025-07-21 08 09 32-.png|RTENOTITLE]]

 

To create a new user, select the '''"Add User"''' option. This will open a user creation form where you can enter relevant details. The form includes various fields such as username, email address, password, user role, and other profile-related information. Some of these fields are mandatory and must be completed before proceeding:

Once all the necessary information has been entered, click the '''"Save"''' button to finalize the creation of the new user account. Upon successful creation, the user will be added to the system and will appear in the user list. You can then proceed to assign permissions or roles as needed, depending on your organization’s access control policies.

[[File:User.png|RTENOTITLE]]

This built-in feature allows administrators to efficiently manage user access and maintain control over who can use the application, ensuring a secure and organized workflow within Camotool.

 

'''''HOW LOOKS A USER:'''''

[[File:Howlooksuser.png|RTENOTITLE]]

MAINTENANCE

2026-05-04T09:13:25Z

Msugranyes:

'''MAINTENANCE'''

== '''''What is “maintenance” in aviation?''''' ==

Aircraft maintenance is the combination of inspection, servicing, repair, and overhaul activities carried out on an aircraft and its components. These tasks are performed according to strict regulations established by aviation authorities to guarantee safety and reliability.

== '''''Main types of maintenance:''''' ==

'''Preventive maintenance:''' This is scheduled maintenance performed at regular intervals to prevent failures before they occur. It includes routine inspections, lubrication, and replacement of life-limited parts.

'''Corrective maintenance:''' This is performed when a fault or malfunction is detected. It involves troubleshooting, repairing, or replacing defective components.

'''Predictive maintenance:''' This type is based on data analysis and monitoring systems to detect early signs of wear or failure. It helps reduce unexpected breakdowns and improve maintenance planning.

 

== '''''Maintenance levels:''''' ==

'''''Aircraft maintenance is also divided into different levels:'''''

'''Line maintenance:''' Light and frequent checks carried out before or between flights, such as visual inspections and fluid checks.

'''Base maintenance:''' More detailed and time-consuming work performed in hangars, including structural inspections and major repairs.

'''Common maintenance checks include:'''

A-check (light and frequent).

B-check (moderate, less common).

C-check (deep inspection).

D-check (major overhaul or heavy maintenance).

 

== '''''Areas involved in maintenance:''''' ==

'''''Maintenance covers all major aircraft systems, including:'''''

 -Engines.

- Avionics (navigation and communication systems).

- Airframe (structure, wings, fuselage).

- Hydraulic and pneumatic systems.

- Landing gear and braking systems.

 

== '''''Regulations and standards:''''' ==

Aircraft maintenance must comply with strict international regulations set by authorities such as the Federal Aviation Administration (FAA) and the European Union Aviation Safety Agency (EASA). These organizations define maintenance procedures, inspection intervals, and certification requirements.

== '''''Main objectives:''''' ==

'''''The main goals of aviation maintenance are:'''''

To ensure flight safety.

To maintain reliability and performance.

To extend the aircraft’s service life.

To comply with international aviation regulations.

 

== '''''Summary:''''' ==

Aircraft maintenance is a fundamental part of aviation that ensures every aircraft is safe, reliable, and ready to operate through continuous inspection, repair, and monitoring.

MAINTENANCE

2026-05-04T09:12:42Z

Msugranyes:

'''MAINTENANCE'''

== '''''What is “maintenance” in aviation?''''' ==

Aircraft maintenance is the combination of inspection, servicing, repair, and overhaul activities carried out on an aircraft and its components. These tasks are performed according to strict regulations established by aviation authorities to guarantee safety and reliability.

== '''''Main types of maintenance:''''' ==

'''Preventive maintenance:''' This is scheduled maintenance performed at regular intervals to prevent failures before they occur. It includes routine inspections, lubrication, and replacement of life-limited parts.

'''Corrective maintenance:''' This is performed when a fault or malfunction is detected. It involves troubleshooting, repairing, or replacing defective components.

'''Predictive maintenance:''' This type is based on data analysis and monitoring systems to detect early signs of wear or failure. It helps reduce unexpected breakdowns and improve maintenance planning.

 

== '''''Maintenance levels:''''' ==

Aircraft maintenance is also divided into different levels:

'''Line maintenance:''' Light and frequent checks carried out before or between flights, such as visual inspections and fluid checks.

'''Base maintenance:''' More detailed and time-consuming work performed in hangars, including structural inspections and major repairs.

'''Common maintenance checks include:'''

A-check (light and frequent).

B-check (moderate, less common).

C-check (deep inspection).

D-check (major overhaul or heavy maintenance).

 

== '''''Areas involved in maintenance:''''' ==

Maintenance covers all major aircraft systems, including:

 -Engines.

- Avionics (navigation and communication systems).

- Airframe (structure, wings, fuselage).

- Hydraulic and pneumatic systems.

- Landing gear and braking systems.

 

== '''''Regulations and standards:''''' ==

Aircraft maintenance must comply with strict international regulations set by authorities such as the Federal Aviation Administration (FAA) and the European Union Aviation Safety Agency (EASA). These organizations define maintenance procedures, inspection intervals, and certification requirements.

== '''''Main objectives:''''' ==

'''''The main goals of aviation maintenance are:'''''

To ensure flight safety.

To maintain reliability and performance.

To extend the aircraft’s service life.

To comply with international aviation regulations.

 

== '''''Summary:''''' ==

Aircraft maintenance is a fundamental part of aviation that ensures every aircraft is safe, reliable, and ready to operate through continuous inspection, repair, and monitoring.

MAINTENANCE

2026-05-04T08:59:48Z

Msugranyes:

'''MAINTENANCE'''

== '''''What is “maintenance” in aviation?''''' ==

Aircraft maintenance is the combination of inspection, servicing, repair, and overhaul activities carried out on an aircraft and its components. These tasks are performed according to strict regulations established by aviation authorities to guarantee safety and reliability.

== '''''Main types of maintenance:''''' ==

'''Preventive maintenance''' This is scheduled maintenance performed at regular intervals to prevent failures before they occur. It includes routine inspections, lubrication, and replacement of life-limited parts.

'''Corrective maintenance''' This is performed when a fault or malfunction is detected. It involves troubleshooting, repairing, or replacing defective components.

'''Predictive maintenance''' This type is based on data analysis and monitoring systems to detect early signs of wear or failure. It helps reduce unexpected breakdowns and improve maintenance planning.

 

== '''''Maintenance levels:''''' ==

Aircraft maintenance is also divided into different levels:

'''Line maintenance:''' Light and frequent checks carried out before or between flights, such as visual inspections and fluid checks.

'''Base maintenance:''' More detailed and time-consuming work performed in hangars, including structural inspections and major repairs.

'''Common maintenance checks include:'''

A-check (light and frequent)

B-check (moderate, less common)

C-check (deep inspection)

D-check (major overhaul or heavy maintenance)

 

== '''''Areas involved in maintenance:''''' ==

Maintenance covers all major aircraft systems, including:

 -Engines.

- Avionics (navigation and communication systems).

- Airframe (structure, wings, fuselage).

- Hydraulic and pneumatic systems.

- Landing gear and braking systems.

 

== '''''Regulations and standards:''''' ==

Aircraft maintenance must comply with strict international regulations set by authorities such as the Federal Aviation Administration (FAA) and the European Union Aviation Safety Agency (EASA). These organizations define maintenance procedures, inspection intervals, and certification requirements.

== '''''Main objectives:''''' ==

The main goals of aviation maintenance are:

To ensure flight safety.

To maintain reliability and performance.

To extend the aircraft’s service life.

To comply with international aviation regulations.

 

== '''''Summary:''''' ==

Aircraft maintenance is a fundamental part of aviation that ensures every aircraft is safe, reliable, and ready to operate through continuous inspection, repair, and monitoring.

Not all the options in the menus

2026-05-04T08:56:45Z

Msugranyes:

= '''WHY AREN'T THERE ALL THE OPTIONS?''' =

 

*One of the key strengths of '''''CamoTool '''''lies in its high level of '''''modularity and customization'''''. We fully understand that no two aviation organizations operate in exactly the same way, and as such, our system has been built from the ground up to '''''adapt to your specific workflows, needs, and operational focus:'''''

 

*CamoTool is composed of '''''several modules''''' covering areas such as warehouse and inventory management, maintenance planning and execution, airworthiness tracking, CAMO management, invoicing, reporting, and more. However, '''''not all modules need to be visible or active by default'''''. In fact, we encourage our clients to start with only the modules that are essential to their daily operations. This approach keeps the user interface clean, intuitive, and tailored to the user’s immediate responsibilities:

 

*For example, if your current scope is limited to warehouse operations, we can configure the system so that only inventory-related features are visible to your team. Other modules, such as maintenance work orders or invoicing, can be '''''hidden in the background''''', reducing clutter and making it easier for users to navigate and focus on what matters most to them. For example some users probably not need the '''''accounting''''' section because is it managed by another company:

 

*Despite being hidden or inactive, these modules are still '''''fully integrated and available''''' in the system. You can request to activate additional modules at any point in time — whether that’s weeks or months down the line — without the need for complex reinstallation or configuration processes. Activating a new module is seamless and can be done remotely, allowing your operations to '''''scale and evolve naturally''''' as your needs grow or change:

 

*Moreover, the system allows for '''''role-based access control''''', so even within active modules, different users can see or access only the functionalities that are relevant to their role. This not only improves usability but also enhances data security and operational efficiency because you don't have all the data adn you have only acces to essential data:

 

*In summary, CamoTool is not a one-size-fits-all solution. It is a '''''scalable, customizable ERP platform '''''that grows with your organization, and gives you full control over which tools you use and when. Whether you're a small operation focused on logistics or a full-scale MRO/CAMO organization:

 

= '''CLEAR CACHE ON DIFERENTS BROWSERS''' =

Some tips to clear cache on the most populars browsers.

[[From_Chrome|'''Clear Cache on Google Chrome:''']]

[[From_Firefox|'''Clear Cache on Firefox:''']]

[[From_Safari|'''Clear Cache on Safari:''']]

[[From_Edge|'''Clear Cache on Microsoft Edge:''']]

New Part On a New Aircraft

2026-05-04T08:55:43Z

Msugranyes:

= '''''New Part On a New Aircraft:''''' =

Within the '''Aircraft Parts''' module, the system provides functionality to '''install (add) a component to the aircraft configuration''', ensuring full traceability and alignment with maintenance and airworthiness requirements.

When initiating the action to add a part, a modal dialog titled ''“Part into aircraft”'' is displayed. This dialog defines two distinct workflows for associating a component with the aircraft:

=== '''1. From Store (Inventory-based installation)''' ===

This option allows the user to '''select an existing part record from the inventory (store)''' and assign it to the aircraft. Technically, this implies:

*The part already exists as a '''serialized or batch-controlled inventory item''' within the system.
*All relevant metadata (e.g., '''Part Number, Serial Number, Manufacturer, configuration attributes''') is already defined.
*The system maintains '''traceability''', including stock location, previous installations (if applicable), and lifecycle status.
*Upon installation, the component is '''linked to the aircraft configuration''', and its status transitions from ''in stock'' to ''installed''.
*Any associated '''maintenance rules, life limits, or inspection programs''' are automatically inherited and activated for that aircraft.

This workflow is typically used for controlled components that are managed through logistics, repair cycles, or rotational pools.

=== '''2. New (Direct creation and installation)''' ===

This option enables the user to '''create a completely new part record at the moment of installation''', without relying on pre-existing inventory data. In this case:

*The user must manually define all required attributes, such as:
**Part Number
**Serial Number (if applicable)
**Manufacturer
**ATA Chapter classification
**Configuration or positional data
*The part is immediately '''instantiated and bound to the aircraft''' as an installed component.
*This approach is useful for:
**Components not previously registered in the system
**Non-serialized parts or ad-hoc entries
**Initial aircraft configuration setups or data migration scenarios

=== '''3. Additional considerations''' ===

*Once installed, the part becomes part of the '''aircraft configuration baseline''', contributing to its technical status.
*The system may trigger or associate '''continuing airworthiness requirements''', such as:
**Life limits (e.g., hours, cycles, calendar time).
**Scheduled inspections.
**Airworthiness directives or service bulletins.
*Installation events are typically '''timestamped''' and may be audited for regulatory compliance.

- In summary, the interface supports both '''inventory-driven installation (controlled, traceable parts)''' and '''on-the-fly creation (flexible, manual entry)''', allowing the system to accommodate a wide range of operational and maintenance scenarios.

Also you can see the related rules of the specific part.

 

= [[File:Addpart.png|RTENOTITLE]] =

New Part On a New Aircraft

2026-05-04T08:23:23Z

Msugranyes:

= '''''New Part On a New Aircraft:''''' =

Within the '''Aircraft Parts''' module, the system provides functionality to '''install (add) a component to the aircraft configuration''', ensuring full traceability and alignment with maintenance and airworthiness requirements.

When initiating the action to add a part, a modal dialog titled ''“Part into aircraft”'' is displayed. This dialog defines two distinct workflows for associating a component with the aircraft:

=== '''1. From Store (Inventory-based installation)''' ===

This option allows the user to '''select an existing part record from the inventory (store)''' and assign it to the aircraft. Technically, this implies:

*The part already exists as a '''serialized or batch-controlled inventory item''' within the system.
*All relevant metadata (e.g., '''Part Number, Serial Number, Manufacturer, configuration attributes''') is already defined.
*The system maintains '''traceability''', including stock location, previous installations (if applicable), and lifecycle status.
*Upon installation, the component is '''linked to the aircraft configuration''', and its status transitions from ''in stock'' to ''installed''.
*Any associated '''maintenance rules, life limits, or inspection programs''' are automatically inherited and activated for that aircraft context.

This workflow is typically used for controlled components that are managed through logistics, repair cycles, or rotational pools.

=== '''2. New (Direct creation and installation)''' ===

This option enables the user to '''create a completely new part record at the moment of installation''', without relying on pre-existing inventory data. In this case:

*The user must manually define all required attributes, such as:
**Part Number
**Serial Number (if applicable)
**Manufacturer
**ATA Chapter classification
**Configuration or positional data
*The part is immediately '''instantiated and bound to the aircraft''' as an installed component.
*This approach is useful for:
**Components not previously registered in the system
**Non-serialized parts or ad-hoc entries
**Initial aircraft configuration setups or data migration scenarios

=== '''3. Additional considerations''' ===

*Once installed, the part becomes part of the '''aircraft configuration baseline''', contributing to its technical status.
*The system may trigger or associate '''continuing airworthiness requirements''', such as:
**Life limits (e.g., hours, cycles, calendar time)
**Scheduled inspections
**Airworthiness directives or service bulletins
*Installation events are typically '''timestamped''' and may be audited for regulatory compliance.

- In summary, the interface supports both '''inventory-driven installation (controlled, traceable parts)''' and '''on-the-fly creation (flexible, manual entry)''', allowing the system to accommodate a wide range of operational and maintenance scenarios.

 

= [[File:Addpart.png|RTENOTITLE]] =

New Part On a New Aircraft

2026-05-04T08:23:05Z

Msugranyes:

= '''''New Part On a New Aircraft:''''' =

Within the '''Aircraft Parts''' module, the system provides functionality to '''install (add) a component to the aircraft configuration''', ensuring full traceability and alignment with maintenance and airworthiness requirements.

When initiating the action to add a part, a modal dialog titled ''“Part into aircraft”'' is displayed. This dialog defines two distinct workflows for associating a component with the aircraft:

=== '''1. From Store (Inventory-based installation)''' ===

This option allows the user to '''select an existing part record from the inventory (store)''' and assign it to the aircraft. Technically, this implies:

*The part already exists as a '''serialized or batch-controlled inventory item''' within the system.
*All relevant metadata (e.g., '''Part Number, Serial Number, Manufacturer, configuration attributes''') is already defined.
*The system maintains '''traceability''', including stock location, previous installations (if applicable), and lifecycle status.
*Upon installation, the component is '''linked to the aircraft configuration''', and its status transitions from ''in stock'' to ''installed''.
*Any associated '''maintenance rules, life limits, or inspection programs''' are automatically inherited and activated for that aircraft context.

This workflow is typically used for controlled components that are managed through logistics, repair cycles, or rotational pools.

=== '''2. New (Direct creation and installation)''' ===

This option enables the user to '''create a completely new part record at the moment of installation''', without relying on pre-existing inventory data. In this case:

*The user must manually define all required attributes, such as:
**Part Number
**Serial Number (if applicable)
**Manufacturer
**ATA Chapter classification
**Configuration or positional data
*The part is immediately '''instantiated and bound to the aircraft''' as an installed component.
*This approach is useful for:
**Components not previously registered in the system
**Non-serialized parts or ad-hoc entries
**Initial aircraft configuration setups or data migration scenarios

=== '''Additional considerations''' ===

*Once installed, the part becomes part of the '''aircraft configuration baseline''', contributing to its technical status.
*The system may trigger or associate '''continuing airworthiness requirements''', such as:
**Life limits (e.g., hours, cycles, calendar time)
**Scheduled inspections
**Airworthiness directives or service bulletins
*Installation events are typically '''timestamped''' and may be audited for regulatory compliance.

- In summary, the interface supports both '''inventory-driven installation (controlled, traceable parts)''' and '''on-the-fly creation (flexible, manual entry)''', allowing the system to accommodate a wide range of operational and maintenance scenarios.

 

= [[File:Addpart.png|RTENOTITLE]] =

New Part On a New Aircraft

2026-05-04T08:22:47Z

Msugranyes:

= '''''New Part On a New Aircraft:''''' =

Within the '''Aircraft Parts''' module, the system provides functionality to '''install (add) a component to the aircraft configuration''', ensuring full traceability and alignment with maintenance and airworthiness requirements.

When initiating the action to add a part, a modal dialog titled ''“Part into aircraft”'' is displayed. This dialog defines two distinct workflows for associating a component with the aircraft:

=== '''1. From Store (Inventory-based installation)''' ===

This option allows the user to '''select an existing part record from the inventory (store)''' and assign it to the aircraft. Technically, this implies:

*The part already exists as a '''serialized or batch-controlled inventory item''' within the system.
*All relevant metadata (e.g., '''Part Number, Serial Number, Manufacturer, configuration attributes''') is already defined.
*The system maintains '''traceability''', including stock location, previous installations (if applicable), and lifecycle status.
*Upon installation, the component is '''linked to the aircraft configuration''', and its status transitions from ''in stock'' to ''installed''.
*Any associated '''maintenance rules, life limits, or inspection programs''' are automatically inherited and activated for that aircraft context.

This workflow is typically used for controlled components that are managed through logistics, repair cycles, or rotational pools.

=== '''2. New (Direct creation and installation)''' ===

This option enables the user to '''create a completely new part record at the moment of installation''', without relying on pre-existing inventory data. In this case:

*The user must manually define all required attributes, such as:
**Part Number
**Serial Number (if applicable)
**Manufacturer
**ATA Chapter classification
**Configuration or positional data
*The part is immediately '''instantiated and bound to the aircraft''' as an installed component.
*This approach is useful for:
**Components not previously registered in the system
**Non-serialized parts or ad-hoc entries
**Initial aircraft configuration setups or data migration scenarios

=== '''Additional considerations''' ===

*Once installed, the part becomes part of the '''aircraft configuration baseline''', contributing to its technical status.
*The system may trigger or associate '''continuing airworthiness requirements''', such as:
**Life limits (e.g., hours, cycles, calendar time)
**Scheduled inspections
**Airworthiness directives or service bulletins
*Installation events are typically '''timestamped''' and may be audited for regulatory compliance.

In summary, the interface supports both '''inventory-driven installation (controlled, traceable parts)''' and '''on-the-fly creation (flexible, manual entry)''', allowing the system to accommodate a wide range of operational and maintenance scenarios.

 

= [[File:Addpart.png|RTENOTITLE]] =

New Part On a New Aircraft

2026-05-04T08:16:44Z

Msugranyes:

= '''''New Part On a New Aircraft:''''' =

Within the '''Aircraft Parts''' module, the system provides functionality to '''install (add) a component to the aircraft configuration''', ensuring full traceability and alignment with maintenance and airworthiness requirements.

When initiating the action to add a part, a modal dialog titled ''“Part into aircraft”'' is displayed. This dialog defines two distinct workflows for associating a component with the aircraft:

=== '''1. From Store (Inventory-based installation)''' ===

This option allows the user to '''select an existing part record from the inventory (store)''' and assign it to the aircraft. Technically, this implies:

*The part already exists as a '''serialized or batch-controlled inventory item''' within the system.
*All relevant metadata (e.g., '''Part Number, Serial Number, Manufacturer, configuration attributes''') is already defined.
*The system maintains '''traceability''', including stock location, previous installations (if applicable), and lifecycle status.
*Upon installation, the component is '''linked to the aircraft configuration''', and its status transitions from ''in stock'' to ''installed''.
*Any associated '''maintenance rules, life limits, or inspection programs''' are automatically inherited and activated for that aircraft context.

This workflow is typically used for controlled components that are managed through logistics, repair cycles, or rotational pools.

=== '''2. New (Direct creation and installation)''' ===

This option enables the user to '''create a completely new part record at the moment of installation''', without relying on pre-existing inventory data. In this case:

*The user must manually define all required attributes, such as:
**Part Number
**Serial Number (if applicable)
**Manufacturer
**ATA Chapter classification
**Configuration or positional data
*The part is immediately '''instantiated and bound to the aircraft''' as an installed component.
*This approach is useful for:
**Components not previously registered in the system
**Non-serialized parts or ad-hoc entries
**Initial aircraft configuration setups or data migration scenarios

=== '''Additional considerations''' ===

*Once installed, the part becomes part of the '''aircraft configuration baseline''', contributing to its technical status.
*The system may trigger or associate '''continuing airworthiness requirements''', such as:
**Life limits (e.g., hours, cycles, calendar time)
**Scheduled inspections
**Airworthiness directives or service bulletins
*Installation events are typically '''timestamped''' and may be audited for regulatory compliance.

In summary, the interface supports both '''inventory-driven installation (controlled, traceable parts)''' and '''on-the-fly creation (flexible, manual entry)''', allowing the system to accommodate a wide range of operational and maintenance scenarios.

= [[File:Addpart.png|RTENOTITLE]] =

New Part On a New Aircraft

2026-05-04T08:02:53Z

Msugranyes:

= '''''New Part On a New Aircraft:''''' =

Within the '''Aircraft Parts''' module, the system provides functionality to '''install (add) a component to the aircraft configuration''', ensuring full traceability and alignment with maintenance and airworthiness requirements.

When initiating the action to add a part, a modal dialog titled ''“Part into aircraft”'' is displayed. This dialog defines two distinct workflows for associating a component with the aircraft:

=== 1. From Store (Inventory-based installation) ===

This option allows the user to '''select an existing part record from the inventory (store)''' and assign it to the aircraft. Technically, this implies:

*The part already exists as a '''serialized or batch-controlled inventory item''' within the system.
*All relevant metadata (e.g., '''Part Number, Serial Number, Manufacturer, configuration attributes''') is already defined.
*The system maintains '''traceability''', including stock location, previous installations (if applicable), and lifecycle status.
*Upon installation, the component is '''linked to the aircraft configuration''', and its status transitions from ''in stock'' to ''installed''.
*Any associated '''maintenance rules, life limits, or inspection programs''' are automatically inherited and activated for that aircraft context.

This workflow is typically used for controlled components that are managed through logistics, repair cycles, or rotational pools.

=== 2. New (Direct creation and installation) ===

This option enables the user to '''create a completely new part record at the moment of installation''', without relying on pre-existing inventory data. In this case:

*The user must manually define all required attributes, such as:
**Part Number
**Serial Number (if applicable)
**Manufacturer
**ATA Chapter classification
**Configuration or positional data
*The part is immediately '''instantiated and bound to the aircraft''' as an installed component.
*This approach is useful for:
**Components not previously registered in the system
**Non-serialized parts or ad-hoc entries
**Initial aircraft configuration setups or data migration scenarios

=== Additional considerations ===

*Once installed, the part becomes part of the '''aircraft configuration baseline''', contributing to its technical status.
*The system may trigger or associate '''continuing airworthiness requirements''', such as:
**Life limits (e.g., hours, cycles, calendar time)
**Scheduled inspections
**Airworthiness directives or service bulletins
*Installation events are typically '''timestamped''' and may be audited for regulatory compliance.

In summary, the interface supports both '''inventory-driven installation (controlled, traceable parts)''' and '''on-the-fly creation (flexible, manual entry)''', allowing the system to accommodate a wide range of operational and maintenance scenarios.

= [[File:Addpart.png|RTENOTITLE]] =

How To Add, Modify or Delete TBOS

2026-05-04T07:59:19Z

Msugranyes:

= TBOS. =

With '''Camotool''', you can easily manage '''TBOS''' by '''adding, modifying, or deleting entries'''. The tool allows you to create new TBOS records, update existing configurations, and remove those that are no longer needed, helping keep the system '''organized and up to date'''.

 

'''1 STEP:'''

The image shows the '''maintenance rules table''', where different tasks and their related information are displayed, such as the '''performed date''', '''last due date''', '''tolerance''', '''next due date''', and the '''TBOS value''' associated with each rule.

Each row represents a specific maintenance rule. In the example, the rule ''“Check calibration of airspeed indicator and altimeter”'' is shown together with its maintenance data. The '''TBOS column''' indicates the time between overhauls or scheduled maintenance for that rule.

To access and manage the '''TBOS information''', you must first open the performed rule window. To do this:

Locate the maintenance rule you want to review in the table and move the display to the right.

'''Right-click on the row of that rule.'''

A context menu will appear:

'''Click on “View performed rule".'''

This action opens the '''performed rule window''', where you can access the detailed configuration of the rule, including the '''TBOS settings'''. From there, you can review or manage the TBOS values associated with that maintenance rule.

[[File:1.png|RTENOTITLE]]

 

 

'''STEP 2:'''

'''The table contains several fields:'''

'''Detail''' – Indicates the type of interval used. In this case it is '''Months/Days recurring''', meaning the task repeats periodically based on time.

'''Performed hours / Performed cycles''' – Counters related to the moment the task was last performed. In this example they are set to 0.

'''Performed date''' – The last date when the task was recorded as completed (2021-07-19).

'''Value''' – The TBO interval. Here it is '''24''', meaning the task must be repeated every '''24 months'''.

'''Next Due''' – The calculated next due date for the task (2023-07-19) with a '''±1 month tolerance'''.

'''First alert / Second alert / Third alert''' – These define the warning alerts before the due date. In this example:

'''First alert:''' 3 months before

'''Second alert:''' 2 months before

'''Third alert''': 0 months before

'''Active''' – Indicates whether this TBO is currently active.

'''Comment''' – Field to add notes if needed.

 

=== '''How to modify the TBO:''' ===

To modify the TBO value:

- Go to the '''TBOS tab''' of the performed rule.

- In the top-right corner of the table, click the '''Edit (pencil) icon'''.

- The fields in the row will become editable.

- Modify the '''Value''' field to change the TBO interval (for example, change it from '''24 months''' to another value).

- Adjust other parameters if necessary, such as '''alerts''' or '''tolerance'''.

- Click the '''Save (disk) icon''' to store the changes.

After saving, the system will '''recalculate the next due date''' according to the new TBO configuration and hours.

 

[[File:2.png|RTENOTITLE]]

 

'''''* EVERY MODIFICATION YOU NEED TO SAVE THE CHANGES.'''''

How To Add, Modify or Delete TBOS

2026-05-04T07:36:43Z

Msugranyes:

= TBOS. =

With '''Camotool''', you can easily manage '''TBOS''' by '''adding, modifying, or deleting entries'''. The tool allows you to create new TBOS records, update existing configurations, and remove those that are no longer needed, helping keep the system '''organized and up to date'''.

 

'''1 STEP:'''

The image shows the '''maintenance rules table''', where different tasks and their related information are displayed, such as the '''performed date''', '''last due date''', '''tolerance''', '''next due date''', and the '''TBOS value''' associated with each rule.

Each row represents a specific maintenance rule. In the example, the rule ''“Check calibration of airspeed indicator and altimeter”'' is shown together with its maintenance data. The '''TBOS column''' indicates the time between overhauls or scheduled maintenance for that rule.

To access and manage the '''TBOS information''', you must first open the performed rule window. To do this:

Locate the maintenance rule you want to review in the table and move the display to the right.

'''Right-click on the row of that rule.'''

A context menu will appear.

'''Click on “View performed rule".'''

This action opens the '''performed rule window''', where you can access the detailed configuration of the rule, including the '''TBOS settings'''. From there, you can review or manage the TBOS values associated with that maintenance rule.

[[File:1.png|RTENOTITLE]]

 

 

'''STEP 2:'''

'''The table contains several fields:'''

'''Detail''' – Indicates the type of interval used. In this case it is '''Months/Days recurring''', meaning the task repeats periodically based on time.

'''Performed hours / Performed cycles''' – Counters related to the moment the task was last performed. In this example they are set to 0.

'''Performed date''' – The last date when the task was recorded as completed (2021-07-19).

'''Value''' – The TBO interval. Here it is '''24''', meaning the task must be repeated every '''24 months'''.

'''Next Due''' – The calculated next due date for the task (2023-07-19) with a '''±1 month tolerance'''.

'''First alert / Second alert / Third alert''' – These define the warning alerts before the due date. In this example:

'''First alert:''' 3 months before

'''Second alert:''' 2 months before

'''Third alert''': 0 months before

'''Active''' – Indicates whether this TBO is currently active.

'''Comment''' – Field to add notes if needed.

 

=== '''How to modify the TBO:''' ===

To modify the TBO value:

- Go to the '''TBOS tab''' of the performed rule.

- In the top-right corner of the table, click the '''Edit (pencil) icon'''.

- The fields in the row will become editable.

- Modify the '''Value''' field to change the TBO interval (for example, change it from '''24 months''' to another value).

- Adjust other parameters if necessary, such as '''alerts''' or '''tolerance'''.

- Click the '''Save (disk) icon''' to store the changes.

After saving, the system will '''recalculate the next due date''' according to the new TBO configuration and hours.

 

[[File:2.png|RTENOTITLE]]

 

'''''* EVERY MODIFICATION YOU NEED TO SAVE THE CHANGES.'''''

How To Add, Modify or Delete TBOS

2026-05-04T07:34:00Z

Msugranyes:

= TBOS. =

With '''Camotool''', you can easily manage '''TBOS''' by '''adding, modifying, or deleting entries'''. The tool allows you to create new TBOS records, update existing configurations, and remove those that are no longer needed, helping keep the system '''organized and up to date'''.

 

'''1 STEP'''

The image shows the '''maintenance rules table''', where different tasks and their related information are displayed, such as the '''performed date''', '''last due date''', '''tolerance''', '''next due date''', and the '''TBOS value''' associated with each rule.

Each row represents a specific maintenance rule. In the example, the rule ''“Check calibration of airspeed indicator and altimeter”'' is shown together with its maintenance data. The '''TBOS column''' indicates the time between overhauls or scheduled maintenance for that rule.

To access and manage the '''TBOS information''', you must first open the performed rule window. To do this:

Locate the maintenance rule you want to review in the table and move the display to the right.

'''Right-click on the row of that rule.'''

A context menu will appear.

'''Click on “View performed rule".'''

This action opens the '''performed rule window''', where you can access the detailed configuration of the rule, including the '''TBOS settings'''. From there, you can review or manage the TBOS values associated with that maintenance rule.

[[File:1.png|RTENOTITLE]]

 

 

'''STEP 2:'''

'''The table contains several fields:'''

'''Detail''' – Indicates the type of interval used. In this case it is '''Months/Days recurring''', meaning the task repeats periodically based on time.

'''Performed hours / Performed cycles''' – Counters related to the moment the task was last performed. In this example they are set to 0.

'''Performed date''' – The last date when the task was recorded as completed (2021-07-19).

'''Value''' – The TBO interval. Here it is '''24''', meaning the task must be repeated every '''24 months'''.

'''Next Due''' – The calculated next due date for the task (2023-07-19) with a '''±1 month tolerance'''.

'''First alert / Second alert / Third alert''' – These define the warning alerts before the due date. In this example:

'''First alert:''' 3 months before

'''Second alert:''' 2 months before

'''Third alert''': 0 months before

'''Active''' – Indicates whether this TBO is currently active.

'''Comment''' – Field to add notes if needed.

 

=== '''How to modify the TBO:''' ===

To modify the TBO value:

- Go to the '''TBOS tab''' of the performed rule.

- In the top-right corner of the table, click the '''Edit (pencil) icon'''.

- The fields in the row will become editable.

- Modify the '''Value''' field to change the TBO interval (for example, change it from '''24 months''' to another value).

- Adjust other parameters if necessary, such as '''alerts''' or '''tolerance'''.

- Click the '''Save (disk) icon''' to store the changes.

After saving, the system will '''recalculate the next due date''' according to the new TBO configuration and hours.

 

[[File:2.png|RTENOTITLE]]

 

'''''* EVERY MODIFICATION YOU NEED TO SAVE THE CHANGES.'''''

How To Add, Modify or Delete TBOS

2026-05-04T07:04:21Z

Msugranyes:

= TBOS. =

With '''Camotool''', you can easily manage '''TBOS''' by '''adding, modifying, or deleting entries'''. The tool allows you to create new TBOS records, update existing configurations, and remove those that are no longer needed, helping keep the system '''organized and up to date'''.

 

'''1 STEP'''

The image shows the '''maintenance rules table''', where different tasks and their related information are displayed, such as the '''performed date''', '''last due date''', '''tolerance''', '''next due date''', and the '''TBOS value''' associated with each rule.

Each row represents a specific maintenance rule. In the example, the rule ''“Check calibration of airspeed indicator and altimeter”'' is shown together with its maintenance data. The '''TBOS column''' indicates the time between overhauls or scheduled maintenance for that rule.

To access and manage the '''TBOS information''', you must first open the performed rule window. To do this:

Locate the maintenance rule you want to review in the table and move the display to the right.

'''Right-click on the row of that rule.'''

A context menu will appear.

'''Click on “View performed rule".'''

This action opens the '''performed rule window''', where you can access the detailed configuration of the rule, including the '''TBOS settings'''. From there, you can review or manage the TBOS values associated with that maintenance rule.

[[File:1.png|RTENOTITLE]]

 

 

'''STEP 2'''

The table contains several fields:

'''Detail''' – Indicates the type of interval used. In this case it is '''Months/Days recurring''', meaning the task repeats periodically based on time.

'''Performed hours / Performed cycles''' – Counters related to the moment the task was last performed. In this example they are set to 0.

'''Performed date''' – The last date when the task was recorded as completed (2021-07-19).

'''Value''' – The TBO interval. Here it is '''24''', meaning the task must be repeated every '''24 months'''.

'''Next Due''' – The calculated next due date for the task (2023-07-19) with a '''±1 month tolerance'''.

'''First alert / Second alert / Third alert''' – These define the warning alerts before the due date. In this example:

'''First alert:''' 3 months before

'''Second alert:''' 2 months before

'''Third alert''': 0 months before

'''Active''' – Indicates whether this TBO is currently active.

'''Comment''' – Field to add notes if needed.

 

=== '''How to modify the TBO''' ===

To modify the TBO value:

- Go to the '''TBOS tab''' of the performed rule.

- In the top-right corner of the table, click the '''Edit (pencil) icon'''.

- The fields in the row will become editable.

- Modify the '''Value''' field to change the TBO interval (for example, change it from '''24 months''' to another value).

- Adjust other parameters if necessary, such as '''alerts''' or '''tolerance'''.

- Click the '''Save (disk) icon''' to store the changes.

After saving, the system will '''recalculate the next due date''' according to the new TBO configuration and hours.

 

[[File:2.png|RTENOTITLE]]

 

'''''* EVERY MODIFICATION YOU NEED TO SAVE THE CHANGES.'''''

WAREHOUSE

2026-04-29T08:55:34Z

Msugranyes:

= '''''WAREHOUSE''''' =

=== '''''1. Input details''''' ===

'''Functionality:'''

Allows users to enter and manage records of incoming inventory.

Used for documenting shipments received, recording parts, quantities, and related supplier information.

'''Features:'''

- Set Stock.

- Part Numbers.

- ID.

- Reviewed.

 

'''Typical Use Case:''' A warehouse clerk logs newly received parts into the system, associating them with the correct categories and storage locations.

 

[[File:Inputdetail.png|RTENOTITLE]]

 

----

=== '''''2. Manufacturers''''' ===

'''Functionality:'''

Maintains a database of all part manufacturers.

Allows users to link parts to their original manufacturers for traceability.

'''Features:'''

- Manufacturer name

- Contact information

- Country of origin

- Certification and quality details

 

'''Typical Use Case:''' A quality control team needs to trace the manufacturer of a defective part.

 

[[File:Manufacturedwarehouse.png|RTENOTITLE]]

 

----

=== '''''3. Parts category''''' ===

'''Functionality:'''

Groups inventory parts into major categories to organize stock.

'''Categories:'''

- ID

- Category ID

- Part category description

 

'''Typical Use Case:''' When adding a new part to the system, the user selects its primary category to simplify searches and reporting.

 

[[File:Partcategory.png|RTENOTITLE]]

----

=== '''''4. Provider''''' ===

'''Functionality:'''

Manages information about suppliers or vendors that deliver parts or raw materials.

'''Features:'''

- Company name

- Contact person

- Lead times

- Delivery history

- Pricing agreements

'''Typical Use Case:''' The purchasing department views provider records to assess delivery reliability before placing a large order.

 

[[File:Provider.png|RTENOTITLE]]

 

----

=== '''''5. Subcategory parts''''' ===

'''Functionality:'''

Further refines the categorization of parts under more specific classifications.

'''Examples:'''

Under “Mechanical parts,” subcategories might include “Bearings,” “Gears,” or “Shafts.”

'''Typical Use Case:''' Allows for more accurate filtering, reporting, and part selection during maintenance or production planning.

 

[[File:Subcategory.png|RTENOTITLE]]

----

=== '''''6. Units parts''''' ===

'''Functionality:'''

Defines measurement units associated with inventory items.

'''Examples:'''

Piece, Box, Kilogram, Liter, Meter

'''Typical Use Case:''' Ensures that quantities are tracked accurately during transactions like receiving, transferring, or issuing stock.

[[File:Unit.png|RTENOTITLE]]

----

=== '''''7. Wharehouse locations ''''' ===

'''Functionality:'''

Organizes the physical or logical structure of storage areas within a warehouse.

'''Examples:'''

Aisle 3, Shelf B2

Cold storage section

Receiving dock

'''Typical Use Case:''' When receiving inventory, the system requires the user to assign a storage location for traceability and retrieval.

[[File:Warelocation.png|RTENOTITLE]]

----

=== '''''8. Wharehouses''''' ===

'''Functionality:'''

Manages data on multiple warehouse facilities if the organization operates in several locations.

'''Possible Features:'''

Warehouse name and address

Capacity

Assigned staff

Inventory status by location

'''Typical Use Case:''' A company operating in multiple regions uses this module to monitor and manage inventory at each site.

MAINTENANCE

2026-04-29T07:58:49Z

Msugranyes:

'''MAINTENANCE'''

== '''''What is “maintenance” in aviation?''''' ==

Aircraft maintenance is the combination of inspection, servicing, repair, and overhaul activities carried out on an aircraft and its components. These tasks are performed according to strict regulations established by aviation authorities to guarantee safety and reliability.

== '''''Main types of maintenance:''''' ==

'''Preventive maintenance''' This is scheduled maintenance performed at regular intervals to prevent failures before they occur. It includes routine inspections, lubrication, and replacement of life-limited parts.

'''Corrective maintenance''' This is performed when a fault or malfunction is detected. It involves troubleshooting, repairing, or replacing defective components.

'''Predictive maintenance''' This type is based on data analysis and monitoring systems to detect early signs of wear or failure. It helps reduce unexpected breakdowns and improve maintenance planning.

 

== '''''Maintenance levels:''''' ==

Aircraft maintenance is also divided into different levels:

'''Line maintenance:''' Light and frequent checks carried out before or between flights, such as visual inspections and fluid checks.

'''Base maintenance:''' More detailed and time-consuming work performed in hangars, including structural inspections and major repairs.

'''Common maintenance checks include:'''

A-check (light and frequent)

B-check (moderate, less common)

C-check (deep inspection)

D-check (major overhaul or heavy maintenance)

 

== '''''Areas involved in maintenance:''''' ==

Maintenance covers all major aircraft systems, including:

 -Engines

- Avionics (navigation and communication systems)

- Airframe (structure, wings, fuselage)

- Hydraulic and pneumatic systems

- Landing gear and braking systems

 

== '''''Regulations and standards:''''' ==

Aircraft maintenance must comply with strict international regulations set by authorities such as the Federal Aviation Administration (FAA) and the European Union Aviation Safety Agency (EASA). These organizations define maintenance procedures, inspection intervals, and certification requirements.

== '''''Main objectives:''''' ==

The main goals of aviation maintenance are:

To ensure flight safety

To maintain reliability and performance

To extend the aircraft’s service life

To comply with international aviation regulations

 

== '''''Summary:''''' ==

Aircraft maintenance is a fundamental part of aviation that ensures every aircraft is safe, reliable, and ready to operate through continuous inspection, repair, and monitoring.

MAINTENANCE

2026-04-29T07:37:49Z

Msugranyes:

'''MAINTENANCE'''

== '''''What is “maintenance” in aviation?''''' ==

Aircraft maintenance is the combination of inspection, servicing, repair, and overhaul activities carried out on an aircraft and its components. These tasks are performed according to strict regulations established by aviation authorities to guarantee safety and reliability.

== '''''Main types of maintenance''''' ==

'''Preventive maintenance''' This is scheduled maintenance performed at regular intervals to prevent failures before they occur. It includes routine inspections, lubrication, and replacement of life-limited parts.

'''Corrective maintenance''' This is performed when a fault or malfunction is detected. It involves troubleshooting, repairing, or replacing defective components.

'''Predictive maintenance''' This type is based on data analysis and monitoring systems to detect early signs of wear or failure. It helps reduce unexpected breakdowns and improve maintenance planning.

 

== '''''Maintenance levels''''' ==

Aircraft maintenance is also divided into different levels:

'''Line maintenance:''' Light and frequent checks carried out before or between flights, such as visual inspections and fluid checks.

'''Base maintenance:''' More detailed and time-consuming work performed in hangars, including structural inspections and major repairs.

'''Common maintenance checks include:'''

A-check (light and frequent)

B-check (moderate, less common)

C-check (deep inspection)

D-check (major overhaul or heavy maintenance)

 

== '''''Areas involved in maintenance''''' ==

Maintenance covers all major aircraft systems, including:

 -Engines

- Avionics (navigation and communication systems)

- Airframe (structure, wings, fuselage)

- Hydraulic and pneumatic systems

- Landing gear and braking systems

 

== '''''Regulations and standards''''' ==

Aircraft maintenance must comply with strict international regulations set by authorities such as the Federal Aviation Administration (FAA) and the European Union Aviation Safety Agency (EASA). These organizations define maintenance procedures, inspection intervals, and certification requirements.

== '''''Main objectives''''' ==

The main goals of aviation maintenance are:

To ensure flight safety

To maintain reliability and performance

To extend the aircraft’s service life

To comply with international aviation regulations

 

== '''''Summary''''' ==

Aircraft maintenance is a fundamental part of aviation that ensures every aircraft is safe, reliable, and ready to operate through continuous inspection, repair, and monitoring.

Work Orders

2026-04-28T11:49:05Z

Msugranyes:

== '''Work Orders''' ==

The '''"Work Orders"''' menu in Camotool provides users with access to tools for managing maintenance tasks, repairs, inspections, or any other operational jobs that are tracked in the system. Work orders are essential for documenting, assigning, and following up on these tasks in a structured way.

This menu includes options to view all work orders or search for specific ones.Menu Options.

[[File:Workorder1.png|RTENOTITLE]]

 

'''''List Work Order'''''

Displays a complete list of all work orders registered in the system.

'''The list view typically includes key information such as:'''

- Work order ID.

- Title or description.

- Assigned personnel.

- Status.

- Start and due dates.

'''From this page, users can:'''

- Open individual work orders to see full details:

- Edit or update existing work orders (based on permissions):

- Track progress and follow-up actions:

- Useful for maintenance planners, supervisors, and technicians managing multiple tasks:

 

'''''Search Work Order'''''

'''Opens a search interface that allows users to locate specific work orders using filters or keywords.'''

- Search criteria may include:

- Work order number:

- Status (e.g. open, in progress, completed):

- Assigned user or team:

- Date ranges:

- Related equipment or location:

- Designed to improve navigation and quickly access relevant information without scrolling through long lists.

Documents Section

2026-04-28T11:28:46Z

Msugranyes:

= '''''DOCUMENTS SECTION:''''' =

=== '''''1. Documents Origin''''' ===

This section tracks '''where a document comes from'''. For example:

- Internal departments (e.g., Maintenance, Engineering, Quality)

- External sources (e.g., OEMs, regulatory agencies)

'''Third-party contractors or partners:'''

 - It’s important for '''traceability''' and determining the document’s authority or trust level.

 

----

=== '''''2. Document Origin Types''''' ===

'''ID: Identification name.'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

Manufacturer-supplied This allows better filtering, searching, and workflow configuration.

[[File:Documentorigintype.png|RTENOTITLE]]

 

----

=== '''''3. Document Types''''' ===

'''Document type ID'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

[[File:Documentype.png|RTENOTITLE]]

----

=== '''''4. Documents''''' ===

This is the '''core repository''' where actual documents are managed. Likely features:

- Upload and download documents

- Assign document metadata (type, origin, date, revision)

- Set access permissions

- Link documents to aircraft, parts, findings, inspections, etc.

- Track version history and expiration dates (if applicable)

- Document viewer or preview support

Documents Section

2026-04-28T11:28:30Z

Msugranyes:

= '''''DOCUMENTS SECTION:''''' =

=== '''''1. Document Origin''''' ===

This section tracks '''where a document comes from'''. For example:

- Internal departments (e.g., Maintenance, Engineering, Quality)

- External sources (e.g., OEMs, regulatory agencies)

'''Third-party contractors or partners:'''

 - It’s important for '''traceability''' and determining the document’s authority or trust level.

 

----

=== '''''2. Document Origin Types''''' ===

'''ID: Identification name.'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

Manufacturer-supplied This allows better filtering, searching, and workflow configuration.

[[File:Documentorigintype.png|RTENOTITLE]]

 

----

=== '''''3. Document Types''''' ===

'''Document type ID'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

[[File:Documentype.png|RTENOTITLE]]

----

=== '''''4. Documents''''' ===

This is the '''core repository''' where actual documents are managed. Likely features:

- Upload and download documents

- Assign document metadata (type, origin, date, revision)

- Set access permissions

- Link documents to aircraft, parts, findings, inspections, etc.

- Track version history and expiration dates (if applicable)

- Document viewer or preview support

Documents Section

2026-04-28T11:25:39Z

Msugranyes:

= '''''DOCUMENTS SECTION:''''' =

=== '''''1. Document Origin''''' ===

This section tracks '''where a document comes from'''. For example:

- Internal departments (e.g., Maintenance, Engineering, Quality)

- External sources (e.g., OEMs, regulatory agencies)

Third-party contractors or partners: It’s important for '''traceability''' and determining the document’s authority or trust level.

 

----

=== '''''2. Document Origin Types''''' ===

'''ID: Identification name.'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

Manufacturer-supplied This allows better filtering, searching, and workflow configuration.

[[File:Documentorigintype.png|RTENOTITLE]]

 

----

=== '''''3. Document Types''''' ===

'''Document type ID'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

[[File:Documentype.png|RTENOTITLE]]

----

=== '''''4. Documents''''' ===

This is the '''core repository''' where actual documents are managed. Likely features:

- Upload and download documents

- Assign document metadata (type, origin, date, revision)

- Set access permissions

- Link documents to aircraft, parts, findings, inspections, etc.

- Track version history and expiration dates (if applicable)

- Document viewer or preview support

Documents Section

2026-04-28T11:24:14Z

Msugranyes:

= DOCUMENTS SECTION =

=== '''''1. Document Origin''''' ===

This section tracks '''where a document comes from'''. For example:

- Internal departments (e.g., Maintenance, Engineering, Quality)

- External sources (e.g., OEMs, regulatory agencies)

Third-party contractors or partners: It’s important for '''traceability''' and determining the document’s authority or trust level.

 

----

=== '''''2. Document Origin Types''''' ===

'''ID: Identification name.'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

Manufacturer-supplied This allows better filtering, searching, and workflow configuration.

[[File:Documentorigintype.png|RTENOTITLE]]

 

----

=== '''''3. Document Types''''' ===

'''Document type ID'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

[[File:Documentype.png|RTENOTITLE]]

----

=== '''''4. Documents''''' ===

This is the '''core repository''' where actual documents are managed. Likely features:

- Upload and download documents

- Assign document metadata (type, origin, date, revision)

- Set access permissions

- Link documents to aircraft, parts, findings, inspections, etc.

- Track version history and expiration dates (if applicable)

- Document viewer or preview support

Documents Section

2026-04-28T10:51:56Z

Msugranyes:

= DOCUMENTS SECTION =

=== '''''1. Document Origin''''' ===

This section tracks '''where a document comes from'''. For example:

- Internal departments (e.g., Maintenance, Engineering, Quality)

- External sources (e.g., OEMs, regulatory agencies)

Third-party contractors or partners: It’s important for '''traceability''' and determining the document’s authority or trust level.

 

----

=== '''''2. Document Origin Types''''' ===

'''ID: Identification name.'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

Manufacturer-supplied This allows better filtering, searching, and workflow configuration.

[[File:Documentorigintype.png|RTENOTITLE]]

 

----

=== '''''3. Document Types''''' ===

'''Document type ID'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

[[File:Documentype.png|RTENOTITLE]]

----

=== '''''4. Documents''''' ===

This is the '''core repository''' where actual documents are managed. Likely features:

Upload and download documents

Assign document metadata (type, origin, date, revision)

Set access permissions

Link documents to aircraft, parts, findings, inspections, etc.

Track version history and expiration dates (if applicable)

Document viewer or preview support

Documents Section

2026-04-28T10:40:57Z

Msugranyes:

= DOCUMENTS SECTION =

=== '''''1. Document Origin''''' ===

This section tracks '''where a document comes from'''. For example:

- Internal departments (e.g., Maintenance, Engineering, Quality)

- External sources (e.g., OEMs, regulatory agencies)

Third-party contractors or partners: It’s important for '''traceability''' and determining the document’s authority or trust level.

 

----

=== '''''2. Document Origin Types''''' ===

'''ID: Identification name.'''

'''Name: Name of the Document.'''

'''Description: Here you can put a liitel words to inform what it is.'''

Manufacturer-supplied This allows better filtering, searching, and workflow configuration.

[[File:Documentorigintype.png|RTENOTITLE]]

 

----

=== '''''3. Document Types''''' ===

'''Document type ID'''

'''Name'''

'''Description'''

[[File:Documentype.png|RTENOTITLE]]

----

=== '''''4. Documents''''' ===

This is the '''core repository''' where actual documents are managed. Likely features:

Upload and download documents

Assign document metadata (type, origin, date, revision)

Set access permissions

Link documents to aircraft, parts, findings, inspections, etc.

Track version history and expiration dates (if applicable)

Document viewer or preview support

Documents Section

2026-04-28T08:29:05Z

Msugranyes:

= DOCUMENTS SECTION =

=== '''''1. Document Origin''''' ===

This section tracks '''where a document comes from'''. For example:

- Internal departments (e.g., Maintenance, Engineering, Quality)

- External sources (e.g., OEMs, regulatory agencies)

Third-party contractors or partners It’s important for '''traceability''' and determining the document’s authority or trust level.

 

----

=== '''''2. Document Origin Types''''' ===

'''ID: Identification name'''

'''Name: '''

'''Description: Here you can put a liitel words to inform what it is.'''

Manufacturer-supplied This allows better filtering, searching, and workflow configuration.

[[File:Documentorigintype.png|RTENOTITLE]]

 

----

=== '''''3. Document Types''''' ===

'''Document type ID'''

'''Name'''

'''Description'''

[[File:Documentype.png|RTENOTITLE]]

----

=== '''''4. Documents''''' ===

This is the '''core repository''' where actual documents are managed. Likely features:

Upload and download documents

Assign document metadata (type, origin, date, revision)

Set access permissions

Link documents to aircraft, parts, findings, inspections, etc.

Track version history and expiration dates (if applicable)

Document viewer or preview support

How to replace parts

2026-04-24T11:55:30Z

Msugranyes:

= '''Replace or Overhaul Parts in CAMOTOOL''' =

'''''1. Access the Work Order (WO)'''''

Navigate to: '''Work Orders''' > '''List Work Orders'''.

Select a '''Package Work Order (PWO)'''. These are grouped tasks tied to inspections or scheduled maintenance like:

'''- AMP REVIEW''' – Airworthiness Maintenance Program review.

'''- 100H ENG + PROP INSP''' – Every 100 flight hours, inspect engine and propeller.

'''- ARC/Annual''' – Annual Review of Airworthiness.

[[File:WO.png|RTENOTITLE]]

GREEN: '''CLOSE Work Order.'''

RED: '''OPEN Work Order.'''

'''''2. Review Tasks Related to Part Replacement or Overhaul'''''

Each PWO will contain individual tasks—some require part replacements due to life limits (e.g., filters, seals), others require inspections that might trigger a replacement or overhaul (e.g., worn brake discs, magnetos).

Look for task cards like:

“Replace oil filter – 50H Interval”

“Overhaul landing gear – 1,000H or 6 years”

“Remove & inspect propeller – 100H interval”

Its a small description about the tasks to do.

'''''3. Navigate to the ‘Parts’ Module'''''

'''Parts''' > '''Inventory''' or '''Installed Parts'''.

Search for the part by:

'''- Part Number'''

'''- Serial Number'''

If the part is installed and needs removal:

Use the “Remove” option and link it to the active WO task.

[[File:Listparts12.png|RTENOTITLE]]

 

'''''4. Replace or Overhaul the Part'''''

'''Replacement:'''

Locate the new part in inventory.

Use the “Install” option in the WO.

'''Overhaul:'''

If a part is being overhauled you need:

Remove it using the WO.

Send to a certified MRO (Maintenance, Repair, Overhaul facility).

Once returned with overhaul certs, mark it as "overhauled" and re-install or move it back to inventory.

Attach overhaul documentation.

 

'''''5. Attach Documentation'''''

Go to: '''Documents''' module or link directly in the WO.

Upload:

- Installation/Removal reports.

- Overhaul reports or release certificates.

- Task cards with technician sign-offs.

Ensure traceability is complete for auditors and safety reviews.

 

'''''6. Close Work Order and Review'''''

A supervisor or CAMO engineer must '''review and approve''' the WO.

- Check off the '''“Reviewed”''' checkbox (as shown in your image).

- This step ensures everything has been signed off by a licensed certifying staff.

- Only after this step can the WO be marked “Completed” or used for billing.

 

Some parts you can mark in a check box if is mandatoy Replace/Overhaul, take care when you assign this option.

How to replace parts

2026-04-24T10:53:37Z

Msugranyes:

= '''Replace or Overhaul Parts in CAMOTOOL''' =

'''''1. Access the Work Order (WO)'''''

Navigate to: '''Work Orders''' > '''List Work Orders'''.

Select a '''Package Work Order (PWO)'''. These are grouped tasks tied to inspections or scheduled maintenance like:

'''- AMP REVIEW''' – Airworthiness Maintenance Program review.

'''- 100H ENG + PROP INSP''' – Every 100 flight hours, inspect engine and propeller.

'''- ARC/Annual''' – Annual Review of Airworthiness.

[[File:WO.png|RTENOTITLE]]

GREEN: CLOSE Work Order

RED: OPEN Work Order.

'''''2. Review Tasks Related to Part Replacement or Overhaul'''''

Each PWO will contain individual tasks—some require part replacements due to life limits (e.g., filters, seals), others require inspections that might trigger a replacement or overhaul (e.g., worn brake discs, magnetos).

Look for task cards like:

“Replace oil filter – 50H Interval”

“Overhaul landing gear – 1,000H or 6 years”

“Remove & inspect propeller – 100H interval”

Its a small description about the tasks to do.

'''''3. Navigate to the ‘Parts’ Module'''''

'''Parts''' > '''Inventory''' or '''Installed Parts'''.

Search for the part by:

'''- Part Number'''

'''- Serial Number'''

If the part is installed and needs removal:

Use the “Remove” option and link it to the active WO task.

[[File:Listparts12.png|RTENOTITLE]]

 

'''''4. Replace or Overhaul the Part'''''

'''Replacement:'''

Locate the new part in inventory.

Use the “Install” option in the WO.

'''Overhaul:'''

If a part is being overhauled you need:

Remove it using the WO.

Send to a certified MRO (Maintenance, Repair, Overhaul facility).

Once returned with overhaul certs, mark it as "overhauled" and re-install or move it back to inventory.

Attach overhaul documentation.

 

'''''5. Attach Documentation'''''

Go to: '''Documents''' module or link directly in the WO.

Upload:

- Installation/Removal reports.

- Overhaul reports or release certificates.

- Task cards with technician sign-offs.

Ensure traceability is complete for auditors and safety reviews.

 

'''''6. Close Work Order and Review'''''

A supervisor or CAMO engineer must '''review and approve''' the WO.

- Check off the '''“Reviewed”''' checkbox (as shown in your image).

- This step ensures everything has been signed off by a licensed certifying staff.

- Only after this step can the WO be marked “Completed” or used for billing.

 

Some parts you can mark in a check box if is mandatoy Replace/Overhaul, take care when you assign this option.

How to replace parts

2026-04-24T10:25:55Z

Msugranyes:

= '''Replace or Overhaul Parts in CAMOTOOL''' =

'''''1. Access the Work Order (WO)'''''

Navigate to: '''Work Orders''' > '''List Work Orders'''.

Select a '''Package Work Order (PWO)'''. These are grouped tasks tied to inspections or scheduled maintenance like:

'''- AMP REVIEW''' – Airworthiness Maintenance Program review.

'''- 100H ENG + PROP INSP''' – Every 100 flight hours, inspect engine and propeller.

'''- ARC/Annual''' – Annual Review of Airworthiness.

[[File:WO.png|RTENOTITLE]]

 

'''''2. Review Tasks Related to Part Replacement or Overhaul'''''

Each PWO will contain individual tasks—some require part replacements due to life limits (e.g., filters, seals), others require inspections that might trigger a replacement or overhaul (e.g., worn brake discs, magnetos).

Look for task cards like:

“Replace oil filter – 50H Interval”

“Overhaul landing gear – 1,000H or 6 years”

“Remove & inspect propeller – 100H interval”

Its a small description about the tasks to do.

'''''3. Navigate to the ‘Parts’ Module'''''

'''Parts''' > '''Inventory''' or '''Installed Parts'''.

Search for the part by:

'''- Part Number'''

'''- Serial Number'''

If the part is installed and needs removal:

Use the “Remove” option and link it to the active WO task.

[[File:Listparts12.png|RTENOTITLE]]

 

'''''4. Replace or Overhaul the Part'''''

'''Replacement:'''

Locate the new part in inventory.

Use the “Install” option in the WO.

'''Overhaul:'''

If a part is being overhauled you need:

Remove it using the WO.

Send to a certified MRO (Maintenance, Repair, Overhaul facility).

Once returned with overhaul certs, mark it as "overhauled" and re-install or move it back to inventory.

Attach overhaul documentation.

 

'''''5. Attach Documentation'''''

Go to: '''Documents''' module or link directly in the WO.

Upload:

- Installation/Removal reports.

- Overhaul reports or release certificates.

- Task cards with technician sign-offs.

Ensure traceability is complete for auditors and safety reviews.

 

'''''6. Close Work Order and Review'''''

A supervisor or CAMO engineer must '''review and approve''' the WO.

- Check off the '''“Reviewed”''' checkbox (as shown in your image).

- This step ensures everything has been signed off by a licensed certifying staff.

- Only after this step can the WO be marked “Completed” or used for billing.

 

Some parts you can mark in a check box if is mandatoy Replace/Overhaul, take care when you assign this option.

How to replace parts

2026-04-24T08:50:51Z

Msugranyes:

= '''Replace or Overhaul Parts in CAMOTOOL''' =

'''''1. Access the Work Order (WO)'''''

Navigate to: '''Work Orders''' > '''List Work Orders'''.

Select a '''Package Work Order (PWO)'''. These are grouped tasks tied to inspections or scheduled maintenance like:

'''- AMP REVIEW''' – Airworthiness Maintenance Program review.

'''- 100H ENG + PROP INSP''' – Every 100 flight hours, inspect engine and propeller.

'''- ARC/Annual''' – Annual Review of Airworthiness.

[[File:WO.png|RTENOTITLE]]

 

'''''2. Review Tasks Related to Part Replacement or Overhaul'''''

Each PWO will contain individual tasks—some require part replacements due to life limits (e.g., filters, seals), others require inspections that might trigger a replacement or overhaul (e.g., worn brake discs, magnetos).

Look for task cards like:

“Replace oil filter – 50H Interval”

“Overhaul landing gear – 1,000H or 6 years”

“Remove & inspect propeller – 100H interval”

 

'''''3. Navigate to the ‘Parts’ Module'''''

'''Parts''' > '''Inventory''' or '''Installed Parts'''.

Search for the part by:

'''- Part Number'''

'''- Serial Number'''

If the part is installed and needs removal:

Use the “Remove” option and link it to the active WO task.

[[File:Listparts12.png]]

 

'''''4. Replace or Overhaul the Part'''''

'''Replacement:'''

Locate the new part in inventory.

Use the “Install” option in the WO.

'''Overhaul:'''

If a part is being overhauled you need:

Remove it using the WO.

Send to a certified MRO (Maintenance, Repair, Overhaul facility).

Once returned with overhaul certs, mark it as "overhauled" and re-install or move it back to inventory.

Attach overhaul documentation.

 

'''''5. Attach Documentation'''''

Go to: '''Documents''' module or link directly in the WO.

Upload:

- Installation/Removal reports.

- Overhaul reports or release certificates.

- Task cards with technician sign-offs.

Ensure traceability is complete for auditors and safety reviews.

 

'''''6. Close Work Order and Review'''''

A supervisor or CAMO engineer must '''review and approve''' the WO.

- Check off the '''“Reviewed”''' checkbox (as shown in your image).

- This step ensures everything has been signed off by a licensed certifying staff.

- Only after this step can the WO be marked “Completed” or used for billing.

 

Some parts you can mark in a check box if is mandatoy Replace/Overhaul, take care when you assign this option.

File:Listparts12.png

2026-04-24T08:50:17Z

Msugranyes:

How to replace parts

2026-04-24T08:50:03Z

Msugranyes:

= '''Replace or Overhaul Parts in CAMOTOOL''' =

'''''1. Access the Work Order (WO)'''''

Navigate to: '''Work Orders''' > '''List Work Orders'''.

Select a '''Package Work Order (PWO)'''. These are grouped tasks tied to inspections or scheduled maintenance like:

'''- AMP REVIEW''' – Airworthiness Maintenance Program review.

'''- 100H ENG + PROP INSP''' – Every 100 flight hours, inspect engine and propeller.

'''- ARC/Annual''' – Annual Review of Airworthiness.

[[File:WO.png|RTENOTITLE]]

 

'''''2. Review Tasks Related to Part Replacement or Overhaul'''''

Each PWO will contain individual tasks—some require part replacements due to life limits (e.g., filters, seals), others require inspections that might trigger a replacement or overhaul (e.g., worn brake discs, magnetos).

Look for task cards like:

“Replace oil filter – 50H Interval”

“Overhaul landing gear – 1,000H or 6 years”

“Remove & inspect propeller – 100H interval”

 

'''''3. Navigate to the ‘Parts’ Module'''''

'''Parts''' > '''Inventory''' or '''Installed Parts'''.

Search for the part by:

'''- Part Number'''

'''- Serial Number'''

If the part is installed and needs removal:

Use the “Remove” option and link it to the active WO task.

 

'''''4. Replace or Overhaul the Part'''''

'''Replacement:'''

Locate the new part in inventory.

Use the “Install” option in the WO.

'''Overhaul:'''

If a part is being overhauled you need:

Remove it using the WO.

Send to a certified MRO (Maintenance, Repair, Overhaul facility).

Once returned with overhaul certs, mark it as "overhauled" and re-install or move it back to inventory.

Attach overhaul documentation.

 

'''''5. Attach Documentation'''''

Go to: '''Documents''' module or link directly in the WO.

Upload:

- Installation/Removal reports.

- Overhaul reports or release certificates.

- Task cards with technician sign-offs.

Ensure traceability is complete for auditors and safety reviews.

 

'''''6. Close Work Order and Review'''''

A supervisor or CAMO engineer must '''review and approve''' the WO.

- Check off the '''“Reviewed”''' checkbox (as shown in your image).

- This step ensures everything has been signed off by a licensed certifying staff.

- Only after this step can the WO be marked “Completed” or used for billing.

 

Some parts you can mark in a check box if is mandatoy Replace/Overhaul, take care when you assign this option.