Systems and methods for high-speed falling conductor protection in electric transmission systems

Systems, methods, and computer-readable media are disclosed for high-speed falling conductor protection in electric distribution systems. An example method may include calculating, by a processor, at a first time, and for each phase, one or more first impedance values associated with one or more terminals of a transmission line. The example method may also include calculating, by the processor, at a second time, and for each phase, one or more second impedance values associated with the one or more terminals. The example method may also include determining, by the processor, that a rate of change of an impedance of the one or more terminals is greater than a threshold rate of change. The example method may also include determining, by the processor and based on the determination that the rate of change of the one or more terminals is greater than the threshold rate of change, that the transmission line has broken. The example method may also include sending, by the processor and based on the determination that the transmission line has broken, a signal to de-energize the transmission line before a broken conductor reaches a ground surface.

FIELD OF DISCLOSURE

The present disclosure is related to power transmission, and more particularly to systems and methods for high-speed falling conductor detection (FCD) or falling conductor protection (FCP) in electric transmission systems.

BACKGROUND

An energized overhead power line can break and fall to the ground or other objects for a variety of reasons such as severe weather conditions, natural disasters, conductor clamp failures, tree fall and/or pole knock-overs. When the falling conductor touches the earth or other grounded objects, it may cause a high-impedance (High-Z) fault which may not be reliably detected by conventional overcurrent protection schemes. Moreover, as the live conductor contacts the ground, the conductor may produce electrical arcing, which can ignite flammable materials or vegetation and start a fire. An undetected High-Z fault is a risk to people and their properties as well as having a potential to evolve into a full-blown fault. Most of the conventional methods are not able to detect all High-Z faults, and operation of the relay for downed conductor faults is not guaranteed. In addition, for the broken or falling conductors, it is expected to detect the condition and trip the corresponding breaker(s) before the conductor touches the ground. Currently, conventional methods for detection of broken falling conductors use electric currents, voltages, and conductor geometry.

DETAILED DESCRIPTION

Overview

This disclosure relates to, among other things, systems, methods, computer-readable media, techniques, and methodologies for high-speed falling conductor detection in electric transmission systems. The algorithm described herein may address the challenges associated with broken conductor detection for two- and three-terminal transmission lines using data received from other end(s) of the transmission line (for example, data, such as voltage and/or current data exchanged between intelligent relays associated with the transmission line). While the descriptions provided herein may be specific to two- and three-terminal transmission lines, similar methods may be applicable to transmission lines with any other number of terminals as well. To ensure that the most updated data is used for detection purposes, the algorithm described herein may also ensure that the data exchanged between relays and/or a centralized controller (described in further detail below) is time synchronized and up-to-date. Additionally, since during a broken conductor scenario a transmission line conductor may typically only take between one and two seconds to hit the ground, the algorithm described herein may be capable of detecting a falling transmission line conductor scenario and de-energize the impacted circuit even prior to the broken conductor reaching the ground (for example, as quickly as about 500 ms after the conductor breaks).

More particularly, the algorithm described herein may represent a transmission falling conductor protection (TFCP) algorithm that may use an impedance change ratio (ICR) based on transmission line impedance(s). The TFCP function may identify a falling conductor condition when the rate of change of impedance for the transmission line exceeds a threshold (which may be at about 15 times the normal value, or any other value). In some cases, the algorithm may be used to detect single-phase broken/open conductors (however, multi-phase broken/open conductors may also be detected in some cases as well). To prevent incorrect operation of the TFCP for a fault happening on the transmission line, a high current threshold may be used to block the TFCP logic if the line current exceeds a predefined value (which may be defaulted at about 1.2 pu, or any other value). The TFCP logic may also be blocked when the phase voltage is outside a pre-defined range at all line terminals, indicating other abnormal scenarios than a broken falling conductor. More specific details relating to the logic of the algorithm may be provided in the description associated withFIG.4. The transmission line relays may exchange the voltage and current data associated with local and remote line terminals with each other, either via an existing line differential channel or a separate communication medium.

