ESA ODFCB#4 Minutes, Rev1

Mar04

Minutes ODFCB # 4 (ESA Columbus System ODF)

3-5 March 2004 at ESTEC, Rev 1

See Annex A below for list of participants.

See separate web page for all attachments.

Welcome and Meeting Objectives presented by M.Wolff (attachment 1a and 1b)

  • To get a better understanding of overall current ESA SODF product status including development and validation.
  • Discuss configuration control processes and associated facilities, such as ESA ODF repository and basic CR System.

Membership list: (attachment 2, updated)

  1. A new secretary has to be nominated by EADS, Action 1:G.Hajen due: ready for next ODFCB meeting
  2. N. Illmer was confirmed as secretary backup.
  3. K. Kayal was proposed as alternate for Jens Schiemann,
  4. The chairman proposed to have one Payload Developer Representative for all ESA payloads.
  5. Wim van Leeuwen was nominated as ESA alternate representative for COL-CC and ATV-CC.
  6. ATV Prime contractor requires an alternate, currently TBD. Action 2: F.Allard/C. Beskow to provide name until next meeting
  7. G. Soellner Action 3: to check with DLR if G.Soellner takes the place as the representative and will provide a name for alternate, due next meeting.
  8. ATV- CC Prime contractor has TBD for both, rep and alternate; F.Allard takes the Action 4: to get the names for both until next meeting.
  9. A new representative line was opened, representing the Ops Preparation team on the ESA side, nominating R. Luettgens as the ESA rep and P.Granseuer as alternate
  10. A new represented body was introduced: ESA Operations Preparations Representative Roland Luettgens as nominated and Peter Granseuer as alternate.
  11. List will be updated and posted on the web.

Charter presentation of focal points for this meeting by Peter Granseuer (Attachment 3)

ESA to create a process that shows how to cover the hazard controls in the ESA ODF identified by the SRB.

Action 5: P.Granseuer, work out a process with G.Woop to document the process as a draft CR to the ODF MP, by 19 March. Coordinate a subsequent telecon for CR disposition.

COL Flight ODF Status, Gerd Hajen, (attachment 4)

  • Agreement will be required between ESA and NASA for the handling of Emergencies (procedures) in Columbus. This shall be handled in the next EJOP. The agreement needs to be in place before the procedures can be developed.
  • No Columbus ODF procedures have been validated up to now.
  • The validation of multielement procedures was discussed. It was pointed out that the BIVP Test 3B would allow for some multielement procedures validation including dedicated Columbus PCS displays. These test objectives are currently not agreed between ESA and NASA. The approach for multielement procedure / display validation has to be defined. The ESA ODFCB chairman will bring this to the attention to the next multilateral face-to-face ODFCB.
  • Some existing multielement procedures require updates on the NASA side when a new element like Columbus is attached to the ISS (example: false USOS fire alarm). This task needs to be triggered on the NASA side by the EJOP.
  • The assessment performed by EADS to figure out the complete set of procedures required for 1E and beyond has to be continued in the frame of mission preparation. A complete list of procedures has to be established.
  • Columbus Rack/Payload activation procedures are not yet developed for the rack and external payload installation and activation. These procedures between P/L and system are joint system/payload (single element) procedures. The ODF CB is responsible to trigger the procedure development process that is split between the different groups like P/L and system and USOCS. Action 6: K.Kayal to present current status including contractual coverage of the required tasks for next ODFCB meeting.
  • The presented list (p.4) reflects the Columbus C/D status.

Presentation of ESA ODF schedule (p.6 of attachment 4).

