Payload Programme Cycle

This chapter provides an overview of themany preparatory activities that have tobe completed by both the user and theAgency before the flight takes place.

Fig. 48 helps users to appreciate:• outer circle A: the major programme

phases that payloads genericallyundertake;

• circle B: a perspective of thecorresponding hardware developmentphases;

• circle C: the generic evolution of thescience objectives and aims;

• circle D: the Agency point-of-contactfor users to address their programmetechnical and programmatic issues and concerns.

The inner circles aresynchronised with the outer circle.

Fig. 48. Major payloadprogramme phases.

Payload Reviews andPlanning TemplateAs part of the programme cycle, anumber of reviews are planned in orderfor the Agency to determine payloadprogress and compliance with Columbuslaboratory requirements. These reviews are:

• Preliminary Design Review (PDR), todemonstrate the payload functionalrequirements and compatibility ofpreliminary design with the Columbuscarrier, ground physical and operationsenvironments, payload integrationschedule and initial payload data sets;

60

61

Flight PlanningThe first step in the programme cyclebegins with entering payload informationfor evaluation and possible inclusion intothe ESA-specific Partners Utilisation Plan(PUP). The information required ishighlighted in Fig. 50.

All the ISS Partners regularly develop andmaintain their PUPs for combination intothe Consolidated Operations andUtilisation Plan (COUP). This COUPprovides the ISS Operations andUtilisation Plan for the upcoming 5 yearsand includes the assignment of newpayloads for flight in a specific year.

The payloads addressed in this chapterare complete rack facilities or complexinstruments on an Express Pallet Adaptersize; these are sometimes known asClass 1 or Facility Class payloads. Payloads‘embedded’ in a facility (sometimesknown as Class 2 payloads) have specificprogramme requirements and capabilitiesthat are available directly from the facility-responsible developer. Their schedules areconsiderably shorter than for the Class 1payloads, as are the drawer-type payloadsto be accommodated in the EDR.

• Critical Design Review (CDR), todemonstrate the payload detaileddesign and compatibility with theColumbus Laboratory, and payloadcompatibility with the ground physicaland operations

• Preliminary Acceptance Review (PAR) todemonstrate the payload qualification/acceptance programme of the FlightModel (FM) and associated equipmentprior to shipment to ColumbusLaboratory compatibility testing;

• Final Acceptance Review (FAR) todemonstrate the completion of thequalification testing, the post-shipmentcheckout and the laboratory/payloadinterface compatibility verification;

• Safety Reviews (SRs) to demonstrate theprogressive reporting of all payloadhazard items, that their assessment andappropriate hazard controls have beenimplemented and hazard reports havebeen completed.

The Agency will provide support topayload users in the preparation ofmaterial for these reviews. The planningof these reviews and the major payloadactivities are shown in Fig. 49. Theindicated schedule is typical for majorcomplex payloads (Class 1 facility types).The major phases shown are detailedbelow.

Fig. 49. Genericpayload planningtemplate.

62

payload developer as part of its utilisationintegration responsibility.

This documentation is regularly updatedas the payload development proceedsand the payload assignment to a specificIncrement approaches. The updating isgenerally synchronised with the variouspayload development reviews, wherepayload developers can expect to providethe majority of the review inputs.

The ESA Utilisation Manager provides theAgency point-of-contact during thisstarting phase.

Around 30 months before the year forflight, further detailed payload inputsenable ESA planners to evaluate thepayload for a specific Increment withinthat year. An Increment is of about3 months duration and basically reflectsthe period between two consecutiveShuttle visits.

Once the payload has been assigned to aspecific Increment, then the ESA PayloadAccommodation Manager (PAM) becomesthe Agency point-of-contact and analyticalintegration can start. The PAM isresponsible for the total Incrementpayload complement from this point onuntil the successful on-orbit activation ofthe payload has been accomplished.

Fig. 50. Overview ofpayload information

requirements.

Once ESA has accepted a payload into itsPUP, the Agency then prepares thePayload Interface Agreement (PIA) foragreement with the payload developer.The PIA and its Addendum detail theprogrammatic requirements, includingroles and responsibilities as well asschedules and commitments for specificflights and on-orbit needs. Followingsignature of that agreement, the Agencyinitiates payload interface controldocumentation development. The majoritems of this documentation include:

• Interface Control Document (ICD),which provides the controlleddescription of all the interfaces betweenthe Station element and the payload.

• Payload Verification Plan (PVP), whichprovides the controlled description ofthe ICD verification requirements andtheir traceability. For every ICDdeveloped, there will be acorresponding PVP to be developed;

• Payload Data Set (PDS) records, whichprovide the controlled description ofthose data needed to integrate apayload into the physical andoperational environment of the Station.

The Agency will undertake the developmentof this documentation together with the

63

During this step, the payloaddevelopment model philosophy isestablished to ensure that adequatepayload models are developed to supportflight qualification, crew training and in-flight ground control operations.

The necessary tools required to supporttraining will be consolidated atLaboratory level for a specific planningperiod. These tools, including traininghardware and software as well as hi-fidelity simulators, will support the trainingactivities, for both flight and groundcrews, that begin during this step andcontinue through the programme cycle.

Analytical IntegrationThe second step in the programme cyclebegins with a provisional manifesting of apayload for inclusion in an Increment’spayload complement in the ColumbusLaboratory or on its externalaccommodation site.