The algorithm may provide more sensitivity in detecting broken falling conductors, when compared to traditional methods for detecting broken falling conductors. Based on the availability of the data, this algorithm may calculate the rate of change of phase impedances, or virtual positive-sequence impedance, and/or virtual Clarke impedance of the line to detect broken conductors on two- or three-terminal transmission lines. Where virtual positive-sequence impedance is defined as the impedance calculated using phase currents and positive-sequence voltage; and virtual Clarke impedance is defined as the impedance calculated using phase currents and Clarke voltage.

The algorithm may include different configurations that may be implemented depending on the type of the data that is captured in a given transmission line system. That is, certain transmission line systems may already be configured to capture certain types of data, and the algorithm may account for this by being able to switch between different configurations that are able to use particular data that is already captured by the given transmission line system. For example, one configuration may be implemented in transmission line systems that capture Clark voltage data. A second configuration may involve a transmission line system that captures positive-sequence voltage data. A third configuration may involve a transmission line system that captures synchrophasor data. The main difference between the third configuration and the two previous configurations may be that the synchrophasor data may not be exchanged between the relays. Instead, the data may be directly streamed to a real-time controller or Phasor Data Concentrator (PDC) to be processed. Consequently, this configuration may require a separate communication channel in addition to the direct differential link that exists between the relays.

The algorithm described herein may provide a number of aspects over conventional methods for quickly detecting broken conductor in transmission lines. First, the algorithm is immune to existing system imbalance and transient events since it is using the ICR over a period of time. Second, the algorithm can work based on available voltage of the remote end of the line. Third, the algorithm can operate within existing transmission line systems that capture different types of data, such as synchrophasor data, positive-sequence voltages, and extended Clarke voltages. Fourth, the algorithm may be implemented using the existing line differential relays. Alternatively, a real-time controller can easily be added to the system to perform centralized processing as well. Fifth, the algorithm may support any number of terminal transmission lines. The proposed method may also be vendor agnostic since all vendors offer multi-ended fault location in their line differential relays and hence communicate voltage values between the relays using C37.94 protocol. The proposed algorithm may also be future proof since it is capable of using PMU data which many system operators have started deploying (similarly, a vendor agnostic approach using standard communication protocols). The algorithm can detect and isolate the broken conductor circuit within about 500 ms, well before the conductor hits the ground. If modifications to the existing relays are not cost effective, adding one real-time controller can cover multiple transmission lines depending on placement and type of available data.

Turning to the figures,FIG.1is a schematic diagram of an example system100, in accordance with one or more example embodiments of the disclosure. The system100may include a transmission line101including two or more terminals. For example, the particular transmission line101illustrated in the figure may include three terminals (a first terminal102, a second terminal104, and/or a third terminal106). AlthoughFIG.1depicts a system100with three terminals, as mentioned above, the algorithm described herein may similarly apply to a two-terminal system, as well as a system including any other number of terminals as well. Each of the terminals in the system100may include at least an intelligent electronic device (IED) (for example, IED120, IED122, and/or IED124), such as a relay. Additionally, each terminal of the transmission line101may be associated with a line impedance (for example, line impedance114, line impedance116, and/or line impedance118). Furthermore, the system100may also include a real-time controller128, which may be a centralized controller that may process data received from any of the IEDs. However, the IEDs may also individually, or combined, be able to perform any of the processing as well.

FIG.2is a schematic illustration of another example system200, in accordance with one or more example embodiments of the disclosure. The system200may be the same as the system100, however, instead of the IEDs sharing data between one another, the IEDs in the system200may instead provide data directly to the real-time controller228for processing. In some cases, this configuration may be applicable when synchrophasor data is used in a transmission line system, however, this configuration may also be used for other types of transmission line systems as well.

FIG.3is a schematic illustration of an example falling conductor protection system300in accordance with one or more example embodiments of the disclosure.

