定价： 605元 / 折扣价： 515 元 加购物车

1.1 This document specifies quality assurance requirements for additive construction (AC) concerning building and construction projects in which additive manufacturing techniques are used for construction. The requirements are independent of the material(s) and process category used.1.2 This document does not apply to metals.1.3 This document specifies the criteria for additive construction processes, quality-relevant characteristics, and factors along AC system operations. It further specifies activities and sequences within an AC cell (additive construction site) and project.1.4 This document applies to all additive manufacturing technologies in building and construction (load bearing and non-load bearing), structural and infrastructure building elements for residential and commercial applications and follows an approach oriented to the process.1.5 This document does not cover environmental, health and safety aspects that apply to printing facility setup, material handling, operating of robotic equipment, and packing of equipment and/or elements for shipping but material supplier guidelines, robotic solution operating guidelines, and local and regional requirements are applicable.1.6 This document does not cover design approvals, material properties characterization and testing.1.7 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.1.8 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

定价： 843元 / 折扣价： 717 元 加购物车

4.1 Purpose—This practice provides a framework for an authority to assess, plan, and execute: (1) the construction of new systems of tangible and intangible infrastructure; and (2) operate, maintain, monitor, and repair existing systems of infrastructure assets so as to maximize their use value by providing desired services for the benefit of infrastructure asset service recipients of the authority’s unit of government or private sector organization.4.2 How to Use Information—The information generated by this practice is used to assess the quality and frequency of delivered infrastructure asset services, which then provides the basis for changing the amounts or proportions of funding for one, many, or all types of infrastructure assets in the subsequent cycle of assessment, planning, and execution. The user shall identify an acceptable score for each infrastructure asset system being assessed with the practice (using resources listed in Table 4) and is encouraged to set targets for higher scores for each subsequent cycle of assessment (so that continuous improvement may be achieved) that shall not exceed four years.4.3 Who Should Use Information—The authority should use the generated information from the use of this practice to: (1) life safety-prioritize capital expenditures (extraordinary outlays) and spending on operations, maintenance, monitoring, and repair (ordinary outlays) of each infrastructure asset system that is assessed; (2) ensure costs are based on a life cycle basis, and, (3) triage those expenditures when insufficient funds limit the number of prioritized infrastructure asset services that can be improved or upgraded. The infrastructure asset service recipient should use generated information from the use of this practice to: (1) advocate for improved services; (2) coordinate communication among other infrastructure asset service recipients to voice concerns about service quality, frequency, and equity; and (3) identify new sources of revenue if present revenues are not sufficient for projects prioritized by the authority or by infrastructure asset service recipients.4.4 Regulatory Context—This practice does not supersede or replace federal, State, or local regulations, or reporting guidelines of the Governmental Accounting Standards Board or the Financial Accounting Standards Board. The user is responsible for determining the regulatory context, and associated constraints and obligations associated with the information generated in the performance of this practice.4.5 Use of Practice—An authority may incorporate this practice, in whole or in part, into general regulatory or guidance documents.4.6 Professional Judgment—This practice allows for transparency and accountability for an authority. The Infrastructure Management Process (Fig. 2) includes two community engagement steps, whereby the authority seeks concurrence with her/his infrastructure asset service recipients on goals and priorities for such services. Importantly, the authority is obliged to make final decisions that result in provided infrastructure asset services. Should this practice become part of the user’s system of governance, those results will be revisited continuously.FIG. 2 Infrastructure Management Process4.7 The user should review the standards in Table 4 before each iteration of this practice’s use.4.8 Elimination of Uncertainty—Professional judgment, interpretation, and some uncertainty are inherent in the processes described herein even when decisions are based upon objective scientific principles and accepted industry practices. In addition, new methods are continually being developed for this evolving field.4.9 Process Overview—At initiation, the user reviews: Section 3 Terminology; and then proceeds to Section 4 ; Section 5 Planning and Scoping; Section 6 Integrated Infrastructure System Management Process; and Section 7 Infrastructure System Reporting and Documentation, and becomes familiar with Fig. 2, an overview of the Infrastructure Management Process.1.1 This asset management practice establishes requirements of transparency and accountability for an assemblage of tangible and intangible infrastructure asset systems for a public or private organization.1.2 This practice promotes the life safety-prioritized and cost efficacious delivery of 15 types of infrastructure assets to infrastructure asset service recipients. These services include direct uses (for example, water supply or police protection) and indirect uses (for example, preventing adverse impacts on the environment while minimizing nature’s adverse impacts on infrastructure assets).1.3 This practice may be used as the basis for training guides for infrastructure asset system employees and operators.1.4 This practice provides an acceptability framework for 15 systems of infrastructure assets, including (1) potable water supply, (2) food systems, (3) sewage and storm water systems, (4) buildings, (5) healthcare, (6) security, (7) power, (8) communication, (9) transit and travel, (10) waste disposal, (11) education, (12) cultural heritage, (13) recreation and entertainment, (14) nature, and (15) financial systems.1.5 This practice is composed of the following sections: referenced documents; terminology; significance and use; planning and scoping; integrated infrastructure system management process; and infrastructure system reporting and documentation.1.6 The values stated in inch-pound units are to be regarded as standard. No other units of measurement are included in this standard.1.7 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.1.8 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

