EverySpec Logo
Your free source for specifications, standards, and handbooks

TORs

AEROSPACE REPORT NUMBER: TOR-2004(3909)-3537 (REV. B). SOFTWARE DEVELOPMENT STANDARD FOR SPACE SYSTEMS (11 MAR 2005)
Ident. Num:
TOR-2004(3909)-3537 
  Rev. Num:

AEROSPACE REPORT NUMBER: TOR-2004(3909)-3537 (REV. B). SOFTWARE DEVELOPMENT STANDARD FOR SPACE SYSTEMS (11 MAR 2005). This Technical Operating Report (TOR) contains a standard for the software development process intended for use on SMC and NRL contracts as a compliance document. It can be applied in any phase of the system life cycle. It contains the requirements for developing, modifying, and documenting software. It defines standard terminology and captures the activities, tasks, and products for a software development or maintenance project. It can be applied to any type of software, including application software, the software portion of firmware, reusable software, etc.
AEROSPACE REPORT NUMBER: TOR-2005(8583)-2, ELECTRICAL POWER SYSTEMS, DIRECT CURRENT, SPACE VEHICLE DESIGN REQUIREMENTS (11 MAY 2005)
Ident. Num:
TOR-2005(8583)-2 
  Rev. Num:

AEROSPACE REPORT NUMBER: TOR-2005(8583)-2, ELECTRICAL POWER SYSTEMS, DIRECT CURRENT, SPACE VEHICLE DESIGN REQUIREMENTS (11 MAY 2005). This standard establishes requirements for direct current (DC) electrical power systems (EPS) for space vehicles. This standard ensures compatibility between the space vehicle DC EPS and all its interfaces, including the utilization equipment. It also ensures that the space vehicle will not be damaged or degraded by certain unintended or anomalous conditions, as described herein.
AEROSPACE REPORT NUMBER: TOR-2005(8583)-3 (REV. A), SYSTEMS ENGINEERING REQUIREMENTS AND PRODUCTS (29 SEP 2005)
Ident. Num:
TOR-2005(8583)-3 
  Rev. Num:

AEROSPACE REPORT NUMBER: TOR-2005(8583)-3 (REV. A), SYSTEMS ENGINEERING REQUIREMENTS AND PRODUCTS (29 SEP 2005). This Technical Operating Report (TOR) specifies requirements for the conduct of a complete, integrated systems engineering effort, not a specific systems engineering model or method of implementation. Integration of a comprehensive technical effort will also include requirements from other technical documents selected for contractual implementation to satisfy program requirements and to comply with DOD policy. These requirements provide a robust systems engineering approach that balances total system performance and total ownership costs within the family-of-systems and systems-of-systems context. This document is intended to govern the execution of systems engineering when levied on contractors as a compliance document. These requirements constitute the government’s requirements for an executable contractor systems engineering efforts to assist in defining, performing, managing, and evaluating systems engineering efforts in defense system acquisitions and technology developments. Systems engineering is described in terms of what must be done, not how to do it. The requirements in this document, including those for systems engineering management, are delineated in terms of the required systems engineering tasks, products and the required attributes of those products. This document may need to be tailored to ensure that only necessary and appropriate requirements are cited in specific solicitations and contracts. Tailoring guidance can be found in MIL-HDBK-248, Acquisition Streamlining, and in paragraph 6.3 of this document. This document also provides a reference to the government, or other customers, for analyzing competing contractor proposals and for evaluating the contractor’s systems engineering products once on contract. The customer will perform initial tailoring of this document to address appropriate program scope, appropriate program size, and progress within the acquisition life cycle. This TOR and tailoring, if any, will be part of the draft and final Requests for Proposal (RFP) along with instructions for contractors to perform further tailoring as part of their proposal submittals.
AEROSPACE REPORT NUMBER: TOR-2005(8583)-3, SYSTEMS ENGINEERING (DRAFT) (15 APR 2005)
Ident. Num:
TOR-2005(8583)-3 
  Rev. Num:

AEROSPACE REPORT NUMBER: TOR-2005(8583)-3, SYSTEMS ENGINEERING (DRAFT)(15 APR 2005). This TOR contains a new draft version of MIL-STD-499, Systems Engineering. It incorporates suggested revisions to the MIL-STD-499 and the "B" revision to that document, which was never officially released. It was prepared by an SM team that included Aerospace, government, SETAs, and independent consultants. This draft has had only limited review by SMC SPOs and industry. This draft is being published at this teime to support near-term SMC acquisitions with the intent of using it as a compliance standard.
AEROSPACE REPORT NUMBER: TOR-2006(8583)-5236, TECHNICAL REQUIREMENTS FOR ELECTRONIC PARTS, MATERIALS, AND PROCESSES USED IN SPACE AND LAUNCH VEHICLES
Ident. Num:
TOR-2006(8583)-5236 
  Rev. Num:

AEROSPACE REPORT NUMBER: TOR-2006(8583)-5236, TECHNICAL REQUIREMENTS FOR ELECTRONIC PARTS, MATERIALS, AND PROCESSES USED IN SPACE AND LAUNCH VEHICLES (13 NOV 2006). The requirements of this document were developed for long mission life and/or high reliability space and launch vehicle equipment for successful operations of space hardware. Attention to every detail is required at every level of assembly throughout development, manufacture, qualification, and testing, starting with the parts, materials, and processes used. This document supersedes Aerospace Technical Operating Report TOR-2004(3909)-3316, titled Technical Requirements for Electronics Parts, Materials, and Processes Used in Space and Launch Vehicles, and shall be used for all future procurements of space, launch, and experimental programs. The objective of this document is to specify the technical baseline in the selection, application, procurement, control and standardization of parts (electrical and mechanical), materials, and processes for space and launch vehicles. This TOR is intended to be used in conjunction with TOR-2006(8583)-5235 (Parts, Materials, and Processes Control Program for Space and Launch Vehicles) in order to achieve a high reliability space program. Every effort was made to utilize standard document format, but this document retains the separately called out technical sections (starting with Section 100) to focus the user industry on the unique space quality items that are paramount for mission success in each technical section.
AEROSPACE REPORT NUMBER: TR-2004(8583)-1 REV.A, (SMC-TR-06-11) TEST REQUIREMENTS FOR LAUNCH, UPPER-STAGE, AND SPACE VEHICLES (6 SEP 2006)
Ident. Num:
TR-2004(8583)-1 
  Rev. Num:

AEROSPACE REPORT NUMBER: TR-2004(8583)-1 REV.A, (SMC-TR-06-11) TEST REQUIREMENTS FOR LAUNCH, UPPER-STAGE, AND SPACE VEHICLES (6 SEP 2006)., This Standard establishes the environmental and structural ground testing requirements for launch vehicles, upper-stage vehicles, space vehicles, and their subsystems and units. In addition, a uniform set of definitions of related terms is established. This Standard is applicable to the procurement of space system hardware as a compliance document for the establishment of baseline test requirements. The test requirements herein focus on design verification and the elimination of latent defects to help ensure a high level of confidence in achieving successful space missions. Revision A to TR-2004(8583)-1, the proposed Military Standard 1540E, is being released to capture clarifications, corrections and changes identified by the user community during the initial implementation of the document for the acquisition of space systems. The modifications contained in this revision are not intended to impact the requirements of the original version of this document. The applicable documents section (2.1) has been updated to reflect the latest versions of the referenced documents. It had extensive review by SMC, NRO, NASA, and industry. It is being published at this time to support near-term government acquisitions with the intent of using it as a compliance document and to provide the basis for the updated Military Standard 1540 (Revision E).


EverySpec powered by Epiware document management software contact: jimkern@everyspec.com Valid HTML 4.01 Strict