About Usha Martin

Founded more than 50 years ago and headquartered in Kolkata, India, Usha Martin is a leading steel and wire rope manufacturer. The company’s products are used in sectors such as oil and gas, aerial haulage, and general engineering.

Industries: Manufacturing

Location: India

Usha Martin operates several wire and rope manufacturing plants in India, Thailand, the United Arab Emirates, and the United Kingdom. In 1974, Usha Martin established an integrated alloy steel plant in Jamshedpur, India.

The business operates a range of joint ventures internationally, including a partnership with Joh Pengg AG of Austria to produce oil-tempered wire for the automotive industry and a venture with TESAC of Japan to manufacture and sell specialized wire rope.

Usha Martin’s ICT strategy had traditionally been highly localized, with independent IT infrastructures in all the manufacturing plants and businesses globally. These infrastructures were not integrated, leading to extensive duplication of effort and activities across the business.

In 2016, Usha Martin corporate started a project to integrate ICT across the business and establish centralized financial and technology controls.

“We established a program to integrate our communications infrastructure, security policies, and software licenses and implement a centralized enterprise resource planning system across our business,” says Jayanta Bhowmik, SVP-IT and CIO, Usha Martin. This program is being initiated primarily in Usha Martin’s Indian businesses before being extended to international markets.

In parallel with these initiatives, Usha Martin decided to consolidate the disparate email infrastructures and systems used by its corporate team, plants, and business units.

“We faced security threats and control problems managing and interconnecting all our very different email systems,” Bhowmik says.

“For example, we experienced on average about three to four ransomware attacks every year. We decided there was no alternative but to deploy a centralized email system.”

Usha Martin weighed its options and went so far as to purchase a license to run a single email system on its in-house infrastructure. However, the challenges of migrating a 4,000-strong workforce from up to seven existing email systems to an in-house platform proved difficult to overcome.

“We would have had to plan for server infrastructure, backups, security, and disaster recovery and execute smoothly, which would have been a time-consuming, expensive exercise,” Bhowmik says. “We estimated an in-house deployment would take seven to eight months to complete.”

“We looked at cloud-based services and Google presented a unique opportunity for us to consolidate our email without having to plan for our own infrastructure and worry about project planning, architectures, and deployment,” Bhowmik says.

“We also considered another service, but realized Google also gave us the opportunity to move our personal productivity applications to G Suite.”

A competitive evaluation regarding hosting and disaster recovery confirmed Usha Martin’s positive impressions. Google technology and processes in these areas outstripped the capabilities of the company’s own data centers.

“Google came up with a migration timeline and process that met our needs, with an expert partner to ease the transition,” Bhowmik says. “This was extremely important as the change represented a paradigm shift for a business that is very traditional and conservative.”

The Google partner worked closely with the internal Usha Martin team to complete phase one of the migration to the senior executive team. The partner also undertook training and worked with the IT team to hold meetings at various plants and locations to explain the changes. In addition, the partner conducted a skills transfer exercise to enable Usha Martin team members to complete the remaining phases of the project.

The business migrated the 1,500 team members in its Indian operations, as well as those in its Austrian joint venture, to the new platform.

“Using Google gives us wonderful alternatives to traditional systems,” Bhowmik says. “For example, using Google Hangouts Meet for video calls means we can reduce the number of video conferences that occupy large rooms and help ensure there are enough time-slots to meet demand.”

Improved Security of Information and Systems

One of the key differences between Usha Martin’s existing email systems and Gmail is the improvement in security and online safety.

“We had an anti-spam engine but, despite this, our employees received a lot of spam emails and messages carrying ransomware viruses,” Bhowmik says.

“With G Suite, we don’t receive these messages anymore and we minimize the risk of our network being compromised by malicious infections that could prevent us from accessing our files.”

Using G Suite has reduced team members’ use of USB drives to share large files that would otherwise be blocked due to email attachment limits.

“In addition, people are reducing the practice of printing documents for meetings. One person in each meeting can now steer and control documents, reducing duplication and the possibility of errors.”

