Thursday, December 6, 2012

IRS Releases Job Killing Medical Device Tax Guidance

The Office of the Federal Register has released the Internal Revenue Services (IRS) guidance document on the job killing Taxable Medical Devices, that I covered last year: Do you work in the Medical Device field? You won't after 2013 due to this new Tax. My four top picks:

One commenter suggested that the listing rule is overbroad because it includes virtually all types of medical devices in the tax base. The commenter requested that the final regulations narrow the definition of a taxable medical device so that the excise tax is imposed only on devices that Congress specifically intended to subject to the tax.

The final regulations do not adopt this suggestion.

[Doublespeak translation: It is a device if we say it is a device.]


Sale price:

Numerous commenters suggested that the IRS apply the constructive sale price rules with flexibility and sensitivity to data limitations that medical device companies face. The IRS and the Treasury Department recognize that the medical device industry will likely face some implementation issues when the medical device excise tax goes into effect on January 1, 2013, and the IRS intends to work with stakeholders on compliance-related issues, such as the determination of price.

[Doublespeak translation: You and I are going to pay through the nose for any medical device to just to handle all this new paperwork!]


Licensing of software:

One commenter requested clarification on whether the licensing of software that is a taxable medical device is a taxable event. Under existing chapter 32 rules, the manufacturers excise tax generally attaches upon the sale or use of a taxable article by the manufacturer. The lease of a taxable article by the manufacturer is considered a sale. Neither the existing chapter 32 rules nor the final regulations address the issue of whether the licensing of a taxable article is a taxable event. However, the IRS and the Treasury Department will issue separate interim guidance along with these regulations to address this issue.

[Doublespeak translation: Not even the FDA can figure out what the IRS wants, or is it the other way around?]


Semimonthly deposits:

Several commenters suggested that the semimonthly deposit requirements under section 6302 are burdensome to medical device manufacturers because device manufacturers have little or no experience with returning and paying federal excise taxes and because manufacturers need time to develop their systems to implement these final regulations...Given that the tax goes into effect on January 1, 2013, the IRS and the Treasury Department will issue separate interim guidance along with these regulations that addresses penalties under section 6656.

