DRAFT #18 we#18:ccpolse

13 Jul 93

DEPARTMENT OF THE AIR FORCE SMC REGULATION 800-XX

Headquarters Space and Missile Systems Center (AFMC)

Los Angeles Air Force Base, California 90009-2960 July 1993

Acquisition Management

SPACE SYSTEMS ENGINEERING

1. For the purposes of this Commander's Policy, the following definitions apply:

a. Systems Engineering (per MIL-STD-499B (Draft)): "An interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and life-cycle balanced set of system product and process solutions that satisfy customer needs. Systems engineering encompasses: (a) the development, manufacturing, verification, deployment, operations, support, disposal of, and user training for, system products and processes, (b) the management of the system configuration, (c) the translation of system definitions into work breakdown structures, and (d) information for management decision making."

b. SMC System: For SMC programs, the system is defined to include the entire mission of SMC as a total, integrated system. The three major elements of the SMC System include space systems (satellites, sensors, and user equipment), launch systems (including upper stages), and ground systems (operator and user). Each individual program (DSP, GPS, DMSP, Titan IV, ARTS, etc) is a key part of the whole system. Key elements of SMC systems engineering include multi-program projects (e.g., projects beneficial to more than one program), standardization opportunities, interoperability opportunities, and design options to be used in satisfying future customer requirements.

2. An SMC Systems Engineering Process shall be developed and implemented. The process shall ensure implementation of MIL-STD-499B systems engineering for the entire SMC "system" across all SMC acquisition and support activities. The process shall also include formal mechanisms to identify and implement space systems engineering across multi-program projects to include: tailoring guidelines, standardization opportunities, interoperability opportunities, and pro-active design options for all SMC programs whenever proven to be cost effective. The continuum of systems engineering opportunities includes processes, specifications, environments, interfaces, subsystems, a standard bus, and a "system of systems" throughout all phases of the acquisition cycle.

3. Responsibilities:

a. The SMC Chief Engineer (EN) shall develop detailed procedures to implement and manage the SMC space systems engineering process throughout all phases of the acquisition cycle. The SMC Chief Engineer shall document the processes, definitions, roles, responsibilities, and detailed procedures in SMC Pamphlet 800-XX (TBD).

b. The SMC Commander (SMC/CC) and the Air Force Program Executive Officer for Space (AFPEO/SP) herein charter three Integrated Product Teams (IPTs), one each for Space, Launch, and Ground Systems. These IPTs are charged with implementing this policy in each of their respective areas. The Government Chairpersons of the Space, Launch, and Ground Systems IPTs shall be the SMC Chief Engineer (SMC/EN), the System Program Director of Launch Programs Program Office (CL), and the System Program Director Satellite Control and Data Handling Systems Program Office (CW), respectively. The Aerospace Corporation shall appoint an appropriate management level Co-Chairperson to each IPT. All SMC System Program Directors are responsible for appointing members to serve on the IPTs. A representative from the Directorate of Developmental Planning (XR) shall participate in the three IPTs and be responsible for SMC Vision/Roadmaps. The Systems Engineering Division (SDE) and Directorate of Acquisition Logistics (AL) shall also participate in the IPTs by providing systems engineering and acquisition logistics expertise and guidance. Figures 1 through 4 describe the organizational relationships of the IPTs described above.

c. The SMC Chief Engineers' Council is chartered by the SMC Senior Leadership Council (SLC) to integrate technical activities across the space, launch, and ground systems IPTs. The Council also acts as the SMC Center Technology Council (CTC). The Council is led by the SMC Chief Engineer (SMC/EN) and The Aerospace Corporation Chief Engineer. The Council consists of Chief Engineer representatives of all Systems Program Directors, including their Aerospace Corporation counterparts, AFSPACECOM liaison representatives, and representatives from XR, SD, and AL.

d. The Aerospace Corporation, as an integral part of the SMC systems engineering team, is responsible for all systems engineering activities in accordance with SMC Regulation 800-8, "The Aerospace Corporation Technical Support." The Aerospace Corporation shall be pro-active in such activities as co-chairing and supporting the IPTs, supporting across-program systems engineering, accomplishing program systems engineering, implementing space systems engineering projects, identifying standardization and interoperability opportunities, identifying common problems/solutions, accomplishing trade-off analyses and implementation efforts, providing preliminary design options for future space systems requirements, developing systems engineering tools which have application across all SMC programs, and integrating all technical activities at SMC.

e. SMC Systems Program Directors shall support all systems engineering activities by complying with the requirements of MIL-STD-499B tailored to individual program requirements as well as by examining their programs for standardization and interoperability opportunities, identifying common problems/solutions, communicating those opportunities, problems and solutions to EN, and implementing cost effective, SMC-wide solutions.

f. EN, SD, XR and the SPOs shall work closely with our users and customers to involve them in the systems engineering process in the development of requirements.

EDWARD P. BARRY, JR.

Lieutenant General, USAF

Commander

DRAFT #18

13 Jul 93

DRAFT # 4

26 Apr 93

SMC PAMPHLET 800-XX

Space and Missile Systems

Systems Engineering

TABLE OF CONTENTS

I. PURPOSE

II. DEFINITIONS

A. SMC SYSTEM

B. SYSTEMS ENGINEERING PROCESS

C. CTC ORGANIZATION

D. IPT ORGANIZATIONS

E. SYSTEMS ENGINEERING (PER MIL-STD-499B)

III. ROLES AND RESPONSIBILITIES

A. SMC/CC

B. AFPEO/SP

C. SMC CHIEF ENGINEER'S OFFICE

D. IPT CHAIRPERSONS

E. CENTER TECHNOLOGY COUNCIL

F. SYSTEM PROGRAM DIRECTORS

F. AEROSPACE CORPORATION

G. AFSPACECOM

H. SYS ENGINEERING ORGANIZATIONS IN SINGLE OR BASKET SPOs

I. IPT MEMBERS

1. XR ON IPTs

2. SDE ON IPTs

3. SPACE SYSTEMS IPT

4. LAUNCH SYSTEMS IPT

5. GROUND SYSTEMS IPT

IV. PROCESSES AND PROCEDURES

A. MIL-STD-499B FOR SINGLE PROGRAMS

B. MIL-STD-499B FOR SMC SYSTEM

C. SYSTEMS ENGINEERING PROCESS FLOW

D. SMC SPACE SYSTEMS ENGINEERING PROCESS FLOW

E. WORKING PROCEDURES OF THE THREE IPTs

1. COLLECTION AND EVALUATION OF IDEAS

2. DECISIONS WITHIN SINGLE IPT AREA

F. COMBINING TWO OR THREE IPTs

1. EVALUATION PROCESS

2. DECISION MAKING PROCESS

G. DECISION MAKING/ISSUE RESOLUTION PROCESSES

H. CUSTOMER BUY-IN PROCESS

1. INTERFACING WITH CUSTOMERS

2. REQUIREMENTS EVALUATION/OPTIONS

I. METRICS

1. MEASURES OF SUCCESSFUL IMPLEMENTATION OF SE PROCESS

a. PROCESS PARTICIPATION

b. PROJECTS

c. IMPLEMENTATION OF NEW IDEAS

DRAFT # 4

26 Apr 93