“Document sharing is now happening much more in the cloud rather than through external media, improving control and security,” Bhowmik says.

Manage Calendars More Effectively

G Suite now enables Usha Martin team members to manage their calendars more effectively and share documents with multiple people without having to aggregate feedback or manage version control.

“Thanks to G Suite, our people are coming into a world of collaboration and modernization,” Bhowmik says.

While many of us are navigating the shift to hybrid work, every team’s experience is unique. Distributed work is taking many different forms—from the fully remote to a specific mix of in-person and in-office—but there are potential gaps across all the places that people work. Google Workspace helps teams bridge these gaps by providing tools for them to connect, create and collaborate securely wherever they are. Today, we’re taking this one step further by announcing new ways to bring Miro’s intuitive whiteboard experience to Google Workspace so that teams can ideate and innovate more immersively.

With a shared commitment to extending inclusive, flexible collaboration experiences for all, we’re partnering with Miro to bring whiteboarding capabilities into Google Meet. We’re also deepening the existing experience within Google Docs, Sheets and Slides, making it easier for teams to ideate and co-create asynchronously and in real time. 

Deepening collaboration in meetings 

With the new Miro experience in Meet, you’ll get an immersive side-by-side video and whiteboard experience that’s ideal for brainstorming, sketching, and iteration during meetings. This approach fosters idea generation and participation from all team members, even if they’re in different locations. And using a Miro whiteboard in Meet is seamless: simply attach the Miro whiteboard to the meeting in Google Calendar or select a board during a meeting to share and collaborate in real-time. These new experiences will be available in early 2022.

Seamlessly integrate content from Google Docs, Sheets, and Slides 

Real-time collaboration across a distributed team often spans multiple files—from brainstorming in documents, to project management in spreadsheets, to presenting your ideas in slides. Miro integrates with Google Drive, so teams can easily access and embed their Google Docs, Sheets, and Slides into Miro’s infinite canvas, making it easier to visualize and manage all the pieces of a project from one shared space. You can also save your Miro boards to Drive, and Docs, Sheets, and Slides automatically sync across both applications, so you’re always working with the latest content.

Start using Miro in Google Workspace today

The Miro app for Workspace is one of the growing number of 3rd-party applications you can use to bring the apps and services you use every day to your Google Workspace experience. Try the Miro app in Workspace with your existing credentials, or sign up for Workspace and Miro to start using the free versions together. And stay tuned for future innovation as we partner with Miro on delivering visual collaboration capabilities that are mission critical for the hybrid workplace.

Since its initial release in 1995, MySQL has not only been the de-facto database for many data storage needs, but has gathered much attention over the years as one of the most well-recognized databases around when it comes to Relational Database Management Systems and transactional data processing.

Any application in retail, e-commerce, or banking has likely had its fair share of business depending on a relational database for its transactional needs. Many of these applications are built on MySQL due to its flexibility, open source nature, and strong community support.

Whether in the context of a migration from a relational database (like MySQL or PostgreSQL) , migration from a NoSQL database (like Cassandra), or a green grass workload, many companies turn to Cloud Spanner seeking a high availability SLA (99.99% for regional instances and 99.999% for multi region instances),  unlimited scale,  and low operational overhead – no patching required, no maintenance or other planned downtimes, just to name a few benefits.

The tooling and open source ecosystem around Spanner has evolved and grown ever since the service was introduced. HarbourBridge is a part of this ecosystem, and it’s meant to help customers port their existing MySQL or PostgreSQL schema to a Cloud Spanner schema. 

Application Migration Tips

Despite helpful tools like HarbourBridge, database migrations are never trivial. Here are a few things to pay attention to when migrating from MySQL to Spanner, and how to update your application logic to address them.

Note – The following snippets use the PHP client for Cloud Spanner. A couple of the snippets reference a partial Magento port that our friends over at Searce have been working on. Once you understand the operations, you should be able to implement the same in any of the other languages that Cloud Spanner supports.

Cloud spanner enforces strict data types  

