• Increase font size
  • Default font size
  • Decrease font size
Apogee Consulting Inc

Innovation: Not Invented Here Anymore

E-mail Print PDF

Google_Barge_Data_Center
In the 5/18/2014 edition of the National Defense Industrial Association magazine, Sandra Erwin wrote-

Cuts to federal spending have wreaked havoc on Defense Department research and technological pursuits, officials insist. Potential adversaries are modernizing while the next generation of U.S. weaponry remains bogged down in budget quagmires. … But the Pentagon also has itself to blame for losing the cutting edge, current and former defense officials contend. While budget cuts and sequestration have disrupted the Defense Department's research-and-development flow, they argue, a major impediment to innovation is a hidebound military establishment that cannot stay apace with advances in technology.

Another obstacle to innovation is the Pentagon's propensity to build 'big, robust, work-forever' systems with closed architectures that are incompatible with other software or computers … How the Pentagon connects with the private sector also hinders progress …

We've noted this challenge before. Others are noticing the same thing.

Bill Greenwalt, writing in Wired magazine, stated-

Despite some initially promising reforms in the early 1990s, the IT acquisition problem has gotten worse and the government continues to trail the private sector in its effective use of new technologies and approaches. Nor is the $500 billion annual federal acquisition problem limited to IT; it transcends major defense systems, research and development, construction, services contracting and commodities. A one-size fits all, rules based, Rube-Goldberg machine ensures that procurement failures are magnified and not left to chance.

The great mystery in all of this is why the federal government is failing in its IT programs when some of the best IT talent resides in U.S. The answer is that Silicon Valley is not involved in government contracting. … many of the most dynamic, innovative, successful, commercial firms will not bid on a standard government contract because of the costs of complying with federal acquisition rules and the limited returns associated with federal procurement. Limited? Think under ten percent for government contractors, versus returns of 20 percent and above in the commercial world.

Reforms made in the Federal Acquisition Streamlining Act of 1994 and the Clinger Cohen Act of 1996 made it easier to sell to the federal government, and for a while, commercial firms tiptoed into the federal market. However these reforms did not go far enough for many commercial companies. For example, the changes failed to remove the requirements to comply with unique government accounting standards, they failed to protect commercial intellectual property rights, and failed to stop arbitrary government audits. With the passage of time and without senior leadership support, bureaucratic inertia set in and resulted in the re-imposition of old requirements, in the creation of new barriers to doing business with the government, and in a de facto preference for government-unique rather than commercial solutions. So Silicon Valley did what it does best: ignore the government and make a lot of money elsewhere.

The current strained fiscal environment demands that the federal government move away from a process-driven acquisition system if it is ever going to access the cost saving opportunities and innovative solutions that have arisen in the commercial market. A system that only works by going around it is not a workable system and should be dismantled.

Not to be outdone, the Center for a New American Security issued a report (with significant input from former Deputy Defense Secretary William Lynn) that "the U.S. weapons industry moves too slowly to adjust to current trends." According to the Reuters story (link above), the report "said industry and government need to invest more in new technologies and remove regulatory and acquisition barriers that hinder U.S. firms. … The report called for reforms to allow more U.S. and foreign firms to participate in the U.S. weapons market, greater communication about the Pentagon's technology needs and measures to safeguard private intellectual property."

Whether you call it a triumph of bureaucracy or an innovation shortfall, the fact of the matter is that the Pentagon finds itself falling behind the private sector in terms of development speed and effectiveness. We don't have any brilliant answers to help DOD solve its innovation challenges, but we do have one observation to make.

When you keep buying based on the lowest priced solution, when you keep awarding contracts based on lowest perceived risk, when you insist on high Technology Readiness Levels … you are not going to get much innovation.

There was a time when basic research was seen as a public good, even when that research resulted in a dead end. The government was pleased to fund scientific inquiry, secure in the notion that knowledge was good and that progress would sooner or later result from that knowledge. Those days seem to have largely faded away. Nowadays we have Apple and Google and Facebook (which are the end product of government-funded research) and they seem to have plenty of money to splash around in the name of research and innovation.

You want to spearhead defense innovation? Then you had better ask one of those big players to help you out.

 

Choice of Contract Type

E-mail Print PDF

