| Maintenance Levels |
|
First Level - Routine and recurring maintenance by Government and on-site support contractors.
Second Level - First attempt at repair or replacement of a failed component (e.g., board swap or unit replacement) by Government and on-site support contractors.
Third Level - Maintenance support from specialized vendors to supplement on-site Government and support contractors. Usually through contracts with associated response times. |
|
Manifest |
|
In the context of the Ground Segment interface to CLASS, an XML-format file that contains a list of the GOES-R products currently available for delivery to CLASS and is sent to initiate the archive delivery process. |
|
| Manifest (Ground Segment) |
|
In the context of the Ground Segment interface to the Archive, a file that contains a list of the GOES-R products available for delivery to Archive, which is sent to initiate the archive delivery process. |
|
| Margin |
|
The amount by which a capability exceeds mission requirements, as defined by: Margin% = [(Available Resource - Current Best Estimate) / (Available Resource)] x 100%. |
|
| Marginal |
|
Minor injury/illness and/or minor equipment damage resulting in limited delay of mission. |
|
| Material |
|
Substances including hardware, software and data that wholly or partially comprise a system, subsystem, component, or assembly. |
|
| Material/Failure Review Board (MRB) |
|
The formal Contractor board established for the purpose of reviewing, evaluating, and disposing of specific nonconforming materials, supplies or services, and for ensuring the implementation and accomplishment of corrective action to preclude recurrence. |
|
| Mean Time Between Failure (MRD) |
|
The average time that a system/component works without a failure. |
|
| Mean Time to Failure |
|
The expected time that a system/component will operate before the first failure will occur. |
|
| Mean Time to Repair |
|
The average time required to repair a system/component. |
|
| Maximum Time To Restore Services |
|
The specified time required to restore services of a system or component. |
|
| Measurement Resolution |
|
Resolution of the A/D converter. |
|
| Mesoscale (MESO) |
|
Defined as the equivalent of a 1.6043 x 1.6043 degree, 1000 x 1000 km nadir viewed area. |
|
| Metadata |
|
Information about data. An information file that exists to provide supplementary details about a data product. Metadata specifications are tailored to the needs and content of the product file. Metadata may include items such as product quality flag, data time span, algorithm version used for creation, ancillary file name(s), etc. |
|
| Metric |
|
A defined variable or set of variables, that uses collected measurements and information to describe the performance of a unit, subsystem, or a system. |
|
| Mission |
|
The full life cycle development and operation of a particular satellite. The Mission Phases are: Pre-launch, Launch and Orbit Raising, Post-Launch Test, Operations, Storage, and Disposal. |
|
| Mission Allowable Temperature (MAT) |
|
The established range of temperatures that units are permitted to experience while operating and non-operating in orbit. Mission allowable temperatures are established based upon analytical temperature predictions and upon the temperature range over which the hardware can operate. MAT encompasses worst case operating and non-operating temperature predictions, uncertainty, and any contractor desired temperature margin. |
|
| Mission availability |
|
The probability that the entire GOES-R series system can be successfully used for its specified mission over the stated period of time. |
|
| Mission Critical (Ground Segment) |
|
Having the potential to adversely affect either the health and safety of a flight system resource or the capability of the end-to-end GOES-R System to provide KPP product data. Components or functions designated as “mission critical” may include hardware, software, and procedural components and functions in either flight or ground systems. |
|
Mission Critical
(Space Segment) |
|
Hardware or software whose loss could affect the health and safety of the personnel, the satellite vehicle in flight, or the launch vehicle during launch. |
|
| Mission Critical Events |
|
Critical events are the events in a mission that must occur in sequence to achieve overall mission success. If the event is not executed properly and without anomaly, it could result in failure to accomplish the mission. Examples of critical events include orbit raising, station keeping and appendage deployment. |
|
| Mission Management (MM) |
|
Includes satellite mission scheduling, operations, state-of-health trending, orbital analysis, data acquisition, and ground operations. |
|
| Mission Operations |
|
Activities including real-time console operations, offline engineering and trending, bus and instrument health and safety and performance monitoring, anomaly detection and resolution, procedure development, spacecraft resource accounting, and special operations planning and execution. |
|
| Mission Operations Support Team (MOST) |
|
A team formed by the Program Office to focus on mission operations, from pre-launch planning and development, through launch and orbit raising, post-launch test, and transition to sustaining operations. The MOST includes personnel from both the Flight and Ground Segment Projects, including discipline engineers (spacecraft bus and instrument), systems engineers, flight and ground controllers, mission planners and schedulers, ground systems engineers, software maintenance, and associated support personnel. Membership will include Flight and Ground Segment contractor personnel, depending on mission phase. A key feature of the GOES-R MOST will be early involvement of several NOAA operations staff dedicated to GOES-R mission operations in the early stages of pre-launch development. The MOST will be lead by the GOES-R Mission Operations Manager. |
|
| Mission Readiness Test |
|
Any of the series of tests performed prior to satellite launch, to verify and validate the connectivity and communications between the ground segment and the various external entities that will provide launch and early orbit operations support (e.g., launch site tracking stations). Tests usually performed near to launch time when such interfaces are configured and available for testing. |
|
| Mode |
|
Manner of operation, use or existence of a system. |
|
| Monitor |
|
To track or witness the progress of an activity. |
