Creating technical log information

This page can be used to create the technical log information of a journey, corresponding to the journey log of the same flight. Tell me more.

• Select the “Create Technical Log” link under the “Flight Log” business component.

The “Create Technical Log” page appears.

The system displays the following field:

The system displays the following fields in the “Tech Log Details” group box:

• Enter the following fields in the “Tech Log Details” group box:

Note: The “Tech.Log Category” cannot be modified after the technical log is created.

The system displays the following field in the “Tech Log Details” group box:

• Enter the following fields in the “Tech Log Details” group box:

Note: The aircraft registration number must correspond to the journey log specified in the “Journey Log#” field. If this field is left blank, the system displays the aircraft registration number that is referred by the “Journey Log#”, if the “Operations type” is set as “Flight Ops”.     

The system displays the following:

•  Enter the following field:

Note: The “Tech Log Date and Time” must be later than or equal to the date and time entered in the “Gate-in Date & Time” field. The system displays the current server date and time by default.

Note: The “Tech Log Date & Time” must be later than the operational date and time of the aircraft.

Note: Ensure that “Tech Log Date & Time” does not fall in the range of the closed reliability period for the reliability fleet to which the aircraft is associated.

The system displays the following field:

• Enter the following fields:

• Click the “Get Details” pushbutton to retrieve details pertaining to the aircraft registration number entered.

• Enter the following in the “Execution Details” group box:

The system displays the following field:

• Enter the following fields in the “Journey Log Details” group box:

Note: The journey log number, flight and leg numbers and line number cannot be modified or deleted, if action has been recorded against the pilot reported discrepancies associated to the technical log through the journey log.   

If no action is taken against the pilot-reported discrepancies, the journey log number, flight and leg numbers and line number can be modified, deleted or no longer associated to the technical log. The status of such discrepancies is reverted to the previous status.

Note: If the “Tech Log Basis” is set as “JL - consolidated” or “JL - Leg Level”, and if only Journey Log # is entered, then the system ensures that the Journey Log #/Flight#/Leg# combination or Journey Log #/Line# combination for the Aircraft Reg # is not referred in any technical log. If the Journey Log has not been referred in any other Technical Log, system retrieves the Flight #/Leg # or Line # from the Journey Log whose arrival date and time is lesser or equal to the entered execution date and time and for which  “Maint. Execution” is set as “Yes”.

The system displays the following in the “Customer Order Details” group box:

• Enter the following fields in the “Customer Order Details” group box:

The system displays the following in the “Customer Order Details” group box:

• Select the hyperlinked "Customer Order Desc" to view the customer order information.

• Select the “Discrepancy Details” tab to record discrepancy details associated to the technical log.

• Select the “Inspector / Mechanic Information” tab in the main page, if you wish to record additional information for the technical log.

• Select the “Cost & Additional Information” tab in the main page,  to record additional information and cost details incurred on the technical log.

To create a technical log

• Click the “Create Log” pushbutton to create the technical log.

Note: This action is workflow-enabled. Notification messages can be sent and you can configure further processing of this document in the "Workflow Management" business component.

The system performs the following:

• While creating a technical log, if any of the maintenance report associated to the current technical log is deferred, the system checks the deferral limits based on the deferral limit and the deferral limit basis.

Note: The system does not allows you to defer the maintenance report if the threshold date (or) revised threshold date is earlier than the current server date, and if the threshold value (or) revised threshold value is less than the current parameter value associated to the aircraft.

• If the “Auto inclusion of jobs based on Alert Date/Value” field is set as “Technical Log” or “Line Package & Technical Log” in the “Set Options” activity of the “Compliance Tracking & Control” business component, then the system retrieves all the pending jobs from component planning and Compliance Tracking & Control pending tray, whose alert date is earlier than or same as the current technical log date and time. This is not applicable if the back end option “Retrieval of Forecasted Work Units/Deferred Discrepancies" is set as either “Deferred Discrepancies” or “None”.

• The system retrieves and allocates the pending work units and discrepancies to the current technical log based on the value set for the backend set option “Retrieval of Forecasted/Deferred Discrepancies” and “Allocation Basis of Pending Workunits to Techlog”. The “Retrieval of Forecasted/Deferred Discrepancies” back end set option could be any one of the following options: “Forecasted/Overdue work units”, “Deferred Discrepancies”, “Both”, or “None”, and the “Allocation Basis of Pending Workunits to Techlog” could be “Scheduled Date”, “Planned Start Date” or “Which ever is earlier”.