[Doublespeak translation: We don't care if you know how any of this stuff works, and we have not gotten around to writing the statute that would tell you yet, even tho we had a year to do it, but we do have the system of applying involuntary monetary fortuities {high fines that raise costs for you and I} in place now.]

The job killing tax, part of the Patient Protection and Affordable Care Act, has already been taking its toll this year. It may hit the Cleveland/Pittsburgh area hard. Resume anyone?


Friday, November 23, 2012

Yet More Government Responses on Software License Questions and Study Guide

This month I received responses from Maryland and Idaho to the questions I asked in August, and IEEE-USA has released the Study Guide for New Software Engineering Exam. See my previous blogs on the subject at Do you have your license to write firmware? and Government Responses on Software License Questions.

The Idaho Board of Professional Engineers and Professional Land Surveyors, sent me a formal written response via Snail Mail:


November 9th, 2012

Dear Mr. Paddock:

At its meeting on November 7 and 8, 2012 the Idaho Board of Licensure of Professional Engineers and Professional Land Surveyors voted not to utilized the NCEES Principles and Practice of Software Engineer examination at this time for licensing professional engineers in Idaho, but they may reconsider that decision in the future.

Please call if you have any questions.

Sincerely, David K. Bennion , P.E. Board Chair.


Nov. 13 2012

Dear Mr. Paddock:

In your e-mail of August 12, 2012 you asked a number of questions regarding the NCEES Software Engineering, Principles and Practice of Engineering Examination. Please excuse us for not responding sooner, but I needed to consult the Board in detail to be able to provide you answers to your questions.

You asked if the "Software Engineering" license will be required in Maryland. Maryland does not license engineers by discipline. So no a "Software Engineer License" is not required (because there is no Software Engineer license), However, the practice of any engineering discipline including software engineering in the State of Maryland, does require a Professional Engineer License, subject to the exception provided in statute.

You asked: "Should such a license be required by the state, will there be any distinction made between types of computer systems such as your desktop PC, your Smart Phone or an Embedded System (those that run your microwave and your car)?" The practice of engineering is defined in Maryland statue as including: consultation; design; evaluation; inspection of construction to ensure compliance with specifications and drawings; investigation; planning; and design coordination. The planning, design, evaluation of any kind of software that could affect the health, safety or welfare of the public would fall be included in this definition and be considered the practice of engineering in Maryland.

You asked: "What will the prerequisites for taking the test, should it become required? Software is significantly different than any of the current required licenses." The requirements for taking the exam are the same as any other Principles and Practice of Engineering Examination (see § 14-304 and § 14-305). You also stated that you are concerned that there "..will there be academic requirements that will exclude those that have been practicing in the industry for years, yet have do not have a degree from a state recognized institution" Current Maryland Statute provides a path for licensure without a degree (see § 14-304 and § 14-305).

You asked: "Does Maryland license by comity?" Yes, Maryland does license by comity.

You asked: "How often will this license have to be renewed and what is the expense?" A Professional Engineering License in Maryland is renewed once every two years. The cost to renew is currently $68.00.

Finally you asked: "As a holder of a CSQE, will there be any ramifications of using the word 'Engineer' on my business card or web site?" Only Licensed Professional Engineers may practice, attempt to practice or offer to practice engineering in the State of Maryland. This includes using the title "engineer" on business cards, web sites or any other forms of communications.

I hope this clarifies the issues you were concerned with regarding software engineering and the practice of engineering in Maryland.

Please feel free to contact me again if you need any additional clarification on these issues or additional information.

Pam Edwards Executive Director - DLLR's Division of Occupational and Professional Licensing [Maryland].




News Release: Study Guide for New Software Engineering Exam Now Available:

WASHINGTON (31 October 2012) - A study guide for those planning to take the new software engineering exam is now available from IEEE-USA. It includes 40 representative questions and solutions, a suggested reference list and test specifications.

The Principles and Practice of Engineering (PE) Software Engineering exam - PE Software exam -- will be offered by NCEES, The National Council of Examiners for Engineering and Surveying, for the first time in April 2013.

IEEE Fellow Dr. Phillip Laplante, a professor of software engineering at Penn State University's Malvern, Pa., campus and chair of the Software Engineering Licensure Examination Development Committee, said the study guide is an essential tool in preparing for the exam.

"All prospective exam takers would be well-served to review the book to help identify weaknesses in their knowledge prior to taking the exam," Laplante said.

The study guide is $39.99 for IEEE members and $49.99 for nonmembers. http://ieeeusa.org/communications/ebooks/info.asp?Keyword=career&Product=Software+PE+Exam+%96+Sample+Questions+and+Solutions#=

PE Software exam registration begins 17 December. Check http://ncees.org/exams to find out about your state's approval and registration process. See exam specifications at http://engineers.texas.gov/downloads/ncees_PESoftware_2013.pdf...



Just as I predicted the people that have been pushing this have a vested interest in selling training material. What prices should there be on safety?


The Time At the Tone is Nov. 19th 2000. Say what?

On November 19th one of the primary Network Time Protocol (NTP) clocks, The Official Source of Time for the Department of Defense (DoD) for the Global Positioning System (GPS), and a Standard of Time for the United States, broke for 51 minutes, reporting that the year is now 2000, about 30 million seconds ago.

USNO NTP FAILURE -- 19 NOV 2012

On Monday, November 19, USNO made what was expected to be a routine upgrade. Unfortunately, for 51 minutes, between 21:07:32 - 21:58:56 UTC, the server gave out the year as 2000 instead of 2012. We have resolved the issue that caused this error.

We regret the disruptions that this may have caused. We strongly recommend that all NTP users configure their software to get time from three different sources at a minimum. Most software should be able to use the redundant data to identify and ignore incorrect time sources. You can find a list of other time sources at http://support.ntp.org/bin/view/Servers/WebHome.

Many of our Embedded Widgets rely on getting accurate time from Internet. Sometimes because we are to cheap to put in a real clock, or we think that the Internet will always be here and is always telling the truth which will give us accurate time.

Ask Bjørn Hansen who runs the http://www.pool.ntp.org time pool, what I believe to be the most common source of time for Embedded Widgets had some comments on the Nov. 19th incident.

The official advice from NTP is that you should always configure at least four different NTP time servers when you use NTP. No two from the same organization and, as much as possible, reachable only via diverse, nonintersecting paths, and no more than 128 ms apart. Can your Embedded Widget coupe with that? Many do not have the required resources to do it.

In an related time issue that shows that time can be truly hard to code correctly, as it can take literally forever to test all future dates, Android 4.2 Deletes December From People App.

One year one of my colleagues got a yearly calender that he used all year long. In December he showed us that Thursday December 17th was missing. Calendar went from Wednesday 16th to Thursday the 18th. The lesson here is that even pre-Internet technology still can't figure out time...


Wednesday, November 14, 2012

MARK V Home Computer Alarm Robo-Judge vs Google's 4ft Gator

Today [Nov/14/2012] reading Google's Server Cooling Plan Produces 4ft Alligator and the comments about adding a moat around the facility, reminded me of this classic from Creative Computing Magazine (Sep-Oct 1977). Now, 35 years later, this MARK V Alarm system is almost reality. What is left to do? Do take note of the impressive time marks.

 How'd you like to have a computer like this one:
    * D * A * N * G * E * R  *
        *  D  *  A  *  N *  G  * E * R *

I, the MARK V Home Computer Alarm, detect a suspicious looking individual attempting to force entry into the building.

Commencing Intruder Log:
18:33:47.023  Front door breached.
18:34:54.543  Photocell Checkpoint Alpha passed.
18:36:06.105  Weight of 97 kilograms detected on first stair-step.
18:37:22.133  Intruder on  landing; digital photograph taken.
18:37:22.345  Photograph stored and processed: analysis indicates White Anglo Saxon Catholic male with a scar above the left eye and a slight lisp.
18:37:22.665  Photograph dispatched via telesat to interpol.
18:37:22.982  Interpol returned id as "Greg Heiss," known computer thief  and Arlingtonite.
18:37:22.995  Energize defense system.
18:37:23.442  Target on fifth step of second tier.
18:37:23.445  Defense system ready.
18:37:25.045  Target at top of stairs. Lock on 50 megawatt laser.
18:37:25.050  Laser locked on. Query supreme court Robo-Judge for permission to terminate life of intruder.
18:37:25.052  Permission granted and verified.
18:37:25.053  ======  Z  A   P  ======
18:37:25.054  Switch air recirculation system to High Clean.
18:37:25.100  Notify building engineering office of repairs needed to front door and rear wall over stairs.
18:37:25.125  Reset alarm system.
18:37:25.143  Terminate Intruder Log.
       MARK V, ready.

[Alas they confuse Weight with Mass. Killiograms are a unit of Mass. Sigh.]


Sunday, October 28, 2012

Near Death at the Rhine Research Center

The Eve of All Saint's Day better known as Halloween is almost upon us this week. It is a sad commentary on society when we remember to celebrate the demonic and forget the pure. Why do I bring this up?

This week I found myself in Durham North Carolina, at the International Association for Near-Death Studies, Inc. They let me checkout their private library once they figured I was not a flake chasing ghosts. No one in these organizations have any interest and don't want to be bothered by Ghost Hunters et.al. I did not see my favorite book on the subject, for those that are technically inclined, is The Ghost of 29 Megacycles by, one of my favorite authors, the late John G. Fuller. What thirteen tones would you use?

While Near Death Experience are interesting I was really here to visit the Rhine Research Center, that shares office space with IANDS, to discuss their research into Human Biofields. In 1930, academic research into the field of parapsychology began at Duke University and in 1935 the Duke Parapsychology Labs were established. Joseph B. Rhine led this department and provided a professional study of parapsychology in a university environment.

One of the projects fitting to Halloween is trying to verify the research of Dr. Duncan MacDougall whom in 1907 tried to figure out how much a Human Soul weighed at the time of death, by measuring the weight of the body immediately before and after death. There is also a bit of newer research in the 1980's. As the research center does not want to kill anyone/anything they are trying to weigh people that clam to be able to leave their bodies, and see if it changes when they come back. Regardless of what you may think of the experiment, it still offers technical challenges that need solved. How would you design a precision weigh scale that needed to measure a change of +/- 5 ounces? Load Cells, LVDTs, or something fittingly strange? There are interesting challenges of layout and power supply design as well.

I spent a good two hours taking to the Executive Director, John Kurth about their current line of research into Biofeilds, the reason for my visit.

I was a bit disappointed, as all they are using is a Photo-Multiplier Tube in the Ultra-Violet range. They get people that claim to be able to do Energy Healing and such. They put them in a double dark room, establish a base line. An empty room has about four photons per minute. With anyone, you for example, will be in the ten to forty photons per minute. Of the 150+ people that they have tried the test on, they have found ten that give repeatable results every time. Some people just give "spikes" of photons with no pattern to them. People that ask for feedback learn to make more photons. The best person puts out 600,000+ photons per minute consistently. The highest peak they ever saw was 1.2M but it was not repeatable.

The reason for my disappointment was they knew nothing about such things as Mitogenic Radiation, and could not tell me if their PM was made of Quartz or Glass, which is important. Mitogenetic Radiation is the force or specific energy that is supposedly given off by cells undergoing division. It may in turn stimulate the process of mitosis in other cells, better known as Gurvich Radiation, named after Alexander Gurwitsch. See also Otto Rahn Invisible Radiations of Organisms. V.P. Kaznacheyev work is summarized in The Excalibur Briefing. Kaznacheyev work has been more recently carried on by Michaylova in Novosibirsk, that explains the Quartz/Glass issue..

At any rate it was an interesting few hours. They have the largest library of PSI related books I've ever heard of, and that makes a visit worthwhile if you are in the area.


Saturday, October 6, 2012

"What Good Are Strong Specifications?"

"I'll go up and find out what they need [this project to actually do], the rest of you stat coding it [right now]" is meant to be humorous, alas I've seen it the Real World far to often. What is our new widgets actually required to do (Validation: Have we built the correct device? Do we meet the customer's requirements)? Which brings us to the subject of this blog, writing software specifications (Verification: Have we built the device correctly? Did we find and remove all of the 'bugs'?) and User Documentation.

