Home
What's new
Latest activity
Authors
Store
Latest reviews
Search products
Forums
New posts
Search forums
What's new
New posts
New listings
New products
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
Cart
Cart
Loading…
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Change style
Contact us
Close Menu
Forums
SVTPerformance's Chain of Restaurants
Road Side Pub
Gas Prices After The Cyber Attack (by Russia?)
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="JPKII" data-source="post: 16619013" data-attributes="member: 12867"><p>I've had many battle-royal with corporate IT types about how to integrate an industrial process into their corporate network. For many reasons, even beyond security. Almost all industrial devices these days (PLC's, VFDs, DC Drives, Sensors) communicate via Ethernet IP. Commingling of industrial and corporate networks is where folks botch the design. These two discrete networks need physical separation. Where the PLC or automation system needs to feed data into an upstream business system, there are good ways to do this without physically crossing the networks. Sadly most traditionally trained IT folks have no clue what is needed on the industrial side and, conversely, most industrial or automation engineers have no clue what is needed on the corporate side. Trying to convince a corporate IT guy that I need a range of static IP addresses on their network is nearly as bad as arguing with a liberal that there are only 2 genders.</p></blockquote><p></p>
[QUOTE="JPKII, post: 16619013, member: 12867"] I've had many battle-royal with corporate IT types about how to integrate an industrial process into their corporate network. For many reasons, even beyond security. Almost all industrial devices these days (PLC's, VFDs, DC Drives, Sensors) communicate via Ethernet IP. Commingling of industrial and corporate networks is where folks botch the design. These two discrete networks need physical separation. Where the PLC or automation system needs to feed data into an upstream business system, there are good ways to do this without physically crossing the networks. Sadly most traditionally trained IT folks have no clue what is needed on the industrial side and, conversely, most industrial or automation engineers have no clue what is needed on the corporate side. Trying to convince a corporate IT guy that I need a range of static IP addresses on their network is nearly as bad as arguing with a liberal that there are only 2 genders. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
SVTPerformance's Chain of Restaurants
Road Side Pub
Gas Prices After The Cyber Attack (by Russia?)
Top