Trabajador de construcción

FAQ

Frequently Asked Questions

Solution

Is Beawre a documentation or program management tool?


No. Beawre solution provides continuous risks management on top of your existing workflows. Beawre's solution connects to your existing documentation management tool, program management tools and others, extract data our of those and brings value on top of your existing tools.




What tools does Beawre's solution replace?


No. Beawre's follows a non-intrusive approach. We offer a flexible solution that connects to your existing ecosystem. We never force our customers to change their existing tools or workflows. Through the notion of evidence collectors, we can connect to any of your tool (p.e. using APIs) but also reading through Microsoft Excel spreadsheets or any other Office 365 format, or reading unstructured data, such as that scanned from e-mails. We do not change your workflows unless you decide to do it. Our solution adapts to any existing workflow and provides your teams information to understand the risks related to these workflows.




What is the benefit of using Beawre's solution?


Our solution helps your organization to reduce project delays in real-time and budget overruns. It also improves your negotiation capacity and reduces the number of claims by providers and customers due to increased awareness and better data insights.




What is the ROI generated from using Beawre's solution?


Our solution helps teams working in construction projects to anticipate risks related to different business processes performed during the execution of the project and, thus, reduce project delays and overspending. The ROI produced by our solution is mainly based on 3 main pillars:

  • Reduction of project delays: our solution allows for anticipating unwanted incidents such as a document being late or a permission not being issued in time, to give some examples. Our solution minimizes reaction time in decision making.

  • Better capacity to negotiate with providers and client: information collected from monitoring business allows understanding process performance and where bottlenecks happen if any. In particular, this allows decision makers to know who is the responsible for delays, improving their capacity to negotiate with customers and providers.

  • Total team staff optimization: also, because of the information collected from business processes performance, it is possible to understand potential bottlenecks created by your own resources, allowing you to optimize your team’s organization.

Our solution also generates other benefits. For instance, a better-informed decision making can generate additional benefits such as savings related to removing IT infrastructure costs and mid-/long-term benefits from information centralization, etc. All these estimations are extracted directly from the opinions of our current customers through many interviews.

Depending on the size of the project and the scope of application, our technology can produce savings up to 3 million euros per year.

For instance, in the following table we show the potential economic savings lost with the lack of real-time risk management related to documentation submittal, review and approval:





How does a project/operations director benefit from using Beawre's solution?


Project director/manager roles can now mitigating risks related to different workflows much faster. For instance, they are aware of risky situations much faster and they have data to support their negotiation with subcontractors and the client. With this, they can avoid many budget overruns and delays. In general, project directors are now able to understand the project health and the level of risk related to the program, documentation, consents or contracts, because they can now transversally analyze information across the different tools used by their staff in the project.




How does a documentation controller suffer from lack of workflow control?


Thanks to our solution, documentation controlers can now make sure documents are ready in time to avoid program delays and budget overruns, and thus immediatly detect any anomalous situations that may jeopardize this objective. Thanks to this: - They now have mechanisms to predict documents approval workflow evolution and to understand in advance what are the documents that are most likely to generate significant delays. This is provided thanks to our AI-based predictive capabilities. - They can now focus on those aspects that are really important, as our tool helps them prioritize work based on risk levels and avoiding problems related to excess of information. - They have means to immediately understand how changes in the program affect requirements on documentation in real-time avoiding many hours of meetings with their colleagues to figure those impacts out. Our solution automates many of their processes involving manually data updates. This avoids many errors introduced manually. Also, data is updated in real-time, removing delays which may create disruption and confusion among team members. In general, with Beawre's technology documentation controllers gain overall visibility to understand what are the most risky situations and they can decide where to focus, to anticipate different unwanted incidents related to documents.




How does a project planner benefit from using Beawre's solution?


Thanks to Beawre's solution, project planners have easy mechanisms to understand how the continues changes made to the program will affect requirements on documents, consents or other project assets. By having visibility on the actual impact of program changes on other assets, now they can act in a smarter way and help the organization avoid delays and budget overruns.