In a MySQL query, the value of an attribute can be referenced as either a string or an integer. Example:

• select * from catalog_eav_attribute where attribute_id = 46;
• select * from catalog_eav_attribute where attribute_id = “46”;

Both are valid and equivalent. 

In Cloud Spanner, the query will return an error if you try to reference an integer type by using a string representation.

Here is an example of a working query from Cloud Spanner:

• select * from catalog_eav_attribute where attribute_id = 46; — this will work
• Select * from catalog_eav_attribute where attribute_id = “46” — will fail, since we are supplying a string with “46” 

You may use a function like the following to assist you with such transformations.

  /**
    * Formats the SQL for Cloud Spanner
    * Example
    * Input SQL : <select statement> WHERE 
    *    (`product_id` = '340') ORDER BY position  ASC
    * Output SQL : <select statement> WHERE 
    *    (`product_id` = 340) ORDER BY position  ASC
    * In the above example integer 
    *`340` is sanitized by removing single quotes.
    * Sanitization is required since Cloud Spanner
    * has strict typing
    * @param string $sql
    * @return string $sql
    */
   public function sanitizeSql(string $sql)
   {
       if (preg_match_all("/('[^']*')/", $sql, $m)) {
           $matches = array_shift($m);
           for($i = 0; $i < count($matches); $i++) {
               $curr =  $matches[$i];
               $curr = filter_var($curr, 
                   FILTER_SANITIZE_NUMBER_INT);
               if (is_numeric($curr)) {
                   $sql = str_replace($matches[$i], 
                       $curr, $sql);
               }
           }
       }
       return $sql;
   }

Using sequences in primary keys is not a Spanner best practice

Cloud Spanner does not implement a sequence generator,  and it is not a Spanner best practice to use sequential IDs because doing so can cause hotspotting.

An alternative mechanism of generating a unique primary key is to use a UUID or any other similar mechanisms that result in non-sequential values. For more information, please refer to this article.

In order to convert all existing primary keys to a UUID pattern, you can change the schema using the snippet here

You may use this code snippet to modify the application code to generate the UUID for the auto increment. There are other ways to do this as well, such as using PHP built-in uniqid function.

  /**
    * Generate UUID.
    * @return string
    */
   public function getAutoIncrement()
   {
       if (function_exists('com_create_guid') === true) {
           return trim(com_create_guid(), '{}');
       }
       return sprintf('%04X%04X-%04X-%04X-%04X-%04X%04X%04X',
           mt_rand(0, 65535), mt_rand(0, 65535),
           mt_rand(0, 65535), mt_rand(16384, 20479), 
           mt_rand(32768, 49151),  mt_rand(0, 65535),
           mt_rand(0, 65535), mt_rand(0, 65535));   
   }

Implicit casting and the need for explicit casting of field data types 

Both MySQL and Cloud Spanner follow the SQL standard, hence much of the query syntax is the same. One notable difference is that the Cloud Spanner field types are implicitly cast to an appropriate data type out of the ones mentioned here. When implicit casting of the field type fails, Spanner returns a read error, so it would be safer to perform the casting to the appropriate type when issuing the SELECT statement.

Modify application code to cast to respective data type before execution of query.

  $con = $this->getSpannerConnection();
 /**
 * Cloud Spanner follows strict type so cast the columns appropriately
*/
$select = $con->addCast($select, "`t_d`.`value`", 'string');
$select = $con->addCast($select, "`t_s`.`value`", 'string');
$select = $con->addCast($select, "IF(t_s.value_id IS NULL, 
    t_d.value, t_s.value)", 'string');
$values = $con->fetchAll($select);

Modify the application code to cast the column to its respective type 

  /**
    * Cast the column with type
    * @param string $sql
    * @param string $col
    * @param string $type
    * @return string
    */
   public function addCast(string $sql,
       string $col, string $type)
   {
      $cast = "cast(".$col." as ".$type.")";
      return str_replace($col, $cast, $sql);
   }

Using interleaved tables to improve read performance

