Configuration & data management · Malaysia

Every change, kept under control.

I’m Azuan Hanafi, a configuration and data management specialist with 9+ years keeping engineering lifecycle data controlled and traceable, now in certification-driven airborne engineering aligned to DO‑254, DO‑178C and ARP4754A.

  • 9+ years in regulated industries
  • Aerospace · Medical device · Automotive
Aerospace
Scroll

About

Baselines, change control, and audit-ready status accounting across aerospace, medical device, and automotive. I keep every configuration item identified, every change approved and every release reproducible.

More about my experience

Experience

Four roles, one discipline.

A track record of tool and repository governance, process discipline, and cross-functional collaboration across regulated, standards-driven industries.

Download full resume
Current Aerospace

Software Configuration Management Specialist

Turkish Aerospace Malaysia

Apr 2026 - Present Cyberjaya

  • Handle configuration management for 5 concurrent airborne hardware and software projects, keeping each project’s baselines, changes, and releases controlled in parallel.
  • Developed a project Software Configuration Management Plan (SCMP), mapped against DO‑178C to cover configuration identification, baselines, change control, status accounting, and release.
  • Define and maintain configuration items across the engineering lifecycle (requirements, design, implementation, verification, release) for airborne electronic hardware and embedded software programs.
  • Establish and manage requirements, design, and release baselines so changes stay controlled and traceable.
  • Lead Software Change Control Board (SCCB) meetings and operate change control workflows (CR/PR/ECN) - impact assessment, change-request approval, and prevention of unauthorized changes.
  • Maintain release records and support reproducible builds and releases, including versioning of tools, inputs, and outputs.
  • Provide configuration status accounting and keep data audit-ready for compliance activities aligned to DO‑254, DO‑178C, and ARP4754A.
  • Support disciplined use of JIRA, IBM DOORS, LDRA, and SVN/Git for issue tracking, requirements, verification evidence, and release tagging.
  • Took ownership of JIRA administration, securing management approval for SCM to hold full responsibility for JIRA workflow governance, and designed the change management architecture now rolling out across the CM function.
  • Built a JIRA Change Request Dashboard from scratch for real-time visibility into CR status, approvals, and ownership.

Capabilities

Four ways I keep change controlled.

The four functions every configuration management plan has to cover, each one run on the same rules and leaving the same evidence.

01 / 04

Configuration identification

SCMP planning and configuration items defined across the lifecycle.

  • Software Configuration Management Plan (SCMP) mapped to DO‑178C
  • Configuration items across requirements, design, implementation, verification and release
  • One traceable item ID scheme, so items trace across baselines

Projects

Systems already at work.

Screenshots below are redacted - ticket assignees, ticket text, and internal program names have been removed or replaced with generic placeholders. No proprietary, confidential, or personal data is shown; only the tool and workflow I built are represented.

Self-initiated · Delivered

PQRE Dashboard

JIRA change request dashboard

JIRA Change Management Architecture

JIRA change control redesign

Upcoming

More Work in Progress

Another project is in the works. Details will be added here once it’s ready to share.

How I work

Controlled from request to release.

Every change follows the same path, so nothing slips in unapproved and nothing ships without a record.

  1. Step 1: Identify

    Define configuration items and baselines so every change has a home.

  2. Step 2: Control

    Route each change through impact assessment and board approval.

  3. Step 3: Account

    Report what changed, what’s approved and what’s released, ready for audit.

Skills & tools

The toolkit behind the work.

Six areas I work across, from the CM discipline itself to the systems and standards it runs on.

Configuration Management

Planning and running CM end to end, from identifying items to releasing them.

  • CM planning (SCMP)
  • Baseline management
  • Change control (CR/PR/ECN, CRB/SCCB)
  • Configuration status accounting
  • Configuration item identification
  • Release management
  • Audit & compliance evidence readiness

Engineering CM & Requirements Tools

Tools that hold controlled lifecycle data on airborne hardware and software programs.

  • JIRA
  • IBM DOORS
  • LDRA
  • SVN
  • Git

PLM / ERP & Service Management

Systems of record for product data, parts and service changes.

  • Windchill PLM
  • Oracle ERP
  • SAP
  • Cherwell CSM

Reporting & Analysis

Turning workflow and data-quality metrics into reports stakeholders can act on.

  • Microsoft Power BI
  • Google Looker Studio
  • Excel (Advanced, incl. VBA)
  • SQL

Collaboration & Documentation

Where plans, procedures and change records are written, reviewed and shared.

  • Confluence
  • Microsoft 365
  • Teams
  • SharePoint

Standards & Regulated Environments

Frameworks I’ve worked under across aerospace, medical device and automotive.

  • DO‑254
  • DO‑178C
  • ARP4754A
  • IATF 16949
  • ISO 9001
  • IEC 60601

Education & certifications

Learning that backs the work.

Diploma in Automotive Management Systems

DRB‑HICOM University of Automotive Malaysia

CGPA 3.95 / 4.00

  • Windchill PLM Super UserCochlear Academy
  • First Aid at WorkplaceSt John Ambulance of Malaysia
  • SQL Essential TrainingLinkedIn Learning
  • Advanced Excel: VBALinkedIn Learning
  • Fundamental Skills for Data Work: Data Analysis and InterpretationLinkedIn Learning

Let’s talk

Have a change that needs control?

Open to configuration and data management roles.