semi合集-English.pdf - 第1838页

SEMI E42-0704 © SEMI 1995, 2004 107 15.6.1 Distributed Recipe Namesp ace Segment Compliance Table — Tabl e 15.10 provides a statement of compliance for the distribute d recipe nam espace segment. Table 15.10 Distributed …

SEMI E42-0704 © SEMI 1995, 2004 106

15.5.3 Distributed Recipe Namespace Management Compliance Table — Table 15.8 provides a statement of

compliance for distributed recipe namespace management.

Table 15.8 Distributed Recipe Namespace Management Compliance Table

RMS Compliance Statement

Fundamental RMS Requirements Implemented RMS Compliant

Managed Recipe Object ❒ Yes ❒ No

Recipe Namespace Object ❒ Yes ❒ No

Recipe Namespace Manager Object ❒ Yes ❒ No

Distributed Recipe Namespace Object ❒ Yes ❒ No

Distributed Recipe Namespace Manager Basic

Requirements

❒ Yes ❒ No

OSS services ❒ Yes ❒ No

Attachment and detachment ❒ Yes ❒ No

Attached segment read-only level ❒ Yes ❒ No

Delete distributed namespace ❒ Yes ❒ No

Change request management ❒ Yes ❒ No

Segment change request ❒ Yes ❒ No

Segment action complete ❒ Yes ❒ No

Get change request ❒ Yes ❒ No

Rebuild distributed recipe namespace ❒ Yes ❒ No

❒ Yes

❒ No

Do not mark YES unless all fundamental RMS requirements are implemented.

15.6 Distributed Recipe Namespace Segment — Table 15.9 describes the requirements for compliance to the

distributed recipe namespace segment.

Table 15.9 Section References for Distributed Recipe Namespace Segment Capabilities

Capability Reference Fundamental

Fundamental compliance to managed recipe 15.2

Basic requirements 5.4, 5.11.1 (Table 5.1),

10.1.2

OSS services 5.3.1 Y

Change management 5.4.2, 5.9, 10.1.2.1 Y

Segment change approval (RMDSApproveAction) 10.1.2.2, 13.2.1 Y

Master segment 5.4.1, Table 5.2 N

SEMI E42-0704 © SEMI 1995, 2004 107

15.6.1 Distributed Recipe Namespace Segment Compliance Table — Table 15.10 provides a statement of

compliance for the distributed recipe namespace segment.

Table 15.10 Distributed Recipe Namespace Segment Compliance Table

RMS Compliance Statement

Fundamental RMS Requirements Implemented RMS Compliant

Managed Recipe ❒ Yes ❒ No

Basic Requirements ❒ Yes ❒ No

OSS Services ❒ Yes ❒ No

Change Management ❒ Yes ❒ No

Segment Change Approval ❒ Yes ❒ No

❒ Yes

❒ No

Additional Capabilities Implemented RMS Compliant

Master Segment ❒ Yes ❒ No ❒ Yes ❒ No

Do not mark YES unless all fundamental RMS requirements are implemented.

Additional capabilities may not be marked RMS compliant unless all fundamental RMS requirements are implemented.

15.7 Distributed Recipe Namespace Recorder — Table 15.11 describes the requirements for compliance to the

distributed recipe namespace recorder.

Table 15.11 Section References for Distributed Recipe Namespace Recorder Capabilities

Capability Reference Fundamental

Basic requirements 5.5, 5.11.2, Table 5.3 Y

OSS services 5.3.1, 10.2.1.1–10.2.1.3 Y

Add segment record (RMDRAddSegRecord) 10.2.2, 13.3.1 Y

Delete segment record (RMDRDelSegRecord) 10.2.3, 13.3.2 Y

Add change request record (RMDRAddChgRecord) 10.2.4, 13.3.3 Y

Delete change request record (RMDRDelChgRecord) 10.2.5, 13.3.4 Y

Get change request record (RMDRGetChgRecord) 10.2.6, 13.3.5 Y

15.7.1 Distributed Recipe Namespace Recorder Compliance Table — Table 15.12 provides a statement of

compliance for the distributed recipe namespace recorder.

Table 15.12 Distributed Recipe Namespace Recorder Compliance Table

RMS Compliance Statement

Fundamental RMS Requirements Implemented RMS Compliant

Basic Requirements ❒ Yes ❒ No

OSS Services ❒ Yes ❒ No

Add Segment Record ❒ Yes ❒ No

Delete Segment Record ❒ Yes ❒ No

Add Change Request Record ❒ Yes ❒ No

Delete Change Request Record ❒ Yes ❒ No

Get Change Request Record ❒ Yes ❒ No

❒ Yes

❒ No

Do not mark YES unless all fundamental RMS requirements are implemented.

15.8 Execution Recipe Compliance — This section defines RMS compliance for the execution recipe. An execution

recipe exhibits RMS compliance (1) through its attributes and (2) through its structure when transferred.

Table 15.13 describes the requirements for compliance to the execution recipe.

Table 15.13 Section References for Execution Recipe Capabilities

Capability Reference Fundamental

Mandatory and required attributes Table 6.1 Y

Recipe identifier (namespace, class, name, version) 6.3.3 Y

Preservation of designated downloaded attributes 6.3.5 Y

Change management (ChangedBody) (required if recipe executor can change

recipes)

6.3.1, Table 6.1 Y

Recipe modification EditedBy Table 6.1 N

Variable parameters (ExecLinkParam) Table 6.1 N

Multi-part recipe (LinkList) Table 6.1 N

Recipe compression (SrcRcpID) Table 6.1 N

Verification signature (VerificationID) Table 6.1, 11.2.2.2 N

15.8.1 Execution Recipe Compliance Table — Table 15.14 provides a statement of compliance for the execution

recipe.

Table 15.14 Execution Recipe Compliance Table

RMS Compliance Statement

Fundamental RMS Requirements Implemented RMS Compliant

Mandatory and required attributes ❒ Yes ❒ No

Recipe identifier (namespace, class, name, version) ❒ Yes ❒ No

Preservation of designated downloaded attributes ❒ Yes ❒ No

Change management ❒ Yes ❒ No

❒ Yes

❒ No

Additional Capabilities Implemented RMS Compliant

Recipe Modification ❒ Yes ❒ No ❒ Yes ❒ No

Variable Parameters ❒ Yes ❒ No ❒ Yes ❒ No

Multi-Part Recipe ❒ Yes ❒ No ❒ Yes ❒ No

Recipe Compression ❒ Yes ❒ No ❒ Yes ❒ No

Verification Signature ❒ Yes ❒ No ❒ Yes ❒ No

Do not mark YES unless all fundamental RMS requirements are implemented.

Additional capabilities may not be marked RMS compliant unless all fundamental RMS requirements are implemented.