Coflyr · Backend model field catalog
EngineeringOrder
public.EngineeringOrders.
90 mapped fields8 field groupsGenerated 2026-10-06
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.
← All model classes · AMOS Workpackage example
Dropped as a separate header: merge its fields into WorkTemplateMaster with TemplateType = EngineeringOrder. Preserve technical approval, release, source revisions and per-asset compliance. This retires the separate header proposal, not its business functionality. Original fields remain visible; backend/database adoption pending.
Identity and naming
4 fields| # | Field | EF type | Storage | Business purpose | Review |
|---|---|---|---|---|---|
| 1 | Id | Guid | Required | Stable identifier for this record. | Reviewed |
| 2 | EoNumber | string | Required | Records eo number for this engineering order. | Reviewed |
| 3 | ProjectNumber | string | Nullable | Records project number for this engineering order. | — |
| 4 | Title | string | Required | Records title for this engineering order. | Reviewed |
Relationships and references
2 fields| # | Field | EF type | Storage | Business purpose | Review |
|---|---|---|---|---|---|
| 1 | AtaId | Guid? | Nullable | Selects the related ata record. | Reviewed |
| 2 | ModificationId | Guid? | Nullable | Drop ModificationId from WorkTemplateMaster and replace it with PublicationId, a nullable UUID lookup to PublicationMaster. Resolve legacy modification references to the correct publication explicitly and preserve historical associations; this field replacement does not drop the Modification catalog. Backend/database adoption deferred. | Dropped Removal pending complete review |
Status and controls
33 fields| # | Field | EF type | Storage | Business purpose | Review |
|---|---|---|---|---|---|
| 1 | AffectsFlightOperations | bool | Required | Dropped from WorkTemplateMaster; move to CriticalEvent.AffectsFlightOperations. Select the operational-impact category through CriticalEventId. Indicates that the selected critical-event classification identifies changes affecting flight procedures or flight operations. Preserve legacy values and approved/historical impact snapshots during later adoption. Backend/database adoption pending complete review. | Dropped Removal pending complete review |
| 2 | AffectsGroundOperations | bool | Required | Dropped from WorkTemplateMaster; move to CriticalEvent.AffectsGroundOperations. Select the operational-impact category through CriticalEventId. Indicates that the selected critical-event classification identifies changes affecting ground handling or ground operating procedures. Preserve legacy values and approved/historical impact snapshots during later adoption. Backend/database adoption pending complete review. | Dropped Removal pending complete review |
| 3 | AffectsSimulator | bool | Required | Dropped from WorkTemplateMaster; move to CriticalEvent.AffectsSimulator. Select the operational-impact category through CriticalEventId. Indicates that the selected critical-event classification identifies changes affecting simulator configuration or training. Preserve legacy values and approved/historical impact snapshots during later adoption. Backend/database adoption pending complete review. | Dropped Removal pending complete review |
| 4 | AirworthinessMotivation | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.AirworthinessMotivation definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 5 | ApprovalDecidedAt | DateTime? | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ApprovalDecidedAt nullable timestamp definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 6 | ApprovalRemarks | string | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ApprovalRemarks nullable text definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 7 | ApprovalRequestedAt | DateTime? | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ApprovalRequestedAt definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 8 | ApprovalRequestedWithinDays | int? | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ApprovalRequestedWithinDays definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 9 | ApprovalStatus | int | Required | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ApprovalStatus definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 10 | CommercialMotivation | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.CommercialMotivation definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 11 | ControlledComponent | bool | Required | Reserved for later review. Legacy Boolean whose name suggests controlled component tracking; its precise business meaning and required workflow are not established by current code. Confirm component configuration/compliance ownership before adoption. Retain the field and legacy values; backend/database unchanged. | Later review |
| 12 | CostBudgeted | bool | Required | Dropped from WorkTemplateMaster; reserved for future review of cost ownership and financial workflow. Retain the original EngineeringOrder.CostBudgeted definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 13 | CostCapitalized | bool | Required | Dropped from WorkTemplateMaster; reserved for future review of cost ownership and financial workflow. Retain the original EngineeringOrder.CostCapitalized definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 14 | CustomerRequestMotivation | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.CustomerRequestMotivation definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 15 | DirectMaintenanceCostImprovement | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.DirectMaintenanceCostImprovement definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 16 | DirectOperatingCostImprovement | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.DirectOperatingCostImprovement definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 17 | ElectricalLoadAffected | bool | Required | Dropped from WorkTemplateMaster; move to CriticalEvent.ElectricalLoadAffected and select through CriticalEventId. 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. Preserve legacy values and approved change-specific context; shared category edits must not overwrite approved or historical values. Backend/database move remains pending complete review. | Dropped Removal pending complete review |
| 18 | EoStatus | int | Required | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.EoStatus definition and legacy values for review/history. Backend/database removal and adaptation of existing engineering issuance, effectivity and lifecycle consumers remain pending complete review. | Dropped Removal pending complete review |
| 19 | EtopsMotivation | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.EtopsMotivation definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 20 | FlightSafetyImprovement | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.FlightSafetyImprovement definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 21 | InterchangeabilityAffected | bool | Required | Indicates that the engineering change affects interchangeability of parts or configurations. Example: a new connector fits only the modified wiring harness and cannot directly replace the old connector. The flag does not itself define approved substitutes, compatibility rules or modification applicability. Reviewed in the HTML proposal; backend/database adoption pending complete review. | Reviewed |
| 22 | IsActive | bool | Required | Indicates whether active applies to this engineering order. | Dropped Removal pending complete review |
| 23 | IsRepetitive | bool | Required | Drop IsRepetitive from WorkTemplateMaster. Manage repetition through the linked Requirements record and its applicable time/counter limits, recurrence and compliance rules, selected through RequirementId and the existing requirement relationships. Preserve one-time versus recurring meaning, repeat intervals, baselines, limit-combination logic and approved historical requirements when mapping legacy Boolean values during adoption; do not infer a repeat interval from this flag alone. Backend/database adoption pending complete review. | Dropped Removal pending complete review |
| 24 | IssuedBy | string | Nullable | Drop IssuedBy from the WorkTemplateMaster proposal as requested. Preserve legacy issuer values and historical approved content during deferred backend/database adoption. No replacement field introduced by this decision. | Dropped Removal pending complete review |
| 25 | LabourUnderWarranty | bool | Required | Indicates whether labour under warranty applies to this engineering order. | Reviewed |
| 26 | MaintenanceMotivation | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.MaintenanceMotivation definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 27 | MassAndBalanceAffected | bool | Required | Dropped from WorkTemplateMaster; move to CriticalEvent.MassAndBalanceAffected and select through CriticalEventId. Indicates that the engineering change affects aircraft/component mass and balance and requires the applicable assessment. This impact flag is distinct from RequiresWeightAndBalance (work to perform) and from numerical WeightChangeKg and MomentChange values. Preserve legacy values and approved/historical category context during adoption. Backend/database move remains pending complete review. | Dropped Removal pending complete review |
| 28 | MaterialUnderWarranty | bool | Required | Indicates whether material under warranty applies to this engineering order. | Reviewed |
| 29 | OperationsMotivation | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.OperationsMotivation definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 30 | PerformanceMotivation | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.PerformanceMotivation definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. | Dropped Removal pending complete review |
| 31 | ReliabilityImprovement | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.ReliabilityImprovement definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. This supersedes the earlier separate ReliabilityImprovement Boolean consolidation. | Dropped Removal pending complete review |
| 32 | ReliabilityMotivation | bool | Required | Dropped as a separate Boolean field; merged into the single MotivationText field describing why the work is proposed and its intended benefits. Retain the original EngineeringOrder.ReliabilityMotivation definition and legacy values for review/history. Preserve existing motivation text and explicitly reconcile legacy true/false values during later adoption; do not invent narrative or silently discard source values. Backend/database merge remains pending complete review. This supersedes the earlier separate ReliabilityImprovement Boolean consolidation. | Dropped Removal pending complete review |
| 33 | TrialInstallation | bool | Required | Indicates whether trial installation applies to this engineering order. | Reviewed |
Dates and timing
5 fields| # | Field | EF type | Storage | Business purpose | Review |
|---|---|---|---|---|---|
| 1 | ComplianceDeadlineDate | DateTime? | Nullable | Dropped as a separately stored template field. Link through RequirementId to Requirements and its TimeRequirementLimit rules. Legacy fixed compliance deadline date. Manage this deadline through the selected RequirementId and its calendar/due-limit rules. Preserve the exact existing date, date/time interpretation and its relationship to the hours/cycles limits; define the explicit fixed-date mapping during adoption rather than converting it silently into a relative interval. The approved requirement and limits must remain stable for issued revisions and historical compliance. Original field is Dropped from WorkTemplateMaster and retained visibly for review/history; backend/database adoption pending complete review. | Dropped Removal pending complete review |
| 2 | EoEffectiveDate | DateTime? | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.EoEffectiveDate definition and legacy values for review/history. Backend/database removal and adaptation of existing engineering issuance, effectivity and lifecycle consumers remain pending complete review. | Dropped Removal pending complete review |
| 3 | EoIssueDate | DateTime | Required | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.EoIssueDate definition and legacy values for review/history. Backend/database removal and adaptation of existing engineering issuance, effectivity and lifecycle consumers remain pending complete review. | Dropped Removal pending complete review |
| 4 | ImplementationEndDate | DateTime? | Nullable | End date/time of the overall engineering implementation or rollout. Example: finish fleet rollout by 31 January. The legacy field does not distinguish planned from actual dates; resolve this meaning explicitly during adoption. Per-aircraft execution dates remain on the applicable work records. Reviewed in the HTML proposal; backend/database adoption pending complete review. | Reviewed |
| 5 | ImplementationStartDate | DateTime? | Nullable | Start date/time of the overall engineering implementation or rollout. Example: begin fleet rollout on 1 November. The legacy field does not distinguish planned from actual dates; resolve this meaning explicitly during adoption. Per-aircraft execution dates remain on the applicable work records. Reviewed in the HTML proposal; backend/database adoption pending complete review. | Reviewed |
Amounts and measurements
8 fields| # | Field | EF type | Storage | Business purpose | Review |
|---|---|---|---|---|---|
| 1 | ComplianceThresholdCycles | long? | Nullable | Dropped as a separately stored template field. Link through RequirementId to Requirements and its TimeRequirementLimit rules. Legacy compliance threshold in cycles. Manage this threshold through the selected RequirementId and its structured TimeRequirementLimit cycle dimension. Preserve the counter definition, baseline and cycle value and its combination with the deadline/hours limits. The approved requirement and limits must remain stable for issued revisions and historical compliance. Original field is Dropped from WorkTemplateMaster and retained visibly for review/history; backend/database adoption pending complete review. | Dropped Removal pending complete review |
| 2 | ComplianceThresholdHours | decimal? | Nullable | Dropped as a separately stored template field. Link through RequirementId to Requirements and its TimeRequirementLimit rules. Legacy compliance threshold in hours. Manage this threshold through the selected RequirementId and its structured TimeRequirementLimit flight-hour dimension. Preserve decimal precision, units, counter definition and baseline and its combination with the deadline/cycles limits. The approved requirement and limits must remain stable for issued revisions and historical compliance. Original field is Dropped from WorkTemplateMaster and retained visibly for review/history; backend/database adoption pending complete review. | Dropped Removal pending complete review |
| 3 | CostPerAircraft | decimal? | Nullable | Dropped from WorkTemplateMaster; reserved for future review of cost ownership and financial workflow. Retain the original EngineeringOrder.CostPerAircraft definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 4 | CostPerFleet | decimal? | Nullable | Dropped from WorkTemplateMaster; reserved for future review of cost ownership and financial workflow. Retain the original EngineeringOrder.CostPerFleet definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 5 | EstimatedLabourCost | decimal? | Nullable | Stores the estimated labour cost used by this engineering order. | Reviewed |
| 6 | EstimatedManHours | decimal | Required | Records estimated man hours for this engineering order. | Reviewed |
| 7 | EstimatedMaterialCost | decimal? | Nullable | Stores the estimated material cost used by this engineering order. | Reviewed |
| 8 | WeightChangeKg | decimal? | Nullable | Dropped from WorkTemplateMaster; move to CriticalEvent.WeightChangeKg and select through CriticalEventId. 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. Preserve legacy values and approved change-specific context; shared category edits must not overwrite approved or historical values. Backend/database move remains pending complete review. | Dropped Removal pending complete review |
Descriptions and details
10 fields| # | Field | EF type | Storage | Business purpose | Review |
|---|---|---|---|---|---|
| 1 | AdditionalRequirementsText | string | Nullable | Records additional requirements text for this engineering order. | Reviewed |
| 2 | BackgroundText | string | Nullable | Optional background and technical context explaining the history or situation that led to this template or engineering directive. Example: repeated connector failures led to a manufacturer recommendation for an improved connector. Preserve the existing 4,000-character maximum. Reviewed in the HTML proposal; backend/database adoption pending complete review. | Reviewed |
| 3 | CarryOutText | string | Nullable | Optional implementation summary describing how this template or engineering directive is to be carried out, including references to approved instructions, required tests and compliance recording. Example: replace the connector using the referenced service bulletin, perform the functional test and record compliance. Detailed executable instructions remain on linked WorkSteps. This field is currently included in modification reports. Preserve the existing 4,000-character maximum. Reviewed in the HTML proposal; backend/database adoption pending complete review. | Reviewed |
| 4 | EngineeringText | string | Nullable | Records engineering text for this engineering order. | Reviewed |
| 5 | ImplementationNotes | string | Nullable | Additional implementation guidance and coordination notes. Example: ensure connector kits are available before scheduling each aircraft. Preserve the existing EngineeringOrder 2,000-character maximum. Reviewed in the HTML proposal; backend/database adoption pending complete review. | Reviewed |
| 6 | MotivationText | string | Nullable | Single optional narrative describing why this template or engineering directive is proposed and its intended benefits, consolidating the former motivation and improvement Boolean flags. Example: requested by the customer to reduce recurring connector failures, improve dispatch reliability and lower maintenance costs. Retain the existing 4,000-character maximum and preserve existing MotivationText. Explicitly map/reconcile legacy flags without treating intended benefits as proven results; retain historical source values and approved content. Backend/database consolidation remains pending complete review. | Merge target; backend / DB adoption pending |
| 7 | PlanningText | string | Nullable | Records planning text for this engineering order. | Reviewed |
| 8 | ReasonText | string | Nullable | Reviewed optional narrative explaining the immediate reason for creating the engineering directive. Example: repeated connector overheating prompted this order to introduce an improved connector. AMOS specifies that the reason appears on reports; the current backend includes ReasonText in engineering-order reports. Retain this separate field, nullable string storage, the existing 4,000-character maximum and historical approved content. BackgroundText holds supporting history; MotivationText describes rationale and intended benefits. Backend/database adoption pending complete review. | Reviewed |
| 9 | RecommendationText | string | Nullable | Reviewed optional narrative recording the engineering team’s recommended action or adoption approach for this engineering directive. Example: incorporate the improved connector at the next suitable maintenance visit. Distinct from motivation, implementation consequences and detailed execution instructions. Preserve nullable string storage, the existing 4,000-character maximum and historical approved content. This narrative does not itself approve or release the directive. Backend/database adoption pending complete review. | Reviewed |
| 10 | SafetyText | string | Nullable | Reviewed optional narrative describing the engineering directive's safety considerations, assessment rationale and supporting context for the severity and recurrence-probability selections. Preserve the existing 4,000-character maximum and legacy values. The text does not itself approve the directive or replace formal safety assessment evidence. Backend/database adoption remains pending complete review. | Reviewed |
Audit and revision
2 fields| # | Field | EF type | Storage | Business purpose | Review |
|---|---|---|---|---|---|
| 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. | Reviewed |
Other fields
26 fields| # | Field | EF type | Storage | Business purpose | Review |
|---|---|---|---|---|---|
| 1 | ApprovedBy | string | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ApprovedBy definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 2 | CheckedBy | string | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.CheckedBy nullable text definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 3 | Classification | int | Required | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.Classification enum definition (ApprovedDataOrStandardPractice, AuthorityApprovalRequired) and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 4 | ComplianceType | string | Nullable | Reserved for later review. Legacy free-text compliance category used in modification reports. Review whether the selected RequirementId and its ComplianceTypeDefinitionId should supply this classification. Retain the field and legacy values pending that decision; backend/database unchanged. | Later review |
| 5 | ControlledBy | string | Nullable | Reserved for later review. Legacy free-text person or department responsible for engineering document control. Review ownership, staff/department lookups and document-control workflow before adoption. Retain the field and legacy values; backend/database unchanged. | Later review |
| 6 | DistributionCode | string | Nullable | Drop DistributionCode from the WorkTemplateMaster proposal as requested. Preserve legacy distribution codes and historical approved content during deferred backend/database adoption. No replacement field introduced by this decision. | Dropped Removal pending complete review |
| 7 | EoType | int | Required | Records eo type for this engineering order. | Reviewed |
| 8 | ImplementationConsequences | string | Nullable | Effects and follow-up obligations of implementing the engineering change. Example: update wiring diagrams, revise spare-parts records and brief maintenance staff. Preserve the existing 4,000-character maximum. Reviewed in the HTML proposal; backend/database adoption pending complete review. | Reviewed |
| 9 | ImplementationOccasion | string | Nullable | Maintenance opportunity during which the engineering change should be performed. Example: at the next scheduled heavy-maintenance visit. Preserve the existing 100-character maximum. Reviewed in the HTML proposal; backend/database adoption pending complete review. | Reviewed |
| 10 | MaintainedBy | string | Nullable | Drop MaintainedBy text and replace it with reviewed MaintainedByBusinessPartnerId, a nullable UUID lookup to BusinessPartner identifying the maintenance provider. Resolve legacy codes and preserve historical values during deferred backend/database adoption. | Dropped Removal pending complete review |
| 11 | MandatoryLevel | int | Required | Records mandatory level for this engineering order. | Reviewed |
| 12 | MethodOfCompliance | string | Nullable | Records method of compliance for this engineering order. | Reviewed |
| 13 | ModificationPlan | int | Required | Records modification plan for this engineering order. | Reviewed |
| 14 | ModificationScope | int | Required | Reviewed scope of the engineering change. Retain existing EngineeringModificationScope enum values: Aircraft = 1, Component = 2, AircraftAndComponent = 3, Other = 4, corresponding to AMOS Type of Modification. Identifies whether the change affects the aircraft/airframe installation, the component itself, both, or another documented scope. Distinct from WorkClass and actual aircraft/component applicability or compliance links. Required for EngineeringOrder-type records, preserving the current Aircraft default; nullable in the common master for other types until applicability is defined. Preserve legacy values and historical approved scope during adoption. Backend/database adoption pending complete review. | Reviewed |
| 15 | MomentChange | decimal? | Nullable | Dropped from WorkTemplateMaster; move to CriticalEvent.MomentChange and select through CriticalEventId. 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. Preserve legacy values and approved change-specific context; shared category edits must not overwrite approved or historical values. Backend/database move remains pending complete review. | Dropped Removal pending complete review |
| 16 | OwnerCode | string | Nullable | Drop OwnerCode text and replace it with OwnerBusinessPartnerId, a nullable UUID lookup to BusinessPartner identifying the document-owner organization. Resolve legacy codes explicitly and preserve unmapped text and historical ownership. Backend/database adoption deferred. | Dropped Removal pending complete review |
| 17 | PoolAddress | string | Nullable | Drop PoolAddress text and replace it with PoolBusinessPartnerId, a nullable UUID lookup to BusinessPartner for the pool-partner role. Resolve legacy address codes explicitly; preserve unmapped text and historical references during deferred adoption. | Dropped Removal pending complete review |
| 18 | PreparedBy | string | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.PreparedBy nullable text definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 19 | ProjectCurrencyCode | string | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ProjectCurrencyCode nullable text definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 20 | RejectionConsequences | string | Nullable | Reviewed optional narrative recording the expected effects of deciding not to adopt the engineering change. Example: existing connectors remain installed, recurring failures may continue and additional inspections may remain necessary. Distinct from consequences of implementation; does not itself authorize rejection or noncompliance. Preserve nullable string storage, the existing 4,000-character maximum and historical approved content. Backend/database adoption pending complete review. | Reviewed |
| 21 | ReleasedBy | string | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ReleasedBy nullable text definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 22 | ReturnOnInvestmentMonths | int? | Nullable | Dropped from WorkTemplateMaster during field review. Retain the original EngineeringOrder.ReturnOnInvestmentMonths nullable integer definition and legacy values for review/history. Backend/database removal remains pending complete review. | Dropped Removal pending complete review |
| 23 | SafetyRecurrenceProbability | string | Nullable | Reviewed likelihood that the safety problem addressed by this engineering directive will recur. Replace the legacy optional text with proposed nullable EngineeringSafetyRecurrenceProbability { Low, Medium, High }, matching the AMOS Engineering Orders Safety tab (Engineering Orders.pdf.txt, lines 803–808). Distinct from consequence severity and overall risk. Null means not assessed or not recorded; do not default missing values to Low. Map legacy text explicitly and preserve unmapped labels and historical approved values during adoption. Enum conversion and backend/database adoption remain pending complete review. | Reviewed |
| 24 | SafetySeverity | string | Nullable | Reviewed safety-consequence severity classification. Replace the legacy optional text with proposed nullable EngineeringSafetySeverity { Negligible, Minor, Major, Hazardous, Catastrophic }. These are project proposal values; align their definitions with the organization's approved safety matrix before backend adoption. Severity describes the seriousness of consequences, separately from recurrence probability or overall risk. Null means not recorded or not yet assessed; do not default missing values to Negligible. Explicitly map legacy labels and preserve unmapped text for review and approved/historical values. Enum conversion and backend/database adoption remain pending complete review. | Reviewed |
| 25 | WorkCategory | int | Required | Engineering classification of the work: Minor = 1 or Major = 2. Required for EngineeringOrder-type records; nullable for other master types until an explicit applicability rule is defined. Preserve the existing enum values and Minor default for engineering orders during adoption. This field does not itself determine authority approval. | Reviewed |
| 26 | WorkClass | int | Required | Kind of engineering work: Modification = 1, Repair = 2, Inspection = 3 or Administrative = 4. Required for EngineeringOrder-type records; nullable for other master types until an explicit applicability rule is defined. Preserve the existing enum values and Modification default for engineering orders during adoption. Distinct from the master TemplateType. | Reviewed |