CONFIGURATION MANAGEMENT NAGEMENT - NASA · • Configuration Management Topics ... – Recording...

CONFIGURATION MANAGEMENT

ECS Release 6A Training

CONFIGURATION MANAGEMENT

ECS Release 6A Training1

625-CD-612-001

Overview of Lesson

• Introduction • Configuration Management Topics

– M&O role in CM activities – Configuration Control Boards (CCBs) – Configuration Change Request (CCR) Process – Software Change Process – Hardware Change Process – Baseline Change Process

• Practical Exercise

2 625-CD-612-001

Objectives

• Overall: Proficiency in ECS Configuration Management

– Describe M&O role in CM activities – List Configuration Control Boards (CCBs), roles, and

responsibilities – Process a Configuration Change Request (CCR) – Prepare a request for impact analysis – Process a software change – Review Configuration Parameters in Configuration

Registry – Process a hardware change – Process a baseline change Not currently fully supported

3 625-CD-612-001

Importance

Lesson provides preparation for several roles to ensure effective CM for implementation of system changes

• CM Administrators • System Engineers, System Test Engineers,

Maintenance Engineers

4 625-CD-612-001

M&O Role and CM Activities

• Maintenance and Operations CM activities – After acceptance of ECS – Administrative and technical support of change control – Documentation and coordination of changes to site

hardware, software, and procedures – Configuration identification

– Maintenance and control of technical documentation

– Configuration status accounting – Recording and reporting information about the configuration

status of ECS documentation, hardware, and software – XRP-II

– Configuration audits – M&O supports internal and ESDIS assessments of project

compliance with relevant CM plans 5

625-CD-612-001

Problem Management Change Adjudication Development, Deployment and Installation

M&O Role: Change Management

TT DB 2

Pr

NCR DB 5

CCR DB 14

p

DAAC Top 20

Patch CCR/ECO/DCN

Class I CCRs

Future Release CCRs

DM/CM Document Master DB

17

A

Approved Status

ECS Configuration Baseline DB

19

Content/Cost/Schedule Coordination

g

Trouble Ticket (TT) Submitters �� DAACs �� Help Desk

1

Submit TT DB 2

Status

TT Investigators

Assign 3

Status

Status Report

TT Tele-conference

�� TT Management - Assess Impact - Prioritize - Assign - Status/Report - Close

�� DAAC Top 20 - Request Updates - Status

4

Priority Assign Close

NCR DB 5

Initial Priority Forward

Submit

Status NCR Assignee

Sustaining Engineering

7

Assign6

DAAC Top 20 Status

NCR Prioritization Team

- Impact and program priority

8

DAAC Top 20

M&O CCB/IPT Chair 15

Priority Status

Sustaining Engineering20

Patch CCR/ECO/DCN

Sustaining Engineering Deployment IPT

�� Patch Content �� Cost/Schedule Estimates �� Track NCR Work-off and

Testing �� Patch Release CCR/ECO/

DCN �� Conducts PSRs

9 10

Priority

NCR Board Recommends

Closure

11

Verified NCRs

CCR DB 14

CCR Closure

Progress Reports

M&O CCB

�� Attends PSR �� Approves CCR/ECO/DCN �� Approves NCR Closing �� Monitors/Supports

Changes

13

Verified NCRs

CCR Submitters �� DAACs �� Sustaining Engineering

Requests for Perfective

Change CCRs

12

Data Management

Drawing ECOs/DCNs

16

DM/CM Document Master DB

17

Document/Drawing Masters

Changes Installed

(ECO Closed) Status

SMC/DAACs

18CCR Approval & Schedule

Approved Status

ECS Configuration Baseline DB

19

Changes Shipped

(Released) Status

Perfective Change Request

Perfective Change

Coordination

ESDIS CCB (SS PCMB)

21

Class I CCRs 22

Future Release CCRs

ECS Development Facility (EDF)/

Science Development (SCDV) CCB

Sustaining Engineering

- Create Changes/ Procure - Test Changes

23

CCR/ECO/DCN: - Patches - Install Instructions - Requirement/Design

Documents - Configuration Baseline

Changes - OPS Procedures

Test Plans and Procedures Test Report

Content/Cost/Schedule Coordination