How does Beawre solve interoperability issues?


We gather data from different and non-interoperable digital tools and combine it in our solution. Think about it. Very often your program management tool does not exchange information with the documentation management tool. Or maybe you keep the information about consents or documents in an spreadsheet that you need to update continuously. In many cases, the information in your spreadsheet is not coherent with the actual information in some of your other management tools. This does not only generate confussion and makes your team waste time, but it also makes it very hard to transversally analyze data. With Beawre solution, all these issues are solved, because we integrated all these fragmented data in our solution and we keep it update it by automatically consuming and integrating data continuously from the different tools in your ecosystem. Even if you are using a software platform that integrates several tools, you will always need to use other tools (maybe because they are imposed by the client or other partners in the consortium or maybe because you still keep control of some aspects of the project through e-mails or through spreadsheets).




How does an engineering manager benefit from using Beawre's solution?


With Beawre's solution engineering or technical managers can now make sure documentation will be ready in time to avoid program delays and budget overruns. Using our technology: - They can predict documents approval workflow evolution and understand in advance what are the documents that are most likely to generate significant delays. They can do this thanks to the fact that our solution automatically explores subcontractors performance in the past, and their performance processing a particular type of document, learns from this past data and predicts what will happen with new workflows. - They can now easily understand the workload in the upcoming weeks. - They can now focus on those aspects that are really important, based on risk estimation. Avoiding unnecessary communications and excess of information. - They can immediatly see how changes in the program affect the level of risk related to documentation, consents, etc, avoinding hundreds of hours in meetings with their colleagues to capture the status of the project. In addition, many manual tasks are automated eliminating human errors that may jeopardize data coherence. Beacause data is now updated in real-time, delays are removed and, with them, disruption and confusion among team members. In general, now technical managers have overall visibility to understand what are the most risky situations and it becomes easy for them to decide where to focus, to anticipate the worload in the next few weeks and different unwanted incidents.




How does a consent manager/controller benefit from using Beawre's solution?


With our solution, consent managers/controllers can now predict whether consents will be ready in time to avoid program delays and budget overruns: - They can now predict the consents or permissions that will generate significant delays, as our solution allows them to understand third-parties performance in the past, and performance processing a particular type of consent. - They can process information in a very easy way, allowing them to focus on those situations that represent a higher risk. - They have a good visibility to understand the actual status of documents required to request consents and predict what documents may be late and cause problems, without having to spend ours with engineers and doc controllers. - They can now understand the current level of risk of each consent to be late in real-time, even when the program may be continuously changing, without investing large amounts of time they can usually not afford asking to other colleagues. - They can control the workload in the upcoming weeks. In addition, thanks to Beawre's solution, they increase the level of automation. For instance the status of a consent can be changed automatically and in real-time, without having to update spreadsheets manually, avoiding errors that may jeopardize data coherence, disruption and confusion amond the team members. With Beawre's solution, consent controllers/managers gain overall visibility to understand what are the most risky situations, making it easier for them to prioritize and anticipate the worload in the next few weeks and different unwanted incidents.





Onboarding

How long does it take to deploy Beawre's solution in a new project?


The answer depends on the construction project and the tools they use in the project. Onboarding a new project to use our solution may take from a few weeks to a couple of months. Length of this process depends on the number of digital tools we need to connect to, the mechanisms we need to use to connect to these tools, etc. Length may also depend on the scope of the use of our solution (if you use it to control risks related to one or more assets: documentation, consents, contracts, etc), the number of workflows you want to monitor, etc. Finally, the size of the project is also relevant. Large projects tend to have more staff members involved in the workflows, a more complex digital ecosystem, etc.




Does my staff need to define the workflows and risk?