定价： 646元 / 折扣价： 550 元 加购物车

4.1 Motivation for the PMI comes from several organizational and application areas. For example:4.1.1 Supporting a distributed heterogeneous application architecture with a homogeneous distributed security infrastructure leveraged across the enterprise; providing user and service identities and propagation; and providing a common, consistent security authorization and access control infrastructure.4.1.2 Providing mechanisms to describe and enforce enterprise security policy systematically throughout the organization for consistency, maintenance, and ease of modification and to demonstrate compliance to applicable regulation and law.4.1.3 Providing support for distributed/service-oriented architectures in which enterprise-wide services and authoritative sources are protected by providing security services that themselves are also distributed using common interfaces and communication protocols.4.1.4 Providing “economies of scale” where it is desired to change the approach of individually managing the configuration of each point of enforcement to one that establishes a consolidated view of the safeguards in effect throughout the enterprise.4.1.5 Providing centralized control, management, and visibility to security policy across the enterprise and when connecting to other organizations. This allows for additional key features such as delegated administration, centralized policy analysis, and consolidated reporting.4.1.6 Providing a distributed computing security architecture allowing for synchronized security services that are efficiently maintained across the enterprise while also allowing for centralized policy control and distributed policy decision-making/enforcement. Ensuring proper security controls are enacted for each service and when used in combination.4.1.7 Provisioning incremental updates to policy and configuration data simultaneously across all distributed decision/enforcement points. Establishing and enforcing new policies not envisioned when individual applications were fielded and adapting to new requirements and threats. Managing identity and security implemented in a diverse mix of new and old technologies.4.1.8 Permitting an organization to grant, suspend, or revoke centrally any or all ability to connect to or access enterprise resources either individually or collectively and with the capability to enforce these policies at run-time.4.1.9 Supporting access decisions that are sensitive to a user’s credentials in addition to identity. For example, the user may have to be a licensed healthcare professional to access a medical record.4.1.10 Supporting Delegation—A user might delegate access for a resource to another user (for example, a physician might delegate access to his patient’s records to a specialist). This shows the need for a delegation capability for some applications.4.1.11 Supporting Sender Verification—When a user receives a signed document, he shall be sure the sender was, in some sense, authorized to sign and send the document. A simple example would be a prescription that shall be signed by a doctor. A simple identity certificate is insufficient, as it does not indicate the sender’s credentials (that is, that he is a doctor).4.1.12 Supporting Document Cosigning—Multiple examples exist in which more than one signature is required on a document (2). For example, a transcriptionist transcribes and signs a document, but it is not a valid part of the record until it is reviewed and signed by the primary care physician. Similar mechanisms can be used to provide cosignature controls when processing claims transactions. These types of applications require the ability to convey user authorizations (in assertions, credentials, authorization certificates, or possibly as extensions in identity certificates), to label documents and other objects with their security attributes (or to extract such attributes from the document), and to express authorization rules in machine-readable form.4.2 Existing standards, including ANSI X9.45, ISO 9594-8, IETFRFC 3280 X.509, OASIS SPML, SAML, WS-*, and XACML, define a number of mechanisms that can be used to construct a healthcare-specific PMI specification. This would include the following features:4.2.1 Privileges needed to access a target are conveyed in a claimant’s authorization credential. The claimant’s authorization credential may be an authorization certificate compliant with ISO 9594-8 (a particular form of attribute certificate) or a policy set description compliant with XACML or other referenced authorization standards.4.2.2 The sensitivity or other properties of the target being accessed may be held in a local database or in a signed data structure. This guide does not define a standard way to represent this information, since this is a local matter. It does provide guidance on how such information might be represented and manipulated using common mechanisms such as ASN.1 and XML. For a given target object, there may be multiple operations that may be performed; each such operation may have a different set of sensitivity attributes.4.2.3 The privilege policy may be held centrally, locally, or may be conveyed as a signed data structure. Different operations on a target may be subject to different privilege policies. This guide defines several standard policies, and applications may define additional policies.4.2.4 In the document authorization paradigm, cosignature requirements may be associated with a user or document, such that the signed document is considered authorized only if all necessary signatures are attached.4.2.5 Users may delegate privileges to other users.4.2.6 Users may be assigned to roles that convey permissions.4.2.7 Some authorizations may be sufficiently dynamic that it is not feasible to place them in an enterprise authorization infrastructure (that is, the cost of maintenance is too high given the short lifetime or rapid frequency of change of the privileges or constraints). Such authorizations may be kept in a local authorization server’s database and accessed as environmental variables.4.3 The remaining sections of this guide discuss mechanisms to convey privilege, sensitivity, and policy information in a distributed PMI.1.1 This guide defines interoperable mechanisms to manage privileges in a distributed environment. This guide is oriented towards support of a distributed or service-oriented architecture (SOA) in which security services are themselves distributed and applications are consumers of distributed services.1.2 This guide incorporates privilege management mechanisms alluded to in a number of existing standards (for example, Guide E1986 and Specification E2084). The privilege mechanisms in this guide support policy-based access control (including role-, entity-, and contextual-based access control) including the application of policy constraints, patient-requested restrictions, and delegation. Finally, this guide supports hierarchical, enterprise-wide privilege management.1.3 The mechanisms defined in this guide may be used to support a privilege management infrastructure (PMI) using existing public key infrastructure (PKI) technology.1.4 This guide does not specifically support mechanisms based on secret-key cryptography. Mechanisms involving privilege credentials are specified in ISO 9594-8:2000 (attribute certificates) and Organization for the Advancement of Structured Information Standards (OASIS) Security Assertion Markup Language (SAML) (attribute assertions); however, this guide does not mandate or assume the use of such standards.1.5 Many current systems require only local privilege management functionality (on a single computer system). Such systems frequently use proprietary mechanisms. This guide does not address this type of functionality; rather, it addresses an environment in which privileges and capabilities (authorizations) shall be managed between computer systems across the enterprise and with business partners.1.6 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.

