{"data":{"slug":"instrument-data-sheets","title":"Instrument Data Sheets and Specification Documents","summary":"An instrument data sheet is the specification document that defines everything about an instrument: what it measures, under what conditions, with what…","category":{"slug":"technical-guides","name":"Technical Guides"},"url":"https://wiki.aspotomasyon.com/article/instrument-data-sheets","markdown_url":"https://wiki.aspotomasyon.com/article/instrument-data-sheets.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/instrument-data-sheets","published":"2026-08-11T13:05:24+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":813,"image":"https://wiki.aspotomasyon.com/assets/social/instrument-data-sheets-203d78f85089.png","html":"<p>An <strong>instrument data sheet</strong> is the specification document that defines everything about an instrument: what it measures, under what conditions, with what accuracy, over which communication interface, and with which approvals. It is the contract between the process engineer (what the plant needs), the instrument engineer (how it is selected), and the vendor (what is delivered). Data sheets are the backbone of instrumentation engineering — and the quality of a plant's data sheets determines the quality of its procurement, installation, and maintenance for decades.</p><figure class=\"article-figure\"><img src=\"https://wiki.aspotomasyon.com/assets/diagrams/technical-guides-context.svg\" width=\"1100\" height=\"460\" loading=\"lazy\" decoding=\"async\" alt=\"A commissioning evidence chain: every acceptance result should lead back to a requirement and identify the configuration that was actually tested.\"><figcaption>A commissioning evidence chain: every acceptance result should lead back to a requirement and identify the configuration that was actually tested. <a href=\"https://wiki.aspotomasyon.com/assets/diagrams/technical-guides-context.svg\" target=\"_blank\" rel=\"noopener\">View full size</a></figcaption></figure>\n\n<h2 id=\"standard-data-sheet-format\">Standard Data Sheet Format</h2>\n\n<p>The ISA-20 standard defines the classic instrument specification sheet (transmitters, valves, analyzers, etc.). A complete data sheet has sections:</p>\n\n<ul>\n  <li><strong>Identification</strong> — tag number, service description, line/equipment reference, document number and revision, plant/project name.</li>\n  <li><strong>Process data</strong> — the measured variable, fluid and its properties (density, viscosity, composition), normal/design operating conditions: temperature, pressure, flow range, and the required accuracy at the normal point.</li>\n  <li><strong>Functional requirements</strong> — signal type (4–20 mA HART, FOUNDATION Fieldbus, PROFIBUS PA, WirelessHART), range and range limits, accuracy and repeatability, response time, turndown, alarm functions.</li>\n  <li><strong>Construction</strong> — wetted materials, process connection (size, rating, flange standard), enclosure and electrical classification (Ex zone/division, IP rating), mounting type, and accessories (manifold, bracket).</li>\n  <li><strong>Environmental and approvals</strong> — ambient temperature range, hazardous-area approval (ATEX/IECEx/Class I Div), SIL rating if safety-related, and marine/industry certifications.</li>\n  <li><strong>Commercial</strong> — quantity, required deliverables (certificates, calibration reports), and inspection/test requirements.</li>\n</ul>\n\n<p>The secret of a good data sheet is <em>completeness with intent</em>: every field is filled because someone decided it, not because the form demanded it. Blank fields on a data sheet become vendor choices — and vendor choices rarely match the plant's intent.</p>\n\n<h2 id=\"writing-requirements-not-solutions\">Writing Requirements, Not Solutions</h2>\n\n<p>The data sheet should state the <em>requirement</em> and leave the <em>solution</em> to qualified vendors — but only where it matters. Good practice:</p>\n\n<ul>\n  <li>State functional needs precisely: \"accuracy ≤ 0.1% of span including drift over 12 months,\" not \"high accuracy.\"</li>\n  <li>Specify the interface and protocol (HART device revision, OPC UA server capability) — modern instruments are network citizens; the data sheet is where that is decided.</li>\n  <li>Name the process fluid, its composition limits, and the process conditions at the mounting point — a pressure transmitter selected for a clean gas will not survive a slurry service.</li>\n  <li>Leave manufacturer/model open for competitive bidding unless the plant standardizes (a legitimate choice — standardization documents should say so).</li>\n  <li>Reference the plant's engineering standards (wiring, mounting, tagging) so the vendor's offering conforms without asking.</li>\n</ul>\n\n<h2 id=\"data-sheets-in-the-lifecycle\">Data Sheets in the Lifecycle</h2>\n\n<p>The data sheet is created during design, but it lives on:</p>\n\n<ul>\n  <li><strong>Procurement</strong> — the RFQ package and the purchase order reference the sheet; the vendor's quotation is compared against it line by line.</li>\n  <li><strong>Vendor document review</strong> — the vendor returns the filled sheet with the offered model; review against the requirement: accuracy, materials, approvals, and options must match.</li>\n  <li><strong>Receiving and installation</strong> — the delivered instrument is checked against the sheet (tag, model, options); a wrong manifold discovered at commissioning costs a shutdown, not a purchase order change.</li>\n  <li><strong>Maintenance</strong> — the sheet is the reference for spare parts, calibration ranges, and replacement; keep it updated when a substitution is approved.</li>\n  <li><strong>Retirement</strong> — the record of what was installed remains in the plant's instrument database, linked to the loop folders.</li>\n</ul>\n\n<h2 id=\"modern-instrument-data-management\">Modern Instrument Data Management</h2>\n\n<p>Instrument data today usually lives in a database (CMMS or a dedicated instrument management system) rather than paper files: tag, data sheet fields, calibration history, and device configuration linked to the device management tool (AMS-style). The discipline is the same as paper: one authoritative record per tag, change control for substitutions, and the data sheet as the template the database follows. The DB also enables the strategic views — device age, spare part coverage, SIL proof-test planning — that paper cannot.</p>\n\n<h2 id=\"summary\">Summary</h2>\n\n<p>Instrument data sheets are the specification contracts of the instrumented plant: process conditions, functional requirements, construction, approvals, and commercial terms — written as requirements, reviewed against vendor offers, and maintained through the lifecycle. Invest in the data sheet at design time; it is the cheapest quality control the plant will ever buy, and it is the document every later engineer will look for first.</p><section class=\"engineering-check\"><h2 id=\"apply-this-to-your-project\">Apply this to your project</h2><ul><li>Agree the test boundary and site authorization, especially where outputs or communications can affect operating equipment.</li><li>Record expected and actual values, equipment identifiers, software revision, test conditions, and exceptions.</li><li>Retest changed behavior and archive the final configuration with the test record and recovery instructions.</li></ul><p><a href=\"https://wiki.aspotomasyon.com/guides\">Follow an ASP project guide</a> to connect the fundamentals with implementation and acceptance.</p></section><figure class=\"article-figure\"><img src=\"https://wiki.aspotomasyon.com/assets/diagrams/technical-guides-review.svg\" width=\"1100\" height=\"460\" loading=\"lazy\" decoding=\"async\" alt=\"Engineering review sequence: Prepare → Execute → Resolve → Release. Keep the recorded evidence with the accepted configuration.\"><figcaption>Engineering review sequence: Prepare → Execute → Resolve → Release. Keep the recorded evidence with the accepted configuration. <a href=\"https://wiki.aspotomasyon.com/assets/diagrams/technical-guides-review.svg\" target=\"_blank\" rel=\"noopener\">View full size</a></figcaption></figure><h2 id=\"primary-references-and-further-reading\">Primary references and further reading</h2><p>Use the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.</p><ul><li><a href=\"https://csrc.nist.gov/pubs/sp/800/82/r3/final\" rel=\"noopener noreferrer\" target=\"_blank\">NIST SP 800-82 Rev. 3 — OT configuration and operational considerations</a></li><li><a href=\"https://www.isa.org/standards-and-publications/isa-standards/isa-standards-committees\" rel=\"noopener noreferrer\" target=\"_blank\">ISA — Automation standards and committees</a></li></ul><!-- asp-editorial-202609 -->","markdown":"# Instrument Data Sheets and Specification Documents\n\n> An instrument data sheet is the specification document that defines everything about an instrument: what it measures, under what conditions, with what…\n\n- Canonical URL: https://wiki.aspotomasyon.com/article/instrument-data-sheets\n- Publisher: ASP OTOMASYON A.Ş. (ASP OTOMASYON Wiki)\n- Category: Technical Guides\n- Published: 2026-08-11 · Updated: 2026-09-13\n- Reading time: 4 min · Language: English\n\nAn **instrument data sheet** is the specification document that defines everything about an instrument: what it measures, under what conditions, with what accuracy, over which communication interface, and with which approvals. It is the contract between the process engineer (what the plant needs), the instrument engineer (how it is selected), and the vendor (what is delivered). Data sheets are the backbone of instrumentation engineering — and the quality of a plant's data sheets determines the quality of its procurement, installation, and maintenance for decades.\n\n![A commissioning evidence chain: every acceptance result should lead back to a requirement and identify the configuration that was actually tested.](https://wiki.aspotomasyon.com/assets/diagrams/technical-guides-context.svg)\n\n*A commissioning evidence chain: every acceptance result should lead back to a requirement and identify the configuration that was actually tested.*\n\n## Standard Data Sheet Format\n\nThe ISA-20 standard defines the classic instrument specification sheet (transmitters, valves, analyzers, etc.). A complete data sheet has sections:\n\n- **Identification** — tag number, service description, line/equipment reference, document number and revision, plant/project name.\n- **Process data** — the measured variable, fluid and its properties (density, viscosity, composition), normal/design operating conditions: temperature, pressure, flow range, and the required accuracy at the normal point.\n- **Functional requirements** — signal type (4–20 mA HART, FOUNDATION Fieldbus, PROFIBUS PA, WirelessHART), range and range limits, accuracy and repeatability, response time, turndown, alarm functions.\n- **Construction** — wetted materials, process connection (size, rating, flange standard), enclosure and electrical classification (Ex zone/division, IP rating), mounting type, and accessories (manifold, bracket).\n- **Environmental and approvals** — ambient temperature range, hazardous-area approval (ATEX/IECEx/Class I Div), SIL rating if safety-related, and marine/industry certifications.\n- **Commercial** — quantity, required deliverables (certificates, calibration reports), and inspection/test requirements.\n\nThe secret of a good data sheet is *completeness with intent*: every field is filled because someone decided it, not because the form demanded it. Blank fields on a data sheet become vendor choices — and vendor choices rarely match the plant's intent.\n\n## Writing Requirements, Not Solutions\n\nThe data sheet should state the *requirement* and leave the *solution* to qualified vendors — but only where it matters. Good practice:\n\n- State functional needs precisely: \"accuracy ≤ 0.1% of span including drift over 12 months,\" not \"high accuracy.\"\n- Specify the interface and protocol (HART device revision, OPC UA server capability) — modern instruments are network citizens; the data sheet is where that is decided.\n- Name the process fluid, its composition limits, and the process conditions at the mounting point — a pressure transmitter selected for a clean gas will not survive a slurry service.\n- Leave manufacturer/model open for competitive bidding unless the plant standardizes (a legitimate choice — standardization documents should say so).\n- Reference the plant's engineering standards (wiring, mounting, tagging) so the vendor's offering conforms without asking.\n\n## Data Sheets in the Lifecycle\n\nThe data sheet is created during design, but it lives on:\n\n- **Procurement** — the RFQ package and the purchase order reference the sheet; the vendor's quotation is compared against it line by line.\n- **Vendor document review** — the vendor returns the filled sheet with the offered model; review against the requirement: accuracy, materials, approvals, and options must match.\n- **Receiving and installation** — the delivered instrument is checked against the sheet (tag, model, options); a wrong manifold discovered at commissioning costs a shutdown, not a purchase order change.\n- **Maintenance** — the sheet is the reference for spare parts, calibration ranges, and replacement; keep it updated when a substitution is approved.\n- **Retirement** — the record of what was installed remains in the plant's instrument database, linked to the loop folders.\n\n## Modern Instrument Data Management\n\nInstrument data today usually lives in a database (CMMS or a dedicated instrument management system) rather than paper files: tag, data sheet fields, calibration history, and device configuration linked to the device management tool (AMS-style). The discipline is the same as paper: one authoritative record per tag, change control for substitutions, and the data sheet as the template the database follows. The DB also enables the strategic views — device age, spare part coverage, SIL proof-test planning — that paper cannot.\n\n## Summary\n\nInstrument data sheets are the specification contracts of the instrumented plant: process conditions, functional requirements, construction, approvals, and commercial terms — written as requirements, reviewed against vendor offers, and maintained through the lifecycle. Invest in the data sheet at design time; it is the cheapest quality control the plant will ever buy, and it is the document every later engineer will look for first.\n\n## Apply this to your project\n\n- Agree the test boundary and site authorization, especially where outputs or communications can affect operating equipment.\n- Record expected and actual values, equipment identifiers, software revision, test conditions, and exceptions.\n- Retest changed behavior and archive the final configuration with the test record and recovery instructions.\n\n[Follow an ASP project guide](https://wiki.aspotomasyon.com/guides) to connect the fundamentals with implementation and acceptance.\n\n![Engineering review sequence: Prepare → Execute → Resolve → Release. Keep the recorded evidence with the accepted configuration.](https://wiki.aspotomasyon.com/assets/diagrams/technical-guides-review.svg)\n\n*Engineering review sequence: Prepare → Execute → Resolve → Release. Keep the recorded evidence with the accepted configuration.*\n\n## Primary references and further reading\n\nUse the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.\n\n- [NIST SP 800-82 Rev. 3 — OT configuration and operational considerations](https://csrc.nist.gov/pubs/sp/800/82/r3/final)\n- [ISA — Automation standards and committees](https://www.isa.org/standards-and-publications/isa-standards/isa-standards-committees)\n\n---\n\nCite the canonical article: https://wiki.aspotomasyon.com/article/instrument-data-sheets (Instrument Data Sheets and Specification Documents, ASP OTOMASYON, updated 2026-09-13).\n","headings":[{"id":"standard-data-sheet-format","title":"Standard Data Sheet Format"},{"id":"writing-requirements-not-solutions","title":"Writing Requirements, Not Solutions"},{"id":"data-sheets-in-the-lifecycle","title":"Data Sheets in the Lifecycle"},{"id":"modern-instrument-data-management","title":"Modern Instrument Data Management"},{"id":"summary","title":"Summary"},{"id":"apply-this-to-your-project","title":"Apply this to your project"},{"id":"primary-references-and-further-reading","title":"Primary references and further reading"}],"faq":[],"references":[{"name":"NIST SP 800-82 Rev. 3 — OT configuration and operational considerations","url":"https://csrc.nist.gov/pubs/sp/800/82/r3/final"},{"name":"ISA — Automation standards and committees","url":"https://www.isa.org/standards-and-publications/isa-standards/isa-standards-committees"}],"related":[{"slug":"how-to-read-pid-diagrams-isa-5-1","title":"How to Read a P&ID: ISA 5.1 Symbols, Tags, and Control Loops","summary":"A P&ID shows what is piped, measured, and controlled, and it is read by tracing each loop from sensor to final element while decoding the ISA 5.1 tag letters.","category":{"slug":"technical-guides","name":"Technical Guides"},"url":"https://wiki.aspotomasyon.com/article/how-to-read-pid-diagrams-isa-5-1","markdown_url":"https://wiki.aspotomasyon.com/article/how-to-read-pid-diagrams-isa-5-1.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/how-to-read-pid-diagrams-isa-5-1","published":"2026-10-11T11:46:21+00:00","modified":"2026-10-11T11:46:21+00:00","reading_minutes":9,"word_count":1932,"image":"https://wiki.aspotomasyon.com/assets/social/how-to-read-pid-diagrams-isa-5-1-27c726226ae8.png"},{"slug":"instrument-loop-diagrams-documentation","title":"Instrument Loop Diagrams and Documentation","summary":"Instrument loop diagrams (loop sheets) are the detailed engineering drawings that show exactly how a single instrument or control loop is wired, connected, and…","category":{"slug":"technical-guides","name":"Technical Guides"},"url":"https://wiki.aspotomasyon.com/article/instrument-loop-diagrams-documentation","markdown_url":"https://wiki.aspotomasyon.com/article/instrument-loop-diagrams-documentation.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/instrument-loop-diagrams-documentation","published":"2026-08-06T12:26:37+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":874,"image":"https://wiki.aspotomasyon.com/assets/social/instrument-loop-diagrams-documentation-6eba9eb90f1d.png"},{"slug":"reading-electrical-schematics","title":"Reading Electrical Schematics and P&IDs: An Engineer's Guide","summary":"Every automation engineer's working life revolves around two drawing types: electrical schematics , which show how the control system is wired, and P&IDs…","category":{"slug":"technical-guides","name":"Technical Guides"},"url":"https://wiki.aspotomasyon.com/article/reading-electrical-schematics","markdown_url":"https://wiki.aspotomasyon.com/article/reading-electrical-schematics.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/reading-electrical-schematics","published":"2026-08-11T13:05:24+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":867,"image":"https://wiki.aspotomasyon.com/assets/social/reading-electrical-schematics-50d766a7f328.png"},{"slug":"control-panel-design-standards","title":"Industrial Control Panel Design: Standards and Layout","summary":"An industrial control panel is the physical heart of an automation system — and one of the most regulated pieces of it.","category":{"slug":"technical-guides","name":"Technical Guides"},"url":"https://wiki.aspotomasyon.com/article/control-panel-design-standards","markdown_url":"https://wiki.aspotomasyon.com/article/control-panel-design-standards.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/control-panel-design-standards","published":"2026-08-11T13:05:24+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":821,"image":"https://wiki.aspotomasyon.com/assets/social/control-panel-design-standards-97c6d20ab389.png"}],"citation":"ASP OTOMASYON. Instrument Data Sheets and Specification Documents. Updated 2026-09-13. https://wiki.aspotomasyon.com/article/instrument-data-sheets"}}