# Presentation: 844655

## AMS-02 QUALITY SYSTEM, 

**CONFIGURATION MANAGEMENT OVERVIEW AND **
**AMS WEBSITE **

## AMS QUALITY SYSTEM, CONFIGURATION MANAGEMENT OVERVIEW, AND AMS WEBSITE

- AMS QUALITY SYSTEM  	MIKE FOHEY
- CONFIGURATION MANAGEMENT PLAN 	MIKE FOHEY
- LMSO QUALITY SYSTEM &
-           CONFIGURATION MANAGEMENT  	DAVE ELMORE
- SAFETY & MISSION ASSURANCE PLAN  	DAVID KAPLAN
- EXPERIMENT MILESTONE LOG  	CHRIS TUTT
- JSC AMS WEBSITE 	MIKE FOHEY

## ALPHA MAGNETIC SPECTROMETER – 02 

**(AMS-02)**
**QUALITY SYSTEMS**

- Mike Fohey
- July 15, 2004

## AMS QUALITY SYSTEMS

-  The Quality Management System (QMS) for JSC onsite design, development, and manufacturing shall be in accordance with JPD 5335.1, JSC Quality Policy and Quality Manual.
-  For offsite Lockheed Martin Space Operations (LMSO) activities (including procurements) the QMS shall conform to LMSEAT-31041, Quality System Manual (QSM) for the Science, Engineering, Analysis, and Test (SEAT) Operation.
-  The AMS Collaboration is responsible for selecting their own QMS. A QMS consistent with ISO 9001-2000 requirements is recommended.

## ALPHA MAGNETIC SPECTROMETER – 02 

**(AMS-02)**
**CONFIGURATION MANAGEMENT PLAN **

- Mike Fohey
- July 15, 2004

## PURPOSE

-   The CMP ensures that:
-   Programmatic commitments are met
-   Shuttle/Space Station-to-AMS Payload and 	Experiment-to-AMS Payload Integration 	Hardware (PIH) compatibility is achieved
-   Proposed AMS Experiment and Payload interface 	changes are processed and dispositioned in a 	formal and coordinated manner

## SCOPE

-  The CMP encompasses the management of:
-  	Design Requirements
-  	Specifications
-  	Critical Milestones
-  	Interface Agreements
-  	Flight Hardware Mission Requirements

## SCOPE

-  The CMP specifically addresses the configuration control of the AMS interfaces to the Shuttle and Space Station
- The CMP does not address the internal AMS Experiment configuration.

## CONFIGURATION CONTROL BOARD

-   The CMP establishes a **Configuration Control Board (CCB)** as the controlling authority for:
-  	Establishing the initial AMS project-level baseline
-  	Making changes to the baseline (when required)
-  	Controlling the AMS project-level documents and 	drawings
-  	Reviewing and dispositioning AMS generated 	change requests

## CONFIGURATION CONTROL BOARD

| AMS Configuration Control Board |  |  |
| --- | --- | --- |
| Chairman | Steve Porter | NASA Project Manager |
| Member | TBD | NASA Deputy Project Manager |
| Member | Anne Vaughan | NASA DA Representative	 |
| Member | J.J. Conwell | NASA MA Payload Integration Manager |
| Member | David Kaplan | NASA NA Representative |
| Member | Winston Reid | NASA OZ Payload Integration Manager |
| Member | Jack Keifenheim | NASA KSC Representative |
| Member | Mike Capell | AMS Experiment Representative |
| Member | Trent Martin | LMSO Project Manager |
| Secretary | Donna Cox | LMSO Representative |

**CONFIGURATION CONTROL BOARD**

## MEETING SCHEDULE

-   There will be weekly AMS Status Meetings on Tuesdays from 9:00 – 10:00 AM beginning August 3, 2004. The preliminary standard agenda includes: Risk Management Plan updates, status reports from LMSO and the Collaboration, and a review ofproject milestones.
-  The first Tuesday meeting of each month will be reserved for the AMS CCB. (NOTE: The meeting on August 3rd may or may not be a CCB.)

## CONTROLLED CLASSES* & IDENTIFICATION

