You are currently not logged in! Enter your authentication credentials below to log in. You need to have cookies enabled to log in.
This is an old revision of the document!
OBOGS?
OBOGS?
Definition: This core qualification involves the ability to meet organizational goals and customer expectations. Inherent to this ECQ is the ability to make decisions that produce high-quality results by applying technical knowledge, analyzing problems, and calculating risks.
JPALS2
Definition: This core qualification involves the ability to manage human, financial, and information resources strategically.
V-22 JPALS incentive?
In 2016, I developed a novel incentive approach which ultimately reduced the total contract price of an ACAT 1 program by 2%. It was a failure: the incentive was designed to reduce Total Ownership Cost (TOC) by adding incentive payments, increasing contract price. Nonetheless, I am proud of how the incentive was structured to align Navy and Contractor interests, and how broad the consensus was that this was the right path forward.
In the late spring of 2016, I was the lead Reliability and Maintainability (R&M) engineer on the Joint Precision Approach and Landing System (JPALS). For various reasons, we were under pressure to sign a new contract, and were on track to get one at the end of the summer. As I suddenly learned, we also intended to directly incentivize reliability improvement. This was bad: All the low-hanging fruit were already plucked, so the remaining reliability increases might significantly increase TOC –JPALS was likely to pay an incentive fee and also realize increased TOC. Worse, it would poisoned an unusually good contractor relationship by paying more for a less sustainable system. If we were to reduce TOC, we would have to align the contractor's incentives with ours. I asked for and was given a few days to build a better option.
Over one late evening, I developed a metric which paralleled TOC, but was simplified enough to put on contract. Instead of a series of performance goals it would use a sliding scale. Finally, three obstacles remained: it needed a simple method of estimating prices, it needed some proof that every way of increasing incentive payment would redound to the Navy's benefit, and it was novel enough to need careful explanation.
For cost estimating, I leveraged trust I had built with the 4.2 Cost experts. Although by policy 4.2 will not release detailed cost models, JPALS had some of the best cost estimators I have worked with. We were able to identify a more basic estimating method which they could still endorse as valid, but which was releasable and unambiguous enough for contracting.
For proof of goodness, I had recently investigated a general-purpose analysis tool (Octave) as a way of modelling system-of-systems availability. It was ineffective for that, but was ideally suited for producing multi-dimensional graphs of TOC over the entire possibility space of JPALS design changes. We showed that increased incentive fee always followed better performance, and the proof was an impressive-looking visual.
Convincing, in 100 words or less
Definition: This core qualification involves the ability to build coalitions internally and with other Federal agencies, State and local governments, nonprofit and private sector organizations, foreign governments, or international organizations to achieve common goals.
JPALS 1
Building Coalitions is challenging enough when working from the top down, but my greatest success came when I had no positional authority.
Nearly ten years ago, I was a lowly CSS contractor supporting R&M Engineering on the Joint Precision Approach and Landing System (JPALS). JPALS was an ACAT 1 program originating in early '90s to develop a system based on GPS which could replace the current ground-radar-based navigation and landing systems, including in areas with degraded or denied GPS. Very cool stuff. The basic technology had been demonstrated years earlier, but the program had hit various snags. I had arrived just in time for Milestone B, and departed shortly before Milestone C. After a long delay for a nasty protest and a thorough-but-rapid run to PDR, I faced several key challenges: IETMs support, FMECA quality, and