定价： 0元 / 折扣价： 0 元

定价： 3413元 / 折扣价： 2902 元

1.1 This terminology is a compilation of definitions of technical terms used in the underground infrastructure and plastic piping industry. Terms that are generally understood or adequately defined in other readily available sources are not included.1.2 When a term is used in an ASTM document for which Committee F36 is responsible, it is included only when judged, after review, by Subcommittee F36.91 to be a generally usable term.1.3 Definitions that are identical to those published by other ASTM committees or other standards organizations are identified with the committee number (for example, F17) or with the abbreviation of the name of the organization (for example, IUPAC, International Union of Pure and Applied Chemistry).1.4 A definition is a single sentence with additional information included in discussions.1.5 Definitions are followed by the committee responsible for the standard(s) (for example, [F36.10]) and standard numbers(s) in which they are used (for example, F2233).1.6 Abbreviated Terminology: 1.6.1 Abbreviated terminology is intended to provide uniform contractions of terms relating to infrastructure that have evolved through widespread common usage. The compilation in this standard has been prepared to avoid the occurrence of more than one abbreviated term for a given term and to avoid multiple meanings for abbreviated terms.1.6.2 The abbreviated terminology and descriptions in this standard are intended to be consistent with usage in the infrastructure industry and the standards under F36 jurisdiction. Other ASTM committees may assign a different word-phrase description to the same abbreviated terminology. In such cases, the abbreviated terms in this standard shall apply to usage in F36 standards, or if widespread misunderstanding could result from conflicting abbreviated terminology descriptions, the abbreviated terminology for the word-phrase shall not be used in F36 standards.1.6.3 Acronyms and Initialisms—A word formed from the letters or parts of words of a longer word-phrase, usually from the initial letters or parts of the words. An acronym is pronounced as a word, for example, radar for radio detection and ranging. An initialism is pronounced as a series of letters, for example, DOT for Department of Transportation.1.6.4 The acronym or initialism description is the origin word-phrase for the acronym or initialism, not a definition.1.7 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.1.8 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