6 625-CD-612-001

M&O Role: Science Software CM

• Science Software CM – developed at Science Computing Facilities – upon delivery to DAAC, enters custody

of DAAC CMO – SSI & T: DAAC management and I &T team – M&O role

• support during I & T • support DAAC Manager after acceptance • if Science Software has inter-DAAC dependencies, support

coordination with affected DAACs • ensure any necessary coordination with ESDIS prior to

moving Science Software into production operations

7 625-CD-612-001

System Operations Support

• SOS -- System Operations Support

– liaison between sites and ESDIS CCB – liaison between operations and the Sustaining

Engineering Organization (SEO) – coordination of CM functions – maintenance of Change Request Manager (DDTS) – oversight for dissemination of controlled items to sites – monitoring of installed configurations of hardware and

software for conformance to approved baselines – M&O ensures coordination and availability of needed

data for change management

8 625-CD-612-001

M&O Role: Maintenance of the M&O Libraries

• Maintenance of M&O Documentation and Software Library – both common and site-specific software – site personnel responsible for CM associated with

library

9 625-CD-612-001

M&O Role: Library Administration

• Soft or hard copy maintained in library • Document support directories

– CUSTOM/docs: file descriptive materials

– CUSTOM/docserver: document repository

• Microsoft Access database for library holdings and index

• Baseline Manager tool for documents that are under baseline CM control

10 625-CD-612-001

Baseline Control

• Baseline control milestones during maintenance and operations – Installation Plan (IP): COTS hardware configuration – Consent to Ship Review (CSR): hardware and software

configuration and plans for host sites – Release Readiness Review (RRR): documents state of

configuration items at each host site – Operational Readiness Review (ORR): documents flight

certified, ESDIS-approved, fully integrated EGS

• Site authority – ESDIS - authority over changes to common software – site CCB - authority over site-specific Class II changes – site-specific parameters for COTS software – specific configuration of tools and utilities, as delegated

by ESDIS 11 625-CD-612-001

Configuration Identification

• Establishes unique identifiers for ECS control items: Hardware, Software, Databases, Documentation

• ECS System Baseline Specification identifies Configuration Items (CIs) – Defines configuration baseline data structure and data

schema – Delineates how items will be named, described,

versioned, and controlled – Defines the item’s associated engineering specifications

and location of the actual controlled baseline data (including the ECS Configuration Baseline database)

• Configuration Baseline may change with a new System Release or with a patch

12 625-CD-612-001

Configuration Status Accounting

• Reports, metrics, records to support configuration management with status tracking information – identification and resolution of configuration problems

(e.g., Trouble Ticket, NCR listings, progress reports) – M&O CCB review/approval of baseline changes (e.g.,

CCR listings,progress reports, CCB agendas, minutes) – monitoring progress for change implementation (e.g.,

ECO/DCN status reports, IPT Drop Matrix listings) – maintenance of ECS Configuration Baseline status (e.g.

Approved/Shipped Changes, Installed Changes) – Verification and auditing of baselines (e.g. discrepancy

metrics/reports reflecting differences between the approved and installed baselines in both the testing environment in the Verification and Acceptance Test Center [VATC] or Performance Verification Center [PVC] and at the DAACs) 13

625-CD-612-001

Configuration Audits

• Conducted by ECS CMO, supported by site CM • Functional Configuration Audit (FCA) and

Physical Configuration Audit (PCA) validate that: – as built configuration compares with the approved

baseline – test results verify that each ECS product meets its

specified performance requirements to the extent determinable by testing

– the as-built configuration being shipped compares with the final configuration tested in the VATC

• Differences between the audited configuration and the final tested configuration are documented

• Automated scripts compare DAAC configurations to baseline documentation

14 625-CD-612-001

CCB Hierarchy

NASA Headquarters Earth Science Enterprise

Configuration Control Board (CCB)Mission Planning, CCRs, ECPs, and

Management of ECS Operations

ESDIS CCB

Science Systems Project Configuration Management Board

(PCMB)

Mission Systems Project Configuration Management Board

(PCMB)

CCRs, Impacts, DirectivesControl of ECS

Product Baseline

ECS CCB

M&O CCB, Release CCBs, FOS Segment CCB, and

