UP Aerospace Inc. (2011) All Rights Reserved

SpaceLoft Payload Progress report (PPR)

[A] Payload Title: / [B] Payload Owner:
[C] NASA Payload Mission Manager
Name:
Organization:
Email:
Phone: / [D] Payload Mission Manager
Name:
Organization:
Email:
Phone:
[E] Mission Designation: SL-X / [F] Qualified for Flight Status: Pending PORR
[G] Weight:
Value: Units: Kg / [H] Date (Month / Day / Year):
[I] Balanced Weight:
Date:
Engineer:
QA: / [J] Vehicle Designation:
[K] Payload description
1) Payload Container Size (PTS10, PTS4, or Nosecone):
2) Description (what is it, how it works):
3) Objectives:
4) Deployables (Y/N) if yes describe:
5) Sensors (list active and passive sensors):
6) Structural Bounding Box (indicate L (cm), W (cm), H (cm) in schematic or picture):
7) Power:
Volts Amps
(Peak):
(average):
8) Mission success criteria:
[L] Payload access panel modifications description (PTS-10 only)
[M] Launch commit criteria
[n] Power on sequence steps
1.
2.
3.
[o] Pre-launch payload integration Required yes [ ] No [ ]
Description of tasks:
Time required:
[p] Launch scrub / recycle instructions
1) Pre Payload Activation:
2) Post Payload Activation:
[q] Special handling instructions
[r] Payload Inspection summary and environmental testing recommendations
Date:
Engineer:
QA:
[S] Payload environmental testing summary (optional)
Date:
Engineer:
QA:
[T] Payload Combined systems Test (CST) summary
Date:
Engineer:
QA:
[U] Post flight payload shipping instructions
[V] pOST FLIGHT PAYLOAD PROVIDER QUESTIONAIRE
Date:
1) Mission Success Statement:
2) Anomalies:
3) Lessons Learned as they relate to the payload integration and launch process:
4) Suggestions for future missions:

Payload Progress Report (PPR) Version 2.1 NASA Flight Opportunities Program

Appendix A: Document Instructions:

The Payload Progress Report (PPR) is a “living document” throughout the life cycle of the payload for a given launch. The PRR function is two-fold. First, the PPR provides information needed by the launch services provider and second ,acts as an active record of the payload integration process. The document is updated throughout the entire payload integration and launch process. If a section is intended to be left blank, indicate this by typing in that section the words NOT USED. Below are two sections. The first gives a description of the process steps involved for this document and who is responsible for each step. Second, a detailed description is provided for the intended information expectations of each of the block within this document.

Document Process Flow Steps:

The process for payload report is outlined in this section with specific steps.

Step 1(Payload Provider): The payload provider fills out the applicable sections of this form electronically and submits it electronically to UP Aerospace prior to the Payload Acceptance and Integration Review (PAIR).

Note: Any changes that the payload provider wishes to make in any of the sections can be emailed to UP Aerospace for incorporation into the official working copy of the document.

Step 2 (Launch Contractor): UP Aerospace reviews the document and discusses any details with the payload provider. Changes or clarifications are mode (if any) by UP Aerospace with the concurrence of the payload provider.

Step 3 (Launch Contractor): UP Aerospace fills in a summary of the payload inspection section [R ] and provides a copy to the payload provider and NASA mission management for review and decisions regarding optional environmental testing recommendations.

Step 4 (Payload Provider): Within 4 working days after launch the Payload Provider fills in the questionnaire in section [V] and provides the final copy to UP Aerospace for incorporation with the other payload reports into the NASA Post Flight Report.

Section Input Instructions:

Below is a description of information that is to be supplied in each of the boxes in the Payload Report form.

[A] The payload tittle is the name of the payload that can be used in discussion and meeting formats to uniquely identify your payload. Examples could be University of New Mexico, or TechSat-1, etc.

[B] The name of the organization who owns the payload. This can be the name of an individual, an educational institution, government organization or corporation.

[C] This is the contact information for the NASA Payload Mission Manager point of contact.

[D] This is the contact information for the Payload Mission Manager from the organization that is providing the payload.

[E] (Internal use) UP Aerospace fills in the launch vehicle mission number that this payload is scheduled to be launch on. For example a designation of SL-7, represents the flight is on a SpaceLoft vehicle flight number seven.

[F] (For internal use only) This section provides a status of the qualified payload. At the beginning of the payload integration process it is designated as “Pending PORR” (Payload Operational Readiness Review). After successfully passing the PORR the payload will be given the status of “Qualified for Flight”.

[G] The payload provider records the as weighed mass in Kg. This is the completed mass of the payload including the PTS container that is ready for shipment to UP Aerospace to begin the payload integration processing. If items are to be added to the experiment just prior to the launch please estimate this extra mass, include it in the value provided, and record the nature and amount of the additional mass as a note. The first step in the payload integration process at UP Aerospace is to verify the mass as received against the value recorded in this section.

[H] The payload provider records the date that the payload report was initially filled out.

