Standard Tag List – Renewable Solar Project

Answer

A1:

“Standard Tags” refer to standardized SCADA monitoring parameters that have been consolidated from multiple previously executed project templates.

These parameters are common across solar projects and are used for monitoring, reporting, and performance analysis.

The standard list was prepared by:

1. Reviewing multiple SCADA templates
2. Identifying common parameters
3. Eliminating duplicates
4. Freezing a uniform parameter set

This finalized parameter set is treated as the Standard Tag List.

A2:

A tag is considered Non-Standard if:

• It is not available in the consolidated list
• It is project-specific or client-specific
• It requires additional logic or database restructuring
• It introduces new calculation or derived logic

Such tags require technical review before implementation.

A3:

 Standard Tag

A tag is considered Standard if:

• It exists in the approved consolidated parameter list
• It is part of company template library
• It has been used in previous executed projects
• It aligns with performance monitoring requirements

 Non-Standard Tag

A tag is considered Non-Standard if:

• It is not available in the consolidated parameter list
• It is project-specific or client-specific
• It requires new mapping or database modification
• It is not part of previously standardized templates

A4:

• The project shall implement only the predefined Standard Parameter Tag List.
• Any additional parameter requested by the client shall be reviewed by Product Team.
• Non-standard tags will only be implemented after technical validation and approval.
• The standard tag list will remain the governing reference document for new integration.

A5:

No.

The Standard Tag List already includes all critical parameters required for:

• Performance monitoring
• Grid compliance
• Energy accounting
• Fault analysis
• O&M reporting

Additional tags can be evaluated if justified.

A6:

No, it will not limit plant analytics.

• All critical tags required for analytics have already been added.

• Standard Tags cover the necessary operational and performance parameters.

• Current monitoring, analytics, reporting, and KPI calculations are fully supported.

• Additional tags will only be required if new analytics requirements arise in the future.

This ensures full analytics capability within the current project scope.

A7:

Consistency is maintained by:

• Using previously validated templates
• Maintaining a centralized standard tag list
• Avoiding project-specific customization unless approved

A8:

Yes, but only through controlled revision.

If approved:

• The master list is updated
• Revision is documented
• Future projects may incorporate the update