Quality Management Process

Quality and MYNAH Technologies

Quality is a guiding principle of business at MYNAH Technologies, LLC. Because our customers rely upon our products to operate their plants and test their process automation systems, we are committed to provide the highest-quality, highest-performance software and process simulation solutions available.

To ensure that we are meeting the needs of the marketplace that we serve, we are committed to comply with our customer requirements. This includes all aspects of running our business from designing and manufacturing products that meet industry accepted standards to shipping products per the agreed upon timeframe.

MYNAH Technologies’ management team communicates the quality policy within the organization on a regular basis throughout the year and periodically reviews the company quality policy to ensure that it is appropriate to the purpose of the organization as dictated by the needs of our customers and marketplace. In addition, management annually reviews the Quality Management System to determine whether process modification is appropriate.

MYNAH Core Values and Business Definition

MYNAH Technologies operates in accordance with the following core values, in fulfillment of our business definition.

Core Values:

  • INTEGRITY – Unmatched honesty, Responsibility, and Commitment
  • ATTITUDE – Positive energy; Respect for each individual
  • INNOVATION - Desire for knowledge; Open to new ideas
  • EXCELLENCE – Motivation to be the best individually and corporately

Business Definition

We reduce the Cost, Risk, and Complexity of Plant Operations.

How We Do It

We do it with Innovative and Flexible Connections for Process Automation and Simulation.

MYNAH Organization and Quality Team

MYNAH Technologies LLC is an ISO 9001:2008 certified business. The quality team consists of the Quality Coordinator, Vice-President Technology, Vice-President Operations, Vice-President Engineering and the President and COO. The Quality Coordinator has audit responsibility to ensure that quality procedures and documentation have been followed and completed for all approved processes. The Vice-President Technology has responsibility for the quality process within the software development group. The Vice-President Operations and the President and COO have responsibility for the quality process within the sales and operations group. The Vice-President Engineering has the responsibility for the quality process within the Engineering group.

Personnel Qualification and Testing

The success of our company is dependent upon the capabilities of the MYNAH Technologies’ staff. MYNAH personnel are provided with orientation and ongoing training and development in order to maintain or increase the skills necessary to carry out the responsibilities of their job role. MYNAH personnel have frequent Agile Performance Management discussions with their respective supervisor. The APM process allows the supervisor to provide guidance and input to the employee in the following areas:
  • Performance: Clarify expectations, set business goals, and provide regular check-in.
  • Impact: Personal performance and how it ties to the company. Communicate expectations of the organization with regard to employee performance.
  • Feedback: Perspective, positive feedback, and constructive criticism.
  • Preferences: Performance related to organizational core values, talents, interests, and competencies.
  • Career: What would the employee like to do in the future?
  • Development: In what areas does the employee need to improve or develop skills?

In addition, all MYNAH personnel are trained in the quality procedures they are required to perform by the Vice-President Operations and the Quality Coordinator.

Customer Service and Software Support

All customer service requests received via phone or email are logged into the Website ticket system. A unique call tracking ID number is assigned to each ticket. The Application Engineering Team handles support tickets. Technical issues that cannot be resolved within one working day by the Application Engineers are escalated to the Vice-President Technology. The Vice-President Technology directs resolution of all product problems and software defect fixes.

To follow are the customer service standards for MYNAH Technologies LLC:

  • All commercial inquiries receive a response in one working day.
  • All technical inquiries receive a response in one working day.
  • Standard delivery of released product is 5 working days after receipt of purchase order.

Security Policy

Access to MYNAH Technologies LLC office in Chesterfield, Missouri, is restricted to MYNAH employees only outside of the hours of 7:30 AM to 6:00 PM CST during the work week. Entryways to the office space are key locked and distribution of the key is restricted.

Sensitive electronic documentation is stored in a private cloud hosted internally at MYNAH Technologies, LLC and backed up nightly to a secure third party server. Other electronic documentation is stored in a public cloud hosted and backed up by Google.

The MYNAH website, www.mynah.com, is hosted by Pantheon. Access to site documents and updates on www.mynah.com are password protected. In addition, Pantheon provides a SSL certificate and security services as part of the monthly hosting service for the website.

Source Code Management and Security

