Affordability

How do you define affordability?  By combining our personal experience with Webster's definition of 'afford,' we can perhaps arrive at a more relevant meaning.  Note that while it includes the purchase price and implies an ability to pay that price, it also covers the performance and availability requirements of the product or service.  Naturally, all of this is through the customers' filter.  Regardless of price, if a product or service doesn't respond to the buyer’s requirements or isn't available when needed, they can’t afford it.


The Department of Defense defines affordability as the degree to which the life-cycle cost of an acquisition program is in consonance with the long-range investment and force structure plans of the Department of Defense or individual DOD Components.  Affordability procedures establish the basis for fostering greater program stability through the assessment of program affordability and the determination of affordability constraints.  Affordability management is part of the OMB's balanced scorecard evaluation of government projects.  It is also a Systems Engineering metric and -- for most business people -- a criteria for decision making.  

Speaking from PRICE Systems' cost estimating perspective, Making the Case for Affordability Management, it is based on a credible estimate, a method for controlling project growth and a captured knowledge base from which to make future decisions.  It isn't any one of these three things, it is all of them reinforcing one another and building upon one another at every gate in the project life cycle. 

How do you define affordability at your company?  Do you rely on analyses like CAIV or something else? What are your 'must have' tools?  Tell us what you think! 

SYSTEMS ENGINEERING "META 'V'" - ON THE RIGHT TRACK?

Monday, August 8, 2011 by Quentin Redman

PRICE Systems is involved with the formulation of the total Life Cycle/Whole Life of systems of systems and is asking the question, "Is the META 'V' on the right track?"

INCOSE is considering the total life of the system, the traditional Development Engineering V must be expanded to account for the life of the system beyond Initial Operational Capability.  In this writer's opinion, we have to extend the development V to account for this with this Meta-V concept
.  The Affordability Working Group recognizes that IOC is:

·        The initial release of both the Primary and Enabling system; and the initial release of a successful system continues to evolve to meet environmental changes. Further, monitoring and feedback are integral parts of the evolutionary process.

                                                   


What do you think?  Post a comment or a question; we'd love to hear from you.

INCOSE DESIGN FOR AFFORDABILITY INITIATIVE

Friday, July 29, 2011 by Quentin Redman

PRICE Systems is integral in the INCOSE Design for Affordability Initiative as a vital member of the Working Group Internationally.

The INCOSE Affordability Working Group’s definition of Affordability is:

Affordability is the balance of system performance, cost and schedule constraints over the system life while satisfying mission needs in concert with strategic investment and organizational needs.

The INCOSE Affordability Working Group’s definition of SE Design for Affordability is:

Design for Affordability is the Systems Engineering practice of balancing system performance and risk with cost and schedule constraints over the system life satisfying system operational needs in concert with strategic investment and evolving stakeholder value.

 

To meet the Affordability Working Group goals we need to move from the conceptual to the concrete (i.e., how do we demonstrate that the affordability of a system has been improved; or define the trade space).  To do this, we can decompose the definitions into their potential constituent parts.  The definitions lead to considering three constituents for affordability:

Which represent the central concept of affordability as “Cost of Capability over time.”

 

a.      Required Capability – what does the system contribute to the mission or the next higher System Context, or How does the system generate operational value? e.g., search, detection, rescue, transport

b.      Required Capability Performance – How well must the system perform the required capability, e.g., defeat X% of the threats, detect Y% of the targets, or top speed of N kts. How do we measure?

c.      Budget, Risk and Schedule – Resources, technical, financial & temporal available to provide the capabilities and needed performance (system value). How do we measure?

System Life Cycle or Affordability over time

It is important to note that there is a significant difference between the INCOSE approach and the Gate’s definition.  That is, INCOSE is addressing the entire system life cycle while Gate’s considers “conducting a program”.  This is a significant difference as the B-52 is a single system; however, there have been many programs over the life of B-52 system.  Since INCOSE is considering the total life of the system, the traditional Development Engineering V must be expanded to account for the life of the system beyond Initial Operational Capability.The Affordability Working Group recognizes that IOC is:

·        The initial release of both the Primary and Enabling system; and

·        The initial release of a successful system continues to evolve to meet environmental changes.

Further, monitoring and feedback by PRICE Systems as a member of the INCOSE Working Group are integral parts of the evolutionary process.