TimeRequirements

Maya creates “Inspect the hydraulic filter”. Coflyr gives that record its own ID automatically.

What this means in practice Another record can select this exact inspection even if Maya later changes its title. Each inspection rule, limit and meter reading gets a separate ID.

Maya enters 1 for the hours limit and 2 for the calendar limit.

What this means in practice The screen can show hours first and months second. These numbers do not mean one hour or two months.

Maya selects a maintenance-programme document and enters “Task 29-10-00, paragraph 3”.

What this means in practice When someone asks why this inspection exists, they can open the document and find the paragraph instead of searching the whole manual.

The inspection applies only to aircraft fitted with pump P100. Maya selects the applicability record for those aircraft.

What this means in practice The intended rule covers those aircraft. Aircraft with a different pump should not receive it just because they belong to the same fleet; adoption must enforce this link.

Maya creates the main “Filter inspection” rule. On both its 500-hour limit and its six-month limit, she selects “Filter inspection” as the parent.

What this means in practice Both limits belong to the same inspection. This does not mean one task must happen before another; it organizes the timing records.

Maya selects “Operator Maintenance Programme — Revision 12”.

What this means in practice The requirement points to a real document record instead of just typed text. Historical work must keep the version that was used, even when Revision 13 is issued.

For an hours counter, Maya selects the existing “Hours” unit. For a cycles counter, she selects the existing “Cycles” unit.

What this means in practice The record stores the selected unit’s ID and shows its code/name or symbol. Users choose a recognizable unit from a dropdown; they do not type a UUID. The unit says what the number is measured in, not which aircraft owns it.

Maya marks an advisory inspection note as information only.

What this means in practice The note remains useful to planners. This flag’s relationship to mandatory/compliance settings must be resolved before software uses it to suppress scheduling.

The manufacturer controls a pump life-limit instruction. Maya marks it externally controlled.

What this means in practice The team knows changes come from the manufacturer. The flag does not download revisions or approve changes automatically.

A component has an approved mandatory retirement limit. Maya marks the requirement mandatory.

For a counter definition or template, the aircraft setup requires flying-hours and cycles counters; IsMandatory marks those counters as required.

What this means in practice The intended workflow treats the applicable row as mandatory. On requirement rows, reconcile the flag with ComplianceLevel. On counter rows, it governs the counter obligation. The flag alone does not implement enforcement.

A one-time modification inspection uses OneTime. A filter inspection every 500 flying hours uses Repetitive. A requirement with neither old flag set uses NonPeriodic once its source meaning is confirmed.

What this means in practice OneTime prevents automatic repetition for the same applicable subject/context. Repetitive uses structured Interval limits and the approved next-due strategy. NonPeriodic does not automatically schedule repeats or impose a once-only restriction; any independent event activation is defined by the linked event rule.

For illustration, an approved operating-category rule counts 100 actual hours as 120 life-consumption hours.

What this means in practice The adjustment rule supplies the factor. Selecting Yes alone does not tell Coflyr to multiply by 1.2; AMOS describes this in life-limit workflows.

The pump manufacturer issued the inspection instruction. Maya selects that manufacturer’s BusinessPartner record as the issuing organization.

What this means in practice A reviewer sees the selected organization’s name, while the field stores its BusinessPartner identifier. Selecting the issuer does not itself confirm approval.

An investigation requires keeping an inspection history record. The responsible user marks it on hold.

What this means in practice The intended retention workflow preserves it. This does not change when the inspection is due; actual retention enforcement still needs implementation.

A source defines a particular requirement as having “No Limit”.

What this means in practice Do not enter zero to mean unlimited. AMOS distinguishes unlimited first and repeat limits; this single field still needs an explicit mapping.

A source gives a nominal 12-month interval with a specified approved allowance.

What this means in practice The allowed window can be shown only according to the approved rule. Current Coflyr calculations do not apply these tolerances automatically.

A source requires repeated crack checks until a permanent modification is completed.

What this means in practice The completed terminating action ends that inspection sequence where approved. It must not stop unrelated inspections.

The hours limit is expected on 30 June; the calendar limit is 1 July. The rule says whichever comes first.

What this means in practice The hours limit controls because it is earlier. If utilization changes, the calendar limit may become the earlier one instead.

A shop process counter is allowed to restart after an approved reset event.

What this means in practice The reset operation may be permitted. It must not be used simply to erase aircraft total hours or make an overdue inspection disappear.

A six-month inspection starting on 1 January 2026 is due on 1 July 2026.

What this means in practice A planner sees 1 July as the deadline. If an exact time matters, the timestamp field and the agreed calendar/timezone rule are also needed.

An aircraft has 300 flying hours left and usually flies five hours per day.

What this means in practice The estimate is about 60 days away. If it starts flying less, this estimate changes; the approved hours limit does not.

The approved rule says count from the deferral date, so Maya selects FromDeferralDate.