As shown inFIG.3, the falling conductor protection system300may include one or more IEDs321(1), . . . ,321(N) (e.g., the IEDs120-124ofFIG.1or220-224ofFIG.2), a falling conductor protection controller340(e.g., the controller104ofFIG.1), and one or more monitoring and computing devices380.

In an illustrative configuration, an IED may be a protective device configured to measure impedance values of overhead lines. In that case, a distributed architecture may be implemented without a need to an additional real-time controller, when IEDs are time-coordinated with proper margin. Alternatively, an IED may stream out one or more phasor measurements (also referred to as synchrophasor) that may estimate the magnitude and phase angle of an electrical phasor quantity (such as voltage or current) in the overhead lines using a common time source for synchronization, and may also determine the impedance values using the phasor measurements. Examples of an IED may also include a phasor measurement unit (PMU) and/or any suitable device that performs the impedance and/or phasor measurements. The falling conductor protection system300may detect broken conductor conditions for multiple lines. In some embodiments, as shown inFIG.3, the falling conductor protection system300may further include two or more IEDs per line, e.g., IEDs321(1), . . . ,321(N).

The falling conductor protection controller340(also referred to as controller340) may be configured to communicate with two or more IEDs321, and the one or more monitoring and computing devices380. The controller340may be any type of computing devices, such as, but not limited to, real-time computing devices, real-time gateway devices, computers, and/or servers. The controller340may include one or more servers, perhaps arranged in a cluster, as a server farm, or as individual servers not associated with one another.

The controller340may include at least a memory350and one or more processing units (or processors)342. The processors342may be implemented as appropriate in hardware, software, firmware, or combinations thereof. Software or firmware implementations of the processors342may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described (e.g., in real time).

The memory350may store program instructions that are loadable and executable on the processors342, as well as data generated during the execution of these programs. Depending on the configuration and type of the controller340, the memory350may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.). The controller340or server may also include additional removable storage348and/or non-removable storage352including, but not limited to, magnetic storage, optical disks, and/or tape storage. The disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computing devices. In some implementations, the memory350may include multiple different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), or ROM.

