TraaCSS How To TraCSS Sat File - Owners/Operators

TraCSS_How-To-TraCSS Sat File - Owner Operator-MB.docx

Traffic Coordination System for Space (TraCSS)

TraaCSS How To TraCSS Sat File - Owners/Operators

OMB:

Document [docx]
Download: docx | pdf


How-To

Owner/Operator

TraCSS Satellite File

This guide explains how to complete the Owner/Operator TraCSS Satellite File for claiming satellites as a Satellite Owner/Operator Admin. Relevant FAQs can be found at the end of the guide.


General Guidelines

It is recommended to start with the Owner/Operator TraCSS Satellite File Template provided at time of upload. You should rename this file to match the following file naming convention: OrganizationName_Sats_YYYY-MM-DD.csv with the date reflecting the current calendar day. The template contains the necessary header row of information to be provided. For each satellite you own or maintain the legal authority to operate, create a new row within the file and provide the requested information. For more context on the meaning of a field or the reason for collection, please refer to the "Spacecraft Information and Attributes” table within the provided TraCSS Data Policy. Your Owner/Operator TraCSS Satellite File will be validated after upload to ensure the minimum required fields, NORAD ID and Satellite Name, are completed for each satellite and formatting guidelines are met for all completed fields.


For details on the data types and allowed values for each field within the Owner/Operator TraCSS Satellite File, see the specification table below. Fields with a data type of “Enumerated Value" should be populated with one of the options provided. It is strongly encouraged to complete all fields within the Owner/Operator TraCSS Satellite File with known information pertaining to the satellites you are claiming at the time of registration. However, if fields are left incomplete, they should be updated following account approval in a timely manner by submitting a new Owner/Operator TraCSS Satellite File with the most current data. Any fields you choose not to provide should be left blank and remain denoted in the comma separated fashion. For example, a satellite with no alternate names would show:

satelliteName,alternateNames,noradID,...

My Sat Name,,12345,...





TraCSS Satellite File Specification


Field Name

Data Type Restrictions

Allowed Values & Further Details

satelliteName

String

Any

alternateNames

Semi-colon separated list of Strings

Any

Example: sat1;sat2;sat3

noradId

Integer

Any

InternationalDesignator

String

Any

Format: YYYY-NNNP{PP}

Example: 2025-002A

countryOfHeadquarters

String

Any

Format: Alpha-3 Code

countryOfLaunchLicense

String

Any

Format: Alpha-3 Code

countryProviding

CommunicationsLicense

String

Any

Format: Alpha-3 Code

countryProviding

RemoteSensingOrNovel

ActivitiesLicense

String

Any

Format: Alpha-3 Code

countryOfUNRegistry

String

Any

Format: Alpha-3 Code

constellation

String

Any

Example: Starlink

operationalStatus

Enumerated Value

BACKUP_STORAGE_STANDBY, DECAYED, DEGRADED_OPERATIONS, EXTENDED_MISSION, UNKNOWN, REENTRY_MODE, NONOPERATIONAL, OPERATIONAL_MANEUVERABLE, OPERATIONAL_NONMANEUVERABLE

Definitions: CCSDS Operational Status


Field Name

Data Type

Allowed Values & Further Details

orbitCategory

Enumerated Value

GEO, GSO, GTO, HELIOCENTRIC, HEO, INTERPLANETARY, LEO, PLANETARY, <P1>_<P2>_<N>, LUNAR, MEO, OTHER

Definitions: CCSDS Orbit Categories

wetMass

Double

Any

Units: Kilograms

Example: 1000.344

hardBodyRadius

Double

Any

Units: Meters

Example: 3.392

hardBodyRadius

CalculationMethod

String

Any

Example: Circumscribing Sphere

conjunctionMitigation

Capabilities

Semi-colon separated list of Enumerated Values

chemical propulsion, electric propulsion, differential drag, object reorientation, none

expectedOperational

MissionLifetime

Double

Any

Units: Years

Example: 12.4

estimatedTotalTime

OnOrbit

Double

Any

Units: Years

Example: 12.6

launchProvider

String

Any

launchVehicle

String

Any

launchSite

String

Any matching the UN global launch locations or “OTHER”

Example: Woomera Australia

Note: Exclude commas from name

launchDate

Date

Any

