![[NASA Logo]](../Images/nasaball.gif) |
NASA Procedures and Guidelines |
||||
This Document is Obsolete and Is No Longer Used.
|
|||||
|
|
|||||
|
|
||||
| | TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | AppendixA | AppendixB | AppendixC | AppendixD | ALL | | |||||
This chapter identifies the requirements that are specific to the NASA ELV payload safety review and approval process, including the required sequence of activities and associated deliverables. For each NASA ELV payload project, the overall goals of this process are to:
a. Assure the appropriate representation and involvement of all organizations that support the mission.
b. Identify and resolve any safety concerns as early as feasible during the project timeline.
c. Assure that the project obtains the formal approval of all required approving authorities for the mission (internal and external to the Agency).
NASA ELV payload missions involve various combinations of payload organizations, payload contractors, launch vehicles, payload processing sites, and launch sites. To address this situation, a key aspect of the safety review process is the establishment of a unique PSWG for each payload. Each PSWG and its required activities are designed to ensure the appropriate involvement and coordination of all organizations and stakeholders that support the associated mission and share safety responsibility for the mission (internal and external to the Agency). PSWGs provide guidance on tailoring project-specific safety requirements from NASA-STD 8719.24 Annex, assist in the development of any waiver requests, and help the payload project ensure safety submittals are complete, reviewed, and approved per this NPR. PSWGs ensure compliance with safety requirements that apply to their payload and provide clear and useful guidance to the Payload Project Office. PSWGs also work proactively with the project to identify potential hazards and safety issues and their impact on the resources of the organizations at risk. The PSWGs advise their respective payload project organizations on strategies for early hazard abatement, mitigation, or resolution. Paragraph 2.3.2.a of this NPR identifies the organizations represented in each PSWG.
Figure 2-1, Typical ELV Payload Safety Review Process Interfaces
2.3.1 Each NASA ELV Payload Project Manager (or designee) shall:
a. Ensure that Contract, Grant, Cooperative Agreement, or other Agreement Officers are provided with NASA-STD 8719.24 and other requirements documentation and provisions to satisfy the requirements of NASA-STD 8719.24 and this NPR for incorporation into contracts and agreement(s) (Requirement).
b. Implement a System Safety Program that complies with this NPR, NPR 8715.3, and NASA-STD 8719.24, properly implement the applicable safety requirements, and successfully complete the payload safety review and approval process (Requirement).
Note: This includes funding for additional safety support or the involvement of subject matter experts.
c. Ensure that all project technical development, design, test, and review processes incorporate system safety engineering throughout all project phases and in accordance with NPR 7120.5, NPR 7123.1, NPR 8715.3, NASA-STD 8719.24 and the project's System Safety Plan (Requirement).
d. Ensure that the design and operations of flight hardware, software, and associated GSE provide for safety through the use of approved design, analysis, and verification techniques (Requirement).
e. Ensure that the payload project's timeline provides for compliance with the established payload safety review and approval process (Requirement).
f. Assign a Payload Project System Safety Engineer for the project (see paragraph 2.3.2 of this NPR) (Requirement).
g. Notify the NASA ELV Payload Safety Manager of the new project and provide contact information for the appointed Payload Project System Safety Engineer (Requirement).
h. Ensure all project personnel involved in the ELV payload safety review process understand the process, understand their associated roles and responsibilities, and have experience commensurate with the complexity of the project (Requirement).
i. Establish and implement any project-level processes and requirements needed to satisfy safety requirements and to ensure that the project fully participates in, and supports, the safety review and approval process activities identified in paragraph 2.4 of this NPR regardless of the launch vehicle provider or launch vehicle procurement method (Requirement).
j. Ensure that all requirements contained in the project's tailored requirements document developed per paragraphs 1.4.1 of this NPR are implemented for its payload and associated GSE or that the project obtains an approved ELS determination or waiver per paragraphs 1.4.7 and 1.4.8 of this NPR for any requirement not satisfied (Requirement).
k. Ensure spacecraft contractor oversight is defined in the Project Safety and Mission Assurance Plan required by NPR 7120.5 and the project's System Safety Plan required by NASA-STD 8719.24 and performed and documented to enable safe integration, testing, and other processing of the payload and prevent the transfer of unanticipated hazards (Requirement).
l. Ensure safety information (including safety review status and any safety concerns associated with each subsystem and integrated system) is presented at appropriate project reviews, including (but not limited to) System Requirement Reviews, Preliminary Design Reviews (PDR), Critical Design Reviews (CDR), Pre-Environmental Reviews, and Pre-Ship Reviews (Requirement).
Note: The Payload Project System Safety Engineer typically presents the safety information at the various project reviews (see paragraph 2.3.2).
m. Approve all safety review and approval process deliverables per paragraph 2.4 of this NPR prior to submittal to the PSWG (Requirement).
n. Obtain all safety approvals and ensure safety review activities are completed in accordance with paragraph 2.4 in this NPR as needed to accomplish project management requirements per NPR 7120.5 and accomplish mission processing (Requirement).
o. Ensure that the project fully implements all safety plans and procedures required by this NPR and NASA-STD 8719.24 and as approved by the PSWG (Requirement).
p. Ensure that the payload design process incorporates system safety engineering activities integral to identifying hazards, developing solutions to mitigate or eliminate the hazards, verifying the implementation of these solutions, and ensuring compliance with this NPR (Requirement).
q. Ensure that all open hazard control safety verification actions are completed and that the status of any open items in the Safety Verification Tracking Log and any payload safety issues that could impact major project milestones are briefed during safety and project reviews (Requirement).
r. Ensure that the PSWG Chairperson is notified of any mishaps or close calls that take place during launch area payload processing and ground operations (Requirement).
s. Ensure that when the project includes a planned return-to-Earth payload recovery or sample return, the following actions are accomplished (Requirement):
(1) All potential hazards associated with the payload or sample recovery are identified and controlled.
(2) A safety plan is developed addressing roles, responsibilities, interfaces, safety requirements, processes, and activities to be applied in ensuring safe payload or sample recovery.
(3) Documented procedures are developed.
(4) The project's Mishap Preparedness and Contingency Plan addresses payload or sample recovery.
(5) A safety representative for the return-to-Earth payload or sample-return participates on the project???s PSWG as necessary.
Note: These payload or sample-recovery documents must be reviewed and approved by the appropriate authorities.
2.3.2 The Payload Project System Safety Engineer for a payload project performs as the project's primary member of the PSWG including serving as the project's lead for preparation and submittal of safety review and approval process deliverables specified in paragraphs 2.4 of this NPR and NASA-STD 8719.24. The Payload Project System Safety Engineer shall:
a. Coordinate with the NASA ELV Payload Safety Manager to ensure establishment of the project's PSWG and that it includes the following members as applicable to each mission (Requirement):
(1) PSWG Chairperson (see paragraph 2.3.4 of this NPR).
(2) Payload Project System Safety Engineer.
(3) Payload contractor safety representative(s).
(4) Launch site range safety organization representative(s).
(5) Launch vehicle contractor system safety engineer.
(6) Payload processing facility safety representative.
(7) NASA Kennedy Space Center (KSC) Safety and Mission Assurance Launch Services Division System Safety Engineer or equivalent.
(8) Payload or sample-recovery organization safety representative (as needed).
Note: The NASA ELV Payload Safety Manager will coordinate with the KSC Safety and Mission Assurance Launch Services Division in establishing the project's PSWG for projects using Launch Services Program services. For these projects, the NASA KSC Safety and Mission Assurance Launch Services Division System Safety Engineer typically serves as the PSWG Chairperson.
For projects not acquiring a launch vehicle via the NASA Launch Services Program, the ELV Payload Safety Manager coordinates with the Payload Project Office to establish a PSWG. Composition of the PSWG and member participation may vary based on project activities, technical issues, multi-Center project involvement, or operational requirements.
If there is a planned return-to-Earth payload or sample recovery, the recovery operations are often handled by a separate organization. It may or may not be beneficial for the recovery organization to have a safety representative on the PSWG depending on the level of impact the recovery hardware and operations have on payload design and processing prior to launch.
(9) Other subject matter experts as appropriate.
b. Keep the Payload Project Manager informed of mission safety status (Requirement).
c. Ensure that a Safety Verification Tracking Log is established, maintained, and made available for viewing electronically by the project, PSWG, and Agency Team (Requirement).
Note: The Safety Verification Tracking Log is a deliverable for Safety Review III per paragraph 2.4.2.e.(2).(b) of this NPR and is used to track closure of each open hazard control verification identified in the hazard reports until all verifications have been completed.
d. Ensure that technical operating procedures are submitted for review and approval by local safety authority and other responsible organizations in accordance with the safety requirements of the specific operating location (Requirement).
e. In coordination with the PSWG Chairperson, establish and maintain an integrated schedule of PSWG activities and all relevant project, launch, and other mission milestones, reviews, or meetings that address the topic of payload safety to include place, time, and date for each activity (Requirement).
2.3.3 Each PSWG member participates in the safety review and approval process to ensure compliance with all safety requirements for their area of responsibility and authority. Each PSWG member shall:
a. Review and provide comments or a "No Comments" statement to the PSWG Chairperson on all payload project safety review deliverables within 30 days after submittal and on meeting minutes within five days after distribution (Requirement).
b. In response to requests for concurrence per paragraph 1.4 of this NPR, determine the acceptability of project-specific payload safety requirements, including ELS determinations, and requests for waivers to safety requirements that are within their scope of responsibility or may be a concern to their organization (Requirement).
Note: PSWG members obtain their management's determination as needed.
c. Coordinate with the PSWG and, if needed, with the Agency Team, to resolve payload safety concerns (Requirement).
d. Ensure that payload, facility, and payload/launch vehicle integration issues are disseminated to their organization and to other PSWG members (Requirement).
e. Participate in all PSWG activities associated with their areas of responsibility, including, but not limited to, meetings, mission safety reviews, design reviews, ground operations reviews, and others activities as required by the PSWG Chairperson (Requirement).
f. Assess and concur on plans and hazard reports for operations in facilities that fall under their safety responsibility as needed to receive and process the payload (Requirement).
2.3.4 The PSWG Chairperson for a payload project shall:
a. Coordinate with the Payload Project System Safety Engineer to schedule and conduct PSWG meetings (Requirement).
b. Ensure that PSWG activities and decisions include the collective input and participation from all PSWG members (Requirement).
c. Ensure that the PSWG signature on official correspondence indicates documented concurrences from the PSWG members (Requirement).
d. Ensure all required safety review deliverables are made available to the PSWG members and others as needed (Requirement).
e. Ensure that the PSWG, the Agency Team, and the Launch Services Program representative (or equivalent) are invited to all PSWG activities and have access to all deliverables in accordance with applicable export control requirements (see paragraph 2.6.5 of this NPR) (Requirement).
f. Ensure all comments to safety review submittals are consolidated, coordinated, and furnished to the Payload Project System Safety Engineer no later than 35 days after data submittal (Requirement).
g. Ensure PSWG activities are documented to include notices, scheduling, data receipt and distribution, minutes, data/document review comments, action items, key issues, decisions, and overall project status regarding completion of the safety review and approval process (Requirement).
h. Ensure documentation of actions and major decisions from each PSWG meeting are reviewed for concurrence by attendees at the end of the meeting and draft minutes are available for review following the meeting (Requirement).
i. Ensure distribution of final minutes within seven business days after each PSWG meeting (Requirement).
j. Ensure availability/distribution/timely notification of the project safety schedule and changes to all parties involved in the safety review and approval process (Requirement).
k. Ensure PSWG participation by appropriate PSWG members, as required, at payload/launch vehicle integration working group meetings (e.g., Ground Operations Working Groups, Mission Integration Working Groups) (Requirement).
l. In coordination with all PSWG members, schedule and conduct PSWG meetings concurrently with major project reviews (e.g., PDR and CDR) and as required to meet the safety milestones in this NPR (Requirement).
Note: Throughout this NPR, "PDR" and "CDR" refer to theproject's mission PDR and CDR.
Note: The PSWG has the flexibility to hold meetings in conjunction with any of the design or readiness reviews (e.g., mission, system, instrument, ground systems).
m. Ensure the NASA ELV Payload Safety Manager is informed of any important safety issues to include potential risk issues that may impede the safety review process, waiver issues, and safety requirements interpretation issues (Requirement).
n. Ensure that all mission support and safety-related documents are made available to the PSWG members, Agency Team, the NASA ELV Payload Safety Manager, or other subject matter experts or technical authorities (Requirement).
Note: The preferred approach is to use a secure Web site for this purpose.
o. Coordinate with the NASA ELV Payload Safety Manager to establish a resolution approach if the PSWG cannot reach concurrence on an issue (Requirement).
p. Coordinate with the PSWG and the project to ensure implementation of recommendations, interpretations, and resolutions of any safety concern provided by the Agency Team (Requirement).
Note: The PSWG Chairperson also has responsibilities under the Tailoring Process per paragraph 1.4.1 of this NPR.
2.3.5 The NASA ELV Payload Safety Manager (or designee) shall:
a. Track the status of each payload project as it proceeds through the safety review and approval process and provide guidance on the associated activities, tools, and deliverables as needed (Requirement).
b. Notify the Payload Project Manager and other authorities of any concern that may adversely impact the project and provide guidance on how the project should proceed (Requirement). For example:
(1) A major safety-related risk is identified during the safety review process.
(2) The required safety review activities or deliverables of this NPR are not met (or product quality is inadequate for that phase of the project life cycle) and fail to fulfill the required safety gate products prior to the project's Key Decision Points (KDP) per NPR 7120.5.
c. Sign the Certificate of ELV Payload Safety Compliance upon ensuring that all Agency Team concerns have been addressed (Requirement).
d. Issue a letter forwarding the Certificate of ELV Payload Safety Compliance to the Payload Project Manager and others signifying the successful completion of the ELV Payload Safety Review III and that the ELV Payload Safety Program does not have any constraints to the continued processing of the spacecraft (Requirement).
Note: The NASA ELV Payload Safety Manager's overall responsibilities for the ELV Payload Safety Program are provided in paragraph 1.3.3 of this NPR.
2.4.1 In accordance with paragraph 2.3 of this NPR, the Payload Project Manager or designee and the PSWG Chairperson ensure that the payload safety review and approval activities take place as required in paragraph 2.4.2 of this NPR regardless of the launch vehicle provider or launch vehicle procurement method. The Payload Project System Safety Engineer ensures the preparation and submittal of the associated deliverables for review. Requirements regarding the contents of the deliverables are specified in NASA-STD 8719.24.
Note: The safety review and approval activities are designed to coincide with and provide safety input to the project management reviews required by NPR 7120.5; e.g., PDR, CDR, and Pre-ship Review. The safety review and approval activities identified below may also provide safety input to other required project, Center, and NASA Headquarters reviews; e.g., Peer Reviews, Launch Readiness Reviews, and Safety and Mission Success Reviews.
2.4.2 The Payload Project System Safety Engineer, in coordination with other payload project personnel, as needed, and the PSWG shall ensure that the safety review and approval process incorporates the following sequence of activities and associated deliverables, including compliance with the associated required schedule timing of deliverables (Requirement).
Exception: The Payload Project Office and the PSWG may alter process and deliverable dates required by this NPR through a formal agreement reached and documented before the original deliverable dates provided that safe processing, project schedule, and safety review input to KDPs as defined in NPR 7120.5 are not impacted.
Figure 2-2, Timeline of ELV Payload Safety Review Process
Note: The ELV Payload Safety Review Process shown in Figure 2-2 is conducted by a project's PSWG in order to provide necessary safety status and input to the Mission Project Reviews and the project's KDPs. Each Safety Review typically consists of several PSWG meetings spanning over a period of time versus a single meeting at a single point in time (see paragraphs 2.4.2b, c, and e of this NPR).
a. A Payload Safety Introduction Briefing is typically the first meeting of the PSWG (see definition in Appendix A).
(1) The Payload Project Office ensures that the Payload Safety Introduction Briefing occurs as early as possible, but no later than, midpoint of the Preliminary Design Phase (Phase B as defined in NPR 7120.5 and depicted in Figure 2-2).
(2) The Payload Project Office shall submit the following material for presentation, review, and discussion and be prepared to present the items listed in the Annex to NASA-STD 8719.24, Volume 1, Attachment 5 during the Payload Safety Introduction Briefing (Requirement):
(a) A list of nonapplicable chapters and sections using the Annex to NASA-STD 8719.24 Table of Contents, Volumes 3 and 6, as they relate to payload systems, instruments, operations and hazards known to date.
(b) A list of any known tailoring issues, previously approved waivers, and previously approved alternative approaches.
(c) Draft System Safety Plan that, as a minimum, provides a conceptual overview of the System Safety Program in accordance with NASA-STD 8719.24, Volume 3, Paragraph 4.1.1.
(d) Identification of known spacecraft/payload systems and a preliminary assessment of potential hazards documented in a preliminary hazard list.
(e) A high-level Ground Operations Flow Overview providing the location and relative timeline of major payload activities and tasks (e.g. payload arrival, special testing, fueling, payload integration, roll-out to pad, any known hazardous operations) as best known at the time of the Payload Safety Introduction Briefing.
Note: This briefing provides a forum for the project to introduce the mission to the PSWG and other authorities and allows for early identification of any safety concerns associated with the payload. The information provided at this briefing should be as complete as the technical maturity of the conceptual design and operations allow.
b. Safety Review I begins with the submittal of data no later than 30 days prior to the PDR per paragraph 2.4.2.b.(3) and shall be completed no later than 60 days after the project's PDR and no later than necessary to provide the PSWG's input to the project's KDP C as defined in NPR 7120.5 and depicted in Figure 2-2, whichever date comes first (Requirement).
(1) Safety Review I shall include a PSWG meeting held no later than 60 days after the PDR (Requirement).
(2) During Safety Review I, the PSWG shall approve the final System Safety Plan, discuss the resolution of comments to the Safety Data Package (see Appendix A for definition), address requirements issues through the review of the tailored requirements (project-specific NASA-STD 8719.24 Annex), assess the Preliminary Hazard Analysis and any Hazard Reports, and address any safety issues identified during the PDR (Requirement).
Note: Hazard Reports are to be documented on NF 1825 NASA ELV Payload Safety Hazard Report and Instructions found on the NASA ELV Payload Safety Web site at https://kscsma.ksc.nasa.gov/ELVPayloadSafety under the "ELV Payload Safety Forms" button. See NASA-STD 8719.24 Volume 1, Attachment 2 for further information on documenting Hazard Analysis.
(3) The payload project shall submit the following material no later than 30 days prior to the PDR (Requirement):
(a) Final System Safety Plan in accordance with NASA-STD 8719.24, Volume 3, Paragraph 4.1.2.
(b) Draft of tailored payload safety requirements using NASA-STD 8719.24 Annex with rationale for proposed tailoring using NASA-STD 8719.24 Annex.
(c) Safety Data Package I (as complete as possible) (see NASA-STD 8719.24, Volume 3, Paragraph 4.2.2 and Volume 3, Attachment 1).
(4) The PSWG Chairperson shall provide the Payload Project Manager with the status of Safety Review I including any safety concerns following the PDR meeting (Requirement).
(5) Safety Review I shall culminate with the PSWG Chairperson providing the Payload Project Manager with an assessment of the project's safety efforts and identification of any safety concerns to support the project's KDP C (as defined in NPR 7120.5) (Requirement).
c. Safety Review II begins with the submittal of data no later than 30 days prior to the project's CDR per paragraph 2.4.2.c.(3) and shall be completed no later than 60 days after the project's CDR to provide the PSWG's input to the project's KDP D as defined in NPR 7120.5 and depicted in Figure 2-2 (Requirement).
(1) Safety Review II shall include a PSWG meeting held no later than 60 days after the CDR (Requirement).
(2) During the Safety Review II, the PSWG shall discuss the resolution of comments to the Safety Data Package I, discuss any safety issues identified during the CDR, and review the project for any changes to the design, processing, or interfaces for new or increased hazards or safety issues (Requirement).
(3) The payload project shall submit the following material no later than 30 days prior to the CDR (Requirement):
(a) Safety Data Package II (see NASA-STD 8719.24 Annex, Volume 3, Attachment 1).
(b) If not yet completed, the final tailored payload safety requirements with sufficient rationale, derived from tailoring NASA-STD 8719.24 Annex.
(c) A Draft Ground Operations Plan (GOP) in accordance with NASA-STD 8719.24, Volume 6, Attachment 1, as a stand-alone document or included as part of Safety Data Package II.
(4) Safety Review II shall culminate with the PSWG Chairperson providing the Payload Project Manager with an updated assessment of the project's safety efforts and identification of any safety concerns to support the project's KDP D (as defined in NPR 7120.5) (Requirement).
d. If the payload will undergo processing at a NASA-owned facility or any facility where NASA personnel control the operation or are actively involved in performing work prior to the Safety Review III (see paragraph 2.4.2.e of this NPR), the project shall coordinate to define the applicable requirements and processes for safe payload processing at the host Center that meet the intent of the requirements defined in this NPR and NASA-STD 8719.24 (Requirement).
e. Safety Review III begins with the submittal of data per subparagraph (2), below, of this NPR and shall be completed at a PSWG meeting held at least 30 days prior to payload shipment to the processing site (Requirement).
(1) During Safety Review III, the PSWG shall verify that all safety requirements have been or will be satisfied at the appropriate time and any associated waivers have been approved (Requirement).
(2) The payload project shall submit the following material no later than 90 days prior to the payload shipment to the processing site (Requirement):
(a) Safety Data Package III (see NASA-STD 8719.24 Annex, Volume 3, Attachment 1).
(b) A Safety Verification Tracking Log identifying the open verifications from the Hazard Reports as required in Task 1 of the project's SSP (see NASA-STD 8719.24 Annex, Volume 1, Paragraph A2.2.1.8.1).
(c) A final GOP, in accordance with NASA-STD 8719.24, Volume 6, Attachment 1, as a stand-alone document or included as part of Safety Data Package III.
(3) Safety Data Package III shall be finalized, resolving all PSWG comments at least 30 days before the intended shipment of hardware to the prelaunch payload processing site (Requirement).
(4) The project shall provide a Certificate of ELV Payload Safety Compliance, signed by the Project Manager, with signature blocks for the PSWG Chairperson, Project SMA Technical Authority, and the ELV Payload Safety Manager (see Appendix D) (Requirement).
(5) PSWG Chairperson will obtain concurrence signatures and provide the ELV Payload Safety Manager with the Certificate of ELV Payload Safety Compliance and attachments. Then, the PSWG Chairperson will provide the Payload Project Manager with the status of Safety Review III including any safety concerns.
2.4.3 Upon receiving the Certificate of ELV Payload Safety Compliance, the ELV Payload Safety Manager shall provide the Payload Project Manager with a copy of the signed Certificate via a letter indicating successful completion of Safety Review III and the project's PSWG safety review and approval process (Requirement).
2.4.4 After transportation of the payload to the launch area processing facility, the project shall update the Safety Verification Tracking Log at least weekly (more frequently if the open items must be closed to remove operational constraints) and make the current Safety Verification Tracking Log available to all officials involved in the mission (Requirement).
2.6.1 Each payload project shall work with the PSWG chair to determine how the data submittals will be accomplished (Requirement).
2.6.2 The Payload Project Office shall manage the submission of data to ensure NASA information technology requirements are met; where applicable, it will ensure access by the PSWG, Agency Team, and others as designated; and that submittals are legible and uploaded in English (Requirement).
2.6.3 The security of electronic safety data submittals is governed by NPR 2810.1, Security of Information Technology.
2.6.4 Export Controlled Data
a. The export control data submittal requirements apply to U.S. Payload Project Offices only in accordance with NPR 2190.1, NASA Export Control Program.
b. Foreign Payload Project Offices are not normally required to provide the U.S. export control classification of their deliverables.
c. In the event that a foreign deliverable requires a U.S. export control classification, NASA export control resources shall be used to classify it (Requirement).
2.6.5 Proprietary and Sensitive But Unclassified (SBU) Data
a. The Payload Project Office and source of data shall determine the necessary requirements for SBU and proprietary data (Requirement).
b. The Payload Project Office shall implement the requirements and provide appropriate instruction (Requirement).
c. The Payload Project Office shall ensure that SBU and proprietary data are distributed only to persons who have a need to review such data in support of the safety review process (Requirement).
Note: Typically, the PSWG, NASA ELV Payload Safety Manager, Agency Team, and all other participating parties, as deemed necessary by the PSWG Chairperson or NASA ELV Payload Safety Manager, will have access to the secure project safety data. It is the responsibility of all parties to follow NPR 1600.1, NASA Security Program Procedural Requirements, and use NASA Form NF 1686 as required for controlling the data.
d. If the Payload Project Office discovers that the classification of data has changed, the Payload Project Office shall inform the PSWG and Agency Team in writing (Requirement).
| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | AppendixA | AppendixB | AppendixC | AppendixD | ALL | |
| | NODIS Library | Program Management(8000s) | Search | |