Hind Sight

Question

What is your opinion?
"Looking back, what’s the most important lesson you learned while setting up new modules—something you wish you had approached differently before launching?"

Tim.Mowery · Answer

You can replicate your connections to your test environments to various other systems even if it is SAP or oracle.   Those systems should have non production environments that allow you to load and push data to test these types of connectivity and verify things are set up.

Thank you for the feedback

Jainz.Jose · Answer

Looking back to our early days, i would have recommended myself to take up a live project in the control module at that time and just really explore all the features control had, We did take a live Project but by then we have taken serval months in each module, even now im finding cool features which if knew earlier would have saved a lot of lead time, but regardless nothing beats the experience knowledge that you get from these production environments which we just cannot replicate from tst environment like SAP integration, Payroll, Power bi..etc..

Tim.Mowery · Answer

Here is my two cents.

In my experience with InEight, we began our journey by implementing the Work Packaging module. However, when we later introduced the Estimating module, we faced several challenges. One of the biggest lessons learned was that the SaaS Estimating module operates with its own “library.” When we attempted to connect it with the next module—Control—we quickly realized that the decisions made during the Work Packaging implementation had a direct impact on Estimating, and those choices could not seamlessly transfer to Control.

For example, creating an original budget from an estimate requires that the core products—Estimate, Control, and Work Packaging—share consistent “dictionaries.” Without this alignment, critical data such as units of measure or tagged fields cannot flow cleanly from Estimate into Control. This experience taught me the importance of building consistency across modules from the very beginning, rather than trying to reconcile differences later.

I also recognize that this process will continue to evolve as the various modules become more integrated. That said, one key takeaway is the importance of being fully aware of how modules and data connect (Data map)—and identifying which elements are critical to closing the historical data loop for your company!