No, Beawre does that for you if you need us to. We organize a couple of interview sessions with the relevant actors in your teams to understand how workflows work and to get access to the relevant documentation explaining how those workflows work, if any. Then we create the workflows in our solution using our own editor and validate them later on with your teams. If you already have your workflows in a digital format, we consume them automatically and load them in our solution. Analogously to workflow definition, Beawre's team also facilitates one or two sessios with your team to understand the most common issues related to the workflows to be controlled. Then we use our more than 10 years of experience in risk management (RM) to apply RM methodologies to identify risks, define mechanisms for continuous risk assessment and define the evidence in your system we will use to perform this assessment. Of course, if you prefer someone in your organization to digitalize workflows or identify risks through our solution, you can also do it using our online solution.




Can Beawre's solution be deployed in a project that is already running?


Yes, we have onboarded our solution in the middle of the execution in large projects. In many cases, during the planning, design and construction phases, teams realize they have understimated the need for resources, or the complexity managing non-physical assets of the project such as the documentation or consents. In these situations, they realize they lack better control of their workflows and this generates delays and budget overruns, and then they decide to deploy Beawre's solution to get better control on their projects. Since our solution does not force them to modify their tools and workflows, you can onboard it at any time. Also, because we follow a pay-per-use model, you can always start and stop using our solution at any time, giving a lot of flexibility to our customers.




I do not use many digital management tools, can I still use Beawre's solution?


Yes, if you just use a shared repository to upload your documents but you do not use an Electronic Document Management System (EDMS) or you use an Excel spreadsheet to control documents or consents, you can still use our solution. Through our evidence collectors, we are able to connect to document repositories such as Microsoft Sharepoint, Excel spreadsheets or others and monitor activity. In this way, we know when new documents are created or a document is modified, when consents chage their status, etc. and we can also deduce what is happening in your workflow. Besides, we can also help you control if your staff classifies documents properly and warn you when we automatically detect that they may be misclassified.




How does Beawre identify the main risks in a workflow?


Beawre's team has more than 10 years of accumulated experience in continuous risk management. We have internally developed continuous risk management methodologies on top of workflows. Based on our experience analyzing workflows in construction projects, we have the ability to identify risks in those processes and validate those risks with your teams.




Our workflows are already digitalized, can Beawre consume those automatically?


Yes, our solution will consume BPMN-based workflow definitions. In the case you have ditigized your workflows using a different formalism, we can also build connectors to consume from any other format you may use.




Our workflows are not digitized, can I use Beawre's solution?


Yes, we never assume that workflows in a construction project are digitized. Part of the onboarding process includes the digitization of the workflows the risks of which we want to control. However, if they are already digitized, we can consume them automatically.




What happens during the onboarding process?


The onboarding process consists in 3 main steps: - identifying the workflows on top of which we need to manage risk and loading them in Beawre's solution - identifying the relevant digital tools in your ecosystem that will serve as data source for Beawre's solution and connecting to them - identifying risks related to the identified workflows and setting up the monitoring mechanisms in Beawre's solution to control those risks





AI & Data

Where does Beawre's solution obtain data from to train models?


There are two main sources we get data from: - Repetitive workflows: because we are monitoring workflows that may happen hundreds or thousands of time per month, your project immediately starts generating very valuable data. We consume informantion about how workflows execute to predict what is going to happen with a new workflow as we keep collecting new evidence. - Past projects: many customers facilitate us access to data from previous projects so that we can reuse information from those past projects and train our models even better.




Do you share data among different customers?


No, never. Data we manage is stored using the highest security and privacy standards. We understand construction projects data may be very sensitive and thus confidential, specially if related to risk status. We use different instances of our solution using containerization technology, so that data from two different organizations can never be mixed up in the same container. However, we can share data among different projects if the organization is willing to, to use data from past projects to predict what is going to happen in an ongoing project, and enabling an effective mechanism to leverage lessons learned automatically.




Can we reuse data from past projects?


Yes, organizations may give us access to data from past projects and we can also use those data to train our models to make predictions in ongoing projects.




Can I use Beawre's solution if this is the first project and I cannot reuse data from previous projects?


