Coflyr · HTML model review
WorkTemplateMaster
Shared definition header · proposed Maintenance.WorkTemplateMasters
Under development58 proposed active fields57 dropped fields retained10 template types
HTML proposal only. WorkTemplate and EngineeringOrder are merged into this single WorkTemplateMaster; both former headers are marked Dropped. All WorkTemplate fields are included once in this combined inventory. EngineeringOrder becomes TemplateType.EngineeringOrder; add Task, Modification and Troubleshooting. Backend models, services and database adoption remain pending complete review.
Model index · Template types · Ownership and revisions · Former WorkTemplate fields · Former EngineeringOrder fields · WorkTemplateRevision
Field review inventory
Active fields pending review appear first, followed by Reviewed fields and then Dropped fields. Each group is alphabetical. Shared duplicates appear once. Dropped fields remain visible with their types, source definitions and review decisions. Engineering-only value fields are nullable in the common record; applicability and source validation requirements are retained below. Requiredness for new Task, Modification and Troubleshooting types remains subject to detailed field review.
115 fields · 58 proposed active · 57 dropped retained
| Field | Proposed type | Nullability | Purpose | Source definitions | Review decision |
|---|---|---|---|---|---|
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ComplianceType · string? · Nullable | Later review |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ControlledBy · string? · Nullable | Later review |
ControlledComponent | bool? | Nullable | 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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ControlledComponent · bool · Required | Later review |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.MotivationText · string? · Nullable EngineeringOrder.ReliabilityMotivation · bool · Required EngineeringOrder.AirworthinessMotivation · bool · Required EngineeringOrder.CommercialMotivation · bool · Required EngineeringOrder.CustomerRequestMotivation · bool · Required EngineeringOrder.EtopsMotivation · bool · Required EngineeringOrder.MaintenanceMotivation · bool · Required EngineeringOrder.OperationsMotivation · bool · Required EngineeringOrder.PerformanceMotivation · bool · Required EngineeringOrder.DirectMaintenanceCostImprovement · bool · Required EngineeringOrder.DirectOperatingCostImprovement · bool · Required EngineeringOrder.FlightSafetyImprovement · bool · Required EngineeringOrder.ReliabilityImprovement · bool · Required | Merge target; backend / DB adoption pending |
PoolBusinessPartnerId | Guid? | Nullable | Nullable UUID lookup to BusinessPartner identifying the pool partner associated with this engineering directive or template. Example: select the component-pooling provider supplying replacement pumps. Display the selected partner code/name. Replaces legacy PoolAddress text; explicitly resolve address-directory codes to saved BusinessPartner records and preserve unmapped text and historical partner identity during adoption. Keep the pool-partner role distinct from CustomerBusinessPartnerId and integrate its relationship with the common EntityLink framework during implementation. Backend/database adoption pending complete review.EngineeringOrder or other template types when a pool-partner relationship applies. | WorkTemplateMaster.PoolBusinessPartnerId (new lookup proposal) · Guid? · Nullable EngineeringOrder.PoolAddress · string? · Nullable | Replace PoolAddress with BusinessPartner lookup; backend / DB adoption pending |
PublicationId | Guid? | Nullable | Nullable UUID lookup to PublicationMaster identifying the source or governing publication for this template or engineering directive. Display the publication number, subject and applicable issue/revision. Replaces ModificationId in this proposal. Map each legacy Modification reference to the appropriate saved publication explicitly; never copy Modification UUIDs into PublicationId. Preserve unresolved associations, original source identity and exact approved publication issue/revision for issued work. Integrate the publication relationship with the common EntityLink framework during adoption. The Modification catalog is not retired by this field replacement. Backend/database adoption pending complete review.Template types with a source or governing publication; validate publication type and approved issue/revision during adoption. | WorkTemplateMaster.PublicationId (new lookup proposal) · Guid? · Nullable EngineeringOrder.ModificationId · Guid? · Nullable | Replace ModificationId with publication lookup; backend / DB adoption pending |
SystemAuditId | Guid? | Nullable | Links to system audit history when this model stores the reference.Shared header | WorkTemplate.SystemAuditId · Guid? · Nullable EngineeringOrder.SystemAuditId · Guid? · Nullable | Merged duplicate definitions; adoption pending |
AdditionalRequirementsText | string? | Nullable | Records additional requirements text for this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.AdditionalRequirementsText · string? · Nullable | Reviewed |
AtaId | Guid? | Nullable | One shared optional ATA lookup. Merge the former template/order ATA references and retain scope and validation.Shared header | WorkTemplate.AtaId · Guid? · Nullable EngineeringOrder.AtaId · Guid? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.BackgroundText · string? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.CarryOutText · string? · Nullable | Reviewed |
ConfigurationId | Guid? | Nullable | Nullable UUID lookup to Configuration identifying the functional position applicable to this reusable template. Validate that the selected position belongs to ConfigurationMasterId and is consistent with LocationReferenceId when both apply. Reusable templates must resolve the definition against the issued aircraft/component during adoption; a template position alone does not identify the currently installed unit. Replaces free-text PositionCode together with the other location/configuration lookups. Resolve legacy position codes in their aircraft/component and configuration context; preserve unresolved and historical values during adoption. Backend/database adoption pending complete review.Template types with applicable location or configuration position context; conditional validation pending adoption. | WorkTemplateMaster.ConfigurationId (new lookup proposal) · Guid? · Nullable WorkTemplate.PositionCode · string? · Nullable | Reviewed |
ConfigurationMasterId | Guid? | Nullable | Nullable UUID lookup to ConfigurationMaster identifying the configuration definition that provides the template’s applicable aircraft/component position context. Replaces free-text PositionCode together with the other location/configuration lookups. Resolve legacy position codes in their aircraft/component and configuration context; preserve unresolved and historical values during adoption. Backend/database adoption pending complete review.Template types with applicable location or configuration position context; conditional validation pending adoption. | WorkTemplateMaster.ConfigurationMasterId (new lookup proposal) · Guid? · Nullable WorkTemplate.PositionCode · string? · Nullable | Reviewed |
CriticalEventId | Guid? | Nullable | Nullable UUID lookup to CriticalEvent selecting the operational-impact and task-control classification for this template master. Replaces the duplicated AffectsFlightOperations, AffectsGroundOperations, AffectsSimulator, ElectricalLoadAffected and MassAndBalanceAffected flags on the master. The HTML proposal also moves MomentChange and WeightChangeKg here, retaining their numerical types and requiring approved change-specific context. Display the category code and name. Approved revisions and issued work must preserve the selected category identity and impact/control values; later edits to the category must not rewrite historical requirements. Backend/database adoption pending complete review.All template types when an operational-impact or task-control classification applies. | WorkTemplateMaster.CriticalEventId (new proposal) · Guid? · Nullable | Reviewed CriticalEvent review |
CustomerBusinessPartnerId | Guid? | Nullable | Selects the related customer business partner record.Existing template behavior; applicability for new types to be reviewed. | WorkTemplate.CustomerBusinessPartnerId · Guid? · Nullable | Reviewed |
EngineeringText | string? | Nullable | Records engineering text for this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.EngineeringText · string? · Nullable | Reviewed |
EoType | EngineeringOrderType? { AirworthinessDirective, ServiceBulletin, Modification, SpecialInspection } | Nullable | Technical engineering document category: AirworthinessDirective, ServiceBulletin, Modification or SpecialInspection. This remains distinct from the master TemplateType: a legacy EO with EoType.Modification still maps to TemplateType.EngineeringOrder. Review further classification consolidation separately.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.EoType · EngineeringOrderType · Required | Reviewed |
EstimatedLabourCost | decimal? | Nullable | Stores the estimated labour cost used by this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.EstimatedLabourCost · decimal? · Nullable | Reviewed |
EstimatedManHours | decimal? | Nullable | Records estimated man hours for this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.EstimatedManHours · decimal · Required | Reviewed |
EstimatedMaterialCost | decimal? | Nullable | Stores the estimated material cost used by this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.EstimatedMaterialCost · decimal? · Nullable | Reviewed |
Id | Guid | Required | Stable UUID of the unified master. Preserve legacy IDs where possible and migrate incoming references using an explicit identity map where collisions exist.All WorkTemplateMaster records | WorkTemplate.Id · Guid · Required EngineeringOrder.Id · Guid · Required | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ImplementationConsequences · string? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ImplementationEndDate · DateTime? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ImplementationNotes · string? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ImplementationOccasion · string? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ImplementationStartDate · DateTime? · Nullable | Reviewed |
IncludeAlternateParts | bool | Required | Indicates whether the component-maintenance template is intended to apply to alternate parts. Example: apply the template to pump P100 and its approved alternate P101. Current test-assignment returns the flag; automatic alternate-part expansion and applicability validation are not implemented by that endpoint. Reviewed in the HTML proposal; backend/database adoption pending complete review.Existing template behavior; applicability for new types to be reviewed. | WorkTemplate.IncludeAlternateParts · bool · Required | Reviewed |
InterchangeabilityAffected | bool? | Nullable | 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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.InterchangeabilityAffected · bool · Required | Reviewed |
LabourUnderWarranty | bool? | Nullable | Indicates whether labour under warranty applies to this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.LabourUnderWarranty · bool · Required | Reviewed |
LocationReferenceId | Guid? | Nullable | Nullable UUID lookup to LocationReference identifying the general location or position reference applicable to this reusable template. Display the selected location code/name and category. Replaces free-text PositionCode together with the other location/configuration lookups. Resolve legacy position codes in their aircraft/component and configuration context; preserve unresolved and historical values during adoption. Backend/database adoption pending complete review.Template types with applicable location or configuration position context; conditional validation pending adoption. | WorkTemplateMaster.LocationReferenceId (new lookup proposal) · Guid? · Nullable WorkTemplate.PositionCode · string? · Nullable | Reviewed |
MaintainedByBusinessPartnerId | Guid? | Nullable | Reviewed nullable UUID lookup to BusinessPartner identifying the maintenance provider associated with this engineering directive or template. Display the selected provider code/name. Replaces legacy MaintainedBy text; explicitly resolve address-directory codes to saved BusinessPartner records and preserve unmapped text and historical provider identity during adoption. Keep maintenance-provider role distinct from document owner, customer, issuer and pool partner. Integrate this role with the common EntityLink framework during implementation. Backend/database adoption pending complete review.EngineeringOrder or other template types when a maintenance-provider relationship applies. | WorkTemplateMaster.MaintainedByBusinessPartnerId (new lookup proposal) · Guid? · Nullable EngineeringOrder.MaintainedBy · string? · Nullable | Reviewed |
MandatoryLevel | EoMandatoryLevel? | Nullable | Records mandatory level for this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.MandatoryLevel · EoMandatoryLevel · Required | Reviewed |
MaterialUnderWarranty | bool? | Nullable | Indicates whether material under warranty applies to this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.MaterialUnderWarranty · bool · Required | Reviewed |
MethodOfCompliance | string? | Nullable | Records method of compliance for this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.MethodOfCompliance · string? · Nullable | Reviewed |
ModificationPlan | ModificationPlanType? | Nullable | Records modification plan for this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ModificationPlan · ModificationPlanType · Required | Reviewed |
ModificationScope | EngineeringModificationScope? { Aircraft, Component, AircraftAndComponent, Other } | Nullable | 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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ModificationScope · EngineeringModificationScope · Required | Reviewed |
OrderReason | MaintenanceOrderReason? { Inspection, Repair, Overhaul, Modification, Testing, Servicing, Calibration, Other } | Nullable | Reviewed nullable MaintenanceOrderReason enum identifying the purpose for which maintenance work is requested and this reusable template is selected: Inspection, Repair, Overhaul, Modification, Testing, Servicing, Calibration or Other. Rename legacy OrderReasonCode to OrderReason. These are project-defined choices, not a fixed AMOS enum; AMOS uses configurable reason codes for template matching. Null means no reason selected. Explicitly map legacy text without silently converting unknown codes to Other, and preserve unmapped codes and historical values. This classification is distinct from ReasonText, which explains why an engineering-order document was created. Enum conversion, template matching and backend/database adoption remain pending complete review.Templates selected by maintenance reason; applicability and matching rules for other types retained for adoption. | WorkTemplateMaster.OrderReason (renamed enum proposal) · MaintenanceOrderReason? · Nullable WorkTemplate.OrderReasonCode · string? · Nullable | Reviewed |
OwnerBusinessPartnerId | Guid? | Nullable | Nullable UUID lookup to BusinessPartner identifying the organization that owns this engineering-order document or template definition. Display the selected partner code/name. Replaces legacy OwnerCode text; resolve address-directory codes to saved BusinessPartner records explicitly and preserve unmapped text and historical owner identity during adoption. Keep document ownership distinct from customer, issuer and pool-partner roles. This lookup does not grant access permissions. Integrate its role with the common EntityLink framework during implementation. Backend/database adoption pending complete review.EngineeringOrder or other template types when a document-owner organization applies. | WorkTemplateMaster.OwnerBusinessPartnerId (new lookup proposal) · Guid? · Nullable EngineeringOrder.OwnerCode · string? · Nullable | Reviewed |
PartId | Guid? | Nullable | Selects the related part record.Existing template behavior; applicability for new types to be reviewed. | WorkTemplate.PartId · Guid? · Nullable | Reviewed |
PlanningText | string? | Nullable | Records planning text for this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.PlanningText · string? · Nullable | Reviewed |
PriorityCode | ComponentWorkpackagePriority? { VeryUrgent, Urgent, Normal, NotUrgent, NiceToHave } | Nullable | Reviewed nullable maintenance planning priority. Replace free-text PriorityCode with the existing ComponentWorkpackagePriority enum already used by WorkorderMaster: VeryUrgent = 1, Urgent = 2, Normal = 3, NotUrgent = 4, NiceToHave = 5. Reuse these project values rather than introduce a second priority enum. Null means priority not specified; do not silently default to Normal. These are project enum values; AMOS uses a configurable priority table and may contain other legacy codes, including M (Mandatory). Explicitly map legacy codes and preserve unmapped text and historical priorities for review. Priority does not replace a governing compliance requirement or mandatory-compliance classification. Enum conversion and backend/database adoption pending complete review.Existing template behavior; applicability for new types to be reviewed. | WorkTemplate.PriorityCode · string? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.ReasonText · string? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.RecommendationText · string? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.RejectionConsequences · string? · Nullable | Reviewed |
RequiredConditionCode | string? | Nullable | Records required condition code for this work template.Existing template behavior; applicability for new types to be reviewed. | WorkTemplate.RequiredConditionCode · string? · Nullable | Reviewed |
RequirementId | Guid? | Nullable | Nullable UUID lookup to Requirements selecting the governing compliance requirement for ComplianceDeadlineDate, ComplianceThresholdCycles and ComplianceThresholdHours. Display the selected requirement code/title and linked calendar, flight-hour and flight-cycle limits. Reuse the existing RequirementToWorkTemplate EntityLink as the authoritative relationship, with WorkTemplateMaster as its target after adoption; expose this lookup as a projection rather than introduce independently maintained duplicate relationship storage. Reconcile existing WorkTemplateLink requirement associations and retain additional requirement links. Preserve exact fixed dates, counter units and baselines, limit-combination logic and approved requirement/limit snapshots for issued work. Backend/database adoption pending complete review. Repetition formerly represented by IsRepetitive is also governed by the linked requirement and its applicable recurrence/limit rules; preserve one-time/recurring meaning and historical approved requirements during adoption.Templates with a governing compliance requirement; EngineeringOrder limits use this relationship. Other types require applicable requirement validation. | WorkTemplateMaster.RequirementId (new lookup proposal) · Guid? · Nullable | Reviewed Requirements review |
SafetyRecurrenceProbability | EngineeringSafetyRecurrenceProbability? { Low, Medium, High } | 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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.SafetyRecurrenceProbability · string? · Nullable | Reviewed |
SafetySeverity | EngineeringSafetySeverity? { Negligible, Minor, Major, Hazardous, Catastrophic } | 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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.SafetySeverity · string? · Nullable | Reviewed |
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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.SafetyText · string? · Nullable | Reviewed |
TemplateDescription | string? | Nullable | Records template description for this work template.Existing template behavior; applicability for new types to be reviewed. | WorkTemplate.TemplateDescription · string? · Nullable | Reviewed |
TemplateNumber | string | Required | Single business number for the template master. Merge WorkTemplate.TemplateNumber and EngineeringOrder.EoNumber, preserving all existing text and external references. Reconcile cross-source collisions explicitly; preserve existing UUIDs or a stable legacy-ID mapping and use at least the existing 100-character capacity.All WorkTemplateMaster records | WorkTemplate.TemplateNumber · string · Required EngineeringOrder.EoNumber · string · Required | Reviewed |
TemplateText | string? | Nullable | Records template text for this work template.Existing template behavior; applicability for new types to be reviewed. | WorkTemplate.TemplateText · string? · Nullable | Reviewed |
TemplateType | WorkTemplateType { WorkTemplate, Jobcard, Shopcard, CustomerRequirement, ManagedWorkTemplate, ComponentMaintenance, EngineeringOrder, Task, Modification, Troubleshooting } | Required | Required kind of the unified definition. Preserve existing values 1–6; append EngineeringOrder=7, Task=8, Modification=9 and Troubleshooting=10. Each kind retains its own validation and workflow. Existing engineering orders map to EngineeringOrder; do not infer this value from EoType or WorkClass.All WorkTemplateMaster records | WorkTemplate.TemplateType · WorkTemplateType · Required | Reviewed |
Title | string | Required | Shared definition title. Merge the two Title properties and preserve the existing 250-character template capacity without truncating engineering titles.All WorkTemplateMaster records | WorkTemplate.Title · string · Required EngineeringOrder.Title · string · Required | Reviewed |
TrialInstallation | bool? | Nullable | Indicates whether trial installation applies to this engineering order.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.TrialInstallation · bool · Required | Reviewed |
UpdateId | Guid? | Nullable | Links to the preceding revision or update record.Shared header | WorkTemplate.UpdateId · Guid? · Nullable EngineeringOrder.UpdateId · Guid? · Nullable | Reviewed |
WorkCategory | EngineeringWorkCategory? { Minor, Major } | Nullable | 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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.WorkCategory · EngineeringWorkCategory · Required | Reviewed |
WorkClass | EngineeringWorkClass? { Modification, Repair, Inspection, Administrative } | Nullable | 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.EngineeringOrder; retain source requiredness for this type. Other types require an explicit rule before reuse. | EngineeringOrder.WorkClass · EngineeringWorkClass · Required | Reviewed |
ActiveRevisionId | Guid? | Nullable | Dropped from WorkTemplateMaster. Retain the legacy active-revision reference in history for review. Issued work and compliance still retain their exact source revision; determine the authoritative active-revision selection mechanism during adoption.Dropped from the unified master; retained for review. | WorkTemplate.ActiveRevisionId · Guid? · Nullable | Dropped |
AffectsFlightOperations | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.AffectsFlightOperations · bool · Required | Dropped Moved to CriticalEvent |
AffectsGroundOperations | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.AffectsGroundOperations · bool · Required | Dropped Moved to CriticalEvent |
AffectsSimulator | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.AffectsSimulator · bool · Required | Dropped Moved to CriticalEvent |
AirworthinessMotivation | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.AirworthinessMotivation · bool · Required | Dropped Merged into MotivationText |
AppliesToRotablesOnly | bool | Required | Dropped from WorkTemplateMaster. Retain the legacy Boolean and its original values for review; remove this master-level restriction only during backend/database adoption.Dropped from the unified master; retained for review. | WorkTemplate.AppliesToRotablesOnly · bool · Required | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.ApprovalDecidedAt · DateTime? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.ApprovalRemarks · string? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.ApprovalRequestedAt · DateTime? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.ApprovalRequestedWithinDays · int? · Nullable | Dropped |
ApprovalStatus | EoApprovalStatus? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.ApprovalStatus · EoApprovalStatus · Required | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.ApprovedBy · string? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.CheckedBy · string? · Nullable | Dropped |
Classification | EngineeringClassification? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.Classification · EngineeringClassification · Required | Dropped |
CommercialMotivation | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.CommercialMotivation · bool · Required | Dropped Merged into MotivationText |
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 from the unified master; retained for review. | EngineeringOrder.ComplianceDeadlineDate · DateTime? · Nullable | Dropped RequirementId · Time limits |
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 from the unified master; retained for review. | EngineeringOrder.ComplianceThresholdCycles · long? · Nullable | Dropped RequirementId · Time limits |
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 from the unified master; retained for review. | EngineeringOrder.ComplianceThresholdHours · decimal? · Nullable | Dropped RequirementId · Time limits |
CostBudgeted | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.CostBudgeted · bool · Required | Dropped · Later review |
CostCapitalized | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.CostCapitalized · bool · Required | Dropped · Later review |
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 from the unified master; retained for review. | EngineeringOrder.CostPerAircraft · decimal? · Nullable | Dropped · Later review |
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 from the unified master; retained for review. | EngineeringOrder.CostPerFleet · decimal? · Nullable | Dropped · Later review |
CustomerRequestMotivation | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.CustomerRequestMotivation · bool · Required | Dropped Merged into MotivationText |
DirectMaintenanceCostImprovement | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.DirectMaintenanceCostImprovement · bool · Required | Dropped Merged into MotivationText |
DirectOperatingCostImprovement | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.DirectOperatingCostImprovement · bool · Required | Dropped Merged into MotivationText |
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 from the unified master; retained for review. | EngineeringOrder.DistributionCode · string? · Nullable | Dropped |
ElectricalLoadAffected | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.ElectricalLoadAffected · bool · Required | Dropped Moved to CriticalEvent |
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 from the unified master; retained for review. | EngineeringOrder.EoEffectiveDate · DateTime? · Nullable | Dropped |
EoIssueDate | DateTime? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.EoIssueDate · DateTime · Required | Dropped |
EoStatus | EoStatus? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.EoStatus · EoStatus · Required | Dropped |
EtopsMotivation | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.EtopsMotivation · bool · Required | Dropped Merged into MotivationText |
FlightSafetyImprovement | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.FlightSafetyImprovement · bool · Required | Dropped Merged into MotivationText |
IsActive | bool | Required | Dropped from WorkTemplateMaster. Merge the duplicate WorkTemplate.IsActive and EngineeringOrder.IsActive definitions into this retained dropped review row. Preserve original values and adapt activation/cancellation consumers during later backend/database adoption.Dropped from the unified master; retained for review. | WorkTemplate.IsActive · bool · Required EngineeringOrder.IsActive · bool · Required | Dropped |
IsRepetitive | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.IsRepetitive · bool · Required | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.IssuedBy · string? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.MaintainedBy · string? · Nullable | Dropped Merged into MaintainedByBusinessPartnerId |
MaintenanceMotivation | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.MaintenanceMotivation · bool · Required | Dropped Merged into MotivationText |
MassAndBalanceAffected | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.MassAndBalanceAffected · bool · Required | Dropped Moved to CriticalEvent |
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 from the unified master; retained for review. | EngineeringOrder.ModificationId · Guid? · Nullable | Dropped Merged into PublicationId |
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 from the unified master; retained for review. | EngineeringOrder.MomentChange · decimal? · Nullable | Dropped Moved to CriticalEvent |
NextRevisionNumber | int | Required | Dropped in the template review. Revision allocation still needs an authoritative server-side mechanism; retire this stored counter only when revision creation is adapted.Existing template behavior; applicability for new types to be reviewed. | WorkTemplate.NextRevisionNumber · int · Required | Dropped |
OperationsMotivation | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.OperationsMotivation · bool · Required | Dropped Merged into MotivationText |
OrderReasonCode | string? | Nullable | Replace OrderReasonCode text with reviewed OrderReason (MaintenanceOrderReason?) enum. Explicitly map legacy reason codes and preserve unmapped/historical values during deferred backend/database adoption.Dropped from the unified master; retained for review. | WorkTemplate.OrderReasonCode · string? · Nullable | Dropped Merged into OrderReason |
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 from the unified master; retained for review. | EngineeringOrder.OwnerCode · string? · Nullable | Dropped Merged into OwnerBusinessPartnerId |
PerformanceMotivation | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.PerformanceMotivation · bool · Required | Dropped Merged into MotivationText |
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 from the unified master; retained for review. | EngineeringOrder.PoolAddress · string? · Nullable | Dropped Merged into PoolBusinessPartnerId |
PositionCode | string? | Nullable | Drop PositionCode text and replace it with LocationReferenceId (LocationReference lookup), ConfigurationMasterId (ConfigurationMaster lookup) and ConfigurationId (Configuration lookup), all nullable UUIDs. Resolve legacy codes explicitly in the correct context and preserve unresolved/historical values during deferred adoption.Dropped from the unified master; retained for review. | WorkTemplate.PositionCode · string? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.PreparedBy · string? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.ProjectCurrencyCode · string? · Nullable | Dropped |
ProjectNumber | string? | Nullable | Dropped in the template-master review. Preserve the original field and source values in review/history until adoption; do not reactivate it through the EngineeringOrder merge.Shared header | WorkTemplate.ProjectNumber · string? · Nullable EngineeringOrder.ProjectNumber · string? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.ReleasedBy · string? · Nullable | Dropped |
ReliabilityImprovement | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.ReliabilityImprovement · bool · Required | Dropped Merged into MotivationText |
ReliabilityMotivation | bool? | Nullable | 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 from the unified master; retained for review. | EngineeringOrder.ReliabilityMotivation · bool · Required | Dropped Merged into MotivationText |
RequirementTypeCode | string? | Nullable | Drop RequirementTypeCode from the WorkTemplateMaster proposal. Use the linked Requirements record through RequirementId and its RequirementTypeDefinitionId lookup to display the governing requirement type. Reconcile legacy free-text codes with authoritative requirement-type definitions during later adoption. Backend/database changes remain deferred until complete project review.Dropped from the unified master; retained for review. | WorkTemplate.RequirementTypeCode · string? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.ReturnOnInvestmentMonths · int? · Nullable | Dropped |
ShopFacilityId | Guid? | Nullable | Drop ShopFacilityId from the common WorkTemplateMaster proposal as requested. Backend/database adoption remains deferred until complete project review.Dropped from the unified master; retained for review. | WorkTemplate.ShopFacilityId · Guid? · Nullable | Dropped |
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 from the unified master; retained for review. | EngineeringOrder.WeightChangeKg · decimal? · Nullable | Dropped Moved to CriticalEvent |
TemplateType
Existing enum values are preserved. New values are appended; adoption must not renumber existing records.
| Type | Value | Purpose |
|---|---|---|
| WorkTemplate | 1 | Existing general reusable work template. |
| Jobcard | 2 | Existing reusable jobcard definition. |
| Shopcard | 3 | Existing reusable shopcard definition. |
| CustomerRequirement | 4 | Existing customer-requirement template. |
| ManagedWorkTemplate | 5 | Existing managed work-template definition. |
| ComponentMaintenance | 6 | Existing component-maintenance template. |
| EngineeringOrder | 7 | Engineering directive with technical classification, controlled approval/release and per-asset compliance records. |
| Task | 8 | Reusable task instruction. This type does not merge or replace the MaintenanceTask or TaskCard models. |
| Modification | 9 | Reusable modification instruction linked to the relevant Modification definition and execution evidence. |
| Troubleshooting | 10 | Reusable diagnostic instruction and decision sequence. Actual findings and diagnostic actions belong to issued execution records. |
Ownership, revisions and execution
WorkTemplateMaster → controlled WorkTemplateRevision → reusable instructions/linked WorkSteps → issued WorkorderMaster and WorkStep records. Each issued execution retains its source revision.
An EngineeringOrder-type master also owns technical approval/release requirements and links to separate aircraft/component compliance records. Ordinary Task or Troubleshooting definitions do not automatically create fleet-wide compliance assignments. Engineering applicability and revision scope must be explicit.
Example: EO-001 is an EngineeringOrder-type master. Revision 2 defines the approved connector replacement. Aircraft A has completed its linked workorder; aircraft B still has an open compliance record. A Troubleshooting-type master can separately supply the diagnostic instructions used during execution.
| Related model | Review treatment |
|---|---|
| WorkTemplateRevision | Keep Under development. Redirect WorkTemplateId to the new master (proposed name WorkTemplateMasterId); retain immutable issued revision identity and content. |
| EngineeringOrderCompliance | Retain per-aircraft compliance. Redirect EngineeringOrderId to the master with EngineeringOrder-type validation and add an exact issued revision reference during adoption. Do not treat activation as accomplishment. |
| ComponentModificationStatus | Retain the serialized-component compliance register; redirect EngineeringOrderId and preserve directive/revision lineage. |
| ManagementOfChange | Retain the safety-change aggregate and rebind its EngineeringOrderId to the corresponding EngineeringOrder-type master. |
| WorkTemplateItem | Dropped; template instructions become TemplateStep-role WorkStep rows owned through WorkTemplateMasterId. Preserve hierarchy, ordering, full instructions, structured planned demands and exact revision/source history during adoption. |
| WorkTemplateLink / ComponentMaintenanceTemplateTask | Retain existing revision associations. These models are not retired by the WorkTemplateItem consolidation. |
| Requirements / TimeRequirementLimit | Use the proposed RequirementId lookup for compliance deadline, flight-hour and flight-cycle limits. Reuse the existing RequirementToWorkTemplate EntityLink and rebind its template target to WorkTemplateMaster during adoption. Preserve exact deadline dates, units, baselines, combination logic and approved requirement snapshots; additional requirement links remain available. |
| WorkorderMaster / WorkStep | Issued work references its source definition/revision; actual execution, findings, readings and sign-offs remain issued records. |
Dropped fields remain visible in the unified inventory, including their original source definitions. Source values must remain recoverable until adoption is reviewed.