Coflyr · Backend model field catalog

CriticalEvent

Administration.CriticalEvents.

6 mapped fields3 field groupsGenerated 2026-10-09Later review

Model class: coflyr.models.administration.CriticalEvent
Source: Features/Administration/CriticalEvents/Models/CriticalEvent.cs
Table: Administration.CriticalEvents
Review: Later review · marked 2026-10-06 · Critical-event category review: proposed AOG-risk, corrosion, critical-work, incident-related, occurrence-reporting and structural-damage flags replace header fields. Engine-change, independent-inspection, ramp-activity, taxi and weight-and-balance requirement flags move from WorkStep into this category. WorkorderMaster retains CriticalEventId; WorkStep adds its own optional CriticalEventId lookup. Backend/database adoption pending complete review. Latest decision: WorkStep task controls are also managed here through proposed ControlOptions; WorkStep.TaskControlProfileId is Dropped in favor of CriticalEventId. The independent-inspection flag is a derived view of the corresponding control option.

Every mapped scalar field appears once. Types and nullability come from the current EF model snapshot. Navigation properties and unmapped DTO fields are outside this page. Purpose text is inferred from names and should be checked against the feature workflow.

Reviewed changes

Proposal: add nullable integer CorrosionLevel here, replacing the work header field. This classifies the selected critical event; backend/database implementation remains deferred.
Proposal: move IsAogRisky, IsCorrosion and IsCriticalPackage from unified WorkorderMaster into CriticalEvent as required Boolean category flags. Keep CriticalEventId on the header; reconcile legacy header values into category selections during later adoption.
Pending complete review: move IsIncidentRelated to CriticalEvent as a required Boolean category flag and mark it Dropped from unified WorkorderMaster. Backend/database changes deferred.
Pending complete review: move IsOccurrenceReport to CriticalEvent as a required Boolean category flag and mark it Dropped from unified WorkorderMaster. Backend/database changes deferred.
Pending complete review: move IsStructuralDamage to CriticalEvent as a required Boolean category flag and mark it Dropped from unified WorkorderMaster. Backend/database changes deferred.
Move RequiresEngineChange, RequiresIndependentInspection, RequiresRampActivity, RequiresTaxi and RequiresWeightAndBalance from the unified WorkStep proposal to CriticalEvent as required Boolean category flags, default false. Add optional WorkStep.CriticalEventId; reconcile combinations and preserve approved/historical requirement values during later adoption. HTML only; backend/database unchanged.
Manage WorkStep task controls through CriticalEvent.ControlOptions using the existing TaskControlOption enum. Mark WorkStep.TaskControlProfileId Dropped in favor of CriticalEventId. Treat RequiresIndependentInspection as derived from ControlOptions, preserving one authoritative setting and the existing inspection-sign closure checks during adoption. Other TaskControlProfile uses remain for separate review; HTML only.
HTML review: add nullable WorkTemplateMaster.CriticalEventId. Move AffectsFlightOperations, AffectsGroundOperations and AffectsSimulator to CriticalEvent as required Boolean category flags and mark their original template rows Dropped. Preserve approved revision and issued-work impact values during later adoption; backend/database unchanged.
HTML review: move ElectricalLoadAffected, MomentChange and WeightChangeKg from WorkTemplateMaster to CriticalEvent; mark original rows Dropped with destination comments/links. Preserve numerical weight/moment types, precision, units and change-specific approved context. This supersedes the prior WeightChangeKg location decision. Backend/database unchanged.
HTML review: mark WorkTemplateMaster.MassAndBalanceAffected Dropped and move its required Boolean impact classification to CriticalEvent, selected through CriticalEventId. Preserve its distinction from RequiresWeightAndBalance and numerical change values. Backend/database unchanged.

WorkStep CriticalEvent lookup

← All model classes · AMOS Workpackage example

WorkTemplateMaster selects this category through CriticalEventId. AffectsFlightOperations, AffectsGroundOperations and AffectsSimulator move here; their former master rows remain visible as Dropped. Operational impacts and required execution actions retain distinct meanings. HTML review only; backend/database adoption pending.

Identity and naming

3 fields

#	Field	EF type	Storage	Business purpose
1	`Id`	`Guid`	Required	Stable identifier for this record.
2	`Code`	`string`	Required	Records code for this critical event.
3	`Name`	`string`	Required	Records name for this critical event.

Descriptions and details

1 fields

#	Field	EF type	Storage	Business purpose
1	`DescriptionText`	`string`	Nullable	Records description text for this critical event.

Audit and revision

2 fields

#	Field	EF type	Storage	Business purpose
1	`SystemAuditId`	`Guid?`	Nullable	Links to system audit history when this model stores the reference.
2	`UpdateId`	`Guid?`	Nullable	Links to the preceding revision or update record.

Proposed shared fields · pending complete review

20 fields

These decisions do not change the current backend table count.