EDF CCB

Site-Level CCBs Control Operational Baseline

DAAC CCB at each site

M&O provides services; ATO integrates and tests next release

until RRR acceptance

Controls Operational Baseline

SCF CCB Controls Science SW Baseline

Algorithm Development, Integration, and Test;

Scientific Investigations

EOC CCB Controls Operational Baseline



SMC CCB Controls Operational Baseline



Network/Scheduling/Services

ECPs, DRs, and Technical Direction

Feedback of all System Changes,

TTs, CCRs

Sustaining Engineering Changes to Common Baseline

System Acceptance

(RRR)

Technical Direction

EMOS Only

(CSR/RRR/ORR/ Approved Upgrades)

Science Only

System Enhancements

Level 1

Level 2

Level 3

Level 4

15 625-CD-612-001

CM Responsibilities

• ESDIS Management – establishes ECS CM policies

• CCBs – classify, prioritize, evaluate, recommend, and approve

(within their authority) changes to baselines

• CM Administrators (at SMC, EOC, DAACs, SCFs) – establish and maintain CM records – facilitate the configuration change request (CCR)

process – monitor and report status of proposed and approved

CM actions – support their respective CCB (as required)

16 625-CD-612-001

CM Responsibilities (continued)

• Sustaining Engineering Organization (SEO) -– assesses feasibility and cost, schedule and

performance impacts of proposed system-wide changes – implements such changes when directed by ESDIS

• DAAC Sustaining Engineers -– assess DAAC impacts of system-wide proposed

changes – develop and maintain ESDIS-approved DAAC-specific

modifications to ECS products

• Maintenance Engineers -– maintain ECS HW and report configuration changes

resulting from maintenance actions

17 625-CD-612-001

18

ECS CCB

ECS Development

CCBs

Potential changes, Change authorization

Impact assessments, Incorporation schedules, ORR baseline, Release baseline

ESDIS CCB

Mission Systems PCMB

Science Systems PCMB

ESDIS Project Office ECS System Items

Sc only

EMOS only

Potential changes, Change authorization, M&O baseline updates, Incorporation schedules

Impact assessments, Incorporation schedules, ORR Baseline Release baseline

DAAC CCB at each site

“CM” at

each SCF

SMC CCB

EOC CCB

Host Site CCBs

Deliver Science Algorithms

Operational CCB Relationships

Potential changes, Incorporation changes, M&O baseline update, Site extensions, Impact assessments

ORR baselines, EP baselines M&O baseline updates, Operational documentation, Potential changes, Technical direction, Science algorithms, SCF services

Coordination of system-level SW distribution and inventory; problem reporting, network management, and baseline management

Mission Operations configuration control of ECS FOS and external interfaces to EDOS, NISN, and ETS

FOS Segment

CCB

Release CCBs

M&O CCB

ECS Enhancement CCRs

Site Tailored Items

Coordination of science algorithms, SCF services, data production, archive, and distribution services as allowed by policy

625-CD-612-001

Science Software and Change Control

• Science Computing Facility (SCF) performs configuration control – Software and Databases to be executed at another site – SCF resources that are made available to EOSDIS

community • ECS M&O function directed by DAAC CCB

– Accepts science software and data from the SCF – Provides services to support EOC control of the EOC

operational baseline • Central coordination by Project Control Manage

ment Board – ECS integrity and quality of service – Coordination with internal and external networks,

systems, facilities – ESDIS CCB visibility into ECS operations – Convenient user administrative services 19

625-CD-612-001

Configuration Change Requests (CCRs)

• No undocumented changes – all requests for change documented using CCR form – CCR generated against the baseline affected by the

proposed change – Form can be completed electronically

• Word processing form • Change Request Manager tool (CM Administrator)

• CCB review – CCR submitted to appropriate CCB – CCR form may also be a cover sheet for a request to

CCB for a deviation or waiver from baseline

20 625-CD-612-001

ECS CCR Form

Earth Observing System Data and Information System (EOSDIS) Core System (ECS)

Configuration Change Request (CCR)

1. Configuration Change Board (CCB) ESDIS:___ CS:___ SMC:___ DAAC: GSFC___, LaRC ___, ASF___, EDC___, JPL___, NSIDC___, ORNL___ EOC:___

