Page 1 A Guide to the Procurement of Trusted Systems: An ... - csirt
Page 1 A Guide to the Procurement of Trusted Systems: An ... - csirt
Page 1 A Guide to the Procurement of Trusted Systems: An ... - csirt
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
System<br />
U<br />
Resource Requirements & Constraints<br />
C<br />
Programming Affordability Affordability Firm Unit O<br />
& Budgeting Goals Constraints Costs N<br />
System<br />
Figure 2-1 Key Interactions<br />
2.2.1 PLANNING, PROGRAMMING AND BUDGETING<br />
PPBS is supported by three operational functions: 1) <strong>the</strong> Action Officer (AO)<br />
is <strong>the</strong> primary advocate <strong>of</strong> a particular program. He/she develops a Program<br />
Decision Package (PDP) and presents it <strong>to</strong> senior management. 2) The Program<br />
Element Moni<strong>to</strong>r (PEM) is <strong>the</strong> functional staff advocate. The PEM guides and<br />
moni<strong>to</strong>rs PDPs through <strong>the</strong> PPBS process. When a PDP is approved, <strong>the</strong> PEM<br />
moni<strong>to</strong>rs and briefs its progress (e.g., quarterly). The AO needs <strong>to</strong> stay in<br />
contact with <strong>the</strong> PEM <strong>to</strong> ensure <strong>the</strong> latest information is available. 3) The<br />
Resource Advisor (RA) is <strong>the</strong> person in <strong>the</strong> SPO or PMO who moni<strong>to</strong>rs <strong>the</strong> use<br />
<strong>of</strong> resources on a day-<strong>to</strong>-day basis, helps develop fund targets, and prepares<br />
<strong>the</strong> annual budget submission.<br />
2.2.2 REQUIREMENTS GENERATION<br />
The mission users are present in all acquisitions. They generate mission<br />
requirements and ultimately receive and use <strong>the</strong> item or services acquired. The<br />
user function may be represented by a functional area expert, a major<br />
organization (e.g., agency), or even a special <strong>of</strong>fice. The user sometimes<br />
maintains a liaison in <strong>the</strong> Program Office.<br />
2.2.3 ACQUISITION MANAGEMENT<br />
This function can be fur<strong>the</strong>r divided in<strong>to</strong> Program Management and Contract<br />
Management. 1) The program management function could have any <strong>of</strong> several names<br />
- PMO, SPO, or Program Office. In a large acquisition, <strong>the</strong> program<br />
management function is a separate organization staffed with specialists who<br />
are tasked <strong>to</strong> conduct <strong>the</strong> acquisition. In a small acquisition, it could be one<br />
person. 2) A contracting function is present in all acquisitions and usually<br />
includes a Contracting Officer and a Buyer. The contracting function may be<br />
located within <strong>the</strong> program management organization or within a special<br />
contracting activity. The Contracting Officer is <strong>the</strong> ~ person authorized <strong>to</strong><br />
obligate <strong>the</strong> Government (i.e., negotiate, modify, and sign contracts). It is<br />
important <strong>to</strong> seek <strong>the</strong> Contracting Officer's advice and assistance early <strong>to</strong><br />
avoid later problems.<br />
2.3 FINANCIAL MANAGEMENT<br />
A structured process <strong>of</strong> identifying financial requirements, obtaining funds,<br />
and allocating <strong>the</strong>m <strong>to</strong> competing programs (so <strong>to</strong>p priorities are satisfied) is<br />
T<br />
I<br />
<strong>Page</strong> 22