All source code is managed using Subversion. The Subversion system maintains audit trails. Revision history, incorporating detailed description of all changes, is included in each source module. All source code is backed up on a daily basis and the back-up media is stored off site. All servers are kept in a locked room with access restricted to network management personnel only.

Escrow source code beneficiary agreements are available as an optional Mimic Software Support service. MYNAH Technologies LLC source code escrow is managed by a professional software escrow service company.Software Product Development

Software Product Development Standards

Standards Product Development Methodology

The MYNAH Technologies Product Development Methodology is documented in product realization section 7 3.

Product Release Planning

The Vice-President Technology and the President and COO complete a product release plan on a quarterly basis. Product releases are planned based upon customer and sales force requests and marketing direction and planning. Major software releases include new software functionality and are distributed for general use. Maintenance releases include bug fixes and customer specific features and are initially released only to designated users. Major releases incorporate all bug fixes and customer specific features.

Programming Standards and Guidelines

Programming standards and development guidelines are set by the Vice-President Technology and defined in the MYNAH Technologies LLC Programming Standards and Guidelines Document. This includes standards for source code documentation, acceptable technology, and system management.

MYNAH Technologies LLC software products are developed with MFC (Microsoft Foundation Classes) and FCL (Framework Class Library), and DevExpress (application development tools).

Functional Requirements Definition

All products and product releases are defined with a product direction statement, detailed design document, and use case descriptions. These documents are used with the Programming Standards and Guidelines to develop new products.

Software Development and Code Testing

The product is developed under the direction of a Mimic Product Manager. The control documents used during programming are the Detailed Design and Data Model and the Programming Standards and Guidelines. The Vice-President Technology has the responsibility to review and audit samples of all source code developed. All products are tested, by the Software Development Engineer, for completeness and functionality in support of the detailed design document. The Vice-President Technology reviews all testing, performed by the Software Development Engineer.

Functional Product Testing

Functional tests are performed per the product use case requirements by an Application Engineer. The Vice-President Technology reviews all testing, performed by the Application Engineer.

Software Release Process

Upon completion of the functional test, all products are available for beta release. Beta release is a controlled release of the product to a select group of users who have agreed to test the product under specific conditions. The Mimic Product Manager supports beta release users. During the Beta testing period, final product documentation is completed by the Mimic Product Manager with support from the Marketing Associate.

Custom Projects Process

Project Execution Methodology

The MYNAH Technologies Custom Projects Process Execution Methodology is documented in support of the design and development standards - sections 7.3.2-7.3.7.

Document Checklist

The controlled forms that are used during project execution are referenced with respect to their project record names and folder locations in each Custom Project’s Document Checklist. The Document Checklist is a reference guide that indicates to project team members and auditors what controlled forms were employed in a project, and it also gives a general indication of the progress of a project based on the document rows that have been completed at any given point in time.

Project Plan

A Project Plan is defined and reviewed with the customer during the Planning Phase of the custom project. The project plan includes detailed project execution information for the custom project, design information for the implementation approach of the project, and personnel/contact information for the MYNAH, partner, and customer project team.

Definition Tasks

Definition tasks utilize MYNAH expertise in a front-end engineering design to assist in defining a system that best suits the desired functionality as defined by Customer.

  • Training DefinitionMYNAH helps define simulator training capabilities and helps define structured training scenarios. This is done by interviewing Customer’s training lead on overall training plans and simulator training goals. MYNAH organizes a review of the difficulty, importance, and frequency of standard tasks (DIF Analysis) to methodically identify the optimum strategy for each task — simulator training, pre- and post-work reviews, job aids, and/or no training. Then, MYNAH interviews Customer on possible custom expert scenarios based on process hazard analysis, human risk factors, plant incidents, or loss scenarios. After completion of the DIF Analysis, MYNAH provides a design considerations document that will be used as an input for development tasks.
  • Virtual Dynamic Simulator (VDS) Definition
    MYNAH helps define the simulator architecture to meet system requirements by interviewing Customer personnel. This enables MYNAH to perform a detailed design of a virtualized system architecture that meets the training requirements and information technology standards of the plant. MYNAH provides upfront review of the VDS hardware and software design, which confirms that the standards and expectations have been met. After completion of this review, MYNAH provides a design considerations document that will be used as an input for development tasks.

Development Tasks

