Proudly Serving Washington

---

Washington Aviation Repair Software Since 1998

Deliver excellence in aircraft disassembly for stronger customer fleet.

When I took flight to software development in aviation I soared right into a new and exciting industry.  Since then I have assisted companies in aviation software development for the aircraft maintenance industry.

Washington Customers

Some information I know about Washington is I believe the state was admitted or ratified to the United States around or about 'November 11, 1889'.  Washington is located around latitude '47.751076' and longitude of '-120.740135' and has a population of roughly '7,705,281 million'.  If I remember correctly the capital is 'Olympia' and the largest city is 'Seattle'. 

What's my Experience in Jet Aircraft Parts Production?

Above is an image of an aircraft repair facility.  While at TIMCO I was over Symix manufacturing software modifications written in Progress 4GL.  The process of aircraft repair often times meant creating new parts.  Often our computers and floors would shake at TIMCO when new sheet metal was being stamped out for repairs.  The Symix software ran on HP Unix and operational to support 3 production shifts.

Aviation software can be desktop software or embedded software with legally mandated safety and reliability concerns used in avionics.

If at any point you decide to reach to me just know the area codes I am familiar with for Washington are '206, 253, 360, 425, 509, 564'.  For Aviation Repair assistance you will find my rates very reasonable for Washington.  Now just keep in mind my time zone is 'Eastern Standard Time (EST)' and I know the time zones in Washington are 'Pacific Standard Time (PST)' in case you wish to call me.  Anyway let me continue.

Since I touched on desktop vs embedded I would like to say the main difference between avionic software and conventional embedded software is that the development process is required by law and is optimized for safety. It is claimed that the process described below is only slightly slower and more costly (perhaps 15 percent) than the normal ad-hoc processes used for commercial software.

Since most software fails because of mistakes, eliminating the mistakes at the earliest possible step is also a relatively inexpensive, reliable way to produce software. 

You know, I don't make it out to Washington much but I would like to see the 'Willow Goldfinch' state bird.  I am a little familiar with the Washington 'Western rhododendron' state flower as well.  However, I do not know much about Washington's state tree the 'Western Hemlock'.  Fishing is fun to me perhaps I would like reeling in the Washington 'SteelHead Trout' state fish.  Anyway, sorry I went off topic.  Let me continue.

In some projects, however, mistakes in the specifications may not be detected until deployment.  At that point, they can be very expensive to fix.