Utilizing a Low-Code Automation Platform for Collaboration

2022-08-26 01:53:11
关注

Illustration: © IoT For All

A low-code approach to unifying disparate things in an organization to create a new service is game-changing because, for the first time, a shared canvas or interactive whiteboard can translate the ideas humans conceive into live services in operations or the field in hours. So, how many of us have been in product design meetings where all of the stakeholders are present—sales, marketing, product, engineering, and others—and we agree on what we want to create and build except for the engineers who want to take this napkin of concepts and actually figure out how to bring this into production? Let’s dive deeper into this issue and look at how a low-code automation platform may be a potential solution.

'The answer is to find a low-code automation platform built for a formula one integration problem where all of your investment in software applications, even your legacy systems, are preserved.' -WaylayClick To Tweet

Addressing the Cost & Resources for Digital Transformation

Let me give a random example. 

During a health and safety conference in New York City with the New York State Professional Fire Fighters Association (NYSPFFA) in attendance, a fire safety regulator for buildings in New York explained why there is a new compliance opportunity in the pipeline. With the onset of IoT, it now meant everything in a building needed to be automated and connected in real-time to emergency services. Meaning that the nature of firefighting, safety, and response would also need to change with the times.

Also in the audience were Bert Beaney, head of buildings for Empire, Inc., and his colleague Marty Spark, the president of Fire Safety Solutions, who were listening with a lump in their throats. Why? At that moment they realized that vendor solutions marketing has gone too far ahead on messaging. Bert and Marty knew there is no real automation of IoT workflow things between building and fire safety. Even worse, their BMS, fire control, and facilities management systems were all static island operations. Worse yet, the field service and emergency maintenance response was yet another platform and, all in all, the hyper nirvana of an end-to-end “event to response” control solution did not exist yet.

This example is fundamentally why the cost, time, and resource loss in digital transformation is monstrous because a methodology to automate things has been ignored, not to mention the impact on organizational confidence. 

According to TechTarget, $1 trillion had been invested in digital transformation projects with the Boston Consulting Group estimating at least 70 percent of these initiatives fell far short of their original goals by March 2021. As mentioned in my recent blog on automation OS, “the problem has become so apparent that it is not unusual for a CEO to dodge analysts’ questions in earnings calls on digital transformation.” Even scarier, I spend a lot of time with investment analysts and they do not even know what questions to ask to find out what is really going on, making it especially tricky to pick winners because, in theory, an organization that succeeds in digital transformation will make stunning market share gains within five years. 

Facing Digital Transformation Challenges

Anyway, let’s get back to Bert and Marty’s dilemma.

They arranged a conference call with their newly hired CTO originally from Belfast, Jim Finnegan. They explained to him what was coming down the tracks and asked Jim what they needed to do to finally fix the forthcoming digital transformation challenges. 

Jim paused and said, “Well, for starters, we need people to make peace with each other, stop the tribalism of ‘ownership of things’ and introduce a genuinely collaborative approach to designing the easier ‘automation of things’ to deliver what is becoming mandatory for buildings and associated services like fire and safety.” He then exhaled, “Give up the ghost!”  

He went on to say, “What we need is a kid internally fooling around with low-code tools to pick something that enables us to bring our SMEs together to design and build integrated workflow between IT-OT services fast.” Jim added, “Better still will be when we can focus on better customer outcomes by automating the underlying business logic.” 

Jim provided an example. “FIRE” template: ! building A, zone 102: HVAC alert, tune carbon sensor to max, smoke detected, alert FDNY, fire electrical (sprinkler off/gas ready), people zone 102 SMS/Twilio evacuate, people occupancy in 102 negative, cancel cyber keys, fire doors shut, air vents closed, emergency lighting on, FDNY at 102, building BMS activates emergency maintenance alert out—human to human voice call confirmation executed. 

In his mind, Jim had RPA (Uipath, AA, etc.) as a quick stitch approach to get going, but Marty started his career as an engineer in GE and countered. “Jim, what we also need is a rules engine at the heart of things that automates the underlying IoT workflows between the OT and IT world,” stated Marty, “and hides all the spaghetti from everyone because that is where things break down whenever organizations try to go digital.” He added, “We need to conceal the complexity of software to make this work.” 

