Rimas is an IT professional with 30 years of experience in the field. He has a wealth of hardware experience on platforms ranging from IBM mainframes all the way down to hand-held mobile devices (and everything in between). He is equally diverse from a software perspective with experience developing part of the kernel of one OS, the communications protocols of another OS, middleware, web applications, web services and mobile apps. But most importantly, he is passionate about learning new technologies and applying that knowledge to solve problems.
- React Native
- Web services
|2019 - Present||Senior Consultant||EY (Ernst & Young)|
Currently, Rimas is a Mobile Architect in the Technology Transformation practice of EY Advisory Services where his first client was a large power & utility company undergoing an extensive customer experience and technology transformation.
|2017 - 2018||Technical Consultant||Solstice Consulting|
Rimas worked with two major clients helping to develop innovative high-quality mobile apps in the IoT (Internet of Things) space. He added GDPR support to a native iOS app for a major automobile manufacturer, in addition to many smaller new features to a React Native based app on iOS and Android for a major boat manufacturer.
|2013 - 2017||Mobility Architect / Developer||Baxter / Baxalta / Shire|
As a key member of the Mobility CoE (Center of Excellence) in Shire’s Global IT organization, Rimas fostered the adoption of mobility by consulting with business units on their mobility needs, as well as by architecting and developing several corporate-wide mobile apps. His duties also included mobile application management (MAM) and mobile device management (MDM).
|2011 - 2013||Technical Consultant||Baxter Healthcare|
Rimas was an Integration Architect in Baxter’s Global IT organization working in the Enterprise Platforms department on the Application Integration Platform. The Application Integration Platform was based on IBM’s WebSphere MQ, WebSphere Enterprise Service Bus, WebSphere Transformation Extender, and WebSphere Partner Gateway. The platform was used across all of Baxter for A2A (application-to-application) and B2B (business-to-business) integration.
Rimas’ responsibility was to make sure that the developers who used the platform did so in the best way possible. In order to facilitate this, he defined “best practices” and patterns for the efficient use of the platform. Rimas also consulted with developers during the design and implementation phases of their projects providing guidance based on his years of experience with this set of products and technologies.
|2009 – 2011||SOA Architect||American Medical Association|
Rimas was the SOA Architect at the American Medical Association. Working in the Enterprise Architecture group, he was responsible for establishing a service-oriented architecture (using IBM’s WebSphere Enterprise Service Bus) and for implementing SOA governance (using IBM’s WebSphere Service Registry and Repository) across the entire AMA IT organization.
In this role Rimas mentored the IT operations staff on the maintenance and operation of the IBM SOA product suite. Having defined AMA standards and “best practices”, he also mentored the IT development staff on proper service-orientation. This includes designing and prototyping services, as well as the ESB mediation modules used to integrate applications and the services they consume.
|2009 – 2009||Principal Consultant||Noblis, Inc.|
As a Principal Consultant with Noblis, Inc., Rimas helped design and prototype a case handling system for the federal government using IBM’s WebSphere Business Process Management (BPM) product suite. The system leveraged the human task management features of the suite.
|2005 – 2009||Senior Software Engineer||IBM Corporation|
Rimas worked for the IBM Application Integration Middleware (AIM) Customer Programs team, which was responsible for running alpha, beta and (post-GA) customer acceleration programs for all WebSphere software products. Rimas was focused on the WebSphere Business Process Management (BPM) product suite, more specifically WebSphere Process Server (WPS) and WebSphere Integration Developer (WID). He very quickly became the team’s subject matter expert on the Business Process Choreographer (BPC) component of WPS/WID.
In this role Rimas worked with product architects and developers to create skills transfer educational material (presentations, lab exercises and demonstrations) to highlight the new features in the latest releases of the software. Besides providing training to beta program participants (as well as IBM’s sales and support staff), Rimas consulted with customers on their initial projects using these products to accelerate their adoption of these technologies.
|2002 – 2005||Industry Standards Architect||IBM Corporation|
Rimas represented IBM in the Web Services – Interoperability (WS-I) industry standards organization. Initially he participated in the Sample Application Working Group where he architected and designed the WS-I Supply Chain Sample Application. The sample application was used to demonstrate the interoperability of various vendors’ web services software stacks. As in any Service Oriented Architecture (SOA), the key task in the architecture and design of the application was to identify the (web) services.
With the architecture and design of the sample application complete, Rimas focused on the future work of the organization. Feeling strongly that it should be the users (not the providers) of web services technology who decide which standards/specifications should be profiled for interoperability, Rimas petitioned the WS-I board for the creation of the Requirements Gathering Working Group, which he initially chaired. Here he worked with WS-I members who are web services users to assess and analyze their requirements, and ultimately to present those requirements to the WS-I board in the form of charters for new working groups.
|1998 – 2002||Consulting IT Specialist||IBM Corporation|
As a consultant with the IBM Software Services for WebSphere practice, Rimas had J2EE engagements in a variety of industries: automotive, insurance, telecom and banking. Since the products and the technologies were in their infancy, Rimas did everything from architecting and designing solutions, to implementing and testing those solutions, to providing training for the clients’ staff. Responsibilities included installing WebSphere software, creating architecture and design documentation, writing Java code for JSPs, servlets, and EJBs, debugging customer code, debugging product code (including one severe memory leak problem), performing function tests, performance tests, stress tests, and eventually monitoring production systems.
Two of Rimas’ most significant and most successful projects include an internal call center application (Java on the client, C++, CICS and DB2 on the server) for a large insurance company in Norway, and the Internet on-line banking system for a major U.S. bank (JSPs on the client, Java servlets, EJBs, CICS and DB2 on the server). All of Rimas’ projects involved integrating disparate systems using a variety of distributed object oriented technologies (IBM’s DSOM, CORBA, and J2EE). Most projects also involved relational database management systems (typically IBM’s DB2).
|1988 – 1998||Staff Programmer||IBM Corporation|
Rimas began his professional career in operating systems development. After joining IBM as an associate programmer, he quickly stepped up to the role of development team lead of the subsystem of VM/XA CP responsible for defining virtual machines and performing logon/logoff processing for users. Rimas continued in a team lead role after moving to the AS/400 division where he and a small team of developers ported the SNA protocol portion of the OS/400 communications stack from the IMPI processor to the PowerPC.
With the code porting project complete, Rimas joined a team researching distributed object oriented technologies such as IBM’s DSOM and OMG’s CORBA. This research culminated in the development of a product called Component Broker, which was later re-branded as WebSphere Enterprise Edition. His responsibility was the definition of the programming model for distributed components, including the APIs for the Managed Object Framework, based on the idea of a container providing services to objects. These ideas (and APIs) were subsequently used jointly by IBM and Sun as input in the creation of the EJB specification.