A "Brick" is a EA tool used in planning and communication. It is based heavily on the NIH Enterprise Architecture Brick. A brick has the following categories, arranged in the ideal lifecycle flow from emerging to retirement.
- The term "technology" includes tools, products, platforms, and protocols. Bricks could also be used to categorize the lifecycle of things other than technologies.
- Technologies in tactical and strategic designations should be selected for future implementations and will begin to, or continue to, reside in the baseline.
- A technology can exist in one or more brick categories. For example, "HTTP" may be both baseline and containment, while "HTTPS" is both baseline and "tactical". The categories "tactical" and "strategic" can provide roadmap qualifications to "baseline" technologies
- A technology typically enters the environment designated as "emerging." If the technology is approved and supported, it will become "baseline". It will exit the environment through "retirement", and almost always by passing through "containment."
- Technologies in "containment" may still deliver great value
- Scope of a brick can vary, but the brick becomes less useful when its scope is too big or too small.
- Strive for an open environment with one brick per domain area rather one brick to communicate to customers and one brick for internal team communication
- Maintain a brick through periodic review
- How to track pilots? NIH places technologies that are to be evaluated or are being evaluated in "emerging."
- How to track things that have been evaluated and dismissed ("misfit bricks")? NIH removes them from "emerging," but we may want to communicate that they have been removed.
- How do we capture investment levels?
- Should a brick communicate service levels? How do we communicate how long we expect to endorse something for?