Technical guide: design and consulting

Input data, analyses, deliverables, and normative references for the 21 Sky Meridian services: airport infrastructure, AACR permitting, roads, water and sewerage, construction, consulting, and investment management.

The guide is addressed to beneficiaries and specialists preparing projects in Bihor and across Romania. Each chapter defines the technical scope of the service and the information required to define a contractual brief.

Normative references are selected based on object, site, phase, organization domain, and application date. A list of acts does not replace the project requirements registry or the verification of applicable editions.

Design basis and regulatory applicability

A requirements registry is drawn up for each project, allowing for the tracking of links between references, calculations, documents, and verification. The registry is updated under control when the brief, configuration, or applicable framework changes.

  • Reference identification: issuer, code, edition, revision, amendments, and approval act, where applicable.
  • Applicability: object, phase, domain, and date of application; transitional provisions and the reason for the inclusion or exclusion of the requirement are noted.
  • Demonstration: the relevant article or criterion is associated with input data, calculation method, result, and the document constituting proof.
  • Data control: source, revision, coordinate system, elevation datum, units, precision, and limitations; conversions and assumptions are explicit.
  • Responsibilities: author, checker, data owner, and the body that accepts, permits, or approves, according to the applicable framework.

In the field of aerodromes, a distinction is made between mandatory regulations, CS specifications from the certification basis, acceptable means of compliance (AMC), and guidance material (GM). Technical or industry standards incorporated by contract are identified separately. The existence of a new edition does not, in itself, establish its applicability to an already certified configuration.

Airport terminology: "design aircraft" is used, identifying the type, variant, and parameters determining the verification performed. The aerodrome classification, aircraft geometry, pavement loading, and operating conditions are explicitly correlated.

Regulatory updates: for urban planning and construction, check Law no. 169/2026 — The Code of Spatial Planning, Urbanism, and Construction and transitional situations. For aeronautical permitting, RACR-AVZ is used in consolidated form, including the 2026 amendments. Historical references from existing documentation are not adopted automatically.

1. Water, sewerage, and utility installations

The sizing of water supply, sanitary sewerage, and rainwater drainage networks is based on flow balances, operating regimes, and connection conditions. The solution is correlated with vertical systematization, geotechnics, and the capacity of the receiving infrastructure.

Input data

Topographic survey, geotechnical study, utility inventory, permits and data from operators, population or equivalent consumers, technological consumption, collection areas, hydrological conditions, and discharge levels. The source, date, and units of each data set are specified.

Technical analyses and checks

  • Water: determination of design flows, pressure losses, and nodal pressures; verification of consumption scenarios and, where relevant, fire scenarios; pump selection based on the duty point and transient regime analysis if configuration requires.
  • Sewerage: sizing of gravity and pressure collectors, verification of slopes, velocities, and degree of filling; evaluation of backwater, rainwater retention, and discharge flow limitation.
  • Constructive: invert and cover levels, intersections with utilities, crossings, shoring, and dewatering; stability verification of buried structures and operational conditions.

Deliverables

Specialty reports, hydraulic summary, site plans and longitudinal profiles, pumping schemes, constructive details, technical specifications, quantities, and interference matrix. Calculation assumptions and verified scenarios are identifiable in the documentation.

Normative basis and scope

Foundational condition: The boundary between external networks and building installations, data guaranteed by the operator, and the discharge regime. Solutions for gas, energy, or other utilities are addressed only within the contracted scope, with the necessary specialists and authorizations.

Sky Meridian Service: Water, sewerage, and utility installations · Back to contents

Practical article: Water and sewerage design: what to prepare before the project

2. Roads, accesses, and parking lots

The design of roads, accesses, and parking lots correlates route geometry, design traffic, pavement structure, and water drainage. The road regime and relationship with the infrastructure administrator to which it connects are established from the beginning.

Input data

Topography, cadastre and property boundaries, geotechnical study, existing and forecast traffic, design vehicle, road category and function, road system surveys, drainage status, and intersected networks.

