Abstract: Included are embodiments for ReNAT communications address communications. Some embodiments include a network operations center (NOC) that includes a ReNAT twin NAT that translates between a customer-assigned private IP address and a unique private IP (UPIP) address. The NOC may additionally include a ReNAT VPN component coupled to the ReNAT twin NAT, where the ReNAT VPN provides a source IP address to the ReNat twin NAT. The NOC may include logic that when executed by a processor, causes the processor to facilitate communication between a user workstation on a private network and a remote computing device, wherein facilitating communication includes receiving the data from the user workstation via a traditional VPN portal, wherein address translation has been performed by a ReNAT twin NAT client on the user workstation.

Abstract: Included are embodiments for ReNAT communications address communications. Some embodiments include a network operations center (NOC) that includes a ReNAT twin NAT that translates between a customer-assigned private IP address and a unique private IP (UPIP) address. The NOC may additionally include a ReNAT VPN component coupled to the ReNAT twin NAT, where the ReNAT VPN provides a source IP address to the ReNat twin NAT. The NOC may include logic that when executed by a processor, causes the processor to facilitate communication between a user workstation on a private network and a remote computing device, wherein facilitating communication includes receiving the data from the user workstation via a traditional VPN portal, wherein address translation has been performed by a ReNAT twin NAT client on the user workstation.

Abstract: Included are embodiments for ReNAT communications address communications. Some embodiments include a network operations center (NOC) that includes a ReNAT twin NAT that translates between a customer-assigned private IP address and a unique private IP (UPIP) address. The NOC may additionally include a ReNAT VPN component coupled to the ReNAT twin NAT, where the ReNAT VPN provides a source IP address to the ReNat twin NAT. The NOC may include logic that when executed by a processor, causes the processor to facilitate communication between a user workstation on a private network and a remote computing device, wherein facilitating communication includes receiving the data from the user workstation via a traditional VPN portal, wherein address translation has been performed by a ReNAT twin NAT client on the user workstation.

Abstract: Included are embodiments for ReNAT communications address communications. Some embodiments include a network operations center (NOC) that includes a ReNAT twin NAT that translates between a customer-assigned private IP address and a unique private IP (UPIP) address. The NOC may additionally include a ReNAT VPN component coupled to the ReNAT twin NAT, where the ReNAT VPN provides a source IP address to the ReNat twin NAT. The NOC may include logic that when executed by a processor, causes the processor to facilitate communication between a user workstation on a private network and a remote computing device, wherein facilitating communication includes receiving the data from the user workstation via a traditional VPN portal, wherein address translation has been performed by a ReNAT twin NAT client on the user workstation.

Abstract: Included are systems and methods for providing a ReNAT virtual private network (VPN). Accordingly, some embodiments include receiving, at a network operations center (NOC), external packets from a client workstation on a private network and providing source addressing for the external packets to identify the private network from where the external packets were received. Similarly, some embodiments include receiving data from the external packets from a ReNAT twin NAT, where the ReNAT twin NAT includes both a destination public address and a public source address for the data and decrypting the data and forwarding the data with the public source address to the ReNAT twin NAT. In some embodiments the NOC provides a virtual private network within the NOC for facilitating communication of the data between a remote computing device across a wide area network and the client workstation in the private network.

Abstract: Included are systems and methods for providing dual network address translation. Accordingly, some embodiments include translating, via a processor at a network operations center (NOC), a public source address and a public destination address to and from assigned unique private addresses for data to be communicated across a wide area network, while including gateway functions to manage an application with an imbedded IP address. Some embodiments include communicating, via the processor at the NOC, the data to a ReNAT virtual private network (VPN) with packets wrapped in a private ReNAT defined protocol that includes the public source address and the public destination address. Still some embodiments include mapping, via the processor at the NOC, a unique private address in the data to customer defined private IP addresses.