1. If the backend option is set as “Forecasted/Overdue workunits”, then the system automatically retrieves all the work units on creation of technical log

2. If the backend set option is set as “Deferred Discrepancies”, then the system automatically retrieves all the deferred discrepancies on creation of the technical log.

3. If the backend set option is set as “Both”, then the system retrieves both the work units and the deferred discrepancies on creation of the technical log. Else, if it is set as “None”, then none of the workunits/deferred discrepancies will be retrieved.

Note: The system will retrieve the Maintenance Reports (Deferred Discrepancies) only on clicking the “Get Details” pushbutton.

• If the back end set option is “Forecasted/Overdue Work Units”, then the system automatically retrieves and allocates the work units from the pending tray to the current technical log that is being created in spite of whether the work unit is due or not, based on the value set for the back end option “Allocation Basis of Pending Workunits to Techlog”.

Note: For example: If the “Allocation Basis of Pending Work Units to Techlog” is “Scheduled Date”, then the system retrieves and allocates the work units to the technical log based on the schedule date alone. But, if the work unit does not have a “Schedule date” against it, for eg: in case of As Required Work Units, the system will retrieve and allocate the work unit based on its “Planned Start Date”. If the back end option is “Which ever is earlier”, then the system will allocate the work units depending on the “Scheduled Date” or the “Planned Start Date” which ever is earlier.

Note: The above mentioned validation is not applicable if the “Retrieval of Forecasted/Deferred Discrepancy” back end option is set to either “Deferred Discrepancy” or “None”.

Note: If the technical log is created with reference to line package, then the system does not consider the back end set option set for “Retrieval of Forecasted/Deferred Discrepancies”

• While creating a technical log, the system simultaneously updates the maintenance report details in the “Discrepancy Processing business component when the “Action” field is set to “Deferred”.

Note: The system updates the record status of the maintenance report from “Deferred” to “Under Resolution”, if the “Action” field is set to a value other than “Defer”.

The system performs the following, when the operations type is not set as “Repair Station:

• Updates the “Transfer To: Part #” and “Transfer To : Serial #” as the "Removed Part #" and "Removed Serial #"  and the “Object Type” as “Component” in the  "Replace Component" page.

• Retrieves the resource requirements for work units in the "Report Resource Consumption" page at the task level. For example, if the work unit retrieved is a work package, this work package is exploded into a standard procedure and tasks and resource requirements are retrieved for each level.

If the operations type is not  “Repair Station”, the system retrieves work units and updates them in the "Record Work & Sign-off Information" page if:

• The work units have a plan date or a schedule date, or both, which is earlier than or equal to the execution date and time of the technical log.

• The job status of the work units is “Pending”.

Note: Work units are retrieved for the aircraft, component attached to the aircraft, engineering order or fleet campaign directives in which, the status of the work units is “Pending” and transient status is “Forecasted” or “Deferred” and the job type is "Aircraft", “On-wing” or “Removal”.

The system updates the following for the retrieved work units, if the operations type is not “Repair Station”:

• The job status is updated as “Allocated”, in the aircraft pending tray of the “Compliance Tracking & Control” business component and the component pending tray of the “Component Maintenance Planning” business component.

• The source of the work units is set as “Forecast” .

• The “Planning type” is set as “Planned”.

• The default “Execution Status” is set as “Pending”.

Note: For overdue or pending work units that are fetched, the system updates their source as “Pending” and “Incomplete” respectively.

If the operations type is not “Repair Station”, the system also retrieves work units that have been included in some other technical logs, for which “Execution Status” is “Incomplete”, and performs the following:

• Identifies the source for these work units in the aircraft or component pending tray and sets the type as “Planned”.

• The default execution status is set as “Pending”.

Note: For pending or overdue work units that are fetched, the system updates their source as “Pending” and “Incomplete” respectively.

Note: The system does not retrieve the above details, if the “Operations type” is set as “Repair Station” irrespective of the value set in the back end option “Retrieval of Forecasted Work Units/Deferred Discrepancies.

The system updates the following:

• Material requirements in the “Request Material & Report Consumption” page.

• Position Code, Level Code and Component ID of work units whose job type is “Component Removal”. The object type for these work units is set as “Component”.

