Tag Archives: engineering blog

The Exploration and Discovery of NFPA Foundation Regarding Electrical Safety

The Fire Protection Research Founded by National Fire Protection Association or NFPA currently sponsored an assembly for the Second Draft meetings for the National Electrical Code (NEC) comprised of Electrical Safety Research Advisory Committee (ESRAC). This took place in San Diego, California last October. Represented by Vince Baclawski, NEMA took part in this general Assembly. Baclawski is the senior technical director, together with Jack Lyons the Northeast field representative.

The meeting was started and opened by Casey Grand the director of the The Fire Protection Research Founded by National Fire Protection Association together with Donny Cook the advisory committee chair. The meeting started with the members of the co-making panels and other stakeholders coming from different industries regarding the electrical safety features that should take part in the foundation’s projects concerning about research.

The agenda in this meeting is comprised of the total overview of the organization: its current, completed, and planned or proposed projects. One of which is the discussion about the Power over Ethernet or others call it as (PoE) and several discussions about pools and marinas.

In identifying some future possible concerns, the foundation greatly put emphasis on what is the greatest value or impact that can be done for the electroindustry. With this in mind, the ESRAC functions as the trailblazing committee to make the foundation consider projects such as these.

To increase the number of installations the PoE systems are making caused concerns to arise because of the possible effects of the installations on the building safety. With this in mind, the NEC has successfully addressed some of the cabling structures placed within the buildings by heavily focusing on some of the bundling data cables that helps engineers to make up the overall system.

With this in mind, overheating is a safety and performance issue for the PoE systems. In addition to this, the Article 725 has mentioned the possible concerns regarding the ampacity tables for data/power cables that comes with the new cable designations. There are some key takeaways on this, they are:

Proper identification for the inherently safe installations

Expansion in the usage of life safety systems

Safety of the personnel working in electric industries

Identify the code applications and the necessary licensing requirements

Recent issues about cybersecurity

Together with valuable inputs from the attendees, the meeting identified the top five topics research projects can focus on, such as:

Proper code adoption and regulatory licensing

Equipment grounding conductors

Types of cord-connections installed in the kitchens

Electrical systems installed in some Marinas and Pools

Data gathered about the collection on electrical fires

In a separate meeting, it was said in the discussion that NEMA is enabled to help in the development and sponsorship on webinars about the necessary fundamentals, benefits, and some limitations on the PoE installed systems.

Lamp Index by NEMA Currently Adjusts to the Newly Available A-Line LED Data

The general service (A-line) lamps have a newer take on its look according to the NEMA Lamp Index. When this said lamp was first produced and innovated last 2012 (together with its developments) it was intended to be used to measure the shift in general service (A-line) lamp technology. This came about as a result of the recent implementation of Energy Independence and Security Act of 2007 (EISA-2007). This served as a guideline for different manufacturers to shy away from the incandescent lamp that consumes a lot more technology. Halogen incandescent lamp consumed 28% than the incandescent counter parts.

During this time, the only innovation and technology considered as general service lamp available in the market was compact fluorescent lamp (CFL). With this in mind, this LED lamp was barely available in the market last 2012 because it was introduced in the market with $60 price point.

However, the market scenario quickly changed. Towards the end of 2015, the traditional incandescent lamps were almost phased out from the market shelves and the manufacturers of lamps almost no longer carry incandescent lamps for shipment because of the regulation EISA-2007. Because of ongoing demand and decreasing supply, LED lamps became affordable for the consumers and sales started picking up for the first time.

In line with this market scenario, Lamp Index showed a reasonable current direction of the A-line shipments since its first development way-back 2012. In the recent two calendar years, the said lamp shipment rates quickly grew and the LED lamp shipments significantly took the majority of the actual share of the LED light shipments. This is because there is a significant volume of orders from non-MEMA-member improts.

Usually, NEMA will be confidently trust on its strength to make use of this difference – as with the recent market changes with halogen and CFL bulbs – according to historical data. However this information about the A-line LED bulbs are not ready because of its drastic changes when it first entered the market.

Last 2017, the United States government took on the initiative of publishing data of A-line LED lamp imports for its domestic consumption in the country. This data was also published with other information that empowered NEMA to measure the shipments for the A-line LED lamps. Together with the consistency of the numbers and what the consumers are currently experiencing with the A-line LED lamps, it can be said that this lamp effectively entered the market efficiently.

Incandescent shipments included a relatively small number of low lumen lamps (15W, 25W) outside of this lumen range because of the way NEMA historically collected incandescent lamp data prior to 2012.

