# Day & Zimmermann > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-11-07. - **Brand record:** https://optimly.ai/brand/day-zimmermann - **Dataset:** https://optimly.ai/brand/day-zimmermann.json - **Markdown:** https://optimly.ai/brand/day-zimmermann/llms.txt - **Official website:** https://dayzim.com - **Slug:** day-zimmermann - **Categories:** construction-engineering ## Overview - **Tagline:** Day & Zimmermann provides maintenance and construction, engineering, munitions, government, security, and workforce solutions. Source: Brand's website (https://dayzim.com) · 2026-11-07 - **Description:** Day & Zimmermann is a company offering maintenance and construction, engineering, munitions, government services, and recruiting and workforce solutions. Source: Brand's website (https://dayzim.com) · 2026-11-07 ## Identity - **Founders & leadership:** Leadership includes Harold L. Yoh, III; Kathleen King; Lisa Ann Cooney; Sankara Viswanathan; Daniel Ross; Mike Yoh; BG (Ret) John J. McGuiness; Doug Magee; and Jason Dunaway. Source: Brand's website (https://dayzim.com) · 2026-11-07 - **Website:** https://dayzim.com Source: Brand's website (https://dayzim.com) · 2026-11-07 ## Offerings - **Problem solved:** Supports organizations with industrial maintenance and construction, engineering, munitions production and demilitarization, government operations, security, intelligence support, and workforce needs. Source: Brand's website (https://dayzim.com) · 2026-11-07 - **Core capabilities:** - Maintenance and construction - Engineering - Munitions production and demilitarization - Government services - Architecture and engineering - Operations and maintenance - Integrated security - National intelligence support Source: Brand's website (https://dayzim.com) · 2026-11-07 - **Products / SKUs:** - Nuclear maintenance and construction - Fossil energy maintenance and construction - Chemical and industrial maintenance and construction - Solar field construction - Data center construction - Advanced manufacturing - Battery energy systems - Radiological protection Source: Brand's website (https://dayzim.com) · 2026-11-07 ## Audience - **Target industry:** Energy, industrial, defense, government, infrastructure, and manufacturing. Source: Brand's website (https://dayzim.com) · 2026-11-07 - **Customer base:** Government and industrial organizations, including customers requiring energy, infrastructure, defense, security, and workforce services. Source: Brand's website (https://dayzim.com) · 2026-11-07 - **Use cases:** - Nuclear projects and construction - Fossil energy projects and life extensions - Industrial and chemical maintenance - Solar field construction - Data center construction - Battery storage and energy systems - Munitions production and demilitarization - Government facility operations and maintenance Source: Brand's website (https://dayzim.com) · 2026-11-07 Page last updated 2026-11-07. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.