What Good Are Strong Specifications? [PDF] by Nadia Polikarpova, Carlo A. Furia, Yu Pei, Yi Wei and Bertrand Meyer Chair of Software Engineering, ETH Zurich, Switzerland.

Abstract:

Experience with lightweight formal methods suggests that programmers are willing to write specification if it brings tangible benefits to their usual development activities. This paper considers stronger specifications and studies whether they can be deployed as an incremental practice that brings additional benefits without being unacceptably expensive. We introduce a methodology that extends Design by Contract to write strong specifications of functional properties in the form of preconditions, postconditions, and invariants. The methodology aims at being palatable to developers who are not fluent in formal techniques but are comfortable with writing simple specifications. We evaluate the cost and the benefits of using strong specifications by applying the methodology to testing data structure implementations written in Eiffel and C#. In our extensive experiments, testing against strong specifications detects twice as many bugs as standard contracts, with a reasonable overhead in terms of annotation burden and runtime performance while testing. In the wide spectrum of formal techniques for software quality, testing against strong specifications lies in a "sweet spot" with a favorable benefit to effort ratio.

- {Trackback}

In a less formal, more practical implementation to the everyday Embedded System Developer, Doxygen is a popular method of generating documentation from source code. Doxygen can be extended with 'alias' to add features, and a thread over at Stack Overflow, Custom tags with Doxygen shows how to add 'Requirement' and 'Requirement Verification' aliases.