Development tasks include the effort to design and build the system excluding integration tasks. Preliminary development considerations are obtained from the Customer on the training system objectives through the design considerations document. MYNAH reviews this document and creates a project plan which includes project scope, constraints, assumptions, new methods, uncertainties, and team contacts. MYNAH assigns key responsibilities to each individual based on a standard project schedule.

Model Development

Model development is the process of creating the simulation from the process or plant model perspective. This includes process models and transmitters up to the I/O models corresponding to the field instrumentation and devices and their associated control system I/O.
  • Review Process Data
    Using the available inputs — P&IDs, PFDs, equipment datasheets and sizing, performance data, and piping isometrics — MYNAH will organize and analyze the data to conceptualize the process model and identify areas where additional information may be required. In the case that information is not available, MYNAH makes reasonable approximations based on available data inputs.
  • Configure and Test Process Model
    MYNAH configures the process model with available data inputs. Using engineering design information is most effective in developing a representative process model, since dynamic behavior will be incorporated into the model. Once configured, the model will be tested to verify it meets model requirements.
  • Configure and Test Internal Controls
    When a control system is being constructed in parallel with the model development, MYNAH creates simplified controls in Mimic that will be utilized for testing the model until the control system is prepared for model integration to proceed. MYNAH uses the P&IDs along with the instrument index or the I/O list to lay out and configure internal controls if needed for plant model internal testing. These controls are specifically implemented in a way that can be later removed for integration purposes.
  • Configure and Test Local Controls
    The plant model includes models of all plant components that will operated by the control system, so the plant model includes local controls if they are present in the project scope. MYNAH uses local controller functional specs, I/O maps, and programs to lay out and configure the local controls. Normally, it is not important during control system operator training to practice operating the local controls, but it is important to be able to restore snapshots that include the state of the local controls. Therefore, the local controls are typically laid out and configured in simplified form in Mimic.
  • Conduct Process Model Review
    The process model review is a brief demonstration of the design basis to Customer. The process model typically is not yet controlled by the control system that will end up being the operator interface, so the process model review is not a preview of the operator experience. Instead, it is a look under the hood. MYNAH conducts the review early on, well before the process model is complete. The review may focus on a proof-of-concept of a key operating unit, or the review may show a complete plant area. The timing is chosen to provide an informative early introduction to the modeling approach and provide a valuable opportunity for detailed discussion of the design basis.
  • Conduct Model Acceptance Test
    The model acceptance test is a review demonstrating that the process models are complete and acceptably represent the plant’s steady state and dynamic performance. MYNAH provides an acceptance test agenda and test procedures prior to the model acceptance test. Issue tracking reports will be used to document issues encountered during testing. After these issues have been resolved, MYNAH will submit a completed report to Customer for approval.

Training Development

Training development includes the design and configuration of instructor screens, instructor controls, and training scenarios to meet training requirements as defined by Customer.

  • Review Training Data
    Potential training objectives — including instructor controls, snapshots and scenarios — may be identified through the completion of the design considerations by Customer. Identifying training objectives early using the design considerations document allows for development to be tailored to align with the training objectives. While this document will be used to help guide discussion on training needs, further definition is necessary to configure instructor controls and scenarios.Using other available inputs — process hazards analysis report, operating manuals, startup and shutdown procedures, instructor controls list, and scenario descriptions — MYNAH will organize and analyze the data for use throughout the project.
    Additional documentation that may assist in identifying current training needs can be provided or discussed in further detail on request.
  • Configure and Test Training
    MYNAH uses the design considerations to initially layout and configure instructor screens and controls in preparation for the training review. After this review, MYNAH will configure the instructor controls and scenarios based on the instructor controls list and scenario descriptions. Then MYNAH will perform representative dry-run testing of the training system’s operation under various conditions.
  • Conduct Training Review
    MYNAH provides upfront review of the instructor controls graphical lay out and of a representative training scenario sequence. Seeing the actual instructor control graphics and scenarios can help confirm that expectations are being met or work out useful changes early in the training development.

VDS Development