What this means in practice The calculation must use that recorded date rather than discovery time. Whether this field is needed for other kinds of timing records still needs review.

Maya chooses LastAccomplishment for a 500-hour repeat inspection completed at 1,000 aircraft hours.

What this means in practice Start counting from 1,000, so the next counter deadline is 1,500 hours. Choosing Installation would require the installation reading instead.

The source says inspect after 500 flying hours OR six months, whichever comes first.

For separate groups, if group A gives a June deadline and group B gives a September deadline, WhicheverComesFirst selects June.

What this means in practice Plan for the earlier deadline. Do not wait until both limits are exceeded. Other logic choices need explicit approved rules and implementation support.

The inspection was due at 1,500 hours but was done early at 1,480. The repeat interval is 500 hours.

What this means in practice Counting from completion gives 1,980. Counting from the previous due value gives 2,000. The selected approved strategy decides which applies.

Task A finishes at 09:00. A linked rule requires task B two hours later.

What this means in practice Task B is due at 11:00 even if the aircraft never flies. These are elapsed hours, not flying hours.

An approved rule requires action 30 elapsed days after 1 May at 08:00 UTC.

What this means in practice The deadline is 31 May at 08:00 UTC. Unlike DueDate, this field retains the time of day.

The inspection was last done at 1,000 flying hours and repeats after 500 more.

What this means in practice DueValue is 1,500 hours. It is not 500; 500 is the interval amount.

A qualification-related timing record says the qualification is valid through 31 December.

What this means in practice This can support validity checking under defined rules. It is not automatically an aircraft inspection deadline; the intended role needs review.

For the hours limit Maya enters 500 and selects flight hours. For the other limit she enters 6 and selects calendar months.

What this means in practice 500 means 500 additional flying hours; 6 means six months. The unit and starting point are necessary to calculate the deadline.

Maya writes “Inspect the hydraulic filter for the condition specified in the approved procedure”.

What this means in practice People understand the obligation. The timing and the detailed work instructions still come from their controlled records.

Maya changes the approved interval after review; the record links to its audit history.

What this means in practice A reviewer can find who changed it and when. This ID does not represent an interval, aircraft or meter reading.

The new requirement version links to the version it replaces.

What this means in practice The history can be followed. This is different from selecting the parent inspection that owns a limit; the exact version-link rules still need adoption review.

The saved note says “1,000 + 500 = due at 1,500 hours; current 1,200; remaining 300”.

What this means in practice A planner can check the arithmetic. If a required reading is missing, this field can explain that instead of showing a misleading deadline.

A legacy record contains 5 days of grace.

What this means in practice The team must check the approved source before using those five days. The field alone does not authorize completing a mandatory inspection late.

Maya selects the BusinessPartner record for the regulatory or jurisdiction authority identified by the controlled compliance document.

What this means in practice A reviewer sees the selected regulatory authority’s name, while the field stores its BusinessPartner identifier. The source publication, version and clause still identify the applicable rules; selecting an authority alone does not prove approval or applicability.

A qualification expires on 31 December, and its renewal window is 30 days.

What this means in practice The intended workflow can begin renewal planning 30 days before expiry. It does not allow 30 extra days after expiry.

Maya enters HYD-FILTER-INSPECTION-01.

What this means in practice People can search or quote the code. The computer still keeps a separate permanent ID, and the code is not an hours/cycles counter code.

The first inspection at 5,000 cycles has RequirementType = Threshold. Repeat inspections every 500 cycles have RequirementType = Interval.

What this means in practice A threshold means “first due”; an interval means “repeat after this much more”. Keep RequirementType consistent with the LimitType of its individual limits.

Maya enters “Hydraulic filter inspection”.

What this means in practice People recognize the requirement without decoding its business code. The title itself does not configure the 500-hour interval.

The inspection instruction comes from a manufacturer publication, so Maya chooses Publication.

What this means in practice The origin is clear. It is different from how a meter reading was entered; legacy SourceKind values must be reconciled here.

Maya adds the manufacturer portal link for the inspection instruction.

What this means in practice A reviewer can reach the source more quickly. The selected publication and version are still necessary because content at a link can change.

The aircraft has 300 flying hours left and is expected to fly five hours per day.

What this means in practice The estimate is 60 days. This is a forecast, not permission to fly for 60 days regardless of the actual hours accumulated.

A qualification’s validity duration is 12, with Months selected.

What this means in practice The duration means twelve months. The agreed starting event is still needed to calculate the exact expiry date.

Maya enters 12 and selects Months in ValidityPeriodUnit.

What this means in practice The record describes a one-year validity period, if that is the approved rule. It does not describe a 12-day renewal window.

For “500 flying hours” select FH. For “six calendar months” select MO.

What this means in practice Coflyr can interpret the amount. AMOS uses AH for APU hours and OD for operational days; current Coflyr OD handling differs and needs review.