Each payload is analysed in sufficientdetail to ensure individual payloadcompatibility with other ColumbusLaboratory payloads as well as with theColumbus Laboratory systems.

The analytical integration is shown inFig. 51. The Agency undertakes theanalytical integration function as part ofits utilisation integration responsibility.Should incompatibilities be establishedduring this process, then the Agency willrequire the payload user to develop andestablish a solution that ensurescompatibility.

Physical CheckoutThe third step in the programme cyclestarts off with the user completingpayload development. That means, forexample, that the payload checkout hasbeen completed in readiness forColumbus Laboratory compatibilityverification.

The compatibility verification isaccomplished through the Rack Level TestFacility (RLTF) for rack payloads or, forexternal payloads, through the SuitcaseTest Equipment (STEP) capability.

Fig. 51. Analyticalpayload integrationprocess.

The RLTF is an integration and testenvironment that provides a high-fidelityemulation of the resource interfacesbetween an ISPR and the ColumbusLaboratory. This capability provides theopportunity for payload developers tocomplete payload verification andacceptance. The STEP provides anequivalent capability for externalpayloads.

The Agency leads the physical checkoutfunction as part of its utilisationintegration responsibility. The payloaduser is expected to support this activityand ensure that the payload is workingaccording to the agreed baseline.

Following the successful completion ofverification and acceptance activities, thePayload Accommodation Manager (PAM)accepts and certifies the payload for flightreadiness, and subsequently delivers thequalified payload to the launchintegration process.

Launch IntegrationThe fourth step in the programme cyclebegins with the delivery of the qualifiedpayload to the launch integrator by thePAM.

For the Columbus Laboratory launchcomplement, the Columbus Primecontractor represents the launch integratorand performs the actual integration of thepayload racks into the laboratory. Thelaunch complement payloads will betested in their on-orbit locations to verifypower-up and checkout. This is followedby a short mission sequence test to verify

simultaneous payload operations. Aftercompletion of all tests, the Columbuslaboratory is then delivered to the SpaceShuttle launch site for Orbiter integrationand launch.

For post-Columbus Laboratory launchpayload racks, as well as for all ColumbusLaboratory launch complement mid-deckstowage items and external payloads, thelaunch integrator is represented by theNASA Payload Mission Integrator (PMI)team. The PMI team will receive thepayload items from the PAM at the Shuttlelaunch site. The PMI will integrate theMid-Deck Lockers and payload supplyitems into the Mini Pressurised LogisticsModule (MPLM) or on to theunpressurised payload cargo carrier.

On-Orbit OperationsThe fifth step in the programme cyclebegins with the arrival of the payload atthe ISS, where it is transferred into itsColumbus Laboratory on-orbit location.After physical integration, a short activationcheckout is then performed to verify payloadreadiness for on-orbit user operations.

Up until the successful accomplishment ofpayload activation, the PAM is the user’sprimary point of contact with the ISSprogramme. After successful payloadactivation, the Payload Operations Managerbecomes the European point of contact.

On-orbit operations cover a wide varietyof aspects and include nominaloperations to accomplish the payload’smission objectives as well as any nominalservicing and maintenance that may be

64

history of electronic data products, to thepayload user. The payload users areexpected to make a detailed examinationof their equipment and data, andsubsequently prepare both their ‘lessonslearned’ and scientific results. The ‘lessonslearned’ will be consolidated at ColumbusLaboratory level with the goal ofidentifying whether system issues need tobe addressed in pursuit of improvingpayload control and support functions.

This last activity of payload return marksthe end of the payload’s utilisation forthat campaign.

SafetyThe role of safety and product assuranceis continuously active from the beginningthrough to the completion of a payload’sengagement in the ISS programme. Allground and flight segment equipmentand operations are regularly assessed forhazardous situations that could endangerthe crew, other payloads, ground team,etc. Regular safety reviews are organisedwithin the programme cycle, when all thehazards and hazard controls areaddressed. The successful completion ofthese reviews plays a very significant rolein the eventual certification of flightreadiness for a payload.

Smaller PayloadsEssentially the same kind of steps willhave to be followed by smaller Class 2payloads but in a simplified andshortened schedule. It is the objective ofthe Programme to offer rapid access forless small and complex payloads.

needed to ensure the continued well-being of the payload’s equipment. Thepayload users, located at their local USOCor UHB, will be able to monitor andinteractively control their experimentoperations based upon the data receivedthrough the ground communications.

At the completion of the payload’s on-orbit operations, it is shut down andtransferred from the ISS to the returningShuttle. All mission samples andspecimens are transferred to Shuttle mid-deck or MPLM stowage for return toEarth, or to the ATV for controlleddestructive reentry.

Landing De-IntegrationThe sixth step in the programme cyclebegins with the delivery of the payload tothe point-of-contact by the NASA PMIafter de-integration from the Shuttleand/or MPLM.

The point-of-contact performs a localcheckout of the payload and follows thisup with the transportation preparationand shipment of all payload items to thepayload developer site.

In parallel with these transportationactivities, the User Support andOperations Center (USOC) provides acomplete history of all the payload’stelemetry/telecommanding history to thepayload user in an electronic form.

Payload ReturnThe last step in the programme cyclebegins with the delivery of the payloadequipment, including the complete

65