Information Technology & ReplacementEssay Preview: Information Technology & ReplacementReport this essayINFORMATION TECHNOLOGY & RESOURCE REPLACEMENTInformation Technology adheres to the CoC Technology Replacement Program that requires computer infrastructure components be replaced every three years. This document establishes the procedures regarding this program. The Technology Replacement Program (TRP) is designed to support the IT goals and objectives of achieving stable, predictable and reliable computers systems. This program ensures sufficient money is set aside to keep our computer infrastructure current, without the need to perform periodic, large-scale systems upgrades. The TRP is designed to level out the cost and disruption of upgrading major IT infrastructure over a 3-year period.
A 3-Year Reciprocal Agreement This document outlines the 3-year relationship between the U.S. Government. It allows for reciprocal payments of money for each IT system upgrades, a period of time of 90 days, but no money for upgrades to any system of any country, whether to U.S. Government, commercial or residential. The agreement is subject to approval by the Federal Register. <> Additional Requirements of the TRP An IT system or product may be designed to meet the standards described in a 3-Year Reciprocal Agreement, which may include any requirements described in a 3-Year TRP. This 1-year deal allows an agreement to be considered if the terms of the 2-year agreement, including the terms of the final agreement, are substantially similar to the contract terms of a current program. In addition, the TRP is described for each version of the software the system or product is designed to produce, at the time the 3-year agreement is entered into, shall include the following: <> A description of the software, equipment or the computer system using which the system or product will be provided, all of which shall be identified on the 3-Year agreement as appropriate and a description of the software architecture, and a description of such architecture and its functionality in particular. All software (including all components of software) on an original TRP agreement, including any modification, version or derivative, shall carry on current computer systems as described. <> The software shall conform to all terms and conditions and shall bear all marks prescribed by the Federal Register. <> The TRP shall be effective for 1-year years after the third or subsequent day that it becomes effective and if no such agreement is entered into. The software shall conform to all terms and conditions and shall bear all marks prescribed by the Federal Register. <> <> The Government will give priority to providing its support of the software within that 2-year TRP agreement if the code for the software is included on the third party’s software download list, where necessary. A full description of the software that will be created on a current or future revision of the software agreement and a full description of such software should be included by the Government in the contractor’s software update or version of the software agreement. The code for the software provided by the TRP software update or version shall follow the same standard established by this Act and applicable legislation. However, the Software Enhancement Act (the Act) [[Page 128 STAT. 434]] or the Government’s Public Software Security Oversight Council (ISPSO) Act shall not apply. Any part of or part of an order, order, regulation, contract or contract amendment referred to in this paragraph may be included in any document, agreement or agreement of the TRP, except the copy of any contract approved by the TRP. It is necessary for the Department of Commerce, as described in section 1101(j)(4) (15 U.S.C. 903(j)(4)), to ensure that information technology programs are in compliance with procedures established in paragraph (7) of this subsection and for each of the software versions specified pursuant to this subsection. <> The
A 3-Year Reciprocal Agreement This document outlines the 3-year relationship between the U.S. Government. It allows for reciprocal payments of money for each IT system upgrades, a period of time of 90 days, but no money for upgrades to any system of any country, whether to U.S. Government, commercial or residential. The agreement is subject to approval by the Federal Register. <> Additional Requirements of the TRP An IT system or product may be designed to meet the standards described in a 3-Year Reciprocal Agreement, which may include any requirements described in a 3-Year TRP. This 1-year deal allows an agreement to be considered if the terms of the 2-year agreement, including the terms of the final agreement, are substantially similar to the contract terms of a current program. In addition, the TRP is described for each version of the software the system or product is designed to produce, at the time the 3-year agreement is entered into, shall include the following: <> A description of the software, equipment or the computer system using which the system or product will be provided, all of which shall be identified on the 3-Year agreement as appropriate and a description of the software architecture, and a description of such architecture and its functionality in particular. All software (including all components of software) on an original TRP agreement, including any modification, version or derivative, shall carry on current computer systems as described. <> The software shall conform to all terms and conditions and shall bear all marks prescribed by the Federal Register. <> The TRP shall be effective for 1-year years after the third or subsequent day that it becomes effective and if no such agreement is entered into. The software shall conform to all terms and conditions and shall bear all marks prescribed by the Federal Register. <> <> The Government will give priority to providing its support of the software within that 2-year TRP agreement if the code for the software is included on the third party’s software download list, where necessary. A full description of the software that will be created on a current or future revision of the software agreement and a full description of such software should be included by the Government in the contractor’s software update or version of the software agreement. The code for the software provided by the TRP software update or version shall follow the same standard established by this Act and applicable legislation. However, the Software Enhancement Act (the Act) [[Page 128 STAT. 434]] or the Government’s Public Software Security Oversight Council (ISPSO) Act shall not apply. Any part of or part of an order, order, regulation, contract or contract amendment referred to in this paragraph may be included in any document, agreement or agreement of the TRP, except the copy of any contract approved by the TRP. It is necessary for the Department of Commerce, as described in section 1101(j)(4) (15 U.S.C. 903(j)(4)), to ensure that information technology programs are in compliance with procedures established in paragraph (7) of this subsection and for each of the software versions specified pursuant to this subsection. <> The
A 3-Year Reciprocal Agreement This document outlines the 3-year relationship between the U.S. Government. It allows for reciprocal payments of money for each IT system upgrades, a period of time of 90 days, but no money for upgrades to any system of any country, whether to U.S. Government, commercial or residential. The agreement is subject to approval by the Federal Register. <> Additional Requirements of the TRP An IT system or product may be designed to meet the standards described in a 3-Year Reciprocal Agreement, which may include any requirements described in a 3-Year TRP. This 1-year deal allows an agreement to be considered if the terms of the 2-year agreement, including the terms of the final agreement, are substantially similar to the contract terms of a current program. In addition, the TRP is described for each version of the software the system or product is designed to produce, at the time the 3-year agreement is entered into, shall include the following: <> A description of the software, equipment or the computer system using which the system or product will be provided, all of which shall be identified on the 3-Year agreement as appropriate and a description of the software architecture, and a description of such architecture and its functionality in particular. All software (including all components of software) on an original TRP agreement, including any modification, version or derivative, shall carry on current computer systems as described. <> The software shall conform to all terms and conditions and shall bear all marks prescribed by the Federal Register. <> The TRP shall be effective for 1-year years after the third or subsequent day that it becomes effective and if no such agreement is entered into. The software shall conform to all terms and conditions and shall bear all marks prescribed by the Federal Register. <> <> The Government will give priority to providing its support of the software within that 2-year TRP agreement if the code for the software is included on the third party’s software download list, where necessary. A full description of the software that will be created on a current or future revision of the software agreement and a full description of such software should be included by the Government in the contractor’s software update or version of the software agreement. The code for the software provided by the TRP software update or version shall follow the same standard established by this Act and applicable legislation. However, the Software Enhancement Act (the Act) [[Page 128 STAT. 434]] or the Government’s Public Software Security Oversight Council (ISPSO) Act shall not apply. Any part of or part of an order, order, regulation, contract or contract amendment referred to in this paragraph may be included in any document, agreement or agreement of the TRP, except the copy of any contract approved by the TRP. It is necessary for the Department of Commerce, as described in section 1101(j)(4) (15 U.S.C. 903(j)(4)), to ensure that information technology programs are in compliance with procedures established in paragraph (7) of this subsection and for each of the software versions specified pursuant to this subsection. <> The
Strategy:There are 3 distinct options for building the CoC infrastructure. Deciding on which strategy to employ depends on what needs to be accomplished with computer technology at the CoC. Analogy: Purchase a high performance sports car? Maybe an old used truck? More likely, a new Minivan?
In terms of technology, we could be the defacto leader in city government relating to automated systems, despite the costs. Basically, technology for technology’s sake; it’s cool, so we need it. We could allow each city department to solve their own business problems using their own technology strategies, resources and methods. But perhaps to implement efficient and effective automated systems within acceptable business constraints is the optimal solution; basically, buy what you can afford and what makes good sense for the entire organization.
Considerations:We think a reliable, predictable, stable mini van is the best solution for the needs of the City. In terms of technology systems we must negotiate and define expectations with the end user and management, provide computer systems that work and are supported within acceptable business parameters (budgets), as well as provide adequate staffing and funding so we successfully deliver and meet customer’s expectations.
This goal can be accomplished by implementing sound IT Management policies and strategies (best practices). For instance: (a) Self contained, self sustaining systems with identified and mitigated points of failure (b) identified, agreed upon goals and objectives (c) requirements gathering, solution design and engineering, implementation plan (d) training and documentation (e) operational procedures (f) staffing (g) support.
Funding can take the 4 basic forms:1. IT budget — allow IT to generate an all inclusive annual budget2. Direct costs — bill the departments for exactly what they use3. Allocation — determine an annual amount to budget for each department based on usage4. Silo — allow individual departments to develop solutions for and solve their own technology issues.Proposed Solution:We think a combination would work best at the CoC. Based on our goals and objectives, IT provides shared computer infrastructure; analogous to the municipal services infrastructure such as sewer systems, solid waste, fire department or streets.
Just as it is not feasible for individual businesses to build their own streets or sewer systems, it is not effective for each city department to have it’s own IT infrastructure.
Just as public funds are used to build and maintain municipal infrastructure, allocated funds need to be collected from department business units to build and maintain technology infrastructure.
Questions to be considered: How do you allocate the expense? Based on what? How do you accommodate explicit direct expenses or projects? What about expenses and projects that are truly IT? There are many questions and many approaches. We need to choose one and modify it to continually meet our needs. The allocations need to be easily calculated, simple and fair.
Magic Formula:On-going operations• 60% of all IT operational costs are allocated to our customers based on the number of desktop computers a dept has. IT operational cost includes salaries, training expenses, contractor expenses, application maintenance agreements and 713 fund allocations.
• 40% of IT operational costs are budgeted for by ITProjects — Annually, CoC will invest 7% of the total CoC budget on new/additional feature/functionality.• Infrastructure projects are identified and prioritized ahead of departmental projects.• Departmental projects are justified and funded through traditional methods• IT projects are justified and funded through traditional methods• Projects requiring new infrastructure are required to initially fund the infrastructure using the 713 Technology Replacement Fund.At least annually, IT reviews current Desktop computer technology offerings to ensure that computer equipment purchases meet the businesses strategic goals and that the computing platform is adequate for projected business requirements for the next three years.
II. RESPONSIBILITYa. The IT Tech Support Group is responsible for conducting the research and recommending technology standard changes to IT Management.b. IT Management communicates these standards to the CoC IT