-   The CMP establishes Configuration Control for all AMS GFE hardware, software and firmware that is Class I (Flight), Class II (controlled Non-flight), Class IIIW (controlled Non-flight), and GSE*
- The CMP defines the requirements for configuration identification of all controlled hardware, software and firmware

- * See CMP for definitions of Hardware Classifications

## CHANGE DEFINITIONS

- Requirements contained in the AMS Baseline
- Contract cost/provisions
- Interchangeability
- Safety
- Interfaces
- Any change to baselined documentation under configuration control

- Corrections to drawing errors
- “As-built” changes (i.e. does not affect fit, form, or function) to hardware which do not affect Class I items
- Additions of “either/or” items giving such choices as color preference

- _Type I Changes_

- _Type II Changes_

-  Type I Changes to baselined hardware, software, firmware, drawings, and AMS baselined documents shall be submitted to and approved by the CCB prior to implementation.
-  Type II Changes do not require CCB approval.

## CHANGE REQUEST PROCEDURES

-   Detailed procedures for preparing and submitting AMS Change Requests can be found in JSC 27542, Alpha Magnetic Spectrometer – 02 (AMS-02) Configuration Management Plan

## ALPHA MAGNETIC SPECTROMETER – 02 

**(AMS-02)**
**SAFETY AND MISSION ASSURANCE PLAN**

- David Kaplan
- July 15, 2004

## ALPHA MAGNETIC SPECTROMETER – 02 

**(AMS-02)**
**EXPERIMENT MILESTONE LOG**

- Chris Tutt
- July 15, 2004

## Experiment Milestone Log

-  	Goal is to give NASA project management 	insight into experiment status, not control.
-  	Log will be maintained by LMSO and 	status reported monthly at AMS CCB.

## Sample Log Items

- Non-safety related test dates and status for experiment hardware.
- Functional tests
- Non-safety structural and thermal tests
- Major integration milestone dates for collaboration hardware.
- Manufacturing schedules for collaboration hardware.
- Certification of Compliance status for major hardware items.

## Experiment Milestone Log Status

- Milestone log still in early development.
- LMSO will meet with collaboration at next quarterly TIM and begin selecting appropriate milestones.
- Final selection of what will be tracked will be made jointly by AMS collaboration and NASA/JSC.

## ALPHA MAGNETIC SPECTROMETER – 02 

**(AMS-02)**
**ENGINEERING DIRECTORATE (EA) WEBSITE**

- Mike Fohey
- July 15, 2004

## AMS-02 EA WEBSITE

- A “green” server is open for public access as opposed to the current “amber” server that is open to users on the JSC domain (JSC, contractors, and other NASA sites).
- To facilitate configuration management, both the internal and external web pages will access files that reside on the external server.

**AMS-02 EA WEBSITE**

## AMS-02 EA WEBSITE – JSC INTERNAL

- The internal website gives users in the JSC domain the ability to use the links on the left side of the page to access locations inside the JSC firewall.
- The internal website gives users access to the AMS RID System and the AMS Risk Management System.

**AMS-02 EA WEBSITE – JSC INTERNAL**

- _[http://www4.](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[jsc](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[.](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[nasa](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[.](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[gov](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[/](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[eaprojects](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[/ea-projects/](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[flightgfe](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[/](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[ams](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[_02/html/](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[ams](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[_02.](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)__[htm](http://www4.jsc.nasa.gov/eaprojects/ea-projects/flightgfe/ams_02/html/ams_02.htm)_

## AMS-02 EA WEBSITE – JSC INTERNAL

**AMS-02 EA WEBSITE – JSC INTERNAL**

## AMS-02 EA WEBSITE – EXTERNAL

- A potential work-around for the Risk Management System would be to modify the AMS Risk Management Application link to point to an overview report that provides a status of the risks.
- Members of the AMS Project Team that do not have access to the Internal Website will submit RIDs using RID forms and they will be entered into the RID System for them.

**AMS-02 EA WEBSITE – EXTERNAL**

## AMS-02 EA WEBSITE – EXTERNAL