Technical analyses and checks

  • Geometry: plan route, longitudinal profile, cross-sections, visibility, slopes, and connections; verification of design vehicle maneuvers at intersections, accesses, and parking lots.
  • Pavement structure: design traffic and perspective period, foundation soil and material characteristics, dimensioning checks, and behavior regarding water and frost, according to the adopted solution.
  • Drainage and phasing: platform runoff, ditches, gutters, culverts, and discharges; maintenance of access and traffic organization during works.

Deliverables

Route justification report, pavement structure dimensioning summary, plans and profiles, drainage and connection details, signage, technical specifications, and quantities.

Normative basis and scope

Foundational condition: A public road, a private access, and an airport service road do not automatically have the same design basis. For roads in the operational area, interfaces with aerodrome safety are added.

Sky Meridian Service: Roads, accesses, and parking lots · Back to contents

Practical article: Road design: necessary data and documentation phases

3. Civil engineering

Design coordinates architecture, structure, and installations through verifiable performance requirements. For existing buildings, the solution is based on surveys, investigations, and the technical expertise required for the intervention.

Input data

Functional brief, urban planning and authorization documents, topography and geotechnics, project importance class and category, surveys, technological loads, fire requirements, and utility connection conditions.

Technical analyses and checks

  • Structure and foundations: calculation model, actions and combinations, verification for ultimate and serviceability limit states, displacements, stability, and deformation compatibility; geotechnical parameters are correlated with investigations.
  • Architecture and fire safety: functional organization, circulation, evacuation, compartmentalization, and performance of elements; coordination with the fire safety scenario, when necessary.
  • Installations and envelope: openings and routes, supplies, evacuations, electrical protections, crossing seals, thermal bridges, and maintenance access; resolving incompatibilities before issuing drawings.

Deliverables

Reports, summaries, and calculation models, coordinated drawings, details, performance specifications, quantities, and documents for project technical verification, according to the contracted phase.

Normative basis and scope

Foundational condition: The normative registry separately specifies applicable structural standards and national annexes. For ventilation, HVAC, and fire protection installations, the standards for the effectively included specialties are supplemented.

Sky Meridian Service: Civil engineering · Back to contents

Civil engineering design: brief, documents, and specialty coordination: practical article for project preparation.

4. Airports and airport infrastructure

The design brief establishes the design aircraft, operational scenarios, and aerodrome certification basis. Design aircraft parameters are documented for each verification; the aircraft determining geometry may differ from the one determining pavement structure loading.

Input data

Certificate and certification basis, aerodrome configuration, AIP, measurements and terrain model, geotechnics, design aircraft data, traffic scenarios, CNS/MET facilities, and operational limitations during works.

Technical analyses and checks

  • Geometry: wingspan, outer main gear wheel span, wheelbase, and turn geometry; clearances, safety distances, and taxi routes. Turnaround pads and parking positions are verified for the maneuvers actually envisaged.
  • Infrastructure: load-bearing capacity, surfaces and slopes, drainage, shoulders, strip, RESA, and stopway, depending on the work object. For stopways, the function, constructive characteristics, and declared distances are correlated.
  • Operation: markings, lighting, and signage, jet blast effects, vehicle access, FOD, and CNS interference. Phasing includes unavailable areas, temporary obstacles, separations, and reopening conditions.

Deliverables

Design basis, compliance report for applicable CS, summaries, plans and details, interface matrix, change management documentation, and data for updating aeronautical information, within contract limits.

Normative basis and scope

Foundational condition: CS-ADR-DSN is not applied by simply choosing the newest edition: the reference is correlated with the certification basis and the proposed change. The national regime is analyzed separately for aerodromes outside the European scope.

Documented experience: Reconfiguration of apron no. 1 — Oradea; Aircraft hangars — Oradea; Turnaround pads, stopway, and shoulders — Oradea. Team contribution and documentation phase are specified in the case studies.

Sky Meridian Service: Airports and airport infrastructure · Back to table of contents

Airport design: from reference aircraft to work phasing: practical article for project preparation.

5. Urban Planning: PUG, PUZ, and PUD

Urban planning documentation is established in relation to approved regulations, the proposed development, and the legal framework applicable at the initiation and resolution of the procedure. In the context of the 2026 amendments, the classification of the instrument and the content of the documentation are reconfirmed prior to contracting.

Input data

