The mandate was that no coding changes were to be made to any of the 40 existing applications…
The mandate was that no coding changes were to be made to any of the 40 existing applications connected to OES, and that the user interface and functionality would remain completely seamless to the current OES services. In other words, an end user should not see any difference before or after the implementation of PlainID. Additionally, the solution would need to be be fully functional in production prior to the OES contract expiration date which was a fairly tight time window.
Leveraging the PlainID dynamic policy engine, wrappers were developed for both Java and…
Leveraging the PlainID dynamic policy engine, wrappers were developed for both Java and .NET based applications to replace the existing authorization wrapper solution. This eliminated the need for applications to make any code changes beyond updating properties files to support the transition. Additionally, Python scripts were developed to automate the migration of policy data from OES to PlainID. The PlainID policy design model reduced policy count for applications by up to 95%. An example of this was a loss mitigation application that was supported with over 900 legacy OES policies. PlainID policies accomplished the same result with just forty dynamic, fine-grained, real time policies.
We assisted the customer with all facets of testing, including unit, system, integration and performance testing of the new PlainID authorization service. Prior to redirecting applications to PlainID in production, PlainID and CTI Global worked closely with the client applications teams to ensure all application policy data was fully functional and met the performance criteria. In addition to the technical work, PlainID and CTI Global provided training sessions for application teams as new users of the PlainID system. Throughout the engagement, ongoing training, knowledge transfer, and mentoring was provided to the client team responsible for the on-going support and expansion of the new PlainID system. Developed customer specific operations documents/run book.
All applications were successfully migrated from OES to PlainID in the desired time period and were…
All applications were successfully migrated from OES to PlainID in the desired time period and were… launched on time into production. With OES license, support and maintenance costs of over $2M per year, an enormous savings was realized by implementing the PlainID Solution.