Archive for January 2016

Request History

No previous requests logged.

Session

• Config(array)
  • userAgent3a0f2117feed0d51d550e82bc4b6de72
  • time1566897499
  • countdown10
• Auth(array)
  • redirect/blog/posts/archive/01/2016
• Blog(array)
  • Options(array)
    • Path/blog
    • DisqusShortnamebrooksidestudios
    • Comments(true)

Request

Cake Params

• pluginblog
• controllerposts
• actionarchive
• named(empty)
• pass(array)
  • 001
  • 12016
• isAjax(false)

Post data

No post data.

Query string

No querystring data.

Cookie

• 0(empty)

Current Route

• keys(array)
  • 0plugin
  • 1controller
  • 2action
• options(array)
  • pluginblog|debug_kit|hero_manager|html_compressor
  • defaultRoute(true)
• defaults(empty)
• template/:plugin/:controller/:action/*

Sql Logs

Logs

View Variables

• title_for_layoutArchive for 01/2016
• posts(array)
  • 0(array)
    • Post(array)
      • id54
      • user_id1
      • blog_category_id4
      • titleDisaster Clean-Up: Common Forms Of Waste Encountered
      • slugdisaster-clean-up-common-forms-of-waste-encountered
      • blurbWhen a natural disaster, like a tornado, earthquake or flooding, occurs, demolition contractors are often called on to help with the clean-up of debris. Our unique skill set qualifies us to properly
      • content<p style="text-align: center;"><a href="/blog/uploads/2016/01/shutterstock_147158528.jpg"><img class="alignnone wp-image-195" src="/blog/uploads/2016/01/shutterstock_147158528-300x207.jpg" alt="Debris following natural disaster" width="358" height="247" /></a></p> When a natural disaster, like a tornado, earthquake or flooding, occurs, demolition contractors are often called on to help with the clean-up of debris. Our unique skill set qualifies us to properly dispose of materials and demolish structures that are no longer safe. Because of the nature of these disasters, there are dangerous materials spread into the environment and in places you wouldn't normally expect to find them. These are similar materials that experienced demolition teams work with on any project, however. Here are a few of the typical forms of waste and debris that need to be mitigated after natural disasters. <ul> <li><strong>Appliances</strong></li> </ul> In a typical demolition job, appliances would be removed well before demolition work began, either by the site owner, or by our crews during preliminary phases of the project. There's no such luxury or planning opportunities in a natural disaster, however. And, many appliances found in a typical home or office setting contain hazardous materials like refrigerants, mercury, and PCB capacitors. For that reason, appliances need to be removed from the rubble and demanufactured, with these hazardous materials removed and disposed of responsibly. Once that's done, metal from the appliances can be recycled. <ul> <li><strong>Asbestos</strong></li> </ul> Again, a typical demolition job would identify asbestos well before demolition and safely remove it from a structure. In a natural disaster clean-up effort, asbestos containing materials like siding, flooring, roofing and insulation can be found anywhere throughout the disaster area. Clean-up crews need to be properly trained to both identify asbestos containing materials and to properly handle and dispose of them safely. <ul> <li><strong>Electronics</strong></li> </ul> Items such as computers, printers, televisions, smartphones, digital cameras, mp3 players and electronic games can pose a threat to human health and to the environment due to the hazardous materials they contain. Often referred to as e-waste, or brown goods, electronic equipment is another example of debris that complicated clean-up efforts after a disaster. Typically, the best option is to collect any e-waste and transport it to a nearby facility that's permitted and licensed to dispose of it properly. <ul> <li><strong>Clean waste</strong></li> </ul> Not all debris in a natural disaster contains hazardous materials. Some is considered clean, which it's unpainted, untreated and free from contamination from chemicals like petroleum. The only real concern with clean waste is that it's disposed of so it doesn't impact the local environment including surface waters, wetlands or flood plains. Clean waste presents an opportunity to reuse and recycle waste generated from a natural disaster. Brick, building stone, concrete, asphalt, and untreated wood, including wood from downed trees, is all considered clean waste. Wood can be composted, chipped or used as firewood. Brick, stone, concrete and asphalt can all be reused in other building projects, which could help the recovery process. Experienced demolition contractors are vital for a variety of services. To find out more about our capabilities at Demolition Technologies, contact us at 918-379-0966.
      • tags(null)
      • expires(null)
      • views2629
      • keywords(null)
      • description(null)
      • active1
      • featured0
      • is_video0
      • comments_allowed(false)
      • comments_visible(false)
      • image(null)
      • image_caption(null)
      • image_link(null)
      • start_date_selected0
      • start_date(null)
      • created2016-01-26 09:50:38
      • modified2017-03-31 14:31:40
      • url/posts/view/54/disaster-clean-up-common-forms-of-waste-encountered
      • display_date2016-01-26 09:50:38
  • 1(array)
    • Post(array)
      • id53
      • user_id1
      • blog_category_id4
      • title3 Common Issues Related To On-Site Pollution
      • slug3-common-issues-related-to-on-site-pollution
      • blurbA dedication to environmental stewardship and responsibility in demolition projects means that materials are responsibly handled, stored, transported and disposed of, and that a site is left in bett
      • content<p style="text-align: center;"><a href="/blog/uploads/2016/01/shutterstock_135130892.jpg"><img class="alignnone wp-image-191" src="/blog/uploads/2016/01/shutterstock_135130892-300x300.jpg" alt="Demolition rubble" width="349" height="349" /></a></p> A dedication to environmental stewardship and responsibility in demolition projects means that materials are responsibly handled, stored, transported and disposed of, and that a site is left in better condition after the job is finished than it was when the project began. At Demolition Technologies, we believe a focus on the environmental impact of our work is important and crucial to successful demolition projects. With that, however, comes pollution liability concerns. Accidents, poor planning and poor execution of phases of a project can expose the environment and the surrounding community to pollution. This can include the actual release of pollutants, or the violation of a law put in place to protect the environment or community. These pollution events can occur in a number of ways if a demolition recycling company isn't experienced or detailed in their planning. Here are three common pollution claims that stem from these contractors' mistakes. <ul> <li><strong>Nuisances</strong></li> </ul> A demolition job is naturally loud and disruptive for the surrounding community. A responsible demolition contractor will take the necessary precautions to minimize the disturbances and form a relationship with nearby residents and businesses. Failing to do so could result in a nuisance claim, which pertains to any situation that interferes with a property owner's enjoyment of their property. For demolition projects, this could include loud noises, noxious fumes, and dust creation, to name a few common issues. All of these can be considered pollution that negatively impacts nearby properties and need to be considered in the planning stages of a project. <ul> <li><strong>Trespassing</strong></li> </ul> In this case, trespassing doesn't necessarily refer to being on someone else's property unlawfully. Instead, it refers to allowing disruptive or objectionable materials on someone else's property. There is some overlap with the nuisance claim. For example, an excess of dust created by a demolition job could be a nuisance to nearby businesses, or it could be considered trespassing if the dust settles on the business's property and creates a problem. A trespassing claim can apply to any material, regardless of whether it is hazardous or not. Even clean water and soil can lead to a trespassing claim if they're dumped irresponsibly on someone else's property. <ul> <li><strong>Contractual obligations</strong></li> </ul> In this case, a business owner could incur a loss and be liable for injuries on the job site when they're due to the release of pollutants. This, again, stems from a lack of proper planning that results in improper safety procedures being in place during the handling of hazardous materials. A common example would be a worker who breathes a contaminant and is injured. In that case, liability could fall to the owner. Working with an inexperienced or irresponsible demolition contractor can lead to dangerous situations, sub-par quality of work and liability issues. Contact us at Demolition Technologies to learn about our proven processes and capabilities.  
      • tags(null)
      • expires(null)
      • views3105
      • keywords(null)
      • description(null)
      • active1
      • featured0
      • is_video0
      • comments_allowed(false)
      • comments_visible(false)
      • image(null)
      • image_caption(null)
      • image_link(null)
      • start_date_selected0
      • start_date(null)
      • created2016-01-14 16:07:38
      • modified2017-03-31 14:31:40
      • url/posts/view/53/3-common-issues-related-to-on-site-pollution
      • display_date2016-01-14 16:07:38
  • 2(array)
    • Post(array)
      • id52
      • user_id1
      • blog_category_id4
      • title3 Key Concerns Prior To An Environmentally Responsible Demolition
      • slug3-key-concerns-prior-to-an-environmentally-responsible-demolition
      • blurbFor each of our demolition projects, environmental considerations dictate our processes and our approach. We place a priority on environmental stewardship and conservation, which means that addition
      • content<p style="text-align: center;"><a href="/blog/uploads/2016/01/shutterstock_167695379.jpg"><img class="alignnone wp-image-188" src="/blog/uploads/2016/01/shutterstock_167695379-300x200.jpg" alt="Demolition contractor doing site survey" width="357" height="238" /></a></p> For each of our demolition projects, environmental considerations dictate our processes and our approach. We place a priority on environmental stewardship and conservation, which means that additional planning is necessary before each project. Here are three key considerations we need to know before starting the demolition of a structure in order to leave the site in better condition than we found it. <ul> <li><strong>What materials are present? </strong></li> </ul> The building owner should be able to give us a good idea of what materials have been used to construct the building by supplying blueprints and other documentation. We also conduct walkthroughs and site visits to verify those documents and look for hazardous materials. Lead paint or asbestos in older buildings is common, but not something you'd necessarily know without investigating. By identifying the materials we're going to encounter, we can accurately plan for safely removing and disposing of them, or plan for recycling or salvaging efforts. <ul> <li><strong>Has the site ever been used for industrial purposes? </strong></li> </ul> This is a valuable question that could expose the need for additional site surveys and testing before a demolition can begin. If the answer is yes, it suggests that a number of hazardous materials may be present that aren't typical of a non-industrial site. This makes this question especially important if the site is no longer being used for industrial work. There also may be underground storage tanks present that will need to be part of our plans. Special procedures should be taken to remove these outside of the usual above ground demolition work. Underground tanks also may be leaking, which again calls for additional procedures and abatement of hazardous materials. <ul> <li><strong>What's the history of the structure? </strong></li> </ul> Similar to finding out if there has been industrial activity on the site, understanding the history of the building gives you clues about what state the structure is in and what materials may be present. If the building has been abandoned for decades, as many sites planned for demolition are, there's a great potential for mold, and the possibility of a weakened structure. While the structure of a building rarely dictates environmental concerns, it is significant for the safety of workers and will dictate how the building is brought down. Additionally, looking through the history of permits for the building can tell you where renovations have been made, which may suggest the building isn't entirely consistent throughout. That again may force some alternative demolition methods. Through effective planning, demolition projects are efficient, safe and environmentally responsible. To learn more about the way we handle demolition at Demolition Technologies, contact us at 918-379-0966.
      • tags(null)
      • expires(null)
      • views2534
      • keywords(null)
      • description(null)
      • active1
      • featured0
      • is_video0
      • comments_allowed(false)
      • comments_visible(false)
      • image(null)
      • image_caption(null)
      • image_link(null)
      • start_date_selected0
      • start_date(null)
      • created2016-01-08 14:22:55
      • modified2017-03-31 14:31:40
      • url/posts/view/52/3-key-concerns-prior-to-an-environmentally-responsible-demolition
      • display_date2016-01-08 14:22:55
• STORE(false)
• PLUGINblog
• isMobile(false)
• _sessid97a6b78718f49d2d1fefe678dfe60794
• _USER(false)
• slider_for_layoutslider element
• header_for_layoutheader element
• footer_for_layout<h3> <a href="tel:9183790966">918-379-0966</a> </h3>
• sidebar_for_layoutsidebar element
• featured_for_layoutfeatured element
• $request->data(empty)
• $this->validationErrors(array)
  • Page(empty)
  • PageElement(empty)
  • Setting(empty)
  • Option(empty)
  • Post(empty)
  • Category(empty)
  • Form(empty)
• Loaded Helpers(array)
  • 0Form
  • 1Html
  • 2HtmlCompressor
  • 3Paginator
  • 4Session
  • 5Text
  • 6Time
  • 7Number
  • 8SimpleGraph
  • 9DebugTimer
  • 10Toolbar
  • 11Nav
  • 12HtmlToolbar

App Constants

CakePHP Constants

PHP Environment

Included Files

Include Paths

• 0/home/dtwreckit/public_html/lib
• 2/usr/share/pear
• 3/usr/share/php
• 4-> /home/dtwreckit/public_html/lib/Cake/

Included Files

• core(array)
  • Behavior(array)
    • 0CORE/Model/Behavior/ContainableBehavior.php
  • Cache(array)
    • 0CORE/Cache/Cache.php
    • 1CORE/Cache/Engine/FileEngine.php
    • 2CORE/Cache/CacheEngine.php
  • Component(array)
    • 0CORE/Controller/Component/AuthComponent.php
    • 1CORE/Controller/Component/CookieComponent.php
    • 2CORE/Controller/Component/SessionComponent.php
    • 3CORE/Controller/Component/RequestHandlerComponent.php
  • Config(array)
    • 0CORE/Config/routes.php
    • 1CORE/Config/config.php
  • Controller(array)
    • 0CORE/Controller/Controller.php
    • 1CORE/Controller/ComponentCollection.php
    • 2CORE/Controller/Component.php
  • Datasource(array)
    • 0CORE/Model/Datasource/CakeSession.php
    • 1CORE/Model/Datasource/Database/Mysql.php
    • 2CORE/Model/Datasource/DboSource.php
    • 3CORE/Model/Datasource/DataSource.php
  • Error(array)
    • 0CORE/Error/exceptions.php
    • 1CORE/Error/ErrorHandler.php
  • I18n(array)
    • 0CORE/I18n/I18n.php
    • 1CORE/I18n/L10n.php
  • Log(array)
    • 0CORE/Log/CakeLog.php
    • 1CORE/Log/LogEngineCollection.php
    • 2CORE/Log/Engine/FileLog.php
    • 3CORE/Log/Engine/BaseLog.php
    • 4CORE/Log/CakeLogInterface.php
  • Model(array)
    • 0CORE/Model/ConnectionManager.php
    • 1CORE/Model/Model.php
    • 2CORE/Model/BehaviorCollection.php
    • 3CORE/Model/ModelBehavior.php
  • Network(array)
    • 0CORE/Network/CakeRequest.php
    • 1CORE/Network/CakeResponse.php
  • Other(array)
    • 0CORE/bootstrap.php
    • 1CORE/basics.php
    • 2CORE/Core/App.php
    • 3CORE/Core/Configure.php
    • 4CORE/Core/CakePlugin.php
    • 5CORE/Event/CakeEventListener.php
    • 6CORE/Event/CakeEvent.php
    • 7CORE/Event/CakeEventManager.php
    • 8CORE/Core/Object.php
  • Routing(array)
    • 0CORE/Routing/Dispatcher.php
    • 1CORE/Routing/Filter/AssetDispatcher.php
    • 2CORE/Routing/DispatcherFilter.php
    • 3CORE/Routing/Filter/CacheDispatcher.php
    • 4CORE/Routing/Router.php
    • 5CORE/Routing/Route/CakeRoute.php
    • 6CORE/Routing/Route/PluginShortRoute.php
  • Utility(array)
    • 0CORE/Utility/Hash.php
    • 1CORE/Utility/Folder.php
    • 2CORE/Utility/Inflector.php
    • 3CORE/Utility/ObjectCollection.php
    • 4CORE/Utility/Debugger.php
    • 5CORE/Utility/CakeText.php
    • 6CORE/Utility/ClassRegistry.php
  • View(array)
    • 0CORE/View/HelperCollection.php
• app(array)
  • Component(array)
    • 0APP/Controller/Component/AutoLoginComponent.php
  • Config(array)
    • 0APP/Config/core.php
    • 1APP/Config/config.php
    • 2APP/Config/bootstrap.php
    • 3APP/Config/functions.php
    • 4APP/Config/routes.php
    • 5APP/Config/database.php
  • Controller(array)
    • 0APP/Controller/AppController.php
  • Model(array)
    • 0APP/Model/Page.php
    • 1APP/Model/AppModel.php
    • 2APP/Model/PageElement.php
    • 3APP/Model/Setting.php
  • Other(array)
    • 0APP/webroot/index.php
• plugins(array)
  • Blog(array)
    • Config(array)
      • 0Blog/Config/bootstrap.php
      • 1Blog/Config/routes.php
    • Controller(array)
      • 0Blog/Controller/PostsController.php
      • 1Blog/Controller/BlogAppController.php
    • Component(array)
      • 0Blog/Controller/Component/ProcessFileComponent.php
      • 1Blog/Controller/Component/SanitizerComponent.php
      • 2Blog/Controller/Component/ProcessImageComponent.php
    • Model(array)
      • 0Blog/Model/Option.php
      • 1Blog/Model/BlogAppModel.php
      • 2Blog/Model/Post.php
      • 3Blog/Model/Category.php
  • DebugKit(array)
    • Component(array)
      • 0DebugKit/Controller/Component/ToolbarComponent.php
    • Plugin(array)
      • 0DebugKit/Lib/DebugMemory.php
      • 1DebugKit/Lib/Panel/HistoryPanel.php
      • 2DebugKit/Lib/DebugPanel.php
      • 3DebugKit/Lib/Panel/SessionPanel.php
      • 4DebugKit/Lib/Panel/RequestPanel.php
      • 5DebugKit/Lib/Panel/SqlLogPanel.php
      • 6DebugKit/Lib/Panel/TimerPanel.php
      • 7DebugKit/Lib/Panel/LogPanel.php
      • 8DebugKit/Lib/Log/Engine/DebugKitLog.php
      • 9DebugKit/Lib/Panel/VariablesPanel.php
      • 10DebugKit/Lib/Panel/EnvironmentPanel.php
      • 11DebugKit/Lib/Panel/IncludePanel.php
      • 12DebugKit/Lib/DebugTimer.php
  • HeroManager(array)
    • Config(array)
      • 0HeroManager/Config/bootstrap.php
      • 1HeroManager/Config/routes.php