Cadastral boundaries, land deeds, approved urban planning documentation, local regulations, building restrictions, utility network capacity, accessibility, protection zones and servitudes, as well as the status of any initiated procedures.

Technical analyses and checks

  • Territorial diagnosis: land use, circulation, utilities, natural and technological risks, heritage, and environment; identification of incompatibilities with the investment.
  • Regulation: functions, indicators, heights, setbacks, access, and building equipment, at the level allowed by the applicable instrument; correlation of plans with the regulation and balance sheets.
  • Permitting: inventory of required permits and studies, traceability of observations, and integration of aeronautical restrictions when the site is affected by them.

Deliverables

Report and supporting studies included in the brief, analysis and regulation plans, associated regulation, territorial balance sheets, documents for permitting, and revision records.

Normative basis and scope

Grounding condition: Urban approval and AACR (Romanian Civil Aeronautical Authority) permit have distinct objectives. Urban height allowance alone does not demonstrate the aeronautical acceptability of a construction.

Sky Meridian Service: Urban Planning: PUG, PUZ, and PUD · Back to table of contents

PUG, PUZ, and PUD: what to check before preparing urban planning documentation: practical article for project preparation.

6. Investment Planning and Preparation

Investment preparation transforms the beneficiary's need into capacities, performance requirements, technical alternatives, and acceptance criteria. The level of detail must support the investment decision and the subsequent phase.

Input data

Justified need, legal and technical status of the site, existing capacities, estimated demand, source of funding, operational restrictions, available studies, and dependencies on other investments.

Technical analyses and checks

  • Defining the brief: functions, capacities, performance, and intervention limits; each requirement is linked to a justification and a verification method.
  • Comparing alternatives through technical feasibility, investment, operation, maintenance, risks, and phasing; estimation uncertainties are explicitly retained.
  • Planning studies, permits, design, and procurement; monitoring interfaces that may alter the solution, cost, or timeline.

Deliverables

Conceptual note and brief, pre-feasibility study when necessary, Feasibility Study (SF) or DALI as appropriate, comparative analysis, estimate and budget according to the phase, schedule, and risk register.

Normative basis and scope

Grounding condition: SF and DALI are not interchangeable. Classification is based on the nature of the objective and the intervention; for mixed projects, components are delimited.

Sky Meridian Service: Investment Planning and Preparation · Back to table of contents

Investment preparation: from need to conceptual note and design brief: practical article for project preparation.

7. Documentation for AACR Permitting

Documentation for AACR permitting must unambiguously describe the location, dimensions, and characteristics of the objective. The assessment correlates geometric, operational, and radio-electric effects, depending on the affected aeronautical zones.

Input data

Urban planning certificate and required legal data, coordinates and elevations with specified reference systems, measurements by authorized specialists, location and site plans, sections, elevations, and report. Elements on the roof and relevant temporary clearances, such as cranes, are included.

Technical analyses and checks

  • Verifying site identity across all documents, ground elevation, height, and maximum absolute elevation. Planimetric and altimetric conversions are documented.
  • Identifying affected surfaces and zones: geometric obstruction, flight procedures, CNS/MET facilities, and aerodrome development. Additional studies are delimited according to AACR requirements.
  • Compiling the file for the requested phase and responding to observations in a traceable manner. Changes in position, volume, or height are verified against permit conditions and the current RACR-AVZ format.

Deliverables

Application and technical documentation, inventory of coordinates, correlated plans and reports, contracted supporting studies, table of responses to observations, and record of permit conditions.

Normative basis and scope

Grounding condition: The consultant prepares the technical support; AACR issues the permit and establishes conditions. The file must distinguish between the geometric study, shading study, and radio-electric compatibility assessment.

Sky Meridian Service: Documentation for AACR Permitting · Back to table of contents

Practical article: AACR Permit: what documents to prepare before submission

8. Obstacle Limitation Studies and Aeronautical Data

The analysis distinguishes between geometric obstruction and effects on flight procedures or radio-electric compatibility. Fitting under a geometric surface does not, by itself, demonstrate the absence of an effect on ILS or other CNS facilities.

Input data

Geodetic data and metadata, terrain model, existing and proposed objectives, maximum height and their configuration, applicable aeronautical surfaces, and data provided by CNS facility managers. For ILS, the localizer (LOC) and glide path (GP) are identified separately.

