As we mentioned before, the Maturix system allows you to follow the temperature and strength development in real-time. This will help you to keep your project plan, make a more efficient use of resources, ensure good concrete quality and fulfil the documentation and quality assurance requirements. Moreover, it will allow you to take proactive decisions based on data instead of using data passively.
For example, one of our clients experienced that one day, while being at home during the weekend, there was a sudden drop in temperature in his concrete. He asked a colleague to check the job site and found that one of the concrete covers had flown away. Luckly, it was not too late so the cover was placed back and the concrete cured successfully. The situation could have been disastrous, the concrete could have frozen (the project was located in Norway) causing innumerable delays to the rest of the project and a lot of added stress. Instead, thanks to the remote access to the temperature data from a smartphone, the client could solve the issue easily and fast.
When working on a project, there are many things that can go wrong. The heating or cooling equipment might break, the covers might blow away or the concrete may cure slower than expected. This added to the fact that many times the project site is far from other infrastructures makes it challenging to keep an eye on everything. You may be home on the weekend hoping that your concrete is doing fine.
With Maturix In-situ, you could be home and simply check on your phone how the cast is doing at any time. Moreover, you can also set alarms to get notified if the temperature drops or exceeds certain values, if the strength is reached or if there is data coming in. Say goodbye to the long drives done to check if all is okay, now you can accomplish the same simply by looking at the data from your phone or laptop.
A thermal control plan is often a requirement on big scale projects and on publicly owned (infrastructure, utility buildings etc.).
Requirements might include requirements such as:
In the table below, we have compared the procedure of creating the thermal control documentation with a traditional data logger against doing it with a smart concrete sensor.
Gather Data
Extensive work of gather information, as distance from office to concrete both on job sites and precast facilities might be long
Two types of maturity sensors are available: Short-range (bluetooth, wifi etc.) and Long range (GSM, Sigfox, Lora etc.)
If true remote collection is wanted, then you have to find a long range solution like Maturix
Transfer to PC
When datalogger is brought to the office from the casted concrete data has to be transfer to a PC
This process will be done automatically.
From Raw Data to Charts
The raw temperature readings has to be upload to an excel sheet , aligned and charts made
This process will be done automatically.
From Excel to Word to PDF
Charts and data tables transferred to word and made into a PDF
This process will be done automatically.
If you want to also calculate the maturity and strength from the temperature readings, this will involve a lot of manual work and increase the risk of errors.
With Maturix, all the calculations will be done automatically. This means that you can use the temperature readings for the thermal monitoring documentation, but also for strength monitoring. Moreover, as all data the data is automatically stored and formatted in reports in the Maturix in-situ platform. These reports are ready to be exported, in PDF or another format, and printed anytime. The reports are updated every 10 minutes when new data is received and contains both data from the concrete, temperature, and the ambient humidity and KPI’s like maximum temperature, production time etc. Everything done automatically without any use of labor – this is what we call automatic reporting.
Concreting under either very cold or very hot conditions can make concreting extremely challenging. In hot weather conditions, with the temperatures rising, you might risk exceeding the maximum recommended temperature, normally set to 70°C. Having such a high temperature (often in the core) could cause your concrete to:
In low weather conditions, normally defined as three consecutive days of temperatures below 5, the curing speed is very low which means that the strength will be gained very slowly. Moreover, if the concrete falls below a certain temperature the reaction will stop completely and there may cause irreparable damage.
For these reasons, it is very important that you monitor the temperature under both hot and cold temperatures. You could do this with traditional data loggers but these can be very labour intensive and time consuming. A much better option is to use the Maturix system (composed of transmitters and an online platform) to gather your temperature, maturity and strength data, get to see it and create reports in the online platform and even invite external users to view it.
One of the new big concrete trends globally are the new green concrete mixes with a low (at least lower) carbon footprint compared to traditionally used concrete. Some of these new concrete mixes substitute part of the limestone or calcium silicate, present in normal concrete, with clay products.
The new types of concrete often face the challenges of:
The brown-ish color is often “just” an architectural/design challenge, while the reduced internal heat development from the hydration will have a significant impact on the curing process. The reduced heating can be an advantage on very big and thick castings, where you often use retarders and cooling to avoid high maximum and high-temperature variations in the cross-section. But the low heat development can also be a challenge on most castings where you need to achieve a certain early strength fast. Therefore, it is crucial to keep track of the temperature and strength development of the concrete by using sensors.
Cookie | Type | Duration | Description |
---|---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. | |
__Host-GAPS | 2 years | This cookie allows the website to identify a user and provide enhanced functionality and personalisation. | |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. | |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. | |
__hstc | 1 year 24 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). | |
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. | |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. | |
_ga_RLNWVZCCTJ | 2 years | This cookie is installed by Google Analytics. | |
_gat_gtag_UA_49231349_2 | 1 minute | Set by Google to distinguish users. | |
_gat_UA-49231349-2 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. | |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. | |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. | |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. | |
_pk_id.2.8459 | 1 year 27 days | No description | |
_pk_ref.2.8459 | 6 months | No description | |
_pk_ses.2.8459 | 30 minutes | No description | |
ajs_anonymous_id | never | This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. | |
ajs_group_id | never | This cookie is set by Segment to track visitor usage and events within the website. | |
ajs_user_id | never | This cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability. | |
AnalyticsSyncHistory | 1 month | No description | |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. | |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. | |
connect.sid | 1 month | This cookie is used for authentication and for secure log-in. It registers the log-in information. | |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. | |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . | |
cookielawinfo-checkbox-analytics | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . | |
cookielawinfo-checkbox-functional | 1 year | The cookie is set by the GDPR Cookie Consent plugin to record the user consent for the cookies in the category "Functional". | |
cookielawinfo-checkbox-necessary | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Necessary" category . | |
cookielawinfo-checkbox-others | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Others". | |
cookielawinfo-checkbox-performance | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Performance". | |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. | |
debug | never | No description available. | |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. | |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. | |
hubspotutk | 1 year 24 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. | |
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. | |
lang | session | LinkedIn sets this cookie to remember a user's language setting. | |
li_gc | 2 years | No description | |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. | |
loglevel | never | No description available. | |
loom_anon_comment | session | No description available. | |
loom_referral_video | session | No description | |
NID | 6 months | NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads. | |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. | |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. | |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. | |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. | |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. | |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. | |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. | |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. | |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. | |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
__hstc | 1 year 24 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_RLNWVZCCTJ | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_49231349_2 | 1 minute | Set by Google to distinguish users. |
_gat_UA-49231349-2 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
ajs_anonymous_id | never | This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. |
ajs_group_id | never | This cookie is set by Segment to track visitor usage and events within the website. |
ajs_user_id | never | This cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
hubspotutk | 1 year 24 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
__Host-GAPS | 2 years | This cookie allows the website to identify a user and provide enhanced functionality and personalisation. |
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
NID | 6 months | NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_pk_id.2.8459 | 1 year 27 days | No description |
_pk_ref.2.8459 | 6 months | No description |
_pk_ses.2.8459 | 30 minutes | No description |
AnalyticsSyncHistory | 1 month | No description |
debug | never | No description available. |
li_gc | 2 years | No description |
loglevel | never | No description available. |
loom_anon_comment | session | No description available. |
loom_referral_video | session | No description |