A source says first inspect at 5,000 cycles, then every 500 cycles.

What this means in practice Create a Threshold of 5,000 and an Interval of 500. The first number is not automatically reused as the repeat interval.

An approved rule applies to components from 5,000 to below 10,000 cycles. Enter 5,000 as the lower boundary.

What this means in practice The range selects the applicable rule. It is not the amount of extra cycles allowed before the inspection; boundary treatment must be explicitly defined.

An AMOS example is due at 6,000 cycles, with an early window beginning at 4,000 cycles; the negative allowance is 2,000 cycles.

What this means in practice This describes the early window. It does not mean subtract 2,000 from all future deadlines; next-due treatment depends on the approved strategy.

A source gives a nominal 12-month interval with a specified one-month positive allowance.

What this means in practice The allowance can be considered only under its approved rules. It must not automatically shift every later interval or act as a blanket extension.

One approved interval applies below 10,000 cycles; another applies from 10,000 cycles.

What this means in practice The boundary decides which interval is relevant. Define inclusivity so an asset at exactly 10,000 does not fall into both rules or neither.

The previous inspection was completed on 1 January 2026 at 08:00 UTC.

What this means in practice That timestamp is saved as the starting point before adding six calendar months. TimeBaselineType explains why that starting point was chosen.

The previous inspection was completed when the aircraft had 1,000 flying hours.

What this means in practice Save 1,000 here. Adding the 500-hour interval produces a deadline of 1,500 aircraft hours.

VT-ABC currently has 1,200 flying hours, and a due calculation is saved using 1,200.

What this means in practice When a new flight raises the live total to 1,205, the old saved calculation must still show the 1,200 it originally used.

On 1 May the aircraft has 300 flying hours remaining. At five hours per day, this is about 60 days.

What this means in practice The forecast is around 30 June. If utilization changes, the forecast date changes; the fixed 1,500-hour limit remains the same.

Maya uses five flying hours per day for VT-ABC’s forecast.

What this means in practice 300 hours remaining divided by five hours/day gives about 60 days. This assumption forecasts a date; it does not alter the approved hours deadline.

The counter definition has a default of five flying hours per day.

What this means in practice This may provide an initial forecast assumption. A saved aircraft-specific forecast records the actual assumption used in UtilizationPerDay, which may be different.

A flying-hours counter is classified Hours; a flight-cycles counter is classified Cycles.

What this means in practice The system can check unit compatibility. An APU-hours counter also measures hours, so the broader category alone is not enough to select the correct counter.

Maya writes “Airframe counters”.

What this means in practice The description is helpful, but an actual aircraft-type or part assignment must still identify who receives the bundle.

The latest aircraft hours reading is from yesterday at 18:00.

What this means in practice A planner can judge whether the live total is current. Recalculating a forecast today does not make that old reading a new observation.

A pump’s meter has been replaced and shows 50 hours, but its documented total since new is 2,350 hours.

What this means in practice Its component history must preserve 2,350, not pretend it is a new 50-hour pump. Meter display and total life usage can differ.

Ravi saves a reading of 1,200 flying hours for VT-ABC.

What this means in practice That reading remains 1,200 even after later readings reach 1,205. The latest live total and the history are separate records.

“Filter inspection” is a RequirementDefinition; “500 hours” is a LimitDefinition; “VT-ABC read 1,200 hours today” is a CounterReading.

What this means in practice Although they share one table, they are different kinds of records and need different fields. This type is explicit; it is not guessed from whether a record has children.

An old record contains “Maintenance Programme Revision 12, Amendment 3”.

What this means in practice During adoption, match that text to the correct saved publication/version. This old field stays dropped; unmatched text needs review rather than being discarded.

An old record selects engineer Maya as the person who checked VT-ABC’s connector configuration.

What this means in practice It explains the old reviewer link. The field remains dropped here; this example does not introduce a new active reviewer field.

An old inspection record points to a component task card for pump P100.

What this means in practice Map it to the intended maintenance task explicitly. The owning-task link now belongs to EventRequirements; this old spelling stays dropped.

The work needs an A320 B1 qualification, so the resource rule selects that qualification template.

What this means in practice This answers “what qualification is needed?” A separate timing rule answers “when does it expire or need renewing?” Future competency implementation remains pending.

A required pre-dispatch action is Open until valid evidence shows that it was completed.

What this means in practice The condition can then be recorded as Satisfied under its rules. This is different from reaching a calendar deadline and does not itself authorize release.

An approved deferred-item instruction requires a MaintenanceAction.

What this means in practice The event/condition record identifies that action type. The linked timing rule separately tells the team when it must be done.

The approved workflow requires a check before task B can be completed, so the proposed rule uses BlockCompletion.

What this means in practice Implementation must enforce that particular gate using evidence. Storing the choice alone does not create a working block.

An approved deferred-item instruction contains a particular operating restriction, which is recorded with its source.

