Artificial Intelligence - Neural Nets

By -

Artificial Intelligence (AI) is on the move and the race is on.  In previous years, and for the most part even today, AI has been dominated by the worlds high tech companies like Google, Microsoft and Amazon.  Regardless of where you work or the size of your business, the industry is starving for more information and true knowledge management.  AI goes beyond knowledge management and moves us into knowledge engineering.

As found in an MIT Technology Review article, Microsoft has its own AI-powered cloud platform.  You may have heard of Azure.  This team is joining with Amazon to offer Gluon.  It is an interesting name. I don’t know its origin, but it is essentially an open-source deep-learning library. Gluon is supposed to make building neural nets – a key technology for AI that crudely mimics how the human brain learns – as easy as building a smartphone app.

It is no longer just a high-tech game.   With the onslaught of cloud services, any/all service providers (including enterprise-wide and small startups) can join the race.  Machines today can, to some extent, think and act like humans.  Collecting and analyzing patterns of business activity for AI will include many elements including:
  • Speech recognition
  • Learning
  • Planning
  • Problem-solving
  • Auto-Actions (including moving objects)
Exciting isn’t it? Let’s not forget that as we build these neural nets that we must include the essential basics that become the cornerstone for success. AI is and will continue to play a key role for DevOps, Continuous Delivery and Agile Service Management. 

Comments

Post a Comment

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

By -
I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
·Process Owner – this individual is “Accountable” for the process.  They are the goto person and represent this process across the entire organization.  They will ensure that the process is clearly defined, designed and documented.  They will ensure that the process has a set of Policies for governance.
o Example:  The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, …  all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  oAn example of a policy in could be…  “All Incidents must be logged”.  Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do),  Procedures (details on how to perform the activity) and the policies …
Read more

The Difference between Change and Release Management

By -
There is often confusion between the goals, authorities and roles of Change and Release Management.  In fact, the objectives of each of process are very, very different.
Change rules! Change Management is an authoritative process that governs anything that potentially impacts a new or existing service.  It is both the enabler of innovation and protector of stability.   It is first and foremost a risk management process.   It is also a planning process.  
If Change Management is a governance process, Release Management is an action process.  Under the authority of Change, Release builds, tests and releases new or updated services into the production environment.  Every release is comprised of a single change or package of changes.  Release Management is more technical than Change.
If done well, both processes will avoid unnecessary levels of bureaucracy and will build a collection of change and release models that pre-define and pre-approve the rigor required based on levels of risk.  The…
Read more

Incidents when a Defect is Involved

By -
Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…
Read more

Search This Blog