Manufacturer's Recommendations All work or materials shall be installed in accordance with the manufacturer's recommendations and requirements. The Contractor shall obtain the manufacturer’s recommendations and requirements, for its use at the Site in executing the Work, copies of bulletins, circulars, catalogues, or other publications bearing the manufacturer’s titles, numbers, editions, dates, etc. If the manufacturer’s recommendations and requirements are not available, the Contractor shall request installation instructions from the Design Professional.
Conclusion and Recommendations D. Evaluations for Offenders without a sex offense conviction shall answer the following additional referral questions in the evaluations:
Conclusions and Recommendations The demonstration and evaluation process provided an opportunity to test community specific tools with a range of end users from the memory institution domain and to gain greater insight into both the current and future evolution of the SHAMAN prototypes for preservation, access and re-use. Xxxx et al. (2000) in their user evaluation study of the Alexandria Digital Library which incorporated the evaluation of a Web prototype by earth scientists, information specialists and educators raised four key questions in relation to their findings that SHAMAN may be well advised to consider, they are paraphrased here with our conclusions from the investigations. What have we learned about our target organizations and potential users? Memory institutions are most definitely not a homogenised group; their needs and requirements differ greatly across the domain. Representatives of the archives community are agreed on the benefits of SHAMAN‟s authenticity validation function. The representatives of government information services remained unconvinced as to the need or benefit of grid technologies or distributed ingest while librarians saw the value of grid access as an asset of the framework. What have we learned about the evaluation approach for digital preservation? Within the limits of the exercise, in terms of time-frame and resources, the approach adopted has generated useful information for the further development of demonstrators and for the development of the SHAMAN framework overall. What have we learned about the SHAMAN ISP1 demonstrator? Respondents to the evaluation questionnaires and the focus groups indicate that, overall, the presentation of the demonstrator worked effectively and that, in general, participants in the demonstration and evaluation events were able to understand the intentions of the demonstration and to apply the ideas presented to their own context. What have we learned about the applicability of the SHAMAN framework to memory institutions? Respondents to the questionnaires and participants in the focus groups readily identified the value of the SHAMAN framework to their own operations. The majority had not yet established a long-term digital preservation policy, but recognized the need. Generally, the concepts of distributed ingest and grid operations found favour. Virtually all practitioners in the focus groups, however, drew attention to need of a lower level demonstration that would be closer to their everyday preservation troubles, especially for digital preservation to be applied to non-textual materials, such as film, photographs and sound archives. In addition to the criteria suggested by Xxxx et al., we can add a further project-related question: What have we learned that has implications for the training and dissemination phase of the Project? It was not part of the remit of the demonstration and evaluation specifically to discover information of relevance to the training and dissemination function. However, a number of factors will affect the efficacy of any training programme in particular. o First, no common understanding of digital preservation can be assumed of the potential target audiences for training. Consequently, it is likely that self-paced learning materials will be most effective in presenting the SHAMAN framework. o Secondly, the aims of SHAMAN as a project must be conveyed clearly: specifically, that it is a kind of „proof-of-concept‟ project and is not intended to deliver a package of programs capable of being implemented by institutions. o Thirdly, it needs to be emphasised that the SHAMAN framework is not limited to text documents; it can be applied to materials of all kinds. However, the demonstrations relate to bodies of material that were actually available for use. o Fourthly, the existing presentation materials are capable of being adapted for use in training activities. o Finally, the target audiences will appreciate the possibility of online access to the demonstrator, which will need to have very great ease of access in order that people with diverse backgrounds are able to use it with equal facility. We believe that, overall, WP14 has met its aims and objectives in this demonstration and evaluation of ISP1. Valuable lessons have been learnt by all parties involved, which will be transferred to the evaluation of ISP2 in the coming months.
JOINT SETTLEMENT RECOMMENDATION 2. Staff conducted an investigation of the Respondent’s activities. The investigation disclosed that the Respondent had engaged in activity for which the Respondent could be penalized on the exercise of the discretion of the Hearing Panel pursuant to s. 24.1 of By-law No. 1.
SUPPLIER PUBLICATIONS 4.1 Any marketing materials in relation to this Framework Agreement that that Supplier produces must comply in all respects with the Branding Guidance. The Supplier will periodically update and revise such marketing materials.
Recommendations It is recommended that:
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Technical Advisory Committee (TAC The goal of this subtask is to create an advisory committee for this Agreement. The TAC should be composed of diverse professionals. The composition will vary depending on interest, availability, and need. TAC members will serve at the CAM’s discretion. The purpose of the TAC is to: • Provide guidance in project direction. The guidance may include scope and methodologies, timing, and coordination with other projects. The guidance may be based on: o Technical area expertise; o Knowledge of market applications; or o Linkages between the agreement work and other past, present, or future projects (both public and private sectors) that TAC members are aware of in a particular area. • Review products and provide recommendations for needed product adjustments, refinements, or enhancements. • Evaluate the tangible benefits of the project to the state of California, and provide recommendations as needed to enhance the benefits. • Provide recommendations regarding information dissemination, market pathways, or commercialization strategies relevant to the project products. The TAC may be composed of qualified professionals spanning the following types of disciplines: • Researchers knowledgeable about the project subject matter; • Members of trades that will apply the results of the project (e.g., designers, engineers, architects, contractors, and trade representatives); • Public interest market transformation implementers; • Product developers relevant to the project; • U.S. Department of Energy research managers, or experts from other federal or state agencies relevant to the project; • Public interest environmental groups; • Utility representatives; • Air district staff; and • Members of relevant technical society committees. The Recipient shall: • Prepare a List of Potential TAC Members that includes the names, companies, physical and electronic addresses, and phone numbers of potential members. The list will be discussed at the Kick-off meeting, and a schedule for recruiting members and holding the first TAC meeting will be developed. • Recruit TAC members. Ensure that each individual understands member obligations and the TAC meeting schedule developed in subtask 1.11. • Prepare a List of TAC Members once all TAC members have committed to serving on the TAC. • Submit Documentation of TAC Member Commitment (such as Letters of Acceptance) from each TAC member. Products: • List of Potential TAC Members • List of TAC Members • Documentation of TAC Member Commitment
Technical Proposals Technical proposal information will be streamlined, e.g., the Government anticipates written proposals consisting of thirty (30) pages or less stating compliance or exception to requirements, risks, assumptions and conflict of interest issues. Proposals shall not merely restate PWS/SOO requirements. Written technical proposals shall normally address: * Technical Approach and descriptive narrative of the contractor's understanding of the requested effort * PWS in response to a SOO * Integrated Master Plan (if applicable) * Integrated Master Schedule (if applicable) * Key Personnel Assigned * Quantities/Hours of Personnel by Labor Categories and narrative justification (if applicable) * Other Direct Costs (ODCs) (materials and supplies, travel, training, etc.(quantities and types only)) * Period of Performance * Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI) * Security (including clearance level) * Teaming Arrangement (including subcontracting; identify new ACAs) * Small Business Plan (if a large business) * Other Pertinent Data, such as assumptions made.
zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