The memory350, the removable storage348, and the non-removable storage352may be all examples of computer-readable storage media. For example, computer-readable storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for the storage of information such as computer-readable instructions, data structures, program modules, or other data. The memory350, the removable storage348, and the non-removable storage352may be all examples of computer storage media. Additional types of computer storage media that may be present include, but are not limited to, programmable random access memory (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the controller340or other computing devices. Combinations of any of the above should also be included within the scope of computer-readable media.

Alternatively, computer-readable communication media may include computer-readable instructions, program modules, or other data transmitted within a data signal, such as a carrier wave, or other transmissions. However, as used herein, computer-readable storage media does not include computer-readable communication media.

The controller340may also contain communication connection(s)372that allows the controller340to communicate with a stored database371, another computing/storage device or server, user terminals, the IEDs321, the computing devices380, and/or other devices on the communication network330. The controller340may also include input device(s)344such as a keyboard, a mouse, a pen, a voice input device, a touch input device, etc., and output device(s)346, such as a display, speakers, printers, etc.

Turning to the contents of the memory350in more detail, the memory350may include an operating system354and one or more application programs or services for implementing the features disclosed herein, including, for example, the falling conductor protection module360and/or the alarm/command generator370. The falling conductor protection module360and/or the alarm/command generator370may be executed to perform any of the operations described herein (for example, operations described with respect toFIGS.4-6and9).

FIG.4is a schematic diagram of an example flow diagram400, in accordance with one or more example embodiments of the disclosure. Particularly, the flow diagram400may depict example logic that may be used to perform falling conductor protection in transmission systems as described herein (for example, by using extended Clarke voltage, positive-sequence voltage, and/or synchrophasor data). It should be noted that flow diagram400may illustrate logic specific to a three-terminal line. The logic used for a two-terminal line may be similar to the logic presented in the flow diagram400, but may not include the third terminal. In other words, a two-terminal line may be a reduced version of the three-terminal line. Although not depicted in the figure, this logic for a two-terminal line may also be described in further detail below as well. In flow diagram400, Va, Vb, and Vc may be voltage synchrophasors, V1 may be a positive-sequence voltage, and Vcl may be an extended Clarke voltage. Variables included in the Equations described below may be defined in Table 1.

In some embodiments, the flow diagram400may initiate at block408with data being obtained from two or more relays (for example, IEDs) in the transmission line system. For example, data may be obtained from a first relay402, a second relay404, a third relay406, and/or any other number of relays. Once the data is obtained from the two or more relays, block410of the flow diagram400may involve line impedance calculations. Line protection relays may normally offer multi-ended fault location features, which may require the voltages of the line terminals be exchanged over a direct differential communication channel. As a result, the local voltages may be communicated to the remote line terminal through a direct communication channel (for example, using the IEEE C37.94 standard). The high-speed falling conductor protection described herein uses the existing communicated data between line differential relays to detect a broken/falling conductor. For a three-terminal line, two impedances may be calculated for each phase of the line at each terminal (for example, impedances between the local terminal and two remote terminals). As a result, there may be a total of six and eighteen impedance calculations for a two-terminal and three-terminal lines, respectively.

As mentioned earlier, for a three-terminal line, two impedances may be calculated for each phase of the system at each line terminal.FIG.6may depict of a three-terminal transmission line which may be used to derive the following equations.

The two impedances calculated for each phase of the line at each line terminal use the voltage and current values from the local terminal and the other two remote terminals. The following equations show the derivation of line impedances at one terminal of the line:

Vy,j-Vx,j=(Iy,k-Vy,j⁢Yy2)⁢Zy-(Ix,k-Vx,j⁢Yx2)⁢Zx(Equation⁢1)Vz,j-Vx,j=(IZ,k-Vz,j⁢Yz2)⁢Zz-(Ix,k-Vx,j⁢Yx2)⁢Zx(Equation⁢2)
where k may represent the phase of the line and would take a, b, and c; and index j may represent the type of available voltage data. For example, the index j in any other variables included in Equations 1 and 2 (as well as any other equation described herein) may change depending on the type of data being captured by the relays (as described above, different transmission line systems may capture different types of data). For example, “a,” “b,” and “c” may be used in place of the index j for synchrophasor data (phase impedance), “1” may be used in place of the index j for positive-sequence voltage (virtual positive-sequence impedance), and “cl” may be used in place of the index j for extended Clarke voltage (virtual Clarke impedance). For terminal X, impedance ratios for different line sections may be defined as:

Substituting Equations 3 and 4 into Equations 1 and 2, the following relationships may be obtained:

Then, for the extended Clarke voltage, the virtual Clarke impedances may be defined at terminal X for various line sections, as shown below (with Equations 7 and 8 representing phase a, Equations 9 and 10 representing phase b, and Equations 11 and 12 representing phase c):

It should be borne in mind the exact impedance calculation may not be necessary for falling conductor detection. However, it may be important to detect the rate of change of impedance for the affected section of the line in order to de-energize the broken line selectively.

The equations presented for calculation of three-terminal line impedances may also be used for two-terminal line with small modifications. Since the Terminal Z does not exist for a two-terminal line, only one impedance may be calculated for each phase at each terminal. Moreover, the length ratio is eliminated from the equations.FIG.7shows a simplified PI model for a two-terminal line which may be used to derive the equations.

The following equations are used to calculate the line impedance for a two-terminal line at a local terminal (Terminal X).

Once the line impedances are calculated, the impedance change ratio of the transmission line (δZ) may be derived by subtracting the previous impedance Z′ (Z′=Zt0-n) from the current impedance Z (Zt0) and then divided by previous impedance Z′, as follows:

Taking Phase ‘a’ at Terminal X of a three-terminal line as an example, the impedance change ratios (δzxy,aand δzxz,a) may be calculated using the following formula (other phases impedance change ratios are calculated similarly):

In some embodiments, once the impedance calculations are performed in block410, broken conductor detection may be performed at block412. The TFCP function may identify a falling conductor condition when the rate of change of impedance for the transmission line exceeds a threshold (which may be at about 15 times the normal value, or any other value). In some cases, the algorithm may be used to detect single-phase broken/open conductors (however, multi-phase broken/open conductors may also be detected in some cases as well). To prevent incorrect operation of the TFCP for a fault happening on the transmission line, a high current threshold may be used to block the TFCP logic if the line current exceeds a predefined value (which may be defaulted at about 1.2 pu, or any other value). Additional details about the broken conductor detection performed in block412may be described with respect toFIG.6.

FIG.5is a schematic diagram of an example flow diagram500, in accordance with one or more example embodiments of the disclosure. In some embodiments, the flow diagram500may correspond to the falling conductor protection block ofFIG.4. The flow diagram500may begin with operation502. Operation502may involve performing one or more impedance calculations. Following operation502, the flow diagram500may proceed to operation504. Operation504may involve performing an ICR calculation (for example, calculations described with respect toFIG.4or otherwise herein). In some cases, the ICR calculation may be performed between the latest and third values (or any other value in the buffer) in the moving buffer. The flow diagram500may then proceed to condition506. Condition506may involve determining if a change in impedance exceeds a threshold value. If the change in impedance does exceed the threshold value, the flow diagram500may proceed to condition508. Otherwise, the flow diagram500may return to operation502. Additionally, if the change in impedance exceeds the threshold value, then the flow diagram500may also proceed to operation510. Condition508may involve determining if an external loss of phase is detected. External loss of phase may be detected if that phase is de-energized at all terminals of the line. This may mean that an upstream/out of protection zone incident has de-energized the phase. Operation510may involve freezing a copy of the buffer. The actual buffer may still be receiving data and updating itself during this time. The frozen copy of the buffer provides a snapshot of the time at which the change in impedance exceeded the threshold value.

If an external loss of phase is not detected in condition508, then the flow diagram500may proceed to condition512. Condition512may involve determining if there is more than one phase picked up after a given period of time (for example, about 150 ms or any other amount of time). In some cases, if the ICR of more than one phase is above the threshold, it may need to be determined which phase is actually broken. For example, if a broken conductor happens in phase a, the impedance measured for phase b may change and the ICR may go above the threshold. In this situation, the phase that actually has a broken conductor need to be distinguished from the phase that has experienced a fake change of impedance because of the broken conductor on the other phase. If it is determined that there is not more than one phase picked up, then the flow diagram500may proceed to condition516. However, if it is determined that more than one phase is picked up, then the flow diagram500may proceed to condition514.

Condition514may involve performing change in impedance supervision. The phase with an ICR more than a given value greater than the ICR of the other phase may be selected as the phase that actually has the broken conductor. For example, if the threshold value is five, and the ICR of phase a is 16 and the ICR of phase b is 200, then 200 divided by 16 is greater than five and phase b may be selected as the broken phase since its impedance change is significant.

Condition516may involve performing current supervision. If condition516is met, then the flow diagram500may proceed to condition518. If condition516is not met, the flow diagram500may proceed back to condition514. Condition518may involve performing a final change in impedance check. The final impedance check may involve comparing the latest sample in the moving buffer with the oldest sample in the frozen buffer, which may be the impedance value before the break in the conductor. If condition518is met, then at operation520, it may be determined that a broken conductor condition is met.

FIG.8is an example process flow diagram of an illustrative method800for impedance-based broken conductor detection for a two-terminal transmission line in accordance with one or more example embodiments of the disclosure. The method800may also be applicable of transmission lines including any other number of terminals as well. InFIG.8, computer-executable instructions of one or more module(s) (e.g., the controller128/340) of the falling conductor protection system100/300may be executed to perform falling conductor detection and protection. At block802, the method800may include calculating, by a processor, at a first time, and for each phase, one or more first impedance values associated with one or more terminals of a transmission line. At block804, the method800may include calculating, by the processor, at a second time, and for each phase, one or more second impedance values associated with the one or more terminals. At block806, the method800may include determining, by the processor, that a rate of change of an impedance of the one or more terminals is greater than a threshold rate of change. At block808, the method800may include determining, by the processor and based on the determination that the rate of change of the one or more terminals is greater than the threshold rate of change, that the transmission line has broken. At block810, the method800may include sending, by the processor and based on the determination that the transmission line has broken, a signal to de-energize the transmission line before a broken conductor reaches a ground surface.

The operations described and depicted in the illustrative process flow ofFIG.8may be carried out or performed in any suitable order as desired in various example embodiments of the disclosure. Additionally, in certain example embodiments, at least a portion of the operations may be carried out in parallel. Furthermore, in certain example embodiments, less, more, or different operations than those depicted inFIG.8may be performed.

One or more operations of the process flow ofFIG.8may have been described above as being performed by a user device, or more specifically, by one or more program modules, applications, or the like executing on a device. It should be appreciated, however, that any of the operations of process flow ofFIG.8may be performed, at least in part, in a distributed manner by one or more other devices, or more specifically, by one or more program modules, applications, or the like executing on such devices. In addition, it should be appreciated that processing performed in response to execution of computer-executable instructions provided as part of an application, program module, or the like may be interchangeably described herein as being performed by the application or the program module itself or by a device on which the application, program module, or the like is executing. While the operations of the process flow ofFIG.8may be described in the context of the illustrative broken conductor detection controller, it should be appreciated that such operations may be implemented in connection with numerous other device configurations.

FIG.9is a block diagram of an example of a machine or system900for falling conductor protection in accordance with one or more example embodiments of the disclosure.

In other embodiments, the machine900may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine900may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine900may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments. The machine900may be a server (e.g., a real-time server), a computer, an automation controller, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (Saas), or other computer cluster configurations.

The machine (e.g., computer system)900may include a hardware processor902(e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory904and a static memory906, some or all of which may communicate with each other via an interlink (e.g., bus)908. The machine900may further include a power management device932, a graphics display device910, an input device912(e.g., a keyboard), and a user interface (UI) navigation device914(e.g., a mouse). In an example, the graphics display device910, input device912, and UI navigation device914may be a touch screen display. The machine900may additionally include a storage device (i.e., drive unit)916, a signal generation device918(e.g., an emitter, a speaker), a falling conductor protection device919, a network interface device/transceiver920coupled to antenna(s)930, and one or more sensors928, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine900may include an output controller934, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).

The storage device916may include a machine readable medium922on which is stored one or more sets of data structures or instructions924(e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions924may also reside, completely or at least partially, within the main memory904, within the static memory906, or within the hardware processor902during execution thereof by the machine900. In an example, one or any combination of the hardware processor902, the main memory904, the static memory906, or the storage device916may constitute machine-readable media.

The falling conductor protection device919may carry out or perform any of the operations and processes (e.g., the flow diagrams400-500ofFIGS.4-5and/or the method800ofFIG.8) described above. The falling conductor protection device919may be one embodiment of the controller128/340.

Although specific embodiments of the disclosure have been described, numerous other modifications and alternative embodiments are within the scope of the disclosure. For example, any of the functionality described with respect to a particular device or component may be performed by another device or component. Further, while specific device characteristics have been described, embodiments of the disclosure may relate to numerous other device characteristics. Further, although embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the embodiments. Conditional language, such as, among others, “can,” “could.” “might.” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments could include, while other embodiments may not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements, and/or steps are in any way required for one or more embodiments.

Other examples of programming languages include, but are not limited to, a macro language, a shell or command language, a job control language, a script language, a database task or search language, or a report writing language. In one or more example embodiments, a software component comprising instructions in one of the foregoing examples of programming languages may be executed directly by an operating system or other software component without having to be first transformed into another form.