• Stock status as “PBH” if the part is identified as PBH.

• Stock status is “Accepted” if the part is identified as non-PBH in the “Report Part Consumption” activity.

Note: If a pending authorized material request exists for the aircraft on the given warehouse, the system updates the material request number. The technical log for the material request is updated and the pending quantity of the material request is reduced. The material request source is updated as "Planned".

Note: A part is identified as PBH, if the specified aircraft registration number and specified part, or the specified part and any of its higher assembly parts, are identified in the PBH object list for a supplier. The supplier should have reference for both the part number and any of the higher assembly part number.

The system retrieves the work units identified against the selected maintenance event, from the “Aircraft Maintenance Program ” business component, into the “Record Work & Sign-off Information” page and sets the source for these work units as “Maintenance Events”, the planning type as “Planned” and execution status as “Pending”.

Note: For pending or overdue work units that are fetched, the system updates their source as “Pending” and “Incomplete” respectively.  

Note: The system does not retrieve the above details if the “Operations Type is set as “Repair Station".

The system performs the following "Suppress" action when associating work units that are overdue or planned for execution:

• When a component has multiple replacement work units, the earliest replacement work unit alone is associated to the technical log

• When a replacement work unit is present for a higher assembly component and a replacement work unit or an on-wing work unit arising from a component maintenance forecast is also present on its lower level component, the replacement work unit on the higher assembly component alone is considered.

The system posts the financial entries to the relevant account codes in the "Finance Book Processing" business component.

To confirm a technical log

Before confirmation, ensure the following:

• A discrepancy is reported in the technical log, when the “Discrepancy Rep?” field is set as “Yes” while providing sign-off information in the “Record Work & Sign-Off Information” page.

• The status of the technical log is not “Confirmed” or “Cancelled”. On confirmation, the status of the technical log is updated to “Confirmed”.

• The “Execution Status” drop-down list box in the multiline of the “Record Work & Sign-off Information” page is not selected as “Pending” or “Incomplete”, if the work unit “Planning Type” is “Unplanned” and “Source” is “Discrepancy”.                                                                    

• Click the “Confirm Tech Log” pushbutton to confirm the technical log.

Note: This action is workflow-enabled. Notification messages can be sent and you can configure further processing of this document in the "Workflow Management" business component.

The system performs the following:

• The system processes and updates the financial postings in the “Finance Book Processing”  business component from the “Account Group” business component and, if interaction exists, with the “Book Keeping” business component.

• The system calculates the actual cost for the technical log as the sum of material cost, resource cost, employee cost, labour cost, facilities cost and miscellaneous cost.

If the Tech Log is based on a customer order with a service price list that has the “Pricing Method for Skills” set to “Roster Code”, the system (i) splits the time sheet records into various time slabs and (ii) computes the skill price as defined in the roster code details of the service price list attached to the customer order.

• While confirming the technical log, the system ensures that a deferral task exist for the Maintenance Report, of deferral type “CDL” or “MEL”, if the “Sign-off reqd. for Deferral of Discrepancy” field is set to “Yes” in the “Set Options” activity of the current business component.

• On confirmation of the technical log, when any of the maintenance report associated to the current technical log is deferred, the system checks the deferral limits based on the type of the deferral limit and the deferral limit basis.

Note: The system does not allows you to defer the maintenance report if the threshold date (or) revised threshold date is earlier than the current server date, and if the threshold value (or) revised threshold value is less than the current parameter value associated to the aircraft.

• For the Aircraft Reg # - Work Unit combination, the system deletes the work units from Compliance Tracking & control pending tray

1. if the source of the work units is “Forecast” and the execution status is “Completed”, and

2. if the source of the work units is “Deferment Request” and the work unit execution status is  “Completed” or “Pre-Closed”

Parameter value updation

For planned, unplanned and direct work units where the job type is on-wing and execution status is “Completed”, based on their maintenance type, the system resets the following parameter values of the components on which work units are executed in the “Edit Consumption and Range Parameters” page of “Edit Component Record” activity in the “Aircraft” business component

• If the maintenance type is overhaul, the system resets the “Since Overhaul”, “Since Repair” and “Since Inspection” parameter values to zero.

• If the maintenance type is repair, the system resets the “Since Repair” and “Since Inspection” parameter values to zero.