定价： 618元 / 折扣价： 526 元 加购物车

5.1 This guide is intended for use by communities, which may include towns, incorporated cities, counties, or similar entities with the authority to convene and implement resilience planning. The process described in this guide may have applications to a broader set of users, such as those described in Guide E3032.5.2 This guide is intended to be applied at a community or regional geographical and administrative scale. Smaller geographic and administrative scales, such as neighborhood scales, may also use this guide; however, there may be limitations in the range of solutions (see Step 4B) that are available due to statutory, regulatory, financial, or administrative constraints caused by limitations in governance bodies.5.3 This guide provides an analytical framework for establishing desired versus current anticipated performance in terms of time to recovery of function for clusters and infrastructure systems. The output of this analytical framework provides an objective basis for establishing priorities among proposed strategies and solutions to help meet community resilience goals.5.4 The planning and analytical process can be applied to any hazard, though the focus is on natural hazards. Steps 1 and 2 (form a collaborative planning team and understand the situation) do not require the use of hazard information and provide useful information for communities that can be incorporated into a resilience plan. The activities described in Steps 3 and 4 (determine goals and objectives, and develop the plan) require technical information about hazards and an assessment of their impact on community systems.5.5 This guide provides a planning process that emphasizes disaster recovery outcomes. However, all phases of preparedness, including prevention, protection, mitigation, response, and recovery, are important to the successful achievement of disaster recovery objectives. The analytical outputs of this guide should inform all phases of preparedness and provide an objective approach to prioritize pre-event mitigation action.5.6 The steps of this guide, presented in Section 6, are best initiated in the order provided. However, with the exception of the formation of a collaborative planning team in Step 1 and implementation and reporting Steps 5 and 6, it is feasible to complete Steps 2 to 4 in a non-consecutive order. Depending on a community’s specific needs, timeline, resources, or technical capabilities, Steps 2 to 4 may occur in a different order than described in this guide. In Section 6, supplemental information that elaborates on how to implement each step and collaborative planning team flexibilities is provided in a discussion note following each step.NOTE 1: The collaborative planning team provides the foundation for stakeholder engagement and input in subsequent steps, even if later steps are completed in a different order than what is described in this guide. Ideally, each step should be at least initiated to describe how the plan will eventually address all elements of resilience planning.5.7  Resilience plans developed with the support of this guide should be compatible with, inform, and augment other hazard mitigation planning and comprehensive planning processes. It is compatible with the National Preparedness Goal, the National Infrastructure Protection Plan, and the National Disaster Recovery Framework, and should inform and be consistent with other state and local plans and priorities. In practice, this includes general plans, capital improvement programs, hazard mitigation, emergency response, recovery, economic development, and transportation plans.1.1 This guide sets forth a flexible approach for communities to develop customized, comprehensive resilience plans for buildings and infrastructure systems that include input from relevant stakeholders; consider the social, economic, and physical systems of a community; establish community-scale performance goals that encourage recovery-oriented planning; and recommend processes to implement and maintain community resilience plans over time as community priorities evolve and change.1.1.1 The social dimensions of a community should drive the requirements of a community’s resilience plans and the performance of its physical systems, especially during recovery. The identification of social functions is a fundamental element of developing community resilience plans that accurately reflect priorities for recovery after a hazard event.1.2 The guide process steps address how to (1) form collaborative planning teams; (2) evaluate the current condition of social and built dimensions of a community; (3) determine community goals and objectives for built systems and hazards; (4) develop plans that address performance gaps and identify solutions; (5) prepare, review and approve final community resilience plans; and (6) implement and maintain resilience plans.1.3 This guide provides a process that facilitates priority setting and decision making regarding the establishment of community resilience goals and associated solutions. The process provides a framework for community resilience planning needs and is not intended to be prescriptive.1.4 Limitations of Guide—This guide does not advocate or specify any particular analytical methodology for ascertaining the performance of the built environment. This guide also does not directly address the effects of climate change, although the planning process can incorporate such events and impacts. (For additional information on these processes to address climate resilience planning, refer to Guide E3032.) This guide addresses buildings and infrastructure systems and how they support the social dimensions of communities, and considers how the elements of the built environment support social and economic community functions. The application of this guide is intended to support community resilience planning efforts across a community’s interdependent building and infrastructure systems. Applications beyond this scope were not considered in the development of this guide.1.5 Units—The values stated in SI units are to be regarded as the standard. No other units of measurement are included in this standard.1.6 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.1.7 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