Yes, that is not an issue. We collect evidence from repetitive workflows in your projects. Probably, after the first weeks, you have already processed hundreds of documents and consents. We collect this information immediatly and continuously and keep training models automatically. Every time you execute a new workflow your models evolve and prediction accuracy improves. And this happens very fast to generate valuable information very soon.




How often does Beawre's solution retrain AI models?


Beawre's solution retrains models continuously. Almost every time a new workflow is finished, we add this information to our models. Model training happens in the background and it is completly transparent to the user.




Is Beawre the owner of the AI technology used in the solution?


Yes, Beawre has developed 100% of the AI technology used in our solution. We have created novel algorithms and techniques to predict workflow evolution and automatically assess risks on top of these workflows.




My data is highly confidential and I prefer not to use the cloud, can I still benefit from Beawre's technology?


Yes, our technology is based on the use of containers using Kubernetes. Our solution can be deployed in a proprietary server as well as in a cloud server, without any additional effort or reconfiguration. This way, highly confidential environments such as those related to nuclear for instance, can run our solution without having to use cloud solutions. In general, unless imposed by regulations, we always recommend to move to the cloud, both from a security and a financial perspective. It is not always easy to guarantee the same level of security in a server managed by your organization, compared to the security measures implemented in cloud servers from top providers.




What is Beawre's philosophy in terms of applying AI techniques?


AI by itself may just be a buzzword. From clustering algorithms to the most sophisticated Deep Learning techniques, they all fall under the AI category. We adapt the AI algorithms to each customers needs. For many of our customers, explainability is essential. If they make a decision based on the level of risk they need to understand how this was computed. Some other customers prioritize accuracy over explainability. In other contexts, the amount of data may be large and more sophisticated AI techniques, like transformers, can be used to learn aspects of your ecosystem. In some other cases, less data is available at the beginning and you need to resort to statistical approaches first, and let our solution to automatically switch to more sophisticated options when enough data is available to train better and more accurate models. We have decades of experience in this field, let us help you understand the best approach for you.




Can we easily explain decisions made on predictions beased on AI?


For many of our customers, explainability is essential. This means that if they make a decision based on the level of risk calculatd with our solution they need to understand how this was computed to justify decisions in the future if required. Not all AI algorithm guarantee explainability. Some techniques may generate very accurate predictions, but they behave as blackboxes making it almost impossible to justify certain predictions. In certain contexts, these techniques are not suitable. At Beawre, we have developed explainable AI techniques that make it possible for you to understand where recommendations come from and to justify decisions when necessary.





Service and fees

What is your pricing model?


Beawre’s solution is developed in modules. Each module represents a vertical application of our technology. Our fee is structured per project and module.




Is it possible to activate and deactivate modules at any time in the project?


Yes, you can activate or deactivate modules at your convenience, depending on the requirements of the project at any moment.




Is there any limitation in terms of number of users per project?


No, licenses always allow for an unlimited number of users per construction project.




Can we benefit from any discounts?


Yes. you can optionally choose to benefit from annual commitment discounts. At the end of each full year, you will be able to indicate if you want to keep the annual commitment option. Beawre is also open to negotiate discounts for multi-year commitment.




Can license fees be paid yearly?


In general, fee payments are executed monthly. In the case annual commitment is selected, license fees can be paid monthly or once per year at the beginning of the period.




What does the license fee include?


License fee includes the right to access and use our solution.

License fees also include:

  • Continuous improvements and bug fixes.
  • Ability to propose new features or improve existing ones.
  • Annual review of dashboards for improvements and additions.
  • Product documentation in an online Knowledge-Base.
  • 2-hours training session for all users of the tool (session will be recorded and available online).
  • Customer support (includes 120 e-mails per year).
  • Hosting services for IT infrastructure and IT operations services




Where does Beawre offer their services?


Beawre business model was born with an international focus from the very beginning. Our software is developed taking into account globalization and localization principles from the very beginning. Our solution can be offered in any language required by our customers around the world. Beawre offers their solution around the globe.





Challenge

