The file's text, extracted by GovTribe without its formatting.
NNG17588638R
ATTACHMENT A
STATEMENT OF WORK (SOW)
for
SPACE EXPLORATION NETWORK SERVICES AND EVOLUTION
(SENSE)
April 2017
INTRODUCTION
| The | Exploration | and | Space | Communications | Projects | Division | (ESC) | is | a | national | resource | located | at | | | |
| Goddard | Space | Flight | Center | (GSFC) | which | enables | scientific | discovery | and | space | exploration | by | providing | | | |
| innovative | and | mission-effective | space | communications | and | navigation | solutions | to | a | large | community | of | | | | |
| diverse | customers. | | ESC | manages | operational | geostationary | communications | relay | satellites | and | ground | | | | | |
| systems | for | the | Space | Communications | and | Navigation | (SCaN) | Program | at | NASA | Headquarters. | | Today, | SCaN | | |
| network | systems | consist | of | the | Space | Network | (SN), | the | Near | Earth | Network | (NEN), | and | the | Deep | Space |
| Network | (DSN). | | The | day-to-day | management | of | these | three | networks | is | currently | not | fully | consistent. | It | is |
| the | intention | of | the | Government | to | unify | the | SN | and | NEN | where | practicable | under | this | contract | using |
| integrated, | common | management | practices | and | network | solutions. | | | | | | | | | | |
| ESC | customers | include | other | NASA, | other | government | agency, | commercial, | and | foreign | partner | missions. | | | |
| ESC | networks | operate | 24 | hours | a | day, | 365 | days | a | year | (24X7X365), | providing | Telemetry, | Tracking, | and |
| Commanding | (TT&C), | high | rate | data | downlink, | and | radiometric | tracking | services. | | More | than | 30 | terabytes | of |
| data | flow | over | ESC | networks | on | a | daily | basis. | | | | | | | |
| The | ESC | and | its | predecessor | organizations | have | a | long | history | of | providing | excellent | communications | and | |
| tracking | solutions | to | customer | missions. | | The | SENSE | Contactor | shall | continue | to | provide | reliable | and | highly |
| available | communications | and | tracking | services | while | simultaneously | implementing | efficiencies | as | the | ESC | | | | |
| moves | forward | to | develop | the | next | generation | of | space | communications | and | navigation | services. | | | |
Background
| The | SN | consists | of | a | fleet | of | Tracking | and | Data | Relay | Satellites | (TDRS) | and | associated | ground | systems | that |
| provide | relay | telecommunications | and | tracking | services | to | customer | missions. | | The | SN | is | operated | 24x7x365 | | | |
| at | Government-owned, | Contractor-operated | facilities. | | The | SN | nominally | operates | in | an | automated | fashion | in | | | | |
| response | to | schedule | requests, | service | change | requests, | and | state | vectors. | | Contingency | operations | may | | | | |
| require | manual | intervention. | | | | | | | | | | | | | | | |
| The | SN | operational | TDRS | spacecraft | are | stationed | at | three | orbital | locations: | the | Pacific | Ocean | Region | (POR), | |
| the | Atlantic | Ocean | Region | (AOR), | and | the | Indian | Ocean | Region | (IOR). | | Additional | TDRS | spacecraft | are | stored |
| at | other | orbital | locations. | | The | TDRS | constellation | is | composed | of | three | generations | of | spacecraft: | | |
| • 1st | generation | - | Flight | 3 | (F3), | F5, | F6, | and | F7 | | | |
| • 2nd | generation | - | F8, | F9, | and | F10 | | | | | | |
| • 3rd | generation | - | F11, | F12, | and | TDRS | M | (to | be | launched | in | 2017) |
| SN | activities | include | maintenance | and | operation | of | four | ground | stations | and | several | auxiliary | support | sites. |
| Real | time | system | operations | are | managed | from | the | Second | TDRS | Ground | Terminal | (STGT). | | Administrative |
| management | is | performed | at | GSFC. | | The | four | SN | ground | stations | are | located | at: | |
| • White | Sands | Complex | (WSC) | (2 | stations, | STGT | and | White | Sands | Ground | Terminal | (WSGT)) | - | Las |
| Cruces, | NM | | | | | | | | | | | | | |
| • Guam | Remote | Station | (GRS) | - | Guam | | | |
| • Blossom | Point | Remote | Station | (BPRS) | - | La | Plata, | MD |
| The | Near | Earth | Network | (NEN) | is | a | direct-to-earth | communications | and | tracking | network | that | provides | |
| TT&C, | high | rate | data | acquisition | downlink, | and | radiometric | tracking | services. | | The | NEN | operates | and |
| maintains | antenna | systems | located | at: | | | | | | | | | | |
| • Wallops | Ground | Station | - | Wallops | Island, | VA | |
| • McMurdo | Ground | Station | – | McMurdo, | Antarctica | | |
| • WS1 | - | Las | Cruces, | NM | | | |
| • Kennedy | Uplink | Station | – | KSC, | FL | | |
| • Ponce | de | Leon | station | - | Ponce | Inlet, | FL |
NEN-contracted commercial services provide almost half of the approximately 150 daily NEN passes.
| Network | integration | activities | support | the | establishment | of | communication | and | navigation | services | across | | | | |
| all | stages | of | the | mission | lifecycle | including | pre-formulation, | formulation, | implementation, | integration | & | test, | | | |
| pre-launch | and | launch, | and | operations | through | end | of | mission. | | Activities | include | collaborating | with | pre- | |
| operational | customer | missions | to | establish | and | document | requirements, | communications | link | analysis, | | | | | |
| interface | definition, | and | coordination | of | system | changes. | | Network | integration | activities | also | include | mission | | |
| integration | testing, | pre-launch | testing, | simulations, | and | compatibility | testing. | | Compatibility | test | resources | | | | |
| include | compatibility | test | sets | that | emulate | the | relay | and | direct-to-earth | networks, | portable | test | sets | for | use |
| at | customer | sites, | and | a | compatibility | test | lab | that | provides | an | isolated | environment | for | testing. | |
| Electromagnetic | Spectrum | Management | (ESM) | is | a | GSFC | center-level | activity | managed | by | ESC | and | offers | an | | |
| essential | service | to | stakeholders | within | and | external | to | NASA. | | The | primary | ESM | functions | are | Spectrum | |
| Management | and | Communications | Link | Analysis. | | The | goals | of | Spectrum | Management | are | to | comply | with | | |
| spectrum | policy | and | to | shape | national | and | international | policy | with | the | goal | of | protecting | NASA | and | ESC |
| spectrum | usage. | | Communications | Link | Analysis | and | Communications | Systems | Engineering | define | | | | | | |
| communications | link | interfaces | and | end-to-end | data | delivery | paths | to | ensure | missions | are | compatible | with | | | |
| SCaN | assets, | and | are | integral | functions | of | ESC. | | | | | | | | | |
| In | addition | to | managing | the | SCaN, | NEN, | SN, | and | network | integration | functions, | ESC | also | supports | the |
| Satellite | Laser | Ranging | (SLR) | Network, | the | Very | Long | Baseline | Interferometry | (VLBI) | Network | and | the | | |
| Electronic | Systems | Test | Laboratory | (ESTL). | | | | | | | | | | | |
For more information on ESC Systems visit the ESC website at http://esc.gsfc.nasa.gov/.
Vision
| While | continuing | our | superb | customer | support, | ESC | will | evolve | toward | capabilities | and | capacities | that | meet | | |
| the | needs | of | future | customers, | including | providing | higher | bandwidths | while | simplifying | the | customer | | | | |
| interface | and | experience | such | that | the | customer | is | unaware | of | the | individual | elements | and | differences | | |
| among | internal | ESC | solutions. | | Through | use | of | new | areas | of | the | electromagnetic | spectrum | and | innovative | |
| space | and | ground | architectures, | ESC | will | extend | communications | services | to | meet | the | demands | of | new, | | |
| innovative | mission | approaches | and | a | much | larger | concurrent | customer | set | in | a | full | variety | of | mission | phases. |
| A | key | element | of | the | ESC | vision | for | the | SENSE | contract | is | the | integration | of | technical | solutions | and |
| management | functions | across | the | contract | to | achieve | efficiencies. | | While | ESC | manages | multiple | functional | | | | |
| and | independent | areas, | the | Government | vision | for | the | Contractor | is | to | achieve | cost | reductions | and | to | obtain | |
| execution | efficiencies | and | optimization | through | the | employment | of | contractor-implemented | cross- | | | | | | | | |
| organizational | involvement, | engagement, | execution, | and | management | arrangements | while | meeting | or | | | | | | | | |
| exceeding | technical | requirements. | | Additionally, | ESC | maintains | the | path | forward | to | meet | the | SCaN | long-term | | | |
| architectural | vision. | | To | this | end, | architecture | planning, | management | and | development | are | included | in | the | | | |
| SENSE | contract | scope | of | work. | | | | | | | | | | | | | |
Objectives The objectives for this contract are:
| • Program | Management | objectives: | | | | | | | | | | |
| o Manage | resources | to | deliver | services | that | enable | the | missions | supported | to | achieve | their |
objectives
| o Safely | and | securely | support | the | missions | and | protect | the | network | assets | |
| o Serve | the | missions | throughout | the | mission | lifecycle | with | highly | responsive | and | informative |
support to their requirements
| o Deliver | services | and | products | that | meet | or | exceed | technical | performance | requirements |
| within | cost | and | schedule | | | | | | | |
| o Reduce | the | volume | of | contract | transactions | by | minimizing | the | number | of | task | orders |
| o Reduce | the | cost | of | delivering | services | through | integration, | automation, | opportunities | for | | |
| efficiency, | and | reduction | of | redundancies | | | | | |
| o Enable | evolution | of | the | services | and | systems | | | |
| o Protect | national | security | and | further | U.S. | foreign | policy | objectives | |
| o Work | cooperatively | to | achieve | objectives | across | NASA | organizations, | external | stakeholders, |
| independent | systems | engineering | support | contractors, | development | contractors, | mission |
| contractors, | program | support | contractors, | and | O&M/Sustaining | contractors | |
| o Identify | and | implement | risks/mitigations | and | issues/resolutions | | | | | | | | |
| o Conduct | all | work | in | compliance | with | laws, | policies, | procedures, | and | the | terms | and | conditions |
| of | the | contract |
| • System | Architecture | objectives: |
| o Identify | areas | for | architectural | improvement | to | gain | consistency | and | efficiency | |
| o Engender | a | systems | approach | to | network-provided | services | across | networks | and | functions |
| o Maintain | internal | system | consistency | and | cohesion | to | ensure | long-term | efficiency | and |
| effectiveness | of | technical | solutions | | | | | | | | | |
| o Ensure | a | solid | baseline | of | architecture | concepts, | artifacts, | analyses, | roadmaps, | and | plans | are |
| in | place | to | transition | new | capabilities | into | operations | in | support | of | day-to-day | mission |
| success | and | future | evolutionary | planning | | | | | | | | |
| • System | Engineering | objectives: | | | | | | | | | | |
| o Identify | areas | for | process | and | design | improvement | for | gains | in | consistency | and | efficiency |
| across | networks | and | functions | | | | | | | | |
| o Ensure | solid | baselines | of | requirements, | specifications, | processes, | and | procedures | are | in | place |
| and | are | consistently | applied | to | support | all | lifecycle | phases | including | systems | transitioning |
| into | operations, | day-to-day | mission | success, | and | future | evolutionary | planning | | | |
| • Development | objectives: | | | | | | | | |
| o Provide | new | and | innovative | products | and | services | for | ESC | customers |
| o Achieve | technical | requirements | within | cost | and | schedule | commitments | | |
| • Operations, | Maintenance | and | Sustainment | objectives: | | | | | | | | |
| o Ensure | the | reliability, | availability, | and | maintainability | of | all | facets | of | operations | and | mission |
| data | delivery | | | | | | | | | | |
| o Provide | timely | response | to | inquiries | requesting | support | or | status | updates | on | specific |
| missions, | products | or | services | | | | | | |
| o Identify | opportunities | for | migrating | to | integrated, | common | services | for | resource |
optimization
| o Maintain | accurate | accountability | of | government | property | | | | | | |
| o Ensure | continued | service | delivery | at | required | performance | levels | and | at | reasonable | retention |
of government property value
• Facilities:
o Safely and efficiently design, build, maintain and operate facilities
Scope
| This | Statement | of | Work | (SOW) | identifies | work | required | to | support | continuous | operations, | maintenance, | and |
| sustainment | of | the | relay | and | direct-to-earth | networks | and | their | evolution | toward | a | future | architectural |
vision.
| Government | issued | task | orders | will | specify | the | specific | work | to | be | performed, | including | the | requirements | to |
| be | met, | the | standards(s) | of | performance, | required | deliverables | or | output, | government | furnished | property | or | | |
| information, | and | applicable | documents | within | this | broader | contract | scope. | | | | | | | |
Unless specifically stated in each individual task order, the requirements listed in section 1.0 shall apply to all tasks issued under the contract. The IDIQ requirements are outlined in the remaining SOW Sections.
1 Contract Management
| The | Contractor | shall | perform | all | necessary | management | functions | (plan, | execute, | track, | report | progress, | etc.) | | |
| in | order | to | meet | or | exceed | contractual | requirements. | | The | Contractor | shall | implement | an | integrated | program |
| management | approach | which | consolidates | common | management | practices | and | technical | solutions | in | order | | | | |
| to | gain | efficiencies | across | tasks, | customers, | and | missions. | | The | Contractor | shall | identify | opportunities | for | |
| efficiencies, | including | but | not | limited | to, | innovative | approaches, | cost | and | schedule | savings, | and | process | | |
improvements.
| The | Contractor | shall | maintain | a | qualified | workforce | as | demonstrated | by | training | and | skills | certification, |
| engineering | and | operations | workforce | experience, | educational | attainments | and | security | clearances. | | The | | |
| Contractor | shall | maintain | training | and | certification | records, | as | appropriate, | for | each | employee. | | The |
| Contractor | shall | maintain | training | and | certification | plans | for | designated | critical | positions. | | | |
| The | Contractor | shall | develop | and | submit | Task | Implementation | Plans | (TIP), | including | cost | proposals | [DRD | | | | | |
| MGT-02] | in | response | to | task | orders | issued | by | the | government. | | The | Government | may | provide | the | task | Work | |
| Breakdown | Structure | (WBS) | or | require | the | task | WBS | [DRD | MGT-06] | be | included | in | the | TIP. | | Task | orders | will |
| be | issued | by | the | Government | through | the | Task | Order | Management | System | (TOMS). | | | | | | | |
| The | Contractor | shall | submit | reports, | conduct | reviews, | and | participate | in | meetings | to | keep | the | Government |
| informed | of | status, | risks, | and | issues. | | | | | | | | | |
| The | Contractor | shall | plan, | track, | accumulate, | and | report | contract | costs. | | The | Contractor | shall | maintain | a |
| financial | management | system | capable | of | accommodating | WBS | changes | with | minimal | disruption. | | All | | | |
| Contractor | financial | systems | shall | support | NASA’s | agency-wide | Integrated | Enterprise | Management | System | | | | | |
| in | accordance | with | NPR | 9130.1. | | | | | | | | | | | |
| The | Contractor | shall | identify | and | manage | contract | and | task | level | risks | associated | with | safety, | cost, | schedule, |
| and | technical | performance. | | | | | | | | | | | | | |
The Contractor shall conduct formal document configuration management.
| The | Contractor | shall | support | NASA | mandated | audits, | such | as | Inspector | General, | IT | security, | physical |
| security, | health | and | safety, | International | Organization | for | Standardization | (ISO), | and | property. | | | |
| The | Contractor | shall | develop | and | implement | a | phase-out | plans | as | required | by | task | orders | to | ensure | an |
| orderly | transition | of | work, | including | engineering | knowledge, | processes, | procedures, | documentation, | and | | | | | | |
| tools, | to | the | Government | or | to | a | successor | contractor. | | | | | | | | |
| The | Contractor | shall | comply | with | applicable | international, | Federal, | state, | and | local | environmental | | |
| requirements, | environmental | Executive | Orders, | NASA | procedural | requirements | and | directives, | and | GSFC | | | |
| environmental | directives, | procedures, | and | policies. | | The | Contractor | shall | implement | and | maintain | an | |
| Environmental | Management | System | (EMS), | or | include | SENSE | facilities | in | an | existing | corporate | EMS | that |
| conforms | to | NPR | 8553.1B: | NASA | Environmental | Management | System. | | | | | | |
| The | Contractor | shall | use | NASA | Operational | Messaging | and | Directory | Service | (NOMAD) | services | for | all | NASA |
| business. | | The | Government | will | furnish | NOMAD | accounts. | | | | | | | |
The Contractor shall provide the government on-line access to documentation developed under the contract.
The Contractor shall control system and data access in accordance with:
| • NPR | 2841.1: | Identity, | Credential, | and | Access | Management | (ICAM) | |
| • NASA | IT-HBK-2841-002: | Identity, | Credential, | and | Access | Management | (ICAM) | Services |
The Contractor shall adhere to NIST SP 800-44: Guidelines on Securing Public Web Servers.
The Contractor shall comply with Federal and NASA export control regulations including:
| • Title | 22 | CFR | 120-130: | International | Traffic | in | Arms | Regulations | (ITAR) | | | |
| • Title | 15 | Code | of | Federal | Regulations | (CFR) | Parts | 730-774: | Export | Administration | Regulations | (EAR) |
| • NPD | 2190.1B: | NASA | Export | Control | Program | | | | | | | |
| • NPR | 2190.1B: | NASA | Export | Control | Program | | | | | | | |
| The | Contractor | shall | mark | documents | delivered | to | the | Government | in | accordance | with | the | above | export |
| control | regulations. | | | | | | | | | | | | | |
The Contractor shall control Sensitive But Unclassified (SBU) information in accordance with:
| • NPR | 1600.1A: | NASA | Security | Program | Procedural | Requirements | |
| • NID | 1600.55: | Sensitive | But | Unclassified | (SBU) | Controlled | Information |
| The | contractor | shall | perform | all | software | application | development, | including | the | development | of | code, | in |
| compliance | with: | | | | | | | | | | | | |
| • R.A. | of | 1973, | Sec | 508: | Final | FAR | Rule | For | Implementing | Section | 508 | of | the | Rehab | Act | Electronic | and |
| Information | Technology | Accessibility | for | Persons | with | Disabilities | | | | | | | | | | | |
| CFR-2011-36-V3-1194: | Electronic | and | Information | Technology | Accessibility | Standards; | Final | Rule, | to | | | | | | |
| include | 1194.21 | Software | applications | and | operating | systemsThe | Contractor | shall | comply | with | NPR | | | | |
| 8800.15C: | Real | Estate | Management | Program | any | NASA | real | property | transactions | (any | use | of | land | or | |
| buildings). | | The | Contractor | shall | complete | a | basic | ASTM | E1527-13 | Phase | I | Environmental | Site | Assessment | to |
| meet | the | requirements | of | NPR | 8800.15C | for | an | Environmental | Baseline | Survey | (EBS) | for | NASA | real | property |
transactions.
| The | Contractor | shall | procure | all | technologies | accordance | with | CNSSP | No. | 11, | "National | Policy | Governing | the | |
| Acquisition | of | Information | Assurance | and | IA-Enabled | Information | Technology | Products." | The | Contractor | | | | | | |
| shall | procure | only | technologies | that | have | been | validated | by | Common | Criteria | Testing | Labs, | in | accordance | | |
| with | the | National | Information | Assurance | Partnership | (NIAP) | Protection | Profiles | (PPs). | | Where | a | PP | exists | | |
| but | the | desired | product | has | not | been | validated | against | it, | the | Contractor | shall | validate | their | product | against |
| the | appropriate, | corresponding | PP. | | The | Contractor | shall | use | technologies | from | the | Commercial | Solutions | for | | |
| Classified | (CSfC) | Components | List, | in | accordance | with | NSA's | published | CSfC | Capability | Packages | | | | | |
| (Commercial | Solutions | for | Classified | (CSfC) | Customer | Handbook) | for | systems | containing | classified | data. | | | | | |
| The | Contractor | shall | produce, | control, | and | maintain | contract | documentation | in | accordance | with | the | Data | |
| Requirements | Descriptions | (DRDs) | and | the | Data | Requirements | List | (DRL). | | All | data | shall | be | prepared, |
| maintained, | and | delivered | to | National | Aeronautics | and | Space | Administration | (NASA) | in | accordance | with | the | |
| requirements | of | the | task | order | SOWs | and | CDRL. | | | | | | | |
2 Security
| The | Contractor | shall | perform | physical, | personnel, | operations, | communications, | information, | and | information | | | |
| technology | security | functions | for | space | and | ground | systems | in | accordance | applicable | Federal, | NASA | and |
| GSFC | regulations, | policies, | procedures, | standards, | and | guidelines | and | the | Contract | Security | Classification | | |
| Specification | (Attachment | M, | Form | DD | 254). | | | | | | | | |
| On | a | contingency | basis, | the | Contractor | shall | provide | physical | security | services | that | require | personnel |
| certified | as | Security | Police | Officers | with | Federal | Arrest | Authority. | | | | | |
| 3 Systems | Architecture | and | Engineering | | | | | | | | | | | |
| The | Contractor | shall | perform | system | architecture | and | engineering | for | space | and | ground | systems. | | The |
| Contractor | shall | analyze, | develop, | document, | and | maintain | system | architectures | including | concepts, | | | | |
| architecture | domains | and | views, | roadmaps | and | plans | for | modernization, | enhancement, | evolution, | and | | | |
| sustainment | of | new | and | existing | systems | that | support | current | and | future | architectures. | This | systems | |
| architecture | work | shall | include | the | identification | and | evaluation | of | technologies, | standards, | and | concepts | | |
| which | may | be | incorporated | into | the | network | systems | to | enhance | network | performance | and | provide | |
| additional | capabilities. | | | | | | | | | | | | | |
| The | Contractor | shall | perform | work | involving | all | phases | of | the | system | engineering | lifecycle | including | studies, |
| technology | evaluations, | prototyping, | customer | planning, | concept | development, | requirements | definition, | | | | | | |
| design, | verification, | validation, | and | transition | to | operations. | | | | | | | | |
| The | Contractor | shall | perform | communication | and | navigation | engineering | analyses, | and | shall | perform |
| network | loading | analyses. | | | | | | | | | |
| The | Contractor | shall | perform | Electromagnetic | Spectrum | Management | (ESM) | engineering | analyses | and |
| provide | technical | recommendations | and | documentation | for | GSFC, | national, | and | international | spectrum |
matters.
| The | Contractor | shall | manage | all | aspects | of | government-provided | IT | systems | including | planning, | acquisition, |
| integration, | security, | maintenance, | sustainment, | and | remediation. | | | | | | | |
The Contractor shall conduct formal system configuration management.
4 Development
| The | Contactor | shall | develop | new | ground | system | capabilities | and | capacity. | | Requirements | include | the |
| following: | analyze | and | assess | needs, | conduct | trade | studies, | develop | operational | concepts, | derive | and | control |
| requirements, | develop | preliminary | and | detailed | designs, | implement | and/or | procure | hardware, | software, | and | | |
| firmware | components, | integrate | subsystems | and | elements, | conduct | tests | and | inspections, | verify | and | validate | |
| requirements, | generate | operational | and | maintenance | documentation, | and | transition | systems | to | operations. | | | |
| 5 Integration | and | Test | | | | | | | | | | | | |
| The | Contractor | shall | integrate | network | services | including | those | provided | by | commercial | service | providers, | | |
| partner | service | providers, | and | the | Contractor, | using | elements | furnished | by | the | Government, | to | provide | the |
| complete | set | of | communications | and | tracking | services | required | by | customer | missions. | | | | |
| The | Contractor | shall | assess | and | document | new | mission | support | requirements | and | identify | new | or | mission- |
| unique | service | capabilities | or | configurations. | | | | | | | | | | |
| The | Contractor | shall | conduct | interface | compatibility | analysis | and | testing | to | verify | and | validate | that | customer |
| mission | interfaces | are | compatible | with | network | interfaces. | | The | Contractor | shall | conduct | integrated | | |
| networks | testing | to | validate | and | verify | new | customer | requirements | for | services | from | the | integrated | |
networks.
| The | Contractor | shall | integrate, | test, | verify, | validate, | and | transition | to | operations | configuration | changes, |
| upgrades, | enhancements, | interface | changes, | and | new | customer | data | flows. | | | | |
6 Operations The Contractor shall operate space and ground systems.
| The | Contractor | shall | safely | operate | the | TDRS | spacecraft | and | network | ground | systems | to | provide |
| communications | and | tracking | services. | | The | Contractor | shall | subcontract | with | commercial | entities | for | the |
| provision | of | commercial | communications | and | tracking | services. | | The | Contractor | shall | conduct | geodetic | |
| observations | using | government-furnished | VLBI | and | SLR | systems. | | | | | | | |
| The | Contractor | shall | schedule | services | and | observations, | configure | and | monitor | systems, | identify | and |
| address | discrepancies, | and | generate | operational | reports. | | | | | | | |
The Contractor shall conduct continuity of operations preparedness planning and rehearsals.
The Contractor shall manage government property and provide logistical services.
The Contractor shall provide desktop computing, local area network, administrative, and library services.
7 Maintenance The Contractor shall maintain space and ground systems.
| The | Contractor | shall | maintain | custom | and | Commercial | Off-The-Shelf | (COTS) | software, | firmware, | hardware, | |
| and | mechanical | components. | | The | Contractor | shall | perform | preventative | and | corrective | maintenance | to |
| meet | contract | performance | requirements | and | retain | government | property | value. | | The | Contractor | shall |
| calibrate | test | equipment. | | | | | | | | | | |
| 8 Sustaining | Engineering | | | | | | | | | | | | | |
| The | Contractor | shall | perform | sustaining | engineering | for | space | and | ground | systems | in | order | to | meet |
| customer | needs, | achieve | contract | performance | requirements, | and | minimize | lifecycle | costs. | | | | | |
| The | Contractor | shall | perform | spacecraft | sustaining | engineering | including | monitoring | spacecraft | telemetry, | |
| tracking | parameter | trends, | assessing | the | health | of | spacecraft | systems, | supporting | anomaly | resolution, |
| planning | constellation | configurations, | and | planning | end | of | mission | activities. | | | |
| The | Contractor | shall | perform | ground | system | sustaining | engineering | including | identifying, | evaluating, | | | |
| planning, | designing, | and | implementing | system | and | configuration | changes | needed | to | sustain | system | | |
| operations. | | The | Contractor | shall | implement | a | discrepancy | reporting | and | tracking | process | and | systems |
| configuration | management | process. | | | | | | | | | | | |
9 Facilities
| The | Contractor | shall | operate | and/or | maintain | ground | system | facilities | including | buildings, | grounds, |
| antennas, | heating, | ventilation, | and | air | conditioning | (HVAC) | systems, | electrical | power | plants, | uninterruptable |
| power | systems, | vehicles, | mechanical | systems, | locks, | plumbing, | environmental | systems, | lighting | systems, | |
| supervisory | control | and | data | acquisition | systems, | security | systems, | and | fire | protection | systems. |
The Contractor shall provide custodial services and utilities at ground system sites.
| The | Contractor | shall | provide | Architect-Engineer | (A&E) | services | in | support | of | Construction | of | Facilities |
| projects | including | preliminary | engineering | reports, | design | packages, | minor | and | major | construction, | | |
| modification/rehabilitation | construction, | and | repair | construction. | | These | services | shall | include | safety, | | |
| reliability, | and | maintainability | studies, | engineering, | project | management, | construction, | supervision, | | | | |
| inspection, | documentation, | commissioning, | training, | activation, | and | validation. | | | | | | |
The contractor shall conduct Environmental Baseline Survey.
| The | Contractor | shall | outfit | facilities | with | workstations, | equipment, | signage, | and | materials | required | for | the |
| facility | to | be | fully | functional | in | support | of | personnel | and | equipment. | | | |
10 Appendices Appendix A. Definitions
The following terms and definitions are used throughout this contract.
| The | term | “ESC | Systems” | includes | the | total | scope | of | the | communications | and | radiometric | tracking |
| architecture | (including | networks) | and | functionality | identified | in | this | SOW | and | Appendices. | | | |
| Systems | include | ground-based | satellite | operations, | ground | based | network | operations, | their | | | | |
| distribution | elements | and | user | access | and | support | systems. | | The | main | functional | elements | include |
| Mission | Management, | Enterprise | Management, | Data | and | Information | Management | and | | | | | |
| Distribution, | and | Infrastructure. | | | | | | | | | | | |
| The | term | “Information | System” | refers | to | a | discrete | set | of | information | resources | organized | for | the |
| collection, | processing, | maintenance, | use, | sharing, | dissemination, | or | disposition | of | information. | | | | | |
| [Note: | Information | systems | also | include | specialized | systems | such | as | industrial/process | controls | | | | |
| systems, | telephone | switching | and | private | branch | exchange | (PBX) | systems, | and | environmental | | | | |
| control | systems.] | | (44 | U.S.C., | Sec. | 3502: | USCODE-2009-title44-chap35-subchapI-sec3502, | Public | | | | | | |
| Printing | and | Documents.) | | | | | | | | | | | | |
| The | term | “Information | Technology” | refers | to | any | equipment | or | interconnected | system | or | | | | | | | |
| subsystem | of | equipment | that | is | used | in | the | automatic | acquisition, | storage, | manipulation, | | | | | | | |
| management, | movement, | control, | display, | switching, | interchange, | transmission, | or | reception | of | data | | | | | | | | |
| or | information | by | the | executive | agency. | | For | purposes | of | the | preceding | sentence, | equipment | is | used | | | |
| by | an | executive | agency | if | the | equipment | is | used | by | the | executive | agency | directly | or | is | used | by | a |
| Contractor | under | a | contract | with | the | executive | agency | which: | (i) | requires | the | use | of | such | | | | |
| equipment; | or | (ii) | requires | the | use, | to | a | significant | extent, | of | such | equipment | in | the | performance | of | | |
| a | service. | | The | term | information | technology | includes | computers, | ancillary | equipment, | software, | | | | | | | |
| firmware, | and | similar | procedures, | services | (including | support | services), | and | related | resources. | (40 |
| U.S.C., | Sec. | 1401: | USCODE-1998-title40-chap25-sec1401, | Public | Buildings, | Property, | and | Works.) | | | |
| The | term | “firmware” | refers | to | software | or | set | of | instructions | programmed | on | a | hardware | device |
| that | provides | the | necessary | instructions | for | how | the | device | communicates | with | the | other | computer | |
| hardware. | | Firmware | is | considered | "semi-permanent" | because | it | remains | the | same | unless | updated | | |
| by | a | firmware | updater. | | | | | | | | | | | |
| The | term | “applicable | documents” | denotes | Government | prepared | and | controlled | documents | and | | |
| industry | standards | documents | that | levy | requirements | on | the | Contractor. | | The | Contractor | shall |
| comply | with | the | documents. | | | | | | | | | |
| The | term | “reference | documents” | denotes | documents | that | amplify | or | clarify | the | information | | | |
| presented | in | this | document, | and | the | Contractor | is | not | required | to | meet | any | requirements | listed |
| within | these | documents. | | | | | | | | | | | | |
| The | term | “CDRL” | refers | to | the | Contract | Deliverable | Requirements | List. | | A | specific | deliverable | on | | | | |
| that | list | will | be | identified | by | reference | that | begins | with | the | phrase | “CDRL-” | and | will | be | followed | by | a |
| CDRL | identifier. | | A | specific | CDRL | referenced | within | the | requirement | or | statement | will | have | an | | | | |
| associated | Data | Requirements | Document | (DRD) | that | specifies | the | requirements | for | that | particular | | | | | | | |
CDRL.
| The | term | “DRD-” | will | be | followed | by | an | identifier | and | is | a | Data | Requirements | Document | that |
| specifies | the | requirements | for | the | content | and | delivery | of | the | associated | CDRL. | | | | |
The term “shall” designates a requirement. The terms “will” and “is” designate statements of fact.
| The | term | “(TBS)” | is | an | acronym | for | “to | be | supplied” | and | identifies | missing | or | incomplete |
| information, | values, | or | data | needed | to | fulfill | a | requirement. | | | | | | |
The term “(TBD)” is an acronym for “to be determined” and identifies a missing requirement.
The terms “Government” and “Government personnel” means Federal Government employees.
The term “Government representatives” means Federal Government employees and support contractors.
| The | term | “support | contractors” | means | Government | Federally | Funded | Research | and | Development |
| Centers | (FFRDC) | and | Systems | Engineering | and | Technical | Assistance | (SETA) | support | contractors. |
The term “On-Site” refers to work being performed on Government-owned facilities.
The term “Off-Site” refers to work being performed on Contractor and non-Government facilities.
| The | term | “Mission” | refers | to | a | user | mission | platform/system | that | utilizes | communication | and |
| navigation | services. | | | | | | | | | | | |
The term “Customer” refers to any entity requiring communications and navigation services.
| The | term | “Mission | Support” | refers | to | the | nominal/routine | activities, | processes | and | procedures |
| required | to | provide | service | to | a | mission. | | | | | |
| The | use | of | the | term | “Electromagnetic | Spectrum” | instead | of | “Radio | Frequency” | (RF) | or | “Optical” | in |
| reference | to | communication | science | and | technologies | is | intended | to | broaden | the | potential | for | use | of |
| other | spectrum | in | addition | to | the | traditional | frequencies. | | | | | | | |
| The | term | “radiometric | tracking” | refers | to | the | specific | time | of | flight | and | frequency | change | due | to | | | |
| Doppler | shift | measurements | available | from | a | communications | link | and | the | angular | pointing | of | an | | | | | |
| antenna | for | receipt | or | transmit | of | the | signal. | | Time | of | flight | is | translated | to | a | measure | of | range; |
| Doppler | frequency | change | (or | sometimes | measured | as | carrier | phase | change) | translates | to | a | | | | | | |
| measure | of | velocity. | | | | | | | | | | | | | | | | |
| The | term | “navigation” | is | a | global | term | employed | to | capture | all | inputs, | processes, | and | outputs | used | | |
| in | the | act | of | developing | knowledge | of | an | object’s | position | and | velocity | at | a | given | time. | In | some |
| cases, | the | term | navigation | may | be | extended | to | include | the | orientation | of | the | object | in | three- | | |
| dimensional | space | at | a | given | time. | | Inputs | may | be | a | combination | of | measurements | from | several | | |
| sources | (e.g. | radiometric | tracking | from | a | communications | link, | relative | angles | between | celestial | | | | | | |
| objects, | environmental | models). | | Processes | are | varied | and | refer | to | the | algorithms | and | the | models | | | |
| for | dynamics, | environment, | and | measurements | used | to | estimate | the | object’s | state. | | Outputs | are | | | | |
| generally | the | object’s | state | and | other | estimated | variables | at | a | given | time. | | | | | | |
| The | term | “Maintenance” | refers | to | activities | performed | to | ensure | the | continued | operation | of | the | |
| system | and | to | ensure | overall | system | performance | meets | availability | and | proficiency | requirements. | | | |
| Hardware | maintenance | activities | may | include: | re-installation | and | modification | of | existing | | | | | |
| equipment; | preventive | and | corrective | maintenance, | and | replacement | of | equipment | as | needed | to | | | |
| maintain | original | hardware | configuration | functionality; | and | documentation | of | equipment | | | | | | |
| architecture | and | cabling | configurations. | | Hardware | maintenance | includes | mechanical | devices, | such | | | | |
| as | motor | assemblies. | | Software | (including | firmware) | maintenance | activities | may | include: | arranging | | | |
| vendor | maintenance | agreements | for | COTS | products, | corrective | maintenance | of | operational | custom | | | | |
| software | systems, | modifications | to | existing | operational | custom | software | systems, | supporting | test | | | | |
| and | integration | of | new | or | modified | software, | installation | of | software | products | and | patches, | | |
| documenting | software | changes | and | problems, | maintenance | of | operational | parameter | databases, | | | | | |
| maintaining | currency | of | software | licenses, | and | control | of | software | system | configurations. | | | | |
| Maintenance | of | all | types | is | necessary | to | ensure | continued | operations | of | the | system. | | Maintenance |
| includes | the | following | types: | | | | | | | | | | | |
| • Preventive | maintenance | – | activities | to | prevent | errors, | problems | or | failures | before | they | occur |
| • Corrective | maintenance | – | fixes | needed | as | a | result | of | system | discrepancies | | |
| The | term | “Sustaining | Engineering” | refers | to | activities | necessary | to | ensure | support | to | achieve | |
| readiness | and | performance | requirements | over | the | operational | life | of | the | ground | system | and | its |
| associated | supporting | infrastructure, | as | well | as | activities | associated | with | the | development | of | | |
| required | design | changes | to | resolve | operational | issues. | | It | includes | technical | tasks | (engineering | and |
| logistics | investigations | and | analyses) | to | ensure | continued | operation | and | maintenance | of | a | system | |
| with | managed | (i.e., | known) | risk. | | Sustaining | Engineering | involves | the | identification, | review, | | |
| assessment, | and | resolution | of | deficiencies | throughout | a | ground | system | and | its | associated | | |
| infrastructure | life | cycle. | | Sustaining | engineering | both | returns | a | system | to | its | baselined | configuration |
| and | capability, | and | identifies | opportunities | for | performance | and | capability | enhancements. | | It | | | |
| includes | the | measurement, | identification | and | verification | of | system | technical | and | supportability | | | | |
| deficiencies, | associated | root | cause | analyses, | the | evaluation | of | the | potential | for | deficiency | correction, | | |
| and | the | development | of | a | range | of | corrective | action | options. | | Sustaining | Engineering | also | includes |
| the | implementation | of | selected | corrective | actions | to | include | configuration | or | maintenance | | | | |
| processes, | and | the | monitoring | of | key | sustainment | health | metrics. | | This | includes: | | | |
| • Collection | and | triage | of | all | service | use | and | maintenance | data | | |
| • Analysis | of | failure | causes | and | effects, | reliability | and | maintainability | trends, | and | operational |
| usage | profiles | changes | | | | | | | | |
| • Root | cause | analysis | of | in-service | problems | (including | operational | risks, | deficiency | reports, |
| and | reliability | degradation) | | | | | | | | |
| • The | development | of | required | design | changes | to | resolve | operational | issues | |
| • Other | activities | necessary | to | ensure | support | to | achieve | readiness | and | performance |
requirements over the operational life of a ground system and its associated supporting infrastructure
| Results | of | Sustaining | Engineering | feed | forward | into | the | needs | definition | phase | of | major |
| enhancements, | typically | associated | with | a | new | development | task | order. | | | | |
The term “Development” refers to the creation and implementation of a major new capability or capacity.
| The | following | table | further | clarifies | the | distinctions | among | Maintenance, | Sustaining | Engineering, |
| and | Development | activities | for | each | system | element. | | | | |
| Element | Maintenance | Sustaining | Engineering | Development |
| Hardware | • Corrective | and | emergency | |
| actions | to | identify | and | remove |
| defects | in | hardware | | |
components
| • Replace | hardware, | or | |
| components, | with | spares | or |
| similar | components | | |
| • Replace | hardware | or | upgrade |
| to | new | versions | |
| • Perform | hardware | | |
| preventative | maintenance | on | |
| mechanical | equipment | | |
| accordance | with | maintenance | |
manual
| • Technology | refresh | | |
| • Design | and | documentation | of |
| configuration | changes | to | |
| support | maintenance | | |
| activities | (e.g. | Engineering | |
Changes)
| • Major | improvements | |
| driven | by | new |
| requirements | in | |
performance, dependability,
| maintainability | or | |
| addition | of | new |
capability
| • Implementation | of | new |
| systems, | testing, | |
| integration, | verification | |
| and | validation, | and |
training
| Software | • Corrective | and | emergency | |
| actions | to | identify | and | remove |
| defects | in | system | and | |
| application | software | | | |
| • Updates | system | and | | |
| applications | software | versions | | |
| • Preventive | actions | to | identify | |
| and | correct | latent | faults | |
| • Minor | system | and |
| application | software | |
| enhancements | to | improve |
performance
| • Minor | improvements | in |
| performance, | dependability, | |
maintainability
• New or enhanced products
| • Major | improvements | |
| driven | by | new |
| requirements | in | |
performance, dependability, maintainability
| Element | Maintenance | Sustaining | Engineering | Development |
| • Maintain | ability | to | “build” | |
| operational | applications | in | | |
| baseline | environment | | | |
| • Adapt | systems | and | | |
| application | software | to | new | |
| hardware | components | | | |
| • Updates | tables | | | |
| • Design | and | documentation | of |
| software | configuration | | |
| changes | to | support | |
| maintenance | activities. | | |
| • System | and | application | |
| software | enhancements | to | |
| improve | performance | or | |
| introduce | new | capability | |
| • Addition | of | new |
| functionality | or | |
capability
Local Area Networks
| • Help | desk | response | |
| • Upgrade | local | area | networks |
| to | support | evolving | technology |
| • Preventive | maintenance | | |
| • Network | administration | and | |
configuration
• Add switches/routers
• Establishing or combining networks
| • Upgrading | bandwidth | and | |
| capability | to | handle | new |
missions
| • Performance | monitoring | | |
| • Trend | analysis | | |
| • Root | cause | determination | |
| • Recommendations | for | larger | |
| sustainment | actions | (e.g. | |
| network | “State | of | Health” |
assessments)
| • Develop | new | local | area |
| networks | for | new | major |
| capabilities | or | | |
capacities
System Admin-istration
| • Apply | Patches | | | | |
| • Upgrade | to | new | version | of | OS |
| • Tune | system | performance | | | |
| • Manage | installation | and | | | |
| integration | or | system | fixes, | | |
| updates | and | enhancements | | | |
• Technology refresh
| • Conduct | system |
| administration | for |
| development | activities |
| Appendix | B. | Applicable | Documents | | | |
| Document | # | Title | | | | |
| Human | Space | Flight | (HSF) | Management | Plan |
User Guide for National Aeronautics and Space Administration
| Task | Order | Management | System | | | | |
| NASA | Fault | Tree | Handbook | with | Aerospace | Applications |
(http://www.hq.nasa.gov/office/codeq/doctree/fthb.pdf) IEC TR 62380 model is based on the Reliability Data Handbook
| - | Universal | Model | for | Reliability | Prediction | of | Electronic |
| Components, | PCBs, | and | Equipment, | published | by | the | |
| International | Electrotechnical | Commission | (IEC) | | | | |
| Chinese | standard | GJB/z | 299B, | Reliability | Prediction | Model | for |
| Electronic | Equipment | | | | | | | |
GSFC Code 322 Failure Mode and Effects Analysis guidance documentation
400-PG-8621.1.1 Anomaly Notification System for Code 400 Programs and Projects
| 450_1-NOSP-X | Network | Operations | Support | Plan | (NOSP) | (Multiple: | Aqua, |
| Aura, | Balloon | Program, | COSMIC, | DSCOVR, | FGST, | GRACE, | IRIS, |
| Landsat-8, | LOR, | MetOp, | MMS, | NPP, | NuStar, | OCO-2, | QuikSCAT, |
| RBSP, | SCaN | Testbed, | SMAP, | Solar-B | (HINODE), | SWIFT, | TDRS, |
THEMIS)
| 450-215 | EO-1 | DCN | 001 | 450-215 | EO-1 | Document | Change | Notice | 001 |
| 450-AGMT-0020 | (Expires | | | | | | | | |
6/2019)
| Memorandum | of | Agreement | (MOA) | between | 36th | Air | Base | |
| Wing, | Pacific | Air | Forces | and | NASA's | GSFC | (Concerning | PMEL |
| Support | of | NASA's | GRGT | Equipment) | | | | |
| 450-CONOPS-X | 450-CONOPS | (Multiple: | DSCOVR, | GOES-R, | MMS, | SMAP) |
| 450-DMR-TIMED | R2 | 450-Detailed | Mission | Requirements-TIMED | R2 | |
| 450-ISI-X | 450-Interim | Support | Instruction: | (Multiple: | C_NOFS | |
| Termination, | GPM) | | | | |
| 450-NRD-X | 450-Network | Requirements | Document | (Multiple: | Balloon |
| Program, | DSCOVR, | GOES-R, | ICESat-2, | ICON, | JPSS-1, | MMS, | OCO- |
| 2, | SMAP) | | | | | | |
| 450-OIP-WSC/DSMC | White | Sands | Complex | (WSC)/Data | Services | Management |
| Center | (DSMC) | Operations | Interface | Procedures | (OIP) | |
| 450-OPN-IRIS | 450-OPN-IRIS | | | | | | | |
| 450-PG-1310.1.1 | Networks | Integration | Process | | | | | |
| 450-PG-1310.1.3 | Space | and | Near | Earth | Networks | Priority | List | Process |
| 450-PG-1410.2.1 | 450/ESC | - | Configuration | Management | Procedure | | | |
| 450-PLAN-0007 | Exploration | and | Space | Communications | (ESC) | Projects | Division | |
| Risk | Management | Plan | (RMP) | | | | |
| 450-PROC-CTP/SN/NEN | Radio | Frequency | (RF) | Compatibility | Test | Procedures | between |
| Spacecraft | and | the | Space | Network | (SN) | and/or | Near | Earth |
| Network | (NEN) | | | | | | | |
| 450-PSLA-X | 450-Project | Service | Level | Agreement | (Multiple: | COSMIC, | |
| DSCOVR, | GOES-R, | GRACE, | GRACE-FO, | HST, | ICESat-2, | ICON, | |
| JPSS-1, | JWST, | MMS, | OCO-2, | SMAP, | Solar-B | (HINODE), | STPSat-5, |
| SWIFT, | TESS, | Van | Allen | Probes) | | | |
| 450-RFICD-X | (SBU) | 450-Radio | Frequency | Interface | Control | Documents | (Sensitive |
| But | Unclassified) | (Multiple: | ACE_Near | Earth | Network_R1, | | |
| BP_Space | Network | Document | Change | Notice | 002, | CPOD_Near | |
| Earth | Network, | DSCOVR_Near | Earth | Network_Deep | Space | | |
| Network_Space | Network_R1, | GOES | R-U_Near | Earth | | | |
| Network_D1, | GPM_Space | Network_Near | Earth | Network | R1D1, | | |
| GRACE-FO_Near | Earth | Network, | GRACE-GN | Document | Change | | |
| Notice | 001, | ICESat-2_Near | Earth | Network_Space | Network | | |
| (final), | ICON_Near | Earth | Network_Space | Network, | JPSS-1_Space | | |
| Network_Near | Earth | Network, | JWST_Space | Network_R1, | | | |
| MMS_Deep | Space | Network_Near | Earth | Network_Space | | | |
| Network_R1, | MTRS_Space | Network, | NEOWISE_Space | Network | | | |
| Document | Change | Notice | 002, | OCO-2_Near | Earth | | |
| Network_Space | Network_D3, | RHESSI_Near | Earth | Network, | | | |
| SMAP_Near | Earth | Network_Space | Network_R1, | STPSat-5_Near |
| Earth | Network, | TESS_Space | Network) | |
| 450-SARD-X | 450-Service | Agreement | Requirements | Document | (Multiple: | | |
| AIM, | Aura, | CPOD, | GOES_13-15, | GPM, | Landsat-7, | RHESSI, | SDO, |
SPTR-2)
| 450-SNUG | Space | Network | Users | Guide | SBU | | |
| 450-SPEC-CTL | 450-Space | and | Near | Earth | Networks | Compatibility | Test |
| Laboratory | Specifications | | | | | |
| 450.1-LIST-NEN/Priority | Near | Earth | Network | (NEN) | Priority | List |
| 450.1-LIST-SN/Priority | Space | Network | Priority | List | | |
| 450.1-WI-1310.1.10 | Networks | Services | Request | Process | | |
| 450.1-WI-1310.1.11 | Radio | Frequency | Compatibility | Test | Plan/Report | |
| 450.1-WI-1310.1.12 | Networks | Integration | Management | Office | (NIMO) | Lessons |
| Learned | Process | | | | | |
| 450.1-WI-1310.1.13 | Networks | Integration | Management | Office | (NIMO) | Post-Mission |
| Report | Process | | | | | | |
| 450.1-WI-1310.1.1 | Networks | Integration | Management | Office | (NIMO) | Mission | Set |
Maintenance
| 450.1-WI-1310.1.2 | Project | Service | Level | Agreement | (PSLA) | Process | | | |
| 450.1-WI-1310.1.4 | Networks | Integration | Management | Waiver | Process | | | | |
| 450.1-WI-1310.1.5 | Network | Operations | Support | Plan | (NOSP) | Process | | | |
| 450.1-WI-1310.1.6 | Networks | Feasibility | Analysis | | | | | | |
| 450.1-WI-1310.1.7B | Mission | Operations | Readiness | Review | (MORR) | Process | | | |
| 450.1-WI-1310.1.8 | Network | Requirements | Document | (NRD) | Process | | | | |
| 450.1-WI-1310.1.9A | Networks | Integration | Scheduling | | | | | | |
| 452-PLAN-SOAR | Spacecraft | On-orbit | Anomaly | Report | (SOAR) | Process | | | |
| 453-NENUG | Near | Earth | Network | (NEN) | Users' | Guide | | | |
| 453-UG-NEN-Scheduling | Users’ | Guide | for | Near | Earth | Network | Scheduling | | |
| AC | No: | 70-1 | Federal | Aviation | Administration | Advisory | Circular | on | Outdoor |
| Laser | Operations | | | | | | | | |
| Alert_No. | Alert | Notices | | | | | | | |
| ANSI/ESD | S20.20-2014 | Protection | of | Electrical | and | Electronic | Parts, | Assemblies | and |
| Equipment | [Excluding | Electrically | Initiated | Explosive | Devices] | | | | |
| ANSI/NCSL | Z540.1-1994 | Calibration | Laboratories | & | Measuring | & | Test | Equipment | - |
| General | Requirements | | | | | | | | |
| ANSI/NCSL | Z540.3-2006 | Requirements | for | the | Calibration | of | Measuring | and | Test |
Equipment
| ASTM | E1527-13 | | Phase | I | Environmental | Site | Assessment | |
| CCSDS | 311.0-M-1 | CCSDS | Reference | Architecture | for | Space | Data | Systems |
(http://www.ccsds.org)
CFR-2009-title48-vol1-part46
| Federal | Acquisition | Regulations, | paragraphs | Parts | 46.103, |
| 46.104, | 46.202-2, | 46.4, | and | 46.5 | |
| CFR-2011-36-V3-1194 | CFR-2011-title36-vol3-part1194—Electronic | and | Information | |
| Technology | Accessibility | Standards: | Final | Rule |
| CMMI-Dev | CMMIR | For | Development | | | | | | |
| CMMI-Dev, | Errata | CMMIR | For | Development, | Errata | | | | |
| CNSSP | No. | 11 | National | Policy | Governing | the | Acquisition | of | Information |
Assurance (IA) and IA-Enabled Information Technology Products
Consldtd Lsr Rngng Frmt (CRD)_v1.01
Consolidated Laser Ranging Data Format (CRD)
CPR_DID-MGMT-
| 81466_Forms | Instructions | | | |
| for | the | CPR | Formats | 1 |
Instructions for the CPR Formats 1 -https://acc.dau.mil/CommunityBrowser.aspx?id=19544
CPR_DID-MGMT-
81466_Forms
Excel spreadsheet of CPR Formats -https://acc.dau.mil/CommunityBrowser.aspx?id=19543
| CSFC | Commercial | Solutions | for | Classified | (CSfC) | Customer | Handbook | |
| DHS | -USCIUS | Form | I-9 | Instructions | for | Employment | Eligibility | Verification |
| DI-IPSC-81427 | Software | Development | Plan | | | | | |
| DI-IPSC-81431 | System/Subsystem | Specification | (SSS) | | | | | |
| DI-IPSC-81432 | System | Design | Description | | | | | |
| DI-IPSC-81433 | System | Requirements | Specification | (SRS) | | | | |
| DI-IPSC-81434 | Interface | Requirements | Specification | (IRS) | | | | |
| DI-IPSC-81435 | Software | Design | Description | (SDD) | | | | |
| DI-IPSC-81436 | Interface | Design | Description | (IDD) | | | | |
| DI-MGMT-81466 | Contract | Performance | Report | | | | | |
| DI-MGMT-81644 | DoD | Architecture | Framework | Documentation | | | | |
| DOD-5220-22-M | National | Industrial | Security | Program | Operating | Manual | | |
(NISPOM)
| DRD002402 | Monument | Peak | Use | Permit | thru | 2020 | | | |
| DSCOVR | NFA | Tasking | Memo | DSCOVR | NFA | Tasking | Memo | | |
| ECSS-E-10 | Space | Engineering | System | Engineering | | | | | |
| ECSS-Q-ST-40-02 | Space | Product | Assurance | – | Hazard | Analysis | | | |
| ECSS-Q-ST-40 | Space | Product | Assurance: | Safety | | | | | |
| ECSS-Q-ST-70-10 | Qualification | of | Printed | Circuit | Boards | | | | |
| Exec. | Order | 12114 | Environmental | Effects | Abroad | of | Major | Federal | Actions |
| FAR | 18-001 | Emergency | Acquisitions | | | | | | |
| FAR | Part | 45 | Government | Property | | | | | |
(https://www.acquisition.gov/far/current/html/FARTOCP45.h tml)
FAR Subpart 42.5 Federal Acquisition Regulations, Subpart 42.5 (https://www.acquisition.gov/far/html/Subpart%2042_5.html
| FDCC | USGCB | From | Federal | Defense | Corporate | Council | (FDCC) | to | United |
| States | Government | Configuration | Baseline | (USGCB): | Managing | | | | |
the Transition to a New Federal Government Security Mandate (https://usgcb.nist.gov/)
| FIPS-PUB-199 | Standards | for | Security | Categorization | of | Federal | Information |
| and | Information | Systems | | | | | |
| FIPS-PUB-200 | Minimum | Security | Requirements | for | Federal | Information | and |
| Information | Systems | | | | | | |
FISMA Public Law 113–283
Federal Information Security Modernization Act (FISMA) of
| GEIA-STD-0005-1 | Performance | Standard | for | Aerospace | and | High | Performance |
| Electronic | Systems | Containing | Lead-free | Solder | | | |
| GEIA-STD-0005-2 | Standard | for | Mitigating | the | Effects | of | Tin | Whiskers | in |
| Aerospace | and | High | Performance | Electronic | Systems | | | | |
| GPD | 7120.1 | Goddard | Space | Flight | Center | (GSFC) | Policy | Directive | (GPD): |
| Space | Asset | Protection | Policy | | | | | | |
| GPD | 8500.1 | GPD: | Environmental | Policy | and | Program | Management | | | | |
| GPR | 1860.2 | Laser | Radiation | Protection | | | | | | | |
| GPR | 4100.2 | Hazardous | Material | Data | Management | | | | | | |
| GPR | 6400.1 | Logistics | Support | | | | | | | | |
| GPR | 7120.4 | Risk | Management | | | | | | | | |
| GPR | 7123.1 | Systems | Engineering | | | | | | | | |
| GPR | 8500.1 | Environmental | Planning | and | Impact | Assessment | | | | | |
| GPR | 8500.3 | Waste | Management | | | | | | | | |
| GPR | 8500.4 | Air | Quality | Management | Program | | | | | | |
| GPR | 8500.5 | Water | Management | | | | | | | | |
| GPR | 8500.8 | Site | Investigation | and | Remediation | | | | | | |
| GPR | 8700.6 | Engineering | Peer | Reviews | | | | | | | |
| GSFC | 23-35 | LU | Laser | Radiation | Source | Personnel | Approval | | | | |
| GSFC | 23-6L | Laser | Radiation | Source | Use | Approval | (2 | files | - | Monument | Peak |
| and | Greenbelt) | | | | | | | | | | | | |
| GSFC | 5x5 | Risk | Matrix | GSFC | 5x5 | Risk | Matrix | For | Class | A-C | Type | Missions | (NASA |
| provided | definitions | of | likelihood | and | severity | for | risks | and |
| their | categories) | | | | | | | |
| HRD5 | Handbook | for | Reliability | Data | for | Electronic | Components | used |
| in | Telecommunications | Systems, | Developed | by | British | | | |
| Telecommunications | plc | | | | | | | |
(https://www.tib.eu/en/search/id/TIBKAT%3A184134048/H andbook-of-reliability-data-HRD5-for-electronic/)
IEEE 730-2014 IEEE Standard for Software Quality Assurance Plans (http://www.ieee.org/)
| IEEE | Std | 1413-1998 | IEEE | Standard | Methodology | for | Reliability | Prediction | and |
| Assessment | for | Electronic | Systems | and | Equipment | | | | |
(http://www.ieee.org/)
| IPC-J-STD-001F | Space | Applications | Electronic | Hardware | | |
| IPC-J-STD-001FS | Joint | Industry | Standard, | Space | Applications | Electronic |
Hardware Addendum (except Chapter 10 of IPC-J-STD-001F)
| IPC/WHMA-A-620AS | Requirements | and | Acceptance | for | Cable | and | Wire | Harness |
| Assemblies, | Space | Addendum | | | | | | |
| ISO | 17025-2005 | General | requirements | for | the | competence | of | testing | and |
| calibration | laboratories | | | | | | | | |
(http://www.iso.org/iso/catalogue_detail?csnumber=39883)
| IVS | TOW | 2105 | VLBI | Pre-Checks | and | Operations | Manual | |
| TL-MAN-0002 | United | States | Antarctic | Program | - | Packing | & | Shipping |
Instructions
| M4FR1 | | MOBLAS | 4 | Infrastructure | Requirements | | | |
| MIL-HDBK-217F | Reliability | Prediction | of | Electronic | Equipment | | | |
| MIL-HDBK-472 | Maintainability | Prediction | | | | | | |
| Mil-STD-1629A | Procedures | for | Performing | a | Failure | Mode, | Effects | and |
| Criticality | Analysis | | | | | |
| MIL-STD-2073-1 | Standard | Practice | for | Military | Packing | |
| MIL-STD-756B | Reliability | Prediction | | | | |
| MIL-STD-882E | Standard | Practice | for | System | Safety | |
| MIL-STD-961E | Defense | and | Program-Unique | Specifications | Format | and |
Content
| MMS | Certification | Report |
| for | Santiago | |
| Hartebeesthoeck | Ground | |
| Stations | (final) | |
| MMS | Certification | Report | for | Santiago | Hartebeesthoeck | Ground |
| Stations | (final) | | | | | |
| MOBLAS | 7 | 04-0034b | GSFC |
| 23-28L | 532nm | | |
| Request | for | Radiation | Safety | Committee | Action | – |
| Laser | Radiation | Source | Questionnaire: | MOBLAS | 7 | 04-0034b |
| GSFC | 23-28L | 532nm | | | | |
| NASA | Conjunction | |
| Assessment | Risk | Analysis |
(CARA)
NASA Conjunction Assessment Risk Analysis (CARA):
https://spaces.gsfc.nasa.gov/display/CODE595/Conjunction+A ssessment+Risk+Analysis+(CARA)
| NASA | FMM | Volume | 9000: |
| Principles | and | General | |
Policies
| NASA | Financial | Management | Manual | (FMM) | Volume | 9000 |
| Chapter | 9060 | (https://www.hq.nasa.gov/fmm/fmmintro.htm) | | | | |
| NASA | FMM | Volume | 9100: |
| Agency | Coding | Structure | |
| NASA | Financial | Management | Manual | (FMM) | Volume | 9100 |
| Chapter | 9060 | (https://www.hq.nasa.gov/fmm/fmmintro.htm) | | | | |
| NASA | IT-HBK-2841-002 | Identity, | Credential, | and | Access | Management | (ICAM) | Services |
| NASA-SP-2007-6105 | NASA | Systems | Engineering | Handbook | | | | |
| NASA-SP-2010-3403 | | NASA | Schedule | Management | Handbook | | | |
| NASA-STD-2804 | Minimum | Interoperability | Software | Suite | | | | |
| NASA-STD-2805 | Minimum | Hardware | Configurations | | | | | |
| NASA-STD-6016 | Standard | Materials | and | Processes | Requirement | for | Spacecraft | |
| NASA-STD-8719.13 | Software | Safety | Standard | | | | | |
| NASA-STD-8719.14 | Process | for | Limiting | Orbital | Debris | | | |
| NASA-STD-8719.7-1 | (in | | | | | | | |
| three | parts: | Chapter | 1 | to | 6, | | | |
| Chapter | 7 | to | App | C, | and | | | |
| Appendix | D) | | | | | | | |
Facility System Safety Guidebook
| NASA-STD-8719. | Lifting | Standard | | | | | | |
| NASA-STD-8729.1 | Planning, | Developing | and | Managing | an | Effective | Reliability | and |
| Maintainability | (R&M) | Program | | | | | |
| NASA-STD-8739.1 | Workmanship | Standard | for | Polymeric | Application | on | Electronic |
Assemblies NASA-STD-8739.4 Workmanship Standard for Crimping, Interconnecting Cables,
| Harnesses, | and | Wiring | w/Change | 6 | | | |
| NASA-STD-8739.5 | Workmanship | Standard | for | Fiber | Optic | Terminations, | Cable |
| Assemblies, | and | Installation | | | |
| NASA-STD-8739.6 | Implementation | Requirements | for | NASA | Workmanship |
Standards
| NASA-STD-8739.8 | Software | Assurance | Standard | w/Change | 1 |
| NEPA | National | Environmental | Policy | Act | |
| NFS | 1852.204-76 | NOTE: | | | |
| This | is | a | clause | | |
Security Requirements for Unclassified Information Technology Resources (https://www.hq.nasa.gov/office/procurement/regs/5200- 11.htm#sec1852_203_76)
NFS Part 1845 Government Property (https://www.hq.nasa.gov/office/procurement/regs/1845.ht m)
| NHPA, | Section | 106 | Section | 106 | of | the | National | Historic | Preservation | Act |
| NIAP | PP | National | Information | Assurance | Partnership | (NIAP) | Protection | | | |
| Profiles | (PP) | (https://www.niap-ccevs.org/Profile/PP.cfm) | | | | | | | | | |
| NID | 1600.55 | Sensitive | But | Unclassified | (SBU) | Controlled | Information | | | | |
| NID | 8000.108 | Agency | Risk | Management | Procedural | Requirements | | | | | |
| NIST | 800-30 | NIST, | Guide | for | Conducting | Risk | Assessments | | | | |
This is the start of the file's text. The full file is on GovTribe.