• If the maintenance type is inspection, the system resets the “Since Inspection” parameter value to zero.

Note: The system will not reset any value if the maintenance type for the work unit is “Others” or “Retire”.

For the work units retrieved from "Compliance Tracking & Control" business component, the system updates the "Job Status" of work units (for which the "Execution Status" is set as "Completed” in the "Record Work & Sign-off Information" page) as "Completed" in the "Compliance Tracking & Control" business component.

If parameter values are recorded against the technical log, the system updates the parameter values with Techlog # / Line # / WorkUnit #/ Task# / Sub Task# reference in the parameter value history in the “Aircraft” business component, based on the update mode.

For the work units retrieved from "Compliance Tracking & Control" business component, the system updates the "Job Status" of work units (for which the "Execution Status" is set as "Completed” in the "Record Work Information" page) as "Completed" in the "Compliance Tracking & Control" business component.

Compliance history updation for work units

On confirmation, for unforecasted work units added from the “Perform Opportunity Maintenance” page, and the direct work units added in the “Record Work and Sign-Off Information” page, where the execution status is set as “Completed”, the system updates the compliance information such as the ‘Last Performed Date’ and ‘Last Performed Value’. If those work units are repetitive, then their ‘Next Schedule Date’ and ‘Next Schedule Value’ are also updated in their respective aircraft maintenance program or component maintenance program. If work unit is scheduled more than once in the maintenance program, the system updates the compliance information for all of them.

For work units with “Execution Status” as “Incomplete”, the system displays the first compliance date as the “Compliance Date” for these work units.

If the operations type is “Flight Ops”, the system updates the compliance date of the work units in the compliance history of the “Aircraft” business component, based on the option set for the “Ref. Date for Compliance against Flight Ops” in the “Set Options” activity. If the option setting is “Start Date”, the system considers the start date of the technical log. If the option setting is “End Date”, the system considers the end date of the technical log. If the option setting is “User Defined”, the system considers the compliance date specified in the “Record Work Unit & Sign-off Information” page.

Note: The compliance date specified in the “Record Work Unit & Sign-off Information” page should lie between the “Actual Start Date & Time” and “Actual End Date & Time” of the technical log.

If the operations type is “Repair Station”, the system updates the compliance date of the work units in the compliance history of the “Aircraft” business component, based on the option set for the “Ref. Date for Compliance against Repair Station” in the “Set Options” activity. If the option setting is “Start Date”, the system considers the start date of the technical log. If the option setting is “End Date”, the system considers the end date of the technical log. If the option setting is “User Defined”, the system considers the compliance date specified in the “Record Work Unit & Sign-off Information” page.

Note: The compliance date specified in the “Record Work Unit & Sign-off Information” page should lie between the “Actual Start Date & Time” and “Actual End Date & Time” of the technical log.

Note: If any work unit of the current technical log is “Pre-Closed”, the system updates the compliance details in the Compliance Tracking & Control pending tray based on the option setting.

Note: The system calculates the next schedule for incomplete work units based on usage schedules.

Note: The system does not perform the above updates for work units whose source is “Maintenance Event”.

For the planned work units, if the execution status of the planned work units is “Completed” in the technical log, the system updates the compliance details in their corresponding “Aircraft Maintenance Program” or “Component Maintenance Program”.

If the “Enforce Excess/Core Returns?” field in the “Set Options” activity is set as “No”,  the technical Log gets confirmed without checking for the pending return qty.

If the “Enforce Excess/Core Returns?” field in the “Set Options” activity is set as “Yes”, ensure that the following conditions are satisfied for work units available in the “Record Material & Report Consumption” page:

• “Issued Quantity” is specified for the corresponding part number and material request number.

• “Pending Return Qty” and “Pending Return Qty-Core“ is zero, when the “Enforce Excess/Core Returns ?” field in the “Set Options” activity is set as “Yes”.

The system will short close the material requests associated to the technical log, which are in “Authorized” or “Partially Issued” status. While short closing, Issue or Stock Transfer Issue documents, if any, created in “Fresh” status for those material requests, will be canceled. Stock Transfer documents associated with such canceled Stock Transfer Issue documents will also be short-closed.

If the “Automatic Confirmation of Maint.Report” option is set to “Yes” in the “Set Options” activity, then the status of the maintenance report is automatically set to “Confirmed” on confirmation. The system also checks whether the login user has been assigned the rights to confirm a maintenance report in the “Discrepancy Processing” component. If the login user does not have the required rights, then the status of the maintenance report will not be automatically confirmed even when the “Automatic Confirmation of Maint.Report” option is set to “Yes” in the “Set Options” activity.

If the work units have been retrieved from the “Opportunity Maintenance” page of the “Compliance Tracking & Control” business component and the execution status of these work units are “Completed”, the system updates the job status of these work units as “Completed” in the “Compliance Tracking & Control” business component.

The system also updates the compliance status of these work units based on the source. If the source of the work unit is “AMP”, the schedule status is left blank in the “Aircraft Maintenance Program” business component. If the source of the work unit is “CMP”, the execution status is updated as “Completed” in the “Component Maintenance Program” business component.

If these work units have any reference to EO or FCD, the system updates the “Engineering Order” business component with the execution comments of the work unit.

The system posts the financial entries to the relevant account codes in the "Finance Book Processing" business component.

The system ensures that component replacement details are recorded for the completed replacement work units reported in the 'Record Work and Sign-Off Information' page.

If component replacement details are available, the system updates them before confirming the technical log.

Note: You cannot confirm a technical log when the component replacement records, with the “Source” set as “Remove”, “Attach” or “Swap”, are not confirmed in the “Replace Components” page.

The system performs the following if component replacement details are available:

• If the component that is getting attached, or any of the child components, has some calender-based schedules and the updation is based on the date of attachment, the system adds the interval to the current replacement date. This date is updated as the next schedule date, in the “Component Maintenance Program” business component, when the next schedule date is blank.

• If the installed component, or any if its child components, has position-based schedules, the system checks if the current aircraft model, configuration class and attached position or its child component has a defined position- based schedule. If so, the system adds the position-based interval to the last schedule date of the work unit for the respective component in the “Component Maintenance Program” business component.

• If the end date is left blank, the warranty date is updated depending on the flag set in warranty agreement for the component, or any of its child components in the “Warranty” business component.

• If the component is removed from PBH assembly, the system updates the ownership as “PBH” and the possession status as “PBH” in the “Aircraft” business component.

• If the “Expense Type” is set as “Capital”, the system updates the “Ownership” of the identified Aircraft Reg # as "Owned" or "Leased Out" in the “Aircraft” business component.

• Ensures that the "Installed Part#", "Installed Serial#" and "Incoming Part Description" fields are entered, when the “Object Type” is set as “Component”.

Note: The above check is not performed for component whose job type is “Component Removal”

• Ensures that the removed component is attached to the aircraft.

The system generates the Component Replacement number and the Cannibalization number for components for which the "Object Type" is set as "Component" in the "Replace component" page only for those records, which do not have a component replacement number.

Note: The system will not generate a component replacement number when outgoing component details are available but incoming component details are not specified.

Note: If the "Source" of the component to be replaced is set as "Cannibialize", the system generates two transactions, one for the aircraft from which the component is removed and replaced, and another for  the aircraft from where cannibalization is done. The status of the first transaction is updated as "Replaced" and the status of the second transaction is updated as "Removed".

Note: If the "Source" is other than "Cannibalize", the system generates only one transaction and updates the status as "Replaced".

To cancel the technical log

• Click the “Cancel Tech Log” pushbutton to cancel the technical log.

Note: Only technical logs that are in the “Fresh” status can be canceled.

Note: This action is workflow-enabled. Notification messages can be sent and you can configure further processing of this document in the "Workflow Management" business component.

Note: The system does not allow you to cancel the technical log, if the selected technical log has been referenced in the purchase order of type “Adhoc PO” or “Service PO”, and if the status of the line item (technical log) is other than “Short Closed” or “Cancelled”.

Note: Ensure that the “Execution Status” of the planned work units is not “Completed” or “Incomplete”.

If the source of work units is “Aircraft Forecast“ or “Component Forecast”, the system updates the execution status of the work units as “Pending”.

If the source of the work units is “Line Package”, the system updates the status of the work units from “Techlog Created” to “Package Created”, and removes the Tech Log # reference in the line package created in the “Line Planning and Control” business component.

Note: If the source of the work units is “Deferred”, the system updates the “Execution Status” of the work units as “Deferred”.

The system will short close the material requests associated to the technical log, which are in “Authorized” or “Partially Issued” status. While short closing, Issue or Stock Transfer Issue documents, if any, created in “Fresh” status for those material requests, will be canceled. Stock Transfer documents associated with such canceled Stock Transfer Issue documents will also be short-closed.

To proceed, carry out the following

• Select the “Record Work & Sign-off Information” link to update  work information.

Refer “Updating work information  – An overview” for more details.

Note: On confirmation of the technical log, the execution status of all the work units specified in the “Report Work Information” page is set to “Completed”.

• Select the “Request Material & Report Consumption” link to update material and report consumption details.

Refer “Updating material request and reporting  consumption for the technical log – An overview” for more details.

• Select the “Replace Components” link to update component replacement details.

Refer “Updating component replacement details for technical log – An overview” for more details.

• Select the “Record Employee Timesheet” link to update employee timesheet information.

Refer “Updating employee actual information for the technical log – An overview” for more details.

• Select the "Perform Opportunity Maintenance" link to update opportunity maintenance details.

• Select the “Defer PIREP & Tech Log Reported Discrepancies” link to defer discrepancies reported in the technical log.

Refer to the “Discrepancy Processing” online help for more details.

• Select the “Edit References” link to edit reference document details for the technical log.

• Select the “Create General Material Request” link to create a material request.

Refer to the “Material Request” online help for more details.

Select the “Create Maintenance Return” link to create a maintenance return document for returning excess stock or core-returnable, if any.

Refer to “Stock Return” online help for more details.

• Select the “Report Resource Consumptions” link to update resource actual information.

• Select the “Release Aircraft” link to update release aircraft details for the technical log.

• Select the “Update Parameter Details” link to update the aircraft parameter values.

• Select the “Print Technical Log” link to preview and print details for the technical log.

• Select the “Report Fuel / Oil Log” link to enter the fuel and oil consumption details.

• Select the “View Journey Log” link to view journey log details.

• Select the “View Aircraft Maintenance Log” link to view the aircraft maintenance log details.

Refer to the “Aircraft” online help for more information.

• Select the “Create CWO/RO” link to process the pending work units that were created for component maintenance work.

•  Select the “View Associated Discrepancies” link to view the details of the selected discrepancy.

Refer to the “Discrepancy Processing” online help for more details.

Recording technical log information – An overview

In this page, the technical log details corresponding to a journey log can be recorded. Aircraft and journey details can also be entered. Both PIREP and technical log discrepancy details can be noted. Additionally, you can edit these details or revise the deferral limits. The maintenance report and the corresponding deferred discrepancy resolution details can be recorded. Also, mechanic and inspector details can be filled in. The technical log details can then be saved, confirmed or cancelled.

What you can do in this page

Choose a numbering pattern to generate the technical log number

Specify the category for the technical log

Set the default action for discrepancies in the multiline

Create technical log

Choose a numbering pattern to generate the technical log number

You can select a numbering type for the technical log. A unique technical log number will be generated by the system based on the numbering type you select in this page.

• Select the numbering type in the “Numbering Type” drop-down list box.

• Enter all other technical log details.

On clicking the “Create Log” pushbutton, the system generates the technical log number based on the selected numbering type.

Specify the category for the technical log

You can select the category to which the technical log belongs.

• Select the category from the “Tech. Log Category” drop-down list box.

• Enter all other details.

Set the default action for discrepancies in the multiline

You can set the default action for all the discrepancies in the multiline.

• Select the action from the “Default Action” drop-down list box.

• Enter all other details.

On clicking the “Create Log” pushbutton, the system updates the default action in all the rows in the multiline.

Create technical log

You can create a new technical log and also confirm the details in the same page.

• Enter the flight, fuel, APU parameter, hydraulic oil and UOM details in the respective group boxes.

• In the multiline, enter the amount of oil in the flight on arrival, and the amount of oil uplifted in the flight before departure.

• Enter the remedial action for the reported discrepancies, in the “PIREP & Tech Log Reported Discrepancies” multiline.

• Enter the remedial action for the deferred discrepancies, in the “Deferred Discrepancy Resolution Details” multiline.

• Enter the outgoing flight details, inspector details and mechanic details in the respective group boxes.

• Click the “Create Log” pushbutton to create the technical log.

The system assigns the “Fresh” status to the created technical log.