2. Product Objectives
• Make Track™ easier to use; reduce contract service costs
– For the Owner
• Enterprise deployment/easy to use ERP integration
• Standardization; optimize contractor selection/utilization
– For the Contractor
• Remove redundant effort
• Many-to-Many connection
• Improve Project Control
– Project estimating and forecasting
– Analytics, Alerts
October 24, 2012 Management Controls, Inc. — CONFIDENTIAL 2
3. Improve existing features/modules
• Labor, Equip.& Materials • ERP Integration
• Lump Sum • Track Estimating
• Unit Price • Track Forecasting
• Analytics
October 24, 2012 Management Controls, Inc. — CONFIDENTIAL 3
8. Project control Turnaround (Day 1)
2 Years 1 Year
Turnaround (T/A) 30 + days
(prior to T/A) (prior to T/A)
Turnaround Estimating Plan & Schedule Turnaround Cost Control Turnaround Forecasting
P6 Gate System
Forecasting
Estimating Scheduling
Track™ • Original Estimate
• Project • Commitments
• Scope / B.U. SAP • Actuals
• Equipment List Track Cost Control • Contingencies
• Activities • Contractors • Cost Impacts
• Norm Direct Hours • WO/PO/WBS • Productivity
• Estimates Planning • Location/Site • EV / %complete
• What-if Scenarios Contracting • Project • Forecast
• Final Estimate • Actuals • Reports
Planning • Direct Hrs.
• Indirect Hrs.
• Cost Objects • Activity
• Work Orders • Contract
• Purchase Orders • Specific $$
• WBS / CBS • L, E, M
• Contracts • T&M, LS, UP
• Original Estimate • By Shift
• SEs & TCs back to SAP
October 24, 2012 Management Controls, Inc. — CONFIDENTIAL 8
9. Product strategy 2013 2014 2015
Software as a Product: Track v6.3 Track v6.3
Track v6.3 Track v6.4
• Perpetual License (or lease)
• ‘On-premise’ installation OR
• Hosted (SAVVIS) Estimating
Continue Track 6.2, 6.3, 6.x series
• Provide clients with “on-premise” solution
Forecasting • Some clients may prefer to stay on current
Target Market: or older versions
• Existing customers • Continue product enhancements
• Traditional large customers • Continue offering and building out a
SAP & Maximo “hosted” solution (SAVVIS)
• SAP/ERP customers Integration
2013 2014 2015
Software-as-a-Service:
• Scalable for smaller markets
• Multi-Tenant Architecture 18-24 month development cycle Track v7.0
• New functionality (e.g. Smart Contracting)
Target Market:
• Early “Cloud” adopters Focus on Track Future releases
• Small-Midsize customers/markets • Many to Many (multi-tenant) – Track for Contractors
• Contractors • Other possibilities – TrackMobile, Asset Tracking
9
10. Architecture (current)
Contractors
Standard remote access
for contractors Track Owners
or Contractors
Citrix
Track v7.0
Track v6.2
Track v7.0
Track v6.2
Stand- “Hosted”
“On Premise”
Alone
SAP ACS Contractor B
Interface Interface
Contractor A
Owner B
ACS Owner Systems
SAP ACS
Owner A
Interface Interface
Owner C
Owner D
ACS
October 24, 2012 Management Controls, Inc. — CONFIDENTIAL 10
11. Architecture (Future)
Contractors
Contractors
Standard remote access Single point sign on for contractors to
for contractors not access multiple owners Track Owners
licensed for Track
Connector or Contractors
Citrix
Multi-Tenant
Connector
Connector
Track for
Track
Track v7.0 Contractors
Track
Track v7.0 Functionality
Stand- SSL “SaaS”
“On Premise”
Alone
SAP ACS Contractor B
Interface Interface
Contractor A
Owner B
ACS Owner Systems
SAP ACS
Owner A
Interface Interface
Owner C
Owner D
ACS
October 24, 2012 Management Controls, Inc. — CONFIDENTIAL 11
Editor's Notes
As Track has grown with added features and functionality we realize that it has become increasingly complex. Our over arching objective has always been to make Track easy to use, and in a production environment user profiles that limit what tasks a user can perform help with this however we are also going to look at improved workflow management to help with usability. Along with this, we are going to continue to provide new features and benefits will help control and reduce contract service costs.For example for the owner we want make to help make enterprise deployments are seamless and provide smooth integration with ERP systems. We will continue to add features like the easy button that automatically adds missing ins/outs, or report scheduling, or per diem-handling. We want to support Owner efforts for standardization of contractor management practices across sites. We are going to build tools that will help in this effort and in fact we have session running tomorrow about Labor Rate Management that you may be interested in.For the contractor we want to reduce redundancy where possible with contractor focused functionality. In the past, when contractors had to enter allocations into their own system and then re-enter this information in Track we removed this redundancy by enabling this information to be imported and then compared to the calculated net billable hours in Track. For contractors that work with multiple owners that use Track it can be very laborious to constantly login and logout of each Track system to perform their daily tasks. With our new architecture for Track 7.0 we will eliminate this by enabling contractors to login once and view all the owners that work with through a drop down. I will be discussing our planned architecture later during this presentation.We are improving Project control with added tools to help with Turnarounds and Capital projects with estimating and forecasting and I will provide an overview of these in a upcoming slides. In addition to these tools we are looking to improve our analytics and alerting.
Our goal is to continue to build on our existing feature set within Track v6.x. With Labor, Equipment and Materials we are looking at technology that may enable you to track where equipment is located and if it is being used though asset tracking. In our session tomorrow one our technology partners will be demonstrating some of this capability. With ERP integration we have already release our SAP Integration Module and will be adding integration with Maximo. As I mentioned already Track Estimating and Forecasting will covered in a few minutes.
Designed for those with budget responsibility or project teams we have created our analytics functionality in Track. You can view this as analytics or as dashboard and what we are trying to do here is push information out to decision makers. We have 9 analytic views and here are a few examples. On the top left chart here we are looking at Labor, Equipment and Material spend by contractor, you will notice these red/green thresholds that you can set to help with your analysis. You can set a target level and a ceiling level and then look where things are moving away from the norm. In this case this bar has exceeded the ceiling in September and you can drill down to perform root cause analysis as to why this occurred.
In terms of improving project control you may not be aware of the additional tools we have for Turnarounds or large capital projects. Track Estimating on the left of this diagram is used for early stage budgetary estimating of scope, activities and costs for work list items. It designed to be used 18-24 months before the start of the turnaround. The output of this tool would then feed a system such as Primavera, where you would combine this estimate with all the other information in Primavera to build an Original Estimate. Once the Turnaround begins you are familiar with Track and it’s capabilities, however what you may not be aware of is Track Forecasting. This product which you may have heard of as PCF will help a cost engineer compare the original estimate from Primavera, the commitments from SAP and the daily actuals from Track. It will make allowances for contingencies such as generators not included in the original estimate, or for cost impacts such as a turbine that has just blown up, or flooding in the refinery. All this will help evaluate productivity, earned value analysis and ultimately with a forecast. The output from Track Forecasting will then feed the Estimating tool and help determine a better estimate for future Turnarounds
Before I discuss our product strategy, I want to address the people here that attended last years user’s conference. Last year we had plans very similar to what I am about to describe and you may be asking yourself why aren’t we further along. Good question. Last year we began working with a client with an enormously large site. For example, most of you in the audience have sites that process $100MM per year though our software. This one client site was processing this amount and more per month though Track. At this point we decided to step back and allocate dev resources to make sure our software was optimized to handle the largest daily volume imaginable. So with that said, let’s take a look at the top half of this slide. We are going to continue to build our on premise and hosted Track 6.x series. Presently we are at Track v6.2 and as we move to 2013 we will release Track v6.3 that will include new features such as ad-hoc reporting. Allowing for user customization of reports. We will also be enhancing our Estimating and Forecasting products, along with adding a Maximo integration module. This development plan will continue out into 2014, 15 etc. Parallel to this on the lower half of this graphic is our plans to re-architect Track. This architecture will multi-tenant. You may ask what does this mean. The best way I can describe this to you is to imagine an apartment building. There is a security guard at the door and there are many tenants inside the apartment. Only those with keys can enter their apartment, and all these tenants are sharing the resources of the building such as the plumbing, electricity etc. That is what I mean by be a multi-tenant architecture. So, over the next 18-24 months we will be redesigning Track and build into it the same functionality as the Track v6.4 or Track v6.5 that will be shipping at that time.So what does that look like …
Presently with Track we have the option to install our software on-premise or in our hosted environment. On premise users can login securely either remotely or behind their firewall and run Track and access their data. In our hosted we have owners today that are logging into their own Track environment that is integrated with their SAP and to multiple ACS systems.
For Track 7.0 everything looks very similar to what we have in place today. Both on-premise and hosted. The main difference is that Track v7.0 is multi-tenant and we have added these interfaces called Track Connectors. In the on-premise environment nothing really changes for contractors that wish to only work with one owner. However for contractors with multiple owners running Track we now have this Track connector that they can license that will allow them though a single login to view all the owners they are working with. They will also benefit from additional functionality that we will build into Track that is tailored for contractors. If the owner agrees, we can also install a connector at the on-premise location to enable these licensed contractors to connect to this Track installation. Everything else, with SAP integration and ACS connectivity works as smoothly as it does today.Thank you for your time today. I hope this was informative. Any questions?