While Doxygen excels at Program Documentation, it is often pressed into service to generate User Documentation, which far to often a novel concept to software authors, that is not the domain Doxygen was intended for and often has to be beat into submission. On the other-hand AsciiDoc is written specifically to author User Documentation, and ADExtract.py can be used to extract the User Documentation from the source code files. If you truly want to keep your project on track then write the User Documentation first before any line of code is ever written. Keeping the Source Code, Program Documentation and User Documentation as a single file gives them the best hope of actually being maintained.

Something I always find extremely frustrating is the disconnect between Academia Research into Software Safety, and the Real World of "we must ship 782 Widgets by Friday to meet payroll!". Take for example Net-Centric Software & Systems Consortium's Software Safety Tutorial, that is reproduced below, which seems more like an expedition for finding more funding from industry. How do you actually apply this kind of information in the Real World? The European Network of Excellence of Embedded Systems Design is a bit more in-line with the concept that a product must having shipping it as one of its primary requiremnts...

Alas the problem is not just one of academic discussion as Dave Woll explains the issues of our aging infrastructure impending failure in The coming wave of process safety system migration: Systems changes require rigorous hazards analysis.

If you do like Slid Shows check out CPLD Course Draft International Software Safety Conference 2011:


"A Methodological Framework for Software Safety in Safety Critical Computer Systems"

