Lean MES Open Source Manufacturing Execution System
Flexible Manufacturing Solutions through Open Standards and Free Software....
MES Virtualization Tools and Techniques for Development and Production Environments
Construction of QA test and development environment (the environment) for MES related projects,
application test-bed scenarios, simulations, and prototyping.

    Environment infrastructure content.

1. Hardware.

    1.1. Development/QA Server. Server running virtual machine(s) application to host multiple virtual systems
        and builds. Builds act as a templates, build to have a specific; OS and pre-installed
        application(s) to meet typical solution(s) criteria(s).
        New virtual machine is created using one of the available build in event of new project, solution,
        customer, modification to existing solution/project that have no corresponding virtual machine,
        new application test and prototyping, stress test and similar scenarios.
        Example of Virtual Machine FTP upload to VM Builds Strorage.

    1.2. Development/QA Network (further: the network). Physically isolated network, not a part of any office or
        other network(s), not connected to the internet. Network routing is not allowed between the network
        and any other network. The network is designated for device communication and application'
        communications related to project development. High isolation required to minimize any potential
        interference from non-related devices and computers.

        1.2.1. Access to the network provided through application layer of standard OSI model or virtual
            machines consoles. Access through OSI application layer possible trough multi-homed virtual
            machines with 2 or more NICs. (Optionally allow only controlled outgoing access to the Internet).

    1.3. Automation controllers, barcode readers, sensors, gateways and similar devices (further: the  devices).
        Minimum set of typical devices include; PAC, PLC, Vision Sensors, Tools, RFIDs, Ethernet I/Os, Sensors,
        Device servers, Industrial switches, Barcode readers and similar. Purpose, - allow to assemble and test
        an exact or miniature     or mimic representation of the actual environment. Enables to construct a
        prototype or test case for further replication/reuse in the actual environment.

    1.4.  Software licensing. Install and enable distribution, if distribution is possible, of software licenses. Software
        identified as the application(s) required to develop and/or run the solution during it's construction state.
        Licensing may use software and hardware key/activation. The environment provides mechanism to
        assign hardware key, e.g. USB, to a specific virtual system.

2. Software.
    2.1. Virtualization software. VMWare Server, WorkStation or Fusion, or Hyper-V.
           VMWare ESXi is not applicable as a result of required conversion while porting to/from ESXi host system.
           VMWare Fusion is AATech LLC preferred tool due to it's exceptional stability, excellent performance ( disk i/o
           operations gain of 20-50% over VM running in VMWare engines for Microsoft).
           Example of VMWareFusion environment.
           Important! Virtual Machines built in VMWareFusion and VMWareWorkstation are fully interoperable.
           In other words virtual machine constructed in Fusion can be ported and run in Workstation and vice-versa.  

    2.1. MES software. Currently available software available from software developers free and/or through
        contract(s), and/or through partner/SI agreement(s).

3. Objectives and Expectations.

    3.1. Enable rapid creation of development system(s) using a specific build(s) or templates.

    3.2. Provide test-bed environment for safe application(s) testing and solution(s) development.

    3.3. Provide QA environment to support standard develop-test-stabilize-release-maintain cycle flow of

    3.4. Enable disaster recovery process for configuration(s), applications(s), script(s), interface(s) configuration
        and any other applicable static content. Thus allows quickly reconstruct the production environment,
        except any dynamic or historical content.

    3.5. Allows multiple development resources to work in parallel using the same virtual system remotely or local
        copies of the same virtual system, to develop and merge solution' artifact(s) for QA and final delivery.

    3.6. Allows developer(s) to have functional solution(s) while performing changes/deployment onsite. Any
        changes to actual production either tested on the developer' local virtual system or copied from
        production system if performed directly, except when latter is restricted by agreement.

    3.7. Build a collection of various artifacts, methods and techniques for future reuse and references in similar

    3.8. Creates demo/study cases for perspective customer(s) and/or internal resources development.