Cloud Spanner’s table interleaving is a great choice for many parent-child relationships where the child table’s primary key includes the parent table’s primary key columns. Interleaving ensures that child rows are collocated with their parent rows, which can significantly improve query performance.

Refer to the statements here for a few samples of creating interleaved tables. To learn more about table interleaving, visit the documentation.

Conclusion

Database migrations are complicated.  Hopefully, using HarbourBridge and the  list of tips in this article can make that task easier.  For additional tips, please take a look at this migration guide and read more about HarbourBridge.

About Bank BRI

Bank Rakyat Indonesia is one of the largest banks in Indonesia and is committed to increasing financial inclusions among un-banked Indonesians. Bank BRI specializes in using modern digital banking to facilitate microfinance lending across its network of over 10,000 branches and thousands of branchless agents.

Google Cloud Results

• Contributes $50M in revenue through the Apigee monetization feature
• Wins recognition for best digital bank in Indonesia from The Asian Banker in 2019
• Achieves ISO 27001 information security for open APIs, earning distinction as the only bank in ASEAN to receive certification to date
• Reduces partner onboarding from 6 months to under 1 hour with Apigee developer portal

Bank Rakyat Indonesia is making waves in Asia with its award-winning digital strategy. As a government-owned bank, Bank BRI is dedicated to changing the lives of its customers through accelerating financial inclusion across Indonesia. With an aggressive target of 84 percent of Indonesians participating in the banking system by 2022, Bank BRI is leapfrogging fintech competition thanks to its innovative digital strategy that has APIs at its core. By the end of 2019, Bank BRI expects to have reached a 70 percent financial inclusion rate among the country’s population, in part due to the adoption of the Cloud Apigee API Management Platform as the bank’s digital nucleus.

Transforming a legacy into a digital future

In the banking business, trust is essential, not only between the bank and its customers, but also between the bank and its partners. Recognizing that gaining and maintaining this trust would be key to customer and partner adoption of the new Bank BRI products and services, the bank decided to pursue ISO 27001 certification in 2018, becoming the first bank in ASEAN (the Association of Southeast Asian Nations) to become certified as information security compliant. Now the international community of partners and customers who use the bank’s APIs have yet another reason to place their trust Bank BRI.

“Apigee has become the central nervous system for all communications between the digital core banking, the microservices, the frontend, and the apps. Apigee has become our sun. Everything rotates around Apigee.”—Kaspar Situmorang, Executive Vice President, Bank Rakyat Indonesia

Kaspar Situmorang, Executive Vice President of Bank BRI, had the original vision for how the bank could transform itself into a fintech with digital technology and APIs. His team got started by implementing a web-native frontend over a new technology stack with Apigee as a second layer. This was a big change from the legacy technologies that existed when Situmorang joined the bank in 2017. Previously all of the bank’s products had their own public APIs, which were very difficult to manage, secure, and monetize.

Since deploying Apigee, it’s become much easier to manage the entire API lifecycle. Situmorang’s digital bank team of 15 uses the Apigee monetization and developer portal features while managing and securing APIs and conducting big data integrations. Apigee has become Bank BRI’s center of communications, handling all transactions between the bank and third parties.

Whereas previously it could take up to six months to onboard a new partner using host-to-host and VPN technology, now it takes less than an hour for partners to self-onboard using the Bank BRI Apigee developer portal. On the portal, partners can register, browse APIs, test in the sandbox, and go into production — all in less than an hour.

“Apigee has become the central nervous system for all communications between the digital core banking, the microservices, the frontend, and the apps. Apigee has become our sun. Everything rotates around Apigee,” says Situmorang.

Increasing financial inclusions

With more than 10,000 offices across Indonesia, Bank BRI has the largest network of any bank in ASEAN. The bank is also the biggest microfinance lender in the region. Though already present in even the most far-flung corners of Indonesia, Bank BRI is still working on increasing financial inclusion among un-banked Indonesians. With 56 million people that haven’t accessed banking services, Indonesia is in the bottom four countries for financial literacy in the world, along with Bangladesh, India, and China. It’s estimated that there is up to $8.3 billion in currency being held outside the banking system.

