A "Brick" is a EA tool used in planning and communication. It is based on the NIH Enterprise Architecture Brick.
- Technologies include tools, products, platforms, and protocols. Bricks could also be used to categorize the lifecycle of things other than technologies.
- 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
- Typical lifecycle of technologies in a brick: emerging -> baseline -> containment -> retirement
- Technologies typically enter the lifecycle as emerging.
- Baseline technologies exit the environment through retirement, and almost always by passing through containment.
- Scope of a brick can vary, but the brick becomes less useful when it 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?
- How to track things that have been evaluated and dismissed ("misfit bricks")?
- How do we capture investment levels?
- Should a brick communicate service levels? How do we communicate how long we expect to endorse something for?