What this means in practice People can read the actual restriction. Its exact wording comes from the approved instruction, not from a generic deadline field.

The restriction concerns ground handling, so the category is GroundHandling.

What this means in practice The category organizes the restriction. The actual instruction and conditions must still be recorded separately.

An approved deferred item requires a check described in a specified maintenance procedure.

What this means in practice The team can identify what work is required. The time rule separately controls when it must be performed.

A defect’s approved MEL item is marked NoGo.

What this means in practice Rectification and the authorized release process are required as applicable. A future due date does not cancel the prohibition.

An approved deferred-item instruction requires a specified operating procedure until rectification.

What this means in practice The instruction is visible to the relevant users. It does not define the maintenance interval by itself.

The instruction specifies an “INOPERATIVE” placard at a stated location.

What this means in practice The team knows the required wording. Separate evidence must show that the required placard was actually installed.

The approved deferred item requires a placard, so its event condition records Yes.

What this means in practice Yes means an obligation exists, not that someone has already fitted the placard. Completion evidence is still needed.

A qualification check is required before assigning the technician to the task.

What this means in practice The future workflow must check the qualification before assignment. This is not a time interval and is not enforced merely by saving the flag.

An organization-defined check must be satisfied before that person certifies the relevant work.

What this means in practice The authorization and condition need to be validated together. This flag does not grant the person a privilege.

An independent check must be evidenced before the applicable release process.

What this means in practice The release workflow must verify that evidence. Completing the timing calculation or marking a task complete is insufficient.

The rule starts when a component-installation event occurs for the relevant asset.

What this means in practice The actual installation event supplies the starting time. Selecting an event definition does not mean an installation has already occurred.

Task A is “Install the component”; task B is “Perform the follow-up leak check”.

What this means in practice When valid completion of task A is matched, the timing rule for B can start. B is selected through its own owning-task link.

The follow-up check begins counting after the installation task is completed, so choose AfterTaskCompletion.

What this means in practice A start event would not be enough. The event rule must match valid completion evidence and supply the correct timing baseline.

The event requirement selects defect DD-104.

What this means in practice Its conditions and linked rectification timing belong to DD-104. Another deferred defect must have its own context even if the same kind of rule applies.

A reusable “Component installation” event definition owns a related requirement.

What this means in practice That is the description of the event kind. An actual installation on VT-ABC is a separate occurrence with its own time and evidence.

The filter-inspection task belongs to the operator’s approved maintenance programme.

What this means in practice The source programme and approved version remain traceable. The detailed hours/months limits are managed through linked timing records.

For the follow-up rule, select task B, “Perform leak check”.

What this means in practice This identifies the work being made due. TriggerMaintenanceTaskId can separately select task A, whose completion starts the rule.

An old record points to the page containing the inspection instruction.

What this means in practice Preserve that old page reference during review. A page ID is not automatically the same as the full publication’s ID.

A resource or event obligation is associated with a particular operation-specification record.

What this means in practice The business context is linked there. A separate time requirement can govern a relevant review/validity date; this old timing field stays dropped.

An organization’s certifying authorization requires a particular qualification.

What this means in practice The qualification requirement belongs under that authorization. A linked time rule can separately govern renewal.

An A320 qualification template contains a practical-assessment requirement.

What this means in practice The resource requirement is organized under that template. Its parent is not the date from which an inspection interval is counted.

An old child rule points to the main filter-inspection rule.

What this means in practice Preserve that relationship under the new name. The old spelling stays dropped; it does not create a second parent link.

A resource requirement selects replacement filter part P100.

What this means in practice This answers which part is required. PartMasterId retained in the timing proposal has a different role: assigning a counter setup to a part number.

An old interval-review record identifies Maya as process owner.

What this means in practice This described responsibility, not the timing calculation. Keep the legacy link available for reconciliation rather than assuming it is an inspection deadline input.

Two inspection requirements were placed under the old “Hydraulic checks” group.

What this means in practice The old grouping must be mapped explicitly. Do not assume it means one task must wait for the other, or that it defines earliest/latest timing logic.

An event obligation is associated with a defined operational safety scope.

What this means in practice The safety context is stored with the event requirement. Any related review deadline can be expressed by a separate linked time rule.

An old record contains “Maintenance Programme MP-01”.

What this means in practice Match it to the correct controlled publication record and preserve unmatched information for review. Do not simply erase the text.

An old inspection requirement says “Revision 12”.

What this means in practice Keep that edition associated with historical work when mapping to controlled publications. Do not silently replace it with today’s latest revision.

One old field says Regulation and another says Regulatory.

What this means in practice Review and map the combined source meaning explicitly. This old field stays dropped rather than remaining a second independently editable classification.

The 500-hour limit previously selected the main filter-inspection requirement through RequirementId.

What this means in practice It still belongs to that requirement after the rename. The old spelling stays dropped; ownership is not removed.

