PMT 360 Exam 2
Terms in this set (41)
1. The payment event or criteria. 2. The definition of successful completion. 3. The value of the event. All three pieces need to ne considered together to ensure adequate cash flow to the contractor. Appropriate motivation for the contractor and that achieving the payment events will lead to the successful completion of the contract.
Techinical Management Processes
1. Techinical Planning
2. Requirements Management
3. Configuration Management
4. Interface Management
5. Techinical Data Management
6. Decision Analysis
7. Techinical Assessment
8. Risk Management
Ensures that the SE processes are applied properly throughout a system's life cycle, includes defining the scope of the techinical effort required to develop, field, and sustain the system, as well as providing critical quantative inputs to program planning and life cycle cost estimates.
Ensures bi-directional traceability from the high level requirements down to the syste elements through the lowest level of the design (top-down) and from any derived lower level requirements up to the applicable source from which it originates (bottom-up)
Establishes and maintains the consistency of a systems functional, performance, and physical attributes with its requirement, design and operational documentation throughout the systems life cycle.
Ensure interface definition and compliance amoung the systems elements, as well as with other systems. Documents all internal and external interface requirements and requirement changes in accordance with the programs Configuration Management Plan.
Technical Data Management
Identifies, acquires, manages, maintains, and ensures access to the techinical data and computer software required to manage and support a system throughout the acquisition life cycle.
Transforms a broadly stated decision opportunity into a traceable, defendable, and actionable plan. Enploy procedures, methods, and tools, such as trade studies, for identifying, representing, and formally assessing the important aspects of alternative decisions to select an optimum decision.
Compares achieved results with defined creteria to provide a fact based understanding of the current level of product knowledge, technical maturity, program status, and technical risk. Includes methods such as technical reviews and use of technical performance measures. (TPMs)
Involves the mitigation of program uncertainities that are critical to achieving cost, schedule and performance goals at every stage of the life cycle. Encompass identification, analysis, mitigation, and monitoring of program risks.
1. Stakeholders Requirements Definitions
2. Requirements Analysis
3. Architecture Design
Stakeholder Requirements Definitions
Involves the translation of requirements from relevant steakholders into a set of top level techinical requirements. The process helps ensure each individual steakholder's requirements, expectations, and perceived constraints are understood fromt the acquisition perspective.
Involves the decomposition of top level requirements captured by the steakholders requirements definition process into a clear, achieveable, verifiable and complete set off system requirements.
Involves a trade and systhesis process that translates the outputs of the Steakholder Requirements Definition and Requirements Analysis processes into a system allocated baseline that describes the physical architecture of the system and the specifications that describe the functional and performance requirements for each configuration item along with the interfaces that compose the design.
Involves two primary efforts, detailed design and realization. Outputs included the detailed design down to the lowest system elements in the system architecture , and the fabrication/production procedures.
Incorporates the lowest level system elements into a higher-level system element in the physical architecture. Key schedule risk area.
Provides evidence tha the system or system element performs its intended functions and meets all performance requirements listed in the system performance specification and functional and allocated baselines. Verification answers the question, "Did you build the system correctly?"
Provides objectives evidence that the capability provided by the system complies with steakholder performance requirements, achieving its use in its intended operational environment. Validation answers the question, "Is it the right solution to the problem?"
Moves any system element to the next level in the physical architecture. For the end-item system, it is the process to install and field the system to the user in the operational environment.
Cost Reimbursement Contracts
Cost Plus Fixed Fee
Cost Plus Incentive Fee
Cost Plus Award Fee
Fixed Price Contracts
Firm Fixed Price
Fixed Price Award Fee
Fixed Price Incentive (Firm Target)
Best Effort, Low Risk to Contractor, High Risk to Government, Invoice payments.
Shall Deliver, High Risk to Contractor, Low Risk to Government, Performance or Progress Payments
Getting to a MDD (Material Development Decision)
JCIDS Capability Based Assesment (CBA) leading to a ICD, approval to enter acquisiton process.
Materiel Solution Analysis Phase (MSA)
Guided by Validated ICD, AoA Study Plan. Major activities - Conduct AoA, Develop AS, Draft CDD and translate capability gaps into specific requirements.
AS must be approved by MDA prior to RFP release prior to TMRR activities. Includes Acquisition approach and Business strategy, Framing assumptions adn Risk management (should cost targets)
Technology Maturation and Risk Reduction Phase (TMRR)
Basis for entry MDA approved Materiel soulution and Acq Strat - Major activities: Competitive prototyping, preliminary design review (PDR) CDD Validation, Plan for sustainment, develop RFP release, technology readiness assessment (TRA). Phase is complete when afforddble increment of military-useful capability identified: technology demostrated in relevant environment\; manufacturing risks identified: PDR conducted prior to Milestone B (unless waived)
Spectrum Certification Process
1. Spectrum Certification
2. Host Nation Coordination
3. Frequency Assignment
4. Electromagnetic Compatibility
Organizations Involved in Spectrum Certification Process
International Telecommunications Union (ITU)
DOD Military Communications Electronic Board (MCEB) aka Combatant Commands (CCMD)
Federal Communications Commission (FCC)
National Telecommunications and INformation Administration (NTIA & FCC)
Conceptual Application - MDD
Conceptual allocation is prudent prior to releasing funds for studies or assembling "proof-of-concept" test-beds. Initial planning complete, including proposed frequency bands
Expermental Application - Milestone A
An experimental allocation is required prior to the release of funds for building a radiating test model or assignment of a radio frequency for experimental usage. Preliminary design complete, radiation using test equipment and preliminary models may be required
Developmental Application - Milestone B
Prior to the release of funds for engineering development models, or assignment of a radio frequency for developmental usage, a stage three allocation must be obtained. Major design complete and radiation required for testing\
Operational Application - Milestone C
An operational radio frequency allocation is mandatory prior to release of funds for production units. Development is complete and final operating constraints or restrictions required to assure compatibility need to be identified.
Notes to Holders
A mechanism that allows minor changes
to an existing frequency allocation in lieu of generating a new, separate allocation. Minor Changes Allowed: Adding the nomenclature Adding Comment that have already been provided Documenting minor modifications or improvements that do not alter operating characteristics
System Requirements Review - SRR
The SRR ensures tha tthe PMO, user and contractor all have a common understanding and agreement on the system level techinical requirements and the associated costs, schedule and risks associated with realizing a system to meet the requirements.
Processes used throughtout architectual design
Decision Analysis, Interface Management, Risk Management
What the system must do - functions How well it must do it - performance - at the "system" level Defines the interfaces/dependencies among the functions, groups and the environment. Main artifacts = System Performance Spec and Subsystem/Segment Specs.
Describes how system level functional and performance requirements are allocated to physical components (hardware items, software items, and users) Describes the interfaces among system components and external systems/environment. Main artifacts = Hardware Configuration Item Performance Spec, Computer Software Configuration Item Requirements Spec, Interface Requirement Spec.
Describes in detail how to fabricate components and code software and how to manfacture, operate and maintain the system and its componenets and how to train various users. (CDR)
the repeated alloication of processess to design next lower layer system or to realize next upper layer end products withing the system structure.
the applications of a process to the same product of set of products to correct a discovered discrepancy of other variation from requirements.