2. CCR No.

3. Submitted Date: 4. Revision 5. Priority Emergency Urgent Routine

6. Change Class 7. Status

8. CCR Title:

9. Originator: Org: e-mail: phone: 10. Approval:__________________________ _______________

signature date

11. Reason for Change

12. Description of Change

13. Impact Analysis: Cost: None Small Medium Large

Evaluation Engineer: Org: e-mail: phone: Impact Evaluators: ESDIS___; ECS Dev___; SEO___; SMC___; DAACs: GSFC___,

LaRC ___, ASF___, EDC___, JPL___, NSIDC___, ORNL___; EOC___; Others_______________________________________________

(indicate attachment ___)




(Not exceeding $100,000) ($100,000 to $500,000) (Over $500,000)

14. Comments: (Indicate Sites/ Organizations Affected)

15. Board Action: Approved Withdrawn Disapproved Deferred Until_____ date

Further Action Required: ECP Waiver Deviation Tech Direction Contract Mod. DCN Other:_______________________________________________

16. CCB Approval Chair:_______________ ________

signature date

17. CCR Implemented CM Admin. signature:_________ date:____

E

21 625-CD-612-001

Change Request Manager (DDTS)

22 625-CD-612-001

Request for Impact Analysis

• Support of ESDIS CCB may require assessment of the impact of a proposed CCR on local or system maintenance and operations

• Assessing the impact of CCRs with significant system implications and/or potential system-wide application may require the assistance of the ECS development organization

• Formal request for impact assessment according to Mission Operation Procedures for the ECS Project (611-CD-510-001)

• Impact assessments consolidated into a CCR Impact Summary

23 625-CD-612-001

CCR Impact Analysis Form

CCR Impact Analysis

Responder Request Number: ____ Responder:______________________ Responder Point of Contract:

address:____________________ ___________________________ phone:______________________ e-mail:______________________

CCB Schedule Date:_____________ CCR Number:___________________ CCR Log Date:___________________ CCR Originator:__________________ CCR Originator Point of Contract:

address:____________________ ___________________________ phone:______________________ e-mail:______________________

Evaluation Engineer: ______________ Evaluation Engineer Point of Contact:

address:___________________ __________________________ phone:_____________________ e-mail:_____________________

Requested Return Date:____________

Rough Order of Magnitude (ROM) Impact Analysis

Basis of Estimate:

Technical Assumptions and Comments:

Cost Impact: None [ ] Small [ ] < $100,000 Medium [ ] $100,000 < x < $500,000 Large [ ] > $500,000

Schedule Impact:

Technical Assessment: ( Your impact analysis should consider the implementation approach; interfaces affected; HW or SW changes required; documentation changes required -- change from/to pages; suggested alternatives, if any; and impact to security features. If your system is not impacted, please provide that information to the CM Administrator. )

Comments: Signed:__________________________

(Responder) Date:________________

24 625-CD-612-001

CCR Impact Summary

CCR Impact Summary

Evaluation Engineer: ______________ Evaluation Engineer Point of Contact:

address:____________________ ___________________________ phone:_____________________ e-mail:_____________________

CCR Board Date:_____________

Resources Summarized:

Technical Summary:

ROM Summary (BOE, Cost, and Schedule):

Recommendation:

Signed:__________________________ (Evaluator)

Date:________________ 25 625-CD-612-001

Software Baselines and Changes

• Software release is through ESDIS SMC or, with ESDIS permission, directly to the sites – Version Description Document (VDD) provides summary

documentation package – ECS Project CMO assembles and packages the delivery

• Change Scenarios – COTS software problem – custom software problem – science software upgrade – COTS software upgrade – system enhancement

26 625-CD-612-001

Transfer Functional Flow

ESDIS CCB

SEO CM Administrator

directs transfer of

SW Maintenance Change

Notify DAAC

MSS (SMC)

Invoke Baseline Manager

MSS (SMC)

Invoke Software

Distribution Manager

(SDM)

MSS (SMC)

Copies, transfers S/W from Library to

SDM

MSS (SMC)

Provides DAAC

Receiving Address

MSS (SMC)

Sends S/W Package to DAAC

