Proudly Serving North Dakota

---

North Dakota Self Healing Systems Since 2002

Self-aware systems can assist in disaster recovery and more.

Computers do a lot for us and when utilized properly can actually resolve common issues.  Imagine if a monitor could detect an issue before it becomes a problem, before users complain, before it gets worse.  I used to write systems which would monitor for issues and run scripts to repair / rectify the issue if possible and notify IT Support of the issue, if it was automatically resolved and how.  If the system could not automatically repair/address the issue it would notify IT Support as well.

North Dakota Customers

Some information I know about North Dakota is I believe the state was admitted or ratified to the United States around or about 'November 2, 1889'.  North Dakota is located around latitude '47.650589' and longitude of '-100.437012' and has a population of roughly '779,094 million'.  If I remember correctly the capital is 'Bismarck' and the largest city is 'Fargo'. 

I have written systems that do just that.  Understanding computers, network architecture, network infrastructure and protocols allows me to develop monitors which allow systems to become self healing.

Processes and hardware are prone to issues.  Even network infrastructures not under my control can cause problems when they are an integral component of systems.  Vendors need monitoring as well.

If at any point you decide to reach to me just know the area code I work within for North Dakota is '701'.  For Self Healing Systems assistance you will find my rates very reasonable for North Dakota.  Now just keep in mind my time zone is 'Eastern Standard Time (EST)' and I know the time zones in North Dakota are 'Most of the state: Central Standard Time (CST) / Western North Dakota: Mountain Standard Time (MST)' in case you wish to call me.  Anyway let me continue.

Why wait for the problem to occur?  I don't, I develop methods to fix and notify thus saving your company thousands if not millions in service calls and down time.

Here's the most challenging self healing scenario.  Disaster Recovery!!!!  How in the world I build systems that automate disaster recovery across diverse architecture, protocols and ensure I do not make matters worse?  It is not easy but I first develop a team to ensure every aspect is covered, test on a small scale, repeat the test, repeat the test again.  Try on a slightly larger scale with different hardware and protocols until I am comfortable automation works.  In this scenario not 100% of everything can be automated.  Human intervention is needed at key steps.

You know, I don't make it out to North Dakota much but I would like to see the 'Western Meadowlark' state bird.  I am a little familiar with the North Dakota 'Wild prairie rose' state flower as well.  However, I do not know much about North Dakota's state tree the 'American Elm'.  Fishing is fun to me perhaps I would like reeling in the North Dakota 'Northern pike' state fish.  Anyway, sorry I went off topic.  Let me continue.

Areas of Hardware and Process Mitigation

Understand, Plan, Implement, Manage:

1. Understand your processes
2. Understand failure points
3. Understand command level methods for resolving issues
4. Understand those issues which need manual resolution by a human
5. Plan through creating monitors that are scheduled and have a frequency
6. Implement monitors and monitor the monitors until your sure they are running correctly
7. Manage by tweaking monitors, adding more monitors as the needs arise