Notice: applying this to your agency.
The IT Project Resources are not meant to replace your agency’s internal project management practices or prescribe how you must operate. Instead, they offer concepts and tools that can strengthen delivery by providing a scalable framework for project level coordination. All project documentation should be maintained throughout each stage in alignment with agency policies and, where applicable, WaTech requirements and oversight expectations.
Develop a comprehensive understanding of the current technical and business environment before beginning future‑state solution design. This task establishes the architectural baseline needed to identify gaps, dependencies, constraints, and integration considerations. The System Architecture Plan documents existing systems, data flows, integrations, infrastructure, and agency‑specific configurations that will inform the future‑state architecture.
This work creates a clear and complete view of the current‑state architecture to support planning and solution design. It includes documenting integration points, data flows, infrastructure components, hosting environments, and any technical or business constraints that may influence the future solution.
Note: This documentation may contain sensitive information and may need to be classified as Confidential 3.
For Programs
Programs must capture the full architectural landscape across all participating agencies to support enterprise alignment and cross‑agency integration.
- Document the existing system architecture across all participating agencies.
- Identify current integration points, data flows, infrastructure components, and hosting environments.
- Capture agency‑specific configurations, variations, and technical constraints.
- Compile a consolidated view of the enterprise ecosystem relevant to the program’s scope and future‑state planning.
For Agency Sub‑Projects
Agency sub‑projects must document the agency’s current ecosystem as it relates to the enterprise solution. Identify legacy systems, platforms, interfaces, and data sources that will interact with or be impacted by the future solution. Document system behaviors, data exchanges, and operational dependencies. Provide system documentation to the enterprise program team to support cross‑agency mapping, alignment, and integration planning.
For Projects
Projects must produce a complete and accurate current‑state architecture package that reflects the systems and technical components within the project’s scope.
- Document systems, workflows, integrations, and technical components relevant to the project.
- Establish the architectural baseline that will be used to inform gap analysis and future‑state solution design.
WaTech available template: System Architecture Plan