What is the problem Beawre is trying to solve?


Construction projects are like icebergs. The visible part is the onsite physical construction. However, this visible part could never work without the proper management of the non-physical assets of the project such as the project program, documentation, permissions, contracts or quality procedures. Project central offices run, formally or informally, thousands of repetitive workflows to generate, classify, review, request and approve aspects related to these assets.

The execution of these workflows generate risks to projects, which may end up resulting in delays and budget overruns. Today, the construction sector lacks tool to control risks in these workflows in real-time.




Why adopting all-in-one platforms does not solve interoperability issues?


Some companies try to adopt unique platforms with new and interoperable tools. But this does not match reality, specially in large and complex projects, where general contractors work in consortia, and tools are often imposed by the client or other partners in the consortia.

Therefore, data fragmentation and lack of interoperability issues persist.




Can you show me an example of a workflow?


As an example, we show a workflow related to documentation management: a provider generates and submits a document. Then engineers and doc controllers review it. If everything is fine they send it to the client for the final assessment. If it is approved we are done, otherwise we start all over again. When these workflows face issues, they generate severe issues to projects.

There are several questions associated to this workflow that may represent risks. For instance, will the provider deliver in time? Will my team have enough resources to execute each of the steps of this workflow timely? Will my client review the documentation in time? How many times a document will be rejected? Will the whole workflow finish in time so that the related tasks in the program can start when planned? The answer to all these questions may negatively impact the program and budget of the project.




Who suffers from lack of control on workflows?


We help general contractors. There are different actors working in the site office that are involved in those workflows and meet these challenges in their day-to-day work. Some examples are: - Engineering/Technical managers - Consent controllers/managers - Documentation controllers - Project planner or program manager - Project director/Operations director




Why do existing digital management tools do not suffice to control risks in workflows?


Construction companies use e-mail, excel spreadsheets and even physical paper and more and more often different digital tools to control projects and workflows. Many of these digital channels and tools become obsolete and do not allow leveraging smart features including advanced analytics or AI. Besides, very often these tools lack interoperability, making it almost impossible to perform any type of transversal analytics.




How does an engineering manager suffer from lack of workflow control?


Engineering or technical managers own documentation, generated by their own staff or by providers/subcontractors. They need to make sure documentation is ready in time to avoid program delays and budget overruns. They need to face several challenges: - They do not have mechanisms to predict documents approval workflow evolution and to understand in advance what are the documents that are most likely to generate significant delays. The main reason for this is that they do not have effective mechanisms to understand subcontractors performance in the past, and performance processing a particular type of document. - They do not have mechanisms to easily understand the workload in the upcoming weeks. - They struggle to process information as they may receive tenths or up to hundreds of e-mails per day, making it hard to focus on those aspects that are really important. Also, when the workload is high, the number of communications may saturate the capacity of different actors to consume the e-mails from their inboxes, causing further delays. - Program is continuously changing. Every time tasks are rescheduled, that has an effect on when documents need to be ready. The engineering manager does not have means today to understand all these changes in real-time without investing large amounts of time they can usually not afford. In addition, many processes are managed manually, for instance having to change the status of a document in a spreadsheet containing the documentation schedule. Manual updates are prone to errors that may jeopardize data coherence. Additionally, the data is never updated in real-time, but there is a delay which creates disruption and confusion among team members. In general, technical managers lack overall visibility to understand what are the most risky situations and it becomes difficult for them to decide where to focus, to anticipate the worload in the next few weeks and different unwanted incidents.




How does a consent manager/controller suffer from lack of workflow control?