MSS (DAAC)

Sends S/W Package to DAAC

Check Pkg MSS (DAAC)

Plan Installation

of Maintenance Change S/W

Software Transfer & Installation:

27625-CD-612-001

28

Installation Functional Flow

Sustaining Engineering--

S/W Maintainer

DAAC CCB

DAAC CM Administrator

directs installation of

SW Maintenance Change

Execute

MSS

Install with ECS

Assistant

Initiate

MSS

Makes/ Builds

S/W

Execute

MSS

Distributes

Perform

MSS

Tests

[failure]

Trouble Ticket Review Board

(TTRB)

Refer for problem resolution Resolution

Execute

MSS

Runs in operational

environment

Perform

MSS

Notifies TTRB of Results

Notify

DAAC CCB

DAAC CM Administrator updates the

Baseline Record and Inventory

Software Transfer & Installation:

625-CD-612-001

Software Transfer

• When software maintenance change package is ready and approved by ESDIS CCB, SEO CM Administrator requests SMC to distribute

• SMC CM Administrator promotes the change to the Operational Baseline and updates the Baseline Record and Inventory Record

29 625-CD-612-001

Software Change Installation

• Review/approval by ESDIS precedes systematic installation – VDD final updates for system and center-specific

material; final VDD is published – Installation of the build and operational and user

documentation IAW installation schedule • ECS Assistant for installation • Scripts for System Administrator to do installation

– Controlled document updates provided to SEO Document Maintenance and entered into CM

– CM system updated to reflect M&O and center-specific baselines

30 625-CD-612-001

Software Change Installation (Cont.)

• Implementation and test of software by DAAC Software Maintenance Engineer – Tests individual packages (unit, subsystem, system) – Runs full final software in operational environment – Notifies SMC of results

• DAAC CM Administrator updates site baseline record using Baseline Manager (BLM) tool – DAAC CCR Number – Software package identification – Package name – Software upgrade name – Version – File structure – Type – Installation date 31

625-CD-612-001

Configuration Parameters

• Default settings may or may not be optimal for local operations

• Changing parameter settings – May require coordination among Configuration

Management Administrator, Database Administrator, and Operations personnel

– Some parameters accessible on GUIs – Some parameters changed by editing configuration files – Some parameters stored in databases

• Configuration Registry (Release 5B, 2nd delivery) – Script loads values from configuration files – GUI for display and modification of parameters – Move (re-name) configuration files so ECS servers

obtain needed parameters from Registry Server when 32starting

625-CD-612-001

Configuration Registry

33 625-CD-612-001

Configuration Registry (Cont.)

34 625-CD-612-001

Hardware Baselines and Changes

• Hardware baseline established at Release Readiness Review (RRR) following formal Physical Configuration Audit (PCA) and Functional Configuration Audit (FCA) – ESDIS approves establishment of operations baseline – Configuration baseline recorded in Engineering Release

Record – M&O conducts testing of builds to ensure proper

implementation of CCRs with no defects introduced

• Change Scenarios – COTS hardware problem repair that requires a CCR – System enhancement

35 625-CD-612-001

Hardware Change Installation

• Repair with part of same make, model, version does not require CCR

• Change in make, model, version of a part to be used for repair, e.g., in an emergency, necessitates CCR to document the change – Review/approval by site CCB – Review by SEO/ESDIS for impacts/applicability to other

sites – Provision of controlled document updates to SEO

Document Maintenance and entry into CM – CM system updates to reflect change – Audits (FCA/PCA)

36 625-CD-612-001

Changes to the Baseline

• CM Tools for baseline changes – Change Request Manager: DDTS – Baseline Manager: XRP-II – Inventory/Logistical Manager: XRP-II

Incomplete: ine Database may not be deployed; Inventory Database for information only

Basel

• Related tools – From Management Subfunction software

• Trouble Ticket System (TTS) • Problem reporting and tracking • Used by users, operators, system administrators

37 625-CD-612-001

CCR Approval Flow

ECS CCB and Other CCBs

ESDIS CCB (PCMB)

Site CCB Site

Engineering Site

Operations

TT Telecon

Approved TT

1

Escalate TT?

2

CCR Proposed

3

CCR Telecon

4

Rew

