Getting the Most from Your OmniSMS Manual System

A well-structured SMS manual is the foundation of an effective Safety Management System. The OmniSMS® Manual System is designed to help organizations review, customize, maintain, and continuously improve their safety documentation while ensuring consistency across policies, procedures, and operational processes.

Every OmniSMS document is written in clear English using standardized aviation terminology and incorporates essential system safety attributes throughout. These manuals are designed to support organizations in implementing structured safety policies, effective controls, measurable processes, and continuous safety improvement throughout their aviation operations.

Understanding the OmniSMS Manual Framework

The OmniSMS Manual serves as the central document that links all supporting programs into one integrated SMS documentation system.

Rather than operating independently, supporting manuals are connected through referenced procedures and paragraph numbering, creating a harmonized management system that simplifies implementation and regulatory review.

The manual structure also aligns section numbering with FAA SMS Voluntary Program components and references applicable Specific Regulatory Requirements (SRRs), making both internal self-assessments and FAA design validation activities more efficient.

Supporting Programs That Complete the System

The complete OmniSMS documentation package includes several supporting programs maintained as individual documents, including:

  • Emergency Response Plan (ERP)
  • Internal Evaluation Program (IEP)
  • Event Investigation Guide
  • SMS Training Program

Because these programs reference one another, organizations should avoid changing paragraph numbering during editing to prevent cross-reference errors.

Maintaining separate documents also makes future revisions easier while keeping the primary SMS Manual concise and manageable.

Integrating Documentation with the OmniSMS Web Application

The manuals are designed to work alongside the OmniSMS web application rather than as standalone documents.

Many Safety Risk Management (SRM) and Safety Assurance (SA) activities described throughout the documentation rely on processes performed within the web application.

Organizations using the OmniSMS subscription receive access to:

  • Documentation
  • Web application
  • Training resources
  • Ongoing support

This integrated approach allows documentation and operational processes to remain synchronized.

Responsibilities When Customizing Your Manuals

Omni manuals are licensed for use by the purchasing organization and are intended to be fully customized; not used as generic templates.

Each organization should ensure that:

  • Policies accurately reflect operational practices
  • Organizational structures are correctly represented
  • Management titles and responsibilities are current
  • Regulatory references match the applicable authority

Management participation during document review is strongly recommended to ensure the final manuals accurately represent actual company operations.

Managing Document Templates and Revisions

Organizations are responsible for maintaining their customized Word templates after editing.

Best practices include:

  • Saving every revision with a new revision number and date
  • Preserving previous versions for historical reference
  • Maintaining revision integrity throughout document updates

Revision histories included in Omni templates should be removed when creating the organization’s original branded manuals.

Formatting Standards That Simplify Future Updates

OmniSMS manuals are delivered in Microsoft Word format to simplify editing and future revisions.

The formatting system includes:

  • Section-based page numbering
  • Revision history tracking
  • List of Effective Pages (LEP)
  • Hyperlinked Tables of Contents
  • PDF bookmark support

Rather than referencing page numbers, organizations should reference paragraph numbers because page numbering may change after revisions.

Publishing and Accessing Electronic Documents

After editing, manuals should be converted into PDF format before publication.

Electronic versions can then be uploaded into the OmniSMS platform where personnel can quickly access:

  • Policy Statements
  • SMS Manual
  • Emergency Response Plan
  • Internal Evaluation Program
  • Event Investigation Guide
  • SMS Training Program
  • Additional company documents

Electronic document management also helps ensure personnel always access the latest approved revision.

Editing Guidelines for Better System Integration

When customizing OmniSMS documentation, organizations should review:

  • Company names and branding
  • Regulatory references
  • Contact information
  • Organizational titles
  • Operational terminology

Existing company programs, such as Emergency Response Plans or Internal Evaluation Programs, may also be integrated with OmniSMS guidance where appropriate.

This approach supports employee familiarity while minimizing unnecessary procedural changes.

Tips for Efficient Document Editing

Several Microsoft Word features simplify customization, including:

  • Find and Replace for organization names
  • Automatic Table of Contents updates
  • Consistent revision numbering
  • Standardized headers and logos

After edits are completed, organizations should verify:

  • Table of Contents accuracy
  • List of Effective Pages
  • Footer revision numbers
  • Revision dates throughout the document

Creating Your Organization’s Original Manuals

Most operators convert Omni templates into their own original manuals by:

  • Updating the cover page
  • Changing the revision status to “Original”
  • Clearing previous revision history
  • Removing revision blacklines
  • Updating revision records
  • Revising page footers

This process creates a customized document set that accurately reflects the organization’s operations.

Validating Critical Documents Before Publication

Certain documents require additional review before release.

For example, Emergency Response Plans should always be verified by:

  • Confirming contact information
  • Conducting emergency response drills
  • Updating procedures based on exercise results

Testing these procedures before publication helps improve document accuracy and operational readiness.

Keeping Documentation Current

Subscription clients periodically receive revised templates that incorporate:

  • Regulatory updates
  • Process improvements
  • Enhanced safety guidance

Organizations can compare new revisions against their existing manuals, incorporate desired changes, update revision records, and publish new editions while preserving their own customized content.

This structured revision process simplifies long-term document management and helps maintain document consistency.

Electronic Documentation Supports Better Control

Electronic document delivery significantly reduces administrative effort compared with traditional paper manuals.

Benefits include:

  • Easier revision management
  • Improved document currency
  • Global accessibility
  • Reduced printing costs
  • Faster employee access
  • Improved version control

As aviation organizations increasingly rely on digital systems, electronic document management has become an important component of effective SMS administration.

Conclusion: Using an SMS Implementation Guide for Long-Term Success

An integrated documentation system is essential for maintaining a consistent and effective Safety Management System. The OmniSMS Manual System provides organizations with harmonized manuals, supporting programs, structured revision processes, and integrated web-based tools that simplify customization and ongoing management.

By following this SMS implementation guide, organizations can maintain accurate documentation, align operational procedures with regulatory requirements, support continuous improvement, and ensure their Safety Management System remains current, practical, and ready for future regulatory oversight.

Leave a Reply

Your email address will not be published. Required fields are marked *