The majority cases the software accomplishment of the systems control happens during the system installation of manufacturing. The programming of PLC is available to control the engineers who may have fewer understanding about systematic and methodical design and programming. Only in major and demanding projects, devoted service provider systems for automation and information are requested. These specialists track a thorough sequential project methodology. Roughly, the steps of project are functional specification, manufacturing and procurement, hardware design, integration and control system development, factory acceptance test (FAT), and delivery including installation and documentation. The manpower allocated is based on observed data from previous projects. Nevertheless, the control system delegation design to committed subcontractor embodies the less interaction problem and communication between the control system and the mechanical system design team.
Approach of integrated design
Sequentially to give a rational information flow and to reach a decrease in the design lead-time we suggest an incorporated design come up to based on theory of axiomatic design. Axiomatic design is an easy, but powerful methodology of design. It bears the design process with a universal set of design procedures forcing the designer to consider systematically from a perspective of top-down. Thus, the two axioms, they are Information Axiom and Independence Axiom, guide the designer to produce a “good” solution and to choose the best one amongst alternatives. Theoretically, the design of axiomatic approach separates the design process into four syntactical perspectives and separated semantic, the domains of functional requirements (FR), customer requirements (CR), process variables (PV), and design parameters (DP). Even though originally built for mechanical systems engineering, the design of axiomatic has been practical to many other design contexts, together with software engineering. Consequently, the domains may have dissimilar understandings in various design contexts.
In the manufacturing system design, the DPs explain the processes in a format of solution-neutral, while the PVs specify the chosen resources, including hardware systems and human resources, software systems. The DPs in the developed system design consequently contact the FRs of the system of control to be designed. These are control actions, processes, and temporal requirements. This conceptual illustration will finally be mapped into the control system (PVs) implementation domain indicating the program builds and program code of the particular language, and the platform of run-time.
Moreover, common user specifications, for example reliability and re-configurability, best performance, are applying to the FRs from processes of manufacturing to be realized by the control system. Therefore, the control software design process of FR domain is pooling the specifications, resulting from the configuration of manufacturing system, and the most wanted the attributes of control system.