Part IV Flashcards

(56 cards)

1
Q

What are the elements of a system?

A

Configuration items, subsystems, segments, components, assemblies, and parts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What disciplines support systems engineering?

A

Also include PQM, Software Dev, and cybersecurity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

SE IPT activities

A
  • Translate the Need
  • Define the Design
  • Monitor the Design
  • Assure Design Quality
  • Test the Design
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

3 legs of innovation/problem solving stool

A

Commerical industry, government employees, academic/research centres

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

3 FFRDC categories

A
  • System Engineering and Integration Centers
  • Study and Analysis Centers
  • Research and Development Centers (includes national laboratories)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Generally what does the SEP define

A

Who, what, when, why, and how

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

When do PDR and CDR happen?

A
  • PDR - TMRR
  • CDR - EMD
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

When are PDR and CDR mandatory?

A

For all program initiated before MS-C

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

SVR

A

The SVR establishes and verifies final product performance. The SVR is an audit trail from the Critical Design Review (CDR) that assesses the system final product meets the functional requirements derived from the Capability Development Document (CDD) to the Functional, Allocated, and Product Baselines.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

PCA

A

The PCA is a “physical, hands-on” audit that verifies the product (as built) is consistent with all baseline documentation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Process for integrating cybersecurity into the acquisition life cycle

A

RMF

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Cybersecurity in the Acquistion Life Cycle

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Cybersecurity Objectives

A

Prevention of damage to, protection of and restoration of computers, electronic communication systems, electronic communication services, wire communication, and electronic communication, including information contained therein, to ensure its confidentiality, integrity, and availability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

SE V Model

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

SE Risk Management Tools

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Commericial Item vs. COTS

A

Formally, COTS is a commercial item sold in substantial quantities in the commercial marketplace and offered to the Government under a contract or subcontract at any tier, without modification, in the same form in which it was sold in the marketplace.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Baselines

A

Functional Baseline - The approved functional requirements for a product or system describing the functional, performance, interoperability, interface, and verification requirements established at a specific point in time and documented in the functional configuration documentation.
Allocated Baseline - Documentation that designates the Configuration Items (CIs) making up a system and then allocates the system function and performance requirements across the CIs (hence the term “allocated baseline”). It includes all functional and interface characteristics that are allocated from those of a higher-level CI or from the system itself, derived requirements, interface requirements with other CIs, design restraints, and the verification required to demonstrate the achievement of specified functional and interface characteristics. The performance of each CI in the allocated baseline is described in its item performance specification.
Product Baseline - Documentation describing all of the necessary functional and physical characteristics of the Configuration Item (CI), the selected functional and physical characteristics designated for production acceptance testing, and tests necessary for deployment/installation, operation, support, training, and disposal of the CI. The initial product baseline is usually established and put under configuration control at each CI’s Critical Design Review (CDR), culminating in an initial product baseline at the system-level CDR. The system product baseline is finalized and validated at the Physical Configuration Audit (PCA).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

HSI & Maintenance

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

ASOE

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

DoD Architecture Focus

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What are the CMMI flavours?

A
  • DEV
  • ACQ
  • SVC
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What is SCAMPI?

A

Based on the CMMI model used, a SCAMPI evaluation enables a sponsor to:
* Gain insight into an organization’s capability by identifying the strengths and weaknesses of its current processes relative to appraisal reference model(s).
* Focus on improvements (correct weaknesses that generate business risks) that are most beneficial to the organization given its current level of process implementation.
* Identify risks relative to achieving capability or maturity targets.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Manufacturing 5 Ms

A

Machinery, Manpower, Material, Measurement, and Method

24
Q

DT vs OT

A
  • Developmental Test & Evaluation (DT&E) is an engineering tool used to reduce risk throughout the system acquisition management cycle.
  • Operational Test & Evaluations (OT&E) is the actual employment, by typical users, of a system under realistic operational conditions.