Format: YYYY-MM-DD

Example: 2025-01-26


Field Name

Data Type

Allowed Values & Further Details

deploymentDate

Date

Any

Format: YYYY-MM-DD

Example: 2025-01-27

Note: Only required if different than launch date

additionalDeployments

Enumerated Value

YES, NO

Note: Used to identify Orbital Transfer Vehicles (OTVs)

launchName

String

Any

plannedOrbit

Semi-color separated list of Doubles

Note: Initial and final orbits should be provided if there is a planned change



Units:

Nodal Period, min

Apogee & Perigee, km

Inclination, deg



Initial Only Format: nodalPeriod;apogee;perigee;inclination


Initial & Final Format:

nodalPeriod1;apogee1;perigee1; inclination1;nodalPeriod2;apogee2; perigee2;inclination2

generalFunction

Semi-colon separated list of Enumerated Values

Choose From:

  • spacecraft engaged in investigation of spaceflight techniques and technology

  • spacecraft engaged in research and exploration of the upper atmosphere or outer space

  • spacecraft engaged in practical applications and uses of space technology such as weather or communications

  • spent boosters, spent maneuvering stage, shrouds and other non-functional objects

  • reusable space transportation systems



Field Name

Data Type

Allowed Values & Further Details

objectType

Enumerated Value

Debris, Payload, Rocket Body, Unknown, Other

Note: Defaults to Payload if left blank

contactInfo

Semi-Colon separated list of Strings

Any

Format: First;Last;Phone;Email

Multiple Phone/Email Format:

First;Last;Phone;Phone;Email;Email


FAQs

Why are certain fields deemed necessary?

For more context on the meaning of a field or the reason for collection, please refer to the "Spacecraft Information and Attributes” table within the TraCSS Data Policy.


Why is my file failing the validation checks?

Your file is being tested for compliance for all completed fields. At a minimum, the two required fields to submit a Owner/Operator TraCSS Satellite File are Satellite Name and NORAD ID. Any additional fields that are completed will be tested for compliance in addition to these two required fields. Please refer to the error messages provided after a submission attempt for guidance on updating your Owner/Operator TraCSS Satellite File to meet compliance requirements.


Will the contact information provided be made publicly available?

No, the operational contact information for a satellite will not be made open data. Use and redistribution of this information is outlined within the TraCSS Data Policy.


A Federal agency may not conduct or sponsor, and a person is not required to respond to, nor shall a person be subject to a penalty for failure to comply with an information collection subject to the requirements of the Paperwork Reduction Act of 1995 unless the information collection has a currently valid OMB Control Number. The approved OMB Control Number for this information collection is 0648-XXXX. Without this approval, we could not conduct this information collection. Public reporting for this information collection is estimated to be approximately 2 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the information collection. All responses to this information collection are voluntary. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden to the NODC Data Officer, SSMC3, 4th Floor, E/OC, 1315 East West Highway, Silver Spring, MD 20910.


Privacy Act Statement


Authority: The collection of this information is authorized under 5 U.S.C. § 301, Departmental regulations which authorizes the operations of an executive agency, including the creation, custodianship, maintenance and distribution of records, and 15 U.S.C. 1512, Powers and duties of Department.


Purpose: NOAA collects limited information, such as name, address, phone number, or email address for a variety of purposes. This information will be used to respond to user inquiries or provide services requested by the user.


Routine Uses: Disclosure of this information is permitted under the Privacy Act of 1974 (5 U.S.C. Section 552a) to be shared among Department staff for work-related purposes. Disclosure of this information is also subject to all of the published routine uses as identified in the Privacy Act System of Records Notice COMMERCE/NOAA-11, Contact Information for Members of the Public Requesting or Providing Information Related to NOAA’s Mission.


Disclosure: Furnishing this information is voluntary. By providing this information, you are consenting to the use of that information only for the purpose for which it is submitted.


NOAA OSC TraCSS Forms and Instructions

OMB 0648-XXXX

Expiration Date: XX/XX/20XX

Office of Space Commerce | www.space.commerce.gov | [email protected]

4

File Typeapplication/vnd.openxmlformats-officedocument.wordprocessingml.document
AuthorJesse Gutknecht
File Modified0000-00-00
File Created2025-07-29

© 2025 OMB.report | Privacy Policy