In order to reach this mostly rural, subset of the population, the bank launched Agent BRILink, a nationwide network of branchless agents. These agents can open new accounts, take deposits, pay out withdrawals, and process and disburse loans in under two minutes with the Pinang microfinance mobile app. To date, over 30,000 customers have received loans through Pinang. Handling its own risk-scoring and automatic payroll deductions for payments has translated into less risky and more profitable loans for Bank BRI.

“Customers download the app and scan their ID, capturing their credit score in just a few seconds. The digital offer letter says how much they’re approved for. They can then accept it, go to the approval screen, and do facial recognition. The money is disbursed immediately. GCP has transformed us into a fintech.”—Kaspar Situmorang, Executive Vice President, Bank Rakyat Indonesia

BRILink agents are bank customers who have been scored highly for reliability by the bank’s big data analyses and who maintain a minimum balance of around $800. Combining this data with the Google Maps API, Bank BRI is able to score all 75.5 million of its customers and identify which of them should be recruited as agents for underbanked areas. Since 2018, the bank has been able to appoint more than 200,000 branchless agents using the Agent BRILink app, eliminating the need for logistically challenging face-to-face meetings. This has resulted in an increase in loan volume from branchless business from $15 billion in 2017 to $26 billion in 2018.

To enable branchless agents to sign up new customers and provide banking services, all they need is a mobile phone and internet service. With many parts of rural Indonesia not covered by commercial 3G, Bank BRI has overcome this hurdle by operating its own satellite. With the connectivity the satellite guarantees, branchless agents can help customers obtain microfinancing and open new shops and businesses in all parts of the country. The satellite also provides internet service across the APAC region wherever the bank operates, from Sri Lanka to New Zealand. While it might seem unusual for a bank to operate a satellite, it’s reflective of Bank BRI’s commitment to reaching its financial inclusion targets and meeting its customers wherever they are.

“Pinang was created to win against fintechs trying to compete against us on speed, cost, and security,” says Situmorang. “The truth is that Indonesian regulators closed about 650 fintechs, mainly in the peer-to-peer lending space, because they were unsafe, too expensive, and very slow.”

Using APIs to create and monetize new products

Another way that Bank BRI is leveraging Google Cloud Platform solutions is through an innovative use of the Cloud Vision API, which enables the bank to integrate with the Indonesian government ID database. Identities of new customers — whether they’re coming in via a branch, a BRI Link Agent, or a mobile app — are automatically verified in seconds through facial recognition. With instant credit scoring and identity fraud concerns essentially eliminated, the bank can make more confident lending decisions.

“Monetization is very important to us. It enables us to define our pricing based on API calls and bill automatically based on usage. We’ve already recognized $50 million through the Apigee monetization feature.”—Kaspar Situmorang, Executive Vice President, Bank Rakyat Indonesia

“Customers download the app and scan their ID, capturing their credit score in just a few seconds,” explains Situmorang “The digital offer letter says how much they’re approved for. They can then accept it, go to the approval screen, and do facial recognition. The money is disbursed immediately. GCP has transformed us into a fintech.”

Bank BRI sees a bright digital future, in part thanks to the API product marketplace it’s creating to serve fintechs. With its digital technologies and massive customer base, the bank is sitting on a treasure trove of big data. Bank BRI already packages this data through more than 50 monetized open APIs for more than 70 ecosystem partners wanting to do credit scoring, business assessments, and risk management. Fintechs, insurance companies, and financial institutions don’t have the talent or the financial resources to do quality credit scoring and fraud detection on their own, so they are turning to Bank BRI.

“Monetization is very important to us. It enables us to define our pricing based on API calls and bill automatically based on usage. We’ve already recognized $50 million through the Apigee monetization feature,” says Situmorang.

Bank BRI is meeting and surpassing the goals it has set for itself for digitalization, increasing financial inclusion, and creating new revenue streams with APIs.