MEP and fire protection specification sections with addenda, one firm

Summary

Project specification sections from one US MEP and fire protection engineering firm, 2010 to 2025, with the addenda and bulletins that changed them. Each section is tagged with its CSI MasterFormat number, building type, issue stage and the code editions it cites, and carries a redline against the firm's master section where one exists. Defense, aerospace and secure federal projects are excluded, and engineer names, seals, client names and site addresses are removed.

Collected to order. We collect it from US companies for your order. Scope, volume and timing are confirmed in writing before you sign.

Pricing on request

Request scope and pricing

At a glance

Planned scope. Volume, sources and timing are confirmed in writing before you sign.

Records: 253Kspecification sections and addenda items
Size: 3.9 GB
Tokens, estimated: 850M
Years: 2010 to 2025
Firms: 1

Owner profile: One US MEP and fire protection engineering firm, 50 to 150 staff
Industry: Professional services
Data type: Code and engineering
Headcount: 50 to 150 staff
Region: United States
Languages: English
Formats: JSONL
Updated: 2026-09-26

Sources

System	Kind	Records
Shared drives	Shared files	215K specification sections
Microsoft 365 mail	Email	38.1K addenda and bulletin items
Deltek Vision	Databases	6.9K project records

Good for

training models to draft MEP specification sections from a design narrative
checking specification text against cited code editions such as NFPA 13 and ASHRAE 90.1
detecting conflicts between specification sections and later addenda
evaluating long-document editing against a master template

Fields

Field	Type	Description
section_id	string	Stable section id
project_ref	string	Project code, links to the project record
building_type	enum	office, education, industrial, retail, hospitality, mixed_use, laboratory or civic
csi_number	string	CSI MasterFormat section number
title	string	Section title
issue_stage	enum	permit, bid, addendum or conformed
code_editions	array<string>	Codes and standards cited, with edition
text	string	Section text in Part 1, 2 and 3 order
master_redline	array<string>	Insertions and deletions against the firm master section

Example record

{
  "section_id": "MF-SPEC-118204",
  "project_ref": "[SITE_31]",
  "building_type": "education",
  "csi_number": "21 13 13",
  "title": "Wet-pipe sprinkler systems",
  "issue_stage": "addendum",
  "code_editions": [
    "NFPA 13, 2019 edition",
    "NFPA 25, 2020 edition",
    "IFC 2021 as amended by [CITY_8]"
  ],
  "text": "PART 2 PRODUCTS. 2.3 SPRINKLERS. A. Quick-response, standard-coverage pendent sprinklers in finished ceilings, K-factor 5.6, white finish, recessed escutcheons. B. Concealed pendent sprinklers in the media center, cover plates factory painted to match the ceiling. C. Dry pendent sprinklers in the kitchen walk-in cooler, barrel length per manufacturer for the ceiling assembly. PART 3 EXECUTION. 3.4 TESTING. A. Hydrostatic test of new piping at 200 psi for 2 hours per the NFPA 13 acceptance test requirements, witnessed by [PERSON_5] for the authority having jurisdiction.",
  "master_redline": [
    "+ 2.3.C dry pendent sprinklers at walk-in cooler, Addendum 2",
    "- 2.3.D residential sprinklers, no dwelling units on this project"
  ]
}

One record, de-identified. Placeholders such as [PERSON_12] and [COMPANY_4] stay the same across the whole dataset, so threads still read correctly.

Licenses available

Exclusive
One buyer. Nobody else can license it during the exclusive term, usually 2 years.
Non-exclusive
Licensed to more than one buyer.
First look
One buyer gets 2 to 4 weeks to make an offer before anyone else sees the dataset.

What ships with it

Datasheet: what it is, what it is good for, verified size, sources, years, format and limits.
Provenance file: the owner shown by code, staff notice and consent status, exclusions, mapped to the EU AI Act Article 53 training-data summary and California AB 2013.
Manifest with a hash for every file.
QC report and de-identification report.
Your own copy, with unique canary records.

How it is de-identified

Default exclusions removed, files flattened to text, identifiers found in three layers and replaced with consistent placeholders, and the result measured against a 99% bar for each identifier type in each source.

The full method