Please report any problems to the Shared Tools Team at st-help@doit.wisc.edu    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • IT Assets Subcommittee Description
Skip to end of metadata
Go to start of metadata

File Created Comment

IT Assets Subcommittee Description-2018-03-27.docx

Apr 17, 2018 14:41  

IT Assets Subcommittee

of the Policy Planning and Analysis Team

Purpose

The purpose of the IT Assets Subcommittee of the Policy Planning and Analysis Team (PAT) is to make recommendations on the definition of IT goods and services of all kinds for which acquisition or contracting is subject to IT governance policies and procedures.

Organization and Reporting

The PAT is not the appropriate group to make a final decision on the definition, nor to guide application of the definition.  The PAT is assisting IT governance by quickly creating a draft definition in order to expedite further work by others.

To that end, the Subcommittee is commissioned by the PAT Executive Committee (PAT EC) as described in the PAT Charter . The PAT EC serves as the sponsor of the the Subcommittee, and will advise the Subcommittee as needed.  The Subcommittee reports to the PAT EC, which will comment on and pass the Subcommittee’s recommendations to the PAT, and from there onward to IT governance and other relevant groups and offices.

Scope

The use of the term ‘assets’ in this charter is merely a convenient label, and is not intended to limit the scope of the recommendations of the Subcommittee.

The Subcommittee :

  1. should make recommendations on the definition of  IT goods or services of all kinds for which acquisition or contracting is subject to IT governance policies and procedures.
  2. may choose to present their recommendations in the form of a draft definition, along with other material that clarifies the meaning or intent of the definition.
  3. The recommendations or draft definition from the Subcommittee are a starting point for further work by IT governance and other relevant groups and offices.

Out-of-Scope

The Subcommittee should not write policies and procedures that implement the definition, but may make general recommendations on such to the extent necessary to clarify the meaning or intent of the definition.

Timeframe

Further work by IT governance and other relevant groups and offices is waiting for the draft definition. Speed is important. Quality is also important. Speed should be obtained not by rushing, but by focusing narrowly on the scope in order to avoid scope creep.

  1. The Subcommittee should deliver a preliminary report by May 11.
  2. The final report should be delivered by July 13.
  3. This Subcommittee’s defined work ends upon delivery of the final report. If there is further work for a follow on s ubcommittee, the Subcommittee’s definition and membership can be adjusted accordingly.

 

  • No labels