定价： 843元 / 折扣价： 717 元 加购物车

5.1 The purpose of this guide is to provide, at the undergraduate college level, a basic educational structure in the infrastructure aspects of nanotechnology to organizations developing or carrying out education programs for the nanotechnology workforce. This guide helps to describe the minimum knowledge base for anyone involved in nanomanufacturing or nanomaterials research.5.2 The basic education should prepare an individual for varied roles in the nanotechnology workplace. The material in this guide may require a post-secondary two-year science or technology background to be understood sufficiently.5.3 Workers may transition in their roles in the workplace. Participants in such education will have a broad understanding of a complement of topics related to the infrastructure required for advanced research and manufacturing, thus increasing their marketability for jobs within as well as beyond the nanotechnology field.5.4 Because nanotechnology is a rapidly developing field, the individual educated in nanotechnology needs to be cognizant of changing and evolving safety procedures and practices. Individuals should be aware of how to maintain an up-to-date understanding of the technology and have sufficient base education to enable the synthesis of emerging or evolving safety procedures and practices.5.5 This guide is intended to be one in a series of standards developed for workforce education in various aspects of nanotechnology. It will assist in providing an organization a basic structure for developing a program applicable to many areas in nanotechnology, thus providing dynamic and evolving workforce education.1.1 This document provides guidelines for basic workforce education in the infrastructure topics related to nanotechnology to be taught at an undergraduate college level. This education should be broad to prepare an individual to work within one of the many areas in nanotechnology research, development, or manufacturing. The individual so educated may be involved in material handling, manufacture, distribution, storage, use, or disposal of nanoscale materials.1.2 This guide may be used to develop or evaluate an education program for the infrastructure used in the nanotechnology field. This guide provides listings of key topics that should be covered in a nanotechnology education program on this subject, but it does not provide specific course material to be used in such a program. This approach is taken in order to allow workforce education entities to ensure their programs cover the required material while also enabling these institutions to tailor their programs to meet the needs of their local employers.1.3 While no units of measurements are used in this guide, values stated in SI units are to be regarded as standard.1.4 This standard does not purport to address all of the methods and concepts pertaining to the infrastructure for nanotechnology. It may not cover knowledge and skill objectives applicable to local conditions or required by local regulations.1.5 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.1.6 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

定价： 515元 / 折扣价： 438 元 加购物车

定价： 364元 / 折扣价： 310 元