The IOT Geoff is referring to is the IOT (Immediate OuTput) instruction in a Logix processor, not "Internet of Things"
To map your prox, you just map it into one of the bits of a DINT. Let's say you're going to produce 10 DINT's, with one of them being reserved for Boolean data like your prox signal, and the other 9 being reserved for integer data. You might create a tag called "Produced_Data" of data type DINT[10]. This creates an array of 10 DINT's, called Produced_Data[0] through Produced_Data[9]. Let's use Produced_Data[0] for your Boolean data, and 1 through 9 for your integer data.
Map the data something like this:
Code:
| Prox_Input Produced_Data[0].0
|-------| |--------------------------( )----|
|
| Some_Other_Signal Produced_Data[0].1
|-------| |--------------------------( )----|
|
| Singularity_Imminent Produced_Data[0].2
|-------| |--------------------------( )----|
|
| Produced_Data[0].3 Produced_Data[0].3
|-------| |--------------------------( )----|
|
...and so on. You'll note that with the last (spare) bit, I mapped it into itself. This is just a personal preference thing - basically, it just means that it won't every do anything, but if I did want to toggle it on and off for e.g. diagnostic purposes to watch it change in the other PLC, it's easy to do. Also avoids using AFI's which I prefer.
With your remaining DINT's, I again prefer to map them into themselves - i.e. just put 9 MOV instructions on the subsequent rung, with the source and destination the same in each case. Again, it just means you can see and manipulate the data easily for diagnostic purposes, and means that later on when you want to map some additional data, your code structure is already in place and all you have to do is change the input to your MOV instruction.