Consent controlers/managers own consent request and approval workflows management. They need to make sure consents are ready in time to avoid program delays and budget overruns. They need to face several challenges: - They do not have mechanisms to predict consents approval workflow evolution and to understand in advance what are the consents or permissions that are most likely to generate significant delays. The main reason for this is that they do not have effective mechanisms to understand third-parties performance in the past, and performance processing a particular type of consent. - They do not have mechanisms to easily understand the workload in the upcoming weeks. - They struggle to process information as they may receive tenths or up to hundreds of e-mails per day, making it hard to focus on those aspects that are really important. Also, when the workload is high, the number of communications may saturate the capacity of different actors to consume the e-mails from their inboxes, causing further delays. - Besides, consents requests require documents to be ready in time. Consent managers do not have a good visibility to understand the actual status of documents and predict what documents may be late and cause problems to to get consents approved in time. - Program is continuously changing. Every time tasks are rescheduled, that has an effect on when consents need to be ready. The consent controller/manager does not have means today to understand all these changes in real-time without investing large amounts of time they can usually not afford. In addition, many processes are managed manually. For instance they may have to change the status of a consent in a spreadsheet containing the consent schedule. Manual updates are prone to errors that may jeopardize data coherence. Additionally, the data is never updated in real-time, but there is a delay which creates disruption and confusion among team members. In general, consent controllers/managers lack overall visibility to understand what are the most risky situations and it becomes difficult for them to decide where to focus, to anticipate the worload in the next few weeks and different unwanted incidents.




How does a documentation controller suffer from lack of workflow control?


Documentation controlers overview any workflows related to documentation management. They need to make sure documents are ready in time to avoid program delays and budget overruns, and thus detect any anomalous situations that may jeopardize this objective. For instance, once a document is validated by the owner, they may need to review and update documentation status through an Electronic Document Management System (EDMS). However, they may also need to upload documents to the client’s independent EDMS, once these have been reviewed internally. Analogously to documentation owners, they may also need to manually change the status of a document in the spreadsheet containing the documentation schedule, once significant progress occurs (i.e. a document is reviewed and accepted internally, or the review from the client is received). They need to face several challenges: - They do not have mechanisms to predict documents approval workflow evolution and to understand in advance what are the documents that are most likely to generate significant delays. The main reason for this is that they do not have effective mechanisms to understand subcontractors performance in the past, and performance processing a particular type of document. - They struggle to process information as they may receive tenths or up to hundreds of e-mails per day, making it hard to focus on those aspects that are really important. Also, when the workload is high, the number of communications may saturate their capacity to consume the e-mails from their inboxes, causing further delays. - Program is continuously changing. Every time tasks are rescheduled, that has an effect on when documents need to be ready. The doc controller does not have means today to understand all these changes in real-time without investing large amounts of time they can usually not afford. In addition, many processes are managed manually, for instance having to change the status of a document in a spreadsheet containing the documentation schedule. Manual updates are prone to errors that may jeopardize data coherence. Additionally, the data is never updated in real-time, but there is a delay which may create disruption and confusion among team members. In general, documentation controllers lack overall visibility to understand what are the most risky situations and it becomes difficult for them to decide where to focus, to anticipate different unwanted incidents related to documents.




How does a project/operations director suffer from lack of workflow control?


Project directors manager roles also participate in mitigating some risks related to different workflows. For instance, discussions and negotiations with subcontractors and the client may require their attention and involvement. Because of the general lack of control in workflows, they just learn about risky situations too late, and they cannot act in time to mitigate risks and avoid budget overruns and delays. Even when they understand the situation before it is too late, lack of data-driven approaches make negotiations difficult and subject to interpretation. In general, project directors are not able to understand the project health and the level of risk related to non-physical assets such as program, documentation, consents or contracts, because they do not have means to transversally analyze information across the different tools used by their staff in the project.




How does a project planner suffer from lack of workflow control?


Tasks in the program depend on documents or consents, for instance. If a set of documents is not reviewed and approved in time or a consent is not approved, certain construction tasks cannot start. Apart from becoming an important source of risk, this also generates a lot of uncertainty in the process related to managing documentation. The construction project program is being continuously adjusted by the project planner, because of the continuous unexpected events occurring in the project. With every change, the deadline established for documents to be ready in time changes, making the control of those cumbersome. When these updates are produced, planners do not have mechanisms to understand how these will affect requirements on documents or consents.