Technical analyses and checks

  • Obstruction: modeling OLS surfaces and, where applicable, OFZ; calculating penetrations with consistent elevations and conventions; inventory of permanent and temporary obstacles. The effect on flight procedures is addressed through appropriate specialized evaluation.
  • Geometric shading: justifying the relationship between the objective and existing obstacles admitted as reference, according to applicable criteria. The mere fact that one building is behind another is not sufficient demonstration.
  • ILS and CNS: analysis of position relative to antennas, protection zones, and relevant critical/sensitive areas, geometry, materials, and mobile configurations. Electromagnetic shading is delimited from reflections, diffraction, and multipath propagation; a preliminary geometric check alone does not quantify signal degradation.
  • When demonstrating radio-electric effect is necessary, the model, manufacturer data, scenarios, and acceptance criteria are established with AACR and the facility manager. The need for simulations, measurements, or flight inspections results from the applicable assessment.

Deliverables

Obstacle report, plans and sections, inventory of coordinates and elevations, penetration table, assumptions, and limitations. The CNS component explicitly specifies whether the deliverable is a preliminary geometric check or a radio-electric compatibility study based on modeling or measurements.

Normative basis and scope

Grounding condition: For the DANA methodology, the applicable controlled copy is required. Edition 2/2018 is identified in the consulted AACR bibliography, but the current revision and full text must be confirmed before using criteria or thresholds from the procedure.

Sky Meridian Service: Obstacle Limitation Studies and Aeronautical Data · Back to table of contents

Obstacle limitation studies: data required for OLS, CNS, and shading analysis: practical article for project preparation.

9. AIP Updates

AIP updating aims for consistency between the authorized or approved configuration, the measured situation, and the published information. Data preparation and publication via the aeronautical information service are distinct responsibilities.

Input data

AIP and current amendments, measured data, approved plans, operational decisions, coordinates and elevations, declared distances, characteristics of surfaces and equipment, proposed entry-into-service date.

Technical analyses and checks

  • A record of changes is maintained, and text, tables, charts, and datasets are cross-checked; each value has an identifiable origin, unit, precision, and responsible party.
  • Conversions, rounding, transfer integrity, and revisions are controlled. For declared distances or modified coordinates, technical documents justifying the values are retained.
  • Handover is coordinated with the AIS provider, including the AIRAC calendar where applicable and the choice of the appropriate information product according to the nature and duration of the change.

Deliverables

Package of data and proposed text, plans or charts in the required format, verification report, source-value-publication matrix, and record of acceptance or received observations.

Normative basis and scope

Grounding condition: Transmitting a data package does not equate to publication or approval of the operation of the modified configuration. Timelines are coordinated with data provision agreements.

Sky Meridian Service: AIP Updates · Back to table of contents

AIP updating: how to prepare data and the AIRAC calendar: practical article for project preparation.

10. Aircraft Compatibility with the Aerodrome

Compatibility is demonstrated for the reference aircraft, its configuration, and the analyzed operational scenario. The aerodrome reference code is a classification benchmark; the evaluation must cover all constraints relevant to the operation.

Input data

Manufacturer data for the aircraft variant, wingspan, length, wheelbase, main gear track, turning dimensions, weights, and gear characteristics; measured infrastructure, published load-bearing capacity, obstacles, service facilities, and operating conditions.

Technical analyses and checks

  • Geometry: trajectories and swept paths, edge and object clearances, taxiway/apron/stand separations; verifying access and exit in the effective configuration.
  • Structure and operation: aircraft load compared to available bearing capacity in the applicable reporting system; weights and operational frequencies, jet blast effects, restrictions, and protection measures.
  • Interfaces: rescue and firefighting, handling, towing, fueling, equipment parking, and potential influences on CNS. Compensatory measures are evaluated and assigned to responsible parties.

Deliverables

Compatibility report, maneuver plans, requirement-verification-result matrix, proposed restrictions, and safety assessment associated with the change, as applicable.

Normative basis and scope

Grounding condition: For use by aircraft exceeding certified design characteristics, the approval procedure in ADR.OPS.B.090 must be verified. Acceptability is established for documented conditions, not for any operation of the respective type.