It was noted that there were ops prep milestones (e.g. Paper JMST # 2), that do not match with the ODF development template based on new launch date (NET 3-2006)

  • Roland Luettgens proposed a basic ODF delivery for 12-2004, under configuration control.

Action 7:G.Hajen:Collect requirements and generate a draft ESA ODF delivery schedule. To be agreed upon per telecon on 26 March.

Snapshot of ODF procedures.

Action 8:G.Hajen: draft Flight ODF snapshot including table of content for the complete Columbus ODF, reflecting ops prep, will be sent to ESA in two weeks time from now. It is not a formal delivery.

Ground ODF presentation, Gerd Soellner (attachment 5)

  • The presentation covers the differences of flight versus ground related info in ODF procedures.

The following has been mutually decided by the ODFCB:

1.The System and Payload ODF procedures shall contain all information needed for execution by both ground and crew in one common procedure.

2.The viewer shall support capabilities for flight-only, ground-only, combined view of the procedure.

3.The ODF format enhancement shall be based on the concept as shown on slides 6/7 of the presentation „Ground ODF Generation“.

4.The format enhancement has to be reflected in the ODF Standard. A change request has to be written and forwarded to the multilateral ODF CB.

5.The development and delivery of all System ODF procedures (including the ground book) shall be done under the overall responsibility of Engineering Support (EADS-ST). The ODF Management plan has to be updated accordingly.

ODFCB Rationale for Decisions 1-5:

The decisions are needed to start/continue the work on the ODF procedure development. Otherwise the procedure generation would be hindered, leading to a worsening of the existing schedule conflicts (see slide 6 of presentation „Col Flight ODF status“). The decisions need to be taken now.

ODFCB Recommendation:

When using the MCS Command Stack, the usage of fully and partly instantiated commands is recommended. The ESA ODFCB recommends adaptations of MCS/MDB for proper handling of these commands. Technically, these commands could also be used in ground displays.

Implementation Notes:

For decision no.2: The technical implementation for Checklist format seems to be straightforward. Logic Flow and Power Bus Loss formats to be assessed.

For decision no.4: The CR shall be formulated as soon as possible, draft for end of March 04 (proposal coordinated between ESA/EADS/Col-CC/FRC). The information provided in the ground control specific part of the procedure shall follow the ODF standards to the maximum extent possible.

  • Action 9: A proposal for the resulting CR to the ODF STD to be drafted by G.Soellner by 19 March 2004 and then coordinated by telecon on 26 March.
  • A CR for the update of the management plan needs to be prepared to reflect ESA ODF responsibilities. Action 10: ESA ODFCB chairman, due 26 March.
  • The decisions and recommendation will be forwarded to the OCB asap, together with an OCB meeting request. Tool upgrade required to support decisions and recommendations (e.g. IPV, PAT).

ESA Columbus Ground ODF Validation, Simon Challis (attachment 6)

The ODF validation process and plan needs to be developed (and attached to the ESA ODF MP). It was noted that EADS-ST has currently one validation process, not one per ESA ODF sub-component.

A similar process and plan has to be developed for displays.

Action 11: S.Challis will work out a more detailed ODF validation process based on the presentation. Draft due for 7 May.

ESA ODF Management System, M.Wolff, U.Brauer (attachment 7a & 7b)

Workflow and CR flow schematics, ODF management system presented.

Draft specification available with supporting s/w prototype. ESA suggests that further specification work shall include development of Use Cases.

Action 12: Industrial Operator Team, G.Hajen to provide refinement of the specification before the next ODFCB for review.

Columbus Flight Displays, Andrea Brinkmann, EADS (attachment 8)

PWS Displays Status report.

2 crew reviews have been performed whereby, the first one concentrated on synoptic displays and the second one on overall laptop functionality and applications. An ECR has been raised to implement some of the findings. Susan Stone (NASA, MOD) is currently reviewing the PWS displays and providing feedback to EADS. DGCS requires cleanup of the ESA Columbus display specifics delta.

Action 13: A.Brinkmann to provide ESA Columbus updates in DGCS until next IDAGS (foreseen for May 2004).

In the discussion with the crew rep it was debated whether the additional cmd information (e.g. instantiation info) in the flight displays compared to the ground displays would constitute an improvement in the communication with the ground control team. If the command could be directly sent from the procedure, it would considerably reduce the configuration control effort. However the proposals for a combined flight/ground ODF procedure (viewable on ground) improves the flight to ground communication.

PCS Displays Status report.

The Columbus PCS Display development was started according to the bilateral agreement. The development process was stalled and needs to be continued in order meet the 1E operations preparation milestones. The following actions are required to re-initiate the process.

An ICD / requirements document as per the bilateral agreement needs to be generated to control the development of the displays. The content and responsibility has to be discussed and agreed between all parties.

Note:

The PCS displays (on the NASA Sagan Server) can be accessed from ESTEC. Contact M.Wolff for further information.

Action 14: P.Granseuer to check status of the PCS Displays action AI-APM-Mgmt-4760 to clarify the development process with NASA. After clarification, discuss and agree work plan with EADS.

Due 15 March 2004

Action 15: M.Wolff. ESA to request an official delivery of the PCS displays and discuss with NASA generation and control process for the requirements document. Due April 2004

Ground Control Displays Status report: displays not yet available due to outstanding MCS V1 delivery.

IPV/PAT Presentation, M.Wolff, (Attachment 9)

Current PAT is available for download now, IPV in a couple of weeks (URL )

Action 16: M.Wolff: Find out effort to migrate from word to IPV from NASA SODF. Due April 2004

ODF for crew training & simulation, M.Wolff for N.Illmer, (attachment 10)

For information only.

Discrepancy between training and simulation schedule and ODF production schedule. Training and simulation need the ODF earlier for preparation of training material.

Operations Nomenclature System status, M.Wolff, (attachment 11)

Columbus Op Nom and ATV Op Nom have been discussed during several ESA/NASA telecons. It is expected that a formal CR approval will be achieved soon.

AOB:

  • Next ESA ODFCB planned for 6-7 July 2004.
  • Next face-to-face multilateral ODFCB is planned for 10-14May 2004 in Bremen hosted by EADS/ST
  • Simon Challis to become optional reviewer for ISS ODF MP CR’s

Annex A:

List of Participants ESA ODFCB#4, ESTEC, 3-5 March 2004

Names / Day 1 / Day 2 / Day 3
M.Wolff / x / x / x
G.Hajen / x / x / x
K.-U.Peters / x / x
A. Brinkmann / x / x
K.Kayal / x / x / x
U.Brauer / x
C.Knorr / x
A.Nietsch / x / x / x
R.Kozlowski / x / x
S.Challis / x / x
G.Soellner / x / x / x
N.Illmer / x / x
P.Granseuer / x / x / x
P.Duque / x
R.Luettgens / x
G.Woop / x
F.Allard / x

1