ork

Status = PENDING

5Status =

PENDING

6Impact Assess

ment

7

8 Status = APPROVE

Status = APPROVE

Status = APPROVE

10

9 CCR Telecon

11

Schedule Implement

ation

12

TT Telecon

13 CCR

Implemented

14

M&O CCB

TT Telecon

Resolve TT/NCR

No

Yes

38 625-CD-612-001

Baseline Terms and Concepts

• Baseline Management is to identify and control baselined versions of hardware and software, and maintain a complete history of baseline changes

• Control Item is any ECS item under version control by CM

• Configuration Item (CI) is an aggregation of hardware, firmware, software, or any discrete component or portion, which satisfies an end user function and is designated for configuration control

• Baseline is a configuration identification document or set of such documents formally designated by the Government at a specific time in the life cycle of a CI

• Configured Article is a control item reportable as part of the Configured Articles List (CAL)

39 625-CD-612-001

Baseline Terms and Concepts (Cont.)

• ECS Structure and Baseline Terms – Assembly: an item made up of other items

• Parent: a higher-level item (e.g., an assembly) • Child: an item that is a component of a higher-level item

– Bill of Material: list of items that comprise an assembly – Product Structure: the parent-child pairings that define

the bill of material for an assembly; each product structure record specifies the effective dates and quantities for a single component of a parent for each engineering change

– Active Date: the date a component becomes effective in an assembly’s bill of material

– Inactive Date: the date a component is no longer effective in an assembly’s bill of material

40 625-CD-612-001

Baseline Terms and Concepts (Cont.)

• ECS Structure and Baseline Terms (Cont.) – Engineering Change: a mechanism for grouping,

reporting, and controlling product changes collectively – Revision: sequence number of a product structure

change to an assembly; signifies a change to the configuration of an assembly that does not alter its form, fit, or function

– Implementation Status: a record describing the deployment of a control item to a site and the current state and associated date of its implementation; each control item has one record for each site to which it is deployed

– Exporting Data: creating a formatted file or records extracted from the BLM database; control item engineering change, product structure, and interdependency records may be extracted and sent to another BLM site via ftp

– Importing Data: loading BLM data from a formatted file 41

625-CD-612-001

Product Structure - Design View

S ub system -1 ver: 2.0

C om p o nent - 1 ver: 2.0

C o m p o nent - n ver: 2.0

HW CI - 1 ver: 2.0

HW C I n ver: 2.0

SW C I 1 ver: 2.0

CS C 1 ver: 2.0

CS C - n ver: 2.0

SW C I - n ver: 2.0

Sub system 2 ver: 2.0

S ub system - 3 ver: 2.0

S ub system -4 ver: 2.0

EC S Pro d uct B a seline ver: 2.0

Configured Articles

42 625-CD-612-001

Product Structure - Operational (Network) View

S i te 1 O p e ra ti o n a l N e t w o r k B a s e l in e ve r : 2 . 0

S ite n F D D I N e t w o r k - 1 ve r: 2 .0

S it e n F D D I R in g 1 v e r : 2 . 0

H u b m o d e l: x x

F D D I C o n c e n t r a t o r m o d e l : x x

P r in te r m o d e l: x x

P l a tfo r m /P ro c e s s o r m o d e l : x x

R A I D m o d e l : x x

D is k D riv e - 1 m o d e l : x x

D is k D riv e - n m o d e l : x x

M o n i t o r m o d e l : x x

M e m C a rd m o d e l : x x

H a rd w a re B u n d le v e r : 2 . 0

P r o g ra m n ve r: 2 .0

D a t a b a s e n ve r: 2 .0

D a ta n ve r: 2 .0

C o n fig P a r a m s n ve r: 2 .0

I n s t a l la b le U n it 1 v e r: 2 . 0

P r o g r a m n v e r : 2 . 0

D a ta b a s e n v e r : 2 . 0

D a ta n v e r : 2 . 0

C o n fig P a ra m s n v e r : 2 . 0

In s ta ll a b le U n it n ve r : 2 . 0

P a c k a g e 1 (c u s t o m ) v e r : 2 . 0

P ro d u c t 1 ve r : n n

P ro d u c t n ve r : n n

