2. Work Breakdown Structure
2.1 Developing Organizations
The responsibilities of various organizations
involved in Payload implementation are shown in Figure 24.
Figure 24. Organizational responsibilities for S-U Payload implementation.
JPL has the overall responsibility
for managing development and integration of the Payload. JPL
also has the responsibility for developing the Canister, the Canister
Mechanisms, and the Collector Arrays. Los Alamos National Laboratory
(LANL) has the responsibility to develop the Concentrator and
the Monitors. Johnson Space Center (JSC) has the responsibility
for providing overall guidance on contamination control. JSC
will provide facilities and combine with JPL to implement final
clean assembly of the flight Canister prior to shipping to Lockheed
Martin Astronautics (LMA) for integration with the spacecraft,
and for disassembly of the recovered Payload.
The JPL activity will be carried out
by the Mechanical Engineering Section of the Mechanical Systems
Engineering and Research Division, which is the same organization
that has implemented many flight hardware systems including Cassini,
Galileo, Voyager and many flight instruments.
The solar wind Monitors and Concentrator
are being developed by the Space and Atmospheric Sciences Group
at the Los Alamos National Laboratory (LANL), with collaboration
from scientists at JPL, Caltech, and the Southwest Research Institute
(SWRI). This Space Plasma Team has been developing, operating,
and analyzing data from space plasma instruments for over 30 years
and has developed over 50 space plasma Monitoring instruments
for various agencies.
The S-U cleanliness requirements are
equally stringent before launch and after recovery of solar wind
samples. JSC, the designated NASA Center for curation of extraterrestrial
materials, was selected to partner with JPL for final cleaning
and assembly, and eventual disassembly of the Payload. The facilities
developed under the S-U Program will remain as a national resource
for future sample return missions.
2.2 Work Breakdown Structure (WBS)
The product-oriented WBS for the Payload
is shown to level 4 in Figure 25. There are six major elements
of the Payload WBS. Management and System Engineering (41000),
residing at JPL, is provided to assure that requirements, plans,
reviews and overall cognizance of the work is administered through
one office. Nevertheless, development of the Payload is being
carried out by a partnership, and each participating institution
will carry out its assigned responsibilities according to its
own institutional policies and procedures. JPL Payload elements
(42000) include all the activities necessary to develop the Canister,
collector arrays and mechanisms. The LANL Payload elements (43000)
include a small management effort plus development of the Concentrator
and Monitors. Payload integration and test (44000) is accomplished
by JPL. WBS element (45000) is provided for auxiliary handling
and support equipment, ground support equipment, and shipping.
Final cleaning and assembly of the flight Canister will be done
at JSC by a combined partnership of JPL and JSC (46000).
A more detailed WBS and a WBS Dictionary are provided at the end of Part 7 of the PIP.
Figure 25. Payload Work Breakdown
Structure
| Can Cover | ||||
| Array Latch Mechanism, Cover side (new) | ||||
| Array Assy, Fixed | ||||
| Canister | ||||
| Canister Seal Assembly | incl | |||
| Fixed Saddle | ||||
| Array Latch Mechanism, Can side (new) | ||||
| Array Assy, 4 deployables Total | ||||
| Array Deployment Mechanism | ||||
| Cover Mechanism incl linkage | ||||
| Locking Ring | ||||
| Locking Ring drive mechanism | ||||
| Connector Brackets | ||||
| Cabling & connectors | ||||
| Array Deploy Mech Drive Electronics (new) | ||||
| Concentrator | ||||
| Concentrator HVPS | not incl | |||
| Estimated Canister Mass Total (kg) | ||||
| Canister Mass Allocation (kg) | ||||
| Canister Mass Margin (%) | ||||
| Ion Monitor | ||||
| Electron Monitor | ||||
| Estimated Monitors Mass Total (kg) | ||||
| Monitors Mass Allocation (kg) | not avail | |||
| Monitors Mass Margin (%) | ||||
| Payload Total Mass Estimate | ||||
| Payload Mass Allocation (kg) | not avail | |||
| Payload Mass Margin (%) |
Another constraint of significance for the Science
Canister Assembly is the overall volume or envelope. The SRC
has a limited size and therefore limited internal volume due to
the physical limits imposed by both launch and reentry. Therefore,
a significant amount of effort was expended during Phase A to
understand the volume of the Canister and how it fits within the
SRC. Preliminary Interface Control Drawings have been generated,
first in Vellum software with dimensions and later in SDRC
Master Series to be compatible with the design database used
at LMA. The Payload model generated at JPL was then "plugged
in" to the LMA database to verify compatibility of the Canister
design.
4.2 Master Payload Schedule
The Payload schedule is dictated by the need to conform
to the overall LMA Spacecraft and Sample Return Capsule development
schedule as described in the colored fold-out sheet in this Plan.
The four key deliveries to LMA for the Payload in the S/C and
SRC schedule are:
Receive Payload Mass Simulator Wed 5/8/96
Receive JPL Payload STM Fri 4/18/97
Receive P/L Engineering Model Mon 6/2/97
Receive P/L Flight Hardware Tue 11/10/98
A detailed schedule for development of the Canister
is shown in Figure 30 (not available on web). This schedule shows all major deliveries
between the various participating organizations. This schedule
is arranged in time sequence, with the flow of effort defined
by Phase, rather than by work element. A rearranged schedule
is shown in Figure 31 (not available on web) in which the tasks are arranged by work
element (i.e. Arrays, Mechanisms, etc.). A network view of Figure
31 is given in Figure 32 (not available on web).
Phase B is a 9 month effort from January through
September 1996. The Payload mass simulator is delivered to LMA
midway through Phase B. The Payload Preliminary Design Review
takes place 9/20/96, ten days after the project PDR, which occurs
on 9/10/96.
Phase C/D starts at the beginning of the fiscal year
in September 1996. The first part of Phase C/D is devoted to developing
the Payload engineering models. The two engineering model deliveries
in April and June 1997 represent the major effort in the first
part of this phase. The Payload Critical Design Review occurs
on 9/8/97, a week before the system CDR on 9/15/97. After the
CDR, work begins on the flight hardware.
The schedule for development of the Concentrator
is given in Figure 33 (not available on web). The schedules for development of the Monitors
and the Ground Support by LANL are given in Figures 34 and 35 (not available on web).
4.3 Receivable and Deliverable List4.3 Receivable and Deliverable List
Table 3 shows the Suess Urey level REC/DEL list.
This list has been agreed to by all team members and provides
the framework for exchange of critical hardware and data between
institutions. We have incorporated the REC/DEL approach into
our WBS level schedule construction. This REC/DEL list starts
with ICD agreements in Phase B, progresses to development model
deliveries, and finally flight unit deliveries in Phase C/D.
The MS Project network schedules, provide a notes feature that
can be attached to any activity or milestone. This provides the
Payload Team with a convenient tool for use in tracking the progress
of all inputs and outputs of a given task. By incorporating the
data into an existing tool, we keep the process simple. These
REC/DEL data can be published in tables by date, or WBS and made
available to the Payload participants via a collaborative server.
Table 3. List of critical deliverables and receivables
for the S-U Payload.
| Canister ICD input info | JPL | LMA | Fri | 2/2/96 |
| Concentrator/HVPS ICD info | LANL | JPL | Fri | 2/2/96 |
| Monitors ICD input info | LANL | LMA | Fri | 2/2/96 |
| Concentrator/HVPS ICD Prelim | LANL | JPL | Thu | 2/29/96 |
| Monitors ICD - Prelim | LANL | LMA | Thu | 2/29/96 |
| Canister ICD Prelim | LMA | JPL | Thu | 2/29/96 |
| Concentrator HVPS Elec Parts List | LANL | JPL | Fri | 3/15/96 |
| Monitors Elec Parts List | LANL | JPL | Fri | 3/15/96 |
| Collector Array ICD Final | JPL | CIT | Mon | 3/25/96 |
| Concentrator & HVPS Mtls List | LANL | JPL | Mon | 4/15/96 |
| Concentrator/PS ICD Final | LANL | JPL | Fri | 4/19/96 |
| Monitors Mtls List | LANL | JPL | Thu | 5/2/96 |
| Monitors ICD Final | LANL | LMA | Mon | 5/6/96 |
| Canister ICD Final | LMA | JPL | Mon | 5/6/96 |
| Canister Mtls List | JPL | JSC | Fri | 5/17/96 |
| 6 Canister/SRC I/F Trunnion Assys | LMA | JPL | Fri | 5/17/96 |
| 200 Test Collector Wafers | CIT | JPL | Fri | 3/8/96 |
| 50 Test Collector Wafers | CIT | JSC | Fri | 3/8/96 |
| Concentrator HV Feedthru Connectors | JPL | LANL | Thu | 11/7/96 |
| Mating HV Feedthru Connectors | LANL | LMA | Thu | 11/7/96 |
| Mating Monitors Connectors | LANL | LMA | Thu | 11/7/96 |
| 1200 EM Collector Wafers | CIT | JPL | Fri | 11/22/96 |
| Deliver EM Collector Array Assy | JPL | JSC | Wed | 1/22/97 |
| LANL Delivers EM Concentrator | LANL | JPL | Wed | 1/22/97 |
| EM Canister to LMA | JPL | LMA | Wed | 6/4/97 |
| Deliver Canister Eng Model (002) | LMA | JPL | Fri | 11/14/97 |
| Deliver Canister Eng Model (002) | JPL | JSC | Wed | 1/7/98 |
| Collector wafers, Flight Units (500) | JPL | JSC | Tues | 3/17/98 |
| Concentrator & HVPS, Flight Models | JPL | LANL | Thu | 4/16/98 |
| Concentrator & HVPS, Flight Models | LANL | JSC | Wed | 6/17/98 |
| Return Canister Eng Model (002) | JSC | JPL | Wed | 6/17/98 |
| 500 flt test Collector wafers | CIT | JPL | Mon | 9/29/97 |
| 500 flt Collector wafers | CIT | JPL | Wed | 1/7/98 |
| Return Canister Str/Ther Model (001) | LMA | JPL | Fri | 8/8/97 |
| 6 Canister/SRC I/F Trunnion Assys | LMA | JPL | Fri | 1/16/98 |
| Deliver Flt Concentrator | LANL | JPL | Tue | 2/10/98 |
| Deliver 7 Flt Array Frames | JPL | JSC | Fri | 3/13/98 |
| Deliver Flt Canister Assy | JPL | JSC | Tue | 6/9/98 |
| Return Canister EM to JPL (002) | JSC | JPL | Wed | 9/2/98 |
| Deliver Flt Model Canister to LMA | JSC | LMA | Fri | 11/10/98 |
4.4 Schedule Reserve4.4 Schedule Reserve
Schedule slack is provided in the
Payload schedule as shown in Table 4.
Table 4. Slack periods in Payload
development. (Slack periods bridge the gap between "from"
and "to" columns).
| Completion of the Canister STM | Delivery of this STM to LMA | 6 weeks |
| Completion of Canister EM testing | Delivery to LMA | 11 weeks |
| Completion of Flight Canister post-clean assembly and test | Delivery to LMA for integration with the SRC | 13 weeks |
| Completion of the Flight Concentrator | Delivery to JPL for integration with the Canister | 8 weeks |
| Completion of coating the Flight Concentrator | Delivery to JPL for integration with the Canister | 4 weeks |
| Completion of the Flight Monitors | Delivery to LMA | 12 weeks |
| Reintegration of the Flight Monitors | Final acceptance on the LMA Spacecraft | 14 weeks |
These slack periods were provided to allow for unforeseen occurrences in development of the various elements of the Payload. Of great importance to schedule risk mitigation is the 13 weeks of slack allocated between the end of the scheduled environmental qualification testing of the Canister Assembly at JSC, and delivery to LMA. This time is allocated to allow for the possibility that problems may occur during testing, and rework/retest may then be required. Additionally, six weeks of slack is provided prior to delivery of the Canister STM unit to LMA. Schedule risk for inter-partner activities is thereby reduced by the incorporation of slack in the JPL schedule.
The slack incorporated in this schedule is fully funded in our cost estimates. In other words, the cost estimate has been compiled with the assumption that the slack time is fully staffed by the workforce rate at the beginning of the slack duration.
4.5 Schedule Management
The S-U project will utilize earned value schedule variance information generated monthly by the Microframe Project Manager (MPM) software to detect, identify, and determine the magnitude of Project schedule problems. Schedule variance will be calculated monthly at the Work Element level (one level below the Cost Account) with rollups to the Cost Account and all higher WBS levels. Since the same person at JPL acts as Financial Administration Assistant for the Project and for the Payload, the Payload Team Leader will derive information on Payload issues through this process.
Another main tool for S-U Project schedule management will be the top-level task network, which contains all of the Payload's major milestones, and all of the Receivable/ Deliverable (REC/DEL) tasks across team boundaries. Once the schedule baseline is set within this network, all changes thereto must be negotiated with and approved by the Payload Team Leader. Critical Path Method (CPM) analysis of all networks will be used to evaluate schedule options when necessary. The Payload Team Leader will use CPM in a "Slack Table" as a periodic metric for slack trend analysis purposes. The Slack Table contains key milestone information showing previous period's slack, current period's slack, original task duration, remaining task duration, and a quotient which measures the relative diminution of the remaining slack versus the remaining task duration. In addition, "Milestone Trend Charts" showing cumulative milestone completions planned versus accomplished will be utilized as a periodic metric. These tools will provide continuous information on the degree to which the schedule is being met, and the amount of slack remaining to deal with future problems.
The combination of successively more realistic engineering
models, together with the provision of schedule slack at critical
junctures in development, provides the Payload Team leader with
the assurance that the development program is on track, and the
flexibility to absorb unavoidable delays during the development
program. The resource-loaded MS Project Scheduling Tool will
provide a "pulse" of the state of the Payload development
process which can be compared with the estimated progress for
the known expenditures at any point. This invaluable tool will
be used routinely, for the schedule (like any variable) cannot
be controlled if its position cannot be sensed accurately.
ON TO SECTION 5