The Journal of Computer Science is frequently overlooked in the Embedded Space for the solutions to many problems, for example the September issue covered topics as diverse as, Speed Control of Switched Reluctance Motor Using New Hybrid Particle Swarm Optimization for the hardware types and among us, and Fuzzy Cost Enabled Cluster Based Multipath Routing Algorithm for Mobile Ad-Hoc Networks for those putting together the latest sensor net.

Of particularly interest to me is A Methodological Framework for Software Safety in Safety Critical Computer Systems [PDF] by P. V. Srinivas Acharyulu and P. Seetharamaiah. These authors have put together one of the best introductions to issues related to the safety of systems controlled by software, from defining the terms to building a model system out of a real model train set to demonstrate the techniques described.

Abstract

"Software safety must deal with the principles of safety management, safety engineering and software engineering for developing safety-critical computer systems, with the target of making the system safe, risk-free and fail-safe in addition to provide a clarified differentaition for assessing and evaluating the risk, with the principles of software risk management. Problem statement: Prevailing software quality models, standards were not subsisting in adequately addressing the software safety issues for real-time safety-critical embedded systems. At present no standard framework does exist addressing the safety management and safety engineering priniciples for the development of software safety in safety-critical computer systems. Approach: In this study we propose a methodological framework involving safety management practices, safety engineering practices and software development life cycle phases for the development of software safety. In this framework we make use of the safety management practices such as planning, defining priniciples, fixing responsibilities, creteria and targets, risk assessment, design for safety, formulating safety requirements and integrating skills and techniques to address safety issues early with a vision for assurance and so on. In this framework we have also analysed integration of applicability of generic industrial heirarchy and software development heirarchy, with derived cyclical review involving safety professionals generating a nodal point for software safety. Results: This framework is applied to safety-critical software based laboratory prototype Railroad Crossing Control System (RCCS) with a limited complexity. The results have shown that all critical operations were safe and risk free. Conclusion: The development of software based on the proposed framework for RCCS have shown a clarified and improved safety-critical operations of the overall system peformance."

Journal of Computer Science
DOI: 10.3844/jcssp.2012.1564.1575
Volume 8, Issue 9
Pages 1564-1575

Do keep in mind it is an introduction, a real Rail Road Crossing Control System (RCCS) would be made from two or more systems running parallel, using different processors, different hardware developed by different teams in different languages such C and ADA. The real fun part is developing a system that must run for a few decades and not the eighteen month life span for many components today.


More Government Responses on Software License Questions

I have been covering how the Government is getting involved in writing firmware in a couple of past blogs. Two more States have responded to my questions.

The state of Idaho previously said they would send me a formal written letter with their response. I now have that in hand as you can see below. While the nostalgia of a formal letter is nice, was it really required when a email would have done?

Board of Professional Engineers and professional Land Surveyors

Dear Mr. Paddock


At its meeting on September 5 and 6, 2012 the Idaho Board of Licensre of Professional Engineers and Professional Land Surveyors reviewed the email inquiry about licensing of software engineers which you submitted to David Curtis dated August 5, 2012. You have raised some interesting question which the Board has voted to take under advisement and study. We will communicate with you further after we have had the opportunity to determine how we will handle the issues.

Please call if you have any questions

For the Board [Signed] David K. Bennion, P.E. Board Chair

DLC/DKB/dc:Paddock,Bob.2012-09 Meeting

From the state of Mississippi:

Mr. Paddock,

At this week's Board meeting, the members reviewed and discussed your email below.

Your questions about the exam should be referred to NCEES (www.ncees.org).

The requirements (education, examination and experience) are all on our website at www.pepls.state.ms.us; look at Initial PE licensure requirements. These requirements are set by both Mississippi statutes and by Board regulations.

If a person passes the NCEES Software PE exam in Mississippi, then the person would be a licensed Professional Engineer in this state. The license expires every Dec. 31; the current renewal rate is $35 and 15 hours of continuing education every year.

Regarding the use of the title "engineer", Mississippi statute 73-13-39 restricts this title to those who are licensed Professional Engineers. When it comes to the Board's attention that an unlicensed person is using this title in a public manner, such as to to solicit business, to claim credentials or to certify something, the Board is compelled by state law to direct the person to cease and desist.

I hope this information is helpful to you.

- Rosemary Brister