“That is sort of BPM like Tibco, Appian right or maybe even a BMS like switch automation?” said Jim in response.  

Yes, it would be exciting to hear how Bert, Marty, and Jim came together to resolve their problem. 

Solution: Low-Code Automation Platform 

From my perspective, I would argue the nut will not be cracked by Empire with a kludge of things, e.g. RPA/BPM tools, which do not help avoid more big software and perpetuate a semi-frozen world in digital transformation. The answer is to find a low-code automation platform built for a formula one integration problem – one where all of your investments in software applications, even your legacy systems, are preserved. Such that digital transformation becomes a simpler and feasible integration of things capable of addressing the needs of very sophisticated use cases in operations across industrial, energy, telecoms, and financial services markets.

The upside for enterprises is going to be mega on many fronts. As the world braces for a very tough economic backdrop, the biggest win to focus on – going back to our example – is hitting new bars in safety and customer satisfaction. Let’s face it, enormous savings will be reaped from automation at a time of record software skill shortages globally. Other target metrics to look for from an automation OS are: 10x faster time to market, 100x less code, 15x less development time, and up to 20x operating expenses (OPEX) and capital expenditures (CAPEX) cost savings. And finally, a break-even ROI within nine months or less.

A Collaborative Approach

Facilitating a collaborative cross-functional teams service (product) development environment in low-code is great, but then abstracting everyone away from the underlying complexity with automation workflow management at work is even better again. A low-code automation platform will lead to a collaborative approach for product management and development teams.

Tweet

Share

Share

Email

  • Automation
  • Building Automation
  • Cloud Software
  • Digital Transformation
  • Factory Automation

  • Automation
  • Building Automation
  • Cloud Software
  • Digital Transformation
  • Factory Automation