P a c k a g e n (C O T S ) v e r :2 . 0

O S ve r : n n

O S P a tc h 1 ve r : n n

O S P a tc h n ve r : n n

O S P a tc h e s v e r: 2 .0

P ro g r a m P a tc h - 1

P ro g r a m P a tc h - n

P r o g ra m P a t c h e s v e r : 2 . 0

S o ft w a r e B u n d l e ve r: 2 .0

D is k P a rt itio n 1 v e r : 2 . 0

D is k P a r t it io n 2 ve r: 2 .0

F o rm - 1 ve r: 2 .0

F o rm - 2 ve r: 2 .0

C o n fi g u r a t io n D a ta ve r : 2 . 0

H o s t 1 v e r : 2 . 0

H o s t n ve r : 2 . 0

C o n fi g u r a t i o n D a t a ve r: 2 .0

S it e n F D D I R in g - n v e r : 2 . 0

F D D I S w it c h / R o u te r m o d e l : x x

C o n fi g u r a t i o n D a t a ve r: 2 .0

S it e - n F D D I N e t w o r k n ve r: 2 .0

S i te n H IP P I N e tw o r k v e r: 2 . 0

C o n fig u ra ti o n D a t a v e r : 2 . 0

S ite n N e tw o r k ve r : 2 . 0

S ite - n D o c u m e n t s ve r : 2 . 0

S i te n O p e ra t i o n a l N e t w o r k B a s e l in e ve r : 2 . 0

E C S O p e r a t i o n a l N e t w o r k B a s e li n e ve r: 2 .0

Configured Articles

43 625-CD-612-001

(Subsystem) View

S ite 1 O p e ra tio n a l S u b sys t e m B a s e lin e ve r: 2 . 0

S ite n S u b s y s te m 1 ve r: 2 . 0

H o s t 1 ve r: 2 .0

P la t fo rm / P ro c e s s o r m o d e l: xx

R A I D m o d e l: xx

D is k D riv e 1 m o d e l: xx

D is k D riv e n m o d e l: xx

M o n it o r m o d e l: xx

M e m C a rd m o d e l: xx

H a rd w a re B u n d le ve r: 2 . 0

P ro g ra m n ve r: 2 . 0

D a t a b a s e n ve r: 2 . 0

D a ta n ve r: 2 . 0

C o n fig P a ra m s - n ve r: 2 . 0

I n s ta lla b le U n it - 1 ve r: 2 . 0

P ro g ra m n ve r: 2 .0

D a t a b a s e n ve r: 2 .0

D a t a n ve r: 2 .0

C o n fig P a ra m s - n ve r: 2 .0

In s t a lla b le U n it - n ve r: 2 . 0

P a c k a g e - 1 (c u s t o m ) ve r: 2 . 0

P ro d u c t 1 ve r: n n

P ro d u c t n ve r: n n

P a c k a g e - n (C O T S ) ve r: 2 . 0

O S ve r: n n

O S P a tc h 1 ve r: n n

O S P a tc h n ve r: n n

O S P a tc h e s ve r: 2 . 0

P ro g ra m P a t c h - 1

P ro g ra m P a t c h - n

P ro g ra m P a tc h e s ve r: 2 . 0

S o ft w a re B u n d le ve r: 2 .0

D is k P a rt it io n - 1 ve r: 2 . 0

D is k P a rtit io n - 2 ve r: 2 . 0

Fo r m 1 ve r: 2 . 0

Fo r m 2 ve r: 2 . 0

C o n fig u ra t io n D a t a ve r: 2 . 0

H o s t n ve r: 2 . 0

P rin t e r m o d e l: xx

F D D I S w itc h / R o u te r m o d e l: x x

H u b m o d e l: xx

F D D I C o n c en t ra t or m o d e l: xx

S ite n S u b s y s te m n ve r: 2 . 0

S it e n D o c u m e n ts ve r: 2 . 0

S it e - n O p e ra t io n a l S u b s ys te m B a s e lin e ve r: 2 .0

E C S O p e ra t io n a l S yb s ys t e m B a s e lin e ve r: 2 . 0

Configured Articles

Product Structure - Operational

44625-CD-612-001

XRP-II Main Screen

45 625-CD-612-001

