Many of our clients mention that one key benefit from using the Maturix sensors is the real-time insight into the temperature, maturity and strength development of their concrete. Having this information allows them to do things that they could not before. Such as being able to optimize the use of resources, get insights into their concrete curing, monitor critical spots in the structure, reduce the risk of thermal cracks and create documentation automatically. These benefits have been experienced both by clients doing on-site castings on projects and in precast factories. Below, we have explained more in detail each of the benefits mentioned above:
In recent years, we have seen a huge growth in the use of green concrete, which are concrete mixes with a lower co2 footprint. The general experience is that these concrete types have a much slower strength development as well as a lower temperature increase during the hydration process. This means that if a low carbon concrete cement is used, this will have a significantly lower strength after 1 day of curing compared to a traditional basic cement. This can be extremely critical both on job sites and precast factories where keeping daily schedules and production cycles is key to stay competitive in the market. Some research (Lasse Frølich, Portland Open 2021) shows that the new concrete types have a very limited additional strength development after 28 days. This contrasts with the previous experience with normal concrete types where the strength can gradually develop well beyond the 28 day mark.
These problems can obviously be compensated with use of accelerators and/or adding heating measures to the concrete before casting or in the curing stage. However, the experience obtained working with normal concrete mixes can be difficult to directly apply to these new concrete types. Therefore, it can be beneficial to use sensors to keep track of the curing progress and learn how to get the most out of these new concrete types.
Placing concrete sensors in the concrete structure also enables you to view how the curing is progressing in one or more spots. There are certain places in the structure that cure much faster or slower than the rest. Conventional methods do not provide you with information about these critical spots so you do not know how those are doing. In contrast, the Maturix sensors can be placed anywhere in the structure to keep track of cross sections, corners with low temperature development, temperature outside the castings, strength around hooks, prestressed wires etc. Then, the data about each of the spots can be seen individually, you can see an example of this below:
Low breaks or inconsistent compressive test results are a common problem in the construction industry. There are many standard procedures describing proper handling and preparation of test samples, however, many times the procedure is not done according to the specifications resulting in inconsistent results.
Therefore, when receiving low break results, it becomes difficult to identify what caused the low result. These results could indicate that the concrete mix was not designed well or that the supplied material was not up to the specifications. But it could also have happened because the samples were not prepared or cured properly, they were damaged during transport or the testing machine was not calibrated properly.
All of these potential causes will create a lot of uncertainty in the project as it would become unclear how to proceed next, wasting a lot of time waiting and investigating the different possible causes. In contrast, if sensors are placed in the structure, it becomes possible to track the progress continuously and instantly detect if something is not going well. Then, if a low break happens, you will have a much richer information of what might be the cause.
Keeping track of the curing process with the Maturix sensors enables an optimized:
The cement content in the concrete is one of the big determinants of the Co2 footprint. Even a small reduction in the cement content will enable a meaningful Co2 footprint reduction. Using the concrete sensors’ data in conjunction with an ambient monitoring enables you to:
Thermal cracking can be one of the most challenging effects to manage in concrete. The risk of cracks and defects increases when the concrete is cured under extreme environments, which might be the case in very hot or cold weather, when producing special concrete elements, or in mass concrete applications.
In many of these applications, concrete simulations are made beforehand in order to design the structure correctly and choose the appropriate concrete mix. However, these simulations might be inaccurate, as several factors such as the ever-changing weather conditions can be hard to predict in advance.
Constant monitoring on-site with the maturity method can provide more precise data about your in-field concrete. Some customers of Maturix even monitor their cooling systems to stay in full control allowing them to always deliver concrete works of excellent quality.
Large concrete jobs like infrastructure, mass concreting, high rises, damps or other utility structures do often have specific requirements for thermal monitoring. Embedding sensors enables automatic documentation, and a lot of labour hours can be saved compared to using a traditional data logger. In Maturix we call this Documentation as you build.
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 |