Issue 01C-1: Testability metrics based on maintenance philosophy, such as Fault Resolution, can provide a means of validating predictive measures. At this point, the information models used to support definition of metrics in P1522 are insufficient to address maintenance philosophy. Need to add a link to the SIMICA information model to reference P1522 and update P1522 to specify both predictive and actual measures. Then need to emphasize the role of MAI in collecting data based on maintenance practice. Still need something to make sure the predictive measures in P1522 reflect those maintenance practices. All of this is contingent upon P1522 surviving.
Status: CLOSED. IEEE Std 1522-2004 is being withdrawn.
Issue 06C-1: IEEE Std 1522 is not currently being used. Need to examine reasons for this and determine the future of the standard. Some possibilities to examine include: Does it a need management component (ala MIL HDBK 2165)? Are metrics too inaccessible due to tie to 1232? Is it simply a publicity/perception issue? Is there resistance to objective accountability? Discuss with program managers (Russell Shannon—NAVAIR).
Status: CLOSED. IEEE Std 1522-2004 is being withdrawn.
Issue 07B-1: The current order constraint in 1232-2002 is difficult to understand and, therefore, difficult to use. The DMC decided to “minimalize” the order constraint to focus only on preconditions and added actions to the model. It is recognized that this minimalist construct is at best suboptimal and possibly “broken.” Unfortunately, timing prevents a new construct being included in the model, and the DMC felt something needed to be there to address ordering. For the next revision, a more expressive and usable order constraint facility needs to be incorporated into the model, replacing the current minimalist construct. One proposal on hand is Log #451.
Status: OPEN Medium Priority
Issue 07C-1: Need to perform a trade study to determine what new services are actually required. This is essential for establishing a usable scope for the service specification. The focus here is for the next revision of the standard.
Status: OPEN Low Priority
Issue 07D-1: These standards (especially AI-ESTATE) are difficult to understand due to the large number of options available to an implementer. It is really important to provide some kind of guidance to the implementer. The hope is that a User's Guide can be put together once the revision has cleared its next ballot.
Status: OPEN Medium Priority
Issue 08A-1: Craig M of NAVAIR suggest several additions to the SIMICA model at the 08-A meeting. One of those suggestions was to add a subtype of Design Model: Obsolescence Model. The question is whether the Obsolescence Model can be used a basis for triggering a maturation event and thereby affecting the Diagnostics Model. John S. has the use case (Asset Specific Diagnostics).
Status: OPEN Medium Priority
Issue 08A-2: John S. and Darryl B. raised the issue of Part 28 for XML schemas to support validation of instance models against the information model. The general issue of validating XML instance documents against EXPRESS information models needs to be explored, whether using a schema derived from Part 28 or an XML schema geared toward XSLT translation to Part 21.
Status: OPEN High Priority