Back in the day we were somewhere in the Northeast, consulting on a new thing called "Program Management Effectiveness" or PME. PME was the result of applying a CMMI approach to Defense Program Management. It evaluated the maturity of numerous attributes and (hopefully) identified "pain points" experienced by the Program (or Project) Management team, so that the organization could eliminate them. It was a fairly successful service offering but, like so many things in the consulting biz, the ultimate success or failure was largely in the hands of the client. We could identify immature processes, capability gaps and pain points, but if the client took our output and then stuck it on the bookshelf to gather dust, then it was all just an expensive waste of time.

Our team deployed at a designer and manufacturer of aircraft. We were invited to evaluate a couple of in-process major design initiatives that, if successful, were going to be franchise programs for that contractor. The problem was that they were not going very well, and senior management wanted a fresh, independent, perspective on what the contributing problems might be.

We interviewed several IPT leads and various levels of program management. We interviewed Contracts folks and Subcontract Management folks and Procurement folks. We interviewed HR and IT and a host of other functions. We delivered on our end. We never really learned what the client did with our recommendations, but I still read about those programs today; and they seem to be relatively successful as new aircraft programs go.

Out of the many issues we identified, one is relevant to today's article. It concerns contract type.

One of the more important metrics used by senior program management was "time to contract," which essentially measured the time it took to get a suppler an executed contract, once the requirements had been identified. Obviously, the quicker the better, right?

Maybe not.

When we interviewed the Subcontract Management and Procurement folks, they were quite pleased at their "time to contract" metrics. So many of the suppliers had been put under contract early in the program, and the personnel involved were proud of their efforts. They were also proud that they had placed 100% firm, fixed-price (FFP) contracts with their suppliers. FPP subcontracts were seen as lower-risk, since they put the risk of cost overrun on the subcontractor instead of the prime contractor. The folks saw it as a huge feather in their caps that they had negotiated and placed FPP subcontracts so early in the program life cycle.

They had never considered the ramifications of putting FFP subcontracts in place before the overall design had been finalized. They had never considered the implications of putting their suppliers on contract without having a final detailed design in place.

One thing we all know for sure is that no design is fixed until it's completely fixed. Until the design is fixed, expect changes. Perhaps lots of them. And even after the design is fixed, complete, done - expect more changes. Because just like no plan of war survives contact with the enemy, no aircraft design survives contact with a design review team, or a systems engineering team, or a manufacturability team, or an "as-built" review team. Changes are a given in any defense contract, let alone one for an aircraft that had never been built before.

Thus, the SCM and Procurement folks had never considered that their early FFP subcontracts were going to be subject to a multitude of changes. Changes initiated by the IPTs, changes initiated by the subcontractor, changes initiated by the customer that impacted the subcontractor, etc. There were going to be lots and lots of changes as the design went through reviews, and each of those changes had the potential to generate Requests for Equitable Adjustment (REAs) that could impact that tidy FFP subcontract price the folks had so quickly negotiated.

Processing REAs takes time and money. Time and money which nobody had budgeted for. We pointed that out to the contractor's senior management team; but I don't believe they ever really understood the fundamental point. The fundamental point was that the requirements needed to be close to final before a FFP subcontract was negotiated. The fundamental point was that establishing a metric that incented people to move quickly might, in this set of circumstances, be counter-productive to smart program management. If they were going to award FFP subcontracts then those should come later in the program life cycle, not earlier. Awarding them too early was going to lead to downstream cost and schedule impacts.

The Under Secretary of Defense (Acquisition, Technology and Logistics), Honorable Frank Kendall, recently discussed when it would be appropriate to issue FFP contracts and when it would not be as appropriate to do so. As many readers know, the Obama Administration has been hell-bent-for-leather on issuing as many FFP contracts as possible, while avoiding as many cost-type contracts as possible-judging cost-type contracts to be higher risk than FFP contract types.

As we just illustrated, that is not always the case. And apparently Mr. Kendall agrees with us on that, especially when a development contract is being contemplated.

He wrote (link above)-

FFP development tends to create situations where neither the government nor the contractor has the flexibility needed to make adjustments as they learn more about what is feasible and affordable as well as what needs to be done to achieve a design that meets requirements during a product's design and testing phases. … Most sophisticated weapons systems development programs deal with maturing designs and challenging integration problems. As a result, the government often will and should provide technical guidance and make tradeoff decisions during development. … While it certainly is possible to negotiate changes in a fixed-price contract environment, the nature of development is such that informed decisions need to be made quickly and in close cooperation with our industry partners. The focus in a fixed-price environment is squarely on the financial aspects of the contract structure and not on flexibly balancing financial and technical outcomes.