Sky Meridian Service: Aircraft Compatibility with the Aerodrome · Back to table of contents

Aircraft compatibility: how to prepare the evaluation for an aerodrome: practical article for project preparation.

11. AltMoC, ELOS, and Special Conditions

AltMoC, ELOS, and special conditions have different functions and procedures. Classification is based on the regulatory requirement, the target AMC or certification specification, and the reason why the standard solution does not cover the situation.

Input data

The exact requirement and its edition, the certification basis, the existing or proposed situation, the technical demonstration, relevant operational experience, and the limits within which the use of the solution is requested.

Technical analyses and verifications

  • AltMoC: describes the alternative means to the AMC and demonstrates that the regulatory requirement is met; includes the affected procedures and manual revisions.
  • ELOS: formulates the demonstration of an equivalent level of safety for the alternative to the certification specification, with assumptions, arguments, evidence, and conditions of use.
  • Special conditions: documents the characteristic for which the CS are inadequate or unsuitable; the competent authority establishes the special conditions and their integration into the certification basis.

Deliverables

Classification memorandum, compliance matrix, technical and safety demonstration, operational conditions, revised documents, and response package to authority observations.

Regulatory basis and scope

Foundational condition: A favorable risk assessment does not automatically transform a non-compliance into an approved AltMoC or ELOS. Implementation follows the applicable procedure and approvals.

Sky Meridian Service: AltMoC, ELOS and special conditions · Back to table of contents

AltMoC, ELOS and special conditions: how to choose the mechanism and prepare the dossier: practical article for project preparation.

12. Operational, technical, and safety consulting

Technical and operational consulting starts from an identified configuration and a measurable problem: capacity, availability, restriction, change, or non-compliance. The assessment tracks the interdependencies between infrastructure, procedures, and organizations.

Input data

Certification basis, aerodrome manual, procedures, traffic data, inspection reports, occurrences, supplier contracts, and current technical configuration.

Technical analyses and verifications

  • Delimits the analyzed system, scenarios, and acceptance criteria; findings are separated from assumptions requiring additional data.
  • Compares solutions by operational effect, compliance, resources, residual risk, and maintenance; includes effects on organizations using the same infrastructure.
  • Plans the implementation and effectiveness verification of measures, including procedure modification, training, and aeronautical data updates when affected.

Deliverables

Technical report, options analysis, contracted assessments, implementation plan with owners and deadlines, validation criteria, and monitoring conditions.

Regulatory basis and scope

Foundational condition: The scope of the consulting must be separated from operator responsibilities, certified supplier activities, and AACR decisions.

Sky Meridian Service: Operational, technical, and safety consulting · Back to table of contents

Airport consulting: from operational diagnosis to a verifiable action plan: practical article for project preparation.

13. Compliance monitoring and SMS

Compliance monitoring verifies adherence to applicable requirements. The safety management system identifies hazards, assesses risks, and tracks the effectiveness of measures. The two processes are correlated through evidence, without substituting one another.

Input data

Requirements register, organization structure, manuals, monitoring program, previous findings, occurrence reports, hazard register, planned changes, and indicators used.

Technical analyses and verifications

  • Compliance: planning audits based on domain and risk, evidence sampling, formulating findings against requirements, and tracking corrective actions.
  • SMS: description of the hazard and consequences, assessment of initial and residual risk through the organization's approved method, assignment of measures, and documentation of risk acceptance.
  • Effectiveness: root cause analysis, implementation verification, and outcome testing; indicators have definitions, data sources, thresholds, and owners.

Deliverables

Monitoring program and reports, findings register, action plans, safety assessments, hazard register, and management reports, within the limits of contracted services.

Regulatory basis and scope

Foundational condition: Administrative closure of an action does not demonstrate its effectiveness. Evidence must show both implementation and the effect on the targeted requirement or risk.

Sky Meridian Service: Compliance monitoring and SMS · Back to table of contents

Compliance and SMS: how to link audits, risks, and corrective actions: practical article for project preparation.

14. Handling and fuel handling audits

