CharacteristicA Characteristic entity specifies properties of an entity.falsetruefalseValueValue represents this Characteristic's current value.falsetrueTEXT1UnitsUnits represents this Characteristic's units used to measure the value, such as pounds or miles per hour.falsetrueTEXT10ResourceA Resource entity specifies a consumable or producible Asset.falsetrueC8falseUnitsUnits represents this Resource's units used to measure the amounts, such as each or tons.falsetrueTEXT4Initial AmountInitial Amount represents this Resource's starting amount.falsetrueNUMBER1minIdStringPBmaxIdStringPCMinimum AmountMinimum Amount represents this Resource's minimum amount allowed.falsetrueNUMBER2maxIdStringPCMaximum AmountMaximum Amount represents this Resource's maximum amount allowed.falsetrueNUMBER3minIdStringPBEquationAn Equation entity specifies an equation (mathematical or logical) that can be used to describe a part of the model.falsetruefalseValueValue represents this Equation's text.falsetrueTEXT1LogicalA Logical entity specifies relationship between Assets. It is primarily used in database schema development and entity-relationship diagrams.falsetrueCSfalseStatementA Statement entity specifies text referenced by the knowledgebase and usually contain in an Artifact.falsetruefalseLocationA Location entity specifies where an entity resides.falsetruetrueTest CaseA Test Case entity represents a set of conditions utilized to determine whether a system works as intended.falsetrueC1falseSet UpSet Up represents the prerequisites that must be fulfilled before executing this Test Case.falsetrueBIG_TEXT-4Actual ResultActual Results represents the results that are captured after executing a Test Case.falsetrueBIG_TEXT-2Expected ResultExpected Result represents the result expected when executing this Test Case.falsetrueBIG_TEXT-3StatusStatus represents the current state of this Test Case.falsetrueENUMERATION-1choicesListNot RunIn ProgressBlockedFailedPassedMeasureA Measure entity specifies properties of measurements and measuring methodologies, including metrics.falsetrueCGfalseProjected ValueProjected Value represents this Measure's expected value to be achieved with existing resources.falsetrueTEXT2Threshold ValueThreshold Value represents the minimum acceptable value for this Measure.falsetrueTEXT2Objective ValueObjective Value represents the goal for this Measure.falsetrueTEXT3Improvement DirectionImprovement Direction represents the direction in that metric improvement occurs. It is the direction from the Threshold Value to the Objective Value.falsetrueENUMERATION11defaultValueStringPositivechoicesListN/APositiveNegativeToleranceTolerance represents the percentage of the value that forms the positive and negative tolerance bands. Tolerance is used when Value represents the planned measure value at a given time.falsetrueTEXT12OrbitalAn Orbital entity specifies a location along an orbit around a celestial body.falsetrueC1DfalseOrigin of LongitudeOrigin of Longitude represents the reference meridian from where the Longitude of Ascending Node will be calculated.falsetrueTEXT8Longitude of Ascending NodeLongitude of Ascending Node represents the angle from the Origin of Longitude to the ascending node, measured in the Reference Plane. For the Earth, the origin of longitude is typically the Prime Meridian. The Longitude of Ascending Node must be specified with the Inclination to characterize the orbital plane.falsetrueNUMBER7unitsStringdegreesReference PlaneReference Plane represents the reference plane from where the Inclination angle will be calculated.falsetrueTEXT6InclinationInclination represents the angle between the orbital plane and a reference plane, such as the equatorial plane for Earth. The Inclination must be specified with the Longitude of Ascending Node to characterize the orbital plane.falsetrueNUMBER5unitsStringdegreesSemimajor AxisSemimajor Axis represents the one half of the length of the longest diameter of the orbital ellipse. The Semimajor axis must be specified with the Eccentricity to characterize the orbital ellipse shape.falsetrueNUMBER4unitsStringkmEccentricityEccentricity represents the amount the orbit deviates from a perfect circle (0 being perfectly circular and 1 is a parabola - no longer a closed orbit). The Eccentricity must be specified with the Semimajor axis to characterize the orbital ellipse shape.falsetrueNUMBER3PeriapsisPeriapsis represents the point of closest distance from the celestial body being orbited. For Earth, the term is perigee. For the Sun the term commonly used is perihelion. The Periapsis must be specified with the Apoapsis to characterize the orbital ellipse shape.falsetrueNUMBER2unitsStringkmApoapsisApoapsis represents the point of greatest distance from the celestial body being orbited. For Earth, the term is apogee. For the Sun the term commonly used is aphelion. The Apoapsis must be specified with the Periapsis to characterize the orbital ellipse shape.falsetrueNUMBER1unitsStringkmArgument of Periapsis Argument of Periapsis represents the angle between the Periapsis and the ascending node as measured in the orbital plane in the direction of motion.falsetrueNUMBER9unitsStringdegreesMean AnomalyMean Anomaly represents the proportion of orbital area swept since the last Periapsis at the specified time. It is used to define the position of the orbiting Asset along the orbital ellipse.falsetrueNUMBER10ConnectionA Connection entity specifies the mechanism relating Assets. This is an abstract class.falsetruetrueConduitA Conduit entity specifies the connection between Assets and has capacity and latency, which carries an Input/Output.falsetrueCSfalseCapacityCapacity represents the maximum rate supported by the Conduit. (Used in simulation as to add time delay by dividing the Input/Output size with the capacity value.)falsetrueNUMBER1LatencyLatency represents the time required to transmit the information or Input/Output entity over this Conduit. This value does not factor in any delays due to capacity limitations.falsetrueDURATION2UnitsUnits represents this Conduit's units used to measure the capacity, such as bits per second or gallons per minute.falsetrueTEXT3Input/OutputAn Input/Output entity specifies the information, data, or object input to, triggers, or output from an Action.falsetruefalseUnitsUnits represents this Input/Output's units used to measure the size, such as Gigabyte or tokens.falsetrueTEXT2SizeSize represents the amount or proportion of this Input/Output, such as 100 as in 100 Gigabytes or number of entities (e.g. 10 as in 10 tokens).falsetrueNUMBER1minValueDouble0.0CostA Cost entity specifies the outlay or expenditure (as of effort or sacrifice) made to achieve an objective associated with another entity.falsetruefalseRateRate represents this Cost's billing rate.falsetrueENUMERATION3defaultValueStringFixedchoicesListFixedPer HourUnitsUnits represents this Cost's units used to measure the amount, such as $ or Euro.falsetrueTEXT2Contract TypeContract Type represents this Cost way to identify the reimbursement structure (i.e. CPFF vs T&M).falsetrueENUMERATION5defaultValueStringN/AchoicesListCPFFCPAFCPIFFFP-CompletionFFP-LOET&MN/ACategoryCategory represents the part of the lifecycle for which the money is used (commonly called Color of Money). This matches the Federal Government (DoD) cost phases.falsetrueENUMERATION4defaultValueStringN/AchoicesListProcurementMILCONMILPERSO&MRDT&ESCNN/AAmountAmount represents this Cost's value.falsetrueNUMBER1PhysicalA Physical entity specifies a location on or above the surface.falsetrueC1DfalseAltitudeAltitude represents the distance above the surface.falsetrueNUMBER3CoordinatesCoordinates represents the coordinate points for this Location (GPS or other system).falsetrueGEOPOINT2AddressAddress represents this Location's complete address.falsetrueTEXT1RiskA Risk entity specifies the combined probability and consequence in achieving objectives.falsetruefalseConsequenceConsequence represents the level of effect from this Risk occurring.falsetruePERCENT2invertedBooleantrueConsequence DescriptionConsequence Description represents the result of this Risk occurring.falsetrueBIG_TEXT1ProbabilityProbability represents the chance that this Risk will occur.falsetruePERCENT3invertedBooleantrueStatusStatus represents the current state of this Risk.falsetrueENUMERATION4defaultValueStringOpenchoicesListOpenDuplicateDeclinedResolvedPortAn interaction point of a block, specifying the input and output flow.truetrueC8falseDirectionDirection represents the flow of data on this port.falsetrueENUMERATION1choicesListNoneInOutIn and OutVirtualA Virtual entity specifies a location within a digital network.falsetrueC1DfalseAddressAddress represents the identification address using the Uniform Resource Identifier (URI) protocols.falsetrueURI2147483647ArtifactAn Artifact entity specifies a document or other source of information that is referenced by or generated in the knowledgebase.falsetruefalseFileThe File that represents this Artifact.falsetrueFILE2Date PublishedDate Published represents the date when this Artifact was accessed (webpage), published, or uploaded to the knowledgebase.falsetrueDATETIME1TimeA Time entity specifies a point or period when something occurs or during which an action, asset, process, or condition exists or continues.falsetruefalseStartStart represents the time when this Time begins.falsetrueDATETIME2startIdStringP2KdurationIdStringP2JDurationDuration represents the period of time this Time occurs.falsetrueDURATION1startIdStringP2KdurationIdStringP2JActionAn Action entity specifies the mechanism by which inputs are transformed into outputs.falsetruefalsePercent CompletePercent Complete represents the percentage this Action is complete.falsetruePERCENT3StartStart represents the time when this Action begins.falsetrueDATETIME2startIdStringP3durationIdStringP2DurationDuration represents the period of time this Action occurs.falsetrueDURATION1startIdStringP3durationIdStringP2DecisionA Decision entity specifies a challenge and its resolution.falsetruefalseJustificationJustification represents the reason and context for making this Decision.falsetrueBIG_TEXT1AssumptionsAssumptions represents facts that are used as a basis for this Decision. These assumptions can be taken for granted by the decision maker.falsetrueBIG_TEXT2RequirementA Requirement entity identifies a capability, characteristic, or quality factor of a system that must exist for the system to have value and utility to the user.falsetrueC24falseConsistentConsistent represents if this Requirement is not in conflict with other requirements.falsetrueQUALITY5weightDouble11.11111111111111VerifiableVerifiable represents if this Requirement is provable (within realistic cost and schedule) that the system meets the requirement.falsetrueQUALITY11weightDouble11.11111111111111ClearClear represents if this Requirement is unambiguous and not confusing.falsetrueQUALITY3weightDouble11.11111111111111TraceableTraceable represents if this Requirement is uniquely identified, and able to be tracked to predecessor and successor lifecycle items/objects.falsetrueQUALITY10weightDouble11.11111111111111CompleteComplete represents if this Requirement expresses a whole idea.falsetrueQUALITY4weightDouble11.11111111111111RationaleRationale provides a place to capture the reason(s) behind this Requirement.falsetrueBIG_TEXT1Quality ScoreThe calculated quality score.falsetrueQUALITY_SCORE2DesignDesign represents if this Requirement does not impose a specific solution on design; says "what", not "how".falsetrueQUALITY7weightDouble11.11111111111111CorrectCorrect represents if this Requirement describes the user's true intent and is legally possible.falsetrueQUALITY6weightDouble11.11111111111111ModularModular represents if this Requirement can be changed without excessive impact on other requirements.truetrueQUALITY9weightDouble11.11111111111111FeasibleFeasible represents if this Requirement is able to be implemented with existing technology, and within cost and schedule.falsetrueQUALITY8weightDouble11.11111111111111AssetAn Asset entity specifies an object, person, or organization that performs Actions, such as a system, subsystem, component, or element.falsetruefalseresolved byResolved by identifies the entity that closes this Risk.falsetrueR56refined byRefined by identifies the Requirement that clarifies this Requirement.falsetrueR4ZverifiesVerifies identifies the Requirement that is supported by this entity.falsetrueR5Vtraced toTraced to identifies an entity that is accredited to this Statement.falsetrueR5Nsource ofSource of identifies the Statement that is contained in this Artifact.falsetrueR5JconsumesConsumes identifies the Resource that this Action uses. After this Action is completed the amount consumed is not returned to the Resource.falsetrueR32AmountAmount represents how much of the resource is consumed by the Action. Units are relative to the units selected for the resource.falsetrueNUMBER2147483647occursOccurs identifies the Time (or timespan) this entity happens.falsetrueR4DpushesPushes identifies the Action that this State Characteristic generates.falsetrueR4Rresults inResults in identifies the Decision that is caused by this entity.falsetrueR5Apushed byPushed by identifies the State Characteristic that this Action is generated from.falsetrueR4QreferencesReferences identifies the Artifact that specifies and/or enhances the definition of this entity.falsetrueR4Wsatisfied bySatisfied by identifies the entity that fulfills this Requirement.falsetrueR5Dlocated atLocated at identifies the Location where this entity exists.falsetrueR48variable ofVariable of identifies the Equation that this Characteristic is represented in.falsetrueR5TreceivesReceives identifies the Input/Output or Action that is taken in by this Action or Characteristic.falsetrueR4STriggerTrigger represents this relation as an enabling requirement for the Action. An Action begins execution when it has received control enablement, all of its triggers have arrived, and its necessary resources are available.falsetrueBOOLEAN2147483647defaultValueBooleantruealternative ofAlternative of identifies the Decision that has this Statement as a potential choice.falsetrueR2SChoiceChoice represents if this alternative was the choice selected.falsetrueBOOLEAN2147483647defaultValueBooleanfalseincurred byIncurred by identifies the entity that has this Cost value.falsetrueR41fetchesFetches identifies the State Characteristic that this Action receives.falsetrueR3Vhas dependentHas Dependent identifies the Action that depends on this Action.falsetrueR3Gjoined byJoined by identifies the Connector that connects to this Connector. Joined by implies the end of the relationship.falsetrueR45BidirectionalBidirectional represents if the connection between two connectors is bidirectional. If the connector is not bidirectional the connector that has the relation joins is the start and the connector with joined by is the end.falsetrueBOOLEAN2147483647defaultValueBooleantrueextended byExtended by identifies the Action (use case) that is added from this Action (use case).falsetrueR3RrelatesRelates identifies the peer-to-peer entity that is tied to this entity.falsetrueR50ContextContext represents a description of this relation.falsetrueTEXT2147483647related toRelated to identifies the entity that ties in a peer-to-peer way with this entity.falsetrueR51ContextContext represents a description of this relation.falsetrueTEXT2147483647joinsJoins identifies the Connector that is connected to this Connector. Joins implies the start of this relationship.falsetrueR44BidirectionalBidirectional represents if the connection between two connectors is bidirectional. If the connector is not bidirectional the connector that has the relation joins is the start and the connector with joined by is the end.falsetrueBOOLEAN2147483647defaultValueBooleantrueequation forEquation for identifies the entity that this Equation represents.falsetrueR3QlocatesLocates identifies an entity that exists at this Location.falsetrueR47generatesGenerates identifies the Input/Output or Action that this Action or Characteristic transforms.falsetrueR3Wspecified bySpecified by identifies a Characteristic that provides further information about this entity.falsetrueR5Mdecided byDecided by identifies the Decision scheduled for closure at this Time.falsetrueR3AderivesDerives identifies the Requirement that this Requirement develop from.falsetrueR3JalternativeAlternative identifies the Statement that is a potential choice for this Decision.falsetrueR2TChoiceChoice represents if this alternative was the choice selected.falsetrueBOOLEAN2147483647defaultValueBooleanfalsegenerated byGenerated by identifies the Action or Characteristic that this Input/Output or Action was transformed by.falsetrueR3Xtransferred byTransferred by identifies the Connector that passes this Input/Output.falsetrueR5RincludeInclude identifies the Action (use case) that is added to this Action (use case).falsetrueR3Zdepends onDepends on identifies the Action that this Action has a dependency on.falsetrueR3Hrepresented inRepresented in identifies the Asset who's diagrams include this Asset.falsetrueR54enablesEnables identifies the Decision that is empowered from this entity.falsetrueR3Msourced bySourced by identifies the Artifact that contains this Statement.falsetrueR5HcopiesCopies identifies the Requirement that this Requirement clones.falsetrueR35connected byConnected by identifies the Connector that adjoins this Asset.falsetrueR2ZOriginOrigin represents if the Asset is the origin of the Connector. This attribute enables unidirectional (one or the other Asset's relationship origin is False), in additional to the default bi-directional flow (both origins are set to True as a default).falsetrueBOOLEAN2147483647MultiplicityMultiplicity represents if this connection has multiple connections to the Asset.falsetrueMULTIPLICITY2147483647refinesRefines identifies the Requirement that this Requirement clarifies.falsetrueR4YcausesCauses identifies the Risk resulting from this entity.falsetrueR2WseizesSeizes identifies the Resource that this Action uses. After this Action has completed the Resource is released for use by other Actions.falsetrueR5EAmountAmount represents how much of the resource is captured by the Action. Units are relative to the units selected for the resource.falsetrueNUMBER2147483647decision dueDecision due identifies the Time when this Decision is scheduled to be closed.falsetrueR39mitigatesMitigates identifies the Risk that this entity plan alleviates.falsetrueR4Bequation ofEquation of identifies the Equation that represents this entity.falsetrueR3PincursIncurs identifies the Cost value for this entity.falsetrueR40result ofResult of identifies the entity that caused this Decision.falsetrueR5BorbitsOrbits identifies the Asset that this Asset revolves around, such as the Moon orbits the Earth.falsetrueR4Fresponded byResponded by identifies the Asset (usually a person or organization) that acts on this Decision.falsetrueR58ResponsibilityResponsibility represents the Asset that has the responsibility for resolving the Decision.falsetrueENUMERATION2147483647defaultValueStringPrimarychoicesListPrimarySecondaryinstantiatesInstantiates identifies another entity that has this entity as an instance.falsetrueR42responds toResponds to identifies the Decision that is acted on by this Asset (usually a person or organization).falsetrueR57ResponsibilityResponsibility represents the Asset that has the responsibility for resolving the Decision.falsetrueENUMERATION2147483647defaultValueStringPrimarychoicesListPrimarySecondarymadeMade identifies the Decision that this Asset decided.falsetrueR4Aproduced byProduced by identifies the Action that creates this Resource. Resources are produced when the execution of the action completes.falsetrueR4NAmountAmount represents how much of the resource is produced by the Action. Units are relative to the units selected for the resource.falsetrueNUMBER2147483647defined protocol byDefined protocol by identifies the Artifact that contains the standard used by this Connector.falsetrueR3Freferenced byReferenced by identifies the the entity that specified and/or enhanced its definition by this Artifact.falsetrueR4Xtraced fromTraced from identifies a Statement that accredited this entity.falsetrueR5Pmade byMade by identifies the Asset that decided this Decision.falsetrueR49defines protocol forDefines protocol for identifies the Connector that uses the standard identified in this Artifact.falsetrueR3Eincluded byIncluded by identifies the Action (use case) that is added from this Action (use case).falsetrueR3YdecomposesDecomposes identifies the parent of this entity.falsetrueR3BMultiplicityMultiplicity represents if this decomposition has multiple instances of the child.falsetrueMULTIPLICITY2147483647decomposed byDecomposed by identifies the children of this entity.falsetrueR3CMultiplicityMultiplicity represents if this decomposition has multiple instances of the child.falsetrueMULTIPLICITY2147483647occurred byOccurred by identifies the entity that happens at this Time.falsetrueR4Eenabled byEnabled by identifies the entity that empowers this Decision to be made.falsetrueR3Nderived byDerived by identifies the Requirement that is developed from this Requirement.falsetrueR3Kverified byVerified by identifies the entity that supports this Requirement.falsetrueR5WresolvesResolves identifies the Risk that is closed by this entity.falsetrueR55connects toConnects to identifies the Asset that this Connector adjoins.falsetrueR2YOriginOrigin represents if the Asset is the origin of the Connector. This attribute enables unidirectional (one or the other Asset's relationship origin is False), in additional to the default bi-directional flow (both origins are set to True as a default).falsetrueBOOLEAN2147483647MultiplicityMultiplicity represents if this connection has multiple connections to the Asset.falsetrueMULTIPLICITY2147483647performsPerforms identifies the Action that is executed by this Asset.falsetrueR4HAmountAmount represents how many Asset are used in the execution of the Action.falsetrueNUMBER2147483647copied byCopied by identifies the Requirement that is a clone of this Requirement.falsetrueR36caused byCaused by identifies the entity that this Risk results.falsetrueR2XtransfersTransfers identifies the Input/Output that is passed by this Connector.falsetrueR5Qperformed byPerformed by identifies the Asset that executes this Action.falsetrueR4JAmountAmount represents how many Asset are used in the execution of the Action.falsetrueNUMBER2147483647extendExtend identifies the Action (use case) that is added to this Action (use case).falsetrueR3Sorbited byOrbited by identifies the Asset that revolves around this Asset, such as the Earth is orbited by the Moon.falsetrueR4Gmitigated byMitigated by identifies the entity that contains the plan to alleviate this Risk.falsetrueR4Chas variableHas variable identifies the Characteristic that is represented in this Equation.falsetrueR5Sdate resolved byDate resolved by identifies the Time when this Decision was closed.falsetrueR38seized bySeized by identifies the Action that uses this Resource. After the Action has completed this Resource is released for use by other Actions. falsetrueR5FAmountAmount represents how much of the resource is captured by the Action. Units are relative to the units selected for the resource.falsetrueNUMBER2147483647date resolvesDate resolves identifies the Decision that is closed at this Time.falsetrueR37representsRepresents identities the Asset that is included in this Asset's diagrams.falsetrueR53received byReceived by identifies the Action or Characteristic that takes in this Input/Output or Action.falsetrueR4TTriggerTrigger represents this relation as an enabling requirement for the Action. An Action begins execution when it has received control enablement, all of its triggers have arrived, and its necessary resources are available.falsetrueBOOLEAN2147483647defaultValueBooleantrueinstantiated byInstantiated by identifies another entity that is an instance of this entity.falsetrueR43satisfiesSatisfies identifies the Requirement that is fulfilled by this entity.falsetrueR5CproducesProduces identifies the Resource that is created by this Action. Resources are produced when the execution of the action completes.falsetrueR4MAmountAmount represents how much of the resource is produced by the Action. Units are relative to the units selected for the resource.falsetrueNUMBER2147483647specifiesSpecifies identifies an entity that this Characteristic provides further information about.falsetrueR5Kfetched byFetched by identifies the Action that this State Characteristic is received by.falsetrueR3Tconsumed byConsumed by identifies the Action that uses this Resource. After the Action is completed the amount consumed is not returned to the Resource.falsetrueR33AmountAmount represents how much of the resource is consumed by the Action. Units are relative to the units selected for the resource.falsetrueNUMBER2147483647CGR5DC2502147483647falseCGR3VC102147483647falseCGR41CZ02147483647falseProgram ManagementCGR5MCG02147483647trueCGR5MC1Z02147483647trueCGR5MC2402147483647trueCGR4TC1A02147483647falseCGR5WC2502147483647falseCGR5MC102147483647trueCGR4TC102147483647falseCGR50CG02147483647falseCGR5SC1802147483647falseCGR4CC1Z02147483647falseProgram ManagementCGR5MC502147483647trueCGR5MC802147483647trueCGR3QC1802147483647falseCGR4EC2H02147483647falseProgram ManagementCGR5BC1502147483647falseProgram ManagementCGR5MC1D02147483647trueCGR51CG02147483647falseCGR5MC1A02147483647trueCGR42CG02147483647falseCGR4QC102147483647falseCGR3NC1502147483647falseProgram ManagementCGR5NC2402147483647falseCGR47C1D02147483647falseProgram ManagementCGR5MCS02147483647trueCGR56C1Z02147483647falseProgram ManagementCGR3BCG02147483647trueCGR5MC2H02147483647trueCGR3XC102147483647falseCGR2XC1Z02147483647falseProgram ManagementCGR5MCZ02147483647trueCGR43CG02147483647falseCGR5KCG02147483647falseCGR4XC502147483647falseCGR3CCG02147483647trueCGR3XC1A02147483647falseC9R32C102147483647trueC9R5EC102147483647trueC9R4MC102147483647trueC18R3BC1802147483647trueC18R3PCS02147483647trueC18R3PC502147483647trueC18R3PC802147483647trueC18R3CC1802147483647trueC18R5TCG02147483647trueC18R3PC1A02147483647trueC18R3PCZ02147483647trueC18R3PC2H02147483647trueC18R3PC1D02147483647trueC18R51C1802147483647falseC18R3PC1Z02147483647trueC18R3PCG02147483647trueC18R3PC102147483647trueC18R50C1802147483647falseC18R3PC1502147483647trueC18R3PC2402147483647trueC24R5PC1A02147483647trueC24R5PC1D02147483647trueC24R5PCG02147483647trueC24R41CZ02147483647falseProgram ManagementC24R5PC2402147483647trueC24R5PC102147483647trueC24R5PC502147483647trueC24R4CC1Z02147483647falseProgram ManagementC24R51C2402147483647falseC24R5PC802147483647trueC24R4EC2H02147483647falseProgram ManagementC24R3QC1802147483647falseC24R5BC1502147483647falseProgram ManagementC24R3CC2402147483647trueC24R3NC1502147483647falseProgram ManagementC24R3BC2402147483647trueC24R5NC2402147483647trueC24R47C1D02147483647falseProgram ManagementC24R50C2402147483647falseC24R5PCS02147483647trueC24R56C1Z02147483647falseProgram ManagementC24R2TC1502147483647falseC24R5PC1502147483647trueC24R2XC1Z02147483647falseProgram ManagementC24R5JC502147483647trueC24R5PCZ02147483647trueC24R5KCG02147483647falseC24R4XC502147483647trueC1DR5DC2502147483647falseC1DR50C1D02147483647falseC1DR48C1Z02147483647trueC1DR48C2402147483647trueC1DR48CS02147483647trueC1DR48C102147483647trueC1DR48C502147483647trueC1DR48C802147483647trueC1DR51C1D02147483647falseC1DR5NC2402147483647falseC1DR5WC2502147483647falseC1DR48C1A02147483647trueC1DR4CC1Z02147483647falseProgram ManagementC1DR5KCG02147483647falseC1DR4EC2H02147483647falseProgram ManagementC1DR3QC1802147483647falseC1DR48CZ02147483647trueC1DR48CG02147483647trueC1DR3BC1D02147483647trueC1DR3CC1D02147483647trueCSR5DC2502147483647falseCSR44CS02147483647falseCSR45CS02147483647falseCSR51CS02147483647falseCSR41CZ02147483647falseProgram ManagementCSR2ZC802147483647trueCSR3NC1502147483647falseProgram ManagementCSR5NC2402147483647falseCSR47C1D02147483647falseProgram ManagementCSR5WC2502147483647falseCSR56C1Z02147483647falseProgram ManagementCSR4CC1Z02147483647falseProgram ManagementCSR2XC1Z02147483647falseProgram ManagementCSR5KCG02147483647falseCSR3QC1802147483647falseCSR4EC2H02147483647falseProgram ManagementCSR5BC1502147483647falseProgram ManagementCSR4XC502147483647falseCSR50CS02147483647falseCTR3CCT02147483647trueCTR3BCT02147483647trueCTR3EC502147483647falseCTR42CT02147483647falseCTR43CT02147483647falseCTR5RC1A02147483647trueC1AR5DC2502147483647falseC1AR42C1A02147483647falseC1AR50C1A02147483647falseC1AR4SCG02147483647trueC1AR4SC102147483647trueC1AR3WC102147483647trueC1AR41CZ02147483647falseProgram ManagementC1AR51C1A02147483647falseC1AR3NC1502147483647falseProgram ManagementC1AR43C1A02147483647falseC1AR5NC2402147483647falseC1AR47C1D02147483647falseProgram ManagementC1AR3CC1A02147483647trueC1AR5WC2502147483647falseC1AR56C1Z02147483647falseProgram ManagementC1AR4CC1Z02147483647falseProgram ManagementC1AR2XC1Z02147483647falseProgram ManagementC1AR5QCT02147483647trueC1AR5KCG02147483647falseC1AR4EC2H02147483647falseProgram ManagementC1AR3QC1802147483647falseC1AR3WCG02147483647trueC1AR5BC1502147483647falseProgram ManagementC1AR4XC502147483647falseC1AR3BC1A02147483647trueCZR5DC2502147483647falseCZR40CS02147483647trueCZR5WC2502147483647falseCZR4CC1Z02147483647falseProgram ManagementCZR3QC1802147483647falseCZR4EC2H02147483647falseProgram ManagementCZR5BC1502147483647falseProgram ManagementCZR51CZ02147483647falseCZR3BCZ02147483647trueCZR40C1Z02147483647trueCZR3CCZ02147483647trueCZR40C102147483647trueCZR3NC1502147483647falseProgram ManagementCZR40C802147483647trueCZR40C502147483647trueCZR5NC2402147483647falseCZR40C2402147483647trueCZR47C1D02147483647falseProgram ManagementCZR56C1Z02147483647falseProgram ManagementCZR50CZ02147483647falseCZR2XC1Z02147483647falseProgram ManagementCZR5KCG02147483647falseCZR40C1A02147483647trueCZR40CG02147483647trueCZR4XC502147483647falseC1ZR55C2402147483647trueC1ZR2WCS02147483647trueC1ZR4BCS02147483647trueC1ZR55CZ02147483647trueC1ZR55C1Z02147483647trueC1ZR41CZ02147483647falseProgram ManagementC1ZR2WC1Z02147483647trueC1ZR4BCZ02147483647trueC1ZR2WCG02147483647trueC1ZR51C1Z02147483647falseC1ZR55C1A02147483647trueC1ZR55C102147483647trueC1ZR4EC2H02147483647falseProgram ManagementC1ZR3QC1802147483647falseC1ZR4BCG02147483647trueC1ZR5BC1502147483647falseProgram ManagementC1ZR2WC802147483647trueC1ZR2WCZ02147483647trueC1ZR2WC1A02147483647trueC1ZR4BC1D02147483647trueC1ZR2WC502147483647trueC1ZR3BC1Z02147483647trueC1ZR4BC1A02147483647trueC1ZR3CC1Z02147483647trueC1ZR4BC502147483647trueC1ZR2WC102147483647trueC1ZR3NC1502147483647falseProgram ManagementC1ZR55C802147483647trueC1ZR4BC2H02147483647trueC1ZR55C502147483647trueC1ZR4BC802147483647trueC1ZR4BC2402147483647trueC1ZR47C1D02147483647falseProgram ManagementC1ZR55CS02147483647trueC1ZR4BC102147483647trueC1ZR56C1Z02147483647falseC1ZR2WC2402147483647trueC1ZR2XC1Z02147483647falseC1ZR50C1Z02147483647falseC1ZR5KCG02147483647falseC1ZR55CG02147483647trueC1ZR4XC502147483647falseC5R5DC2502147483647falseC5R50C502147483647falseC5R3BC502147483647trueC5R41CZ02147483647falseProgram ManagementC5R4WC2402147483647trueC5R51C502147483647falseC5R3CC502147483647trueC5R4WC102147483647trueC5R5WC2502147483647falseC5R3FCT02147483647falseC5R4CC1Z02147483647falseProgram ManagementC5R3QC1802147483647falseC5R4EC2H02147483647falseProgram ManagementC5R5BC1502147483647falseProgram ManagementC5R4WC1A02147483647trueC5R4WCG02147483647trueC5R4WC802147483647trueC5R3NC1502147483647falseProgram ManagementC5R5NC2402147483647trueC5R47C1D02147483647falseProgram ManagementC5R4WCS02147483647trueC5R4WCZ02147483647trueC5R56C1Z02147483647falseProgram ManagementC5R4WC1Z02147483647trueC5R2XC1Z02147483647falseProgram ManagementC5R5KCG02147483647falseC5R5HC2402147483647trueC2HR5DC2502147483647falseC2HR4DCZ02147483647trueC2HR4DC502147483647trueC2HR50C2H02147483647falseC2HR4DC802147483647trueC2HR39C1502147483647falseC2HR51C2H02147483647falseC2HR3BC2H02147483647trueC2HR38C1502147483647falseC2HR5WC2502147483647falseC2HR4DC1D02147483647trueC2HR4DCG02147483647trueC2HR4DC2402147483647trueC2HR4CC1Z02147483647falseProgram ManagementC2HR4DC1A02147483647trueC2HR4DCS02147483647trueC2HR4DC102147483647trueC2HR5KCG02147483647falseC2HR3QC1802147483647falseC2HR3CC2H02147483647trueC2HR4DC1Z02147483647trueC1R5DC2502147483647falseC1R50C102147483647falseC1R4RCG02147483647falseC1R51C102147483647falseC1R41CZ02147483647falseProgram ManagementC1R3CC102147483647trueC1R33C902147483647falseResourceC1R4TC1A02147483647trueC1R5WC2502147483647falseC1R4CC1Z02147483647falseProgram ManagementC1R5FC902147483647falseResourceC1R3BC102147483647trueC1R3RC102147483647falseC1R3QC1802147483647falseC1R4EC2H02147483647falseProgram ManagementC1R5BC1502147483647falseProgram ManagementC1R3SC102147483647falseC1R4SCG02147483647falseC1R3TCG02147483647falseC1R3GC102147483647falseC1R3ZC102147483647falseC1R3NC1502147483647falseProgram ManagementC1R5NC2402147483647trueC1R47C1D02147483647falseProgram ManagementC1R3YC102147483647falseC1R3HC102147483647falseC1R4HC802147483647trueC1R56C1Z02147483647falseProgram ManagementC1R2XC1Z02147483647falseProgram ManagementC1R5KCG02147483647falseC1R3WCG02147483647falseC1R4NC902147483647falseResourceC1R4XC502147483647falseC1R3XC1A02147483647trueC15R5AC1502147483647trueC15R5AC502147483647trueC15R4AC802147483647trueC15R5AC802147483647trueC15R3BC1502147483647trueC15R3MCS02147483647trueC15R3MC1502147483647trueC15R5AC102147483647trueC15R3MC1A02147483647trueC15R41CZ02147483647falseProgram ManagementC15R2SC2402147483647trueC15R37C2H02147483647trueC15R3CC1502147483647trueC15R3MCZ02147483647trueC15R5AC1A02147483647trueC15R57C802147483647trueC15R4CC1Z02147483647falseProgram ManagementC15R4EC2H02147483647falseProgram ManagementC15R3QC1802147483647falseC15R50C1502147483647falseC15R5BC1502147483647falseC15R5ACS02147483647trueC15R3MC102147483647trueC15R51C1502147483647falseC15R3MC2402147483647trueC15R5AC2402147483647trueC15R3MC502147483647trueC15R3MC802147483647trueC15R5ACZ02147483647trueC15R3NC1502147483647falseC15R3MC1Z02147483647trueC15R5AC1Z02147483647trueC15R5NC2402147483647trueC15R47C1D02147483647falseProgram ManagementC15R5ACG02147483647trueC15R3AC2H02147483647trueC15R56C1Z02147483647falseProgram ManagementC15R3MCG02147483647trueC15R2XC1Z02147483647falseProgram ManagementC15R5KCG02147483647falseC25R5VC1A02147483647falseC25R5VC1D02147483647falseC25R4ZC2502147483647falseC25R5VC802147483647falseC25R5CC1A02147483647falseC25R35C2502147483647falseC25R5VCS02147483647falseC25R5WC2502147483647falseC25R5CC1D02147483647falseC25R3JC2502147483647falseC25R4YC2502147483647falseC25R5VC2502147483647falseC25R5VCG02147483647falseC25R5CCG02147483647falseC25R36C2502147483647falseC25R5VC102147483647falseC25R5VC2H02147483647falseC25R5VCZ02147483647falseC25R5CC802147483647falseC25R5VC502147483647falseC25R5CC502147483647falseC25R5CCZ02147483647falseC25R3KC2502147483647falseC25R5CC102147483647falseC25R5CCS02147483647falseC25R5CC2H02147483647falseC8R5DC2502147483647falseC8R3BC802147483647trueC8R2YCS02147483647trueC8R50C802147483647falseC8R4JC102147483647trueC8R49C1502147483647falseC8R41CZ02147483647falseProgram ManagementC8R51C802147483647falseC8R3CC802147483647trueC8R5WC2502147483647falseC8R4CC1Z02147483647falseProgram ManagementC8R53C802147483647falseC8R3QC1802147483647falseC8R4EC2H02147483647falseProgram ManagementC8R5BC1502147483647falseProgram ManagementC8R3SC802147483647falseC8R58C1502147483647falseProgram ManagementC8R43C802147483647falseC8R3RC802147483647falseC8R3NC1502147483647falseProgram ManagementC8R5NC2402147483647falseC8R47C1D02147483647falseLocationsC8R54C802147483647falseC8R56C1Z02147483647falseProgram ManagementC8R42C802147483647falseC8R4GC802147483647falseLocationsC8R2XC1Z02147483647falseProgram ManagementC8R5KCG02147483647trueC8R4XC502147483647falseC8R4FC802147483647falseLocationsAppendix H. Compliance MatricesfalsefalseC5L6JSERIALSTARTENDL265yCompliance Matrix for Centers<p>Template Instructions</p>
<p>This Compliance Matrix documents the Center's compliance with the requirements of this NPR or justification for tailoring of those requirements. While all requirements of this NPR are fundamentally owned by the OCE, in some cases responsibility for those requirements has been delegated to the Center Director. Since approval for tailoring of those delegated requirements is the responsibility of the Center Director (or delegate), only the undelegated OCE requirements are listed in this table. This compliance matrix will be filled out and submitted to the OCE upon request and attached to a copy of the Center procedures. The matrix lists:</p>
<ul><li>The unique requirement identifier</li><li>The paragraph reference</li><li>The NPR 7123.1 requirement statement</li><li>The rationale for the requirement</li><li>The requirement owner (the organization or individual responsible for the requirement)</li><li>A "Comply?" column to describe applicability or intent to tailor</li><li>The "Justification" column to justify how tailoring is to be applied</li></ul>
<p>The "Requirement Owner" column designates which organization is responsible for maintaining the requirement for the Agency and which therefore has the authority for tailoring unless this authority has been formally delegated. The "Comply?" column is filled in to identify the Center's approach to the requirement. An "FC" is inserted for "fully compliant," "T" for "tailored," or "NA" for a requirement that is not applicable. The column titled "Justification" documents the rationale for tailoring, documents how the requirement will be tailored, or justifies why the requirement is not applicable.</p>falsefalseC24H.1L265ySERIALSTARTe5SERIALENDCompliance Matrix for Programs/Projects<p>Template Instructions</p>
<p>The Compliance Matrix documents the program/project's compliance or intent to comply with the requirements of this NPR or justification for tailoring. It is attached to the SEMP when submitted for approval. The matrix lists:</p>
<ul><li>The unique requirement identifier</li><li>The paragraph reference</li><li>The NPR 7123.1 requirement statement</li><li>The rationale for the requirement</li><li>The requirement owner (the organization or individual responsible for the requirement)</li><li>A "Comply?" column to describe applicability or intent to tailor</li><li>The "Justification" column to justify how tailoring is to be applied</li></ul>
<p>Programs/Projects may substitute a matrix that documents their compliance with their particular Center's implementation of NPR 7123.1, if applicable.</p>
<p>The "Requirement Owner" column designates which organization is responsible for maintaining the requirement for the Agency and which, therefore, has the authority for tailoring unless this authority has been formally delegated.</p>
<p>The "Comply?" column is filled in to identify the program/project's approach to the requirement. An "FC" is inserted for "fully compliant," "T" for "tailored," or "NA" for a requirement that is "not applicable." The column titled "Justification" documents the rationale for tailoring, documents how the requirement will be tailored, or justifies why the requirement is not applicable.</p>falsefalseC24H.2L265ySERIALSTARTe3T281SERIALENDTable 1<table><tbody><tr><td><strong>Req ID</strong></td><td><strong>SE NPR Paragraph</strong></td><td><strong>Requirement Statement</strong></td><td><strong>Rationale</strong></td><td><strong>Req. Owner</strong></td><td><strong>Comply?</strong></td><td><strong>Justification</strong></td></tr><tr><td>SE-01</td><td>2.1.4.3.a</td><td>Center Directors shall
perform the following
activities: establish policies,
procedures, and processes
to execute the requirements
of this SE NPR.</td><td>The requirements of
this NPR are to be
flowed into Center-level
command media for
execution. This may
require not only
Center-level
requirements, but also
policy statements, work
instructions, or other
supporting or enabling
processes. It is the
responsibility of the
Center Directors or
designees to ensure
that this occurs.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-02</td><td>2.1.4.3.b</td><td>Center Directors shall
perform the following
activities: assess and take
corrective actions to
improve the execution of
the requirements of this SE
NPR.</td><td>Continual improvement
of Agency and Center
processes is necessary
to ensure they are
efficient and effective. It
is the responsibility of
the Centers to bring
forward any
recommendations for
improvement of this NPR.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-03</td><td>2.1.4.3.c</td><td>Center Directors shall
perform the following
activities: select appropriate
standards applicable to
projects under their control.</td><td>It is the responsibility of
the Center
organizations to identify
which Agency and/or
Center technical
standards should be
applied to the programs
and projects within their
purview. These will be
recommended to the
programs/projects
through the technical
authority lines.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-04</td><td>2.1.4.3.d</td><td>Center Directors shall
perform the following
activities: Complete the
compliance matrix, as
tailored, in Appendix H.1
for those requirements
owned by the Office of
Chief Engineer, and
provide to the OCE upon
request.</td><td>The Centers are to fill
out the compliance
matrix in Appendix H.1
to indicate how the
OCE-owned
requirements of this
NPR have been flowed
into Center-level
processes. This
ensures that the OCE
requirements of the
Agency are flowed into
the Centers and that
any waiver/deviation
from the Agency
requirements has been
identified and approved
by the OCE.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-07</td><td>3.2.2.1</td><td>Center Directors or
designees shall establish
and maintain a Stakeholder
Expectations Definition
process to include
activities, requirements,
guidelines, and
documentation for the
definition of stakeholder
expectations for the
applicable product layer.</td><td>This requirement
ensures that the
Centers identify how
they will gather and
address stakeholder
expectations. This
ensures that the project
will gain a thorough
understanding of what
the customer and other
stakeholders expect out
of the programs/projects.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-08</td><td>3.2.3.1</td><td>Center Directors or
designees shall establish
and maintain a Technical
Requirements Definition
process to include
activities, requirements,
guidelines, and
documentation for the
definition of technical
requirements from the set
of agreed upon stakeholder
expectations for the
applicable product layer.</td><td>This requirement
ensures that the
Centers identify how
they will select and gain
agreement on the
technical requirements
for the program/project.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-09</td><td>3.2.4.1</td><td>Center Directors or
designees shall establish
and maintain a Logical
Decomposition process to
include activities,
requirements, guidelines,
and documentation for
logical decomposition of the
validated technical
requirements of the
applicable product layer.</td><td>This requirement
ensures that the
Centers identify how
they will take the
technical requirements
for the program/project
and glean from them
what is needed to
accomplish them
(functional block
diagrams, timing,
architectures, etc.).
This places the
requirements into
context and ensures
they are understood
well enough to begin
the design process.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-10</td><td>3.2.5.1</td><td>Center Directors or
designees shall establish
and maintain a Design
Solution Definition process
to include activities,
requirements, guidelines,
and documentation for
designing product solution
definitions within the
applicable product layer
that satisfy the derived
technical requirements.</td><td>This requirement
ensures that the
Centers identify how
they will take the
information from the
stakeholder
expectations,
requirements, and
logical decomposition
and perform the design
function. Since all
designs are unique, this
will describe the
general steps that are
taken. The specifics for
each of the
program/projects will be
documented in the SEMP.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-11</td><td>3.2.6.1</td><td>Center Directors or
designees shall establish
and maintain a Product
Implementation process to
include activities,
requirements, guidelines,
and documentation for
implementation of a design
solution definition by
making, buying, or reusing
an end product of the
applicable product layer.</td><td>This requirement
ensures that the
Centers identify how
they will execute the
designs, whether
through buying items off
the shelf or contracting
to have them built,
building/coding them
within the Center, or
reusing products
already developed by
another
program/project. The
specifics for how each
program/project will
make this determination
for the various
components/assemblies
within the product
hierarchy are
documented in the SEMP.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-12</td><td>3.2.7.1</td><td>Center Directors or
designees shall establish
and maintain a Product
Integration process to
include activities,
requirements, guidelines,
and documentation for the
integration of lower level
products into an end
product of the applicable
product layer in accordance with its design solution
definition.</td><td>This requirement
ensures that the
Centers identify how
they will approach the
integration of products
within successive levels
of the product
hierarchy. This ensures
that planning is
performed that will
enable a smooth integration of products
into higher level
assemblies.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-13</td><td>3.2.8.1</td><td>Center Directors or
designees shall establish
and maintain a Product
Verification process to
include activities,
requirements/specifications,
guidelines, and
documentation for
verification of end products
generated by the product
implementation process or
product integration process
against their design
solution definitions.</td><td>This requirement
ensures that the
Centers identify how
they will verify that the
end products will
comply with the
technical requirements.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-14</td><td>3.2.9.1</td><td>Center Directors or
designees shall establish
and maintain a Product
Validation process to
include activities,
requirements, guidelines,
and documentation for
validation of end products
generated by the product
implementation process or
product integration process
against their stakeholder
expectations.</td><td>This requirement
ensures that the
Centers identify how
they will show that the
end products will meet
the stakeholder
expectations in the
intended environment.
This is in addition to
verifying they meet the
stated requirements
and ensures the
stakeholder is getting
what was expected.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-15</td><td>3.2.10.1</td><td>Center Directors or
designees shall establish
and maintain a Product
Transition process to
include activities,
requirements, guidelines,
and documentation for
transitioning end products
to the next higher level
product layer customer or
user.</td><td>This requirement
ensures that the
Centers identify how
they will handle the end
products as they move
from one location to
another. This includes
shipping, handling,
transportation criteria,
security needs, and
receiving facility
storage needs. It
ensures that receiving
facilities are ready to
accept the product and
that no damage occurs
to the product during
handling and transportation.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-16</td><td>3.2.11.1</td><td>Center Directors or
designees shall establish
and maintain a Technical
Planning process to include
activities, requirements,
guidelines, and
documentation for planning
the technical effort.</td><td>This requirement
ensures that the
Centers identify how
they will perform and
document all the
technical planning for
the program/project.
This includes all plans
developed for the
technical effort
??"Systems
Engineering
Management Plans, risk
plans, integration plans,
and VandV plans. This
ensures that the
program/project teams
are thinking ahead for
the work to be performed and
capturing that
information so it can be
communicated to the
rest of the team,
customers, and other
stakeholders.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-17</td><td>3.2.12.1</td><td>Center Directors or
designees shall establish
and maintain a
Requirements Management
process to include
activities, requirements,
guidelines, and
documentation for
management of
requirements throughout
the system life cycle.</td><td>This requirement
ensures that the
Centers identify how
they will handle tracking
and changes to the
baselined set of
requirements. It defines
who has authority to
submit and approve
changes and how
requirements are
tracked as they flow
down to other elements
in the product
breakdown structure.
This ensures that
changes to
requirements are
evaluated and that their
impacts are understood
and communicated to
the rest of the team.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-18</td><td>3.2.13.1</td><td>Center Directors or
designees shall establish
and maintain an Interface
Management process to
include activities,
requirements, guidelines,
and documentation for
management of the
interfaces defined and
generated during the
application of the system
design processes.</td><td>This requirement
ensures that the
Centers identify how
they will manage the
internal and external
interfaces of their end
product. This will
ensure compatibility
when the various parts
of the system are
brought together for
assembly/integration.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-19</td><td>3.2.14.1</td><td>Center Directors or
designees shall establish
and maintain a Technical
Risk Management process
to include activities,
requirements, guidelines,
and documentation for
management of the risk
identified during the
technical effort.</td><td>This requirement
ensures that the
Centers identify how
they will handle the
technical portions of the
program/project risks
and report them for
inclusion with the
programmatic risk
portions. It ensures that
the technical aspects of
risks to the
program/project's
successful execution
are captured and
reported to
program/project
management who will
be developing the
overall risk posture.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-20</td><td>3.2.15.1</td><td>Center Directors or
designees shall establish
and maintain a
Configuration Management
process to include
activities, requirements,
guidelines, and
documentation for
configuration management.</td><td>This requirement
ensures that the
Centers identify how
they will perform
configuration
management of the end
products, enabling
products and other
work products key to
the program/project.
The technical products
to be controlled are
identified and tracked to
ensure that the team
knows what the
configuration of their
system is at all phases
of the life cycle.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-21</td><td>3.2.16.1</td><td>Center Directors or
designees shall establish
and maintain a Technical
Data Management process
to include activities,
requirements, guidelines,
and documentation for
management of the
technical data generated
and used in the technical
effort.</td><td>This requirement
ensures that the
Centers identify how
they will handle all the
technical data that is
generated by the
program/project. This
will include all data
needed to manage,
operate, and support
the system products
over the life cycle. It
ensures that the data is
available and secure
when needed.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-22</td><td>3.2.17.1</td><td>Center Directors or
designees shall establish
and maintain a Technical
Assessment process to
include activities,
requirements, guidelines,
and documentation for
making assessments of the
progress of planned
technical effort and
progress toward
requirements satisfaction</td><td>This requirement
ensures that the
Centers identify how
they will assess the
progress of the
program/project's
technical efforts,
including life-cycle
reviews. It ensures that
the program/project
team, customers, and
other key stakeholders
know how the effort is
progressing and if
additional actions are
needed to resolve
issues prior to
becoming too costly.</td><td>OCE</td><td></td><td></td></tr><tr><td>SE-23</td><td>3.2.18.1</td><td>Center Directors or
designees shall establish
and maintain a Decision
Analysis process to include
activities, requirements,
guidelines, and
documentation for making
technical decisions.</td><td>This requirement
ensures that the
Centers identify how
they will make and
document key technical
decisions. It helps to
ensure that all team
members know who
can make decisions,
what their authority
levels are, and where to
go to gain an
understanding of what
key decisions have
been made.</td><td>OCE</td><td></td><td></td></tr></tbody></table>falsefalseC24H.1.1L265ySERIALSTARTENDTable 2<table><tbody><tr><td><strong>Req ID</strong></td><td><strong>SE NPR Paragraph</strong></td><td><strong>Requirement Statement</strong></td><td><strong>Rationale</strong></td><td><strong>Req. Owner</strong></td><td><strong>Comply?</strong></td><td><strong>Justification</strong></td></tr><tr><td>SE-05</td><td>2.1.5.2</td><td>For those
requirements
owned by Center
Directors, the
technical team
shall complete
the compliance
matrix in
Appendix H.2
and include it in
the SEMP.</td><td>For programs and
projects, the
compliance matrix in
Appendix H.2 is filled
out showing that the
program/project is
compliant with the
requirements of this
NPR (or a particular
Center's
implementation of
NPR 7123.1,
whichever is
applicable) or any
tailoring thereof is
identified and
approved by the
Center Director or
designee as part of the
program/project SEMP.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-06</td><td>2.1.6.1</td><td>The DGA shall
approve the
SEMP, waiver
authorizations,
and other key
technical
documents to
ensure
independent
assessment of
technical content.</td><td>The DGA, who is often
the TA, provides an
approval of the
SEMPs, waivers to
technical requirements
and other key
technical document to
provide assurance of
the applicability and
technical quality of the
products.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-24</td><td>4.2.1</td><td>The NASA
technical team
shall define the
engineering
activities for the
periods before
contract award,
during contract
performance,
and upon
contract
completion in the
SEMP.</td><td>It is important for both
the Government and
contractor technical
teams to understand
what activities will be
handled by which
organization
throughout the product
life cycle. The
contractor(s) will
typically develop a
SEMP or its equivalent
to describe the
technical activities in
their portion of the
project, but an
overarching SEMP is
needed that will
describe all technical
activities across the life
cycle whether
contracted or not.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-25</td><td>4.2.2</td><td>The NASA
technical team
shall use
common
technical
processes, as
implemented by
the Center's
documentation,
to establish the
technical inputs
to the RFP
appropriate for
the product to be
developed,
including product
requirements
and Statement of
Work tasks.</td><td>The technical team's
participation in the
development of the
RFP is critical to
enabling a successful
contracted effort.
Ensuring that the
proper application of
the common technical
processes into the
contracted effort will
enhance the chances
for success.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-26</td><td>4.2.3</td><td>The NASA
technical team
shall determine
the technical
work products to
be delivered by
the offeror or
contractor, to
include a
contractor SEMP
that specifies the
contractor's
systems
engineering
approach for
requirements
development;
technical solution
definition; design
realization;
product
evaluation;
product
transition; and
technical
planning, control,
assessment, and
decision analysis.</td><td>The technical team is
in the best position to
determine what kind of
work products from the
technical effort will
need to be delivered.
These products will
eventually be used by
the technical team to
determine the
suitability of the
contracted effort in its
ability to meet
requirements, satisfy
the stakeholder
expectations, and
perform as planned.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-27</td><td>4.2.4</td><td>The NASA
technical team
shall provide the
requirements for
technical insight
and oversight
activities planned
in the NASA
SEMP to the
contracting
officer for
inclusion in the
RFP.</td><td>In addition to the work
description and
products to be
delivered, how the
technical team will
gain an adequate
understanding of the
contracted work, what
authority (if any) they
will have to direct or
influence the work,
and their participation
at key milestone
reviews. In the end the
technical team needs
enough information to
advise the
program/project
manager as to the
adequacy of the
technical work.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-28</td><td>4.2.5</td><td>The NASA
technical team
shall have
representation in
the evaluation of
offeror proposals
in accordance
with applicable
NASA and
Center source
selection
procedures.</td><td>Technical personnel
will need to be
involved in reviewing
the proposals and
providing
advice/guidance on
their merits. These
personnel may or may
not be part of the
technical team that will
execute the
program/project.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-29</td><td>4.3.1</td><td>The NASA
technical team,
under the
authority of the
contracting
officer, shall
perform the
technical insight
and oversight
activities
established in
the NASA SEMP.</td><td>After the contract is
awarded, the
contracting officer will
depend on the
technical team to
execute the
oversight/insight of the
technical work as
defined in their SEMP
and the contract.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-30</td><td>4.4.1</td><td>The NASA
technical team
shall participate
in the review(s)
to finalize
Government
acceptance of
the deliverables.</td><td>Per the agreement in
the SEMP and the
contract, the technical
team will participate in
the milestone reviews.
Ultimately, this
knowledge will enable
the technical team to
provide advice to the
program/project as to
the suitability of the
product for acceptance.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-31</td><td>4.4.2</td><td>The NASA
technical team
shall participate
in product
transition as
defined in the
NASA SEMP.</td><td>In accordance with the
SEMP, the technical
team will participate in
the execution of the
final aspects of the
end product??"either
its transference in
whole to the
program/project
customer, its
operations and/or the final decommissioning,
and disposal. These
activities may be
performed by the
same team that was
involved in its
development or by
other technical teams.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-32</td><td>5.2.1.1</td><td>The technical
team shall
develop and
document plans
for life-cycle and
technical reviews
for use in the
project planning
process.</td><td>Each of the life-cycle
reviews, as well as any
other technical status
reviews, needs to be
identified and
documented so that all
stakeholders will know
how the
program/project's
progress will be
assessed. This will
typically be captured
within the SEMP or in
a separate Review Plan.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-33</td><td>5.2.1.3</td><td>The technical
team shall
conduct the
life-cycle and
technical reviews
as indicated in
the governing
project
management
NPR.</td><td>The technical team will
be responsible for
generating and
presenting many of the
technical topics during
a life-cycle and
technical review.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-34</td><td>5.2.1.4</td><td>The technical
team shall
participate in the
development of
entrance and
success criteria
for each of the
respective
reviews.</td><td>The entrance and
success criteria in
Appendix G are
provided as guidelines
(not requirements)
except where notated.
It is expected that they
will be modified as
needed by the
program/project
according to their size,
complexity, type of
end product being
produced, formality,
etc. Specific names of
documents may be
provided for clarity,
non-applicable
products eliminated,
and new products
added as needed for
clarity and completeness.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-35</td><td>5.2.1.5.a (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
MCR: Baselined
stakeholder
identification and
expectation definitions.</td><td>For a MCR one of the
key products is
capturing the
stakeholder
expectations. These
may be identified as
needs, goals, and
objectives, or other
methods for capturing
their expectations.
These are captured in
a document or a
database/model. After
all comments from the MCR are
dispositioned, the set
of stakeholder
expectations are
updated with the
approved comments
and then baselined.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-36</td><td>5.2.1.5.a (2)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
MCR: Baselined
concept definition.</td><td>Presenting one or
more feasible ways of
accomplishing the
stakeholder
expectations is a key
product of the MCR.
These are captured in
a document or a
database/model. After
all comments from the
MCR are
dispositioned, the
concept(s) are
updated with the
approved comments
and then baselined.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-37</td><td>5.2.1.5.a (3)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
MCR: Approved
MOE definition.</td><td>The Measures of
Effectiveness capture
the stakeholder's view
of what would be
considered the
successful
achievement of each
expectation. These will
help in the later
identification of
requirements, criteria
for trade studies and in
the success criteria for
the validation efforts.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-38</td><td>5.2.1.5.b (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
SRR: Baselined
SEMP for
projects,
single-project
programs, and
one-step AO
programs.</td><td>The SEMP is a key
document for the
technical effort in a
similar manner that the
program/project plan
captures the
programmatic efforts.
These are captured in
a document or a
database/model. For
projects, single-project
programs, and
one-step AO programs
after all comments
from the SRR are
dispositioned, the
SEMP is updated with
the approved
comments and then
baselined. The SEMP
is baselined in a later
phase for the other
types of programs and
so will be a "Not
Applicable" in this line
for uncoupled, tightly
coupled, and loosely
coupled programs.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-39</td><td>5.2.1.5.b (2)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
SRR: Baselined
requirements.</td><td>The program/project
requirements are a
key product for the
SRR. These are
captured in a
document or a
database/model. After
all comments from the
SRR are
dispositioned, the
requirements are
updated with the
approved comments
and then baselined.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-40</td><td>5.2.1.5.c (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
MDR/SDR:
Approved TPM
definitions.</td><td>A key product at the
SDR is the set of
TPMs that the
program/project has
identified as the
important measures to
track for their efforts.
These may be
associated with the
key driving
requirements, key
performance
parameters, leading or
lagging indicators, or
other measures that
are important to
periodically measure
and track.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-41</td><td>5.2.1.5.c (2)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
MDR/SDR:
Baselined
architecture
definition.</td><td>One of the key
products of a SDR is
the proposed
architecture that will
accomplish the
requirements. These
are captured in a
document or a
database/model. After
all comments from the
SDR are
dispositioned, the
architecture
description is updated
with the approved
comments and then
baselined.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-42</td><td>5.2.1.5.c (3)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
MDR/SDR:
Baselined
allocation of
requirements to
next lower level.</td><td>Now that the
overarching
architecture has been
defined, it is important
to show how the
requirements are
allocated to the
architecture elements
of the next lower level
of the product
hierarchy. These are
captured in a
document or a
database/model. After
all comments from the
SDR are
dispositioned, the
allocation is updated
with the approved
comments and then baselined.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-43</td><td>5.2.1.5.c (4)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
MDR/SDR: Initial
trend of required
leading indicators.</td><td>The trend is presented
for the leading
indicators that have
been identified by the
Agency as required for
each program/project.
These will typically be
in graphical form but
could also be tabular
or other form
appropriate for the
project. At SDR this
will be the initial set of
trends that have been
captured since SRR.
Since final hardware
has not been produced
at this point, the trends
will be on the
estimated parameters.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-44</td><td>5.2.1.5.c (5)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
MDR/SDR:
Baseline SEMP
for uncoupled,
loosely coupled,
tightly coupled,
and two-step AO
programs.</td><td>The SEMP is a key
document for the
technical effort in a
similar manner that the
program plan captures
the programmatic
efforts. These are
captured in a
document or a
database/model. For
uncoupled, loosely
coupled, tightly
coupled, and two-step
AO programs, after all
comments from the
MDR/SDR are
dispositioned, the
SEMP is updated with
the approved
comments and then
baselined. The SEMP
is baselined in an
earlier phase for
projects and
single-project
programs and so will
be a "Not Applicable"
in this line for those
types of programs.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-45</td><td>5.2.1.5.d (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
PDR: Preliminary
design solution
definition.</td><td>The key product of a
PDR is the preliminary
design itself. The
design is captured in
one or documents,
models, databases,
drawings, and other
means. Comments
from the PDR will be
captured in the final
design for the next
review.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-46</td><td>5.2.1.5.e (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
CDR: Baseline
detailed design.</td><td>The key product of a
CDR is the final
design. The design is
captured in one or
more documents,
models, databases,
drawings, and other
means. The final
design is updated with
approved comments
from the review, and
the design is updated
to represent the design
that will be implemented.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-47</td><td>5.2.1.5.f (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
SIR: Updated
integration plan.</td><td>A key product of a SIR
is the updated
integration plans.
These will describe
how the products
associated with this
review will be
integrated.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-48</td><td>5.2.1.5.f (2)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
SIR: Preliminary
VandV results.</td><td>Another key product of
a SIR is the initial
VandV results from
any of the lower level
products that are
associated with this
review. With the
recursive nature of the
SE engine, products
will be integrated and
verified/validated from
the bottom of the
product layer to the
top. So, prior to
integration into larger
assemblies, lower level
products will have
been through their
VandV activities. This
ensures that, when
they are assembled
into the higher product
layers, they will work
as intended.
Programs/projects
may decide to perform
VandV only at
assembly levels??"as
captured in their
SEMP??"and so initial
VandV results may or
may not be available.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-49</td><td>5.2.1.5.g (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
ORR: Updatedoperational
plans.<br></td><td>The plans on how the
product will be
operated during its
operational/sustaining
phase are presented
at the ORR. This is to
ensure that all
stakeholders are
aware and approve of
these plans.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-50</td><td>5.2.1.5g (2)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
ORR: Updated
operational
procedures.</td><td>The procedures on
how the product will be
operated during its
operational/sustaining
phase are presented
at the ORR. This is to
ensure that all
stakeholders are
aware and approve of
these procedures.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-51</td><td>5.2.1.5.g (3)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
ORR:
Preliminary
decommissioning
plans.</td><td>AT ORR it is important
to describe how the
product will ultimately
be decommissioned
when it has
accomplished its
mission. This is to
ensure that
decommissioning will
be feasible before the
product is put into use.
These are captured in
a document or a
database/model. After
all comments from the
ORR are
dispositioned, the plan
is updated with the
approved comments
and then baselined.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-52</td><td>5.2.1.5.h (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
FRR: Baseline
disposal plans.</td><td>AT FRR it is also
important to describe
how the product will
ultimately be disposed
of when it has
accomplished its
mission. This is to
ensure that disposal
will be feasible before
the product is put into
use. These are
captured in a
document or a
database/model. After
all comments from the
FRR are dispositioned,
the plan is updated
with the approved
comments and then
baselined.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-53</td><td>5.2.1.5.h (2)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
FRR: Baseline
VandV results.</td><td>At FRR, the baselined
VandV results for the
product are presented
and any remaining
open work identified.
This is to ensure that
the product is ready for
flight. Note that for
some
programs/projects the
VandV results may
need to be baselined
at ORR per Centerpolicies/procedures.
Maturing and
presenting a product
earlier than required in
the Agency NPR is at
the discretion of the
program/project/Center
and does not require a
waiver.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-54</td><td>5.2.1.5.h (3)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
FRR: Final
certification for
flight/use.</td><td>The key product at the
FRR is the certification
that the product is
ready for flight/use.
This gains agreement
with all key
stakeholders that the
product is ready to put
into the operational
phase. Any remaining
open items are
identified, and plans
for closure are
developed.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-55</td><td>5.2.1.5.i (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
DR: Baseline
decommissioning
plans.</td><td>The key product at the
DR is the plan on how
the product will be
removed from service.
The approved
comments from the DR
are used to baseline
the plan.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-56</td><td>5.2.1.5.j (1)</td><td>The technical
team shall
provide the
following
minimum
products at the
associated
milestone review
at the indicated
maturity level:
DRR: Updated
disposal plans.</td><td>The key product of the
DRR is the plan on
how the product will be
disposed of after it has
been
decommissioned. The
approved comments
from the DRR are
used to update the plan.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-57</td><td>5.2.2.2</td><td>Technical teams
shall monitor
technical effort
through periodic
technical status
reviews.</td><td>In addition to the
life-cycle reviews, the
technical teams need
to periodically monitor
the technical progress
of their
program/project.
These may be held
formally or informally
with relevant personnel.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-58</td><td>6.2.3</td><td>The technical
teams shall
define in the
project SEMP
how the required
17 common
technical
processes, as
implemented by Center documentation,
including
tailoring, will be
recursively
applied to the
various levels of
project product
layer system
structure during
each applicable
life-cycle phase.</td><td>The SEMP is the key
document that lays out
the work that the
technical team needs
to perform and the
manner in which they
will perform it. This
requirement ensures
that each of the 17 common technical processes is
addressed and how it
will be applied to the
various levels in the
end-item product
hierarchy and their
associated enabling
products.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-59</td><td>6.2.6</td><td>The technical
team shall
ensure that any
technical plans
and discipline
plans are
consistent with
the SEMP and
are
accomplished as
fully integrated
parts of the
technical effort.</td><td>Since the SEMP is the
primary planning
document for the
systems engineering
effort, all subsequent
planning documents
are in alignment and
consistent with the
SEMP.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-60</td><td>6.2.7</td><td>The technical
team shall
establish TPMs
for the project
that
track/describe
the current state
versus plan.</td><td>The measures that the
program/project will
use to track the
progress of key
aspects of the
technical effort are
identified and
documented. These
TPMs will include the
required leading
indicators described in
other requirements of
this NPR and also any
project-unique
measures deemed
necessary to track the
key performance
parameters.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-61</td><td>6.2.8</td><td>The technical
team shall report
the TPMs to the
program/project
manager on an
agreed-to
reporting interval.</td><td>The selected TPMs
need to be measured
periodically and their
trends reported to the
program/project
manager at the
agreed-to interval as
documented in the
SEMP. This ensures
the PM is kept up to
date on these key
parameters so that
decisions can be made
in a timely manner.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-62</td><td>6.2.9.a</td><td>The technical
team shall
ensure that the
set of TPMs
include the
following leading
indicators: Mass
margins for
projects involving
hardware.</td><td>If the program/project
has hardware
elements, tracking of
the remaining margins
associated with their
mass is a required
leading indicator
measure by the
Agency. This is
especially important for
flight projects. For
ground or other projects in which mass
is not relevant, a
waiver to this
requirement can be
documented in the SEMP.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-63</td><td>6.2.9.b</td><td>The technical
team shall
ensure that the
set of TPMs
include the
following leading
indicators: Power
margins for
projects that are
powered.</td><td>If the program/project
has elements that
require power, tracking
of the remaining
margins associated
with their power
consumption is a
required leading
indicator measure by
the Agency. This is
especially important for
flight projects. For
ground or other
projects in which
power consumption is
not relevant, a waiver
to this requirement can
be documented in the
SEMP.</td><td>CD</td><td></td><td></td></tr><tr><td>SE-64</td><td>6.2.10</td><td>The technical
team shall
ensure that the
set of Review
Trends includes
closure of review
action
documentation
(Request for
Action, Review
Item
Discrepancies,
and/or Action
Items as
established by
the project) for
all software and
hardware
projects.</td><td>During life-cycle
reviews, comments
from the reviewers are
captured on forms,
databases,
spreadsheets, or other
manner. Depending on
the program/project,
these may be called
RFAs, RIDs, Action
Items, or other
terminology. Whatever
they are called, the
disposition and closure
of these comments -
typically called their
burndown - are
required indicator
trends by the Agency.
This ensures that the
approved comments
are incorporated into
the designs and plans
in a timely manner.</td><td>CD</td><td></td><td></td></tr></tbody></table>falsefalseC24H.2.1L265ySERIALSTARTENDe1R5He4e1R5He3e3R3Be5e3R5Je1e4R5Je1e4R3Be3T281e5R3Ce3e3T281R3Ce4