Risk is inherent in development, particularly for systems that push the state of the art. Even with strong risk reduction measures in Technology Demonstration phases and with competitive risk reduction prototypes, there still is often a good deal of risk in EMD [Engineering, Manufacturing, and Development]. Here are the considerations I look for before I will approve a fixed-price or FPI [Fixed-Price Incentive] EMD program:

  • Firm Requirements
  • Low Technical Risk
  • Qualified Suppliers
  • Financial Capability to Absorb Overruns
  • Motivation to Continue [in the event of overrun]


There was more but that a good summary. Mr. Kendall emphasized that FFP or FPI contract types are preferred, but that the contract type must be right for the circumstances. We agree.

 

Admiral William McRaven Discusses "10 Life Lessons from Navy SEAL Training"

E-mail Print PDF

Admiral William McRaven is the Commander of the United States Special Operations Command (USSOCOM). In mid-May, he spoke to some 8,000 new graduates at the University of Texas commencement ceremony.

We here at Apogee Consulting, Inc. like to post thoughts about leadership and what it means to lead a workforce through challenging times, balancing near-term expectations with long-term success. We've often thought that the military services are a great place to learn and practice leadership skills. Thus, we are very pleased to offer Admiral McRaven's commencement speech to our readers, edited for space.

It matters not your gender, your ethnic or religious background, your orientation, or your social status. Our struggles in this world are similar and the lessons to overcome those struggles and to move forward-changing ourselves and the world around us-will apply equally to all.

I have been a Navy SEAL for 36 years. But it all began when I left UT for Basic SEAL training in Coronado, California. Basic SEAL training is six months of long torturous runs in the soft sand, midnight swims in the cold water off San Diego, obstacles courses, unending calisthenics, days without sleep and always being cold, wet and miserable. It is six months of being constantly harassed by professionally trained warriors who seek to find the weak of mind and body and eliminate them from ever becoming a Navy SEAL. But, the training also seeks to find those students who can lead in an environment of constant stress, chaos, failure and hardships. To me basic SEAL training was a life time of challenges crammed into six months.

So, here are the ten lesson's I learned from basic SEAL training that hopefully will be of value to you as you move forward in life.

1. Every morning in basic SEAL training, my instructors … would show up in my barracks room and the first thing they would inspect was your bed. If you did it right, the corners would be square, the covers pulled tight, the pillow centered just under the headboard and the extra blanket folded neatly at the foot of the rack-rack-that's Navy talk for bed. It was a simple task-mundane at best. But every morning we were required to make our bed to perfection. It seemed a little ridiculous at the time, particularly in light of the fact that were aspiring to be real warriors, tough battle hardened SEALs-but the wisdom of this simple act has been proven to me many times over.

If you make your bed every morning you will have accomplished the first task of the day. It will give you a small sense of pride and it will encourage you to do another task and another and another. By the end of the day, that one task completed will have turned into many tasks completed. Making your bed will also reinforce the fact that little things in life matter. If you can't do the little things right, you will never do the big things right. And, if by chance you have a miserable day, you will come home to a bed that is made-that you made-and a made bed gives you encouragement that tomorrow will be better.

If you want to change the world, start off by making your bed.

2. During SEAL training the students are broken down into boat crews. Each crew is seven students-three on each side of a small rubber boat and one coxswain to help guide the dingy. Every day your boat crew forms up on the beach and is instructed to get through the surfzone and paddle several miles down the coast. In the winter, the surf off San Diego can get to be 8 to 10 feet high and it is exceedingly difficult to paddle through the plunging surf unless everyone digs in. Every paddle must be synchronized to the stroke count of the coxswain. Everyone must exert equal effort or the boat will turn against the wave and be unceremoniously tossed back on the beach. For the boat to make it to its destination, everyone must paddle.

You can't change the world alone-you will need some help- and to truly get from your starting point to your destination takes friends, colleagues, the good will of strangers and a strong coxswain to guide them.

If you want to change the world, find someone to help you paddle.