Handling and fuel handling audits evaluate processes and evidence against stated criteria. Criteria may originate from requirements applicable to the aerodrome operator, supplier authorizations, and contractually assumed standards.

Input data

Scope of services and locations, authorizations, contracts, procedures, personnel competence, equipment inventory, maintenance, occurrence reports, and for fuel, reception documents, traceability, and quality control.

Technical analyses and verifications

  • Handling: observation of aircraft operations, equipment positioning, collision and FOD prevention, communication, airport interfaces, and compliance with equipment limits.
  • Fuel: documented quality chain, reception and storage, checks and sampling prescribed by applicable procedures, filtration, equipment, refueling, and prevention of contamination or fire.
  • Findings: requirement, evidence, deviation, consequence, and owner; distinguishes immediate correction from root cause action.

Deliverables

Audit plan and checklist, report with evidence, prioritization of findings, action plan, and closure verification. JIG/EI or beneficiary standards are identified with the contractual edition if they are part of the audit criteria.

Regulatory basis and scope

Foundational condition: A consulting audit is not equivalent to a JIG/EI certification. New European requirements for handling with application from March 27, 2028, are tracked separately from obligations applicable in 2026.

Sky Meridian Service: Handling and fuel handling audits · Back to table of contents

Handling and fuel audit: the documents and verifications that matter: practical article for project preparation.

15. Airport procedures and manuals

Manuals and procedures must describe the configuration and the actual way of operating. A revision has an object, owner, trigger criteria, sequence of actions, and records that allow for the verification of implementation.

Input data

Applicable requirements, approved manual, existing processes and workflows, interfaces with ATS/CNS and suppliers, technical limitations, relevant occurrences, and planned changes.

Technical analyses and verifications

  • Constructs the requirement–procedure–owner–record matrix; verifies activity coverage and the elimination of contradictions between documents.
  • Defines thresholds and conditions for normal, degraded, and emergency operations; procedures specify communication, restrictions, and authorization for returning to normal.
  • Validates applicability through walkthroughs, exercises, or field observations, according to the process; controlled distribution and training are planned in conjunction with entry into force.

Deliverables

Revised manual or procedures, process diagrams when useful, forms, compliance matrix, revision history, and implementation package.

Regulatory basis and scope

Foundational condition: Editorial revision, internal approval, and approval or notification to the AACR are distinguished based on the type of change and the applicable requirement.

Sky Meridian Service: Airport procedures and manuals · Back to table of contents

Airport procedures: how to transform requirements into applicable instructions: practical article for project preparation.

16. Training in the airport domain

The training program is defined starting from job responsibilities and necessary competencies, not just from a list of topics. The evaluation must show that the individual can apply the relevant procedures under the intended operating conditions.

Input data

Job descriptions, competence matrix, local procedures, equipment types, training history, competence assessment results, and changes affecting the activity.

Technical analyses and verifications

  • Establishes observable objectives, access conditions, theoretical and practical content, instructor qualifications, and evaluation method.
  • Differentiates between initial, periodic, refresher, and change-associated training, depending on the applicable requirement and the organization's program.
  • Verifies application in relevant scenarios and defines criteria for promotion, remediation, and re-verification.

Deliverables

Adapted program and materials, practical scenarios, evaluation tools, results, participation and competence records, plus recommendations for supplementing the local program.

Regulatory basis and scope

Foundational condition: Course attendance and demonstration of competence are different outcomes. The issued document must describe exactly the training and assessment performed, without suggesting an authorization that is not included.

Sky Meridian Service: Training in the airport domain · Back to table of contents

Airport training: how to build a competency-based program: practical article for project preparation.

17. Assistance for aerodrome certification

Assistance for certification organizes the compliance demonstration for the aerodrome and the operator. The starting point is the scope of the application and the certification basis established by the competent authority.

Input data

Application and AACR correspondence, certification basis, aerodrome plans and data, organization documents, manual, procedures, training records, and list of open findings.

Technical analyses and verifications

  • Develops the compliance matrix with links to identifiable and current evidence; separates physical configuration compliance from organizational and operational requirements.
  • Identifies differences between documents and the field, gaps in evidence, and cases requiring ELOS, special conditions, or other applicable mechanisms.
  • Prepares inspections and demonstrations, tracks responses to findings, and verifies the integration of restrictions into the manual and operational data.