An inspection done at 1,480 hours has a 500-hour repeat interval and uses completion as its starting point.

What this means in practice The next due value remains 1,980 after the field mapping. Renaming must not change the approved strategy.

An old calendar rule starts from the component’s installation date.

What this means in practice After the rename it still starts from installation, not manufacture or today. The actual installation date must remain available.

The hours and months limits in a group use whichever comes first.

What this means in practice That choice survives the mapping. TimeGroupLogic remains the separate choice between different groups.

A limit was shown second using Sequence = 2.

What this means in practice It stays second under SequenceNo = 2. The number does not become an interval amount or a group identity.

The flying-hours definition used Dimension = Hours.

What this means in practice Map it to CounterValueDimension = Hours. A maintenance deadline can still separately use Dimension = FH; these fields describe different levels of meaning.

A historical reading was imported, so its old Source is DataImport.

What this means in practice It remains an imported reading after mapping. The source of the inspection rule, such as a publication, is recorded separately in SourceType.

Group 1 contains one set of hours/months limits; group 2 contains a different approved set.

What this means in practice They must not be accidentally combined when adopting the shared table. AMOS uses group numbers to match its editor and diagrams, so the lost grouping identity needs an explicit solution.

Code H had the name “Flight hours”.

What this means in practice The name helped people understand the code. AMOS requires a counter name; dropping this field in Coflyr still leaves a naming/display decision to resolve later.

The old bundle “Standard A320 counters” contained flying-hours and cycles setups.

What this means in practice The bundle’s member counters and assignments must survive even if this name field is dropped. Review how the bundle will be identified for users.

For a 500-flying-hour inspection, Maya selects the “Flight hours” counter definition.

What this means in practice Coflyr knows the rule uses flying hours. It still needs the particular aircraft’s counter to know how many hours that aircraft has flown.

A source rule uses one interval below 10,000 cycles and another above it. Maya selects “cycles” as the range unit.

What this means in practice The range is checked in cycles, not hours. The exact treatment of the 10,000 boundary must be defined before implementation.

Maya selects “VT-ABC — Flight hours”, currently showing 1,200 hours.

What this means in practice The inspection uses VT-ABC’s hours. It must not use VT-DEF’s hours even though both counters measure the same thing.

Maya selects “VT-ABC filter inspection — June 2026 occurrence”.

What this means in practice The calculated deadline is saved against this occurrence. The next inspection will be a different occurrence with its own saved calculation.

Maya assigns the standard flying-hours and cycles counters to the A320 aircraft type.

What this means in practice This describes the counter setup for the type. VT-ABC and VT-DEF still keep separate actual readings.

Maya selects “Standard aircraft counters”, containing flying hours, cycles and calendar age.

What this means in practice The bundle can be assigned together instead of choosing the same counter setups repeatedly. It is different from a group of inspection deadlines.

Pump part P100 needs flying-hours and cycles counters. Maya selects P100 for the counter-group assignment.

What this means in practice All applicable serialized P100 pumps can receive that setup. Each individual pump still has its own usage history.

Maya chooses Part, then selects pump part P100.

What this means in practice The assignment is treated as a part assignment. Choosing AircraftType instead would require selecting an aircraft type.

Maya selects aircraft VT-ABC.

What this means in practice The 1,200-hour total belongs to VT-ABC. It is not a fleet-wide total or the total for every aircraft of the same type.

VT-ABC’s flying-hours counter selects the standard “Aircraft flight hours” setup.

What this means in practice The setup explains how the counter is intended to work. The aircraft’s actual 1,200 hours are stored on its own counter, not in the reusable setup.

A pump is fitted when VT-ABC has 10,000 flying hours. The pump’s counter selects VT-ABC’s hours counter as its master.

What this means in practice If the aircraft flies another 300 hours before removal, those 300 hours can be attributed to the pump’s installation period under the adopted counting rules.

Maya selects pump P100, serial S123.

What this means in practice The usage belongs to that particular pump. Another P100 pump with serial S124 must have its own history.

Flight log FL-204 records a 2.5-hour flight. The new hours reading links to FL-204.

What this means in practice A reviewer can trace the increase from 1,197.5 to 1,200 hours back to the flight that produced it.

Maya prepares a revised interval as New, then it is activated through the approved process.

What this means in practice The active rule can be used for new work. Earlier work keeps its original rule version; completing an inspection is a different action.

The rule is Active, and the inspection is Planned for a June maintenance visit.

What this means in practice Planners can see progress. The method for deriving this summary from individual work occurrences still needs definition.

An aircraft leaves the fleet, so its usage counter is deactivated.

What this means in practice Its historical readings remain. AMOS deactivation stops new automatic readings; this is different from closing a maintenance task.

One aircraft needs an approved different APU-hours formula.

What this means in practice That aircraft can keep its special rule while the other aircraft retain the standard setup. The exact per-row implementation still needs review.