[I] (Internal use) UP Aerospace records the weight of the payload and container after the balancing process is complete.

[J] (Internal use) UP Aerospace records the location of the payload within the vehicle. This is used for loading sequence and order on launch day for power on payload sequencing.

[K] This section contains a brief description of the payload.

1) The payload provider indicates which payload container size they are using for this mission. Indicate the payload container as either a PTS-10 (10 inch tall) or PTS-4 (4 inch tall) (PTS: Payload Transportation System).

2) A brief narrative of the payloads description and purpose

3) Provide the objectives of the payload system

4) Indicate the mission success criteria that will be used to evaluate the payload performance during the post flight quick look review period.

Note: If additional information such as schematics and photos are required provide them in an appendix providing a reference in this section.

[L] For PTS-10 customers only. Provided with each PTS-10 is a payload access panel that is mounted to the outer mold line of the vehicle. Customers are allowed to modify this panel to mount hardware or provide convenient power on access etc. If modifications are made to the panel the payload provider fills in this section with a brief description of the changes with a reference to a drawing of the changes provided in the appendix. See our Payload Users Guide for dimensions and description. If no changes are to be made to the access panel indict with the words NOT USED.

Note: the access panel with modification are to be shipped back to UP Aerospace with the payload for integration.

[M] The payload provider indicates any Launch Commit Criteria for the payload. The payload LCC are used in the Launch Operations Document countdown procedures. The following guidelines are to be used to determine the classification of each LCC.

Mandatory (M)

MANDATORY requirements are those that cannot be compromised. Violation of these requirements could severely impact mission success or safety. Violation of a MANDATORY requirement shall result in a launch scrub unless waived.

Waiver of a MANDATORY requirement shall be implemented only with full concurrence of the Spaceport Commander (SpaceCOM).

Required (R)

REQUIRED requirements are necessary for the achievement of primary test objectives or vehicle performance.

Waiver of a REQUIRED requirement may be done by the Launch Conductor, with the concurrence of the Launch Director and the Payload Provider if it is a payload LCC.

Desired (D)

DESIRED requirements are necessary for the achievement of secondary test objectives. The Launch Conductor has the authority, based on the recommendations of supporting teams, to waive these constraints and proceed with launch.

[N] Provide the payload power on sequence steps that will be used during the payload compatibility test and on day of launch. For each step indicate what the successful exit criterion (if any) is before proceeding with the next step.

[O] The section the payload provider describes any pre-launch payload integration activities that need to be completed prior to day of launch. Examples can include battery charging, chemicals added to the experiment. Provide a brief description of tasks to be completed and the amount of time needed.

Note: It is recommended that the payload provider exercise caution with the section of pre-launch integration tasks to prevent the possibility of Payload Operational Readiness Review (PORR) exit criteria violations. UP Aerospace will evaluate the payload provider’s pre-launch integration planned work in this section and make a determination of its risk as it relates to the PORR.

[P] In this section the payload provider will describe any re-work that must be done to the payload in the event that the launch is scrubbed. There are two possibilities;

1) The launch scrub occurs prior to payload activation or power up.

2) The launch scrub occurs after the payload has been activated or powered on.

For each, the payload provider should indicate the nature of the re-work and the amount of time required.

Note: All launch scrub and recycle re-work must be accomplished with the payloads inside the vehicle thru access port openings.

[Q] The payload provider indicates here any special handling of the payload. This can include special shipping instructions or ESD sensitive handling procedures. For particularly sensitive payloads the payload provider has the option to bring the payload directly to the UP Aerospace facilities for balancing and then “self-ship” the payload to the Schafer facilities for the remainder of the payload integration work. If this is the desire of the payload please indicate it here and provide a brief description of the shipping plan.

[R] (For internal use only) This section is filled in by UP Aerospace and Schafer Corporation at the completion of the payload inspection. The information contained here will summaries the inspection, list any re-work required, and provide recommendations (if any) for environmental testing required for the payload to be qualified for flight.

[S] (For internal use only)

[T] (For internal use only)

[U] Payload provider indicates the method of post flight shipping of the payload. Examples can include hand carry payload container to the Payload Provider at the launch site on the day of launch, or shipping via a commercial shipping carrier such as FedEx or UPS.

[V] Within 6 days of the launch, the Payload Provider is required to submit to UP Aerospace a brief statement in each of the 4 categories listed in this section. If more in-depth information such as data plots etc. are needed to convey a particular message the Payload Provider is encouraged to supply that information in an appendix to this document.

1) Mission Success Statement: provide a brief statement indicating if all or part of the mission objectives were satisfied referencing the information provided in section [K].

2) List any anomalies of the payload experiment noticed. This can range from a “failure” of a system or sub-system, partial failure or “anomaly”, or a “data item” which is generally something seen in the data and not expected.

3) Summarize a list of lessons learned from the payload as they relate to the launch and payload integration process.

4) Provide any suggestions for future missions that the launch services provider could implement to further enhance mission success.

Payload Progress Report (PPR) Version 2.1 NASA Flight Opportunities Program