Does the export produce a GlobalDB XML or a PLC tag table?

Both. The GlobalDB XML imports via TIA Portal Openness and arrives as a single block in the project tree. The flat PLC tag table CSV covers shops that import through the tag-table editor. The two formats carry identical tag names, data types, and addresses.

Which CPU families are supported?

S7-1200 and S7-1500 with TIA Portal V15 and later. ET 200SP CPUs that use the standard STEP 7 import path are also covered. The GlobalDB format and Openness import path are the same across both CPU families.

How is signal class mapped to data type and address space?

AI rows take Real data type at consecutive %IW word offsets. AO rows take Real at %QW. DI rows take Bool at %I bit addresses. DO rows take Bool at %Q. Starting addresses are configurable per export, with %IW256, %QW256, %I10.0, and %Q10.0 as the defaults.

Are tag names sanitized for IEC 61131-3 identifier rules?

Yes. Hyphens, dots, and other separators in the source tag are converted to underscores. The original tag string is preserved in the Comment field so the TIA Portal project traces back to the source document.

Can the same I/O list export to TIA Portal and Studio 5000 at the same time?

Yes. Each export endpoint reads the same reviewed I/O list. A site running mixed Siemens and Rockwell hardware can export both formats from one workspace without re-extracting.

What if a TIA Portal block already exists at the chosen number?

TIA Portal rejects an import when a GlobalDB with the same block number already exists. Either change the block number in the export dialog before downloading, or remove the conflicting DB from the project tree before importing.

I/O list to TIA Portal.

A reviewed I/O list becomes a GlobalDB block and a PLC tag-table CSV. Tag names sanitized for IEC 61131-3, data types assigned by signal class, %IW / %QW / %I / %Q addresses allocated from a configurable start. Ready for an S7-1200 or S7-1500 project.

Generate the GlobalDB See the I/O list schema

Read one of your own drawings.

Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.

PDF · DWG · DXF · TIFF · PNG · XLSX

Browse filesor drop a file anywhere on this card

Column mapping.

Every I/O list column has a TIA Portal destination. Auto-mapped fields populate from defaults you can override at export; derived fields use I/O list values when present and fall back to auto-allocation otherwise.

#	I/O list column	TIA Portal field	Data type	Mapping	Rule
01	Tag	`Name`	string	auto	Tag string written verbatim into the Name attribute. Hyphens and dots are converted to underscores to satisfy IEC 61131-3 identifier rules. Original string preserved in the comment.
02	Service description	`Comment`	string	preserved	Service text from the I/O list copied into the Comment attribute. Equipment tag and line number appended when present, separated by a slash.
03	Signal class = AI	`LogicalAddress %IW`	Real	auto	Analog input rows allocated consecutive word offsets from the start address you set at export (default %IW256). Real data type.
04	Signal class = AO	`LogicalAddress %QW`	Real	auto	Analog output rows allocated consecutive word offsets from the start address (default %QW256). Real data type.
05	Signal class = DI	`LogicalAddress %I`	Bool	auto	Digital input rows bit-packed within input bytes from the start address (default %I10.0). Bool data type.
06	Signal class = DO	`LogicalAddress %Q`	Bool	auto	Digital output rows bit-packed within output bytes from the start address (default %Q10.0). Bool data type.
07	Cabinet / Card / Ch	`LogicalAddress`	derived	derived	When the I/O list cabinet, card slot, and channel are filled, the export uses them to compute the address directly instead of auto-allocating. Lets a controls team pin specific tags to specific hardware slots.
08	Loop number	`Comment suffix`	string	optional	Loop number appended to the Comment as "Loop L-{number}" so loop folders are traceable inside the project tree.
09	Sub-class (BPCS/SIS)	`GlobalDB target`	routing	optional	SIS rows can route to a separate GlobalDB block when the project enforces IEC 61511 separation between basic process control and safety.
10	Range / units	`not exported`	-	optional	Engineering range stays inside the I/O list. The TIA Portal block carries the raw integer or float; scaling lives in the application logic, not the tag table.

Other targets.

The same reviewed I/O list reshapes to every other PLC platform and data-exchange format your project might use.

From I/O list to project tree.

01UploadI/O list or P&ID set
02MapColumns to TIA fields
03Allocate%IW / %QW addresses
04ImportGlobalDB or tag table

Bring it into your project.

Upload an I/O list or a P&ID set, review the rows, export a GlobalDB XML or a PLC tag-table CSV ready for an S7-1200 or S7-1500 project.

Start a workspace Pricing

I/O list to TIA Portal.

Column mapping.

#	I/O list column	TIA Portal field	Data type	Mapping	Rule
01	Tag	`Name`	string	auto	Tag string written verbatim into the Name attribute. Hyphens and dots are converted to underscores to satisfy IEC 61131-3 identifier rules. Original string preserved in the comment.
02	Service description	`Comment`	string	preserved	Service text from the I/O list copied into the Comment attribute. Equipment tag and line number appended when present, separated by a slash.
03	Signal class = AI	`LogicalAddress %IW`	Real	auto	Analog input rows allocated consecutive word offsets from the start address you set at export (default %IW256). Real data type.
04	Signal class = AO	`LogicalAddress %QW`	Real	auto	Analog output rows allocated consecutive word offsets from the start address (default %QW256). Real data type.
05	Signal class = DI	`LogicalAddress %I`	Bool	auto	Digital input rows bit-packed within input bytes from the start address (default %I10.0). Bool data type.
06	Signal class = DO	`LogicalAddress %Q`	Bool	auto	Digital output rows bit-packed within output bytes from the start address (default %Q10.0). Bool data type.
07	Cabinet / Card / Ch	`LogicalAddress`	derived	derived	When the I/O list cabinet, card slot, and channel are filled, the export uses them to compute the address directly instead of auto-allocating. Lets a controls team pin specific tags to specific hardware slots.
08	Loop number	`Comment suffix`	string	optional	Loop number appended to the Comment as "Loop L-{number}" so loop folders are traceable inside the project tree.
09	Sub-class (BPCS/SIS)	`GlobalDB target`	routing	optional	SIS rows can route to a separate GlobalDB block when the project enforces IEC 61511 separation between basic process control and safety.
10	Range / units	`not exported`	-	optional	Engineering range stays inside the I/O list. The TIA Portal block carries the raw integer or float; scaling lives in the application logic, not the tag table.