Ravi looks at a component’s meter and sees 8,420.5 hours.

What this means in practice He can record that physical reading. AMOS readable counters do not calculate readings from formulas; Coflyr’s input-mode rules must be reconciled with that.

A received pump has no reliable since-new hours record.

What this means in practice Mark the total unknown instead of pretending it is zero. In AMOS this marker does not stop every future reading or calculation.

Group A produces a June deadline and group B produces a September deadline. The source says use the earlier group.

What this means in practice June is selected. This differs from choosing between hours and months inside a single group; the group links must remain clear after GroupNumber is dropped.

Maya enters “Left main landing gear”.

What this means in practice A person can identify the relevant area. The text does not calculate a deadline or select a structured location record by itself.

The source says the requirement applies to model A320-214.

What this means in practice The intended applicability is narrower than the whole aircraft family. Adoption must reconcile this text with the actual aircraft/model records.

A fleet uses subtype code SUB-A for aircraft with a particular approved configuration.

What this means in practice The code helps describe which subgroup is intended. Its exact meaning must come from the fleet’s defined codes, not from guessing the abbreviation.

Maya enters the source’s aircraft-type code, A320.

What this means in practice This describes the requirement’s applicability. It is different from AircraftTypeId on a counter-group assignment, which selects an actual saved aircraft-type record.

The instruction affects old connectors. VT-ABC has the new connector, so a reviewer records NotApplicable with evidence.

What this means in practice The applicability decision is visible. It must be established before treating an aircraft as exempt; a due calculation does not decide it.

The reviewer writes “Not applicable: delivery configuration confirms the new connector is already installed”.

What this means in practice Another reviewer can understand and check the decision instead of seeing only a Yes/No status.

The engineer checks the configuration on 15 April at 10:00.

What this means in practice The review timestamp is recorded. It does not mean the inspection is due on 15 April or that the rule starts that day.

An approved seasonal inspection rule applies from 1 November.

What this means in practice The rule is relevant from that date. Its interval and starting point still determine the actual inspection deadlines.

The seasonal rule applies until 31 March.

What this means in practice The applicable period ends then, but past inspection records must remain. Outstanding obligations need explicit treatment rather than being silently erased.

The June inspection’s calculation selects the approved “500 flight hours” limit.

What this means in practice Later, if the programme changes to 450 hours, reviewers can still see that the June calculation was made using the earlier 500-hour rule.

Ravi reads a pump meter during workorder WO-1042 and enters WO-1042 as the reference.

What this means in practice Someone can find the supporting workorder later. Typing the workorder number does not itself add hours to the counter.

Ravi chooses Workorder and enters reference WO-1042.

What this means in practice Coflyr knows WO-1042 is a workorder reference. This differs from saying the reading was entered manually.

Maya creates a heading called “Landing gear checks”.

What this means in practice Individual checks appear beneath it. The heading itself should not accidentally become a maintenance task with a deadline.

A source counter record has IsCounterGroup = Yes.

What this means in practice This is not enough to know which counters it groups. Keep it under review; the explicit counter-template group records identify actual bundle membership.

The aircraft setup requires flying-hours and cycles counters.

What this means in practice Those counters must be maintained under the adopted rules. An optional inspection can still use them; counter obligation and inspection obligation are different.

An earlier entry says 1,020 hours, but the signed record shows 1,200 hours.

What this means in practice The correction needs supporting evidence. The 180-hour difference must not be mistaken for a newly flown 180-hour flight.

A component was manufactured on 1 January 2025 and has an approved two-year age limit.

What this means in practice Its age-based deadline can be calculated from manufacture. Installing it later does not silently change that starting date.

Maya writes “Use the earlier of the hours and calendar deadlines”.

What this means in practice A reviewer understands the intention. The structured calculation setting must agree with the note; prose alone does not configure the calculator.

Maya writes “Total APU running hours recorded for this aircraft”.

What this means in practice Someone selecting a counter can distinguish APU hours from aircraft flying hours even though both are measured in hours.

Maya writes “Counters used for our standard aircraft setup: flight hours and flight cycles”.

What this means in practice A user understands what the bundle is for before assigning it to an aircraft type.

Maya writes “Component counter follows aircraft flying hours while the component is installed”.

What this means in practice A user understands the setup before creating an individual component counter. The description itself is not a calculation formula.

Ravi writes “Corrected 1,020 to 1,200 hours after checking the signed receiving record”.

What this means in practice A reviewer sees the reason for the change instead of suspecting unexplained additional operation. Keep the supporting evidence.

Ravi writes “Physical meter checked during receiving inspection; photograph attached”.

What this means in practice A later reviewer understands how this reading was obtained. The actual numerical value is stored separately.

The June inspection was calculated using Maintenance Programme Revision 12.

What this means in practice Even after Revision 13 is issued, the saved calculation can still explain which approved source was used.