3. Over a few weeks of difficult training my SEAL class which started with 150 men was down to just 35. There were now six boat crews of seven men each. [ Ed. Note: Do not question the Admiral's math.] I was in the boat with the tall guys, but the best boat crew we had was made up of the little guys-the munchkin crew we called them-no one was over about 5-foot five.

The munchkin boat crew had one American Indian, one African American, one Polish America, one Greek American, one Italian American, and two tough kids from the mid-west. They out paddled, out-ran, and out swam all the other boat crews. The big men in the other boat crews would always make good natured fun of the tiny little flippers the munchkins put on their tiny little feet prior to every swim. But somehow these little guys, from every corner of the Nation and the world, always had the last laugh- swimming faster than everyone and reaching the shore long before the rest of us.

SEAL training was a great equalizer. Nothing mattered but your will to succeed. Not your color, not your ethnic background, not your education and not your social status.

If you want to change the world, measure a person by the size of their heart, not the size of their flippers.

4. Several times a week, the instructors would line up the class and do a uniform inspection. It was exceptionally thorough. Your hat had to be perfectly starched, your uniform immaculately pressed and your belt buckle shiny and void of any smudges. But it seemed that no matter how much effort you put into starching your hat, or pressing your uniform or polishing your belt buckle-- it just wasn't good enough. The instructors would fine "something" wrong.

For failing the uniform inspection, the student had to run, fully clothed into the surfzone and then, wet from head to toe, roll around on the beach until every part of your body was covered with sand. The effect was known as a "sugar cookie." You stayed in that uniform the rest of the day-cold, wet and sandy. There were many a student who just couldn't accept the fact that all their effort was in vain. That no matter how hard they tried to get the uniform right-it was unappreciated. Those students didn't make it through training.

Those students didn't understand the purpose of the drill. You were never going to succeed. You were never going to have a perfect uniform. Sometimes no matter how well you prepare or how well you perform you still end up as a sugar cookie. It's just the way life is sometimes.

If you want to change the world get over being a sugar cookie and keep moving forward.

5. Every day during training you were challenged with multiple physical events-long runs, long swims, obstacle courses, hours of calisthenics-something designed to test your mettle. Every event had standards-times you had to meet. If you failed to meet those standards your name was posted on a list and at the end of the day those on the list were invited to-a "circus." A circus was two hours of additional calisthenics-designed to wear you down, to break your spirit, to force you to quit. No one wanted a circus.

A circus meant that for that day you didn't measure up. A circus meant more fatigue-and more fatigue meant that the following day would be more difficult-and more circuses were likely. But at some time during SEAL training, everyone-everyone-made the circus list. But an interesting thing happened to those who were constantly on the list. Over time those students--who did two hours of extra calisthenics-got stronger and stronger. The pain of the circuses built inner strength-built physical resiliency.

Life is filled with circuses.

You will fail. You will likely fail often. It will be painful. It will be discouraging. At times it will test you to your very core.

But if you want to change the world, don't be afraid of the circuses.

6. At least twice a week, the trainees were required to run the obstacle course. The obstacle course contained 25 obstacles including a 10-foot high wall, a 30-foot cargo net, and a barbed wire crawl to name a few. But the most challenging obstacle was the slide for life. It had a three level 30 foot tower at one end and a one level tower at the other. In between was a 200-foot long rope. You had to climb the three tiered tower and once at the top, you grabbed the rope, swung underneath the rope and pulled yourself hand over hand until you got to the other end.

The record for the obstacle course had stood for years when my class began training in 1977. The record seemed unbeatable, until one day, a student decided to go down the slide for life-head first. Instead of swinging his body underneath the rope and inching his way down, he bravely mounted the TOP of the rope and thrust himself forward.

It was a dangerous move-seemingly foolish, and fraught with risk. Failure could mean injury and being dropped from the training. Without hesitation-the student slid down the rope-perilously fast, instead of several minutes, it only took him half that time and by the end of the course he had broken the record.

If you want to change the world sometimes you have to slide down the obstacle head first.

7. During the land warfare phase of training, the students are flown out to San Clemente Island which lies off the coast of San Diego. The waters off San Clemente are a breeding ground for the great white sharks. To pass SEAL training there are a series of long swims that must be completed. One-is the night swim. Before the swim the instructors joyfully brief the trainees on all the species of sharks that inhabit the waters off San Clemente. They assure you, however, that no student has ever been eaten by a shark-at least not recently.

But, you are also taught that if a shark begins to circle your position-stand your ground. Do not swim away. Do not act afraid. And if the shark, hungry for a midnight snack, darts towards you-then summons up all your strength and punch him in the snout and he will turn and swim away.

There are a lot of sharks in the world. If you hope to complete the swim you will have to deal with them.

So, If you want to change the world, don't back down from the sharks.

8. As Navy SEALs one of our jobs is to conduct underwater attacks against enemy shipping. We practiced this technique extensively during basic training. The ship attack mission is where a pair of SEAL divers is dropped off outside an enemy harbor and then swims well over two miles-underwater-using nothing but a depth gauge and a compass to get to their target. During the entire swim, even well below the surface there is some light that comes through. It is comforting to know that there is open water above you. But as you approach the ship, which is tied to a pier, the light begins to fade. The steel structure of the ship blocks the moonlight-it blocks the surrounding street lamps-it blocks all ambient light.

To be successful in your mission, you have to swim under the ship and find the keel-the centerline and the deepest part of the ship. This is your objective. But the keel is also the darkest part of the ship-where you cannot see your hand in front of your face, where the noise from the ship's machinery is deafening and where it is easy to get disoriented and fail.

Every SEAL knows that under the keel, at the darkest moment of the mission-is the time when you must be calm, composed-when all your tactical skills, your physical power and all your inner strength must be brought to bear.

If you want to change the world, you must be your very best in the darkest moment.

9. The ninth week of training is referred to as "Hell Week." It is six days of no sleep, constant physical and mental harassment and-one special day at the Mud Flats-the Mud Flats are area between San Diego and Tijuana where the water runs off and creates the Tijuana slue's-a swampy patch of terrain where the mud will engulf you.

It is on Wednesday of Hell Week that you paddle down to the mud flats and spend the next 15 hours trying to survive the freezing cold mud, the howling wind and the incessant pressure to quit from the instructors. As the sun began to set that Wednesday evening, my training class, having committed some "egregious infraction of the rules" was ordered into the mud. The mud consumed each man till there was nothing visible but our heads. The instructors told us we could leave the mud if only five men would quit-just five men and we could get out of the oppressive cold.

Looking around the mud flat it was apparent that some students were about to give up. It was still over eight hours till the sun came up-eight more hours of bone chilling cold. The chattering teeth and shivering moans of the trainees were so loud it was hard to hear anything and then, one voice began to echo through the night-one voice raised in song. The song was terribly out of tune, but sung with great enthusiasm.

One voice became two and two became three and before long everyone in the class was singing. We knew that if one man could rise above the misery then others could as well. The instructors threatened us with more time in the mud if we kept up the singing-but the singing persisted. And somehow-the mud seemed a little warmer, the wind a little tamer and the dawn not so far away.

If I have learned anything in my time traveling the world, it is the power of hope. The power of one person-Washington, Lincoln, King, Mandela and even a young girl from Pakistan-Malala-one person can change the world by giving people hope.

So, if you want to change the world, start singing when you're up to your neck in mud.

10. Finally, in SEAL training there is a bell. A brass bell that hangs in the center of the compound for all the students to see. All you have to do to quit-is ring the bell. Ring the bell and you no longer have to wake up at 5 o'clock. Ring the bell and you no longer have to do the freezing cold swims. Ring the bell and you no longer have to do the runs, the obstacle course, the PT-and you no longer have to endure the hardships of training.

Just ring the bell.

If you want to change the world don't ever, ever ring the bell.

Start each day with a task completed.

Find someone to help you through life.

Respect everyone.

Know that life is not fair and that you will fail often, but if you take some risks, step up when the times are toughest, face down the bullies, lift up the downtrodden and never, ever give up-if you do these things, then next generation and the generations that follow will live in a world far better than the one we have today and-what started here will indeed have changed the world-for the better.

Thank you very much. Hook 'em horns.

 

Goodbye SOP 81-1 and SAB 104 and Topic 605: Hello Topic 606

E-mail Print PDF

We suspect that many readers will find the headline of this blog article more than a little difficult to decipher. The title discusses changes to Generally Accepted Accounting Principles (GAAP) in the area of revenue recognition. Revenue recognition doesn't often factor into government contract accounting, since the primary focus tends to be on contract cost accounting rather than the measurement of revenue (and project margin) during contract performance. Nevertheless, government contractors and their accountants (both internal and external) spend a lot of time thinking about revenue recognition on government contracts.

For example, if you have a firm, fixed-price contract to deliver 20 widgets over a 36-month period of performance, do you recognize revenue as each widget is delivered (say, at 1/20th of the contract price for each delivery) or do you recognize revenue based on the percentage of completion of the entire contract? What about if you believe you planned profit won't materialize because of unplanned cost growth? How does that knowledge factor in to the picture? What's the impact on revenue recognition when you file a Request for Equitable Adjustment (REA) that you believe will lead to a contract modification that will cover the cost growth? What happens if you file the REA but the government customer rejects it?

These are just some of the questions involved in government contractor revenue recognition. And we didn't even touch on issues such as providing services at fixed hourly rates, accounting for repairs and warranty expense, and contracts that involve multiple CLINS, each with a different contract type. Suffice to say, for those accountants who deal with the matter, proper measurement of revenue at a government contractor is far from easy.

And things just got more complicated. It's called "convergence".

Convergence is the elimination of differences between U.S. GAAP and International Financial Reporting Standards (IFRS). It has been in process since 2000 and is nearing a significant milestone: the merging of revenue recognition standards. In May 2013, the Financial Accounting Standard Board (FASB) issued Topic 606, entitled, "Revenue from Contracts with Customers." At the same time, the International Accounting Standards Board (IASB) is issuing IFRS 15 with the same title.

According to the FASB, Topic 606 establishes the following broad process steps:

Step 1: Identify the contract(s) with a customer.

Step 2: Identify the performance obligations in the contract.

Step 3: Determine the transaction price.

Step 4: Allocate the transaction price to the performance obligations in the contract.

Step 5: Recognize revenue when (or as) the entity satisfies a performance obligation.

The FASB believes that the new revrec principles will make it easier on companies, because they are more broad-based than previous GAAP and some industry-specific topics (e.g., SOP 81-1) are being discontinued.

There's more - far more - to the new Topic than we've glossed-over here. For instance, our initial reading seems to confirm that percentage of completion, cost to cost, revrec will still be permissible under Cost-Type contracts. But you will need to read the Topic closely if you are one of the affected companies.

You are one of the affected companies if you are a public entity, in which case you have until December 2016 to implement any required revrec changes. If you are a nonpublic entity, you have an extra year. But make no mistake, Topic 606 is the new Standard for revenue recognition and you had better prepare for it.

 

DCAA Audits of Contractor Mandatory Disclosures

E-mail Print PDF

After a tortuous journey lasting nearly two years, I published a new article in the May edition of West's Government Contracts Costs, Pricing & Accounting Report (edited by Karen Manos, Esq.). It addressed challenges posed by DCAA's approach to auditing contractor disclosures made pursuant to the requirements of the 52.203-13 contract clause. You can find the article under "knowledge resources" on this site.

But of course you must be a member in order to access that part of the site. Membership has privileges, after all.

Thank God the article was published in mid-May, because just a couple of weeks later the DCAA website was updated with new audit guidance that mooted much if not all of my points.

The new audit approach outlined in the MRD (link above) triages contractor disclosures based on risk and creates a more efficient audit process for those contractor disclosures that are risky enough to warrant an audit.

The first step in the new audit approach is for the Justice Liaison Auditor (JLA) at Fort Belvoir to evaluate each contractor disclosure received from the DOD Inspector General. The JLA will classify each contractor disclosure into an "Information Notification" or an "Action Required Notification." The JLA will consider "the nature of the violation being disclosed; the impact or damage to the Government; the impact on current or future audit planning; and the potential that an audit or an assessment could impact ongoing criminal or civil investigations."

When formal action is requested via an Action Required Notification then the FAO "will not be required to conduct a GAGAS compliant examination of the disclosure as an immediate response. Instead, the FAO will establish an assignment using DMIS Activity Code 17920 and conduct a disposition analysis to determine the best course of action to address the disclosure. Follow the guidance discussed in CAM 4-707 for general procedures for a disposition analysis. The FAO will (generally) have 60 days to disposition each Notification it receives from the JLA.

The FAO can disposition the ARN without too much in the way of follow-up activity. The CAM states:

An auditor may conclude that a contractor disclosure is other than high risk only after the completion of a disposition analysis. A documented disposition analysis will ensure our audit resources are efficiently used while fulfilling our audit responsibilities under the program.

a. Some examples of criteria for assessing the risk of a contractor's disclosure while performing a disposition analysis may include:

(1) the nature of the subject matter disclosed,

(2) financial or monetary degree of damage to the Government,

(3) prior significant deficiencies noted on the relevant control environment, and

(4) the contractor's degree of compliance with the Contractor's Code of Business

Ethics and Conduct Program (see CAM 5-306)

There are more details in the CAM (now). If you are dealing with a contractor disclosure, you really need to read that new section in the CAM to understand the new DCAA audit approach.

 


Page 132 of 279

Newsflash

Effective January 1, 2019, Nick Sanders has been named as Editor of two reference books published by LexisNexis. The first book is Matthew Bender’s Accounting for Government Contracts: The Federal Acquisition Regulation. The second book is Matthew Bender’s Accounting for Government Contracts: The Cost Accounting Standards. Nick replaces Darrell Oyer, who has edited those books for many years.