Solutions / Software And Services

Oracle / Microsoft / OpenVMS / Integration / C++ / C# / Proprietary & OpenSource Frameworks 

Have provided numerous proprietary solutions that implemented, migrated, converted and updated ERP host and cloud-based business systems. What follows are client case studies employing proprietary SQL Framework solutions where client specifications were either ambiguous or completely absent. These successful project management examples transcend mere scope of work, project management
application, and GANTT/GAP analysis. They evidence a diversity of specialized skills that transformed project/program ambiguity into a manageable matrix of problem, definition, units of work effort, validation, documentation and deployment.

Case Brief #3. Extended the TelEnvy Framework to send/receive data from a hosted AWS/EC2 portal to a Mainframe ERP. The client needed to communicate in real-time with the ERP from AWS/EC2. The client requested the solution execute as a middleware between mainframe and the EC2 systems.  

For this project, there was no specification, documentation, scope of work or technology review, and a third- party web-service developer group located in Bangalore India. On the mainframe side was an ERP consultant-programmer. To build an interface required the data clues be inferred from minimal data input/output data elements enumerated in Microsoft Excel worksheet documents. What seemed apparent
was the eventual necessity of the middleware to support the receipt and handoff of data for any number of transaction-sets (derived Excel worksheet documents). Thus, the project scope evolved from a fixed middleware interface between AWS and the ERP to a framework which supported not just AWS but any provider/consumer service on both sides of the middleware interface. The approach leveraged the technologies which I previously developed and incorporated available framework technologies via existing Open-Source libraries. After a considerable search of the Open-Source libraries, I employed data envelopes which had the broadest interface options for SAP and other data stores. Candidate data envelopes from/to AWS support data envelopes created in: SOAP, REST, EDIFACT, FTP, SFTP and flat file. The transaction engine provides for data cleansing and transformation between transaction interfaces in real-time. As such, the middleware deployed was highly agile/adaptable and responsive. The framework was evaluated for transaction processing from AWS/EC2 to systems in Romania on IBM/AS400, and ERPs executing in Central America. Subsequent performance testing revealed the framework could handle any number of simultaneous transaction requests to most ERP host-based systems, and for this implementation achieved sub-second response times for minimal real-time transaction delays.