In conclusion, the adjustment of the newly available A-line lamps and the LED data available, made NEMA discontinue the ongoing reporting of incandescent A-line lamps in the lamp index. When NEMA published the first lamp index, originally it was intended to show the data about the shipments of A-line lamps with the lumen rage of 310-2600 lumens. With this data, it can be said that the incandescent shipments that were included showed a relatively small amount of total shipments. The incandescent lamps were classified by having low lumen lamps (15W, 25W) and it is outside of its lumen rage. This is because of the way NEMA collected historical data of incandescent lamps before the year 2012.

4 Effective Ways on Achieving Successful Skid Integration in Batching Operations

Four major guidelines for having a successful skid integration when it comes to batching operations 

The integration of the kid equipment in OEM in the overall batch management system will be requiring a clear and specified level of coordination. This coordination should come between the salve and master (DCS or SCADA) systems. The simplistic command set the slave system that does not give the provision for visual representation of the whole system. Once everything is working perfectly fine, a simple command from the master to the slave system is already sufficient to make everything work. However, there is an exemption to this rule. Once the exception condition is bound to happen, it is going to be very hard to determine or troubleshoot without the need to go out to the equipment’s HMI. This is the local human-machine interface to identify the issue. 

With this in mind, this kind of interference can increase the batch cycle time, can lessen the equipment utilization and it can decrease the overall efficiency of the operations. The only solution to this dilemma is to combine a slave OEM system inside the overall master processing system by following these four simple guidelines: 

Distribute the operating modes 

Standard operating states should be followed 

Identify the status feedback definition 

Have communications standardized 

The only thing that can solve this problem is to have tow different pieces of the equipment synchronized by identifying the agreed methodological set of interactions. The flexible batch solution should have an isolation happening between different set of functions. 

1. Distribute the operating modes 

The different operating modes of the remote equipment is a little bit complicated because the boundaries are not well defined. Should an operator implement changes to the local equipment once the controlled variables have been given instructions remotely coming from an overall recipe? Is the recipe will go to the “hold” state when a specified operating status is bound to change? These are the sample few questions that has to be considered when remote systems are to be integrated. The operating philosophy and interface should over rule. This happens between the master and the salve system and should be identified to continually give a uniformed interface between two different systems. 

2. Standard operating states should be followed 

Standard operating states should be followed to enable a mechanism to handle the hardest part of a batch. With this in mind, this is the exception condition. This is identified as a mechanism behavior that exists in the outside of the usual normal or desired behavior of the system process. The critical elements of the batch production includes the handling, processing, and recovering from these types of systematic operations.  

4 Effective Ways on Achieving Successful Skid Integration in Batching Operations Part 3

  1. Engineers Should Define the Status Feedback

Status feedback is part of many things, but it is an essential part of operations to make it more efficient and is between two systems. The information structured for status feedback is constructed for different modes, error in conditions, and operating states as well. The representation of a status feedback presented through standard modes and states are popular among all equipment but there is one catch. Every error in conditions should be specific to each equipment. The information specific to the equipment will better provide the engineers of a better view for the error in the condition of the machine. The information transmitted from a machine can also help the engineers prevent any further damage of the equipment and this will help them utilize it even better. This will contribute to overall efficiency of the whole operating system.

2. Status Feedbacks help in the standardization of communication status

The communication between different systems are attainable in a very good and efficient manner by using the single integer value designations in status feedback. The communication that are happening can be very simple and just by using one word as a command. The word is transmitted to the slave system and this in return gives them a status that comes from the slave system. In addition to this, there should be additional parameters or variables in the system that needs to be written and programmed to the programmable logic controller (PLC) that can result to the overall recipe setting in the main system of the status feedback. Having a good standard on different communication types of remote or 3rd party equipment makes the system feedback more controllable. Because this can be easily maintained and extended over the life-cycle. The different development of several communication standards for remote interfaces should be designed wide enough to be able to fit into different application types, but specific enough to show and display value.

The final solution

The different integration of slave or remote systems can be quite challenging for many engineers. However, the standardization of its’ interfaces can make this process easy to manage. The last two of the four guidelines discussed in this article are clearly set by the ISA 288.01 standards. The status feedback and the communication packaging between different systems can have meaning to cover all the 3rd party solutions. The common interface design between systems can have a unison design that can make the coordination more efficient across several systems. Which makes it to be more easy to maintain and easier to expand. The different integration of these kind of systems (slave or remote systems) is hard for many engineers. With this in mind, the interface’s standardization can make this process easier to manage.

Lastly, the common interface solutions should be well documented in a design that is deliverable. The design should be standardized by the User Requirement Specification (URS) to OEM to meet manufacturing standards. In this way the programming of the remote system is ensured to meet expected quality standards.