Deliverables

Compliance file, requirement–evidence matrix, remediation plan, revised documents, record of responses, and support for technical interaction with the AACR.

Regulatory basis and scope

Basis condition: The issuance or modification of the certificate belongs to the competent authority. The support service cannot guarantee a decision independent of the demonstration of compliance.

Sky Meridian Service: Assistance for aerodrome certification · Back to table of contents

Aerodrome certification: how to organize the file and the demonstration of compliance: practical article for project preparation.

18. Hardware and software solutions

Solutions for monitoring, records, and automation of aerodrome processes are specified through verifiable requirements regarding data, availability, security, and fail-safe behavior. The applicability of aeronautical requirements depends on the function and use of the system.

Input data

Processes, users and roles, data sources, interfaces, volumes, precision and acquisition intervals, environmental conditions, required availability, and the consequences of incorrect data or unavailability.

Technical analyses and checks

  • Architecture is defined: acquisition, validation, storage, processing, display, and export; each interface has a format, units, time conventions, and error handling rules.
  • Role-based access, traceability of changes, backups, and restoration procedures are implemented; for sensors, calibration, uncertainty, and periodic checks are specified.
  • Functional requirements and defect scenarios, loss of communication, or missing data are tested; migration, integration, and reversion to a known configuration are validated.

Deliverables

Specification, architecture and interfaces, prototype or system implemented according to the contract, plan and test reports, operational, administration, and maintenance documentation.

Regulatory basis and scope

Basis condition: A record-keeping application does not become a certified CNS system through use. Functions with a safety impact require specific classification and demonstrations before operational use.

Sky Meridian Service: Hardware and software solutions · Back to table of contents

Aerodrome digital solutions: how to define requirements, data, and testing: practical article for project preparation.

19. Project management

Project management integrates scope, schedule, cost, quality, and changes through an approved baseline. Reporting must allow for decisions on critical activities and the responsibilities for unblocking them.

Input data

Contracts, brief, funding, schedule, budget, permits, deliverables, resources, and interfaces between design, verification, procurement, execution, and operation.

Technical analyses and checks

  • The scope is broken down into activities and deliverables, with dependencies and acceptance criteria; the schedule distinguishes work duration from approval and access times.
  • Physical and documentary progress, committed costs, and forecasts are tracked; deviations are linked to causes, effects, and measures.
  • Changes are evaluated before decision-making through impact on the solution, cost, schedule, and approvals; approved revisions are distributed under control.

Deliverables

Management plan, schedule and updates, risk and change register, progress reports, record of decisions, and documents for stage acceptance.

Regulatory basis and scope

Basis condition: The project manager, designer, verifier, site inspector, and contract supervisor have distinct roles. The contract specifies the mandate and limits of each.

Sky Meridian Service: Project management · Back to table of contents

Project management: how to correlate schedule, costs, and decisions: practical article for project preparation.

20. Contract administration GD No. 1/2018

Contract administration tracks the application of contractual conditions to documented facts. Identify the Annex to GD No. 1/2018 used, the applicable form, and the order of precedence of the contract documents.

Input data

Contract agreement, general and special conditions, accepted offer, specifications, drawings, schedule, instructions, correspondence, work progress reports, and records contemporaneous with the events.

Technical analyses and checks

  • A matrix of obligations and deadlines is constructed; notifications are correlated with the event, clause, and proof of transmission.
  • For changes and claims, the cause, the invoked contractual right, the effect on the schedule, and the cost basis are analyzed; confirmed facts are differentiated from estimates.
  • Approvals, payments, schedule updates, handovers, and subsequent obligations are tracked according to the contract and applicable legal framework.

Deliverables

Correspondence and deadline register, event analyses, supporting documents for notifications and claims, contractual reports, and record of decisions.

Regulatory basis and scope

Basis condition: Deadlines or clause numbers from another contract are not automatically adopted. Verify the annex, special conditions, legal amendments, and the authority of the person issuing the decision.

Sky Meridian Service: Contract administration GD No. 1/2018 · Back to table of contents

GD No. 1/2018 contracts: how to document notifications, delays, and changes: practical article for project preparation.

