1 / 7

IT Standards Process

IT Standards Process. QTS Meeting May 21, 2008. Three Standards Conditions. Standard Setting Waivers from Existing Standards* Individual instances to use a technology where no standard exists. This briefing is on the first condition: Establishing standards

olin
Download Presentation

IT Standards Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IT Standards Process QTS Meeting May 21, 2008

  2. Three Standards Conditions • Standard Setting • Waivers from Existing Standards* • Individual instances to use a technology where no standard exists. This briefing is on the first condition: Establishing standards * The Official IT Standard Process is under review and may be revised. (subject of another briefing)

  3. Process for Establishing New IT Standards Standard Types: New function, or new standard for existing function; proposed technology solution may or may not be known • QTS members propose new standards to the QTS. Or the ITSC could propose to the QTS. If approved at the QTS, the ITSC decides what research needs to be done, and proposes (to the CTO?) how its to be conducted. Recommendations can also come directly from ITSC analyzes. Note: Proposals to QTS require must certain amount of information, See slides x) • ITSC checkpoint: Proceed to conduct research? • Perform “Procurement-like” research (requirements analysis, market analysis, lifecycle cost/benefit); findings presented thru ITSC to QTS • QTS checkpoint: Proceed to select technology? • Evaluate candidate IT products; develop recommendation and support plan; presented thru ITSC to QTS • QTS checkpoint: Proceed with acquisition, implementation? • Agency funds technology acquisition and new standard is established • OTOP develops WCF service(s), if applicable • Implementer develops standard configuration, user/developer guidance (usually OTOP) • Implement

  4. Proposal Process for Architecture Change (Submitted to QTS) • New standards for existing categories • New categories QTS Sponsor (Programs/Regions) QTS ITSC Chief Technology Officer OEI/OTOP IT Architect Technology Managers Government Initiatives IT Standards Committee • Inputs: • Mission requirements • Federal mandates • Changing business practices • New technology developments, opportunities • Recognized shortcomings in existing standards • Recognized opportunities for efficiency QTS recommendation & CTO Decision

  5. Role of IT Standards Committee • Provides forum for reviewing the Agency’s IT standards • Serves as the recommending body to establish and revise IT standards, as they are brought to the QTS: • As proposed by a Program’s QTS member • As a direct recommendation of the IT Standards Committee (by committee chairs) • Establishes guidelines a requestor must follow in order for the ITSC to consider a standards change proposal • Serves as reviewing body for all analyses required to support the need for new standard • Notes: • In individual instances where a technology is requested but no standard exists, then it may be better handled similar to OTOP’s official IT waiver process. • OTOP’s waiver process is not part of the IT Standards approval process and will be handled separately.

  6. Initial Proposal to Consider Standard(and to conduct Research) • Name of sponsoring QTS member • Purpose/requirement • Benefit of establishing/modifying an Agency Standard • Description of existing solutions already in use in EPA • Description of architecture for proposed technology (all that apply): • User Environment: Who are the users, where are they, how many are there, • Application Hosting Infrastructure: What hosting platform is required, • Network/Telecom: Any new technology required, any expected signficant network impacts • Security: Any known security issues • Application Development:: Use of/relationship to Enterprise Tools and E-gov Tools • Estimated life cycle cost • Other considerations

  7. Proposal to Establish a New Agency IT Standard • Name of sponsoring QTS member • Purpose/requirement • Benefit of establishing/modifying an Agency Standard • Description of existing solutions already in use in EPA, if any • Description of architecture for proposed technology (all that apply): • User Environment: Who are the users, where are they, how many are there, what devices/user interface software would they use for this function • Application Hosting Infrastructure: What hosting platform is required, where will it be hosted, what is development environment • Network/Telecom: Any new technology required, what EPA networks and technologies will be used/affected • Security: Any new technology required, what is Identity and Access Management approach • Application Development: Use of/relationship to Enterprise Tools • Relationship to, interdependencies with, implications for other EPA technology infrastructure • Estimated life cycle cost, by phase • Results of market research and alternatives analysis • Support requirements, proposed approach • Proposed methodology for selecting, acquiring standard technology • Proposed funding source • Working Capital Fund implications • Other considerations

More Related