Every project is unique, which makes prediction of its future hard. We developed the Nodes & Links’ Opportunity feature to address this challenge: predicting the future of your project without relying on generic databases that underplay the uniqueness of your project. We use your project’s schedule updates to understand your performance and give you a realistic prediction for all future activities.
Nodes & Links’ Opportunity feature is twice as accurate in predicting the future compared to existing methods (and twice as robust against optimism bias).
Predicting your project’s progress by using past databases of other projects has limited applicability. After all, even constructing the exact same project twice will still involve different teams (and equipment), which inevitably drive differences in future performance. Once you start taking into account additional scope peculiarities, unique sites and contracts, your project’s uniqueness becomes even more evident.
This is why we developed the Nodes & Links’ Opportunity feature — a new way of predicting the progress of your unique project using updated schedules from your project only.
Nodes & Links’ Opportunity uses your project’s schedule updates to understand your performance to date, and uses it to give you a realistic prediction for all future activities and WBS.
Therefore, every project created in Nodes & Links has its own, tailored prediction model.
Nodes & Links’ Opportunity relies on a combination of peer-reviewed technology and cloud engineering to deliver predictions straight out of the box — no complicated integrations and large data uploads needed!
The AI uses your existing schedule to learn your performance across the different kinds of activities that you have completed up to now. It then looks into the future activities and updates their expected duration based on the learned performance. That learning is applied in a way that takes into account the similarity between past and future activities.
Today, project teams already update their schedules (and future activity completion dates) to reflect the project’s up to date performance. So the challenge is, who can make better predictions for the future plan based on the up to date project performance - the Human or the AI?
We look at the completion dates from activities that have now been completed, as found in later schedules from the same project. We compare those completion dates with the predictions and assess who was more accurate at their prediction — the Human the AI.
We repeated the challenge across 100s of different projects, from energy and construction to aerospace and defence. The result? The AI is twice as accurate than a Human. In addition, the AI is twice as robust against optimism bias, compared to a Human.
Let’s dive into a live project!.
As an example, let’s see focus on this rail project, with a planned duration of 640 days.
For this example, we first use a schedule where 47% of the work has already been completed - this is our training data set and is the only input for our AI (see technical note). This schedule already includes the project’s team prediction about the future plan, based on the work already completed. Let’s dive into a live project!
We then use a later schedule from the same project, where 73% of work has now been completed. This means that there is 73%-47%=26% of additional work completed compared to the training schedule. Let’s dive into a live project!
We can now treat this 26% of additional work that has been completed as our ground truth, and assess the accuracy of the Human prediction vs the AI prediction. In other words, we can now compare the project’s team prediction (which was already included in the training schedule) with the AI’s prediction which learned the project’s performance from exactly the same schedule as the Human. Let’s dive into a live project!
The AI is twice as accurate in predicting the completion date of activities and twice as robust against optimism bias. Accuracy is measured using the number of activities that have been correctly predicted to finish. Optimism bias is measured using the number of activities that have been optimistically predicted to finish.
The figure below showcases the results for this rail project. These results are representative across our entire database with 100s of live projects.
Most Machine Learning techniques require tons of data to train their models in order to make predictions. Our proprietary, peer-reviewed technology gets around this hard constraint by unlocking accurate predictions using your project's schedules only.
This means that effectively, every project created in Nodes & Links has its own, tailored prediction model.
At a high level, our technology is multifolded and relies on the following steps.
Once the first schedule is uploaded, the AI model will first group activities in the past (completed up to the Data Date) and future (rest of activities).
Focusing on the past activities, the AI model will first (1) classify similar activities together; in this case, similarity is computed based on a wide range of parameters that take into account context (like WBS assignment and resources), time (like float and time stamps), and connectivity (like paths and embedndess). It will then (2) assign performance rates on each of these activity classes. These performance rates are weigthed ratios of actual vs expected performance.
The AI model will now focus on the future activities, by first (3) classifying them in a way similar to Step 1, and then will (4) revise the duration of these activities by weighting their similarity to the classes in Step 2. Once completed, we then enirch the output of this AI model with Monte Carlo simulations to assess the impact of the performance rates (and to get convergence).
These steps are repeated every time a new updated schedule is uploaded, which means that the AI model is continuously updated with the latest information. The entire process on a 50k activity schedule takes just a few minutes.
In this way, you can rest assure that any project your upload on Nodes & Links gets a tailored prediction model that takes into account your project's unique nature.
Cookie | Duration | Description |
---|---|---|
li_gc | 6 months | Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. |
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 |
---|---|---|
_calendly_session | 21 days | Calendly, a Meeting Schedulers, sets this cookie to allow the meeting scheduler to function within the website and to add events into the visitor’s calendar. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | Facebook sets this cookie to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising after visiting the website. |
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gcl_au | 3 months | Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services. |
_hjSession_* | 1 hour | Hotjar sets this cookie to ensure data from subsequent visits to the same site is attributed to the same user ID, which persists in the Hotjar User ID, which is unique to that site. |
_hjSessionUser_* | 1 year | Hotjar sets this cookie to ensure data from subsequent visits to the same site is attributed to the same user ID, which persists in the Hotjar User ID, which is unique to that site. |
AnalyticsSyncHistory | 1 month | Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie. |
cb_anonymous_id | 1 year | Clearbit sets this cookie to track page views and traits for Clearbit. |
cb_group_id | 1 year | Clearbit sets this cookie to track page views and traits for Clearbit. |
nQ_cookieId | 1 year | Albacross sets this cookie to help identify companies for better lead generation and more effective ad targeting. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
Cookie | Duration | Description |
---|---|---|
_rdt_uuid | 3 months | Reddit sets this cookie to build a profile of your interests and show you relevant ads. |
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
cb_user_id | 1 year | Clearbit sets this cookie to collect data on visitors. This information is used to assign visitors into segments, making website advertising more relevant. |
li_sugr | 3 months | LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant. |
NID | 6 months | Google sets the cookie for advertising purposes; to limit the number of times the user sees an ad, to unwanted mute ads, and to measure the effectiveness of ads. |
VISITOR_INFO1_LIVE | 6 months | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
VISITOR_PRIVACY_METADATA | 6 months | YouTube sets this cookie to store the user's cookie consent state for the current domain. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt.innertube::nextId | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
__tld__ | session | Description is currently not available. |
_cfuvid | session | Description is currently not available. |
_cio | 1 day | No description available. |
_cioanonid | 1 year | Description is currently not available. |
_lfa_test_cookie_stored | less than a minute | Description is currently not available. |
cbtest | 1 year | Description is currently not available. |
debug | never | No description available. |
m | 1 year 1 month 4 days | No description available. |
nQ_userVisitId | 1 hour | No description available. |
pfjscookies | 1 year | Description is currently not available. |
site_identity | 1 year | No description available. |
sliguid | 1 year | No description available. |
slireg | 7 days | No description available. |
slirequested | 1 year | No description available. |