Object_Naming_Submittal_TEMPLATE-v1.xlsx
XLSX spreadsheet 13 KB Posted
- Attached to
- replace chiller Federal contract opportunity
- Solicitation number
- 47PJ0018Q0029
About this file
Object Naming Submittal Template - reference document
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| RESPONSE_TO_QUESTIONS.pdf | ||
| Amendment_0003.pdf | ||
| Solicitation_Amendment_47PJ0018Q0029_0002.pdf | ||
| PembinaChiller-amendment_0001.pdf | ||
| GSA_R8_Open_Protocol_Implementation_Guide_-_BACnet_-_v1_0_0_FINAL.pdf | ||
| solicitation29-Pembina_chiller.pdf | ||
| GSA_PBS_Telecommunications_Distribution_Design_Guide.pdf | ||
| GSA_Data_Normalization_for_Building_Automation_Systems.pdf | ||
| Device_Schedule_TEMPLATE-v2.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Object Naming Submittal
| Contractor/Vendor | GSA OFM BAS | |||||
| Existing Object | Object Description | Object Type | Proposed Object Name | Vendor Comment | GSA Comment | Status |
EXAMPLE Object Naming Submittal
| Contractor/Vendor | GSA OFM BAS | |||||
| Existing Object | Object Description | Object Type | Proposed Object Name | Vendor Comment | GSA Comment | Status |
HELP
| Section/Field | Description |
| Contractor/Vendor | This section is to be completed by the contractor/vendor |
| Existing Object | This field should contain the existing name of an object that is to be re-named - this field does not apply to new construction, only to retrofits and upgrades |
| Object Description | This field should contain a description of the object that will allow the GSA reviewer/approver to determine if the Proposed Object Name is compliant with the GSA Data Normalization for Building Automation Systems standard and appropriate for the object |
| Object Type | This field should contain the type of object: AI, AO, AV, BI, BO, BV, MO, MV, Schedule, Calendar, Trend Log, Notification Class, Event Enrollment, File, Command |
| Proposed Object Name | This field should contain the GSA Data Normalization for Building Automation Systems standard-compliant object name that the contractor/vendor has determined is appropriate for the object |
| Vendor Comment | This field is provided for any comments the contractor/vendor wants to transmit |
| GSA OFM BAS | This section is to be completed by GSA OFM BAS Team |
| GSA Comment | The GSA reviewer/approver will use this field to provide comments/direction to the contractor/vendor |
| Status | This field will contain the current status of the proposed name: Rejected, Clarification |
Refer to GSA Data Normalization for Building Automation Systems for naming and metadata tagging requirements for BAS devices and objects. The latest version of this document can be obtained from GSA by requesting it from the GSA PBS OFM BAS team or from the GSA Project Manager.
Failure to conform to GSA standards and specifications may result in additional costs. The BAS contractor/vendor is liable for these costs; GSA is NOT RESPONSIBLE for projects costs associated with correcting device and/or object naming that does not conform to GSA standards. The contractor/vendor is strongly urged to submit naming and obtain GSA approval prior to implementation.
File details come from the government source that posted it.