参考译文
利用低代码自动化平台进行协作
插图:© IoT For All → 采用低代码方法,统一组织中分散的事物,以创建新的服务,这将带来变革性的影响。因为,第一次,我们可以通过共享画布或交互式白板将人类构想的想法,几小时内转化为运营或现场的实时服务。那么,我们中有多少人曾在产品设计会议中,所有的相关方都在场——销售、市场、产品、工程等——我们一致同意我们要创建和构建的东西,除了工程师,他们希望把这张概念的纸巾变成现实?让我们深入探讨这个问题,看看低代码自动化平台是否可以成为一个潜在的解决方案。 “答案是找到一个为‘一级方程式集成问题’而设计的低代码自动化平台,你的所有软件应用投资,甚至遗留系统,都能被保留。” ——Waylay 点击推文 消除数字化转型的成本与资源问题 我举个随机的例子。在纽约市召开的一场健康与安全会议中,纽约州职业消防员协会(NYSPFFA)在场出席。一位纽约市的建筑物消防安全监管人员解释了为什么有一项新的合规机会即将出现。随着物联网的兴起,现在意味着建筑物中的每样事物都需要实时地自动化并与紧急服务连接。这意味着消防、安全与响应的性质也必须与时俱进地改变。 同样在场的还有帝国公司建筑部门的负责人Bert Beaney和他的同事Marty Spark,后者是Fire Safety Solutions的总裁,他们听得很揪心。为什么?在那一刻,他们意识到供应商解决方案的营销信息已经远远超前。Bert和Marty知道,建筑与消防安全之间还没有真正的物联网工作流自动化。更糟糕的是,他们的楼宇管理系统(BMS)、消防控制和设施管理系统都是静止的孤岛式运营。更糟的是,现场服务和应急维护响应是另一个平台,总体而言,实现端到端“事件到响应”的控制解决方案的“完美天堂”尚未存在。 这个例子正是为什么数字化转型的成本、时间与资源损失是巨大的,因为一种自动化事物的方法已被忽视,更不用说它对组织信心造成的影响了。根据TechTarget的报道,1万亿美元已投资于数字化转型项目,而波士顿咨询公司估计,截至2021年3月,至少有70%的这些项目远未达到最初目标。正如我在最近关于自动化操作系统(Automation OS)的博客中提到的,“问题已经变得如此明显,以至于CEO在财报电话会议上常常回避分析师关于数字化转型的问题。”更令人担忧的是,我花了很多时间与投资分析师在一起,他们甚至不知道该提出哪些问题,去了解事情的真相,使得挑选赢家尤其困难,因为理论上,一家在数字化转型中成功的组织将在五年内实现惊人的市场份额增长。 面对数字化转型的挑战 无论如何,让我们回到Bert和Marty的困境。他们安排了一次与他们新聘的CTO——来自贝尔法斯特的Jim Finnegan——的电话会议。他们向他解释了即将发生的事情,并问Jim需要做些什么来最终解决即将到来的数字化转型挑战。Jim停顿了一下,说:“好吧,首先,我们需要人们彼此和解,停止关于‘事物所有权’的部落主义,并引入一种真正协作的方式来设计更简单的‘事物自动化’,以实现建筑物和相关服务如消防与安全的强制要求。” 他然后叹了一口气,“放弃幻想吧!” 他接着说道:“我们需要的是一个内部的‘孩子’,他可以用低代码工具随便摆弄,选择一些能让我们整合专家团队,快速设计和构建IT-OT服务之间的集成工作流的工具。” Jim补充道:“如果还能通过自动化底层业务逻辑来关注更好的客户结果,那就更好了。” Jim举了一个例子。 “FIRE”模板:!建筑A,区域102:暖通空调警报,将碳传感器调至最大,检测到烟雾,通知FDNY,火灾电气(关闭喷淋/准备燃气),向区域102人群发送短信/Twilio进行疏散,区域102人群密度为负,取消网络密钥,关闭防火门,关闭通风口,开启应急照明,FDNY到达102,建筑BMS激活紧急维护警报——执行人对人的语音确认呼叫。 在他看来,Jim最初考虑使用RPA(如UiPath、AA等)作为快速连接方法来启动工作,但Marty曾在通用电气(GE)以工程师身份开始职业生涯,他反驳道。 “Jim,我们还需要在事物核心有一个规则引擎,它能自动管理物联网工作流在OT和IT世界之间的底层流程,”Marty说,“并且隐藏所有杂乱无章的连接,因为每当组织尝试数字化时,问题就出在这里。” 他补充道:“我们需要隐藏软件的复杂性,才能让这一切起作用。” “那是不是有点像Tibco、Appian这样的BPM系统,或者甚至是一个开关自动化(Switch Automation)的BMS系统?”Jim问道。 是的,听Bert、Marty和Jim如何携手解决问题将是令人兴奋的。 解决方案:低代码自动化平台 从我的角度来看,我认为Empire不会通过一些临时拼凑的事物(比如RPA/BPM工具)来破解这个问题,因为这些工具无助于避免更多庞大的软件系统,并且会延续半冻结的数字化转型世界。答案是找到一个为“一级方程式集成问题”设计的低代码自动化平台——一个能够保留你所有软件应用投资,甚至遗留系统的平台。从而使数字化转型成为一种简单可行的集成方式,能够满足工业、能源、电信和金融服务市场中复杂用例的操作需求。 企业将从多个方面获得巨大的收益。随着世界准备迎接一个非常严峻的经济环境,最大的赢面——回到我们的例子——是在安全和客户满意度方面实现新的高度。说到底,当全球软件技能短缺创纪录时,自动化将带来巨大的节省。 从自动化操作系统中可以预期的其他目标指标包括:市场进入时间加快10倍、代码减少100倍、开发时间减少15倍,以及运营支出(OPEX)和资本支出(CAPEX)成本减少高达20倍。最后,投资回报周期将在九个月内或更短。 一种协作方法 在低代码环境中促进跨职能团队服务(产品)开发的协作方法是很好的,但通过自动化工作流管理将所有人从底层复杂性中抽象出来,会更好。低代码自动化平台将引领产品管理和开发团队采用协作方法。 推文分享邮件自动化建筑自动化云软件数字化转型工厂自动化
您觉得本篇内容如何
评分

评论

您需要登录才可以回复|注册

提交评论

广告
提取码
复制提取码
点击跳转至百度网盘