Definition General Info Policies Guides Communities Training Related
DEFINITION
Describe system-unique requirements, management responsibilities, and procedures used to ensure that PHS&T requirements are identified and met in a timely manner during the acquisition process.
GENERAL INFORMATION/NARRATIVE
Packaging and Handling Requirements: The PHS&T concept describes any anticipated special considerations for the packaging, handling, storage and transportability required for deployment and sustainment of the system. as well as the process for determining these requirements. The operational environment conditions (temperature, humidity, etc.) and potential for use of hazardous materials must be considered. The PHS&T concept is developed by the combat developer in coordination with the materiel developer and must be described in the capabilities document.
Describe anticipated PHS&T modes and constraints.
Identify system, component, part, and test equipment/TPS environmental storage and climatic requirements (for example, humidity and static control and grounding requirements).
Summarize actions necessary to resolve logistic problem areas identified, to include the tradeoffs of PHS&T requirements and risk areas.
Describe PHS&T assets required and those expected to be available at first unit equipped.
Identify current and projected changes of PHS&T systems and procedures. Determine the interface with PHS&T equipment undergoing parallel development or testing.
Verify PHS&T test requirements have been identified and included in the TEMP.
Identify PHS&T requirements for shipment of equipment and ASIOE to CONUS and overseas commands, including special PHS&T requirements of participating services.
Identify special care required during PHS&T (that is, removal of sensitive components, calibration, special PHS&T requirements during repair and movement).
Identify actions taken to determine if containers are or will be available for system shipment.
List the supply bulletin number(s) of the storage serviceability standard that is appropriate for the materiel system. If none is required, so state.
Describe any unique transportation and transportability responsibilities, requirements, and constraints, including those related to unit and force deployability. Identify required strategic and tactical transport modes and aircraft and rail/road/water vehicle type. Identify user transportability limitations and restrictions including container compatibility. When appropriate, discuss design or performance tradeoffs for mobility, transportability, and rapid deployment. This should also include transportation requirements for ASIOE, TMDE, parts, and BSM (ammunitions, POL, and so on).
Identify requirements for development of a transportability request (using the LMI data, transportability engineering characteristics, and DODI 4540.7 ), to be submitted to the MSDDC Transportation Engineering Agency for approval. Include this request (and subsequent transportability approval) as an annex to the SS. Summarize actions necessary to resolve problem areas.
Describe current transportation assets and those expected to be available at FUE and identify current and projected changes to transportation systems and procedures. Determine the interface with new equipment undergoing parallel development or testing.
Identify transportability test requirements for inclusion in the TEMP.
In coordination with SDDC, record if a transportability guidance TM is required, and who will prepare the manual.
For systems being acquired for multiservice use: (1) identify transportability requirements for shipment of equipment to CONUS and overseas commands, including special requirements of participating services, (2) describe loading and unloading configuration layout by appropriate aircraft type when air transportation is to be used. Include weight and cube; (3) identify lifting/tie-down requirements and procedures to ensure these will be included in final system configuration.
GEIA-STD-0007 Interface: H Entities, Provisioning and Cataloging Requirements. The "H" data Entities are used to document packaging/provisioning data requirements. Included in these Entities are static parts data (non-application dependent) related to provisioning screening and cataloging, packaging, handling, storage and common maintenance data. Also included under these data Entities are application data of items used to document the data required for initial support requirements determination, repair parts manuals, and design change information. J Entities, Transportability Requirements. Data Entities beginning with "J" in the first position of the entity name are structured to capture the information pertaining to the transportability shipping modes and to the transported end item. In the event that the end item is sectionalized for transport, the information shall be completed for each section of the end item.
POLICIES, DIRECTIVES, REGULATIONS, LAWS
BEST PRACTICES, LESSONS LEARNED, STORIES, GUIDES, HANDBOOKS, TEMPLATES, EXAMPLES, TOOLS
COMMUNITIES OF PRACTICE
TRAINING RESOURCES
RELATED ARTICLES
Definition General Info Policies Guides Communities Training Related