|
PEO/Executive
Pentagon Action Officer
|
Acquisition oversight, funding
advocacy
Motivate introduction of new/commercial
technologies
Policy issues
|
Overview/introductory info
Baseline reference document
Cliff's Notes approach -- provides
high-level, 4-6 page quick study
Tradeoff information
|
|
System Program Manager (SPM) and
Technical Staff
(Includes FFRDCs (MITRE, etc.) and may
include government laboratories)
|
Writes Request for Proposal (RFP) or some
form of solicitation based on user requirements
Reviews proposals and selects
developers
Manages development and/or maintenance
work
|
All of previous category,
plus:
Taxonomies to aid in identifying
alternatives
Back pointers to high-level, related
technologies
Criteria and guidance for
decision-making
Tech transfer/insertion
guidelines
Selected high-value references to more
technical information, to include usage and experience
data
Generally the sort of analysis and survey
information that would not be accomplished under normal
project circumstances
|
|
Developer (to include research and
development (R&D) activity)
|
Performs advanced development,
prototyping, and technology investigation focused on risk
reduction and securing competitive advantage
Concerned about transition and insertion
issues
Writes a proposal in response to
solicitations
Performs engineering development and
provides initial operational system
|
Same as previous category.
|
|
Maintainer
|
Maintains operational system until the
end of the life cycle
Responds to user requirements for
corrections or enhancements
Concerned about inserting new
technologies and migrating to different
approaches
|
Same as previous category.
|
|
User
|
Communicates operational needs
End customer for operational
system
|
Communicates alternatives and risks, and
provides perspective of what technology can (reasonably)
provide
|