XRP-II Hierarchical Menu Structure

Baseline Management System Tools

Main

ILM Main Menu System Utilities MenuBaseline Management

Disk Partition Items Only

All Control Items Hardware Items OnlySoftware Items OnlyHost Items Only Document Items Only

Control Item Master

Engineering Change Entry Engineering Change Items Page

Engineering Change Approval Engineering Change Items Page

Bill of Material

Product Structure Manager Replace Component in Selected Bills

All Control Items QueryHardware Items QuerySoftware Items QueryHost Items QueryDocument Items QueryDisk Partition Items QueryProduct Structure QueryEngineering Change Query

Query Menu

Implementation Status Query

Unit of Measure Manager Unit of Measure Conversion Vendor Master Manager Control Item Interdependency Mgr

Vendor Address Maintenance Implementation Status Control Item Date Manager Low Level Code Manager

Utilities Menu

Responsible Organization Maintenance Item Class Manager Function Manager Clone Manager

MultiLevel Bill Reports Summarized Bill Reports MultiLevel Where Used Reports Configuration Item List - One Configuration Item List - Two Configured Articles Reports Version Description Reports Site Baseline Report Change History

Reports Menu

BOM Comparison Reports Hardware/Software/Patch Map Reports Software Baseline Reports Site - Host MapBaselined Documents Reports 46

625-CD-612-001

(Cont.)


Main

ILM Main Menu System Utilities MenuILM Main Menu

EIN Entry EIN Manager EIN Structure Manager EIN Inventory Query

EIN Menu

EIN Installation EIN Shipment EIN Transfer EIN Archive EIN Relocation Inventory Transaction Query

EIN Transactions

Order Point Parameters Manager Generate Order Point Recommendations Recommended Orders Manager Transfer Order Point Orders Consumable Inventory QuerySpares Inventory QueryTransfer Consumable & Spare Mat’l

Inventory Ordering Menu

Material Requisition Manager Material Requisition Master Purchase Order Entry Purchase Order Modification Purchase Order Print Purchase Order Status Receipt Confirmation Print Receipt Reports Purchase Order Processing Vendor Master Manager

PO/Receiving Menu

Work Order EntryWork Order Modification Preventative Maintenance Items Generate PM Orders Work Order Parts Replacement HistoryMaintenance Work Order Reports

Maintenance Codes Maintenance Contracts Authorized Employees

Maintenance Menu

Work Order Status Reports

ILM Inventory Reports EIN Structure Reports Install/Receipt Report EIN Shipment Reports

ILM Report Menu

Transaction History Reports PO Receipt Reports Open Purchase Order Reports Installation Summary Reports

Employee Manager Assembly Manager System Parameters Manager Inventory Location Manager Buyer Manager Hardware/Software Codes Status Code Manager Report Number Export Inventory Data

ILM Master Menu

DAAC Export Inventory Data OEM Part Numbers Shipment Number Manager Carriers ILM Import Records Sales/Purchase Terms Maintenance Reason Code Maintenance Site Codes for Scanned Data Scanned Data Process Scanned Data

License Entitlement Manager License Manager License Allocation Manager Maintenance Contracts Adjust License Quantities

License Menu


47625-CD-612-001

(Cont.)


Main

ILM Main Menu System Utilities MenuSystem Utilities Menu System Tools System Parameters Manager System Defaults Manager Note Code Maintenance Data Delete Utility Calendar Utility Calendar Report Transaction Log Transaction Archive Site Master Manager Machine Network Maintenance Commodity Code Maintenance Import BLM Records Export Release Records Export Site-Unique Change Records Export SMC Change Records

Screen Manager User Manager Groups Manager Screen Permission Control Menu Manager Printer Manager Data Dump Utility Data Load Utility Call Accell System


48625-CD-612-001

BLM Software Items Only CHUI

49 625-CD-612-001

BLM Engineering Change

50 625-CD-612-001

ILM EIN Entry & Manager Screens

51 625-CD-612-001

CONFIGURATION MANAGEMENT NAGEMENT - NASA · • Configuration Management Topics ... – Recording...

Documents

Transcript of CONFIGURATION MANAGEMENT NAGEMENT - NASA · • Configuration Management Topics ... – Recording...