25
When are EOA, OA, IOT&E, and FOT&E done?
* EOA - TMRR * OA - EMD * I/F O&TE - P&D
26
Live Fire T&E
During Live Fire T&E (LFT&E) the system will be tested and evaluated in both DT as well as OT environments. LFT&E provides a realistic assessment of weapon platform, crew vulnerability and survivability, and lethality of conventional munitions/missiles.
27
System Production Tests
28
3 Net Ready Requirement Attributes
* IT must be able to support military operations * IT must be able to be entered and managed on the network * IT must effectively exchange information
29
TEMP
30
Questions the TEMP answers
31
"Variables" in the TEMP
* COIs - Top-level issues that must be examined in OT&E to determine the system's capability to perform its mission. COIs are included in Part III of the TEMP. The following are the two categories of COIs: * Effectiveness: Will the system detect the threat in a combat environment at adequate range to allow successful engagement? * Suitability: Will the system be safe to operate in a combat environment? * CTPs - Derived from and support KPPs and KSAs and are employed in Developmental Testing (DT). CTPs are the engineering design factors that a system must meet or exceed to ensure that established performance thresholds are achieved. CTPs are derived from the CDD, critical system characteristics, Acquisition Product Baseline (APB), and systems engineering documents. * MOEs/MOSs - Part III of the TEMP lists the MOE and MOS. These measures are derived from the Critical Operational Issues (COI) developed in Operational Test and Evaluation plans and planning processes. These measures (MOEs and MOSs) are used to determine the attainment of the top-level performance parameters.
32
When is TEMP approved by?
MS-B
33
Goal of life cycle sustainment
To ensure a highly supportable system by integrating sustainment considerations into all planning, implementation, management, and oversight activities associated with the acquisition, development, production, fielding, support, and disposal of a system across its life cycle.
34
What is the LCSP?
The LCSP is the primary program management reference governing operations and support planning and execution from program inception to disposal. It is the detailed product support plan, including sustainment metrics, risks, costs, and analyses used to deliver the performance-based best value strategy covering the Integrated Product Support (IPS) elements.
35
What is the PSS?
Recall from prior learning that the Product Support Strategy (PSS) is the overarching strategy to meet sustainment requirements to deliver affordable readiness, defined as providing mission capability to the Warfighter at a reduced cost to the taxpayer. Such a strategy must be adaptable to change over the life cycle of the program. The PSM will implement the PSS via the LCSP through arrangements with various public and/or commercial PSIs and/or PSPs.
36
12 PSS Elements
37
Sustaining Engineering
Technical tasks (engineering and logistics investigations and analyses) to ensure the continued operation and maintenance of a system with managed (i.e., known) risk.
38
Product Support Management and Design Interface
Product Support Management: Planning and execution includes the enterprise-level integration of all twelve IPS Elements throughout the lifecycle commensurate with the roles and responsibilities of the PSM position created under 10 USC 2337 and captured in DoDI 5000.02. Design Interface: The relationship of logistics-related design parameters to readiness and support resource requirements. Logistics-related design parameters
39
3 levels of product support implementation
System, subsystem, and component
40
Product Support Business Model
41
How do the PSM and the LCL work together in supportability?
* Recall that the Product Support Manager (PSM) is responsible for managing the package of support functions required to field and maintain the readiness and operational capability of major weapon system elements (systems, subsystems, and components), including all functions related to weapon system readiness, in support of the PM’s life cycle management responsibilities. * The Life Cycle Logistician (LCL) should recognize that a system’s design determines how effectively and efficiently it can be supported.
42
Design for Supportability Considerations
* Logistics footprint * Reliability * Availability * Maintainability * Other logistics technologies
43
Reliability
44
Availability
45
Maintainability
46
Maintainability, LORA, and MTA
MTBF predicts the average elapsed time between failures and Mean Time to Repair (MTTR) is a basic technical measure of maintainability. A Level of Repair Analysis (LORA) ensures that operational readiness is achieved throughout a system's lifecycle by developing maintenance concepts. Maintenance Task Analysis (MTA) begins with identifying each step of the repair process. The steps are analyzed and a description written as to how they would be physically performed. After the description, resources to perform that task are identified, such as spares, tools, etc.
47
General Note on Product Support Throughout the Life Cycle
Throught the life cycle we are constantly endeavouring to work trade-offs and optimizations to ensure the system is supportable and push down LCC
48
Product Support Analysis
* Primarily an O&S function * Continues to focus on design changes, regardless of the need for the change, and adjusting the support package to accommodate the changes.
49
Product Support Analysis Activities
* Failure Mode, Effects, and Criticality Analysis (FMECA): Systematically identifies likely modes of failure, possible effects of failures, and the criticality of each effect on mission completion * Fault Tree Analysis (FTA): Applies deductive logic to determine the possible causes of defined undesired operational results * Reliability Centered Maintenance (RCM): Analyzing system safety data to determine preventative maintenance * Level of Repair Analysis (LORA): Ensures operational readiness is achieved and influences the systems design and maintenance planning by producing an effective support solution * Maintenance Task Analysis (MTA): Identifies steps, spares and materials, tools, support equipment, personnel skill levels as well * Core Logistics Analysis (CLA): Title 10 USC 2366a, Section (b)(5) states that MDAP or subprogram may not receive MS A or be initiated to MS B until core logistics capability requirements determinations have been made * Source of Repair Analysis (SORA): Evaluates repair sources * Depot Source of Repair (DSOR) Decision Process: Determination facilitates establishing new organic depot-level maintenance capabilities through procurement funding
50
Outcome based vs. transactional
Outcome based is essentially pay for performance whilst transactional is pay for service (think health care fee for service)
51
PBL Metrics
* Reliability and O&S Cost are KSAs * Availability is KPP * Mean Time Down
52
Incentives in PBL Contracts
Generally try to use a mix of financial and non-financial incentives
53
CTA vs. VOLT
* CTAs are not specific to a program; they are general threat information. They are used as source material for VOLTs and other threat-informed program documents * VOLT report describes the threat to be countered and the projected threat environment. It aids to transition technological developments for use by operational forces. The DIA provides validation for the VOLT Report, prepared by the appropriate Service, to support Acquisition Category (ACAT) ID/Major Defense Acquisition Programs (MDAPs).
54
CIPs
Key performance thresholds of foreign threat systems, which, if exceeded, could compromise the mission effectiveness of the U.S. system in development
55
Who is in charge of cybersecurity for DoD systems?
USCYBERCOM
56
What does CI have to do with acquisition?
When an acquisition program containing Critical Program Information (CPI) is initiated, the Program Manager (PM) should request a CI analysis of CPI from the servicing CI organization. The CI analysis focuses on how the opposition sees the program and on how to counter the opposition's collection efforts