Fever Chart / StoplightReporting Standards for PDS Nodes

Bill Knopf

RYG

PDS Stoplight Reporting Standards

• The "G" indicator should universally mean that all is going smoothly with a flight project interaction, throughout pipeline development, data review, and deliveries.

PDS Stoplight Reporting Standards• The "Y" and "R" indicators will vary, depending on whether

they are being reported by a Lead Node or a Participating Node, as follows:

– A Participating Node will note issues with a flight project with a "Y" indicator if the Node believes it can resolve the issues on its own. If not, the Participating Node will tag the flight project with a "R" flag, which indicates that help is required from the Lead Node.

– A Lead Node will note issues with a flight project with a "Y" indicator if the Node believes it can resolve the issue to the satisfaction of the Participating Node. If not, the Lead Node will tag the flight project with an "R" flag, which indicates that help is required from HQ.

PDS Stoplight Reporting Standards

• For this to work effectively, proactive communication between the Lead Node and all Participating Nodes associated with a flight project is assumed.

• In the rare event of a breakdown of communications, or an even rarer instance where two or more nodes disagree, a "B" (black) indicator may be used by any node.– This will ensure that help from Program and HQ

Management is on the way.

PDS Lead and Participating Nodes• As to establishment of a Lead Node and

Participating Node(s) for a newly selected flight project, the PDSMC will meet (in-person or via telecon/videocon) to appropriately distribute responsibilities and assignments.

• I suggest that a PDS Letter of Understanding be issued to the flight project PI, Project Manager and Program Office.– A goal of these actions is to ensure stability in the

Lead/Participating Node structure to minimize or eliminate the need to make changes downstream.