Field	Requested type	Nullability	Purpose	Review
`CorrosionLevel`	`int?`	Nullable	Optional corrosion level associated with this critical-event classification. Work headers select the classification through CriticalEventId instead of storing a separate CorrosionLevel. Preserve the existing nullable integer type; reconcile legacy header values with critical-event records during later adoption.	Merge here Backend / DB pending
`IsAogRisky`	`Boolean`	Required	Indicates that this critical-event category represents aircraft-on-ground risk. A work header selects the category through CriticalEventId instead of storing this flag separately. Backend/database adoption pending complete review.	Merge here Backend / DB pending
`IsCorrosion`	`Boolean`	Required	Indicates that this critical-event category concerns corrosion. CorrosionLevel remains a separate optional category field; a work header selects the category through CriticalEventId. Backend/database adoption pending complete review.	Merge here Backend / DB pending
`IsCriticalPackage`	`Boolean`	Required	Indicates that this critical-event category classifies the associated work header as critical and requiring special attention. Retain the reviewed name pending further review. This flag alone does not define priority, approvals, release rules or evidence requirements; no dedicated workflow use was found in the current implementation. Backend/database adoption pending complete review.	Merge here Backend / DB pending
`IsIncidentRelated`	`Boolean`	Required	Indicates that this critical-event category is related to an incident. WorkorderMaster selects the category through CriticalEventId instead of storing this flag separately. This flag does not identify a particular incident record. Backend/database adoption pending complete review.	Merge here Backend / DB pending
`IsOccurrenceReport`	`Boolean`	Required	Indicates that this critical-event category flags associated work for inclusion in an occurrence-reporting workflow. WorkorderMaster selects the category through CriticalEventId instead of storing this flag separately. This flag does not identify a report or mean one has been created, submitted or accepted. Reporting integration and backend/database adoption remain pending complete review.	Merge here Backend / DB pending
`IsStructuralDamage`	`Boolean`	Required	Indicates that this critical-event category concerns structural damage. WorkorderMaster selects the category through CriticalEventId instead of storing this flag separately. This flag classifies the work; it does not identify a particular damage record or establish its severity, repair instructions or approval. Damage-workflow integration and backend/database adoption remain pending complete review.	Merge here Backend / DB pending
`RequiresEngineChange`	`Boolean`	Required	Indicates that this critical-event category requires an engine change. Identify engines, positions, replacement parts and removal/installation evidence through the applicable component-change records. A WorkStep selects this category through CriticalEventId. Preserve existing false/true requirements and review mapping of combinations to categories; changing a reusable category must not silently rewrite historical or approved revision requirements. Backend/database adoption remains pending complete review.	Merge here Backend / DB pending
`RequiresIndependentInspection`	`Boolean`	Required	Independent-inspection requirement for this category, derived from whether ControlOptions includes TaskControlOption.RequiresIndependentInspection. Retain this prior field proposal for review; do not implement it as a second independently editable setting. Preserve legacy repository revision Boolean values when mapping to ControlOptions and retain the required signed inspection evidence before workstep closure. Historical requirements must remain stable when categories change. Backend/database adoption remains pending complete review.	Merge here Backend / DB pending
`RequiresRampActivity`	`Boolean`	Required	Indicates that this critical-event category requires ramp activity. Specific activities, locations, resources and bookings belong to the operational planning records. A WorkStep selects this category through CriticalEventId. Preserve existing false/true requirements and review mapping of combinations to categories; changing a reusable category must not silently rewrite historical or approved revision requirements. Backend/database adoption remains pending complete review.	Merge here Backend / DB pending
`RequiresTaxi`	`Boolean`	Required	Indicates that this critical-event category requires aircraft taxiing. Routes, crew, times and movement authorization belong to the movement workflow. A WorkStep selects this category through CriticalEventId. Preserve existing false/true requirements and review mapping of combinations to categories; changing a reusable category must not silently rewrite historical or approved revision requirements. Backend/database adoption remains pending complete review.	Merge here Backend / DB pending
`RequiresWeightAndBalance`	`Boolean`	Required	Indicates that this critical-event category requires aircraft weighing or weight-and-balance work. Measurements, calculations and resulting reports belong to the relevant execution records. A WorkStep selects this category through CriticalEventId. Preserve existing false/true requirements and review mapping of combinations to categories; changing a reusable category must not silently rewrite historical or approved revision requirements. Backend/database adoption remains pending complete review.	Merge here Backend / DB pending
`ControlOptions`	`TaskControlOption[] (multi-select)`	Required	Multi-select task controls managed on this CriticalEvent category, replacing the WorkStep-specific TaskControlProfile selection. Reuse the existing TaskControlOption enum and its numeric values; allow an empty list when no task controls apply. Options: IsAd, IsAli, IsCdccl, IsCmr, IsCpcp, IsCriticalTask, IsEtopsRelevant, IsEwis, IsFal, IsInsuranceWork, IsSsid, IsWarrantyWork, RequiresDefuel, RequiresDoubleInspection, RequiresElectricalPowerOff, RequiresExternalHydraulic, RequiresHydraulicPowerOff, RequiresIdleTestRun, RequiresIndependentInspection, RequiresNdt, RequiresPowerRun, RequiresReinspection, RequiresTankEntry, RequiresTestFlight, RequiresTroubleshooting. Double inspection also requires independent inspection. Preserve current closure requirements for signed independent-inspection, double-inspection and reinspection entries; other controls require their respective workflow review. Reconcile the previously proposed RequiresIndependentInspection Boolean with this option: it must be derived from ControlOptions rather than independently editable, so the category has one authoritative requirement. Map existing profile combinations and inherited controls to categories, preserve approved/historical values, and define category revision behavior before adoption. Backend/database and UI implementation remain pending complete review.	Merge here Backend / DB pending
`AffectsFlightOperations`	`Boolean`	Required	Indicates that the selected critical-event classification identifies changes affecting flight procedures or flight operations. This describes operational impact, separately from execution requirements such as RequiresTaxi. WorkTemplateMaster selects the category through CriticalEventId. Preserve existing engineering-order Boolean values through an explicit category mapping and freeze impact values for approved revisions and issued work; later category edits must not rewrite historical requirements. Backend/database adoption pending complete review.	Merge here Backend / DB pending
`AffectsGroundOperations`	`Boolean`	Required	Indicates that the selected critical-event classification identifies changes affecting ground handling or ground operating procedures. This describes operational impact, separately from execution requirements such as RequiresTaxi. WorkTemplateMaster selects the category through CriticalEventId. Preserve existing engineering-order Boolean values through an explicit category mapping and freeze impact values for approved revisions and issued work; later category edits must not rewrite historical requirements. Backend/database adoption pending complete review.	Merge here Backend / DB pending
`AffectsSimulator`	`Boolean`	Required	Indicates that the selected critical-event classification identifies changes affecting simulator configuration or training. This describes operational impact, separately from execution requirements such as RequiresTaxi. WorkTemplateMaster selects the category through CriticalEventId. Preserve existing engineering-order Boolean values through an explicit category mapping and freeze impact values for approved revisions and issued work; later category edits must not rewrite historical requirements. Backend/database adoption pending complete review.	Merge here Backend / DB pending
`ElectricalLoadAffected`	`Boolean`	Required	Indicates that the selected change affects electrical load and requires the applicable electrical-load review. This Boolean does not store a load calculation, identify circuits or prove that review is complete. WorkTemplateMaster links through CriticalEventId. Numeric weight/moment values are specific to the approved change and asset/configuration context; reusable category selection must not apply one change value indiscriminately to unrelated templates or aircraft. Preserve the selected category/version and values in approved revisions and issued work; later shared-category edits must not rewrite historical values. Backend/database move and context/ownership validation remain pending complete review.	Merge here Backend / DB pending
`MomentChange`	`Decimal?`	Nullable	Proposed signed numerical change in moment for the specific approved engineering change. Preserve the legacy numeric(18,3) precision. The legacy field does not declare a unit; establish and retain the applicable moment unit, reference datum and calculation context explicitly before adoption. Do not convert this value to a Boolean. WorkTemplateMaster links through CriticalEventId. Numeric weight/moment values are specific to the approved change and asset/configuration context; reusable category selection must not apply one change value indiscriminately to unrelated templates or aircraft. Preserve the selected category/version and values in approved revisions and issued work; later shared-category edits must not rewrite historical values. Backend/database move and context/ownership validation remain pending complete review.	Merge here Backend / DB pending
`WeightChangeKg`	`Decimal?`	Nullable	Proposed signed numerical weight change in kilograms for the specific approved engineering change. Preserve the legacy numeric(18,3) precision, sign and unit. This value does not itself establish the resulting aircraft weight or center of gravity, and is distinct from a flag requesting weight-and-balance work. WorkTemplateMaster links through CriticalEventId. Numeric weight/moment values are specific to the approved change and asset/configuration context; reusable category selection must not apply one change value indiscriminately to unrelated templates or aircraft. Preserve the selected category/version and values in approved revisions and issued work; later shared-category edits must not rewrite historical values. Backend/database move and context/ownership validation remain pending complete review.	Merge here Backend / DB pending
`MassAndBalanceAffected`	`Boolean`	Required	Indicates that the selected engineering change affects aircraft/component mass and balance. WorkTemplateMaster selects this category through CriticalEventId. This impact classification is distinct from RequiresWeightAndBalance, which requests work, and from numerical WeightChangeKg and MomentChange values. The flag does not calculate or approve weight and balance. Preserve legacy Boolean values and approved/historical category context; backend/database adoption pending complete review.	Merge here Backend / DB pending