The ABC Of Type C FIBCs


On 4th August 2020, a powerful explosion rocked the Port of Beirut in Lebanon killing 218 people and injuring 7,000[1]. Considered as one of the largest non-nuclear explosions, the blast rendered half of Beirut’s healthcare centres nonfunctional and caused an estimated USD 3.8 – 4.6 billion in damages to infrastructure and physical assets. [2]

However, this was neither a terrorist attack nor a war strike from a hostile country. The explosion was an industrial accident, one of the worst of its kind, caused by the improper storage of Ammonium Nitrate, a highly flammable substance used in manufacturing fertilizers.

Read more - https://emmbi.com/the-abc-of-type-c-fibcs/

Comments

Post a Comment

Popular posts from this blog

Image
  E-commerce payment settlement: an opportunity for banks The Indian E-commerce industry has been on an upward growth trajectory and is expected to reach $200 billion by 2026. The growth is mainly driven by increasing internet penetration and awareness about the ease and convenience of buying online. The COVID-19 outbreak is further driving the growth of e-commerce sales with millions of consumers shopping online from the safety of their homes. According to Goldman Sachs review of global e-commerce markets, Indian e-commerce is expected to grow over 18% in 2020. Read more at -  https://datanimbus.com/blog/e-commerce-payment-settlement-an-opportunity-for-banks/
Read more
Image
  Ok, TLS! We are paranoid. Paranoid about security and always trying to strike a fine balance between security and usability. One of the simplest forms of security, which anyone can adopt while building APIs, is to expose them over a secure channel.  HTTPS   to be precise. In HTTPS, the “S” stands for secure and uses  TLS or Transport Layer Security  to encrypt the transmissions. Read more at -   https://datanimbus.com/blog/ok-tls/
Read more
Image
  Designing payment APIs, for those in a hurry The team at  37signals  are notorious for their catalog of ideas (what they call, signals), of which one in particular is pretty interesting (and almost polarizing) when it comes to API design: context > consistency. To quote 37signals: “Following a formula can be comforting, but when it comes to design, we think designing around the current context is better than designing to satisfy prior consistency.” Read more at -  https://datanimbus.com/blog/designing-payment-apis/
Read more