Abstract: Included are systems and methods for providing dual network address translation. Accordingly, some embodiments include translating, via a processor at a network operations center (NOC), a public source address and a public destination address to and from assigned unique private addresses for data to be communicated across a wide area network, while including gateway functions to manage an application with an imbedded IP address. Some embodiments include communicating, via the processor at the NOC, the data to a ReNAT virtual private network (VPN) with packets wrapped in a private ReNAT defined protocol that includes the public source address and the public destination address. Still some embodiments include mapping, via the processor at the NOC, a unique private address in the data to customer defined private IP addresses.

Abstract: Included are embodiments for ReNAT communications address communications. Some embodiments include a network operations center (NOC) that includes a ReNAT twin NAT that translates between a customer-assigned private IP address and a unique private IP (UPIP) address. The NOC may additionally include a ReNAT VPN component coupled to the ReNAT twin NAT, where the ReNAT VPN provides a source IP address to the ReNat twin NAT. The NOC may include logic that when executed by a processor, causes the processor to facilitate communication between a user workstation on a private network and a remote computing device, wherein facilitating communication includes receiving the data from the user workstation via a traditional VPN portal, wherein address translation has been performed by a ReNAT twin NAT client on the user workstation.

Abstract: Included are systems and methods for providing a ReNAT virtual private network (VPN). Accordingly, some embodiments include receiving, at a network operations center (NOC), external packets from a client workstation on a private network and providing source addressing for the external packets to identify the private network from where the external packets were received. Similarly, some embodiments include receiving data from the external packets from a ReNAT twin NAT, where the ReNAT twin NAT includes both a destination public address and a public source address for the data and decrypting the data and forwarding the data with the public source address to the ReNAT twin NAT. In some embodiments the NOC provides a virtual private network within the NOC for facilitating communication of the data between a remote computing device across a wide area network and the client workstation in the private network.

Abstract: Systems and methods are presented for automated induction hardening of crankshaft bearings while controlling the crankshaft TIR, in which one or more first bearings are hardened by induction heating and quenching, followed by measurement of the crankshaft TIR. The measured TIR is then evaluated and one or more second bearings are hardened using a second induction heating power profile and a second quench flow profile, at least one of which is selectively adjusted according to the measured crankshaft TIR. In this manner, the hardening of the second bearing(s) can counteract any bending or warpage caused by the first hardening process to control the resulting final TIR of the crankshaft.

Abstract: An apparatus and method for hardening the concentric main bearing surfaces and orbital pin bearing surfaces of a crankshaft for an internal combustion engine. The apparatus includes an inductor that is connected to a high frequency power source with a power controller to cause the power source to direct a given power to the inductor at given rotational heating positions of the crankshaft. A master controller creates output signals to control the power controller. The apparatus and method includes a first multi-surface hardening station with inductors for all of the main bearing surfaces, a second multi-surface hardening station with inductors for some of the orbital pins and a third multi-surface hardening station with inductors for the remaining orbital pins. Total indicator run out (TIR) is measured after the first station to adjust the heating process in the third station to produce a straight crankshaft.

Abstract: An apparatus and method for hardening the concentric main bearing surfaces and orbital pin bearing surfaces of a crankshaft for an internal combustion engine rotatable about the common center axis of the main bearing surfaces. The apparatus comprising an inductor for encircling each one of the surfaces to be hardened over at least a portion of the surface and riding on the surface where the inductors are connected to a high frequency power source with a power controller to cause the power source to direct a given power to the inductor at given rotational heating positions of the crankshaft. A quench chamber is associated with the inductor and has outlet orifices directed toward the surface encircled by the inductor. A supply of quenching liquid with a flow controller directs a given quantity of quench liquid against the surface after the surface has been inductively heated by the inductor.

Abstract: Systems and methods are presented for automated induction hardening of crankshaft bearings while controlling the crankshaft TIR, in which one or more first bearings are hardened by induction heating and quenching, followed by measurement of the crankshaft TIR. The measured TIR is then evaluated and one or more second bearings are hardened using a second induction heating power profile and a second quench flow profile, at least one of which is selectively adjusted according to the measured crankshaft TIR. In this manner, the hardening of the second bearing(s) can counteract any bending or warpage caused by the first hardening process to control the resulting final TIR of the crankshaft.