21. Public procurement and tendering

Preparing a procurement or a tender begins with framing the procedure and translating requirements into verifiable results and evidence. Maintain consistency between the technical solution, resources, schedule, and price.

Input data

Award documentation, clarifications and amendments, technical requirements, qualification and evaluation criteria, forms, contract, quantities, deadlines, and proposed resources.

Technical analyses and checks

  • For technical documentation: describe performance and acceptance criteria, correlate parts and quantities, and eliminate contradictions that may affect tendering.
  • For the tender: prepare the requirement-response-evidence matrix, methodology, schedule, and resources; check the link between activities, productivity, and costs.
  • Control revisions and responses to clarifications, assumptions, subcontractor responsibilities, and document completeness before submission.

Deliverables

Technical documents for award or technical proposal, compliance matrix, schedule, resource plan, verification of correlation with the financial proposal, and technical responses to clarifications.

Regulatory basis and scope

Basis condition: The airport or utility name alone does not establish the procurement regime: verify the entity, activity, and subject of the contract. Thresholds and deadlines are taken from the legal form applicable to the procedure.

Sky Meridian Service: Public procurement and tendering · Back to table of contents

Public procurement: how to correlate the technical proposal, resources, and price: practical article for project preparation.

Defining the brief and deliverables

The contractual brief must allow for the evaluation of the proposal content and the acceptance of deliverables based on technical criteria. Specify at least:

  • Subject and phases: physical and functional limits, capacities, specialties, scenarios, design phases, or evaluated processes.
  • Data and studies: existing sources, additional investigations, data owners, and conditions under which these are accepted for calculation.
  • Methods and references: regulatory register, analysis methods, assumptions, and acceptance criteria.
  • Submission: reports, summaries, drawings, models and databases, editable or signed formats, revisions, and verification documents.
  • Interfaces: responsibilities of the designer, beneficiary, verifiers, operators, and authorities; procedure for resolving observations.
  • Schedule and changes: stages, dependencies, site access, submission deadlines, and handling of brief modifications.
  • Costs: fee, studies, verifications, travel, external taxes, and assistance, delineated in the proposal.

Technical questions

What does the reference aircraft mean in the project?

It is the aircraft identified for supporting the analyzed verification, by type, variant, and documented parameters. Different critical conditions may result for geometry, load-bearing, or servicing; these are recorded in the design basis.

Does the geometric obstruction study demonstrate compatibility with ILS?

Geometric conclusions refer to the analyzed surfaces and criteria. Effects on LOC and GP require specific evaluation of CNS protection and, where appropriate, radio-electric basis based on data, modeling, or measurements accepted for that situation.

Can geometric shading be used as a demonstration of electromagnetic shading?

The two demonstrations have different objectives and criteria. The radio-electric analysis must address the position relative to the facility, propagation, and obstacle configuration according to the applicable methodology. The geometric conclusion is not automatically transferred to the ILS signal.

Which edition of a regulation applies?

Verify the approval act, amendments, application date, scope, and transitional provisions. For an aerodrome, add the certification basis and change regime. For internal procedures, request the controlled copy.

What else needs to be confirmed for the DANA reference?

The official AACR bibliography consulted identifies AACR-DANA-MET-CNS-02, edition 2/2018. The full text and applicable controlled revision must be confirmed before citing articles, geometric parameters, or acceptance criteria in a project's documentation.

Do regulations change between a project in Bihor and one in another county?

The national and European framework applies according to its scope. Site data, local regulations, permits, design parameters, and operator conditions may differ; these are established for each investment.

Register of normative references

The official sources below support the identification of the regulatory framework. The project-specific register complements articles, standard editions, national annexes, application dates, and references resulting from the design brief. Links to the Legislative Portal must be consulted together with the history of consolidations.

Documentary revision: 14 October 2026. The AACR-DANA-MET-CNS-02 reference remains subject to confirmation of the controlled copy; the guide does not reproduce unverified internal criteria.

Defining services for your project

Send the site location, project object and phase, available documents, and target deadline. For an airport project, add the targeted configuration, reference aircraft, and operational scenarios to be verified.

Discuss the technical topic with Sky Meridian

All services · Our team's projects