A recurrent qualification timing rule concerns an aircraft type, so its scope is AircraftType.

What this means in practice This classifies the context. The actual qualification template belongs to ResourceRequirements; whether this field belongs on every maintenance timing row still needs review.

A source instruction is assessed as Recommended under the applicable controlled process.

What this means in practice The intended planning treatment differs from a mandatory life limit. This setting must agree with IsMandatory and InfoOnly before enforcement is implemented.

Maya writes “Pumps from the affected production batch listed in the source instruction”.

What this means in practice A reviewer understands the intended coverage. A structured applicability record is still needed to identify the exact assets reliably.

A revision is approved in April but becomes effective on 1 May.

What this means in practice New work uses it according to the controlled adoption rule. The approval/review date and the work’s due date are separate dates.

A new approved counter setup is valid from 1 January.

What this means in practice The setup’s applicability period starts then. This is not automatically the date an individual component was installed or its meter was read.

The setup is replaced at the end of December.

What this means in practice Its old readings and history must remain. Ending a setup’s validity is not the same as deleting all counters created from it.

Pump S123 is installed when the aircraft has 10,000 flying hours.

What this means in practice This starts measuring the aircraft usage attributable to that installation period. It is not necessarily the pump’s total since-new usage.

The pump is removed when the aircraft has 10,300 flying hours.

What this means in practice 10,300 minus the installation value 10,000 gives 300 hours during that installation, under the approved counting rules.

An approved reset for a shop process counter uses value 0.

What this means in practice The reset is kept as an evidenced event. AMOS fixed-value resets and current Coflyr resets handle history/differences differently, so do not assume matching behavior.

AMOS uses H for flying hours and C for cycles.

What this means in practice Many aircraft can use the H definition, but each keeps its own hours. The code is not an individual aircraft’s registration or current value.

A deferred defect’s approved MEL item has category C.

What this means in practice The label describes the item’s classification. The exact rectification deadline and conditions must come from the approved item, not from guessing based on the letter alone.

Maya writes “Enter the performed date and the aircraft hours from the signed work record”.

What this means in practice Ravi receives clear completion-recording guidance. The next inspection must use valid accomplishment evidence, not just a clicked Completed button.

Maya places several checks under “Hydraulic periodic inspections”.

What this means in practice The requirements are easier to browse. The label alone does not say whether their deadlines use earliest, latest or another combination rule.

A qualification rule may be an ExaminationRequirement because it requires an examination.

What this means in practice This helps classify that obligation. The retained list contains competency categories, so an appropriate treatment for maintenance-only timing rows still needs review.

An inspection is due this year, but its history must be preserved until a later policy-defined date.

What this means in practice The preservation endpoint is separate from the maintenance deadline. A hold may require keeping the record longer under implemented records rules.

The organization classifies a record as inspection history rather than temporary planning information.

What this means in practice Its retention policy can differ accordingly. Accepted categories and actual enforcement must be defined by the project.

Maya and Ravi open the same rule. Maya saves a change first; Ravi then tries to save his older copy.

What this means in practice The intended update check detects Ravi’s stale copy so he can refresh. This is not the manual’s revision number and users do not normally type it.

Ravi records the inspection as accomplished at 14:30 on 10 June.

What this means in practice The system can preserve that accomplishment time. For a repeating rule, the next inspection is still needed; completion alone does not release the aircraft.

A requirement is attached to an applicability definition, so Maya chooses Effectivity scope.

What this means in practice The scope tells the system what kind of context to expect. EffectivityId must still select the exact saved applicability definition.

The source uses FLEET-A as the code for an aircraft subgroup.

What this means in practice The code only makes sense within its defined context. Do not treat an unrelated part named FLEET-A as the same scope.

The forecast was refreshed yesterday, but a new flight was entered this morning.

What this means in practice A planner can see that the forecast may be stale and needs recalculation. Refresh time is not the time the aircraft’s meter was read.

The aircraft’s 1,200-hour total is associated with 18:00 yesterday; the forecast job runs at 19:00.

What this means in practice The calculation keeps 18:00 as the observation time. Running the job later does not make the underlying reading newer.

The inspection is due at 1,500 flying hours and the aircraft currently has 1,200.

What this means in practice There are 300 flying hours left. If the aircraft has 1,510, the value is −10, meaning it is beyond the nominal threshold, subject to the approved rule.

Ravi reads a meter at 09:00 and enters it at 10:00.

What this means in practice Current Coflyr records 10:00 UTC as entry time. The actual 09:00 observation needs its own preserved context; the two times must not be confused.

The previous aircraft reading was 1,197.5 hours and the new reading is 1,200.

What this means in practice The increase is 2.5 hours. A correction/reset difference needs special interpretation; not every numerical increase is actual flying.

The aircraft hours counter is Master. An installed pump’s hours counter can be Child.

What this means in practice The child follows usage attributable to its installation under the approved counting rules. Standalone means it is not a master/child counter.

