Ancillary Files Uplink Process
The operations steps needed to upload ancillary files. These include things like configuration files, log files, etc.
|
# |
Task |
Nominal Timeline |
Responsibility |
Notes |
||
|---|---|---|---|---|---|---|
|
ROI Exp Team |
ROI SW Team |
PI |
||||
|
1 |
File update |
Per Experiment Schedule |
|
|
✔ |
|
|
2 |
File testing (unofficial) |
1-2 weeks |
(✔) |
✔ |
(✔) |
Use correct upcoming service packs and OS. |
|
3 |
VDD baselined/updated (if necessary) |
2 weeks |
(✔) |
✔ |
(✔) |
A separate VDD may be required for the ancillary file(s). VDD for the main software item will document if the ancillary file(s) constitute a change in configuration of the main software item. If the main software item configuration is changed, a VDD will need to be baselined for the ancillary files. |
|
4 |
Software delivered to ROI |
4 weeks |
|
|
✔ |
PI Team to provide CoC for the file(s) delivered with PI and software developer signatures. For ancillary files, element cover letter/email not required. |
|
5 |
Procedure verification/operational testing |
✔ |
|
|
Required for first time use on ISS, if ancillary file significantly changes instructions to crew within the software, or per discretion of Experiment/Operations Team. |
|
|
6 |
Submit request to uplink software and schedule crew activity (if needed) |
|
✔ |
|
|
|
|
7 |
Crew installs update (if needed) |
2 weeks |
(✔) |
|
|
|
|
✔ - Primary Responsibility, (✔) - Secondary Responsibility (assists Primary) |
||||||