Procurement
Language
1.
For EA Compliance in new Request for Proposals (RFPs), the following
language will be required for the RFP cover letter; Section C, Statement
of Work (SOW); and possibly Section H, Special Provisions:
"The
Department of Housing and Urban Development (HUD) has developed
an Enterprise Architecture (EA). All contractors that design, build,
or modify information systems for HUD must comply with HUD's Enterprise
Architecture. Information on the HUD EA is contained in the Enterprise
Architecture Management System (EAMS). All IT contractors will have
access to EAMS, and must use EAMS as a guide in development and
enhancement efforts to assure that all IT systems conform to HUD's
Business, Data, Applications, and Technology Target Architectures.
HUD will assess the contractor's proposed changes for EA compliance
approval prior to any development or enhancement. At the completion
of development and prior to implementation, the summary of changes
to the EA must be provided to HUD at the same time as the software
deliverables, in electronic and hardcopy format."
The
deliverable schedule should reflect two additional items:
- An
architectural impact statement of the proposed system development/enhancement.
It shall include any proposed changes to the current "baseline"
architecture at all affected levels. This is to be delivered following
design and prior to development.
- A
similarly scoped architectural impact statement of the software
as developed/enhanced. This is to be delivered following testing
and prior to implementation
2.
For EA Compliance where a contract is already in place, the above
could be issued as a blanket change order, with additional costs
for performance negotiated.
Benefits
Simplifies
IT investment decisions
Accelerates
system implementation
Reduces
system diversity
|