1. Introduction
    1.1. Project/Component Working Name:
	FMA IO Domain Service

    1.2. Name of Document Author/Supplier:
	dawn.tse@sun.com

    1.3. Date of This Document:
    	July 17, 2008

    1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project:
		HS PAC

	1.4.2. The ARC(s) you expect to review your project:
		FWARC

	1.4.3. The Director/VP who is "Sponsoring" this project:
		Jerri-Ann Meyer

	1.4.4. The name of your business unit:
		Solaris Software

    1.5. Email Aliases:
     	1.5.1. Responsible Manager: jay.jayachandran@sun.com
     	1.5.2. Responsible Engineer: dawn.tse@sun.com
     	1.5.3. Marketing Manager: Neil.Sadaranganey@sun.com
	1.5.4. Interest List: ldoms-fma@sun.com

2. Project Summary
    2.1. Project Description:

	This project defines a Fault Management Architecture (FMA) domain
	service required in a logical domain environment where ownership of one
	or more PCI root complexes is removed from the control domain and
	assigned to so-called root domains. This project extends the set of FMA
	Domain Services originally specified in FWARC/2006/141.

    2.2. Risks and Assumptions:

	See FWARC/2006/141

3. Business Summary
    3.1. Problem Area:

	See FWARC/2006/141

    3.2. Market/Requester:

	See FWARC/2006/141

    3.3. Business Justification:

	See FWARC/2006/141


    3.4. Competitive Analysis:

	See FWARC/2006/141


    3.5. Opportunity Window/Exposure:

	See FWARC/2006/141


    3.6. How will you know when you are done?:

	When FMA is able to utilize this service to successfully diagnose PCI
	fabric errors that occur in root domains.


4. Technical Description:

	See material in case directory.


5. Reference Documents:
	
	FWARC/2006/141


6. Resources and Schedule:
    6.1. Projected Availability:
	
	LDoms 1.1

    6.2. Cost of Effort:

	One staff month

    6.3. Cost of Capital Resources: N/A

    6.4. Product Approval Committee requested information:
    	6.4.1. Consolidation Name: LDoms Manager, Solaris
    	6.4.2. Contributing OpCo/BU/Division Name: Solaris
	6.4.3. Type of PAC Review and Approval expected: N/A
        6.4.4. Project Boundary Conditions: N/A
	6.4.5. Is this a necessary project for OEM agreements: No
	6.4.6. Notes/Dependencies: None
	6.4.7. Target RTI Date/Release: TBD
	6.4.8. Target Code Design Review Date: TBD
	6.4.9. Update approval addition: N/A

    6.5. ARC review type: Fast Track

7. Prototype Availability:
    7.1. Prototype Availability:
	Q1FY09

    7.2. Prototype Cost:
	Done using existing resources.