Your SlideShare is downloading. ×
Word - Financial Systems Integration Office
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Word - Financial Systems Integration Office

1,720

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,720
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. TARGET TECHNOLOGY STANDARDS Deliverable #8 Submitted On July 30th 2004 To: Office of Management and Budget New Executive Office Building 725 17th Street, NW Washington, DC 20503 On behalf of: Financial Management Line of Business Taskforce Enterprise Architecture Working Group (EAWG)
  • 2. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Version History Description Date Name Initial draft July 16, 2004 FM LOB EAWG Deliverable #8 Target Technology Standards Submitted Draft.doc Final July 30, 2004 FM LOB EAWG Deliverable #8 Target Technology Standards Final.doc 1 of 16
  • 3. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Table of Contents Target Technology Standards......................................................................................................1 2 i. Target Architecture Target Technology Standards Deliverable Traceability Matrix................3 Introduction..................................................................................................................................4 1. Target Technology Standards...................................................................................................4 1.1. Architecture-Specific Technology Standards...............................................................4 1.2. Component-Specific Technology Standards.................................................................9 2. Conclusion..............................................................................................................................14 2 of 16
  • 4. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 i. Target Architecture Target Technology Standards Deliverable Traceability Matrix LoB Target Architecture Technology Relevant section of this document Standards Deliverable Requirements 1. Each target architecture is required to This requirement is addressed in use the standards (third layer) of the sections 2.1 and section 2.2. FEA TRM. 2. Two levels of analysis are required: This requirement is addressed in Architecture wide: Standards that are Sections 2.1, 2.2. used to enable the target architecture as a whole (include hosting, network, etc.); identification of common solutions that will make use of these standards; and associated rationale Component: Specific technology standards that are used to support specific components and an associated rationale (please identify components that are re-used across the target architecture) 3 of 16
  • 5. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Introduction The success of the President’s Management Agenda (PMA) depends upon agencies working across traditional boundaries to better serve the American people by focusing on citizen-centered, results- oriented, and market-based initiatives. Pursuant to the PMA, the Office of Management and Budget (OMB) created the Line of Business (LOB) initiative addressing redundant information technology (IT) investments and business process across the Federal Government. The LOB task forces and OMB are developing a business-driven common solution and target architecture. The LOB initiatives afford agencies an unprecedented opportunity to influence the direction of specific core business functions government-wide. The vision of the Financial Management (FM) LOB is to establish the framework for a government-wide financial management solution that is efficient and improves business performance while ensuring integrity in accountability, financial controls and mission effectiveness. The Federal Enterprise Architecture (FEA) is a business and performance-based framework supporting cross-agency collaboration, transformation, and government-wide improvement. It provides a new way of describing, analyzing, and improving the ability of the Federal Government to serve the citizen. Underpinning accomplishment of the FM LOB goals is the development of an enterprise architecture using the FEA taxonomy to describe the FM target architecture in a consistent manner while providing sufficient details within the architectural deliverables so that agencies can begin transition planning and analysis in support of the common solution. 1. Target Technology Standards This document, addressing Target Technology Standards for the Financial Management Line of Business, identifies the technology standards and business components that support the Technology Reference Model (TRM) of the FEA. Included are technology standards that are applicable to the FM LOB and technologies that support the delivery and exchange of business and application components (service components) that can be used and leveraged in a component-based, service-oriented architecture (SOA). The TRM for FM LOB will potentially consolidate existing Federal and e-Gov guidance to foster reuse of technologies and component services across government. 1.1. Architecture-Specific Technology Standards Table 1 lists the FEA Service Areas, Categories, Standards, and Specifications applicable to the FM LOB and provides a brief rationale for each. The list was derived from responses to the FM LOB Request for Information (RFI) and supplemented with information provided in agency Exhibit 300 submissions for FM applications. For an information technology (IT) investment of this scope, most, if not all of the FEA standards and specifications are applicable. To the greatest degree possible these standards and specifications should be leveraged across all of the LOBs as well as all of the e-Gov initiatives. There are few IT specifications that are specific to any LOB. Reuse of IT components across LOBs is of the essence. Table 1: Technical Reference Model Service Standards, Specifications, and Rationale 4 of 16
  • 6. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Service Service Service Area Service Specification Rationale Category Standard Service access Access channels Web browser Netscape Navigator Netscape is the second most widely and delivery used World Wide Web browser. Internet Explorer (IE) IE is the most widely used World Wide Web browser. Others Any XML-enabled browser should be supported. Other electronic System to System Provides exchange of data or channels interaction without human interaction. Uniform Resource Locator Provides the global address of documents and other resources on the Web. Collaboration Facsimile (Fax) Many financial documents are still Communications paper-based. Delivery Delivery Internet The ability to provide information on channels channels the internet. Intranet The ability to provide information on a private network within an enterprise. Extranet The ability to provide information to the public. Service Legislative / Section 508 Required to meet the government 508 requirements compliance requirements. Security Security is of the essence for many financial records. Privacy: Liberty Alliance Privacy is important for some financial data. Hosting Internal (Within agency) The ability to host the application within the enterprise. Service transport Supporting Internet message access IMAP allows remote client/server network services protocol / Post office capabilities between the client and protocol (IMAP / POP3) the mail server and provides greater capability than Post Office Protocol (POP) 3. Multipurpose Internet mail IMAP allows remote client/server extensions (MIME) capabilities between the mail client and mail server, and provides greater capability than Post Office Protocol (POP) 3. The major Email server vendors support IMAP. Secure multipurpose Increase security for messages sent Internet mail extensions into domain that MIME doesn’t (S / MIME) support. Simple mail transfer Almost all communications product protocol (SMTP) suppliers support SMTP. It is necessary for Internet email. Lightweight directory LDAP is vendor-independent and access protocol (LDAP) supports multi vendor interoperability in the same fashion as TCP/IP, SMTP, Domain Name Space (DNS), and others. Supporting Directory Services (X.500) The ability to discover and identify network services resources on a network and make them accessible to users and applications. Service transport Wireless application protocol WAP enables web content to be (WAP) presented on wireless devices. 5 of 16
  • 7. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Service Service Service Area Service Specification Rationale Category Standard Service Supporting Platform Java 2 Enterprise Edition J2EE and .Net are the two dominant platform and platforms independent (J2EE) distributed computing architecture infrastructure frameworks. Platform Windows Various versions of Windows should dependent be supported. Platform Windows .NET .Net supports a wide range of dependent languages. Database / Database SQL All of the SQL compliant relational storage databases should be supported. XQuery The emerging class of native XML databases should also be supported. Storage Network-attached storage Provides extended storage (NAS) capabilities for file sharing. Storage Area Network High-speed subnet of shared storage (SAN) devices. Hardware Servers / Mainframe Large-scale hosted applications will Computers require mainframe computing power. Embedded Hard Disk Drive Magnetic storage will be required Technology both on the hosts as well as the Devices clients. Peripherals Printer Many financial documents will need to be printed. Wide Area Asynchronous Transfer Widely used protocol for WANs. Network (WAN) Mode (ATM) Local Area Ethernet Widely used protocol for LANs. Network (LAN) Network Digital Subscriber Line Widely used standard for relatively Devices / (DSL) high-speed access via the Web. Standards 6 of 16
  • 8. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Service Service Service Area Service Specification Rationale Category Standard Component Security Certificates / Secure Sockets Layer SSL is an integral part of each framework Digital signature (SSL) Netscape browser. If a Website is on a Netscape server, SSL can be enabled and specific Web pages can be identified as requiring SSL access. Digital Certificate Digital certificates are required to Authentication provide for authentication and non- repudiation. Supporting Transport layer security TLS is an integral part of each security services (TLS) Netscape browser. If a Website is on a Netscape server, SSL can be enabled and specific Web pages can be identified as requiring TLS access. WS-Security Describes enhancements to SOAP messaging to provide message integrity, message confidentiality and single message authentication. Security Assurance XML framework for exchanging Markup Language (SAML) authentication and authorization information. Presentation / Dynamic/ Server- Java Server Pages (JSP) JSP is part of Sun’s J2EE Interface Side Display architecture and provide template capabilities. Active Server Pages.Net A web server technology from Microsoft that allows for the creation of dynamic, interactive sessions with the user. Content Cascading style sheets CCS is the emergent standard for rendering (CSS) web browsers. Dynamic HTML (DHTML) DHTML is used to render dynamic pages on the Web. Wireless Markup WML is used to enable transmission Language (WML) of XML formatted data to wireless devices. Business logic Platform Java 2 platform enterprise J2EE and .Net are the two dominant independent edition (J2EE) distributed computing architecture frameworks. Platform JavaScript Many Web pages employ JavaScript independent for easy script use. Data interchange Data exchange Enterprise Application Allows the movement and exchange Integration (EAI) of information between different applications and business processes within and between organizations. Electronic Business using Emerging XML-based standard for XML (ebXML) business. Simple Object Access SOAP is a lightweight protocol Protocol (SOAP) intended for exchanging structured information in a decentralized, distributed environment. Open Financial OFX is a specification for the Interchange (OFX) electronic exchange of financial data between financial institutions, business and consumers via the Internet. Interactive Financial IFX is an XML-based, financial Interchange (IFX) messaging protocol. 7 of 16
  • 9. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Service Service Service Area Service Specification Rationale Category Standard Java Online Analytical Provide a common, nonproprietary Processing (JOLAP) language for access to databases on a network. XML for Analysis Provide a nonproprietary vocabulary for data analyses. eXtensible Business Nonproprietary, XML-based Reporting Language vocabulary for financial business (XBRL) reporting. Service Interoperability Middleware Message Oriented Provides a client/server interface and Middleware (MOM) http://www.sei.cmu.edu/str/description integration s/clientserver.html infrastructure that increases the interoperability, portability, and flexibility of an application by allowing the application to be distributed over multiple heterogeneous platforms. Data format / XML schema Is the standard format for web data, classification and is beginning to be used as a common data format at all levels of the architecture. Namespaces Required in some form to avoid “collisions” when the same terms are used with different meanings in different data domains. Electronic Data EDI will continue to be used in some Interchange (EDI) sectors for the foreseeable future and must be supported. Data Types / Document Type Definition DTDs are suitable for documents that Validation (DTD) are not highly structured in the sense of using strong data typing. Data eXtensible Sylesheet XSLT is a W3C standard for Transformation Language Transformation transformation of data. (XSLT) Interface Service Universal description Provides a searchable registry of discovery discovery and integration XML web services and their (UDDI) associated URLs and WSDL pages. Service Web Services Description Is an XML based interface description Description/ Language (WSDL) language for describing XML Web Interface Services and how to use them. Middleware Database Access: ISQL iSQL-Viewer is an open-source JDBC 2.x compliant database front end written in Java. Business Process Enables federation of business Execution Language processes across distributed (BPEL) platforms. 8 of 16
  • 10. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Service Service Service Area Service Specification Rationale Category Standard Web Services An extensible framework for Coordination (WS- providing protocols that coordinate Coordination) the actions of distributed applications. Web Services Describes two coordination types -- Transactions (WS- Atomic Transaction (AT) and Transactions) Business Activity (BA) -- that are used with the extensible coordination framework described in the WS- Coordination specification. Enterprise Application Connectivity EAI components will be required to Application share data between the “as is” and “to Integration be” components, both as a migration/ conversion strategy as well as on a longer-term basis, when the FM LOB solution itself becomes a “legacy” application. 1.2. Component-Specific Technology Standards Two other technical standards that warrant consideration for use by the FM LOB as well as all other LOBs include WebDAV and XForms. WebDAV is an Internet Engineering Task Force (IETF) standard for Web Distributed Authoring and Versioning. It is a set of extensions to the HTTP protocol that allow users to collaboratively edit and manage files on remote Web servers. It has been widely implemented in commercial applications, some of which are listed at http://www.webdav.org/projects/#commercial Additional information on WebDAV is available at http://www.ietf.org/rfc/rfc2518.txt, http://www.ics.uci.edu/~ejw/authoring/, and http://www.webdav.org/ XForms is a recommendation of the World Wide Web Consortium (W3C). It is an XML application that represents the next generation of forms for the Web. Among the key design goals for XForms are: a richer user interface to meet the needs of business, consumer and device control applications; advanced forms logic; and seamless integration with other XML tag sets. The XForms specification is available at http://www.w3.org/TR/xforms/ It has also been widely implemented in commercial applications, many of which are listed at http://www.w3.org/MarkUp/Forms/#implementations Additional information on XForms is available at http://www.w3.org/MarkUp/Forms/ Besides the ability to fill out and submit forms and to collaboratively author documents on the Web, another set technical requirements applicable not only to the FM LOB but to all LOBs relates to records management. The international standard for records management is ISO 15489, which outlines the four attributes of a record -- integrity, reliability, authenticity, and usability. The purpose of all IT systems is to create records having sufficient degrees of those attributes, consistent with the requirements of the business process, including the need to be able to efficiently and effectively audit data maintained in databases. Additional information on ISO 15489 is available at http://www.iso.ch/iso/en/commcentre/pressreleases/2002/Ref814.html The U.S. federal government’s standard for records management is DoD Std. 5015.2. Although the standard was specified by the Department of Defense (DoD), it has been endorsed for government-wide use by the National Archives and Records Administration (NARA). NARA’s bulletin endorsing the standard 9 of 16
  • 11. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 is available at http://www.archives.gov/records_management/policy_and_guidance/bulletin_2003_03.html DoD tests and certifies commercial products for compliance with the standard. A listing of applications that have been certified is available at http://jitc.fhu.disa.mil/recmgt/register.htm Additional information on the 5015.2 standard is available at http://jitc.fhu.disa.mil/recmgt/ With reference to records management, two other specifications that warrant consideration are the emerging PDF Archive (PDF-A) standard and Extensible Forms Description Language (XFDL). Under leadership of the U.S. Courts and with the active support of the Government Accountability Office (GAO) and other agencies, the Association for Information and Image Management (AIIM) is shepherding PDF-A toward establishment as an ISO standard for archival records. Although archives are commonly viewed as dusty repositories of documents that are seldom, if ever used, the U.S. Courts, GAO, and other enlightened agencies are beginning to understand the vital business connection between electronic records whose integrity is inviolate versus data that is subject to manipulation in databases. Additional information on PDF-A is available at http://www.aiim.org/pdf_a/ XFDL has been proposed for establishment as a W3C recommendation for legally sufficient “transaction records” (forms). The W3C’s note on XFDL is available at http://www.w3.org/TR/1998/NOTE- XFDL-19980902 Although software vendors have been slow to recognize the need to ensure that transaction records have all four of the attributes outlined in ISO 15489, agencies like the Securities and Exchange Commission (SEC) and the U.S. Air Force (USAF) have placed priority on the requirements specified in XFDL in the selection of their forms automation components. To the degree that records are maintained in inviolate, nonproprietary, valid XML format in DoD-certified electronic records management systems (ERMSs) throughout their full life-cycles, the process of auditing transactional data in databases can largely be automated. With respect to the audit function, it is no stretch of logic to suggest that IT systems which are not designed to facilitate record-keeping and auditing are, in effect, enabling waste, fraud, and abuse. Too many examples are documented in the news media every day to ignore the shortcomings of “business as usual” with respect to IT investments. By their very nature, financial records are often highly sensitive and require high degrees of protection to ensure they have the attributes outlined in ISO 15489. At the very least, IT systems that do not make it easy to conduct audits are making it more difficult and expensive than necessary to protect the rights and interests of citizens as well as government officials. In an annual poll conducted by the Council for Excellence in Government, on three successive years the largest benefit of electronic government cited by members of the public is greater accountability of government official. http://www.excelgov.org/displayContent.asp? NewsItemID=3399&Keyword=mReleases However, greater accountability will not occur unless and until IT systems and business record-keeping practices are designed and implemented to support it. The components of those systems and practices are especially important in the FM LOB and the FM LOB should exert strong and effective leadership in implementing them. However, to greater or lesser degrees, the very same requirements apply to all LOBs. Indeed, record-keeping is a distinguishing factor for business versus purely social activities. The Statement on Auditing Standards (SAS) No. 70, Service Organizations, is an internationally recognized auditing standard developed by the American Institute of Certified Public Accountants (AICPA). Its intent is to document that a service organization has been through an in-depth audit of their control activities, which generally include controls over information technology and related processes. Additional information on SAS 70 is available at http://www.sas70.com/about.htm#about%20100 Some have questioned the value of SAS 70 audits. See, for example, http://www.systemexperts.com/tutors/sas70.pdf 10 of 16
  • 12. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 However, since the standard has been specified by AICPA and auditability is of particular importance with respect to financial records and IT systems, SAS 70 appears to warrant serious consideration for application to the FM LOB centers of excellence. Table 2 contains a listing of the FM LOB Target Business Processes mapped to the FEA Service Component Reference Model (SRM). A number of technical standards have been identified that may be applicable to the FM service components, and Web references have been provided for each of them. However, it will be necessary for subject matter experts (SMEs) to identify and provide rationales for the standards pertinent specifically to FM. This listing is by no means comprehensive or authoritative. At best, it should be taken as a starting point for further consideration by the SMEs. Establishing service standards is not something that can be done by a centralized bureaucracy acting in isolation from front-line workers. Modern management practice dictates not only that those workers be supportive of performance goals and objectives but also that they be actively engaged in establishing those standards. Moreover, the scope and scale of the FM LOB is such that no single individual or group can possibly acquire and retain sufficient knowledge and expertise to do justice to these standards. A truly collaborative effort will be required. Table 2: Target Business Processes, SRM Components, and Technical Standards Target Business SRM Technical Standard Rationale Process Component GL - Manage GL Transaction Data Integration ISO/IEC 11179 ISO/IEC 11179 is the international standard for the specification and standardization of data elements. IDEF1x http://pueblo.lbl.gov/~olken/X3L8/drafts/draft.docs.ht ml OMB Information Quality Guidelines IDEF1X is a method for designing relational http://www.whitehouse.gov/o databases with a syntax designed to support the mb/inforeg/agency_info_quali semantic constructs necessary in developing a ty_links.html conceptual schema. http://www.idef.com/idef1x.html Metamatrix provides an instructive, albeit proprietary, overview of Enterprise Information Integration (EII) at http://www.dmreview.com/whitepaper/wid339.pdf Informatica provides a similarly proprietary overview of Universal Data Services (UDS) at http://www.informatica.com/products/architecture/ud s_technote_0422904.pdf CM - Define Model Instrumentation IEEE standards on instrumentation and and Testing measurement are listed at http://standards.ieee.org/catalog/olis/im.html However, few, if any of them are directly applicable to the FM LOB. GL - Manage GL Transaction Billing and AICPA’s Accounting Standards page is at PM - Manage Payment Accounting http://www.aicpa.org/members/div/acctstd/ RM - Manage Receivable RM - Manage Collection The Financial Accounting Standards Board’s RM - Manage Treasury technical inquiry service is at Execution http://www.fasb.org/inquiry/ However, any standards they may have issued are not self-evident. ACORD is fostering billing standards in the insurance industry, but those standards may or may not be reusable in the FM LOB. http://www.acord.org/Standards/pdfs/AIG.pdf PM - Manage Payment Credit / Charge Fair Credit Reporting Act The U.S. Chamber of Commerce addresses national RM - Manage Collection (FCRA) credit standards at http://www.uschamber.com/government/issues/econt ax/fcra.htm The Credit Standards Advisory Committee is summarized at http://www.docloan.com/loans/loan_terms/Credit- 11 of 16
  • 13. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Target Business SRM Technical Standard Rationale Process Component Standards-Advisory-Committee-Csac The term “credit standards” is defined at http://www.moneyglossary.com/? w=Credit+Standards PM - Manage Payment Debt Collection A discussion of standards for debt collection under RM - Manage Treasury the Fair Debt Collection Practices Act (FDCPA) is at Execution http://www.lectlaw.com/files/ban07.htm RM - Manage Collection RM - Manage Receivable RPT - Generate Financial Financial Reporting Extensible Business XBRL is a language for the electronic Statement Reporting Language (XBRL) communication of business and financial data that aims to revolutionize business reporting around the IASB International Financial world. http://www.xbrl.org/Home/ Reporting Standards http://www.iasb.org/standards /index.asp See also http://www.asb.org.uk/asb/tec hnical/standards.cfm RPT - Generate Financial Auditing Government Auditing AICPA’s Accounting Standards page is at Statement Standards ( GAO’s Yellow http://www.aicpa.org/members/div/acctstd/index.htm Book) http://www.gao.gov/govaud/y AICPA’s Audit and Attest Standards page is at http:// bk01.htm www.aicpa.org/members/div/auditstd/index.htm Standards Recently Issued by AICPA http://www.aicpa.org/member s/div/auditstd/riasai/index.htm SAS No. 70 http://www.sas70.com/about. htm#about%20100 AICPA Proposed Statement on Auditing Standards http://www.aicpa.org/downloa d/auditstd/2003_0318_SSAE _intcontrl.pdf RM - Manage Treasury Payment / ANSI X9.59 ANSI standard for secure financial transactions. Execution Settlement Provides sufficient detail for software vendors to create components of payment systems that interoperate between conforming consumer systems and conforming merchant systems. http://www.ca0.net/X9App.html FM - Evaluate Budget Balanced While no standards directly relevant to Balanced Scorecard Scorecards have been identified, useful information on the basics of Balanced Scorecards is available at http://www.quickmba.com/accounting/mgmt/balance d-scorecard/ Guidelines for implementing a Balanced Scorecard are provided at http://www.qpr.com/protected/whitepapers/QPR_Imp lementing_BSCpdf.pdf FM - Develop Program Decision Support Abstract for article on standard, reusable software FM - Formulate Budget and Planning components for decision support FM - Support Budget http://portal.acm.org/citation.cfm? Execution id=635747&dl=ACM&coll=portal FM - Reprogram Funds CM - Perform Analysis Mathematical MathML MathML is a W3C specification for describing mathematics as a basis for machine to machine communication. It provides a foundation for the inclusion of mathematical expressions in Web 12 of 16
  • 14. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Target Business SRM Technical Standard Rationale Process Component pages. http://www.w3.org/Math/ CM - Perform Analysis Modeling BPMN Business Process Modeling Notation (BPMN) as a standard notation for business process modeling. http://www.bpmi.org/PR.esp?id=301 FM - Formulate Budget Predictive A set of statistics and probability standards for students is provided at http://www.wrsd.net/mathematicsstandard9.htm CM - Define Model Structural/Thermal FM - Evaluate Budget Performance ANSI/EIA 748-A-1998, Some project performance management standards Management Guidelines for EVM Systems are listed at http://www.dtic.mil/ndia/2002c http://www.pmforum.org/prof/standard.htm#PPMS mmi/solomon2b1.pdf However, they are not readily identifiable or obtainable. FM - Develop Program Portfolio The Project Management Institute is working on an FM - Support Budget Management standard for program/portfolio management. Execution http://www.pmi.org/info/PP_ProgPortStnd.asp FM - Reprogram Funds FM - Construct Plan Strategic Planning A proposal has been submitted to AIIM for & Management specification of an XML schema as an international standard for strategic plans. http://www.xml.gov/draft/AIIMProjectProposalXSDfor StrategicPlans.htm FM - Develop Program Requirements Requirements management is addressed at FM - Support Budget Management http://www.iturls.com/English/SoftwareEngineering/S Execution E_36.asp & http://www.cutter.com/cgi-bin/catalog/store.cgi? action=link&sku=RP18DC & http://www.galaxyscientific.com/areas/infoassurance/ rm.htm However, it is unclear whether any standards have been specified. GL - Manage GL Structure Change IBM addresses the phases and steps of change Management management at http://www-1.ibm.com/services/us/its/pdf/cwp- itchangemgmt.pdf Links to commercial, scenario-based change management resources are provided at http://www.change-management.com/how-to-guide- g.htm CM - Define Model Configuration IEEE Std. 828-1009, The Project Management Institute has initiated an Management Software Configuration effort to develop a standard for the practice of Management Plans configuration management. http://www.pmi.org/info/ PP_ConfigMgmt.asp IEEE 1042-1987, Guide to Software Configuration Additional software configuration management Management standards are listed at http://www.12207.com/test.htm & http://www.assetmanagement- toolkit.com/ConfigurationManagementStandards.htm l& http://www.snuffybear.com/ucmcentral_standards.ht m GL - Manage GL Structure Governance / Policy Management FM - Support Budget Requirements Requirements management is addressed at Execution Management http://www.iturls.com/English/SoftwareEngineering/S CM - Define Model E_36.asp & CM - Populate Model http://www.cutter.com/cgi-bin/catalog/store.cgi? CM - Perform Analysis action=link&sku=RP18DC & http://www.galaxyscientific.com/areas/infoassurance/ rm.htm However, it is unclear whether any standards have been specified. CM - Define Model Risk Management ISO/IEC Guide 73, Risk Additional risk management standards are RM - Manage Treasury management – Vocabulary – addressed at Execution Guidelines http://www.airmic.com/RiskManagementStandard.as RPT - Generate Financial http://www.iso.ch/iso/en/com p, 13 of 16
  • 15. FM LOB Target Architecture Deliverable # 8: Target Technology Standards July 30, 2004 Target Business SRM Technical Standard Rationale Process Component Statement mcentre/pressreleases/2002/ http://www.airmic.com/AIRMIC_RiskManagementSta CM - Populate Model Ref833.html ndard.pdf & CM - Perform Analysis http://www.idrisk.com/uploads/AIRMIC.pdf as well as http://www.zurich.co.uk/strategicrisk/referencelibrary/ Riskmanagementstandards.htm & http://sparc.airtime.co.uk/users/wysywig/risk_1.htm CM - Populate Model Configuration IEEE Std. 828-1009, The Project Management Institute has initiated an Management Software Configuration effort to develop a standard for the practice of Management Plans configuration management. http://www.pmi.org/info/ PP_ConfigMgmt.asp IEEE 1042-1987, Guide to Additional software configuration management Software Configuration standards are listed at Management http://www.12207.com/test.htm & http://www.assetmanagement- toolkit.com/ConfigurationManagementStandards.htm l& http://www.snuffybear.com/ucmcentral_standards.ht m 2. Conclusion The identification and enhancement of the Target Technology Standards will improve FM across the Federal Government by establishing an open, standards-based, market-driven approach to a shared services model, target architecture, and standardized set of business processes. This methodology supports the vision of the FM LOB by improving business performance while ensuring integrity in accountability, financial controls, and mission effectiveness. However, realizing the vision will require additional, ongoing engagement of the subject matter experts and front-line workers in a truly collaborative effort over an extended period of time. 14 of 16

×