VDS development is the process of architecting the hardware and software required to support the plant model and the offline control system. This includes the physical infrastructure comprised of a server pc, network, and thin clients as well as the virtual infrastructure comprised of virtual machines and virtual networks. The system will be designed and built using the inputs provided by Customer.

  • Review VDS Design
    MYNAH assesses the provided inputs to align the design according to Customer’s system requirements. Identifying all of the hardware and software requirements allows for development of the VDS to align with the training objectives. MYNAH provides the system architecture and prepares the design of the VDS system hardware and software for review.
  • Configure and Test Hardware and Software
    MYNAH incorporates any changes indicated by the VDS review and finalizes the VDS system hardware and software design. MYNAH purchases the hardware and software components then configures the operating system software, virtualization software, and application software so that the VDS is ready to be loaded with the plant model and offline control system.
  • Review VDS Development Checkout
    MYNAH provides a checkout of the VDS system software and hardware build with Customer prior to shipment. This ensures that the system is properly prepared for delivery.

Integration Tasks

Although process model development is decoupled from control system development to minimize impact on the simulation schedule, integration tasks cannot be completed without a copy of the production control system.

Integration tasks are those required to establish a connection between the plant model and the offline control system. The offline control system refers to the production system modified to work in an offline environment.

Integration with Control System

MYNAH uses the P&IDs and offline control system along with the instrument index or the I/O list to lay out and configure the I/O model. The I/O model is Mimic’s interface between the plant model and the offline control system. It can be visualized as being Mimic’s model of the control system’s communications wiring or wireless networking as well as field instrumentation and devices.

Integration can be completed on the virtual dynamic simulator system hardware and software, or on Customer’s/control system integrator’s hardware and software if the required Mimic licensing is available.

Integration can start as early as the offline control system is provided. Note that integration tasks will not be able to be completed until the provided copy of the production control system is approved as final.

  • Support Control System FAT
    During control system FAT, MYNAH provides support to quickly identify issues caused by the offline control system or plant model configuration.
  • Conduct Integrated Model Acceptance Test
    Following the plant model development and control system integrations, MYNAH provides a model acceptance test. This integrated model acceptance test demonstrates the model performance while operated by an offline copy of the production control system.MYNAH provides an acceptance test agenda and tests prior to the integrated model acceptance test. Issue tracking reports will be used to document issues encountered during testing. After these issues have been resolved, MYNAH will submit a completed report to Customer for approval.After completion of testing, MYNAH provides a final design basis document.
  • Conduct Training Acceptance Test
    The training acceptance test demonstrates that the instructor training controls deliver the simulator training experience desired while operated by an offline copy of the production control system.MYNAH provides an acceptance test agenda and tests prior to the integrated model acceptance test. Issue tracking reports will be used to document issues encountered during testing. After these issues have been resolved, MYNAH will submit a completed report to Customer for approval.After completion of testing, MYNAH provides a final design basis document.It is common to combine this acceptance testing with the integrated model acceptance test, if the necessary data inputs are available.
  • Create Operation & Maintenance Manual
    MYNAH develops a reference manual that will describe how to operate the system and how to maintain the system. The subject matter of this document will encompass all phases of the project.
  • Install Hardware and Software
    MYNAH installs VDS or existing hardware, starts up the system and installs associated databases.
  • Conduct Site Acceptance Test
    Once issues from acceptance testing have been approved, MYNAH delivers the system to site. The key components delivered include the VDS hardware and software, the Mimic simulation and training database, the control system simulation database, and the operation & maintenance manual. Onsite, MYNAH demonstrates the training simulator in the form of a final site acceptance test and handoff.MYNAH provides an acceptance test agenda and tests prior to the site acceptance test. Issue tracking reports will be used to document issues encountered during testing. After these issues have been resolved, MYNAH will submit a completed report to Customer for approval.
  • Provide Instructor Training
    Following the system installation and site acceptance testing, MYNAH reviews the operation and maintenance manual with Customer to demonstrate the full capabilities of the system as installed. This ensures for proper training before handoff to Customer. Additional product specific training is available as a part of the MYNAH Simulation Maintenance Services.

How to Contact Us

For more information about MYNAH Technologies LLC Quality Management Process please contact us at:

MYNAH Technologies, LLC
390 South Woods Mill Road, Suite 100
Chesterfield, Missouri 63017 USA
1-636-728-2000 (International)
1-636-728-2001 (Fax)
ISO 9001:2008 Certified

E-mail: support@mynah.com