The domain team or working group begins its work with a formal orientation, or training, kickoff session, during which all members are informed of the work to be accomplished by the team and the plan to accomplish it. The domain team or working group then begins its work. The following are the basic steps each domain team or working group performs to develop their recommendations:
- Understand the current state for the team’s technology area of focus. (For teams that are selecting technology standards this will be defining the current NIH baseline for the specific technology area [i.e., technical domain]).
- Establish or validate guiding principles.
- Finalize the decision criteria the team will use to make its decisions.
- As appropriate, conduct market research to ensure a complete scan of all available products and technologies within the technical domain, and understand the strengths and weaknesses of each vis-à-vis the decision criteria.
- Write and issue a Request for Information (RFI) so that all vendors have an opportunity to be included in the evaluation process.
- Deliberate to achieve consensus based on analysis of available information (i.e., current baseline, market research).
- Develop recommendations.
- Compile the team’s next steps and final recommendations.
|
Attendance Roster (XLS). Document used to track attendance of domain team or working group attendees.
Certificates Of Appreciation (PPT). Template used to recognize attendees for their participation. Printed on cardstock and handed out to attendees at the final meeting. Signed by the Chief IT Architect.
CIO Survey (XLS). Survey used to document the current inventory of software for a given IC. Useful in uncovering any technologies not already documented.
CIO Survey Email (DOC). Sample email used when sending the CIO Survey. Generally sent by the Chief IT Architect or the team's chair.
Meeting Minutes (DOC). Template for tracking meeting discussions and key decisions.
Name Tents (PPT). Template used to create name tents which help identify attendees at meetings.
NIH Certification Forms (DOC). Conflict of interest and confidentiality cerfication for individuals evaluating proposals or RFI responses.
NIHRFC 0001 - Enterprise Architecture Standards Process (PDF). Documents the standards process. Defines the stages in the standardization process, the requirements for moving a document between stages, and the types of documents used during this process.
NIHRFC 0003 - Instructions to NIHRFC Authors - How to Write a Standard (PDF). This document is a guide for NIH IT and architecture standards writers. It defines those characteristics that make standards coherent, unambiguous, and easy to interpret.
NIHRFC 0015 - Decision Criteria For Selecting NIH Standards (PDF). Decision Criteria for Selecting NIH Standards. Documents the baseline decision criteria to be used in NIH Enterprise Architecture processes for selecting and gaining consensus on the architecture standards to be recommended to the Architecture Review Board for approval.
Presentation Template (PPT). Standard NIH template used for all domain team and working group meetings.
Reminder Email For Attendees (DOC). Sample email to attendees the day prior to a domain team or working group meeting.
Request For Information Questionnaire (DOC). Template used to help the NIH understand market availability, technical characteristics, and functionality of specific technology tools or products. (Requires NIH Login.)
Request For Information Worksheet (XLS). Spreadsheet template for determining technical and functional requirements for a technology area. Used in conjunction with the request for information questionnaire (above) to collect greater details of a technology or product. (Requires NIH Login.)
Sign-In Sheet (DOC). Template used for attendees to sign-in for each meeting to track attendance. |
Exit Criteria:
- Meetings are conducted.
- Proposed artifacts are either updated or created, e.g., new bricks and patterns.
- Draft executive briefing is created.
- Domain team checklist is updated.
Previous Step: Establish The Team.
Next Step: Produce Team Products.