Pump serial S123 is installed in the left hydraulic-pump position.

What this means in practice The counter history can be associated with that installation location. Structured configuration consistency still needs explicit validation.

Maya uses AIRFRAME-STD for a bundle containing hours and cycles.

What this means in practice Users can find and assign that bundle. The code does not identify an inspection limit group or a particular aircraft’s counter.

An approved setup specifies what to do if required flight timestamps are missing.

What this means in practice The software can apply a validated rule once implemented. Free text or arbitrary JSON must not be assumed to be a working calculation.

A physical meter is read manually; a flight-hours counter may be calculated from flight logs.

What this means in practice The mode guides permitted entry. AMOS readable counters are not formula-calculated, so Coflyr’s Hybrid choice needs explicit validation rather than assuming it is equivalent.

One aircraft has an approved special APU-hours counting rule.

What this means in practice Its special settings can be saved without changing the standard fleet setup. The project still needs a validated format and implementation for these settings.

Maya gives flying hours display order 1 and cycles display order 2.

What this means in practice Users see flying hours before cycles. This does not decide which counter is calculated first or which inspection deadline controls.

The screen shows 1,200 FH for flight hours and 8,400 FC for flight cycles.

What this means in practice People know what the number measures. Typing a different label does not convert hours into cycles.

Cycles appear as 12,345; flying hours may appear as 1,200.5.

What this means in practice The chosen appearance helps users read the value. Formatting must not silently change the stored quantity or confuse decimal hours with hours-and-minutes notation.

A custom counter needs the flight-duration result, so flight duration is calculated first.

What this means in practice The required input is available before the dependent calculation runs. The design must also reject circular dependencies rather than relying only on an order number.

The approved flying-hours setup derives flight duration from the flight records.

What this means in practice That formula can produce usage increments when implemented and validated. It is different from the inspection rule “repeat every 500 flying hours”.

A calculation uses software rule-engine version 2 and Maintenance Programme Revision 12.

What this means in practice Investigators can distinguish a software-version change from a maintenance-document revision. This value is normally assigned by the software.

The organization records “Keep with the aircraft’s controlled maintenance history”.

What this means in practice Records-management rules can use this information once implemented. This does not change the inspection interval or automatically delete records.

Maya uses REQ-HYD-01 for a hydraulic inspection record.

What this means in practice It helps identify the record in a list. Its distinction from RequirementCode and ShortcutCode still needs review; it does not specify a usage unit.

A reading comes from flight log FL-204, so its source is FlightLog. A technician’s entry is Manual.

What this means in practice Reviewers understand the reading’s origin. This is separate from whether the inspection rule came from a manufacturer publication.

Maya enters “Hydraulic filter inspection”.

What this means in practice The list is easier to read. This name does not tell Coflyr how often to inspect; the interval must be entered separately. Its overlap with RequirementTitle still needs review.

The pump manufacturer issued the inspection instruction. Maya selects that manufacturer from Business Partners.

What this means in practice A reviewer knows who supplied the instruction. The aircraft’s airline is selected only if that airline actually issued the rule.

Maya selects the BusinessPartner record for the jurisdiction authority identified in the controlled compliance record.

What this means in practice Reviewers see the selected authority’s name, while the field stores its BusinessPartner identifier. Selecting it does not automatically determine applicability or verify regulatory compliance.

Maya enters 24, with Months selected in RecurrentFrequencyUnit.

What this means in practice Together they describe a two-year repeat period. The number alone does not say when counting starts.

A recurrent training rule has value 24 and unit Months.

What this means in practice The pair means every 24 months, not every 24 flying hours. Reconcile it with the detailed timing-limit design before choosing one calculation path.

A legacy record says inspect every 500 flying hours.

What this means in practice Use flying hours, not 500 clock hours or APU hours. Reconcile this field with the detailed hours-limit record.

A legacy record says repeat the inspection every 500 flight cycles.

What this means in practice Map it to the reviewed cycle-limit record. Do not evaluate the old field and the new limit as two unrelated obligations.

A legacy inspection rule allows 30 days from installation.

What this means in practice The start date and meaning of “day” are needed. Reconcile it with a detailed 30-day limit so the software does not run two conflicting rules.

The source says the first inspection is due at 5,000 cycles.

What this means in practice The number 5,000 alone is insufficient. Reconcile this old field with the detailed cycle-limit record so two competing calculations are not created.

An aircraft needs a one-time inspection after a modification.

What this means in practice After valid accomplishment, the system should not keep creating another identical periodic inspection unless a separate rule requires one.

The filter must be inspected every 500 flying hours.

What this means in practice After valid completion, another inspection becomes due according to the repeat rule. It is different from a one-time modification check.

Maya uses HYD-FLT as a shortcut for the hydraulic filter inspection.

What this means in practice A planner can search the short code. It does not replace the full business code, source document or permanent record ID.