Loading...
HomeMy WebLinkAboutContract 43341i i i SECRETARY 33N1 f i dw CITY OF FORT WORTH AND CIBER, INC. aft ERP PHASE II CONTRACT DOCUMENTS fm aft .n m r t. MR OFFICIAL RECORD "' CITY SECRETARY FT. WORTH, TX �r 06-21-12 Pi)3: 52 IN i TABLE OF CONTENTS PROFESSIONAL SERVICES CONTRACT............................................................................................................1 EXHIBIT A - STATEMENT OF WORK..............................................................................................................16 EXHIBIT B - PAYMENT SCHEDULE................................................................................................................94 EXHIBIT C - NONDISCLOSURE AGREEMENT...............................................................................................120 EXHIBIT D - NETWORK ACCESS AGREEMENT............................................................................................125 EXHIBIT E - DELIVERABLE ACCEPTANCE FORM.........................................................................................129 EXHIBITF - MWBE FORM..........................................................................................................................130 EXHIBIT G - INITIAL TECHNICAL SCOPE AND ESTIMATES..........................................................................131 EXHIBIT H - INSURANCE CERTIFICATE.......................................................................................................201 EXHIBIT I -SOFTWARE REQUIREMENTS AND RESPONSES.......................................................................202 EXHIBITJ - DISPOSITION OF CIBER EXCEPTIONS TO RFP TERMS AND CONDITIONS.................................203 EXHIBIT K - DELIVERABLES CROSS REFERENCE..........................................................................................208 EXHIBIT L- SAMPLE DELIVERABLE DEFINITION DOCUMENTS(DDD)........................................................217 EXHIBIT M - LIST OF SOFTWARE REQUIREMENTS THAT ARE KNOWN TO BE SUPPORTED BY MODULES NOTIN SCOPE............................................................................................................................................226 EXHIBIT N: SYSTEMS TO BE REPLACED......................................................................................................227 EXHIBIT O: REFINEMENTS AND CLARIFICATIONS TO APPENDIX N WORK -PRODUCT DESCRIPTIONS ....... 231 EXHIBIT P: PROPOSED STAFFING PLAN.....................................................................................................240 EXHIBIT Q: VERIFICATION OF SIGNATURE AUTHORITY.............................................................................244 SOFTWARE REQUIREMENTS AND RESPONSES REFERENCED BY EXHIBIT I...............................................245 M&C C-25669............................................................................................................................................407 PROFESSIONAL SERVICES CONTRACT This Professional Services Agreement ("Agreement") is made and entered into by and between the City of Fort Worth (the "City"), a home rule municipal corporation organized under the laws of the State of Texas, located in Tarrant, Denton and Wise Counties, Texas, with its principal location at 1000 Throckmorton Street, Fort Worth, Texas 76102, acting by and through Susan Alanis, its duly authorized Assistant City Manager, and CIBER, Inc. ("Contractor"), a Delaware corporation, with its principal location at 6363 South Fiddler's Green Circle, #1400, Greenwood Village, CO 80111, acting by and through Rick Genovese, its duly authorized Executive Vice President and Chief Operating Officer/representative. CONTRACT DOCUMENTS: The Contract Documents shall include the following: A. This Professional Services Agreement plus any attachments hereto shall include: a) Exhibit A — Statement of Work b) Exhibit B — Payment Schedule Exhibit B.1 — Phase IIA Exhibit B.2 — Phase IIB Exhibit B.3 — Phase IIC c) Exhibit C — Nondisclosure Agreement d) Exhibit D — Network Access Agreement e) Exhibit E — Milestone Acceptance Form f) Exhibit F — Minority and Women Business Enterprise (M/WBE) Form g) Exhibit G — Initial Technical Scope and Estimates h) Exhibit H — Insurance Certificate i) Exhibit I — Software Requirements and Responses j) Exhibit J — Disposition of CIBER Exceptions to RFP Terms and Conditions k) Exhibit K — Deliverables Cross Reference 1) Exhibit L — Sample Deliverable Definition Documents (DDD) m) Exhibit M — List of Software Requirements that are known to be supported by modules not in scope n) Exhibit N — Systems to Be Replaced o) Exhibit O — Refinements and Clarifications to Appendix N Work -Product Descriptions p) Exhibit P — Proposed Staffing Plan q) Exhibit Q — Signature Authority Form Any reference to Prime Vendor or Responder in the attachments is considered a reference to CIBER, Inc. B. The following documents from the City of Fort Worth Request for Proposals No. 10-0364 for Oracle PeopleSoft Financial and Supply Chain Management Software and Oracle Hyperion Budget Preparation Software Implementation Services (the "RFP") are incorporated herein by reference, in order of precedence: a) Contractor's Best and Final Offer (BAFO) b) The City's Request for Best and Final Offer c) Contractor's Proposal to the RFP (Proposal) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 1 of 418 d) The City's Request for Proposals All documents referenced herein in this section and any and all exhibits attached hereto are hereby incorporated herein and become a part of this Agreement for all purposes. In the event of a conflict between the documents the order of precedence shall be (a) this Professional _ Services Agreement and its attachments, including any formally approved change orders and/or amendments subsequent to execution of this Agreement; (b) the BAFO; (c) The City's request for BAFO; (d) the Proposal; and (e) the RFP. SCOPE OF SERVICES. Contractor hereby agrees to provide the City with professional consulting services for the purpose of implementing Oracle PeopleSoft Financial Management Software and Oracle Hyperion Budget Preparation Software ("the Oracle ERP Software Suite") and to provide professional consulting services to implement PeopleSoft Supply Chain Management Software, if the City exercises the option for such services, as defined in Exhibit A — Statement of Work, Section 2.0 General Obligations and Scope of Project and any related applications, tools, and hardware. Attached hereto and incorporated for all purposes incident to this - Agreement is Exhibit A - Statement of Work, more specifically describing the services to be provided hereunder. The term "Contractor" shall include Contractor, its officers, directors, employees, agents, representatives, and subcontractors. 2. TERM. This Agreement shall commence upon the last date that both the City and the Contractor have executed this Agreement ("Effective Date") and shall continue in full force and effect until March 31, 2016, unless terminated earlier in accordance with the provisions of this Agreement. If all services have not been completed by March 31, 2016, the parties may extend the term of this Agreement for an additional one year period through March 31, 2017. The term of this Agreement shall not be extended beyond March 31, 2017 unless extended by written agreement of the parties. 3. COMPENSATION. The City shall pay the Contractor an amount not to exceed $16,523,521 in accordance with the provisions of this Agreement and the Payment Schedule attached as Exhibit B, which is incorporated for all purposes herein. The Contractor shall not perform any additional services for the City not specified by this Agreement unless the City requests and approves in writing the additional costs for such services. The City shall not be liable for any additional expenses of the Contractor not specified by this Agreement unless the City first approves such expenses in writing. 4. TERMINATION. 4.1 For Convenience upon Written Notice. The City or Contractor may terminate this Agreement at any time and for any reason by providing the other party with 60 days written notice of termination. All Statements of Work ("SOWs") in effect as of the Agreement's termination date shall continue until completed or terminated as provided in this Section. Within City's termination notice, City will state which City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 2 of 418 fixed fee deliverables City desires Contractor to complete. Upon receipt of the termination notice, Contractor will advise City of the extent to which performance has been completed. In the event of such termination by the City, City will pay (i) in full for all completed and accepted Services and deliverables as of the date of the termination notice, and (ii) all deliverables in process that Contractor is requested to complete in accordance with the milestones established in the Deliverable Definition Document (as such document is defined in the SOW) for such deliverables in process. Both parties recognize that the completion dates for such _ deliverables in process may extend outside the effective date of termination and (iii) for partially completed deliverables, based on percent complete of the milestones for such deliverables set forth in the Deliverable Definition Document. Additionally, upon termination, City will release all applicable retainage. 4.2 Breach or Default. Either party may terminate this Agreement if the other party fails to cure a material breach or default within thirty (30) calendar days of receipt of written notice being given by the other party. If more than thirty (30) calendar days are required to cure such default or breach, a reasonable time in excess of said days may be established, provided both parties agree in writing as to the time period to be substituted. In the event such default or breach is not cured within the specified time frame, the non -breaching party may terminate this Agreement immediately upon written notification. If City terminates this Agreement or any SOW for CIBER's breach or default, City is obligated to pay for all undisputed Services and Deliverables accepted by City up through the effective date of termination. If City terminates this Agreement or any SOW for breach or default, the City shall be entitled to withhold all applicable retainage under this Agreement until a determination is made of whether CIBER has caused a breach or default that was not cured by CIBER as set forth in this section. If it is determined that CIBER has failed to cure a breach or default as set forth in this section, then the City is entitled to withhold all applicable retainage. If CIBER terminates this Agreement or any SOW for the City's breach or default, City is obligated to pay for all (i) undisputed Services and Deliverables that are completed and accepted as of the effective date of termination and (ii) for partially completed deliverables, based on percent complete of the milestones for such deliverables as set forth in the Deliverable Definition Document through the effective date of termination. If CIBER terminates this Agreement or any SOW for City's breach or default, and a determination is made that the City has failed to cure such breach or default as set forth in this section, then the City shall release all applicable retainage held by City. 4.3 Non -appropriation of Funds. In the event no funds or insufficient funds are appropriated by the City in any fiscal period for any payments due hereunder, City will promptly notify the Contractor of such occurrence and this Agreement shall terminate on the last day of the fiscal period for which appropriations were received without penalty or expense to the City of any kind whatsoever, except as to the portions of the payments herein agreed upon for which funds have been appropriated. 4.4 Duties and Oblioations of the Parties. In the event that this Agreement is terminated prior to the Expiration Date, the City shall pay the Contractor for services actually rendered up to the effective date of termination and the Contractor shall continue to provide the City with services requested by the City and in accordance with this Agreement up to the effective date of termination. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 3 of 418 5. DISCLOSURE OF CONFLICTS AND CONFIDENTIAL INFORMATION. Contractor hereby warrants to the City that the Contractor has made full disclosure in writing of any existing or potential conflicts of interest related to the Contractor's services under this Agreement. In the event that any conflicts of interest arise after the Effective Date of this Agreement, the Contractor hereby agrees immediately to make full disclosure to the City in writing. The Contractor, for itself and its officers, agents and employees, further agrees that it shall treat all information provided to it by the City as confidential and shall not disclose any such information to a third party without the prior written approval of the City in accordance with the applicable Non -Disclosure Agreement. The Contractor shall store and maintain City Information in a secure manner and shall not allow unauthorized users to access, modify, delete or otherwise corrupt City Information in any way. The Contractor shall notify the City immediately if the security or integrity of any City information has been compromised or is believed to have been compromised in which event, Contractor shall, in good faith, use all commercially reasonable efforts to cooperate with the City in identifying what information has been accessed by unauthorized means and shall fully cooperate with the City to protect such information from further unauthorized disclosure. 6. RIGHT TO AUDIT. The Contractor agrees that the City shall, until the expiration of three (3) years after final payment under this contract, have access to and the right to examine at reasonable times any directly pertinent books, documents, papers and records of the Contractor involving transactions relating to this Contract at no additional cost to the City. The Contractor agrees that the City shall have access during normal working hours to all necessary Contractor facilities and shall be provided adequate and appropriate work space in order to conduct audits in compliance with the provisions of this section. The City shall give the Contractor reasonable advance notice of intended audits. Contractor further agrees to include in all its subcontractor agreements hereunder a provision to the effect that the subcontractor agrees that the City shall, until expiration of three (3) years after final payment of the subcontract, have access to and the right to examine at reasonable times any directly pertinent books, documents, papers and records of such subcontractor - involving transactions related to the subcontract, and further that City shall have access during normal working hours to all subcontractor facilities and shall be provided adequate and appropriate work space in order to conduct audits in compliance with the provisions of this paragraph. City shall give subcontractor reasonable notice of intended audits. 7. INDEPENDENT CONTRACTOR. It is expressly understood and agreed that the Contractor shall operate as an independent contractor as to all rights and privileges granted herein, and not as agent, representative or employee of the City. Subject to and in accordance with the conditions and provisions of this Agreement, the Contractor shall have the exclusive right to control the details of its operations and activities and be solely responsible for the acts and omissions of its officers, agents, servants, employees, contractors and subcontractors. The Contractor acknowledges that the doctrine of respondeat superior shall not apply as between the City, its officers, agents, servants and employees, and the Contractor, its officers, agents, employees, servants, contractors and subcontractors. The Contractor further agrees that nothing herein shall be construed as the creation of a partnership or joint enterprise between City and the Contractor. _ City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 4 of 418 It is further understood that the City shall in no way be considered a Co -employer or a Joint employer of Contractor or any officers, agents, servants, personnel, employees or subcontractors of Contractor. Neither Contractor nor any officers, agents, servants, personnel, employees or subcontractors of Contractor shall be entitled to any employment benefits from the City. Contractor shall be responsible and liable for any and all payment and reporting of taxes on behalf of itself, and any of its officers, agents, servants, personnel, employees or subcontractors 8. LIABILITY AND INDEMNIFICATION. 8.1 LIABILITY THE CONTRACTOR SHALL BE LIABLE AND RESPONSIBLE FOR ANY AND ALL PROPERTY LOSS, PROPERTY DAMAGE AND/OR PERSONAL INJURY, INCLUDING DEATH, TO ANY AND ALL PERSONS, OF ANY KIND OR CHARACTER, WHETHER REAL OR ASSERTED, TO THE EXTENT CAUSED BY THE NEGLIGENT ACT(S) OR OMISSION(S), MALFEASANCE OR INTENTIONAL MISCONDUCT OF THE CONTRACTOR, ITS OFFICERS, AGENTS, SERVANTS OR EMPLOYEES EXCEPT TO THE EXTENT CAUSED BY THE NEGLIGENT ACT(S) OR OMISSION(S), MALFEASANCE OR INTENTIONAL MISCONDUCT OF THE CITY, ITS OFFICERS, AGENTS, SERVANTS AND EMPLOYEES. 8.2 INDEMNIFICATION. THE CONTRACTOR COVENANTS AND AGREES TO, AND DOES HEREBY, INDEMNIFY, HOLD HARMLESS AND DEFEND THE CITY, ITS OFFICERS, AGENTS, SERVANTS AND EMPLOYEES, FROM AND AGAINST ANY AND ALL CLAIMS OR. LAWSUITS FOR EITHER PROPERTY DAMAGE OR LOSS (INCLUDING ALLEGED DAMAGE OR LOSS TO THE CONTRACTOR'S BUSINESS AND ANY RESULTING LOST PROFITS) AND/OR PERSONAL INJURY, INCLUDING DEATH, TO ANY AND ALL PERSONS, OF ANY KIND OR CHARACTER, WHETHER REAL OR ASSERTED, ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT, TO THE EXTENT CAUSED BY THE NEGLIGENT ACTS OR OMISSIONS OR MALFEASANCE OF THE CONTRACTOR, ITS OFFICERS, AGENTS, K SERVANTS OR EMPLOYEES EXCEPT TO THE EXTENT CAUSED BY THE NEGLIGENT ACT(S) OR OMISSION(S), MALFEASANCE OR INTENTIONAL MISCONDUCT OF THE CITY, ITS OFFICERS, AGENTS, SERVANTS AND EMPLOYEES. CONTRACTOR'S INDEMNITY OBLIGATIONS ARE EXPRESSLY CONDITIONED UPON THE FOLLOWING: (1) THAT CITY SHALL PROMPTLY NOTIFY CONTRACTOR IN WRITING; (2) THAT CONTRACTOR SHALL HAVE CONTROL OF THE DEFENSE OR SETTLEMENT; (3) THAT CITY SHALL COOPERATE WITH CONTRACTOR IN A REASONABLE WAY TO FACILITATE THE SETLEMENT OR DEFENSE. 8.3 LIMITATION OF LIABILITY NEITHER PARTY WILL BE LIABLE TO THE OTHER PARTY FOR ANY LOST DATA, LOST PROFITS, OR INCIDENTAL, CONSEQUENTIAL, PUNITIVE, SPECIAL, OR OTHER INDIRECT DAMAGES OF ANY KIND FOR ANY REASON WHATSOEVER INCLUDING, BUT NOT LIMITED TO, DAMAGES BASED UPON, CONTRACT, WARRANTY, TORT, NEGLIGENCE, STRICT LIABILITY, OR ANY OTHER THEORY EVEN IF A PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. EACH PARTY AGREES City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 5 of 418 THAT THE OTHER PARTY'S LIABILITY HEREUNDER FOR DAMAGES, REGARDLESS OF THE FORM OF ACTION, WILL NOT EXCEED THE TOTAL AMOUNT ACTUALLY PAID FOR SERVICES AND WORK PRODUCTS FOR THE CORRESPONDING PHASE SET FORTH IN Exhibit B — PAYMENT SCHEDULE UNDER THE APPLICABLE SOW GIVING RISE TO THE DAMAGES. �. 9. ASSIGNMENT AND SUBCONTRACTING. The Contractor shall not assign or subcontract any of its duties, obligations or rights under this Agreement without the prior written consent of the City. If the City grants consent to an assignment, the assignee shall execute a written agreement with the City and the Contractor under which the assignee agrees to be bound by the duties and obligations of the Contractor under this Agreement. The Contractor and Assignee shall be jointly liable for all obligations under this Agreement prior to the assignment. If the City grants consent to a subcontract, the subcontractor shall execute a written agreement with the Contractor referencing this Agreement under which the subcontractor shall agree to be bound by the duties and obligations of the Contractor under this Agreement as such duties and obligations may apply. The Contractor shall provide the City with a fully executed copy of any such subcontract. �- In accordance with City of Fort Worth policies, the City has goals for the participation of Minority Business Enterprises and Women Business Enterprises (M/WBE) in City contracts. Contractor acknowledges that the M/WBE goal established for this contract is twenty-six percent (26%), and acknowledges its commitment to meet that goal. Contractor shall provide a "Letter of Intent" in the form designated by the City evidencing such commitment. Any misrepresentation of facts (other than a negligent misrepresentation) and/or the commission of fraud by the Contractor may result in the termination of this Agreement and debarment from participating in City contracts for a period of time of not less than three (3) years. Contractor will submit information concerning the M/WBE (s) that will participate in the contract to meet the set goal in the manner and form as prescribed by the City, including (1) the name, address and telephone number of each M/WBE; (2) the description of the work to be performed by each M/WBE; and (3) the approximate dollar amount/ percentage of the participation. If -- Contractor fails to meet the stated goal, then the Contractor must submit detailed documentation of good and honest efforts as to why the goal was not achieved. 10. INSURANCE. The Contractor shall provide the City with certificate(s) of insurance documenting policies of the following minimum coverage limits that are to be in effect prior to commencement of any work pursuant to this Agreement: 10.1 Workers' Compensation Insurance: Except as provided below, the Contractor must provide Workers' Compensation insurance for all its employees and, in case any work is subcontracted, the Contractor will require the subcontractor to provide Workers' Compensation ` insurance in accordance with the requirements of the City, including Coverage B, Employer's Liability: Insurance minimum amounts are as follows: • $100,000 —Bodily Injury by Disease per employee • $500,000 — Bodily Injury by Disease aggregate $100,000 —Bodily Injury by Accident If City exempts the Contractor from Workers' Compensation insurance or if the Contractor has no employees in the City, the Contractor must provide a written statement, signed by an City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 6 of 418 authorized representative, indicating the qualifying exemption that excludes the Contractor from the City's Workers' Compensation requirements. 10.2 Commercial General Liability: The Contractor is required to maintain insurance protecting it from claims for damages for bodily injury, including sickness or disease, death, and for care and loss of services as well as from claims for property damage, including loss of use which may arise from operations under the Contract whether the operations are by the Contractor or by a subcontractor or by anyone directly or indirectly employed by the Contractor under the contract. Insurance minimum amounts are as follows: • $1,000,000 — per occurrence • $2,000,000 — annual aggregate • $2,000,000 — annual aggregate-Products/Completed Operations The following coverage shall be included: • Premises and Operations Bodily Injury and Property Damage • Personal and Advertising Injury • Blanket Contractual Liability • Products and Completed Operations Liability • Other; please list • City named as an Additional Insured 10.3 Commercial Automobile Liability: The Contractor is required to maintain insurance protecting the contractor from claims for damages for bodily injury as well as from claims for property damage resulting from the ownership, operation, maintenance or use of all owned, hired, and non -owned autos which may arise from operations under this contract, and in case any work is subcontracted the Contractor will require the subcontractor to provide Commercial Automobile Liability. Insurance minimum amounts are as follows: $1,000,000 — per occurrence Combined Single limit for Bodily Injury and Property Damage • In addition, the following coverage should be included: ■ Owned, Hired, and Non -owned Automobile • City named as an Additional Insured 10.4 Technology Liability (E&O) $1,000,000 Each Claim Limit $1,000,000 Aggregate Limit Coverage shall include but not be limited to the following: ■ Failure to prevent unauthorized access ■ Unauthorized disclosure of information ■ Implantation of malicious code or computer virus ■ Fraud, Dishonest or Intentional Acts with final adjudication language Technology coverage may be provided through an endorsement to the Commercial General Liability (CGL) policy, or a separate policy specific to Technology E&O. Either is acceptable if coverage meets all other requirements. Any deductible will be the sole responsibility of the Contractor and may not exceed $2,500,000 for the errors and omissions policy and $50,000 v for other policies without the written approval of the City. Coverage shall be claims -made, with City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 7 of 418 a retroactive or prior acts date that is on or before the effective date of this Contract. Coverage shall be maintained for the duration of the contractual agreement and for two (2) years following completion of services provided. An annual certificate of insurance shall be submitted to the City to evidence coverage. 10.5 Additional Insurance Conditions: • Contractor's policy(ies) shall be primary insurance to any other valid and collectible insurance available to the City with respect to any claim arising out of this contract. • Contractor's policy(ies) will provide the City with thirty (30) days advance notice of cancellation, non -renewal, or reduction in limits of coverage or other material change. • Notice shall be sent to the Risk Manager, City of Fort Worth, 1000 Throckmorton, Fort Worth, Texas 76102, with copies to the City Attorney at the same address. • Policies shall have no exclusions by endorsements which nullify the required lines of coverage, nor decrease the limits of said coverage unless such endorsements are approved by the City. • If insurance policies are not written for specified coverage limits, an Umbrella or Excess Liability insurance for any difference is required. Excess Liability shall follow form of the -- primary coverage. • Contractor is responsible for payment of Contract related insurance premiums and deductibles. • Any deductible in excess of $2,500,000 for the errors and omissions policy and $50,000.00 for any policy that does not provide coverage on a first -dollar basis, must be acceptable to and approved by the City's Risk Manager and verified by the Contractor's latest audited financial statement. If the Contractor is self -insured, a Certificate of Self -Insurance must be attached and must be approved by the City. • Include legal defense fees in addition to its liability policy limits. • Obtain insurance policies from an insurance company having an "AM BEST" rating of A, Financial Size Category (FSC) VII or better and must be authorized to do business in the City. • The City will reserve the right to immediately terminate the contract if the Contractor is not in compliance with the insurance requirements and retains all rights to pursue any legal remedies against the Contractor. • All insurance policies where the City is named as an additional insured must be open to inspection by the City, and copies of policies must be submitted to the City's authorized representative upon written request. • The successful responder is required to submit acceptable evidence of insurance coverage requirements prior to commencing work under the contract. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 8 of 418 11. COMPLIANCE WITH LAWS, ORDINANCES, RULES AND REGULATIONS. The Contractor agrees to comply with all applicable federal, state and local laws, ordinances, rules and regulations. If the City notifies the Contractor of any violation of such laws, ordinances, rules or regulations, the Contractor shall immediately desist from and correct the violation. Contractor shall verify the identity and employment eligibility of all Contractor personnel who perform work under this Agreement. Contractor shall complete the Employment Eligibility Verification Form (1-9), maintain photocopies of all supporting employment eligibility and identity documentation for all Contractor personnel, and upon request, provide City with copies of all 1-9 forms and supporting eligibility documentation for each Contractor personnel who - perform work under this Agreement. Contractor shall establish appropriate procedures and controls so that no services will be performed by any worker who is not legally eligible to perform such services. Contractor shall provide City with a certification letter that it has complied with the verification requirements required by this Agreement. Contractor shall indemnify City from any penalties or liabilities due to violations of this provision. City shall have the right to immediately terminate this Agreement for violations of this provision by Contractor. 12. NON-DISCRIMINATION COVENANT. The Contractor, for itself, its personal representatives, assigns, subcontractors and successors in interest, as part of the consideration herein, agrees that in the performance of the Contractor's duties and obligations hereunder, it shall not discriminate in the treatment or employment of any individual or group of individuals on any basis prohibited by law. If any claim arises from an alleged violation of this non-discrimination covenant by the Contractor, its personal representatives, assigns, subcontractors or successors in interest, the Contractor agrees to assume such liability and to indemnify and defend the City and hold the City harmless from such claim. 13. NOTICES. Notices required pursuant to the provisions of this Agreement shall be conclusively determined to have been delivered when (1) hand -delivered to the other party, its agents, employees, servants or representatives, (2) delivered by facsimile with electronic confirmation of the transmission, or (3) received by the other party by United States Mail, registered, return receipt requested, addressed as follows: To The CITY: To CIBER, Inc. 1000 Throckmorton Street 6363 S. Fiddler's Green Circle, #1400 Fort Worth TX 76102-6311 Greenwood Village, CO 80111 Facsimile: (817) 392-8966 Facsimile: 303-224-4125 Attn: Lena H. Ellis, CFO Attn: Legal Department With copy to: City Attorney 1000 Throckmorton Street Fort Worth, Texas 76102 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 9of418 14. SOLICITATION OF EMPLOYEES. Neither the City nor the Contractor shall, during the term of this agreement and additionally for a period of one (1) year after its termination, solicit for employment or employ, whether as employee or independent contractor, any person who is or has been employed by the other during the term of this agreement, without the prior written consent of the person's employer. This restriction shall not apply to any employee or independent contractor who responds to a general solicitation of employment. 15. GOVERNMENTAL POWERS. It is understood and agreed that by execution of this Agreement, the City does not waive or surrender any of its governmental powers. 16. NO WAIVER. The failure of the City or the Contractor to insist upon the performance of any term or provision of this Agreement or to exercise any right granted herein shall not constitute a waiver of the City's or the Contractor's respective right to insist upon appropriate performance or to assert any such right on any future occasion. 17. GOVERNING LAW / VENUE. This Agreement shall be construed in accordance with the laws of the State of Texas. If any action, whether real or asserted, at law or in equity, is brought on the basis of this Agreement, venue for such action shall lie in state courts located in Tarrant County, Texas or the United States District Court for the Northern District of Texas, Fort Worth Division. 18. SEVERABILITY. If any provision of this Agreement is held to be invalid, illegal or unenforceable, the validity, legality and enforceability of the remaining provisions shall not in any way be affected or impaired. 19. FORCE MAJEURE. The City and Contractor shall exercise their best efforts to meet their respective duties and obligations as set forth in this Agreement, but shall not be held liable for any delay or omission in performance due to force majeure or other causes beyond their reasonable control (force majeure), including, but not limited to, compliance with any government law, ordinance or regulation, acts of God, acts of the public enemy, fires, strikes, lockouts, natural disasters, wars, riots, material or labor restrictions by any governmental authority, transportation problems and/or any other similar causes. 20. HEADINGS NOT CONTROLLING. Headings and titles used in this Agreement are for reference purposes only and shall not be deemed a part of this Agreement. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 10 of 418 21. REVIEW OF COUNSEL. The parties acknowledge that each party and its counsel have reviewed and revised this Agreement and that the normal rules of construction to the effect that any ambiguities are to be resolved against the drafting party shall not be employed in the interpretation of this Agreement or exhibits hereto. 22. AMENDMENTS. No amendment of this Agreement shall be binding upon a party hereto unless such .. amendment is set forth in a written instrument, which is executed by an authorized representative of such party. 23. ENTIRETY OF AGREEMENT. This Agreement, including the schedule of exhibits attached hereto and any documents incorporated herein by reference, contains the entire understanding and agreement between the City and Contractor, their assigns and successors in interest, as to the matters contained herein. Any prior or contemporaneous oral or written agreement is hereby declared null and void to the extent in conflict with any provision of this Agreement. 24. NETWORK SYSTEM ACCESS. Prior to performing any Services, Contractor, on behalf of its employees, agents and Subcontractors, as necessary, who require access to City data, software, and City Network Systems, shall execute the City's agreements and forms concerning system security, information access and protection of data as set forth in the Network Access Agreement attached hereto and incorporated herein as Exhibit D. 25. SIGNATURE AUTHORITY. The person signing this Agreement hereby warrants that he/she has the legal authority to execute this agreement on behalf of the respective party, and that such binding authority has been granted by proper order, resolution, ordinance or other authorization of the entity. This Agreement, and any amendment(s) hereto, may be executed by any authorized representative of Contractor whose name, title and signature is affixed on the Verification of Signature Authority Form, which is attached hereto as Exhibit "Q" and incorporated herein by reference. The other party is fully entitled to rely on this warranty and representation in entering into this Agreement. 26. ACCEPTANCE. Acceptance criteria and required approvals for Fixed Fee Deliverables shall be set forth in each Deliverable Definition Document (described in Exhibit A — Statement of Work), which shall be completed before work starts on a Fixed Fee Deliverable. The Deliverable Definition Document will also identify the City Representative who is authorized to approve the document, or in such other document that the parties mutually agree in writing, including without limitation, project charters or project governance plans. Each of the foregoing and the Deliverable Definition Document shall be incorporated into the Agreement by this reference. The Approval and Acceptance Process is set forth in the Statement of Work. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page I I of 418 Acceptance criteria for work provided under the not -to -exceed portion of this contract for development related work will be defined in the functional specification for the development object (defined as either a report, interface, automated conversion, enhancement or complex workflow requiring programming resources) and acceptance will be documented through the _ documented results of a formal unit test to be completed by a City Project Team Member, and reviewed by the City Project Manager or City Technical Team Lead. Acceptance criteria for work initiating through a formal change order process shall be defined as part of the change order, and shall follow the same acceptance process as Fixed Fee Deliverables. 27. INVOICE AND PAYMENT. Contractor will invoice charges for third party materials purchased pursuant to its Change Order upon delivery of the materials to City. Contractor will invoice time and materials charges for Services or Work Products biweekly. Contractor will invoice fixed price charges for Services or Work Products/Fixed Fee Deliverables in accordance with the payment schedule in the Exhibit B. Contractor will invoice for Custom Development biweekly for all development objects (Reports, Interfaces, Conversions, Enhancements and Complex Workflows (defined as those that cannot be configured without programming) as they are accepted through a formal unit testing process. CIBER will invoice for work associated with formal change orders in a manner R to be specified in the Change Order document. All invoices will be in Contractor's standard form, and shall be accompanied by a signed copy of the Deliverable Acceptance Form (as described in Exhibit E) and the Fixed Fee Deliverable document, unless specifically excepted from this requirement in the Fixed Fee Deliverable Definition document. Except for charges City disputes in good faith, all amounts less retainage are due and payable not more than 30 days from the date the invoice is received. City must raise any concern or dispute in writing within 30 days from the date of the invoice or the invoice will be presumed payable. City's dispute of any amounts will not delay its payment of undisputed charges. If City defaults in payment of any charges, CIBER may immediately suspend further performance under any or all SOWs. City will _ withhold 10% of all amounts invoiced by CIBER for retainage as reflected in the Payment Schedule. Upon implementation of the system in a production environment, City shall release 50% of the total amount of retainage, and the remaining 50% shall be released upon completion of the 120-day warranty period, less up to one hundred twenty-five percent (125%) of the value of unresolved warranty items. The value of unresolved items shall be upon mutual agreement. 28. TAXES. Charges do not include taxes including, but not limited to, sales, use, gross receipts, and ad valorem taxes, duties or similar charges ("Taxes") imposed on the Services or deliverables (exclusive of taxes based on the property or net income of Contractor). City will pay or reimburse Contractor for all Taxes. If City is exempt from taxes, a valid tax exemption certificate _ or direct pay permit (collectively, "Certificate") must be provided to Contractor upon execution of this Agreement or any applicable Taxes will be included on invoice to City. If City provides such a Certificate to Contractor, City agrees that Contractor is entitled to and will rely on the _ Certificate. If the City's tax-exempt status changes at any time during the term of the Agreement so that Taxes are imposed on the Services or deliverables, the parties agree to enter into a written change order for the imposition of such Taxes. In the event of a tax examination involving Taxes imposed on the Services or deliverables provided pursuant to this Agreement, City agrees to reasonably cooperate with Contractor in any such examination. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 12 of 418 29. OWNERSHIP. Unless the parties agree otherwise in writing, Work Products developed by Contractor pursuant to this Agreement belong to City. "Work Products" mean all data, documentation, materials, processes and procedures that are developed by Contractor or City as a part of any Deliverable to be submitted for the City's acceptance under this Agreement or any amendment hereto. City shall retain all right, title and interest to all "Work Products." This provision does not apply to third party works, products, or materials or to Contractor Materials as defined below. City acknowledges that Contractor is in the business of providing information technology consulting services and has accumulated expertise in this field and agrees that Contractor will retain all right, title, and interest in and to all Contractor Materials. "Contractor Materials" means all discoveries, concepts, and ideas, whether or not registerable under patent, copyright, or similar statutes, including, without limitation, patents, copyrights, trademarks, trade secrets, processes, methods, formulae, techniques, tools, solutions, programs, data, and documentation, and related modifications, improvements, and know-how, that Contractor, alone, or jointly with others, its agents or employees, conceives, makes, develops, acquires, or obtains knowledge of at any time before, after, or during the term of this Agreement without breach of Contractor's duty of confidentiality to City or the use of any City resources. If Contractor Materials are included in any Work Products, Contractor hereby grants City a perpetual, irrevocable, nonexclusive, worldwide, royalty free license to use, execute, reproduce, display, perform, _ distribute internally, and prepare for internal use "derivative works" as defined in the Copyright Act, 17 U.S.C. §101, based upon the Contractor Materials, solely in conjunction with the Work Products. Contractor's grant to City of any interest in the Services and Work Products is effective only upon City's payment of all fees and charges invoiced by Contractor. 30. RESIDUAL RIGHTS. Either party shall be free to use Residuals (as hereinafter defined) from any Confidential Information provided by the disclosing party for any purpose, including, without limitation, providing services or creating programming or materials for customers, subject to the obligation not to disclose confidential information as required by applicable federal, state or local laws, publish or disseminate such Confidential Information and subject to the patent rights and statutory copyrights of the other party. "Residuals" shall mean that information which may be retained in intangible form in the minds of those personnel of the receiving party, without intentionally reducing such information to memory, who have had access to Confidential Information in tangible form of the disclosing party during the term of this Agreement. 31. WARRANTY AND DISCLAIMER. Contractor warrants that it will perform all Services in a professional and workmanlike manner and provide Work Products that conform in all material respects to the specifications set forth in the SOW as further defined in the Deliverable Definition documents that will precede work on any deliverable. The warranty period for each phase shall be one hundred and twenty (120) days and shall begin upon the date of cutover into production of each phase and will expire 120 days after such date. CITY must report any deficiencies in the services of Contractor in writing within such 120 day period. City's initial remedy and Contractor's initial liability is to provide Services to correct the deficiencies. If Contractor is unable to correct the deficiencies, City is entitled to recover the fees paid to Contractor for the Fixed Fee Deliverable or associated Development Object (as defined in section 28 - Invoicing and Payment) and may, at its option, withhold release of project retainage and/or performance bonds in order to cover City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 13 of 418 the costs of finding a solution to the deficiency from other parties. CONTRACTOR DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR PARTICULAR PURPOSE. Contractor makes no warranties regarding any portion of any deliverable developed by City or by any third party, including any third party software, hardware, or other third party products provided by Contractor. 32. DISPUTE RESOLUTION. Pursuant to the Statement of Work, in the event of a dispute, the parties will first follow the Issue Resolution and Escalation process documented in the Project Charter. Should the parties fail to resolve issues pursuant to such Issue Resolution and Escalation process, each party will promptly notify the other in writing of any dispute. The notice shall state the nature and specific reasons for the dispute. The parties' designated project managers will meet within ten (10) business days following the receipt of such written notice and will attempt, in good faith, to resolve the dispute within five (5) business days of the initial meeting. If the project managers cannot resolve the dispute, the appropriate executives of the City and Contractor shall meet and attempt to resolve the dispute. If the dispute cannot be resolved by the appropriate executives, then the parties may agree to submit the dispute to non -binding mediation upon written consent of both parties. Such mediation shall be in accordance with the rules of the American Arbitration Association. The parties shall mutually select a mediator with knowledge and expertise of the subject matter of the dispute within thirty (30) days of agreeing to mediate. Each party shall be liable for its own expenses, including attorney's fees; however, the parties shall share equally in the costs of the mediation. Notwithstanding the fact that the parties may be attempting to resolve a dispute through this informal process, the parties agree to continue without delay all of their respective duties and obligations under this Agreement not effected by the dispute. If the dispute cannot be resolved via the foregoing efforts or through mediation, either party may file an action at law or in equity with a court of competent jurisdiction in Tarrant County, Texas. [SIGNATURE PAGE FOLLOWS] City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 14 of 418 IN WITNESS WH REOF, the parties hereto have executed this Agreement in multiples this 1 day of �u {�,Q_ 2-& - . IMe-1 0?61.a CITY OF FORT WO By• usan Alanis sistant City Manager Date: I ATTE By: ary J. Kayser City Secretary CONTRACTOR: 0/ Rick Genovese Chief Operating Officer Date: 3// 2 APPROVED AS TO FORM AND APPROVAL RECOMMENDE LEGALITY: B By. Males is B. Farmer na Elli Assistant City Attorney tirector inancial Management Services / Chief Financial Officer CONTRACT AUTHORIZATION: M&C: --�S" q Date Approved: In P 21 1 Z City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 15 of 418 J OFFICIAL RECORD CITY SECRETARY FT. WORTH, TX EXHIBIT A - STATEMENT OF WORK Introduction The ERP Phase II Project is the second part of a city-wide effort to replace aging systems that lack functionality and are insufficiently integrated. This project includes redesign of the chart of accounts (fund/account/center), implementation of Oracle PeopleSoft Financial Management Software, Oracle Hyperion Budget Planning Software, integration between the City's BuySpeed Online purchasing solution and an option to implement PeopleSoft's Procurement and Inventory Software. Implementation services for Phase II were solicited with RFP 10-0364 and CIBER has been engaged to provide implementation services according to this Statement of Work. CIBER will also provide training, change management, business process redesign, and post go -live services. The following sections in this document detail the scope of the project and provide the guidelines and procedures necessary for a successful implementation. Citv Goals The City's long-term goal is to replace a disparate collection of aging administrative systems with a new Enterprise Resource Planning (ERP) system, and introduction of additional functional capabilities beyond that of the current systems. The first part of this strategy was the replacement of the City's human resource, payroll, and time and attendance applications with an integrated system supporting those functions. This Statement of Work (SOW) represents the second part of this strategy. Its objectives are: • To replace the core finance applications and integrate with BuySpeed Online (per the defined scope) by October 1, 2014 in Phase IIA. • To replace the City's budget preparation with Hyperion Workforce Planning and Planning Plus as Phase 116, to support development of the FY2016 operating budget. • To expand the City's use of certain functions within PeopleSoft (such as replacing disparate project management systems) as Phase IIC in 2016. • As an option, the City may replace its BuySpeed Online purchasing software with PeopleSoft's Procurement and Inventory offerings, hereafter referred to as "Phase IIC," (Option) in 2016. The City has chosen Oracle PeopleSoft as the ERP product and Oracle Hyperion as the Budget Preparation product and CIBER, Inc. for the implementation of these applications. The City currently employs a series of systems to support the finance and procurement functions of the City's departments. Many of these systems are aging, lack desired functionality and are insufficiently integrated. Primary systems include: • Municipal Accounting and Reporting System (MARS) — The General Ledger (GL) system used by the City is the GEAC E-series for Government. The financial system is supplemented with auxiliary applications to separate and alleviate critical processes (i.e., the purchasing/payment functions have been moved to a client/server application that feeds City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 16 of 418 financial transactions to GEAC's General Ledger). The General Ledger system is required to ,T produce financial statements in conformity with Generally Accepted Accounting Principles (GAAP), guidelines set forth in the AICPA (American Institute of Certified Public Accountants) Industry Audit Guide Audits of State and Local Governmental Units, and GFOA's (Government Financial Officers Association) publication Governmental Accounting, Auditing and Financial Reporting (using the GASB 34 Model). The system conforms to all Governmental Accounting Standards Board or Financial Accounting Standards Board pronouncements applicable to local governments. The number of users for MARS is approximately 830. An estimated 650,000 transactions are processed by MARS annually. • The GL is capable of handling (including storage, retrieval, and reporting) multi -year ledgers for over 200 funds. Funds may be operating, bond, enterprise, or grant funds; these may close revenues and expenditures to fund balances on an annual or periodic (e.g., upon the close of a construction project) basis. The GL facilitates a variety of journal entries with distributed entry, review and approval. A broad mix of external GL data is posted to the GL such as gas bills, electric bills, water bills, court fine payments, credit cards, revenue collections, etc. via a GL interface. BuySpeed Online (BSO) - Periscope's BuySpeed Online is an advanced, in-depth solution for managing and streamlining purchasing and inventory processes from beginning to end by providing a seamless solution for all procurement functions including: Vendor Management, Requisitions, Bid/Quote, Purchase Orders/Contract Award/Releases, delivery of orders to vendors, Inventory, Change Orders, Receiving, Invoice -entry, Fund Account Center and Budget Validation, Workflow and accounting transactions, National Institute of Governmental Purchasing (NIGP) code management, update and buyer assignment, and Reporting. The number of users for BSO is approximately 400. An estimated 500,000 transactions are processed by BSO annually. BRASS (Budget Reporting and Salary System), a commercial off -the -shelf program from CGI-AMS, is the City's budgeting system. This stand-alone client/server based system was installed in 2001 as a way to improve the City's annual budget process. BRASS is managed by the Budget and Research Division of the City Manager's Office. The system is interfaced with the MARS GEAC system to provide transaction data and Genesys (HRIS) to provide Human Resources Position Control to produce the annual City budget. The number of users for BRASS is approximately 220. An estimated 10,000 records are processed by BRASS annually. • Capital Projects Management System (CPMS) Unifier — CPMS is a comprehensive capital projects tracking system that the City implemented in 2007 to help it effectively deliver approximately one billion dollars in capital projects, which are being driven by an increasing annexation inventory, aging infrastructure and new development / housing starts, among other factors. The system, which is managed by the Program Management Office within the City Manager's Office, was implemented to enhance project coordination, increase project status and financial visibility, improve availability of project information for citizens and decision makers, standardize capital project delivery policies and procedures across the organization, and generally increase the number of projects delivered within scope, schedule and budget. The CPMS is a web -based application hosted outside of the City's network infrastructure that utilizes the proprietary Unifier software developed by Skire, Inc. The application allows for electronic routing and tracking of key business processes, as well as financial integration, via a Data Mart, across multiple City systems, including finance, payroll and purchasing. CPMS allows for detailed project scope, schedule and budget tracking from project inception to close-out. The system also provides for capital planning, real time executive reports, and fund (as well as expenditure) management. The number of City of Fort Worth / CIBER, Inc. s Professional Services Agreement Page 17 of 418 users for CPMS is approximately 400. An estimated 75,000 transactions are processed by CPMS annually. • The City intends for the Oracle ERP Software Suite to replace the above mentioned systems over the course of the remaining phases. The City expects CIBER will conduct an .. assessment of additional systems that exist at a departmental level as potential candidates for replacement; a potential list of these is included in the City's Request for Proposal (the RFP) Appendix A — Inventory of City Systems with Administrative Component. Other related systems include, but are not limited to, the following: City Wide Billing — The in-house developed City Wide Billing System is used to create miscellaneous invoices for various City departments. The user enters the name and description of the transaction along with the date, amount, and the Fund/Account/Center to be charged and the one to receive the revenue. System interfaces provide integration to — MARS and Tax Revenues. Housing and Economic Development uses the system to bill citizens for plats. Transportation and Public Works uses the system to charge rental on parking spaces. The system is also used for miscellaneous low volume Accounts — Receivable. IT Finance Asset Management System — The IT Asset Management System is a system for tracking IT assets along with the people, department and the associated Fund/Account/Center. The IT Asset Management System provides one of the exported source data for City Wide Billing. Fixed Asset Accounting — Various home-grown spreadsheets and databases have been developed to provide maintenance, depreciation, and capital assets reports on a scheduled or ad hoc basis. There are approximately 31,500 assets currently supported through the various fixed asset spreadsheets and applications. The City's finance and small dollar procurement operations are de -centralized across the City — with central control responsibility exercised within the Financial Management Services (FMS) Department. Larger dollar purchases are coordinated centrally in the FMS Purchasing Division. The City processes financial transactions for 6,382 authorized (full-time) employees and approximately 1,050 temporary or contract employees. City departments are responsible for the capture and entry of finance and procurement data on a daily basis. Protect Background The ERP project has been divided into two significant phases: Phase I consisting of the _ implementation of the Human Resource//Payroll modules and Phase II consisting of the Finance, Budget, and Capital Project suite of modules, with an option to implement the PeopleSoft Procurement and Inventory modules. Phase I of the project is currently live. ERP Phase II began with the development of project requirements which were compiled during a series of requirements review sessions. Participants included a total of approximately 80 employees representing twenty-one (21) City departments. The final requirements document consisted of a detailed listing, in table format, of the City's functional requirements organized into forty-one (41) categories. An assessment of the current hardware and software environment was also performed. - The project continued with the software selection process. The defined functional requirements were submitted to the PeopleSoft vendor - Oracle America, Inc. - for review. Gaps in — City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 18 of 418 functionality were then identified to determine if any of them were severe enough to warrant expanding the software solutions evaluated for implementation. Software demonstrations followed where the capabilities of PeopleSoft was assessed through pre -scripted software tasks targeting critical City business functions. At the completion of the software assessment activities the decision was made to proceed with PeopleSoft software solution. The project team then began the vendor selection process for implementation services. RFP proposals were evaluated and CIBER Inc. was selected to provide implementation services for the ERP Phase II project. Scope Introduction The City has selected Oracle PeopleSoft Enterprise Financial and Supply Chain Management version 9.1 and Oracle Hyperion Budget Planning version 11.1.1.3.0 as the combined software solution and has through the execution of this SOW engaged CIBER and its partners to work with the City in the implementation of this city-wide Oracle ERP Software Suite in accordance with scope topics described below. This section describes the work that is considered In -Scope and Out -of -Scope for the PeopleSoft/Hyperion implementation project. In -Scope Services The In -Scope work is organized into the following list: • Deployment Approach and Project Schedule • Systems Implementation Scope o Functions to be Supported o Software Requirements o Modules to be Implemented o Systems to be Replaced o Transactional Scope • Organizational Scope • Internal Controls Scope • Change Management Scope o Organizational Change Management o Leadership/Organizational Alignment o End -User Training • Development Scope o Interfaces o Conversions o Enhancements (including Workflow) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 19 of 418 o Reports • Deliverables • Production Support Deployment Approach and Project Schedule For purposes of this Agreement: • Phase I refers to the HR/Payroll Implementation phase of the City's overall implementation of an ERP System. • Phase II refers to the Finance/Procurement implementation phase of the City's ERP system. In order to mitigate risk, the ERP Phase II project will deploy functionality in 3 distinct phases — and will include the option to implement Procurement and Inventory modules, if approved by the City: • Phase IIA —Core Functionality • Phase 1113 — Budget Prep • Phase IIC — Capital Projects • Phase IIC — Procurement and Inventory Option Phase IIA, Phase 116, and Phase IIC — Capital Projects, and Phase IIC — Procurement and Inventory Option are described in additional detail in the "Functions to be Supported" section of r the Statement of Work. Note: All previously created procurement document references to ERP Phase II and Phase III — are incorporated into the Phases now described as IIA — Core Functionality, 1113 — Budget Prep, IIC — Capital Projects, and IIC — Procurement and Inventory Option. The chart below is an example of the high level project schedule that will be refined and detailed by the Master Project Work Plan. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 20 of 418 81v3O [Za$Ed lua[uaalsv SaowaS juuOTSSa3O.id 'auI `dasio / gvolA U0d3O �?D AMV =-Ti .� O Z m D m O c� m D ➢ m O Z O m C C:C D T m m 0 0 m D � DDD - O�Zi0 m C C C y D m ➢.maoi co ➢ m C C'C T. O Z y rn m 0 o (-) M D rn C O j m Z n < -i 0 L� � Z { 7J ]7 m Z o < O,L� Z;{ p;oo Z (7,<?� V L� Z { C'Z (7.< _L7 MZ Ad SWZ AJ _ mz Ad W—, I`. c- a I r It 1 9 1 1 1 r 9, 1 e System Implementation Scope The System Implementation Scope is defined from the following perspectives: Functions to be Supported, Software Requirements, Modules to be Implemented, Systems to be Replaced, and Transactional Scope. Functions to be Supported The functional scope of Phase II includes the following activities that are organized by the phases of the deployment approach. While the Procurement and Inventory functions described below are more fully enabled by the modules that are currently optional for implementation, Ciber is required to support the PeopleSoft controlled financial -related activities resulting from T the Procurement and Inventory functions for the duration of Phase II implementation: PHASE IIA —CORE FUNCTIONALITY • General Ledger: The basic functions include general GL activities, financial controls, journal entries, month end/year end close, interdepartmental billing, cost allocation, job costing and reimbursement, petty cash, financial reporting and encumbrance — accounting, as well as investment, cash and bank accounting and reconciliation. • Budgetary Control: The basic functions include budget entry and workflow, budget maintenance and workflow, budgetary control for expenditure and revenue transactions, performance indicators, and reporting. • Accounts Payable: The basic functions include vendor maintenance (in terms of receiving vendor information and updates from BuySpeed Online), invoice and credit memo entry, employee expenditure reimbursement and check writing. • Accounts Receivable: The basic functions include financial controls and reporting, customer and item maintenance, customer invoices entry, cash receipts for billed and -` unbilled items, end -of -day deposit recording, customer accounts and credits, and Insufficient Funds (NSF) checks. • Fixed Assets: The basic functions include asset additions and maintenance, asset disposition, retirement, asset theft, surplus property, depreciation, physical inventory, capitalization of projects, capital leases and asset warranties. • Project Accounting: The basic functions include general project accounting, project definition, project plans and budgets, project billing and funding, periodic processing, close-out, budget control and financial controls. • Grant Accounting: The basic functions include financial controls and reporting, budgetary control, grantor definition, sub -recipient definition, grant applications, grant award, grant budget, grant advances, grant expenditures, pass through grant funds, grantor billing, grant in -kind and match, indirect costs, grantor reports and grant close- T out. PHASE IIB — BUDGET PREPARATION • Budget Preparation: The basic functions include calendar maintenance, general budget prep, revenue estimates, budget preparation guidance, position -based budgeting, base budget, department submission, budget submissions through various phases and budget prep reporting, including preparation of the approved Final Budget Book. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 22 of 418 PHASE IIC—CAPITAL PROJECTS Project Management: The basic functions include maintenance of general project information, project approvals, project management, planning, budgeting and scheduling and construction design and bid management. PHASE IIC—PROCUREMENT AND INVENTORY OPTION The City shall have the option to purchase the services and support for the Procurement and Inventory Option, Phase IIC, under this Agreement. All services set forth herein in the Contract Documents related to Phase IIC shall be deemed optional, with the exception of Phase IIA year- end support hours reflected in the staffing plan and milestone payment for Phase IIC given that it occurs in months 37 and 38, unless and until the City exercises such option. The parties will only become obligated for the services and costs set out in Phase IIC in the event the City exercises such option, with the exception of Phase IIA year-end support. The City shall have until December 5, 2014 to exercise the option for Phase IIC. The City shall give Contractor 30 days' written notice that the City wishes to exercise the Phase IIC Option, which such notice shall become an Exhibit to this Contract and be incorporated herein by reference. The costs for Phase IIC shall be set forth in the attached Exhibit B.3, Payment Schedule. • Purchasing: The basic functions include requisitions/requests, commodity/service lines, solicitation creation and issuance, vendor selection, electronic bid posting, amendments to bids, vendor responses, bid tabulation/evaluation and negotiation support, contract award, creation of purchase orders, purchase orders changes, purchase orders issuance, requisition and purchase order accounting, goods and service receipt, vendor invoice, matching and payment request information, contract administration, contract renewals, contract catalog, releases, notifications and approval work flows. Also, commodity data maintenance, vendor registration, vendor master data, vendor maintenance, vendor performance, and procurement card (payment card) processing. • Additional Accounts Payable functions such as invoice matching to source purchase order and receipts. • eProcurement: The basic functions include employee and vendor self-service for requisition management, status tracking, requisition changes, vendor on-line registration and bid entry. • Inventory: The basic functions include inventory activity, inventory accounting, goods receipt, stock issuance, reordering, transaction processing, physical inventories and inventory reporting. • Enhanced eProcurement Features: The basic functions include on-line invoice entry, E- Sourcing, E-Marketplaces, Vendor catalog management, and supplier relationship management. Software Requirements Software Requirements are initially defined in the Response to Software Requirements, as reasonably interpreted. During the Fit/Gap Process Software Requirements will be confirmed and may be enhanced through Business Process Design workshops and through several iterations of the prototyping sessions. (The second and third prototyping sessions described in IPM are validation tests and will not be events to identify Software Requirement enhancements. Exceptions during these prototyping sessions will be handled through the Scope Change Management Process). Any Software Requirement enhancements will be captured in the Requirements Traceability Matrix, acceptance of which defines the final Software Requirements scope. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 23 of 418 Modules to be Implemented The following modules will be installed and implemented to support the functions and software requirements identified above. • PeopleSoft Enterprise Financials • General Ledger • Accounts Payable • Accounts Receivable • Billing • Treasury/Cash Management • Asset Management • PeopleSoft Project Costing • PeopleSoft Contracts • PeopleSoft Grants • PeopleSoft Purchasing (Phase IIC - Procurement and Inventory Option) • PeopleSoft Inventory (Phase IIC - Procurement and Inventory Option) • PeopleSoft eSupplier Connection(Phase IIC - Procurement and Inventory Option) • PeopleSoft eProcurement(Phase IIC - Procurement and Inventory Option) • eSettlements (Phase IIC - Procurement and Inventory Option) • PeopleSoft Strategic Sourcing (Phase IIC - Procurement and Inventory Option) • PeopleSoft Supplier Contract Management (Phase IIC - Procurement and Inventory Option) _ • Hyperion Workforce Planning • Hyperion Planning Plus • Associated PeopleSoft Enterprise User Productivity Kit Applications The following Phase I applications will be revisited to accommodate Phase II requirements: • Human Resources (for position budgeting and control and integration with Hyperion — Budget Preparation functionality) • Time and Labor (for job/project costing) • Payroll and Benefits Administration • Any other modules or functionality in production that are dependent on Chart of Accounts or ChartField decisions that may be impacted by redesign to the City's _ Financial Data Classification Structure, as potentially outlined in the Software Requirements • Enterprise Portal (to provide access to financial applications) The modules presented above are considered in scope for this implementation, in order to meet the stated functional requirements as put forth by the City in its RFP, reflected in Exhibit I — Software Requirements and Responses. Software Requirements met by out -of -scope — PeopleSoft modules will be satisfied by using either delivered functionality of in -scope modules, through approved custom development enhancements or through a business process work- around. A list of software requirements that fall into this category is included in Exhibit M: - List _ of Software Requirements that are known to be supported by modules not in scope. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 24 of 418 Oracle has introduced a new module, Hyperion Public Sector Budgeting, which will be evaluated in the ERP Phase II project. If the City chooses to implement this functionality, it will follow the Scope Change Management procedures. Systems to Be Replaced Exhibit N — Systems to Be Replaced contains a list of systems that are candidates to be replaced through the ERP Phase II Implementation. This list was developed based on an understanding that the functionality of those systems is wholly covered in the ERP Phase II Scope documented in other areas of the Statement of Work. If further requirements are identified that are not defined within the existing software requirements, module, business process or functional scope, support for the additional requirements will be subject to the Scope Change Management Process, and as appropriate, this system will be added to the list of potential interfaces and be subject to the Approach for Managing Custom Development. Transactional Scope Initially: All Transactions within the modules as necessary to perform the functions above. After Fit/Gap: As included in the Configuration and System/Configuration Test Plan, acceptance of which will become a scope defining document. Organizational Scope The organizational scope of Phase II includes the centralized finance and procurement sections within the Department of Financial Management Services, the Budget Office and Program Management Office within the Mayor and City Manager's Department for centralized budget preparation and Project Accounting and Management activities, and all City departments through participation in decentralized financial activities, and procurement activities limited to transactions controlled within PeopleSoft, which would include facilitating the identification and design of approaches to ensure that appropriate financial and accounting transactions resulting from procurement and inventory activities update PeopleSoft. During Phase IIA, CIBER will not be responsible for organizational change activities that are associated with changes to the BuySpeed system. In addition for Inventory, the following organizational scope is included as a part of Phase ll, should the City exercise the Phase IIC Purchasing and Inventory Option: Transportation and Public Works — Traffic Services Inventory (Number of Sites: 2) Site Items 5001 James Ave. Warehouse St. Lights Prfles and Arms, Cobra Heads, Lamps, and Pole Yard: Fuses, Copper Wire, Aluminum Wire, Brackets, Alum. Sign Blanks, Reflective Sign Sheeting Material, Signal Heads, Solar Flasher, Personnel Items, Gloves, Safety Vest, Rubber Boots (Knee/Hip), Batteries, Assorted Nuts, Bolts and Paint with all Related Items. S.E. Yard -Village Creek Pole Signal Poles and Arms, Street Ught Poles and Yard Arms • Fire Department — Fire Supply Inventory (Number of Sites: 1) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 25 of 418 Site Items 3000 W. Bolt St. Office supplies, janitorial supplies, tools (wrench, hammer etc.), kitchen utensils, major appliances (refrigerator, dishwashers etc.), lawn care supplies & equipment (rakes, hoses etc.) furniture (bed, chair, mattress etc.), kitchen utensils (plates, pots etc.) bath & bed supplies (blankets, shower curtains etc.), batteries, uniforms, bunker gear, ems bag supplies and medicines (glucometer, dressings, albuterol, ibuprofen). • Information Technology Solutions — IT Inventory (Number of Sites: 1) ISike� Items Holly Treatment Plant Pieces and parts for networking, telephones and radios • Equipment Services Department — Fuel Inventory (Number of Sites: 85 Fuel Pump and Tank Locations) 2 '.. �Si Airport (2 Fueling Locations) Diesel Fuel, Liquified Petroleum Gas (LPG), Unleaded Gas ESD Brennan Service Center Lubricants, Diesel, LPG, Unleaded Gas (1 Fueling Location) ESD Downtown Service Unleaded Gas Center (1 Fueling Location) ESD James Avenue Service Lubricants, Diesel, Unleaded Gas Cntr (2 Fueling Locations) ESD South East Service Diesel, Unleaded Gas Center (1 Fueling Location) ESD South Side Service Lubricants, Diesel, LPG, Unleaded Gas Center (1 Fueling Location) ESD Tire Shop (1 Fueling LPG Location) ESD Water Service Center (1 Lubricants, Diesel, LPG, Unleaded Gas Fueling Location) Fire Stations (38 Fueling Diesel and Unleaded Fuel Locations) Marshall's Office (1 Fueling LPG Location Parks and Community Services (9 Fueling Locations) Police (3 Fueling Locations) Public Events (2 Fueling Locations) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 26 of 418 Diesel and Unleaded Fuel Diesel, Jet Air Fuel and Unleaded Fuel Diesel and Unleaded Fuel r• PM ON ile Itc.nIS Tankers, Mobile (21) Lubricants, Diesel, and Unleaded Gas Village Creek (1 Fueling Diesel, LPG and Unleaded Fuel ., Location) If the City chooses to exercise the option of implementing Phase IIC — Procurement and Inventory, the organizational scope will be expanded to include: (1) All City departments utilizing decentralized procurement activities during Phase IIA; and (2) the organizational scope for City inventories as described in the bulleted list above. Internal Controls Scope Internal Control scope is defined to include: • Provision of an Internal Control Framework for the functions in scope at the initiation of the project; • Participation in critical design and implementation activities as identified in RFP Appendix N; • Documentation of System Supported Internal Controls tested through normal system testing activities; and • Documentation of manual internal controls for the functions in scope within policies, financial directives, procedures and business process narratives, as identified by the City. Change Management Scope Organizational Change Management The scope of the Organizational Change Management focus for Change Management Services shall encompass the activities necessary to implement the Organizational Design Changes as identified in the Business Process Design Documentation and catalogued in the Business Change Impact, acceptance of which will become a scope defining document. Leadership/Organizational Alignment The scope and focus of the Leadership/Organizational Alignment efforts for Change Management shall include: • Conducting initial assessments to measure alignment of the City's executive leadership, department management, and affected staff to the "To -Be" process and organizational design; • Conducting alignment workshops for affected levels of the enterprise to identify barriers to change; • Planning activities and education efforts to minimize resistance to change; • Periodically measuring effectiveness of alignment efforts; and • Communicating successes and obstacles to Project Leadership, Sponsors and Advisory Bodies. City of Fort Worth / CIBER, Inc. am Professional Services Agreement Page 27 of 418 End -User Training Training Strategy With the implementation of new application modules, training planning, development and delivery is critical to the overall success of the implementation and will facilitate ease of use and user acceptance of the new processes and systems. To assist the City with train -the -trainer and end -user training, CIBER will develop a training program organized into several phases. For End -User Training, a more detailed training strategy will be outlined in the Training Strategy deliverable. End -User Training Approach CIBER will use a modified Train -the -Trainer strategy for end -user training. This - approach will support the City by creating an in-house training team comprised of CIBER provided trainers and City provided trainers (as identified in the Exhibit P: Proposed Staffing Plan contained in this document) that is primed to develop and deliver end -user - training, support their peers post production and also prepare new hires and newly transferred employees to do their job. In the event that the City is able to assume hours currently shown in Exhibit P: Proposed Staffing Plan as CIBER trainer hours, Project - Management will determine the appropriate credit based on the rate chart provided in this SOW. Conversely, if the City is not able to provide the anticipated level of Training hours shown in Exhibit P: Proposed Staffing Plan shown in this SOW, Project Management will determine the additional hours to be provided by CIBER and will execute the appropriate change order (i.e., hours times rate) shown in the rate chart for trainers. A further discussion of the End -User Training development and delivery is included in the Methodology section of this SOW. Development Scope CIBER has identified the technical scope below from review of the City's RFP and in responding to the software requirements matrix. The technical development scope is grouped into: • Interface Development • Data Conversion • Enhancements (including Workflows) • Report Development The following section presents the technical development scope. Interfaces Initial interface scope is defined in Exhibit G.1: Initial Interface Scope CIBER's estimate of effort to complete these Interfaces is included in Exhibit G.2: Estimate of Effort for Interface Development. These estimates are included in support of communicating a general understanding of the complexity of the development effort and to help prepare a "not to exceed" development cost target. They do not comprise a restriction of scope for individual _ interface development to the estimated levels. Final fixed costs for development objects will be negotiated after the Fit/Gap and prior to finalization of the Development Object List and Unit Test Plan. This scope will be modified throughout the Discovery Stages of the Project and for each of the three phases (Phase IIA, IIB, IIC - Capital Projects and IIC - Procurement and Inventory Option) will be finalized after the Fit/Gap document is accepted. Final Development Scope will City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 28 of 418 be managed through the Development Object List and Unit Test Plan, acceptance of which will constitute a scope defining document. Conversions Initial conversion scope is defined in Exhibit G.3: Initial Conversion Scope CIBER's estimate of effort to complete these programmatic Conversions is included in Exhibit G.4: Estimate of Effort for Conversion Development. These estimates are included in support of communicating a general understanding of the complexity of the development effort and to help prepare a "not to exceed" development cost target. They do not comprise a restriction of scope for individual conversion development to the estimated levels. Final fixed costs for development objects will be negotiated after the Fit/Gap and prior to finalization of the Development Object List and Unit Test Plan. This scope will be modified throughout the Discovery Stages of the Project and for each of the three deployment waves will be finalized after the Fit/Gap document is accepted. Final Development Scope will be managed through the Development Object List and Unit Test Plan for conversions that are not manual Final Development Scope will be managed through the Development Object List and Unit Test Plan, acceptance of which will constitute a scope defining document The City will be responsible for developing the data extracts from current City systems to the temporary tables that will be used to translate into PeopleSoft/Hyperion. CIBER will mentor City staff on that work. Through the knowledge transfer process, CIBER will document and demonstrate the data conversion processes for the City. This process will permit City staff to become acquainted with the technology and understand how to perform similar activities in the future. City resources will cleanup any invalid or inconsistent data in current systems in preparation for data conversion. If data translation routines cannot programmatically correct any data inconsistency and cleanliness issues, manual intervention will be required by the City to resolve and correct the data issues within in the current systems. All data that is not a candidate for programmatic conversion will either be manually loaded by the City resources, or archived into a data warehouse for future access and reporting by the City resources. CIBER resources will define the conversation strategy with the City and provide technical design assistance should a data warehouse be used for archived data. Enhancements (including Workflows) Exhibit G.4: Initial Enhancement Scope contains a list of enhancements and estimated hours for development as defined in Appendix F of CIBER's response to the RFP that may be in -scope. This scope will be modified throughout the Discovery Stage of the Project and for each of the three phases (Phase IIA, IIB, IIC — Capital Projects and IIC — Procurement and Inventory Option) will be finalized after the Fit/Gap document is accepted. Final Development Scope will be managed through the Development Object List and Unit Test Plan, acceptance of which will constitute a scope defining document. City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 29 of 418 Reports In addition to the Reporting Requirements captured in Exhibit GA: Initial Enhancement Scope marked as Development Type "R" (Reports). Exhibit G.5: Initial Additional Reporting Requirements contains a list of additional reporting requirements. Final Development Scope for reports will be managed through the Development Object List and Unit Test Plan, acceptance of which will constitute a scope defining document. De/iverab/es RFP Appendix N Incorporated Exhibit K: - Deliverables Cross Reference, associates CIBER's project deliverables with the City's requested work products from RFP Appendix N, the contents of which are incorporated by reference into this Statement of Work. Some refinements to these work -products are included in Exhibit O: Refinements and Clarifications to Appendix N Work -Product Descriptions. Production Support Overview of Post Go -Live Support Post Go -Live Support will continue for a period of 90 days after go -live for each respective phase. CIBER and the City will be responsible to work together on Post Go -Live support in order to complete the transfer of system ownership from CIBER to the City. CIBER will provide onsite functional and technical assistance in the following areas: • Problem analysis and resolution • Knowledge transfer reviews or refresher to same audiences as during project • Coaching users on use of the new system Service requests that involve changed or new specifications (new development) will be handled by the City. The City may request assistance from and if the work effort can be performed without interfering with or exceeding CIBER's post go -live responsibilities and obligations, the work will be done by CIBER as part of the post go -live support. By the end of the 90-day period, the City will be solely responsible for ongoing support of the PeopleSoft/Hyperion System. Activities for the 90-day post go -live support effort are: • Support and direct assistance for business owner departments and key City staff • Guidance and mentoring to the City staff who provide application support functions and user help desk support (problem resolution) • Validation and auditing of system health and data integrity checks — CIBER will help the key staff of business owner departments create such audits in production; audits will be run by the user in production The types of service support that will be provided are: • Respond to help requests and resolve system defects • Provide proactive support and special attention to central business owner departments and operational units that are run for the first time during the 90 day post go -live period City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 30 of 418 • Conclude knowledge transfer by finding out in advance important topics that staff who will own and operate the system, would like to review. The scope for Post Go -Live Support also includes 2,000 hours of support for key milestone activities such as Year End Close support. CIBER will deliver this additional support with personnel reviewed and approved by the City. The City and CIBER will jointly define the areas, objectives, outcomes, and assumptions for the delivery of services to fulfill the 2,000 hour requirement. The following will be out of scope for post go -live support: • Implementation of bundles and maintenance packs • Extensions and customizations of functionality other than defect corrections • Support for non-ERP systems • Network or workstation support Out -of -Scope Services Consistent with professional practices, CIBER has used due diligence and depended upon the accuracy of the information provided by the City to estimate and price the scope of this work. Incomplete, inaccurate or erroneous information may cause an increase in contract price and schedule. If, during the execution of this engagement, unforeseen conditions are discovered that materially affect the original scope of work, CIBER retains the right to negotiate staffing, schedule, or scope changes, or terminate this agreement in accordance with Section 4 of the Professional Services Agreement, without penalty. Any changes to scope that are not specially listed in the SOW or the Fixed Fee Deliverable Definition Document will be subject to the scop shall mutually agree in writing to scope changes. Contract Amount by more than $50,000 must be Council. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 31 of 418 e change management process. Both parties Any change in scope that increases the Total specifically approved by the Fort Worth City Project Staffing Plan, Roles and Responsibilities Each Deliverable Definition Document will identify specific responsibilities of CIBER and the City of Fort Worth. In addition, the chart below identifies general project responsibilities by role. Roles Responsibilities Executive • Makes decisions that can change project organization, project scope, or Sponsor allocation of project funding. • Monitors that the direction of the project continues to be in line with the original mission and goals set forth at the beginning of the implementation, or new directions as determined. • Removes obstacles to meeting critical success factors which may impact the successful outcome of the project. • Approve financial expenditures and provide budget oversight Sponsor CIBER Project Executive • Periodic client site visits to review progress and discuss any issues related to project success • Participate in Advisory Committee meetings monthly, or as scheduled • Support Project Management in achieving resolution of issues, mitigation of risks and decisions on all change orders • Monitor adherence to the project implementation strategy • Budget oversight related to contracted project hours and dollars • Provide project management escalation leadership • Review findings and provide written responses to Advisory Committee as necessary City of Fort Worth Sponsor • Periodic project site visits to review progress and discuss any issues related to project success • Facilitate City Manager and Assistant City Manager involvement • Facilitate Team Commitment • Participate in Advisory Committee meetings monthly and serve as conduit between project managers and Advisory Committee • Support project management in achieving resolution of issues, mitigation of risks and decisions on all change orders • Monitor adherence to the project implementation strategy • Provide project management escalation leadership • Review findings and provide written responses to Advisory Committee as necessary Quality CIBER Quality Assurance Assurance • Provide oversight on project quality management Oversight • Perform periodic reviews to objectively assess the health and status of the Lead project against its goals, objectives and schedule milestones. • Assess the effectiveness of project team established quality control standards and procedures • Provide objective view of project issues • Offer resolution and guidance for project issues • Provide a sounding board for City of Fort Worth executives to discuss their own concerns, and issues as to the direction of the project Project CIBER Project Manager Manager Work in concert with City of Fort Worth Executives, Project Manager and CIBER Executive to fulfill the responsibilities of the role, project scope, and management of the Team's activities toward the successful completion of the project City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 32 of418 A Rat s. Kdsoofsilb iiti T Coordinate with Oracle for software issues and Quality Assurance Reviews • Management of project risks and issues • Management of project plan W Make regular (monthly) updates/refinements to the PMRx or comparable project site repository as necessary • Manage CIBER project team staff Maintain team contact numbers, email lists, and regular communications • Manage CIBER sub -contractors. • Coordinate and report weekly status to the City of Fort Worth. • Communicate project status, needs, and issues to project sponsors, as required • Interact with external (to the core team) City of Fort Worth project sponsors, as required • Execute the full and complete scope of the contract • Point of contact for City of Fort Worth for contractual, staffing, and delivery matters City of Fort Worth Project Director • Facilitate City Manager and Assistant City Manager involvement • Facilitate Team Commitment • Work in concert with City of Fort Worth Executives, City of Fort Worth Project Manager, CIBER Project Manager and Executive to fulfill the responsibilities of the role, project scope, and management of the Team's activities toward the successful completion of the project • Serve as conduit between Department Heads and project managers • Manage and sustain customer and stakeholder relationships for the project • Participate in Advisory Committee meetings and serve as conduit between project managers and Advisory Committee • Communicate change, critical needs, and critical issues to project sponsors, Advisory Committee and other stakeholder groups • Support project management in achieving resolution of issues, mitigation of risks and decisions on all change orders • Review findings and provide written responses to Executive level sponsors as necessary • Provide project management escalation leadership • Provide first level sign -off of project deliverables • Provide first level sign -off of change requests • Provide leadership in the coordination of strategic initiatives City of Fort Worth Project Manager • Work in concert with City of Fort Worth Executives and CIBER Project Manager and Executive to fulfill the responsibilities of the role, project scope, and management of the Team's activities toward the successful completion of the project • Manage project change, risks and issues • Maintain/update the project scope, schedule, & cost during the life of the project (including change orders) • Ensure the deliverables and work products are produced in accordance with contractual obligations, the scope and defined quality requirements of the project M Make regular (monthly) updates/refinements to the PMRx or comparable project site repository • Manage City of Fort Worth project team staff • Communicate project status, needs, and issues to project sponsors, advisory City of Fort Worth / CIBER, Inc. Professional Services Agreement ' Page 33 of 418 ra Rolgs' Responsibilities, committee and other stakeholder groups • Point of contact for CIBER for contractual, staffing, and delivery matters • Lead, manage, and direct the efforts of the City of Fort Worth Project Team • Interact with external (to the core team) City of Fort Worth project sponsors • Oversee/manage contractual activities (agreements and contracts) • Oversee and monitor financial activities associated with the project, including approval of expenditures and invoicing • Ensure the project is closed out per defined guidelines Project CIBER Project Administrator Management . Provide support to the Project Management Team Staff 0 Responsible for all project invoicing (Project • Manage subcontractor time entry and reporting Admin) 0 Manage CIBER time entry, approvals and reporting City of Fort Worth Project Administrator • Provide support to the Project Management Team • Make regular (monthly) updates/refinements to the PMRx project site repository (or the designated project repository) • Administer SharePoint permissions for the project team • Setup and maintain physical and electronic files • Manage and compile project invoices and other expense related documents — • Prepare weekly task list for the project team members • Take and transcribe meeting minutes (documents action items, issues, decisions, assumptions, etc.) • Schedule and setup project meetings and work sessions • ( confirm attendees, schedule conference rooms, setup conference calls, and manage multi -media needs) • Oversee the calendar for the reservation of conference rooms, projectors, training room, etc. • Perform training administrative activities (refer to the "Training Team" roles) • Provide copies of meeting materials for the project team as needed Serve as the primary point of contact for phone calls • Greet vendors and visitors and escort them when needed • Create and maintain documents as needed (memos, forms, spreadsheets, logs, etc.) • Maintain project contact lists (internal and external contacts) and provide general communications to the project team • Maintain project org chart — • Make travel arrangements for the project team as needed and oversee the submission and approval of the required City travel forms • Coordinate all aspects of building maintenance activities — Receive and distribute mail • Facilitate the ordering of office supplies, and maintain office supply inventory • Facilitate the ordering of office furniture, PC software, office equipment • Manage office equipment (clearing jams from copy machines; order toner, ink and other supplies; and be the contact person for machine repairs). • Assist the Project Manager in the sign -off of project work products • Other duties as assigned — Functional CIBER Finance Lead and Supply Chain Lead if the City chooses to exercise the Leads option to implement Phase IIC — Procurement and Inventory • Coordinate the definition of the business requirements for the functional area (module) within the context of the PeopleSoft modules assigned to each manager for the project • Coordinate the project work plan and schedule for his/her respective team City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 34 of 418 .04 Roles �2esponsibilt�t�e� Coordinate the definition of specific business processes and associated metrics • Ensure quality of team deliverables • Interface with other teams • Co -Lead design sessions • Serve as chief architect for his or her specific functional area Work closely with Change Management throughout the project (including _ definition of the organization, job and skill requirements, implementation and support) • Work closely with the Technical Team to ensure proper support and timely - completion of modifications/enhancements, reports, interfaces and conversions within their functional area • Conduct a fit analysis and business process review to determine how the proposed application software can best be used to meet the City of Fort Worth's processing needs, business objectives, and requirements, and to oversee the functional aspects of configuration, customizations & extensions, reports and interfaces that are in -scope — Identify opportunities to improve City of Fort Worth business processes to minimize customizations/extensions and gain fullest advantage of the PeopleSoft software product and identified third party products • Assist in the development of UPK training materials • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository • Identify and assist in managing project risks and issues. • Report weekly status to the CIBER project manager. • Update the Microsoft Project workplan • Manage functional test process City of Fort Worth Finance and Procurement Team Leads • Participate in the definition of the business requirements for the functional area (module) within the context of the PeopleSoft modules assigned to each manager for the project • Coordinate the definition of specific business processes and associated metrics • Interface with other teams • Co -Lead design sessions • Work closely with Change Management Team throughout the project (including definition of the organization, job and skill requirements, implementation and support) • Work closely with the Technical Team to ensure proper support and timely completion of modifications/enhancements, reports, interfaces and conversions within their functional area • Work with CIBER to conduct a fit analysis and business process review to determine how the proposed application software can best be used to meet ._ the City of Fort Worth's processing needs, business objectives, and requirements, and to oversee the functional aspects of configuration, customizations & extensions, reports and interfaces that are in -scope • Identify opportunities to improve Fort Worth City of Fort Worth business processes to minimize customizations/extensions and gain fullest advantage of the PeopleSoft software product and identified third party products • Assist in the development of UPK training materials • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository • Identify and assist in managing project risks and issues • Report weekly status to the City of Fort Worth project manager City of Fort Worth / CIBER, Inc. ` Professional Services Agreement Page 35 of 418 Rales, Responsibittties • Review for final approval the results of functional test activities • Ensure the delivery of quality work products • Ensure the proper delivery of all project documentation BSO CIBER BSO Integration Lead Integration 0 Co -Lead interface design sessions with the City and its BuySpeed Leads implementation partner • Participate in the updating of requirements identified in Table 2: Review Due to Phase IIC: Procurement and Inventory Option to document design decisions that may impact the requirement and/or the applicable functional team's understanding of the direction of the interface • Coordinates table structure/file layout for mapping of data between systems in creating the CIBER interface components functional specification for the interface • Works with development team to ensure coding of the CIBER interface components is in line with specifications • Testing of CIBER interface components to ensure intended results City BSO Integration Lead • Coordinate with BuySpeed implementation partner to ensure availability during project milestones • Co -Lead in interface design sessions with CIBER and the City's BuySpeed implementation partner • Participate in the updating of requirements identified in Table 2: Review Due to Phase IIC: Procurement and Inventory Option to document design decisions that may impact the requirement and/or the applicable functional team's understanding of the direction of the interface • Represents City specific needs of the interface based upon the elimination of legacy systems being decommissioned • Participates in interface testing to ensure intended results • Works with the City Change Manager to help facilitate a change management plan to deal with the impact of change on the BuySpeed side of operations Functional CIBER Functional Team Members Team • Prepare application for design sessions Members • Co -lead design sessions Review and confirm requirements • Design and develop configuration • Develop functional design documents for modifications to the application _ • Provide Knowledge Transfer of PeopleSoft and best practices • Assist developers during build and test phase Develop system test plans (scenarios, cases, and scripts), conditions and expected results • Participate in system testing activities • Identify areas where improvements in policies and procedures can significantly advance the City of Fort Worth's goals. • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository • Identify and assist in managing project risks and issues • R Report weekly status to Functional Team Leads for his or her respective area (module) • Provide post -implementation support, • Provide guidance in defining data necessary to support training exercises " • Design and develop PeopleSoft user security • Provide functional expertise to support Department Advocate activities • Provide functional expertise and input to the Communications timeline and City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 36 of 418 of Resparls'rbilities... r +M messages • Participate in delivery of targeted communication events • Review training materials for accuracy and appropriate PeopleSoft context • Provide coaching support during training delivery City of Fort Worth Functional Team Members • Prepare application for design sessions • Co -lead design sessions • Review and confirm requirements • Identify any project concerns, issues, and/or risks • Provide feedback regarding ways to improve business processes or products • Design and develop configuration • Develop functional design documents for modifications to the application • Provide overall Knowledge Transfer of City of Fort Worth specific information • Assist developers during build and test phase • Develop system test plans (scenarios, cases, and scripts), conditions and expected results • Participate in system testing activities • Identify areas where improvements in policies and procedures can significantly advance the City of Fort Worth goal of improved financial management • Define data necessary to support training exercises • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository City of Fort Worth Subject Matter Experts • Provide functional expertise/input to training developers during the training design and development phases • Provide functional expertise to support Department Advocate activities • Identify any project concerns, issues, and/or risks • Provide feedback regarding ways to improve business processes or products • Provide functional expertise and input to the Communications timeline and messages • Participate in delivery of targeted communication events • Provides feedback regarding project requirements, current business procedures, business rules, data processing needs, etc. • Provides input regarding training and testing needs 4 Change CIBER Change Manager Manager • Responsible for planning, scheduling and managing the resources and work associated with training, communications, preparing the end users and Departments to use the new technology and business processes • Responsible for leading the effort to define and manage the business case for change • Coordinate the efforts of all change management resources and training sub - teams • Day-to-day management of responsibilities for all of the tasks that the members of the team perform and for the deliverables produced .� • Provide organizational change management expertise to the team and overall project team. Apply that expertise broadly, by ensuring all aspects of their team's solution work correctly and in concert • Coordinate overall Knowledge Transfer program i Manage risks and resolve issues in a timely manner • Participate in quality reviews designed to verify that the team is completing work in accordance with standards that are established at the onset of the City of Fort Worth / CIBER, Inc. Professional Services Agreement '� Page 37 of 418 Rotes Responsibilities project • Oversee knowledge transfer activities for Change Management and Training Team members • Participate in knowledge transfer activities as required • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository • Develop program for measurement of success of change management and knowledge transfer activities • Provide weekly status report to CIBER Project Manager City of Fort Worth Change Management Manager • Responsible for planning, scheduling and managing the resources and work associated with training, communications, preparing the end users and Departments to use the new technology and business processes • Responsible for leading the effort to define and manage the business case for change • Coordinate the activity of City resources for all change management and training sub teams • Assume day-to-day responsibility for all of the tasks that the members of the team perform and for the deliverables produced • Provide organizational change management expertise to the team and overall project team. Apply that expertise broadly, by ensuring all aspects of their team's solution work correctly and in concert • Participate in quality reviews designed to verify that the team is completing work in accordance with standards that are established at the onset of the project • Participate in knowledge transfer activities as required • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository • Collaborate with the CIBER Change Manager on the development of a program for measurement of success of change management and knowledge transfer activities • Provide weekly status report to City of Fort Worth Project Manager Change CIBER Change Management Team Member Management . Develop and deliver tools, templates and reference materials to assist the Team Department Advocates and Department Coordinators in their implementation Member preparations • Plan and deliver monthly Department Implementation meetings • Compile readiness progress from all Departments, assess and summarize results • Prepare and coordinate Department Readiness Workshops • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository Communications • Assist in development and maintenance of overall communication plan • Determine optimal communication methods for each stakeholder group • Prepare and deliver ongoing communications to stakeholders according to the communications plan and needs of varied audiences • Provide communications activities and interface with project management and other team members as needed for information and/or approval • Evaluate and assess City of Fort Worth project website feedback and adjust as necessary • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 38 of 418 w a RolesIes�oi�slbilities City of Fort Worth Change Management Team Member • Plan and deliver monthly Department Implementation meetings • Compile readiness progress from all Departments, assess and summarize results • Also serve as Department advocates Communications • Assist in development and maintenance of overall communication plan • Determine optimal communication methods for each stakeholder group • Provide communications activities and interface with project management and other team members as needed for information and/or approval • Evaluate and assess City of Fort Worth project website feedback and adjust as necessary • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository Training CIBER Training Manager Team • Create the Training Plan and work plan • Oversee the training needs analysis • Design and development of training • Plan and delivery of Pilot training • Plan and co -manage team's work effort to meet established quality standards, schedule and budget • Document/communicate training issues; resolve in timely manner • Provide guidance in defining data necessary to support training exercises • Review team's training work products for consistency and fulfillment of the requirements • Assess training evaluations and quantitative results; identify corrective or remedial duties as needed • Report weekly status to Project Management • Facilitate client reviews and sign -offs • Coordinate overall Knowledge Transfer program • Mentor and coach team members • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository Training Administration • Set up and prepare classrooms for end user training delivery • Assess City of Fort Worth project team members skill and knowledge needs City of Fort Worth Training Manager • Design and development of training • Planning and delivery of Pilot training • Training delivery Plan and co -manage team's work effort to meet established quality standards, schedule and budget • Review team's training work products for consistency and fulfillment of the requirements • Assess training evaluations and quantitative results; identify corrective or remedial duties as needed • Report weekly status to Project Management • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository Training Administration • Set up and prepare classrooms for end user training delivery • Register/notify participants for training courses City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 39 of 418 w Rotes Responsibilities • Assess City of Fort Worth project team members skill and knowledge needs • Schedule City of Fort Worth project team members for relevant PeopleSoft training courses Training CIBER Training Developer Developer Design and develop training courses and supporting materials and tools in accordance with the training approach and plan (e.g., guides, web -based training(WBT), and UPK web based learning assessment(WLA), job aids etc.) • Develop training and support deliverables (WBTs, WLA, presentations, business procedures, instructor and facilitator guides, participant outlines, job aids etc.) as defined by the design plans • Test training materials • Participate in Pilot training • Report weekly status to team lead • Identify problems and bring them to team lead's attention with sufficient lead time to address • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository related to training material development Trainer CIBER Trainer • Attend Trainer orientation sessions and participate in Knowledge transfer activities as planned • Prepare for end user training delivery • Conduct train -the -trainer sessions and orientations • Meet with relevant team leads in preparation for sessions • Provide support to City of Fort Worth trainers in the delivery of end user training • Perform training administrative functions as defined in training roll -out approach City of Fort Worth Trainer • Attend Trainer orientation sessions and participate in Knowledge transfer activities as planned • Prepare for end user training delivery • Attend train -the -trainer sessions and orientations • Meet with relevant team lead in preparation for session • Deliver end user training to the City of Fort Worth's end users • Perform training administrative functions as defined in training roll -out approach Internal CIBER Internal Controls and Security CIA Executive Controls • Attend planning sessions and status meetings Team • Monitor adherence to timeline and strategy and provide support for escalation of issues • Interact with City of Fort Worth leadership to ensure expectations are met • Budgetary oversight related to hours allocated to the team • Review key deliverables to ensure quality and adherence to standards CIBER Internal Controls and Security Lead • Conduct planning sessions with Functional Leads to finalize timeline and strategy • Coordinate with the Project Manager to plan and schedule resources for internal control review activities • Coordinate the setup of work sessions with Process Owners • Attend business process redesign, fit -gap analysis and other sessions with the Functional Team Leads to incorporate internal controls into the design City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 40 of 418 wk AND WE Roles Responsibilities • Develop risk assessment based on business requirements and prioritize • Review risks and internal controls to identify gaps and develop recommendations • Coordinate with the process owners in the development of action plans to mitigate any residual risk as necessary • Review all deliverables with the Functional Leads and Process Owners and obtain approvals as necessary • Supervise the internal control team and provide oversight of day-to-day activities to ensure adherence to schedule and budget • Review all team deliverables to ensure quality CIBER Internal Controls and Security Team Members • Attend business process redesign and fit -gap analysis sessions to understand business requirements • Review existing documentation including directives, policies and administrative regulations • Review the design of custom programs, interfaces, workflows and roles for design effectiveness of internal controls • Review test plans and test results for all unit, system and integration testing that involves internal controls • Document the risks and internal controls in the internal control framework • Update training manuals with information related to internal controls City of Fort Worth Internal Controls and Security Leads • Attend planning meetings to help finalize the timeline and internal control review strategy • Provide the necessary contact information for process owners and help coordinate the setup of work sessions • Provide insight into and available documentation for existing policies and procedures • Coordinate the City of Fort Worth review and approval of deliverables • Attend work sessions to develop action plans based on the recommendations • Monitor the progress of implementation of the action plans Technical CIBER Technical Manager Manager • Responsible for planning, scheduling and managing the resources and work associated with technology and application development and design. • Create the technical architecture and technical design for the PeopleSoft solution in accordance with the City of Fort Worth's architectural document, or identify gaps. Manage the resources for all technical sub -teams • Plan, schedule and manage all work tasks associated with the team • Day-to-day responsibility for managing all of the tasks that the members of the team perform and for the deliverables produced • Provide organizational change management technical expertise to the team and overall project team. Apply that expertise broadly, by ensuring all aspects of their team's solution work correctly and in concert • Resolve issues in a timely manner • Participate in quality reviews designed to verify that the team is completing work in accordance with standards that are established at the onset of the project • Plan, schedule and manage all work tasks associated with the application development team • Review and approve and modifications implemented by the software enhancement team • Responsible for assuring developers functionally understand modifications City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 41 of 418 Roles :Responsibilities before commencing development work • Review unit tests prior to submitting migration requests for completed development • Responsible for developing own functional knowledge of modifications being implemented • Raise issues to project management and implement interventions to address • Participate in knowledge transfer activities as required • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository • Manage the Microsoft Project workplan. • Design and develop security and compliance for PeopleSoft in accordance with City of Fort Worth policies and procedures • Manage technical testing activities • Provide hands on development to include coding and unit testing as needed once development scope is determined City of Fort Worth Technical Lead • Responsible for planning, scheduling and managing the resources and work associated with technology and application development. • Manage the resources for all technical sub -teams • Plan, schedule and manage all work tasks associated with the team • Resolve issues in a timely manner • Participate in quality reviews designed to verify that the team is completing work in accordance with standards that are established at the onset of the project • Plan, schedule and manage all work tasks associated with the application development team • Assume day-to-day responsibility for all of the tasks that the members of the team perform and for the deliverables produced • Review and approve and modifications implemented by the software enhancement team • Review unit tests prior to submitting migration requests for completed development • Responsible for developing own functional knowledge of modifications being implemented • Raise issues to project management and implement interventions to address issues • Participate in knowledge transfer activities as required • Provide hands on development to include coding and unit testing as needed once development scope is determined PeopleSoft City of Fort Worth PeopleSoft System Administrator System • Participate in hardware sizing and configuration exercise Administrator • Install and configure PeopleSoft instances /DBA • Provide PeopleSoft System Administration including installation and testing of PeopleSoft patches and fixes • Provide migration of objects between environments using appropriate toolset • Build and test configuration management processes including migrations. • Provide PeopleSoft User security administration (Handled by core team during design and development, then City of Fort Worth Security Administrators after go -live.) • Provide technical testing, tuning, problem resolution and documenting related to system administration • Support other teams as they do their business process testing as it relates to the technical architectures City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 42 of 418 W Rples' Responsrbilites. • Act as a backup for configuration management. • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository City of Fort Worth Database Administrator • Installation and configuration of the database and associated software • Administration of the database including DB patches and fixes Administration of database security • Configuration of DB specific components and monitoring of database utilization and performance • Data synchronization and management among all the PeopleSoft related databases • Performance tuning and problem resolution • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository Network City of Fort Worth Network Administrator Administrator Install and configure new network components including firewalls, switches, routers, IDS, and network cabling as needed • Administer the network components • Administer the servers • Administer network security • Configuration of monitoring software specific to network components Application CIBER Application Developers Developers Write Interfaces, Customization/Extensions , Conversions and Reports • Develop Interfaces, Customizations/Extensions, Conversion and Reports • Provide knowledge transfer to City of Fort Worth to develop Interfaces, Enhancements and Reports • Responsible for developing functional understanding of modifications prior to commencement of development • Responsible for implementing modifications based on approved designs per outlined development procedures • Responsible for documenting modification in detail per (technical specifications) outline development procedures • Responsible for raising issues and potential solutions to Technical Manager Participate in knowledge transfer activities as required • Make regular (monthly) updates/refinements to the PMRx or comparable project site repository City of Fort Worth Application Developers • Develop Interfaces, Customizations/Extensions, Conversion and Reports • Responsible for developing functional understanding of modifications prior to commencement of development • Responsible for implementing modifications based on approved designs per outlined development procedures • Responsible for successfully completing the unit test of assigned modifications • Responsible for raising issues and potential solutions to Technical Manager • Participate in knowledge transfer activities as required City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 43 of 418 Methodologies To satisfy the scope for the project, CIBER will employ the following three methodologies: Incremental Prototyping Methodology (IPM): structures and provides the key activities related to system design, development, testing, and rollout. • Change Management Methodology: structures and provides the key activities that prepare the organization to transition to the new PeopleSoft system and related business processes. Internal Control Methodology: structures and provides the key activities for the internal control strategy, risk assessment, identification of risks and exposure, and identification of mitigation activities. The IPM Methodology serves as the foundational structure of the overall project in terms of stages of work, objectives of each stage, and work activities. The project team will follow IPM as enhanced to include the agreed upon Work Products identified in Appendix N of the RFP as — mapped to standard IPM deliverables reflected in EXHIBIT B - PAYMENT SCHEDULE CIBER will adhere to IPM methods and the project team will produce deliverables as the means of performing the Services and providing the Work Products identified in this SOW. The Change Management and Internal Control Methodologies identify appropriate input and output points of interaction between work activities of IPM and those of the respective methodologies. The project plan will blend these three methodologies to provide a comprehensive, consistent — approach for executing the scope of this statement of work. Incremental Prototwinq Methodoloqy CIBER employs comprehensive System Implementation Methodologies that provide effective management of the solutions delivery process. This methodology is a set of repeatable, measurable processes that guide software implementations and help in evaluating project performance, risk, and the overall management of the engagement. CIBER's project approach will employ our Incremental Prototyping Methodology or IPM. IPM utilizes a building block approach to deliver incrementally more sophisticated capabilities of the _ software as the project progresses through each prototyping stage. Each prototype builds on the work of the previous stage allowing users to grasp the concepts of the current prototype before progressing to the next. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 44 of 418 The overview sections that follow describe the major IPM tasks and deliverables. M IR incremental prototyping methodology F Discovery Stage During the Discovery Stage of the project, CIBER will assist the City ink f Eli translating the Oracle system into a tactical plan. At a high level, the Discovery Stage describes the strategies of how the project will accomplish the project's objectives. At a more granular level, it translates those strategies into executable steps designed to accomplish the project objectives. • Project initiation activities identify the scope, approach, objectives, success criteria, and related project specific administrative functions. . The Project Charter establishes how the project team agrees to interact between themselves, the Project's Stakeholders, and ° constituents; and formulates the high-level implementation strategy for each major project component. Project Administration specifies the frequency and content of project reporting, risk and issue analysis and review, and steering committee and project team meeting schedules. Governance describes the leadership, management and decision making structure of the project team. • The Project Work Plan identifies, at a task level, the work that must be accomplished by the joint team, the estimated effort required, resource assignments, and relationship between tasks. • Fit/Gap establishes the core business and technical requirements for the initial implementation of the Oracle software. The fit analysis will resolve all high priority gaps using various approaches including process redesign, workarounds, and technical solutions such as workflow or reports. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 45 of 418 At the conclusion of the Discovery Stage, the team will have developed the Project's Charter which will refine and clarify the objectives and scope of the project. i P M Discovery Stage On a tactical level, the project team will have completed an initial definition of business and technical requirements, and performed high level process analysis. With this information the project team begins to configure the Oracle system to achieve the objectives established in the - Project Charter. IPM key tasks and deliverables for the Discovery Stage are identified in the graphic to the right. /PM Configuration Stage The Configuration Stage will focus on identifying and analyzing alternative approaches to performing business requirements and processes. The project team will use structured working sessions to review alternatives for a specific business topic. Prototypes may be created in the Development instance to demonstrate challenges and benefits of a particular alternative. For the sessions to be successful, the City team members will be responsible for bringing their knowledge of the City's business, the business topic to be examined, and an open mind to alternative practices that may not always exactly replicate the existing business processes. CIBER consultants will be responsible for drawing upon their prior implementation experiences and other CIBER resources to help design the City solution and resolve gap issues. High level Configuration Stage tasks include the following activities: IM IM E_J Basic Configuration —Conduct configuration planning sessions on the new system to define how the system will be configured to meet the City's requirements. The configuration planning _ sessions will also be an opportunity to identify any additional end -user training needs. Interface Planning —Detail plans are created for the interfaces identified in the City's requirements and any additional interfaces identified during the Fit Gap process. Conversion Planning —Conversion sources, data mapping and data cleanup occurs. The conversion approach and schedule are developed into a comprehensive plan. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 46 of 418 Report Planning —Detailed reporting analysis occurs to define which standard reports will be used and custom reports are required. Security Planning —Design and establish the access profiles to meet the business and security requirements of the City. Basic Conversion —Define data mapping and data cleanup requirements for each conversion source. Develop conversion approach and program. Conversion data is validated. Conversion scope expands with each prototype. Acceptance (Validation) Testing — Perform testing to ensure configuration settings produce desired results. iPM Complex Extensions Stage IPM Configuration Stage In the Complex Extensions Stage, the prototyping effort adapts the Oracle software by developing approved customizations. Representative tasks for the Complex Extensions Stage include: Customizations —Design and develop the customizations defined and approved during the Fit/Gap and Configuration Stage based on the project customization standards and documentation agreed upon in the Project Charter and in compliance with Oracle recommendations. Unit testing to verify each component functions as designed. Expanded Conversion —Conversion processing is expanded to incorporate more complex data or historical data based on conversion scope defined in the Conversion Plan. User Acceptance Testing —Perform testing, as mutually agreed upon per the user acceptance test plan, to ensure that the individual customizations and modular integration functions as designed. Key tasks and deliverables for the Complex Extensions Stage are included in the graphic below: iPM Environmental Adaptations Stage tPM Complex Extensions The Environmental Adaptations Stage addresses development and unit testing of all in -scope reports, interfaces, and any remaining data conversions. Custom components necessary to City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 47 of 418 support each report, interface, and remaining conversion requirements are created, documented according to the mutually agreed upon Project standards. As each technical development element is completed, it is unit tested according to a pre -defined test script to verify that the result sets satisfy the functional and technical design. Before a technical element is passed to pre -production Integration Testing, the documentation supporting installation and execution is completed. This, in effect, facilitates testing of both the documentation and the custom code. During this Stage, the Functional team will be formalizing procedures and materials development to support end user training and testing. Learning materials are designed in such a way to support the re-skilling of those employees whose knowledge, skills and aptitudes need to change to achieve optimal benefit from the new technology. Key tasks undertaken during the Adaptation Stage include: Interfaces —Design and develop the Interfaces defined and approved during the Fit/Gap and — Configuration Stage. All of the interfaces will be coded based on project standards and documentation agreed upon in the Project Charter and in compliance with Oracle recommendations. Unit test to verify each component functions as designed. _ Reports —Design and develop the Reports defined and approved during the Fit/Gap and Configuration Stage. All of the Reports will be coded based on project standards and documentation agreed upon in the Project Charter and in compliance with Oracle recommendations. Unit test to verify each component functions as designed. Expanded Conversion —Conversion processing expanded to incorporate any remaining data based on conversion requirements defined in Conversion Plan. User Acceptance Testing— Perform testing, as mutually agreed upon per the user acceptance test plan, to ensure that the individual customizations and modular integration functions as designed. lPM Deployment Stage The final Stage of the project is the migration from test to production. At the beginning of this stage, final checkpoints are used to review all areas of the organization's readiness. When all areas are deemed ready, the detailed cutover plan is executed as planned and tested during the mock cutover. Once all tasks in the cutover plan have been completed, but prior to commencement of normal business transactions, or `go live', the system will undergo one final test to ensure that it is _ functioning as expected. This final test is usually conducted by the implementation team and consists of running a random sample of transactions through the system to verify that all transactions have completed correctly. This test is generally executed in a non -production environment that has been copied from the actual production database. Key tasks for the Deploy Stage include: Conduct User Acceptance Testing— Conduct UAT processing to ensure that the system is — operating appropriately. This test will first be run by the core project team with the addition of some training resources. Here the users will ensure that the system is acting appropriately and that all objects have been migrated appropriately. In a second phase of UAT there will be an — expanded testing team. A series of "break me" tests will be run to ensure that the system will work under most conditions. In addition to this type of testing expanded users will have the chance to validate that the system will work for their day to day operations. _ Final Go Live Plan —Develop a detailed schedule of events that must occur to prepare the production environment and support for "Go Live". City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 48 of 418 Go Live Readiness Assessment —Assess whether all aspects of the organization: the system, users, management, communication and production support is ready to support "Go Live." Conduct End User Training —Develop End User Training Plan, training manuals and perform end user training to prepare the end users to support final testing and ultimately production Conduct Final Testing —Conduct processing in current legacy system and the new systems. Validate that the new system matches the results of the old system or reflects the requirements and approved solutions resulting from the Fit/Gap Analysis. Validate that the system is ready to transition to Production. Transition the software to the production environment via a structured and planned approach. Final Data Conversion —Conduct Final Data Conversion to ensure the most current data is present for all applications as planned in the Conversion Plan. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 49 of 418 Additional Detail relatinq to C/BER's Incremental Prototypinq Methodoloqy CIBER's Implementation Prototyping Methodology is a collaborative implementation approach that applies itself to the implementation of ERP packages by building upon the delivered working system and providing multiple stages of testing to confirm user requirements are met using system functionality and delivered configurations wherever possible. Stage Activities There are five stages of the IPM Methodology to be performed and the tasks that will be performed during the implementation are listed below. The five stages are: • Discovery Stage • Configuration Stage • Complex Extensions Stage • Environmental Adaptations Stage • Deploy Stage Establish Baseline Schedule and Budget • Introduce Project Change Management • Host Project Kick -Off • Approve Planning Outputs • Initiate Project Execution City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 50 of 418 Im •w Mr • Review Project Scope, Team Roles and Responsibilities, Project Management controls and processes with the project team • Define key project strategies for communication, conversion, process analysis, training, and testing r Define Performance Based on objectives defined in the Project Charter and those Measures in support specific to each module (where applicable) define the following of Project Objectives types of Performance Measures: i 1� i City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 51 of 418 • Transaction processing improvements • Workflow routing and associated streamlining of approvals • Month -end and Year-end processing (closing the books) • System performance metrics (based on transaction types identified in this Statement of Work and system availability) At this time, City Department Subject Matter Experts begin to be involved in the design process. do on Discovery Stage ,aj A0t1ulty fi te�s� Qte --r Create Project Establish the Project Charter during the project start-up process. Charter The Project Charter will: • Determine the critical success factors to successfully complete the project and confirm project scope, technical infrastructure requirements, and Project Team resource requirements -- • Identify project team roles and responsibilities; review and confirm project implementation strategy with project team (conversion, testing, training, etc.) — • Establish and communicate project management control processes • Identify risks and develop the approach and action items to mitigate risks, this information will feed into the Risk Management Plan • Identify communication requirements and schedule for executive team and project team meetings, this information will feed into the Communication Plan • Be signed off by project management and be used by the team as a foundational document Create Initial Project Create an initial Project Work Plan that includes tasks, schedule Work Plan and resource assignments. • The initial plan will focus on the Discovery Stage of the project and detail out all tasks associated with that stage T • Post Discovery stage the Project Work Plan will be updated with detail based on the defined Scope, Requirements, and Gap Solutions approved by the project leadership at the conclusion of the Fit/Gap Analysis • The plan will be monitored and updated by the project leads on a weekly basis - City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 52 of 418 M tage77 1 ct� by Steps/Notes , Identify Project Conduct Project Risk Assessment and develop Risk Management Assumptions, Plan: w Resource The Risk Management Plan will clearly define project Constraints, Risks, risks, identify the potential for those risks to become and Other Critical Path items realities, and provide effective risk mitigation options, as -- well as listing all project assumptions, and associated project constraints • Risks and issues will be reviewed on a bi-weekly basis between the project managers and formal reports will be updated on a monthly basis • Formal Risk Assessment Reviews will be conducted throughout the project. These assessments will be scheduled based on major project events - configuration, development, testing, training and cutover are examples of those major events Create Refer to the Change Management Section of this SOW Organizational _ Change Management Plan Build Weekly and Develop a project Communication Plan during the project start-up Monthly Project activities to manage the internal project team communication Communication Plan efforts. • This plan will establish tools, processes, and procedures for communications • Effective measures will be established and updated at each major project milestone • The plan will be monitored by the change leads and updated as appropriate Build Organizational Develop an external Communication Plan during the project start - Change Management up activities to manage the external project communication efforts. Communication Plan • This plan will identify the activities and tasks the project team will execute to inform all parts of the organization of the project successes, changes to the organization as a result of the implementation, and other impacts relating to the transition to the new system • Effective measures will be established and updated at each major project milestone • The plan will be monitored by the change leads and updated as appropriate Departments are also involved in this activity to begin identifying communication content and methods. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 53 of 418 Discovery Stage Activity StcpslNotes Review current Complete the following "as -is" business process review activities: Business Processes • Schedule, confirm, and prepare for process definition sessions by business area • Identify the core business processes (level 1 using Oracle Business Models) and develop summary descriptions of each process • Conduct interviews using questionnaires and other information sources to clarify processes _ • Gather any other current business materials that enhances team understanding and documentation of current business process requirements • Identify any issues regarding the current business analysis • Review the Current Business Baseline with users and business area management ! • Secure acceptance of the Current Business Baseline from business area management Departments are involved in this activity to communicate current processes and are exposed to the PeopleSoft Demo Instance so that they can begin learning the standard PeopleSoft business processes and configuration options. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 54 of 418 Discovery Stage 04 Activity StepslNotos i Perform Fit/Gap Complete the following Fit/Gap activities: Analysis • Conduct Fit/Gap analysis to identify and confirm any additional implementation requirements for the City • Walk through the delivered functionality of PeopleSoft applications and contrast those processes against City requirements. For purposes of this implementation, the initial Demo Environment will be configured to support basic Public Sector functionality, including Fund Accounting and Commitment Control. • Identify the details of how the PeopleSoft system fits and does not fit with City requirements • Conduct Fit/Gap analysis in either one-on-one or group sessions that are scheduled to: • Compare PeopleSoft functionality to business requirements • Identify functionality that enables improvements to current processes • Reach consensus and decisions on the features to be used, involving departmental Subject Matter Experts. • Document current critical business practices and identify areas of shared ownership • Capture potential future enhancements needed for on- going business needs • Produce a finalized assessment (Fit/Gap) document The Fit/Gap process will determine the necessary changes to the delivered baseline system. Where gaps are identified, the team will consider the following resolution options: • Process change (revising the business process to meet delivered system requirements) • System modification (customizing the system to meet business process requirements) A blend of process change and system modifications For each gap, workarounds that do not require system modification and solutions that do require system modification will be documented, and the costs for each system modification will be estimated City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 55 of 418 Discovery Stage Activity StepslNntes Deliver Fit/Gap Complete the following Fit/Gap finalization steps: Report • Prepare and deliver Fit/Gap Report based on documentation developed through the Fit/Gap process • Brief appropriate (as final report is being completed) approvers on gaps that will require broad socialization across departments • Identify additions to the catalog of reports, interfaces, conversions and extensions/modifications, City will decide and sign -off on development list for all technical objects. • Update Project Work Plan to reflect additions, changes and deletions • Prepare positive, negative, or no -cost change orders to document changes of scope Business Process Please see Business Process Redesign Methodology description Redesign in this SOW Configuration Stage Activity BtepslNotes Configure and Set Up Complete the following configuration steps: Base Tables Based on completed requirements and Fit/Gap analysis, (Prototype One) develop the Configuration Plan • Conduct configuration planning sessions on the new system to define how the system tables will be configured to meet the requirements • Educate City counterparts on value sets by module/table that will need to be defined/gathered and assign responsibility confirming deadlines for completion as per approved Work Plan • As values are received, CIBER and City counterparts configure the tables within the system and documenting the values entered in the base tables. This does not reflect the full set of values to be gathered and configured, which will be done in Prototype Two. • Update the configuration document throughout the project lifecycle as necessary • Test configurations internally with the project team and City Subject Matter Experts and Departmental personnel to be defined City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 56 of 418 Configuration Stage Activity - - StepslNctes Create initial System Complete the following system testing activities: Test Plan and Scripts Develop the Testing Plan to describe the testing activities, .. (Prototype One) tools, and techniques to be used during the project • Include the methods for the development of test scenarios, documentation of results and fixes, and retesting. • Include requirements for testing environment and staffing; schedule of testing activities; development of scenarios, tester training, and other preparatory activities; and templates. Testing scripts and worksheets will also include the following: • Task information and priority Problem status • Initiator and owner of the problem • Script number and problem description • Date and time of the script execution • Database (development, test, or production) • Problem resolution approach City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 57 of 418 y on Iguratlon stagy Activity Steps/ 4 N Define Gap Solutions Complete the following activities gap solution related activities: and Functional Specifications • Using the list of approved gaps, facilitate design sessions to _ review options, prototype solutions with the department Subject Matter Experts and select the approved option • Review final design alternatives with management and gain approval signoff • For each gap solution that has been approved, develop a functional specification that describes the purpose of the object, the business process supporting the object and any associated processes • Once the functional specifications are approved update the Project Work Plan and associated documentation • Turnover the functional specifications to the technical team to create technical specifications T • The functional specification process includes: • Document business requirements • Identify current versus proposed process steps and assess the feasibility of proposed alternatives • Clearly identify the chosen alternative that best suits the City • Document major operating and policy decisions related to the chosen alternative -- • Evaluate how practices would change and pass potential impacts to Change Management and City Project Director that need to be passed to City Approvers via briefs • Facilitate the appropriate handoff from functional team members to the technical team for development of approved modifications City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 58 of 418 Activity + Finalize Project Development Scope 11 '1 Update Detailed _ Project Work Plan reflecting results of Fit/Gap Analysis City of Fort Worth / CIBER, Inc. Professional Services Agreement ` Page 59 of 418 - Configuration Stage Stepsimotes Complete the following project activities: • Management will make final decisions on how to solve open gaps based on the Fit/Gap Document • The catalog of development objects will be finalized. This will become the scope defining document for the development effort. • The decisions will be documented and resources will be assigned to development objects according to the approach outlined in the Approach to Managing Custom Development • Change leads will communicate decisions to both the project team and external entities • Once the final design alternatives have been approved the project managers will write up a change order to process any scope changes, if development estimates exceed the not -to - exceed amount in the payment schedule. Complete the following Project Plan update activities: • During the Post Discovery stage the Project Work Plan will be updated with the details of the defined Scope, Requirements, and Gap Solutions approved by the project leadership at the conclusion of the Fit/Gap Analysis • The Project Work Plan will include detailed tasks, estimated hours to complete, and resources that are leveled to no more than an average of 40 hour week • The plan will be monitored and updated by the project leads on a weekly basis r+ Pit figuration Stage Acttvtty $tepr;/NQtes Perform second Complete the following Configuration activities: round of system Prototype Testing — In a highly collaborative work session, testing utilizing CIBER leads the City staff through the following interactive delivered system with all customer prototyping steps: configurations 0 Identify unit test case scenarios (Prototype Two) • Interactively test and revise configurations • Validate requirements • With the base system model already populated with a representative set of data, CIBER gives the City staff a guided tour through the system's menus, pages, tables and reports • Gather missing configuration values and populate the system tables as they are received. • Drive testing sessions with City configurations to familiarize — City staff with the system enabling them to proceed through the following steps more rapidly, This is where City functional staff will begin assuming configuration responsibilities as part of Capability Transfer Plans • CIBER will collaborate with City staff to modify system test scripts templates provided by CIBER, to represent the range and complexity of the City requirements • Demonstrate the system's functionality in the process, test boundary conditions, unexpected input, error recovery, and _ security • In this first prototype CIBER will be doing the majority of the work with the City team's assistance _ • In subsequent prototypes, the City team will take on the majority of the tasks • CIBER will guide the City Core Team in altering baseline test scripts and assist them in monitoring, interpreting, and evaluating the results of the subsequent prototypes • When tests fail or results do not conform to requirements, CIBER and City staff will isolate the cause of the failure, and make necessary changes to the test data or the base system model and retest as necessary • Through this iterative process, the team will gain invaluable knowledge and skill in adapting PeopleSoft rapidly City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 60 of 418 M w 6o_n iguratlon Stage d I Activity stepsimotes Prototype Testing — As the final step of the Configuration Prototype, the team will roll Expanded Team out the initial testing to an expanded user base of Subject Matter Experts and Departmental personnel, these users will be selected by the core team to help with the testing process to validate that the business requirements are being met, to accomplish: • "Buy -in" of the system by various departments • Any business requirement that was missed. The second level Prototype Testing process is: • CIBER will collaborate with City staff to modify test scripts that were created in the previous round of testing ' • City will run actual testing which involves the actual processing of the test script population CIBER will assist in the initiation of the test scripts and assist — in the monitoring, interpretation, and evaluation of the results At the end of the Prototype Stage, business process and software requirements are finalized and documented in the Traceability Matrix as discussed in the Business Process Redesign Approach Complex Extensions Stage Activity StepslNotes Write Technical Once functional specifications are approved and have been Specifications to handed off by the functional team the technical team will begin the support approved creation of technical specifications Customizations, Reports, Workflow Technical specifications will include: and Conversions 0 Resource assigned • Completion date Estimated hours • Requirements associated to the object Description of the solution Tools used to complete the solution • Testing scripts and results The technical leads will keep track of the inventory of specifications and the progress against Project Work Plan for the specification development. Project Managers will use information related to development provided by the technical leads and update the Project Work Plan for progress and note the completion of each object as it is finished City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 61 of 418 ON Pa Gotxie JE=xtensis 5ta�e /31C IVltj% Application Security Create an initial security design document that will identify: design • Initial design for security _ • Communication procedures to get information from the departments • Security roles and profiles • Processes associated with the profiles • Testing mechanisms _ Security roles and responsibilities will be established by listing the Components and Pages in an EXCEL Workbook. This will allow the City to design the security patterns needed for each User Role. As each Role is defined, they will be entered into the system and validated. Once a core Role has been established, the cloning process delivered within PeopleSoft will be used to create the remaining Roles and edit accordingly. Functional leads will track the progress of security activities for their modules, information will be documented on their weekly status reports. Once all roles have been defined, the following will occur: • Identify user roles across all business functions and organizations • Identify security requirements for each user role • Map user roles onto application security structures • Define application module access for each system user role • Secure acceptance of the Security Profiles City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 62 of 418 Complex Extensions Stage ActivitytepsfNotes Build Technical �llowing development activities will be completed: Solutions to support Review Application Extensions Functional Specification approved Customizations, • Describe the high-level approach Reports, Workflow and Conversions • Define detailed program logic for modules (forms, reports, and programs) • Document integration issues • Document any upgrade considerations • List installation requirements • Document any additional information that may be helpful during the implementation of the customization • Update Application Extensions Functional Specification, as needed • Review existing materials and the Current Process Model and conduct interviews (if needed) • For conversions: • Describe the purpose of the Data Conversion Requirements • List the objectives of conversion and critical success factors • Describe the conversion approach, key inputs, resource requirements, organization, risks and contingencies • List the tool and deliverable naming standards to be followed for conversion • Identify the key business objects and data translations for data cleanup, as well as data normalization and reduction requirements • Describe the high-level conversion testing strategy • Review the Data Conversion Requirements and Strategy with the designated approver and secure acceptance • Identify any material changes to project scope and associated task estimates City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 63 of 418 Update Help Desk Support Process and Procedure Documentation City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 64 of 418 • Engage core team and deliver UPK development overview/refresher • Establish a common set of shared training development guidelines to include screen resolution (800x600) graphic design standards and wording principles • Core team will provide list of business processes and subjects (a single business process will likely have multiple subjects from which actual courses are developed) by module and forward to developers • Core team will record the initial pass (will also be used for test scripts) transactions within each business process subject by module with UPK developer guidance • UPK developers will take base recording of transactions and create the explanatory frames, bubble text and other details to support final draft of materials • CIBER/City core team members will review final draft of materials by module and business process and approve content after development suggesting any adjustments necessary • UPK development team will make necessary adjustments and store each Module, Section and Topic in the UPK repository controlling all versioning from a single point • Test the materials and prepare online and classroom logistics as noted in the Training Plan • Training materials for the various training audiences will be based upon the City finalized future business processes • The courseware will be role based and comprehensive in the number and type of exercises it will employ to provide hands- on activities for the City's diverse end user community • The material will be process -oriented and promote user understanding by following a step-by-step progression Documentation of procedures related to reports, interfaces, conversions and extensions/modifications developed by CIBER will be incorporated into the Functional/Technical specifications Review of existing Help Desk Support procedures will be completed by each functional CIBER/City team by module and updated to reflect changes to existing procedures that are impacted as a result of the Phase IIA — 2C implementation in Complex Extensions Stage .. Activity StepsfNates ' Create Production Refer to the Post Production Section of this SOW Support Plan a Environmental Adaptations Stage i Activity I $tepslNotes Update and Finalize The following configuration related activities are completed: Configuration and Setup of Base Tables 0 Complete updates of configuration guides after the execution of System testing • Finalize the configuration guides after execution User Acceptance testing Add finalized documents to the project library Enhance Test Plans The following testing related activities are completed: = to include interfaces, customizations and Update Testing Plans and Scripts after the execution of reports System testing . Finalize the Testing Plans and Scripts after execution User _ Acceptance testing • Add finalized documents to the project library Load Data and The following conversion related activities are completed: Execute Conversion Tests • After the conversions have been unit tested and approved the data will be loaded into a separate conversion environment Functional users will test and validate the data in the conversion environment Once the conversions have been validated and approved they will be migrated into the Gold configuration environment • Specifications will be updated as necessary by the technical team t City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 65 of 418 rA • Resource assigned • Completion date PM • Estimated hours • Requirements associated to the object ... • Description of the solution • Tools used to complete the solution • Testing scripts and results The technical managers will keep track of the inventory of specifications and the progress against plan for the specification — development Project Managers take the information provided by the tech leads and update the Project Work Plan Build Technical Refer to Environmental Adaptations and Build Technical Solutions Solutions to support sections above approved Interfaces Build End -User Refer to End -User Training Design section above and in the Training in support of Methodology section of the Statement of Work Training Plan Perform System Test The primary purpose of system testing is to validate the system as that includes all a whole (i.e. servers, security, applications, Custom Developed configurations, applications, workflows, data and interfaces) works together as customizations, designed and meets the defined business requirements and workflows, interfaces processes and conversions The project team will • Create the initial environment from the Gold environment • Migrate of all configuration, data, technical objects, and _ security • Execute the test plan for system testing • Update all corresponding project documentation City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 66 of 418 Environmental, Adaptations Stage Activity StepslNotes Create Cutover Plan The project team will develop the Production Cutover plan to be I used to track the status of all activities necessary to bring up production As part of the plan the team will also develop a short interval schedule for 48 hours preceding start of cutover and duration of all cutover activities. This plan and schedule will: • List all steps, responsibility and target time increments • Include a cutover dress rehearsal, inclusive of performance testing that will be executed as part of the deployment stage • Include a implementation backout plan ti Establish the staffing model, communication mechanisms and support procedures to prepare transition support team for post -implementation support The technical lead will be responsible for keeping the plan updated as the project team uncovers information such as conversion program run times and possible cleanup tasks Other Cutover Activities include: • Reviewing the proposed system architecture, locations, and resources within locations • Determining the migration priority of applications and critical business functions and organizations • Deriving the resources and tools required in support of migrating business systems, software, and hardware • Anticipating implementation contingency situations by reviewing similar City implementation projects • Defining a Transition Support Strategy • Updating the schedule to reflect the need -by dates for receiving and installing production hardware and software • Reviewing the draft deliverable with senior management and obtain approval • Identifying any material changes to project scope and associated task estimates with the project manager City of Fort Worth / CIBER, Inc. Professional Services Agreement T Page 67 of 418 MR w►at►nnetttal Adaptations Sage 5 Activrty $te s otes p Evaluate Readiness Covered by the development of the Readiness Assessment deliverable, the team will consider the following items contained in other descriptions within this SOW and deliverables that are mapped to work products in RFP Appendix N and noted in the Exhibit K: - Deliverables Cross Reference contained in this SOW • Environment stability • Production Data Configuration and completeness • Development completion _ • Data Conversion • Business Processes • Reporting • End User Training • Issue Status • Cut Over and Contingency • Production Support *4 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 68 of 418 0" wo Qeploy Stage, t Agt "Ity taps%iVczte jp Prepare Production Update (if needed) the Architecture Plan for hardware, software Environment and middleware purchases for production environments Plan for production implementation including: • Validate hardware infrastructure • Schedule resources for the installation • Develop configuration/installation checklists, as required • Develop installation verification plans Install all application, middleware and tool software for the production environment Conduct certification of environment Set up production security for testing activities The technical leads will be responsible for updating the corresponding technical documentation Perform User Execute the Acceptance Testing procedures as outlined in the Acceptance Test User Acceptance Test Plan to validate the system as a whole (i.e. servers, security, applications, Custom Developed applications, workflows, data and interfaces) is accepted by the end user community The project team will: • Create the initial environment from the Gold environment • Migrate all configuration, data, technical objects, security and seed data End users will execute scripts that were used during prior stages of the project Any system defects identified are confirmed by the core project team, if actual defect exists the core functional and technical team will follow existing defect resolution process and correct Re -test all corrected defects Update all corresponding project documentation by the project team that results from User testing activities Perform Cutover Execute the cutover plan Monitor the plan and communicate any issues to the project sponsors City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 69 of 418 Change Management Methodology CIBER's Change Management Methodology supports its Incremental Prototyping Methodology (IPM) throughout all stages of a project. The focus of IPM is not just on implementation, but on engaging the right people to be a part of the implementation process. The expectations are that these individuals want to understand what the PeopleSoft software can provide in efficiencies (hard or soft cost reduction) and effectiveness (value-added activities) to manage the City's business functions. Doing so enables the making of good business decisions with an eye toward the future versus the status quo. The following is a diagram of how CIBER's Change Management Methodology integrates with IPM: CIBER's Change Management Methodology Vision and StrategyAlignment • Leadership/StakehoiderAlignment •Organizational Readiness Assessment 'Communication and Change Strategy Discovery I Final headiness Preparation • Business Readiness Workshops • Business Readiness Assessments ■ Establish Help Desk Support System Complex .�_ Configuration Extensions Environment Adaptations EnablingC- Deployment * Change M�Y Training or * Communication and Leadershipand Manners CMTraining Go Live FeedbackPlan Organizational impact Analysis & Plan Go Live & Support • Leadership and CM * Go Live Readiness Workshops Sponsorship Roadmap • Business Readiness Assessment ■ Celebrate Success! End -User Training Development and Delivery Methodology - The text below outlines the end -user training activities and associated deliverables. Specifics such as number of users, maximum number of users in a classroom setting or lab, training hours, training dates and training outcomes will be products within the end -user training deliverable, Training Plan Creation. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 70 of 418 y.n End User Training Assessment Towards the completion of Base Configuration members of the CIBER and the City's Training Team will validate the following: • Application scope for the project phase in progress • Process owners for each functional area in scope • Current access for users managers, helpdesk employees, support, executives v and others as appropriate • Future access that each user group will need • Training methods that have historically worked best for the City • Use of UPK as the training development tool - Major activities include: • Review documented To -Be Business Processes that are supported by the new system — determines the baseline for the development of training materials and of the impact to roles, agencies and the organization • Audience identification — identifies users who are directly impacted by the new business processes and system, and the number of users, their role in the future state and their location Trainer Identification — In support of the Train -the -Trainer approach, the City will identify trainers in addition to those being provided by CIBER, who are committed to the project and will provide end user training in a classroom environment, scheduled labs and/or as a coach for self -paced online training for a particular roll -out • Training facilities assessment — evaluates the required number of training facilities, hardware requirements and infrastructure needs including LAN capabilities and web -access • Curriculum Plan — identifies required training courses, learning objectives, applicable roles and required pre -requisites • Developer Identification — identifies those who will develop the end -user training curriculum The deliverables in the Preliminary Training Plan include: • Preliminary Roles and Curriculum Grid • Training facilities assessment - Trainers for each scheduled roll -out • Preliminary Curriculum Plan • Developers for training curriculum City of Fort Worth / CIBER, Inc. _ Professional Services Agreement Page 71 of 418 End User Training Curriculum and Course Design Assuming UPK as the tool, identify each course by name, summarize the content, " learning objectives, and identify applicable roles and any required prerequisite classes. Major activities include: • Update curriculum design plan — as applicable. Additional information about how each process will be used may come available as this set of activities progress. • Final determination of training material — initial analysis is transferred into .� concrete form and consensus is reached on what training material will be developed for each of the identified training tracks. • Course days analysis — analyzes course days based on the audience �. identification, assessment, role descriptions and the curriculum plan as well as the required number of courses and length of each course. • Install development tool if not already installed - CIBER will conduct UPK training rt to the identified City curriculum developers. • Determine schedule of classes — the schedule will be based on deployment of _ the City's modules, availability of training facilities and anticipated Go -Live date(s). The deliverable is a finalized Training Plan to include: • Finalized Curriculum Plan • Training schedule — • Preliminary course days requirements analysis by location, module and training audience Develop Training Materials Within the following set of activities, the materials needed for training delivery per the End -User Training Plan will be created. Major activities include: • Setup training development environment and database(s) — includes entering staged training data to reflect business processes during training. • Develop training materials — including job aids, business process documents and instructor / participant guides that are based on the new Oracle processes with any customizations to reflect the customized environment. • Review and approve training materials — as part of the iterative preparation process, the identified trainers will continually review and test the draft training components specific to their functional area. Once this process is complete, finalized training materials will be approved by the City. • Pilot End -User Training — as part of the development and testing process, , members of the CIBER/City training team will conduct pilot training that familiarizes end users with the new processes in advance of User Acceptance Testing (UAT). This also provides an opportunity for the "new" trainers to become familiar with the new business system and processes in an informal environment. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 72 of 418 • Create training assessment tools — this may include paper -based or online questionnaires or to assess the delivery effectiveness and content relevance. Evaluation of the Training Plan is almost continuous as the training program is constantly subjected to internal review and adjustment throughout the development and delivery process. Deliverables include: • Finalized Training Schedule • Environment(s) for the development and delivery of all end user training Classroom Training Delivery Pilot End -User training as described above will be completed by pairing an experienced CIBER trainer and a City trainer. Actual classroom training will be completed as follows: • By a single CIBER/City trainer and augmented by functional team members or City SME's as required for low impact (entering an invoice as an example) classes. A complete list of low impact classes will be identified in the training curriculum deliverable. • By both a CIBER and City trainer and augmented by functional team members or City SME's as required for high impact (procurement requisitioning and purchasing as an example) classes. A complete list of high impact classes will be identified in the training curriculum deliverable. UPK Online Training Delivery Online UPK delivery will be offered via the following modes. All classes to be delivered via these methods will be identified and documented in the training curriculum deliverable: • See it — Allows users to watch the class as the system goes through the standard delivered PeopleSoft business process steps explaining each step as it moves forward. This will be used to familiarize new city participants to PeopleSoft as they are integrated into activities pre fit/gap. • Try it — Allows users to follow the directions of a standard PeopleSoft delivered business processes as directed step by step by the UPK program as delivered. Both of the above are predicated on the UPK content that was purchased by the City. • Know It — Allows the user to assess how well they know the system. The user performs the City business process (with the appropriate training instructions/materials) and the system will prompt them if a mistake/step is made, but does not tell the user the step required to correct the mistake. At the conclusion of the exercise, the system provides the user with a test score. This mode can be taken multiple times and is useful in measuring proficiency with the business process and application prior to granting access to the production system. The actual use of this mode will be defined and agreed to in advance of rollout to the City end -users. City of Fort Worth / CIBER, Inc. Professional Services Agreement �' Page 73 of 418 Internal Control Methodoloqv and Work Plan CIBER has defined a staged approach for the security and internal control aspects of the Enterprise Resource Planning implementation project. The project will be executed across five distinct project stages. The Internal controls project team will be embedded in the ERP implementation team and the timeline will be adjusted to correspond to the overall timeline and the IPM stages. • Separation of duties strategy review • Conduct planning sessions with City finance team leads and the functional project team leads • Update the project timeline, review strategy and risk assessment approach based on the planning sessions • Review chart of accounts design to identify related risks that Major need to be mitigated Activities Review preliminary design of BSO to PeopleSoft interface to identify related risks that need to be mitigated • Develop separation of duties matrix identifying potential conflict scenarios related to the modules in scope (PeopleSoft) as well as conflict scenarios related to the PeopleSoft payments of BuySpeed matched invoices processed through the PeopleSoft voucher build process • Internal Control Review Strategy • Risk Assessment and Plan Dellverbles _ Chart of accounts design review • BuySpeed to PeopleSoft design review • Separation of duties matrix City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 74 of 418 04 OR 4" M City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 75 of 418 Stage 111 ,Internal Controls Design Effectiveness Review, ,dW The design review stage will, span across the Configuret%gn, Complex Exti~nslons and Environmental Adaptations IRM: Stages. During this Stage, GIBER will review the core functionality, design of any custom functionality, workflows .and interfaces to identify if : related risks are mitigated through automated- internal c<ontroi"s where possible. CISER will also review. the roles developed to identify any separation of duties conflicts froma design perspective. Any internal control: gaps will be documented and recommendations provided to mitigate' those gaps through either system enhancements and workarounds.or establishment of manual controls, • Assess the design effectiveness of internal controls through the Objeptwes review of standard and custom system design • Assess the level of separation of duties achieved through the design of system roles • Review core functionality to assess the design effectiveness of the internal controls • Review the design of custom programs, interfaces and workflows to assess the design effectiveness of the internal controls • Review role design to identify any potential separation of duties Major Activities conflicts • Document all system related internal controls and map them to the associated risks • Develop recommendations to mitigate gaps due to ineffective — design of internal controls or lack of automated internal controls • Document potential manual internal controls where the risks cannot be mitigated through automated controls • Updated Internal Controls Framework to reflect actual controls in place Deliverables' • Role definitions • Separation of duties design analysis • Internal Controls Gap Tracker with recommendations City of Fort Worth / C1BER, Inc. Professional Services Agreement Page 76 of 418 M on City of Fort Worth / CIBER, Inc. Professional Services Agreement ` Page 77 of 418 ION Ort d' Stage V:- Knowledge Transfer Knowledge. transfer even though separately identified es: 2 stage occurs throughout the ro ect: The internal control framearork will be u dated;,throu throughout the ro act and�an P 1 .. P g P J, y issues ''communicated to Management. ` During the Deployment, Stage, the`" control ' framework will be finalized and'CIBER will work with Management to formulate:: ctio plans for any residual risk to be re,mediated: CIBER will also update the training i materials to reflect the internal controls; and c{uties related them. • Finalize the Internal Control Framework Objectives Communicate and educate City personnel on internal controls and associated duties • Finalize and obtain management approval of the Internal Control Framework Major Conduct work sessions with key process owners to develop action Activities plans to mitigate any residual risks as necessary • Update training manuals with information related to internal controls • Finalized Internal Controls Framework Deliverables . Residual risk mitigation action plans • Training materials .-• City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 78 of 418 ,R Additional Approach Discussions A Project Charter will be created during the planning stage of the project to define the management processes to be followed for the project. These processes will minimally include the project planning and project controls described below. Protect Planninq CIBER will create and maintain a Project Work Plan throughout the project life cycle that represents the project's scope of work and responsibilities as defined in this SOW and those dependent work efforts that affect the project's schedule or staffing. The initial Project Work Plan will be established with the City's approval of the Project Plan Deliverable and updated for each Phase. During the project, the CIBER and City Project Manager will: • Manage the baseline Project Work Plan • Control change to the planned scope, staffing, and schedule through the Scope Change Management Process. (See the Project Control Processes described below) • Track approved changes to scope, staffing, and schedule by revising the baseline Project Work Plan and maintaining its currency Project Work Plan Contents The baseline Project Work Plan will contain: • Project's major activities and associated tasks - no task shall be less than eight hours • Dependencies that affect the project's schedule • Specific resources assigned to project tasks • Estimates of effort for each project staff assigned to a task, leveled to no more than 40 hours per week • Milestone and deliverable dates • Project schedule City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 79 of 418 Proiect Controls Project control processes manage project progress, project scope, enforcement of standards for quality assurance, and resolution of issues. Project controls include Status Management, Issue Management, Scope Change Management and Quality Assurance. Status Management On a regular schedule, CIBER and City Project Managers will track, document, and communicate project status to the City Project Sponsors and Advisory Committee or other designated management oversight group. The project will also undergo periodic management reviews by a CIBER Center for Project Performance reviewer as described in the Quality Assurance section. The CIBER and City Project Managers will produce status reports, based on project team meetings with project team members. They will confer with the City Project Sponsors to discuss project progress every week and attend scheduled Advisory Committee meetings. The format of the Status Report will be defined in the Project Charter. The Project Managers will work through project issues, risks, and changes. The CIBER and City Project Manager will review project progress and status with the project leads and team members for both CIBER and the City on a weekly basis, or more often if deemed necessary by either Project Manager. The project team will meet to review the Project Work Plan and each team member's progress toward the successful completion of their assigned tasks. The team will focus on estimates -to -complete and early notification and assessment of project issues and change requests. The City Project Manager, with the CIBER Project Manager's assistance will also review the Project's progress and status with the City Advisory Committee (or other governing group) on a monthly basis or as alternately scheduled by the Committee. The City Project Manager will present information and lead discussions regarding project progress, Quality Assurance Review recommendations and items escalated for Committee resolution. Issue Management The CIBER and City Project Manager are responsible for documenting, tracking, and bringing to closure project issues that affect the project team's ability to complete its work. If an issue cannot be resolved, the City and CIBER Project Managers will escalate per the agreed to Issue Resolution and Escalation process documented in the Project Charter. Any other specific issue management policies will be defined in the Project Charter produced during the planning phase for the project. Scope Change Management The Project Scope Change Management process encompasses any alterations to the tasks, resources, schedule, or costs of deliverables for the project, as defined by the Scope section of the Statement of Work. The CIBER and City Project Managers are responsible for ensuring that changes affecting the project's scope, schedule, or cost are City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 80 of 418 documented, tracked, and closed. Notification of intended changes must be communicated in writing to the City Project Manager by the CIBER Project Manager, and will include justification and analysis of the impact on the project. As part of the development process of a change order, an assessment will be made for impacts on scope and milestone payment timing of existing deliverables as defined in the Payment Schedule. If necessary, existing deliverables may need to be adjusted by dividing or merging deliverables, adjusting the expected timing of a deliverable, and potentially adjusting cost to reflect changes to work efforts. Each agreed to scope change order may result in an additional milestone payment. If the impact of a scope change creates a project delay of greater than 10 calendar days, a revised milestone payment schedule may be developed and agreed to. Change Control Procedure Specific change control policies will be defined in the Project Charter produced during the planning phase for the project, and will include the following: • Change Request Approvers: Persons from CIBER and the City that have been designated as the approvers of change requests for the project. • Approval/rejection turnaround timeframe: An agreed to timeframe for approval or rejection by City approver for change requests, including the sample form to submit for requests to be called the "Change Request Form". The format of the Change Request Form will be determined and mutually accepted by the CIBER and City Project Managers during the Project Charter. • Course of action if an approver is unavailable or does not respond with a decision in the timeframe specified: If the City approver does not approve or reject the change request within a timeframe documented in the Project Charter and does not communicate a timeframe in which a decision will be made, the requested change will be considered deferred: The change request status will be logged, tracked and managed as a `Deferred' request. Work will progress without incorporating the requested change into the work plan. Where an approval or rejection decision is necessary for the project to progress, the change request decision will be escalated as a project issue in accordance with the project's Issue Management Process defined and documented in the Project Charter. • Analysis of 'out of scope' Change Requests: For change requests that are determined to be outside the stated project scope, the City approver will authorize budget and/or schedule allowance on a fixed fee basis for the initial analysis of a change request, either as direct funding for the analysis effort or as part of the overall funding for the implementation of an approved request. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 8l of 418 • Resolution of scope disputes: Please see the dispute resolution process defined in the terms and conditions of the contract between CIBER and the City in the event the CIBER and City Project Managers are unable to resolve the scope dispute within the timeframe mutually accepted and defined in the Project Charter. Quality Assurance CIBER's Quality Assurance Process will: (a) Evaluate processes, work products, and _ services against the applicable process descriptions and methodologies, standards, and procedures as defined below; (b) Identify and document noncompliance issues, and (c) Provide a report of observations and recommendations regarding quality assurance to project staff and managers. Further elaboration on CIBER's Quality Assurance process will be defined in the Project Charter. The CIBER Project Manager is responsible for assuring project sponsors and _ stakeholders that project policies and processes related to CIBER's work performance are being applied and noncompliance are addressed. The following specific Quality Assurance Process policies apply: Quality Assurance review personnel: CIBER's Center for Project Performance (CPP) will coordinate and conduct project Quality Assurance reviews. The CPP may delegate this responsibility to a CIBER project management resource, not assigned to this project that is trained to conduct such reviews. Processes, products, and services to be reviewed: CIBER's standard Solution Set methodologies, and their outputs, are components of this Quality Assurance plan Approach for Producing Deliverables Deliverable Definition Document Specific content and responsibility for deliverables will be outlined in the "Deliverable Definition Document" (DDD) to be prepared prior to initiating activity on a Deliverable. The DDD will reflect the agreed to structure content and required approvals, as reflected in the following outline for their content: .r D©p riterlt Desc ption Deliverable Description A unique sequence number assigned to each Document Number payment deliverable in EXHIBIT B - PAYMENT _ SCHEDULE City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 82 of 418 im ,; ADD Content � � CIBER Deliverable Name CIBER Deployment CIBER Stage City Work Product Name Description A name assigned to each payment deliverable in EXHIBIT B - PAYMENT SCHEDULE. This may be renamed at the time of the DDD, if a clear trail of changes is maintained within the DDD. A reference to Phase IIA, 2B or 2C that will describe the deployment wave under which the deliverable is produced A reference to the Project Plan that identifies the Integrated Prototyping Methodology Stage (See Methodology Discussion in Exhibit A — Statement of Work, Methodology Discussion) during which the deliverable will be produced A reference to one of more of the requested work -products from the RFP Appendix N that will be incorporated into the content of this deliverable Description/Objective A description of the content of the deliverable, and activities that will be conducted to complete it Format: The type of documents that will be created (e.g., Microsoft Word, Visio, PowerPoint, etc.) Annotated Outline A list of outline sections and a brief narrative of the contents of the outline Acceptance Criteria A list of criteria that must be met in order for the city to accept the deliverable Required Approvals for City personnel that must approve the deliverable Acceptance Briefing Scope An inventory of the frequency of briefings required per DDD CIBER Role and City Assignment of which entity will lead the effort Role and which will participate. Entity leading the effort will be accountable for its delivery. CIBER Activities and Summary of responsibilities for activities will be City Activities provided in the Deliverable Definition Document and will be reviewed and updated prior to the commencement of each deliverable. Appendices: Templates Where applicable, this section will include blank and Instructions (as templates that will be used by the project team ' appropriate) as well as instructions on how to complete each section of the template 3 samples are included in Exhibit L: - Sample Deliverable Definition Documents (DDD). All sections of the DDD will be prepared, validated and updated if required prior to the commencement of each individual deliverable. City of Fort Worth / CIBER, Inc. Professional Services Agreement '" Page 83 of 418 Approach for incorporating feedback from appropriate parties for key deliverables According to the Briefing Scope defined in each DDD, a briefing(s) will be given to City approvers so that an understanding of the Deliverable is rendered. Briefing frequency will be confirmed in the initial briefing. Briefings may take place in regularly scheduled Project Sponsor Updates or more frequently if needed to facilitate progress of the Deliverable development. For expediency, DDD briefings will include multiple topics when possible. The purposes of the briefings are: • To solicit approver feedback as the deliverable is being developed rather than — after it has been completed whenever possible • To present alternative solutions and garner feedback from approvers when multiple options may be available for issues regarding business process redesign, internal controls, and organization change impacts • To socialize options and make recommendations to approvers related to business process redesign, internal controls and organization change impact and drive consensus • To keep approvers informed of the status and content of the associated deliverable as it develops Approval and Acceptance Process Acceptance Management. The Acceptance Management process ensures that deliverables collaboratively developed by the project team during the project are presented to City approvers for acceptance. Formal acceptance by City approvers indicates that the deliverable has been completed in accordance with this SOW. Acceptance criteria for Work Products shall be set forth in Deliverable Definition Documents (DDD), which shall be incorporated into the SOW by this reference. However, before submission, CIBER will ensure that written deliverables are reasonably free of grammatical errors, spelling errors, and references or terminology from other clients, and have passed an internal quality control review. Upon delivery of Work �- Products, the City approvers must inspect the Work Products for conformance with DDD specifications and Acceptance Criteria. The CIBER Project Manager or his or her designee is responsible for notifying and obtaining from City formal acceptance of the project team's deliverables in accordance with the specific Acceptance Management process policies described below. For deliverable approval at the Assistant City Manager (ACM) Level, or Sponsor Level, it is the responsibility of the City Assistant Director- Financial Management to notify and or brief the respective parties as designated in the City Approver Chart to be finalized and incorporated into the Project Charter. Citv am)rover(s) for proiect deliverables and process terms: The City Approver Chart (as defined in the Project Charter) designates the City Project - Level-1, Sponsor Level-2 and Assistance City Manager (ACM) Level-3 approvers for each project deliverable. Team Leads and their respective Subject Matter Experts will City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 84 of 418 be empowered by the City's executives representing their respective business operations to make decisions supporting the objectives of the project to be documented in the project team's Work Products. Team Leads and their respective Subject Matter Experts will actively involve any respective levels of management or other Business Process Owners in decisions that span multiple business units or affect the operation of the City at -large. Project Level-1 Approvers will be empowered to approve deliverables containing decisions made by empowered team members. Deliverables will include documentation of decisions that have been made through the project's escalation process to higher -level City authority, as necessary. Deliverables and the approval process will not be used as the method of soliciting decisions. The Issue Management Process will be used to manage and resolve issues that require decisions by Business Process Owners or City executives. Approval/reiection turnaround timeframe: CIBER Project Manager, or designee, will provide 15 calendar days advance notice that a deliverable will be submitted for approval. City approver(s) will accept or reject deliverables according to the following schedule: Number of Eusir7ess Days for Review Approval Level Initial Revisions Submission If Not Previously If Previously Reviewed by this Reviewed by this level level Level 1 3 N/A 1 Level 2 3 Same as Initial 1 or as agreed to in writing for extensive changes Level 3 4 Same as Initial 1 or as agreed to in writing for extensive changes In the event the deliverable is rejected, the CIBER Project Manager or designee, will correct any factual errors, resolve any material issues, provide any appropriate updates based upon feedback provided and resubmit the deliverable to the City approver(s), who will accept or reject re -submitted deliverables according to the table above. City approvers acknowledge and accept that time is of the essence as it relates to the objectives set forth for the ERP implementation project. Failure to adhere to the review turnaround timeframes may result in designated successor project task schedule delays and may constitute a change of scope to be processed under the Project (Scope) Change Control Process of this SOW. City of Fort Worth / CIBER, Inc. _ Professional Services Agreement Page 85 of 4l 8 In order to maintain the overall fixed project schedule objective, the City may have to decrease scope or increase resource capacity to recover time lost caused by any delays. Course of action if an approver is unavailable or does not respond with a decision in the time specified: If a City approver does not accept or reject the deliverable within the scheduled timeframe in section b. above, and does not communicate a timeframe in which the deliverable will be reviewed, the deliverable review will proceed according to these steps: • The status of a deliverable review will be logged as 'Escalated' and tracked accordingly. • The Project Manager will document a deliverable as `Escalated' in the next Status Report. • The issue will be handled through the project's Issue Management process. • Work will progress to maintain the established project schedule, with the understanding that any work dependent upon a rejected deliverable is at risk of — re -work. The City may designate the approval of a specific deliverable as "Critical" providing reasonable justification in writing to the CIBER Project Manager in which case the project team will cease work on any project tasks dependent upon approval of that deliverable. Any impact to the established schedule directly related to the stoppage of work may, constitute a change of scope to be processed under the Project (Scope) Change Control Process of this _ SOW. • A scope change request may result if modifications to the deliverable or service are required and those modifications affect other project work, or work that proceeded at risk. Invoicing Process CIBER Project Manager shall submit invoices electronically, via email, or in hard copy to the City Project Manager. Invoices shall be submjtted no more frequently than on a bi-weekly basis for the approved amounts of each deliverable. Each deliverable shall be listed as separate line items on the invoice and include: • assigned number (DDD Number, Work -Product Number and Milestone reference from the Payment Schedule); • amount; • beginning and completion dates; and • brief description of deliverable including the Phase, Focus, and relevant Work Products Upon receipt of invoice, City Project Manager shall: • identify invoice as "original" and the date of receipt shall be recorded on the R invoice; City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 86 of 418 • verify that the Deliverable Acceptance form has been approved in accordance with the terms and conditions of this Contract; • confirm invoiced amount is in accordance with the Deliverable; • attached approved Deliverable Acceptance form to the invoice; and • submit the invoice for payment; and notify CIBER Project Manager via email Approach to Decision Making Any large project will require hundreds or thousands of decisions over the course of its lifetime. Some decisions will require escalation through the issue or scope management processes, and others simply need to be made, documented and acted on. During the Project Charter, CIBER and the City will agree to and document the decision making process to include the following: • Types of decisions • Approach to decision making • Who approves which type of decision • How decisions will be documented and communicated Approach for Managing Custom Development The following section discusses the approach for managing custom development. Once the fit/gap has been completed and the proposed lists of reports, interfaces, conversions and extensions have been identified, CIBER will estimate the level of effort for CIBER and City resources and assign a cost to each development object corresponding to the CIBER effort. This cost will include the effort necessary to: 1) complete the technical specification; 2) create the development object; 3) conduct a technical unit test; 4) complete the technical documentation and 5) either conduct a knowledge transfer hand-off/walk-through of the object to a designated City technical team member for knowledge transfer, or develop a knowledge transfer plan for execution at a later date. • Development items for which CIBER has responded that RFP software requirements are standard functionality will be provided at no cost to the City, except where further elaboration of the requirement by the City materially affects CIBER's reasonable interpretation of the requirement. The development item would be subject to the Scope Change Control Process. • After the estimates are complete, the City will approve the final list of development objects that will be provided. • For development objects that are less than 240 hours, CIBER will invoice completed items that have been handed -off on a bi-weekly basis. • For development objects that are more than 240 hours, CIBER will invoice amounts agreed to as assigned CIBER costs at the following milestones and percentages: • Completion of technical specification — 40 percent • Completion of program development and successful unit test — 40 percent City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 87 of 418 • Completion of knowledge transfer (or development of a knowledge transfer plan) — 20 percent Business Process Redesign Approach The implementation team will develop City-wide standard processes, supported by the selected applications/systems. In the event a City department has sound business reasons for maintaining any existing process(es) or has a unique operational need for any variation, the supported business justification will be documented and managed as part of the implementation. Overall objectives of the Business Process Redesign (BPR) approach include: • Adapting existing City business processes to delivered software functionality; `^ • Using the software to increase process efficiency by eliminating work steps and redundant approvals; • Using the software to improve consistent enforcement of internal controls;; • Shifting focus from transactional/administrative tasks to more strategic, value- added activities. The Business Process Redesign approach used by the implementation team during the project will follow a step-by-step process that includes the following: • Identify and validate the inherent sub -processes associated with the following business process areas: o Financial Accounting o Month End Close o Year End Close o Program Management o Capital Projects Management �- o Order to Cash o Procure to Pay- In Phase IIA, the sub -processes will consist of all of the functions, e.g. chart of accounts updates, budget checking, pre- encumbrance/encumbrance creation and liquidation, vendor, and vouchers, identified and agreed upon in the detailed design of the BuySpeed Online — PeopleSoft interface, including the reversal transactions. In addition, the Business Process Redesign approach for Procure to Pay must include those points where the procurement and inventory processes provide input and/or output to the applicable sub- processes of the other business process areas. As part of Phase IIC — Procurement and Inventory Option, Ciber will include as part of the effort the redesign of the entire Procure to Pay process. • Document using process flow diagrams and related business process description templates the high level processes and the sub -processes; T City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 88 of 418 • Identify and document business requirements during Fit / Gap work sessions that ., are structured around the business process and sub -processes and captured in the traceability matrix; • Analyze business requirements and processes against standard functionality of the software and leading practices; • Determine gaps between standard software functionality and requirements of the department(s), assess options and choose best alternative to be implemented; • Document the redesigned business processes based upon the identified gaps, design decisions and modifications; and • Refine redesigned business processes and sub -process as necessary. Business process redesign methodology will address the following: • What the organization does • How the organization does it Who in the organization does it • Where it occurs including systems and interfaces (for systems NOT being replaced) • The sequence in which it is done • The rules that are followed • Policies, regulations and legal requirements are identified and followed • What business requirements must be considered • Interdepartmental dependencies • The results it obtains As a starting point, the business process redesign methodology will focus on the high- level business processes as identified below: Mm un_Uon High Level Builne ts, ro es; ,;; Financials Financial Accounting Month End Close Year End Close Manage Programs Manage Capital Projects Order to Cash Supply Chain Procure to Pay- In Phase IIA, CIBER may identify areas for improvement in the existing procure to pay process. For those improvements opportunities occurring within the City's BuySpeed Online solution, the City will be responsible for delivering those changes that it chooses to implement. As part of Phase IIC — Procurement and Inventory Option, CIBER includes the redesign of the complete end to end procure to pay process. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 89 of 418 As part of the validation process, the team will identify the sub processes that exist within each of the high level process groups. Below is an example: r■ Receive Proceeds Record Bond Issuance Costs Amortize Bond Issuance Costs (See Periodic Processes) Issue Capital Project Requests for Proposals (with Purchasing) Evaluate Bids (with Purchasing) Manage Contracted Award Contract (with Purchasing) Capital Projects I Monitor Compliance Pay Vendors (with Purchasing) Post Construction in Progress (See Periodic Processes) Complete Project Create Asset Develop Project Plan Create Project Budget Manage Capital Project Create Cost Collector Work Efforts Perform Work Procure Goods and/or Services (See Purchasing) Record Time Worked (See Time Entry) Complete Status Reports Monitor Project Budget Post Construction in Progress (See Periodic Processes) Complete Project Create Asset The implementation team will continue the process with a series of facilitated workshops designed to discover the requirements that support the business process. The workshops will also provide opportunities to identify process improvements in the existing functional areas. In a collaborative manner, the team will review current business practices and explore opportunities for process innovations that could include process standardization, elimination of paper forms and approvals, improved operational lag times and the elimination of unnecessary steps and approvals. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 90 of 418 Workshop participants will consist of the core project team, subject matter experts from the City Departments as needed, technical staff and management from the various lines of business as needed. Participants will attend work sessions designed to identify core City business and design requirements. As the data is collected, the team continues to build out the process using a traceability matrix. As each step of the business process redesign effort is completed by the team, the resulting requirements are documented in the matrix. The goal will be to define consistent, City-wide business processes and the associated requirements that serve as the basis for design of the system that will support the processes. The team will confirm department specific requirements and manage exceptions during the implementation. Impact Statements A goal of organizational impact analysis is to identify and document impacts caused by business process and system changes. The result of this effort is a plan that addresses each impact with: • Business Process Maps and Narrative that identify the impact points and describes the impact; • Communication required to create awareness of the changes that the business process redesign effort will generate; and • Training to develop the skills to perform the process. For Phase II, the organizational impacts are collected by function (Finance, Procurement, and Budget) and business process. The impacts collected typically include: • Business Functions • To -Be Business Process including identified Roles • Processing Schedule Change • Job Function Impact • Skill Requirements Change • Labor Contract Impacts • Policy Impacts • New Data available online or in reports • Unique Department Organizational Impacts City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 91 of 418 The organizational impacts described above as related to Procurement are included here to define the additional organizational impact scope that will be included in Phase IIC — Procurement and Inventory Option. Approach related to Testing of Phase /Applications and Regression Testing in Phase // Per the "Module to Be Implemented" section, the following Phase I applications will be revisited to accommodate Phase II requirements: • Human Resources (for position budgeting and control and integration with Hyperion Budget Preparation functionality) " • Time and Labor (for job/project costing) • Payroll and Benefits Administration • Any other modules or functionality in production that are dependent on Chart of Accounts or ChartField decisions that may be impacted by redesign to the City's Financial Data Classification Structure, as potentially outlined in the Software Requirements The changes in configuration to these applications as a result of implementation of Phase II requirements will be successfully tested in accordance with testing plans and approaches designated for implementation of Phase II modules. Any additional testing of Phase I modules will be the responsibility of the City with the assistance from the CIBER HR/Payroll resource(s) assigned to the project. Any regression testing and problem resolution that is necessary between Phase IIA (Financials) and Phase IIC (Capital Projects) shall be the responsibility of CIBER with assistance from the appropriate City resources. Protect Tools Project Document Repository The project team will use CIBER's PMRx® Project site or mutually accepted, comparable alternative in the work approach and management process. This project site will be a web -based repository and collaboration space that will be used to track _ project progress, information, and artifacts, and to capture, track, and communicate the overall status of the project based on System Implementation Methodology described below. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 92 of 418 EJ Assumptions City approvers will make a good -faith effort to prioritize their work load to expedite their reviews in the shortest timeframe possible and not consume the maximum time allowed as a matter of convenience. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 93 of 418 EXHIBIT B - PAYMENT SCHEDULE The payment schedules that follow in Exhibits B.1-B.3 represent the fixed fee components of this Statement of Work. In addition to the work reflected in the payment schedules, this Statement of Work consists of an amount of up to $3,317,321 for technical development services to be invoiced in accordance with the terms and conditions reflected in the Approach to Managing Custom Development section of this agreement. Exhibit B.1 — Fixed Fee Deliverable Payment Schedule for Phase IIA The following table provides the fixed fee deliverable payment schedule for Phase IIA. Since several of the deliverables are of significant scope and cross multiple modules, larger deliverables may have been broken up into multiple milestones. In these cases the last column defines the basis by which the deliverables will be sub -divided for payment purposes. Work- Work -product = t DDD, , Deliverable Name. "'Milestone Product Number 1 Num 1 Project Charter DDD-01 Project Charter 2 Project Work Plan DDD-02 Project Work Plan Narrative and MS Project Work Plan 3 Scope Change DDD-01 Project Charter Management Process and Tools 4 Issue Management DDD-03 Risk & Issue Process and Tools Management Plan 5 Risk Management DDD-03 Risk & Issue Process and Tools Management Plan 6 Quality Management DDD-04 Quality Assurance Tools and procedures Plan 7 Configuration DDD-05 Configuration Plan management tools and procedures 8 Status Reports DDD-06 Status Report Template City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 94 of 418 Milestone'' Milestone Final go,Retainage Total Retainage Total Less 2 3 Milestone 38,680 38,680 3,867.98 34,812 63,033 63,033 6,303 56,730 38,680 38,680 3,868 34,812 19,340 19,340 1,934 17,406 19,340 19,340 1,934 17,406 77,360 77,360 7,736 69,624 77,360 77,360 7,736 69,624 0 0 0 0 1 t I l w l l i j F II l t Work- ",,'Work -product DDD � DeIIverable me ; Milsstone Mipstano I.Rroduct . P►umber :a 1 2 Nur►� - ,,, 9 Testing Strategy DDD-07 Testing Plan 10 Test Plan DDD-07 Testing Plan 11 Project Team Training DDD-08 Implementation Team Training 12 Technical Infrastructure DDD-09 Technical Roadmap Plan 13 Sand Box Environment DDD-11 Instance Management Plan 14 Conversion Strategy DDD-12 Conversion Plan 15 Interface Strategy DDD-13 Interface Plan 16 Enhancement Strategy DDD-14 Customization Plan 17 Cultural Change DDD-14 Change Management Management Strategy Plan 18 Communications Strategy DDD-15 Communication Plan 19 Communications Plan DDD-15 Communication Plan 20 Training Strategy DDD-19 Training Plan 21 Knowledge Transfer DDD-20 Knowledge Transfer Strategy Plan 22 Application Security DDD-25 Security Plan Strategy 23 Control Review Strategy DDD-24 Internal Control Framework 24 Risk Assessment and DDD-03 Risk & Issue Plan Management Plan 25 Internal Control DDD-24 Internal Control Framework for Finance Framework and Procurement Functions 26 Updated Project Work DDD-02 Project Work Plan Plan and 27 Status Reports DDD-06 Status Report Template City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 95 of 418 Milestone :; Final Total Retainage Total'.Less 3 Milestone J , Retainage 38,680 38,680 3,868 34,812 94,544 94,544 9,454 85,090 38,680 38,680 3,868 34,812 38,680 38,680 3,868 34,812 15,758 15,758 1,576 14,182 31,516 31,516 3,152 28,364 31,516 31,516 3,152 28,364 31,516 31,516 3,152 28,364 77,360 77,360 7,736 69,624 38,680 38,680 3,868 34,812 94,549 94,549 9,455 85,094 18,007 18,007 1,801 16,206 31,516 31,516 3,152 28,364 31,516 31,516 3,152 28,364 38,680 38,680 3,868 34,812 30,886 30,886 3,089 27,797 232,081 232,081 23,208 208,873 0 0 0 0 0 0 0 01 work a+vok product DDA., Deiilreclbl�.Nar!?e Milestone Milestone. Milestone Final Total Retains a g Total Less Product Number ,,, ;,,,. , Qr 9 2 3 Milestone Retainage Nu[r1 28 Development Object List DDD- Finalized list of 9,003 9,003 900 8,103 and Unit Test Plan 13, objects within DDD- Conversion Plan, 14, Interface Plan, DDD-15 Customization Plan 29 Documented Business DDD-18 Business Process "To 35,342 35,342 35,342 35,342 141,368 14,137 127,231 Process Designs Be" maps 30 Prototyping Sessions DDD-16 Prototyping Plan 31,516 31,516 3,152 28,364 31 Documented Fit/Gap DDD-17 Fit/Gap Analysis 22,603 22,603 22,603 22,603 90,410 9,041 81,369 Analysis Report 32 Configuration and Unit DDD-30 Core Table Setup 36,017 36,017 3,602 32,415 Test Plan 33 Analysis of Reporting DDD-17 Fit/Gap Analysis 28,525 28,525 28,525 28,525 114,099 11,410 102,689 Requirements Report 34 Functional Specifications DDD-22 Functional and 133,939 133,939 133,939 133,939 535,756 53,576 482,180 for Design of Interfaces, Technical Conversions, and Specifications Enhancements 35 Technical Architecture DDD-09 Technical Roadmap 31,516 31,516 3,152 28,364 Design 36 Independent Validation DDD-10 QA of Technical 31,516 31,516 3,152 28,364 and Verification Review - Architecture Technical Architecture Design 37 Demo Environment DDD-11 Instance 19,340 19,340 1,934 17,406 Management Plan 38 Prototyping Environment DDD-11 Instance 15,758 15,758 1,576 14,182 Management Plan 39 "Gold" Configuration DDD-11 Instance 9,003 9,003 900 8,103 Environment Management Plan 40 Development Environment DDD-11 Instance 15,758 15,758 1,576 14,182 Management Plan 41 Conversion Plan DDD-12 Conversion Plan 36,013 36,013 3,601 32,412 42 Interface Plan DDD-13 Interface Plan 36,013 36,013 3,601 32,412 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 96 of 418 W>c rk " W k-product DDa pOl veraE�lOzVme ' Ml a nne Product Nunn M 43 Technical Specifications DDD-22 Functional and for Design of Interfaces, Technical Conversions, and Specifications Enhancements 44 Cultural Change DDD-26 Resistance Management Plan Management Plan (CCMP) 45 Communication Plan DDD-15 Communication Plan Content 46 Change Readiness DDD-27 Change Readiness Assessment Assessment 47 Organizational Analysis DDD-27 Change Readiness for Finance and Assessment Procurement Functions 48 Organizational Alignment DDD-27 Change Readiness Workshops Assessment 49 Business Process Change DDD-28 Workforce Transition Impact Assessment Plan 50 Workforce Transition Plan DDD-28 Workforce Transition Plan 51 Role Based Updates to DDD-28 Workforce Transition Job Descriptions and Plan Knowledge, Skills and Abilities (KSA's) 52 End -User Needs DDD-19 Training Plan Assessment 53 Training Plan DDD-19 Training Plan 54 Training Curriculum DDD-19 Training Plan 55 Knowledge Transfer Plan DDD-20 Knowledge Transfer Plan 56 Application Security Plan DDD-25 Security Plan 57 Process Design Review DDD-18 Business Process "To Be" maps 58 Review of Relevant DDD-22 Functional and Functional Specifications Technical Specifications City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 97 of 418 Milestone Milestone Final Total Retainage Total Less 2 3 Milestone Retainage 0 0 0 0 44,123 44,123 4,412 39,711 15,758 15,758 1,576 14,182 25,209 25,209 2,521 22,688 157,583 157,583 15,758 141,825 18,007 18,007 1,801 16,206 27,010 27,010 2,701 24,309 27,010 27,010 2,701 24,309 38,943 38,943 3,894 35,049 31,516 31,516 3,152 28,364 77,886 77,886 7,789 70,097 89,350 89,350 8,935 80,415 63,033 63,033 6,303 56,730 54,020 54,020 5,402 48,618 18,007 18,007 1,801 16,206 67,948 67,948 6,795 61,153 V11ark Wyk lxo�luct peliverable dame Piodbcfi b+ar =� alum ANP 59 Workflow Design Reviews DDD-22 Functional and Technical Specifications 60 Updated Project Work DDD-02 Project Work Plan Plan and 61 Status Reports DDD-06 Status Report Template 62 Integration Test Plan DDD-07 Testing Plan 63 Initial Software DDD-30 Core Table Setup Configuration Documentation 64 Final Software DDD-30 Core Table Setup Configuration Documentation 65 Documented Unit Test DDD-07 Testing Plan Scripts (CIBER sees as System Test Scripts) 66 Integration Test Scripts DDD-31 Integration Test Scripts 67 Knowledge Transfer DDD-21 Team Member Documentation Knowledge Transfer Evaluation 68 Cleansed Data for DDD-33 Converted Data for Conversion legacy Conversions 69 Load and Volume Test DDD-07 Testing Plan Plan and Templates 70 QA and Other Testing DDD-11 Instance Environments Management Plan 71 Workstation Deployment DDD-09 Technical Roadmap 72 Business Continuity Plan DDD-14 Technical Roadmap 73 Independent Validation DDD-10 QA of Technical and Verification Review - Architecture Pre -Production Installed Architecture City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 98 of 418 1 1 1 Milestone Milestone Milestone FlnaU Total Retainage Total Less 1 2 3 Milestone Retanage 67,948 67,948 6,795 61,153 0 0 0 0 0 0 0 0 18,007 18,007 1,801 16,206 123,183 123,183 123,183 123,183 492,733 49,273 443,460 33,974 33,974 33,974 33,974 135,894 13,589 122,305 18,007 18,007 18,007 18,007 72,028 7,203 64,825 29,207 29,207 29,207 29,207 116,830 11,683 105,147 38,943 38,943 3,894 35,049 0 0 0 0 76,042 76,042 7,604 68,438 29,783 29,783 2,978 26,805 76,042 76,042 7,604 68,438 59,568 59,568 5,957 53,611 64,407 64,407 6,441 57,966 1 1 # 1 l t I + P I I i II i I t I A 1 1 I I i 1 .1 1 ' 1 1 i I I 1 k A � Woik Wads product t?DQelliyerable Name `. Mite tone ,, Mllestone Milestone Flnal -, To#a1 Retatnge Total'Less t otl(t ., \ 2 3 Milestone- Retainage;. Num a 74 Technical Documentation DDD-22 Functional and 0 0 0 0 of Interfaces, Technical Conversions, Reports and Specifications Enhancements 75 Upgrade Checklist DDD-22 Functional and 45,379 45,379 4,538 40,841 Technical Specifications (summary of all Object Upgrade impacts) 76 Communication Plan DDD-15 Communication Plan 29,783 29,783 2,978 26,805 Content 77 Workforce Transition Plan DDD-28 Workforce Transition 119,134 119,134 11,913 107,221 Work -products Plan 78 Training Course Outlines DDD-19 Training Plan 37,229 37,229 37,229 37,229 148,917 14,892 134,025 79 Training Course Content DDD-29 Training Materials 113,448 113,448 113,448 113,448 453,794 45,379 408,415 and Database 80 Training Logistics DDD-19 Training Plan 45,379 45,379 4,538 40,841 81 Role Definitions DDD-25 Security Plan 101,921 101,921 10,192 91,729 82 Role Assignments to End DDD-25 Security Plan 83,394 83,394 8,339 75,055 Users 83 Unit Test Script Review DDD-07 Testing Plan 9,003 9,003 900 8,103 and Recommendations (CIBER sees as System Test Scripts) 84 Unit Test Results Review DDD-07 Testing Plan 9,003 9,003 900 8,103 and Recommendations (CIBER sees as System Test Results) 85 Integration Test Script DDD-31 Integration Test 29,783 29,783 2,978 26,805 Review and Scripts Recommendations 86 Integration Test Results DDD-31 Integration Test 22,690 22,690 2,269 20,421 Review and Scripts Recommendations City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 99 of 418 Work= Work -product, 0013 '" Deitverablq M1me M,i1040 one Milestone Milestone Final Total Retainage Total Less Product tlslumber . ! Z 3 Milestone Retainage NU y 87 Training Course Outline DDD-29 Training Materials 29,783 29,783 29,783 29,783 119,133 11,913 107,220 Review and Recommendations 88 Training Course Content DDD-29 Training Materials 22,690 22,690 22,690 22,690 90,758 9,076 81,682 Review and Recommendations 89 Updated Project Work DDD-02 Project Work Plan 0 0 0 0 Plan and Implementation Schedule 90 Status Reports DDD-06 Status Report 0 0 0 0 Template 91 Deployment Plan DDD-34 Cutover Plan 152,084 152,084 15,208 136,876 92 Update to Help Desk and DDD-35 Review & Update of 152,084 152,084 15,208 136,876 Support Procedures Competency Center Material 93 Documented Integration DDD-32 Integration Test 45,379 45,379 4,538 40,841 Test Results 94 User Acceptance Test DDD-07 Testing Plan 45,379 45,379 4,538 40,841 Plan 95 User Acceptance Test DDD-36 User Acceptance 45,379 45,379 45,379 45,379 181,516 18,152 163,364 Scripts Test Scripts 96 User Acceptance Test DDD-36 User Acceptance 34,034 34,034 34,034 34,034 136,137 13,614 122,523 Results Test Scripts 97 Final Production System DDD-34 Cutover Plan 152,084 152,084 15,208 136,876 98 Communication Plan DDD-15 Communication Plan 22,690 22,690 2,269 20,421 Content 99 Workforce Transition Plan DDD-28 Workforce Transition 45,379 45,379 4,538 40,841 Work -products Plan 100 Delivery of Power User DDD-39 Training Delivery 85,292 85,292 85,292 85,292 341,168 34,117 307,051 and End -User Courses 101 Deployment Plan Review DDD-34 Cutover Plan 38,021 38,021 3,802 34,219 and Recommendations 102 Help Desk Procedure DDD-35 Review & Update of 76,042 76,042 7,604 68,438 Review and Competency Center City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 100 of418 II I I I I i I I I i Recommendations Material 103 Internal Control DDD-34 Cutover Plan Framework Go -Live Assessment 104 Updated Project Work DDD-02 Project Work Plan Plan and Implementation Schedule 105 Project Closeout Final i DDD-37 Project Closeout and Report Lessons Learned 106 Status Reports DDD-06 Status Report Template 107 Manage Change Control DDD-38 Production Support Plan Execution 108 Communication Plan DDD-15 Communication Plan Content 109 Workforce Transition Plan DDD-28 Workforce Transition Work -products Plan City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 101 of 418 112,585 112,585 F;inai :. Total Retainage Total „Less Milestone..= Retainage 38,021 38,021 3,802 34,219 0 0 0 0 42,646 1 42,646 4,265 38,381 0 0 0 0 115,997 341,167 34,117 307,050 38,021 38,021 3,802 34,219 228,126 228,126 22,813.00 205,313 Totals 7,788,695 778,871 I 7,009,824 Exhibit 13.2 — Fixed Fee Deliverable Payment Schedule for Phase I113 The following table provides the fixed fee deliverable payment schedule for Phase 1113. Since the scope of Phase IIB is less than Phase 11A, none of these deliverables have been sub -divided for payment purposes. Work -products that will be updated from the prior phase, but which won't be included as payment deliverables are noted as "Update as necessary" in the Total Deliverable Amount Column. Total Total ' DDI1 Deliverable Less _.. Work rsaduct t�iar»ber xx. Deliverable Name.. Amount Retainage Retainage Project Work Plan Narrative and MS Project Work Plan DDD-02 Project Work Plan Project Team Training DDD-08 Implementation Team Training 9,881 988 8,893 Technical Infrastructure Plan DDD-09 Technical Roadmap Sand Box Environment DDD-11 Instance Management Plan Conversion Strategy DDD-12 Conversion Plan - - - Interface Strategy DDD-13 Interface Plan Enhancement Strategy DDD-14 Customization Plan - - Application Security Strategy DDD-25 Security Plan Control Review Strategy DDD-24 Internal Control Framework - - - 9,881 988 8,893 1 Internal Control Framework for Finance and Procurement DDD-24 Internal Control Framework Functions 59,287 5,929 53,358 Updated Project Work Plan and DDD-02 Project Work Plan 9,881 988 8,893 Status Reports DDD-06 Status Report Template Development Object List and Unit Test Plan DDD- Finalized list of objects within - - - 13, Conversion Plan, Interface Plan, 4,941 494 4,447 DDD- Customization Plan 14, DDD-15 Documented Business Process Designs DDD-18 Business Process "To Be" maps 49,406 4,941 44,465 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 102 of 418 I I 1 1 i, 1 1 0 1 1 ! 1 1 1 1 a 0 A l �l y ,r v' Ids' 3 Total Total gpi Deliverable Less Woikrouluct a: ° `Number.... Deliverable Name .. Amount ° Retainage .. Retai Wage Prototyping Sessions DDD-16 Prototyping Plan Documented Fit/Gap Analysis DDD-17 Fit/Gap Analysis Report 59,287 5,929 53,358 Configuration and Unit Test Plan DDD-30 Core Table Setup 19,762 1,976 17,786 Analysis of Reporting Requirements DDD-17 Fit/Gap Analysis Report 39,525 3,952 35,573 Functional Specifications for Design of Interfaces, DDD-22 Functional and Technical Conversions, and Enhancements Specifications 88,931 8,893 80,038 Technical Architecture Design DDD-09 Technical Roadmap Independent Validation and Verification Review - DDD-10 QA of Technical Architecture Technical Architecture Design - - - Demo Environment DDD-11 Instance Management Plan 4,941 494 4,447 Prototyping Environment DDD-11 Instance Management Plan 4,941 494 4,447 "Gold" Configuration Environment DDD-11 Instance Management Plan 4,941 494 4,447 Development Environment DDD-11 Instance Management Plan 4,941 494 4,447 Interface Plan DDD-13 Interface Plan 19,762 1,976 17,786 Technical Specifications for Design of Interfaces, DDD-22 Functional and Technical Conversions, and Enhancements Specifications - - - Cultural Change Management Plan (CCMP) DDD-26 Resistance Management Plan Communication Plan Content DDD-15 Communication Plan Change Readiness Assessment DDD-27 Change Readiness Assessment 13,833 1,383 12,450 Organizational Analysis for Finance and Procurement DDD-27 Change Readiness Assessment Functions - - - Organizational Alignment Workshops DDD-27 Change Readiness Assessment Business Process Change Impact Assessment DDD-28 Workforce Transition Plan City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 103 of 418 Workforce Transition Plan I DDD-28 Workforce Transition Plan Role Based Updates to Job Descriptions and Knowledge, DDD-28 Workforce Transition Plan Skills and Abilities (KSA's) End -User Needs Assessment DDD-19 Training Plan Training Plan DDD-19 Training Plan Training Curriculum I DDD-19 Training Plan Knowledge Transfer Plan DDD-20 Knowledge Transfer Plan Application Security Plan DDD-25 Security Plan Process Design Review DDD-18 Business Process "To Be" maps Review of Relevant Functional Specifications DDD-22 Functional and Technical Specifications Workflow Design Reviews DDD-22 Functional and Technical Specifications Updated Project Work Plan and DDD-02 Project Work Plan Status Reports DDD-06 Status Report Template Integration Test Plan DDD-07 Testing Plan Initial Software Configuration Documentation DDD-30 Core Table Setup Final Software Configuration Documentation DDD-30 Core Table Setup Documented Unit Test Scripts (GIBER sees as System DDD-07 Testing Plan Test Scripts) Integration Test Scripts DDD-31 Integration Test Scripts Knowledge Transfer Documentation I DDD-21 Team Member Knowledge Transfer Evaluation Total flelliviiAb e� k Y Less Amount Retainage Retainage 9,881 988 8,893 14,822 1,482 13,340 29,571 2,957 26,614 9,881 988 8,893 161,261 16,126 145,135 19,762 1,976 17,786 I 39,525 3,952 35,573 29,644 2,964 26,680 9,881 988 8,893 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 104 of 418 i t II I I I I i I 1 i I I 1 0 1 1 1 1 # 4 1 1 a , it I I r in f A a x 4 �� .41 f S 3 E Z :.,elivera6ie Name ...... . Cleansed Data for Conversion DDD-33 Converted Data for legacy Conversions Load and Volume Test Plan and Templates DDD-07 Testing Plan QA and Other Testing Environments DDD-11 Instance Management Plan Workstation Deployment DDD-09 Technical Roadmap Business Continuity Plan DDD-14 Technical Roadmap Independent Validation and Verification Review — Pre- DDD-10 QA of Technical Architecture Production Installed Architecture Technical Documentation of Interfaces, Conversions, DDD-22 Functional and Technical Reports and Enhancements Specifications Upgrade Checklist DDD-22 Functional and Technical Specifications (summary of all Object Upgrade impacts) Communication Plan Content DDD-15 Communication Plan Workforce Transition Plan Work -products DDD-28 Workforce Transition Plan Training Course Outlines DDD-19 Training Plan Training Course Content and Database DDD-29 Training Materials Training Logistics DDD-19 Training Plan Role Definitions DDD-25 Security Plan Role Assignments to End Users DDD-25 Security Plan Unit Test Script Review and Recommendations (CIBER DDD-07 Testing Plan sees as System Test Scripts) Unit Test Results Review and Recommendations (CIBER DDD-07 Testing Plan saes as System Test Results) Integration Test Script Review and Recommendations DDD-31 Integration Test Scripts City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 105 of418 TotaL Total liverable Less Amount Retainage" Retainage 19,762 1,976 17,786 9,881 988 8,893 4,941 494 4,447 9,881 988 8,893 98,812 9,881 88,931 9,881 988 8,893 13,833 1,383 12,450 4,941 494 4,447 s '3 n/l Tout Lotal '• 3 �ff � ? i3Wl `'sj t�� 0f1Yerab'<R 3� ;, ess . jY ,. * . � , ., ,. 3 ;, ,,Work-producs y., y ,, ,, Nurrib r.. „ ,. ... QeiPverable Nari e A autlt Retainage;.' Retainage Integration Test Results Review and Recommendations DDD-31 Integration Test Scripts Training Course Outline Review and Recommendations DDD-29 Training Materials Training Course Content Review and Recommendations DDD-29 Training Materials Updated Project Work Plan and Implementation Schedule DDD-02 Project Work Plan - - Status Reports DDD-06 Status Report Template Deployment Plan DDD-34 Cutover Plan - 19,762 1,976 17,786 Update to Help Desk and Support Procedures DDD-35 Review & Update of Competency Center Material - - - Documented Integration Test DDD-32 Integration Test Results 9,881 988 8,893 User Acceptance Test Plan DDD-07 Testing Plan User Acceptance Test Scripts DDD-36 User Acceptance Test Scripts User Acceptance Test Results DDD-36 User Acceptance Test Scripts 29,644 2,964 26,680 Final Production System DDD-34 Cutover Plan 19,762 1,976 17,786 Communication Plan Content DDD-15 Communication Plan Workforce Transition Plan Work -products DDD-28 Workforce Transition Plan Delivery of Power User and End -User Courses DDD-39 Training Delivery 39,525 3,952 35,573 Deployment Plan Review and Recommendations DDD-34 Cutover Plan Help Desk Procedure Review and Recommendations DDD-35 Review & Update of Competency Center Material - - - Internal Control Framework Go -Live Assessment DDD-34 Cutover Plan City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 106 of 418 41. I f t t I A I A I b 1 1 1 1 1" 1 1 # City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 107 of 418 Exhibit 13.3 — Fixed Fee Deliverable Payment Schedule for Phase IIC The following tables provide the fixed fee deliverable payment schedule for Phase IIC- Capital Projects and Phase IIC — Procurement and Inventory Option. Work -products that will be updated from the prior phase, but which won't be included as payment deliverables are noted as "Update as necessary" in the Total Deliverable Amount Column. Phase IIC — Capital Projects Deliverable Payment Schedule a Total Total DDD Deliverable: Less ri Num 1Ndtk-prc dint ';, ,.r Numbers.. Deliverable Name _ _ Amount Retainage Retainage 2 Project Work Plan Narrative and MS Project Work DDD-02 Project Work Plan - - - Plan 11 Project Team Training DDD-08 Implementation Team Training 13,786 12,407 1,379 12 Technical Infrastructure Plan DDD-09 Technical Roadmap - - - 13 Sand Box Environment DDD-11 Instance Management Plan - - - 14 Conversion Strategy DDD-12 Conversion Plan - - - 15 Interface Strategy DDD-13 Interface Plan - - - 16 Enhancement Strategy DDD-14 Customization Plan - - - 22 Application Security Strategy DDD-25 Security Plan - - - 23 Control Review Strategy DDD-24 Internal Control Framework 13,786 12,407 1,379 25 Internal Control Framework for Finance and DDD-24 Internal Control Framework 82,720 74,448 Procurement Functions 8,272 26 Updated Project Work Plan and DDD-02 Project Work Plan 13,786 12,407 1,379 27 Status Reports DDD-06 Status Report Template - - - 28 Development Object List and Unit Test Plan DDD- Finalized list of objects within 6,893 6,204 13, Conversion Plan, Interface 689 DDD- Plan, Customization Plan 14, DDD-15 City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 108 of 418 I F, II II I II i I 1 I I 'I A I I j 4 ....., Total_ Total DQD Deliverable Less , Num product, :" Number Deliverable Name .." . Amount Retainage Retainage 29 Documented Business Process Designs DDD-18 Business Process "To Be" 68,934 62,041 maps 6,893 30 Prototyping Sessions DDD-16 Prototyping Plan - - - 31 Documented Fit/Gap Analysis DDD-17 Fit/Gap Analysis Report 82,720 74,448 8,272 32 Configuration and Unit Test Plan DDD-30 Core Table Setup 27,574 24,817 2,757 33 Analysis of Reporting Requirements DDD-17 Fit/Gap Analysis Report 55,146 49,631 5,515 34 Functional Specifications for Design of Interfaces, DDD-22 Functional and Technical 124,080 Conversions, and Enhancements Specifications 12,408 111,672 35 Technical Architecture Design DDD-09 Technical Roadmap - - - 36 Independent Validation and Verification Review - DDD-10 QA of Technical Architecture - - - Technical Architecture Design 37 Demo Environment DDD-11 Instance Management Plan 6,893 6,204 689 38 Prototyping Environment DDD-11 Instance Management Plan 6,893 6,204 689 39 "Gold" Configuration Environment DDD-11 Instance Management Plan 6,893 6,204 689 40 Development Environment DDD-11 Instance Management Plan 6,893 6,204 689 42 Interface Plan DDD-13 Interface Plan 27,574 24,817 2,757 43 Technical Specifications for Design of Interfaces, DDD-22 Functional and Technical - - - Conversions, and Enhancements Specifications 44 Cultural Change Management Plan (CCMP) DDD-26 Resistance Management Plan - - - 45 Communication Plan Content DDD-15 Communication Plan - - - City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 109 of 418 Total Total Deliverable Less Num Work-pvoduct Number deliverable Name Amount Retainage Retainage 46 Change Readiness Assessment DDD-27 Change Readiness 19,301 17,371 Assessment 1,930 47 Organizational Analysis for Finance and DDD-27 Change Readiness - - - Procurement Functions Assessment 48 Organizational Alignment Workshops DDD-27 Change Readiness - - - Assessment 49 Business Process Change Impact Assessment DDD-28 Workforce Transition Plan - - - 50 Workforce Transition Plan DDD-28 Workforce Transition Plan - - - 51 Role Based Updates to Job Descriptions and DDD-28 Workforce Transition Plan 13,786 12,407 Knowledge, Skills and Abilities (KSA's) 1,379 52 End -User Needs Assessment DDD-19 Training Plan - - - 53 Training Plan DDD-19 Training Plan - - - 54 Training Curriculum DDD-19 Training Plan 20,681 18,613 2,068 55 Knowledge Transfer Plan DOD-20 Knowledge Transfer Plan - - - 56 Application Security Plan DDD-25 Security Plan 41,360 37,224 4,136 57 Process Design Review DDD-18 Business Process "To Be" 13,786 12,407 maps 1,379 58 Review of Relevant Functional Specifications DDD-22 Functional and Technical - - - Specifications 59 Workflow Design Reviews DDD-22 Functional and Technical - - - Specifications 60 Updated Project Work Plan and DDD-02 Project Work Plan - - - 61 Status Reports DDD-06 Status Report Template - - - 62 Integration Test Plan DDD-07 Testing Plan - - - 63 Initial Software Configuration Documentation DDD-30 Core Table Setup 224,999 22,500 202,499 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 110 of 418 1 4 1 1 1 1 1 1 1 � I J 1 Total Total DDD M Deliverable Less Num Work -product Number- -. .Deliverable Name Amount Retainage Retainage 64 Final Software Configuration Documentation DDD-30 Core Table Setup 27,574 24,817 2,757 65 Documented Unit Test Scripts (CIBER sees as DDD-07 Testing Plan 55,146 49,631 System Test Scripts) 5,515 66 Integration Test Scripts DDD-31 Integration Test Scripts 41,360 37,224 4,136 67 Knowledge Transfer Documentation DDD-21 Team Member Knowledge 13,786 12,407 Transfer Evaluation 1,379 68 Cleansed Data for Conversion DDD-33 Converted Data for legacy 27,574 24,817 Conversions 2,757 69 Load and Volume Test Plan and Templates DDD-07 Testing Plan 13,786 12,407 1,379 70 QA and Other Testing Environments DDD-11 Instance Management Plan 6,893 6,204 689 71 Workstation Deployment DDD-09 Technical Roadmap - - - 72 Business Continuity Plan DDD-14 Technical Roadmap - - - 73 Independent Validation and Verification Review — DDD-10 QA of Technical Architecture - - - Pre -Production Installed Architecture 74 Technical Documentation of Interfaces, DDD-22 Functional and Technical - - - Conversions, Reports and Enhancements Specifications 75 Upgrade Checklist DDD-22 Functional and Technical 13,786 12,407 Specifications (summary of all 1,379 Object Upgrade impacts) 76 Communication Plan Content DDD-15 Communication Plan - - - 77 Workforce Transition Plan Work -products DDD-28 Workforce Transition Plan - - - 78 Training Course Outlines DDD-19 Training Plan - - - 79 Training Course Content and Database DDD-29 Training Materials 137,866 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page II I of418 Total Total. CIDD Deliverable Del Less Num Woric:product Number DeliverabieName . Amount Retainage Retainage 13,787 124,079 80 Training Logistics DDD-19 Training Plan 13,786 12,407 1,379 81 Role Definitions DDD-25 Security Plan - - - 82 Role Assignments to End Users DDD-25 Security Plan 19,301 17,371 1,930 83 Unit Test Script Review and Recommendations DDD-07 Testing Plan 6,893 6,204 (CIBER sees as System Test Scripts) 689 84 Unit Test Results Review and Recommendations DDD-07 Testing Plan - - - (CIBER sees as System Test Results) 85 Integration Test Script Review and DDD-31 Integration Test Scripts - - - Recommendations 86 Integration Test Results Review and DDD-31 Integration Test Scripts - - - Recommendations 87 Training Course Outline Review and DDD-29 Training Materials - - - Recommendations 88 Training Course Content Review and DDD-29 Training Materials - - - Recommendations 89 Updated Project Work Plan and Implementation DDD-02 Project Work Plan - - - Schedule 90 Status Reports DDD-06 Status Report Template - - - 91 Deployment Plan DDD-34 Cutover Plan 27,574 24,817 2,757 92 Update to Help Desk and Support Procedures DDD-35 Review & Update of - - - Competency Center Material 93 Documented Integration Test DDD-32 Integration Test Results 13,786 12,407 1,379 94 User Acceptance Test Plan DDD-07 Testing Plan - - - City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 112 of418 II II li 1 ,1 1 1 1 1 1 4 I I I I I I I II J M "r, TU Totaf Total DOD , Deliverable' Less Nuts Work -product Number- '. Deliverable` Name Amount Retainage Retainage 95 User Acceptance Test Scripts DDD-36 User Acceptance Test Scripts - - - 96 User Acceptance Test Results DDD-36 User Acceptance Test Scripts 41,360 37,224 4,136 97 Final Production System DDD-34 Cutover Plan 27,574 24,817 2,757 98 Communication Plan Content DDD-15 Communication Plan - - - 99 Workforce Transition Plan Work -products DDD-28 Workforce Transition Plan - - - 100 Delivery of Power User and End -User Courses DDD-39 Training Delivery 55,146 49,631 101 Deployment Plan Review and Recommendations DDD-34 Cutover Plan 102 Help Desk Procedure Review and DDD-35 Review & Update of Recommendations Competency Center Material 103 Internal Control Framework Go -Live Assessment DDD-34 Cutover Plan 104 Updated Project Work Plan and Implementation DDD-02 Project Work Plan Schedule 105 Project Closeout Final Report DDD-37 Project Closeout and Lessons Learned 106 Status Reports DDD-06 Status Report Template 107 Manage Change Control DDD-38 Production Support Plan Execution 108 Communication Plan Content DDD-15 Communication Plan 109 Workforce Transition Plan Work -products DDD-28 Workforce Transition Plan 110 Phase IIA Year End Support DDD-38 Production Support Plan Execution (Phase IIA) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 113 of 418 5,515 6,893 6,204 689 55,146 49,631 5,515 318,000 31,800 286,200 1,801,718 180,172 1,621, 546 Phase IIC — Procurement and Inventory (Option) Deliverable Payment Schedule Total Total DDD Deliverable Less Num Work -product � � �"Number ' Deliverable Name Amount . Retainage Retainage_ 2 Project Work Plan Narrative and MS Project Work DDD-02 Project Work Plan - - - Plan 11 Project Team Training DDD-08 Implementation Team Training 23,716 21,344 2,372 12 Technical Infrastructure Plan DDD-09 Technical Roadmap - - - 13 Sand Box Environment DDD-11 Instance Management Plan - - - 14 Conversion Strategy DDD-12 Conversion Plan - - - 15 Interface Strategy DDD-13 Interface Plan - - - 16 Enhancement Strategy DDD-14 Customization Plan - - - 22 Application Security Strategy DDD-25 Security Plan - - - 23 Control Review Strategy DDD-24 Internal Control Framework 23,716 21,344 2,372 25 Internal Control Framework for Finance and DDD-24 Internal Control Framework 142,300 Procurement Functions 14,230 128,070 26 Updated Project Work Plan and DDD-02 Project Work Plan 23,716 21,344 2,372 27 Status Reports DDD-06 Status Report Template - - - 28 Development Object List and Unit Test Plan DDD- Finalized list of objects within 11,858 10,672 13, Conversion Plan, Interface 1,186 DDD- Plan, Customization Plan 14, DDD-15 29 Documented Business Process Designs DDD-18 Business Process "To Be" 118,584 maps 11,858 106,726 30 Prototyping Sessions DDD-16 Prototyping Plan - - - 31 Documented Fit/Gap Analysis DDD-17 Fit/Gap Analysis Report 142,300 14,230 128,070 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 114 of 418 >I I 1 1 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 I :A I I I I I 1 3 1 1 1 1 . 1 .0 1 1 1 Total Total y. DDD .: Deliverable, Less Num Work -product Number �Deliwerable Name Amount Retainage Retainage 32 Configuration and Unit Test Plan DDD-30 Core Table Setup 47,434 42,691 4,743 33 Analysis of Reporting Requirements DDD-17 Fit/Gap Analysis Report 94,866 85,379 9,487 34 Functional Specifications for Design of Interfaces, DDD-22 Functional and Technical 213,450 Conversions, and Enhancements Specifications 21,345 192,105 35 Technical Architecture Design DDD-09 Technical Roadmap - - - 36 Independent Validation and Verification Review - DDD-10 QA of Technical Architecture - - - Technical Architecture Design 37 Demo Environment DDD-11 Instance Management Plan 11,858 10,672 1,186 38 Prototyping Environment DDD-11 Instance Management Plan 11,858 I 10,672 1,186 39 "Gold" Configuration Environment DDD-11 Instance Management Plan 11,858 10,672 1,186 40 Development Environment DDD-11 Instance Management Plan 11,858 I 10,672 1,186 42 Interface Plan DDD-13 Interface Plan 47,434 I I 42,691 4,743 43 Technical Specifications for Design of Interfaces, DDD-22 Functional and Technical Conversions, and Enhancements Specifications 44 Cultural Change Management Plan (CCMP) DDD-26 Resistance Management Plan - I - 45 Communication Plan Content DDD-15 Communication Plan -- 46 Change Readiness Assessment DDD-27 Change Readiness 33,202 I I 29,882 Assessment 3,320 47 Organizational Analysis for Finance and DDD-27 Change Readiness Procurement Functions Assessment 48 Organizational Alignment Workshops DDD-27 Change Readiness Assessment 49 Business Process Change Impact Assessment DDD-28 Workforce Transition Plan - I - 50 Workforce Transition Plan DDD-28 Workforce Transition Plan - City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 115 of 418 - Total Total . DDD Deliverable.. Less Num Work product Number ;. Deliverable Name Amount Retainage Retainage 51 Role Based Updates to Job Descriptions and DDD-28 Workforce Transition Plan 23,716 21,344 Knowledge, Skills and Abilities (KSA's) 2,372 52 End -User Needs Assessment DDD-19 Training Plan - - - 53 Training Plan DDD-19 Training Plan - - - 54 Training Curriculum DDD-19 Training Plan 35,576 32,018 3,558 55 Knowledge Transfer Plan DDD-20 Knowledge Transfer Plan - - - 56 Application Security Plan DDD-25 Security Plan 71,150 64,035 7,115 57 Process Design Review DDD-18 Business Process "To Be" 23,716 21,344 maps 2,372 58 Review of Relevant Functional Specifications DDD-22 Functional and Technical - - - Specifications 59 Workflow Design Reviews DDD-22 Functional and Technical - - - Specifications 60 Updated Project Work Plan and DDD-02 Project Work Plan - - - 61 Status Reports DDD-06 Status Report Template - - - 62 Integration Test Plan DDD-07 Testing Plan - - - 63 Initial Software Configuration Documentation DDD-30 Core Table Setup 387,056 38,706 348,350 64 Final Software Configuration Documentation DDD-30 Core Table Setup 47,434 42,691 4,743 65 Documented Unit Test Scripts (CIBER sees as DDD-07 Testing Plan 94,866 85,379 System Test Scripts) 9,487 66 Integration Test Scripts DDD-31 Integration Test Scripts 71,150 64,035 7,115 67 Knowledge Transfer Documentation DDD-21 Team Member Knowledge 23,716 21,344 Transfer Evaluation 2,372 68 Cleansed Data for Conversion DDD-33 Converted Data for legacy 47,434 42,691 Conversions 4,743 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 116 of 418 II I I I II I I I I I I _ I Ik Ai 1 a I I I Total Total = DDD . ; Deliverable Less Nur Work -product,, _ Number Deliverable Name' Amoiaht.': '.Retainage Retainage; 69 Load and Volume Test Plan and Templates DDD-07 Testing Plan 23,716 21,344 2,372 70 QA and Other Testing Environments DDD-11 Instance Management Plan 11,858 10,672 1,186 71 Workstation Deployment DDD-09 Technical Roadmap - - - 72 Business Continuity Plan DDD-14 Technical Roadmap - - - 73 Independent Validation and Verification Review — DDD-10 QA of Technical Architecture - - - Pre -Production Installed Architecture 74 Technical Documentation of Interfaces, DDD-22 Functional and Technical - - - Conversions, Reports and Enhancements Specifications 75 Upgrade Checklist DDD-22 Functional and Technical 23,716 21,344 Specifications (summary of all 2,372 Object Upgrade impacts) 76 Communication Plan Content DDD-15 Communication Plan - - - 77 Workforce Transition Plan Work -products DDD-28 Workforce Transition Plan - - - 78 Training Course Outlines DDD-19 Training Plan - - - 79 Training Course Content and Database DDD-29 Training Materials 237,166 23,717 213,449 80 Training Logistics DDD-19 Training Plan 23,716 21,344 2,372 81 Role Definitions DDD-25 Security Plan - - I - 82 Role Assignments to End Users DDD-25 Security Plan 33,202 I 29,882 3,320 83 Unit Test Script Review and Recommendations DDD-07 Testing Plan 11,858 10,672 (CIBER sees as System Test Scripts) 1,186 84 Unit Test Results Review and Recommendations DDD-07 Testing Plan - - - (CIBER sees as System Test Results) 85 Integration Test Script Review and DDD-31 Integration Test Scripts - - - Recommendations City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 117 of418 Total Total DDD Deliverable Less Num Work -product Number Deliverable Name Amount' Retainage Retainage 86 Integration Test Results Review and DDD-31 Integration Test Scripts - - - Recommendations 87 Training Course Outline Review and DDD-29 Training Materials - - - Recommendations 88 Training Course Content Review and DDD-29 Training Materials - - - Recommendations 89 Updated Project Work Plan and Implementation DDD-02 Project Work Plan - - - Schedule 90 Status Reports DDD-06 Status Report Template - - - 91 Deployment Plan DDD-34 Cutover Plan 47,434 42,691 4,743 92 Update to Help Desk and Support Procedures DDD-35 Review & Update of - - - Competency Center Material 93 Documented Integration Test DDD-32 Integration Test Results 23,716 21,344 2,372 94 User Acceptance Test Plan DDD-07 Testing Plan - - - 95 User Acceptance Test Scripts DDD-36 User Acceptance Test Scripts - - - 96 User Acceptance Test Results DDD-36 User Acceptance Test Scripts 71,150 64,035 7,115 97 Final Production System DDD-34 Cutover Plan 47,434 42,691 4,743 98 Communication Plan Content DDD-15 Communication Plan - - - 99 Workforce Transition Plan Work -products DDD-28 Workforce Transition Plan - - - 100 Delivery of Power User and End -User Courses DDD-39 Training Delivery 94,866 85,379 9,487 101 Deployment Plan Review and Recommendations DDD-34 Cutover Plan - - - 102 Help Desk Procedure Review and DDD-35 Review & Update of - - - Recommendations Competency Center Material 103 Internal Control Framework Go -Live Assessment DDD-34 Cutover Plan - - - City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 118 of 418 1 1 1 1 A I 1 i I 1 I I t I I I i I I City of Fort Worth / C1BER, Inc. Professional Services Agreement Page 119 of 418 EXHIBIT C - NONDISCLOSURE AGREEMENT THIS AGREEMENT is entered into between CITY OF FORT WORTH ("City") a home rule .. municipal corporation organized under the laws of the State of Texas, located in Tarrant, Denton and Wise counties Texas, acting by and through Susan Alanis, its duly authorized Assistant City Manager, and CIBER, INC., ("Contractor"), a professional services firm and acting by and _ through David C. Peterschmidt, its duly authorized Chief Executive Officer. The Parties hereby agree as follows: For purposes of this Agreement, the term Company hereby includes all officers, directors, employees, subcontractors, parent or subsidiary companies of the Contractor. The term City hereby includes all officers, directors, employees, agents, and representatives. Company and City intend to disclose to each other information, which may include confidential information, for the purpose of providing support on City products. The term "Confidential Information" will mean any information or data which is disclosed by a party to the other parry under or in contemplation of the stated purpose and which (a) if in tangible form or other media that can be converted to readable form, is clearly marked as proprietary, confidential or private when disclosed; (b) if oral or visual, is identified as proprietary, confidential or private at the time of disclosure; (c) identifiable as personal health information; or (d) information that is confidential pursuant to a law, _ rule, regulation or court order. Confidential Information may be either the property of the disclosing parry or information provided by a corporate affiliate of the disclosing party or a third parry. Disclosures under this Agreement may be made from the date of this Agreement until its termination, unless extended in a writing signed by both parties. Disclosures and receipt of Confidential Information will be by authorized representative of both parties. The parties may designate others, in writing, to receive and disclose Confidential Information. — 2. For all Confidential Information, the recipient will: (a) Use the Confidential Information only for the stated purpose; (b) Restrict disclosure of the Confidential Information solely to those employees, _ consultants or agents of such party with a "need to know" and not disclose it to third parties without the prior written consent of the disclosing parry; (c) Advise those employees, consultants or agents who gain access to Confidential Information of their obligations regarding the Confidential Information; (d) Make only the number of copies of the Confidential Information necessary to disseminate the information to those employees who are entitled to have access to it, and ensure that all confidentiality notices set forth on the Confidential Information are reproduced in full on such copies; and - (e) Safeguard the Confidential Information with the same degree of care to avoid unauthorized disclosure as recipient uses to protect its own confidential and private information; City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 120 of 418 (f) Notify disclosing party immediately upon discovery of any unauthorized use or disclosure of Confidential Information or any other breach of this Agreement by recipient, its employees, consultants or agents and will cooperate with disclosing party in every reasonable way to help disclosing party regain possession of the Confidential Information and prevent its further unauthorized disclosure or use. For purposes of this Agreement, a "need to know" means that the employee, Contractor, agent, or other designated person requires the Confidential Information in order to perform his or her responsibilities in connection with the stated purpose. 3. The obligations of Paragraph 2 will not apply to any Confidential Information which: (a) Is or becomes available to the public through no breach of this Agreement; (b) Was previously known by the recipient without any obligation to hold it in confidence; .., (c) Is received from a third party free to disclose such information without restriction; (d) Is independently developed by the recipient without the use of Confidential Information of the disclosing party; (e) Is approved for release by written authorization of the disclosing party, but only to the extent of and subject to such conditions as may be imposed in such written authorization; or (f) Is required to be disclosed pursuant to Chapter 552 of the Texas Local Government Code or pursuant to Section 12 herein. 4. If the disclosing party inadvertently fails to mark as proprietary, confidential or private information for which it desires confidential treatment, it will so inform the receiving party. The receiving party thereupon will return the unmarked information to the disclosing party and the disclosing party will substitute properly marked information. In addition, if the disclosing party, at the time of disclosure, inadvertently fails to identify as proprietary, confidential or private oral or visual information for which it desires confidential treatment, it will so inform the receiving party. The receiving party's obligations under Paragraph 2 in connection with information encompassed by this paragraph will commence upon notice from the disclosing party of the failure to properly mark or identify the Confidential Information. 5. Each party acknowledges its obligation to control access to and/or exportation of technical data under the applicable export laws and regulations of the United States, and each party agrees to adhere to and comply with the laws and regulations governing any technical data received under this Agreement. 6. Confidential Information, including permitted copies, will be deemed the property of the disclosing party. The receiving party, will, within ten (10) days of a written request by the disclosing party, return all Confidential Information, including all copies, to the disclosing party or, if so directed by the disclosing party, destroy all such Confidential Information. The receiving party will also, within ten (10) days of a written request by the disclosing party, certify in writing that it has satisfied its obligations under this Paragraph 6. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 121 of 418 7. Both parties agree that an impending or existing violation of any provision of this Agreement would cause the disclosing party irreparable injury for which it would have no adequate remedy at law, and that the disclosing party will be entitled to seek immediate injunctive relief prohibiting such violation, in addition to any other rights and remedies available to it. 8. No patent, copyright, trademark or other proprietary right is licensed, granted or otherwise transferred by this Agreement or any disclosure hereunder, except for the right to use such information in accordance with this Agreement. No warranties of any kind are given for the Confidential Information disclosed under this Agreement. 9. The term of this Agreement shall commence on the Effective Date and shall continue until expiration or termination of the Professional Services Agreement to which this Non -Disclosure Agreement is attached. This Agreement may not be assigned by either party without the prior written consent of the other party. Any assignment in violation of this Paragraph will be void. This Agreement will be binding upon the parties and their respective successors and assigns. 10. The provisions of this Agreement shall not prohibit a disclosure required by law or any court of competent jurisdiction or any investigation or ruling of a governmental.or regulatory body which is lawfully entitled to require any such disclosure; provided that prior to such disclosure the receiving party shall promptly notify the disclosing party of such requirement so that the disclosing party may contest such disclosure and otherwise protect its interests in the timing and content of such disclosure. The receiving party will exercise reasonable efforts to help disclosing party obtain a protective order or other reliable assurance that confidential treatment will be accorded to the Confidential Information. If a protective order or other remedy is not obtained, the receiving party will furnish only that portion of the Confidential ` Information that the receiving party is legally required to disclose. 11. If any provision of this Agreement will be held invalid or unenforceable, such provision will be deemed deleted from this Agreement and replaced by a valid and enforceable provision which so far as possible achieves the parties' intent in agreeing to the original provision. The remaining provisions of this Agreement will continue in full force and - effect. 12. If either party employs attorneys to enforce any rights arising out of this Agreement, each party shall be responsible for the payment of its owns expenses and fees for such related services. 13. Each party warrants that it has the authority to enter into this Agreement and to lawfully make the disclosures contemplated hereunder. 14. This Agreement represents the entire understanding between the parties with respect to the subject matter hereof and supersedes all prior communications, agreements and understandings. The provisions of this Agreement may not be modified, amended or waived, except by a written instrument duly executed by authorized representatives of both parties. 15. This Agreement may be executed in one or more counterparts, each of which will be deemed to be an original and all of which, when taken together, will be deemed to constitute one and the same agreement. Delivery of an executed counterpart of this Agreement by facsimile or any other reliable means shall be effective for all purposes City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 122 of418 as delivery of a manually executed original counterpart. Either party may maintain a copy of this Agreement in electronic form. The parties further agree that a copy produced from the delivered counterpart or electronic form by any reliable means (for example, photocopy, facsimile or printed image) shall in all respects be considered an original. 16. This Agreement shall be governed by and construed in accordance with the laws of the State of Texas. 17. The individuals executing this Agreement represent and warrant that they have -the right, power, legal capacity, and authority to enter into and to execute this Agreement on behalf of the respective legal entities listed in the caption or recitals above.- [SIGNA�'I",AGE FOLLOWS] City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 123 of 418 IN WITNESS WHEREOF, the parties hereto have executed this Agreement in multiples this ZU day of W f , 2012. CIjanlanis ORT W T By Su Asity Manager Date: tI ATT By: / Mary J. Kayser City Secretary CIBER, INC.: By: Chief Exeeu4ve Officer 1.13112 APPROVED AS TO FORM AND LEGALITY: By:_ Maleshia B. Farmer Assistant City Attorney OFFICIAL RECORD CITY SECRETARY FT. WORTH, TX City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 124 of 418 IA:f: EXHIBIT D - NETWORK ACCESS AGREEMENT This NETWORK ACCESS AGREEMENT ("Agreement") is made and entered into by and between the CITY OF FORT WORTH ("City"), a home rule municipal corporation with its principal location at 1000 Throckmorton Street, Fort Worth, Texas 76102, organized under the laws of the State of Texas and situated in portions of Tarrant, Denton and Wise Counties, Texas, and CIBER, INC. with its principal location at 6363 South Fiddler's Green Circle, #1400, Greenwood Village, CO 80111 ("Contractor"). 1. The Network. The City owns and operates a computing environment and network (collectively the "Network"). Contractor wishes to access the City's network in order to provide [description of services]. In order to provide the necessary support, Contractor needs access to [description of specific Network systems to which Contractor requires access, i.e. Internet, Intranet, email, HEAT System, etc]. T 2. Grant of Limited Access. Contractor is hereby granted a limited right of access to the City's Network for the sole purpose of providing [description of services]. Such access is granted subject to the terms and conditions forth in this Agreement and applicable provisions of the City's Administrative Regulation D-7 (Electronic Communications Resource Use Policy), of which such applicable provisions are hereby incorporated by reference and made a part of this Agreement for all purposes herein and are available upon request. 3. Network Credentials. The City will provide Contractor with Network Credentials consisting of user IDs and passwords unique to each individual requiring Network access on behalf of the Contractor. Access rights will automatically expire one (1) year from the date of this Agreement. If this access is being granted for purposes of completing services for the City pursuant to a separate contract, then, this Agreement will expire at the completion of the contracted services, or upon termination of the contracted services, whichever occurs first. Services are being provided in accordance with City Secretary Contract No. 4. Renewal. At the end of the first year and each year thereafter, this Agreement may be renewed annually if the following conditions are met: 4.1 Contracted services have not been completed. 4.2 Contracted services have not been terminated. 4.3 Within the thirty (30) days prior to the scheduled annual expiration of this Agreement, the Contractor has provided the City with a current list of its officers, agents, servants, employees or representatives requiring Network credentials. Notwithstanding the scheduled contract expiration or the status of completion of services, Contractor shall provide the City with a current list of officers, agents, servants, employees or representatives that require Network credentials on an annual basis. Failure to adhere to this requirement may result in denial of access to the Network and/or termination of this Agreement. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 125 of 418 5. Network Restrictions. Contractor officers, agents, servants, employees or representatives may not share the City -assigned user IDs and passwords. Contractor — acknowledges, agrees and hereby gives its authorization to the City to monitor Contractor's use of the City's Network in order to ensure Contractor's compliance with this Agreement. A breach by Contractor, its officers, agents, servants, employees or representatives, of this Agreement and any other written instructions or guidelines that the City provides to Contractor pursuant to this Agreement shall be grounds for the City immediately to deny Contractor access to the Network and Contractor's Data, terminate the Agreement, and pursue any other remedies that the City may have under this Agreement or at law or in equity. 6. Termination. In addition to the other rights of termination set forth herein, the City may terminate this Agreement at any time and for any reason with or without notice, and without penalty to the City. Upon termination of this Agreement, Contractor agrees to remove entirely any client or communications software provided by the City from all computing equipment used and owned by the Contractor, its officers, agents, servants, employees and/or representatives to access the City's Network. 7. Information Securitv. Contractor agrees to make every reasonable effort in accordance with accepted security practices to protect the Network credentials and access methods provided by the City from unauthorized disclosure and use. Contractor agrees to notify the City immediately upon discovery of a breach or threat of breach which could compromise the _ integrity of the City's Network, including but not limited to, theft of Contractor -owned equipment that contains City -provided access software, termination or resignation of officers, agents, servants, employees or representatives with access to City -provided Network credentials, and unauthorized use or sharing of Network credentials. 8. LIABILITY AND INDEMNIFICATION. Liability and Indemnity shall be governed by Section 8 of the Professional Services Agreement to which this Agreement Is attached. 9. Confidential Information. Contractor, for itself and its officers, agents, employees, and representatives, agrees that it shall treat all information provided to it by the City as confidential �- and shall not disclose any such information to a third party without the prior written approval of the City. Contractor further agrees that it shall store and maintain City Information in a secure manner and shall not allow unauthorized users to access, modify, delete or otherwise corrupt — City Information in any way. Contractor shall notify the City immediately if the security or integrity of any City information has been compromised or is believed to have been compromised. In the event of termination of the agreement or at the completion of the contract, the Contractor shall work with the City to identify all City provided information that resides on staff computers and on CIBER's PMRx® Project site and to plan and execute steps to remove information from these sources and submit acceptable electronic versions of the documentation to the City. 10. Right to Audit. Contractor agrees that the City shall, during the initial term, any renewal terms, and until the expiration of three (3) years after termination or expiration of this contract, have access to and the right to examine at reasonable times any directly pertinent books, data, documents, papers and records, both hard copy and electronic, of the Contractor involving transactions relating to this Agreement. Contractor agrees that the City shall have access during normal working hours to all necessary Contractor facilities and shall be provided adequate and appropriate work space in order to conduct audits in compliance with the provisions of this section. The City shall give Contractor reasonable advance notice of -- intended audits. Contractor further agrees to include in all its subcontractor agreements hereunder a provision to the effect that the subcontractor agrees that the City shall, during the initial term, any renewal terms, and until expiration of three (3) years after termination or _ City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 126 of 418 r� expiration of the subcontract, have access to and the right to examine at reasonable times any directly pertinent books, data, documents, papers and records, both hard copy and electronic, of such subcontractor involving transactions related to the subcontract, and further that City shall have access during normal working hours to all subcontractor facilities and shall be provided adequate and appropriate work space in order to conduct audits in compliance with the provisions of this paragraph. City shall give subcontractor reasonable notice of intended audits. 11. Aqreement Cumulative. This Agreement is cumulative of and in addition to any written contracts, agreements, understandings or acknowledgments with the City signed by Contractor. This Agreement and any other documents incorporated herein by reference constitute the entire understanding and Agreement between the City and Contractor as to the matters contained herein regarding Contractor's access to and use of the City's Network. 12. Amendments. The terms of this Agreement shall not be waived, altered, modified, supplemented, or amended in any manner except by written instrument signed by an authorized representative of both the City and Contractor. 13. Assignment. Contractor may not assign or in any way transfer any of its interest in this Agreement. Any attempted assignment or transfer of all or any part hereof shall be null and void. 14. Severability. If any provision of this Agreement is held to be invalid, illegal or unenforceable, the validity, legality and enforceability of the remaining provisions shall not in any way be affected or impaired. 15. Force Maieure. Each party shall exercise its best efforts to meet its respective duties and obligations as set forth in this Agreement, but shall not be held liable for any delay or omission in performance due to force majeure or other causes beyond their reasonable control (force majeure), including, but not limited to, compliance with any government law, ordinance or regulation, acts of God, acts of the public enemy, fires, strikes, lockouts, natural disasters, wars, riots, material or labor restrictions by any governmental authority, transportation problems and/or any other similar causes. 16. Governinq Law / Venue. This Agreement shall be construed in accordance with the laws of the State of Texas. If any action, whether real or asserted, at law or in equity, is brought on the basis of this Agreement, venue for such action shall lie in state courts located in Tarrant County, Texas or the United States District Court for the Northern District of Texas, Fort Worth Division. 17. Signature Authoritv. The signature below of a acknowledges that the Contractor has read this Agreement and and conditions set forth herein. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 127 of 418 [Signature Page Follows] n authorized representative agrees to be bound by terms ACCEPTED AND AGREED: CITWOF ORT WORTH: By: Alanis A ' tant ity M�i nap Date: l0 9111 Y ATTEST: By: 4 / 44U %? IMaJ. Kayser (amity Secretary APPROVED AS TO FORM AND LEGALITY: By: Assistant Cit Attorney M & C: none required OFFICIAL RECORD CITY SECRETARY FT. WORTH, TX City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 128 of 418 CIBER, INC.: / By: idt /erne G�voy�se etive 0fficeroP--+,-4,,7 100;/.?3//2 OU ow r+ M FM an Mw EXHIBIT E — DELIVERABLBE ACCEPTANCE FORM Deliverable Describe the product, good or service delivered for the project. List all products and services, including specifics like documentation, training and dates of completion Future Work There may be areas where there is future work to be completed or items that need to be addressed, but do not keep the deliverable from being complete. Also, future work areas that this deliverable contributes to should also be listed. Acknowledgment of Completion The purpose of this document is to acknowledge the completion of the deliverable. As of this date: • All tasks have been delivered and are complete • All appropriate documentation has been received • Signatures authorize payment to the vendor for the deliverable completion. I have reviewed the information contained in this Project Deliverable Acceptance. Approver #1 Approver #2 4 Approver #3 Approver #4 Approver #5 Approver #6 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 129 of 418 Date Date Date Date Date Date dNN EXHIBIT F — MWBE FORM om IL d F*SP ,: +±,e J6 1 =sa or a?f+ s,su. UnAi dF tit b � % t � d � �sd.k" ft rdon ro AMU:: 0=t" Plil!o1�Y8��a11�teli ink upr CAt Y�i119r ira oidgrlYd sYlr dlt(p[r1mcm p rildel drE td%[at ! db , iraitlra �ptr M� 4ot�hisi lN1iIPi(;� � � � ter i1q �rre ;irad .+t r�r>i�IfQr�rrd�vr ls�halftifrhea>�xa14lMi ell, ltiirZ.� City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 130 of 418 EXHIBIT G - INITIAL TECHNICAL SCOPE AND ESTIMATES PermitPlus Lease Management System (LMS) ITSM FASTER automated application. Planning & Inbound Bills and Cash receipts Development Aviation Inbound Revenue Bills and Receipts Environmental Management; Information Technology Solutions (ITS) All ESD Fuel Equipment Warehouse Services (Part of Phase IIC — Procurement and Inventory City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 131 of 418 Inbound Revenue Bills and Receipts Batch As Needed 100 Moderate Batch As Needed 10 — 100 Moderate Batch or Weekly 15 — 20 Moderate Manual (depending on volume) Inbound Inbound: Batch or Inbound: 2,700 and Equipment Services Division Near/Real- Monthly as 3,000 Outbound Charges are interfaced at month- Time needed end. Outbound: Outbound: Daily Potential candidate for interfaces re: Purchasing, Goods Receipts and Expenditures. Inbound Fuel issued out of fuel system to Batch Daily 700 be brought into PeopleSoft for Inventory monitoring purposes. — Moderate Low T�tie `User ' Inbound, Description of:the info rrriatiop, ;Transmission Frequency Volume Complexity Depa ne##s} 9 or n iriad Method (per gi�l�l�t#n4i frequency) Option) Event Based Public Events / Inbound End of Day Revenue Batch Daily 10 - 20 Low Management Parks & System (EBMS) Community Services (PACS) M/WBE Vendor All Outbound Vendor Information, Payment Batch Database History, Contracting History Sweeps Code Inbound Revenue Bills and Receipts Batch Compliance Code Ops Code Inbound Revenue Bills and Receipts for Batch Compliance fines, Invoices against a contract for payment requests. Northridge Loan Housing and Inbound Loan Payments (Principal and Batch System Economic Interest) Development Encompass Housing and Inbound Loans Established Batch Econom is Development IDIS (HUD) Housing and Outbound Grant billing Integrated Economic D' b Development Daily TBD Moderate Daily 300 - 350 Moderate Daily 50 - 500 Moderate Daily 10 - 20 Moderate Daily Manual due to Monthly volume 10 - 20 Moderate 10 - 20 N/A is ursement Information System CourtView Municipal Court, Inbound GL Journal and A/P checks Batch Daily GL - 1-100 Low (Evaluated with Legal, Police, processing Phase IIA Code AP - 500- Development Compliance, 1,200 Fire (NOTE: the user departments for City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 132 of 418 i i >V I ! ? � I _ I � i I � I ► � 4 � the financial model are solely Muni Court, with Financial Management Services (FMS) processing the interfaced transmitted financial data) Maximo Water / Waste Inbound To provide an extract file of all the Batch Water Field Ops Warehouse inventory Issue, Transfer and Return transactions made in Maximo for posting into the General Ledger Sungard PS Water / Waste Inbound Financial transactions to General Batch Utility Billing Water Ledger Account Management Capital Project All Inbound/O Until Phase IIC, cost information Batch Management utbound for select projects will need to be System/Unifier interfaced into CPMS and budget transactions will need to be interfaced out of CPMS. Cell Phone Financial Inbound Expenditure distribution for Batch Interface Management previously posted invoice. Services; Information Technology Solutions Class Program Parks & Inbound/O Inbound: General Ledger Batch Community utbound information City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 133 of418 Monthly 350 — 500 Low Daily 100 — Low 73,000 Daily Expenditure: Moderate 0 — 7,000 Budget: 0 — 5, 500 Monthly 6,000 — Low 8,000 Daily 10 — 120 Moderate 'Tale `° U,ser lnt�ound Descrl�ttonofthe,iinforma tion Transmisswn frequency Volume Complexity iej�aTi111elit{$�Ory Interfaced 4per .y 4u#b0uttcl frequency} ,. Services Inbound: A/P Refunds of Revenue PaymentNet(JP Financial Inbound Used to distribute Procurement Batch Bi-Weekly 3,000 — Moderate MChase) Management Card expenditures. 6,000 Services Information Information Inbound Charges for IT Services Batch Monthly 2,300 — Low Services ISSB Technology 5,800 Database Solutions Data Source: Information Inbound Expenditure distribution for Batch Monthly 100 — 2,100 Low Nextel Interface Technology previously posted invoice. Solutions Data Source: Oil Planning & Inbound Revenue Batch Monthly 10 —1,300 Low and Gas Development Revenue Office Services Financial Inbound Service charges to departments. Batch Monthly 8,500 — Low Custom DB Management 12,000 Services USA Mobility Information Inbound Expenditure distribution for Batch Monthly 1,000 — Low Pagers Technology previously posted invoice. 3,000 Database Solutions Redlight Safety Transportation & Inbound Two Revenue Interfaces Batch Daily 50 — 6,000 Low Application Public Works (Lockbox and Manual Payments) Data Source: Financial Inbound Expenditure distribution for Batch Bi-Weekly 75 - 500 Low Gas and/or Management previously posted invoice. Electric Interface Services Verizon Custom Information Inbound Expenditure distribution for Batch Monthly 2,100 — Low Database Technology previously posted invoice. 2,300 Solutions Data Source: Financial Inbound Expenditure distribution for Batch Monthly 650 Low Cable TV Management previously posted invoice. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 134 of 418 I I 1 I I I I f i I I I 11 1 I I I I A tjounsC Des �� tlhe �nfarmation' 'Tr wismtsa� r re uenc Volume Corn' le `it �. ,.��ett p ? '.✓ % , intrfacdifethpd. f %; , �p er, {, �?ut1 .- \ f�equencj " Interface Services Alarms Billing Planning & Inbound Revenue Batch Daily/As 40 — 50 Low Development needed Water Refund Water / Waste Inbound Revenue Refunds to General Batch Daily/As 450 - 500 Low Check Water Ledger needed eCouncil Packet All Both The City is interested in To be To be To be To be integration between this determined determined determined determined application and several PeopleSoft transactions. For example: capturing the PS Requisition number in eCouncil M&C's; and capturing the M&C Number on contracts, grants, purchase orders and budget adjustments. iTerminal / All Inbound Inbound Credit Card information Batch Daily Credit Card Moderate Chase Payment Summaries Tech for 60 — 100 locations Fire Fire Outbound Goods Receipts Automated, As Needed Not Low Apparatus/Equip Batch available ment Tracking STARS FMS / Risk Outbound Automation of claim operations Automated, As Needed Small Low Management and insurance policy Batch management ACH FMS Inbound Reconciliation process with Automated, Daily 2,000 — Low Chase Bank Batch 5,000 Positive Pay FMS Inbound Reconciliation process with Automated, Daily 2,000 — Low Chase Bank Batch 5,000 Radio Tracking Fire Inbound Goods Receipts Batch As Needed 50 - 100 Low City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 135 of 418 T!tie User inbound Diacrip#tart of ik�e �nfarma#ion 't ransmssron Frequency Volume C omplexity . epakrrntl<sj �y interfaced c a• Method(per i Q#b4urid y fre ) "frequency) Database BuySpeed All Inbound/O See section below Online utbound City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 136 of 418 Automated, Daily and near real time on -demand and batch High i i i I 1 I i I 1 I i 1 I I -'s - f 1 --.1 - I Function Ciber/PSFT Periscope Holdings Incorporated Interface (PHI)/BuySpeed Online Item? Cancel Items . Liquidate remaining encumbrance • Cancel items in BSO • Send call to PSFT to release Y encumbrance Generate Invoice • Enter invoice • Complete three way match • Add freight or additional costs (if Y applicable) • Create BSO voucher Generate Payment . Run voucher creation process • Send account and payment information • Liquidate encumbrance • Update BSO voucher with PSFT Y • Create expenditure voucher number Send voucher number back to BSO Issue Check 0 Issue check number • Add PSFT check number to invoice Y • Send check number to BSO (for vendor inquiry) Reporting/Query • Budget Line Item Detail • Provides a current account status of budget, pre -encumbrance, encumbrance, and expenditure N amounts with the associated document number (BSO PO number or Req Number) • Purchasing Line Item Details Provide details of purchasing line N items City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 139 of 418 HIGH-LEVEL BUSINESS PROCESS FLOW DIAGRAMS e «a. \ \. m we -Encumbrance Yes— . �0 _Z \ — Yes ..... ww" , City « Fort Worth ZgBER,Inc. Professional Services Agreement Paplm «qa Prepare & Submit for. Approval No .,?I Purchasing and Approvers City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 141 of 418 teq��x Yes Liquidated I R/T Pre -Encumbrance Liquidated Pass/Faf I Yes Yes Rrr PIE Liquidated Pass/Fai'. RR Encumber 8: Undo Pre-Encum. En �� c- '*Undo 8 Encumbered City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 142 of 418 Document„F:h..Touch Points Rwy peed. BuySpeed People5oit Notify Vendor of City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 143 of 418 R/r Vendor Data VettdaP I MA§tBPr Rfr Vendor Add Pass/Fail' I Liquidate PE .iquidated Pass/Fair Pre -Encumbrance . I. imbrance Budget Check ' Budget Check Pass/Fail City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 144 of 418 7 1� 4E Vendors --F .;', w W M City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 145 of 418 R/r Encumbrance _ Adjustments PeopleSofl 1 K1�7ab}es R T Encumbrance Adjustment Pass/Faih ax. No City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 146 of 418 w M me an Document Ffow with Touch Points - invoices OM BuySpeed -A Uses Buy�ed»at cratsfe i ff . iy u n- `> 4 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 147 of 418 4� T Check' IflC'f` s T Check Document Flow with Touch Points— Invpices page 2 ` BuySpeed Y Users BuySpeed FinanGai S Final pays Yes Amt < PO Amf .:. Yes Aut6met�¢ ~R/r Liquidate z Remaining Encumbrance R!r Pass/Fall of Liquidation Send ' vouchers io. Financial, R/T Matched Vow Syen R/T Records that P Rrr Check #, pate & Amt. Vendors Inquire on Invoices Pktt invb�a� City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 148 of418 i. Peoplai_ K�4 Table�y ; PeopleBoftA@ i checks and Ad to'Vettr M , Vendor Update Process w a Fort Worth Pao �eSbit dote Bu S fed° < R Rr t�14'ru+Eaii, ., . _ Finannak=Ricfaei Vendor Admin Vendor Self Registration & Updates City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 149 of 418 it idor Pepp%So .<..T. : yendpp< as 1 of Update----------' \ F .,.E fN Nightly Batch of .4 Changes/Additions To Chart of Accounts City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 150 of 418 fa qw M M Vw FM M am w A f M OI M Ow INITIAL PEOPLESOFT TECHNOLOGY COMPONENTS Technology Description R Component Commitment Control Commitment Control is used for budgetary control. Commitment control limits spending by comparing the actual expense or expenditure against approved appropriations and includes pre - encumbrances (requisitions), encumbrances (purchase orders) and expenditures (vouchers)._ _ Voucher Build Application Engine process that brings vouchers into PeopleSoft via Process an interface. Process applies edits and business rules for validation and voucher creation. AP Check Run e AP process that creates payments Vendor Master e Maintain vendor information within PeopleSoft Tables Integration Broker e PeopleSoft middleware platform design to facilitate exchange of data between PeopleSoft and non-PeopleSoft appGcai.. ins REQUIREMENTS The City and CIBER have reviewed the detailed requirements to identify those requirements that have implications for and/or are impacted by the final detailed design of the interface. As part of the detailed design process, the City and CIBER will include a review and impact determination for all of the requirements identified in TABLE 2: Review Due to Phase IIC: Procurement and Inventory Option. The capture of the impacts will assist the other functional teams in determining the final disposition of the requirement during the Fit -Gap process and Requirements Traceability Matrix development. CIBER has estimated a level of effort associated with the aforementioned BuySpeed and PeopleSoft interface to be 815 hours of functional consulting and 540 hours of technical development. Should the level of effort required exceed the allocated hours, the City will be subject a Scope Change. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 151 of 418 Exhibit G.2: Estimate of Effort for Interface Development ESD Fuel Warehouse Event Based Management I System (EBMS) M/WBE Vendor Database I Sweeps I Code Ops I Northridge Loan System Encompass I IDIS (HUD) Integrated I Disbursement Information System CourtView I City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 152 of 418 Equipment Services Division Charges are interfaced at month -end. Outbound: Potential candidate for interfaces re: Purchasing, Goods Receipts, and Expenditures. Fuel issued out of fuel system to be brought into PeopleSoft for 80 Inventory monitoring purposes. End of Day Revenue 40 Vendor Information, Payment History, Contracting History 40 Revenue Bills and Receipts 40 Revenue Bills and Receipts for fines, Invoices against a contract for 40 payment requests. Loan Payments (Principal and Interest) 80 Loans Established 80 Grant billing 80 GL Journal and A/P checks processing 40 � f; r •u � •: .1'.. .,, v .. aern•, v.. v x.�w 2" Sy�, � :. � .� e ��� 2� a..sE,. x � i... � � � ; - Maximo I To provide an extract file of all the Field Ops Warehouse inventory 40 Issue, Transfer and Return transactions made in Maximo for posting into the General Ledger Sungard PS Utility Billing I Financial transactions to General Ledger 40 Account Management Capital Project I Until Phase IIC, cost information for select projects will need to be 80 Management interfaced into CPMS and budget transactions will need to be System/Unifier interfaced out of CPMS. Cell Phone Interface I Expenditure distribution for previously posted invoice. 80 Class Program I Inbound: General Ledger information 80 Inbound: A/P Refunds of Revenue PaymentNet(JPMChase) I Used to distribute Procurement Card expenditures. 80 Information Services ISSB I Charges for IT Services 40 Database Data Source: Nextel I Expenditure distribution for previously posted invoice. 40 Interface Data Source: Oil and Gas I Revenue 80 Revenue Office Services Custom I Service charges to departments. 40 DB USA Mobility Pagers I Expenditure distribution for previously posted invoice. 80 Database Redlight Safety I Two Revenue Interfaces (Lockbox and Manual Payments) 80 Application Data Source: Gas and/or I Expenditure distribution for previously posted invoice. 80 Electric Interface Verizon Custom Database I Expenditure distribution for previously posted invoice. 80 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 153 of 418 Data Source: Cable TV I Interface Alarms Billing I Water Refund Check I eCouncil Packet I iTerminal / Chase I Payment Tech Fire Apparatus/Equipment I Tracking Expenditure distribution for previously posted invoice. 80 Revenue 80 Revenue Refunds to General Ledger 40 The City is interested in integration between this application and 120 several PeopleSoft transactions. For example: capturing the PS Requisition number in eCouncil M&C's; and capturing the M&C Number on contracts, grants, purchase orders and budget adjustments. Inbound Credit Card information 40 Goods Receipts 40 STARS I Automation of claim operations and insurance policy management 80 ACH I Reconciliation process with Chase Bank 40 Positive Pay I Reconciliation process with Chase Bank 40 Radio Tracking Database I Goods Receipts 80 Oracle Primavera P6 I To serve scheduling and reporting purposes for capital projects. N/A Professional Uses SQL server as the data backend which are located in the City's SQL Server Farm. (TBD in Phase IIC) Project Dashboard I To provide timely project or program scheduling and financial N/A information and tools specifically designed for types of users to address their need of project or program related information. Could be an interface candidate possibly as a linked into application. Project Dashboards are hosted on a City Server. Not currently being slated for replacement. This is currently 'Best of Breed' technology. No known sources of conversion. Source of the information: Primavera Server (live data), user input (calendars, notices, etc.) and uploads (MS Word, MS Excel, pdf. etc.) (TBD in Phase IIC) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 154 of 418 I I I I I I i l i I I I I I I i 1 1 4 1 A so -1 .•.A _ 1 J 1 4 Exhibit G.3: Initial Conversion Scope The following table represents the initial list of conversion candidates that are in scope for ERP Phase II. Conversion Candidate Fire Description Source Approximate Cc-nversiort Scope Anticipated Volume Conversion Method General Ledger The general ledger is the main accounting record at a MARS TBD during All chart of account Spreadsheet Accounts business which uses double -entry bookkeeping. It redesign. values to support Upload includes accounts for current assets, fixed assets, (currently go -live liabilities, revenue and expense items, gains and losses. 12,000) Funds Fiscal and accounting entity with a self -balancing set of MARS 225 All active at the Spreadsheet accounts recording cash and other financial resources, time of go -live Upload together with all related liabilities and residual equities or balances, and changes therein, that are segregated for the purpose of carrying on specific activities or attaining certain objectives in accordance with special regulations, restrictions, or limitations. [NCGA Statement 1] 7 CFarac�er Center Used to capture the organizational dimension of the MARS 2,000 All active at the Spreadsheet City's financial data classification structure. The first 3 time of go -live Upload digits define Department, the next 2 digits the Division, and the last 2 digits define the Section (i.e. 0130124 - Finance/Accounting/Grants) Capita' Project Centers Used to capture the project and work phase for capital MARS 96,000 All active at the Spreadsheet projects. There are a variety of different numbering time of go -live Upload conventions in use at the City for the project work phase structure. Grant Centers Used to capture the grant and work phase for federal and MARS 630 All active at the Spreadsheet state grants. The first 3 characters represent the time of go -live Upload Department, the next 3 characters capture the grantor, the next 3 represent the work phase, the next 2 identify expcnsc: or revenueL and the final positior. represent is City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 155 of 418 Approxirn;a Can tension Scope Antieio. tWd, `g Volume Converslort . Method zero (0). Departments A listing of all active City Departments MARS 25 Program Codes A new structure to be defined as part of the financial data To be Unknown classification redesign gathered Customers A listing of all active customers, individuals and entities Various 72,000 for which the City provides a service or product Council Districts A listing of the current Council Districts MARS 9 Capital Project A listing of all active Programs which the City has MARS 50 Programs assigned Capital Projects Capital Project Sub- Al listing of all active Sub -Funds which have been MARS 700 Funds assigned to Capital Projects General Ledger Trial A listing of all account balances associated with all open MARS 225,000 Balance Funds Inventory Items (Part of A listing of all active items carried in Inventory for Excel 2,500 Phase IIC — departments that will use PeopleSoft Inventory. Procurement and Inventory Option) Inventory Balances The value and quantity of items stored in the City's Various 2,500 (Evaluated with Phase inventories IIA Development Items) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 156 of 418 I t II I I I I I I 1 ! 1 All active at the Manual time of go -live TBD Spreadsheet Upload All active at the Spreadsheet time of go -live. Upload All active at the Manual time of go -live All active at the Manual time of go -live All active at the Spreadsheet time of go -live Upload All active at the Automated time of go -live All active items at Automated the time of go -live All balances as of Automated the prior fiscal year end. I I I II # I A I I I / I I! I I 1 II M I S� Ires Approxirn�te CJ*Ojop Scope Anticipat6d` Conversion Vntum� ,� i Method Inception to Date — Inception to date revenue and expense balances MARS 140,000 Projects associated with open Projects Inception to Date — Inception to date revenue and expense balances MARS 64,000 Grants associated with open Grants Fixed Asset Locations The associated locations of the recorded fixed assets Excel 650 Fixed Assets A listing of all recorded Fixed Assets for the City with Excel 32,000 their associated value and accumulated depreciation Units of Measure Units used by Purchasing and Inventory BuySpeed 1,000 (Part of Phase IIC — Online Procurement and Inventory Option) Sales Items Commodities sold by the City and used on customer To be Unknown invoices gathered Commodity Code (Part National Institute of Governmental Purchasing (NIGP) 5 BuySpeed 8,200 of Phase IIC — digit codes/descriptions Online Procurement and Inventory Option) Vendors Listing of vendors in the City's Master Vendor file BuySpeed 15,000 Online Open Bids (Part of Listing of Open Bids as identified in the BuySpeed Online BuySpeed 100 Phase IIC — system Online Procurement and City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 157 of 418 All active at the Automated time of go -live All active at the Automated time of go -live All active at the Spreadsheet time of go -live Upload All active at the Automated time of go -live All active at time of Spreadsheet go -live Upload All active at time of Spreadsheet go -live Upload All active at the Spreadsheet time of go -live Upload All registered Automated bidders and other vendors with activity in the last two years. All open at the time Manual or of go -live managed through cut- off of data Inventory Option) Requisitions Listing of Requisitions as identified in the BuySpeed BuySpeed 1,000 (Evaluated with Phase Online system Online IIA Development Items) Purchase Orders Listing of Purchase Orders as identified in the BuySpeed BuySpeed 5,000 (Evaluated with Phase Online system Online IIA Development Items) Contracts (Evaluated Listing of Contracts (annual agreements and City BuySpeed 2,000 with Phase IIA Secretary Contracts) as identified in the BuySpeed Online Development Items) Online system Accounts Payable — Listing of Accounts Payable Invoices as identified in the BuySpeed 2,500 Invoices (Evaluated BuySpeed Online system Online with Phase IIA Development Items) Receipts (Evaluated Listing of Receipts as identified in the BuySpeed Online BuySpeed 1,000 with Phase IIA system Online Development Items) Accounts Receivable - Listing of Accounts Receivable for Insufficient Funds Excel NSF Checks (NSF) Checks City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 158 of 418 3,000 Conversion Scope Anticipated -ry 3 Conversion Method entry at conversion All open at the time Automated or of go -live managed through cut- off of data entry at conversion All open at the time Automated of go -live All open at the time Automated of go -live All open at the time Automated or of go -live managed through cut- off of data entry at conversion All open at the time Automated or of go -live managed through cut- off of data entry at conversion All open at the time Spreadsheet of go -live Upload I I I I I I I I I 1 1 1 1 1 1 1 1 1 1 i 1 i I j 1 I a I 1 1 I i l ! I I I I ✓,3 4 ASP \��� -i .� / E'\ \\�LZW�gM�` "' ✓i $'A h¢%tr �x4. �\ a f'Xa x ga S .< Accounts Receivable - Listing of Accounts Receivable Invoices Various Unknown Invoices Outstanding Checks Listing of unreported checks from the reconciliation Mainframe 4,000 process Check Register Petty Cash Petty Cash Balances for each location General 500 Ledger Balance City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 159 of 418 gnYScope ,Anticip'Ated '„ Conversion Method $• All open at the time Spreadsheet of go -live Upload All at the time of Spreadsheet go -live Upload All active at the Spreadsheet time of go -live Upload Exhibit GA Estimate of Effort for Conversion Development MARS C The general ledger is the main accounting record 40 of a business which uses double -entry bookkeeping. It includes accounts for current assets, fixed assets, liabilities, revenue and expense items, gains and losses.- Spreadsheet Upload MARS C Fiscal and accounting entity with a self -balancing 40 set of accounts recording cash and other financial resources, together with all related liabilities and residual equities or balances, and changes therein, that are segregated for the purpose of carrying on specific activities or attaining certain objectives in accordance with special regulations, restrictions, or limitations. [NCGA Statement 1]- Spreadsheet Upload MARS C Used to capture the organizational dimension of 40 the City's financial data classification structure. The first 3 digits define Department, the next 2 digits the Division, and the last 2 digits define the Section (i.e. 0130124 - Finance/Accounting/Grants)- Spreadsheet Upload MARS C Used to capture the project and work phase for 40 capital projects. There are a variety of different numbering conventions in use at the City for the project work phase structure.- Spreadsheet Upload MARS C Used to capture the grant and work phase for 40 federal and state grants. The first 3 characters represent the Department, the next 3 characters capture the grantor, the next 3 represent the work phase, the next 2 identify expense or revenue, and the final position represent is zero (0).- Spreadsheet Upload MARS C A listing of all active City Departments- Manual 20 To be C A new structure to be defined as part of the 40 gathered financial data classification redesign- Spreadsheet Upload Various C A listing of all active customers, individuals and 40 entities for which the City provides a service or product- Spreadsheet Upload MARS C A listing of the current Council Districts- Manual 20 MARS C A listing of all active Programs which the City has 20 assigned Capital Projects- Manual MARS C A listing of all active Sub -Funds which have been 40 assigned to Capital Projects- Spreadsheet Upload MARS C A listing of all accounts associated with all open 80 Funds- Automated City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 160 of 418 M I= so ,a I��t�Gs��nver� e i��t1'ie flab �Et��'A���d►M: ;�� �� �- �,� � ��°� Excel C A listing of all active items carried in Inventory for 80 departments that will use PeopleSoft Inventory. - Automated Various C The value and quantity of items stored in the City's 80 inventories- Automated MARS C Inception to date revenues and expenses 80 - associated with open Projects- Automated MARS C Inception to date revenues and expenses 80 associated with open Grants- Automated Excel C The associated locations of the recorded fixed 80 assets- Spreadsheet Upload Excel C A listing of all recorded Fixed Assets for the City 80 with their associated value and accumulated depreciation- Automated BuySpeed C Units used by Purchasing and Inventory- 40 Online Spreadsheet Upload To be C Commodities sold by the City and used on 40 gathered customer invoices- Spreadsheet Upload BuySpeed C National Institute of Governmental Purchasing 40 Online (NIGP) 5 digit codes/descriptions- Spreadsheet Upload BuySpeed C Listing of vendors in the City's Master Vendor file- 80 Online Automated BuySpeed C Listing of Open Bids as identified in the BuySpeed 80 Online Online system- Manual or managed through cut- off of data entry at conversion BuySpeed C Listing of Requisitions as identified in the 80 Online BuySpeed Online system- Automated or managed through cut-off of data entry at conversion BuySpeed C Listing of Purchase Orders as identified in the 80 Online BuySpeed Online system- Automated BuySpeed C Listing of Contracts (annual agreements and City 80 Online Secretary Contracts) as identified in the BuySpeed Online system- Automated - BuySpeed C Listing of Accounts Payable Invoices as identified 80 Online in the BuySpeed Online system- Automated or managed through cut-off of data entry at conversion BuySpeed C Listing of Receipts as identified in the BuySpeed 80 Online Online system- Automated or managed through cut-off of data entry at conversion Excel C Listing of Accounts Receivable for Insufficient 40 Funds (NSF) Checks- Spreadsheet Upload Various C Listing of Accounts Receivable Invoices- 40 Spreadsheet Upload City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 161 of 418 Data Conversion Re c;u i rem e nts From RFP Apporidix M Mainframe C Listing of unreported checks from the 140 Check reconciliation process- Spreadsheet Upload Register General C Petty Cash Balances for each location- 40 Ledger Spreadsheet Upload Balance City of Port Worth / CIBER, Inc. Professional Services Agreement Page 162 of418 Exhibit GA Initial Enhancement Scope Requirement Development Modiificationslfnhancements (MIE), Interfaces (1), Conversion (C), and Hours Number(%) or Other Reference Type (M)E,I,C,R) Repo rWQu e ries (R) Short Descriptlon Core 1=finance F1-00-12-03-00 MIE Data entry into one element of the data classification structure defaults or "looks up" other 120 values of the data classification structure through a mapping table. F'I-00-16-00-00 WE ysk.-nj provides for financial data classification structure elements to have a long description of 20 at least 50 alphanumeric characters. F1-00-17-00-00 MIE System provides for finanbial data classification structure elements to have a short description of 20 at least 25 alphanumeric characters. F1-00-20-00-00 MIE System provides the ability to have multiple ledgers that are able to be updated simultaneously. 200 F1-00-23-00-00 M/E System provides the ability to track contract and project numbers in the general ledger for 40 reporting purposes. F1-00-26-00-00 M/E System provides the ability to process mass changes/deletions on data classification structures. 40 F1-00-38-00-00 MIE 5yet maintains an audit trail of changes to financial and non -financial attributes (old value, 20 I new value, date changed, user) F1-01-09-01-00 R Original Budget 40 +Carryforward in -Carryforward out +Transfers in -Transfers out +Supplements - Revisions F1-02-01-05-00 ! me Departmental BudgetT. rthat crosses Division to a central Finance approver. 20 F1-02-01-06-00 F WE Departmental Budget Adjustment to a central Finance approver. 120 �I F1-02-03-01-00 MIE Vendor Crwflon 20 F1-02-03-02-00 491E Vendor Updates 20 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 163 of 418 F1-02-03-03-00 M/E Customer Creation F1-02-03-04-00 M/E Customer Updates F1-02-03-05-00 F1-02-03-06-00 F1-02-03-07-00 F1-02-03-08-00 F1-02-03-09-00 F1-02-03-10-00 F 1 -02-03-11 -00 F1-02-03-12-00 F 1-02-03-13-00 F1-04-03-02-00 F1-04-03-03-00 M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E F1-04-03-04-00 M/E F1-04-03-05-00 M/E F1-04-05-00-00 M/E F1-04-06-01-00 M/E F1-04-06-02-00 M/E F 1-04-06-03-00 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 164 of 418 M/E Recurring Journal Entries 20 Reversing Journal Entries 20 Asset Retirements or Change of Status Asset Transfers Postings to specified accounts Updates to Financial Data Classification Structures Completion of Batch Processes (interfaces) Unsuccessful Batch Processes Prior Period Postings to department fiscal coordinators Carry -forward user -selected pre -encumbrances Carry -forward pre -encumbrances and encumbrances based on user -defined criteria using any element of the financial data classification structure or fields associated with the Appropriation (e.g., appropriation type, fund source) or Fund. Non -selected pre -encumbrances and encumbrances are not carried forward Carry all pre -encumbrances and encumbrances forward Ability to maintain the same encumbrance document number on encumbrances and pre - encumbrances that have been partially liquidated in one fiscal year and carried forward into the next fiscal year. Encumbrances are reported by fund balance reserves and rolled forward to the current year. Keeping prior year funding and tracking fund balance reserve by original budget year separately from the new current year fund balance reserve. Liquidate prior year encumbrances and pre -encumbrances from prior year budget carried forward when encumbrances are either cancelled or paid in current year. 20 20 20 20 20 20 20 200 100 50 50 120 M0 :e 40 1 i I 1 —1 l - 1 1 1 1 1 1 1 1 I I --1 F2-00-14-00-00 R The system shall allow users to specify the level of rounding that occurs in the budget 20 preparation process in reports. F2-00-31-00-00 M/E System has the ability to attach files (e.g., Word, Excel) to budget submissions. 20 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 165 of 418 F2-00-32-00-00 F2-00-33-01-00 F2-00-33-02-00 F2-00-33-03-00 F2-00-33-04-00 F2-00-33-05-00 F2-00-33-06-00 F2-00-33-07-00 F2-00-33-08-00 F2-00-33-09-00 F2-00-33-10-00 F2-00-38-00-00 F2-01-05-04-00 F2-03-02-02-00 F2-03-10-04-00 F2-03-10-05-00 F2-03-10-08-00 F2-03-1 1 -00-00 M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E R M/E R M/E M/E M/E M/E F2-03-12-00-00 M/E F2-03-21-00-00 M/E F2-03-22-03-00 M/E City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 166 of 418 1 1 1 1 %Jp� Repes (R) ShorE Description:„ 3 System has the ability to attach files (e.g., Word, Excel) to budget line items. 20 Purpose 20 Consequences 20 Funding Sources 20 Legal Authority 20 Appropriation Type 20 Appropriation Title 20 Ongoing or One-time 20 User Defined Field #1 20 User Defined Field #2 20 User Defined Field #3 20 The system shall flag funds that have a projected negative fund balance at the end of the year. 20 grant match requirements 20 provides projections of vacancy rates based on historical data 20 Transfer positions 20 Freeze or unfreeze positions 20 Control the number of employees filling a position 20 System will deliver functionality to perform online edit checking and validation to identify when 20 more than one employee is assigned to the same position number. System will deliver functionality to route position change requests online to various staff 20 members for approval. The system shall allow the user to flag positions for inclusion in the position based budget. 20 planned positions, by date 20 I 1 1 1 I I 1 I ! I I I i 1 I l 1 I Requireitnert Numbed 0: ...: Deve�io(prtent .:. "Modifications/EnbanwGdnts ',,,:'Interface' #.k Conversion (G�,al�d Hours h or • YI a r. RIQueray�� Short Desk Ion.. ;�. tt,• v ♦`.d (M 3 3fl 3 }R�✓ �M y� F2-03-23-00-00 M/E The system shall flag budgeted positions that have exceeded appropriations. 20 F2-05-39-01-00 M/E by line item 20 F2-05-39-02-00 M/E in total 20 F2-05-39-03-00 WE by amount 20 F2-05-39-04-00 M/E by percent 20 F2-06-01-00-00 M/E The system shall calculate early retirement incentives and payoff costs. 20 F2-06-05-00-00 R System provides the ability to report and reconcile anticipated operating transfers in/out between 20 departments, funds, sections and programs to ensure that transfers are properly balanced. F2-07-04-00-00 R System generates department budget request that displays base and decision package items. 20 F2-07-06-00-00 R System provides the ability to incorporate textual and other non -financial data on system reports, 20 along with pertinent financial data. F2-00-24-00-00 M/E The system shall automatically load the appropriation and operating budget into the financial 20 system once approved. F2-03-01 -01 -00 WE using the same position information 20 F2-03-01-03-00 WE using the same employee actual information 20 F3-00-02-02-00 F3-00-02-03-00 F3-00-02-04-00 F3-00-02-05-00 173-00-02-06-00 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 167 of 418 M/E Sub -Fund 40 M/E Department 40 M/E Hierarchical Organization (Department, Division, Section) 25 WE Contract 25 M/E Program 25 Re4dli,,4 0)" 1 # # f13 Mod�f nsJl nh menu 1 [n#erFaces {4}, ConversJlon3,,(Ca, and Horis Number($M�O // j/// Rep�xrcSfQueries (R) Short DesCrip#,an Reference I C Rj P/ r�. .. F3-00-02-07-00 M/E Location (e.g., Council District) 25 I I F3-00-02-1 1 -00 M/E General Ledger Account (Expenditure Object, Revenue Source or Balance Sheet Account) 25 F3-00-02-14-00 M/E Function 25 F3-00-02-15-00 M/E Fiscal Month 25 F3-00-02-16-00 M/E Fiscal Year F3-00-02-17-00 M/E User -Defined Field 1 F3-00-02-18-00 M/E User -Defined Field 2 F3-00-02-19-00 M/E User -Defined Field 3 F3-00-06-02-00 M/E Full Accrual basis F3-00-10-10-00 R Breakdown of fund balance into restricted committed assigned and unassigned. F3-00-14-00-00 R F3-01-03-00-00 M/E F3-01-05-00-00 M/E F3-01-06-00-00 M/E F3-01-23-00-00 M/E F3-01-30-00-00 M/E F3-01-31-01-00 M/E F3-01-31-02-00 M/E F3-02-13-00-00 M/E F3-02-15-00-00 M/E City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 168 of 418 1 1 System provides subsidiary ledgers for balance sheet accounts as needed. These subsidiaries must generate reports of open transactions that accumulate to the balance sheet account totals. System allows users to define default data (e.g., cost center, department) for accounting distributions with the ability to override these defaults. System has the ability to electronically attach or reference multiple supporting documents to the journal entry. System has the ability to print documents attached to journal entries. System allows for fields on the journal entry to be configured as either required or optional. System provides the ability for an entry to reference a previously established encumbrance. After the transaction is posted, the referenced encumbrance document should automatically liquidate. support for coding reduction transaction level coding requirement System provides the ability to support workflow processes for recurring transactions. System provides the ability to notify users that recurring transactions are about to generate. 25 25 25 25 200 40 40 20 60 60 20 200 60 60 20 20 $ 0 F3-03-04-00-00 M/E F3-03-05-00-00 M/E F3-03-06-00-00 M/E 173-03-07-00-00 M/E F3-03-08-00-00 M/E F3-03-09-00-00 M/E F3-04-14-00-00 M/E F3-04-15-00-00 M/E F3-04-34-00-00 M/E F3-04-35-00-00 M/E F3-04-37-00-00 M/E 173-04-39-00-00 M/E F3-05-04-07-00 M/E City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 169 of 418 I I I I I I I I I I I I I I Hours System provides the ability to transmit inter/intra-Department billings with line -item detailed 40 charges for review prior to posting. System allows for automatic posting of inter/intra-Department billings after a user specified 40 period of time has elapsed with no response. System provides the ability for the Department receiving charges to establish parameters that 40 determine where items are charged (what fund and cost center is used) while preventing them from changing the account or amount used on the transaction. System provides the ability to send a user -specified notification (e.g., email) back to the 40 originator, if the interdepartment/interfund entries are rejected or a specified period of time lapses, including communication of the correct account distributions to use. System provides the ability to restrict inter -department postings based upon security to 40 authorized users within departments (e.g., fiscal coordinators). System provides the ability to flag an inter -department entry "in dispute" and allow user -defined 40 workflow rules to resolve dispute. System provides a simulation module to determine impact of process changes upon cost 200 allocation activities. System provides the ability to input different cost -driver rates in the cost allocation simulation 200 I module, allowing different rates to be applied over different time periods. System provides the ability to prevent changes to supporting allocation records once the 120 allocation process starts. System provides the ability to compute and use system -generated rates, compare and report 120 past actuals to standard allocations, compute the variance, and calculate new allocation rates for user -specified categories and criteria. System provides the ability to classify costs as direct expense or indirect expense. 120 System provides the ability to maintain the identity for the source of costs and the ability to drill 60 down to the source of costs in an allocation. Department Service Order number 60 F3-07-01-00-00 R F3-07-08-00-00 R F3-07-09-00-00 R F3-07-10-00-00 R F3-07-1 1 -00-00 R F3-07-12-00-00 R F3-07-13-00-00 R F3-07-14-00-00 R F3-07-15-00-00 R F3-07-16-00-00 R F3-07-17-00-00 R F3-07-18-00-00 R F3-07-19-00-00 R F3-07-21-00-00 R F3-07-24-00-00 R F3-07-25-00-00 R F3-07-26-00-00 R F3-07-27-00-00 R F3-07-28-00-00 R City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 170 of 418 Hours System provides ability to trace summarized transactions in General Ledger reports back to 20 detail source documents in other system modules. Statement of Net Assets 20 Statement of Activities 20 Balance Sheet Governmental Funds; Reconciliation of the Governmental Funds Balance Sheet 40 to the Statement of Net Assets; Statement of Revenues, Expenditures, and Changes in Fund Balances -Governmental Funds; 40 Reconciliation of the Change in Fund Balances of the Governmental Funds to the Statement of Activities; Statement of Net Assets -Proprietary Funds; 40 Statement of Revenues, Expenses, and Changes in Fund Net Assets -Proprietary Funds; 40 Statement of Cash Flows -Proprietary Funds; (In -Direct Method) 40 Statement of Fiduciary Net Assets; 40 Statement of Changes in Fiduciary Net Assets 40 Statement of Component Unit Net Assets 40 Statement of Changes in Component Unit Net Assets 40 System presents financial statements on a modified accrual and accrual basis. 40 System provides fund transfer reports, such as inter/intra-fund receivables, inter/intra-fund 20 payables, and inter/intra-fund transfers, that display month and year-to-date transfer information including both the sender and receiver of the transfer. Cash Flow 20 Fund Balance Report- 20 Balance Sheet 20 Income Statement 20 Cash Balance Report 20 A i � ► I 1 i i I � )� ] BUYSPEED ONLINE INTERFACE The purpose of this approach section is to document the high-level design discussions for the BuySpeed Online — PeopleSoft interface. While this section documents a direction and expectation, it should not be considered a restriction or constraint of the final design. It also served as a means to establish a level of costing and staffing. In addition to the functional resources identified in the roles and responsibilities and staffing sections of this contract, there is an additional 540 hours of technical development from CIBER to meet the scope of the interface. The objectives of the BuySpeed — PeopleSoft interface required by the City are: • Improve on the process and steps that characterize the current BuySpeed Online to MARS interface environment • Contribute to improvements in internal controls and reduction of audit issues • Minimize manual steps in related processes • Provide high value, sustainable model • Support transaction visibility The City and CIBER will conduct detailed design activities for the interface early in the project timeline (before October 2012) to facilitate a more complete design of the interface, to understand and establish impacts on the operating environment, and to allow as much project time and resources to be directed to developing the right solution for the City. FUNCTIONAL BREAKDOWN BETWEEN PEOPLESOFT AND BUYSPEED ONLINE Function Account Codes (cost center, fund, gl account) Budget Vendor Master Data Commodity Master Develop Requisition City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 137 of418 Ciber/PSFT Periscope Holdings Incorporated Interface (PHI)/BuySpeed Online Item? • Maintain Valid Account Codes • Receive Valid Account Codes Y • Send updates to BSO nightly • Establishes, maintain budget and rules • N/A N • Receive Vendor Information • Add banking information fields to pass to PSFT Y • Maintains commodity code information N • Create requisition detail N • Issue Req Number Function • Check Budget and Validate Accounts • Approve Requisition Cancel Requisition Develop Purchase Order • Check Budget and Validate Accounts • Approve Purchase Order • Process Change Orders Ciber/PSFT • Provide approve or error message • Create pre -encumbrance in Commitment Control • Maintain requisition number with pre - encumbrance document • Liquidate pre -encumbrance in Commitment Control • Provide approve or error message • Liquidate pre -encumbrance in Comm. Cntrl • Create encumbrance in Comm. Cntrl • Maintain purchase order number with encumbrance • Provide approve or error message • Adjust encumbrance • Route to Fixed Asset Manager for Approval Cancel Purchase Order Liquidate encumbrance in Commitment Control Receive Goods or Services City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 138 of 418 1 1 1 Periscope Holdings Incorporated (PHI)/BuySpeed Online • Issue Call to PSFT passing required information for account validation and budget check • Issue call to PSFT to establish pre - encumbrance • Cancel Requisition • Issue call to PSFT to liquidate pre - encumbrance • Create purchase order item details • Flag item(s) as Asset (if applicable) • Issue Purchase Order • Issue Call to PSFT passing required information for account validation, budget check • Issue call to PSFT to establish encumbrance • Issue call to PSFT passing required information for account validation and budget check • Issue call to PSFT to adjust encumbrance • Route Asset POs for Asset Mgr approval • Cancel PO • Issue call to PSFT to cancel PO • Create Receipt • Capture required asset fields (if applicable) • Capture if receiving into inventory Interface Item? Y Y Y N Y u Y N Y N I I I I I I I I I I I I I P I 1 I 1 E 1 1 I 1 I a I I 1 I l i�an . Reference F3-07-29-00-00 F3-07-30-00-00 F3-07-36-00-00 F3-07-38-00-00 F3-08-02-00-00 F3-08-03-00-00 F5-00-02-01-00 F5-00-03-00-00 F5-00-10-00-00 F5-01-05-00-00 F5-01-07-00-00 F5-01-12-06-00 F5-01-13-00-00 F5-01-15-00-00 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 171 of 418 R R R R M/E M/E M/E Capitalize assets based upon a user -specified criteria, including amount threshold by asset type. 20 M/E System provides the ability to allow modification of asset capitalization and control rules per City 20 and department policy, as necessary (i.e., no hard coding of rules). R System provides the ability to generate standard governmental fixed asset reports and user- 40 defined fixed asset reports in compliance with GASB 34 and 51, and report on all fixed asset balances in the standard CAFR format (with supporting notes and schedules). M/E System provides the ability to identify users of assets, in addition to recording property 20 custodian. M/E An asset number is made up of two parts, the first part is a user -definable prefix and the second 20 part is a system generated sequence number. M/E Multiple Organizational Ownership Info. (including assets loaned to/from other entities) 20 M/E System allows user defined fields to be either entered as free form text or selected from a 20 configured drop -down list. M/E System is able to link component units (parent/child relationship) whereby each component 20 maintains a financial life of its own. R qwu1et»e�1tt ewelapment Modrfrcations/Enhancernents.(M/E); Interfaces (1), Conversion (C), and Hours s j} y ttlrn�br(s) Ither s Ype R,fere0 f Short RepoQuer�es (R) Descrrptron „(M/,I�G,Ftj F5-01-21-00-00 M/E In addition to asset information listed previously, system maintains detailed property information 20 required to identify, properly account for, and safeguard City lands, including, but not limited to the following: F5-01-21-01-00 M/E Legal description per survey 20 F5-01-21-06-00 M/E Fair market value (e.g., for donated land) 20 F5-01-21-08-00 M/E Deed information 20 F5-01-27-00-00 M/E System allows for decoupling assembled asset components and reassembling them in a 20 different configuration (such as moving thermal imager from a fire apparatus and assigning it to a different one). F5-01-28-00-00 M/E System provides the ability for commodity line items to contain the following data items, 20 including but not limited to, the following data elements: Fixed asset Indicator (new, replacement, or enhancement; if replacement or enhancement, need existing tag number). F5-01-29-00-00 M/E System provides the ability to capture a fixed asset indicator (determine whether commodity is 40 an asset based on dollar amount and expenditure object code). F5-01-34-00-00 M/E System allows "placed in service date" to be changed for assets that require assembly before placing in service. 120 F5-01-35-00-00 M/E System evaluates purchase order line items and applies the following edit: If the unit price is 40 greater than the capitalization threshold and the expenditure account is not capital outlay and the commodity code indicates that it may be a fixed asset, then the transaction should produce a warning if the fixed asset indicator is not selected F5-02-02-02-00 M/E Reporting individual 10 F5-02-02-04-00 M/E Description of circumstances surrounding the disappearance/disposition 10 F5-02-02-05-00 M/E Steps taken to locate item 10 F5-02-02-09-00 M/E Police report information (multiple jurisdictions) through file attachments 10 F5-02-03-00-00 M/E System tracks estimated useful life 20 F5-02-04-00-00 M/E System records grant asset dispositions and proceeds of sales which integrate with the Grants 20 Management module. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 172 of 418 a 1 I I I I a 1 I 1 i I I 1 l i i I 11 F5-05-06-00-00 TP System is able to generate customized bar-coded labels for asset identification (inventory 20 control and property number tags), including building, floor and room information. F5-05-08-00-00 TP System provides the ability to be updated real time from bar code scanners. 20 F5-07-04-00-00 R System provides the ability to perform lease/purchase comparative analyses. 20 F5-08-02-00-00 M/E System captures insurance information for fixed assets (insured value, roof type, construction 20 information, square footage, insured contents, etc.) F5-08-03-00-00 M/E System should support hyperlinks to the vendor's web site to reference asset maintenance and 20 warranty information. F5-08-05-00-00 M/E System provides the ability to notify of warranty agreement expiration. 20 F5-09-02-00-00 R System is able to generate standard governmental fixed asset reports and user -defined fixed 40 asset reports in compliance with GASB 34 and 51. F5-09-03-00-00 R System can display or print a report of surplus property, including each item's history. 20 F5-09-06-00-00 R System provides a walk -forward of fixed asset balances by asset type. 20 F5-09-07-00-00 R System can produce a report that facilitates reconciliation to physical inventory counts. 20 F5-09-08-00-00 R System provides a report of all property changes as of a user specified date 20 F5-09-09-00-00 R System provides a property insurance schedule that displays the property value and associated 20 insurance amount. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 173 of 418 Reeuiirement Develop, ent lVl c Cc ttanslEnhancements (Mfg tnterEaces (I), DQnversion (G), and Hours i kb F{S} t F � l4BF y h TOF Yp , y RepartsfQueries (R Sham Descr1ption=: �€ � �V .. .. .. IN ki F6-01-01-13-00 M/E Managing Department 20 F6-01-01-14-00 M/E Managing Department Contact 20 F6-01 -01 -15-00 M/E Sponsoring Department 20 F6-01-01-16-00 M/E Sponsoring Department Contact 20 F6-01-01-21-00 M/E Community Facilities Agreement (CFA) flag 20 F6-01-01-27-00 M/E Start point (linear projects) 20 F6-01-01-28-00 M/E End point (linear projects) 20 F6-03-03-00-00 R System provides the ability to forecast budgets for multi -year periods. 20 F6-03-1 0-01 -00 R between appropriated budget and total (revised) budget 20 F6-05-03-04-00 M/E Based off planned amounts 20 F6-06-01-00-00 R System provides the ability to identify projects lacking financial activity for a user -defined period 20 for possible closeout. F6-06-03-00-00 M/E System provides the ability to support closing multiple projects at once. 20 F6-06-05-00-00 M/E System prevents final close for a project if revenues and expenses are not equal. 20 F6-06-06-00-00 M/E System prevents final close for a project if estimated revenues and the expenditure budget are 20 not equal. F6-06-07-00-00 M/E System prevents final close for a project if estimated revenues do not equal actual revenues and 20 the expenditure budget does not equal actual expenditures. F6-06-1 1 -00-00 M/E System prevents final close of a project if any balance sheet account has a balance. 20 F6-06-12-00-00 M/E System prevents final close of a project if any encumbrances are outstanding. 20 F6-08-01-00-00 M/E System provides the ability to utilize workflow to notify project administrators and other users (at 20 user -defined time periods) of project milestones (expiration dates etc.). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 174 of 418 I I I I I I I I I I I I I I I k I I I Nu F6-10-01-02-03 F6-10-01-05-02 F6-11-02-00-00 F7-00-03-00-00 F7-00-04-00-00 F7-00-08-00-00 F7-00-1 1 -00-00 F7-00-13-00-00 F7-00-14-00-00 F7-00-15-00-00 F7-00-18-00-00 F7-00-19-00-00 F7-00-21-00-00 F7-01 -01 -00-00 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 175 of 418 R R R R x +. R Systemprovides the ability to perform roll -ups and drill -downs at various levels within the coding 20 block hierarchy, including the grant hierarchy. M/E System provides coding reduction of the grant accounting distribution for other elements of the 40 coding block (e.g., entering the grant number infers the fund). R System provides the ability to produce the Schedule of Expenditures of Federal Awards and 20 State Financial Assistance (for the Single Audit Report). R System provides the ability to generate reports by grant attributes, such as the Catalog of 20 Federal Domestic Assistance (CFDA) number. R System provides the ability to report sub -recipient activity by grant. 20 R System provides the ability to summarize grant activities by grantor for user -defined time 20 periods. R System provides the ability to modify grant reports for federal and city reporting purposes 20 without programming knowledge. R System calculates outstanding grant award balance. 20 M/E System provides the ability to perform mass updates to grant reference data. 20 R System provides the ability to track how interest allocations are spent. 20 M/E System will facilitate notification of grant / grant phase applications, approvals and awards via 20 workflow. Hours F7-04-01-08-00 M/E F7-06-01-00-00 M/E F7-06-05-00-00 F7-06-05-01-00 F 7-07-02-06-00 F7-07-02-14-00 F7-07-02-15-00 F7-07-02-19-00 F7-07-02-22-00 F7-07-02-24-00 F7-07-02-29-00 F7-07-02-31-00 F7-07-02-32-00 F7-07-02-38-00 F7-07-02-41-00 F7-07-02-42-00 F7-07-02-43-00 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 176 of 418 M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M&C number Grantor Program Classifications (e.g., IDIS Activity Number) Letter of Intent to Award Date Approved Contract Date Release of funds Date (to prevent expenditures before this date) Department or division contact and phone number (multiple) validated from the Employee table City Secretary Contract Award Number Amounts of In -kind matching funds (multiple) Amounts of Maintenance of Effort (MOE) (multiple) Description for each of the matching funds and Maintenance of Effort amounts Grant Type (e.g., Federal, state, etc.) Pass -Through Agency Pass -Through Agency Contact Information (name, phone, address) Funding Source - user defined (Federal grant, Foundation grant, city, Other, etc) 10 10 10 10 10 10 10 10 10 10 10 10 10 10 I II I I I I 1 I I I I I I I I I I # # # j 1 1 I I I 1 1 I 1 I l I i I City of Fort Worth 1 CIBER, Inc. Professional Services Agreement Page 177 of 418 Requirern rtt Development j Modificatiohi Enhancements (M/E), Interfaces (ly, Conversion (C),"and Hours Number(s) or Other Reference Type (M/E,I,C,R) Reports/Queries (R) Short Description . > - F7-12-20-00-00 WE System provides the ability to track receipts and expenditures of program income by grant and 40 user -defined time period. F7-15-01-00-00 R System provides the ability to group city accounting structures into grantor expense categories. 20 F7-15-02-00-00 R System provides the ability to group city program or organizational classifications into grantor 20 groupings. F7-16-06-01-00 M/E Outstanding Retainage 10 F7-16-06-02-00 M/E Unbilled Expenditures 10 F7-16-06-03-00 M/E Outstanding requests for reimbursement 10 F7-16-06-04-00 M/E Open Procurement Encumbrances 10 F7-16-06-05-00 M/E I Revenues in excess of expenditures for a grant 10 F7-16-06-06-00 M/E ( Grant funded positions tied to the grant 10 F7-17-01-00-00 M/E System provides the ability to support interfaces to Federal or State grant systems so that 20 required grant program and financial reports can be automatically exchanged. F7-17-01-01-00 M/E I IDIS 20 F7-17-01-02-00 M/E DRGR 20 F7-17-01-03-00 M/E Nortridge Loan Management System 120 F7-17-02-00-00 M/E System provides the ability to interface CFDA information for Grantors from the federally 40 provided catalog. F7-17-03-00-00 M/E System interfaces grant awards to M&C tracking system (Ecouncil) 40 F8-00-03-00-00 R System provides the ability for customer invoices, statements, and other customer 20 communications to be changed to comply with ADA requirements (allowing for changes to font, layout, etc). F8-03-05-00-00 M/E City of Fort Worth / CI$ER, Inc. Professional Services Agreement Page 178 of 418 System captures a reason for deactivating a customer 20 I7 I w I I I I I ! I I I I 1 I I I I ' a I Requiiremea "` Madificstions/Enhancements` l4� 1[ +t6rfaces (1), Conl erstQn (C), artd Hours Numbers or R Repors/Queries (R Short ©escr�ption F8-03-06-00-00 WE System provides the ability to prevent duplicate customer records. 40 F8-03-08-00-00 M/E System provides the ability to maintain an on-line audit trail of changes made to the customer 20 master. F8-03-09-00-00 M/E System maintains a history of changes to the customer record (old value, new value, user, date). 20 1 F8-03-12-07-00 M/E TAD account number 20 F8-03-12-09-00 WE Default Account Receivable Control Account 20 F8-03-12-10-00 M/E Alternate open -item managed balance sheet accounts (such as Escrow) 20 F8-04-08-00-00 R System provides the ability to customize the printed invoice/adjustments form to include any field 20 entered in the invoice or adjustments transaction entry screen. F8-04-12-00-00 WE System provides the ability to change account coding on invoices through a mass change 40 functionality, with audit trail and proper security. F8-04-14-00-00 M/E System provides the ability to flag invoices for "special handling" (e.g., hand -delivery) with the 20 ability to enter comments (such as a time to deliver). F8-04-19-01-08 M/E Account Receivable control account (defaults from customer record, can be overridden with 20 1 alternate from customer record) F8-04-20-00-02 M/E By customer or range of customers 20 F8-04-20-00-03 M/E By invoice or document number or range of numbers 20 F8-04-20-00-04 M/E By any element of the financial data classification structure 20 F8-04-23-00-00 R System provides the ability to generate customer statements by department or organizational 20 sub -level (e.g. fund, subfund, etc.). j 178-05-01-00-00 WE System provides the ability to import credit/debit card transaction files from a third party. 40 F8-05-05-07-00 M/E Driver's License (encrypted) 40 F8-05-05-13-00 M/E User -Defined Field 1 20 F8-05-05-14-00 WE User -Defined Field 2 20 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 179 of 418 R uirernent Development Modifications/Enhancements M/E), Inte faatis(l), Conversion (C), and Hours hiurnber(s) vrJther Type .. Reports/Querbes (R) Short Description, teference' (MIE,IG,R) F8-05-06-00-00 M/E System provides the ability to supply an outbound interface for receipts in order to update 40 multiple specialized third -party billing systems whose functionality cannot be implemented in an ERP billing system. F8-05-07-00-00 R System provides the ability to support bar code or scan line printing on envelopes and 20 remittance advices to aid in remittance processing. F8-05-09-00-00 TP System provides the ability to utilize a predefined interface for bar code or scan line information 20 which can capture carry forward invoice information to the payment receipt. F8-05-13-02-00 M/E Check, including capture of ABA number 20 F8-05-13-03-00 M/E Check, including capture of Account number 20 F8-05-13-06-00 M/E Money Orders, including capture of Bank Code 20 F8-05-26-00-00 M/E System provides the ability to associate attachments (e.g., Word, Excel, or scanned documents) 40 with customer payment transactions. F8-06-05-07-00 M/E Driver's License (encrypted) 40 F8-06-05-13-00 M/E User -Defined Field 1 20 F8-06-05-14-00 M/E User -Defined Field 2 20 F8-07-03-05-00 R Generate reports by underlying accounting distributions.. 20 F8-07-04-00-00 M/E Record a pre-printed deposit slip number to support subsequent automated bank reconciliations 20 for deposit activity F8-08-04-00-00 M/E System provides the ability to merge two different customer records and maintain their 20 associated history (e.g., able to review activity for both old customers under the current customer account. F8-08-05-05-00 M/E System has the ability to support 4 levels of dunning notices. 20 F8-08-05-06-00 M/E System supports different dunning timing schedules, by department. 20 F8-08-1 1 -01 -00 M/E Interest -free periods 20 F8-08-11-02-00 M/E Installment payments 20 F8-08-11-03-00 M/E Interest deferrals or suspensions of interest payments 20 City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 180 of418 1 I I I I I I } i I i I 1 i t I + I I I I I} # I 1 ! U I i I 1 I I l I 1 I I Requirement I tDeveloprrient IVlt dill > fi ncements (WE)� Interfaces {I)t Converslrsn (C), and ��� Flours Numbers) or Qther Type ReporkslQuer{es (R) Short ©escrlption, / Reference*(NC/E,I,C,R) �= F8-08-12-00-00 WE System provides the ability to optionally generate an automatic refund transaction on a specified 20 refund date to issue a payment to the customer. F8-08-13-00-00 M/E System provides the ability to optionally generate a refund of revenue to a non -invoiced 40 customer (e.g., grant overpayments), with proper approvals. F8-1 0-01 -00-00 M/E System provides the ability to record dishonored revenue payments (i.e., NSF) by name, 20 account number, deposit number, date and amount F8-10-04-00-00 R System provides a standard communication/letter to notify the customer of the NSF status. 20 F8-10-05-00-00 M/E System provides users the ability to restrict incoming payments from a customer to a pre -defined 20 tender type or types due to NSF check status (e.g., no checks). F8-10-06-00-00 WE System provides a notification to users that a customer has an NSF check outstanding when 20 processing receipts. F8-10-07-00-00 WE System restrict a customer to a specific type of payment 20 The development items below are considered part of the Phase IIC — Procurement and Inventory Option and will be incorporated into scope upon execution of the option. 0101 �. «u d ,s j , . .... .. ,. ,,, , . , •. .. ,,,, , s. ,. .s P1-00-07-00-00 WE System provides the ability for a user to set an automatic renewal flag for recurring purchase 20 orders and releases for contracts P1-00-08-00-00 M/E System produces a list of contracts or releases that are eligible for renewal 120 P1-00-09-00-00 M/E System allows users to select contracts or releases for renewal and creates the subsequent 40 document P1-00-10-00-00 M/E System provides the ability to prompt for automatic renewal requisitions for blanket orders based 40 on percent or dollar values consumed. P 1 -00-11 -00-00 M/E System provides the ability to copy one or multiple lines of field values to the next/subsequent 40 line(s) and change one or more field value elements when using input screens for all purchasing documents P1-00-16-00-00 R System provides the ability to capture and report user defined performance data on measures 20 and indicators of Buyer activities City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 181 of418 Requirement DOV610prn' ' "' ��? # Nlt dr ications/Enhanciimatits`'(M/E) 'tntbrfaces (I), Gpnversion (Cj;;and Hours Nurrtber(s) ar-C1t#terrye x� y R Queries R Short Descri tion Reference ep° {) p �t / P1-00-17-00-00 M/E System provides the ability for the Buyer to view a worklist, including the details of a 20 procurement and the estimated required processing time, or any similar pre -defined performance metric P1-00-18-00-00 R System provides the ability to show contract and spend data for the buyer's commodities or 20 contracts P1-00-23-00-00 M/E System supports periodic updates of commodity codes based on externally provided files. 40 P1-00-28-00-00 M/E System provides the ability to automatically assign a sequential number, with or without a user- 20 defined prefix and/or suffix, to each type of procurement transaction. P1-01-09-00-00 M/E System provides the ability to automatically generate a requisition to renew a contract based on 20 a user -specified number of days before the contract expires. P1-01-10-00-00 M/E System provides the ability for electronic notifications to be sent to the respective purchasing 20 agent informing him/her that the requisition has been generated and is pending his/her action. P1 -01 -17-00-00 R System provides the ability to maintain a schedule that can cause an electronic notification to be 20 sent to a purchasing agent's supervisor if the purchasing activity is not within the processing time assigned to the requisition. P1-02-01-05-00 M/E Requestor phone number 20 P1-03-01-03-00 M/E Buyer phone number (optional) 20 P1-03-01-03-01 M/E Recycled goods indicator 20 P1-03-01-03-02 M/E Recycled goods percentage 20 P1-03-01-03-09 M/E Suggested vendor email 20 P1-03-01-03-10 M/E Suggested vendor address(es) 20 P1-03-01-03-11 M/E User Defined Field 1 20 P1-03-01-03-12 M/E User Defined Field 2 20 P1-03-01-03-13 M/E User Defined Field 3 20 P1-05-01-02-00 M/E Posting of the solicitation on the City's Website. 40 P1-05-01-06-02 M/E Web Site Posting 40 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 182 of 418 Req'uiremen Development Numbers) or Othe z° F"ype Reference T v (M/E,I,C,R) P1-08-01-06-00 M/E d Mours Vendor has previous history of responding on a specific commodity (even if no longer 40 registered) Vendor performance 40 System provides the ability to track and report which solicitations are sent to or downloaded by 20 which vendors. P1-11-02-00-00 M/E System provides the ability to download solicitation responses in industry standard file formats 20 (e.g., Microsoft Excel, Access, etc.) for evaluation and then be able to upload back to the system. P1-11-03-03-00 M/E pre -grouped line items 40 P1-13-03-00-00 M/E System provides the ability to interface with M&C approval process to record M&C number and 20 date on the award. P1-13-09-00-00 M/E System provides the ability to track vendor protests from inception to conclusion and to suspend 40 the procurement until the protest is resolved. u, tracts .� ,, ._ ,,., C ff "' .._::: m ��Eas£ YAN ,� ���� M� 5 �4 T# . - 4Y ./Sf k..t ,.tea .. F'.,. ... - um .. .'�,.fY P2-00-02-00-00 M/E System provides the ability for assignment of a unique purchase order number through system- 20 generated means, with a prefix (for purchase order type - blanket, emergency, contract), fiscal year, and sequential number. P2-00-09-00-00 M/E System provides the ability to capture a fixed asset indicator (determine whether commodity is 40 an asset based on dollar amount and expenditure object code). P2-00-14-17-00 M/E Department -specific reference number 20 P2-01-02-00-00 M/E System provides the ability to track the number of contract renewals (total, exercised, 20 remaining). P2-01-08-04-00 M/E support multiple option periods 20 P2-01-13-08-00 M/E Commodity Class 20 P2-01-13-10-00 M/E Renewals (authorized, used, and available) 20 P1-08-01-09-00 M/E P1-09-03-00-00 M/E City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 183 of 418 requestors and purchasing agents regarding purchases that may be covered by existing contracts. P2-01-22-04-00 WE Sub -Contractor performance P2-02-01-10-00 M/E Origin of procurement request (Department & contact info) P2-02-01-13-00 WE Confirming PO (yes/no) P2-02-01-14-00 M/E Confirming Order Date P2-02-01-30-00 M/E Fiscal Year P2-02-02-00-00 M/E System can be configured to conditionally require a field be populated when pre -defined conditions are met (e.g., when a PO total is greater than $25,000, then the field that captures the M&C reference should be filled.) P2-03-01-19-00 M/E Recycled goods indicator P2-03-01-20-00 M/E Recycled goods percentage P2-03-01-21-00 M/E Hazardous material indicator i P2-03-01-23-00 M/E User Defined Field 1 P2-03-01-24-00 M/E User Defined Field 2 P2-03-01-25-00 WE User Defined Field 3 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 184 of 418 1 1 1 1 1 1 1 1 1 1 1 20 20 20 20 20 20 20 20 20 20 20 all I i . a a I a # a I - 1 I I I a P2-04-03-06-00 M/E P2-04-03-08-00 M/E P2-04-03-09-00 M/E P2-04-03-12-00 M/E P2-04-03-17-00 M/E P2-04-03-19-00 M/E P2-04-03-20-00 M/E P2-04-03-22-00 M/E P2-04-03-26-00 R P2-04-03-27-00 R P2-04-09-00-00 M/E P2-04-10-00-00 1 M/E P2-05-05-02-00 I M/E P2-05-05-04-00 M/E P2-05-13-13-00 R P2-05-13-14-00 R P2-08-05-00-00 M/E P2-08-1 1 -00-00 M/E City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 185 of 418 (G);"and" Hours Distributor name and number 20 Recycled content percentage 20 Recycled content type 20 Manufacturer URL 20 Geographic designation (City, State Highway District, other) 20 Shipping and handling requirements 20 Packaging information 20 UPC code 20 Accumulators for dollar amount purchased for the month, quarter, fiscal year-to-date, prior fiscal 20 year Accumulators for quantity purchased for the month, quarter, fiscal year-to-date, prior fiscal year 20 System provides the ability to attach files in industry standard formats to commodity records 20 (e.g., gif, jpg, xls, doc, URL link, etc.). System provides the ability for an online interface for vendors to update and maintain catalog 20 data/content. Create a single purchase order with line items from multiple purchase requisitions/solicitation 40 Create multiple purchase orders with line items from multiple purchase requisitions/solicitation 40 vendor MWBE status 20 requisitioner 20 System provides the ability to create and process individual POs under an existing manual 40 encumbrance. System provides the ability to configure tolerances by order type (e.g., a percentage or a 40 specified dollar amount) whereby a purchase order amount may exceed or be below the purchase requisition and still be processed, provided sufficient spending authority exists; the tolerance functionality is optional. P2-09-02-00-00 P2-09-12-01-00 P2-09-12-02-00 P2-09-12-03-00 P2-09-12-04-00 P2-09-12-05-00 P2-09-13-00-00 R R R R R R TP P2-10-04-16-00 R P2-10-04-26-00 M/E P2-10-07-00-00 M/E P2-10-14-00-00 M/E P3-00-05-00-00 M/E P3-00-08-00-00 M/E P3-01-01-03-00 M/E P3-01-01-04-00 M/E City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 186 of 418 IAA ct�fl+s�at��»s/Enhancements (MIE)i Interfaces, "and Hquprsy ReportstQueries (R) Short t 4& a System provides the ability to accept, process, and report/inquire on over and under receipts, 20 within pre -established business rules. Compliance with delivery requirements 120 Condition of goods 120 Rejection of goods 20 Over and under shipments 20 Commodity substitutions 20 System provides the ability to support barcode technology to be used to capture receipt 20 information. Previous quantity invoiced 20 Retainage Terms 20 System provides the ability to document comments and resolution to disputes. 20 System allows users to determine whether payment methods carried forward from the purchase 20 order can be changed. System provides a report of potential duplicate invoices. 20 qME System provides the ability to select a commodity and display to the end user all vendors that 40 have registered or that have contract(s) for that commodity. The end user should have the ability to drill -down on the contracts for further item information. 40 System provides the ability to maintain an on-line audit trail of changes to the commodity master 20 file. Ability for vendors to pay registration fees via a credit card 40 For manual payments for registration, the registration will be placed in suspense until the 40 manual payment is successfully processed and City approval is granted. I I I I I 1 I t ! I I 1 f i 1 I 1 I 1 1 1 1 1 1 1 1 - 1 !( 11 1 1 ! P3-01-04-00-00 P3-01-05-01-00 P3-01-05-02-00 P3-01-05-03-00 P3-01-05-04-00 P3-01-05-05-00 P3-01-05-06-00 P3-02-01-07-00 P3-02-01-08-00 P3-02-01-09-00 P3-02-01-23-00 P3-02-01-25-00 P3-02-01-36-00 P3-02-01-37-00 P3-03-02-06-00 P3-03-03-00-00 P3-03-05-00-00 P3-03-06-00-00 P3-03-09-00-00 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 187 of 418 M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E M/E LIFAIl0 u0:4 M/E Modrficatians/ hanctetatl1�/Elraker#caes(I)> ConrersiQ2n (C), and Hours ,Ydi3 3i i �i j 1 3 r a 51 Rears Q efyes (fib Sham ©�ascriptiori" System provides the ability for notices to vendors based on a user -specified number of days 20 prior to registration expiration and after expiration. Name Change 20 Tax ID Number 20 DBA Name 20 Factoring (temporary Pay -To) 20 Assignment (permanent Pay -To) 20 Principals/Ownership Information 20 Registration valid date on 20 Registration valid date off 20 Registration reinstatement date 20 Multiple Methods of Payment (check, ACH, P-Card, etc.) 20 Hold Reason and Hold Source (department level) 20 W9 received (yes/no) 20 Date W9 received 20 MWBE View 20 System provides the ability to permit multiple addresses to be assigned to a specific address 40 type for a specific vendor (e.g., multiple ordering addresses, invoice addresses, etc.). System provides the ability to track vendor history, to include date added or inactivated and 20 reason. System provides the ability to deactivate vendor from vendor listing by date with reason. 20 Historical data should be retained. System provides the ability to maintain an on-line audit trail of changes to the vendor master file 20 including date, time, and user, old and new values. Ryan}�wirer" >� Oevelppmnt 'd'xY Nu r e %» 133-03-11-00-00 M/E P3-04-02-01-00 M/E P3-04-02-02-00 M/E P3-04-02-03-00 M/E P3-04-02-04-00 M/E P3-04-02-05-00 M/E P3-04-02-06-00 M/E P3-04-04-06-00 M/E P3-04-04-07-00 M/E P3-05-05-00-00 M/E P3-05-06-00-00 M/E P3-05-07-00-00 M/E P3-05-08-00-00 M/E P3-05-12-06-00 M/E P3-05-17-04-00 M/E P3-05-17-07-00 M/E P3-05-17-08-00 M/E P3-05-17-09-00 M/E City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 188 of 418 od + at ans% han e e it = lVlflE ;Interfaces (l}, C�n�Vers�on (C1,46d Hours / pe Short Desariptto x .. . ,. , .fir, .. •., ..,.;, . � . ,,. �x� x System provides automated notification to specified users (e.g, originator, buyers and vendors) 20 of vendor name changes. Description of the problem/complaint 80 History (including content) of all related correspondence 40 System -generated email message or form letter (if no email address or invalid email address) to 40 be sent to vendor and copy to the department that submitted the complaint. A second letter will be automatically generated if a response from the vendor is not received 40 within a user -specified number of working days Vendor response 40 Resolution (electronically notify vendor and department) 40 complaints and resolution 20 specific solicitations downloaded 20 System must support automatic e-mail notification to registered vendors that matches a posted 20 bid NIGP code. Vendor e-mail message must include a link to the bid on the public procurement web site. System must allow a user to manually customize and send a message, via the City's e-mail 20 system, to registered vendors that match a NIGP code(s), including attachments. System must allow a user to manually customize and send a message, via the City's E-mail 20 system, to registered vendors based on vendor attributes. System must have the ability to exclude e-mail message to vendors who have been suspended, 20 inactive or disbarred. Category type (i.e. IT, City wide contract, Prof. services etc.) 20 Job title 20 E-mail address 20 Manager name 20 Address 20 I 1 I I I I I I I I I. ! X I I Recjt��"�' De umber(q S her Reference P3-05-17-10-00 M/E P3-05-17-1 1 -00 M/E P3-05-17-12-00 M/E P3-05-17-13-00 M/E P3-05-17-18-00 M/E P3-05-17-25-00 M/E P3-05-17-26-00 M/E P3-05-17-27-00 M/E P3-05-21-00-00 M/E P3-05-45-00-00 R P3-05-54-01-00 R P3-05-54-02-00 R P3-05-54-03-00 R P3-05-54-05-00 R P3-05-54-06-00 R P3-05-54-07-00 R P3-05-54-08-00 R P3-05-54-09-00 R P3-05-67-00-00 M/E P3-06-01-00-00 M/E P3-06-02-00-00 R City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 189 of 418 Mndfio��isfnhancemnts>{MfE) lnteriaces {t), Convert (C), and; Hours > Repa�rksll�afies {R) Short Description,; City 20 State 20 Zip code 20 Agency Name 20 Agency type 20 URL 20 Agency procurement officer (APO) name(s) 20 APO bid approval authority (i.e. yes/no) 20 System must support integration of external applications with bid solicitation information. 20 System must provide functionality to search, display and print audit logs for a specific bid 20 Listing of vendors notified for a bid and/or matching NIGP code(s) 20 Summary listing of registered vendors matching specific NIGP code(s) 20 Detailed registered vendor profile listing matching specific NIGP code(s) 20 I Listing of registered vendors by attributes 20 Listing of bids by Fiscal Year 20 Listing of bids by agency by data range 20 Listing of bids by type 20 Listing of purchasing agent/buyer, APOs and users by agency or all agencies 20 System must provide the capability for the City to publish vendor notifications to the public 40 procurement web site. System provides the ability to report the percent of recycled or other environmentally -sustainable 20 content of purchases by item code, by date range, and by department. System provides the ability to report Small and Minority -owned business/Other Targeted 20 businesses solicitation participation by pre -identified criteria. R quiremsnt rpmnni£ % y N Mipdrficatiosts/Enhancements (M/E)� Interfaces (1), Conversion (C), and Hours Number(s) or t"t z,Y, RepoctsfQueries (R) Short ion Reference (NIIE„ E M.: P3-06-03-00-00 R System provides the ability to maintain and report/inquire on usage statistics on all commodities 20 ordered and purchased, subject to user -defined parameters. P3-07-08-00-00 M/E System provides the ability for workflow for card issuance approvals. 20 P3-07-09-00-00 M/E System provides the ability to export contract vendors information to the bank card issuer, to 40 facilitate authorization strategies. P3-07-18-00-00 M/E System should support the ability for users to apply for Purchase Cards online. 40 P3-07-29-00-00 M/E System should allow the scenario where the Pcard Administrator or Coordinator needs to 20 approve all Purchase Card purchases. P3-07-49-00-00 M/E System should interface with PaymentNet application so that invoices paid by P-Card do not 20 also post via the PaymentNet application. Inve ,xN111 IM-00-03-01-00 TP Provide a pre -defined interface to accept and record bar-coded/RFID data from receiving N/A documents and shipments IM-00-03-02-00 TP Ability to recognize SKU and commodity codes via bar-code technology N/A IM-00-03-03-00 TP Ability to capture product information during inventory picking N/A IM-00-03-04-00 TP Ability to capture product information when performing physical inventories. N/A IM-00-12-00-00 M/E System provides the ability to create and route electronic forms for approval (e.g., approval 20 notification and reporting for write-off of damaged, non-moving, or obsolete inventory). IM-00-22-00-00 M/E System provides the ability to support electronic approval for goods receipts, issues, and other 20 related inventory functions. IM-00-28-00-00 M/E System provides the ability to attach hyperlinks on the inventory item records (i.e., Items with 20 hazardous material indicators linked to the MSDS). IM-01-18-00-00 M/E System provides the ability to define default warehouse views for users (i.e., users are restricted 20 to using certain warehouses based on department, etc.). IM-03-04-00-00 M/E System provides the ability to place a cap on the quantity and dollar amount of an item that can 40 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 190 of 418 I' 1 1 1 I I I i I Hours be issued to a requestor during a specified time period. IM-03-05-00-00 M/E System provides the ability to override caps on items, with proper authority. 40 IM-03-14-00-00 R System provides the ability to report the frequency that items are placed on back -order. 20 IM-03-15-00-00 M/E System provides the ability to record a comment regarding back -order information. 20 IM-03-16-00-00 M/E System provides the ability to record anticipated delivery date for back -ordered items and notify 20 users when delivery date is imminent. IM-03-17-00-00 M/E System provides the ability to perform back -order processing with manual or automatic release 20 or cancellations, and notification sent to requestor. IM-04-09-00-00 R System provides the ability to automatically notify personnel before the item or lot will expire. 20 IM-05-09-00-00 M/E System provides the ability to charge restocking fee to the requesting department for all or some 40 of the items returned to inventory. IM-06-16-04-00 M/E Distributor's number 20 IM-06-16-08-00 M/E Unit of Measure 20 IM-07-04-00-00 R System provides the ability to generate a report on required spare inventory parts and cross 20 reference substitute parts and equipment. IM-07-07-00-00 R System provides the ability to generate reports on warranties. 20 IM-07-08-00-00 R System provides the ability to generate adhoc reports on active/inactive inventory records with 20 various calculations defined by department criteria. IM-07-10-00-00 R System provides the ability to track and report on inventory funded by grants separately than 20 inventory funded by operating funds in the same location. I M-07-1 1 -00-00 R System provides the ability to create a report, by user defined criteria, that will show non- 20 inventory items received to help determine whether they should be inventoried. IM-07-12-00-00 R System provides the ability to generate adhoc reports on any item information field and any 20 transaction data field. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 191 of 418 Exhibit G.5: Initial Additional Reportinq Requirements In addition to the Enhancements listed in Exhibit G.4: Initial Enhancement Scope identified with a Development Type "R". The following list of Reporting Requirements comprises additional initial scope for the ERP Phase II Project. Any overlap between the Initial Enhancement Scope and the Initial Additional Reporting Requirements will be resolved in the Final Custom Development List and Unit Test Plan which will represent the final development scope for the project. Below is a list of reports that were identified in Appendix K of the RFP: ID Report Title DesCrptlion 1 Detailed Expenditures by Source Report that lists expenditure accounting information with Vendor (across all Financial Data Classification Structure elements) and combines it with support from various sources (Procurement, P-Card, Travel or General Ledger) with, as appropriate, vendor and commodity information. 2 Requested elements of the A detailed list of transactions for requested combinations Financial Data Classification of the Financial Data Classification Structure to support Structures, allowing for budgetary, encumbrance and actual research. Users summarization and drill -down should be able to sort and sum at run-time and should be capability. able to collapse and expand hierarchical structures as well. 3 Revenue and Expenditure Report Report that summarizes estimated and actual monthly, for Projects year-to-date and inception -to -date revenue and appropriations, expenditures and encumbrances/commitments for project funds. 4 Revenue and Expenditure Report Report that summarizes estimated and actual monthly, for Operating Funds year-to-date revenue and appropriations, expenditures and encumbrances/commitments for operating funds. 5 Revenue and Expenditure Grant Report that summarizes monthly, year-to-date and Fund Report inception -to -date appropriations, revenues, expenditures and encumbrances by Grant for reporting purposes. 6 Detailed Department Transaction Report that provides totals for: the number of invoices Activity Reports paid, number of credit card transactions, number of office supply orders. This report is used for business planning preparation and Annual Report. 7 Income Statement 8 Procurement Card Expenses 9 Detail Trial Balance 10 Available Funds Inquiry City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 192 of 418 Income statement by fiscal period by fund for different elements of the financial data classification structure. Rolling 12-month expenditure report by Vendor by Department for Procurement card transactions only. A detailed trial balance by fund for operating funds and for individual centers for project funds. Determine current account balances by reporting budget, actual and encumbrances across different elements of the financial data classification structure. M ►Q Report Title Description 11 Purchase order encumbrances Report used to determine funds encumbered and and commitments committed via purchase orders. This is useful throughout the year and in year-end fiscal year cleanup. 12 Governmental Fund Trial Balance Provides a trial balance report for the governmental funds. - 13 Proprietary Fund Trial Balance Provides a trial balance report for the proprietary funds. 14 Government Wide Statement of Assets - liabilities = net assets. The statement of net Net Assets assets presents the same information as a balance sheet. This is the basic government -wide statement of position. 15 Government Wide Statement of Used to report changes in the net assets reported on the Activities government -wide statement of net assets. 16 Fund Balance Analysis Report Beginning Fund Balance by fund plus Revenue less Expenditures, as well as estimated receipts and appropriations. 17 Governmental Fund Balance The basic statement of position for the governmental Sheet funds. 18 Governmental Fund Statement of The basic statement of activities for the governmental Revenues, Expenditures, and funds. The various components should be presented in Changes in Fund Balance the following order: revenues; expenditures; excess (deficiency) of revenues over expenditures; other financing sources and uses (including transfers); special items; extraordinary items; net change in total fund balance; fund balance beginning of period; and fund balance end of period. 19 Budgetary Comparison Report A budgetary comparison must be presented for the general fund and for each major individual special revenue fund for which an annual budget is adopted. At minimum, the budgetary comparison must include the following: original budget, final amended budget, and actual amounts. 20 Proprietary Fund Statement of The basic statement of position for the proprietary funds. Net Assets / Balance Sheet 21 Proprietary Fund Statement of The basic statement of activities for the proprietary funds. Revenues, Expenses, and The following order should be followed: operating Changes in Fund Net Assets / revenues; operating expenses; operating income (loss); Equity non -operating revenues and expenses; income before ... (as appropriate); capital contributions; additions to endowments; special items; extraordinary items; transfer; increase (decrease) in net assets / equity; net assets / equity - beginning of period; and net assets / equity - end of period. 22 Statement of Fiduciary Net The basic statement of position for fiduciary funds. Assets 23 Statement of Changes in The basic statement of activities for fiduciary funds. Fiduciary Net Assets 24 Report of MWBE Vendors Report of all MWBE vendors and spending. 25 Report by NIGP Code (Evaluated Report of all vendors by NIGP Code with the ability to sort } with Phase IIA Development City of Fort Worth ; CIBER, Inc. Professional Services Agreement Page 193 of 418 wo ID Report Title Desc"riptiari Items) by MWBE vendors first. 26 Miscellaneous versions of check Miscellaneous partial parameters - date ranges, register - some with or without Check/Voucher, Vendor number, Vendor name, invoice or PO information Department, Invoice, Purchase Order, Fund/Account/Center, paper vs. ACH. 27 Invoices Reports - paid, unpaid, Miscellaneous partial parameters - date ranges, in progress, selected for Check/Voucher, Unpaid and Closed Purchase Order, payment, document print, etc Vendor number, Vendor name, Department, Invoice, Purchase Order, Fund/Account/Center. 28 ACH transmit report and file Provides information for transmittal and reconciliation to Chase Bank. 29 Positive Pay report and file Provides information for transmittal and reconciliation to Chase Bank. 30 ACH vendors with missing data Used to identify vendors with missing and or invalid data. 31 Credit Memos and Open Invoices Used to assist Accounts Payable with assigning credit memos. 32 Factored Vendors Report This report assists Account Payable in identifying Factored Vendor's Invoices (where the payment is going to another vendor who acquired their Accounts Receivable). Note: There is a whole vendor management process around this and assignments. 33 Transactions Counts by Run by Department, Document Type(s), Fiscal Year. Document Count 34 Bid Report Bid Document, Buyer, workload summary, amendments, Quotes, bid tab, etc. 35 Master Agreements - Days to Select all or by Buyer and Days to Expire. Fields required Expire are: Long Description, Short Description, PO Number; Beginning Date; Ending Date; PO Description, Dollar Agreement, Dollars Spent, Dollar Cap and Vendor Name. 36 Invoice Retainage Report Enter purchase order number and release - lists all invoices to date - payments and retainage. 37 Inventory Reports (Part of Phase Report by transaction, stock item, warehouse, issues, IIC — Procurement and Inventory received, returns, adjustment, transfer, etc. Batch report Option) for daily reconciliation. ABC Analysis, count slip, item list, on order, receiving. 38 Document Attachment Report List of Bids, Purchase Order, Requisition, etc. with (Part of Phase IIC — attachments by Document type, ID or Document location. Procurement and Inventory Click on path to open document. Option) 39 Requisition - Purchase Order - Report allows user to enter any document type or vendor Invoice - Check Cross Reference and delivers the relationships of the documents. (Part of Phase IIC — Procurement and Inventory Option) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 194 of 418 rI OR tD -:.::Report Tithe ;; ";. =:. Desarl�fian 40 Standard Text (Part of Phase IIC Enter any word to get all standard text results used in — Procurement and Inventory documents - examples - T&C, sole source, renewable Option) blankets, LPO, Insurance, quotes, cover sheets, bid solicitation, agreements, etc. 41 NIGP code report (Part of Phase Listing by the following: all, active, commodity code, IIC — Procurement and Inventory Buyer assignments (one or all), unassigned codes, code _ Option) analysis. 42 Purchase Order Report (Part of Purchase Order document - vendor and CFW version, Phase IIC — Procurement and annual agreements, Blankets, Purchase Orders with Inventory Option) Invoices and declining purchase order balance, open purchase orders, change orders, paid - miscellaneous partial parameters (wild card search). 43 Contract Report (Part of Phase Miscellaneous partial parameters and drill down by Buyer IIC — Procurement and Inventory Option) 44 Requisitions Report (Part of Requisition Document, Unassigned - Ready for Phase IIC — Procurement and Purchasing, Requisitions to Multiple POs, Buyer and Inventory) workload summary, miscellaneous partial parameters. 45 Vendor Report (Part of Phase Invalid Federal ID's, Vendor invoices, Performance, IIC —Procurement and Inventory) Vendor history, Vendor Purchase Order list, search by miscellaneous partial parameters, name, email, address, ` etc. 46 Finance Contracts This report shows open Contracts for Financial Management Services — original, inception to date expense, remaining and expirations. 47 Improper Purchasing Report Compares Purchase Order Date to Invoice Date. Fields (Part of Phase IIC — needed are: Purchase Order number, Release number, Procurement and Inventory Invoice number, Vendor number, Invoice Date, Purchase Option) Order Date, Check number, Actual Cost, Department, and Timing. Timing is a calculated field based upon Purchase Order Date and Invoice Date. If the Purchase Order Date is Later than the Invoice Date, it is labeled "not ok". If the Purchase Order Date is before the Invoice Date it is "ok". 48 Invoice Aging Report (Evaluated Reports length of time from Requisition to Check. with Phase IIA Development Items andlimited to PeopleSoft data only 49 Invalid Use of Undesignated This report notifies the Budget office when people use Funds undesignated funds on Requisitions, Purchase Orders and Invoices 50 Open Purchase Order compared Open Purchase Orders compared to Budget for Fiscal to Budget Year End. 51 Approval paths Reports approval paths set up for document. Allows end users to input workflow criteria and returns a list of authorized approvals. 52 Document Status Work Flow Reports requisition, purchase order, invoice, bid, etc. status flow and accounting transaction set up. Show status of a particular document in a workflow. City of Fort Worth ,' CIBER, Inc. Professional Services Agreement Page 195 of 418 ID Report Title Desciptian 53 Fixed Asset Items identified as Fixed Assets by PO and date range. Purchase Order, Description, Account Code, Quantity, Unit, Unit Price, Total. 54 User Reports List of Users and their associated roles and authorizations. For example, user counts, use, role, activity, status. 55 Purchasing Report (Part of Information needed for the Purchasing department Phase IIC — Procurement and includes: Buyer, Requisition number (when applicable), Inventory Option) Dollar Value, Bid number (when applicable), Purchase Order number, Dollar Value, Approved date, Beginning date (when applicable), Expiration date (when applicable), Vendor name, M&C number , Department, Total of each Requisition, Purchase Order, Bids, and Short Description. 56 Buyer Report (Part of Phase IIC Information needed: Requisitions by Buyer, Bids by — Procurement and Inventory Buyer, Purchase Orders by Buyer, Agreements by Buyer, Option) Agreements by Expiration date, Agreements by Commodity, Agreements by Renewals, Agreements/Purchase Orders by Vendor, Agreements/Purchase Orders by Department. 57 Purchasing Manager Report (Part Information includes: Number of Bids, Requisitions and of Phase IIC — Procurement and Purchase Orders by Buyer. Inventory Option) 58 Quarterly Report for Council Information included: Bid Number, Purchase Order (based on dollar threshold) (Part Number, Vendor Name, Vendor Address, Approved Date, of Phase IIC — Procurement and Beginning Date, Ending Date, Renewal options Inventory Option) remaining, Contract cap, Dollars spent to date, Buyer , M&C number (when applicable), Department or city-wide, Short Description. 59 Renewal Report for Buyers (Part Bid Number, Purchase Order Number, Vendor, Beginning of Phase IIC — Procurement and Date, Ending Date, Renewal Options Remaining, Buyer , Inventory Option) M&C number (when applicable), Department or city-wide, Short Description. 60 Renewal Notifications (Part Phase IIC — Procurement Inventory Option) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 196 of 418 of Information includes: Vendor Name, Address, Phone, and Email Address, Contract Short Description, Bid Number, Purchase Order number, Next agreement term dates, Number of renewals remaining, Buyer, Purchasing Manager. (Vendor lists will be system generated and referenced for notification letters. Notification letters to be system generated and automatically faxed or emailed.) ID Report.7iti,e Descript�an. ,. 61 Unpaid Invoices with Closed Invoice Number, Vendor Number, Vendor Group, Invoice Purchase Orders (Part of Phase Date, Invoice description, Entered date , Entered User, IIC — Procurement and Inventory Updated date, Updated User, Invoice Status, Purchase Option) Order Number, Release Number, Current Header Status, Invoice type, Payment terms , Payment discount, Payment date, Handling code, Effective date, Date approved, User approved. 62 Payment voucher by Purchase Vendor, Vendor Number, Purchase Order number, Order (Evaluated with Phase IIA Release, Purchase Order date, Status, Line Item number, Development Items Option) Line Item Description, Item number, Receipt date, Quantity Ordered, Quantity Received, Unit of Measure, Unit Cost, Extended Amount, Other Dollars, Totals. 63 Inventory Item List With Reorder Location number, Stock number, Bin location, Item and Issue History (Part of Phase Description, Current Price, Estimated Value, Overhead IIC — Procurement and Inventory Percent, Change -Out Pricing, ABC designation, Order Option) Method, Quantity on Hand, Issue Unit of Measure, Minimum level, Maximum level, Quantity on Order, Order Unit of Measure. 64 Accounts Receivable - Aging Account number, customer name, invoiced amount, paid Report amount, age, outstanding balance. 65 ACH transmit report and file Transmittal and reconciliation to Chase Bank. 66 Positive Pay report and file Transmittal and reconciliation to Chase Bank. 67 Re -estimates Automatic month end download by department, expense and revenue to excel. 68 Risk Management Checks For Risk Management enters check numbers to be Direct Invoices downloaded in exact excel format for import into STARS. The invoices were imported into BSO from STARS. 69 Check Reconciliation Report Fiscal Year, Fiscal Month check reconciliation and download for Accounting 70 System Property - configuration Report system set up of items such as system defaults, reports thresholds, allowable features, paths, images, enforcement, etc. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 197 of 418 Exhibit G.6: Estimate of Effort for Initial Additional Reportinq Requirements 1 R Detailed Expenditures by Source with Vendor 20 2 R Requested elements of the Financial Data Classification Structures, allowing for summarization and drill -down capability. 20 3 R Revenue and Expenditure Report for Projects 20 4 R Revenue and Expenditure Report for Operating Funds 20 5 R Revenue and Expenditure Grant Fund Report 20 6 R Detailed Department Transaction Activity Reports 80 7 R Income Statement 80 8 R Procurement Card Expenses 40 9 R Detail Trial Balance 80 10 R Available Funds Inquiry 40 11 R Purchase order encumbrances and commitments 40 12 R Governmental Fund Trial Balance 20 13 R Proprietary Fund Trial Balance 20 14 R Government Wide Statement of Net Assets 40 15 R Government Wide Statement of Activities 40 16 R Fund Balance Analysis Report 40 17 R Governmental Fund Balance Sheet 40 18 R Governmental Fund Statement of Revenues, Expenditures, and Changes in Fund Balance 40 19 R Budgetary Comparison Report 40 20 R Proprietary Fund Statement of Net Assets / Balance Sheet 20 21 R Proprietary Fund Statement of Revenues, Expenses, and Changes in Fund Net Assets / Equity 20 22 R Statement of Fiduciary Net Assets 80 23 R Statement of Changes in Fiduciary Net Assets 80 24 R Report of MWBE Vendors 20 25 R Report by NIGP Code 20 26 R Miscellaneous versions of check register - some with or without invoice or PO information 80 27 R Invoices Reports - paid, unpaid, in progress, selected for payment, document print, etc 80 City of Fort Worth ; CIBER, Inc. Professional Services Agreement Page 198 of 418 11 1 0 1 1 1 1 1 1 1 J `=J I I i Reports from RFP Ap ,, 28 R ACH transmit report and file 40 29 R Positive Pay report and file 20 30 R ACH vendors with missing data 20 31 R Credit Memos and Open Invoices 20 32 R Factored Vendors Report 20 33 R Transactions Counts by Document Count 20 34 R Bid Report 20 35 R Master Agreements - Days to Expire 20 36 R Invoice Retainage Report 20 37 R Inventory Reports 80 38 R i Document Attachment Report 80 39 R Requisition - Purchase Order - Invoice - Check Cross Reference 40 40 R Standard Text 40 41 R NIGP code report 40 42 R Purchase Order Report 20 43 R Contract Report 20 44 R Requisitions Report 20 45 R Vendor Report 20 46 R Finance Contracts 20 47 R Improper Purchasing Report 80 48 R Invoice Aging Report 20 49 R Invalid Use of Undesignated Funds 40 50 R Open Purchase Order compared to Budget 20 51 R Approval paths 20 52 R Document Status Work Flow 20 53 R Fixed Asset 40 54 R User Reports 80 55 R Purchasing Report 80 56 R Buyer Report 40 57 R Purchasing Manager Report 40 58 R Quarterly Report for Council (based on dollar threshold) 20 59 R Renewal Report for Buyers 20 60 R Renewal Notifications 20 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 199 of 418 61 R Unpaid Invoices with Closed Purchase Orders 20 62 R Payment voucher by Purchase Order 20 63 R Inventory Item List With Reorder and Issue History 40 64 R Accounts Receivable - Aging Report 20 65 R ACH transmit report and file 20 66 R Positive Pay report and file 20 67 R Re -estimates 40 68 R Risk Management Checks For Direct Invoices 40 69 R Check Reconciliation Report 40 70 R System Property - configuration reports 20 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 200 of 418 1 1 1 1 1 1 1 1 1 1 1 t EXHIBIT I - SOFTWARE REQUIREMENTS AND RESPONSES Given the length of Exhibit I — Software Requirements and Response, the pages F for this exhibit have been added to the end of the document. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 202 of 418 EXHIBIT J - DISPOSITION OF CIBER EXCEPTIONS TO RFP TERMS AND CONDITIONS The following tables represent the final disposition of exceptions that were raised by CIBER in its proposal to RFP Terms and Conditions. 4.1.11 Termination of Agreement Proposed Both Parties agree that terminations shall be governed as set forth in the Disposition contract body, Section .4. Termination 4.1.12 Right to Assurance Original Text Whenever the City has reason to question the Prime Vendor's intent to perform, the City may demand that the successful Vendor give written assurance of Prime Vendor's intent to perform. In the event a demand is made, and no assurance is given within ten (10) calendar days, the City may treat this failure as an anticipatory repudiation of the contract. Disposition Whenever the City has reason to question the Prime Vendor's intent to perform, the City may demand that the successful Vendor give written assurance of Prime Vendor's intent to perform. In the event a demand is made, and no assurance is given within ten (10) business days, the City may treat this failure as an anticipatory repudiation of the contract. 4.1.25 Warranties Disposition Both Parties agree that warranties shall be governed as set forth in the contract body, Section .32. WARRANTY AND DISCLAIMER Topic 4.1.31 Organizational Conflicts of Interest Original Text The Responder warrants that, to the best of its knowledge and belief, and except as otherwise disclosed, there are no relevant facts or circumstances, which could give rise to organizational conflicts of interest. The Responder must provide a list of all entities with which it has relationships that create, or appear to create, a conflict of interest with the work that is contemplated in this RFP. The list should indicate the name of the entity, the relationship, and a discussion of the conflict. This list should be included in Tab 14 — Organizational Conflict of Interest in the Technical Proposal. An organizational conflict of interest exists when, because of existing or planned activities or because of relationships with other persons, a vendor is unable or potentially unable to render impartial assistance or advice to the City, or the Responder's objectivity in performing the contract work is or might be otherwise impaired, or the vendor has an unfair competitive advantage. The Responder agrees that, if after award, an organizational conflict of interest is discovered, an immediate and full disclosure in writing must be made to the City Project Manager, which must include a description of the action that the vendor has taken or City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 203 of 418 proposes to take to avoid or mitigate such conflicts. If an organizational conflict of interest is determined to exist, the City may, at its discretion, cancel the contract. In the event the Responder was aware of an organizational conflict of interest prior to the award of the contract and did not disclose the conflict to the City, the City may terminate the contract for default. The provisions of this clause must be included in all subcontracts for work to be performed similar to the service provided by the Prime Vendor and the terms "contract," "contractor," and "contracting officer" modified appropriately to preserve the City's rights. No public official shall have interest in this contract, in accordance with Vernon's Texas Codes Annotated, Local Government Code, Title 5, Subtitled C., Chapter 171. Disposition Final Language The Responder warrants that, to its knowledge and belief and acting in good faith, and except as otherwise disclosed, there are no relevant facts or circumstances, which could give rise to organizational conflicts of interest. The Responder must provide a list of all entities with which it has relationships that create, or appear to create, a conflict of interest with the work that is contemplated in this RFP. The list should indicate the name of the entity, the relationship, and a discussion of the conflict. This list should be included in Tab 14 — Organizational Conflict of Interest in the Technical Proposal. An organizational conflict of interest exists when, because of existing or planned activities or because of relationships with other persons, a vendor is unable or potentially unable to render impartial assistance or advice to the City, or the Responder's objectivity in performing the contract work is or might be otherwise impaired, or the vendor has an unfair competitive advantage. The Responder agrees that, if after award, an organizational conflict of interest is discovered, an immediate and full disclosure in writing must be made to the City Project Manager, which must include a description of the action that the vendor has taken or proposes to take to avoid or mitigate such conflicts. If an organizational conflict of interest is determined to exist, the City may, at its discretion, cancel the contract. In the event the Responder was aware of an organizational conflict of interest prior to the award of the contract and R did not disclose the conflict to the City, the City may terminate the contract for default. The provisions of this clause must be included in all subcontracts for work to be performed similar to the service provided by the Prime Vendor and the terms "contract," "contractor," and "contracting officer" modified appropriately to preserve the City's rights. No public official shall have interest in this contract, in accordance with Vernon's Texas Codes Annotated, Local Government Code, Title 5, Subtitled C., Chapter 171. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 204 of 418 4.1.33 Performance Bond Both parties agree to forego the requirement for a performance bond in favor of requiring a 10 percent retainage on deliverables. 4.2.2.5 Additional Insurance Conditions Disposition I Both Parties agree that insurance requirements shall be governed as set forth in the contract body, Section . 10. INSURANCE. 4.3 Software Licenses for Third Party Applications Original Text The City requires the Prime Vendor, upon approval by the City, to secure the appropriate software licenses for the City for any third -party applications included in the proposal to meet the requirements included in Appendix B — Software Requirements Matrix. Disposition Final Language In the event that a 3`d party software product is required to support the scope of work identified, the City may require the Contractor to obtain the necessary licenses. Such decisions will be governed by the relevant change order with applicable resale provisions and the City's execution of the applicable software license agreements with the software product vendors. 6.5.5 Project Organization and Staffing Original Text The Responders shall provide a project organization chart, job descriptions, role and responsibility descriptions for all team members assigned to the project. Responders shall provide resumes in Tab 7 for the assigned Project Manager and key personnel who will be assigned to the project, if awarded. For other personnel, the Responder may include resumes that serve as a representation of the level and experience of = personnel who could be assigned to the team. Assigned personnel may be the Responder's employees or employees of sub -contractors. The resumes should specifically include a description of work in the implementation of similar projects. In addition, Responder shall submit references for Key Personnel through the template included in Appendix H - Key Personnel Reference Information. Key Personnel Key personnel should be committed for the duration of the project in order to maintain continuity and stability of the project and not getting disrupted due to ramp up time. The following seven (7) roles on the Prime Vendor's team will be considered key personnel for this project: Project Manager Finance Team Lead Procurement Team Lead Technical Lead Change Management Lead Training Lead Security and Internal Control Lead It is critical to the overall success of the project that the Prime Vendor not City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 205 of 418 6.5.5 Project Organization and Staffing remove or reassign, without the City's prior written approval any of the key personnel until such time as the key personnel have completed all of their planned and assigned responsibilities in connection with performance of the Prime Vendor's obligations under the contract. The unauthorized removal of key personnel by the Prime Vendor without the prior approval of the City's Project Manager shall be considered by the City as a material breach of contract and may result in liquidated damages of up to $50,000 per occurrence. Disposition The Responders shall provide a project organization chart, job descriptions, role and responsibility descriptions for all team members assigned to the project. Responders shall provide resumes in Tab 7 for — the assigned Project Manager and key personnel who will be assigned to the project, if awarded. For other personnel, the Responder may include resumes that serve as a representation of the level and experience of personnel who could be assigned to the team. Assigned personnel may be the Responder's employees or employees of sub -contractors. The resumes should specifically include a description of work in the implementation of similar projects. In addition, Responder shall submit references for Key Personnel through the template included in Appendix H — Key Personnel Reference Information. Key Personnel Key personnel should be committed for the duration of the project in order to maintain continuity and stability of the project and not getting disrupted ., due to ramp up time. The following seven (7) roles on the Prime Vendor's team will be considered key personnel for this project: Project Manager Finance Team Lead Procurement Team Lead Technical Lead Change Management Lead Training Lead Security and Internal Control Lead It is critical to the overall success of the project that the Prime Vendor not remove or reassign, without the City's prior written approval any of the key personnel until such time as the key personnel have completed all of their planned and assigned responsibilities in connection with performance of the Prime Vendor's obligations under the contract . The unauthorized removal of key personnel by the Prime Vendor without the prior approval of the City's Project Manager shall be considered by the City as a material breach of contract. The foregoing shall not apply to the Change Management Lead and the Training Lead roles until Prime Vendor and City agree upon the personnel to be assigned to such roles. CIBER may remove one (1) member of the key personnel team from the project, if the employee self identifies him/herself as not being a "good fit" and requests reassignment in lieu of — resignation. Prime Vendor agrees to provide a minimum of two (2) weeks overlap to provide adequate knowledge transfer between resources. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 206 of 418 Right to Remove Staff Original Text If a change occurs in the Project Team after an award is made, the Prime Vendor shall propose a replacement, and the City shall have the right of refusal of any replacement. Any employee or subcontractor of the Prime Vendor, who in the opinion of the City is unacceptable, shall be removed from the project upon written notice from the City. The City shall approve in writing any changes to the Project Team. Disposition If a change occurs in the Project Team after an award is made, the Prime Vendor shall propose a replacement, and the City shall have the reasonable right of refusal of any replacement. Any employee or subcontractor of the Prime Vendor, who in the City's good faith and reasonable judgment, does not possess the requisite skills to perform his or her duties or is not a good fit with the other members of the City and/or project team, shall be removed from the project. The City shall approve in writing any changes to the Project Team City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 207 of 418 EXHIBIT K - DELIVERABLES CROSS REFERENCE Work-., 'Phase' Methodology Work produlct DDD DeR erable"Name Product Their- Number, Num: 1 Preparation Project Project Charter DDD-01 Project Charter Management - Control 2 Preparation Project Project Work Plan DDD-02 Project Work Plan Management - Narrative and MS — Control Project Work Plan 3 Preparation Project Scope Change DDD-01 Project Charter — Management - Management Control Process and Tools 4 Preparation Project Issue DDD-03 Risk & Issue Management - Management Management Plan Control Process and Tools 5 Preparation Project Risk Management DDD-03 Risk & Issue Management - Process and Tools Management Plan _ Control 6 Preparation Project Quality DDD-04 Quality Assurance Management - Management Plan _ Control Tools and procedures 7 Preparation Project Configuration DDD-05 Configuration Plan _ Management - management tools Control and procedures 8 Preparation Project Status Reports DDD-06 Status Report Management - Template Control 9 Preparation Project Testing Strategy DDD-07 Testing Plan Management - Cross Team Integration _ 10 Preparation Project Test Plan DDD-07 Testing Plan Management - Cross Team Integration ! 11 Preparation Functional Project Team DDD-08 Implementation Training Team Training City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 208 of 418 Work= Pia Methodology E7tt odtuc',QQQ �eli erable Nam. ME Product Themeymber d Num �AN r , 12 Preparation Technical - Technical DDD-09 Technical Infrastructure Infrastructure Plan Roadmap 13 Preparation Technical - Sand Box DDD-11 Instance Infrastructure Environment Management Plan 14 Preparation Technical - Conversion DDD-12 Conversion Plan Development Strategy 15 Preparation Technical - Interface Strategy DDD-13 Interface Plan Development 16 Preparation Technical - Enhancement DDD-14 Customization Plan Development Strategy 17 Preparation Change and Cultural Change DDD-14 Change Communication Management Management Plan Strategy 18 Preparation Change and Communications DDD-15 Communication Communication Strategy Plan 19 Preparation Change and Communications DDD-15 Communication Communication Plan Plan 20 Preparation Training Training Strategy DDD-19 Training Plan Preparation Training Knowledge DDD-20 Knowledge I21 Transfer Strategy Transfer Plan 22 Preparation Security and Application DDD-25 Security Plan Internal Security Strategy Controls 23 Preparation Security and Control Review DDD-24 Internal Control Internal Strategy Framework ' Controls 24 Preparation Security and Risk Assessment DDD-03 Risk & Issue Internal and Plan Management Plan Controls 25 Preparation Security and Internal Control DDD-24 Internal Control Internal Framework for Framework Controls Finance and Procurement Functions 26 Design Project Updated Project DDD-02 Project Work Plan Management - Work Plan and Control 27 Design Project Status Reports DDD-06 Status Report Management - Template Control 28 Design Project Development DDD-13, Finalized list of Management - Object List and DDD-14, objects within Cross Team Unit Test Plan DDD-15 Conversion Plan, Integration Interface Plan, City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 209 of 418 Work- Phase` : Methodology Wotlpoduct DDD ':deliverable Name Product W Theme s Number Num Customization Plan 29 Design Functional Documented DDD-18 Business Process Business Process "To Be" maps Designs 30 Design Functional Prototyping DDD-16 Prototyping Plan Sessions 31 Design Functional Documented DDD-17 Fit/Gap Analysis Fit/Gap Analysis Report 32 Design Functional Configuration and DDD-30 Core Table Setup Unit Test Plan 33 Design Functional Analysis of DDD-17 Fit/Gap Analysis Reporting Report Requirements 34 Design Functional Functional DDD-22 Functional and Specifications for Technical Design of Specifications Interfaces, Conversions, and Enhancements 35 Design Technical - Technical DDD-09 Technical i Infrastructure Architecture Roadmap Design 36 Design Technical - Independent DDD-10 QA of Technical �. Infrastructure Validation and Architecture Verification Review - •-- Technical Architecture Design 37 Design Technical - Demo DDD-11 Instance Infrastructure Environment Management Plan 38 Design Technical - Prototyping DDD-11 Instance Infrastructure Environment Management Plan 39 Design Technical - "Gold" DDD-11 Instance Infrastructure Configuration Management Plan — Environment 40 Design Technical - Development DDD-11 Instance Infrastructure Environment Management Plan — City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 210 of 418 Work: Phase:' Methodology WtF Debi �bl Name a„ Pr - Theiine N�mler� i 'Al 41 Design Technical - Conversion Plan DDD-12 Conversion Plan Development 42 Design Technical - Interface Plan DDD-13 Interface Plan Development TM 43 Design Technical - Technical DDD-22 Functional and Development Specifications for Technical Design of Specifications Interfaces, 4 Conversions, and Enhancements 44 Design Change and Cultural Change DDD-26 Resistance Communication Management Plan Management Plan (CCMP) 45 Design Change and Communication DDD-15 Communication Communication Plan Content Plan 46 Design Change and Change DDD-27 Change Readiness Communication Readiness Assessment Assessment 47 Design Change - Organizational DDD-27 Change Readiness Organizational Analysis for Assessment Design Finance and Procurement Functions 48 Design Change — Organizational DDD-27 Change Readiness Organizational Alignment Assessment Design Workshops 49 Design Change - Business Process DDD-28 Workforce Organizational Change Impact Transition Plan Design Assessment 50 Design Change - Workforce DDD-28 Workforce Organizational Transition Plan Transition Plan Design 51 Design Change - Role Based DDD-28 Workforce Organizational Updates to Job Transition Plan Design Descriptions and Knowledge, Skills and Abilities (KSA's) 52 Design Training End -User Needs DDD-19 Training Plan Assessment 53 Design Training Training Plan DDD-19 Training Plan 54 Design Training Training DDD-19 Training Plan Curriculum City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 211 of 418 rpm i Work`; Phase., , Meth©dology :. '` Wai k product .` DDD Deliverable:Name; Product, : Theme Number Norm- ^ 55 Design Training Knowledge DDD-20 Knowledge Transfer Plan Transfer Plan 56 Design Security and Application DDD-25 Security Plan Internal Security Plan Controls 57 Design Security and Process Design DDD-18 Business Process Internal Review "To Be" maps Controls 58 Design Security and Review of DDD-22 Functional and Internal Relevant Technical Controls Functional Specifications Specifications 59 Design Security and Workflow Design DDD-22 Functional and Internal Reviews Technical Controls Specifications 60 Build Project Updated Project DDD-02 Project Work Plan Management - Work Plan and Control 61 Build Project Status Reports DDD-06 Status Report — Management - Template Control 62 Build Project Integration Test DDD-07 Testing Plan Management - Plan Cross Team Integration 63 Build Functional Initial Software DDD-30 Core Table Setup — Configuration Documentation 64 Build Functional Final Software DDD-30 Core Table Setup — Configuration Documentation 65 Build Functional Documented Unit DDD-07 Testing Plan Test Scripts (CIBER sees as System Test Scripts) r 66 Build Functional Integration Test DDD-31 Integration Test Scripts Scripts 67 Build Functional Knowledge DDD-21 Team Member Transfer Knowledge Documentation Transfer Evaluation 68 Build Functional Cleansed Data for DDD-33 Converted Data for Conversion legacy Conversions _ City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 212 of 418 MM Mef�od0 t) x t R :ems Prods Theme Nu .. �� n 69 Build Technical - Load and Volume DDD-07 Testing Plan Infrastructure Test Plan and i Templates 70 Build Technical - QA and Other DDD-11 Instance Infrastructure Testing Management Plan Environments 71 Build Technical - Workstation DDD-09 Technical Infrastructure Deployment Roadmap i 72 Build Technical - Business DDD-14 Technical Infrastructure Continuity Plan Roadmap 73 Build Technical - Independent DDD-10 QA of Technical i Infrastructure Validation and Architecture Verification Review — Pre - Production Installed Architecture 74 Build Technical - Technical DDD-22 Functional and Development Documentation of Technical Interfaces, Specifications Conversions, Reports and Enhancements 75 Build Technical - Upgrade Checklist DDD-22 Functional and Development Technical Specifications (summary of all Object Upgrade impacts) 76 Build Change and Communication DDD-15 Communication " Communication Plan Content Plan 77 Build Change - Workforce DDD-28 Workforce Organizational Transition Plan Transition Plan Design Work -products 78 Build Training Training Course DDD-19 Training Plan Outlines 79 Build Training Training Course DDD-29 Training Materials Content and Database 80 Build Training Training Logistics DDD-19 Training Plan 81 Build Security and Role Definitions DDD-25 Security Plan Internal Controls 4W City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 213 of 418 M Work, Phase Methodology Work -product DDD Deliverable Name :,. product xTheme Nuttier` y , 82 Build Security and Role Assignments DDD-25 Security Plan Internal to End Users Controls 83 Build Security and Unit Test Script DDD-07 Testing Plan Internal Review and Controls Recommendations (CIBER sees as System Test Scripts) 84 Build Security and Unit Test Results DDD-07 Testing Plan Internal Review and Controls Recommendations (CIBER sees as System Test Results) 85 Build Security and Integration Test DDD-31 Integration Test Internal Script Review and Scripts Controls Recommendations 86 Build Security and Integration Test DDD-31 Integration Test Internal Results Review Scripts Controls and Recommendations 87 Build Security and Training Course DDD-29 Training Materials Internal Outline Review Controls and Recommendations 88 Build Security and Training Course DDD-29 Training Materials Internal Content Review Controls and Recommendations 89 Cutover Project Updated Project DDD-02 Project Work Plan Management - Work Plan and Control Implementation Schedule 90 Cutover Project Status Reports DDD-06 Status Report Management - Template -- Control 91 Cutover Project Deployment Plan DDD-34 Cutover Plan Management - Cross Team Integration City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 214of418 LJ Work- Product Pha _ MethodoIoq Theme Jl :`Deliverable Name Num�_ _. .:.:, "^°'.'.., .:: ,. :%. cam''^•. .,. ,- ,. ...',,n.,,. 92 Cutover Project Update to Help DDD-35 Review & Update Management - Desk and Support of Competency Cross Team Procedures Center Material Integration 93 Cutover Functional Documented DDD-32 Integration Test Integration Test Results 94 Cutover Functional User Acceptance DDD-07 Testing Plan Test Plan 95 Cutover Functional User Acceptance DDD-36 User Acceptance Test Scripts Test Scripts 96 97 98 99 Cutover Functional User Acceptance DDD-36 User Acceptance Test Results Test Scripts Cutover Cutover Cutover 100 Cutover 101 Cutover Technical - Final Production DDD-34 Cutover Plan Infrastructure System Change and Communication DDD-15 Communication Communication Plan Content Plan Change - Workforce DDD-28 Workforce Organizational Transition Plan Transition Plan Design Work -products Training Delivery of Power DDD-39 Training Delivery User and End - User Courses Security and Deployment Plan DDD-34 Cutover Plan Internal Review and Controls Recommendations 102 Cutover Security and Help Desk DDD-35 Review & Update Internal Procedure Review of Competency Controls and Center Material Recommendations 103 Cutover Security and Internal Control DDD-34 Cutover Plan Internal Framework Go - Controls Live Assessment 104 Go -Live Project Updated Project DDD-02 Project Work Plan Management - Work Plan and Control Implementation Schedule 105 Go -Live Project Project Closeout DDD-37 Project Closeout Management - Final Report and Lessons Control Learned City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 215 of 418 e~ Work- Phase F. IVletliodltilogy V1ia �C a tt []! 001liverable Nami' Product Theme r; Irrbr Num w " 106 Go -Live Project Status Reports DDD-06 Status Report Management - Template Control 107 Go -Live Functional Manage Change DDD-38 Production Support Control Plan Execution 108 Go -Live Change and Communication DDD-15 Communication " Communication Plan Content Plan 109 Go -Live Change - Workforce DDD-28 Workforce Organizational Transition Plan Transition Plan Design Work -products City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 216 of 418 EXHIBIT L - SAMPLE DELIVERABLE DEFINITION DOCUMENTS DDD DDD I- Sample Project Charter ................ ................... ..... Deliverable Descriptlon Document Number: DDD-01 CIBER Deliverable Name -:,Project Charter CIBER Stage Discovery �. City Work Product Name: Project Charter City Focus - Project Management I. -Control Description/Objective: This document presents project management related components that will be used in the governance of the Project. The project controls and procedures outlined in this document are based on CIBER's CPMM methodology and will be tailored to meet the requirements of this project. This document is established as a "living" document that is the reference for maintaining the appropriate project controls for the entire project. This document is intended to evolve with the project and allows for processes and controls to be enhanced or added as the project progresses through its lifecycle. All sections of the outline below will be completed with input from the City core project team and key stakeholders prior to submittal to the PMO for review. Any additions/edits resulting will be discussed at the Project Manager level and agreed to and such edits will be included in the final version submitted for approval. Upon approval, this document will be available to all project team members and available in the document repository. Scope: Project Overview inclusive of goals and objectives, Project Team Organization, Governance Processes for Work Products, Work Environment, Project Assets, Work Man Bement, and the other topics outlined below. Format: Note: Include a variety of different methods of delivering the learning for stronger results. For example, Instructor Led Training, Computer Based Training, demonstrations, workshops, coaching sessions, videos, Course -in -a -Box etc. A clear path of learning building blocks needs to be built up. For example, prepare the learning, participate in the learning, practice what has been learned, put this practice in the context of the individual's role, begin to use what has been learned within the individual's role etc. Note: Include a variety of different methods of delivering the learning for stronger results. For example, Instructor Led Training, Computer Based Training, demonstrations, workshops, coaching sessions, videos, Course -in -a -Box etc. A clear path of learning building blocks needs to be built up. For example, prepare the learning, participate in the learning, practice what has been learned, put this practice in the context of the individuals role, begin to use City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 217 of 418 what has been learned within the individual's role etc. Microsoft Word Document Outline: • Message from the Sponsor • Project Overview o Project Summary o Business Goals o Project Objectives • Project Team Organization o Org Chart o Project Groups ■ Steering Committee ■ Work Committee ■ Extended Team ■ Third Parties o Roles and Responsibilities • Governance Processes — Work Environment o Offsite Protocols o Work Rules ■ Core Hours ■ Meeting Attendance ■ Team Meeting Ground Rules ■ Team Conflict o Work Site Security o Entrance/Exit criteria for Stages • Governance Processes -Project Assets o Data Security Protocol o System/Application Access o Off -site Data Security Protocol • Governance Processes -Work Management o Approvals o Escalation ■ Scope ■ Participant Roles and Responsibilities ■ Escalation Process Approach ■ Contact Information o Project Dependencies ■ Internal ■ External Acceptance Criteria: 1) The deliverable contains all the components specified in the Outline of this DDD. 2) The respective CIBER and City Leads assigned to this deliverable have agreed to and accepted the content of each outlined component, or have escalated and City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 218 of 418 R A issues to the project management team. 3) The respective CIBER and City Leads have resolved all material content and/or quality issues. 4) The deliverable meets any and all requirements agreed to in the DDD. 5) The deliverable meets the agreed upon Project Documentation Standards (if applicable). 6) The deliverable is free of formatting and spelling errors. CIBER ROLE CITY OF FORT WORTH ROLE Lead L Assist IES CITY O CIBER ACTIVITIES FORT WORTH ACTIVITIES (._...... _.._..__....................__....... .__...........__.......-....._....................__.........._...._.....-----��_................................................._........_........._...................................................._......_._ ............ _ ...... _..... _ • Provide deliverable format and Approve document format and educate client on content intended content • Schedule data gathering sessions • Develop draft deliverable • Review client feedback and make agreed upon edits • Produce final deliverable • Store deliverable in PMRx document repository and communicate to project team City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 219 of 418 • Identify appropriate key stakeholders and project team participants • Provide content as assigned/requested • Review draft deliverable and provide timely feedback/edits • Review and approve final deliverable DDD 15-Sample Customization Plan DDD [l Deliverable Description Document Number: DDD-15 CIBER Deliverable Name: Customization ICIBER Stage: Discovery Plan_.._..._ .. .._ __._. _. _..._.....__._._._.._._.____ .. I[ f City Work Product Name: Enhancement City Focus — Technical Strategy ! Development Description/Objective: Enhancement Strategy to describe, in general, the approach to be undertaken when a gap is identified and the consensus of the City is that it should be resolved by enhancing the functionality of PeopleSoft. ................................. _........ ...... .... _..... ....................................... _...... _._................ ..... _................................ Scope: This plan documents a change control structure for handling modifications and recommends a process for tracking modifications. The plan also proposes an approach to modifications that includes how, when and why modifications should be done. Format: Note: Include a variety of different methods of delivering the learning for stronger results. For example, Instructor Led Training, Computer Based Training, demonstrations, workshops, coaching sessions, videos, Course -in -a -Box etc. A clear path of learning building blocks needs to be built up. For example, prepare the learning, participate in the learning, practice what has been learned, put this practice in the context of the individual's role, begin to use what has been learned within the individual's role etc. Note: Include a variety of different methods of delivering the learning for stronger results. For example, Instructor Led Training, Computer Based Training, demonstrations, workshops, coaching sessions, videos, Course -in -a -Box etc. A clear path of learning building blocks needs to be built up. For example, prepare the learning, participate in the learning, practice what has been learned, put this practice in the context of the individual's role, begin to use what has been learned within the individual's role etc. Microsoft Word Outline: • Introduction • Objectives • Modification Strategy City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 220 of 418 0 0 0 0 0 0 0 E � 0 Summary of Recommendations Assumptions Change Control Fit/Gap Development Change Control - Recommended Initiation of a Development Change for Modifications Modification Matrix Modification Approach Modification Standards Custom Schema Custom Applications and Custom Folders Preserving the Integrity of the Original Object Naming Standards Modification Tools About Modification Tools Acceptance Criteria: 1) The deliverable contains all the components specified in the Outline of this DDD. 2) The respective CIBER and City Leads assigned to this deliverable have agreed to and accepted the content of each outlined component, or have escalated any issues to the project management team. 3) The respective CIBER and City Leads have resolved all material content and/or quality issues. 4) The deliverable meets any and all requirements agreed to in the DDD. 5) The deliverable meets the agreed upon Project Documentation Standards (if applicable). j 6) The deliverable is free of formatting and spelling errors. .......................__....... .......... _ .................. .............................. CIBER ROLE CITY OF FORT WORTH ROLE Lead � � 11_ Assist CIBER ACTIVITIES CITY OF FORT WORTH L ACTIVITIES • Present deliverable and educate City 11 • Review and understand counterparts on intended approach approach and intended and information required to complete deliverable information to • Schedule and coordinate modification I be provided strategy sessions • Participate in modification • Document results from sessions strategy sessions and • Complete and submit draft provide requested deliverable /assigned information • Incorporate any feedback and submit • Review draft deliverable final document and provide feedback and • Store deliverable in document suggested edits repository and communicate to Review final deliverable project team ? and sign -off City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 221 of 418 7 DDD 21- Sample Training Plan DDD j Deliverable Description Document Number: DDD-21 ..___. _ .... ..,_.. ry—__,___ ._....... CIBER Deliverable Name: Training Pan ' CIBER Stage: II Discove City Work Product Name: Training Strategy, End City Focus — User Needs Assessment & Training Plan _ _ 11 Training _, w Description/Objective: CIBER will prepare a Training Strategy to describe, in general, the scope, approach and activities that will guide the ERP Phase Two training efforts. This work -product will set the stage for planning and execution of project team training and end -user training. E _ CIBER will conduct a role -based training needs assessment and audience analysis to define the knowledge and skill needs of end -users, and compare the results to the instructional content included in off -the -shelf training courses that the Software Vendor will provide. CIBER will use the assessment results to further document the extent to which new courses must be developed "from scratch" and which off -the -shelf training courses can be used "as is" or tailored to best serve the needs of the City. Tailoring of some existing courses will change the content and instructional design to make the course more conducive to meeting learning needs. CIBER will also - apply assessment results to recommend how coaching, mentoring, and performance support tools (on-line help, procedures -at -a -glance, technical documentation, and job aids) can be used to further impart knowledge and skill to the City's users. This Work -product shall include: • Analysis of the importance, frequency and complexity of the ERP- related job tasks end users will perform. • Analysis of learner characteristics that will influence instructional design decisions. • Description of all off -the -shelf training courses the Software Vendor will provide as part of the scope of work with notations that indicate which of these courses can be used as -is and which must be tailored to meet the defined needs of end -users. — • Descriptions of other training courses that must be custom -developed (built from scratch) to further meet defined end -user training needs. Description of how formal training (instructor -led, and Web -based), informal — training (walk-throughs and demos by a trained coach, and mentoring), performance support (on-line help, procedure manuals, and job aids), and users' access to general information about the new system will address _ learning needs. The training plan shall include: • The training goals • Training attendees (i.e. technical, configuration, super user, and City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 222 of 418 pip general user) • The training logistics (PCs, system requirements, and presentation equipment ) • Course overview for each attendee (description, schedule, topics, and training material) • Cross training approach • Users Manuals contents Computer Based Training (CBT) contents PR Scope: PeopleSoft and Hyperion training (classroom and online) approach and plan f i Format: Note: Include a variety of different methods of delivering the learning for stronger results. For example, Instructor Led Training, Computer Based Training, demonstrations, workshops, coaching sessions, videos, Course -in -a -Box etc. A clear path of learning building blocks needs to be built up. For example, prepare the learning, participate in the learning, practice what has been learned, put this practice in the context of the individual's role, begin to use what has been learned within the individual's role etc. 1 Note: Include a variety of different methods of delivering the learning for stronger results. For example, Instructor Led Training, Computer 94 Based Training, demonstrations, workshops, coaching sessions, videos, Course -in -a -Box etc. I A clear path of learning building blocks needs to be built up. For example, prepare the learning, participate in the learning, practice what has been learned, put this practice in the context of the individual's role, begin to use what has been learned within the individual's role etc. Microsoft Word Outline: • Structure and Purpose of this Document Terminology Used in this Document • Implementation Scope i Project Rollout Stages "" • Assumptions and Constraints j End User Training Objectives Training Team Scope End User Training Critical Success Factors • Training Program Development Process City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 223 of 418 • Identifying Training Needs ....._..._._.._...._. ��....__..�.... E Project Training Approach r Project Training Roles and Responsibilities • Assumptions and Constraints • Objectives and Key Deliverables of Courseware Development • Guiding Principles for Courseware Development • Curriculum • Pre -Training Components • Instructor Led Courseware Components • Web Based Training Courseware Components Post -Training Performance Support Components • Courseware Development Tools and Templates i Training Execution Quality Assurance Process • Project Training Delivery Strategy • Trainer Selection and Preparation Training Delivery Logistics o Training Facilities o Training Delivery Plan • Training Environment • Post -Implementation Training Support • Training Program Evaluation • Issues and Concerns • Appendix A: A Methodology: Key Training Deliverables by Stage • Appendix B: Sample Role Profile Document • Appendix C: The City's Enterprise Process Owners • Appendix D: The City's Enterprise Process Team Leaders • Appendix E: General Training Facility Requirements 1 Acceptance Criteria: 1) The deliverable contains all the components specified in the Outline of this DDD. 2) The respective CIBER and City Leads assigned to this deliverable have agreed to and accepted the content of each outlined component, or have escalated any issues to the project management team. 3) The respective CIBER and City Leads have resolved all material content and/or quality issues. 4) The deliverable meets any and all requirements agreed to in the DDD. 5) The deliverable meets the agreed upon Project Documentation Standards (if applicable). i 6) The deliverable is free of formatting and spelling errors. CIBER ROLE i CITY OF FORT WORTH ROLE Lead �........................................Assist .................................................................................................................................................................... ................. ... , CIBER ACTIVITIES CITY OF FORT City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 224 of 418 r • Present deliverable and educate City counterparts on intended approach and information required to complete • Complete and submit draft deliverable • Incorporate any feedback and submit final document • Store deliverable in PMRx document repository and communicate to project team City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 225 of 418 { WORTH ACTIVITIES • Review and understand i approach and intended deliverable information to be provided I • Review draft deliverable and provide j feedback and suggested edits • Review final deliverable and sign -off EXHIBIT M - LIST OF SOFTWARE REQUIREMENTS THAT ARE KNOWN TO BE SUPPORTED BY MODULES NOT IN SCOPE The following requirements, though they can be met with functionality from other PS R modules, will be met under the Module to be Implemented defined in Exhibit A — Statement of Work, using either delivered functionality or through a business process work -around: Qedtile pecrtrp Number 171-02-01-04-11 Employee Travel Reimbursement Expense F3-02-01-00-00 System provides the ability to electronically Deal Management or manually record investment activity of funds held in external financial institutions. F3-06-01-00-00 System provides the ability to maintain and Expense record activity of petty cash accounts, tracked separately. F3-06-03-00-00 System supports the detailed collection of Expense �- expenditures reimbursed from petty cash. F3-06-04-00-00 System supports the attachment of scanned Expense images to petty cash expenditures. F3-06-05-00-00 System provides the ability to reimburse the Expense petty cash accounts, via online user - requests. _ F3-06-06-00-00 System supports the establishment of Expense change funds. F5-00-04-09-00 Amortization of leases or other intangibles Real Estate Management F6-01-01-07-00 Project Approval Request Date Program Management F6-01-01-08-00 Project Approval Status Planned, Program Management Submitted, Approved for Funding F6-01-01-09-00 Project Approval Action Date Program Management F6-02-01-00 System provides the ability to allocate direct Expenses _ costs to projects through expenditure transactions. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 226 of 418 EXHIBIT N: SYSTEMS TO BE REPLACED Title User Department(s) Purpose Replacement Candidate MARS All The General Ledger (GL) system used by the City is the GEAC E-series Phase IIA for Government. The financial system is supplemented with auxiliary applications to separate and alleviate critical processes (i.e., the purchasing/payment functions have been moved to a client/server application that feeds financial transactions to GEAC's General Ledger). The General Ledger system is required to produce financial statements in conformity with Generally Accepted Accounting Principles (GAAP), guidelines set forth in the AICPA (American Institute of Certified Public Accountants) Industry Audit Guide Audits of State and Local Governmental Units, and GFOA's (Government Financial Officers Association) publication Governmental Accounting, Auditing and Financial Reporting (Using the GASB 34 Model). The system conforms to all Governmental Accounting Standards Board or Financial Accounting Standards Board pronouncements applicable to local governments. City -Wide Billing All City -Wide Billing generates hard copy invoices that can be sent to Phase IIA customers and also provides a mechanism to receive payment for the invoice. There is some interface integration to MARS, such as the Tax Revenue Interface. Environmental Environmental Used to generate quarterly bills to cities that participate in Hazardous Phase IIA Management Management Waste collections and disposal. Input is captured from manually Participating Cities completed hard copy forms. Access Database Cold Fusion Police; Water / Waste Used to support budget re -estimates. Phase IIA Water City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 227 of 418 Title User Department(s) Purpose Replacement Candidate Department of Transportation & DOE Master serves as a project tracking system. This is due for phase Phase IIA Engineering (DOE) Public Works is the out with full implementation of CPMS. It has an Access front end with an Master Database owner and primary SQL backend. All time and attendance data is captured in this system, user, Program almost all TPW employees have access to a computer for input (several Management Office in Survey were identified as requiring input from an admin.). Engineering (PMO), Water, Payroll is part of the DOE Master to charge to various projects requesting Aviation, PACS view P119 services using employee salaries, multiplier rates (depending on only users. contractual obligation per project), hours/overtime hours of service per project, mileage per project, misc. charges not through the City numbering system that are project reimbursable, all information is grouped and submitted by MARS weekending structure per pay period Mobius All Facility used for on-line report distribution. Snapshots are run of reports Phase IIA as part of the period -end close and made available to departments via Mobius. BuySpeed On-line All The City's Procurement system. Functions include: Requisitioning, Phase IIC Creating Purchase Orders, Contracts, Releases, Receipts, Invoicing and Matching. Transactions are work -flow enabled to capture on-line approvals. AJ Database Financial Management Stand-alone Access Database used to capture year-end adjustments and Phase IIA Services reclassification. Currently provides an interface to MARS for year-end close journals. IPM-in-house Financial Management Standalone access database that is used to distribute expenditures on a Phase IIA access database Services percentage basis to capital projects from a default expenditure account distribution. JV Database Financial Management Stand-alone Access Database used to capture daily journal entries in Phase IIA Services Financial Management Services. Interfaces daily to the General Ledger. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 228 of 418 Title User Department(s) Purpose Replacement Candidate Inter -Departmental Financial Management The IDB system is a mainframe online system which allows users to bill Phase IIA Billing Services other departments for services. The user selects the revenue account and expense account to be charged, and the accounts are validated. The amount of the transaction, the effective date and general description of the transaction are also entered. Transactions are tracked by department, as a user is always assigned a two character code for their department which becomes part of the description. The transactions are extracted on a monthly basis and interfaced with MARS as all other interfaces. CAFR Database / Financial Management Used at the end of Fiscal Year to complete the CAFR. Combines Phase IIA Trial Balance Services information from the Trial Balance with the AJ Database (used to capture Spreadsheet reclassifications that do not post to the General Ledger) Maintains mapping information for funds and accounts for CAFR reporting purposes. IT Asset Tracking Fire Used to maintain ITS assets, independently of ITS Inventory tracking, Phase IIA Maintains assignments and physical location of ITS equipment. Also used to reconcile to TIVOLI in ITS. Radio Tracking Fire Used to maintain and track radios and other communication equipment. Phase IIA Database Fire Supply Fire Used to maintain and issue inventories for commissary items, uniforms, Phase IIA station equipment, and other inventoried items. Current Interface with MARS. Budget Reporting All Brass, a commercial off -the -shelf program from CGI-AMS, is the City's Phase IIB and Salary System budgeting system. This standalone client/server based system was (BRASS) installed in 2001 as a way to improve the City's annual budget process. Brass is managed by the Budget and Management Services Department. The system is interfaced with the MARS GEAC system to provide transaction data and Genesys (HRIS) to provide Human Resources Position Control to produce the annual City budget. Capital Project All Used to track project management and cost accounting information for Phase IIC Management capital projects. System / Unifier City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 229 of 418 Title User Department(s) Buzzsaw PMO: admin and user, TPW, Water, Aviation, PACS, ITS, CMO, City Council, public, consulting architects, engineers, etc., contractors and other project related businesses City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 230 of 418 Purpose An on -demand collaborative project management solution that is being used by CFW to centralize project design and construction -related documents, simplify communication, and streamline collaboration so to successfully execute projects based on timely decision and accurate information. Also used for secured online bid proposal submittal. Could be interfaced possibly as a linked into application, Buzzsaw is a software as a service provided application hosted by Autodesk. Not currently being slated for replacement. This product is specifically designed for and has supporting tools available for infrastructure project related collaboration. No viable source for conversion. Source of the information: Documents (MS -Word, MS -Excel, pdf, etc.), drawings (CAD files — dwg, dwf, dgn, pdf, etc.), pictures, videos, etc. created and uploaded by Project Team Members. Replacement Candidate Phase IIC I EXHIBIT O: REFINEMENTS AND CLARIFICATIONS TO APPENDIX N WORK -PRODUCT DESCRIPTIONS This exhibit contains a number of clarifications and refinements to work -products described in the RFP Appendix N. Note: References to Prime Vendor are replaced with Contractor through -out these refinements and, by inference, throughout Appendix N. Work Product 01: Protect Charter The Project Charter is refined to assign accountability to the Contractor, rather than to the City because the deliverable as described in the Statement of Work encompasses more of the work -products for which the Contractor is accountable than anticipated in the RFP. Initial Version Refined Version City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 231 of 418 Contributing Accountable \Jj V :. ':�! � . r: C"orac%r Act" "ties 3" Assist with preparation of the Project Charter Prepare Project Charter City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 232 of 418 Work Product 32: Confiquration and Unit Test Plan The Configuration and Unit Test Plan is refined: • To clarify the description of the work -product, and • To replace "Unit Test Plan" references with "System Test Plan" references in order to avoid confusion with the Iterative Prototyping Methodology's use of the "Unit Test" term to describe development object unit tests only and to use the term "system test" to apply to tests of configurable functionality or standard software functions. Initial Version Phase 02 Design ocus 03 _ _ _' Functional y0oik-product 3z, = Configuration and Unit Test Plan f,D6scription Based on completed requirements analysis and fit/gap analysis, ' the Prime Vendor shall prepare a Configuration Plan as a bridge 'c- from requirements to the configured system. This plan also documents the methods used to manage the configuration process z '' and the progression of configuration values from initial prototype to testing to production ., C" _ 4 b1e, .., ,. Prime e tdor .R Contributing Accountable Prime Vendor Acv�s, Review and Approve Configuration and Unit Draft Configuration and Unit Test Plan Test Plan Refined Version Design Functional Configuration and SystemTest Plan Based on completed requirements analysis and fit/gap analysis, the Contractor shall prepare a Configuration and System Test Plan as a roadmap for configuration activities. This Plan will list for each module all of the system transactions that will be configured and system tested. Once accepted by the City, this document will City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 233 of 418 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 234 of 418 r Work Product 65 Documented Unit Test Scripts The Documented Unit Test Scripts is refined to replace "Unit Test" references with "System Test" references in order to avoid confusion with the Iterative Prototyping Methodology's use of the "Unit Test" term to describe development object Initial Version Phase 03 Build Focus 03 Functional Work -product 65 Documented Unit Test Scripts Description The Prime Vendor will provide unit test script procedures and templates. As standard system functionality is configured, results of unit testing will be documented. The Unit Test Scripts should identify the transaction being tested (e.g., purchase requisition), the business requirements that were the basis for configuration (e.g., when processed and approved, must result in a pre - commitment in the operating or capital budget), expected results and actual results. If expected and actual results are not the same, then the unit test script should describe steps taken to remediate the issue. City Role Prime Vendor Role ontrihuti n+ Accountable City Activities Prime Vendor Activities Contribute sample data and scenarios for Develop all test scripts with assistance test scripts from _it_y project team Review and approve all test scripts. Participate in Unit Testing Review unit tests results Perform unit testing on configuration Support fixing problers found during testing. Fix problems found during t q Refined Version Phase 03. Build j ;F4Cus l3 Functional [Vork-product 65., Documented System Test Scripts 11,111bes6HIpboa, The Contractor will provide system test script procedures and City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 235 of 418 templates. As standard system functionality is configured, results of system testing will be documented. The System Test Scripts F should identify the transaction being tested (e.g., purchase requisition), the business requirements that were the basis for configuration (e.g., when processed and approved, must result in a .... prerp -commitment in the operating or capital budget), expected 3 results and actual results. If expected and actual results are not the ° same, then the system test script should describe steps taken to , remediate the issue and the results of subsequent testing. =CityA616 Contractor w e " Contributing Accountable CiiyrActin"ties ;: ; : r Cr►ritractcarActiuities Contribute sample data and scenarios for Develop all test scripts with assistance test scripts from City project team Review and approve all test scripts. Participate in System Testing Lead system testing on configuration Review system tests results Support fixing problems found during testing. Lead fixing problems found during testing Work Product 66: Integration Test Scripts The Integration Test Scripts work -product is refined to introduce the "System Test" language along with the "Unit Test" language as the predecessor task in order to avoid confusion with the Iterative Prototyping Methodology's use of the "Unit Test" term to describe development object Initial Version Phase 03 Focus p3 3 Work: Obd j'ct 66 ­ ,, ,. Build Functional Integration Test Scripts Based on the Integration Test Plan, the Prime Vendor will provide integration test script procedures and templates. After the completion of unit testing, integration test scripts will be documented by the project team. The Integration Test Scripts should identify the business scenario being tested (e.g., from purchase requisition to payment), the individual transactions and City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 236 of 418 Review and approve all test scripts Perform integration testing Coordinate integration testing. Support fixing problems found during testing. Fix problems found during testing Sign off on Integration Test Results Refined Version Phase 03 Build Focus 03 Functional Work -product 66 In ration Test Scripts Description Based on the Integration Test Plan, the Contractor will provide integration test script procedures and templates. After the completion of system and unit testing, integration test scripts will be documented by the project team. The Integration Test Scripts should identify the business scenario being tested (e.g., from purchase requisition to payment), the individual transactions and test data necessary to complete the scenario, where relevant, different variations that need to be tested (e.g., requisition to payment for both capital and non -capital outlay), expected results and actual results. If expected and actual results are not the same, then the test script should describe steps taken to remediate the issue. City Role ortractor Dole Contributing Accountable City Activities Contractor Activities City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 237 of418 Contribute sample data and scenarios for Develop all test scripts with assistance test scripts from City project team Review and approve all test scripts. Perform integration testing Coordinate integration testing. Support fixing problems found during testing. Fix problems found during testing Sign off on Integration Test Results Work Product 68: Cleansed Data for Conversion The Cleansed Data for Conversion work -product description is refined to clarify the role of the vendor in this activity Initial Version Phew U3 4111111MI Build Focus,03 ! Functional Work-product=68 Cleansed Data for Conversion Description The City will be responsible for providing cleansed source data for conversion. The Prime Vendor will be responsible for loading the source data into the system. City Rocs Prfm Verrcior Role Accountable Contributing _ City ,Activities ` Prime Vendor Activities Identify source data Assess validity and consistency of source Provide advice, as assessment of source data data validity and consistency Assist in cleansing source data Support execution of conversion programs for full conversion test. Provide source data for full conversion testing Refined Version Provide automated tool to cleanse data Lead execution of conversion programs for full conversion test Verify results of full conversion test and coordinate resolution of exceptions. Phase U3 Build {.Focus 03 Functional [=Work -pro duct '68 j Cleansed Data for Conversion City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 238 of 418 Qescnb ; The City will be responsible for providing cleansed source data for it conversion. The Contractor will be responsible for loading the ,.a, ,,, .` ,° source data into the system. ...... .. .... IN Contractor- F�e1e Accountable Contributin (. .`City'AGtiVItIQS, C011trrCtoiCtIV1t18S ..,' Identify source data Assess validity and consistency of source Assist in assessment of source data fit to data PeopleSoft tables. Lead in cleansing source data Support execution of conversion programs Lead execution of conversion programs for full conversion test. for full conversion test Provide cleansed source data for full Verify results of full conversion test and conversion testing coordinate resolution of exceptions. Work Product 81: Role Definitions The Role Definition activities are refined to replace the term, "Unit Test" with "System Test" to avoid confusion with the Iterative Prototyping Methodology's use of the "Unit Test" term to describe development object Initial Version City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 239 of 418 profiles Unit Test Roles in PeopleSoft Approve Final Role Definitions and Transaction Assignments Refined Version departments in defining security roles and profiles Create roles in PeopleSoft Phas "03 " Build :Focus 08 Security and Internal Control � Wor"roduct 89 Role Definitions Dscriptiort A list of roles, with a description of the business responsibilities for each role, a list of transactions to which the role provides system access, and a list of authorized field values and permissions which the role can access. "City Role Contractor Role Contributing Accountable City Activities �" Contractor Activities Review and Approve Roles and Descriptions Document Roles and Descriptions Confirm transaction assignments to roles Propose transaction mappings to roles. Support definition of security roles and Advise and assist project team and profiles departments in defining security roles and profiles System Test Roles in PeopleSoft Create roles in PeopleSoft Approve Final Role Definitions and Transaction Assignments Work Product 83: Unit Test Script Review and Recommendations The Unit Test Script Review and Recommendations work product is refined to include the term "System Test" with "Unit Test" to avoid confusion with the Iterative Prototyping Methodology's use of the "Unit Test" term to describe development object Initial Version Refined Version City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 240 of 418 I Work Product 84: Unit Test Results Review and Recommendations The Unit Test Results Review and Recommendations Work Product description is refined to include the term "System Test" with "Unit Test" to avoid confusion with the Iterative Prototyping Methodology's use of the "Unit Test" term to describe development object Initial Version '?hase 03 .n. Build City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 241 of 418 Results and provide comments to the functional team Refined Version and provide comments to the functional team Ph "" Eli Build Faces 0$ Security and Internal Controls Morkroduct'84' `; ` System and Unit Test Results Review and Recommendations 4 ptiori. The Contractor's Security and Internal Control team will review r system and unit test results, as necessary, to assess them for adequacy of testing and identification of potential internal control weaknesses. Observations will be documented and provided to the functional team so that they can incorporate recommendations into the additional system and unit testing. City=Rczie F' :Contcador:Role, Contributing Accountable City Activities Cantrecfcr Ac#ivities Participate in the review of the System and Lead the review of the System and Unit Unit Test Results and provide comments to Test Results and provide comments to the functional team the functional team Work Product 105: Proiect Close Out Report The Project Close Out Report Description is refined to incorporate mutually agreed upon system acceptance criteria. Initial Version City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 242 of 418 IF � � • ■ � �' � if � preventive actions Refined Version Phase 05 Go -Live _ Focus 01 Pr lect Management - Control - Work-produot 105 Proms Close-up Report Description Based on the Contractor's recommended methodology and as outlined in the Project Plan, the City shall develop and execute project closeout activities. Project closeout activities shall include: • Final documentation review and acceptance; • Final project payment schedule reconciliation; • Contract closeout (for each phase); and • Team member roll -off and reassignment plans. • Verification that all deliverables as defined in the Contract have been completed and signed off on by the City Project Manager. • Verification that mutually agreed upon project documentation has been turned over to the City Project Manager • Validation that City's data has been converted in accordance with the Data Conversion Plan • Verification that City resources have signed -off that the Contactor has provided the knowledge transfer as defined in the Knowledge Transfer plans for City project team members City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 243 of 418 Verification that formal transfer of all system administration responsibilities (System and Database Administration) from �U the Contractor to City's Production Support Team has taken place, as described in the Roles and Responsibilities section of the Statement of Work 3 City Rc l WOontractar Ro[± ' Contributing Accountable City Activit es: i1tr dor Activities Execute Project Close Activities Develop Project Close activities as part of the Project Plan Develop Project Close-out Final Report Contribute to lessons learned session Document all lessons learned with preventive actions City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 244 of 418 EXHIBIT P: PROPOSED STAFFING PLAN City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 245 of 418 ' tit Fool Wroth Alt:sc 16 I ?N,1Y1•h111u J.'''1- 7111,ILLL'r1�Ir1iI1h1�7N1U1rl'�L�wLI (lrid -. .. 41. tly6ta Wl} XyL9O��LIlYt1"iVS Wa�uvrrx r�r.�iW .. . 7kao,rvx �.iJmu, '_tat `IwMrT _Ganlurritr 7t,m." FT - inul i:3lo MniNfIFL+era'Y1wf ]k��- — - 1. 1'..'i lei 16- fit_ _ _— luj .1iu Sid LGi Fv :i-I r- — I _I�.,_ 1 f , _-- •_ 1 ]�.: In'. 1��: jr I _ "F 11: 1.4 I r ' I . - 1 Y 460 L_ I +.huf1 .L4r SDi SUL %U AITI ?1. f -',�+l3s+YiiMLP' A91 „7 a,a 1In7 df.1 9W' 14 w� 111t ila7 S1� i� r ++1 n_2m fMLNUL ti rnl'. II. Pir i-- I i �li,nl - I-Y Id 1� 5,. �' I g117rrLw11' _f tlanywlgp.y lVJ��lrlluklgllr,l Vi1n L]►[1Y tiVl{�g1411�C'�111}I 11nrFY RI '.1,1n�„+f tin�14`naut�-� �INwIi I'l.s 141�11�►:y.V11r"R1''y.�' i11...r)l CLw1u.1iTT''T-+k ■i4.�L11�5 ti�Xirvv fidYI�41nGLI W .. F4rhIhITFILE'Yl 11rn�• IhLir�l'� T 111sI klr 1"mm i.lnel.era�7l� I ' --- TRj — -"l~'- iYl lFl In1 I- -- 1 - Ir- i lu' � '—'�� �.. - In lc 7�r� 1��i 1+�� - , 33c 7= 1YJ, 3itr ++J!I 9!i I� SI r3 1rl{ },S JI 75>Lti wl1'1r' ■19 ' -- _ 1fr� Y 1` in"- IT• 3Lt- I[' I * 1•- 3 •_ -A �"- •. ••— +wi %:A "- �4 1T, lh- �f _ I..- I•.- -�` '•� - Int 1M1i I-- 1__ .�- l9' 13 _ 4U, ■11 f - 4f itillb- --- 1wiYJ roil, iliJll L•,-� I --e -ihTi abi41 %11rr} iAY♦ fe-+1�t#�� a/J' M a.r,1 �t','�5 4- 21N: =w,= � Jr- •.tt ==!5 Sli �?. 31011 >!iiU' F:l 1CCLIrJI,�L Ll IMJpn —'iel. I OR kit IC Ipkm m u1:177t6? LS+IT� �rY'1,n1Ya9'ch�� fi�Yya3L*,r,QIlk, t jY-in i Jr rn 1i {. , a63 Sr.: fL# 10,1 Ifho too I .5 VY 1 u 1 JV dr }1 n 1 1�� 3 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 247 of 418 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 248 of 418 dhV 44 F17r1 Wrt4rh Vnnm,, JA 9L�in1n�rrxi�wur.+ (rnrr% IrMr��p��,.laFaeo.a Arm �...rla�l l lli IN NI"" it J t.u10R0.4 in,..:l'h:+.r Jrwltn., F�ji�}y'�rb �mn�'hrLT Res,urtes �inr 3{.n.e.c �W{iri.�Ta4 i�. L] .1Lyr.wrwur _ ISi1W d n1 i.r W.1%;. .nnu r fit•' n4.m1r =n 7erycr'1�u4!c �. c..': c—i L, ft j,"r—n—i ICE 4}. 1b I,y/y. TIrr�IYo_ rLC..wr- 1-,- 'I l e�nPy; 7M1 t�fLXMurRaailWua I I� I J-,1.WJ4 ,`J�I IFua �R t.'mr,-.-.II!!"rrr11�..1,1Lyr.+hT111' �^P ,7MI'IR W `il�i+Il�,y1Y� — if1YVS1iIlYLB�I F.n 1��1ndr.r iuow��nul � ho-rl���yn11k 7eG4i lq of t11n1►^Ik tIl�Ihlr�4i�r • T�J I � I'�''Iwa t 4cI OHM jif 4l�4-+I Jl�• ta, h r`.rWrtrr �LL�l� r1.4n4 ram,= rr x.:LIIIP-- J rf-I+YIY"hYll'r14+17 7y.1- W I IL it li in in n1 -E h ■ 14 I I Lli= w !Y• .Jd'L :ihi i"4 ILM tF :Lri liil'i FLii Y kpt If + i, —i 771 Y - T + 1-7 rA .111 1-1 N' ITLr p' I-f .. I ip +u W. I _ -7j1Er'' Ylt Kl- I It T14 Ty I TT-1 ! R --P# lr ti- 1} In: n 1 f-- - -- - h- 31r— I iM1t vL' 1wT'� i-i 1L1r1 4Fi7C 1i7r' "#! IRE :S1t 3,i MM -1_- 1! l ,}1 '..' j117 FLW nir' ]rn■ ft; Jn} 7G- 3/90 Ti s}i ;A" Jr [wi. if 1}:: tn., IXT r ihs ! Jn1 L'I 1n^ L1 - I 1 +�.. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 249 of418 Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun - City of Fort Worth - Phase 2B Month 19 20 21 22 23 24 ' 25 26 27 28 29 ' 30 31 32 33 CROSS -PHASE RESOURCES GIBER Cross -Phase Resources Account Manager 20 20 20 20 20 20 20 20 20 20 20 220 Project Manager 0 81 81 81 81 81 55 55 55 82 82 82 816 Internal Controls Partner 8 8 8 8 8 8 8 8 8 8 8 8 96 Change Manager 81 81 81 81 81 82 82 82 82 82 82 897 ITotalCIBER Goss Phase 8 190 190 190 190 190 165 165 165 192 192 192 0 0 0 2029 1 (City of Fort Worth Cross -Phase Resources Assistant Director- financial Management 83 83 83 83 83 56 56 56 84 84 84 835 Project Manager 83 83 83 83 83 56 56 56 84 84 84 835 ERP Business Planner/ Administrator 83 83 83 83 83 56 56 56 84 84 84 835 Process Internal Control 167 167 167 167 167 167 111 111 111 167 167 167 1836 Change Management Team Member 167 167 167 167 167 167 111 111 111 167 167 167 1836 ITotal City of Fort Worth Cross Phase 334 583 583 583 583 583,E 390 390 390 586 586 586 0 0 0 6177 .,,, f�•� , , � ,,��a � , '"���_..'���;'� � ` ,°���/`�i�y� , ,,, ,�i SS' i� 78' f �8. �, . � � �A..r; ;�. � ,. ` 32Qfi ICIBER Phase 2B Functional Hours BudgetPrep 163 163 163 163 163 163 163 163 163 163 163 163 163 163 163 2445 Training Team 163 163 163 163 163 163 978 ITotal CIBER Phase 2B Functional Hours 163 163 163 163 163 163 326 326 326 326 326 326 163 163 163 3423 ICity of Forth Worth Phase 2B Functional Hours BudgetPrep 167 167 167 167 167 167 167 167 167 167 167 167 167 167 167 2505 (Total City of Fort Worth Phase 2B Functional Hours 167 167 167 167 167 167 167 167 167 167 167 167 167 167 167 2505 I GIBER Phase 2B Technical Hours Technical Lead 81 81 81 81 81 55 55 55 82 82 82 82 82 980 (Total GIBER Phase 2B Technical Hours 0 81 81 81 81 81 55 55 55 82 82 82 82 82 0 980 City of Fort Worth Phase 2B Technical Hours Technical Lead 83 83 83 83 83 56 56 56 84 84 84 84 84 1003 Tech 167 167 167 501 DBA 83 S3 83 83 83 56 56 56 84 84 84 84 84 84 Total City of Fort Worth Phase 2B Technical Hours 0 166 166 166 166 166 279 279 279 168 168 168 168 168 84 2591 a , ? Z50�259, �e250 , 'z5p. 250. - MI �:",.�, �7V, City of Fort Worth /GIBER, Inc. fyt1445, 245 16 6432 Professional Services Agreement Page 250 of 418 672 11350 11350 11350 11350 1350 1382 11382 1382 11521 1521 15211 580 580 414 17705 ` Thestaffin estl�iove jiateche fixPpolti colnd dr�Qj inclt final cal City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 251 of 418 The staffing plan that follows outlines both in scope and optional Phase IIC staff. In the event the City chooses to "unbundle" and implement the "in scope" and optional scope separately then additional costs would be required for the optional scope with the following positions: account/project management, change management and technical lead positions. This situation would warrant a change order to add these cross phase functions back into scope. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 252 of 418 1 1 1 1 i 1 1 1 1 1 1 A A I 1 I 1 f A . .., _ Oct Nw '. Dec '.1en Feb M.r APr M.Y )un Jul AuR Sep ''tht Nov Dec len Feb Me. CIN at FOR WORK - Ph... 2C c RsmwaR Rraotmcbs R Month s 26 2) za x9 30 11 32 33 34 31 31 a) as 39 40 41 41 I Ie�l ru.r]tevoo•cev j jl I 1 _ _ Acmu nt 20 20 20 21 Ol 40 1 4" 40 M 40 340 P!/)�jt hLn.eer 1(1(nu trob P.eew sl 34 54 16 8 Rl 3 I ] 163 16l 163 1 8 8 8 1383 ll1 Q.n el Rl 81 82 82 63 1 l 163 163 41 1467 1 1 n I Pve hre6.R I I I I Account 411 l 10 40 40 40 40 Zan PJPx�'t M.n�/,nr (n6nnqq.I Canb.�x'.P�h P.rmer SXrorxl-Pmcha nre O O a I I 1 1 0 0 n 0 O n O I 11 ° 3 116-1 163 86 ]3 161 3)4 3 ])3)4 3)4 3)9 3J4 4 I a Jn 4tl 9)x 1Tw.1 GIBER Csoe. Phe.e I lsl 171 161 191 111 111 3)! 374 374 374 374 374 374 1374 374 374 374 374 5696 IClenn.lP l �lirKr r-Fuunc'vI M..^..ee...ent SS 35 x3 16f-1' R) la PIS' Men.�pm dliYbnelneaa l>t.nner/AaMmao-.tnr S5 5! ss a3 167 1.a R3 41fi 111 I Peaaaa lntemel Control 1. 112 112 167 6> 167162 16) t1J 133Y 1 Q neee.nm iced 55 SS 55 93 R3 83 167 167 167 167 167 167 1416 ' 1 Q.n M.ne� [Teem Member I .i.6M�-Cant here 112 f!! 440 f94 444 444 499 499 999 151 )Sz 751 751 )3] 131 " ° 0 0 0 0 336 733S i I rg I A-evi—,;sbnt Direclar-Finenci.l M.neeemer.t 167 / I Bm33iu"��esa.nese�lMr vemee /AdMnbwsa s3 16> > 16> 6J 110 1M 2 0 P« 16> 16> 167 11117 111 111 -1 QQsPEx�K;6l..V1rornnLdm 11b6>> ]6J]b,6) l6)) tm2m�e I- Pn{{ n o 0 I sS 6)1sJ16)sn4Sn1x434 334IY1 a4 .ss4 w 117 16) 167 I._ _Y ]xn2 1n62 3"7 l_7 T"MI Clly d PmtWvPo Go.e Phe IGIBBR Ph..e 2C I 1 arP�(3Fe I Intr9nel ./Saurlty Le.d a2 R2 s2 62 82 12 82 1 I Gtt771 IPe{�k Le.d I TnInMq Twm 163 163 163 163 163 163 63 63 I.,163 169 163 163 163 1b3 163 lYSfi I 9J8 I I UPK IMP1 163 163 113 163 163 1E3 I I 2A Ysr End So�rl 3R6MMl-CanrMlProkc!• I— 1n00 0 I 24.9 245 243 245 211 245 571 3 11 17. 371 3)1 3)1 ]n00 I100n 0 I o 0 n 6A96 I Pwch..Na IntrmelCm.tml./SFueIty l<ed I I I 1 I 1 s1 Rl Pl 1 ] 163 I 9J5 eP.acu..ne.t 163 163 163 t63 163 l63 163 163 163 I ] 3 ] . 2934 Purch..inq/Pee.— 163 163 163 163 — 11' 113 3 1 2934 VL Inwnb�j' 11L Trelner. l2) 163 163 163 163 163 16S 163 163 ]63 ]63 163 16.1 ]63 l63 _ 3 I 12934 j Is3 I ]63 Itl>9 SNrab/-P—..— 1M13 1H9 M6 496 11+ I 32.1111 2 I6 393 1141 1121 1Tnle1 CIB)ER M..e 2CPo .eB.n.trM... 1111 s2 222a. I >34 >J4 )3f >3I �34 13M I304 1466> 1417 143 65 >34 67I 1467 I xlll l 21n I ]u11 uz) z l 6 2 1 nx34 I I I I 1 1 1 I I qa r Ph..e 2e P.nrtmnal Hn..e I I 1 I I I 1 1 I-- --- I G iml P�y-b iad Tt. ner. 22f 167 1 167 167 167 167 167 tb> 67 1 117 167 167 I 167 I I 1 1 200i I 16> 167 1167 1167 1167 upnJ7) I > 1 1 J 1 6> 1 167 11"9 1 1 1 I a s sRrd/nl-c.Ptt.IPmhre. 16J 1 16) 16> 26) 16> 16J 16> 50I Ism I SPI Sot Rol n I 1 I I I I P.rcM.brR .Prmuremmt I I I 16> 16> 16) 16) 16> 161 16> 16> I6> 16> 16J 16> 16> 16> _ _505 Purch.eMn/P—w.v 16> 16> 16> > ]6J 16) I6) 15) 16J 1 1 InvmMr'1 Txlner. lx] 16J 16> 16> 16> 16> 16> l6) 167 _ 67 167 I6> 167 16] 167 1 167 167 3006 1 2xa9 ]6> 16> 369 UPKJJJJ)) 9xb(6(.l-Perch.elrrR 3°3 30] 3n] 50t se] A3> afif Of;> 16> 15] lb) 16> ]6J 301 S01 s 33 5 x93 Nis 4 21>1 I]]3 ]169 H691i002 fi6a 66N ITM.I CIW of PtetWalh Pheve 3C Ponctbn.l Hoo<. 66a 666 66n 666 666 6a9 bee 133a 1336 13aa 1336 1336I 116Y t]69 1169 l0a( 6a& aax 1>x01 IGIBBR Phe.e zc Technlc.l Hm.. —.I— lad 54 54 54 al 1M13 f63 163 121Y .4rrbhNel-C.mMlProhcre 3 31 31 al el a1 a1 of 16a 16 163 163 0 O u 0 0 P•.•h+•hr I 1 1 I I Tedtnlul —d 1 I I t 3 1 l a l 1 3 1 t 3 1 971 s46MMr-Pseh.vhpr a n a 6 0 n ° I X I X n 1 9 1 I63 163 t63 I I6a 163 z63 I I ° I I I I I I I I I I I 1 I I I 1 I TaYI GIBER Ph..e 2C Technic.) Hour 54 I 51 54 61 a] al al 1 ai 1163 I ]63 I63 163 I ]63 iba 163 163 63 161 2191 I I I I I I I I I I I CEmWhM City of Fort Worth/C7BER, Inc. rz• Phave 2C Technir.l Hwr. 1I I II II I I I I 55 I 33 55 83 93 a3 3 3 83 I 83 93 83 I I 2 DBA 55 SS 53 a3 83 R3 ID93"BRb6AMro"r.'r-- P"."rcBh..r.PMmR" " 0 ° "O ° "° I66 166 I66 166 1636 1I 117 ' 2111 "16°) 'I°b°7 I1 1 6243 Professional Services Agreement Page 253 of 418 94 tl4 I6> 161°> 1 1167 167 ]6) 1002 0 O O O 394 34 334 334 2340 ITot.I Gty of PwtWath P6e.e 2C Technlc.l Hn"ry ]l0 ]10 110 lab lab — 166 166 ; 334 1 334 1114 334 i 334 33! — aa9 334 334 1su0 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 254 of 418 I 1 I I I 1 I I I I I I I 1 I I I I I City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 255 of 418 EXHIBIT Q: VERIFICATION OF SIGNATURE AUTHORITY EMBIT 0:1FOrif%13 On Of 61anakture Autharft Full Legal Nam Of Conq my, CIBEk Ind Loyal Hddrsas: WW S. Fiddices Grew Cb'c* 01400, ifgetssood ViiaP. CA 60111 Swvtoss to be pwAdsd: FAmfacatanal t mwA V Sarvkas fnr ft Impb nt modMun of 0"K10 POOP1030 NIBNAgement SOdvr M Exec€Am of this Slyrtaaua VeAMation Farac fForm") bambyt colliks Smt the fopowing irsrltvfnwlb,niVer pwftrrs leave Ste aqf 0* tc lag* WW the Corn wW and to exambo any agreement, amendment at dwVe ruder on behe4 of Gauvany. Such bhWlnq authority has bean grarthat! by Proper Order, resolution, anilin nm or char audtaftatlan of Ccsnparrv. The City is fully enffikd to rely on Sue rtmm otfyr and mpraosrdati n sell tM in this Form irk endsA V Irt any agrsernent or aotatdatent vAlt Company, Ccrep m +ill submit an updated Frmn W tfn ton (10) business flays If th4m We any ahan9ss to Me s rotaq #may- Tian City is entlaea m r* on arrp cerrmtt mmutad Fmm and rt recetwo a mvissd Farm 9*4 has been "poly wrscutsd byih* Carnparty. t. NMW Oersus Wer I're Govarnrrrset, Hlpiwr EdvwNOn �na4re I Naaw: Tory Ph North Aumdu n Pradcas 3. Name: ChO s ft on E77 .. t11A1ssafsslgattt� awt t5gteradgns k Noma: Rk* Genavess Frem= 01111par S�rtabae NMrae: 04V0 PpkN t ,,,,,yr„„� 8{ynaCua � Preatdenk t C,Eq oft" .&&4" cio urral; wolh / cmR,tw fv*4a*a SwlmAsrmone pnok lem Page 256 of 418 SOFTWARE REQUIREMENTS AND RESPONSES REFERENCED BY EXHIBIT I Two tables are included establish the software requirements: Table 1: Phase II Software Requirements and Responses. This table consists of the software requirements and contractor responses provided in their response to the request for proposal. The full scope of Phase 11, which includes procurement and inventory functions, is represented in these requirements for the purposes of defining the requirements scope and software fit response obligation for the contractor for Phase IIA, Phase 1113, and Phase IIC — Capital Projects and of defining the additional requirements scope and software fit response obligation of the contractor if the City chooses to exercise the option of implementing Phase IIC — Procurement and Inventory Option. Table 2: Review Due to Phase IIC: Procurement and Inventory Option. This table consists of those requirements identified as having a potential for the original software fit response to be impacted by the decision to delay the implementation of the modules to support procurement and inventory functions. Also included in this table are requirements from the set of procurement and inventory requirements that are not entirely dependent on delayed functionality or relate to the vendor table, voucher build and commitment control components of PeopleSoft that will be implemented to support the interface. The requirements of Table 2 will be included in the appropriate functional team's Fit -Gap analysis process or PeopleSoft — BuySpeed Online Interface design process for a determination of impacts on the original software fit response and identification of a recommended approach for resolution of a gap. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 257 of 418 Table 1: Phase II Software Requirements and Responses The following pages contain the Contractor's responses to the Software Requirements that were provided in their Proposal, with noted revisions. Functional Requirements Matrix General instructions chengQs should be made to the stntctura or contentg q( the Requirements Matrices xcel files. Responders are welcome to make additional copies of 9 appendix for working purposes, but the official response must be returned in the original format. The completed requirements matrices should be included in hard -copy or Adobe Acrobat pdf file format. The completed requirements matrices must also be returned in Excel format on as well. Responses to the requirements matrices should be offered in light of the complete solution being offered by the responder (i.e.. the primary software product, plus any third -party products offered as an integrated solution). The purpose of each column In the matrices is defined as follows: Reference Number — The Reference number has been assigned by the City to Identify the specific requirement or sub - requirement throughout this RFP and the Responder's proposal. Requirement Text — Statement of the functional or technical need to be met by the proposed software solution. Degree of Fit Response — Proposers must indicate whether their proposed offering meets the listed requirement by providing a response to each requirement or sub -requirement requirement using the legend that follows. Areas that are greyed represent Information provided to structure or add context to the requirements and a response code should not be entered. Any requirements that are left blank, or requirements for which responses other than the responses listed below are given, will be evaluated as an'N'. Module — This column Indicates the software product, or module therein, that is necessary to achieve the indicated degree of fit response. The specific PeopleSoft module to be included in the software procurement documents should be listed. If the indicated fit is achieved through a third -party component or tool, that component or tool should be listed. For example, If the primary software product and a third -party reporting tool are required to accomplish the Indicated degree of fit response, both products should be listed. Complexity of Modification — Any degree of fit response indicating the need for modification or development of custom functionality must be accompanied in this column by an estimate of the number of hour necessary to meet the stated requirement using the following definitions Low — less than 40 hours Medium —41 to 120 hours High — greater than 120 hours Hours should include an estimate of design, coding and unit testing the modification Comments — The comments column should be used at the responder's discretion to offer additional information or assumptions regarding the indicated response. Comments should be added for ournoses of clarification, not to limit or contradict the nature of response. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 258 of 418 X 1 1 SF — Standard The software provides the requested functionality without screen, code, or design changes. The product can satisfy the Functionality specification 'but -of -the -box" without any modification to the standard baseline software offering. Only use "SF if the baseline software as delivered in the current release fully meets the requirement "as is" or through software configuration. NR — Provided in The next release of the software will provide the requested functionality without screen, code, or design changes. Only use Next Release "NR" if the very next release of the baseline software will fully meet the requirement. Only formal releases that will have been published by the anticipated start of the project (October 2010) shall be considered when addressing this requirement. A brief identifier/description of the referenced release should be included in the "Comments" section. MI — Minor Minor modifications must be made to the standard software offering utilizing the delivered "Development Toolset" to satisfy Modification the specified requirement. Examples of minor modifications include changing a field length and creating a new view. In no case, however, can a modification exceeding 120 hours estimated work effort be considered minor, regardless of the development method. A brief explanation is required to support any proposed minor modification; explanations should be provided in the "Comments" section of the matrix. Estimated costs and work effort associated with each minor modification will be addressed in the implementor cost proposal. MA — Major Modifications meeting either of the conditions listed below must be made to the standard software offering to satisfy the Modification to specified requirement: Source Code Required ' Estimated work effort for design, coding, and unit testing exceeds 120 hours; or . Change to underlying source code. A brief explanation is required to support any proposed major modification; explanations should be provided in the "Comments" section of the matrix. Formal Estimated costs and work effort associated with each major modification will be addressed in the implementor cost proposal. RQ — Provided The software supports the data elements necessary for the report/query, but a custom report/query would need to be through developed to meet the requirement. Reporting or Query Tool If a brief explanation is required to support any proposed report/query; explanations should be provided in the "Comments" section of the matrix. Estimated costs and work effort associated with each custom report/query will be addressed in the separate cost proposal. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 259 of 418 CD — Custom The desired feature or functionality is not available as part of the standard (baseline) software functionality but can be custom Development built to satisfy the specified system requirement. Only use "CD" if the functionality can be custom developed as a "bolt -on" to the software without requiring changes to the underlying software source code. A brief explanation is required to support any proposed custom development; explanations should be provided in the "Comments" section of the matrix. Estimated costs and work effort associated with each custom development effort will be addressed in the implementor cost proposal. TP — Third Party The desired feature or functionality is not available as part of the standard (baseline) software functionality but is a standard Software feature of third -party software proposed to satisfy the specified system requirement. The third -party software, which is fully Required integrated with the system, provides the requested functionality without screen, code, or design changes. The proposed third - party product can satisfy the specification "out -of -the -box" without any modification to the standard baseline software offering. Only use "TP" if the third party software fully meets the requirement. NA — Cannot Meet The desired feature or functionality is not available as part of the standard (baseline) software functionality, in the next Requirement software release, through modification/enhancement, reporting tools, or third party software. The requirement would most likely need to be met by a process workaround or by interfacing to an existing legacy application. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 260 of 418 V min .1m Num Ca 4....... 15-4 Degree of Fit Module Complexity of Common Requirement Te.t - Prior Change 3ortl Sort 2 Sort3 Reqt Num Ca agory rise Modilil-fi.. I MM, �W 1, F1 00 01 00 01 provide a i try .- ci Inancla Classification reporting needs through its financial data classification structure (FDCS), and retard transactions against key elements, indudino but not limited to: IF11 001 011 011 001 FI-00-01-01-00 r 00 - Data Fund s, Gen..( Ledger _ lassifidation FI DO F1-00-01-02-00 00 - Data Sub -Fund SF General Ledger - 0, -1 1 1 qN" - ' F1 00 01 03 00 F -00-0 -03-00 lat [)apartment SF G.—al Ledger Cl.ssfficabon F1 00 01 D41 00 FI-0001-04-O0 00 - Data Hierarchical Organization (Department, Division, SF General Ledger C 1—ificabon Section Ft 001 01 051 00 Fl-OMl-05-000() - Data SF General Ledger Classification Ft 001 61 061 00 FI-00-01-06-00 00-Date Program SF General Ledger Classification F 11 00 01 071 00 FI-00-01-07-00 00 ' Data District) SF General Ledger CA— ification FII 001 fill 081 00 F100-01-08-00 C00-Date Project Number SF General Ledger Project I ... ificafic' Costinq' I F1 1 001 011 091 00 FI-WO1-09-00 00 -Data I Work haze or Work Smakdown Structure (5 levels SF General Ledge, Project Classification below work chase) C-tin.' I F1 GOI 011 101 001 F1-00,01-10-00 00 - Data Job SF General Ledger, Project Classification I Cost IFI GOI 01 11 00 Fl-00-01-11-00 00 - Data I General Ledger Account (Expenditure Object C Revenue SF General Ledger C113s(6rAdon Sacra nr Ra lance Sheet Accountl IFI GO 01 12 00 Fl-W-01-12-00 00 -baba Grant SF General Ledger, Grants, 1 1 Classification I PrQTtdCostino F1 CIO 0 3 00 Fl-00-01-13-00 00-Data Grant Phase or Activity (S levels below GramGramPhase) SF General e gar, Grants, Classification 'roi.c, C."" IF1 00 01 14 00 FI-00-01-14-00 OO - Data Function SF General Ledger Classification IF1 00 01 is 001 F1-00-01-150g 00 , Data I Fiscal Month SF I General Ledge, Classification IFI 00 01 16 001 F1-00�01-16-00 00. Data I Fiscal Yw SF General Ledger Classification IF1 00 01 17 DO Fl-00-01-17-00 00 - Data User -Defined Field 1 SF General Ledger Classification IFI 00 01 1 8 00 FI-00-01-18-00 00 - Data User -Defined Field 2 SF Gene, Ledger Classification IFI 00 01 19 00 Fl-00-01-19-00 00 Data I User -Defined Field 3 SF I General Ledger Class ificalion IF11 001 021 001 001 C FI-00-02-00-00 OO - Data ISystent provides hierarchies for each element of the Data lasstfication Classcafion Sir.&.,. I I F1 1 0101 021 011 001 Ft-00-02-01-00 00 - Data FundI SF General Ledge, aussiflicatton F1 00 02 021 00 Fl-00-02-02-00 COO - Data Sub -Fund SF General L.dger 1—ftabon IF CIO 02 031 00 Fl-00-02-03-00 00-DataDepartment SF General Ldger - Data Classification 0 n IF 1 00 02 041 00 Fl-00-02-04-00 C 00-Data Hierarchical Organization (Department, Division, S, General Ledger 10" ification = I IF 001 021 051 00 F1-OD-02-05-OD Os Data SF General Ledger class 'Ificartlon IFl 001 021 061 00 F1-00-02-06-00 00 Data Program SF General Ledger Cla-'ification IF1 001 021 071 00 F1-OD-02-07.00 00 - Data Location (e.g., Council District) SF General Ledger Classification I F1 001 021 081 00 FI-00-02-08-00 00- Data Project Numbs SF General Ledger, Project I Cl.-W—d- r I Costing I I I Fl 001 021 091 00 FI-00-02-09-00 C 00 - Date Work Phase or VVO Breakdown Structure (5 levels SF General Ledger, Project I la"ificate' aow work chase) Costino IFI 001 021 101 00 F1-00-02-10-00 00 - Date SF General Lodger, Project Classification n IFI 001 021 111 001 Fl-00-02-11-00 00 - Data General Ledger Account (Expenditure Object Royal General Ledger Classinds"n Source or Balance Sheet Account) IFI 001 02 121 001 FI-00-02-12-00 00 -Data Grant — SF Cenral Ledger, Grants, C lassiflicatiort P, iCtit no General IFI -1 02 13 00 Fl-W-02-13-00 COO - Data Grant Phase or Activity (S levels below Grant Phase) SF I Classification Pro=c-finq 0 r. IF DO 02 14 00 FI-00-02-14-00 0 -Data Function SF Ledge Classification IF1 001 02 15 00 F1-0002-15-00 00 - Data Fiscal Month SF General Ledger Classification City of Fort Worth CIBER, Inc. Professional Services Agreement Page 261 of 418 IFt 00 02 16 00 Ft-00-02-16-00 00-Data Fiscal Year SF General Ledger Ctassufrad- F1 00 111 17 00 F14)D.02-17-00 oo - Data User -Defined Field 1 5F General Ledger Classification F1 00 02 18 00 F1-00-02-18-00 00 - Data User -Defined Field 2 SF General Ledger I Classification F1 00 4E 19 00 F1.00.02.19.00 00 - Data Usan-0efined Field 3 SF General Ledger Classification F4 00 03 00 00 F1.00-03.00-00 00 - Data System provides the ability to maintain all revenue and SF General Ledger ClessikaUon Lure transactions at the lowest level of the financial Aexpryendi safice F1 00 04 00 W %1-00-04-00-00 00 - Data Sysie n provides multiple organizationat structurea SF General Ledger I Gl"'Ificeaon - -man Uv �(w far rt`fty µre s. Ft 00 05 00 00 Ft-00.05-00-00 00 - Data System provides)he ebilh = group and summarize detail SF General Ledger ClassUication information according to hierarchies maintained in the financial data dassfiestion structure. 00 111 00 00 Ft-00-06-00-00 00 - Data System provides the ability to track starisllcal data (e.g., SF General Ledger JF1 Classification square footage, transactions processed) to any combination of data elements within the Financial Data Classification Structure F1 00 07 00 W F1-00-07-00.00 00 - Data System provides security that restricts maintenance of $F General Ledger "'rfrJUon FRCS valtyas tq �uthgrjzr(+r) ucPrs. F 1 00 08 00 00 1-00-08-00-00 00 'Data System aliowe 6 noel fats classification field lengths b SF General Letlger CtasaffMetlon ne confioured. F1 00 09 00 00 F7-00.09.00.00 00 - Data System permits specified account balances to be stored SF General Ledger Classification inception to date separate from general ledger (e.g., project accounts. grant accounts). F1 00 10 00 00 F7.0040.00-00 00 - Data System permits all finencial data Gasaficetion elements to SF General Ledger Claeeifirabon be added or drenged to an active or inactive status by agt ed use((44 00 11 W 00 F1400-11-00-00 00 -Data Sys am uses effective dating when adding, changing, or SF General Ledger JF1 Clasedkation dextiveting any element of the financial data classification structure and validates entries based upon the effective date. F11 00 12 dA 00 F1-00-12-00-00 00 - Date System provides coding reduction techniques or tools to SF General Ledger Claenhfiration reduce the amount of data entry required on a transaction. F7 00 12 01 00 F7-00-12-01.00 00 •Data A coring reduction value or code references specific SF General Ledger Classification user -defined combinations of any element of the finendaa data clacalfaation structure. 00 12 02 00 F1.00.12-02-00 W -Data Data entry of this specific wdlrig reduction value on a SF General Ledger JF1 Cle—fic.bon transaction can infer er -look uD the combination of elements Instead of requiting data entry of each of these element: on the transaction. 00 12 03 00 F 1-00-12-03-00 00 - Data Data entry one element of the data classification ry intolas MA General Ledger Cffication struehim defaults or looks up' other values of thedata JF1 classification ntnuctu s through a mapping table. F1 00 13 00 00 F1-W-13-00-00 00 - Data System provides an optional level of detae below the city SF General Ledger Claedfkatlon revenue source and expenditure object wdee, established for use by Individual departments at their dl—tion. The department codes should sulomatxaly r(A up to dly Qpa. F1 00 14 00 00 F1.00.14-00-00 00 - Data yclem allows financial data classification stroctum SF Germinal Ledger ClassdMatlon changes and maintains records of the historical financial data classification structure based on effective -dated tables. 00 15 00 00 F7-00-15-00-00 00 - Data System allows the use to upload financial data SF General Ledger JF1 Classification classification etruca"a records from third pony products, including but not limited to: Mdcraso8 Excel, Microsoft Access, and fyhe( eljAun�O(t prypitgpe� F1 00 i6 to 00 Ft-00.16-00-00 00 - Data System provides for Anancial dale clltss iceoon structure MI General Ledger Classiitai elements to have a long description of at least 50 w snore�� 9(i�ggrs. :" Ft 00 17 00 00 F1-00-17-00-00 00 - Dote Sys m provdes Mr y data ciassiffcetion structure MI General Ledger Classification elements to have a short description of at least 25 I at ark red�is. Ft 00 18 00 00 F1-00-18-00-00 00 - Data S is se8 ancug by any user-spectfied or all Char SF General Ledger I ClassBkation of Account elements. I 00 19 00 00 F11-00.19.0g-00 00 - Data System provides the ability to summarize or present detail SF General Ledger (Ft Classification on any firaincial da/taeclassification structure combination both online and y net )r rpechan F 00 20 DO 00 F7-00-20-00-00 00 -Data System provides re a �i'Ay to have muRlpk ledgers that MA General Ledger �Fl Classification are able to be updated simultaneously. Ft 00 21 00 00 F1-00-21-00.00 00 - Data System provides the ability to support project and grant SF Project Costing, Grants Classification accounting both individually and in combination (I.e., the I arant and oroied structures are distinct). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 262 of 418 1 1 1 1 1 1 1 1 1 1 a I HIGH This functionality is not cunenUir available and will need to be created using PearileToois. MEDIUM MEDIUM MEDIUM This functionolity is not currently available and will need to be created using PeooleTools. System provides the ability to group and summarize detail information according to hierarchies maintained the financial data dassfication structure. grammar System permits specified account balances to be stored inieption to date separate from general ledger(e.g., project accounts, grant accounts). formatting F1 00 22 00 00 F7-00.22-00-00 00 - Data System provides the ability to support various project/grant SF Classification years in the COA, including projects that cross fiscal years F1 00 23 00 00 Ft-00-23-00.00 00 - Data System provides the ability to track contract and project MI Classification numbers in the general ledger for reporting purposes. F1 00 24 00 00 F7-00-24-00-00 00 - Data System provides the ability to validate across combinations SF Classification of data classificetion structures (e.g., fund and department; F1 001 25 00 00 FI-00.25-00-00 to d�^d aa�pynt 00 - Data System provides ability to search for or have a drop SF Classification down list for valid date classification structure values. F1 00 26 00 00 Fi-0(O.26,00-00 00 - Data System provides 0te ability to process mass MA Classification changesldeletions on data classification structures. Ft 00I 27 00 00 F1-00-27-00-00 00 - Data System provides the ability to define accounting periods SF Ft 00 28 00 00 F 1.00-28-00-00 Classification within a given year tfisca�enods, auarlers, etc.). 00 - Data System provides the ability to change the data SF Classification classification structures at fiscal year boundaries based on effective -dated tables. F1 00 29 00 00 F1.00-29-00-00 00 - Data System supports a treasury fund which is used to support SF Classification multiple bank accounts. F1 00 30 00 06 Ft-00.90-00-00 00 - Data System has the ability to record and maintain the following Claryg'�ica)lon non -financial data for each uninue fund,_ F1 00 30 01 00 Ft-00-30-01-00 00 Da(s Ordinance SF Claesilicabon F1 00 30 02 00 F1-00-30-02-00 00 - Data Purpose of Fund (such as in a long text field) SF Classificafion F7 00 30 03 00 F1-00.30-03-00I Fund Source(s) SF COO- Data on Ft 00 30 04 00 F1-00-30-04-00 00-Data Aooeptable Uses SF Classification F1 00 30 05 00 F1-00-30-05-00 00-Data Date Closed SF Classification 00 30 06 00 F1-00-30-06-00 00-Date Fund Type for CAFR SF [11 Classification 0] 30 07 00 F1-00-30-07-00 00 - Data Fund Type for Budget (Operating, Project, Grant, Bond) SF �1`11 Classification F7 0] 30 08 00 F1-00-30-08-00 00 - Data Fund Group (for other than CAFR) SF Classification Ft 001 30 09 00 Ft-00-30-09-00I Data Interest bearing and not interest bearing indicator SF Cts00s sification F1 00I 30 10 00 Ft-0D-30-10.00 00 - Data Date created SF I Clasai6cation 00 30 11 00 Ft-00.30-11-00I 00-Data User who created SF IF1 Classification I F1 00 30 12 00 F11-00.30.12A0 00 - Data Long Description SF Classification F1 00 30 13 00 Ft-00-30-13-00 00 - Data Short Description SF Classification F1 00 31 00 00 F1-00-31-00-00I 00 - Date System has the ability to record and maintain the following I Classification non -financial data for each unit account: F 1 00 31 01 00 F1.00.31-01-00 00 - Data Purpose of Account (such as in a long text field) SF Classification City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 263 of 418 General Ledger, Project System provides the ability to support substantive Costing, Grants various projecligrent years in the COA, including projects that cross fiscal years and fiscal years that may be different from the city fiscal year. General Ledger, Project MEDIUM Contract Plumber is not Costing Captured in the general ledger. This can be accomodated it Contract ail part of the chart of accouri l structure. General Ledger General Ledger j I General Ledger HIGH This functionality is not currently available and will need to be created using PeooleToots. General Ledger General Ledger l General Ledger, Cash Bank accounts can be Management assarJated with a single fund or can be used in a cash pooled environment, i i General Ledger This information can be traoked using Ire user• its CnartField General Ledger This information can be tracked using the user - defined ChartField General Ledger This information can he I tracked using the user - defined ChanField 1 General Ledger this information can be tracked using the Uaer- defined ChartF.Id attributes. General Ledger General Ledger This information can be tracked using the user - defined ChartField attributes or using a Tree structure. General Ledger This Information can be tracked using the user- defned ChartField attributes or using a Tree structure, General Ledger This information can be j tracked Ming the user- J defined Chawleld attributes or using a Tree structure. General Ledger This information can be tracked using the user. defined ChenField attributes. General Ledger l General Ledger General Ledger General Ledger l General Ledger I This infomtation can be ' tracked using the user - defined ChartField attributes. F1 00 31 02 00 F1-00.31-02.00 00 - Data CAFR Title SF General Ledger This information can be I I Classification tracked using the user- defined ChartFleld I attributes a using a Tree lllll structure. Fl 00 31 03 00 F1-00-31-03-00 00 - Data Account Type (Asset, Liability. Fund Balance, Revenue, SF General Ledger Classification E�c�ulse, Other Financing Source (Use). 00 31 04 00 Ft-00.31-0400 00-Data Lung Desgiption SF I General Ledger f IF1 Classification 00 31 05 00 F1.)0-31.05-00 00 - Data Short Description SF I General Ledger IF1 Classification Fl 00 31 06 00 F`I-M31-06-00 00 - Data Acceptable Uses SF General Ledger This information can be Classification tracked using the ueer- defined Chartfield attributes. 00 31 07 00 F1-00-31-07-00 00-Data User who created SF General Ledger IF1 Classification 00 31 08 00 FI-00-31-0&DO 00 - Data Date Created SF General Ledger IF1 Gassificeson F1 00 32 00 00 Ft-00-32-00.00 00 - Data System has the ability to record and maintain the following Classification non -financial data for each unique mg —lion unit 00 32 01 00 F7-0032-01-00 00- Data Lag Deaaiption SF General Ledger IF1 Classification 00 32 02 00 F1-00-32.02-00 00-Data Short Description SF General Ledger IF1 Classification 00 32 03 00 F7-00-32-03-M 00- Data User who mated SF General Ledger IF1 Classification 00 32 04 00 F1-00-32-04-00 00-Data Date created SF General Ledger IF7 Classification F1 00 33 00 00 F1-00-33-00-00 00 - Data System has the ability to record and maintain the following Classification non-6nancial data for each unique capital project F1 00 33 011 00 F1.0033-01-00 00 - Data Managing Department SF Project Costing I Classification F1 00 33 02 00 Fl-M33.02-00 00-Data Primary Sponsoring Department SF Project Costing Classification 00 33 03 00 F1-00-33-03-00 00 - Data Location (e.g., Council District) SF Project Costing User -Defined Project Field IF1 Classification 00 33 04 00 Ft-0033.04-00 00 - Data Park Planning Aron or other general geographic SF I Project C-ling User -Defined Project Field i IF7 Classification reference as aoey�f�ed by the department. 00 33 05 00 F7-00.33-%S00 00-Data Sub-Fund(Fu innd g�„ource) SF I Project Costing IF7 Classification Ft 00 33 06 00 FI-00-33-06-00 00- Data GIS Code SF I Project Costing Via it. Project Locaf rin Classification F1 00 33 07 00 F1.00.33.07.00 00 - Data User Defined Field #1 SF Project Costing I User -Defined Project Field; I Classification I Ff 00 33 081 00 F1-00-334NI-W 00 - Data User Defined Field #2 SF Project Costing User -Defined Project Fieldl I Classification I F1 00 33 09 00 F1-00-33-WOO 00 - Data User Defined Field #3 SF os Project Gting I Utter -Defined Project Field Classification , F1 00 34 00 00 Ft-00.34.00-00 00 - Data System has the ability to record and mainain the following i Classification non -financial data for each unique capital project Work I Phase: 00 34 01 00 FI-00-34-01.00 00-Data Long Description SF Project Casting IF1 Classification F1 00 34 02 00 F7-00.34.02.00 00- Data Shot Description SF Project Costing Classification 00 34 03 00 FI-0030-03-00 00- Data User who created SF Project Costing IF1 Gaesification F1 00 34 04 00 F1.0034)4-00 00 - Data Date seated SF Project Costing I Classification I Ff 00 35 00 00 F1-00-35-00-00 00 - Data System has the ability to record and maintain the following Gamificalion non -financial data for each unique Grant Phase: Ff 00 35 01 00 F1400-35-01-00 00 - Data Long Dsaiption SF Project Costing, Grants I Classification 00 35 021 00 F1-00-35-02.00 00 - Data Short Description SF Project Costing, Grants IF1 Classification F1 00 35 031 00 Fl-00-35-03-00 00 - Data Grardofs Activity Number SF Project Costing, Grants User -Defined Project or I Classification I GField rant 00 35 041 00 Ft-00-35-04.00 00-Data Date created SF Project Costing, Grants IF1 Classification I F 1 00 36 00 00 Ft-00.36.00.00 00 - Data System has the ability to record and maintain the following Classification non -financial data for each unique grans Number, I 00 36 01 00 FI-00.36-01-00 00-Data Managing Department SF Project Costing, Grants Classification IF1 F7 00 36 02 00 FI-00.36-02-00 00-Data Grantor SF Project Costing, Grants Classificabon City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 264 of 418 F1 00 38 03 00 F1-0036-03-00 00 - Data Grantor's ID Number (e.g. IDIS or CJS Number) SF Project Costing, Grants User-Deinetl Project or Classification Gram Field l lF1 00 36 04 00 Ft-0036-04-00 00-Data start Date SF Project Costing, Grants Che"ilkatlon F1 00 36 06 00 F1-00-36.05.00 00 - Data End Date SF Project Gosling. Grants Class6 "ji- Ft 00 36 06 00 F1-00-36-00-00 00- Data Status (Open/closed) SF Project Gosling, Grants Claesificetion l F1 00 36 07 00 Fi-00-36-07.00 00-Date CFDA number SF Project Costing, Grants Classification F1 00 36 08 00 F1-00-36.08-00 00-Data Grant Accountant SF Project Coating, Grants User -Defined Project or Classification Grant Field 1 Ft 00 36 09 00 Ft-00-36-WOO 00-Data Mac SF Project Costing, Grants User -Defined Project or Classificetion Grant Field F1 00 38 10 00 F1-00-36-10-00 00-Data Contract SF Project Costing, Grants Classification F7 00 36 11 00 F7-00.36-11.00 00- Data Program Form (Attached file) SF Project Costing, Grants Classification I'll 001 361 121 00 Ft-00-36.12-00 00 - Data I Narrative Program Document (Attached file) SF Project Costing, Grants Grgallkatlan I F11 001 361 131 00 Ft-00-36-13-00 00 -Data I Ordinance SF Project Costing, Grants IUsar-Defined Project or Classificatlon Grant Field Fill 001 36 14 00 F1-00-36-14-00 00 - Data Source Level (Federal, State, Local, other, pass through) SF Project Costing, Grants ClassMka6on F1 GOI 37 00 00 Fl-00-37-00.00 00 - Data System allows non -financial attributes of FOGS values to SF Project Costing, Grants Claestlkatlon be changed (e.g., the CFDA number charges frofn Ona veer to the nextt. Fill OOI 38 00 00 Fi-DO38-00"O 00- Date System maintains an audit trail of changes to financial and MI Project Coaling, Grants HIGH Classification nonfinancial attributes (old value, new value, date the ed. USert 11 OOI 38 00 00 F14)0.39.00.00 DO- Data System slows eulhodzed users tin define what Fund SF General Ledger System allows user to define what Fund Claeaifncation Balance _nt will be updated by individual revenue and Balance account will be updated by -pan- accounts as new funds become available or at individual revenue and expense account the ones of the grem dun ve end Goa nor Fill 00 40 00 00 F1-00.40.00.00 00 - Data Syste Brie 1 data situ t s for validity within SF G neral Ledge Claesiflcation r' when poetin8 . "'rb L. �-0�IIV��II-yy 1 C - f "`cam �� �:�.. - F1 Ot 01 00 � 01 - Budgetary y$Mmprovldes.x -06-00 budgetary conwl options for the council - for this control adopted (epproprobon) budget to be established es follows: F7 O/l Oil Oil 001 F1-01-01-01-00 Ot - Budgetary l Absolute Control - prevents transaction from processing, I SF General Ledger control may not be overridden ( _ 1 1 F7 Oil 01 02 OOI F1-01-01-02-W 01 - Budgetary Override control - prevents transaction from processing SF General Ledger control with the ability to override error with appropriate security I I F11 Gil Oil 031 00 Fl-01-01-03-00 g1 - audgetary I Warning - provides warning message but allows SF l General Ledger l Control VaOsecjiorf to nr"r" F1 01 01 041 00 F1-01-01-04-00 01 - Budgetary No on allows l ansactiun to process without SF General Ledger l Control warning F1 01 02 0] 00 F1-01-02-00.00 01 • Budgetary System provides a flag that sets the default appropriation SF General Ledger , Control control option (e.g-, absolute, override, warning, no control; by fund, organization, account and/or other elements ol the data olassificatbn structure. Ft I 01 03 00 W F1-01-03-00-00 01 - Bu IS:.-.- --. the tolbwin budgetary control options dgetaryD 9 9 ryI I l Control r�fanental buckets: Fill Oil 031 Oil 001 F7-Ot-03-01-00 01 - Budgetary Abselule Control - Drevents transaction from processing, l SF General Ledger I Control may rot be overridden l l ( l l Ft 01 03 02 OO Ft-01-03-02-00 01 - Budgetary Override Control - prnrenta transaction harm processing SF General Ledger Control with the ability to override error with appropriate nearly I F11 01l 031 031 001 Fl-01-03-03-00 1 01 -C Budgetary l Warning --r)provides message but allows I SF l General Ledger awsarning I F11 01l 031 041 001 Fl-01-03-04-001 Ot-contontrolrol Budgetary l No Control - alows rsnsaction to process without l SF l General Ledger warnino Ot 04 00 00 Ft-01-04-00-00 Ot -Budgetary System provides a flag that seta the default departmental SF General Letlger zib Control �F] andtwother'rg Inez a I endsl)yfund, the isrgaaenimitan ��account F7 0] OS 00 00 I'll -01-05-00-00 01 - Budgetary provides multiple levels of departmental budgetary SF General Ledger Control control (i.e., absolute, ovemde, warning, no control) at (System varying levels of the financial data classification structure'sm M arch es (e.g: warning of section level, but absolute at the depar 1: level Lily F1 O7 OB 00 1n 00 F1-01-06-00-00 01 - Budgetary Budgetary control is Integrated with all modules to SF General Ledger Control ensure that all transactions using or affecting budget (appropriation, gram, project, department budget) authority are validated online, real-time against up-to-date budget totals based on established budgetary controls. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 265 of 418 4 F1 01 07 00 00 FI-01-07-00-00 01 - Budgetary System provides the ability to override appropriation, SF General Ledger System provides the ability to override control department, grant, and project budgetary control errors !appropriation, department, grant and with the appropriate seamy authority for each type of !project budget edits with the appropriate budget, without opening the budget to other users. !security authority for each type of budget, !without opening the budget to other users i F1 01 08 00 00 Fl-01-08-00-DO 01 - Budgetary System provides an indicator that determines whether SF General Ledger minor Control budgetary control for payroll transactions is applied to the I appropriation, departmental, grant, andlor project budgets. 01 09I W available fill F1-01-09-00-00ID7 to be calculated based or System allows IF7 Control multiple inducing but not limited fol�npefinablee he F1 Ot 09 01 00 Fl-014)9-01-00 01-Budgetary Original Budget RO General Ledger HIGH The delivered online Control + Cartyforward in inquiries do not segregate - Caryfonvard out budget amounts by these j + Transfers In categories. • Transfers out * Supplements - Recisions F1 01 10 00 00 Fl-01-10.00.00 01 - Budgetary System allows Funds Avallableto be calculated based on I multiple user -definable formulae, Including but not limited thecontrol F1 01 10 01 00 Fl-01-10-01-00 01 -Budgetary I{toAvnrlable Budget (Encumbered Basis) SF General Ledger Control ces 1-Encumbra MM F1 Ot 10 02 00 Fl-01-10-02-00I 01 - Budgetary Avail a�ble Budget (Actual Basis) SF General Ledger IControl I I F1 01 10 03 00 F1-01-10-03.00 01 Budgetary Available Budget (Pre -Encumbered Basis) SF General Ledger Control a I -Encumbrances Expanded Ft 01 1 00 00 Fl-01-11-00-00 01 - Budgetary can be configured to either include or exclude pre- SF General Ledger Control errambran es andlor arvarmbrences while dteddrig System provides for inclusion of pre - ] (System appropriation or department budgets. 1 encumbrances and encumbrances while [mor checking budget as configurable at an !appropriation or department budget level. Ft 01 12 00 00 F1-01-12400-00 01 - Budgetary System performs an appropriated budget available add SF General Ledger Control and commits the 4ansaction 9 it passe the edit or produces an eror menage a the transaction falls the edit F7 01 13 W fill F7-01-134)0-00I 01 -Budgetary ry System provides the ability to control appropriation Coby ussir-disfined ncial data bm and/or element b«a��ud�swclu�budgets ies F1 01 131 01 00 F1-01-13-01-00I 01-Btdgetary Fund SF General Ledger I I F1 Ot 131 02 00 R-01-13A2-00I 01 Budgetary Sub -Fund SF General LedgerCont I — I I F1 01 13 03 00 F"l-13-03-00I Ot Budgetary Department SF General Ledger I I — L — F1 01 131 04 00 F1-01.13-04.00I 01 - Budgetary Hierarchical Organization (Department Division, SF General Ledger Control Section I I I Ft 01 13 05 00 FI-01-13-05-00 01 - Budgetary Contract SF General Ledger If Contract is pan of the Control I Chan of Account structure. Ft 01 131 00 00 F1-01.13-06-00 B etary Program SF General Ledger I 101 ol I I I Ff 01 131 07 00 Fl-01.13.07-0O BudgLocation (e.g., Council District) SF General Ledger 101 �etary I I F1 01 13 08 00 Fl-01-13-08-00I 01 B etary Project Number SF General Ledger I I F1 01 13 09 00 F1-01-134)9.00I 01 Budgetary Work ha or Work Breakdown Stmclure (5 levels SF General Ledger l balm I I IF1 01 13 10 00 Fl-01-13-10-00I 01 Mary I Job SF I General Ledger �n Ft 01 131 11 00 Fl-01-13-11-00I 01 Budgetary GeneralL countShee(Expenditure Object Revenue I I SF I General Ledger Control Source BalanceAccount) — — — —� — — 01 131 12 00 Fl-01-13-12-00I 01 -Butrol dgetary Grant SF General Ledger IF1 I I I F1 01 13 13 00 F1-01-13-13-00I 01 - Budgetary Gram Phase or Activity (5 levels below Grant Phase) SF General Ledger Control I I 01 13 14 00 Fl-01-13.14-00I 01 -Budgetary Function SF General Ledger IF7 Control I I F1 01 13 15 00 F1-01-13-15-00I 01 - Budgetary Fiscal Year SF General Ledger contI I BudgetaryUser-Disfined Field 1 SF Genera F1 01 13I 17 00 F1-01-13-17-00 �1 - B IUser -Defined Field 2 SF I General Ledger City of Fort Worth i CIBER, Inc. Professional Services Agreement Page 266 of 418 1 1 1 1 1 1 1 1 1 1 1 1 T l i J W ! 1 ) 1 Ft 01 13 18 00 F7-01-13-18-00 01 - Budgetary User -Defined Field 3 SF General Ledger Control 01 14 00 00 F1-01.1400.00 01 - Budgetary System provides department budgetary controls for each Control department by uw-defr*d combinations or the financial �Fl data classification structures elements and/or element higra shown below: F1 01 14 01 Ties 00 F1-01-14A1-00 01 - Budgetary Fu SF General Ledger Control 01 14 02 00 F1-01.14.02.00 01- Budgetary Sub -Fund SF General Ledger IFt Control 01 14 03 00 Fl-01-14-03.00 Of - Budgetary Department SF General Ledger IF1 Control I F1 01 14 04 OQ Fl-01.14.04-00 01 - Budgetary Hierarchical Organization (Department, Division, SF General Ledger Control Sectionl F1 01 14 69 00 Fl-01-14-05-00 01 - Budgetary Contra SF General Ledger Control 01 14 06 00 F1.01.14.06-00 01-Budgetary Program SF General Ledger IF1 Control Ft 01 14 07 00 F1-01-1407-00 01 - Budgetary Location (e.g., Council District) SF General Ledger I O..t ol I Ft 01 14 69 00 F7-01.14-08-00 01 - Budgetary Project Number SF General Ledger F1 01 14 64 Control 00 F7-01-14-09-00 01 - Budgetary Work Phase or Work Breakdown Structure (5 levels SF General Ledger I Control below work ohasel F1 01 14 10 0E FI-01.14-10-00 Ot - Budgetary Job SF General Ledger I Control F1 01 14 11 00 F1-01-14-11-00 01 - Budgetary General Ledger Account (Expenditure Objec4 Revenue SF General Ledger I Control Source or Balance Sheet Account) 01 14 12 00 F1-01.14.12.00 Ot - Budgetary Grant SF General Ledger IN Control 01 14 13 00 F1-01-14-13.00 01 - Budgetary Grant Phase or Activity (5 levels below Grant Phase) SF General Ledger IN Control F1 Ot 14 14 00 F1-01-14-14-00 01 -Budgetary Function SF General Ledger Control Ft 07 14 15 00 F1-01-1415-00 01 - Budgetary Fiscal Year SF General Ledger Control Fl 01 14 16 00 F1-01.14-16-00 01 - Budgetary User -Defined Field 1 SF General Ledger Control Fl 01 14 17 00 F1-01.14.17-00 Ot - Budgetary User -Defined Field 2 SF General Ledger Control Ft 01 14 18 06 F1-01-14-18-00 01 - Budgetary User -Defined Field 3 SF General Ledger I Control Ft 01 to 00 00 Ft-01-15-00-00 01 - Budgetary System provides appropriation budgetary control at varying SF General Ledger Control levels and combinations of the financial data classification structures to be specirfbd by authaizedl user (e.g., 3rd level of fund 1 at level of department). F1 01 16 00 00 F1-01-16-00-00 01 - Budgetary System provides department budgetary control at varying SF General Ledger Control levels and combinations of the financial data classification structure. to be specified by authorized user (e.g., 4th level of fund; 4th level of organization, 2nd level of object of expenditure). Fl 01 17 00 00 F1-01-174g0.00 01 - Budgetary System provides inception -to -date appropriation budgetary SF General Ledger Control control for capital projects, granite and other project funds. Ft 01 18 00 00 F1-01-18-00-00 01 - Budgetary System edits all transactions to ensure that appropriation SF General Ledger Control budget Is available before posting the transaction. Fl 01 19 00 00 F1-01-19-00.00 01 - Budgets" System prevents transactions not meeting available SF General Ledger Control appropriation edits from being transmitted to the next _ sqp 1 stage. Ft 01 20 00 od F1-01-20-00-00 01 - Budgetary System prevents transactions not meeting available SF General Ledger Control department budgets that are absolutely controlled from being transmitted to the neM �Ff@rovat stage. Ft 01 21 00 00 F1-01-21-00-00 01 - Budgetary Sysfbm provide the ability to drill tlown from the budget SF General Ledger Control error message to the budget inquiry screen and Ft 01 22 00 eutomaticalli retrieve bu data. 00 F1-01.22-00.00 Ot -Budgetary System provides the abl ry to record a transaction that SF General Ledger Control effects budgetary balances as a revenue or expense, yet updates the general ledger balance sheet balances (e.g., bans given and received). The transaction should be posted uniformly against all sub ledger including, but not limited toGrant Accounting and Project Accounting. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 267 of 418 If Conbact is part oftho Chart of Account structure. System provides inception -locate appropriation budgetary control for capital projects and grants. minor F1 01 23 00 00 Ft-01-23-00-00 01 -Budgetary System provides the ability to record a transaction type the SF General Ledger conlml uses an Expenditure Object but does not edit or update the appropriation or departrrord budget balance (i.e., the transaction posts an expenditure and related oftsets to the general ledger, bud does not reduce budget authority). For example, depredation expense may be posted to a reporting ledger without affecting an operating budget. The transaction should be posted uniformly against all sub ledgers inducing, but not limited to Grant Accounting and Accountin(� F1 01 24 00 00 F1-01-24-00-00 01-Budgetary ya m provides as ability to by-pass budgetary controls MI General Ledger I LOW Control for Wecified Interfaces F1 01 25 00 00 F1-01.25-00-00 01 - Budgetary System provides an exception report of transactions that SF General Ledger Control failed budgatsry controls for interfaces.._ __.. orldlow 'F1 02 01 01 00 F1-02-01-01-00 02-Automated D��eparfmenlal�o(Jo�up4m�a°l�'Enby routed to central Finance SF General Ledger Workflow F't 02 01 02 00 F1-02-01-02-00 02 - Automated Cenfutnel Entry routed to accounting supervisor for SF General Ledger Workflow awroval F1 02 01 03 00 F1-02-01.03.00 02 - Automated Depaanmerm�tal vendxopr invoice routed to central Finance SF Payables orldlow for F1 02 01 04 UA F1-02-01-04-00 02-Automated Eemployee Tre J"rmn�lursement SF Expenses Workflow F1 02 01 05 06 F1-02-01.05-W 02-Automated Departmental Budget Transfer that crosses Division to a MI General Ledger MEDIUM F1 02 01 08 Workflow 00 F7-02-01.OB-00 02 - Autoated m central Finajt�e 4pppYe(. Oepartmen Bit Adjustment to a central Finance MI General Ledger MEDIUM Workow en roger, F1 02 02 00 00 F7-02-02-00-00 02- Automated System allows four esoalattonroff iittesmgs Inpwoor1{k%flow fora SF General Ledger, Payables, user General Ledcer Ft 02 03 00 00 Ft-02-03-00-00 02-Automated prorkflow Systemovides for contiguura(ion of nofa(cattons o1 WoMbw speddied users (not requiring approvals) for the following I financial transactions: IF1 02 03 01 00 Ft-02-03-01-00 02-Automated Vendor Creation MI Purchasing MEDIUM Workflow 02 03 02 00 F1-02-03.02-00 02-Automated Vendor Updates MI Purchasing MEDIUM IF1 Workflow IF1 02 O3 03 00 F1-02-03-03-00 02-Automated Customer Creation MI Receivables MEDIUM Workflow 02 03 04 2-03.04-00 02-Autoated 00 F1-0m m Customer Updates MI Receivables MEDIUM IF1 Workflow Ft 02 03 09 00 F1-02-03-05-oo 02 - Automated Recurring Journal Entries MI General Ledger MEDIUM j Workflow i F1 02 Cd OB 00 F1-02-034XI-M 02 - Automated Reversing Journal Entries MI General Ledger MEDIUM Workflow F1 02 lea 07 oQ F1-02-03-07-W 02 - Automated Asset Resremenls or Change of Status MI Asset Management MEDIUM Workflow F1 02 03 08 00 F1-02-03-D8-00 02 -Automated Asset Transfers MI Asset Management MEDIUM Workflow `F1 02 03 Oil 00 Ft-02-03-O9-00 02-Automated Postings to specified accounts MI General Ledger MEDIUM Workflow FI 02 03 10 00 Ft-02-03-10-00 02-Automated Updates to Financial Data Classification Structures MI General Ledger MEDIUM r Workflow Ft 02 03 11 00 Ft-02-03.11-00 112 - Automated Completion of Batch Processes (interfaces) MI General Ledger MEDIUM Workflow I F1 02 03 12 00 F11-02-03-12-00 02-Automated Unsuccessful Batch Processes MI General Ledger MEDIUM Workflow 02 03 13 00 Ft-02-03.13.00 02 -Automated Prior Period Postings to department fiscal coordinators MI General Ledger MEDIUM (F1 Workflow F1 02 04 00 00 F1-02.04.00-W 02 - Automated System provides functionality to increase the expenditure SF General Ledger Workflow budget as revenues are collected, based off pre- detennired combinations of financial data classification structures up to a co ndl- thorized telling (for example, as fees am collected for Gas Well Revenue, She department's budget au8crty increases for specific capital 0 .. 3r F1 03 01 OQ 00 F1-03-01-00-00 03 - Integretiw Budget control is integ set r avant modules, SF G ontrol is not with other including but not limited to purchasing, asset management, Payables, Receivables, directly integrated with Modules accounts payable, wet allocation, revenue, grants, project: Billing, Project Costing Asset Management. This and general ledger modules. is done through Integration with Purchasing, Payables ' and General Ledger. F1 03 02 00 00 F11-03-02-00-00 03 - Integration Transactions processed in the following sub -ledgers with other aulanatically update the general ledger in real-time Modules City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 268 of 418 ? 1 7 f i I I I 1 0 1 a 1 1 1 1 1 1 1 1 1 1 Ft 03 02 01 00 F1-03-02-01-00 03 - Integratlon Asset Management SF General Ledger, Asset Assumes that users are with other Management actively posting Modules transactions or the City is running batch updates freauentiv. F1 03 02 02 00 F1-03-02-02.00 03-Integration Accounts Payable SF General ledger, Payables, with other General Ledger Modules F1 03 61 03 00 F1-03-02-03.00 03 - integration Accounts Receivable SF General Ledger, Receivables with other Modules F7 03 02 04 00 Fi-03-02-04-00 03 - Integration Purchasing SF General Ledger, Purchasing, with other ( old ---ment Modules F1 03 02 05 00 F1-03-02-05-00 03 - Integration Cost Allocation SF General Ledger w th other Modules F1 03 02 06 00 F1-03-02-06-00 03 -Integration Inventory SF General Ledger, Inventory with other Modules F1 03 03 00 00 F1-03-03-00-00 03 - Integration System interface processes are validated the same as real SF General Ledger with other time entries System Interface processes are edited the same as real-time entries minor ,OILModules .. ,i F1 04 01 00 00 F1404-01-00-00 04 - Year End System provides the a lity to carry rward appropriation SF� General Ledger Cose balances to it,.next period, based on user -defined criteria. F1 04 02 00 00 Ft-04-02-00-00 04 - Year End System provides the ability to carry forward department SF General Ledger Close bu at to the next period based on user defined criteria. I F1 04 03 00 00 F1-04-03-00-00 04 -Year End Sys em Drovides standard and user -defies yearend doss Close ence cumbranrules and functionality, Including but not limitedto: I F11 04 03 01 00 F1404.03-01.00I 04 - Year End Carry -forward user -selected encumbrances SF General Ledger, Purchasing close Fi 04 03 02 00 F1-04-03.02-00 - Year End Carry -forward user -selected preencumbrances MA General Ledger, Purchasing HIGH As delivered, Purchasing l 104 Close and General ledger do no supportcarry-forward of ppre-encumbrances. j F1 04 03 03 00 F1-04-03-03-00 04 - Year End Carry -forward pre -encumbrances, and encumbrances MA General Ledger, Purchasing HIGH As delivered, Purchasing 1I Close based on user defned criteria using any element of the and General Ledger do not financial data classification structure or fields associated support carry -forward of with the Appropriation (e.g., appropriation type, fund pre -encumbrances, source1 or Fu/Wr F1I 04 03 04 00 F1-04-03.04,00 04 - Year End Non -se led pre-encumlxances and encumbrances are MA General Ledger, Purchasing HIGH As delivered, Purchasing Cidee not carried toward and General Ledges do not support Carty-forwrard of F1 04 03 05 00 F7.04.03.05A0 �04 - Year End Carry all pre -encumbrances and encumbrances forward MA General Ledger, Purchasing HIGH ppfe-y/ GumbtQpces. As dot vaned, Purchasing Gass I and General Ledger do no support carry -forward of ore -encumbrances. 1`-1I 04 04 00 00 F1-04-04-00-00) 04 - Year End System creates year end accruals for goods received but SF General Ledger, Purchasing Close notyet invoiced F7 04 05 00 00 F7-04-05-00.00 04 -Year End Abrfiry to maintain the same encumbrance document MA General Ledger, Purchasing HIGH As delivered. Purchasing Close number on encumbrances and pre -encumbrances that I and General Ledger do nog have been partially liquidated in one fiscal year and tamed support carry -forward of toward Into the next war , ar, pre -encumbrances. Fs 04 06 00 00 Ft-04-0&00-00 04 - Year End When encumbrances and prvencumbrances are selected I Close to be carried forward, system is able to beck them as prior year with the tdlowino functionality _ F1 04 06 01 00 F1-04-06-01-00 04 -Year End Encumbrances are reported by fund balance reserves MA General Ledger, Purchasing HIGH As delivered. Purchasing j Close and rdled forward to the current year. and General Ledger do nolf support carry-fonaard of r�7�fe-encumbrances. ' F1 04 06 02 00 Fl-04-W02-00 04 -Year End Keeping prior year funding and tracking fund balance MA General Ledger, Purchasing HIGH As ddtvered, Purchasing Close reserve by original budget year separately from the new and General Ledger do no current year fund balance reserve. support carry-f—ard of n,(f±'i^i imhr, -fuss F1 04 06 03 00 177.04.06.03.00 04 - Year End Liquidate prior year encumbrances and pre- MA General Ledger, Purchasing HIGH !1s dzlivered,�urchasing Close encumbrances from prior year budget carried forward and General Ledger do no when enambrancas ere ailher cancelled or paid in support carry -forward of cuRenl ye r. p%a'ryr�p}umd arid'$ F1 04 06 04 00 Ft-04-06-0440 04 - Year End Repdnt and display prior year encumbrance separately MA General Ledger, Purchasing HIGH A5 delivered, purchasing CID" from anent year encumbrances. and General Ledger do no! support carry -forward of ' ??ra-encumbrances. � 04 06 05 00 F1 .04-06-05-00 04 - Year End When the encumbrance is dosed with a residual unspent MA General Ledger, Purchasing HIGH As delivered, Purchasing Close amount. the residual amount is backed and controlled and General Ledger do I.10 �Fl separately and not added back to current year avaiade support carry -forward of funds. ore -encumbrances. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 269 of 418 F1 04 07 00 00 F7-04-07-00-00 04-Yew End System provides the ability to close encumbrances bytype MI General Ledger, Purchasing MEDIUM Close ofencumbrance. F' 04 08 00 00 F1-04-08-00-00 04- Year End System provides automated year-end close processes SF General Ledger System provides automated year-end Close (I.e., close nominal accounts to fund balance or fund dose processes (i.e.. close nominal equity, raft real accounts forward) for all modules as accounts to fund balance or fund equity, needed. roll mat accounts forward) for all modules as needed. System should close to the level of detail (financial data classification structure Elements) determined by the F{ 04 09 00 00 F1-04-09-00-00 04 - Year End System allows users to initiate year-end processing at any SF General Ledger user. minor Close point in time after the end of the fiscal year (i.e., doesnt have to occur on last day or an any particular day). F1 04 10 DO 00 F1-04-10-00-00 04 - Year End System has the ability to clean activity to fund balance by SF General Ledger close R� or by fund 9rpup. F1 04 11 00 00 F1-04-11-00-00 04. Year End yslam allows any activity after the year and dose balance SF General Ledger Clone carry forward to be reflected as equity In Ne fo6owirg year. System allows any activity after the year end dose balance ceryforw cl to be reflected as equity in the following year, formatting F7 04 12 00 00 F7-04-12-00-00 04 - Year End System allows for maintaining multiple open fiscal years SF General Ledger Close and periods concurrently. which allows users to post transactions for a new fiscal year pmrr to closing the F1 04 13 06 vipus veer. 00 Ft-04-13-00-00 04 - Year End Deeted SF Gererel Ledger System allows new year inputs to be aeleted Close entered prior to the current year fiscal F1 04 14 06 00 Ft-04-14.00-00 04 - Year End System defauls to the current accounting period, with SF General Ledger The accounting period can Close override capability. be overide- by supplying a difrenem accountinw date. Ft 04 116 00 00 Ft-04-15-00-00 04 - Year End Deleted SF General Ledger System allows user -defined types of aeleted Close transactions to post Into a future perod as long as the period is open and line user has appropriate security authority. Fi 04 18 DD 00 Ft-04-18.00-00 04 - Year End System should support pre -close (i,a., trial doses) and SF General Ledger Close tea prp forma fixg) fi� wits. F7 04 17 06 00 Fi-04-17-0-00 004 - Year End em provides then o c%se separate ledgers at SF General Ledger Close different times. F1 04 18 OD 00 Ft-D4-18-00-00 04 - Year End System provides the ability to wnyover open purchase SF General Ledger Close requisitions to the following fiscal year to post against new year budget. F1 04 19 OD 00 Ft-04-19-00-00 04 - Year End System provides the ability to carryover open purchase SF General Ledger Close order to the following focal year to past against new year F1 04 20 00 00 F1-04-20-00.00 04 - Year End � provides the ability to set up standard SF General Ledger Class encumbrance cancellation parameters, based on dollar Is adl e'-,'� Ff 0 01 Ofi W05. F7-OS-01-00-00 05 - System provides she ability for requisitions to be entered MA General Ledger, Pur�asing, HIGH I file tuncbpnalny io not Encumbrance without posting a pre -encumbrance based an eProcurement currently available and will Accounting documenttransactM type. need to be created using PeopleTools. F1 05 02 00 00 F14)5-02.00-00 05- System provides the ability to adjust or cancel a requisition SF General Ledger, Purchasing, Encumbrance and generate appropriate pre -encumbrance accounting eProcure merit Accountmo entries. Ft 05 03 DO 00 Ft-05-03-00-00 05 - System provides the ability to automatically liquidate all SF General Ledger, Purchasing, Encumbrance unused pre -encumbered moray once the requis4ion's eProcurement Accounting solicitation and purchase order(contrad have been related F1 06 04 00 00 F1-0SO4-g 1-00 05- System providesdfhe aN=ange financial data SF General Ledger, Purchasing, Encumbrance hiaseification elements after initial set up with automated eProcumment Accounting uDG�)e of Dre-commitments F1 oS DA lid 00 Fl-05-05-00-00 OS - System provides the ability to increase, decrease, liquidate SF General Ledger, Purchasing, Encumbrance or add new financial data dassif"'bons to requisitions elo—rement Acrnurding after the initial funds have been preencumbared. F1 04 08 00 00 Fl-05-08.00.00 05- System provides me ability to mate an encumbrance for SF General Ledger, Purchasing, Emarmbrence estimated costs for inter-departmentinter-fund work to be eProcurernant Accountlna tletl. F1 05 07 00 00 F1-05-07-00-W oar System provides the ability to establish planned SF General Ledger, Purchasing, System provides the ability to establish Encumbrance expenditures based on Segal obligation' withput the need eProcurement manual encumbrances based on Segal Aoearetkg to process through the procurement system, obligation" without the need to process through the procurement system. minor F1 05 08 DO 00 F7-05-08-00-00 05 - System provides the ability to adjust, change, supplement, 5F General Ledger, Purchasing, Encumbrance or reduce existing encumbrerce and pr"ricvmbrances, .1-mcurement Accounting maintaining an audit bad of all adjwtments. F1 05 O9 00 00 F7-05-09-00-00 05- Planned Expenditures process should capture the V Encumbrance following data: Manual Encumbrance process should Accountinia include the following data: minor City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 270 of 418 I I I I I I I I I I I I I I 1 I I 1 T F1 05 09 01 00 F1-05-09-01-00 05 • Type of encumbrance MI General Ledger MEDIUM Encumbrance Ac tine Fi OS 09 02 00 F1-05-09.02-00 05- Date established SF General Ledger Encumbrance Accounting F7 05 09 03 00 Ft-05-09.03.00 05- Expiration Date MI General Ledger MEDIUM Encumbrance AccWntinc Ft 05 04 00 F1-05.09.04.00 05 • Status (Oper✓Closed) MI General Ledger MEDIUM Encumbrance Accounting F1 05 09 05 00 F1-05-09-05-00 05- financial data classification structure codes (multiple SF General Ledger Encumbrance sets) Accountinn F1 05 09 05 001 F1-05-09.00.00 05- Originating Center A contact info SF General Ledger Can use the desonp9on Encumbrance I fields on the journal entry Accounting nacres. Ft 05 09 07 00J F1-05-09-07.00 OS - Encumbrance number (auto -generated by type of SF General Ledger Encuin encumbrance) Accou t F1 05 09 05 00-1-05-09-0H-00 OSmb- Fiscal year(s) SF General Ledger Encurance Accounting F1 OS 09 09 00 F1.05.09.09.00 05- Description SF General Ledger Encumbrance Accounting Fl 05 09 10 00 F1-05-09.10-00 05- Onginal Amount SF General Ledger Encumb Encumbrance Accounting F1 05 09 11 00 Fi-05-09-11-00 05 • Amended Amount MA General Ledger HIGH This functionality is not Encumbrence currently avallabls and will' Accounting need to be created using Pj)90IeTools. F1 05 09 12 00 Ft-0549-12-00 OS - Current Balance MA General Ledger HIGH Phis )unclionaltly is not Encumbrance ( currently available and will Accounting need to be created using PeWIaTWis. F7 OS 09 13 00 Ft-05-09-13.00 05- Approval fields SF General Ledger Encumbrance Accounting F11 05I 09 14 001 F1-05-09-14A0 05 - Text fields SP General Ledger Can use the description Enwmbris field Ids on the loumal entry Accounting r)�ues. F1 05 09 15 00F1-05-09.15.00 05 - Multiple numbers MA General Ledger HIGH Tnis functionality is not Encumbrance -cranny available and Mill, Aocountitg need to be mated using ! PeooleTools. -i 0`6 111 00 00 F1-05.10-00-00 05 - System provides the ability, y p fly, at the time of purchase order, Encumbrance to: Accounting F1 05 10 01 00 Ft-05-10-01-00 05 - Automatically create the appropriate encumbrance SF General Ledger, Purchasing Enambrance A-'—ntin. Ft 05 10 02 00 Ft-05.10.02.00 Allow auNorized users to edit the purchase order and "Lance SF General Ledger, Purchasing Encumbrance atMmaticelly adjust the encumbrance created by the Accounting sy�(em. F1 OSI 10 0.9 OOI Ft-OS-10-03-00 05- AuFomxtkaly liquidate any pre -encumbrance SF General Ledger, Purchasing, Encumbrance I eProcurement Arcot; F1 05 11 00 DID F1-05-11-OO-OD OS - System provides the ability to release any remaining funds SF General Ledger, Purchasing, Encumbrance o t a requisition related to a partially awarded solic'rletil- elp—ement Accounting Ft 05 12 00 00 Ft-05-12-00-00 05- System provides the ability to set a system -wide variance SF General Ledger, Purchasing, Encumbrance between pre-enambered and encumbered amounts when eProcurament Accounting converting a requisition to a purdlase order. 05 13 00 00 F7.05.13.00-00 05-System allow. creation of a purchase order for an amount SF General Ledger, Purchasing, lli`l� Encumbrance or pen entsge over the amount pre-a—beree- if within I eProcu errant Accounting department and city-wide varlance levels, without having tc increaaw the Drp-gppl(fpjfipgce. F1 OS 14 00 00 ".05-14.01). OS- System pro s the a l or departrnenla o set a MA General Ledger, Purchasing, HIGH This functionality is not Encumbrance venence level that is more his. Ne, but riot leas sProcuremant currently available and .3 Accounting restrictive, then city-wide verlance W.I., noel to ba created using PWolzIs. Ft 05 15 00 00 F1-05.15-00-00 05 • System provides the drill down from obligation balances to SF General Ledger Encumbrance deladed transactions. A-741r. g F1 05 15 00 001 F1-05-15.00.00 m 05 - System provides e ability to define encumbered amountsl SF General Ledger, Purchasing I Encumbrance on a fiscal year basis for purchase orders and releases I Accountko against contracts that cross fiscal years. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 271 of 418 F1 05 17 00 00 F14)5-17.00.00 05- System provides the ability to encumber a single SF General Ledger, Purchasing Encumbrance procurement document across multiple fiscal years. Accountina F1 05 18 00 66 F1-05.1840-00 05- System provides sync points for encumbered releases SF General Ledger, Purchasing Encumbrance against contracts to ensure that encumbered amounts are Accounting in balance with the overall contract amount and fiscal year payment estimates (for operating fund appropriations). F1 05 19 00 00 Fl-05-19.00.00 05- System provides the ability to ensure that a contract is not MI General Ledger, Purchasing HIGH Encumbrance terminated without automatically releasing all associated Accounting encumbrances. F1 05 20 00 00 F14)5.20.00-00 05- System provides the abiKy to accommodate separate SF General Ledger, Purchasing, Encumbrance tolerance thresholds for budgetary control when eProwremem Accounting processing encumbrances and pre-enwmbrenci s. F1 05 21 00 00 F11-05-21-00-00 05- System provides the ability to encumber to multiple SF General Ledger, Purchasing Encumbrance accounting distributions per line item Aceountina F1 05 22 00 00 F1-05.22.00.00 05- System provides the ability to establish encumbrances for SF General Ledger, Purchasing Encumbrance multiple fiscal years on a per PO Nne basis Accounting F1 05 23 00 00 F1-05.23-00-00 05- System provides the ability to automatically generate the SF General Ledger, Purchasing Encumbrance appropriate updates to encumbered amounts and Accounting accounting distributions based on changes to the purchase order. F1 05 24 00 00 F1-05-24-00-00 05- System provides the ability for an option to liquidate SF General Ledger, Purchasing, Encumbrance remaink4outstanding encumbrance on a purchase order Payables Amounting Is dosed. F1 05 25 00 00 F1-05-25-00-00 05- System provides the ability to allow a PO to be charged to SF General Ledger, Purchasing Encumbrance an socorinting distribution other than that of the associated Accountina (eouisitton. F1 05 28 00 00 FI-05-28.00.00 OS - System provides the ability to adjust or cancel a purchase SF General Ledger, Purchasing Encumbrance order and generate appropriate adjustments to Amounting encumbered balances. Ft 05 27 00 00 F1-05.27.0 05- System provides the ability to allow the Initiation of SF General Ledger, Purchasing, Encumbrance requisitions and purchase order documents prior to year- eProcurement Accounting end which cannot be pre-enclmbered until the new budget is loaded. Assumes that the city utilizes the Budget Reference field to track fiscal year at the accounting line level. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 272 of 418 1 1 1 1 1 1 1 1 1 1 1 1 1 1 System provides sync points for encumbered releases against contracts to ensure that encumbered amounts are in balance with the overall contract amount and fiscal year payment estimates. substantive System provides the ability to accommodate tolerance thresholds for budgetary control when processing encumbrances and pre -encumbrances- minor System provides the ability for an option to liquidate remainmgloutstanding encumbrance on a purchase oroer for which no further goods receipts are expected. minor i I I f I M f I i 1 i 1 )1 1 Num Category Requirement Text Degree of Fit Module Complexity of IReqt Re Modification �rise F2 06 01 00 00 F2-00-01-00-00 00 - Budget The system shall support multiple versions of the budget during the Prep -General develgpment g{ocess: F2 00 01 01 00 F2-00-Ot-01-00 00 -Budget Initial expenditure and revenue estimates SF I Planning and Prey - General Bud9etinq F2 00 01 02 00 F2-00-01-02-00 00 - Budget Base Budget Version SF Planning and Prat - General Bud9etinq F2 00 01 03 00 F2-00-01-03-00 OG - Budget Multiple department submission versions SF Planning and PreD - General Budgeting F2 00 01 04 00 F2-00-01 04-00 - Budget Budget Office versions SF Planning and re Pre - General Bud9etinq F2 00 01 05 00 F2-00-01-05-00 0�- Budget Council versions SF Planning and Prep - General Budgeting F2 00 01 06 00 F2-00-01-06-00 00 - Budget Detailed Department operating budget versions SF Planning and Prep - General Bud9etinq F2 00 02 00 00 F2-00-02-00-00 00 - Budget The system shall allow the user to compare different versions of the budget. SF Planning and Prep - General Budgeting F2 00 03 00 00 F2-00-03-00-00 00 - Budget The system shall present historical financial information after a RQ Planning and 'P2-00-04-00-00 Pry - General in both the original structure and the revised structure. Budgeting F2 00 04 00 00 gfroanizatioq 60 - Budget The system shall allow for export of budget results for interface into other SF Planning and F2 00 05 00 00 F2-00-05-00-00 Prep -General department systems. (i.e.Brass) Ol5 - Budget The system shall calculate budget projections using robust modeling tools Budgeting Prep - General and techn(9ues, including but not limited: F2 00 05 01 00 F2-00-05-01-00 00 - Budget multi -variant analysis SF Planning and Prep - General Bud9etinq F2 00 05 02 00 F2-00-05-02-00 Oct - Budget what -if simulation SF Planning and Prep - General Budqetinq F2 00 05 03 00 F2-00-05-03-00 00 - Budget integration with PC based analytical applications SF Planning and PreD - General Bud9etinq F2 00 06 00 00 F2-00-06-00-00 08 - Budget The system shall provide version control for budget versions through: Planning and Prep - General Budgeting F2 00 06 01 00 F2-00-06-01-06 lKl - Budget User defined version names (e.g., 0-"As Distributed", 1= Department SF Planning and Prep - General Internal", 2-"As Submitted", etc. Bud9etinq F2 00 06 02 00 F2-00-06-02-00 00 - Budget User defined statuses within versions (e.g., Not Started; In -Process; SF Planning and Prep - General Submitted; Reviewed; ApprQved,etc.) Budgeting F2 00 06 03 00 F2-00-06-03-00 00 - Budget User defined allowable activities per version (Changes allowed, Frozen for SF Planning and Prep - General Changes, etc.) by different levels of the data classification structure or by Budgeting individual user. F2 00 07 00 00 F2-00-07-00-00 00 - Budget The system shall automatically alert the next user that a version (phase) has SF Planning and Prop - General been submitted. Budgeting F2 00 08 00 00 F2-00-08-00-00 00 - Budget The system shall alert the user that no changes were entered in the system MI Planning and I LOW Prep - General before a version is submitted. Budgeting F2 00 09 00 00 F2-00-09-00-00 00 - Budget The system shall allow the next user to make changes while preventing prior SF Planning and Prqp - General users from makin changes. Budgeting F2 00 10 00 00 F2-00-10-00-00 O6 -Budget The system shall monitor status of submissions against a preset schedule. SF I Planning and P - General Bud9etinq F2 00 11 00 00 F2-00-1 1 -00-00 - Budget The system shall allow entry of negative amounts for line item amounts or SF Planning and Prep -General adjustments. Bud9etinq F2 00 12 00 00 F2-00-12-00-00 00 - Budget The system shall allow components of a budget request to be excluded when SF Planning and Prqp - General copvino one version to another. Budgeting F2 00 13 00 00 F2-00-13-00-00 00 - Budget The system shall allow the user to change key fields and capture a narrative SF Planning and Pr - General description of the reason for the chan9p. Bud9etinq J F2 00 14 00 00 F2-00-14-00.00 �- Budget The system shall allow users to specify the level of rounding that occurs in RQ I Planning and Prey General the budget prgp J�`ion procegs in rep�rts. Bud9etinq F2 00 15 00 00 F2-00-15-00-00 00 - Budget The system sha�( allow users fO specify the level of rounding that occurs in SF I Planning and PreD - General the budget preparation process in Drojections. Bud9etinq F2 00 16 00 00 F2-00-16-00-00 06 - Budget The system shall allow reorganizations to be processed by dropping and SF Planning and Prep - General dragging an organization from one location to another on a graphical Budgeting depiction of the organization. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 273 of 418 F2 00 17 00 00 F2-00-17-00-00 00 - Budget The system shall allow the user to view the impact of organizational shifts on SF Planning and Prep - General the budget. Budgeting F2 00 18 00 00 F2-00-18-00-00 00 - Budget The system shall provide word processing capability for the textual write-up SF Planning and Prep - General of the budget document using user defined templates. Budgeting, BI Publisher F2 00 19 00 00 F2-00-19-00-00 00 - Budget The system shall capture narrative explanation for budget requests and SF Planning and Prep - General decision packages. Budgeting, BI Publisher F2 00 20 00 00 F2-00-20-00-00 00 - Budget The system shall allow unlimited text for decision package narrative. SF Planning and Prep - General Budgeting J F2 00 21 00 00 F2-00-21-00-00 lH) - Budget The system shall allow for multi -page processing when printing decision SF Planning and Prep - General packages. Budgeting, BI Publisher F2 00 22 00 00 F2-00-22-00-00 00 - Budget The system shall provide for multiple fields to capture narrative, and allow SF Planning and Prep - Generel users to configure which will be printed in the formal budget package. Budgeting F2 00 23 00 00 F2-00-23-00-00 00 - Budget The system shall check for approval before loading budgets into the financial SF Planning and Prep - General system. Budgeting F2 00 24 00 00 F2-00-24-00-00 06 - Budget The system shall automatically load the appropriation and operating budget SF Planning and Prep - General into the financial $yrer� once a,Qproved. Budgeting F2 00 25 00 00 F2-00-25-00-00 O6 - Budget The system shelf a�low the user to identify an account code value as one SF Planning and Preg - General which will be used for bu5pet values only. Budgetinq F2 00 26 00 00 F2-00-26-00-00 O6 - Budget System provides the ability to generate budgetary -based funds statements SF Planning and Prep - General based on historical and budgeted financial data. Budgeting F2 00 27 00 00 172-00-27-00-00 00 - Budget System provides the ability to develop operating budgets within fiscal year SF Planning and Prep - General boundaries. Budgeting F2 00 28 00 00 F2-00.28-00-00 00 - Budget System allows users the capability to adjust budget submissions across SF Planning and Prep - General varying levels of the financial data classification structure (e.g., can reduce Budgeting travel at either the section level or at the department level). F2 00 29 00 00 F2-00-29-00-00 00 - Budget System provides the ability to import data into the budget preparation tool SF Planning and Prep - General from the financial system for select combinations of the financial data Budgeting classification structure (e.g., include only operating funds, not capital project funds or grant funds). F� 00 30 00 00 F2-0030-00-00 00 - Budget System provides the ability to receive data from and export data to SF Planning and F2 00 31 00 00 F2-00-31-00-00 Prep - General $yreadsheets and/or database alplications. 00- Budget System has the ability to attach files (e.g., Word, Excel) to budget MI Budgeting Planning and MEDIUM Prep -General submissions. Budgeting F2 06 32 00 00 F2-00-32-00-00 3 - Budget System has the ability to attach files (e.g., Word, Excel) to budget line items. MI Planning and MEDIUM Prep - General Budgeting F2 00 33 00 00 F2-00-33-00-00O6 - Budget System has the ability to record and maintain the following non -financial data Planning and PreD - General for each unique decision package: Budgeting F2 00 33 01 00 F2-00-33-01-00 00 - Budget Purpose MI Planning and MEDIUM Prepp - General Budgeting F2 00 33 02 00 F2-00-33-02-00 O6- Budget Consequences MI Planning and MEDIUM Prep - General Budgeting F2 00 33 03 00 F2-00-33-03-00 00 - Budget Funding Sources MI Planning and MEDIUM Prep - General Budgeting F2 00 33 04 00 F2-00-33-04-00 O6 - Budget Legal Authority MI Planning and MEDIUM Prep - General Budgeting F2 00 33 05 00 F2-00-33-05-00 00 - Budget Appropriation Type MI Planning and MEDIUM Prep -General BudgetingF2 06 33 06 00 F2-00-33-06-00 ) - Budget Appropriation Title MI Planning and MEDIUM Prep -General Budgeting F2 00 33 07 00 F2-00-33-07-00 3 - Budget Ongoing or One-time MI Planning and MEDIUM Prep - General Budgeting F2 00 31 04 00 F2-00-33-08-00 O6 - Budget User Defined Field #1 MI Planning and MEDIUM Prep - General Budgeting F2 00 33 09 00 F2-00-33-09-00 06 - Budget User Defined Field #2 MI Planning and MEDIUM Prep - General Budgeting F2 00 33 10 00 F2-00-33-10-00 00 - Budget User Defined Field #3 MI Planning and MEDIUM Prep - General Budgeting F2 00 34 00 00 F2-00-34-00-00 06 - Budget System allows users to prepare decision packages for any level of the SF Planning and Prep - General Financial Data Classification Structure. Budgeting, BI Publisher City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 274 of 418 F2 00 35 00 00 F2-00-35-00-00 00 - Budget System allows users to prepare decision packages for multiple organization SF Planning and Prep - General units (including ones that cross departments). Budgeting, BI Publisher F2 00 36 00 00 F2-00-36-00-00 00 - Budget System allows users to prepare decision packages that matches sources of SF Planning and Prep - General funding to expenditure requests. Budgeting, BI Publisher F2 00 37 00 00 F2-00-37-00-00 00 - Budget The system shall allow the user to seasonalize data before calculating SF Planning and Prep - General rroiections. �ha Budqetinq F2 00 38 00 00 F2-00-38-00-00 00 -Budget system shall flag funds that have a projected negative fund balance at RQ Planning and Prep - General the end of the vear. Budqetinq F2 001 39 00 00 F2-00-39-00-00 00 - Budget System provides the ability to establish multiple roll -ups of budget data SF Planning and Prep - General across departments to present enterprise benchmarks, compare department- Budgeting to-deoartment, function -to -function, etc. F2 00 40 00 00 F2-00-40-00-00 00 - Budget System provides the ability to create multiple, user -definable attributes that SF Planning and Prep - General can be associated with various submissions (e.g., city-wide categories, Budgeting functional activities, "priorities of�vernmenl" etc; F2 00 41 00 00 F2-00 41-00-00 00 -Budget System allows application of different forecasting calculations to the same SF Planning and Prep - General line item in different _rgani4 tI'QnaI units. Budqetinq F2 00I 42 00 00 F2-00-42-00-00 06 - Budget System allows application o�d�fferent forecasting calculations to different line SF Planning and Preo - General items in the same organizational unit. Budgetinq F2 OOI 43 00 00 F2-00 43-00-00 00 -Budget System allows multiple forecasts for the same line item using different SF Planning and Prep - General forecasting techniques, displays the results, and allows the users to select Budgeting the most appropriate calculation. F2 001 44 00 00 F2-00-44-00-00 00 - Budget The system shall present departmental submissions on a multi -year basis, SF Planning and Prep - General for example, prior year actual, current year actuals, current year budget, Budgeting future vear base budget, future vear submitted hudoet . F2 001 45 00 00 F2-00-45-00-00 00 - Budget System allows the user to create individual formulas for each cell in the SF I Planning and Prep -General budoet worksheet. Budgetinq F2 001 46 00 00 F2-00-46-00-00 00 - Budget System allows the user to input actual numbers into each cell in the budget SF I Planning and Prep - General worksheet. Budqetinq F2 001 47 00 00 F2-00-47-00-00 O6 - Budget System allows the user to forecast amounts based on position counts. SF I Planning and Prqp -General Budqetinq F2 00 48 00 00 F2-00.48-00-00 06 -Budget System allows the user to copy formulas from one cell to many cells. SF Planning and Prep - General Budgetina F2 00 49 00 00 F2-00-49-00-00 00 - Budget System allows the user to include other cell values in the formula. SF Planning and P z- General Budqetinq F2 00 50 00 00 F2-00-50-00-00 - Budget System allows for creating relationships and dependencies between SF Planning and Prej� - General budqeted items. Budqetinq F2 00 51 00 00 F2-00-51-00-00 00 - Budget System allows entering, storing, and reporting non -financial data. SF Planning and 1`2 011 021 001 001 F2-01-02-00-001 01 - Prepare system shall capture revenue estimates in a budget version for SF Planning and Revenue IThe comparison reporting. Budgeting Estimates F2I 011 1131 001 001 F2-01-03-00-001 01 - Prepare The system shall calculate revenue estimates based on user -defined rules SF Planning and Revenue applied to actual or budgeted revenue collected and deposited up to the prior Budgeting F2I 011 041 001 OOI F2-01-04-00-00 Estimates 01 - Prepare 5yyears. �'he system should capture user -defined rules for projecting revenues based SF Planning and Revenue on multiple step calculations. Budgeting Estimates F2 01 05 00 00 F2-01-05-00-00 01 - Prepare system shall allow definition of formulas that will project revenues based Planning and Revenue IThe on: Budgeting Estimates F2 01 05 01 00 F2-01-05-01-00 01 - Prepare SF Planning and Revenue Budgeting Estimates fixed rate adjustments F2I 1111 05 021 001 F2-01-05-02-00 01 - Prepare SF Planning and Revenue Budgeting I Estimates absolute dollar ad)'ustments F2I 1111 05 1131 001 F2-01-05-03-00 01 - Prepare prior year expenditure or revenue balances SF Planning and Revenue Budgeting I Estimates City of Fort Worth / C1BER, Inc. Professional Services Agreement Page 275 of 418 F2 01 05 04 00 F2-01-05-04-00 01 - Prepare grant match requirements MA Planning and MEDIUM Revenue Budgeting Estimates F2 01 05 04 00 F2-01-05-05-00 01 - Prepare statistical information entered by period or year SF Planning and Revenue Budgeting Estimates F2 01 06 00 00 F2-01-06-00-00 01 - Prepare The system shall allow the user to view and access comparative data: Planning and Revenue Budgeting Estimates F2 01 06 01 00 F2-01-06-01-00 01 -Prepare prior year revenue estimate SF Planning and Revenue Budgeting Estimates F2 01 06 02 00 F2-01-06-02-00 01 - Prepare current year revenue estimate SF Planning and Revenue Budgeting Estimates F2 01 06 03 00 F2-01-06-03-00 01 - Prepare future year revenue estimate SF Planning and Revenue Budgeting Estimates F2 01 06 04 00 F2-01-06-04-00 01 - Prepare prior year actual SF Planning and Revenue Budgeting Estimates F2 01 06 05 00 F2-01-06-05-00 01 - Prepare current year actual SF Planning and Revenue Budgeting Estimates F2 01 07 00 00 F2-01-07-00-00 01 - Prepare The system shall allow the user to split estimates by period and report SF Planning and Revenue accordingly. Budgeting Estimates F2 01 08 00 00 F2-01-08-00-00 01 - Prepare The system shall capture up to 10 years of revenue projections. SF Planning and Revenue Budgeting Estimates F2 01 09 00 00 F2-01-09-00-00 01 - Prepare System provides the ability to maintain revenue forecast detail by SF Planning and Revenue department and revenue source, which can be copied into future budget Budgeting Estimates years. F2 02 01 00 00 172-02-01-00-00 02 - Provide The system shall capture the budget calendar. SF Planning and Budget Budgeting Preparation Guidance F2 02 02 o6 06 F2-02-02-00-00 02 - Provide The system shall notify budget coordinators of the establishment of the SF Planning and Budget calendar. Budgeting Preparation Guidance F2 02 03 00 00 F2-02-03-00-00 02 - Provide The system shall use budget calendar dates as the trigger for user -defined e- SF Planning and Budget mail alerts to budget coordinators to monitor budget completion status. Budgeting Preparation Guidance F2 02 04 00 00 F2-02-04-00-00 02 - Provide The system should allow users to define budget forms for: Planning and Budget Budgeting Preparation Guidance F2 02 04 01 06 F2-02-04-01-00 02 - Provide Instructions SF Planning and Budget Budgeting Preparation Guidance F2 02 04 02 00 F2-02-04-02-00 02 - Provide Any combination of the financial data classification structure SF Planning and Budget Budgeting Preparation Guidance F1 02 04 03 00 F2-02-04-03-00 02 - Provide Narrative descriptions SF Planning and Budget Budgeting Preparation Guidance F2 02 04 04 00 F2-02-04-04-00 02 - Provide Narrative justifications SF Planning and Budget Budgeting Preparation Guidance City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 276 of 418 F2 02 04 05 00 F2-02-04-05-00 02 - Provide Internal Service Fund rates SF Planning and Budget Budgeting Preparation Guidance F2 02 04 06 00 F2-02-04-06-00 02 - Provide Administrative Charges for internal service funds SF Planning and Budget Budgeting Preparation Guidance F2 02 05 00 00 F2-02-05-00-00 02 - Provide The system should allow for definition of business rules for each form. SF Planning and Budget Budgeting Preparation Guidance j F2 02 06 00 00 F2-02-06-00-00 02 - Provide The system should allow for electronic distribution of budget instructions. SF Planning and Budget Budgeting Preparation Guidance F2 02 07 00 00 F2-02-07-00-00 02 - Provide The system shall calculate personnel attrition rates for departments and SF Planning and Budget programs. Budgeting Preparation Guidance F2 02 08 00 00 F2-02-08-00-00 02 - Provide System allows department Budget Office to "push" via workflow budget SF Planning and Budget forms out to departments electronically for budget preparation. Budgeting Preparation Guidance 7037'01 00 00 F2-03-01-00-00 03 - Position The system shall provide fully integrated personal services budget Planning and Based preparation with the human resource module that incorporates: Budgeting Bu ptinq F2I 03I 01 01 00 F2-03-01-01-00I 03 - osition using the same position information SF Planning and Based I Budgeting Budgeting F2 03 01 02 00 F2-03-01-02-00 03 - Position using the same job information SF Planning and Based Budgeting Bud(�etino F2 03 01 03 00 F2-03-01-03-00 03- Position using the same employee actual information SF Planning and Based Budgeting Bud yptigy F2I 031 02 00 001 F2-03-02-00-001 03 - Position allows for what -if functionality within the personal services budget Planning and Based (System preparation module that: Budgeting Bud yatipy FZ 03 02 01 00 F2-03-02-01-00 03 - Position commonly applies user -defined payroll assumptions (such as COLA or SF Planning and Based other across the board adjustments) Budgeting ! Bu ptip j F2I 03I 02 02 001 F2-03-02-02-00 03 -Position provides projections of vacancy rates based on historical data i Planning and Based Budgeting Budgettn/, F2 03I 02 03 001 F2-03-02-03-00I 03 - Position provides projections of the impacts of step increments based on HR SF Planning and Based defined business rules I Budgeting I Budgetir� F2 03I 02 04 001 F2-03-02-04-00 03 - Position supports estimating benefits and compensation by position for vacant SF Planning and Based positions i Budgeting Busy ptinq F2 03I 02 05 00 F2-03-02-05-00 03 - Position supports estimating benefits and compensation by actual employee SF Planning and Based information for filled positions Budgeting Budget'nP F2 03I 02 06 00 F2-03-02-06-00 03 -Position supports multiple position -based funding assignments for specified periods SF Planning and Based Budgeting Budoetin� F2 03 02 07 00 F2-03-02-07-00 03 - Position supports projecting only the operating fund portion of a split funded SF Planning and Based position if they are also funded by project or grant funds that are not Budgeting BuV,etigp included in the bud�et process. F2I 03 03 00 001 F2-03-03-00-00 03 - Ffosition IThe system shall provide detail for personal services estimates at any level SF Planning and Based of the financial data classification structure. I Budgeting I Budgetina City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 277 of 418 F2 03 04 00 00 F2-03-04-00-00 03 -Position The system should allow positions (filled, budgeted or planned) to be funded SF Planning and Based by multiple combinations of financial data classification structure and varying Budgeting Budgeting percentages with each assignment to be effective dated. Gall F2 03 05 00 00 F2-03-05-00-00 03 - Position The system allow users to calculate payroll projections based on filled SF Planning and Based and/or vacant (budgeted or planned) positions based on anticipated filled Budgeting Budgeting dates. F2 03 06 00 00 F2-03-06-00-00 03 - Position The system shall calculate anticipated pay raises or decreases based on: Planning and Based Budgeting BudgetinP F2 03 06 01 00 172-03-06-01-00 03 -Position Planned raises increases or decreases SF Planning and Based Budgeting Budgeting F2 03 06 02 00 F2-03-06-02-00 03 - Position Scheduled pay increases or decreases SF Planning and Based Budgeting Budgeting F2 03 06 03 00 F2-03-06-03-00 03 - Position Cost of living Adjustments applied across the board for a group of SF Planning and Based employees Budgeting BudigetinP F2 03 06 04 00 F2-03-06-04-00 03 - Position position down -grades or upgrades SF Planning and Based Budgeting Budgeting F2 03 06 05 00 F2-03-06-05-00 03 -Position User defined rules SF Planning and Based Budgeting Budget nP F2 03 07 00 00 F2-03-07-00-00 03 -Position The system shall estimate healthcare and fringe benefit costs based on: Based BudgetinP F2 03 07 01 00 F2-03-07-01-00 03 - Position personnel assignments SF Planning and Based Budgeting Budgeting position based SF Planning and Budgeting F2 03 07 02 00 F2-03-07-02-00 03 - Position historical fringe benefit ratios SF Planning and Based Budgeting BudgetinP F2 06 08 00 00 F2-03-08-00-00 03 - Position The system shall capture narrative regarding payroll and fringe assumptions. SF Planning and Based Budgeting Budgeting F2 03 06 00 00 F2-03-09-00-00 03 - Position The system shall aggregate position -detailed payroll projections across all SF Planning and Based elements of the financial data classification structure hierarchies. Budgeting BudgetinP F2 03 10 00 00 F2-03-10-00-00 03 - Position System will deliver functionality to perform the following operations online SF Planning and Based when planning position related expenditures: Budgeting Bud III F2 03 10 01 00 F2-03-10-01-00 03 - Position Add or delete positions SF Planning and Based Budgeting Budgyeting F2 03 10 02 00 F2-03-10-02-00 03 - f�osition Reclassify positions SF Planning and Based Budgeting BudgetinP F2 03 10 03 00 172-03-10-03-00 03 - Position Modify positions SF Planning and Based Budgeting BudgetinP FE 06 16 04 00 F2-03-10-04-00 03 - Position Transfer positions MA Planning and MEDIUM Based Budgeting BudgebT F2 03 10 05 00 F2-03-10-05-00 03 - Position Freeze or unfreeze positions MA Planning and MEDIUM Based Budgeting Bu etin F2 03 10 06 00 F2-03-10-06-00 03 - Position Split positions SF Planning and Based Budgeting Budgeting F2 03 16 07 00 F2-03-10-07-00 03 - Position Change the number of authorized full time equivalents per position SF Planning and Based (overage or backfilling a position) Budgeting Budgeting City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 278 of 418 Added I I 1 1 4 1 d 1 t a 1 F2 03 10I 08 00 F2-03-10-08-00 03 - Position Control the number of employees filling a position J Based Budaetin� F2 03 11 00 00 F2-03-11-00-00 03 - Position System will deliver functionality to perform online edit checking and Based validation to identify when more than one employee is assigned to the same Budgeting position number. F2 03 12 00 00 F2-03-12-00-00 03 - Position System will deliver functionality to route position change requests online to Based various staff members for approval. Budoetpp F2 03 13 00 00 F2-03-13-00-00 03 - Position System will deliver functionality to notify requestor when position has been Based approved. Budgetir)p F2 03 14 00 00 F2-03-14-00-00 03 - Position System will have the functionality to maintain position history. Based Budgeting F2 03 15 00 00 F2-03-15-00-00 03 - Position Deleted Based Budgeting F2 03 16 00 00 F2-03-16-00-00 03 - Position System will have functionality with changes in organization structure to Based automatically create a dated record at the employee level to reflect the Budgeting chance. F2 03 17 00 00 F2-03-17-00-00 03 - Position System will have functionality to budget using actual resource costs for filled Based positions and planned position costs for vacant positions Budget'9c; F2 03 181 00 00 F2-03-18-00-00 03 - Position The system shall calculate vacancy rates for positions by any level of the Based organization structure. Budoetipp F2 03 19 00 00 F2-03-19-00-00 03 - Position The system shall control ceilings on planned, budgeted or authorized Based positions for each department. Budgetinq F2 03 20 00 00 F2-03-20-00-00 03 - Position The system shall provide a roster and a view of filled positions, vacant Based positions, and planned/budgeted positions. BudgetirP F2 03 211 00 00 F2-03-21-00-00 03 - Position The system shall allow the user to flag positions for inclusion in the position Based based budget. Budgeting F2 03 22 00 00 F2-03-22-00-00 03 - Position The system shall be able to project position salaries and benefits across any Based element of the financial data classification structure based on: 84V,etinp F2 03 221 01 00F2-03-22-01-00 03-Position filled positions Based Buc;ly¢tinq F2 03 22 02 00 F2-03-22-02-00 03 - Position vacant positions Based Budaetinp F2 03 221 03 00 F2-03-22-03-00 03 - Position planned positions, by date Based Budgeting F2 03 23 00 00 F2-03-23-00-00 03 - Position The system shall flag budgeted positions that have exceeded appropriations. Based Budgeting F2 03 24 00 00 F2-03-24-00.00 03 - Position The system shall record and track justification for position changes. Based Budoetiny F2 03 251 00 00 F2-03-25-00-00 03 - Position The system shall provide flexibility to departments to plan reclassifications Based and carry these reclassifications into the salary estimates. Budgeting F2 03 26 00 00 F2-03-26-00-00 03 - Position The system shall allow department budget analysts to build salary Based projections for vacant positions using different assumptions about pay , Budgetinq increases. Professional Services Agreement Page 279 of 418 MI Planning and Budgeting MI Planning and Budgeting MI Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting MI Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting MI Planning and Budgeting MI Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting SF Planning and Budgeting LOW LOW LOW LOW LOW IN7Ti9 System will have functionality to enter single or multiple funding sources for each position. Duplicate F2 03 27 00 00 F2-03-27-00-00 03 -Position The system shall provide "what if" modeling for payroll projections. SF Planning and Based Budgeting BudgetinP F2 03 28 00 06 F2-03-28-00-00 03 -Position The system shall provide flexibility to cost out new positions at multiple SF Planning and Based grades. Budgeting Budgeting F2 03 29 00 00 F2-03-29-00-00 03 - Position The system shall project fringe benefits within a payroll estimate based on SF Planning and Based position funding assignments. Budgeting BudgetinP F2 03 30 00 00 F2-03-30-00-00 03 - Position The system shall provide the ability to calculate the future fringe factor. SF Planning and Based Budgeting "F2 Bud y�tir)P Xo'sition 03 31 00 00 F2-03-31-00-00 03 - The system shall update healthcare costs to project future payroll costs. SF Planning and Based Budgeting Bud etin F2 04 01 00' 00 F2-04-01-00-00 04 - Develop Base Budget The system shall allow for creation of the initial base budget amounts for the upcoming year based on the following balances from the financial module: F2 04 01 01 00 F2-04-01-01-00 04- Develop SF Planning and Base Budget actual balance from current year Budgeting F2 04 0f 02 06 F2-04-01-02-00 04-Develop SF Planning and Base BudQt't original appropriation amount from current year Budgeting F2 04 01` OS 00 F2-04-01-03-00 04 - Develop SF Planning and Base Budget re -estimated Budgeting F2 04 01 04 00 F2-04-01-04-00 04 - Develop SF Planning and Base Budget final appropriation amount from current year Budgeting F2 04 Ot 05 00 F2-04-01-05-00 04-Develop SF Planning and Base Bud et statistical information. Budgeting F2 04 02 00 00 F2-04-02-00-00 04 - Develop System supports creation of the initial base budget amounts by applying SF Planning and Base Budget adjustments to the balances above Budqetinq F2 04 02 01 00 F2-04-02-01-00 04 - Develop SF Planning and Base Budget fixed rate adjustments Budqetinq F2 0402 02 00 F2-04-02-02-00 04 - Develop SF Planning and Base Budget absolute dollar adjustments Budgeting F2 04 02 03 00 F2-04-02-03-00 04 - Develop SF Planning and Base Budget user -defined formulas Budgeting F2 04 03 00 00 F2-04-03-00-00 04 - Develop The system shall calculate base budget levels based on the same types of SF Planning and Base Budget user -defined rules used for revenue estimates or spending forecasts. Budgeting F2 04 04 00 00 F2-04-04-00-00 04 - Develop The system shall allow base budget levels to be defined at any level of the SF Planning and Base Bud at financial data classification structure. Budgeting F2 04 05 00 00 F2-04-05-00-00 04 - Develop The system shall accept fields for one-time revenues and costs and allow SF Planning and Base Budget these to be excluded from dppet c�Di�S. Budgeting F2 04 06 00 00 F2-04-06-00-00 04 - Develop The system shall prevent aseline budgets from being loaded into coding SF Planning and Base Bud It block elements that are inactive. Budgeting F2 04 07 00 00 F2-04-07-00-00 04 - Develop System provides the ability to automatically copy current year appropriations SF Planning and Base Budget into future budget years as a starting point to develop base financial data. Budgeting I F2 04 08 00 00 F2-04-08-00-00 04 - Develop System provides the ability to create a base budget using the following: Base Budget F2 04 08 01 00 F2-04-08-01-00 04 - Develop Zero balances in all accounts SF Planning and Base Budget I Budqetinq F2 04 08 02 o6 F2-04-08-02-00 04 - Develop Current year's original budget SF Planning and I Base Budget Budgeting F2 04 08 03 00 F2-04-08-03-00 04 - Develop Last years budgeted total SF Planning and Base Budget I Budgeting F2 04 08 04 00 F2-04-08-04-00 04 - Develop Last years actuals SF Planning and Base Budget I Budqetinq F2 04 08 05 00 F2-04-08-05-00 04 - Develop Last years statistics SF Planning and I Base Budget Budgeting F2 04 08 06 00 F2-04-08-06-00 04 - Develop Current years budget or actual +/_ a percentage SF I Planning and Base Bud, et Budgeting F2 04 08 07 00 F2-04-08-07-00 04 - Develop Previous years budget or actual +/- a percentage SF I Planning and Base Budget Budgeting City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 280 of 418 I # I I I I s i I I I I r 1 I I I f i F2 04 08 08 00 F2-04-08-08-00 04 - Develop Straight line projection SF Planning and Base Budgpet Budaetinq F2 04 06 09 00 F2-04-08-09-00 04 - DeveloP Deleted SF Planning and Base Budget Budgeting F2 04 08 10 00 F2-04-08-10-00 04 - Develop Projection based on user -defined formula - including statistical information, SF Planning and Base Budget Budaetinq F2 04 08 11 00 F2-04-08-1 1 -00 04 - Develop Projection based on estimated actuals from current year. SF Planning and Base Budget Budgetnq F2 04 08 12 00 F2-04-08-12-00 04 - Develop Last Year's Adjusted Budget SF Planning and Base Budget Budaetinq F2 04 08 13 00 F2-04-08-13-00 04 - Develop Current year's appropriation SF Planning and Base Bud et Bud�etin wig F2 05 01 00 00 F2-05-01-00-00 05 - Prepare System allows users to distribute portions of their base budget to different SF Planning and Department personnel to complete Budgeting Submission F2 05 02 00 00 F2-05-02-00-00 05 - Prepare The system should capture department submissions in a budget version for SF Planning and Department comparison to revenue estimates. Budgeting Submission F2 05 03 o6 00 F2-05-03-00-00 05 - Prepare The system should capture user -defined rules for preparing department SF Planning and Department submissions based on multiple step calculations. Budgeting Submission F2 05 04 00 00 F2-05-04-00-00 05 - Prepare The system shall allow definition of formulas that will forecast expenditures Department based on: Submission F2 05 04 01 00 F2-05-04-01-00 05 - Prepare fixed rate adjustments SF Planning and Department Budgeting Submission F2 05 04 02 00 F2-05-04-02-00 05 - Prepare absolute dollar adjustments SF Planning and Department Budgeting Submission F2 05 04 03 00 F2-05-04-03-00 05 - Prepare prior year expenditures SF Planning and Department Budgeting Submission F2 05 04 04 o6 F2-05-04-04-00 05 - Prepare budget amounts SF Planning and Department Budgeting Submission F2 05I 04 05 00 F2-05-04-05-00 05 - Prepare statistical information. SF Planning and Department Budgeting Submission F2 05I O5 00 00 F2-05-05-00-00 05 - Prepare The system shall capture various levels of detail within the expenditure Department projections including: Submission F2 05I 05 01 00 F2-05-05-01-00 05 - Prepare Fund SF Planning and Department Budgeting Submission F2 05I 05 02 00 F2-05-05-02-00 05 - Prepare Account SF Planning and Department Budgeting Submission — F2 05 05 03 00 F2-05-05-03-00 05 - Prepare Organization Unit SF Planning and Department Budgeting Submission F2 05 05 04 00 F2-05-05-04-00 05 - Prepare Any other element of the financial data classification structure SF Planning and Department Budgeting Submission F2 05 06 00 00 F2-05-06-00-00 05 - Prepare The system shall allow definition of budget request control totals by fund or SF Planning and Department any level of the fund structure. Budgeting Submission F2 05 07 00 00 F2-05-07-00-00 05 - Prepare The system shall limit users from entering requests that exceed control SF Planning and Department totals. Budgeting Submission City of Fort Worth / CIBEP, Inc. Professional Services Agreement Page 281 of 418 I ! F 1 Projection based on percentage of last year's actual. Duplicate F2 05 08 00 00 F2-05-08-00-00 05 - Prepare The system shall allow departments to enter decision packages that increase SF Planning and Department or decrease the base budget Budgeting, BI Submission Publisher F2 05 09 00 00 F2-05-09-00-00 05 - Prepare The system shall allow departments to invoke budget caps on a version by SF Planning and Department version basis. Budgeting Submission F2 05 10 00 00 F2-05-10-00-00 05 - Prepare The system shall provide department Flexibility to build a budget from top- SF Planning and Department down or bottom -up. Budgeting Submission F2 05 11 00 00 F2-05-1 1 -00-00 05 - Prepare The system shall allow departments to set absolute caps on the amount of SF Planning and Department new decision packages that can be submitted by lower level organizational Budgeting Submission units. F2 05 12 00 00 F2-05-12-00-00 05 - Prepare The system should allow departments to define their budget build-up by any SF Planning and Department element of the financial data classification structure and aggregate the Budgeting Submission results to the p�rovriation level. F2 05 13 00 00 F2-05-13-00-00 05 - Prepare The system s�all allow departments to set targets for divisions or lower level SF Planning and Department organization units at absolute numbers for a new proposal or expansion by Budgeting Submission division. F2 05 14 00 00 F2-05-14-00-00 05 - Prepare The system shall have the ability to set limits at any level of the financial SF Planning and Department data classification structure. Budgeting Submission F2 05 15 00 00 F2-05-15-00-00 05 - Prepare he system shall allow the user to enter decision packages for any level of SF Planning and Department the financial data classification structure. I Budgeting, BI Submission Publisher F2 05 16 00 00 F2-05-16-00-00 05 - Prepare The system shall allow departments to establish limits on positions and/or SF Planning and Department FTEs at lower levels of their organization structure. Budgeting Submission F2 05 17 00 00 F2-05-17-00-00 05 - Prepare The system shall capture department defined controls in a table -based SF Planning and Department structure. Budgeting Submission F2 05 18 00 00 F2-05-18-00-00 05- Prepare system shall allow the authorized user to over -ride the department SF Planning and Department IThe budget controls. Budgeting I Submission F2 05 19 00 00 F2-05-19-00-00 05 - Prepare system shall provide flexibility for division or department budget SF Planning and Department IThe coordinators to 'freeze' the budget for changes. Budgeting Submission F2 05 20 00 00 172-05-20-00-00 05 - Prepare system shall allow for a coding reduction technique to default coding for SF Planning and Department IThe any budget line. Budgeting I Submission F2 05 21 00 00 F2-05-21-00-00 05 - Prepare The system shall maintain multiple versions available to each department for SF Planning and Department budget preparation. Budgeting Submission F2 05 22 00 00 F2-05-22-00-00 05 - Prepare �he system shall allow users to create snapshots of versions at user defined SF Planning and Department points of time. Budgeting I Submission F2 05 23 00 00 F2-05-23-00-00 05 - Prepare system shall allow users to revert to snapshots. SF Planning and Department IThe Budgeting Submission F2 05 24 00 00 F2-05-24-00-00 05 - Prepare System provides the ability to capture and report standardized data on: Department Submission F2 05 24 01 00 F2-05-24-01-00 05 - Prepare department mission SF Planning and Department Budgeting Submission F2 05 24 02 00 F2-05-24-02-00 05 - Prepare departmental goals SF Planning and Department Budgeting Submission F2 05 24 03 001�-05-24-03-00 05 - Prepare performance measures SF Planning and Department Budgeting Submission City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 282 of 418 The system shall maintain at multiple versions available to each department for budget ,preparation. Grammar ! I I I 4 I i 1 i i i ! 1 I i I I i I I I I ? +, i t r 1 11 1 1 F2 05 25 00 00 F2-05-25-00-00 05 - Prepare System provides the ability to add accounts or other structures for elements SF Planning and Department not represented in the City's Financial system. Budgeting Su mission F2 05 26 00 00 F2-05-26-00-00 05- Prepare System provides the ability to create and categorize adjustments to the base SF Planning and Department budget as current year decision packages. Budgeting Submission F2 05 27 00 00 F2-05-27-00-00 05 - Prepare System provides the ability to define adjustment types based on a user- SF Planning and Department defined list of adjustment categories. (drop down menus) Budgeting Submission F2 05 281 00 00 F2-05-28-00-00 05 - Prepare System provides the ability to capture, display, and report descriptive SF Planning and Department information for decision packages. Budgeting, BI Submission Publisher F2 05 29 00 00 F2-05-29-00-00 05 - Prepare System provides the ability to adjust the current year "base" for forecast SF Planning and Department programs. Budgeting Submission F2 05 30 00 00 F2-05-30-00-00 05 - Prepare System provides the ability to calculate and apply centrally defined across- SF Planning and Department the -board adjustments based on user -defined percentages across any level Budgeting Submission of the financial data classification structure. F2 05 31 00 00 172-05-31-00-00 05 - Prepare System provides the ability to apply percentage increase/decrease to any SF Planning and Department line item category in the budget and assess impact on budget as a whole. Budgeting Submission F2 05 32 00 00 F2-05-32-00-00 05 - Prepare System is capable of performing and saving "what it scenarios (including SF Planning and Department parameters) at the department and Citywide levels. Budgeting Submission F2 05 33 00 00 F2-05-33-00-00 05 - Prepare System provides for analysis of fee -supported activities. SF Planning and Department Budgeting Submission F2 05 34 00 00 F2-05-34-00-00 05 - Prepare System provides the ability to produce "rolling" forecasts based on user- SF Planning and Department defined forecasting methodology. Budgeting Submission F2 05 35 00 00 F2-05-35-00-00 05 - Prepare System provides a spreadsheet presentation (form) for end -users to prepare SF Planning and Department or modify the budget request. Budgeting Submission F2 05 36 00 00 F2-05-36-00-00 05 - Prepare System provides for application of percentage increase or decrease to a SF Planning and Department budgeted category. Budgeting Submission F2 05 371 00 00 F2-05-37-00-00 05 - Prepare System allows standard rates to be established and saved within the system SF Planning and Department that can be applied during the budget development process. Budgeting Submission F2 05 381 00 00 F2-05-38-00-00 05 - Prepare System allows departments to return completed budget fors to the SF Planning and Department department Budget Office electronically vie workflow. Budgeting Submission F2 05 39 00 00 F2-05-39-00-00 05 - Prepare System provides for adjusting the base budget through a decision packages: Department Submission F2 05 39 01 00 F2-05-39-01-00 05 - Prepare by line item MI Planning and Department Budgeting Submission F2 05 39 02 00 K2-05-39-02-00 05 - Prepare in total MI Planning and Department Budgeting Submission F2 05 391 03 00 F2-05.39-03-00 05 - Prepare by amount MI Planning and Department Budgeting Submission F2 05 391 04 00 F2-05-39-04-00 05 - Prepare by percent MI Planning and Department Budgeting Submission F2 06 01 00 0 F2-06-01-00-00 06 - Adjust The system shall calculate early retirement incentives and payoff costs. MA Planning and Budget Budgeting Submissions F2I O6I 021 00 00 F2-06-02-00-00 06 - Adjust The system shall allow the user to adjust decision packages at any level of SF Planning and Budget the financial data classification structure from submitted budget requests. Budgeting I Submissions City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 283 of 418 MEDIUM MEDIUM MEDIUM MEDIUM F2 06 03 00 00 F2-06-03-00-00 06 - Adjust System provides flexible tools to report historical, current, and budgeted data SF Planning and Budget for purposes of reorganization. Budgeting Submissions F2 06 04 00 00 F2-06-04-00-00 06 - Adjust System provides the ability to identify historical and requested operating SF Planning and Budget transfers between departments, funds and programs and capture descriptive Budgeting, Submissions text regarding the nature and purpose of the transfer. General Ledger F2 06 05 00 00 F2-06-05-00-00 06 - Adjust System provides the ability to report and reconcile anticipated operating RQ Planning and Budget transfers in/out between departments, funds, sections and programs to Budgeting, I Submissions ensure that transfers are a balanced. General Led er ill I F2 07 01 00 m �! ii9 00 F2-07-01-00-00 07 - Budget System provides the ability to develop preformatted reports allowing users to SF Planning and Prep Reporting select from a standard assortment of parameters to customize the output to I Budgeting fit their needs. F2 07 02 001 001 F2-07-02-00-00 07 - Budget System provides the ability to produce historical, current, and projected data SF Planning and Prep Reporting down to the lowest common level of detail available in the financial data Budgeting classification structure. F2 07 03 00 00 F2-07-03-00-00 07 - Budget System provides an ad hoc budget query tool that will allow users to query SF Planning and Prep Reporting the budget in any stage of development, including final budget signed into I Budgeting law, by user -defined criteria. F2 07 041 001 00 F2-07-04-00-00 07 - Budget System generates department budget request that displays base and RG Planning and Prep Reporting decision package items. I Budgeting, BI Publisher F2 07 051 001 001 F2-07-05-00-00 07 - Budget System provides detail revenue and expense budget information, including I SF I Planning and Pr p Rep�rtinq �7 base and charges to base. Budgeting F2 07 06I 00 00 F2-07-06-00-00 -Budget System provides the ability to incorporate textual and other non -financial RG Planning and Prep Reporting data on system reports, along with pertinent financial data. I Budgeting, BI I Publisher F2 07 071 001 001 F2-07-07-00-00I 07 - Budget (System provides the ability to report real-time status on the budget I SF I Planning and Prep Reporting levelopment pIOCQ�s with proper authoritv. Budgeting F2 07 081 001 001 F2-07-08-00-00I 07 - Budget (System provides drill -down capabilities from budgeted summary categories I SF I Planning and Prep Reporting to line item detail. Budgeting F2 07 09 00 00 F2-07-09-00-00 07 - Budget System displays information graphically. i SF Planning and Prep Reporting I I Budgeting F2 07 101 001 001 F2-07-1 0-00-001 07 - Budget (System provides the ability to drill down from budget to all underlying data of SF Planning and Prep ReAgltigy the yfaph by is irq oj� ea of the apOic press tation. I I Bud etinq IF2 07 11 00 I I 00 F2-07-11-00-00 07 - Bud e4 I I Sys fam row es he abd to dr 11 down from an � ar amount field to I y (supporting SF Plannn and I Prep Reporting data within the udget entry screen. _ j_ Budgeting F2 07 121 001 001 F2-07-12-00-00I 07 - Budget ISystem provides an ad hoc budget query tool that will allow users to query j SF I Planning and Prep RePgMing budget to identify transfer items and amounts. I Budgeting I F2 07 131 001 001 F2-07-13-00-00) 07 -Budget Estemprovides an ad hoc budget query tool that will allow users to query SF I PBud and Prep Reporting budget to identify administrative charges. Budgeting City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 284 of 418 I I I I i ! E I I r I I I -1 T-I I I I 1 l I Regt Num Category Requirement Teat Dogma of Fit Response Module Complexity of Modification Comments .. Prior Text Change uJ ui 1111 I� IYJri.ilu€ F2-00-01-00-M 00 • Budget Prep - General The system shell support mulOple —ID. e{� Ingt�peael �urino the F2-00-01-01-00 W - Budget Prep - General lnibal axpenddure and revenue SF Hyperion Planning Plus esumetea F2-00-01-02-00 I 00 - Budget Prep • General Base Budget Veal- SF Hyperion Planning Plus I I F2-00-01-03-00 I W - Budget Prep - General Multiple department submission I SF I Hyperion Planning Plus I F2.00-014)4-00 I 00 - Budget Prep - General versions Budget OfN- varebns $F I Hyperion Planning Plus I I I I F2-00-01-05-00 I 00 - Budget Prop • General Council —orris SF Hyperion Planning Plus F2-0G-01-06-W I 00 - Budget Prep - General Detailed DeparDnent operating SF Hyperion Planning Plus budsfg0t em— FUM2-00-00 00 - Budget Prep - General The syalam shall allow the user to SF Hyperion Planning Plus {pn+g rn versior)(I �,(ttre F2-00-03-00-00 00 - Budget Prep • General -MrIjt Theeystam s}yfl proeenl h stodcal SF Hyperion Planning Plus financlel information attar a F2.00.04-00-00 I DO- Budget Prep - General The system "aRm for export SF I Hyperion Planning Plus of budYZ results for interface into F2.00-OSOO-00 I 00 -Budget Prep -General The ayslem shag caldulate budget orelryq)ans u n�'al rx dallno F2-00-OS-O7-00 00 - Budget Prop - General mu16-veru s� yore SF Hyperion Planning Plus F2-00-0502-00 00 - Budget Prep • General wnel-ir simulation SF Hyperon Planning Plus F2-00-05-03-00 00 - Budget Prep - General I integre ri with PC based I SF I Hyperion Planning Plus anal�ypal apo�Icatbna F2-00-0640.00 I 00 • Budget Prep - General IThe ayslam aheA provide version aonbol for b at verolons F2-00-06-01-M I 00 - Budget Prep • General I User defined version names I SF Hyperion Planning Plus VAs Distdbtded', 1- I F2-00.0"2-00 I 00- Budget Prep - General Le.a.. I aer defined atolusea within I SF Hyperon Planning Plus veralons/e.g. Nd Slartal In- I F2.00-06-03-00 I 00 - &wool Prep - General Uaer doAnM spowable ac�lvities SF Hyperion Planning Plus 1 per v�e},a m allowg0e''d, I F2-00-07.00-M I 00 - Budget Prep - General ad The system shah auFomadcally I SF Hyperion Planning Plus I I start the next user that a verolon F2-00.0&1-00 W - Budget Prep - General The system shall alert the user SF Hyperion Planning Plus at n0 �egtered In F2-004)"0-00 00 - Budget Prep - General yaVethy a It�hhee next SF Hyperion Planning Plus {p� Iatus F2-00-10.00-00 00 - Budget Prep - General The eyatem s2rrlao�nitar of SF Hyperion Planning Plus I F2.00-11-00-00 W - Budget Prep - General 5yhtem ehdl erhhy of I SF I Hyperion Planning Plus `eaa � Item r Ilre F2.00-12-00-00 00- Budget Prep - General m a I SF I Hyperon Planning Plus [7Plhe p5P; { F2-00-13-00-00 W - Budget Prep - General iliem3yslenm shall e e user ko 1 SF I Hyperion Planning Plus change xer fields and ca Xum a F2-00a4-00-00 W - Budget Prep - General ITh�e si(yystem shall allow users to SF I Hyperon Planning Plus the level of roundino that F2-00-15-00-00 W - Budget Prep - General Yb " I e system shall allow users to SF Hyperion Planning Plus t�o.& the level of mundinq that I F24W-16-00-00 W - Budget Prep - General The system shall allow SF Hyperion Planning Plus morgaira ntions to be processed p drop(s�rw a drr��gq,att��pp en F2-00-17-00-00 - Budget Prep - General 00T1he system a� allow?he user to SF Hyperion Planning Ptus view the Imrir f omryj�fza0o(hal F2-00-1840.00 I W -Budget Prop -General The system shall provide word I BF I Hyperion Planning Plus, el acaa rim �t`(for tlhe Publisher F2-0411M0-00 I 00 •Budget Prep - General Ceylon �he sego s capturo narrative I SF I Hyperion Planning Plus, BI for t re�Peat� Publisher F2-00-20-00-00 I W - Budget Prep - General Canation system shal�aal�l'ow�uenlimited I SF I Hyperon Planning Plus re F2-00-21-0GO0 I 00 - Budget Prop - �erel ystteemyph^a�NJ:9 for m.1& I SF I Heron PlanningPlus, 81 MTh. omr. F2-00-22-00-00 00 - Budget Prep - General The system aI, r SF Hyperon Planning Plus I multiple fields to capture nanetNe, and rullz useJ pon�l�ure wMch F2-00-23-p0{IO W -Budget Prep - General IThe sysem steal(check }or SF I Hyperon Planning Plus F2-00-24-W-00 W - Budget Prep - General a(wroyal before toedino budgets IThe system ssryh1alllQl a�u7fnoma�etice4y MI Hyperion Planning Plus, Oracle ood IThe Oat. Inlaid tor F2-00.25.00•W 00 - Budget Prep - General systemoshall arm the user to Ildanb SF Hyperion Planning Plus F2-00-26-00-W 00-Budget Prep - General c �b as ISystem SF Hyperon Planning Plus mrsuo a budaetarv-based funds City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 285 of 418 F2-00-27.0OW 00 - Budget Prep - General System provides, the ability tto�t� SF Hyperion Planning Plus F2-00-2"0-W 00 - Budget Prep - General Sp alloas 1b; IMecapab SF Hyperion Planning Plus to adfuet badge) aubmill.1— across varvir levels of the F2-00-29-00-00 W - Budget Prep - General System provides the abglly to SF Hyperion Planning Plus import data into the budget preparation rlooll from the finandel systn of F2-OOJO-00-00 00- Budget Prep- GeneralSystem provides a a SF Hyperion Planning Plus rerehve dale from and �prt data F2-00-31-00-W W -Budge) Prep -Genets) Syseeem has, me Ability 6o eMbaWch� SF Hyperion Planning Plus file,161., Word, taatta F2-00.32-00-00 00 - Budget Prep - General Systed'i has Ow ability h SF Hyperion Planning Plus Excel) to F2-W-33-00-00 W - Budget Prep - General Sys(am hasWlha abli y b racord� Hyperion Planning Plus q�la Qlnt do the follow", nM- IF2-o033-01-00 00-Budget Prep -General Purpdse SF Hypenon Planning Plus I F2-00-33-02-00 W - Budget Prep - General Consequences SF Hyperion Planning Plus F2400-33-03-00 W - Budget Prep - General Funding Sources SF Hyperion Planning Plus F2-00-33-0400 W - Budget Prep - General Legal Authority SF Hyperion Planning Plus F2-00-33-05-W 00 - Budget Prep - General Appropriation Type SF Hyperion Planning Plus F2-0033-06-M W - Budget Prep - General Appropriation Title SF Hyperion Planning Plus F2-00-33-07-00 W- Budget Prep - Generel Ongoing or(hu-time SF Hyperion Planning Plus F2-0043-08-00 W - Budget Prep - General User Defined Field N1 SF Hyperion Planning Plus F2-00-33-09-00 W - Budget Prep - Generel User Defined Field N2 SF Hyperion Planning Plus F2-00-33-10-00 W - Budget Prep - Generel Lear Defined Field #3 SF Hyperion Planning Plus 1`2-00-34-00-00 00 - Budget Prep - General System alto" users to prepare SF Hyperion Planning Plus, BI I I (recison ppcke Is. any level of Publisher F2-OO-35-00-00 OD- Budget Prep - General Sy;.im 411ows uses o prepare SF Hyperion Plennilg Plus, BI (1p,^IWAn (yl,Maoea ky muNde PuWbher F2-W-30-00-00 W - Budget Prep -General Sys(em aliowsj�upse%s�1n PPrreperea{ SF Hyperion Planning Plus, BI � Publisher F2-0037-00-Og W - Budget Prep - General ="1** abwttlnetuaar io SF Hyperion Planning Plus hv���ry . data before F2-W38-M00 W - Budget Prep - General sspghy.d11 Mg funds Mel SF Hyperion Planning Plus �pT+++MYYppay618m F2-00-39-00-00 W - Budget Prep - General Syalem provldn Nhs abilityy too SF Hyperion Planning Plus establish multiple rolWps of (��ahqq(tront data /p�qy da b F2-0"0.00-00 W - Budget Prep - General Sy.bm provides line ahilHy b SF Hypenon Planning Plus ccrreejaseelWmultiple, user-daefinoeldle lld npp�l(on F2-00-41-00-00 W - Budget Prop-Generel Syilerri allows a of SF Hyperion Planning Plus d rill f{hrpcast'^{� calwletms to F2-06d2-0U-00 W - Budget Prep - General S e�blry appg . of SF Hypenon Planning Plus deters.t forecast?y celwlathns to F2-00i3-00-00 00- Budget Prep - Generel System allows mufiple torecash SF Hyperion Planning Pius for k- It— rrMeryaeme �acua�irlrg puss, F2-00.M DO-00-00 - Budget Prep -Garlandays em 11 a ll Droaanl SF Hyperion Planning Flue d0e'p�ar`ttmental subnYs�a►dni, w as r F2-0045-00-00 00 - Budget Prep - G-1 SyUBrH aTowa M u3# to Nadl6 SF Hypenon Planning Plus ind vidual formulas for each cell in F2-0048.00.00 W - Budget Prep - General System allows the user to input SF Hyperion Planning Plus actual numbers Into each call in F2-O047-00-00 W - Budget Prep- General System ato vs Me 1b W to forecast SF Hyperion Planning Plus n43 poslr pwnts. F2-00./8-O0-00 W - Budget Prep -Garners) �plfrmb �/jppwms�jps us r �o copyy SF Hyperion Planning Plus `pymss�sm ud— F2-00�9-00.00 W - Budget Prep - Ganeml Syslemrysallows the user to.n.(.a SF Hyperion Planning Plus k,. one formula. Sys%W patovn F2-00-50-00-00 i W - Budget Prep - Ganwat for creating SF Hyperion Planning Plus relation a anti F2-00.51-00.00 W - Budget Prop - General System rq�„, SF Hyperion Planning Plus and reporting non-liunciet dab. F2-01-01-00-00 01 - Prepare Revenue, Estimates s)ystJern capture SF Hyperion Planning Plus (The should src�osmn F2-01-02-00-00 Ot -Prepare Revenue Estlmaten Ihedyer shag ya em ceahlro merrue SF Hyperion Planning Plus I F2-01-03-00-W estimates In y tryldpeJ y rn for 01 - Prepare Revenue Estimates The ryalem slut) ca(wkte SF I Hyperion Planning Plus revenue estmat" based on user. defined rules to edual a F2-01-04-00-W 01 - Prepare Revenue Estimates The system capture user- SF Hyperion Planning Plus defined rules for o0iectno City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 286 of 418 1 1 1 1 1 1 1 1 1 i 1 f I 1 I I I I 1 I F2-01-05A0-00 01 - Prepare Revenue Estimates The system shall allow definition of Hyperion Planning Plus formulas that will orded revenues F2-01-OS-01-00 01 - Prepare Revenue Estimates SF Hyperon Planning Plus I{I faed rate adjustments F2-01-06-02-00 01- Prepare Revenue Estimates SF Hyperion Planning Plus absolute dollar adjuatrnents F2-01-05-03-00 01 • Prepare Revenue Estimates prior year expenditure or SF Hypedon Planning Plus I revenue balances F2-014)5.O4-00 01 - Prepare Revenue Estimates grant match requirements SF Hyperion Planning Plus 1 F2-01-05-05-W 01 - Prepare Revenue Estimates statistical information entered by SF Hyperion Planning Plus a vryar I F2-014)0-00-00 01 - Prepare Revenue Estimates The eye era shall allow tM use o Hyperion Planning Plus vial' and asses compq�atiYe F2-01-06-01-00 01 - Prepare Revenue Estimates prior year revenue sLmake SF Hyperion Planning Plus F2-01.OS-02-00 01 - Prepare Revenue Estimates current year revenue estimate SF Hyperon Planning Plus F2-01 0"3.00 01 - Prepare Revenue Estimaes future year revenue estimate SF Hyperon Planning Plus F2-01-06-04-00 01 - Prepare Revenue Esfimates prior year actual SF Hyperion Planning Plus IF2-01-0"5-00 01 - Prepare Revenue Estimates current year actual SF Hyperion Planning Plus I 1 I F2-01-07.00.00 01 • Prepare Revenue Estimates The system shell alow the user to SF Hyperion Planning Pals 1 t estimates by end F2-01-06-00-00 01 • Prepare Revenue Estimates system shera o 10 SF Hyperion Planning Plus yy euPrelpJu�p revuides F2-01-0900-00 pe Systemf 01 -PrePrepare Revenue ESOmatea prov e a � �o bl OY SF Hyperion Planning Plus maintain revenue forecast detail nt and revenue F2-02-01-00-00 02 - Provide Budget Preparation The system shall capture the SF Hyperion Planning Plus Guidance budges calendar. F2-0242-00-00 02 • Provide Budget Preparation The system shall notify budget SF Hyperion Planning Plus I I Guidance coordinators of the establishment F2-02-03-00-00 02 - Provide Budget Preparation The system shall use budget SF Hyperion Planning Plus Guidance cetender dales as the trigger for uaer-defined e-mail sleds to F2-02-04-00-00 02 • Provide Budget Preparation line system should allow users to Hyperion Planning Plus Guidance define budget bums for. F2-024)4-01-00 102 - Provide Budget Preparation I Insbudlons I SF Hyperion Planning Plus I I I I Guidance F2-02-04-02.00 102 - ProvideBudgetPraparatlon I combinationof the I SF Hyperion Planning Plus dAny ata structure GuiF2-02-04-03-00 02 - Provide Budget Preparation Narrative descriptions SF Hyped. Planning Plus Guidance F2-02-04404-00 02- Provide Budget Preparation Na--justfications SF Hyperion Planning Plus Guidance F2-0210A5.00 02 - Provide Budget Preparation Internal Service Fund rates SF Hyperion Planning Plus Guidance F2-02-0"6-M • Provide Budget Preparation Adminlstra0ve Charges for SF Hypenon Planning Plus 102 ce Guidaninternal service funds I I 1`2-02.05.00-00 - Provide Budget Preparation system should allow far SF Hyperion Planning Plus 102 ITho ce Guidandefinition of business rules for I F2-02-06.00-00 02 - Provide Budget Preparation The system should allow for IylgWon�jF SF Hyperion Planning Plus Guidance rib(�j ' Qt (ludoel F2 02-07-00-00 02 - Provide Budget Proparaton fie syelem small calasale SF Hyperon PWrvt rig Plus I Guidance (Ty�net edritlon dates for F2 02-06-00-00 102 -Provide Budget Preparation yS stern Iowa department Budget I SF Hyperion Plem rig Pius Guidance Office to ^ u • vre workflow l r"irdl, lllu ihll III itVIVH41 VV1itf1161ViuVllii V i F2-03-01410-00 03 - Position Based Budgalirg The system atudf provide fully Intsprated personal services F2-03-01-01-00 03 - Position Based Budgeting using the same poet ion MI Hyperion Planning Plus information Workforce Planning Module, Grade Date I�bgretor F2-03-01-02.00 03 - Position Based Budgeting I tiring ma same job information I SF Workforce Planmig Module, Oracle Data I�Lagfeor F2-03-01-03-00 03 - Position Based Budgeting I using the e somemployee actual I MI Workforce Planning Module, I information Oracle Data Inteoraor F2-03-024)0-00 03 - Position Based Budgeting ISystam allows for what4f I I I funir. n I%within the personal F2-03-02-01-00 03. Position Based Budgeting I comrnort applies usende0ned SF Hyperion Planning Plus, oavrrswrinonpns Ih s Workforce Plenniryq Module F2-03-02.02-00 03 • Position Based Budgeting prov pugs pro vacancy SF Hyperion Planning Plus, rates based on hiss ricat data Workforce Planm,'r�Module F2-03-02-03-00 03 • Position Based Budgeting provides projections of the BF Hyperion Planning FNus, Impacts of Ir rxrements Workforce Plann�'rgl Module F2-03-02-04-00 03 -Position Based Budgeting �upport((11s esigfnmaliyJn�gRsbenefits and SF Hyperion Piannlrynag Plus, .n for eF.a Module WHypenon F2.03-02-05-00 03. Position Based Budgeting stlmaUrq beanefits and SF Pilennl{ng Plus, com soon y actual I Workforce Plannira ule F2-03-02-0600 03 - Position Based Budgeting I supports multiple position -based I SF Hyperion Planning us, funding assignments or Workforce Planning Module City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 287 of418 F2-03-02-07-00 03 - Position Based Budgeting supports projecting only the SF Hyperion Planning Plus, operating fund off�a sslat Woridonce Planning Module llporoonn wis if F2-03-03-00-00 03 - Position Based Budgeting ds delag for SF Hyperion PlanningPlus, lT�eh�ess q�em�slha�llipl� I ry.y orldorce WHyperionp=m. F2-03-04-00-00 03 - Position Based Budgeting The should slow poationa SF P4 ,le (filled, budgeted or planned) to be Waldorce Planning Module handed by multiple combinations of financial data classiflcaticn F2-03-05-00-00 03 - Position Bated Budgeting Tha system shall allow users to SF Hyperion Planning Plus, calculate payroll projections based ( Workforce Planning Module on filled and/or vacant hudaeted F2-03-06-00-00 I 03 - Poston Based Budgeting The system shall ale to an ley rolaea a F2-03.0641.00 I 03 - Position Based Budgeting an moss ncraates or I SF Hyperion Planning Plus, I I decreases Workforn Plafriga Module F2-03-0602-00 I 03 - Position Based Budgeting Scheduled pay inaroases on I SF I Hyperion P mu ng Plus, decrease. Workforce PlanrYj�M�odule F2-03-06-03-00 I 03 - Position Based Budgeting Cost of Iivng Adjustments l SF I Hyperion Plarminp Plus, a o fora ifif kirm` le dig F2-03-0S-0{-00 I 03 -Position Based Budgeting SF Hyperion ists PWs y=ra(I orkforce Modu le WHyperion F2-03-0G05-00 I 03 - Position Based Budgeting (leer riod riles SF Planning Pula Workforce Plannim Module F2-03-07-00-00 l 03 - Position Based BudgaOnng The system shell estimate healthcare and nee benefit costs F2.03-07-01-00 I 03 - Position Based Budgeting personnelass4wrents SF Hyperion Planning Plus, Workforce Plenniro Module position based SF mg Hyperion Plaonvg Plus, I (Added Workforce on, F2-03-07-02-00 03 - Position Based Budgeting hislorical hinge benefit ratios SF Hyperion Plannmg us, Workforce Ptenni�nd Module F2-03-0B-00-00 I 03 - Position Based B udgetirg The system shall capture narrative SF Pating Hyperon nPlus, I (eoarolltln �eV�I and a Workforce Planni Module : F2-03-09-00-00 03 - Position Based Budgelkg The system still aggra� SF Hyperion n ri�i Ph s, position letaibd payroll Workforce Planning Module prdpctlam me across an elements of F2-03-10-00-00 03 - Position Based Budgeting wW deliver fundionegry to SF Hyperion Planning Plus, °9ys WHyperion l F2-03-10-01-00 03 - Position Based Budgeting Atld or ds posdwnrbom SF Plate ny Plus. Warkloroe Plann"l�n Module F2-03.10.02-00 03 - Position Based Budgeting Reclassify positions Sic Hyperion Plarunmfl Plus, Wariroroe Plan�I'Pr�MatlWa F2-03-1043-00 03 - Position Based Budgeting Modify posOkns SF HryyMpearifon�Pylannin°g Plus, WOfkforf'a F2-03-10-01-00 03 - Position Based Budgeting Transfer positions SF Planning , Warkforu PbnMPfv�L�ModUe F2.03.10-05-00 03. Position Based Budgeting Freeze or unfreeze positions SF Hyperon PWnnipjnogPlus, orliforce WHyperion l F2-03-10-0600 03 - Position Based Budgeting Split positions SF Plannihig Plus Workforce Ptennir�p Module lF2-03-10-07-00 03 - Position Based Budgeting Charge the number of SF Hyperion ptennmg Plus. ""hon"d full World— larmipa le pFUnring F2-03.10-0&00 u rgpWvalenb 03 - Position Bated Budgeting Control the numberoollposition SF Hyperion Plus ar pbywa filling a Woricfonce Planning Module, Human Resource Module F2-03.11-00-00 03 - Position Based Budgeting System will deriver functonaly o SF Hyperion Planning Plus, perform Donne edit drockirq and Woddorce Planning Module. vandatlon o id when more Human Resource Mrdula F2-03-12-00-00 arill 03 -Position Based Budgeting ors SF yperion Planning Plus, positionchange ath I I non lentos us forj Hui Resource Module F2-03-13-00-DD MOO deliver functionally, to 03 - Position Based Budgeting I SF Planning Plus, l s I WH�elynrltPyMods le 2-03.1s•00-00 03 - Position Based Budgeting fneve Ihs su ( SF I lS p�nyviGl n � �� Workforce Plaamm�ilnaa Module F2-03-15-00-00 03 - Position Bated Budgeting Debled System wdl have luncdonatty to enter single or multiple funding sources lion each oosilo Duohrate F2-03-10-00-00 03 - Position Based Budgeting System wnl have functionality with SF Hyperion Planning Plus, ry charges in oenlzation atrucoae Workforce, Plenrvtg Module to auomatit" create a dated F2-03-17-0P00 I 03 - Position Based Budgeting System will have functiornehry to I SF Plus, I t acWaI raaounce cosh WHyperio Plannlmg _ F2-03-18-00-00 I 03 - Position Based Budgeting V. lid -ions I SF Hyperion lann ing Plus, I �^�'( rotes fdrl oo U%y env Workforce PlModule 2.03.19-00.00 03 - Position Based Budgeting The rysibm stroll control ooll I SF Hyperion Plano us. I I on planned. buVroled or Workforce Planni Module - - - - -- --- - - -- - F2-03-20-00-00 I 03 - Position Band Budgetinp Thi system stiff provoe s rater I SF I Hyperion Plannmg us, and a view of "ad //yyNMroom. C. Workforce PlanniT Module F2-03-21-00-00 I 03 - Position Based Budgeting 'Me ahall the user to I SF I Hyperion Plannmg Plus, o�soy6sltem forinclusion in the WHyperionpPlannmg F2-03.22-00.00 sue 03 -Poston Based Budgeting Tiro aysrom 5he11 be acts to rob project BF Plus,' position salaries and Workforce Planning Module across arry element of the financial City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 288 of 418 F2-03-22-01-00 03 - Position Based Budgeting filled positions IF2-03-22-02-00 03 - Position Based Budgeting vacant positions IF2-03-2203-00 03 - Position Based Budgeting planned positions, by date F2-03-23-00-00 03 - Position Based Budgeting The system shall flag budgeted Cosmanb that have exceeded F2-03-24-00-00 03 - Position Based Budgeting The system shall record and back �a"'-j0 frh pp9 *9p1ta1N106b F2-03-25.00-00 03 - Position Based Budgeting he sysllem s a prow a ew r to departments to plan recl...ifir -no and car -a- F2-03-26-00-00 03 - Position Based Budgeting fits syslem .hall .lbw department budgetanalysis build �tfoo'adssaalla}ry5 F2-03-27-0000 03 - Position Based Budgeting The byilahe�hdaH provide'whal it F2-03-28-00-00 03 - Position Based Budgeting modelin ( for h troll pmiegj)ojty ry I. syslem s a prow�da �edbi�l to cast out new/y�sitions et F2-03-2"000 03 - Position Based Budgeting IThe system 6helf project tr(nge benefits wimin tj ravroll yljt�male 1 F2-03-30-00-00 03 - Position Based Budgeting IThe syslem shall prow e e ability to calculate the future binge F2-03-31-00-00 03 - Position Based Budgeting IThe system shall update j1 Ffi s to roiect future F2-04-01-00-00 04 - Develop Base Bu7mfortbo? all allow for creation se budget amounts F2-04-010+.(iri 04 - Develo. Base 8W et nayear based on I acluabalance tom current Rear F2-04-01-8j-��iS 04 - Develoi�Bese B et I m� �1 amour F2-04-01-03-00 .t 04 - Develo�Il-- BF2-04-01-04-00 e�py.�ppriadon re$Js�li9�+mEe(1t1�7 F2-04-01 05-00 04uu 04 - Develor�Case Bud(�et n ryglo I stal(sgcA1 IhT088118H. unt from F2-04-02-00-00 04 - Develop Base Budget (System supports creation of the m mniel p�p� pOt empvnts by F2-04-02,(i10�7 04 -Develo Base P���111.gt i fixe(ira'te edp/9lm I F2-04-02-112di1 I F2 04-02-03-00 I 04 - Develo`�ase Bucjpet I i absolute da(lal aQiustmeMs 1 fomSulas 1 F2-04-03-00-00 04 - Develor�Bese B 04 - Develop Base B pe[ gel user -defined system shall calculate base IThe budget levels be— on the name �(O°s of userdefined rules used F2-04-04-00-00 I 04 -Develop Bate Butlget IThe system shall allow base budget I to be defined I F2-04-050000 04 - Develop Base Budget vels at anv The system shall accept fields for one-tirrlP veils and r,�pts gjtd I F2-04-06-00 00 04 -Develop Base Budget The systems prevent aa.lne budaats from beipy toaded Into F2-04-07-0000 04 - Develop Base Budget System provides fhe ability to automatically copy current year gppj.ryjau7 jMn future budget F2-04-08-00-00 I 04 - Develop Base Budget Sys pro des a ability to create a base budget using the I F2-04-08-0100 I 04 - Develor�Base Budget 1 Zero balances in all accounts I F2-04-08-02-00 I F2-0406-03-00 1 04 - Dev¢. Now Budl�et I 64 - Dev®n�Dase Bud at I Eur(ant ears odainal buret I Leal veer s butl�9led total I F2.04080400 F2-04-0B-05-00 I 04 -[� evenn �IIs" oe I 04 - Dever Base u pe I Lastyea,['s acNmt l I eaf ��7 s etatbtks I F2-04-08-06-00 Ip 1 04 - Deve7t�Case .QI I C�urreni vear'aPyp set or actual I I F2.04-0"7.00 1 04-Deve+� E we ��jj q, 1 Previca. nacres bulr(t�.t or actual I F2-04.08-08-00 1 04 - Dav��lse Budr1t11 I S�trjtijrhl lone oroiecti0 1 F2-04-08-09-00 04, Deve Jp Beae Burrrrllllgeii I e11e1leedd I F2-04-08.10-00 I 04 - Develop Bese Budget I Projection based on user- defined formula - Including I F2-04-08-11-00 I F2-0d-08-1%-00 04 - Develo Base Buret I Prjrtaction based on estimated 04 • Develo�ase Budget i LAst Yeafa Adjusted eu et I F2-04-08-1300 04 - Develo�ese Bud el Currant safe a ro en F2-05-01-0000 05 - Prepare Department System allows users to distribute Submission Melrbase budget to I F2-05-02-00.00 05 - Prepare Department WCglonsl�ll1 Tlie sys(6m should capture Submission department submissions in a F2-05-03-OD4W 05 - Prepare Department The system should capture war- defin ryfes 1pl P�fl dpq syslem F2-05-04-OD-00 O6 - Prepare Department 05 The shall allow daRnilfon of Submission formulas that wig forecast I F2-05-04-01-00 05 - Prepare Department fixed rate adjustments Submission F2-05-04-02-00 05 - Prepare Department absolute dollar adjustments I Submission F2-05-04-03-00 05 - Prepare Department I prior year expenditures Submission F2-05-04-04-00 05 - Prepare Department I budget amounts Submission City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 289 of 418 SF Hyperion Planning Plus, Workforce Planni'1a Module SF Hyperion PlammPlus, I Workforce Plonnirnn Module Sf Hyperion Planning Plus SF Hyperion Planning Plus, Workforce Plannir)a Module SF Hyperion Planning Plus, Workforce Planning Module SF Hyperion Plannmg Plus, Workforce Planning Module SF Hyperion Planning Plus, Workforce Planning Module SF Hyperion Planning Plus, Workforce Plannira Module SF perion Planning Plus, I Hy Workforce Plannt Module SF Hyperion Plamm�g Plus, Workforce Planni�ra Module SF Hyperion Ptanning Plus, Workforce Plannipo Module SF Hyperion Planning Plus, Workforce Planni Module SF Plannino Plus SF oerjon Plannjn. Plus I I SF �,erlon .anon AA annln Plus I SF oerion Plarm n P us I SF oerion Planning Plus SF SF Plann fc��Plus I HvoerjpriPlann�lfLPlus I I I I I SF I HNYoenon Plammn�PPlus I I I I SF Hyperion Planning Plus SF I Hyperion Planning Plus SF Hyperion Planning Plus SF Hyperion Planning Plus I SF Hyperion Planning Plus I1 SF I aoerjon annnyPlus I I SF I w n nn�n Plus I P i I I SF I � voer�on Bann ncc��Plus I I I I SF I Voerjnn nP�Plus I I I SF SF 1 APlus 1 1 v.edon Pia rmi i Plus I jl I I I I SF I voerjon Plannp�+c I I I I SF voe on ann'nyPlus I I I I SF yper�iorl Plamm�g Plus Projection based on percentage of last year's actual. I Duplicate SF Hyperion Planning Plus I I SF yy rion Plann4nr�Plus Plus SF SF Hvoerion Plamm�` P Plus Amami SF Hyperion Planning Plus SF Hyperion Planning Plus I SF Hyperion Planning Plus SF Hyperion Planning Plus SF Hyperion Planning Plus SF Hyperion Planning Plus SF Hyperion Planning Plus F2-05-04-05-00 05 - Prepare Department statistical information. SF Hyperion Planning Plus SubrMSsion F2-05-05-00-00 OS - Prepare Department The system shall capture various Submission levels of detall within the F2-05-05-01-00 05 - Prepare Department Fund SF Hyperion Planning Plus Submission F2-05-05-02-00 05 - Prepare Departmem Account SF Hyperion Planning Plus Submission F2-05-05-03-00 05 - Prepare Department Organization Unit SF Hyperion Planning Plus Submission F2-05-05-04-00 05 - Prepare Department Any other element of the SF Hyperion Planning Plus ' Submission financial data classification F2-05-06-00-00 05 - Prepare Department The system shall allow definition of SF Hyperion Planning Plus Submission budoet cf�oauest control totals by F2-05-07-00-00 05 - Prepare Department The syttem shall limit users from SF Hyperion Planning Plus ' Submission entering roauesta that exceed F2-05-08-00-00 05 - Prepare Department The syaEem shall allow SF Hyperion Planning Plus, BI Submission departments to enter decision Publisher F2-05-09-00-00 OS - Prepare Department The system shall allow SF Hyperion Planning Plus Submission rjeoamtnyanIs (p g 6W F2-05-10-00-00 05 - Prepare Department �vo1 TThhee systteem she provide SF Hyperion Planning Plus Submission deoartment flexibility to build a F2.05-11-00-00 05.Prepare Department The system shag allow SF Hyperion Planning Plus Submission daparmwill to set absolute rap. the aJmou R of 'lion F2-05-12-00.00 OS -Prepare Department Ths system a SF Hyperion Planning Plus Submission depaMtents to define their budget build-uo yam agy of the F2-05-13-00-00 OS -Prepare DepartmentThe �=t ays(em she dbw SF Hyperion Planning Plus Submission two set targets for (tlljevlpartmgenb system F2-05-14-0D-00 05 - Prepare Department The shah have the ability SF Hyperion Planning Plus Subnssion to set limits at anv level of the F2-05.15-00-00 05.Prepare Department The system shag allow the user to SF Hyperion Planning Plus, BI Submission gfhhterd for env Publisher F2-05.16-00-00 05 - Prepare Department m3to9Apkppes TI» �m I' e'bx SF Hyperion Planning Pius, Submission 4posirlmiants to establish Itmge on Workforce Plannirrti Module F2405-17.00.00 05 - Prepare Department Me systern shag eapture SF Hyperion Planning Plus, F2.05.18-00-00 SubrMasion 05 - Prepare Department rtmant defined controls in a system shall alkzw the SF Worklorce Plannirpa Module Hyperion Planninig Plus, Submission 8lttan'zfM usFr'lhv gryiQe Me Workforce Plannirpo Module F2-05-18-00-00 05 - Prepare Department Tha system shall rovlde lkxibgity SF Hyperion Planning Plus Submission for division or de t budoet F2-05.2D-00-00 OS -Prepare Department The system sho for a SF Hyperion Planning Plus Submission pilino raducpm0 )echrhyaua to F2-05-21-00-00 05 - Prepare Department The systems main to multiple SF Hyperion Planning Plus The system shall maintain at Submission versions available to each multiple versions available to each I department for budget preparation. Department for budget preparation. Grammar F2-05-224)D-00 05 - Prepare Department The system shall allow user to SF Hyperion Planning Plus Submission create snao.yots of versions at ' F2-05.23.00.00 05 - Prepare Department The system shall allow users to SF Hyperion Planning Plus Submission is F2-05-24-00-00 05 - Prepare Department Syj�sMAluetn provi(rdesothe ability to Submission nderdized ondepartmen! F2-06-24-01-00 OS -Preps Depsrtnnent m= pm SF Hyperion Performance Scorecard, Sub -salon Hyperion Planning Plus F2-05.24-02.00 05 - Prepare Department departmental goals 9 SF Hyperion Performance Scorecard, Submission Hyperion Planning Plus F2-05-24-03-00 05-PS Prepare performsncce measures SF Hyperon r ( Hyperion anning��nt, Plus F2-05-25-00-00 05 - Prepare System t a I SF Hyperion Planning Plus S atsDepartment (Wdes(thhtmablilliiityy F2.05-26-00-00 05 - Prepare Department Systyjea- Providesgtlhyeaa9Wlilt{yy SF Hyperion Planning Plus Submission ents I F2-05-27-00-00 05 - Prepare Department Sysefem provk 1fie argly to I SF Hyperion Planning Plus Submission define adius nil Jvoq+y F2-05-28-00-00 05 - Prepare Department Mon System lfne WI11y fo SF Hyperon Planning Plus, BI Submission capture. tlis,-d!a%. and re Publisher F2-05-28-00-00 OS -Prepare Department System Pnowoea tithes ab(Igy to I SF Hyperion Planning Plus adiust the ar or F2-05-30.00-00 05 - Prepare Dep rtnenl System providesttha ability to SF Hyperion Planning Plus Submission ceoulats and apply centrally I dellned across-the-board F2-05-31-00-00 05 - Prepare Department System proWdes the ability o SF Hyperion Planning Plus Submission apply Percentage I P to an Irlormi item, F2-0532-00-00 OS -Prepare Department S tam is capable of pre SF Hyperion Planning Plus Submission and saving 1Mat it scenarios I F2-05-33-00-00 05 - Prepare Department System provides for analysis of I SF Hyperion Planning Plus Submission fee-suuooted activities. F2-05-34-00-00 05 - Prepare Department System provides the ability to SF Hyperion Planning Plus Submission orodta»'rollin7forecasts based I City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 290 of 418 I I I I 1 I 1 1 $ 1 1 1 1 1 1 1 1 1 1 F205-35-00-00 05 - Prepare Department System provides a spreadsheet SF Hyperion Planning Plus Submission pre entetion/orr�l for end -users F2-05-36-00-00 05 - Prepare Department Sys�em prow es for applica0on of SF Hyperion Planning Plus _ Submission joeWtai increyse or decrease F2-05-37-00-00 05 - Prepare Department System allows standard rates to SF Hyperion Planning Plus Submission be established and saved within F2-0536-00-00 05 - Prepare Department System allows departments to SF Hyperion Planning Plus Submission return comol�'jnd dq$�f�rmq)n 9r _ F2-0539-00-00 05 - Prepare Department System provIles adrysOng {he Submission base hurt through a decision F2-05-39-01-00 05 - Prepare Department by line uem SF Hyperion Planning Plus Submission F2-05-39-02-00 05 - Prepare Department in total SF Hyperion Planning Plus Submission F2-05-39.03-00 05. Prepare Department by amount SF Hyperion Planning Plus Submission F2-05-39-04-00 05 - Prepare Department by percent SF Hyperion Planning Plus Submission F2-06-01-00-00 06 - Adjust Budget Submissions he system shall calculate early SF Hyperion Planning Plus, Letiremgpt mynJ a��oavo f Workforce Plannirp Module F2-06-02-00-00 06 - Adjust Budget Submissions The sys/em aFa a (ow user to SF Hyperion Planning Plus adjust decision packages at any level of the financial data F2-06-03-00-00 06 - Adjust Budget Submissions System provides flexible tools to SF Hyperion Planning Plus revop historical. current and - F2-06-04-00-00 06 -Adjust Budget Submissions System provides the ability to SF Hyperion Planning Plus, General identify historical and requested Ledger operating transf�eTM]rs�between deoaF2-06-05-00-00 06 - Adjust Budget Submissions System prow s the adlityrotarams SF Hyperion Planning Plus report and reconcile anticipated operafina transfers INout between «',3.,' 1' � 1' ., i a„ • _. Gw e> r.i:.. , ". ' 'e� 'mom' � F2-07-01-00-00 07 - Budget Prep Reporting System provides the ability to SF Hyperion Planning Plus develop preformaded reports allowina users to select from a F2-07-02-00-00 07 - Budget Prep Reporting System provides the ability to SF Hyperion Planning Plus Produce historical, current, and orokected data down to the lowest F2-07-03-00-00 07 - Budget Prep Reporting System provides an ad hoc budget SF Hyperion Planning Plus query tool that will allow users to pppery the budget in anv stage of F2-07-04-00-00 07 - Budget Prep Reporting System generates department SF Hyperion Planning Plus, BI t reouest that disolays base Publisher F2-07-05-00-00 07. Budget Prep Reporting ys am provides detail revenue SF Hyperion Planning Plus and explanse budgpet infrm oation. F2-07-06-00 00 ( 07 - Budget Prep Reporting System provides U1e ability to SF Hyperion Planning Plus, BI inco/oorate (BjCfugl and other non- Publisher F2-07-07-00-00 I 07 - Budget Prep Reporting System prov ea a ability to SF Hyperion Planning Plus reo�rt real-time status on the F2-07-00"000 07 - Budget Prep Reporting System pmvides drill -down SF Hyperion Planning Plus caoabil"M1ies from outlasted F2-07-09-0D-00 07 - Budget Prep Reporting System displays information SF Hyperion Planning Plus aratjhimlly. F2-07-10-00-00 � 07 - Budget Prep Reporting ?;ys provides the ability to tlrill SF Hyperion Planning Plus down from bu alto all unde0 1 F2-07-11-00-00 07 -Budget Prep Reporting System provi s the agM�litygto drill SF Hyperion Planning Plus down doltfi y provit Iget F2-07-12-00-00 I 07 - Budget Prep Reporting System aan ad hoc bud SF Hyperion Planning Plus QQpejv lad that will allow users to F2-07-13-00-00 I 07 - Budget Prep Reporting System provides an ad hoc budget SF Hyperion Planning Plus cue, tool that will allow users to City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 291 of 418 I I I I Ilypd(pn hom the same transaction source. I I F3 OOI 02) W °°I F3-00.02-gg.6g 00 • Finenolal Controls r4sasedl security rules based on fina_ Isle s°1n��sinfoic (sew Individually or in combinstions)tlanckaling but fds F3 00 02I 01 00 F3110-02-01-00 00 - Finwtcial Caltrols Fund MA I General Ledger F3 00 02 02 00 F3,1"2-02,00 UO-FinsnWl Controls Sub-FW I MA I Generel Ledger F3 00 02 03I 00 F34"2-03-00 00 - Fasnctal Controls Department I MA General Ledger F3 00 02 04I 00 F3-00-02-04-00 00 - Fasncial Controls Hierarch" 0,9— on (Department. DMeon, S-1k;n) MA I General Ledger F3 00 02 05I 00 F3-00-02-05.00 00 - Finandal Coed, C—Inad I MA General Ledger F3 00 02 08I 00 FaQD-02-06-00 00 - Financial Controls Program I MA General Ledger F3 00 02 07I 00 F340-02-07-00 00 - Fnsnwl Controls Loc fioon (e.g.. G-11 Dismal) I MA Genleral Ledger III a SF IF3 F3 00, 02I 09I 00I F3-00-02-09-00 00- Fkisnckd Controls I Wolf! VtAiwN� Work Breskdovm Sbudtun (5 Nvsls bsbw xrork phess) I SF P is Goa 1 F3 001 F3 00 021 02 101 11 001 F3-00.02-10.00 00 F3-00-02.11-00 00 - Finarbtal Conde 00 - FNMfaid Controls I Job I General Ledger Account (Expendiluns Obpd, Revenue Source a SF MA 1 Prrooqq��0 CoaGnpp 1 G�AA)el Ledpdt Balsrx:a Sheet Account) Gicin I Ph —a Acbvlty 15 levels below Grant MetalI SF I CoatS+k( F3 001 021 141 001 F3-0602-14-00 00-1nancal lFirancial Controls F Its MA F3 00I 02 161 00 F3,0"2-15-00 00- Financial Controls I Fiscal Month MA General ledger F3 00I 02 18 OOI F3-00-02-16-00I 00- Financial Controls I Flue)Year MA General Ledger 13 00 02I 17 001 F3.00-02-17-00 00 - Finrrisl Controls Uasr-Debnad Field 1 MA Generel Ledger F3 00 02 18 00I F3-00.02-18-00 00, F—aid Controls User -Defined Field 2 MA General Ledger F3 00 02 111 001 1`3-00-02-19-00 1 00 - F-1111 Consols Ussr41e1med Field 3 MA Generei Ledger F3 00 03I 001 00 F3-00-03410,00 00 - Ri a dal Consols System edit. tran—lions to ensure that inch entry to a fund t. Isencad SF General Ledger I and oo plea, and ewh fund is maintained as a sand-belanrirg amity, during d 00 04 00 00 F3.00-04-00-00 00 - Financial Consols Syr�l1]b�ra�le{n�u aa�t bvel Usim ff by additional data SF General Ledger �F3 F3 00 051 001 00 F3-00-05400-00 00 - Fansn ad Consols �a jI.— rnd,d,, fS �NNBilt:g WdBaduuhi 6} i 11(nd aocouneng ayatem in SF General Ledger I oonMm:ly wt[h GAAP, GASS, and regulatory standards and guidelines. F3 00 08 00 00 1-3-00.06-00.00 1 00 - Financial Controls System simullaneousy supports multiple bases of accounting for the la fund �pyr� tludino but not limited to: I F3 00 061 011 001 F3-00-OB-01-00 1 00- Finandid Conbds I -AI�Ilkd aeeNlb 6asia SF I Geneml L2 I F3 00 08 02 00 F3-00-0 ,Ol) 00 - Flrww l Gonsoh Full Auld cads MA General Ledger F3 00 07 001 101 F3,C)"1 00,00 ..F .. W Consols System property a000nta for Imsr-fund transactions in accordance with SF Genarei Led," GAAP and maintaina the associated audit trail. Such transactions include bans. advents., intrainterfund transient, intrarintedund services provided and used transactions, and reimbunismient traractins. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 292 of 418 pl xiry of C min is PriorText I Change � .u. ,� .a�i'. .,, ., , ,i^,n, .. ,.s ID ,. „ ..,.r, Y .Y,f; ,, r.. (, „i=.,:v"';'x •'... HIGH Tiis tundionabty is not currently mn0l.bla and will need to be created using Ppp.{{�l{{))IluncponeTnds. HIGH ( �, is not it/ avagabla and win needtobe orseted using HIGH This ins is not I_Iy avaeabb dint will need to be r atsd using PeogleTcols HIGH This lum"onabty is not entry a-M. onto will need to be orested using HIGH peo�laTools, inns uric Idy is not oummily avallabe and will sod to be croatud using HIGH at PI linobonekty is not furrenlly iiva�labla dint will need to be crested usury Peo Tools. HIGH TAs ncbonebry is not q#renlly avedabe and will need to re created using PsooleTool., I I HIGH This f.n ruilnym not —Iy evadable end will need to be created using P_I.Tools. I I HIGH This lunctionelily is not I I currently availaols and .,It need to be created ..in Peeoo((ieTods. HIGH Tho luncbonesly is not wmenily avaiustm orb wd need to be oreeled using PeorlieToo.. HIGH This lundionalny is not currently availabe and will I need to be created using HIGH PeogleTdols TMs Iwicbo..kly Is not wr emly awaable end .11 neon to be .eat" using Peeqq(��I Tools, HIGH TmrnIonadly is not (wrmntly.",law and will need to be created using HIGH ly not WRendy aend.11 IP need to be t"iablg HIGH Gonerel Lodger supports the ability toecoommodew multiple bases of a uilln0; however, the. tranaactons are not all updated ii,nultanaoWy, I I I I i 1 I F x I I 1 I I I 1 i I II I i I I I i F3 01 00 00 F""8-00-00 00- Financial Controls F3 I 09 Od W F3-00-09-00-00 00 - Financial Controls F3 001 10 00 00 F3-00.10-00-00 00-�Finaan7cial/%C''omrrryds F3 001 10 02 00 FO-02-00 00- Finari.'ef Coma F3 F3-00-10-03-00 01- Firar�µr'�IJ�//��I(k�;I F3 (00�0001 IN11 717 1� F3-00-10-0500 DO - Fua'R 1 C6nOMa F3 (���! ���77 On F3-00.1F300-110-06-00 F3 001 10 lull 00 F3-00-10-08-00 Dl1-Fire Il.'bBVdIs F3 OOI 0000F�s�000F 1I 1 001 Y3OO o- 0-00 ta F3 °°I till 00 OOI F3,DI-11-00-00 00 - Finannd'al Controls F3 00 12 00 00 F3-00.1240-00 00 - Financial Controls F3 00 13 00 00 F3-00-13-00-00 00 - Faandal Conbds F3 W 14 00 00 F3-00-14-00-00 00 - Financial Controls F3 00 15 00 00 F3-00-15-00-00 00 - Flnandel Controls F3 01 021 001 OOI F3-01-02-0040 Ot -Journal Entries F3I Oil 031 001 OOI F3-01-03-00-00 01 - Journal Entries F3I Oil G4I 001 OOI F301-04-00-00 01-Journal Entries F3 Oil 051 00 OOI F3-01-05-00-00 01 -Journal Entries F3 01 06 00 00 F3-01-08-00-00 Ot - Journal Erodes F3 01 07 00 00 F3-01-07-00-00 01 - Journal Entries F3 Ot 08 00 00 F3-01-08-00-00 01-Journal Enka F3 01 09 0] 00 F3.0 -09-00-00 01 - Journal Entries F3I Oil 101 Doi 00 F3-01-10-00-W 01 - Joumel Entries I F3I Oil 111 OOI 00 F3-01-1 1-00-00 I 01 - Journal Enures iF3I Oil 121 001 00 F3-01.12.OD,00 I 01 - Jeuma Entries I F3I Oil 131 OOI 00 F3-01-13-00-00 ( 01 -Journal Entrees F3I Oil 141 DOI 00 F3-01-14-00-00I 01-Journal Enures F3I Oil 151 OOI 00 F3-01.15-00-00 i 01 - Journal Entries F31 Oil 1 151 ODI 00 F3-01-16-0aoo 1 0, - Journal Entnes F3I Ot 16 .1I 00—1-1 1) 01 - Jdumal Entries F3 01 IB .100 F301-16-02.00 01 - Journal Enter I F3 Oil 17 001 00 F3-01-17411OOg 1 01 - J.—I Entries F3 Oil 17I Oil OOIIF3-01-17-01-90I 01-Journal Entries F3 Oil 17I 021 OOI F3-01-17-02-00 I 01 - Journal Entries City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 293 of418 System provides ability to balance interfund receivable, payable. and 99�/tyyli���i�n transfer accounts wimin funds. 3yaUm provides trarrm Lion edits that permit. worm, or reject transactions based on user -defined allowable data daseirication structure combinations System has the ability to record and maintain the following financial balances suom al elements of the financial data classification structure: Ad/yl1N Annuall Buti0 tb�e IEudaet 9 Total avenue Pre-Enwmi,mmias Fnwmbrencee tmerhlnd Transactions Fund B.I.— 4B0Nhmkkddo0w�{n� of fund balance Into restncfed, committed, assigned, and Syst8M11 p/b . usaa me ability to select summery or deleted posting oftransactlons to the general ledger horn subsidiary ledgersaf—doles within ma sVatem. pSyysttee�m provides the ability tto(pvalhidaeythat �-main revenue types are Syslemate roll el least 18 ui�dE8ia61e accounting periods per year that can either be used M traneaceng against financial bounces, adjusting period. against financial balances, or adjusting perods that are for memo entries orgy and do not update financial balenrea, but aril be reflected in is m I �OO�� System pFovW. sub i fiM ledgers for baana sheet accounts ea needed. These subsidiaries must genera. reports of open tansactions duet l eceumuate t(l me pre\ ahead aCmdmntotes. System provides tlaCB summarized ban68pti011a on11M in the General Ledger back to dated spume do um-ts a other system modules or subsystems Xon the enterprise ayatem. It the Information must be retrieved from mess modules m or subsystems, it should be transparent to lS�i„>.-.1..'JoOrn►l;ErWkIBE',..,"t�^,,,�.a .3.'r✓'�.,, SSyytstkeni hRal tthheyys(0/i�bt�y w(u�Ierynlewnt�eyd9n8g a jo,Iu�myal entrsr b view of eMrn yS [ea m de)a/uyJH!s{(�Hrydid wdh�iq�S)�jdu7sN�nli�l (tilivfgH. P.O., .(—I year, cunenl date Systedefaum Ill. Ui41! totad38M1E81AUR a6G f6.�.�tbDst center. department) for a bcourltirtg distributions with the ability to override mesa defaults. System provides visibllity, Into the des isra s for alpha -numeric codes that It a at1m�1 en t. SyOostppeoormrltl(hla- ability to a ects to the aboniageeyyyatttryach or referwas multiple System has the ability to to print daocu(hbhts attached to journal entries . System ■iklvn uses to Input journal Mifles as a wi nmbon or adjustment tt) ppv/)Pg� accoun Sydfafff allows us79�al withes, from desktop appliati ins (eg., Microsoft Expel) and validate the entry against the financial data classification structure and allowed coding block combination.. System al_ dawn to designate whether imported tr.—Uora can perbally post or most all post togell r. System alows users to coned imported transactions on-line if they have enors. System provides eno rues with the ability to wetomize their view of the camel e Sys�ytejm ra mpat�tllc�a4 generates and assigns 1dlo�w{ mend control numbers for SystamaifloWkwdiN318 �SV!dbl far bacfioids�iAirtriaLlions (before posting), .kh audit trail. System provides ability to default o0semng entree from sub -ledger trmsemtlats (e.g., pMtacary to Paapyeabbi for vouches, reaaw for oneuSysts bnnpes ton baVch hlb duff .h S�ystle/ym�I�pt�r8oce�ss8egs{J10� OIB�.Wa {� �g ay without cbaing out other uses SSHIifH M Wdi ditllAA VAl MMuld editing for emor identivation and W before actus oo ino or/�' I (1 r� As ernwa are.naun erod i 'nd�al 17R6 the deer is ratlfied of all As ethos are encountered when posting an -Um document, the user m notified of ell enere System provides validation and adding on nndaddingoon tiallds transactions for enor aleN.4ylneriMARl an�nia., Q� enors. As error are encountered when posting an sore dcament, the user is wilif d of all enors SF General Ledger, Recawables, Parables SF General Ledger General Ledger supports comolreld" ads to spenly a llowabb wmbinaoons of the +late 'Lea.dmration etrUmture. SF General Laedd�/1of I SF General Leda SF General LeAA of SF Genera! Le SF General L er SF General SF �r General SF General er SF General L er RG I Gan erattL g HIGH SF General Ledger 1 SF General Ledger, Billing, Receivables I SF General Ledger RG General Ledger HIGH SF General Ledger I ' IF I Garland Ledger SF I Geared Ledger i i MI I General Ledger MEDIUM I SF I General Ledger MI I General Ledger HIGH MI General Ledger HIGH SF Genera Ledger SF I General Ledger SF General Ledger Complel. joumas must be poslad. If an upload Idle contains multiple —plea journals, some can post while ma wrored JV — rejec!ed. SF General Ledger This depends on the se mlyd me anon. Trim-1 ale that do not contain the proper dam to upped 9ucoesstdly will need to be torrectetl et the originating file. SF General Ledger SF General Ledger SF General Ledger System allows user to ..noel or back -out transactions, vill audit _ ,bail. ciadficafion SF General Ledger SF General Ledger SF General Ledger I _ SF General Ledger i i SF General Ledger ! SF I General Ledger i F3 01 18 00 W F3-0t-18.00-00 01 - Jourtwl Entries System provides users with the ability to print a copy of approved journal SF General Ledger enthas that include both manually entered lira dams as well as all system fry�nerated One dams. FS Ot 1g OU OUF3.Ot-1g-00-00 01 - Journal Entries System allows creation of a journal entry with reference to a previously SF General Ledger Using the doscripuon holds. entaretl ��oouumal. F3 07 20 W 00 F3-01-20-00-00 01 - Journal Entes System 6tiows users to reverse a journal entry by referencing the original SF General Ledger document and indicatinf� that f should be reversed. F3 01 21 DO OU F3-01-21-00.00 01 - Journal Entries System allows journals W Ins flagged b miens cheuser-"paused date. SF General Ledger F3 07 22 W W F3.01.2&00.00 Ot - JonrtW Entries provides loomed entry ffyoobwtes m a Me item description area to SF General Ledger F3 01 23 W W F" -2300-00 01 - Journal Entries (S/yyssWn Ms an IM Joumet entry b be configured as either MI General Ledger HIGH FS 01 24 W 00 F301-2".00 01 - Journal Entries ryS'I�ga�pWendaAoowoa�Ion1� Sj�llam provides Ilry to create and prose. transactions against SF General Ledger !I ab6aticel eocounb lo addition b financial acmunta. F3 07 25 W W F301-2500-00 01 - Journal Entries S�ysy�taedm provides for userstosaavvee Journalllrre0ntriies Oat have rot yet been SF Geneal Ledger F3 01 26 W 00 F3-01-26-00-00 01 - Journal Entries S�r{tem provkas Z d6811y fo llEQM6U8pRI Et lAeasure (HWrs, FTE, Los, SF I Geneal Ledger that amounts in Ithe tainse ine of e Syslam labw F3 01 21 W W F3-07-21-00-00 01 - Jounal Entries provides Me ability to entryy a Tram multiple sauces SF General Ledger f�o�M�i�neLL bbMe1cd�y. terrace FS 07 28 W 00 F3-01-28-00-00 01-JWrrW Entries S= ahouWnaaowfor use of templates for transacOom that use a SF General Ledger I common coding block but differing baraectrdn amounts (e.g., distribute a ((�t0q8U{{�r enrlolm� 1 F3 01 29 W W F3-01-29-00-00 Of - Jonnul Entries System poovai W enterpumal entries for multiple departments SF General Ledger �Mdy FS O7 30 W W F3-01J0-00-00 Of - Jounai Entries S Tit u an aril Y b reference a prevaua y MA General Ledger HIGH This funcbonakI Is not astsblNae MGmrtlbrartra. Adam the tremLLaC40n a posted. it. nf—npd currently available atxl will ancumbronce document should automatically liquidate. need to he U"m.d using PeoobToots. F3 01 31 W W F3-01-31-00.00 Ot - Journal Entries System supports establishment of rubs foreach journal type, which I sinn. including. but riot limited to FS 01 31 01 W F3-01 77-0t-00 01 - Journal Enures iu�EfI1n51 iddl�" MA General Ledger HIGH Thai Airy Is not cumenily avalable ono will oum ntly need to be created using Peok leTons F3 01 31 01 OQ FMI41-02-00 Of - Journal Entries transaction level coding requirement MA General Ledger HIGH This �uncdoality is not cummly..liable and will I need to be created using PeooleTrois. F3 07 3:1 W OU F3-01-32-0D•00 01 • Journal Entries System supports Oa use of a Treasury Fu d for Pooled Cash and Investments Out: F3 Ot 31 01 W F3-01-32-01-00 01 - Journal Entries Captures bank account activity (cocks written, deposits made, SF General Ledger, Cash imesNaras' etc.1 n a sil�ple 1urM (Our Thm Fund Manrt0.ement Zger, F3 Ot 31 02 W F3-01-32-02-00 01-Journal Entries BaWlces triraa�c(5�o'pns�Ib�eMeen Ihb primary TiaWtreasurytroll SF General Cash Pooled janti In F3 01 31 03 00 F3.0 .32-03-00 01 - Journal Entries plllfl6fj/ iry posgion Ua Pooled Cashand SF GenealnL&Iper Cash Invest. —Is Mane meth M B f . �~ = • .• • v 1 . •, ,,.I .. ,,. ". !, „,,, a ; '', , ., . - .: _<,- , . .. , , ,,,,.; . F3 0 OT 00 O0sF3-02-01-W-W 02 - Month Ertl Close ability moo. Investment ystema SF li al anagemen De . F3 ill 02 00 06 F3-02-02-00-00 02 - Month End Close hf aid yjpn J�6� �'(N� S'"�• bl pity b �ill(efeslumenidgs ys m provide" tie a e beck to ISystem per0cipaOrq heMe anti prq)ecb Da"etl o Oe LXbwag rMit)dologlas: p—.das the ability to allocate interest earnings back to parbcrpabng funds based on 1Ihe following methodoiNies: substantive F3 02 02 01 W F3-02-02-01-00 02 - Month End Close Avers" dafy cash balance for a period SF I General Ledger, Cash Mans�11Q� nl F3 02 02 02 Od F3.02-02-02-00 02 - Month End Close Endlofl Caen balance for prom period SF General Ldd�er, Cash — _- - - -- - - - - I Man gyp F3 02 02 nJ W IF .02-03-00 D2 - Month End Close Ending cash balance for currant period. SF -nt I General LBtlg.1. Cash Mana,(7,emend ! F3 02 OS W 00 F3-02-03-00-00 02 • Month End Close System provides the ability a allocate bane fund based on another funds SF General Ledger cash balance (route lots set allocated from Capital Project Fonds to Debt Service Fund11 FS 02 04 00 0 0U F3-02-04-OG 0000 02 -Month End Close abi or throughGeneral batch syysttem has 6k il tochimeenter journal transactions chime SF I Letlfler FS 02 05 W W F3-02-05-00-00 02 • Month EM Close byflbm provides the ability b agora a interest earned at van ous owls of the data classification structure. includko but not kmited to:. FS 02 05. 07 W F3-02-05-01-00 02 - Month End Close Fund SF I General L F3 02 OS 0'1 W F3-02-05-02-00 02 • Moth End Close p/DjCg} SF Tw 1 Gaineat L F3 F3 02 0� 05 Oa W Dd W F3-02.05-0b-00 W F3-02-05-M-00 02 - Month End Close 02 •MOM End Ckxe 11HM J]r� ��t SF SF General L General LEE I F3 02 OB W W F3-02-OB-W-0O 02 - Moth EM Ckaa Syd— povbes IM ability to afocate inlerest wtad on funds auoss sebcbd find belatcea, with 6a abrty to Iwo (or con adar) the fimnctions: F3 02 06 01 W F3-02-06-01-00 02 - Month End Close NMs arWor scmulb which have the authomy to aminters"' SF General Ledger FJ 01 06 02 06 F3.02.0602.00 02 - Moth End Close Allocate based on De mart ods listed above, to any I" of Me data SF General Ledger ca"alMation struck- F3 d2 06 03 W F3-02-O6-03-00 02 - Month End Close Aubmaaraay saes a comaponifinp journal entry rerAN from 6a SF General Ledger albcetlon gAcess. F3 0/ 07 0U W F3-02-07-00-00 02 - Moth End Close -y=prou- acausl journals. which can (optionally) automatically SF General Ledger F3 02 06 W W F3-02-06-00-00 02 - Month End Close jj��Q�yy s a user�(I(�(���gl�date In the M ien fee System autdT�gCOgk�V4R111 ofysponerd�fiwrse SF General Ledger F3 O2 W W Olt F3-02-08-OO-00 02 - Month End Close a�i�I �^ SF General Ledger FJ 02 1d OQ W F3-02-10-00-00 02 • Month End Close Hlhle�oliotls a6 isd Wore ea lobwing 1 F1 02 10 Ot W F3-02-10-01-00 02 - Month End Close Parodic month ./� ,Of1y1 SF General L sr I I FS 01 10 01 Od F3-02-tO-02,�(� 02 - Month End Close FWd ts fcll rf��dbA SF General Le er F3 02 10 03 W F3-02-1 02 02 - Month End Close artoun each period, based on filed Percent SF Gone I err Allocations can be used to su000n tba nary+ FS 0'1 tit 04 Off F3-02-111-04-00 02 - Moth End Close Different amounts each period. based on variable percent recorded to SF General Ledger us'`dt Albca�culs can be used to account (such as phone bills distributed across departments support in,, requrement. ��W yAtistics! F3 01 11 Off 00 F3-02-11-00.00 02 - Month End Close SV&A flDYdlss tasks required for month end close SF Enterprise Portal City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 294 of 418 I # I ► 1 i 1 � I 1 `, i # 1 1 � � i i I F3 02 14 Ofl 00 F3-02-14-00-00 F3 02 15 00 W F3-02-15-00-00 IF3 02 16 00 00 F3-02-18.00.00 F3 021 17 00 00 1`3-02-17-00-00 F3 021 18 00 00 F3-02-15-00-00 F3 02 19 00 W F3-02-19-0D-00 t I 1 1 i 6 r 4 y • Month End Close ge�l}te" backs aUhhn r1f �prOMetion jr�r en/�r1�� l SF Entemnse Portal J2 • Month End Close Itif System provides ti1e abllay b suppdrt wo7k11Lw dIJLB$ee 1« rewiring MI General Ladger transactions. 02 - Month End Close System provides the ability to validate all fields in rewmng transaction SF General Ledger {ry't1�Qa. End Close System provides the ability notify users that recurring transactions ability to0'1-Month actions are M General Ledger about-``�� nerete. 02 - Month End Close S=nn ptOvde the ability - Identify reverting oansaction via an rid -aloe SF General Ledger on the transaction. 02 - Month End Class System provides the ability to have multiple open periods within ech sub• SF General Ledger I rsub-module. es wen ea the nyngryrel r 07 • Month End Close S em prevents transactions from posting a period in either the SF General Ledger nenpal iMlaer a rtp `u0-ladnar. 02 -Month End Close Sate elVowa user- i 2efine closing penotls and the period closing dales. 1 SF General Ledger F3 02 20 00 sreorpyeaAjllhp�Irf3 `F3 02 21 00 W I F302-21-00-00 I 02 - Month End Cities will a�ll(1ojwjjs Lbspit(d"PI- i�o7dgnlfLoyr�i5ra[n�aaecrN�o�n� F3 02 22 00 23-00-00 2 - Month End Close y�Olyy�js�jj�(�1J�M. pprroocfe�}spsrinng. ��fnQ IlbUbflllBtecEh181a F3 02 23 00 ODI F3-02- 02 . Month End Glee S1r5[9M 81f 818><pelM1di101d fi1Vd /epuiPbd for F 03 01 00 00 F3-D301-011-00 W -interdepartmental Billing System m provides ato aaaN(/etf1Cn�ketc�/ndE(�ra9-6�epaa mBs from detailed at mfomfion, F3I 031 021 00 001 F3-03-02M.00 I 03 - Interdepartmental Billing Me abilitymate an inteK trraa-Department I pS�ysryl�errm�rProvviidje�s to F3I 031 031 00 OOI F3-03-03-00-00 I 03 - Interdepartmental Billing prb�iNeirdie aBgiild�ytpo orreate ent,ntem�Iell voyr�rwvh�(er that charges gSq'y�(styl�eAlr�i F3I 03 14I 00 001 F3-03-04-00.00 03 - Inlerdepartmenal Billing SryslemeSprovitles IheraWlNy Io lianem mrtern Ira-UapaiUn"r,llirpa with line -Nam detailed charges for review prior to po sing, F3I 03 05 00 DOI F3-03-05-W-00 03. ImardePanmenlal BIPing System snorts for automatic posting a ImeNintm-Department billings after a user specified Penod of time has etapsed with no response. F3 03 16 WI 011F3-03-06-00-00 03-InteMePadmenlal BlNlrg SYstsm Me abill for the Department ng charges to iiiiherst am fund :NtabtNosh nbnp Nemms mcicchar changingnd at t F3 03 07 00 001 F3-03-07-00-00 03 - Interdepartmental Bil �aratst�delrl �alI.isms)tthatw)r1Yelge,�Parninis or System yrrSviBAd IK6 abifdy fo .end a user -specified naafiwtion (e.g., arl back to (he original d ate nledsparimenMnterfund n-es are rejected a specifiedfi(r�p�errioda of time WPses, ecsdirg communication Of th correct 03 181 OOI 00 F3-03-08-00-00 W - Interdepartmental Biking �loNdbii (Eta abifQy to restrict intef-department postings based upon I13 I aecuny, to euth—d users within de,.mnant5 (e.g., fi.ral coordinators). F3I 011 0111 00 - F3-03-Oil-00-00 03 - Inbrdapartmental BiNirg System provides ate ability to flag an inter-depaNmnt entry 7n dispute' I I and allow, userEefned Workflow rules to resol dispute. IF3I 011 101 00 W F3-03.10-00-00 I 03 - Inerdepartmental Still System provides the ability to setae irdardepanmem Invoices to cash. F3I 011 111 W 00 F3-03 11-00-00 03 - IMa tlepart renal BiNinp System provides the ay to establish accounting strings associated with I nerdepannen 1 transalctions tomin ma. keying of the seller arcwnt Ikon on each nl. .. .: ytI F3 04 01 00 00 1`3-04-01-01)-k) W -Cost Allocation System o a information Neat k yal.m provides thaci ro maintain gel consistent and recorttllehle with related general ledger BM budget al ledger dbudgt accounts. F3I al 021 OOI OOI F3-04-02-00-00I O4-Cost Allocation System provides abilityto/allocate costs all filnarriial data I F3I 04I 03I 001 OOI F3-04-03-00-00 I W - Cel Allocation then etto Ve mop ovde�rkhe abilty rb su co rk fullthlwssV n r aFtt ityary�� ri PPo 9 Mon a Programs +�pd services. F3I 041 041 W 001 F3.O4-04-00-00 I N - Cost Allocation System provides allocation processing to distribute all costs that cannot be di sstiqq ad to . direct coat oW..t. F3I (14I 051 00 W I F3-04-05-00-00 04- Cost Allocation m Pmvtdas the ability- have a multiple step cost allocation process. F3 041 061 00 DOI F3-04-OS-00-00 04 - Cost Allowbon System provides the ability - support an unlimhed number of bad percentage albcepe., se that allocalions can be Performed In one step. F3 04 071 001 001 F3L4-074)0-00 I 04 - Coll AlbcaIs System provide the ability to support consistent field lengths of �arcentaaes .toned on r yy F3 04 08 W 00 F3.04-06.00-00 04 - Cost Allocation System provides the obi (o rapture and calculate cost allocation factor I inormation aM.utistica that YI woad the accounting end allocation of indeed and direct aab to activities through the use of met pools. F3 04 "1 00 001 F3-04.OB-00-00 04 - Coal Allocation System provides the ability to allow users to import allocation pool or I Infefarrnap5on from .Pnadsheeb or other desktop bole as a Ns1ttaatissticafll F3 04 101 W WO4 I F3..10-0D-00 I 04 - Cost Allocation S�'�yl1ly'7m��f8�v�i�dyeon adJ�t}�1w(�m.inOf and posting allocaow tourral fill 141 111 00 WI F3-0M11.... O4-Cost Allocerbn yf-I�6.R(i�g� S',Jtt6M p164fdbt A48 51fN1rfolddlPWy user-mainWned effective-dend system tables for cost allocation methods that provide edit checks and 04 72 W W F3-Otto12.OP00 04 -Cost Allocation SAya1Finaookas t*3 einsuppon muaiple cast efloweon methods within a Department City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 295 of 418 I MEDIUM � � I LOW I I SF I General Lar�per SF I General Ledger SF I General Laaod//��00(f SF I General ledge; ww SF GeneralLetlg e &tiling Proied Cosb- Contracts SF I Purchasing I SF Payables MI Genera; Ledger, Sitting, MEDIUM Project Costing, Contracts, Pavables MI General Ledger, Billting, MEDIUM Project Costing, Contracts, ..inbles MI General Ledger, BNlling, HIGH Project Costirg, Contracts, Payable. MI General Ledger, Bdlfing, MEDIUM Project Costing, Contracts. Payables MI Cenerel Ledger, Billting, MEDIUM Project 0.:%, Cantncts, I Mae PaKg MI General Ledger, Billing, MEDIUM Project Costing. Contracts. P�v bias SF General Ledger, Billting, Project Costing, Contracts, Par{dbles SF General Ledger, BNlling, Project Costing, Contracts, SF General Ledger SF General Ledger, Project Costing SF General Lodger SF General Ledger SF Genera; Ledger SF General Ledger SF General Ledger SF General Ledger SF General Ledger SF General Ledger SF General Ledger General Ledger provides oral ability to specJN the ciosmg periods; uwery ho, tharo am not any y,enmed closing dates I ff"k; r47i- •x*'�.g':�:;, 4, r'xa;, °�....:,� iP• tot.-� .tt_:„r.F^7 �I I+ I System Provides the ability for Cost allocation processes to be configured by department and supports mull configurations within an Department to address varying cost allocation needs (e.g., using various .Vocal methods. cost bases. etc.). clarification 04 13 W W F3-04-1300-00 04 - Coal Alteration System provides the ability to create and store a'soapshot' of the inputs SF General Ledger General Ledger supports (F3 and results of each allocation process. The relengcn period for these alloabon log reports and sropshoh can be determined on a user -definable basis. journal reports to show allocation ai W't F3 04 14 W 00 F3-04-14-00-00 a - cost Allocation System provides a simulation module to determine impact of process MA General Ledger HIGH An add itional application, changes upon cost adoration activities. Aclivlly-Based Management, is variable and supports this functionality. However, it is not proposed due to limited redsrementa. F3 04 15 W ' W F3-04-15-00-00 04 - Cost AN-11- System provides the ability to input different cost -driver rates in the cost MA General Ledger HIGH An additional application. allocation simulation module, allowing different rates to be applied over Activity -Based Management, is different I= perods. available and supports this functionality. However, it is not Proposed due to limited mouirements. F3 04 18 W W F3-04-18-00-00 04 - Cost Allocation System provides the ability for users to determine the definition of the cost SF General Ledger I /rom which Ins cwts en allocated. F3 D4 17 W 00 F3-04-17.00.00 04 • Cost Allocation the ability for users to daternim which costs to allocate, SF General Ledger Allocations are e,allied using including Am time period In which those costs occnnd (e.g. effective start Timespans, automated time and and dates). penods defined mthnn the abpliabrn. F3 04 18 W W F34WIS-00-M 04 - Cost Allocation System provides the ability to allocate =is based on sillier cost afiocaton SF General Ledger lactom (e.g. statistics, percentages, number) suppled by the users or System provides the ability to based on acbW espeeditiaes at the level of detail defined by me user. allocate costs based on either cost allocation factors (a g. MaWtcs, peroentagas. number) auppined by the users or direct expenditures at the level of detail defined by the user minor I F3 04 19 W W F"4-19-004i0 04 - Cost Allocation System provides the ability to maintain multiple, effective -dated alliation SF General Ledger F3 04 20 W W F3-04-20-00-00 04 - Cat Allocation alliomes. System aplutynissstatistical bases of allocatioto as focal period (e.g., SF General Lodger rn I Wprorv�itd�fi � F3 04 21 W W F3-04-21-00-00 04 - Cat A oratim SSmystem ansutee�.1tthe tb1i1 M allocated amounts SF General Ledger F3 04 2° W W F3-04-22.00-Oil 04 - Cost Allocation f6px�aa�OJi�rytyo� Syatam provides the aid/lily to prwenl double aloaaon of costs. SF General Ledger System provides the ability to prevent double allocation of costs related to protects and grants "'Min a cost pool by allowing users to specify it ct or grant s Project be the same mrouohout the allpcabdn.. clarification IF3 04 23 W W F344-23-00•01D D4 - Cal Aloation System provides Me ability to allow, users to specify the hpuency that cost SF General Ledger I F3 04 24 00 W F3-04-24-00-0g 04 - Cost Alloaficin to Indicate whether cost allocations an SF Genanl Ledger or 1a1 exoenatturo transactions. I F3 04 25 W W F3-04-25-0t1-00 04 - Cat Aloabon o mares er t Ivry bcatioro. SF General Dash F3 04 2� W W F3414.28-00-00 04 - Cost Allocation supop.,for allocabm (e.g., SF General LAdpar F3 04 27 W 00 F3414-27-00-00 04 - Cost ANocaton fmulc5pl teadq�rWhods r�dryw� Syalerd provides (h1 abilty iM routs slilis4Ls al naAtlple steps in the SF General Ledger I abcetim ate F3 04 28 OG W F3-04.28.00.00 04 •Cost Abaum System WeeM that provide oWs for perantpes SF General Ledger allocated. F3 04 29 W W F34W29-00-00 04 • Cost Allocation System provides to abAdy to uss to an unlimited mentor of cat pods, SF General Ledger allocation and Aned at objectives (i.e.. dfstrldNmro tis) in the cost pbases, np76Vldei F3 04 30 W W F3-04-30.00-00 04 - Cost Aloutm SysdeUm the ability to abate cats bawd on preliminary or SF Geroral Ledger estimated rates. F3 01 31 W W F3-04.3140-00 0/ • Cost ANmation System provides liar aDNfly 10reverse prior bro ansactiobored on SF General Ledger estlmwted rates arc neefiocate bawd on actual rate- at lie and of Ins yesr. F3 D4 32 W 00 F3-04-32-00-00 04 - Cost Allocation System provides tie ability to abate, based on uwr-defined criteria, a SF General Ledger difference belwsen selected finarwAs! dale casaficabn structures values (e.g.. revenue and ehperse accounts) leaving the corresponding revenue aoa win F3 D4 33 Oft O W F3-04-33-00-00 04 - Cost Allocation Bytl ability o abate costs among an unilmited number of SF General Ledger funds F3 04 34 W W F3.04-34-0600 04 - Cat Allocation System provides fha ability to prevent changes to supporting all —bon MA General Ledger HIGH This functionality n not records once me asorat on process starts. —fly ..liableand will need to bedveeled using �` �oaddAional F3 04 35 W W F3-01-35-00-00 a -Cal Allocation System provides Ate ability to compute and caw systenryfarhxated ntw, MA General Ledger HIGH appba"', tampers and report peg arLsls tosterMerd elkhcatlms, oonqute the -Based Management, is varianceand, o calculate new allocation rates for userapecirwries d catego (Activity available and supports this and clime. functionality. However, it is notproposed due to limit reZiniments. F3 D/ 38 W W F3444640-00 04 - Cost Mocation System provides statistical backing apab libes for Ow purpose of SF General Ledger, Project detain, feu cmaJpry; F3 04 3'7 00 W F3-0437-00-W 04 • Coat Abortion System I as direr expense or fntlnecl MA General %. HIGH additional application, eipensi. Activity -Based Management, is available and supports this �An functionality. However, it is not proposed due to limited muiremerila. F3 04 38 W W F3-0438.0O-00 04-Cost Ababa" Delete SF General Ledger System provides multiple standard cost allocation reports. _ aalate F3 04 39 Oft W F34W39-00-00 04 • Cal Allocation System provides the ability to maintain the identity for the source of costs MA General Ledger HIGH M additional applicahon, and the ability to drill dam to the source of cosh In an alkrstion. Activity -Based Management, is available and supports this System provides the ability to [n., functionality. However, it is not maintain the identity for the proposed due to limited source of costs and the ability to t drill down tom sour"of costs n ^?'.I.iinl nw"�Y,tfF.:JMY X..a+&:^a.. ,... �f...dn.�;s,✓. �;ia".yLeYCOBWIb:,MAiY.lUt/ftYD _ M:ya,;.:;'.ydf��t'a,vda-.'i.. ,; ..r„' rrv„e.- City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 296 of 418 f I 1 0 1 1 1 1 I I 1 1 1 1 1 1 1 1 J t J 111 1 1 4 I I i I 1 a 1 f 1 I 13 0 O1 ODI 00 13-05-01-00-00 OS - Job Costing and Reimbursement System provide. the ability to classify jobs as reimbursable or non. SF Project Costing reimbursable. I F3 05 02 a6J 00 F3-05-02-00-00 05 - Job Costing and Reimbursement provides theability to capture direct exPmW to a job Ituough SF Project Costing, Payables (Syyysteem F3 OS 03 00 OU F3-05-03-00-00 05 - Job Coming and Reimbursement SI/EIlM11 pIOWM Mb ability Id fMporUexpon charges for labor W a job. SF Project Costing. Time 6 Labor FJ 051 04 00 00 F34)5-04-00-00 05 - Job Costing ..it Rmnixesement System provides the ability to define jobs by atlrawtes• including but nit limited to the fo lD.ino: I F3 IF3 051 01 00 F3.05-04.01-00 05 - Job a d "mbureemem I Descripp 1 S Pro'�,�'1 Costing I I 3 (),51 51 01 03 (((C'''oa��jll 00 F3.05.04-02-00 OS -trio /yA(IM1e end �elmDunsemenl Locatid5� 00 FMI-04-03-00 05, Job lll:::iititisssiii a arse eimDursemem I Berlm Date SF SF Pr.1Z Caatyw Protect Cc= I I F3 F3 051 OS 04 05 00 F3-05-04-04 05 - Job Costing end Zrinbursemem I E/ld Date 00 F3-05-04-05-00 05 - Job Coaling and Reimbursement Default elements of the financial data classbcaton structures for costing SF SF _ Project GosUTry� Project ColOreg ' I SpeedCharts can be used to Purposes. default eccounling mformaWn related m Projws F3I 051 .1 06 00 F3-050446-00 05 • Job Costing and Reimbursement Billing Information SF Project Coaling. Contracts, I F3 F3 051 011 041 G4I 07 08 00 F3-05-04-07-00 05 -Job Can nit Reimiwnemant r� y�ry'pp 1j�p(nl °°I �3-05.04-06-00 OS •Job Caa rid Reimbursement !.1 'Wr1SuM Ubt(f! AMbuM 16f �08 I MI SF P ) Cr/8 Contracts 4z I:dgi(b�tpl_�, General I f I I I F3 051 041 091 gel F3-05-04-0g-00 105 - Job Costing and Reimbursement elements of the financial data dassficatiwl structures fdr billing I SF Project! l:asang I I 1i F3 I F3 051 051 j�) IjpJ 101 111 pDeffoaru�lltt OOI F3-05.04-10-00105-job (rt�y/g�}}}1N�1 rye I aid Actual yield Won, Data 1 001 F3-054WIl-00 1 05-Job ynrl pl�ern Aeluel Field Work Corry,+] Date I SF SF Project Cosryw I protect Cos(ino I I F3 051 t21 1d 001 F3-05-04-12-00 l:dil OS -Job I:ISit 8Aa mbuneman! MutS User-tlefined fr�lds SF Probed Costing F3 051 OSp 1 �I I if to or(� ry n hq�amhicel structure. 001 F3.05-05-00-00 OS - Joh Coe d �{/J bursein jy(art1 or)jWd�g gqr �"fa of F Pr�acl Costiry� %a. I F3 OSI O6 00I F3-05-0S-00-00 I OS •Job Coup end Re,�mbusemen Sysla h P by fdi I ass gn a a ob to a fixed asset. Projad CosSng• Maryry?7 F3 05I 07 OOI OOI F3-05-07-00-00 05 - Job Coaling and Reimbursement System provides the ability to bill accumulated cost iniomnetion m a SF meet Project Cda' Contracts, I I F3 051 08 001 ,customer. OOI F3-05-08-00-00 05 - Job Coating aid Raimbuwmant System provides the ability m bill accumulated cost information m another SF Billi�p'� Project Costin¢, Contracts, F3 051 OgI 00 de nt °°I F3-05-0g-00-00 OS - Job Cos end Reimbusemem Syl19M �rovitles the ability to group jobs Iw billing purposes. BF Bnli�y`� Project Costing, tantracls, Billy' F3 051 101 001 OOI F3-0540-00-00 05 - Job Costing and Reimbursement System allows the allocation of overhead coats to a job. SF Project Cosbn9. General Legge F3 OS t t I °°I F r.11-00-00 05 - Job Cosun and bil' m lcuiem OOI 3-0 9 Re mbusement Sysem provides he a dy a and post memo costing env ec to I SIF 6 I Prgea Cos n9 General I F3 06 _ Oil w.00 .,,. . ; ... be. ... {{'' _ 00 F3-0601.00.00 O6-Petry Cash system prowdse lid Abil to mainlairflh Ml, diitivl dl pally cash SF trayy ...h��..'..Lav,�4itrs48 CasiManagemem, Expenses -- .�.rk t I F3 O6 02 00 tub �(]�=I� 00 F3-05-02-00-00 OS - Petty Cash �n p ov des V e 86 7y la support the regncsieeo Of fla pety cash I SF Cash Management IF3 D6I 03� 001 OOI F3-0603-00-00 I 06 - Petty Cash �Sysle�mPOuppona the detailed collection of expenditures reimbursed from I SF Cash Management, Expenses I I I I I F3I 061 041 001 OOI F3-06-04-00.00 I 06 - Perry Cash (' s mnaHL�orta the ed..h—.t of awnned images to party, cash SF Expenses I I I I IF3I OBI 05I °°I F� OOI F306.05-00-00 O6 - Peny GeN ISyalem =daa the abilityy to reimburse the petty ,ash accounts, via online SF Cash Management, Expenses IF3I 06 06 00 001 F3-06-O6-00-00 06 - Petty Cash (System supports the establishment of change funds. SF Cash Management. Expenses es�'Y7 k ._ w„.y ,{f. {W�harM F3 0 01 00 15%, b hlyW �J 1 OD F3-07-01-004M1 07 - Fmendal prow sea t, tra 464�d tra secbana m Gene I RG General Letlger MEDIUM Ledger reports bad, to detail source documents m other system modules. F3 07 02 170 00 F3-07-02-00-00 07 - Financial RepMs System provides access m Imancial transactions for any years that have SF Generel Ledger not been archived. F3I 071 031 OOI OOI F3-07403-00-00 07 - Finandal Reports System ties the ability to summarize individual tine -rem accounts into SF General Ledger meaningful groups of accounts for use in finandel reporting, based on user - defined I IF3 I 07 I 04 I 00 I omen. 00 F3.07-04-00-00 07 - Finandal Reports System can produce ad4wc reports using any field in Me financial data °° gaedger I I SF General L I I I F3 07 05 00 11lagppifi�f/+pisct� 00 F3-07-05-00-00 07 - Finandal Reports Syete (el n a h'wmry al all Generel Ledger transactions and SF General Ledger produces detailed transaction reports m provide an apprut nats!Wit trail. F3 071 061 OOI OOI F3-07-06-00-00 07 - Finandal Reports BByA�ups�a0rt6.1Jned,{�detail."am provides aapvial balenca by fund, for any SF General Ledger I ! F3 07 07 00 00 F3-07-07-00-00 07 - Finandal Reports Sy�66M 618ViA 1JS894 U PldEil! (a.g„ Comprehensive An 1 General Ledger Financial Report) and provides the ability m prepare adjusting enures m :System provides GASS 34 account balms'! o(indmdtul GAAP funds and to accumulate, reclassify ';financial reports (e.g.. end prepare adjuatrng entrees to account balances of government -wide (Comprehensive Annual activities. The financial statements should be run across as fund types and 'Financial Report) and provides by gw-Kc fund. The financial statements h the CAFR include the 'the ability m prepare adjusting frWowing: entries to account beof individual GAAP funds and to mulam, reclassify and prepare adjusting !nines toaccount batces of g—nint.nt- !-de The main acbvidea. !statements should be run across all fund types and by specific :fund. The main statements In the ICAFR include the following: minor I F3I Q7 ��jj ��y, 00 11 FF �y7 77 00 F3-07r-0&00 I df - FI f" L StatementSMM�h,li;Governmental (� ^�/o� LOW F3I )) UU 00 00 F3-0/-iWHI 07 • abr}s Funds; Reconclimtion of the RO General Letlperr HIGH Governments] Funds Beanie, Sheet to the Statement of Net Assets, I I F3 07 11 00 00 F3-07-11-00-00 07. FinMaal Respite Statement of Revenues. Expenditures, and Changes in Fund Selancee- RD General Ledger HIGH I Governmental Funds; Recondliabon of the Change in Fund Balances of I the Governmental Fund. to the Statement of ActiMiea; i F3I F3I 071 O7I 12 13 00 00 00 F3-07-12-06-00 I 0JJ - pFinencial (��ry/y statement of Net Assets-P((y�/j(�G�' F� 1: °°I F3-07-13-00-00 I U7 - Fklandel Hi'VeFfs Stalemem of Revenues, 6igdfli2i, aanges in Fund Net Asaem- I RG RG I Ganarat (p5r Caneral �ENQbr NIGH HIGH - --- %/7(I��t�Jy Funds: I _ F31 071 141 001 001 F3-07-14-00-00 1 07 - Financial Regpib 5(iUmelft of Cash Flows-Proonemry Funds: /ln-0irect MCNpdI 1 RG General Leticer HIGH City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 297 of 418 F3 07 15 W W F3-07-15-00-00 F3 07 16 00 W F3-07-16-00-00 F3 0'U 17 W W F3-07-17-00-00 F3 07 18 W W F3-07-18-00-00 F3 07 19 W W F3-07-1940-W F3 07 20 W W F3-07-20-00-00 F3 07 21 W W F307-21-00-00 F3 07 22 W W F3-07-22-00-00 F� 07 Fy 07 2 i W W W F3-01-23-00-00 W F3-07-24-W-00 3 077 25 W 00 F3-07-25-00.00 07 I Fi W Qi %� F3A7-28-0 11-1.} 07 2y W W F3-07-29-DD-00 IF5 07 30 W 0l1 F3-07J000-00 I F3 07 31 W Oft F3-07.31-00.00 IF3 07 32 W W F307-32-0D-00 F3 07 33 00 W F307-33-00-00 F3 07 34 W W F3-07.34-00-00 F3 07 35 W W F3-07-35-00-00 1 F9 07 39 06 W F3-07a8.00-00 I 07 3 IF3 OR I}j W W FMBJJ2-00-00 08- F3 08 117 00 W F3-0e-03-MW 08 - City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 298 of 418 07 - Financal s Statement of Fiduciary Net Assets: 07 - Finerrrlal 07 - Finarcial Statement of sin Fidsw Nat Assets St anent of (.rim hent UnI Nel Assets 07 •Financial 07 -Financial HHH Statement of Cl enges in Co , m Unit Net Assets System proaents finenllal auterri n a modified accrual and aoaual basis. 07 - Financial Reports System has the ability to show different organ tonal structures on a single report displaying accurate prior and current year data. Within the report. • unit eti np under one division in the prior year may be reflected 07 •Financial Reports under a new dWhion or mqyy not exist in the current yy44pp System provides fund transter reports. wch as interl3ntra-fund receivables. Mte7mtra-fund payables, and Inte�ntra-fund tremfers, that display month and -tdete yeao-transfer InformaWn inrludirg both the sender and receiver of the m n far. 07 - Financial Reports System provides the ability to produce the following finerldal reports, Including mull -year comparisons, based upon user-0efined criteria (e.g., tre—ticn date ranges to produce monthly, ouarleriy, and yeady reports) 07 - Financial 07. Finanrlel tar %I )Igp) �p110, fund MX, and tend troop'. I ��I k��a �A C h Flow 07-Financal Fund Salance Report 07 •panUel IF Balance Shoe( 07-unandal Incane Statement 07 - Ffipp��++��flII 07 - F3%ainSLl 07 - F.—I Cash Be"— Re.- Montl�y �oort� pr gW amry p System 3xr= es; ew 1 sand Inenord data �tpi0t'8 report. FF�,{L��II �jj��II��yy1�ii 07 - 4ifGarnllal Ri6bWs S m � MMINddbLLiise n M online in realAm. by various fswrdel data daaaifcation structure elements and transaction number- 07 - Financial Reports System provides the ability to view monthly end year-bEate balances online by any posted abment in the financial data dazatfication structure. 07 - Financial Reports System provides Me ability to view inceptbn-to-date balances for grants projects online bryy any posted element of the financial data ta'nd 07. Fawvlal Reports todrill down from online kWiry screens to 07 - Financial Reports �S��yf�/�y���yppQ�syl'Ipnd�1taialitty, S� 0 yl�JAifa; idllly 101dlondll wunhd acoodnts Wtween 07 - FFirvncielJj/y,�jb 07 07 cru� WEAW&UTme—speorfied period of bma using relevant Information about outlays and Inflows from both Accounts PaYurble and Accounts Rabb_ rovtdes 8w study to nterf ace pertinent financial date dassitication data to other av dams. RO General LV.r RJJ General Lei ar HIGH I HIGH General L eef HIGH I Fff(f GenerelL HIGH RO Gan erol L er HIGH i SF General Ledger I RO General Ledger SF General Laeff((�nl I 1 RO General LeQjjjj{{{{er HIGH I RO General Led/jer HIGH RO Generel L er LOW I RO General Leda IOW ' I Generel Ledger LOW General LOW I Jgrr H6 General Leda FiO LOW SF Cash Man��Rpeamerit I SF General Ledger SF General Ledger SF General Ledger SF General Ledger RO General Ledger I SF General ��.RR�r��07((77��}}��r MEDIUM I RO GanerolU. qpl LAW SF Caen Manegerrrrkk �FSS yaolea, Receivables MI General Leendd� LOW I MI Generel Ledger MEDIUM I I I I I I I I I i f 1 I I I t I 1 1 1 maintain fixed asset records online and Management properly accounts for assets in accordance with the City's hart of accounts. FE, 00 02 00 00 F5.00-02-00-00 00 - General Requirements System provides the ability to maintain pertinent data on both capitalized and non - capitalized assets, which can be either portable or non -portable as follows: F5 00 02 01 00 F5-00-02-01-00 00 - General Requirements Capitalize assets based upon a user- MI Asset LOW specified criteria, Including amount Management threshold by asset Noe. FS 00 02 02 00 F5-00-02-02-00 00 - General Requirements Track assets (non -capitalized SF Asset equipment) that are not to be capitalized Management per City policy but have been deemed to be secured by City or department policy (e.g., mobile phonea). F5 00 03 00 00 F5-00-03-00-00 00 - General Requirements System provides the ability to allow MI Asset LOW modification of asset capitalization and Management control rules per City and department policy, as necessary (i.e., no hard coding of rules). F5 00 04 00 00 F5-00-04-00-00 00 - General Requirements System provides the following Asset Management functionality: F5 001 04 01 00 F5-00-04-01-00 00 - General Requirements Additions SF Asset Ma n�aement F5 001 04 02 00 F5-00-04-02-00 00 - General Requirements Changes to asset Information SIF Asset Management F5 001 04 03 00 F5-00-04-03-00 00 - General Requirements I Impainnents/Disposalarrheft SF Asset Management F5 00 04 04 00 F5-00-04-04-00 00 - General Requirements Updates to accounting balances based SF Asset on changed asset information (e.g., Management charging useful life posts "catch-up" or corrections to depredation). F5I 001 04 05 00 F5-00-04-05-00 00 - General Requirements I Transfers SF Asset Management F5I 001 04 06 00 F5-00-04-06-00 00 - General Requirements I Inquiries SF Asset Ma nr7Bement F5I 00 04 07 0o F5-00-04-07-00 00 - General Requirements i Betterments SIF Asset MarlaAement F5I 00 04 08 00 F5-00-04-08-00 00 - General Requirements I Depreciation $F !asset Management City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 299 of 418 Reverse previous substantive transactions, including depreciation F5 00 04 09 00 F5-00-04-09-00 00 - General Requirements Amortization (of leases) or other SF Asset intangibles Management, Real Estate Management F5 00 0$ 00 00 F5-00-05-00.00 00 - General Requirements System security provides the ability to limit SF Asset the Asset Management functions based on Management the access granted to users by each department. FS 00 06 00 00 F5-00-06-00-00 00 - General Requirements System provides the ability to generate SF Asset "mass" asset transactions (such as mass Management additions, mesa disposals, mass transfers, and mass changes) by user -defined criteria, with proper security/authority. F5 00 07 00 00 FS-00-07-00-00 00 - General Requirements System provides the ability to support a SF Asset physical location hierarchy (i.e., parentichlId Management relationship) of at least four levels. For example, (1) a parcel of land ran have multiple buildings on It, and each building can have multiple rooms, etc. F5 00 08 00 Od F5-00-08-00.00 00 - General Requirements System provides the ability to attach SF Asset electronic documents (including photos) to Management an asset record. F5 00 09 00 00 FS-00-09-00-00 00 - General Requirements System provides the ability to integrate SF Asset between the General Ledger module and Management, Asset Management module to identify General Ledger expenditure transactions as capitalized assets when Items meet user -defined criteria (e.g., capitalize if individual Item cost is greater than S5,000 and minimum 3 year useful fife). FS 00 10 00 00 F5-00-10-00-00 00 - General Requirements System provides the ability to generate RO Asset standard governmental fixed asset reports Management, and user -defined fixed asset reports In General Ledger compliance with GASB 3.4 and 51, and report on all fixed asset balances In the standard CAFR format (with supporting notes and schedules). F5 00 11 00 00 FS-00-11-00-00 00 - General Requimments System provides the ability to support a Sr Asset hierarchical asset definition (e.g., a piece of Management equipment can be comprised of multiple component levels). FS 01 01 00 00 175-01-01-00-00 01 - Asset add and Maint System Is fully integrated with General SF Asset Ledger, Procurement, and Accounts Payable Management, to carry forward relevant purchasing, General Ledger, descriptive, invoice and accounting Purchasing, Information as a starting point for recording Payables the asset. F5 01 02 00 00 F5-01-02-00-00 01 - Asset add and Maint System tracks the following categories of assets: F5 01 02 01 00 F5-01-02-01-00 01 - Asset add and Maint Land SF Asset Management City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 300 of 418 1 1 1 HIGH F5 01 02 02 00 F5-01-02-02-00 F6 01 02 03 00 F5-01-02-03-00 F5 01 02 04 00 FS-01-02-04-00 F5 01 02 05 00 F5-01-02-05-00 F5 01 02 06 00 F5-01-02-06-00 F5 01 02 07 00 FS-01-02-07-00 F5 01 02 08 OQ F5-01-02-08-00 F5 01 02 09 00 F5.01-02-09-00 F51 01 021 10 00 F5-01-02-10-00 FS 01 021 11 00 F5-01-02-11-00 F5I Oil 03 00 00 F5-01-03-00-00 F51 01I 04 00 00 FS-01-04-00-00 F5 01 05 00 00 F5-01-05-00-00 F5 01 06 00 00 FS-01-06-00-00 F5 01 07 00 00 F5-01-07-00-00 F5 Ot OBI 00 00 F5-01-08-00-00 F51 01I 091 00 00 F5-01-09-00-00 F5 01 10 00 00 F5-01-10-00-00 F5I Oil ill 00 00 F5-01-11-00-00 F5 01 12 00 00 FS-01-12-00-00 F51 01I 121 Ot 00 F5-01-12-01-00 FS 01 12 02 CIO F5-01-12-02-00 IF5I Oil 121 03 00 FS-01-12-03-00 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 301 of 418 01 -Asset add and Maint Buildings 01 -Asset add and Maint Leasehold improvements 01 - Asset add and Maint Equipment 01 -Asset add and Maint Furniture and fixtures 01 -Asset add and Maint Vehicles 01-Asset add and Maint Trailers 01 -Asset add and Maint Equipment acquired through capital leases 01 - Asset add and Maint construction in progress 01 - Asset add and Maim Infrastructure 01 - Asset add and Maint Other user -defined categories (please document number and nature) 01 - Asset add and Maint System provides a table to be used for establishing and associating standard asset descriptive data for all assets. 01 - Asset add and Maint System provides the ability to have a free- form narrative long description of each asset item. 01 - Asset add and Maint System provides the ability to Identify users of assets, in addition to recording property custodian. 01 - Asset add and Maint System provides the ability to automatically create and assign an alpha -numeric asset number that is defined by department to a single Item or multiple items purchased. 01 - Asset add and Maint An asset number is made up of two parts, the first part a a user -definable prefix and the second part is a system generated sequence number. 01 -Asset add and Maint System also provides the ability to either manually or automatically assign an asset number based on asset Gasses. Ot - Asset add and Maint System provides the ability to track the detailed cost for each hem that makes up a whole asset. 01 - Asset add and Maint System provides the ability to store multiple different asset numbers/references for assembled assets. 01 - Asset add and Maint System prevents changing the asset 7urt(ber/referp ce. 01 - Asset add and Maint System provides the ability to maintain detailed property information required to identify, property account for, and safeguard all assets, including but not limited to the following: 01 - Asset add and Maint Asaet Number 01 - Asset add and Maim Property Tag Number (inventory control number) 01 - Asset add and Maint User Defined Fields (at least 10) r l � Sr Asset Manaaement SF Asset Manaaement SF Asset Manaaement SF Asset Manaaement SF Asset Manaaement SF Asset Manaaement Sr Aare[ Manaaement SF Asset Mar)rloement SF Asset Manaaement SF Asset Management SF Asset Management SF Asset Management MI Asset LOW Management SF Asset Management MI Asset LOW Management SF Asset Management SF Asset Management SF Asset Management SF Asset Manaaement SF Asset Manaoement SF Asset Management SF Asset Manaaement Other user -defined substantive System also substantive provides the ability to manually assign an asset number. F5 01 12 04 00 F5-01-12-04-00 01 -Asset add and Maint Property Officer F5 01 12 Old 00 F5-01-12-05-00 01 -Asset add and Maint Location Segments (e.g., address, building, floor, section, room) F5 01 12 06 00 F5-01-12-06-00 01 - Asset add and Maint Multiple Organizational Ownership Info. (including assets loaned tolfrem other entities) F5 01 12 07 00 F5-01-12-07-00 01 - Asset add and Maint Accounting distributions from original acquisition F5 01 12 08 00 F5-01-12-08-00 01 -Asset add and Main: Requisition Number F5 01 12 09 00 F5-01-12.09-00 01 -Asset add and Maint Purchasing Document Numbers F5 01 12 10 00 F5-01-12-10-00 01 -Asset add and Maint Asset Acquisition Date F5 01 12 11 00 F5-01-12-11-00 01 -Asset add and Maint Asset Acquisition Source Code (Developer, federal, city, other grant) FS 01 12 12 00 FS-01-12-12-00 01 -Asset add and Maint In-service Date F5 01 12 13 00 F5-01-12-13.00 I 01 -Asset add and Maint ( Asset Condition F5 01 12 14 00 F5-01-12-14-00 01 - Asset add and Maint I Asset Type F5 01 12 15 00 FS-01-12-15-00 01 - Asset add and Maint I Detivery Date F5 01 12 16 00 F5-01-12-16-00 01 -Asset add and Main: Payment Number (Check Number) FS 01 12 17 00 F5-01-12-17-00 01 - Asset add and Maint Asset Status (e.g.. active, Inactive, surpluslsalvage) F5 01 12 18 00 FS-01-12-18-00 01 -Asset add and Main: Unit CostlValue F5 01 12 19 00 F5-01-12-19-00 01 -Asset add and Man/ Book Value I F5 01 12 20 00 FS-01-12-20.00 01 -Asset add and Maint I Fair market value F5 01 12 21 00 F5-01-12-21-00 I 01 - Asset add and Maint I Trademin Credit F5 01 12 22 00 F5-01-12-22-00 01 - Asset add and Maint Item Classillcation Code (user -defined) I with multiple aub -class codes. F5 01 12 23 00 F5-01-12-23.00 I 01 - Asset add and Maint I Vendor Number, Name F5 01 12 24 00 F5-01-12-24-00 I 01 - Asset add and Maint I Asset Descriptive information FS 01 12 25 00 F5-01-12-25-00 I 01 - Asset add and Maint I Manufacturer Number, Name F5 01 12 26 00 F5.01-12-26-00 I 01 - Asset add and Maint I Model Year F5 01 12 27 00 F5-01-12-27-00 I 01 - Asset add and Maint I Model Number F5 01 12 28 00 F5-01-12-2&00 I 01 - Asset add and Maint I Custodian Contact Information F5 01 12 29 00 F5-01-12-29-00 I 01 -Asset add and Maint I Salvage Value F5 01 12 30 00 F5-01-12-30.00 I 01 -Asset add and Maint I Serial Number F5 01 12 31 00 F5-01-12-31-00 I 01 -Asset add and Maint I License Number (t applicable) F5 01 12 32 00 F5-01-1232-00 I 01 -Asset add and Maint I WarrantylMaintonance Information F5 01 12 33 00 FS-01-12-33-00 I 01 - Asset add and Maint I Betterments FS of 12 34 00 F5-01-12-34-00 I 01 -Asset add and Maint I Disposal Information F5 of 12 35 00 F5-01-12-35-0o L I01 - Asset add and Maint I Lease Asset Information (if applicable) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 302 of 418 SF Asset Management SF Asset Management MI Asset Management SF IAsset Management SF (Asset Management, Purchasing SF (Asset Management, Purchasing SF (Asset Management, Purchasing SF Asset Management SF IAsset Management SF IAsset Management SF IAsset Management SF Asset Management, Purchasing SF IAsset Management SF Asset Management SF IAsset Management SF IAsset Management SF IAsset Management SF Asset Management SF Asset Management SF IAsset Management SF IAsset Management SF IAsset Management SF IAsset Management SF IAsset Management SF IAsset Management SF IAsset Management SF IAsset Management SF IAsset Management SF IAsset Management SF I Asset m Manageent SF IAsset Management SF IAsset Management LOW Multiple Chart of substantive Account distributions (by dollar amount) Via the purchase order. IVia the associated receipt. F5 01 12 36 00 F5-01-12-36.00 01 - Asset add and Maint Estimated Useful Life SF Asset Mananement F® 01 12 37 00 F5-01-12-37-00 01 -Asset add and Maint Estimated Residual Value (Trade-in SF Asset Value) Management F5 01 12 38 00 FS-01-12-38-00 01 -Asset add and Maint Replacement Cost —This field can be SF Asset updated as needed by users Management FS 011 12 39 00 F5-01-12-39-00 01 -Asset add and Maint Depreciation Schedule (Method and Life) SF Asset Management FSI 01 12 40 00 F5.01-1240.00 01 - Asset add and Maint Depreciation Frequency and Convention SF Asset (Annual, Beginning of Month, Maff-Year, Management Mid -Month, or user defined) F5I 011 12 41 00 F5-01-1241-00 01 -Asset add and Maint Budget Year (from which asset was SF Asset purchased) Management F51 011 12 42 00 F5-01-1242-00 01 - Asset add and Maint Lest inventory Date SF Asset Mananement F51 011 12 43 00 FS-01-1243-00 01 - Asset add and Maint Next scheduled inventory date SF Asset 0 added Management F5I 0] t3 00 00 F5-01-13-00-00 01 -Asset add and Maint System allows user defined fields to be MI Asset LOW either entered as free form text or selected Management from a configured drop -down list F5 01 14 00 00 F5-01-14-00-00 01 -Asset add and Maint System allows both centrally defined (city- SF Asset wide) use of user defined fields as well as Management departmentally determined use of user defined fields. F5 01 1S 00 00 F5-01-15-00-00 01 - Asset add and Mast System is able to link component units MI Asset LOW (parent/child relationship) whereby each Management component maintains a financial life of its own. F5 01 16 00 00 F5-01-16-00-00 01 -Asset add and Maint System raptures; on audit trail of changss to SF Asset the asset record, including user, date and Management, time, old and new value) Purchasing F5 01 17 00 00 F5-01-17-00-00 01 -Asset add and Maint System allows for drill -down to original SF Asset procurement documents from the asset Management record. F5 01 18 00 00 F5-01-18-00.00 01 - Asset add and Maint System provides for the addition and SF Asset maintenance of assets obtained through non. Management expenditure transactions (e.g., donations, eminent domain) with simultaneous updates to both the fixed assets module and general ledger. F5 01 19 00 00 F5-01-19-00-00 01 - Asset add and Maint System provides the abidty to copy an asset SF Asset record to create a similar asset record. Management, Purchasing, General ledger, Pavables F5 01 20 00 00 F5-01-20-00-00 01 - Asset add and Maint Authorized users are able to correct SF Asset discrepancies In asset records by overriding Management initially loaded information (received from General ledger. Accounts Payable, and Purchasing modules) with proper authorization. F5 01 21 00 00 F5-01-21-00-00 01 - Asset add and Maint In addition to asset information listed MI Asset LOW previously, system maintains detailed Management property information required to identify, properly account for, and safeguard City lands, Including, but not limited to the following: City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 303 of 418 F5 01 21 01 00 F5-01-21-01-00 01 -Asset add and Maint Legal description per survey MI Asset LOW Management F5 01 21 02 06 F5-01-21-02-00 01 -Asset add and Maint Property's full address SF Asset Management F5 01 21 03 00 F5-01-21-03-00 01 - Asset add and Maint Acquisition information (purchased from SF Asset Acquisition clarification whom, etc,) Management information F5 01 21 04 00 FS-01-21-04-00 01 -Asset add and Maint Number of acres SF Asset Management F5 01 21 05 00 F5-01-21-05-00 01 - Asset add and Maint Value per acre SF Asset Manaqement F5 O1 21 06 00 F5-01-21-06-00 01 -Asset add and Maint Fair market value (e.g., for donated land) MI Asset LOW Management F5 01 21 07 00 FS-01-21-07-00 01 - Asset add and Maint Cost per acre (multiple) SF Asset MarlDAement F5 01 21 08 00 F5-01-21-08-00 01 - Asset add and Maint Deed information MI Asset LOW Manaqement F5 01 21 09 00 FS-01-21-09-00 01 - Asset add and Maint Options to purchase property (for leased SF Asset property) Management rs 01 21 10 00 FS-01-21-10.00 01 -Asset add and Maint Geographic Information System SF Asset technology location (latitude and Management longitude) FS 01 21 11 00 F5-01-21-11-00 01 -Asset add and Maint Other user -defined fields SF Asset Manaqement F5 01 22 00 00 F5-01-22-00-00 01 -Asset add and Maint During mass additions process, user can SF Asset split asset record entries for identical items Management and then assign separate property tag Inventory control numbers (e.g., purchase of 20 Identical personal computers). F5 01 23 00 00 F5-01-23-00-00 01 -Asset add and Maint System provides the ability to transfer fixed SF Asset assets within or between departments at the Management individual asset level and to generate the appropriate accounting enures. FS 01 24 06 00 F5A1-24-00-00 01 - Asset add and Maint System raptures explanation of transfer SF Asset (free -form narrative) Management re 01 26 o6 00 F5-01-25-00-00 01 -Asset add and Maint System supports assignment of a single SF Asset System supports substantive department as managing an asset, Management multiple regardless of how many departments funded department asset it.. ownership for each property item (e.g., multiple departments or funds may finance an asset). F5 01 16 00 00 F5-01-26-00-00 01 -Asset add and Maint System tracks assets purchased with SF Asset System tracks clarification various funding sources Q.e., grards) using a Management assets purchased searchable reportable field. with various funding sources (i.e.. arants). F5 01 27 00 00 F5-01-27-00-00 01 - Asset add and Maint System allows for decoupling assembled MI Asset MEDIUM asset components and reassembling them in Management a different configuration (such as moving thermal imager from a fire apparatus and assigning It to a different one). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 304 of 418 It I I F I I I I I I I I I I ! 1 Ir I i a i I i ti I I I # F5 01 28 00 00 F5-01-28-00-00 01 - Asset add and Maint System provides the ability for commodity MI line items to contain the following data items, including but not limited to, the following data elements: Fixed asset Indicator (new, replacement, or enhancement; 0 replacement or enhancement, need existing tag number). F5 01 29 00 00 F5-01-29-W-00 01 - Asset add and Maint System provides the ability to capture a fixed MI asset indicator (determine whether commodity is an asset based on dollar amount and expenditure object code). F5 01 30 00 00 F5-01-30-00-00 01 -Asset add and Maint System provides the ability to drop the SF "asset" indicator that was established at the time a requisition was created, if the associated PO amount is less than the user - specified dollar threshold, based on the City's business rules. FS 01 31 00 00 F5-01-31-00-00 01 -Asset add and Maint System provides the ability to assign multiple SF expenditure line items to a single fixed assset record F5 01 32 00 00 F5-01-32-00-00 01 -Asset add and Maint System provides the ability to capture items SF such as lot number, serial number, asset tag number, and expiration date at time of receipt. F5 01 33 00 00 F5-01-33-00-00 01 - Asset add and Maint System provides the ability to flag purchases SF as "placed in service" as fixed assets upon receipt of good. F5 01 34 00 00 F5-0134-00-00 Ot - Asset add and Maint System allows "placed in service date" to be MI changed for assets that require assembly before placing in service. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 305 of 418 I I I 1 i I i 1 Asset MEDIUM Management Asset MEDIUM Management Asset Management, Payables Asset System provides spelling Management, the ability to Purchasing, assigns multiple Inventory expenditure line items to a single fixed assset record Asset Management, Purchasing Asset Management. Purchasing Asset LOW Management F5 01 35 00 00 F5-01.35-00-00 01 -Asset add and Maint System evaluates purchase order line items MA Asset MEDIUM and applies the following edit If the unit Management price is greater than the capitalization threshhold and the expenditure account is not capital outlay and the commodity code indicates that it may be a fixed asset, then the transaction should produce a warning if the fixed asset Indicator is not selected System evaluates substantive purchase order line items and applies the following edit If the unit price is greater than the capitalization threshhold and the expenditure account is not capital outlay and the commodity code indicates that It is net a service, then the transaction should produce a warning if the fixed asset indicator is not selected 'T ?sf. F5 02 01 00 00 F5-02-01-00-M 02 - Asset Dis, Rat, and Theft System can generate either financial or SF Asset memo transactions to the General Ledger to Management, reflect the financial Impact of asset General Ledger dispositions, and should automatically compute the gainAoss associated with a disposal. F5 01 02 00 00 F5-02-02-00-00 02 - Asset Dis, Rat, and Theft System allows for recording of the following information related to disposals, trade -Ins, missing, lost, or stolen assets: FS 02 02 01 00 FS-02-02-01-00 02 - Asset Dis, Rol, and Theft Property tag / inventory control number SF Asset Manaoement F5 02 02 02 00 F5-02-02-02-00 02 - Asset Dis, Rat, and Theft Reporting individual MI Asset LOW Manaoement F5 of 02 M 00 175-02-02-03-00 02 - Asset Dis, Rat, and Theft Date of occurrence or date first noticed SF Asset missing Management FS 02 02 04 00 F5-02-02-04-00 02 - Asset Dis, Rat, and Theft Description of circumstances MI Asset LOW surrounding the Management disappearance/disposition F5 02 02 05 00 FS-02-02-05-00 02 - Asset Dis. Rat, and Theft I Steps taken to locate item MI LOW ment I Manaoe F5 02 02 06 00 F5-02-02-06-00 02 - Asset Dis, Rot, and Then I Disposal date SF I Asset Management F5 02 02 07 00 F5-02-02-07-00 02 - Asset Dis, Rat, and Theft I Disposal amount SF I ManAsset agment F5 02 02 08 00 F5-02-02-08-00 02 - Asset Dis, Rat, and Theft I Disposal method SF I ManAsset aoement F5 02 02 09 00 F5.02-02-09-00 02 - Asset Dis, Rat, and Theft Police report Information (multiple MI Asset LOW jurisdictions) through file attachments Management F5 02 02 10 00 F5-02-02-10-00 02 - Asset Dis, Rat, and Theft I Proceeds from sales of disposed SF I Asset pionr Management FS 02 03 00 00 F542-03-00-00 02 - Asset Ds, Rat, and Theft System trac s estimated useful life MI Asset LOW System provides substantive Management electronic notification to users when useful life threshold is nearing. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 306 of 418 1 1 1 11 i 1 1 I 1 1 M 1 1 F5 02 04 00 00 FS-02-04-00-00 02 - Asset Dis, Ret, and Theft System records grant asset dispositions and proceeds of sales which integrate with the Grants Management module. F5 02 05 Od 00 F5-02-05-00-00 02 - Asset Dis, Ret, and Theft System provides the ability to flag assets with disposal restrictions and display the restriction message for user handling (e.g., federal grant items that must be returned to the federal government, proceeds returned to federal government, etc.) + i I MI Asset MEDIUM Management MI Asset LOW Management � �i➢)�'�' q" "h�dli�VGV�i'�y��i�1�IdWIII����y��lllil��{uY, IIII � . ,r �:..,� ...,.., ,.„,,,��4f7�s�9t+�°�h�,� ............... FS 03 01 00 00 FS-03-01-00.00 03 -Surplus Property System provides the ability to split and SF Asset distribute the proceeds of an asset sale as Management surplus property.. F5 031 02 00 00 F5-03-02-00.00 03 -Surplus Property System provides the option to establish an SF Asset electronic approval path for sales kom Management surplus property. F5 031 03 00 00 F5.03.03-00.00 03 -Surplus Property System provides the ability for owning SF Asset department to change the asset status Management tolfrom 'surplus'. F5 03 04 00 00 F5-03-04-00-00 03 -Surplus Property System provides the ability to transfer from SF Asset surplus to retired status. Management F5 03 01 00 00 F5-03-05-00-00 03 -Surplus Property System should provide ability to support SF Asset electronic advertisement of items for sale Management, (e.g., on the web) to designated customers. Strategic Sourcing F5 03 06 00 00 F5-03-06-00-00 03 -Surplus Property System supports receipt of seated bid SF Strategic Sourcing responses through electronic means. F5 03 07 00 00 F5-03-07-00-00 03 -Surplus Property If bid opening date and time has expired, the SF Strategic Sourcing System must prohibit the acceptance of a bid through electronic means. F5 03 08 00 00 F5-03-08-00-00 03 -Surplus Property System should support the publishing of SF Asset surplus properties to be sold on a web site. Management, F5 03 09 00 00 F5-03-09-00-00 F5 03I 10 00 00 176-03-10-00-00 F5 03 11 00 00 F5-03-11-00-00 F5 03 12 00 06 F5.03-12-00-00 F5 031 no la"UNKNOWN"AMONOMM 13 00 00 F5-03-13-00-00 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 307 of 418 03 -Surplus Property System maintains a file of customers that commonly bid on surplus properties. 03 -Surplus Property System should allow for sale of items via sealed bid and perform bid tabulations to show highest bidder. 03 -Surplus Property System should allow for grouping of items into lots for sale while retaining specific item owner information. 03 -Surplus Property System should allow for recording of proceeds from sales of assets (net of auction costs) when Item is sold. 03 -Surplus Property System produces a bill of sale for property sales. Strategic Sourcing SF Asset Management, Strategic Sourcing SF Strategic Sourcing SF Strategic Sourcing SF Strategic Sourcing SF Asset Management, Strategic Sourcing, System should grammar support the publishing of surplus properties to be sold to a web site. Shouldn't we record to gross instead of net and record an expenditure of $10? F5 04 01 00 00 F5-04-01-00-00 F5 04 02 00 00 F5-04-02-00-00 F5 04 03 00 00 F5-04-03-00-00 F5 04 03 01 00 F5-04-03-01-00 F5 04 03 02 00 F5.04.0.4.02-00 F5 04 03 03 06 F5-04-03-03-00 F5 04 01 04 00 F5-04-03-04-00 F5 04 03 04 00 F5.04-03-05-00 FA 04 04 00 00 F5-04.04-00-00 F5 04 09 06 00 F5-04-05-00-00 FS 04 06 00 00 F5-04-06-00-00 F5 04 07 00 00 F5-04-07-00-00 FS 04 08 00 00 F5-04-06-00-00 City of Fort Worth I CIBER, Inc. Professional Services Agreement Page 308 of 418 1 1 t I 04 - Depreciation System can generate either financial or SF Asset memo transactions to the General Ledger Management, for capital asset depreciation expense by General Ledger specified funds. 04 - Depreciation System provides the option to process SF Asset depreciation on-line or in batch mode. Management, General Ledqer 04 - Depredation System provides the following depreciation functionality: 04 - Depredation Provide depreciation schedules on SF Asset individual fixed assets Management 04 - Depredation Generate periodic depredation by asset SF Asset for any element In the classification Management struch" (current prance Is annually). 04 - Depreciation Automatically calculate depreciation In SF Asset accordance with the depreciation Management method and convention where designated for an asset. 04 - Depredation Maintain multiple asset basis values for SF Asset each asset if desired, utilizing industry- Management standard depredation methods. 04 - Depreciation Automatically charge depreciation to SF Asset multiple accounting distributions for split- Management funded assets 04 - Depredation System allows for multiple depreciation SF Asset schedules to be applied to an asset to Management support varying depredation reporting requirements (such as a federal useful life er capitalization thresholds different than the citys). 04 - Depredation System allows for changing asset useful life, SF Asset value basis, salvage value, and depreciation Management method, when necessary, and automatically recalculate depreciation expense in accordance with such changes and track the changes. 04 - Depreciation System provides the ability to simulate SF Asset depreciation calculations for individual Management assets or a group of assets without being required to post the results. 04 - Depreciation System provides allocation tables that can Sr Asset be user -defined to allocate asset cost and Management depreciation expense. 04 - Depredation System provides the ability to store an Si, Aa>ee acquisition date and a depreciation start Management date, without the dates having to be the same. System allows for clarification multiple depreciation schedules to be applied to an asset to support varying depreciation reporting requirements. System allows for substantive changing asset useful life, value basis, salvage value, and depreciation method, when necessary, and automatically recalculate depreciation expense in accordance with such chances. F5 04 09 00 00 F5-04-09-00-00 04 - Depreciation System provides multiple depreciation methods, Including but not limited to: F5 04 09 01 00 F5-04-09-0 1 -00 04-Depreciation Straight Line SF Asset Management F5 04 09 02 00 F6-04-09-02-00 04 - Depreciation Declining Balance SF Asset Manaaement F5 041 09 03 00 FS-04-09-03-00 04 - Depreciation Sum of the Years Digits SF Asset Management F5I 041 09 04 00 FS-04-09-04-00 04 - Depreciation Hours/Mileage SF Asset Manaaement F5I 041 09 05 00 F5.04-09-0500 04 - Depreciation User -Defined SF Asset Management F5 04 10 00 00 F5-04-10-00-0004 - Depreciation System prevents the depreciating of an SF Asset asset's value below zero. Management F5 04 11 00 00 F5.04.1 1 -00-00 04 - Depreciation System calculates depreciation adjustments SF Asset System calculates clarification based on the remaining useful life. Management depreciation adjustments based on the balance of the assets useful life. F5I 041 12 00 00 F5-04-12-00-00 04 - Depreciation System provides the ability to allow SF Asset individual assets to be designated as non- Management depreciable (e.g., land). F5 04 13 00 00 F5-04-13-00-00 04-Depredation Delete SF Asset System provides Management the ability to calculate and allocate depreciation based on the funding source used to purchase the asset. F5 05 D1 00 00 FS-05-01-00-00 05 - Physical Inventory System provides fully integrated bar-code TP MEDIUM technology for physical inventory tagging upon acquisition/purchase and annual inventory certlfication(s). FS 05 02 00 00 F5-05-02.00.00 05 - Physical Inventory System provides ability to create a scanned TP MEDIUM record file from bar-coding for comparison to fixed asset and portable equipment records. F5 05 03 00 00 F5-05-03-00-00 09 - Querying and Reporting System provides the ability to produce a RO Asset LOW physical inventory worksheet to be sorted, Management grouped and aggregated based on user deflned criteria to assist In conducting physical Inventory. FS 05 04 00 00 F5-05-04-00-00 05 - Physical Inventory System Is able to record multiple updates to SF Asset System is able to clarification asset location information and'tast Management update asset inventoried date' for an asset. location information and -last inventoried date' for each asset for each certification. F5 05 as 00 00 F5-05-05-00-00 05 - Physical Inventory System provides the ability to report and SF Asset adjust variances between system amounts Management and physical counts. F5 05 06 00 00 F5-05-06A04)0 05 - Physical Inventory System is able to generate customized bar- TP MEDIUM coded labels for asset identification (inventory control and property number tags), including building, floor and room information. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 309 of 418 F5 05 07 00 00 F5-05-07-00-00 05 - Physical Inventory System provides the ability to enter data SF Asset manually, In addition to using bar coding Management technology. F5 05 08 00 00 FS-05-08-00-00 05 - Physical Inventory System provides the ability to be updated TP MEDIUM real time from bar code scanners. FS 06 01 00 00 FS-06-01-00-00 06- Projects -System is able to identify/record all SF Project Costing, capitalizabie costs associated with the Asset construction or purchaselacquisition of an Management asset. F5 06 02 00 00 F5-06-02-00-00 06 - Capital Projects System identifies, records, and depreciates SF Project Costing betterments associated with an asset, including optional unique identification of betterments associated with components. FS 06 03 00 00 F5-06-03-00-00 06 - Capital Projects System provides the ability to capture SF Project Costing, activity/costs resulting from several City Asset departments working ooneurrently on a Management Project. F5 06 04 00 00 F5-06-04-00-00 06 - Capital Projects System provides the ability to produce SF Project Costing notification of project status (e.g., completed) based upon user -defined criteria. FS 06 05 00 00 F5.06-05-00-00 06 - Capital Projects System captures and maintains construction SF Project Costing, work In progress informabon and provides Asset the ability to recognize fixed/capital assets Management when they are placed in seivka, regardless of whether the project has been completed. iWAIIII ®,r IlII if uil .� mm x`W "' � ' t7YXg F5 07 01 00 00 FS-07-01-00-00 07 - Leases System tracks assets in accordance with the requirements of FASB Statement No. 13: Accounting for Leases, as emended, including but rot limited to: F5 07 01 01 00 F5-07-01-01-00 07 - Leases Recording of the capkal lease or SF Asset operating lease and the corresponding Management leasehold improvements F5 07 01 02 00 F5-07-01-02-00 07 - Leases Tracking lease payments I SF Asset Menaoement F5 07 01 03 00 FS-07-01-03-00 07 - Leases Periodic cost recognition SF Asset I Management F5 07 01 04 00 F5-07-01-04-00 07 - Leases Tracking lessee and lessor SF Asset Management F5 07 01 05 00 F5.07-01-05-00 07 - Leases Tracking facility accessibility and SF Asset responsible parry for making accessibility Management modifications (lessee or festtor) FS 07 01 07 00 F5.07-01-07-00 07 - Leases Tracking purchase options SF Asset Management F5 07 01 08 06 F5-07-01-08-00 07 - Leases Tracking lease terms SF Asset _ Management F5 07 Cl 09 00 F5-07-01-09-00 07 - Leases Tracking lease type (e.g., capital, SF Asset operating, eta) Management F5 07 01 10 00 FS-07-01-10-00 07 - Leases Tracking schedule of lease payments SF Asset I Management City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 310 of 418 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 1 F5 07 02 00 00 F5.07-02-00-00 07 - Leases System is able to differentiate between SF Asset leased assets and purchased assets. Management F5 07 03 00 00 F5-07-03-00.00 07 - Leases System facilitates determination of FASB 13 SF Asset lease type (i.e., capital, operating, etc.) Management based on terms and conditions of lease agreement. F5 07 04 00 00 F5-07-04-00-00 07-Leases System provides the ability to perform RQ Asset MEDIUM lease/purchase comparative analyses. Management 119 07 OS 00 00 F5-07-05.00.00 07 - Leases System provides the ability to record the SF Asset transfer of leases to the City. Management F5 07 06 00 00 F5-07-06-00-00 07 - Leases System provides the ability to amortize SF Asset capital leases in compliance with FASB 13 Management and GASS 13. F5 07 07 00 00 F5-07-07-00-00 07 - Leases System supports changes required due to SF Asset lease amendments. Management F5 07 08 00 00 F5-07-08-00-00 07- Leases System provides the ability to automatically SF Asset generate a notification that a lease is going Management to expire within a certain timeframe as specified by the user. F5 07 09 00 00 F5-07-09-00-00 07 - Leases System is able to maintain lease payment SF Asset schedules. Management F5 08 01 00 00 F5-08-01-00-00 08 - Asset Warranties System is able to maintain warranty/service SF Asset agreement information for assets, by type of Management asset F5 08 02 00 00 F5-08-02-00-00 08 - Asset Warranties System raptures insurance information for MI Asset LOW fixed assets (insured value, roof type, Management construction information, square footage, insured contents, etc.) F5 08 03 00 00 F5-08-03-00-00 08 - Asset Warranties System should support hyperlinks to the MI Asset LOW vendors web site to reference asset Management maintenance and warranty Information. F5 08 04 00 00 F5-08-04-00-00 08 - Asset Warranties System provides the ability to inquire on SF Asset warranty information through the entry of a Management serial number and property tagfinventory control number. F5 Of I 05 00 00 F5-08-05-00-00 08 - Asset Warranties System provides the ability to notify of MI Asset LOW warranty agreement expiration. Management x F5 09 01 00 00 F5-09-01-00-00 09 - Querying and Reporting System is able to report on assets for all SF Asset fields required for financial reporting Management purposes. F5 09 02 00 00 F5.09-02.00.00 09 - Querying and Reporting System is able to generate standard RQ Asset HIGH governmental fixed asset reports and user- Management defined fixed asset reports in compliance with GASS 34 and 51. F5 09 03 00 00 F5-09-03-00-00 09 - Querying and Reporting System can display or print a report of RQ Asset LOW surplus property, including each item's Management history. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 311 of 418 F5 09 04 00 00 F5-09-04-00.00 09 - Querying and Reporting System produces a transaction register audit SF Asset trail of at acquisitions, transfers, changes Management and retirements during a user -defined time period by asset type, department, transaction date or purchase amount. F5 09 05 00 00 F5-09-05-00-00 09 - Querying and Reporting System has the ability to produce SF Asset depreciation reports by multiple levels (e.g.. Management All Chart of Account Elements, asset type, responsibility area, etc.). F5 09 06 00 06 F5-09-0"0-00 09 - Querying and Reporting System provides a walk -forward of fixed asse RQ Asset LOW Manaqement F5 09 07 00 00 F5-09-07-00.00 09 - Querying and Reporting System can produce a report that facilitates RQ Asset LOW reconciliation to physical inventory counts. Management F5 09 08 00 00 F5-09-08.-00-00 09 - Querying and Reporting System provides a report of all property RQ Asset LOW changes as of a user specified date Management rf 09 09 00 00 F5-09-09-00-00 09 - Querying and Reporting System provides a property insurance RQ Asset LOW schedule that displays the property value Management and associated insurance amount. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 312 of 418 1 1 1 I I I i I I I I 1 I I I I 1 I 1 I I I i I ! I I I I I 1 1 1 1 i 1 1 $ Requirements upload and download project date from Project Costing. Data from spreadsheets, word can be uploaded into processors, and databases. Project Costing via MS Projects. F6 00 02 00 00 F6.00-02.00-00 00 - General System provides the ability to SF Project Costing Requirements maintain historical data for all projects independent of GL data (across multiple fiscal years). F6 00 03 00 00 F6-00-03-00.00 00 - General System provides the ability to SF Project Costing Requirements post ran -financial transactions to project ledgers without corresponding posting o general lediller accounts. F6 00 04 00 00 F6-00-04-00.00 00 - General System provides the ability to SF Project Costing Re irements dock posti to a ptn act. F6 01 Ot OO 00 F6-01-01-00.00 01 - Define System captures the following Prolect attributes f ac project: F6 01 01 01 00 F6-01-01-01-00 01 - Define Projec( Ffum r SF Project Costing Project F6 01 01 02 00 F6-01-01-02.00 01 • Define Project Type SF Project Costing Project F6 01 01 03 00 F6.01-01.03-00 Comprehensive Project (such SF Project Costing as Trinity River Vision) F6 01 Ot 04 00 F6-01-01-04-00 01 - Define Project Begin Date SF Project Costing PrQiect F6I 01 01 05 00 F6-01-01-05.00 01 -Define Project End Date SF Project Costing Prt Demo F6I 01 01 06 00 F6-01-01-06.00 01 - Project Title SF Project Costing Project F6I 01 01 07 00 F6-01-01-07-00 01 - Define Project Approval Request SF Project Costing, Project Date Program Management F6I 01 01 08 00 F6-01-01-08-00 01 - Define Project Approval Status SF Project Costing, Project (Planned, Submitted, Program Approved for Funding) Management F6 01 Oil O9 00 F6-01-01-09-00 01 - Define Project Approval Action Date SF Project Costing, Project Program Management F6 01 01 10 00 F6-01-01-10-00 01 - Define Descriptive SF Project Costing Protect Inform((tonn/C�jmme[�i. F6 01 01 11 00 F6-01-01-11-00 01 - Define Prolc?Roles (e.g., Project SF Project Costing Project Manager, Supervisor) - Table driven with user -defined values F6 01 Oil 121 00 F6-01-01-12-00 Ot - Define Project Role Employee Name SF Project Costing Protect F6 01 01l 131 00 F6-01-01-13-00 01 -Define Managing Department MI Project Costing LOW Protect F6I Ot 0il 141 00 F6-01-01-14-00 01-Define Managing Department Mt Project Costing LOW Project Contact F6I Ot 0il 151 00 F6-01-01-15.00 01Proeefifa Sponsoring Department MI Project Costing LOW F6I Ot Oil 161 00 F6-01-01-16-00 a 01 -Define Sponsoring Department MI Project Costing LOW Proj Conta F6 01 01 17 00 F6-01-01-17-00 01 - Define Group Code (i.e., value used SF Project Costing Project to group like or associated protects together) F6 01 01 18 00 F6-01-01.18.00 01 - Define Asset Descriptive information SF Project Costing Project for construction projects F6 01 01 19I 00 F6-01-01-19-00 01 - Define Location (e.g.. council district) SF Project Costing Project City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 313 of 418 F6 01 01 20 00 F6-01-01-20.00 Multiple council districts with SF Project Costing allocation F6 01 01 21 00 F6-01-01-21-00 01 - Define Community Facilities MI Project Costing LOW Project ((jjgqreement (CFA) flao F6 01 01 22 00 F6-01-01-22-f1Q M8C reference SF Project Costing F6 01 01 23 00 F6-0t-01-23-00 01 - Define Project Status (e.g., Open for SF Project Costing Project planning, Open for GL Entry, Closed) - Table driven with user -defined values rif 01 01 24 00 F6-01-01-24-00 01 - Define Other geographical SF Project Costing Project breakdown (Department defined F6 01 01 25 00 F6-01-01-25-00 01 - Deflne GIS (x,y SF Project Costing Proleyt F6 01 01 26 00 F6-01-01-26-00 01 - Define GIS (non-knear) SF Project Costing Proiect F6 01 01 27 00 F6-01-01-27-00 01 - Define Start point (linear projects) MI Project Costing LOW Proiect F6 01 01 28 00 F6-01-01-28-00 01 -Define End point (linear projects) MI Project Costing LOW Project Fl 01 01 29 00 F6-01-01-29-W 01 - define Multiple user -defined fields SF Project Costing Project F6 01 02 00 00 F6-01-02-00.00 01 - Define System provides for lower level Project breakdown of projects into at lease four levels. Project Costing provides 10 fields that can be user defined but require a label change during implementation. System provides for lower level breakdown of projects into at lease four levels. grammar F6 01 02 01 00 F6-01-02-01-00 01 - Define Project SF Project Costing Project F6 01 02 02 00 F641-02-02-00 01 - Define Sub -project SF Project Costing Proiect F6 01 02 03 00 F6-01-02-03.00 01- Define Phase SF Project Costing Project F6 01 02 04 00 F6-01-02-04-00 01 - define Job SF Project Costing ProKa F6 01 03 00 00 F6-01-03.0000 01 - befine System captures the following Project attributes for each breakdown of the pf��ff��ect hierarch(' F6 01 03 01 00 F6-01-03-01-00 01 - Define 6s uriated Start Date SF Project Costing PrVFE 01 03 02 00 F6-01-03-02-00 01 -define Estimated End Date SF Project Costing Proiect F6 0'( 03 03 00 F6-W-03.03-W 01 - Define Capital ProJgrraam reference - SF Project Costing Project F6 01 03 04 00 F6.01-03-04-00 01 - Define Qcluaf S`aerl Da�e�low SF Project Costing Prof F6 01 03 05 00 F6-01.03.05-00 01 - Define Actual End Date SF Project Costing Proiae��tt F6 01 03 06 00 F"1-03-06-00 01 - Defne Title SF Project Costing Pro F6 01 03 07 00 F6-01-03.07-00 01 - One Descriptive SF Project Costing Pro'I�t Information/Comments F6 01 03 08 o6 F6-01-03-08-00 01 -Defne Status (Open for Planning, SF F6 01 04 00 00 F6-01-04-00-00 Project 01 - Define O for GL Entry, Close) System has the ability to support Project the following hierarchical organization for capital programs: F6 Ot 04 01 00 F6-01-04-01 -00 01 - Define Capital Program (i.e. 2004 SF Project Costing Project bordl F6 01 04 02 00 F6-01.04.02-00 01 - Define Program Area (i.e. Streets) SF Project Costing Project F6 01 04 03 00 F6-01-04-03.00 01 - befine Service Type (i.e. Street SF Project Costing Prole,t ltghtsl F6 01 04 04 00 F6-01-04-0400 Ot%-Q line fund (i.e. new, SF Project Costing (Sij F6 01 05 00 00 F6-01-05.00.00 Ot -r Define Syefem allows users to attach SF Project Costing Project flies of different formats (MicroSoft Word, Excel, Adobe Acrobat etc. i��qRqf�ry,� IliIV6�ali6lli�l j i�f� _ City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 314 of 418 1 1 3 1 1 1 1 1 1 71 "1 A --1 -73 77-3 77773 _73 � 1 "I F6 02 01 00 00 F6-02-01-00-00 02 - Capture System provides the ability to SF Project Costing, Project Costs allocate direct costs to projects Purchasing, through expenditure transactions. Payables, Expenses, General Ledger F6 02 02 00 00 F6.02-02-00.00 02 - Capture System provides the ability to SF Project Costing, l Project Costs allocate indirect costs to projects General Ledger using cost allocation functions. F6 02 03 00 00 F6-02-03.00.00 02 - Capture System provides the ability to link SF Project Costing, Project Costs multiple projects to a grant. Grants F6 02 04 00 00 F6-02-04-00.00 02 - Capture System provides the ability to SF Project Costing Project Costs access all transaction history for a project (i.e., cannot purge pro act data for active prolectsl. F6 02 05 00 00 F6-02-05-00-DO 02 - Capture System provides the ability to SF Project Costing Project Costs track finandal activity associated with each phase or job within a ohase. F6 021 OB 00 00 F6-02-06.00.00 tem provides the ability to SF Project Costing �Capture Project stsb k prrodveraleaee al fiscyea and dy F6 02 07 00 00 F6-02-07-00-00 02 - Capture System allows users to record Project Costs developer contributions of fixed assets to a capital project with the following dual accounting re4uiremenis F6 02 07 01 00 F6-02.07-01.00 02 - Capture At the fund level, a credit to SF Project Costing, Project Costs contribution revenue and a Asset debit to capital outlay Management F6 021 07 02 00 F6-02-07-02-00 02 - Capture At the government wide level a SF ProJed Cosbng, Project Costs debit to fixed assets and a Asset credh toMullMana amen[ FE 03 01 00 00 F6-03-01-00-00 03- System provides the ability to SF Project Costing, Plan/Budget perform inception to date General Ledger Projects budgeting/budgetary control for capital and operating projects as opposed to annual budgeting for p9peratino fur s. F6 03 02 00 00 F6-03-02-00-00 03- System proves the ability to SF Project Costing. Plan/Budget create project budgets with General Ledger Projects multiple funding sources (e.g., state funds, local Ponds, grant funds, bond fundsl. F6 03 03 00 00 F6-03-03-00-00 03- System provides the ability to RQ Project Costing, MEDIUM Plan/Budget forecast budgets for multi -year General Ledger Projects periods. F6 03 04 00 00 F6-03-04-00.00 03- System provides the ability to SF Project Costing, Plan/Budget establish total project budgets. General Ledger Projects F6 03 05 00 00 F6-03-05.00.00 03- System provides the ability to SF Project Costing, PlanBudget establish budgets for each level General Ledger Projects of the project hierarchy in combination with any other chart of accounts elements. F6 03 06 00 00 F6-03-06-00-00 03- System provides the ability to SF Project Costing, Plan/Budget adjust project budgets. General Ledger Projects F6 03 07 00 00 F6-03-07.00-00 03- System provides the ability to SF Project Costing. Plan/Budget capture the following: original General Ledger Projects budget and adjustments to the bud f et. F6 031 08 00 00 F6-03-08.00.00 03- System provides the ability to SF Project Costing, Plan/Budget lock the original budget, once General Ledger Projecta finalized. F6 031 09 00 00 F6-03-09-00-00 03- System has the ability to SF Project Costing, Plan/Budget distinguish between total project General Ledger Projects budget and appropriated budget. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 315 of 418 F6 03 10 00 00 F6-03-10-00-00 03- System has the ability to track Plan/Budget variances: Pro" F6 03 10 01 00 F6-03-10-01-00 03. between appropriated budget RQ Project Costing. MEDIUM Plan/Budget and total (revised) budget General Ledger Projects F6 03 10 02 00 F6-03-10-02-00 03- appropriated budget and SF Project Costing, Plan/Budget expenditures General Ledger Projects F6 03 10 03 00 F6-03-10-03-00 03- expenditures and total SF Project Costing, Plan/Budget (revised) budget General Ledger Projects F6 03 11 00 00 F6-03-11-00-00 03. Project budgets are maintained SF Project Costing, PlaNBuciget through budget transactions, General Ledger Projects including description of the transaction. F6 03 12 00 00 F6-03-12-00-00 03. All project budget transactions SF Project Costing, Plan/Budget are posted to a "budget" ledger General Ledger Projects that maintains project budget balances. F4 03 13 00 00 F6-03-13-00-00 03- System provides the ability to SF Project Costing, PlanBudget establish project budgets and General Ledger Projects track/control revenues and expenditures against the budget. F6 03 14 00 00 F6-03-14-00-00 03. System provides the ability to SF Project Costing, PlanBudgel summarize or "rollup" General Ledger Projects expenditures to a higher level for budget checking so that budgets are not required at the lowest level of detail. F6 04 01 00 00 F6-04-01-00-00 04 - Project System provides the ability to SF Project Costing, Billing and accumulate and bill for all Contracts, Funding reimbursable portions of projects. Billing F6 04 02 00 00 F6-04-02-00-00 04 - Project System provides the ability to edit SF Project Costing, Billing and transactions to ensure that Contracts. Funding project billings do not exceed the Billing. General reimbursable budget. Ledger F6 04 03 00 00 F6-04.03-00-00 04 - Project System provides for other means SF Project Costing, Baling and of recognzing revenue that funds Billing, Funding projects (bond funds, grant funds, Receivables, operating transfers) General Ledger F6 04 04 00 00 F6-04-04-00-00 04 - Project System captures developer Billing and contributions as revenue receipts Funding Had to a project F6 04 05 00 00 F6-04-05.00-00 04 - Project System provides the ability to bill Baling and other departments or internal Funding organizational units for services or commodities rendered F6 04 OS 01 00 F6-04-05-01-00 04 - Project Engineer hours are captured Billing and during time and attendance Funding entry to a capital project (as well as other elements of the data classification structure such as a fund) F6 04 05 02 00 F6-04.05-02-00 04 - Project Hours are passed to project Billing and module and billed out to otter Funding departments based on actual cost times an illation factor (percent of actual). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 316 of 418 SF Project Costing, Billing, Receivables, General Ledger SF bmject Costing, Contacts, Billing SF Project Costing, Time 6 Labor, Contracts, Billing SF broject Costing, Time 3 Labor, Contracts, Billing System provides for other means of recognizing revenue that funds projects (bond funds, grant funds, operating transfers) grammar F6 04 05 03 00 F6-04-05-03-00 04 - Project Temporary Services hours are SF Project Costing, Billing and billed out to capital projects Time S labor, Funding based on hours recorded in Contracts. Time and Attendance marked Billing up by a fixed dollar amount per hour. F6 04 06 00 00 F6-04-06-00-00 04 - Project System provides the ability to SF Project Costing, Billing and move funding from one project to General Ledger Funding another. F6 04 07 00 00 F6-04-07-00.00 04 - Project System provides the ability to SF Project Costing, Billing and increase or decrease project General Ledger Funding funding after project is in place. F6 04 08 00 00 F6-04-08.00-00 04 - Project System provides the ability to SF Project Costing, Baling and associate multiple funding General Funding sources to multiple phases within Ledger, Grants, projects. Contracts F6 05 01 00 O0 F6-05-01-00-00 05 - Periodic System generates Construction SF Project Costing, Processing in Progress entries during month Asset end close for expenditures Management incurred during the period F6 05 02 00 00: F6.05-02-00-00 05 - Periodic System allows users to post CIP SF Costing, Processing entries to a different fund than (Project Asset the oriainal expense. Manaoemen[ F6 05 03 00 00 F6-05-03-00.00 05 - Periodic System records allocations of Processing funding to project phases on a periodic basis using the following methodoloales: F6 05 03 01 00 76-05-03-01-00 05 - Periodic Fixed percent per funding SF Project Costing, Processing source Contracts, General Ledger F6 05 03 02 00 F6-05-03-02-00 05 - Periodic Fixed amount per funding SF Project Costing, Processing source Contracts, General Ledger F6 05 03 03 00 F6-05-03-03-00 05 - Periodic Fixed amount per funding SF project Costing, Processing source (up to a fixed amount) Contracts, General Ledger F6 05 03 04 00 F6-05-03-0400 05 - Periodic Based off planned amounts MA Project Costing, MEDIUM This functionality is not Processing Contracts, currently available and IN General Ledger need to be created using PeopleTools. F6 06 01 00 00 F6-06-0 I -DO-00 06 - Close -Out System provides the ability to RO Project Costing LOW identify projects lacking financial activity for a user -defined period for possible closeout F6 OB 02 00 00 F6-06-02-00-00 06 - Close -Out System provides the ability to SF Project Costing, allow the user to specify and Enterprise control the project dosing Portal process through user tables and security. F6 06 03 00 00 F6-06-03.00-00 06 - Close -Out System provides the ability to MI Project Costing MEDIUM support closing multiple projects at once. F6 06 04 00 00 F6-06-04-00-00 06 - Close -Out System provides the ability to SF Project Costing close projects partially (allow revenues but no expenditures) or completely (block all - transactional. F6 06 09 00 00 F6-06-05-00-00 06 - Close -Out System prevents final close for a MI Project Costing MEDIUM project If revenues and expenses are not equal. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 317 of 418 F6 06 06 00 00 F6-06-06-00.00 06 - Close -Out System prevents final close for a MI Project Costing MEDIUM project if estimated revenues and the expenditure budget are not �Gual. F6 06 07 00 00 F6-06-07-00-00 06 - Close -Out System prevents final close for a MI Project Costing MEDIUM project if estimated revenues do not equal actual revenues and the expenditure budget does not equal actual expenditures. F6 06 08 00 00 F6-06-06.00-00 06 - Close -Out System provides the ability for an SF Project Costing l automated procedure to purge and archive data for dosed broiacis. F6 O6 09 00 00 F6.06AM00-00 06 - Close -Out System provides the ability to re- SF Project Costing open a dosed project with proper sewrity. F6 06 10 00 00 F6-06-10-00-00 06 - Close -Out System provides the ability to SF Project Costing dose projects independent of the fiscal veer. F6 06 11 00 00 F6-06-11-00-00 06 - Closa-Out System prevents final dose of a MI Project Costing MEDIUM project If any balance sheet account has a balance. F6 06 12 00 00 F6-06-12-00-00 06 - Close-0ut System prevents final close of a MI Project Costing MEDIUM project if any encumbrances are wtstandi F6 06 13 00 00 F6-06-13-00-00 06 - Close -Out System arows, users to capitalize SF Project Costing, CIP to the asset canned for the Asset project once the asset has been Management placed In service. F6 07 01 00 00 F6-07-01-00-00 07 - Budget System provides the ability for Control project budgetary control options by project budget line as follows: F6 07 01 01 00 F6-07-01-01-00 07 - Budget Absolute control - prevents SF Project Costing, Control transaction from processing, General Ledger may not be overridden F6 07 01 02 00 F6-07-01-02-00 07 - Budget Override Contol - prevents SF Project Costing, Control transaction from processing General Ledger with the ability to override error with appropriate security F6 07 01 03 00 F6-07-01-03.00 07 - Budget Warning — provides warning SF Project Costing, Control message but allows General Ledgerl transaction to brewss F6 07 01 04 00 F6-07-01-04-00 07 - Budget No control — allows SF Project Costing,) l Control transaction to process without General Ledger warning F6 07 02 00 00 F6-07-02-00.00 07 - Budget System provides the option to Control alert user with a flag or warning when appropriated project budget Is overcharged either by overall project, sub -project, one", or job and allows the overcharge only with proper security. F6 07 02 01 00 F6-07-02-01-00 07 - Budget Overall project SF Project Costing, l Control General Ledger F6 07 02 02 00 F6.07.02-02-00 07 - Budget Sub -project SF Project Costing, Control General Ledger F6 07 02 03 00 F6-07-02.03.00 07 - Budget Phase SF brcject Costing, l Control General Ledger F6 07 02 04 00 F6-07-02-04-00 07 - Budget Job SF Project Costing,) l Control General Ledger City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 318 of 418 1 I I I ] I 1 I I I 1 I 1 I I 1 I 1 F F6 07 03 00 00 F6-07-03-00-00 07 - Budget System provides the ability to SF Project Costing, Control establish and track capital General Ledger appropriation budgets at user. defined levels of the financial data classification structure. F6 07 04 00 00 F6-07-04-00.00 07 - Budget System provides the ability to SF Project Costing, System Control optionally generate on-line, user- General Ledger provides the defined warnings when project ability to and phase expenditures optionally approach or exceed the generate on- adjusyted project budget line, user - defined warnings when project and phase expenditures approach or exceed the adjusyted ro'ect bud et. IN ill; AUR._ �awatir. ,,. i4 �':,r!k'�,1„ �• �..:.a, 'r4"�s �wwwuumuiwumuuo - �, ,,.. ,,, s _ F6 08, 01 00 00F6-08-01-00-00 08 - Workflow System provides the ability to MI Project Costing MEDIUM utilize workflow to notify project administrators and other users (at user -defined time periods) of project milestones (expiration dates etc.). F6 08 02 00 00 F6-08-02-00-00 08 - Workflow System provides the ability for SF Project Costing workflow to notify project administrators when a review and/or approval of financial transactions is required. F6 08 03 00 00 F6-08-03-00.00 08 - Workflow System notifies users when SF Project Costing, expenditures are within a user General Ledger specified threshold ofthe project 'i u I. F6 09 Ot 00 00 F6-09-01-00.00 09-Financial System provides the ability to SF Project Costing, Controls establish project accounts to General Ledger record project budgets, pre- encumbrances/encumbrances, expenditures, anticipated revenues, receivables, and recejyis. F6 09 02 00 OQ F6-09-02-00-00 09 -Financial Sys ern provides inception to date SF Project Coding, Controls accounting end budgeting that General Ledger does not require a carry forward each fiscal year of available a DgmDriatidns. F6 09 03 00 00 F6-09-03.00.00 09 - Financial System provides the ability to SF Project Costing, Controls record and maintain data at the General Ledger lowest level of the chart of accounts structure and summarize data through roli-ups to higher levels of the projects hierarchy. F6 09 04 00 00 F6-09-04-00-00 09 - Financial System provides the ability to SF Project Costing, Controls prevent contractors from General Ledger receiving payment prior to certain user -defined criteria being met (e.g., prior to the official start date of the project or until other requirements are met). F6 09 05 00 00 F6-09-05.00-00 09 - Financial System provides the ability to SF Project Costing, Controls allow processing of project- General Ledger related revenue transactions outside of the project service the Project Accounting module to Integrate with other relevant modules, including but not limited to City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 319 of 418 F6 10 01 01 00 F6-10-01-01-00 10 - Integration Budget for capturing project SF Project Costing, budgets and controlling General Ledger expenditures against budget F6 10 01 02 00 F6-10-01-02-00 10 - Integration Procurement for capturing oroiects: F6 10 01 02 01 F6-10-01-02.01 10 - Integration on procurement contracts SF Project Costing, Purchasing F6 10 01 02 02 F6-10-01-02-02 10 - Integration on encumbrances SF Project Costing, Purchasing, General Ledger F6 10 01 02 03 F6-10-01-02-03 10 - Integration on retainage balances for RQ Project Costing, MEDIUM vendors Purchasing, Payables FG 10 01 03 00 F6.10-01-03-00 10 - Integration Accounts Receivable for SF Project Costing, capturing project receivables Receivables F6 10 01 04 00 176-10-01-04-00 10 - Integration Asset Management for Integrating in: F6 10 01 04 01 F6-10-01-04-01 10 - Integration capturing CIP SF Project Costing, Asset F6 10 01 04 02 F6-10-01-04-02 10 - Integration establishing assets as they SF ManagflJ�nt Project L`osUng, are placed in service Asset Management F6 10 01 05 00 F6-10-01-05-00 10 - Integration Accounts Payable for captugnq F6 10 Ot 05 07 F6-10-01-05-01 10 -Integratlon vendor invoices related to SF Project Costing, projects Payables F6 10 01 05 02 F6.10-01.0S-02 10 - Integration retainage balances for RD Project Costing, MEDIUM vendors Purchasing, Payables 10 01 06 00 F6.10-01-06.00 10 - Integration Cost Accounting for SF Project Costing, IF6 supporting full project coating General Ledger through indirect cast allocations F6 10 01 07 00 F6-10-01-07-00 10 - Integration Time and Attendance by CaQI rina: F6 10 01 07 01 F6-10-01-07.01 10 - Integration Noun spent on projects SF Project Costing, Time 6 Labor F6 10 01 07 02 F6-10-01-07-02 10 - Integration Payroll expenses for SF Project Costing, projects Time 6 Labor F6 10 01 07 03 F6-10-01-07-03 10 - Integration Hours to bill other SF Project Costing, departments for Time & Labor engineering or temporary F6 10 01 08 00 F6-10-01-08-00 10 - Integratlon services General Ledger SF Project Costing, General Ledger F6 11 01 00 OV F6-11 1-01-00-00- 11 -Reporting System provides reports for SF Pmject Costing, project variance, year-to-date, General Ledger inception -to -date, and user - defined tl nod reporting. F6 11 02 00 00 F6-1-02-00-00 11 -Reporting System prov(des reports for RO Project Costing MEDIUM capital project master date based on user defined parameters (e.g., projects witNn two months of their end date) F6 11 03 00 00 F6-11-03.00-00 11 -Reporting System provides repnns for SF Project Costing, project budget vHrirtnces by dollar General Ledger amount and percentage. F6 11 04 00 00 F6.11-04-00.00 11 -Reporting System provides reports for SF Project Costing, reconciling between Project and General Ledger General Ledger. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 320 of418 Reqt Degree of BAFO CIBER Phase 2A Degree of Num Category Requirement Text Fit Development response Module Fit Response Hours Impacted F1-01- 01 - Budgetary System provides a flag that sets the default SF SF General Y 02-00-00 Control appropriation control option (e.g., absolute, Ledger override, warning, no control) by fund, organization, account and/or other elements of the data classification structure. F1-01- 01 - Budgetary System provides the following budgetary Y 03-00-00 Control control options for departmental budgets: F1-01- 01 - Budgetary Absolute Control - prevents transaction from SF SF General Y 03-01-00 Control processing, may not be overridden Ledger F1-01- 01 - Budgetary Override Control - prevents transaction from SF SF General Y 03-02-00 Control processing with the ability to override error with Ledger appropriate security F1-01- 01 - Budgetary Warning - provides warning message but SF SF General Y 03-03-00 Control allows transaction to process Ledger F1-01- 01 - Budgetary No Control - allows transaction to process SF SF General Y 03-04-00 Control without warning Ledger F1-01- 01 - Budgetary System provides a flag that sets the default SF SF General Y 04-00-00 Control departmental budgetary control option (e.g., Ledger absolute, override, warning, no control) by fund, organization, account and/or other elements of the data classification structure. F1-01- 01 - Budgetary System provides multiple levels of SF SF General Y 05-00-00 Control departmental budgetary control (i.e., absolute, Ledger override, warning, no control) at varying levels of the financial data classification structure's hierarchies (e.g: warning at section level, but absolute at the department level). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 376 of 418 � 1 l 1 � f � ► ! I it 4 � t � A � I � i I i ♦, w q e ng t c m t ab t d t b e 0 h ri id n a n 1 R i Reqt Num Category Re uirement Text City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 375 of 418 Degree of BAFO Phase 2A Fit CIBER Development Module Degree of Response response Hours Fit Impacted MA MA 120 General Y Ledger SF SF General Y Ledger MA MA 200 General Y Ledger SF SF General Y Ledger MA MA 40 General Y Ledger Y SF SF General Y Ledger SF SF General Y Ledger SF SF General Y Ledger SF SF General Y Ledger Table 2: Review Due to Phase IIC: Procurement and Inventory Option Degree of BAFO Phase 2A Reqt Num Category Requirement Text Fit CIBER Development response Module Degree of Fit Response Hours Impacted F1-00- 00 - Data System provides the ability to maintain all SF SF General Y 03-00-00 Classification revenue and expenditure transactions at the Ledger lowest level of the financial data classification structure. F1-00- 00 - Data System provides security that restricts SF SF General Y 07-00-00 Classification maintenance of FDCS values to authorized Ledger users. F1-00- 00 - Data System allows financial data classification field SF SF General Y 08-00-00 Classification lengths to be configured. Ledger F1-00- 00 - Data System permits all financial data classification SF SF General Y 10-00-00 Classification elements to be added or changed to an active Ledger or inactive status by authorized users. F1-00- 00 - Data System uses effective dating when adding, SF SF General Y 11-00-00 Classification changing, or deactivating any element of the Ledger financial data classification structure and validates entries based upon the effective date. F1-00- 00 - Data System provides coding reduction techniques SF SF General Y 12-00-00 Classification or tools to reduce the amount of data entry Ledger required on a transaction. F1-00- 00 - Data A coding reduction value or code references SF SF General Y 12-01-00 Classification specific user -defined combinations of any Ledger element of the financial data classification structure. F1-00- 00 - Data Data entry of this specific coding reduction SF SF General Y 12-02-00 Classification value on a transaction can infer or "look up" the Ledger combination of elements instead of requiring data entry of each of these elements on the transaction. City of Fort Worth) CIBER, Inc. Professional Services Agreement Page 374 of 418 0 I 1 I 1 1 1 1 1 1 f I I IM 06 05 00 00 IM-p6 05-00-00 06 - Physical Inventories System provides the ability to generate random item lists for performing SF Inventory random Physical inventories. IM 06 06 00 00 IM-O6-06-00.00 06 - Physical Inventories System provides the ability to enter physical inventory data online with SF Inventory g oo securjpj anQ anpr�yals. IM 06 07 00 06 IM-06-07-00-00 06 - Physical Inventories System provides ♦fie abll iy to separate the Inventory count and SF Inventory l reconciliation process to prevent the same user from counting and IM 06 08 06 0d IM-06-08-00.00 06 -Physical Inventories reconeilino inventoJv System provides the ability to Yreeze` the perpetual balances of an item at SF Inventory the time the Item Is selected for cycle counts, spot checks or physical inventory. IM 06 09 00 00 IM-06-D9-00.00 06 - Physical Inventories System provides the ability to 'freeze" by location including row in a SF Inventory • warehouse. IM 06 10 00 00 IM-06-10-00.00 06 - Physical Inventories System provides the ability to calculate deviation between "frozen" and SF Inventory counted auanUbes. IM 06 11 00 00 IM-06-11-00-00 06 - Physical Inventories System provides the ability to make appropriate adjusting entries for SF Inventory deviations between "frozen" inventory and counted quantities. IM 06 12 00 00 1M-06-12-00-00 06 - Physical Inventories System provides the ability to enter physical count data from count sheets SF Inventory land compare the physical count amounts to the quantity on hand, and l l calculate variances. IM 06 13 00 00 IM-06-13.00.00 06 - Physical Inventories System provides the ability to create physical inventory reports, including (the followl��}}��aa: IM 06 13 01 00 IM-06-13-01-00 06 - P sical Inventories report pfyuantity variances I I Excegsical SF I Inventory Inventories I In tEn: e th value variance SF IM O6 13 03 00 IM-06-133.03.00 O6 - Physical Inventories I Reconory tlatl g SF I Invent ry IM 06 14 00 00 IM-06-14-00.00 06 - Physical Inventories (System provides the ability to automatically calculate the next cycle count I SF I Inventory date for each commodi based on user defined�y�((Iles. IM 06 15 00 00 IM-06-15-00-00 06 - Physical Inventories (System provides the ability to generate a book-fo-physical adjustment ( SF I Inventory IM 06 16 00 00 IM-06-16-00-00 06 - Physical Inventories trenS,action q{ce ys`'q�I Inventory counts rq determined. System provides a ability to generate an�pdnI cycle count, spot check and physcal Inventory worksheets including, but not limited to the ( l following: IM 06 16 01 00 1M-O6-16-01-00 O6 • Inventories I Item number SF I Inventory IM 06 16 02 00 IM-06-16-02-00 06 - PP �Ysical vsical Inventories I Alternate item codes (SKU, UPC, etc.) SF I Inventory IM 06 16 03 00 IM•06-16-03-00 06 - P vsical Inventories I Manufacturer's o rt number SF I Inventory IMI 06 161 041 00 IM-O6-16-04-001 06 - Physical Inventones I Distributor's number I MI I Inventory I IMI 06 161 051 00 IM-06-16-05-001 06- Physical inventories I DescnPtion I SF 1 Inventory I IMI 06 161 061 00 IM-O6-16-06-001 06- Phvslcal Inventories I Primary Location I SF I Inventory I IMI 06 161 071 00 IM-06-16-07-001 06 - Phvslcal Inventories I Seoondaaj�Vv Location (s) I SF I Inventory I IMI 06 161 081 00 IM-06-16-08-001 06- Physical Inventories I Unit of Massure I MI I Inventory IMI 06 171 OOI 00 )M-06-17-00-001 06 - Physical Inventories provides the ability to perform the physical count and reconciliation SF Inventory (System Qror�ss on dPlnapd. I I IM 06 18 00 00 IM-06-18-00-00 06 - Physical Inventories ys em provides for inventories that are identified as obsolete, SF Inventory discontinued, damaged or otherwise un-Issuable to be removed from inventory, with appropriate accounting entries posted to the general ledger. IM 07 Y Idl61�V�i'i 01 tlVJV�a OOII ��i00 diYi IM-07-01-00-00 07 - Reporting System provides the ability to maintain a central inventory listing and SF Inventory generate raprts from IM 071 02 OOI 00[ IM-07-02-00-00 07 - Reporting provides the ability to generate a report on the value of warehouse SF Inventory (System stock. I IM 071 03 001 00 �M-07-03-00-00 07 • Reporting (System provides the ability to generate transfer twtransfer from reports. SF I Inventory IM 07 04 001 00 IM-07-04-00-00 07 - Reporting (System provides the ability to generate a report on required spare RQ Inventory (inventory �arts�q crp�9 reference substitute Parts and eouiorn(� t. IMI 07 061 OOI OOI IM-07-05-00.00I 07 - Reporting Ibystem provides the atto generate a physical inventory worksheet to I SF Inventory be sorted by user defined criteria. IMI 07 061 OOI 001 IM-07-O6-00-OOI 07 • Reporting allows user to designate whether zero quantity items are Included SF Inventory (System I on the ohvsiraj ir�vanto/y111 IMI 07 071 00 001 IM-07-07-00.001 07 - RepoRi a r 0 oeeet. (System woy es a iti o generate re arts on warrantie I RQ Inventory IMI 07 08 001 001 IM-07-O8-0DO-00l 07 - Reporting provides the obi dy to generate a c reports on ac we/inactive RO Inventory i lSystem Inventory records with various calculations defined by department criteria. l IMI 07 091 00 OOI IM-07-09-00-00I 07 - Reporting System provides the ability to generate a report on inventory value and/or SF Inventory expanse attIrerr vgnpys time periods I IMI 07 101 00 00 IM-07-10-00-00 07 -Reporting System providdes a abrll to track and report on inventory funded by RQ Inventory l grants separately than inventory funded by operating funds in the same location. IM 07 111 00 OOl IM-07-11-00-00 07 - Reporting System provides the ability to create a report, by user defined criteria, that RO Inventory l will "how non -Inventory Items received to help determine whether they should be Inventoried. M 07 121 00 OOI)M•07.12-00-00 07 - Reporting System provides the ability to generate adhoc reports on any item RQ Inventory Information fieid and any transaction data fetid. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 373 of 418 l LOW LOW LOW LOW LOW LOW LOW LOW IM 05 01 00 00 IM-05-01-00-00 05 - Transaction Processing System provides the ability to reverse, cancel, or reject any stock SF Inventory reouisition. IM 05 02 00 00 IM-05-02-00-00 05- Transaction Processing System provides on-line inventory adjustment capabilities. SF Inventory IM 05 03 00 00 IM-05-03-00.Od 05 - Transaction Processing System provides the ability to automatically update inventory balances and SF Inventory order status at the time of transaction entry. IM 05 04 00 00 IM-05-04-00.00 05 - Transaction Processing System provides the ability to adjust the following balances online for all SF Inventory types of inventory transactions: number of units, unit cost and inventory iM 65 OS o0 dollar balance with aapr rate accountina entries. 06 IM-o5-o5-0o-0o 05 - Transaction Processing System provides the ability to maintain an audit trail for inventory transactions including. but not limited to the following: IM 06 05 01 00 IM-05-05-01-00 05 - Transaction Processing User Id SF Inventory IM 06 05 02 00 IM-05-05-02-00 05- Transaction Processing Warehouse SF Inventory IM 06 05 06 00 IM-05-05-03-00 05 - Transaction Processing Item number SF Inventory IM 06 05 04 00 IM-05-05-04-00 05- Transaction Processing Quantity SF Inventory IM 05 05 06 00 IM-05-05-05-00 05 - Transaction Processing Unit of Measure SF Inventory IM 05 05 06 00 IM-05-05-06-00 05 - Transaction Processing Issuance Location (as defined by the hierarchy fisted above) SF Inventory IM 06 05 07 00 IM-05-05-07-00 05 - Transaction Processing Equipment Number (e.g., for gas issued from a tank to a vehicle for SF Inventory subsequent I terdeoartmontal billino). IM 05 05 08 00 IM-O5-05-08-06 05 - Transaction Processing Transaction pe SF Inventory IM 06 05 09 00 IM-05-05-09-00 OS - Transaction Processing Date SF Inventory IM 05 05 10 00 IM-05-05-10-00 05- Transaction Processing Time SF Inventory IM 06 09 11 00 IM-05-05.11-00 05 - Transaction Processing Document number SF Inventory IM OS dS 12 00 IM-05-05-12-00 05 - Transaction Processing All elements of the financial data classification structure SF Inventory IM 0$ 06 00 00 IM-05-06-00-00 05 - Transaction Processing System provides the ability to automatically update inventory on -order SF Inventory information at the time a pumhase order is released. IM 06 07 00 00 IM-05-07-00-00 05 - Transaction Processing System provides the :beto automatically update allocated inventory SF Inventory when stock re uest is received. IM 05 08 00 00 IM-05-08.00-00 05 - Transaction Processing System provides the ability to issue an item and identify it to a specific SF Inventory grant, program, project, contract, or other elements in the financial data classification structure. IM 05 09 00 00 IM-05-09-00-00 05 - Transaction Processing System provides the ability to charge restocking fee to the requesting MA Inventory, Billing MEDIUM This requires customer setup department for all or some of the items returned to inventory. and restocking fees to be applied and billed within Order Management. However, due to limited requirements, this was marked as a modification in lieu of Including Order Management. IM 05 16 00 00 IM-05-10-00-00 05 - Transaction Processing System supports maintenance of inventories for liquids such as gas managed in suo rt of fleet: IM 05 10 01 00 IM-05-10-01-00 05 - Transaction Processing receiving info a special location 11. a tank SF Inventory IM 05 10 02 00 IM-05-10-02-00 05 - Transaction Processing issuing out to a vehicle SF Inventory IM 05 10 03 00 IM-05-10-03-00 05 - Transaction Processing determining the appropriate expense account for that issuance based SF Inventory IM 05 10 04 off a default accougtim ripnment for the vehicle 00 IM-05-10-04-00 05 - Transaction Processing recording revenue from the issuance for the internal service fund that SF Inventory maintains the gas inventories. IM 05 10 05 00 IM-05-10-05-00 05 - Transaction Processing calculating the cost of the goods issued based on the weighted SF Inventory avers cost of the fuel in the tank. IM' 06 01 00 00 IM-06-01-00-00 O6 - Physical Inventories System provides the ability to accommodate automatic scheduling for all SF Inventory �'°�s of Dh%sical t ver�to nth s. IM 06 02 00 00 IM-06-02-00-00 06 - Physical Inventories System provides the abiii to se ect and sequence physical inventory, SF Inventory cycle count and spot check documents (e.g., slocklbin location order). IM 06 03 00 00 IM-06-03-00-00 06 - Physical Inventories System provides the ability to perform cycle counts and/or spot checks of SF Inventory Items by wet ht. I)um)�� In I units of measure. IM O6 04 oo 0o IM-06-04-00-00 06 - Physical Inventories System proves the abtl fo physical inventory, cycle counts and spot yhec on demand by: IM 06 04 01 00 IM-O6-04-01-00 06- Physical Inventories Item SF Inventory I IM 06 04 02 00 IM-06-04-02-00 06 - Physical Inventories GrouD SF Inventory IM 06 04 03 00 IM-06-04-03-00 06 - Physical Inventories Class SF Inventory l IM 06 o4 o4 00 IM-06-04-04-00 06- Physical Inventories Location SF Inventory City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 372 of 418 I 1 I 1 4 1 1 1 1 11 1 1 1 1 1 1 [ # IM 03 01 00 W IM-03-01-00-00 03 - Stock Issuance System provides the ability to create pick tickets based on requisitions from SF Inventory Inventory, either in batch or real-time. IM 03 02 00 00 IM-03-02-00-00 03 - Stock Issuance System provides the ability to generate pick tickets at preschedulad times. SF Inventory IM 03 03 00 00 IM-03-03-00.00 03 - Stock Issuance System provides the ability to bundle items into "groups' or "kits". A group SF Inventory or kit consists of items which are always issued together. IM 03 04 00 00 IM-03-04-00.00 03 - Stock Issuance System provides the ability to place a cap on the quantity and dollar MA Inventory MEDIUM You can setup internal amount of an Item that can be issued to a requester during a specified time requestors as customers and period. limit the dollar value with a credit limit. There is no restriction on quantity however. IM 03 05 00 00 IM-03-05-00-00 03 - Stock Issuance System provides the ability to override caps on items, with proper authority. MA Inventory MEDIUM Credit limits restraints can be IM 03 06 00 00 IM-03.06-00-00 03 - Stock Issuance IM 03 07 00 00 IM-03.07-00-00 03 - Stock Issuance IM 03 081 001 00 IM-03-08-00-00 03 - Stock Issuance IM 03 09 00 00 IM-03-09.00-00 03 - Stock Issuance IM 03 10 00 00 IM-03-10-00-00 03 - Stock Issuance IMI 031 11 001 001 IM-03-1 1-00-001 03 - Stock Issuance IMI 031 121 001 001 IM-03-12-00-001 03 - Stock Issuance IMI 03 131 OOI 001 IM-03-13-00-001 03 - Stock Issuance IMI 031 141 001 00 IM-03-14-00-001 03 - Stock Issuance IMI 031 151 001 00 IM-03-15-00-00I 03 - Stock Issuance IMI 031 161 001 00 IM-03-16-00-001 03 - Stock Issuance IMI 03 17 001 00 IM-03-17-00-001 03 - Stock Issuance IM 03 18 00 001 IM-03-18-00-00 03 - Stock Issuance IMI 03 19 00 00 IM-03-19-00.00 03 - Stock Issuance IM 03 20 00 00 IM-03.20-00.00 03 - Stock Issuance �111,11 I.I:iI d�1L�ii1'' 91 IM 04 01 00 00 IM-04-01-00-00 04 - Reordering IIM 04I 021 001 00 IM-04-02-00-001 04 - Reordering IIM 041 031 001 00 IM-04-03-00-00I 04 - Reordering I IM 041 05 001 00 iM-04-05-00-001 04 - Reordedjfa IIMI 04I 06 00 00 IM-04-06-DO-00 04-Reordering IIMI 04 07 00 001 IM-04-07-00.00 04- Reordering IM 04 08 00 001 IM-04-08-00-00 04 - Reordering IM 04 09 00 00 IM-04-09-00.00 04 -Reordering IM 04 10 00 00 IM-04-10-00.00 04 - Reordering City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 371 of 418 System provides the ability to print a'deliver to" address on pick tickets from requisition information. System provides the ability to issue items at a certain cost and credit the Item back (if returned) at the issue cost from the original transaction. This feature should be the default regardless of inventory costing method used i.e., avemae costtLIFO FIFO. etc-1 System provides" ability to issue items to locations internal to the warehouse such as a module or floor location. System provides the ability to track and differentiate between warehouse order quantities (I.e., case) and inventory issue quantities (i.e., box, when there are 12 boxes in a case). System provides the ability to differentiate between supply items and logistic Items. (Coat of logistic items issued to organizational units are not charged to units. Logistics costs remain centralized but must be tracked to units.). An example of this would be street barricades in which the barricades are lent out and their issue location is tracked, but their costs remain centralized. (System provides the ability to retain requisition information as to what is ordered from warehouses. System provides the ability to process emergency issues (i.e., deduct anything shipped from on -hand stock Immediately and print a receipt for shiomem to the rgyyestor). tlystem provides fhe ability to compare stock Items received to open requests for stock items to determine wNch requests (i.e.. backorders) max be filled. System provides the ability to report the frequency that items are placed onI backorder. System provides the ability to record a comment regarding back -order information. System provides the ability to record anticipated delivery date for back- I ordered items and notify users wgqon dplivgry date is imminent. System provides the lity to perlorn backorder processing with manual or automatic release or cancellations, and notification sent to requester. (System tracks issuance of stock back to the requester (e.g., system provides en audit bail of fire uniform items Issued to individual for both (ra nt-ty and dates Issued. System provides integration with the payroll system to generate a payroll deduction when Issuing items such as extra uniforms to employees. System provides the ablldy to produce a'put' (return -to -stock) ticket which will contain �enbal reference number. .. r,u�..i�y��rwYftifikw�rllWPih+�irtiWY��Ltvttrl6N."Llllotp) System provides the ability to automatically recommend reorder Yor user defined stock' items, mcludt(�o ele�pic request and aooroval. (System provides the ability to track item usage and generate reorders automatically based on item use��g and/or defined ordering schedules. (System provides the ability to tleiine, by item, the variables used in derryryrmininq rPlor @,r oo/p)s and reorder quantities. Svskam orovlcies t e ablli�' Ip rfqrrp reorder-ooit calculation. �ystem provides the ability fo take rate account on -hand and on -order ]amounts alo0 with receipts during the reordepnq fo4�its. I (System provides the ability to generate an online I�t of commodities to reorder and be able to select items from this list to requisition. (System provides the ability to allow manual overrides of reorder points and reorder quantities. System provides the ability to automatically notify personnel before the item or lot will exQ�re. (ystem provides the ability to allow each warehouse location to automatically generate a reorder either to procurement or the central warehouse on item -by -item basis. SF Inventory SF Inventory SF I Inventory SF Inventory SF Inventory SF I Inventory SF Inventory SF inventory RQ I Inventory i MI I Inventory LOW MI I Inventory LOW I MI Inventory LOW SF Inventory NA SF Inventory SF SF SF SF SF SF RQ SF Inventory Inventory Inventory nvenllpry Inventory Inventory Inventory Inventory Inventory LOW overridden with proper security IM 01 09 00 00 IM-01-09-00-00 01 - Inventory Accounting System provides the ability to maintain inventory control accounts (or SF Inventory central stock accounts) as defined by users. IM 01 10 00 00 IM-01-10-00-00 01 -Inventory Accounting System provides the ability to accommodate a multilevel location structure. to include. but not limited to: IM 01 10 01 00 IM-01-10-01-00 01 - Invent] ry Accounto Department SF Inventory I IM 01 10 02 00 IM-01-10-02-00 Oi - Invenf➢1v Accoun( no Warehouse (for example • central suopJyj SF Inventory I IM 01 t0 03 00 IM-01-10-03-00 01 - Inve ory Accountino Storaae area (for example - 2nd floor f`J{A! quadrant) SF Inventory I IM 01 10 04 00 IM-01-10-04-00 01- Inventory Accountinq Aisle SF Inventory I IM 01 10 05 00 IM-01-10-05-00 01 - Inventory AccountinPn Rack SF Inventory I IM 01 10 06 00 IM-01-10-06-00 01 - Invent vv Accound�ro Shelf SF Inventory I IM 01 10 07 06 IM-01-10-07-00 01 - Inventory Accountna Bin SF Inventory 1 IM 01 10 08 00 IM-01.10-08-00 01 - Inventory Accountino Cart SF Inventory I IM I M 01 01 10 10 09 09 00 IM-01-10-09-00 00 IM-01-10-09-00 01 - Inverl{{Pry Accarn " a 01 - InventpN Aecouro Tank EmoiOy�a SF SF Inven( flyv nveni0ry I IM 01 10 10 00 IM-01-10-10.00 01 - inventfppry AccounttPo Truckle (or temppo e y assianed invenlyv items/ SF nven vyy IM 01 11 00 00 IM-01-11-00-00 01 - Inventory Accounting System provides the ability to allow transfers of stock items from project to SF Inven(ory project, between cost centers, among divisiona, and among warehouses with corre5a47)di�1(� ag4i{ion an depletion Ii Ares. IM 01 12 00 00 1M-01-12-00-00 01 - Inventory Accounting System provides the abtli{y to a�locate purc7ases and stock to various SF Inventory departments, divisions, warehouses, section of warehouse, cost center, etc. I.e.. droj� shippinyy` IM 01 13 00 00 IM-01-13-00-06 01 - InventoryAccounting Sys am provides the aity to maintain an unlimited number of separate SF Inventory storerooms for each individual department. IM Of 14 00 00 IM-01-14-00-00 01 - Inventory Accounting System provides the ability to record primary and multiple secondary SF Inventory locations of stocked Items. IM 01 15 00 00 IM-01-15-00-00 01 - Inventory Accounting System provides the ability to indicate stock on hand by each location or SF _ Inventory muitiole locations. I IM 01 16 DO 00 IM-01-16-00-00 01 - Inventory Accountina Svs{em orovjd�9 the abil' to rfortn lot expiration tracking SF Inventory IM 01 17 00 00 IM-01-17-00-00 01 •Inventory Accounting �yslem provides the ability to Aag inventoryi)ems to preveI future 5F Inventory IM 01 18 00 00 IM-01.18-00-00 01 - Inventory Accounting iparchas69. System provides the ability to define default warehouse views for users MA Inventory (i.e., users are restricted to using certain warehouses based on deQ�rtment. etc. IM 01 19 00 00 IM-01-19-00.00 01 - Inventory Accounting System provides a ability to allow users to specify a mark-up or overhead SF Inventory cost for each individual inventory item or commodity code grouping. IM Of 20 00 00 IM-01-20-00-00 01 - Inventory Accounting System provides the ability to allocate the cost of Inventory, based on SF Inventory markup If ap((I' ble, back to the reouestigpp entity. IM 01 21 00 00 IM-01-21-00-00 01 - Inventory Accounting System provides the ability to support the following inventory costing methods by departments and/or inventory warehouse: I IM Of 21 01 00 IM-01-21-01-00 01 - Invenr Accounting Actua) Cost SF Inventory I IM 01 21 02 00 IM-01-21-02-00 01 - Inven ory Accountinq LIFO SF Inventory 1 IM 01 21 03 00 IM-01-21-03-00 01- Inventory Accounting FIFO SF Inventory I IM 01 21 04 00 IM-01-21-04-00 01 - Inventoprvry Account Averaae cost SF Inventory I IM 01 21 05 00 IM-01-21-05-00 01- Inventory Accounting Reglacemenl cost NA I IM 0'( 21 06 00 IM-01-21-06.00 01- Inventory Accountinq Wewhted Average SF Inventory IM 01 22 00 00 IM-01-22-00-00 01 -Inventory Accounting System provides the ability to automatically adjust item costs in the SF Inventory inventory system based upon adjustments mado in accounts payable s stem. IM 02 Ot 00 00 IM-02-01-00-00 02 - Goods Receipt System provides the ability to receipt into inventory, partial or complete, by SF Inventory, Purchasing IM 02 02 00 00 IM-02-02-00-00 02 Goods Receipt line item as well as the 4 Gf purchase� �r�fer. System �o have - provides the ably multiple receipts against each line item. SF Inventory, Purchasing IM 02 03 00 00 IM-02-03.00.00 02 • Goods Receipt System provides the ability to dose out an item not completely received. SF Inventory, Purchasing IM 02 04 00 00 IM-02-04-00-00 02 - Goods Receipt System provides the ability to receive over -shipments with the over- SF Inventory, Purchasing shipment amount subject to a user -defined tolerance setting (e.g., a oertr� ntaae or dollar amount). IM 02 05 00 00 IM-02-05-00-00 02 - Goods Receipt VQ�a^� System provides the ability to automatically generate returns to vendors for SF Inventory, Purchasing items that do Apt VDopss 1' $ irion. 1 IM 02 06 06 00 IM-02-06-00-00 02 - Goods Receipt System provides tFa abrilily to reverse a receipt en^, SF Inventory\Purchasina IM 02 07 00 00 IM-02-07-00-00 02 - Goods Receipt System provides the abilty to populate the receiving Information with SF Inventory, Purchasing appropriate data ( to reduce data entry) after the receiver references the �turchase order. IM 02 08 00 00 IM-02-08.00-00 02 • Goods Receipt System provides the ability to automatically update open purchase order SF Inventory, Purchasing status and balances at time of receipt into inventory. IM 02 09 00 00 IM-02-09-00.00 02 - Goods Receipt System provides the ability to automatically update inventory on -hand and SF Inventory, Purchasing on -order when ite�ls ayg�)3rjved for inventory hems, IM 02 10 00 00 tM-02-10-00.00 02 •Goods Receipt System provides the a city o receive items and not have them available SF Inventory, Purchasing ((,o,r CCyyssumo'ippn (@@ 1.\\received into i tlonl. IM 02 11 00 00 IM-02-11-00-00 02 - Goods Receipt Sys(am provides the ability to capture t c manufacturers stock item 5F Inventory, Purchasing description or distributor's number for each detail line on the receiver documents. IM 01 12 00 00 IM-02-12-00-00 02 - Goods Recelpt System provides the ability to perform an edit check for receipt SF Inventory, Purchasing tire niactio��S,s againstyyurchase order. location and unit of measure. IM 01 13 00 00 IM-02-13-00-00 02 - Goods Receipt System allows receipts of goods into inventory from donations, with SF Inventory, Purchasing appropriate accounting entries. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 370 of 418 1 1 I I I I I 1 1 4 1 1 LOW This would require row -level security to be enabled. I IM 00 17 00 00 IM-00-17-00-00 00- General Requirements System provides the ability to maintain a history of part numbers if the SF Inventory ` manufacturer's p nu �y` changes. I IM 00 18 00 00 IM-00-18-00.00 00 -General Requirements System provides a abilityy lO pro duce a hard copy stock taa. SF Inventory IM 00 19 00 00 IM-00-19.OD-00 00 - General Requirements System provides the ability to accommodate items with zero dollar value SF Inventory and/or zero quantity. IM 00 20 00 00 IM-00-20-00-00 00 - General Requirements System provides the ability to associate requirements for rotating stock for SF Inventory an item. I IM 00 21 00 00 IM-00-21-00-00 00 -General Requirements System provides the ability to associate requirements for managing items SF Inventory in inventory such as reF(ul�.r/namtenapc� stems. IM 00 22 00 06 IM-00-22-00-00 00 - General Requirements System provides the a lllty o suppoorrtt a ectronrc approval for goods MI Inventory receipts, issues, and other related inventory functions. IM 00 23 00 00 IM-00-23-00-00 00 - General Requirements System provides the ability to perform quantity unit of measure conversions (e.g., 4 boxes = 48 units, conversion of pounds of 12 gauge Insulated copr wire into feet of wire etc.). IM 00 24 00 00 IM-00-24-00-00 00 - General Requirements System provides the ability to automatically tarty an Rem code forward from an electronic catalog to a transaction being initiated by a user. IM 00 25 00 00 IM-00-25-00-00 00 - General Requirements System provides the ability to accommodate a free -form character field available for describing special handling requirements, Including but not limited to: IM od 25 01 00 IM-00-25-01-00 00 - General Requirements It do ladeI classTcation IM 00 25 02 00 IM-00-25-02-00 00 - General Requirements sfor 1'�Qp fements IM 00 25 03 00 IM-00-25-03-00 00 - General Reauirements sp- General Requirements�ecc a101 inn reyttirements IM 00 25 04 00 IM-00-25-04-00 IM 00 25 05 00 IM-00-25-05-00 00 - General Requirements is (Ill restnstru`lome ons for handling and disposal IM 00 25 06 00 IM-00-25.06.00 00 - General Requirements re reQ} a're(�1 IM 00 26 00 00 IM-00-26-00-00 00 - General Requirements Sys(em provides fhea biilly to assign a reason code for stock adjustments: IM 00 26 01 00 IM-00-26-01-00 00 - General Requirements Defective IM 00 26 02 00 IM-00-26-02-00 00 - General Requirements E�plred IM 00 26 03 00 IM-00-26-03-00 00 - General Requirements Stolen I IM 00 261 04 00 IM-00-26-04-00 00 - General Requirements Spoiled I IM 00 261 05 OOI)M-00-26-05-00 00 - General Requirements Damaged I IM 00 261 06 00 IM-00-26-06-00 00 - General Requirements Give- wDys or promoy' s I IM 00 261 07 001 IM-00-26-07-00 00 - General Requirements Physical (nventory adl�ment IM 00 261 08 001 IM-00-26-08.00 00 - General Requirements Other I IM 00 27 00 00 IM-00-27-00-00 00 - General Requirements System provides the ability to search other locations! departments and show which have the Rem when a stock -out Is experienced for an item. IM 00 28 00 001 IM-00-28-00-00 00 - General Requirements System provides the ability to attach hypedinks on the inventory item records (i.e., items with hazardous material indicators linked to the MSDS). IM 00 291 00 001 IM-00-29-00-00 00 - General Requirements System provides the ability to crack and report on what freight/shipping or other Item related costs are as a part of the total Item costs, but maintained separately. IM 00 30 00 001 IM-00-30-00-00 00 - General Requirements tystem provides the ability to have multiple ship -to sites with the same address location. IM 00 31 00 001 IM-00-31-00A0 00 - General Requirements System calculates unit price for inventoried items that exclude ancillary costs such as Core costs. 1 ernury ncu°unung Pr.v°uea u,e sunny w auyyu° ­nera, _.tier a.wu°,u.y ,w inventory by 'purchase' method (expensed when purchased and operating I.Y.— budget reduced when paid) as assigned by Individual inventory location. IM 01 021 001 001 IM-01-02-00-00 01 - Inventory Accounting System provides the ability to support General Ledger accounting for inventory by "consumption" method (unit cost expensed and operating budget reduced at the time of issue ) as assigned by Individual Inventory location. IM 01 031 001 001 IM-01-03-00-00 01 -Inventory Accounting (System allows the expense method to differ by specific inventory or item. IM 01 041 001 001 IM-01-04-00-00 01 - Inventory Accounting ISystom supports definition of differing accounting methods by fund type _ governmental vs, pro rietary). IM 01 05 00 00 IM-01-05-00-00 01 - inventory Accounting ystem provides the ability to automatically reverse accounting and (inventory transactions when an order is cancelled and goods have not been received from a vendor. IM 01 061 00 001 IM-01-06-00-00 01 - Inventory Accounting (System provides the ability to automatically reverse accounting and IM 01 07 00 00 IM-01-07-00-00 inventory trelt�agftI ss yyf( prI an order is returned afar being issued. 01 - Inventory Accounting System provides Nta abi illy (O automadwllyreverse accounting and /inventory transactions when an order is partially received and the oustandina purchase order balance is cancelled. IM 01I 081 00 001 IM-01-08-00-00 01 -Inventory Accounting provides the ability to assign user -defined expenditure accounts, (System by default, to transactions based on commodity code, account code, and transaction type (with override capability only with appropriate security). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 369 of418 SF Inventory SF Inventory SF Inventory SF Inventory SF Inventory SF Inventory SF Inventory SF inventory SF Inventory SF Inventory SF Inventory SF Inventory SF Inventory SF Inventory SF Inventory SF Inventory SF Inventory MA Inventory SF Inventory SF Inventory SF Inventory SF Inventory SF I Inventory SF I Inventory SF I Inventory SF Inventory SF Inventory SF I Inventory SF I Inventory MEDIUM This is not standard functionality but could be added with the use of the toolset MEDIUM This would require a customization to integrate a document system with Inventory item records Notes: aoViliku,11111111Y11:111111kiiI1,1111111 I I l'id I I III 1611111111111iJ111116 IM 00 Ot 00 IM-00-01-00-00 00 -General Requirements System provides the ability to establish, maintain, adjust and delete SF Inventory invenlory sto tte�n rasp m real-time. IM 00 02 00 00 IM-00-02-00-00 00 - General Requirements System prov' es the abl i to update stock item data, including but not limited to: IM 00 02 01 00 IM-00-02-01-00 00 - General Requirements Returns SF Inventory IM 00 02 02 00 IM-00-02-02-00 00 -Gen eral Requirements Adiustments SF Inventory IM 00 02 03 00 IM-00-02-03-00 00 - General Requirements Transfers SF inventory IM 00 02 t)4 00 IM-00-02-04-00 00 - General Requirements Recaiptp SF Inventoyry IM 00 02 05 00 IM-00-02-05-00 00 - General Requirements Requisitions SF lnvenfory IM 00 02 06 00 IM-00-02-06-00 00 - General Requirements Issuapre of inventory SF Inventory IM (16 02 07 00 IM-00-02-07-00 00- General Requirements Recalls SF Inventory IM 00 02 08 00 IM-00-02-08-00 00- General R, ulrements DisQPsals SF Inventory I IM 00 02 09 00 IM-00-02-09-00 00 - General Requirements Backorders SF Inventory I IM 00 02 10 00 IM-00-02-10-00 00 - General Requirements Reservations SF Inventory IM 00 02 11 00 IM-00-02-1 "0 00 - General Requirements Balance on hand SF Inventory IM 00 03 00 00 IM-00-03-00.00 00 - General Requirements System provides the ability to support the use of bar-coding/Radio Frequency Identification RFID) technology as follows: IM 00 03 01 00 IM-00-03-01-00 00 - General Requirements Provide a pre -defined Interface to accept and remrd bar-coded/RFID TP LOW Inventory is capable of data from receiving documents and shipments accepting transactions from a 3rd-party barcode transactional system. IM 00 03 02 00 IM-00-03-02-00 00 - General Requirements Ability to recognize SKU and commodity codes via bar-code technology TP LOW Inventory is capable of accepting transactions from a 3rd-party barcode transactional system. IM 00 03 03 00 IM-00-03-03-00 00 - General Requirements Ability to capture product information during inventory picking TP LOW Inventory is capable of accepting transactions from a 3rd-party barcode transactional system. IM 00 03 04 00 IM-00-03.04-00 00 - General Requirements Ability to capture product information when performing physical TP LOW Inventory is capable of inventories. accepting transactions from a 3rd-party barcode transactional system. IM 00 04 00 00 IM-00-04-00.00 00 - General Requirements System provides the ability to classify inventory items by commodity SF Inventory number. IM 00 05 00 00 IM-00-05-00-00 00 - General Requirements System provides the ability to record status of items (e.g., spoiled, SF Inventory IM 00 06 00 cancelled, quarantined damaged/ etc.). 00 IM-00-06-00-00 00 - General Requirements System provides the ability to inlicate items approved for use as SF Inventory substitutes for the original item. IM 00 07 00 00 IM-00-07-00-00 00 - General Requirements System provides the ability to default values for transactions, inferred from SF Inventory transaction type- IM 00 08 00 00 IM-00-08-00-00 00 - General Requirements System provides the ability to track usage statistics on inventory items for SF Inventory user defined in ds. IM 00 09 00 00 IM-00-09-00-00 00 - General Requirements System provides the ability to perform forecasting Rem usage (e.g., SF Inventory seasonal/peak usage. FF��9jJdfj�1r pyg>lli ias\dativery schedules). IM 00 10 00 00 IM-00-10-00-00 00 - General Requirements System provides the abiltty to mainia�n a table of master descriptions to SF inventory ensure common descriptions are used throughout the procurement and intory Drk�c�ss. iM 00 11 00 00 IM-00-1 1 -00-00 00 - General Requirements System provides the ability to perform excess, non-moving inventory SF Inventory and/or obsolete item analyysis and repotting. IM 00 12 00 00 IM-00-12-00.00 00 - General Requirements System provides the abilify to create and route electronic forms for MI Inventory MEDIUM This is not standard approval (e.g., approval notification and reporting for write-off of damaged, functionality but could be non-moving, or obsolete inventory). added with the use of the golset. :M 00 13 00 00 IM-00-13-00-00 00 - Goneral Requirements System provides the ability to maintain an item master and item history. SF Inventory IM 00 14 06 00 IM-00-14-00.00 00 - General Requirements System provides the ability to manage items including multiple numbering SF Inventory nomenclature schemes and gmupirgs (NIGP, UPC, SKU, NAICS, etc.). IM 00 1 S 06 06 IM-00-1 5-00-00 00 - General Requirements System provides the ability to manually Input expiration/spoil date for SF Inventory stocked Items. IM 00 16 00 00 IM-00-16-00-00 00 - General Requirements System provides the ability to track the following fields for each Item in IM o0 16 01 Inventory) including but not limited to: o6 IM-oo-16-01-00 00 - General Requirements Serial number SF Inventory IM 00 16 02 00 IM-00-16-02-00 00 - General Requirements Manufacturer's part number SF Inventyly IM 00 14 03 00 IM-00-16-03-00 W - General Requirements Manufacturer name SF Inven ory IM 00 16 04 00 IM-00-16-04-00 00 - General Requirements Internal q It number (a minimum of 8 alphanumeric characters) SF Inventory IM O6 1G 05 00 IM-00-16-05-00 00 - Genera: Requrements Purchase vs. Stock Kett 'ng Unit SF Inventory I IM O6 16 06 00 IM-00.16-06-00 00 - General Requimmenta Receiving units vs. Issue unifs SF Inventory I IM 00 16 07 00 IM-00-16-07-00 00 - General Requirements Item description SF Inventory I City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 368 of 418 0 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 P3 07 45 00 00 P3-07-45-00-00 13 - P-Card System should allow for review, approval or dispute of transactions via the SF Purchasing internet. P3 07 46 00 06 P3-07-46-00-00 13 - P-Card System should allow default financial data classification structure (FDCS) SF Purchasing assignment with modification allowed. P3 07 47 00 00 P3-07-47-00-00 13 - P-Card SF Purchasing System should allow default financial data classification structure (FDCS) assignment and re-assigqnment of sp�scific P-Cards to P-Card coordinators. P3 07 46 06 00 P3-0736-00-00 13 - P-Card System should allow spiltiting of the line items to multiple financial data SF Purchasing classification structure (FDCS bV Dercent or dollar. P3 07 49 00 00 P3-07-49-00-00 13 - P-Card System should interface with aymentNet application so that Invoices paid MI Purchasing MEDIUM by P-Card do not also post via the PaymentNet application. New integration is reauired. P3 07 50 00 00 P3-0750-00-00 13 - P-Card SF Purchasing System should allow use of an invoice payment via P-Card while allowing CFW the option of stayltl� with Chase's PavfnentRe`aODlication. P3 07 51 0Q 00 P3-07-51-00-00 13 - P-Card System should allow for immediate susD�nsI of P-Card, 24-7. SF Purchasing P3 07 52 00 00 P3-07-52-00-00 13 - P-Card System should allow for both manual and electronic signatures on P-Card ct SF Purchasing recelots. P3 07 53 00 00 P3-0753-00-00 13 - P-Card System should be capable of tracking manual receipts. SF Purchasing I City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 367 of 418 I I P3 07 O» flfl 13 - P-Card It System prov d the abil' for wo w fpf Gird issuance app yals. MI Purchas o FIS 07 09 .flfl�fl�fl 13 - P-Card System prov he orb I b expo conGacE vendors information to the MI Purchasing yes bon jC card, �fyto facilitate authorization strateeies. P3 07 10 00 W P3-07-10-00.00 13- P-Card Sys em prov es the ability to import bank statements, including transaction SF Purchasing detail. I P3 Oj 11 00 01 P3-07-1 1 -00-00 13 - P-Card System provides the:Viit gho�l cards or cardless accounts. SF Purchasing P3 6; 12 00 OC P3-07-12-00-06 13 - P-Card tr System provides the ab(h'ly wo flow bank statements that require review SF Purchasing and the ability to change account assignment information for the line item details. P3 61 11 00 OC P3-07.13-00-00 13 - P-Card System provides the ability to generate accounting documents, including SF Purchasing, Payables the electronic funds transfer to pay the bank and the distribution to charge the poount giypmegt. P3 07 14 00 OC i P3-07-14-00-00 13 - P-Card Sys�em provides Moldy to have users prepare online logs to Include SF Purchasing account distributions. �yqfovat online. P3 07 15 00 00P3-07-15-00-00 13 - P-Card System provides the ability to track purchasing card purchases and items SF Purchasing received by vendor, Item, apiancy. and commodity. P3 07 16 00 0(1 P3-07-16-00-00 13 - P-Card System provides the ability to capture P-card transactions In the system to SF Purchasing, Payables, record expenditures against o (I t General Ledger P3 07 17 00 Of4. P3-07-17-00-00 13 - P-Card System tracks cya5rjd�1*p�urchasersl againstas contract made SF Purchasing �procurer�llm��erJnt h [a urcllase P3 07 16 00 0(1 P3-07-18-00-00 13. P-Card System should support tfte abitrtr y for users kfo apply for P( Cards CD Purchasing online. I P3 07 19 00 O( I P3-07-19-00-00 13 - P-Card System should allow for the activation/disabling of Purchase Cards. SF Purchasing P3 07 20 00 OC 1 P3-07-20-00-00 13 - P-Card SF Purchasing Svstem should allow yI it rr� J credit s ape�Y�ication dhad P3 07 21 00 O(I P3-07-21-00-00 13 - P-Card System should allow f« the o(� defaults, SF Purchasing levels and sp9ndinQ limits. P3 07 22 00 OC; P3-07-22-00-00 13 - P-Card System should be able to load Purchase Card statements from the bank SF Purchasing via n euttortrtl1����ed pro�.g�� P3 07 23 00 OC P3-07-23-00.00 13 - P-Card System should a port f11e ability to map a Purchase Card to GL SF Purchasing accounting data. P3 07' 24 00 0(i P3-07-24-00-00 13 - P-Card System should support the ability to generate an electronic monthly SF Purchasing Purchase Card log for all Purchase Card transactions, including manually entered offline transactions. P3 07 25 00 00 P3-07-25-00-00 13 - P-Card System should support the ability to load and view Purchase Card SF Purchasing stattemeentts online, and match up transactions with Purchase Card gpo�No P3 07 26 00 0C: P3-07-26.OMO 13 - P-Card System should sump abr���tplssue Purchase Card Orders offline SF Purchasing and enter Item into the system after the fact for approval and Purchase Card Iggp. P3 07 27 00 OM P3-07-27-00-00 13 - P-Card System should support the ability to track individual Purchase Card SF Purchasing transactions online by accounting classifications during the month as posted. P3 07 28 00 OC-P3-07-28-00-00 13-P-Card SF Purchasing System should allow Picard Coordinators and Administrators to track Purchase Cardj�yf�ases for all cardholders that they are resr�nsible for. P3 07 29 00 OC- P3-07-29-00-00 13 - P-Card System shouldshow the scenario where the Poard Administra(or or MI eProcurement, Purchasing Corlydina(pf r to P Purchase Card purchases. P3 07 30 00 Ot P3-07-30-00-00 13 - P-Card Vs xgprovrr Sys am should suppo the ability to generate a Purchase Card report by SF Purchasing a jfic account distributions. P3 07 31 00 OC, P3-07-31-00-00 13 - P-Card System should support the ability to generate a Purchase Card report by SF Purchasing card holder. P3 07 32 00 OC P3-07-32-00-00 13 - P-Card System should allow for the reviewing of expenditures by any element of SF Purchasing the Financial Data Classificaflon Structure. I P3 07 33 00 OQ P3-07-33-00-00 13 - P-Card $Vstem should allow for tracking of purchase disputes crime. SF Purchasing P3 07 34 00 do P3-07-34-00-00 13 - P-Card System should capture the comm ty code, where available, with expense SF Purchasing line detail and amount. P3 07 35 00 OC P3-0735-0D-00 13 - P-Card System should contain workflow functionality for the review and approval of SF Purchasing drum codinc. rysfem P3 07 36 00 OC- P3-07.36-00-00 13 - P-Card should be able tpo�export Card data to the Cry Financial SF Purchasing rt, (+Purchase System for P3 07 37 00 00 P3-07-37-00-00 13 - P-Card System should allowlfor fw✓�evel pur2iases to be done entirely in the SF Purchasing Purchase Card system (Pa mentNett. P3 07 38 00 00 P3-07-38-00-00 13 - P-Card System should allow for integration of purchase order related invoice Mi Purchasing transactions to PaymentNet for higher dolla�pumhases. P3 07 39 00 00 P3-07-39-00-00 13 - P-Card System should allow a user to flag Requisitions and POs as Purchase Card SF eProcurement, Purchasing transactions. 1 P3 07 40 00 00 P3.0740-00-00 13 - P-Card System should support the use of Purchase Cards to complete acquisition SF Purchasing actions initiated m the system. P3 07 41 00 00 P3-0741-00-00 13 - P-Card System should support Hie ability to manually enter Purchase Card SF Purchasing out trekyactlops wl out c eating a Purchase Order. P3 07' 42 00 00 P3-0742-00-00 13 - P-Card System allows or of posting date based on transaction date SF Purchasing when interiacln P-Card transactions. P3 07' 43 00 00 P3-0743.00.00 13 - P-Card System should support the ability to use Purchase Cards to perform SF eProcurement, Purchasing catalog purchasing from online catalogs when available. P3 07 44 00 00 P3-07.44-00-00 13 - P-Card SF eProcumment, Purchasing System should support the ability to generate a Purchase Card specific approval flow based on the requester to expedite Purchase Card Orders. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 366 of 418 LOW MEDIUM I I P.F[s1:1 LOW New workflow is required. MEDIUM New integration is required. C P3 05 51 00 00 P3-05.51-OMO 05 - e_Procure System must support the ability to limit administration and user functionality SF Strategic Sourcing, based on role. Purchasi� Payables P3 05 52 00 00 P3-05.52-00-00 05 - e_Procure System must force users to change their password when they logon the SF Strategic Sourcing, first time Purchase Payables P3 66 63 00 00 P3-05-53-00-00 05 - e_Procure System should have ability to generate vendor activity report by bid SF Strategic Sourcing solicitation. P3 05 54 00 00 P3-05-54-00-00 05 - e Procure ,vstem should support the followinp,repo�ls: I P3 05 54 01 00 P3-05-54-01-00 05 - e Procure Listing of vendors notified for a bid and/or matching NIGP code(s) RQ Strategic Sourcing I LOW P3 09 54 02 00 P3-05-54-02-00 05 - e_Procure RQ Strategic Sourcing LOW Summa(v IisS? of registered ye�IrJy� metchiBy speeit�c NIGP code(s) P3 05 54 03 00 P3-05-54-03-00 05 - e Prowre Detailed regis Bred vendor pro i e is ng ma mg specific NIGP RQ Strategic Sourcing LOW cod9{s) P3 d 54 04 00 P3-05-54-04-00 05 - 8-procure Listing of registered vendors. User must have the ability to select a SF Strategic Sourcing LOW vendor name and view a vendor's detail profile P3 05 54 05 00 P3-05-54-05-00 05 - e Procure Listoa of rq jstered vendors by attributes RQ Str rpqA gpurcinq LOW P3 OS 54 06 00 P3-05-54-06.00 OS - e Procure Lisle 9of bids1�y Fiscal Year RQ Strafso Source g LOW I P3 05 54 07 00 P3-05-54-07-001 05 - e Prowre I List n of bids bV; encY by data range RQ Strategic Sourcing LOW I P3 05 54 08 00 P3-05-54-08-0O OS - e Prowre Listing of bids by �VDe RQ Strategc Sourcing I LOW P3 05 54 09 00 P3-05-54-09-00 OS - e_Prowre Listing of purchasing agent/buyer, APOs and users by agency or all RQ Strategic Sourcing LOW encles P3 05 55 00 00 P3-05-55-00-00 05 - e Procure IR2°Q�Qs should be ( aft (or works lion splav aJ�d on ter SF Sirate is Sourcing P3 OS 56 00 00I P3-OS-56-00-0OI OS - e_Prow (System must have the a1V for a reg ere vendor tO pos(quasGons SF Strateg c Sourcing re,7arding a le or tp the DJpGjSremerlt repistry P3 05 57 00 001 3-05-57-00-00 05 - e_Prowre f4Jated System mus prov a vendcrew e cape rl to search for bids by SF Strategic Sourcing I P3 05 58 00 001 e 5 5�� QQ'-QQfQ� 05 - e Procure iovemment entityl bid number, status, bid type and title. System must DFowde the abiii�( fora vendor fo sort a bid search list SF Strategc Sourcing I P3 05 59 00 OOI P�AX10-00 05 - e_Procure Bid search list must provide 6olh summary and detail views of a selected SF Strategic Sourcing bid I P3 05 60 00 001 P3-05.60-00-00 05 - e Procure System mustprovide the capability for vendor to download a bid SF Strategic Sourcing P3 05 61 00 00 P3.05.61-00-00 05 - e_Procure System must provide the capabill for a vendor to upload electronic SF Strategic Sourcing documents In response to a bid. P3 05 62 00 00 P3-05.62-00-00 05 - e_Prowre System must secure all vendor responses in an electronic lock box from SF Strategic Sourcing ger�w user access until the bid due date and time has expired. P3 OS 63 00 00 P3.05-63.00AO 05 - e_Prowre �ys(am must restrict access to the electronic lock box to agency users that SF Strategic Sourcing have authorized access. I P3I 05 641 00 00 P3-05.64-00-0OI 05 - e_Procure ISystem must prevent vendors from responding to a bid after the due date SF Strategic Sourcing and time has expired. I I P3I 05 651 00 00 P3-05.65-00-00� 05 - e_Prowre ystem must capture the following Information in the bid audit log for all uploaded Rles: I P31 05 65 01 001 P3.OS-65-01-00 O5 - e Procure I Vendor Name SF I Stral� c Sourcing 1 P3 O, 65 02 001 P3-OS-65-02A01 05- e Procure I User ID and full name I SF Strategic Sourcing I I P3 OS 65 03 001 P3-05-65-03-001 05 - e Prowre I Date and time I SF Strategic Sourcing I I P3 05 65 04 001 P3-05-65-04-001 05 - e Procure I Electronic file name(s) I SF Strategic Sourcing I I P3 05 65 05 001 P3-05-65-05-001 05 - e Procure I 81d number I SF Strategic Sourcing I P3 05 661 00 001 P3-05-66-00-00 05 • e Procure System must require vendor acknowledge acceptance of bid attachments SF Strategic Sourcing before allowing the vendor to submit a bid re.9 e. ns P3 05 67 00 00 P3-05-67-00-00 05 - e Prowre System must provide the capability for the City fo publish vendor MI Strategic Sourcing MEDIUM notifications to the public procurement web site. P3 06 01 00 00 P3-06-01-00-00 06 - Special Reporting System provides the ability to report the percent of recycled or other MI Strategic Sourcing, MEDIUM environtnentally-sustainable content of purchases by item code, by dale Purchasing rangpe, and by d artment. P3 06 02 00 001 P3-06-02-00-00 06 - Special Reporting System provides the aDliity to report Small and Minonty-owned RQ Strategic Sourcing, LOW business/Other Targeted businesses solicitation participation by pre- Purchasing identified criteria. P3 06 03 00 OOI P3-06-03-00-00 g6 - Special Reporting System provides the ability to maintain and reportfinquire on usage RQ Strategic Sourcing, LOW statistics on all commodities ordered and purchased, subject to user- Purchasing defined remeters. P3 07 01 00 00 P3-07-01-00-00 13 - P-Card System provides the ability to support entry of P-card as a form of payment SF eProcurement for Rems ordered via the eProcurement system (e.g.. catalogs, spot purchases, etc.) and be able to control amounts and usage by agency, commodity, dollar amount and individual. P3 07 02I 00 00 P3.07-02-00-00 13 - P-Card SF Purchasing System provides the ability to support entry of P-Gard as a loan of payment for Rems ordered via the Proy�rerpant J*�odule in the CI{Y Financial System. P3 07 03I 00 00 P3-07-03-00-00 13. P-Card System provides the ability fo capture key accounting classification data at SF eProcurement, Purchasing time of order for subsequent matching to the statement billing file received from bank. P3 07 04I 00 00 P3-07.04-00-00 13 - P-Card System provides the ability to track the P-card procurement vendor to and SF eProcurement, Purchasing small busine plq n rid/ er larlgeted business status. P3 07 05 0Jj 0 P3-07-05-00-00 13 - P-Card System provides 4he aWlf)y for f e race dilation of the P-card. SF Purchasing P3 i 07 �8 0d dO P3-07-06-00-00 13 - P•Card System provides the abifir(y to set up / manage P-card master data SF Purchasing wfthlcard validity data, the card holder's information, dollar limas and approvers. P3 07 07I 00 00 P3.07-07-00-00 13 - P-Card System provides the integration between P-card master setup/maintenance SF Purchasing and the HR module, to verify employee information (employee id and/or position number) for status changes. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 365 of 418 r P3 05 20 00 00 P3-05-20-00-00 05 - :_Procure System must have a facility to export all documents, message and logs by SF Strategic Sourcing Qldj range rated to a bid to an external system. P3 OS 21 00 00 P3-05-21-00-00 OS -a Procure sys am mus support integration of externa applications with bid solicitation MI Strategic Sourcing information. P3 05 22 00 00 P3-05-22-00-00 05 - e_Procure System must support easy customization/personalization of screen layouts NA an- for a ancles including I�Ao and titles. P3 05 23 00 00 P3-05.23-00-00 05 - e Procure Sys must sup,, 7 edit and deactivation of bids SF Strategic Sourcjfq P3 05 24 00 00 P3-05-24-00-00 05 - e Procure Svs em muatyrow e a method of searching for a bid to edit SF Strategic Sourci� P9 05 25 00 00 P3-O5-25-00.00 05 - e Procure Sys ern musf support upload and delete of individual end documents SF Strate�c Sourcing P3 05 26 00 00 P3-05-26-00-00 05 - e Procure System must support create, edit, and delete purchasing agent/buyer and SF Strategic Sourcing P3 05 27 06 00 P3.05-27-00-00 05 - e Procure pep rnfortnation bYauthorized users only. a em mus` sup r' them Wien nCq�� f NIGP codes QfC� SF Purchasing P3 O5 28 06 00 P3-05-28-00.00 05 - e Procure rs ern muss support seaming o codes, including wild card SF Purchasing searching I P3 05 29 00 00 P3-05-29-D"O 05 - e Procure System must sE rrt�yjnq Dl bids with purcJ7a5. q �gagt1buyer SF SVategic Sourcir I P3 06 30 00 00 P3-0530-00-00 05 -:_Procure Sys em must suppo edlflnr deletiniand reacLva(e o vendor data SF Purchasing, Payables P3 O5 31 00 00 P3-05.31.00-00 05 -:_Procure Sys am must have a abi for the i.iry to suspend or disbar vendors from SF Purchasing, Payables garticipatirt� in solicitations. System I P3 OS 32 00 00 P3-05-32-00-00 05 - e Procure must have the ability to deactivate active vendors SF Purchasing Payables P3 OS 33 00 DO P3-05-33-00-00 05 - a_Procure System must support Ema bid notification to vendors and purchasing SF Strateg c ourcing ageVbuyer. P3 05 34 00 00 P3-05-34-00-00 05 - e_Pmcure Sysmust allow agencies to search for open, awarded, cancelled and SF Strategic Sourcing evaluation bids I P3 06 35 06 00 P3-05-35-MOO 05- e Procure Sy�em must allow bid searches to Include: P3 05 35 01 00 P3-0535-014 OS - e Procure Date SF Strategic Sourcing P3 05 35 02 00 [(3- 5 05 - e Procure Date Rapges SF Strate�c Sourcing I P3 05 35 03 00 P3-0.5= 3-00 05 - e Procure purchasiPq renVbuyer K. SF SjfaFogl� turcing P3 P3 05 05 35 35 04 OS 00 P3-05-35-04-00 00 P3-05-35-05-00 OS - e Procure 05 - e Procure (Includfnp wildcard support) Bid number SF SF S{raleglc $ourang Strategic Sourcing P3 05 35 06 06 P3-05-35-06-00 05 - e Procure Fiscal Year SF Strategic Sourcing P3 05 35 07 00 P3-0535-07-00 05-8 Procure Bid ectivl'ty (i.e. qpa cancelled, awarded, evaluation) SF t�gfeg+NSourcing P3 09 36 00 00 P3-05-36-00-00 05 - e Procure System musf supporE swing of bid search results SF 51r�t([,�,glc Sourcing P3 OS 37 00 00 P3-05-374"O 05 - e_Procure SF Strategic Sourcing S gem must su rt bid searching using single or multiple search criteria P3 05 38 00 00 P3-05-38-00-00 05 - e Procure 8 gg�� rcJt rpp�u 5)Jist must include: P3 05 38 01 00 P3-05-38-01-00 05 - e Procure 8'd c(os(n ate SF Strategic Sourcing P3 05 38 02 00 P3-05-38-02-00 05 - e Procure Document title SF Strai Sourcing I P3 05 38 03 00 P3-05-38-03-00 05-9 Procure Bid number SF Strategic Sourcing P3 O5 39 00 00 P3-05-39-00-00 05 - e_Pm—re System must allow a user to select an Item in the bid search list and drill - down to the next level of detail that Includes: P3 05 39 Ot 00 P3-05-39-OMO 05 - e Procure Bid Title SF Strategic Sourcing P3 05 39 02 00 P3-05-39-02-00 05 - e Procure Bid number SF Strategic Sourcing P3 05 39 03 00t�I���-QQ OS - e Procure ency SF Stratec�lc Sourcing I P3 05 39 04 01- 00 P3-OS-39-04-00 OS - e Procureanff�t�� Contact SF $pa1)1stlr,Sourcinq Sourcing I P3 OS 39 OS 00 P3-05-39-05-00 OS - e Procure Phorli number orate SF ate_c I P3 09 39 06 00 P3-05-39-06-00 05 - e Procure Confect e-mail address ! SF Stra"Ic SourcM I P3 06 39 07 06 P3-05-39-07-00 05 - e Procure Bid Qrocess SF Strategic Sourcing i P3 05 30 OB 06 P3-05 39-08-00 05-9 Procure NI Cat�fls97�ory Coda SF S rategic Sourcing I P3 OS 39 09 00 P3-05-3 -09-00 05 - e Procure Qa1egpr. Description SF Strategic Sourcing I P3 05 39 10 00 P3-OS-39-10-00 05- e Procure Dafe Posted SF Strategic Sourcing I P3 05 39 11 00 P3-05-39-11-00 05 - e_Procure Bid closing dateltime SF Strategic Sourcing I P3 05 39 12 00 P3-0539-12-00 05 - e Procure Dollar range SF Strategic Sourcing I P1 06 39 13 00 P3-05-39-13-00 05 -a Procure Bid Status SF Strategic Sourcing I P3 05 39 14 00 P3-05.39-14-00 05 - e Procure Agency Typg (i.e. Ci�, D:p�nment etc) SF Strategic Sourcing P3 05 40 06 00 P3-0540-00-00 05 - e_Procure Users muss be able to se ect a ocument from a search list and open it in a SF Strategic Sourcing P3 OS 41 00 00 P3-0541-00.00 05 - e_Procure viewer. System must have the capability for an authorized user to send an email to SF Strategic Sourcing regijtered a genczrclZng�yenUbyxer or agency users. P3 05 42 00 00 P3-05-42-00-00 05 - e_Procure System mus! pro da a bid au (log of all new and modifications to a SF Strategic Sourcing posted bid P3 05 43 00 00 P3-0543-00-00 05 - e_Procure SF Strategic Sourcing Bid audit log must contain the date, company name, contact and email address of all vendors notified via email when the bid was WqyAted. P3 05 44 00 00 P3-0544-00-00 05 - e_Procure Bid audit log must contain all additional correspondence inifiated from the SF Strategic Sourcing City purchase{1g system. P3 05 45 00 00 P3-0545-00-00 05 - e_Procure System musf provide functionality to search, display and print audit logs for RQ Strategic Sourcing a specific bid P3 05 46 00 00 P3.05-46-00.00 05 -:_Procure SF Strategic Sourcing, SY�1em must support yrq�)Inp and m Paging user -Id and passwords. Purchasing Payables P3 OS 47 00 00 P3-OS-47-00-00 O5 -:_Procure System must aufomaElcally regenera� a new user password and email SF Strategic Sourcing, notification in the event a use�password is forgotten. Purchasing Payables I P3 05 48 00 00 P3.05d8-00.00 05 - e_Procure System must allow the administrator to assign a temporary password for a SF Strategic Sourcing, user Purchasip-q. Payables P$ 05 49 00 00 P3-0549-00-00 05 - e_Procure SF trate Sgic Sourcing, System must support hierarchal security roles Purchasi�g, Payables P3 05 50 00 00 P3-05.50-00-00 05-:_Procure SF Strategic Sourcing, System must support creating, managing and mapping of user -ids to roles Purchasing. Payables City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 364 of 418 f t I 1 1 1 I ! MEDIUM MEDIUM P3 05 04 00 00 P3-05-04-00-00 05 - e Procure P3 05 05 00 00 P3-05-05-00-00 05-e Procure P3 OS O6 00 00 P3-05-06-00-00 05 - e Procure P3 05 07 00 00 P3-05-07-00-00 05 - 9-Procure P31 05 08 00 00 P3-05-08-00-00 05 - e Procure P31 05 09 00 OOP,3-89-iD-0i)-8C P31 05 10 00 00 P4 iD•Di)-8 P31 05 11 00 00 P3-05-11-00-00 P3I 05 12 00 00l i3-05-12-00-00 P31 05. 12. 01 001 P3-05-12-01-00 P3I 051 121 02 001 P3-05-12-02-00 P3I 051 121 03 OOI P3.05-12-03-00 P3 051 12 04 001 P3-05-12-04-00 P31 051 121 051 001 P3-05- 1 2-05-00 P31 051 121 061 001 P3-05-12-06-001 P31 051 121 071 001 P3-05-12-07-001 P31 051 121 081 001 P3-05-12-08-001 P3I OSI 12� 09I 00(,P3-05.12-09-001 P3 05 12 111 001 3-05.12-10-001 P3 051 12 11 OOI P3-05-12-11-001 P31 051 121 121 001 P3-05-12-12-001 P31 051 121 131 001 P3-05-12-13-001 P3I 05I 121 141 OOI P3-05-12-14-001 P3I 05 121 151 001 P3-05-12-15-001 1 051 13 OOI 00 P3.05- 1 3-00-00 P3I 05I 141 00I OOIP3-05-14-00-00 P31 051 151 001 001 P3.05-15-00-00 P3I 05I 161 OOI OOI P3-05-16-00-00I P31 051 171 00 001 P3-05-17-00-00 P3I OSI 171 O1 OOI P3-05-17-01-00 P3I 05 171 02 00 P3-05-17-02-00 P3I 05 171 03 OOI P3-05-17-03-00 P3I 051 171 04 001 P3-05-17-04-001 P31051 171 051 001 P3.05-17-05.001 P3I 05I 171 06 OOI P3.O5-1;-O 0, P3 05 171 07 00 P3-05-17-07-00 P3 05 171 08 00 P3-05-17-08-00 P31 051 17) 09 OOI P3-05-17-09-00 P31 051 171 10 001 P3-05-17-10-001 P31 051 171 111 OOIP3-05-17-11-001 P3 OS 171 12 00 P3-05-17-12-001 13 05 17 13 00 P3-05-17-13-00 P3 05 17 14 00 P3-05-17-14-001 P3I 05 171 151 00 P3-05-17-15-001 I P3I 05 171 161 00 P3-05-17-16-001 I P31 051 171 171 00 P3-05-17-17-001 P31 05I 171 18I 00 P3-05-17-18-001 P3 05 171 19 00 P3-05-17.19-001 I P3I 05 171 201 00 P3-05-17-20-001 1 P3I 051 171 211 00 P3-05-17-21-001 1 P3I 051 171 221 00 P3-05-17-22-001 I P31 051 171 231 001 P3-05-17-23-001 I P3I OSI 17� 241 OO�P3-05-17-24-001 ( P3I OS 17 25 00 P3-OS-17-25-00 I P3I 051 17 26 00 P3-05-17:2.0 1 P31 051 17 27 00 P3-05-17-27-00 P3I 05 181 OOI OOI P3-05-18.00-0OI P31 05 191 001 001 P3.O5-19-00-001 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 363 of 418 05 - e Procure 05- e Procure 05 - e Procure 05-e Procure 05 - e Procure 05 - e Procure 05 - e Procure 05 - e Procure 05 - e Procure 05-e Procure 05-6 Procure 05 - s Procure 05 - e Procure 05-6 Procure 05- e Procure 05 - e Procure 05 - e Procure 05-6 Procure 05-e Procure 05- e Procure 05-e Procure O5 - e_Prroocurre 05 e - e Procure 05 - e Procure 05 -a Procure 05-8 Procure 05 - a Procure 05-e Procure OS - e Procure 05 • e Procure 05-e Procure 05-e Procure 05 - e Procure 05 - e Procure 05-9 Procure 05 - e Procure 05-9 Procure 05 - e Procure 05 - e Procure 05 - e Procure 05 - s Procure 05 - e Procure 05 -a Procure 05 - e Procure 05 - e Procure OS - e Procure 05 • e Procure OS - e Procure OS • a Procure 05 - e Procure 05 - e Procure 05-e Procure System must support the National Institute of Governmental Procurement (NIGP) commodity codes. System must support automatic e-mail notifcatlon to registered vendors that matches a posted bid NIGP code. Vendor e-mail message must include a link to the bid on the public procurement web site. System must allow a user to manually custormze and send a message, via the City's e-mail system, to registered vendors that match a NIGP code(s), including attachments. System must allow a user to manually customize and send a message, via the City s E-mail s1(stem, to rapIstered vendors based on vendor attributes. System must have the ability to exclude e-mail message to vendors who have been suspended, inactive or disbarred. Svsjpm rr)us{ ensure that only acoroyed bids are posted vs em must au�ed delete an add a document to a bid System must be able to retract a bid 5vi(em must include the following information when a bid is posted: Bid number I gy9ncy I fiscal Year I Bid title I Bid type (i.e. RFI, RFP, RFO etc.) I Cateaow type (i.e. IT, City wide contract. Prof. services etc.) I Contact name I Contact hone number Contacf a_mail address Bid closing date Bid closirr��pp time DescrJ)t(on 1 URL (options]) I Dollar Amount (optional) I I Bid status (Information field onlJyy\ I System must support searching NfG codes, including wild card, by description or number and allow a user to attach a new Hem to a posted bid. System must support searching NIGP codes, including wild card, by description or number and allow a registered vendor to submit a bid re6 onse. Sys em must prevent a bid from being posted without a valid 5 digit NIGP code System must limit creating and managing agency and purchasing agent/buyer profiles to those individuals with appropriate security authorization - System must support managing/editing individual user profiles by owner, ourchas/'rw aaenUbuver profile must contain the followinq information: Firsf name Middle initial Lest name 1 Job title I Phone number Fax number E-mail address Manager name Address I Ci�ttyy I State I Z)� code I Ze�v Name purchasing agent/buyer Security Role (i.e. agency purchasing aaenUbuyer �Ae�cy manager, City qurcha np manaoer etc.) IAaeQQQQcv ofoflle lelOnnetlon must contain fits 10 (owing: I encv cod I pencvname I tvDe dress C��11yy I Stale I Z- code I done number I ax number URL I Fq(}�y(1@mr'1\ DprocuremmIent officer/APO) name(s) I Y1Ya Dla ap a authori(v (i.e. �eslnol System must a users to change heir password in accordance with City Security Polivy. ISV6tern must support both vendor summary and detail profile views 1 SF Purchasing MI Strategic Sourcing, LOW Required new workflow. Purchasing MI Strategic Sourcing, LOW Required new workflow. Purchasing MI Strategic Sourcing, LOW Required new workflow. Purchasing MI Strategic Sourcing, LOW (Required new workflow. Purchasing SF SF ggP(ra(ea�c SouroIno Strafe;courcmq SF Strategic Sourcing I SF I Strateca. Sourcing I I SF I stratec.c Sourcina I SF I StraSlaw Sourc�q SF Straleq.: Sourcno SF I Strati Sourcina I MI I Strateoiz Sourcina I MEDIUM SF I Strategc Sourcino I SF Strategc Sourcino I SF Strategic Sourc fo SF Strategic Sourc fa SF Strategc Sourcina I SF Strategc Sourcino SF Strategic Sourcina I SF I Strategic Sourcino I I SF I Strat�c Sourcina I SF Stra(egic Sourcing SF Strategic Sourcing SF I Stratogic Sourcing SF Strategic Sourcing SF I Purchasing I SF I Purchasina I SF I Purchasing MI I Purchasino I MEDIUM SF I Purchasina I I SF Purchasno MI Purchasina MEDIUM MI Purchasina I MEDIUM MI I Purohasina 1 MEDIUM MI I Purchasina MEDIUM MI I Purchasina I MEDIUM MI Purchasina MEDIUM MI Purchasino MEDIUM SF Purchasing SF Purchasina SF Purchasina MI Pumhasinq MEDIUM SF Purchasino SF Purchasina SF Purchasina SF Purchasina I SF Purchasina I SF Purchasina MI Purchasina MEDIUM MI Purchasina MEDIUM MI Purchasirnjau MEDIUM SF Purchasing, Srategic Sourcina SF Purchasina, Pavables I I I I P3 03 03 00 00 P3-03-03-00-00 03 - Vendor Maintenance System provides the ability to permit multiple addresses to be assigned to a MA Purchasing, Payabies HIGH TMs functionality is not specific address type for a specific vendor (e.g., multiple ordering currently avaUable and cuts addresses, invoice addresses, etc.). need to be created using PeopleTools. P6 03 04 00 00 P3-034)4-00-00 03 - Vendor Maintenance System provides the ability to search for a vendor using multiple search SF Purchasing, Payables criteria such as commodity code, commodity code number or description, Small/Nlinority/Other Targeted Business status, vendor name, vendor and number, and Inamet etc. P3 01 05 00 00 P3.03-05-00-00 03 - Vendor Maintenance System the abilay to track vendor history, to include date added or MI Purchasing, Payables LOW inactivated and reason. P3 03 06 00 00 P3-03-06-00-00 03 - Vendor Maintenance System provides the ability to deactivate vendor from vendor listing by date MI Purchasing, Payables LOW with reason. Historical data should be retained. P3 03 07 00 00 P3-03-07-00-00 03 - Vendor Maintenance System provides the ability for vendor numbers (numeric and SF Purchasing, Payables alphanumeric) to bjee system generated or assigned manually based on sy din a, P3 03 08 00 00 P3-03-08-OD-00 03 - Vendor Maintenance Sys(em pray she ability for with authorized security to have the SF Purchasing, Payables ability to add chary�0�e 0r deactiva a yy9Bndor mr� ater file records. P3 03 09 00 00 P3-03-09-00-00 03 - Vendor Maintenance System provides file ability to mainfafn en on-line audit trail of changes to MI Purchasing, Payables LOW the vendor master file Including date, time, and user, old and new values. P3 03 10 00 00 P3-03-1 0-00-00 03 - Vendor Maintenance System provides the ability to maintain vendor open procurements when SF Purchasing, Payables vendor name is changed - (updates PO, but maintains vendor history) P3 03 11 00 00 P3-03-11-00-00 03 - Vendor Maintenance System provides automated notification to specified users (I originator, MI Purchasing, Payables LOW New workflow is required. buv}1rs antl �aJ�do 1 q yyRrl or na/Jr�r��,� c'angee$�� P3 05 12 66 00 P3-03-12-00-00 03 - Vendor Maintenance System provides e a ilfiy maintain an onlme history of vendor SF Purchasing, Payables transactions by month, quarter, fiscal and calendar year, inception to date, contract, bid number, department, etc. P3 69 13 00 00 P3-03-13-00-00 03 - Vendor Maintenance System supports the use of'one-time- vendors that automatically expire SF Purchasing, Payables Purchasing and Payables after a user speed length of time. supports one-time vendors; however, there is not a delivered expiration time. P3 03 14 00 00 P3-03-14.00-00 03 - Vendor Maintenance System can be configured to support capture of the following fields when using a dummy vendor 1 generate P3 i P3 03 03 14 14 01 02 00 P3-03-14-01-06 03 - Vendor Maintenance Dummy vendor number 00 P3-03-14-02-00 03 - Vendor Maintenance Name SF SF Purchasing` Payables Purchasing, Payables I I P3 03 14 03 00 P3-03-14-03-00 03 - Vendor Maintenance Address 1 SF Purchasing`Pavables I{` P3 03 14 04 00 P3-03-14.04-00 03 - Vendor Maintenance Address 2 SF Purchasing, Payables I P3 03 14 05 00 P3-03.14-05-00 03 - Vendor Maintenance Address 3 SF Purchasnq, Payables I P3 03 14 06 00 P3-03-14-06-00 03 - Vendor Mairaenence Address 4 SF Purchasymg `Pavables 1 P3 03 14 07 00 P3-03-14-07-00 03 - Vendor Maintenance cll SF Purchasing \Pavables I P3 P3 03 03 14 14 08 0EI, 06 P3-03-14-08-00 03 - Vendor Maintenance SM. 00 P3-03-14-09-00 03 - Vendor Maintenance Postal Code SF SF Purchasing Payables Purchasin . Pa ables f.,. PZ 04 01 00 00 P3-04-01-00-00 04 - Vendor Performance System provides the ability to track contacts with vendors (e.g., phone SF Purchasing, Payables calls, written contacts regarding problem ordersidelivery of goods and with proper sit l(Y. services), "'Aatdhle/vIgr P3 04 02 00 re 00 P3-04-02-00-00 04 - Vendor Performance System prov es �(htee a ilky for an online, complaint -tracking process that Includes. I P3 04 02 01 06 P3-04-02-01-00 04 - E ee fylmance Descrillt o?�e or%e([�cpr�7pJa.t MI Purchasin�`P Oles HIGH I P3 04 02 02 ll P3-04-02-02-00 04 •Vendor Performance History (includin. content} of all related w7��yo�j�ence MI Pu chasing. Payables HIGH P3 04 02 03 00 P3-04-02-03-00 04 - Vendor Performance System -generated email message or form taker (i1 no email address or MI Purchasing, Payables HIGH Invalid email address) to be sent to vendor and copy to the department that submitted the complaint. P3 04 02 04 00 P3-04-02-04-00 04 - Vendor Performance A second letter will be automatically generated if a response from the MI Purchasing, Payables HIGH vendor is not received within a userapecified number of working days I P3 04 02 05 00 P3.04-02-05-00 04- Vendor Performance Vendyyf fesPo(�5 MI Purchasing, Payables HIGH J I P3 P3 04 04 02 03 06 00 00 P3-04-02-06-00 04 - Vendor Performance "esolufion (eledrpnj{' illy noti1`( vegdon and p r� �T1 n11 00 P3-04-03-00-00 04 - Vendor Performance System compares ac(ual �elivery date to contracfualrtdeli�very data and MI SF Purchasing Payables Purchasing,'Ibayables HIGH ... . updates vendor-pefform nce statistics accordingly P3 04 04 00 00 P3-04-04-00-00 04 - Vendor Performance System provides is ability to automatically track and reportfinquire on yen performance, Including but not limited to: I P3 04 04 01 00 P3-04.04-01-00 04 - Vendor Performance deliivery SF Purchasing, Payables _ I I P3 04 04 02 00 P3-04.04-02-00 04 - Vendor Performance returns SF SF Purchasing Payables Purchasing>avables I I P3 P3 04 04 04 04 03 04 00 P3-04-04-03-00 04 - Vendor Performance fill rate 00 P3-04-04-04-00 04 - Vendor Performance soli lTents SF Purchasipg�ayables I 1 P3 04 04 05 price 00 P3.04-04-05-00 04 - Velf P-1=:nce - pa " hi�sl�ry SF Purchas(ng�ayables I P3 04 04 06 00 P3-04-04-06-00 04 - r ormance com r, m. a. resolution MI Purchasil Payables MEDIUM I IM 04 07 (V/BpJ pPe 00 a ornance specific oaded Strategic Sourci MEDIUM I14iiaill,udli8iil Ml 1 Isofidtatbn8ildi�l6wlilllll lllii.11lj'itll'i�l Ili IIIIdtl1111V1V,lt11'mil�IdailtI�i,i�i!�WCis. ll�� !howl 1Ullill ollIII 11li�1 !' Vo+llIIIIs,e I, �I Ill illl'i V�lll6,1e ill lit It P3 05 01 00 09 P3-05-01-00.00 05 - e_Procure System must have Pudic modules that allow the City to manage bids and SF Strategic Sourcing ven{)ors to ery�,vi �9 Alljve solicitations P3 05 01 00 00 P3-05-02-00-00 05 - e_Procure Sya ern muss eve a y to route bid documents for posting approval to SF Strategic Sourcing assist agencies in complying with procurement laws, purchasing authority and ppurchat qa approval RQ1iggyy P3 05 09 00 00 P3-05-03-00-00 05 -._Procure Sys(em mull be secure and al ow only authorized users access to specific SF Strategic Sourcing administration functionality. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 362 of 418 R 1 4 M ( I P3 02 01 00 00 P3-02-01-00-00 02 - Vendor Master Data P3 02 01 01 00 P3.02-01-01-00 02 - Vendor Master Data Fill 02 01 02 00 P3.02-01-02-00 02 - Vendor Master Data P3 02 01 03 00 P3-02-01-03-00 02 - Vendor Master Data P3 02 01 04 00 P3-02-01-04-06 02 - Vendor Master Data P3 02 01 OB 00 P3-02-01-05-00 02 - Vendor Master Data P3 02 Ot 06 00 P3-02-01-06-00 02 - Vendor Master Data P3 02 01 07 00 P3-02-01-07-00 02 - Vendor Master Data P3 02 Ot 08 00 P3.02-01-08-00 02 - Vendor Master Data P3 02 01 64 00 P3-02-01-09-00 02 - Vendor Master Data P3 02 Ot 10 00 P3.02-01-10-00 02 - Vendor Master Data P3 02 01 11 00 P3.02-01-11-00 02 -Vendor Master Data P3 02 01 12 00 P3-02-01-12-00 02 - Vendor Master Data P3 02 01 12 Ot P3-02-01.12-01 02 - Vendor Master Data P3 02 01 12 02 P3.02-01-12-02 02 - Vendor Master Data P3 02 01 12 03 P3-02-01-12-03 02 - Vendor Master Data P3 02 Ot 12 04 P3.02-0i-12-04 02 - Vendor Master Data P3 02 01 12 05 P3-02-01.12-05 02 - Vendor Master Data P3 02 01 12 07 P3.02-01-12-07 02 - Vendor Master Data P3 02 01 13 00 P3-02-01-13-00 02 - Vendor Master Date P3 02 01 14 00 P3-02-01-14-00 02 - Vendor Master Data P3 02 Ot 16 00 P3.02-01-15-00 02 - Vendor Master Data P3 02 01 16 00 P3.02-01-16-00 02 - Vendor Master Data P3 02 Ot 16 01 P3.02-01-16-01 02 - Vendor Master Data P3 02 Ot 16 02 P3-02-01-16-02 02 - Venda Master Data P3 02 01 16 03 P3-02-01-16-03 02 - Vendor Master Data P3 02 01 16 04 P3-02-01-16-04 02 - Vendor Master Data P3 02 01 16 05 P3-02-01-16-05 02 - Vendor Master Data P3 02 01 16 061 P3-02-01-16-06 02 - Vendor Master Date 1 P3 02 01 16 071 P3-02-01-16-07 02 - Vendor Master Data 1 P3 02 01 16 08 P3-02-01-16-08 02 - Vendor Master Data P3 02 01 17 00 P3-02-01-17-00 02 - Vendor Master Data P3 02 01 18 00 P3-02-W-18-00 02 - Vendor Master Data P3 02 01 19 00 P3-02-01-19-00 02 - Vendor Master Data P3 02 01 20 00 P3-02-01-20-00 02 - Vendor Master Data P3 02 01 21 00 P3-02-01-21-00 02 - Vendor Master Data P3 02 01 22 00 P3-02-01-22-00 02 - Vendor Master Data System provides the ability for the vendor file to include the following information, including but rat limited to (access to Information is based on security) Vendor number Prior vendor name(s) and number(s) Vendor name Vendor status (active. inactive. on hold. ineligible, etc.) DBA Name Prior DBA Name Registration valid date on eg sjjrej'�on va eplaf�ort Ce ofr�o pate�aaxDDmeteddera GaSecurity Number/ITIN Tyyrr11�� of Number (EIN. SSS ITIN Mu(tiole Ye dor contact Information Contact name Contact title GDnt am., �IipP :ccounlira, sales, etc) Con[[�a�c{{ emai address Mull iliihone numbers (voice, fax. mobile. etc,l Commenf Address t Desj (ordering, remittance. 1099 etc.1 Multio�e ohh�($)ca addresses Multiple malirl"�yp addresses (handles PO and foreign addresses) Address sDerdfic fields: Address 1 Address 2 Address 3 Address 4 CitJyy State Coun1�v Postal Code State where vendor headquarters located Webslte address Bank Transit Code (ABA/Routina number) Bank Account Number Bank Name Default (preferred) payment terms (restricted to a city approved list) I P3 021 Oil 23 001 P3-02-01-23-00 02 - Vendor Master Data I Muleole Methods of Payment (check, ACH, P-Card. etc.1 I P3 021 Oil 24 001 P3-02-01-24-00 02 - Vendor Master Data I Default (preferred) method of oaly�menI I P3 021 Oil 25 001 P3-02-01-25-001 02 - Vendor Master Data I Hold Reason and Hold Source (department level) I P3 021 Oil 26 001 P3-02 1.28-001 02 - Vendor Master Data I Business Desuipp}}��on P3 02 Ot 27 OOI P3-02 1-27-001 02 - Vendor Master Data Ownership Type/Business Structure/Governmental Organization (e.g., 1 I C-caQQI federal deDartment P3 02 Ot 28 OOI P3.02-01.28-00 02 - Vendor Master Data mall inority)Other Status and Ce fication Types (MBE, WBE, DBE, I Veteran, etc.) Pal 02 Oil 29 OOI P3.02-01-29-00I 02 • Vendor Master Data Small and Minority-owned/Other Targeted Businesses Certification I NumbsI to registration) P3I 021 01 I 30 001 P3-02-01-30.001 02 - Vendor Master Data 1 099 Repasslyn�ebsequent I P3I 021 01 I 31 001 P3-02-01.31-001 02 - Vendor Master Data 1 1099 Rap000rrtrttiffnry en or Name 1 P31 021 Oil 32 00 P3-02-01-32-001 02 - Vendor Master Data Vendor backup tax withhoId' status I P3 I P3 021 02 Oil 01 I 33 34 00 P3-02-01-3100 02 -Vendor Master Data 00 P3-02-01-34-00 02 - Vendor Master Data Foreign CorQPration II fob j'r,, p r� Geoorallhic Designs n (Oity $(ate Ql way District, other` P3 02 01l 35 00 P3-02-01-35-00 02 - Vendor Master Data User -de med vendor type fields (at least ) -tor future reporting needs P3 02 Oil 36 00 P3-02-0136-00 02 - Vendor Master Data W9 received�yes(no) P3I 021 Ot 37 001'03.02-01-37-001 02 - Vendor Master Data I Date W9 received P3I 02I 01 38 OOI P3-02-01-38-OOI 02 - Vendor Master Data One -Time Vendor Flag (used to expire a vendor record after a user I ( defined number of days) P3I 021 01 39 00 P3-02-01-39-0OI 02 - Vendor Master Data Dummy Vendor Flag (used to require payment information at the time a I I r 1( tint is estec YI11,1111I liilliigill 418i'iiiYlll'16ii6fiill.u.br,dll,miil6lia' '! „iV will P3 03 01 00 00 P3-03-01-00-00 03 - Vendor Maintenance System provides the ability to detect duplicate vendor information based on multiple criteria (e.g., FEIN, SSN, DUNS, address, etc.), with appropriate security. P3 03 02 00 00 P3.03-02-00-00 03 - Vendor Maintenance Systems provides the ability for one Vendor file with different views of the data. with posting and inouiry caoabilities controlled by secudty: I P3I 031 02 Oil 00 P3-03-02-01-001 03 - Vendor Maintenance I Purchasm(l view I P3I 031 02 02I 001 P3-03-02-02-001 03 - Vendor Maintenance I Accounts Pavable view 1 P31 031 02 03 00 P3-03-02-03-001 03 -Vendor Maintenance i End User lP3 03Ij! 02 04 00 ce Pee3-03-0�2r-044-00011 03 -Vend Maintnan Veendor SeNService View View 1 P3I 031 02 06 00) P� 83�2 6 001 03 - Vendor Maintenancee MWstem BE Viewinislrator City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 361 of 418 SF Purchasinq`Pavables SF Purchasing. Pavables SF Purchasinq, Pavables SF Purchasing Pavables SF Purchasing. T5ayables SF Purchasjfq. `Payables MI Purchasmq`avables LOW MI Purchasinq, Payables LOW MI Purchasing, Pavables LOW SF Purchasing, Payables SF Purchasing. Pavables I SF Purchasinq Pavables SF Purchasinq�avables SF Purchasinq"Pavables SF Purchasinq'*P`avables SF Purchasing `Pavables SF Purchasing. Pavables I SF Purchasing `Pavables I SF Purchasinq`Pavables SF Purchasinq, Payables I SF Purchasing, Pavables I I I SF Purchasinq, Pavables I SF Purchasing. Pavables I SF Purchas fa, Payables SF Purchas) ,,paveales SF Purchas fa. Pavables I I SF Purchasing, Pavables I I SF Purchasing Pavables I I SF Purchasino Pavables I SF Purchasing, Pavables I SF Purchas. Pavables I SF Purchasing. Payables SF Purchasino Payables I SF Purchas�9 tayables I SF Purchasing, Payables MI Purchasing. Pavables MEDIUM SF Purchasing \ Payables I MI Purchasinq. tavables I LOW SF Purchasinq. Pavables I SF Purchasing, Payables SF Purchasing, Payables SF I Purchasing, Payables SF I Purchasinq` Payables I SF 1 Purchasina \Pavables I SF I Purchasing, Payables SF Purchasing \ Pavables SF Purchasinq Pavables II SF Purchasing. ayables I i MI Purchasfq, Payables I LOW MI I Purchasing, Payables I LOW SF l Purchasing, Payables l SF Purchasing, Payables SF I Purchasing, Pavables I I SF I Purchasinq, Pavables I SF Purchasing Pavables SF Purchasing,'�ayables, esuQolier Connection SF Purchasinq `Payables I MI Purchasing, i�ayables I LOW I P3 00 02 00 00 P3-00-02-00-00 00 - Commodity Data System provides the ability for authorized users to document additional commodity specifications and/or comments, and attach at different levels of the NIGP hierarchyy. P3 00 03 00 00 P3-00-03.00-00 00 - Commodity Data System provides the ability for authorized users to add and associate key P3 00 04 00 00 P3-00-04-00-00 00 - Commodity Date words in addition to the search stria(1s within the commodi( file. System provides the ability to select a commodity and display to the end user all vendors that have registered or that have contract(s) for that commodity. P3 00 05 00 00 P3-00-05-00-00 00 - Commodity Data The and user should have the ability to drill -down on the contracts for further item Information. P3 00 D6 00 00 P3-00-06-00-00 00 - Commodity Data System provides the ability for the commodity code field to be a variable - length field that accommodates at least 11 alphanumeric characters, with manual and automatic assment capabilities. P3 00 07 00 00 P3-00-07-00-00 00 - Commodity Data System provides the ability for the commodity file to contain, but not be limited to, me followingdate items P3 00 P3 00 07 07 01 02 00 P3.00-07-01-00 00 P3.00-07-02-00 00 - Commoditryy Daa 00 - Commodi�Daa Commod' code -first five dioits required, full 11 dioit capable Cross-re{erences to previous commodity codes P3 00 07 03 00 P344-07-03-00 00 - Commodij�,,ate Key words P3 oo 07 o4 DO P3-DO-07-04-00 00- Commodi� LDaa Lonq description P3 00 07 05 00 P3-00-07-05-00 00 - Commodr`�'lea Short descrp)ion P3 00 07 06 00 P3-00-07-06-00 00 - Cortlmodi)r�Data Comments field P3 00 07 07 00 P3-00-07-07-00 00 - Camnwdi as Source indicator (e.q., contract, spec inventory) P3 00 07 08 00 P3-00-0708-00 00 - Commod�{�Data status IPI 00 d3 00 07 07 010 6d P3-00 07 0-00 Data 00 - Commi Daa �Cjommodity ous lert a Venadodrs for commodity P3 00 07 11 00 P3-00-07-11-00 00 - Comm.ate 711skam Base Uni4 of measure P3 00 07 12 00 P3-00-07-12-00 00 - CommodMaa Inventory information for specific departments that maintain inventories to the svftem. P3 00 08 00 00 P3-00-08-00-00 00 - Commodity Data System provides the ability to maintain an on-line audit trail of changes to P3 01 01 00 00 P3-01-01-00-00 01 -Vendor Registration System provides the ability for a self-service vendor registration function vi the Internet that will allow the followsr P3 01 01 01 00 P3-01-01-01-00 01 -Vendor Registration User -defined data -entry fields which can be specified as mandatory or optional including all required fields to create the vendor master P3 01 01 02 06 P3-01-01-02-00 01 - Vendor Registration Registration functionality that is completely integrated with the rest of the ERP system including vendor master creation P3 01 01 09 00 P3-01-01-03-00 01 - Vendor Registration Ability for vendors to pay registration fees via a credit card P3 01 01 04 00 P3-01-01-04-00 01 -Vendor Registration For manual payments for registration, the registration will be placed in suspense until the manual payment is successfully processed and City approval is granted. P3 01 01 05 00 P3-01-01-05-00 01 - Vendor Registration Ability for vendors to provide additional information, defined by the City, about the commodities for which they are rristenn . P3 01 02 00 00 P3-01-02-00-00 01 - Vendor Registration System provides the ability to wam if a vendor is already registered and provides the ability for the vendor to update select fields with current information. System provides the ability to check various fields to view duplication, including but not limited to: FEIN, TIN, Name, DBA, etc. P3 01 03 00 00 P3-01-03-00-00 01 -Vendor Registration System provides the ability to automatically send a vendor a registration confirmation by email or fax. The confirmation would include the commodity code (a) for which the vendor has registered and eti other pertinent information. P3 Of 04 06 00 P3.01-04-00-00 01 - Vendor Registration System provides the ability for notices to vendors based on a user - specified number of days prior to registration expiration and after expiration. P3 Ot 05 06 00 P3-01-05-00-00 Of -Vendor Registration System prevents vendors from initiating the following changes directly, but p(ovtdes a workflow for them I P3 01 05 01 66 P3-01-05-01-00 Ot -Vendor R Istration Name Chanpe 1 P3 01 05 02 00 P3-01-05-02-00 01 - Vendor R��traU. n Tax ID Number I P3 01 05 03 00 P3-01-05-03-00 01 -Vendor ReglFtretion DBA Name P3 01 05 04 00 P3-01-05-04-00 01 - Vendor Rert�s� tration Faaodno (temoorary Pa To P3 01 OS 05 00 P3-01-05-05-00 01-Vendor Rep tration Zmnmment!permanent av- o) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 360 of 418 SF Purchasing SF Purchasing MI Purchasing HIGH MI Purchasing HIGH SF Purchasing SF Purchasina SF Purchasinq SF Purchasing I SF Purchasinq SF Purchasj/mg SF Purchas fq SF Purchasinq I SF Pumhasina SF Purchasinq SF Purchasing SF Purchasing SF Purchasing, Inventory MI Purchasing LOW SF Strategic Sourcing SF Strategic Sourcing SF Strategic Sourcing, Purchasing Pavables CD Strategic Sourcing HIGH This could be accomplished in a variety of ways but some level of customization is needed. CD Strategic Sourcing HIGH This could be accomplished in a variety of ways but some level of customization Is needed. SF Strategic Sourcing SF Strategic Sourcing SF Strategic Sourcing MI Strategic Sourcing LOW MI Stretec`Ic Sourcina LOW MI Strateciilc Sourcing LOW MI Strategic Sourcing LOW MI Stnii Sourcino LOW MI Strateqlic Sourcna LOW MI Stratenja8mirrinn LOW I I 1 I I I i i 1 1 1 1 I 1 1 1 1 1 1 1 1 1 f P2 10' 19 00 P2-10.04-19-00 10 -Vendor Invoice I P 10 04 20 00 P2-10.04-20-00 10 - Vendor Invoice I P2 10 04 21 00 P2-10-04-21-00 10 - Vendor Invoice I P2 10 04 22 00 P2-10-04-22-00 10 - Vendor Invoice I P2 10 04 23 00 P2-10-04-23-00 10 - Vendor Invoice I P2 10 04 24 00 P2-10-04-24-00 10 - Vendor Invoice I P2 10 04 25 OC P2-10-04-25-00 10 - Vendor Invoice P2 10 2§ 00 P2.10.04-26-00 10 - Vendor Invoice P2 10 2 00 P2-10-04.27-00 10 - Vendor Invoice P2 10' (j�� 2 8 00 P2.10.04-28-00 10 - Vendor Invoice P2 10 04 29 00 P2-10-04-29-00 10 - Vendor Invoice I P2 10 04 30 00 P2-10.04-30-00 10 - Vendor Invoice P2 10 04 31 00 P2-10-04-31-00 10 - Vendor Invoice I P2 10 04 32 00 P2-10-04-32-00 10 - Vendor Invoice I P2 iQ 04 33 00 P2.10.04-33-00 10 - Vendor Invoice P2 0 04 34 00 P2.10.04.34-00 10 - Vendor invoice 1 P2 10 04 35 00 P2-10-04-35-00 10 -Vendor Invoice I P2 1p 04 36 M P2- 1 0-04-36-00 10 - Vendor Invoice I P2 191 04 37 00 P2-10.04-37-00 10 - Vendor Invoice P2 101 05 00 00 P2-10.05.00-00 10 - Vendor Invoice I P2 101 061 001 00 P2-10.06-00-00 10 - Vendor Invoice P2 10 07 00 P2-10.07.00-00 10 - Vendor Invoice 1 P2I 10I 08 � 00 P2-10-08.00-00 10 - Vendor Invoice P2I 10 09 OOI 00 P2-10-09-00-00 10 - Vendor Invoice P2I 10 101 001 00 P2-10-10-00-00 10 - Vendor Invoice P2I 10 11 1 00 P2-10.11-00-00I 10 - Vendor Invoice P2 10I 12 00 DO P2-10-12-00-00I 10 - Vendor Invoice P2 10I 13 0 00 'P2.10-13-00-001 10 - Vendor Invoice P2I 101 141 001 00 P2-10-14-00-001 10 - Vendor Invoice EiY P2 11010001.01-00- 72-,,,, 11 - Matching P2 111 011 Ot 0-t-01-00 11 -Matching I P2 111 Oil 02 001 P2-11-01-02-001 11 - Matching I P2 ill Oil 03 001 P2-11-01-03-001 11 - MatchM I P21 111 Oil 041 001P2-11-01-04-001 11-Malchym I P21 11l 021 001 001 P2-11-02-00-001 11 - Matching P2 11 03 00 00 P2.11.03.00-00 11 - Matching "I rd 1 vvt col ra-i<- I-uvrrul rc- rnynrom rcequesr IP2I 12 0`2I 0000 00 P2-12-02-00-00I 12 - Payment Request Request I P2 f2l 04I 00 00 P2-12.04.00-00 12 - ePaymenj P2 12 05I 00 00 P2-12-05.00-00 12- Paymen}Request P21 121 061 001 001 P2-12-06-00-001 12 - Payment Request P2I 12 071 00 00 P2-12-07.00-00I 12 - Payment Request City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 359 of 418 Unit cost Line item total cost Invoice total cost Pyment terms Discount date Discount terms Discount amount Retainage Terms Retamage Amount Frei lit Fro Nat terms Account distributions Check or ACH payment number (ability to drill -down to see all invoices Raid by the check) avment amount Pavment date I CommenUmerdo field that can be printed on check or passed to ACH transaction Commentimemo field for internal DurDO585 oniv Net Invoice PavrTnt Service Delivery Address System provides the ability to process multiple accounting distributions against a single invoice/voucher. Svstam Drov es the abilityy to track disji I d invoices electronicall`( I System provides the ability to document comments and resdution 10 i)sDutes. ystem provides the ability to process multiple invoices against a single PO. System provides the ability to process single or multiple invoices against multiple Poe. Svstem provides the abillty to c;Wure and process credit memos. I System provides the ability for the distribution of one or more invoice lines to multiple account distributions. This includes the ability to auto -distribute account distributions. System provides the ability for vendors (via self service) to generate an invoice based on hhe p� F�s,So afar Ipi"'PO Fliq$ ), System provides �he ayrack back out invoices entered in error, with aoPr(�Dria aCa,5..counti q elltnI System a s users�o determine whether payment methods carried forward from the purchase order can be changed. System supports an automated matching process and gextbiltry to determine by order type whether a two-way, three-way or fou%ay match i required and the documents 7,quired to be nmcesse! I puchase order and invoice I Purchase or er and rpce vigg info nation I Purchase order, rvolce an recpa7a report I Pumhase order, nvoice, Inspection and receiving report System provides the ability for a successful match, If all match criteria are met, to generate a transaction to the Accounting module to liquidate the �nGppmbrangp end establish a vouch er savable. yslem provides the ability for establishing optional user -defined tolerances (percent and dollar), controlled by line item, total emount, commodity and/or by order type, whereby an invoice amount may diner from the purchase order and still be processed provided suf Iclent budget lavailabilitv and aDDroval autho 'tv exists. l allow for ther1N1a;Im'141 System provides the ability to allow for the release of payment request information to Accounts Pavable module. §ystem provides the ability to automatically calculate payment discounts ased on ver�9pr iZoiWp erins and paY date. vs`am DrOv drips thhee ay l jv k0 rapjure due daje a d discount date. vs amp es the a Ity to capfyf@��qy�n sratained. System provides edits to ensure ddduell p e Invoices are not processed from the same vendor Q.e., invoice amount, unique vendor ID, invoice number, invoice line number. Invoice date combinaflon) unless a user has over -ride authority to enter duplicate invoice numbers. Svstam DrOv Q�S a report Of Potential tlUDIICate Ir1VOIC8S. System provides the ability to allow payment to be charged to an accounting area other than that of the associated PO with proper authority. Encumbrance liquidations are to be based on the original PO. SF SF SF SF SF SF SF MI SF SF SF SF SF SF SF SF SF SF SF SF SF MI SF SF SF SF Payables Payables Pavables Payables Pavables Pavables Pavables Payables Payables Payables Pavables Pavables Payables Pavables Payables Payables Pavables Pavables Payables Payables Payables Payables Payables Payables Payables Payables LOW LOW SF eSetuements SF Payables MI Payables I LOW SF Purchas�nq\Pavables SF Purchasing Payables SF Purchasinq�avables SF Purchasing,'I'ayables SF Purchasing, Payables SF Purchasing, Payables SF I Payables SF Payables SF Payables SF Payables SF Payables RO I Payables I LOW SF Payables i P2 09 0 17 00 P2-09-03-12-00 09 - Goods and Services Rca Line descri �llon SF Purchasinq P2 09 01 1� 00 P2-09-03-13-00 09 - Goods and Services R�inII AccountingNundlnD information (no update catiabllitiesl Ficot SF Purchasinq P2 09 0 14 00 P2-09-03-14-00 09 - Goods and Services Quantl)y received SF Purchasinq P1 09 03 1$ 00 P2-09-03-15-00 09 - Goods and Services Rcotl! Quantjly retorted SF Purchasinq P2 09 03 6 00 P2-09-03-16-06 09 - Goods and Services Rcp Reason for retortion SF Purchasina I P2 09 03 1 00 P2.09-03-17-00 09 -Goods and Services Rca((( QuantlN accepted SF Purchasina 1 P2 D9 03 11�N( '�'Q 09 - Goods and Services Rcoj Quantity backordered SF Purchasinq I P2 0 1 W �Q� 09 - anO�Servjcea Rcp{+ Condition SF Purchasino I P2 rOMr Q 2 I10U\Orl pg-Q 22a 09 - s andServices Rco Recelver�liljpant5 SF Purchasinq P2 0 P2-09-04-00-00 09 - Goods and Services Rcpt System prove es a ability to carry forward specified data captured on the SF Purchasing purchase requisition and purchase order to the receiving report to reduce date entry, but also provide the ability to require receivers to key contain P2 03 05 00 data items (e.1., physical count) from the receivini ticket. 00 P2-09-05-00-00 09 - Goods and Services Rcpt System provides the ability to record multiple receipts and invoices against SF Purchasing ante PO or PO line. P2 09 06 00 00 P2-09.)6-00-00 09 - Goods and Services Rcpt System provides the ability to reverse a receipt transaction and reverse all SF Purchasing other scllons triggered by the original receipt until an invoke is entered. P2 09 07 00 00 P2.09-07-00-00 09 - Goods and Services Rcpt System provides the ability to capture items such as lot number, serial SF Purchasing, Asset number, asset tag number, and expiration date at time of receipt. Management, Inventory P2 09 08 00 00 P2-09.08-00-00 09 - Goads and Services Rcpt System provides the ability to trigger Accounts Payable process based SF Purchasing, Payables upQO reeI t of receivef� req�if information_ P2 09 09 00 00 P2-09-09-00-00 09 - Goods and Services Rcpt System provides the ability to ilag items received as "placed in service' as SF Purchasing, Asset a fixed asset upon receipt of 000d. Management P2 04 10 00 00 P2-09-10-00-00 09 - Goods and Services Rept System provides the ability to over -ride the "placed in service' status of a SF Purchasing, Asset fixed asset that's been received if it requires additional inspection or Management assambly before use. P2 09 11 00 00 P2-09-1 i-0o-00 09 - Goods and Services Rcpt System provides the abildy for receivers to view receiving instructions on SF Purchasing race ).Dt(e.a.% 1pspyyapttiopry /pQular , uarantine etc. P2 09 12 00 I'10 P2-09-12-00-00 09 -Goods orb Services Rcpt Sysfem provides fhe abilty to sunlit receiving data y user ID, date, 6me, etc. including: P2 09 12 01 00 P2-09-12-01-00 09 - Goods and Services Rcpt Compliance with delivery requirements RQ Purchasing MEDIUM This would be delivered functionality with the EPM solution. P2 09 12 02 DO P2-09-12-02-00 09 - Goods and Services Rcpt Condition of goods RQ Purchasing MEDIUM This would be delivered functionality with the EPM P2 09 12 03 00 P2-09-12-03-00 09 - Goods and Services Rcpt Rejection of goods RQ Purchasing solution. LOW 4his would be delivered functionality with the EPM solution. P2 09 12 04 00 P2-09.12-04-00 09 - Goods and Services Rcpt Over and under shipments RQ Purchasing LOW This would be delivered functionality with the EPM solution P2 09 12 05 00 P2-09-12-05-00 09 - Goods and Services Rcpt Commodity substitutions RQ Purchasing MEDIUM This would be delivered functionality with the EPM solution. P2 09 13 00 00 P2-09-13-00-00 09 - Goods and Services Rcpt System provides the ability to support barcode technology to be used to TP MEDIUM � t I ormate0n. ai liili,i.�lhi ... .-, ,. .. .._ _. .. .... ,� _.« >/ —., �� �. ,Y P2 10 Of OD 00,P,. 2-10-01-00-00 10 - Vendor Invoice System provides the ability for electronic invoice acceptance via XML or SF Payables EDI P2 10 02 00 00 P2-10-02-00-00 10 -Vendor Invoice System provides the ability to allow the on-line entry of hard -copy invoices. I SF I Payables P2 10 03 00 00 P2-10-03-00-00 10 - Vendor Invoice System provides the ability to carry forward pertinent purchase order and SF Purchasing, Payables receipt data to the invoice entry screen to reduce data entry and allow for entry of invoice data required for matching/payment processing. P2 10 04 00 00 1!`2-10-04-00-00 10 - Vendor Invoice System provides the ability to capture the following invoice information: P2 10 04 01 00 P2-10-04-01-00 10 - Vendor Invoice Invoice number SF I Payables I 1 P2 10 04 02 00 P2-10-04-02-00 10 - Vendor Invoice Invoice date SF Payables I P2 10 04 03 00 P2-10-04-03-00 10 - Vendor Invoice II voipe fppeiy9Q date Payables I P2 10 04 04 00 P2-10-04-04-00 10 - Vendor Invoice �nvo ce d d SSF F Payables I P2 10 04 0 00 P2-10-04-O6-00 10 - Vendor Invoice Purchase order number SF Payables I P2 1QQ 04 O6 QQ P2.10.04-06-00 10 • Vendor Invoice PO Date SF Pavables I P2 04 Oj M P2-10-04.07-00 10 - Vendor Invoice PO line number SF Payables I P2 1 0 04 0 00 P2.10-04-OMO 10 • Vendor Invoice Vendor name SF Payables I I I P2 10 04 09 00 P2-10-04-09-00 10 - Vendor invoice Ve pr bar/addryss code(s) SF Pavables I I P2 10 04 ?, 00 P2-10-04-10-00 10 - Vendor Invoice Inca ce me item number SF Payables I I P2 10 04 1 00 P2-10.04-11-00 10 - Vendor Invoice Quenty invoiced SF Payables I P2 1d 04 12 OCR P2-10.04-12-00 10 - Vendor Invoice Quill received SF Pavables Captured on Receipt. I I P2 10 04 13 p(j P2-10-04-1"0 10 - Vendor Invoice QuanbP ordered SF Pavables Captured on Purchase Order. I 1 P2 1Q 04 14 00 P2-10-04-14-00 10 - Vendor Invoice Quantity returned SF Pavables Captured on Receint. I P2 10 04 15 {1 l-0 P2-10-04-1"0 10 - Vendor Invoice �ev hreclo� SF Payables P2 1 ,, Q� 1 00 P2-10-04-16-00 10 - Vendor Involca pity lnvokad Payables LOW I P2 70 Qq JJI 00 P2-10.04.17-00 10 - Vendor Invoice Unit of measure SF Payables I I P2 10 (jd 1 00 P2-10-04-1"IS 10 - Vendor Invoice Line Item description SF Payables City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 358 of 418 I 1 I I 1 I 1 l 1 r M 1 1 1 1 Ems:. M [ :It M I P2 07 01 01 00 P2-07-01-01-00 07 - Purchse Order Issuance EDI SF Purchasing 1 P2 07 01 02 0o P2-07-01-02-00 07 - Purchse Order Issuance Hard-copv SF Purchasing P2 01 01 03 00 P2-07-01-03-00 07 - Purchse Order Issuance Facsimile SF Purchasing ity must have third -party fax software and hardware. I P2 07 01 04 00 P2-07-Ot-04-00 07 - Purchse Order Issuance Email SF Purchasing P2 07 01 Ot 00 P2-07-0 1 -05-00 07 - Purchse Order Issuance Direct supplier interface via XML SF Purchasing, eSupplier Connection P2 61 02 OQ 00 P2-07-02-00-00 07 - Purchse Order Issuance System provides the ability to allow user defined onlinefreal-time and batch SF Purchasing Dlinting of P7re gr.o b'1'(y P2 07 03 00 00 P2-07-03-00-00 07 - Purchse Order Issuance [riling provides !1 slot l�(y to view and print a draft PO (with a watermark SF Purchasing or other method of identWrr��q, that it is draft . P2 07 04 00 00 P2-07-04.00-00 07 - Purchse Order Issuance System allows use to reprint hard -copy o>] purchase orders and change SF I Purchasing orders when re wired. P2 08 01 GC 00 P2-08-01 -DO-00 08 - Purchase Order Actg System provides the ability to define auto -distribution rules and apply to the SF Purchasing PO, using standard, user -defined distribution code by accounting line Rem. P2 Od 02 00 00 P2-08-02-00-00 08 - Purchase Order Actg System provides the ability to track multiple releases, receipts, and SF Purchasing, Payables Qavments against a sinllle contract at line Rem level. P2 08 03 00 00 P2-08-03-00-00 08 - Purchase Order Actg System provides the ability to allow for mixed allocations to accounting SF Purchasing distributions on the same purchase order (e.g., some commodity lines are allocated by percentage, some by dollar amount and some by prescribing a specific accounting string to one or more lines). P2 08 04 DO 00 P2-08-04-00-00 08 - Purchase Order Actg System provides the ability to reopen a purchase order if the purchase SF I Purchasing order was closed in error/with app(opria{e securl` nQGpIdures). P2 08 05 00 00 P2-08-05-00-00 08 - Purchase Order Actg System provides the ability to create and process indivi ual POs under an MA Purchasing HIGH This functionality is not existing manual encumbrance. currently available and will need to be created using PeopleTools. P2 08 06 00 00 P2-08.06.00-00 08 - Purchase Order Actg System provides the ability to generate the appropriate accounting entries SF Purchasing based on the PO change notice, including but not limited to increasing or decreasing the encumbrance. P2 08 07 00 00 P2.08-07.00-00 08 - Purchase Order Actg System provides the ability to automatically close a purchase order when SF Purchasing all cemmoddies/services are received and the final invoice is paid. P2 08 08 00 00 P2-08-08-00-00 08 - Purchase Order Actg System liquidates remaining/outstanding encumbrance, if applicable, when SF Purchasing a purchase order is finaly closed. P2 08 09 00 00 P2-08-09-00-00 08 - Purchase Order Actg System provides the ability to carryover open purchase orders to the SF Purchasing, General Ledger following fiscal year for operating funds that use annual budgetary control. P2 08 10 00 00 P2-08-1 0-00-00 08 - Purchase Order Actg System provides the ability to allow a PO to be charged to an accounting SF Purchasing distribution other than that of the associated requisition, with proper authority. Pre -encumbrance liquidations to be based on the original rMon. P2 08 11 00 00 P2-08-1 1 -00-00 08 - Purchase Order Actg System provides the ability to configure tolerances by order type (e.g., a MA Purchasing HIGH Purchasing supports percentage or a specified dollar amount) whereby a purchase order tolerances between requisition amount may exceed or be below the purchase requisition and still be and purchase orders and processed, provided sufficient spending authority exists; the tolerance purchase orders and vouchers, functionality is optional. however, this is not currently established by order type. P2 08 12 00, 00 P2-08-12-00-00 08 - Purchase Order Actg System provides the ability to have many accounting distributions for a SF Purchasing sin le PO line Rem. Idtlldtlli WIIIIWIIIIIVIIIIIIIIIWV�tl111VV(P�i I11 I1I11ill, IllltluW�11116NI�li�nillfllllWliIIIII�IIOGIIiIIIIIIIiIIiYisltlVlViIVVIIIiV�ii�lluliull9l�l�e�lll��'IIIVVV�Iilh��li 19�,u1��i�I iVI� � ="` PZ OS 0f 00 00'P2-09-01-00-00 09 - Goods and Services Rcpt System provides the ability for decentralized recording of the receipt of SF eProcurement, Purchasing goods and services, and provides for the receipt of goods and services to be recorded online on an electronic receiving report by authorized personnel, resulting in an Immediate update of the purchase order status to reflect the recelot of Tods. P2 09 02 001 001 -09-02-00-001 09 - Goods and Services Rcpt System provides the ability to accept, process, and reporVnquire on over RO Purchasing LOW and under recelots/ withinFe.established business rules. P2 091 03 001 001 P2-09-03-00-00I 09 - Goods and Services Rcpt System provides the abilty to capture file following receipt information, Including but not limited to: P2 091 03 O11 o01 P2-09-03-01-001 09 - Goods and Services Rot I lecgI 'ng repor( qulnber (system -generated) SF Purchasing P2 091 03 021 1 9-Qr3 z PI 09-Goods and Services Rcpt I eS� ng repo date SF Purchasing P21 091 03 031I P2yq-8,3 ►pjf'`{ Q1 09 -Goods and Services Rcot I are em received SF Pumhasing P21 091 03 041 00000000 Pldot ili1 09 -Goods and Services Rcpt I Receiver User ID SF Purchasing P2 09 Q 04 011 P2-09-03-04-01 1 09 - Goods and Services Rcp I Receiver name SF Purchasing P2 pp 0 U $ 09 -Goods and Services Res) Receiver pho p n�I(�+ben SF Purchasi g P2 0 03 04 Al P4-09-b3-bd�31 09 - Goods and Services Rcp Receiver emali address SF Purchasing P2 D 03 Q�1 CANIS 109 -Goods and Services Rep P/u(,•{�aV or er number SF Purchasing P2 0� 03 06I 1 09 - Goods and Services Rcp Vendor Nu�r SF Purchasing P2 8 03 071 -�r�'(i Qj 01 09 - Goods and Services Rcp Ven pram aOI(�adSF Purchasing P2 09 03 081-09-0 -08�01 09 -Goods and Services Rcp PJ , ass or9�ag'/ IIIna number SF Purchasing P2 091 03 091 �11 e�n"�,'1{� -0 1 09 -Goods and Services Ropt I Ptrro ase order lme�uantity SF Purchasing P21 091 03 1 801 P2-09-03.1 0, 09 - Goods and Services R�Qt I Purchase order Unit of measure SF Purchasing P21 091 03 111 DOI P2-09-03-11-001 09 - Goods and Services Rcp, I Commodity code of item or service SF Purchasing City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 357 of 418 0 P2 05 07 06 00 P2.05-07.06-00 05 - Create Purchase Order Accounting information from the requisition or solicitation SF Purchasing Requisition only. Solicitations I do not have accounting. P2 0151 07 0 00 P2.05-07-07-00 05 - Create Purchase Order Delivery locations) SF Purchasing I I P2 05 07 4 'QP-00 05 -Create Purchase Order Wf) e�(insl� tons SF Purchasing P2 ds 0� 09 ��-Qr9-pp 05 - Create Purchase Order E3ill fo information SF Purchasing P2 0� 07 10 0 0 05 - Create purchase Order Buyer contact information and buyer phone number (assigned by each SF Purchasing department I P2 05 07 11 00 P2-05-07-11-00 05 -Create Purchase Order Vendor poin of GpPtaCt intormaton pulled from the vendor master SF Pumhasinq I I P2 05 01 11 00 P2-05-07-12-00 05 - Create Purchase Order Manufacturer and pga�1t number SF Purchasing I P2 ds 09 00 00 P2-05-09-00.00 05 - Create Purchase Order System provides the abilty for edit checks and validations at the order level includj�q, but not Nmited to the following: I P2 dS 09 01 QQQQ eeTT QQ QQ�� QQ1i-00 OS - Create Purchase Order Valid account codiga �stribution SF Purchasing I I P2 05 09 02 1 P2-0�09-OZ-00 06 -Create Purchase Order Valid commodi code SF Purchasing I I I I P2 0 09 03 pg0�0j 05 - Create Purchase Order aid Vr��po(jegpt. aal SF hasing 1 P2 09• 04 P2-0P2-0509-04-00 05 - Create Purchase Order p9-03-00 pler t yt. fields SF Purchasing I P2 Q� (�Q P2-05-09-05-00 1 05 - grea�e Purcrysse (Zrtjpr Budpe(ar�"lahll`oi11, SF Purchasing P2 10 0 P2.05-10-00-00 05 - ea a purchase Order System prow es (he a i(y allow entry of payment terms other than the SF Purchasing vendor standard on the p}d[ a rd� r. l+ P2 05 11 00 00 P2-O5.11-00-00 05 - Create Purchase Order System provid((es the ebl('rty determine volume discounts from a contract SF Purchasing or reement at line 1 level). P2 05 i ass Svs(e�mmpnyee Me ability to �,atoA I P2 05 12 0od 0 P2-OS-12-0-0 05 - Creaks Pure u ase roe oil SF Purchasing I 1 P2 1� 02 00 P2-05-12-02-00 05 - �eate eum"se Order descnphon SF Purchasing ( P2 A IS9 12 03 00 P2-OS12-03-00 OS - reate purchase Order Qart SF Purchasing P2 OS 12 d6 P2-05-12.04-00 05- Gregl`e u ase Order class SF Purchasing _ PP2 12 r�04 P2-05.12-06-00 Pu�ase 4jv 6nit q0q5 O6 0000 05 - Create Order of measure SF PurcSF hasing I I P2 0� 12 07 00 P2-05-12-07-00 05 - Create Purchase Order dollars SF Purchasing P2 05 12 08 00 P2-05-12-08-00 05 - Create Purchase Order vendor SF Purchasing - 02 04 12 09 00 P2-05A2-09-00 05- Create Purchase Order account SF Purchasing _ P2 Cis 13 00 00 P2.05-13-00-00 05 - Create Purchase Order Slam provides the abilil`(foI purchasers to: P2 05 13 01 00 P2.05-13-01-00 05 - Create Purchase Order Inser(vendors quoted delivery date or start and end of service dates SF Purchasing P2 D 1$ 0I 00 P2-05-13-02-00 05 - Create Purchase Order Insert -best and final' price if different from offered price SF Purchasing P2 d J�'-. Q 06 P2-05-13-03-00 05 - Create Purchase Order Refine text from solicitation that does not affect propr4y of award SF Purchasing _ P2 05 73 00 P2-05-1 3-04-00 05 - Create Purchase Order Add/Select PO terms and conditions and carry forward terms and SF eProcurement, Purchasing, conditions from the requisition or solicitation Strategic Sourcing - P2 05 1$ d5 00 P2-05.13-05-00 05 - Create Purchase Order Attach files SF Purchasing P1 N 13• 06 00 P2-W13-06-00 05 - Create Purchase Order Designate attached files as internal (department use only) or external SF Purchasing (distributed to the vendor uppJ� PO issuance) P2 0 13 07 00 P2.06-13-07-00 0 - g:a(9 Purchase Order Look-uo PO by envy of the (ellowina fields: I I P2 13 08 00 P2.05-13-08-00 05 -Create purchase Order purchaser I SF Purchasing I P2 13 09 00 P2-05-13-09-00 05 -Create Purc�+�ILh,'ase Gpfrt(aq number I SF Purchasing rl lr I SF asing Q0 QOrder chasing P2 05 11 12 OO P2-O5-13-12-00 05 - Create urchase O�er Comm,e�rtleas I SF PurSF P2 Q5 1? 13 00 P2-05-13-13-00 05- Create Purchase Order vendor BE status I RO Purchasing LOW I P2 OS 11 14 00 P2-05-13-14-00 05 - Create Purchase Order requisitions I RO Purchasing LOW P2 05 13 15 00 P2-05-13-15-00 05 - Create Purchase Order resuisition number SF Purchasing P2 05 13 16 00 P2.05-13-16-00 05 - Create Purchase Order +I solicitation or bid number (if applicable) SF Purchasng P2 05 13 17 00 P2-05-13-17-00 05 - Create urchase Order PO number SF Purchasing I P2 05 13 18 00 P2-05-13-18-00 05 • Crea(p Purchase Order department SF Purchasing I P2 05 13 19 00 P2-05-13-19-00 05 - Create purchase Order vendor name SF Purchasing I P2 3 1 2 06 P2.05-13-20-00 05 - Create Purchase Order vendor iD SF Purchasi P2 13 21 00 P2-05-13-21-00 05 - Create Purchase Order Cancel PO for re -sourcing (resource from original solicitation) SF Purchasing, Strategic $omcing Ily P2 OVA 13 22 00 P2-05-13-22-00 05 - Create Purchase Order Default method of payment from vendor master to carry forward to the SF Purchasing, Payables gF �(] iAbilitynvoiced rI,a Q (�(j) r� (payment P2 l75 14 00 00 P2.05- 4-00-0 05 - Create Purrchase Order Systtem provides�he abilty folcancel aPb and liquidate the encumbrance SF SF Purchasing, General Ledger P2 06 01 00 00 P2-06-01-00-00 06 - Purchase Order Changes System provides the ability to change purchase orders following issuance to the vendor: j P2 06 01 Ot 00 P2-06-01-01-00 06 - Purchase Order Changes Add an additional line item, route through workflow based on business SF Purchasing rules (e.g. pricing Weshold changes, addition of special material workflow, etc. 1 01 06 01 02 e2 �¢Q1 Q O6 -Purchase Ober Changes Delete an axis my line item SF Purchasing P2 OB 01 03 P2-06-01-0 06 - Purchase Order Changes Change an existing line Item (price, quantity, or commodity), route SF Purchasing through workflow based on business rules (e.g. pricing threshold changes. addition of special material workflow. etc.) P2 06 01 04 00 P2-06.01-04-00 06 - Purchase Order Changes Change an existing line item (accounting Information), route through SF Purchasing workflow based on business rules I P2 06 Ot OS DO P2-06-01-05-00 06 - Purchase Order Changes Change internal and external text SF Pufchasin9 I P2 06 01 0 00 P2-06-01-06-00 06 - Purchase Order Chan es Cann a derive locations SF Purchasi y� ... ... i r. :se 1`IIu <sssp ,✓,ar'gdi�`I", .. -. _.:„f''F��.z. �. P2 07 07' 00 00 P2-07-01-00 00 07 - Purchse Order Issuance ystem suDPorts the followinq technology for order issuance: City of Fork Worth / CIBER, Inc. Professional Services Agreement Page 356 of 418 1 1k I 1 ! 4 k t 1 1 1 1 1 I ! I I + I 1 k I I I I I I P2 04 03 16 00 P2-04-03-16-00 04 - Contract/Catalog Content Quantity SF Purchasing Managpeqment P2 04 03 17 and 00 P2-04-03-17-00 04- ntract(Catalog Content Geographic designation (City, State Highway District, other) MI Purchasing and Management P2 04 03 18 00 P2-04-03-18-00 04 - Contract/Catalog Content Lead time for delivery SF Purchasing and MenaQQsment P2 04 03 1s 00 P2-04-03-19-00 04- Contract/Cafelog Content Shipping and handling requirements MI Purchasing and ManagemJ^ent P2 04 03 20 00 P2-04-03-20-00 04 - ContracVCatalog Content Packaging information MI Purchasing end Management P2 04 03 21 00 P2-04-03-21-00 04 - ContracUCatalog Content Commodity codes/NIGP code SF Purchasing and Mona (�ment P2 04 03 22 00 P2.04-03.22-00 04 - ContracVCaigqasslJJo^ng UPC code MI Purchasing and M ['Content P2 04 03 23 00 P2-04-03-23-00 04 • ContracUCafalog Content Long description (at least 8,000 alphanumeric characters) per line Rem SF Purchasing and Mana�e1ment P2 04 03 24 00 P2-04-03-24-00 IM - ContracVCatalog Content Short description (at least 255 alphanumeric characters) per line item SF Purchasing and Manappff��ment P2 04 03 25 00 P2-04-03-25-00 04. ContracVCataiog Content Unit Price and effective dates SF Purchasing and Managqrme t I P2 04 03 26 00 P2.04.03-26-00 04 - ContraG/Cala�og Content Accumulators for dollar amount purchased for the month, quarter, fiscal RQ Purchasing and Managpement year-to-date. prior fiscal vear P2 04 03 27 00 P2-04-03-27-00 04 - ContracVCalalog Content Accumulators for quantity purchased for the month, quarter, fiscal year -I RQ I Purchasing and Management to -dale, p . fiscal `(ear P2 04 03 28 00 P2-04-03-28-00 04 • ContracVCatalog Content I SubstRufe/Altemate items I SF Purchasing and Mana ajjnn nt P2 04 04 OOI 00 P2-04-04-00-00 04 • ConUacUCattalog�ontent System provides the ability to update catalog content, inGuding prices, I SF Purchasing and Managpement descriptions. terms and conditions, etc. P2 04 05 OOI 00 P2-04-05-00-00 04 - Contract/Catalog Content system provides the ability to calculate price discounts for catalog items. I SF I Purchasing i and Management P2 04I 06I OOI 00 P2-04-06-00-00 04 - Contract/Catalog Content System provides the ability to accommodate tiered pricing for catalog and SF I Purchasing and Manape/�ant contract Items. P2 04I 07I OOI 00 P2-04-07-00-00 04 • ConVad/Caialog Content System provides the ability to attach and view vendor terms for catalog SF I Purchasing aril Management items (e.a., Ini U/n uantin ) P2 04I 01 001 00 P2-04-08-00-00 04 - ContradlCatalog Content (System provides abi � for users to search catalogs for items using wild SF I eProcurement, Purchasing I and Managpe�ment card charac(?jjss off' a �rypJds. P2 04I 09I OOI 00 P2.04-09-00-00 04 - ContracUCalalo9 Content System provrdes the ability to attach files in industry standard formats to I MI I Purchasing P2 04I 10I 001 and ManpagQement 00 P2-04-10-00-00 04 - Contraci/Ca{alog Content commodity records (et. off ipg, xis, doc, URL link, etc.). System provides the ability for an online interface for vendors to update MA Purchasing and Management and maintain catalog datalcontent. I s(', imam,mom— P2 05 01 00 W P2-CS01.00-00 05 - Create Purchase Order System provides the ability to have multiple line items per purchase order SF Purchasing with capability for one / multiple delivery schedules per line printed on WWrchase order. P2 OS 02 I� 00 2-OS02-00-00 OS -Create Purchase Order System provides the ability to create purchase orders from requisitions, SF Purchasing, Strategic Sourcing solicitations, and contracts. Information from documents cables forward to the PO. P2 05 03 00 00� P2-05-03-00-00I 05 - Create Purchase Order System provides the ability to support user creallon of PO by copying an SF Purchasing I1I exis,jinp PO�editigp an r�S�`(ing Iith p r i PO number. P2 05 D4 00 00 P2.OSO4-00-00I 05 - Create Purchase Order System provides the a fluty for a point and click' interface to select the SF eProcurement, Purchasing requisition lines to carry forward to the PO being generated. P2 05 05 00 001 -05-05-00-001 05 - Create Purchase Order IS em vfovides the ability to: P2 05 05 01 001 P2-05-05-01 -001 05 - Create Purchase Order I reaie a single purchase order with line items from a single purchase SF eProcurement, Purchasing, reouisition/solicitation Strategic Sourcing P2 05 05 02 001 P2-05-05-02-001 05 - Create Purchase Order Create a single purchase order with line items from multiple purchase MA eProcurement, Purchasing, requisitions/solicitation Strategic Sourcing P2 05 05 03 001 P2-O5-O5-03-00I 05 - Create Purchase Order Create multiple purchase orders with line items from a single purchase SF eProcurement, Purchasing, I (eauisitionlsolicitallon Strategic Sourcing P2 05 05 04 4-0 00 P2-05-05-001 05 - Create Purchase Order Create multiple purchase orders with line items from multiple purchase MA eProcurement, Purchasing, requisitions/sollettation Strategic Sourcing P2 05 06 00 00 P2-O5-O6-00-001 05 - Create Purchase Order system provides the ability to generate a purchase order (on an exception SF Purchasing basis) without first processing a purchase requisition based on department business rules for authorized users. P2 05I 07 001 00 P2-05-07-00-00 05 - Create Purchase Order System provides the ability to carry forward any data maintained in the purchase requisition and solicitation to the purchase order in order to reduce data entry. Data to carry forward at a minimum (accessible, but whether to print is opionall: P2 05I 07 01I OOI P2-05-07-01-00 05 - Create Purchase Order I Commoditycode itemnumber with system -generated description and SF Purchasing additiona,on I P21 051 071 021 001 P2-05-07-02-00 05 - Create Purchase Order I Unit price goofed by the vendor SF Purchasing I P21 051 071 03 001 P2-OS07-03-00 05 - Create Purchase Order I Unit of measure SF Pumhasino 1 P2 QQ 1 071 04 00 P2-oS07-04-00 05 -� Fels eurchase Order Freg4� cv of Service Delivery I I SF Purchasing I P2I 0 071 O5 OOI P2-OS07-OS-0OI OS - Create Pu chase Order QuanEIN SF Purchasing City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 355 of 418 LOW 9.1 User -Defined Contract Fields should address. LOW LOW LOW LOW LOW LOW Captured on Item Definition LOW MEDIUM This functionality is not currently available and will need to be created using HIGH �equisitlons, yes. Not solicitations. Solicitations are awarded individually. HIGH Requisitions, yes. Not solicitations. Solicitations are awarded individually. i P2 03 01 01 00 P2-03-01-01-00 03 - Commodity/Service Lines Line number ( sequential and accommodate up to 999 lines items per SF Purchasing PO) I PT Q 01 02 00 P2.03-01-02-00 03 - Commo/JJ'jj !Service Lines QuenIty ordered SF Purchasing P2 0j 01 03 00 P2-03-01-03-00 03 - Comrnodhy�Service Lines Tent field (to record reason for any difference between quantity SF Purchasing re, Qyested and guanliry ordered) P2 03 01 04 DO P2.03-01-04-00 03 - �ommodjj�Servr Linea Umt of measure SF Purchasino f P2 03 Ot OS 00 P2-03-01-05-00 03 - omnw�i�� )�Serviice Lines Unit pfica SF Purchasing I P2 03 01 06 00 P2.03-01-06-00 03 - Comoro' fService Lines Total line amount SF Purchasing P2 I P2 03 03 0 0' 01 08 OO P2-03-01-07-00 03-Comnmo �ervice Lines 00 P2-03-01-08-00 03 - Comoro (Service Lines Item des�7ption Comm Iffy code validated against commodity master SF SF Purchasinq Purchasing i P2 Q 0 Q9 ,i.. Linea OC P2-03-01-09-00 03 - Qpm#;zm Manufacturers name SF Purchasinq I P2 0 0' {8 00 P2-03-01-10-00 03 - comI ernce Lines Manufactures par) number SF Purchasing 1 P2 03 0 11 06 P2-03-01-11-00 03 - Com/Service Lines Conve on actor e.g., cases to boxes) SF I Purchasinq I P2 0 0 12 00 P2-03-01-12-00 03 - Gqm Lines FOB Terms SF Purchasino I Fr1 0 13 00 P2-03-01-13-00 03 - mce Lines Fretght/Syhiggli efarge SF Purchasinq P2 03 01 14 00 P2-03-01-14-00 03 - Commoy Service Lines Account4y a e emen s at a sub line -item level SF Purchasino P2 03 01 1$ 00 P2-03-01-15-00 03 - Commod/Service Lines Invoics/lhlling address (if entered at header level, value default to SF Purchasing fines] I P2 03 01 1� Oct P2-03-01-16-00 03 - CommodJ'�'�4Service Lines arvice Shi,,)nq address (if entered at header level, value default to linesl SF Purchasing P2 03 01 i1 DO P2-03-01-17-00 03 - Commonkw Lines Delwe insWcllons (if erntered at header level, value default to lines) SF Purchasing P2 03 01 jry SF Purchasin P2 03 � �t�f MI Purchasing P2 03 01 20 OQ P2-03-01-20-00 03-Comrtw ervico Lines Recycled qypo ��faQQ9 MI Purchasinq I P2 01 01 21 00 P2-03-01-21-00 03 - Commod //Service Lines H'Cyc u! material indicator MI Purchasinq P2 03 01 22 00 P2-03-01-22-00 03 - CommodilylService Lines Comment fields (multiple) with indicator designating internal or external SF Purchasing comments (i.e., Internal - only seen by purchasing agents; external - 6int opp PO o be seen by Vendor) P2 03 01 23 00 P2-03-01-23-00 03-CommocIP/Service Lines User aimed ield1 MI Purchasino P2 03 03 01 24 00 P2-03-01-24-00 03 - �om.1 !Seryiip-Lines User Defined Field 2 MI Purchasinq P2 01 25. 00 P2-03-Ot-25-00 03 - omM rvmce Lines User Defined Field 3 MI Pumhasin PT 04 O7 00 00 P2-04-01 -00-00 04 - ContractiCatalog Content System provides the ability to support internal catalogs for. and Management P2 04 01 01 00 P2-04-01-01-00 04- Con1mcVCalalog Content warehouselinventory Items SF Purchasing, Inventory and Menaoo/ymerit P2 04 01 02 00 P2-04-0"2-00 04- ContracUCaWlog Content catalogs for contracted Items, SF Purchasing, Inventory and Man�Q�(neeI P2 04 Ot 03 00 P2-04-01-03-00 04 - ContracUCafalog Content and round trip or punch out capabilities where the vendor hosts the SF aProwrement and Mariayygqment catalog. P2 04 02 00 00 P2-04-02-00-00 04 - Contract/Calalog Content System provides the ability for a catalog management tool for transforming SF Purchasing and Management and cleansing data, importing and exporting content in a variety, of formats, translating various formats (i.e_XML, EDI etc.) P2 04 03 00 00 P2.04-03.00-00 04 - ContractlCattalog Content SystemQprovides the ability or contracts 4o contain the following items, and M It Intl din not to: P2 04 01 01 DO P2-04-03-01-00 04 - ContracVCalalog Contract number SF Purchasing and Manrent P2 04 03 01 00 P2-04-03-02-00 04 - ContracUCalalog Content Contract start date SF Purchasing and Manament P2 04 03 03 00 P2-04-03-03-00 04. ContracVCaCog Content Contract and date SF Purchasing and Mana(c#1@@merit P2 04 03 D4 00 P2.04-03-D4-00 04- Contract/Cafalog Content Vendor part number SF Purchasing and Managqement P2 04 01 05 06 P2-04-03-05-00 04 - ContraWCafalog Content Volume discount price break for each item SF Purchasing and Mariaq�rent P2 04 03 D6 00 P2-04-03-06-00 04 - ContracUCafalog Content Distributor name and number MA Purchasing and Management P2 04 03 07 DO P2-04-03-07-00 04 - Contract/Catalog Content Item specifications (could be a URL link) SF Purchasing and Mariappeerent P2 04 03 08 06 P2.04-03-0"0 04 - ContractlCalalog Content Recycled content percentage MI Purchasing and Ma QeJ^�nt P2 lM 03 09 00 P2-04-03-09-00 04- Conlracf� acc Content Recycled content type MI Purchasing and Managqement P2 04 03 10 00 P2-04-03-10-00 04.Contract/Catalog Content Manufacturer name SF Purchasing and Managqeement P2 04 03 11 00 P2.04-03.11-00 04 - ContracUCatalog Content Manufacturer part number SF Purchasing and Manaagqerrant P2 04 03 12 o6 P2-04-03-12-00 04 - CentracUCatalog Content Manufacturer URL MI Purchasing and Maria((a1eement P1 04 03 13 00 P2-04-03-13-00 04 - ContraWCatalog Content Unit of measure SF Purchasing and Managqement P2 04 03 14 00 P2-04-03-14-00 04-ContracUCaialog Content Alternate unit of measure SF Purchasing and Managqement P2 0403 15 00 P2-04-03-15-00 04.0wire d/Caialog Content Minimum order quantity SF Purchasing and Management City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 354 of 418 i t 1 h 1 1 1 1 1 1 1 Done at the time of receipt. LOW LOW LOW LOW LOW LOW HIGH This functionality is riot currently available and will need to be created using PeopleTools. LOW 9.1 User -Defined Contract Fields should adtlress. LOW 9.1 User -Defined Contract Fields should address. LOW 9.1 User -Defined Contract Fields should address. I P2 01 22 05 00 P2-01-22-05-001 Ot - ContmctlAgreement User -defined milestones 8 thresholds I SF Purchasing, Supplier Contract Administration Management P2 01 22 06 00 P2-01-22-06-00 01 - Contract/Agreement Discounts I SF Purchasing, Supplier Contract Administration Management P2 01 23 00 00 P2-01-23-00-00 01 - Contract/Agreement System provides the ability to attach *comments' to each contract. SF Purchasing, Supplier Contract Administration Comments could be free -forth or standard userdeflned (I.e., selected from Management r�r� myynu or or((p-drt1n Itst . P2 01 24 00 00 P2-01-24-00-00 01 - ContracVAgreement $yslam provides the abili to generate new requisition or solicitation detail SF Purchasing, Supplier Contract Authorized user can create a Administration from the contract detail, with ability to update/modify the information (e.g., Management solicitation in Strategic copy contract Information Into requisition or solicitation document when the Sourcing and copy the contract contract needs to be re -bid . into the solicitation. P2 01 25 00 II 00 P2-01-25-00-00 II 01 - ContracVAgreement System provides the abllity�o convert awarded contract detail to the SF Purchasing Administration sProcuremenl catalog formal (i.e., make awarded contracts available for 1 ` I purchasing from a catalog). Catalogs should also contain the general I �pn,(rad Inf,Tatip/r. P2I 01 261 001 00 P2-01.26-00-00I 01 • Contract/Agreement Sysiam provides the abiliy for contracts and purchase orders to contain SF Purchasing Administration Shipping/Freight terms (e.g., Collect, Prepaid & Add, Prepaid & Allow., I Special Instructions. Blank . P2I 01 27I OOI 00 P2.01-27.00-0OI 01 - Contract/Agreement System provides the abllity�o enter and process net and discount payment I SF Purchasing Administration terms for contracts and a,5e order P2I 01 281 00 1{ 00 P2-01-28-00-00 01 - ContracVAgreement System provides the abr i or the user to enter/track contract amendments I SF �upplier Contract Management I+I Administration and revisions. P2 01 29 001 00 P2-01.29-00-001 01 - Contract/Agreement System provides for notification on expiring contracts and creation of a 9F Purchasing, Strategic Sourcing Authorized user can create a Administration solicitation invitation directly from expiring contract documents. solicitation in Strategic Sourcing and copy the contract into the solicitation. n P2 02 Ot 00 00 P2-02-01-00-00 02. Header Elements System provides the ability to maintain the following header level data elements In respect 10 procurement transactions (accessible from the I header, but ryhtether to print on the PO is optional): I I I P2 ( P2I 021 02I Oil 011 Oil 00 P2-02-01-01-001 ��1-02-01-02-00 02 - Header Elements I PO number I PO I SF SF Purchasinq Purchasino I I I 00 02- Header Elements Chagpa Notice revision number I I I P21 02I 01I 0 00 P2-02-01-03-00� 02- Header Elements PO award date SF Purchasing I i P2 02I 01 O4 00 P2.02-01-04-00 02 - Header Elements I Start Date (for blanket PO's) SF I Purchasing information is stored on Eis e�urchasiz contractP2I 02I 01I 05I OOI P2-02-01-05-0OI 02 - Header Elements End Date (for blanket PO's) I SF Purchasing 1 is lnformahpn is stored on e ourchasinr contract. P21 021 Oil 061 00 P2-02-01-06-001 02 - Header Elements I Maximum Release Amount (for blanket PO's) SF I Purchasing (This information is stored on I the ourchasinq contract. P2 021 Oil 07 00 P2-02-01-07-00 _ 02 - HfWer Elements I Buyer SF I Purchasinq I I P2I 021 011 Q 00-02.01-08-001 02 - Header Elements Buyer dim information (Phone #. Fax #, Email Address) SF Purchasing P2I I 02 0117 00�P2-02-01.09.00 02-Header Elements ,uesferl by I SF Purchasing I Via the requisition. P2I 021 011 001 Pfl.02-01-10-0OI 02 - Header Elements Mrt(1in of orQQFFure an request (Department 8 contact info) MI Purchasinq I LOW I P2I 021 011 11 001 P2-02-01.11-001 02 -Header Elements I Dafa encumbe I SF I Purchasing I IVia the purchase order 1 P21 �l �2I 011 12 00 P2-02-01-12-001 02 - „pair �Es emen`s Re yyppsl 1C���oo (p1. pt rgfor/nalion ( Phone # and Email Address` I I SF Purchasing I Iva the requisition. I P2I 011 13I 00�P2-02-Ot-13-0g1 02-Header Elemen�s Confirm0 MI Purchasinq LOW I P21 021 011 141 00 P2.02-01-14-001 02- Header Elements �s/no1 I Confirtnlnq er ate I MI I Purchasino LOW P2 02 01 1 00I}�P2-02-01-15.00 02 • Header Elements Default requested/scheduled delivery dates (that will default to lines) SF Purchasing P2 02 01 16I 00 P�2.02-01-16-00 02 - Header Elements I Type of procurement transaction (term contract, open market, SF I Purchasing eme�je .etc.) I P2 OZ 011 171 00�P2-02-01-17-00 02 -Header Elements I Default otn ad re5s (that will default to lines) SF I Purchasinq I P2I 021 011 181 001 P�1-02-01-18-00I 02 - Haader Elements I Defaul a i @[v9 $+[d�_4y ioJns (that will default to lines) SF I Purchasinq 1 P2I I 021 O11 19 001 P2-02-01-19-001 02 - Header Elements I Freuencv of Servir a De(ivery SF I Purchasinq I P217 I P2I 021 0117 011 21 00�P2-02-01-20-00 001 P�1-02-01-21-00 02 - Header Elements 02 - Header Elements De suit KvoicelT11ino address (that will default to lines) I Default Parenf terms SF SF I Purchasino I Purchasing P21 021 011 22 001 P2-02-01-22-00 02 - Header Elements I Retain" Terms SF I Purchasinq I 1 I P2I Q�I Otl , �I P2-02-01-23-0OI 02-Header Elements I Solicitalion or bid number (if applIcabie) SF I Purchasing Via Strategic Sourcing Event P2I (j1I 011 f (1♦)I P2-02-01-24-001 02 -Header Elements I Vendor name 8 address SF I Purchasing I fy P2I 021 011 25 001 P2-02-Ot-25-001 02 - Header Elements I endor number SF I Purchasinq I 1 P21 P2I 02 02� 071 01I 00 P9�,� 1- p 00 P2-02�7-27-00� Q rga�gl F AmenjA - 02 -Header Elements I �'j' f talus I ul ple%4proved By' fields, along with approver ID and date time SF SF Purchasino urchasing,Suplier ConVactIstamp �Purchasing, Via Vendor Profile IP2-02-01-28-00I (internal field not to be Included in printed PO). Management P2 02I Ot 21 00 02 - Header Elements M&C reference (for Council approved items) SF Supplier Contract Manrypemen P2 0� 01 29I 00 P2-02-01-29-001 02 - Header Elements Comment fields (multiple) with indicator designating internal or external SF Purchasing comments (i.e., internal - only seen by purchasing agents; external - printed on PO to be seen by Vendor` I P21 0 01 301 DOI P2-02-01-30-001 02 - Header Elements Fiscal Year MI Purchasino I LOW P2 02 02 00 00 P2.02.02-00-00 02 - Header Elements System can be configured to conditionally require a field be populated MI Purchasing LOW when pre -defined conditions are met (e.g., when a PO total Is greater than $25,000, Glen the field that captures the M&C reference should be filled.) P2 03 01 00 00 P2.03-01-00-00 03 -Commodity/Service Lines System provides the ability to maintain the following line item data elements (accessible from the fine item, but whether to print on the purchase order is optional): City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 353 of 418 P2 01 13 04 00 P2-01-13-04-00 01 - ContractfAgreement Quantity (authorized, used, and available) by Calendar/fiscal year by SF Purchasing, Supplier Contract Dollar amounts by year can be Administration line item Management entered as separate contract lines. P2 01 13 09 DO P2.01-13-05-00 01 - Contract/Agmement Dollars (authorized, used, and available) by calendar/fiscal year by line SF Purchasing, Supplier Contract Dollar amounts by year can be Administration item Management entered as separate contract lines. P2 Ot 13 06 00 P2-01-13-06-00 01 - Contract/Agreement Contract status SF Purchasing, Supplier Contract Administration Management P2 01 13 07 00 P2-01-13-07-00 01 - ContractiAgreement Commodity codes SF Purchasing, Supplier Contract Administration Management P2 Ot 13 08 00 P2-01-13-08-00 01 - Contract/Agreement Commodity Class MA Purchasing, Supplier Contract HIGH This functionality is not Administration Management currently available and will need to be created using PeopleTools. P2 01 13 09 00 P2-01-13.09-00 01 - Contract/Agreement Any level of the financial data classification structure SF Purchasing Administration P2 01 13 10 00 P2-01-13-10-00 01 - Contract/Agreement Renewals (authorized, used, and available) MI Purchasing MEDIUM Administration P2 01 13 11 X P2-01.13-11-00 01 - Contract/Agreement Cancellations SF Purchasing Administration a1 01 13 12 00 P2-01-13-12-00 01 - Contract/Agreement Extensions (authorized, used, and available) MI Purchasing MEDIUM Administration P2 01 13 14 00 P2-01-13-14-00 01 - Contract/Agreement Contract type (e.g. Council Approved, City Secretary, Delegated MI Purchasing LOW Administration Authority. etc.) P2 01 13 16 00 P2-01-13-16-00 01 - Contract/Agreement Small and Minority -owned Business status/Other Targeted Businesses, SF Purchasing Administration Inc[ dij�q subcontractor details P2 01 13 17 DO P2-01-13-17-00 Ot - Contract/Agreement Recycled goods indicator MI Purchasing LOW Administration P2 01 13 18 00 P2-01-13-1"0 01 - ContractfAgreement Recycled goods percentage MI Purchasing LOW Administration P2 01 13 19 00 P2-01-13-19-00 01 - ContractlAgreement Contract Administrator's name, phone, fax numbers and email SF Purchasing, Supplier Contract Administration Management P2 01 13 22 00 P2-01-13-22-00 01 - Contract/Agreement User -defined field # 1 MI Purchasing LOW Administration P2 01 13 23 DO P2-01-13-23-00 01 - Contract/Agreement User -defined field # 2 MI Purchasing LOW Administration P2 01 13 24 00 P2-01-13-24-00 01 - Contract/Agreement User -defined field # 3 MI Purchasing LOW Administration P2 01 14 00 Ci P2-01-14-00-00 01 - ContracVAgreement System provides the ability to indicate that insurance certificates and SF Purchasing, Supplier Contract -Administration performance and payment bonds are on file for each contract line Rem. Management P2 Ot 15 00 00 P2-01-15.00-00 01 - Contract/Agreement System provides the ability to track and monitor contractor insurance Administration certificates, flag insurance expiration dates for each contract line Item, and automatical notity the aopnrp��y .a{t, purchasing agent. P2 01 15 01 00 P2-01-15-01-00 Ot - Contrad/Agreement contraZ insurance cerlrflca1a SF Purchasing, Supplier Contract Administration Management P2 01 15 02 00 P2-01-15-02-00 01 - ContractfAgreement flag expiration dates for each contract line item SF Purchasing, Supplier Contract Administration Management P2 01 15 03 00 P2-01-15-03-00 01 - GontractlAgreement notify purchasing agent SF Purchasing, Supplier Contract Administration Management P2 01 16 00 00 P2-01-16-00-00 01 - Contract/Agreement System provides the ability to block the release of all line items if all SF Purchasing Administration �guired items fe.qq i.murancel are not inqIace. P2 01 17 00 00 P2-01-17-00-00 01 - Contract/Agreement System provides ilia ability to track all purchase orders, receipts, SF Purchasing, Payables Administration adjustments, invoices, payments or other reference documents within a single contract. P2 01 18 00 00 P2-01-18-00-00 01 - Contract/Agreement System provides the ability, based on commodities and vendors selected, MI eProcurement, Purchasing LOW The City can, however, limit Administration to provide prompts to requestors and purchasing agents regarding items that are available for purchases that may be covered by existing contracts. purchase to only those on contract. P2 01 19 00 00 P2-01-19-00-00 01 - ContracVAgreement System provides the ability to support various contract periods, including SF Purchasing Administration multiple year contracts (e.g., itloae that span Most and/or calendar years). P2 01 20 00 00 P2-01-20-00-00 01 - Contract/Agreement System provides a configurable print format for purchasing documents. SF Purchasing, Supplier Contract Administration Management P2 01 21 00 00 P2-01-21-00-00 01 - Contract/Agreement System provides the ability to fax, email or print a Blanket Contract/Notice SF Purchasing, Supplier Contract Administration of Award document. Management P2 01 22 00 00 P2-01-22-00-00 01 - ContracVAgreement System provides the ability to support detailed contract performance Administration analysis and generate performance reports, based on the following criteria: P2 01 22 01 00 P2-01-22-01-00 01 - Contract/Agreement Contract compliance (based on compliance criteria as defined by SF Purchasing, Supplier Contract Administration users). Management P2 Ot 22 02 00 P2-01-22-02-00 01 - Contract/Agreement Work completed to date SF Purchasing, Supplier Contract Administration Management P2 01 0 03 00 P2-01-22-03-00 01 - Contraet/Agreement Timelines/deadline dates SF Purchasing, Supplier Contract Administration Management P2 01 22 04 00 P2.01-22.04.00 01 - Contract/Agreement Sub -Contractor performance MI Purchasing, Supplier Contract MEDIUM Administration Management City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 352 of 418 r I 1 t l I 1 11 1 1 1 1 1 1 1 1 1 1 1 I 1i F I I I I I I i I I I I I l 1 I P2 00 14 10 00 P2-00-14-10-00 00 - General Requirements Payment terms SF Purchasing, Strategic Sourcing P2 00 14 11 00 P2-00-14-11-00 00 - General Requirements Bill To information SF Purchasing, Strategic Sourcing P2 00 14 12 06 P2-00. 1 4-12-06 00 - General Requirements Purchaser point of contact information SF Purchasing, Strategic Sourcing P2 00 14 13 00 P2-00-14-13-00 00 - General Requirements Vendor name SF Purchasing, Stratogic Sourcing P2 00 14 14 00 P2.00-14-14-00 00 - General Requirements Vendor number SF Purchasing, Strategic Sourcing P2 00 14 15 06 P2.00.14-15-00 00 - General Requirements Vendor point -of -contact information, pulled from the vendor response SF Purchasing, Strategic Sourcing l P2 00 14 16 00 P2-00.14-16-00 00 - General Requirements Manufacturer and part number Input by vendor SF Purchasing, Strategic Sourcing P2 00 14 17 00 P2.00- 1 4- 1 7-00 00 - General Requirements Department -specific reference number MI Purchasing, Strategic Sourcing LOW P2 00 14 18 00 P2-00-14-18-00 00 - General Requirements Minimum purchase ordder amount SF Purchasing, Strategic Sourcing P2 00 1 5 00 00 for Svslnse3 P2 00 15 01 00 P2-00-15-001-00 00 - General Requirements vendor quoted deliveryability dateor start and end of service dates by SF Purchasing line item P2 00 15 02 00 P2-00-15-02-00 00 - General Requirements Insert'best and final' price, if different from offered price (for SF Purchasing Professional Services Contracts P2 00 15 03 00 P2-00-15-03-00 00 - General Requirements Refine text from solicitation that 8oss not apply to the Purchase SF Purchasing, Supplier Contract I Order/Contract Management f P2 00 15 04 00 P2-00-15-04-00 00 - General Requirements Select Purchase Order/Contract clauses SF Purchasing, Supplier Contract I Management j l P2 00 15 05 00 P2-00-15-05-00 00 - General Requirements Attach files SF Purchasing, Sumpplier Contract Manageent P2 00 16 00 00 P2.00.16-00-00 00 - General Requirements System provides coding reduction techniques to default user -defined SF Purchasing combinations of any element of the financial data classification structure. P2 01 01 00 00 P2-01-01-00-00 01 - ContracVAgreement System provides the ability to convert awarded solicitations to approved SF Purchasing. Strategic Administration contracts, following approval of the award decision. Sourcing, Supplier Contract Management P2 Ot 02 00 001 2-01-02-00-00 01-Contract/Agreement System provides the ability to track the number of contract renewals (total, MI Purchasing, Supplier Contract LOW Administration exercised, remaining). I Management P2 01 03 01 00 P2-01-03-00-00 01 - Contract/Agreement System provides the ability to automatically schedule user -defined contract I SF I Purchasing I Administration releases (be 0 0 daja� gpliar amounts, and quantitiesj. oil P2 01 l n�e'Il n�n�1l 00 P2-Ot-04-00-00 I 01-ContradlAgreement System prov doles the a tty, to encumber contracts or eon{ract releases at SF Purchasing 1 I Administration the Ilne item level. P2 Oil 05l 00 00 P2.01-05-00-001 01 - Contracl/Agreemant System provides the ability to track multiple encumbrances, receipts, and J SF Purchasing J Administration QA`(menIs against a sirryyj�le contract at the line item level. P2I 01I Ohl DO P2-01-06-00-00I 01 - ContracVAgreement System provides the ability to track multiple releases against a single I SF I Purchasing l Administration contract. J ! P21 Oil 071 00 001 P2-01-07-00-00 01 - Contract/Agreement System provides the ability to allow multiple contracts per vendor. SF Purchasing Administration l l P2 01 08l 00 W P2-01-08-00-00 01 - Contract/Agreement System provides the ability to allow a contract to: I l l Administration P2I 01 01 01 00 P2-01-08-01-00 01 - ContraWAgreement I support multiple commodities per contract I SF � Purchasing I Administration 1 P2 01 08 02 00 A2-01-013-02-00 01 - Contract/Agreement support multiple service per contract I_ SF Purchasing Administration P2I Ot 081 03 00 P2-01-08-03-00 01 - Contract/Agreement support multiple delivery dates/locations l - I SF I Purchasing Administration _ P2I 01I 08 04 00 P2-01-08-04-001 01 - Contract/Agreement support multiple option periods I MI I Purchasing MEDIUM Administration P2I Oil 09 OOI 00 A3-01-09-00-00 01 - ContrecVAgreement tys[em provides the ability to dell -down on the contracVagreement to see SF Purchasing Administration the detail of the line items included In the contractlegreement and to view the specifics of each item. P2I 01 10 00 00 2.01-10-00-00 01 - ContractiAgreement System provides the ability for targeted value and quantity contracts with a SF Purchasing Administration user -defined trigger that notifies the purchasing agent when those targets are exceeded or close to beinq exceeded. P2I 01 11 00 00 P2-01-11.00-00 01 - Contract/Agreement System provides the ability to attach electronic documents to a contract SF Purchasing, Supplier Contract Administration Manaqement P2I Oil 12 00 00 P2-01-12-00-00 Ot - ContracVAgreement provides the ability for users to review and print contract text and SF Purchasing, Supplier Contract Administration (System all attachments from within the application, Management l P2I 01l 13 0 00 P2-01-13-00-00 01 - Contract/Agreement provides the ability to allow for contract tracking by: Administration (System P2I 01� 13 01 00 P2-01-13.01-00 01 - Contract/Agreement I Contract number SF Purchasing, Supplier Contract Administration Management P2I 01 13 021 00 P2-01-13-02-00 01 - Contract/Agreement l Vendor SF Purchasing, Supplier Contract Administration Management P2I Oil 131 031 00 P2-01-13-03-001 Ot - ContractlAgreement Date (starting, ending, and order) SF Purchasing, Supplier Contract Administration I Managemi City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 351 of 418 P2 00 02 00 00 P2-00-02-00-00 00 - General Requirements System provides the ability for assignment of a unique purchase order MI Purchasing LOW Purchasing delivers auto number through system -generated means, with a prefix (for purchase order numbering; however, the user - type - blanket, emergency, contract), fiscal year, and sequential number, defined prefixes will require a modification. P2 00 03 00 00 P2-00-03-00-00 00 - General Requirements System provides the ability to differentiate between service procurement SF eProcurement, Purchasing transactions and commodity/supplies procurement transactions. P2 00 04 00 00 P2-00.04-00-00 00 - General Requirements System provides the ability to allow for the retrieval of default vendor SF Purchasing information when creatin new ogjjchase prde� I P2 00 05 00 00 P2-00.05-00-00 00 - General Requirements System provides the; lity to capture and maintain purchasing agent User SF Purchasing j 1D and disdagurchasinyy �Aant activity with dates. P2 00 06 00 00 P2-00-06-00-00 00 - General Requirements System provishe abili(y for an audit (rail of purchase orders to the SF eProcurement, Purchasing, 1 corresponding purchase requisitions, solicitation, contracts, receipts, Strategic Sourcing, Payables invoices, and payments with forward and backward tracking accessible via online queries. P2 00 07 00 00 P2-00-07-00-00 00 - General Requirements System provides the ability to capture receiving instructions and to carry SF Purchasing I` instructions forward to the receipt (e.g., inspection required, quarantine, etc.). P2 00 08 00 00 P2-00-08-00-00 00 - General Requirements System provides the ability to update supply inventory records for quantity SF Purchasing on order H oufphe orQ�J line item is an inventory item. P2 00 09 00 00 P2-00-09-00-00 00 - General Requirements System providdas l e a6it ty to capture a fixed asset indicator (determine MI Purchasing, Asset HIGH Purchasing provides a fixed whether commodity is an asset based on dollar amount and expenditure Management assets indicator on the object code). requisition and purchase order. However, this indicator Is populated based on the Item and commodity selected, not the dollar amount and expenditure object code. P2 00 10 00 00 P2-00-10-00-00 00 - General Requirements System provides the ability to drop the "asset" indicator that was $F Purchasing Authorized users can remove established at the time a requisition was created, if the associated PO the asset prWile from the amount is less than the user -specified dollar threshold, based on the City's purchase order line. business rules. P2 00 11 00 00 'P2-00-1 1 -00-00 00 - General Requirements System provides the ability for zero unit price values (e.g., for kits or SF Purchasing assembly items). P2 00 12 00 00 P2-00-12-00-00 00 - General Requirements System provides the ability to issue purchase order change orders online SF Purchasing and transmit (on demand) the newlchanged purchase order to the vendor using the same delivery mechanism as the original purchase order. I P1 00 13 00 00 P2-00-13-00-00 00 - General Requirements System provides the ability to maintain an audit trail of all purchase order SF Purchasing 1 changes, including the operator and date -time stamp, old and new value. P2 00 14 00 00 P2.00-14-00-00 00 - General Requirements System provides the ability to initiate a purchase order process or award a contract from the solicitation process at the purchasing agent's discretion (e.g., transfer information from the requisition ardlor sollcitation to create a purchase ordericomract). Elements from We solicitation and vendor response that carry over to the purchase order/oontrad, include but are not Iimited to: P1 00 14 0{ 00 P2-00-14-01-00 00 - General Requirements The commodity code item number with system -generated description SF Purchasing, Strategic Sourcing and additional descriptions, or the description from the solicitation P2 00 14 0'f 06 P2-00-14-02-00 00 - General Requirements Unit price quoted by the vendor or updated calculation per the SF Purchasing, Strategic Sourcing P2 00 14 03 00 P2-00-14-03-00 00 - General Requirements Chaser ntity (should be open-ended) SF Purchasing, Strategic Sourcing P2 00 14 04 06 P2-00-14-04-00 00 - General Requirements Line item extensionttotal SF Purchasing, Strategic Sourcing P2 00 14 05 00 P2-00-14-05-00 00 - General Requirements Accounting line information from the solicitation (or requisition, K SF Purchasing, Strategic Sourcing Accounting information is from a requisition) captured on the requisition. P2 00 14 06 00 P2-00-14-06-00 00 - General Requirements g1natV elvery Date SF Purchasing, Strategic Sourcing P2 00 14 07 i00 P2-00-14-07-00 00 - General Requirements Delivery location SF Purchasing, Strategic Sourcing P2 00 14 08 00 P2-00-14-08-00 00 - General Requirements FOB Terms SF Purchasing, Strategic Sourcing P2 00 14 09 00 P2-00-14-09-00 00 - General Requirements Freight Terns SF Purchasing, Strategic Sourcing City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 350 of 418 1 I P1 11 11 07 00 P1-11-13-07-00 11 -Tabulation I Evaluation I Other Criteria and Wei hli I SF Sir "c Sourcin P1 12 01 00 00 P1-12-01-00-00 12 - Negotiation Support System supports requests for revised proposals, such as a request for Best SF Strategic Sourcing and Final Offer P1 12 02 00 00 Pt-12-02-00-00 12 - Negotiation Support System provides the ability to accept multiple revised offers such as a Best SF Strategic Sourcing and Final Offer. P1 12 03 00 00 Pt-12-03-00-00 12 - Negotiation Support System tracks communication related to negotiations for specific bid SF Strategic Sourcing responses P1 12 04 00 00 P1-12-04-00-00 12 - Negotiation Support System tracks responses related to communication requests for specific bid SF Strategic Sourcing c�onses rem, WOM M9092"M ,,.,.2i P1 13 01 OG 00 Pt-13-01-00-00 13 - Award and Notification System provides the ability to facilitate award of purchase orders/contracts: j P1 13 01 01 00 P1-13-01-01-00 13-Award and Notification Single vendor award SF Strategic Sourcing, Purchasing P1 13 01 02 00 Pt-13-01-02-00 13 - Award and Notification Multiple vendors SF Strategic Sourcing, Purchasing P1 13 02 00 00 Pt-13-02-00-00 13 - Award and Notification Svstem provides the abili)y, at the time of award, to: P1 13 02 01 00 Pt-13-02-01-00 13 - Award and Notification Automatically create the appropdate purchase order and encumbrance SF Strategic Sourcing, Purchasing General Ledger P1 13 02 02 00 P1-13-02-02-00 13 - Award and Notification Automatically liquidate any pre -encumbrance SF Strategic Sourcing, Purchasinq, General Ledqer P1 13 02 03 00 P7-13-02-03-00 13 - Award and Notification Immediately print the purchase order at any printer available to the SF Purchasing purchasing aq pnts (local inJnter or on the network) I P1 I P1 13 13 02 02 04 05 00 P1-13-02.04-00 00 P1-13-02-05-00 13 - Award and Notification 13 -Award and Notification Se dyla ou ase orq r via fax Sentj�Y(h[/a pu ase or jr via email I SF SF Purchasinq I I Purchasinq I I Pi 13 02 06 00 P1.13-02-O"0 13 - Award and Notification Se a pu ase or{ ,r Wa XML SF 1 Pumhasinq I Pt 13 02 07 00 P1-13-02-07-00 13 - Award and Notification Send a ply aSP at SF jnQ Pt 13 03 00 00 Pt-13-03-00.00 13 -Award and Notification �l�ro�nte interface with C approval process to I System provides e a I Ml Purchasing record MSC number and date on the award. I I LOW Pt 13 04 00 00 P1.13-04-00-00 13 - Award and Notification System provides the ability to allow a purchasing agent to designate bid SF Strategic Sourcing award vendor(s) in the bid tabulation file based on total bid, by line it am, or I I coJnbinatio, of line items. �ysfem P1I 13 05 00 00 Pi-13-05-00-00 13 - Award and Notification provides the ability to award all line items to a vendor without SF Strategic Sourcing having to click on each line item individually (e.g., "award all' button on the I I screen and an undo button . P1 13 06 00 00 P1-13-06-00-00 13 -Award and Notification tystem provdes the ability o generate an email or fax notification to the SF Strategic Sourcing I be reCeiYlrl a wa(Q I I P1 I 13 07 00 00 Pt-13-07-0000 13 - Award and Notification System provi'Is (�a abi illy to generate an email or fax notification of I SF Strategic Sourcing resection to vendors that did not receive an award, P1 I 13 08 00 00 P1-13-08-00-00 13 - Award and Notification System provides the ability to cancel an award and/or re -award line items SF Strategic Sourcing J or entire award from the original solicitation. I P1 I 13 09 00 00 Pl-13-09-00-00 13 - Award and Notification System provides the ability to track vendor protests from Inception to MI I Strategic Sourcing I MEDIUM conclusion and to suspend the procurement until the protest is resolved City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 349 of 418 I i I Pt 10 02 14 00 P1-10-02-14-00 10 - Vendor If KPB, what percent SF Strategic Sourcing I P1 10 02 15 00 P'610-02-15-00 Response 10 - Vendor Response Contact name SF Strategic Sourcing PI 10 02 16 00 PI-10-02-16-00 Qf�(� esponse 10-iendor Contact date SF Strategic Sourcing P1 10 02 17 00 Pt-10A2-17-00 10-Qyr Ewes Unit gfice SF Stratno Sourcing Strategic Sourcing P1 P1 10 10 02 02 18 19 00 Pt-10-02-18-00 00 P7-10-02-t9-00 10-j� esponse 10-Qprjesponse Unit oT me�spfe/or�dcd A@n Frepuencv0111RIce�OJivery SF SF Stratege Sourcing I P1 10 02 20 00 P1-10-02-20-00 10 - Response Dollar Amount (zero o tars are permitted) SF Strategic Sourcing I Pt 10 02 21 00 P 1 -10-02-21-00 10- Vendor ReaDgrlse Availabill date SF Strategic Sourcing I P1 P1 10 10 02 02 22 23 00 PI-10-02-22-00 00 P1-10-02-23-00 10 - Vendor Response 10 - Vendor Response ��illy? rpmple/t pn date Ident erexcgprlons SF SF Strategic Sourcing SYategic Sourcing I Pt 10 02 24 00 P1-10-02-24-00 10 - Vendor gesponse Comment (text) field (at line and header level) SF Strategic Sourcing 1 I P1 I P1 10 10 02 02 2$ 26 00 P1-10-02-25A0 00 P1-10-02-26-00 1p-Vendor Response 10 - Vendor Response Mlgimu ptQaJ am{tunt Ei�dd reee)pi dale and mime SF SF SVa(�ic Sourcing Strategic Sourcing I I I P7 10 02 27 0a Pt-10-02-27-00 10 - Vendor Response Discount terms SF Strategic Sourcing Strategic I Pt 10 02 28 00 Pl-10-02-28-00 10 - Vendor Response P-card Acceptance (ves/no SF Sourcing I Pt 16 02 29 00 P7-10-02-29-00 10 - Vendor Response Required Licenses and Certifications (e.g., licensed asbestos SF Strategic Sourcing orengineers) Pt 16 02 30 00 P1-10-02-30-00 10-Vendor Response Si1flt/)mePt SF Strategic Sourcing I P1 10 01 31 00 P7-10-02.31-00 10 - Vendor (response Draft certificates of insurance SF Strategc Sourc�o I P1 10 03 00 00 P1-10-03-00.00 10 - Vendor Response System provides the ability for the vendor to attach files to their response. SF Strategic Sourcing P1 t0 o4 oo oo P1-10A4.00-o0 10 - Vendor Response System provides the ability for the vendor to include manufacturer and part SF Strategic Sourcing number bein? bid. P1 10 66 00 A P1-10-05-00-00 10 - Vendor Response System provides the ability for the vendor to indicate the percent and type SF Strategic Sourcing of ra0 material content by line item. P1 10 06 66 00 PI-10-06-00-00 10 - Vendor Response Sysrem allows vendors to propose substitute hems within a solicitation. SF Strategic Sourcing Pt 10 07 00 00 P1-10-07-00.00 10 - Vendor Response provides the ability to support receipt of solicitation responses SF Strategic Sourcing `Systt{em In ides P7 10 08 00 00 P7-10-08-00-00 10 - Vendor Response Shysfam pro the aabi(ity, If solicitation opening date and time has SF Strategic Sourcing expired, to prohibit the acceptance of a solicitation through electronic means. In such rases, an electronic message should be sent to the vendor indkir,,(inq sot cita(Iprt time has closed. P1 10 09 00 00 Pt-10-09-00-00 10 - Vendor Response System provn s the ability for the vendor to receive an automatically SF Strategic Sourcing {Ie rated ca 6r Ill 49on submittal of the sokcitation respPrise. P1 16 to oo 00 P1-10-10-00.00 10 -Vendor Response System provides i�e ability for a vendor to withdraw and resubmit a bid up SF Strategic Sourcing to the bid o enin time with an audit trail. nor �i I I'I' loin�� � �� ��I I�IIiI,u Ili ��J�II� ..... ,. — P1 11 01 00- 00 P1-11-01-00-00 11 - Tabulation / Evaluation System provides the ability to keep all responses secure until userdefined SF Strategic Sourcing opepinq/clos ny date and time except for reers ve auctions). P1 11 02 00 00 Pt-11-02-00-00 11 - Tabulation I Evaluation System prow des me ability to toad solicitation responses in industry MI Strategic Sourcing MEDIUM standard file formats (e.g., Microsoft Excel, Access, etc) for evaluation and than be able to upload back to the system. P1 11 03 00 00 Pl-11-03-00-00 11 - Tabulation / Evaluation System provides the ability to tabulate and award: I I Pt 11 03 01 00 P1-11-03-01-00 11 - Tabulation / Evaluation entire bid jJ��aadraae SF Strategic Sourcing i 1 P1 11 03 02 00 P1-11-03-02-00 N - Tabulation / Evaluation selected ((ne items SF Strategic Sourcing I P7 11 03 03 00 P1-11-03-03-00 11 - Tabulation / Evaluation pre -grouped line items MA Strategic Sourcing HIGH This functionality is not currently available and will need Io be created using PeooleToois. Pt 11 04 00 00 PIA 1-04-00-00 11 - Tabulation / Evaluation System provides the ability for unit of measure conversions and/or ability to SF Strategic Sourcing define specific conversion factors to compare different vendor's responses in the same units. Pt 11 09 00 00 P1-11-05-00-00 11 -Tabulation / Evaluation System provides the ability for purchasing agents to view responses and SF Strategic Sourcing yenQpr coinrr�jl1�jtnIs by line item. P1 11 06 00 00 P1-11-06-00-00 11 - Tabulation / Evaluation Sys{em provides the ability for comparison and summary of multiple SF Strategic Sourcing vendors on a single careen and to automatically identify the lowest bid (overall and by line hem) once all bids have been entered In the rid tabulation file. Pt 11 07 00 00 P1-11A7-00.00 11 - Tabulation / Evaluation System provides the ability to enter the justification for not selecting the SF Strategic Sourcing lowest price bid (e,� , best value criteria). i St I Pt 11 OS Oo 00 Pt-11 A8-00-00 11 •Tabulation /Evaluation System allows for a definition of user -defined evaluation criteria. SF at Sourcing Pt 11 09 00 00 Pt-11-09-00-00 11 - Tabulation / Evaluation System allows for creation and maintenance of user -defined weighting SF Strategic Sourcing factors for application across ail vendors. P1 11 10 00 00 Pt-11-10-00-00 11 - Tabulation / Evaluation System provides access to electronic bid response files to the evaluation SF Strategic Sourcing team (through workflow or other mechanism) as well as the buyer. Pi 11 11 00 00 Pt-11-11-00.00 11 - Tabulation / Evaluation $ys em alloy( yyaaluatio tEtp rpembers to enter evaluations. �iaEes SIF Ic Soule" Pt 11 12 00 00 Pt-11-12-00-00 11 - Tabulation I Evaluation System conso evaluabon team members responses into a single SF S e9tc Sourcing disglev aao�g vepdorq. Pt 17 13 00 00 Pt-71-73-00-00 17 -Tabulation /Evaluation System provides the a lily t0 carry torwartl pertinent solicitation response SF Strategic Sourcing information to the bid tabulation file to reduce data entry. P1 11 13 01 00 PI.11-13-01-00 11 - Tabulation / Evaluation But Number SF Strate�c Sourcing Pt 11 13 02 00 Pt-11-13-02-00 t t - Tabulation / Evaluation Bid Description SF Strateoc Sourcing P1 11 13 03 00 P1-11-13-03-06 11 - Tabulation / Evaluation Buyer Name SF Strategc Sourcing Pt If 13 04 00 131-11-13-04-00 11 -Tabulation I Evaluation Commodity Information SF {fateg� Spurc�g P1 1 f 13 dS 00 P1-11-13-05.00 11 - Tabulation / Evaluation Quantities and units bid SIP ra(pjgtc SOurc)rw P1 tf 13' 06 00 Pt-17-13-06-00 11 - Tabulation / Evaluation Price information SF Stre Vic Sourcing City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 348 of 418 I I I 1 I F 1 I I I 1 I i I 1 I E 1 1 P1 07 05 00 00 P1-07-05-00-00 07 - Solicitetlon Amendment provides the ability for comment fields (multi'pie)about the SF Strategic Sourcing (System amendment both with intemal or extemal comments (a.g., intemal - only seen by authorized users; external - printed on solicitation to be seen by Vendor). P7 08 01 00 00 Pt-08-01-00-00 08 - Vendor Selection System provides the ability to select active, registered vendors to receive the solicitation taking into consideration each of the following (but not limited to): P1 08 01 Ot 001 1-08-01-01-001 O8 - Vendor Selection Vendor commodity reaistration information SF I $)ratect%sourcl; P1 08 01 02 00 P1-08-01-02-00 oe -Vendor Selection Specific vendors SF I Strategc ourana P1 I P1 08 08 01 01 03 00 00 P1-08-Ot.. P1-08-01.04-00 OB - Vendor Selection 08 Selection Geo,' dohlc RBpton Other Ta�raeted Businesses SF I Strategic Sourcing 04 - Vendor (such as veterans or handicaooed) SF I Stratec`c Sourcina P1 08 01 OS 00 P1-08-01-05-00 OB -Vendor Selection Venda identified as sugges ed source by department on purchase SF I Strategic Sourcing �jrge/auletlon P1 08 01 06 00 1-0"1-06-001 08 - Vendor Selection Vefxlor has previous history of responding on a specific commodity MI Strategic Sourcing MEDIUM even If no longer CC s red) P1 08 01 07 08 - Vendor Selection or re-procuriamenfs,'select all vendors that previously bid on the most SF Strategic Sourcing recent version of the prpFjgeJneror.... P1 08 Ot O8 ]PI-O"11-07-001 P1-08-01-08-00 08 - Vendor Selection (e.g., ineligible, suspended, excluded based on ce V dfederaltv SF Strategic Sourcing debarred, etc.)Pi 08 01 09 P1.0B-01-09-00 08 - Vendor Selection Ven JI(p nce MI Strattl Sourcina MEDIUM Pill 081 01 101 001 P1-08-01-10-00 08 - Vendor Selection I SmafUMinodty-owned/Other Targeted Businesses identified as SF I Strategic Sourcing 55}�doDMrbq corqT1�To r$gyp�le pet en pj file �eparGnenl Pt 081 02 OOI OO) PI -08-02-00-001 08 -Vendor Selection fSystem provides thq abi8ty for ffie user / buyer to edit the Isolicile list of re vendors. includina ability to: 1 08 02 Oil 001 P1-0"2-01-001 08 - Vendor Selection iistered 1 Adtl/5u,{tolemen 1 SF I Strategic Soul I Pi l 081 02l 02 001 P 1 -0"2-02-001 08 - Vendor Selection Select/Deselect I SF I Strategic Sourcina I P1 I 08 031 00 001 Pt-08-03-00-00I 08 - Vendor Selection System provides the ability to display during the vendor/bidder selection l I P1I P1 I 08 08 031 031 01 02 0011 -08-03:&001 001 P1-08-03-02-00 08-Vndp`See JIon OS Selection orool Vendor Name I Vendor I SF SF SVateaiq,Sourclno I Sourcina I Pi I 08 031 03 00 P1-08-03- 00 -Vendor I) Selection address JCity and state) Trylenhone tier I Strata Ic I P1 I Pi l 08 08 031 03 04 p5 001 P1-08-03-04-00 001 P1-08-03-05-00 -Vendor OB - ypn p`Sq eG{Ipn 08 Ven�or $election u V nd con F arson I �n I SF SF SF 5rrajeap t5ourclna Strategic Sourclpa I - or co aG onor�(i qu�ritier Strategc Soumina 1 P7I 081 03 061 001 P1-08-03 06 001 08 -Vendor Selection I �(�1jj Opp email address I SF Strata c Sourcina I _ I P1I 081 031 071 001 P1-O8-03-07-001 08-yliltn r$p eq on 1 MW status 1 MI I Strategc Sourcina 1 LOW I P1 O8 03 O81 001 Pt-08-03-OMOI 08 - e eq}[rj Vendor status fill active Inactive. ineligible etc.) / 1 MI 1 Strategic Sourcina LOW P7 08l 04l 001 OOl P7-08-04-00-001 08 - en or a ec on System retains the pre -encumbrance from the original requisition through SF eProcurement, Purchasing, I l the solicitation process. I I General Ledger, Strategic I Sourci II _ 3"hi iiilillilllll 'illlll lu IiIVIiIYVIIWhIYuiilillioiYllY'IIIBIVi!IYIl�tllP11YIIVIIIIYIVIIVVIYIYI�IIIllIIiVYIIllllitltllllYiliIIVYIIIIYtiVIIVIh9VIiJlI!YIYIIiIIYYIIYVV�IYIo'Y P1 09 01 00 00 P1-09-01-00-00 09 - Approval, Release, Post records electronic approvals of solicitations prior to releasing al SF Strategic Sourcing ((Syystem no to P1 I 091 021 00 00� P1-09-02-00-00 09 - Approval, Release, Post ISys�mprovidppes th ability for vendors to search the solicitation Website I SP I Strategic Sourcing for Pt I 09I 03) DO 00 P1-09-03-00.00 09 - Approval, Release, Post provides the ability to track and report which solicitations are sent l Ito MI Strategic Sourcing MEDIUM to or downlq� d �v which vendors. l I P11 09 041 00 001 P1-09-04-00-00 09 -Approval, Release, Post Sysiam provl ea (he ability to automatically send (generate fax, email or SF Strategic Sourcing print letter if no email address is present) addendume to solicitations to I those on a solicitation's bid list. Pt 09 051 00 00 Pt-09-05-00.001 09 - Approval, Release. Post provides the ability to identify vendors that have email or fax 1 lSystem capability, end based on the commodities for which they have registered, 1 electronicallIy send them n.oudinq tta I nts` �nel lesaiption P1 09 05 Ot 00 P1-09-05-01-001 09 - Approval, Release, Post Notiflcatlons of solicitatons w a of each commodity SF Strategic Sourcing 1 being purchased and provide a hypertink that will take the vendor to the I ggpo��t(r'Iteqon do�(�bQ page _ _ I P1 09 05 02 00 P1-09-05-02-001 09 - oroval. Release Post Addenduma Iipthall received the solicitation SF StrataQq�is Sourcina P1 09 05 03 00 Pt-09-OS-03-001 09 - oroval Relekl0s1 ova �olllica or 1 Ill SF Strat P1 09 OS 04 00 P1-09-05-04-00 09- rova� Release -Post of -bP conferences and attachments I SF St 'c Sourl I$IIIIIItlui "I " .. ,. •- ,,� P1 10 01 00 00 Pt-10-01-00-00 10 - Vendor Response System provides the ability to select how responses will be accepted (e.g., SF Strategic Sourcing all li(+e Items pr ngfle. by line Item, etc. . Pt! 101 021 001 00 P1-10-02-00-00 10 - Vendor Response System provides the ability to record s icitation responses for each solicitation. Responses include but are not limited to the following data I elements: P1 101 021 011 00 P1-10-02-01-00 10 - V�nQ�t esoonae �escones Solicitation number I SF ) Strategc Sourcina P11 10 021 02 001 Pt-10-02-02-001 10- I Vendor ID I SF Strategc Sourcina I P1 I 10 021 03 001 Pi-10-02-03-001 10 - V ,nit espouse I Venda name I SF Strategc Sourcina I Pt 1 10 021 04 001 Pt-10.02-04-00 10 - rj fesoonse I V�pgpr Ofder addfes I SF Strategc Sourcina 1 Pit 10 021 05 001 P11-10-02-05-0g 10 - n p RRI::conse I Venda rnvI address I SF Strategc Soul I Pt l 10 021 OB 00 -10-02 10 - pr�tesponse I Venda remlt-to address I SF Strategc Sourci; I P1 10 021 07 OO P1-10.02-07-00 10 • n pr I Vendor contact version I SF Stnil Sourc fa P1I 101 02 08 00 1-10-02.08-001 10 - en jRiesoonse or esponse, Venda phone I SF 1 Strategic Sourcina 1 P11 101 _1221 09l 001 Pt-10-02-09-00I 10 - Vendor Response Vendor fax number SF I Strategic Sourcina I P11 _10 0 10 001 P1-10-02-10-001 10 -Venda Response Venda a -mail address SF Strategc Soul I I P11 10 02 11 0011 0-02.11-001 10 - esoonse MWBE status SF S��rrajjeolc Spurclnq I P11 101 02� 12 001 P1-10-02-12-001 10 -Venda Response Other Tajgeted businesses SF I Srategic Sourcina I Pit 101 02 131 001 P1-10-02-13-001 10 - Venda Response Small/M(Zritv-owned subcontracting (vea/no) SF I Strategic Sourcing I City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 347 of 418 P1 05 06 00 00 P1-05-06-00-00 05 - Solicitations System provides the ability for comment fields (multiple) at the header and SF Strategic Sourcing I line level, with an indicator designating internal or external comments (e.g., internal - only seen by authorized users; external - printed on soictation to 7II be seen by Vendor). P1 05 07 00 00 P1-05-07-OMO 05 - Solicitations System provides the ability to receive electronically solicitation responses SF Strategic Sourcing from vendors, In Industry standard formats such as EDI, as well as via a web 7 or hard co 06 01 00 00 PI-06-01-00-00 D6 - Solicitation ability for the creation of all solicitations, b types of soli both SF Strategic Sourcing qt ITB R O no a P7 i 08 02 00 00 P7-0602-00.00 OB - Solicitation Creation Ses ems v d ern ayes to be y t pro ty, Is� p used in the abllipa develo SF Strategic Sourcing Qevrylopmen ppf RVICitations. P1 OB 66 00 00 P1-06-03-00-00 06 -Solicitation Creation System prov'des fine ability to apply user modifications to the templates. SF Strategic Sourcing P1 06 04 00 00 P1-06-04-00-00 06 - Solicitation Creation System provides the ability for all elements of the requisition to be carried SF eProwrement, Purchasing, over to the solicitation; but be editable by an approved user without Strategic Sourcing affecting the on' trial re��uisition. P7 06 05 00 00 P1-06-05-00.00 06 -Solicitation Creation System provides the abi)ity to separate individual line items from SF eProcurement, Purchasing, isitiona Into separate solicitabons. Strategic Sourcing P1 06 06 00 00 P1-O6.06-00-06 06 - Solicitation Creation ?p System provides the ability to combine like items from multiple requisitions SF eProwrement, Purchasing, into one solicitation. Strategic Sourcing P1 06 07 00 00 P7-06-07-00.00 06 - Solicitation Creation System provides the ability to combine like items from multiple requisitions SF eProwrement, Purchasing, from multiple departments into one solicitation. Strategic Sourcing Pt 06 08 00 00 Pt-06-084)0.00 06 - Solicitation Creation System provides the ability to produce print -ready documents to be sent to SF Strategic Sourcing, Supplier potential vendors/bidders (ay bid documents addenda >� Contract Management P7 06 09 00 00 P1-06-09.00.00 06 - Solicitation Creation System provides the ability kr iYre re -defining oi'need" or start and end of SF eProwrement, Purchasing, service" dates without affecting those entered on the original requisition. Strategic Sourcing P1 06 10 00 06 P1-06.10-OMO 06 - Solicitation Creation System provides the ability to override commodity information in the SF eProwrement, Purchasing, solicitation that is carried )O(wa{(11ig�r py(cryaso (eyyA�ltion. Strategic Sourcing P1 06 11 00 00 P1-O6-11-00-00 O6 -Solicitation Creation System provides the ability o Mach both internal no issued with SF Strategic Sourcing solicitation) and external (issued with solicitation) files to the solicitation documents (e.g,. attach specifications from a MS Word file). P1 06 12 00 00 P1-06-12-00-00 06 - Solicitation Creation System provides the ability for a purchasing agent to select standard terms SF Purchasing, Strategic Sourcing and conditions from a repository within the system for inclusion In the solicitation. P1 06 13 00 00 P1-06-13-00-00 06 - Solicitation Creation System provides the ability to modify the standard terms and conditions. SF Purchasing, Strategic Sourcing P1 06 14 00 00 P1-06-14-0"6 06 - Solicitation Creation System provides the ability to build the solicitation document based on the SF Strategic Sourcing, Supplier purchasing agent selecting items or terms to be included In the solicitation. Contract Management P1 06 15 00 00 Pt-06-15-00-00 06 - Solicitation Creation System provides the ability to define mandatory and optional fields for SF Strategic Sourcing solicitation documents. P1 06 16 00 00 Pi-06-16-00-00 06 - Solicitation Creation System allows users to identify line items on a solicitation as mandatory or SF Strategic Sourcing optional for v 11dolJ ire see. P1 06 17 00 00 P1-O6-17-00-00 06 - Solicitation Creation System provides (or swoon of a solicitation directly from expiring contract SF Purchasing, Strategic Sourcing documents. P1 06 18 00 00 P1-06-18-00-00 06 - Solicitation Creation System provides the ability for a purchasing agent to define bid response the criteria per the following: I P1 06 18 01 00 P1-06-18-01-00 06 - Solicitation Creation Cer&F SF Strategic Sourclfg I I P1 06 18 02 00 P1-06-18-02-00 o6 - Solicitation Creation License SF Straitppc Soumpo I I Pt 06 18 03 00 P1-06-18-03-00 06 - Solicitation Creation Delivef(Tertns =Goals SF Strafeq`c Sourcing I I P1 06 18 M 0o Pi-o6-18.04-o0 06 - Solicitation Creation SF Strategic Sourcing I P1 o6 18 o$ o0 P1-of-i "S-o6 06 - Solicitation Creation Minimum order amount SF Strategc Sourcing I 1 Pt 06 18 06 00 P1-06-18-06-00 06 - Solicitation Creation ExpeCagpe SF Sfajr�. Ic Sj7urlpg I I P1 06 18 07 00 Pt-06-18-07-00 06 - Solicitation Creation User Defined Field 1 SF S'trafegic Sourcing Pf 06 18 08 00 P1-O6-18-08.00 06 - Solicitation Creation User Defined Field 2 SF Strategic Sourcing I P1 06 18 09 00 P1-06-18-09-00 06 - Solicitation Creation User Defined Field 3 SF Strategc Sourcing I P1 06 19 00 00 Pt-06-19-00-00 06 - Solicitation Creation System provides the ability to warn the vendor when ail required fields are SF Strategic Sourcing not entered in the bid response. Pf 06 20 00 00 P1-06-20-00-00 06 - Solicitation Creation System allows some departments, with delegated authority, to create their SF Strategic Sourcing own solicitations while restricting other departments from creating solicitations. P1 07 01 OOr 00 P1-07-01-00-00 07 - Solicitation Amendment System provides the ability to amend solicitations to include: f P1 07 Ot 01 00 Pt-07.01-01-00 07 - Solicitation Amendment add or delete line items SF Strategic Sourcing I P1 07 01 02 06 P1-07-01-02-00 07 - Solicitation Amendment gegp�l¢ notr r o �ndors SF Strajeg `ypurci g I P1 07 01 03 06 P1-07-01-03-00 07 - Solicitation Amendment gpSf to the Ci s Websife MI Strafegic Sourcing MEDIUM I I P1 07 Ot 04 00 P1-07-01.04-00 07 - Solicitation Amendment ability to �fo uce a hard cnpv SF Strategc Sourcing I P7 07 02 00 00 Pi-07-02-0000 07 - Solicitation Amendment System provides the ability to post answers to vendors' questions to the MI Strategic Sourcing MEDIUM 1 C= website as well as distribute responses to the bid list. P1 07 63 00 00 P7-07-03-00-00 07 - Solicitation Amendment Sys em provides the ability to create multiple amendments to a solicitation SF Strategic Sourcing wit version {{�pntrp Pt 07 04 o0 o6 Pf-07-04-00-00 07 - Solicitation Amendment System provides i ability for a revision history on the document with a SF Strategic Sourcing J summary of revisions. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 346 of 418 I I I 1 I I I l I l 1 I U 1 L 1 x I I I i I f F 4 I ! II i i i I I I P1 03 01 27 00 P1-03-01-27-00 03 - Commodity Lines Fixed asset Indicator (new, replacement, or enhancement; if SF I eProcurement, Purchasing, P1 03 01 00 reolacement or enhancement, need extstino tact number) Asset Management I 28 P1-03-01-28-00 03 - Commod Lines Sysyaested vendor number{sl SF eProcuremenl Purchasinq I I P1 03 01 29 00 P11-03-01-29-00 03 - Commod9v Lines S`ug„aested vendor name SF eProcuremenl Purchasino I P1 03 01 30 00 P1-03-01-30-00 03 - Commodity Lines Suaqested vendor emal MI I eProcurement. Purchasino LOW I P1 I P1 03 Ot 31 00 P1-03-01-31-00 03 - Commo' Lines Suagested vp�j� dress(es) MI I eProcurement, Purchasino LOW 03 O1 32 00 P1-03-01-32-00 03-Commodity Lines {�ser Defined Fn{rdl MI eProcurement . Purchasino LOW I P1 03 01 33 00� P7-03-01.33-00 03 - Commod))v Lines User DeOnetl Pield 2 MI I :Procurement. Purchasinq LOW P1 P1 03 03 01 02 34 00 00 P1-03-01-34-00 00 Pt-03-02-00-00 03 - Commo�J(/lr/,y, Lines 03 - Commode Lines User Defined Field 3 System supports multiple line items that are sequentially numbered and MI SF :Procurement Purchasinq eProcurement Pumhasing LOW hat can accommodate ug to 999 lines items perr uisitlon I ,,, . > , fin!°. _,.A'" �+s .3- _ P1 04 O7 00 00 P1-O4-Ot-00-00 04 -Requisition Accounting System provides the ability to allow the initiation of requisitions prior to year. SF :Procurement, Purchasing, end which cannot be c) a -encumbered until budget is available. General Ledger P1 04 02I 00 OOI P1-04-02-00.00 04 - Requisition Accounting �ystem provides the ability for requisitions to be entered without posting a SF eProcurement, Purchasing, Only if the specific object pre -encumbrance based on predefined criteria (such as procuring for General Ledger codes are excluded from the inventory) while controlling that other requisitions always create a pre- budget definitions configured encumbrance such as 1'�ocurina for budgeted expenses). by the City. Pt 04I 031 001 001PI-04-03-00-001 04 - Requisition Accounting (System . vi s the abefity for purchase requisition to allow the entry of SF eProcurement. Purchasing multiple atop �Jtt ggda for allocation of expenditure. P11 04I 04I 00 001 P1-04-04.00-00I 04 - Requisition Accounting (System provi as Eha ability to allocate expenditures by percent of total I SF Procurement, Purchasing j�urchase m%r�isitlon. 1 I P1 041 O51 00 001 P1-04-05-OMO1 04 - Requisiton Accounting System orovldes the abiliy to allocate expenditures by dollar amount. I SF I eProwrement. Purchasinq I Pt 04I O6I 001 001 P1-04-06-00-00I 04 - Requisition Accounting Estero provides the ability to allocate expenditures by purchase requisition I SF I :Procurement, Purchasing line item. P1 04I 07I OOI 00 Pl-04-07-OMOI 04 - Requisition Accounting provides the ability to define auto -distribution rules and apply to the SF Procurement, Purchasing JSystem requisition using standard, user -damned distribution code (e.g., apply a I predefined split for grant and matching finds using a standard code). P11 04I 011 Olt 00 1-04-08-00-00 04 - Requisition Accounting System provides the ability to automatically close a requisition line when all SF eProcurement, Purchasing commoditles/servlces are received and the final Invoice is paid and/or when I the PO is closed. P1 04 091 00 00 1-04-09-00-00 04 - Requisition Accounting System provide the ability to optionally liquidate remaining/outstanding pre- SF eProcurement, Purchasing encumbrances when creating a purchase order from a requisition for less than the full amount renn{{�rested, P1 04 10I OOI 00 Pt-04-10-00-001 04 - Requisition Accounting System provides the abiry to setup standard auto -close parameters for SF eProcurement, Purchasing requisitions, based on dollar amount remaining an0 last activity. P1 04 11I 00 00 P1-04-11-00-0OI 04 - Requisition Accounting (System prov)des the ability to carryover open purchase requisitions to the SF I eProwrement, Purchasing followiru�fiscal year. 1 P1 04I 12I OOI 001 P1-04.12-00-00 04 - Requisition Accounting (System allows users to navigate from the requisition to its associated I SF eProcurement, Purchasing ` ` qurchase orders rpAardless of the status of the reouisition. P1 04I 131 001 001 Pt-04-13-00-00 04 - Requisition Accounting System provides the ability to adjust or cancel a requisition and generate I SF eProcurement Purchasing, aaDo((opdriate a�Aun�ino j�ea. General Ledger P1I 04 14 00 00 P1-04-14-00-00 04 -Requisition Accounting System provitles the wily to reopen a requisition if the requisition was SF eProcurement Purchasing closedi�e wa sop r� naP sewn N Ira a VL eLll `�i�l II li' iilifi,l�Il . III IV! I IIIIVeI ",1 ,1111 dill l' P1 OS 01 00 00 P1-05-01-00-00 05-Solicitations System provides the ability to row" sonroaedurea'. solicitation transactions through rough Me folio wln sta s: P11 05I Oil 01I 001 P1-05-01-01.00I O5 - Solicitations Gea ion o solicitation and addendums from an approved purchase SF Strategic Sourcing requisition (although some acllatations may be created without I I reaulsitions) P1 OS 01 I 021 001 P1-05-01-02-001 OS -Solicitations Postingq of a solicitation on the Cis Websita. I MI I Strategic Sourcing I MEDIUM P11 051 01 I 031 001 Pi-05-01-03-001 05 - Solicitations Notificaion sent to registered vendors via the followino methods: I I I P11 051 01l 031 011 PI.05.01-03-011 05 - Solicitations 1 Fax I SF Slral�Ic Sourcing _ P11 OSI Otl 03I 02 P1 05-01-03-021 05-Solicitations Mail I SF St ra( is Sourcino Ptl OS Ot 03 03 P1-OS-01-03-031 05-Solicitations E-mall I I SF Stra(eglc Sourcinq P1I 05 01I 04 00 P1-05-01.04-00I 05 - Solicitations Receipt of vendor responses electronically (with receipt time and date) I SF Strategic Sourcing I P1 05 01 O51 00 P1-05-01-05-00 05 - Solicitations I Tabulation of Jicit jion responses I SF Strategic Sourcino _ I Pt 05 Ot 06 00 Pt-05-01-06-00 OS •Solicitations Award notification v�a: _ 1 P1 05 01 O6 Ot P1-05-01 -06-01 OS -Sol csatna E-mall SF Strategic Sourcing I Pt 05 01 O6� 021 1-05 01 06-02 05 - Solickations Web Site Postlna MI I SVatA�Qic Sourcing I MEDIUM I P11 051 011 O61 031 P1-05-01-06.03 05-Solicitations I Fax SF I Strategic Sourcinq I I P1 OS 01 06 041 P1-05-01-06-04 05 - Solicitations Mail SF Strategic Sourcing P1I i OSI 02I 00 OOI P1-05-02-00-0OI 05 - Solickat System provides the ability to cross-reference requisitions, solicitations, and I SF eProwrement, Purchasing, award documents (entire document as well as line Items). Strategic Sourcing I I P11 051 031 00 001 P1-05-03-00-001 05 - Solicitations ISg�%y'Stem orovldes the ability to amend or cancel solicitations. SF I Strategic Sourcinq P11 05I 04I OOI 001 Pl-05-04-00-0OI 05 - Solicitations s the ability to support the following types of solicitations I(buttnot provid mited P11 05I 04 01 00 P1.OS-04-01-00 j 05 - Solicitations I Official sealed%ids/RFPs formal process sent via hard -copy or SF Strategic Sourcing I electronically P1 OS 04 02 00 1-05.04-02-00 05 - Solicitations Simplified Bids/Proposals - Informal (phone and fax) quotes received in SF Strategic Sourcing ylp�the oIn he 1Jdent t�red I I Pi 05 04 03 00 P1-05-04-03-001 05 - Solicitations I Simo il`tied B�dslPro owls - �niormal Quotes r����a//iveQp etecrrLyiicatly SF Strata is Sourcing I P11 05I O5I 001 001 P1-05-05-00-00I 05 - Solicitations (System provides the ability to create a new solid�(alion Gansacfion by I SF I SVateg c Sourcing coovina from a orevious solicitation transactions (all or dart). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 345 of 418 II I Pt 01 18 00 00 P1-01-18-00.00 01 - Requisitions / Requests System provides the ability to enable pre -determined users to override SF eProcurement, Purchasing defined sourcing rules with appropriate system -enforced authorizations. P1 01 19 00 00 Pl-01-19-00-00 01 - Requisitions / Requests System provides the ability for cross-referencing of purchase requisitions to SF eProcurement, Purchasing, the corresponding invitation for bid, purchase order, contract receiving Strategic Sourcing. Payables report. order number. invoice and Davment. P1 02 01 01 00 P1-02-01-01-00 02-Header Elements Requisition Number SF eProcurement/Purchasing P7 02 01 02 00 P1-02-01-02-00 02 - Header Elements Requisition Type (Direct Open Market, Inventoryl SF eProcurement. Purchasing P1 02 01 03 00 P1.02-01-03-00 02 - Header Elements gequlsition dale SF eProcuremenPurchasin P1 6-401 04 00 P1-02-01-04-00 02 - Header Elements Requester (Creating requisition) SF eProcurement Purchasing P7 02 01 0$ 00 P1-02-01-05.00 02 - Header Elements Requester phone number MI eProcurement, Purchasing LOW Requestor Phone number is not provided on the Requisition Header however it can easily be retrieved for queries or reports from the Requester table. I P1 02 01 06 00 Pt-02-01-06-00 02 - Header Elements Default suggested yendpr numbs (s) (ogtionat) rSuggestetl SF eProcurement Purchasing P7 02 01 07 00 P1-02-01-07-00 02 - Header Elements Default Suggested venrJ0 name Vendor info. passed to SF eProcurement Purchasing Line Items) I P7 02 01 08 00 P7-02-01-08-00 02 - Header Elements Default Suggested vendw FEIN number SF I eProcurement, Purchasing I Pt 02 01 09 00 P1-02-01-09.00 02 - Header Elements Default Su "led vend- address SF I eProcurement` Purchasing I P1 02 01 10 00 P1-02-01-10-00 02 - Header Elements Vendor CoriTact Name SF eProcurement Purchasing j P1 02 01 11 00 Pt-02-01-11-00 02 - Header Elements Vendor Contact phone number (multiple) SF eProcurement, Purchasing I Pt 02 01 12 00 P7-02-01-12-00 02 - Header Elements Vendor Contactemailaddrre�ss SF J eProcurement Purchasnq Header s act Ve 1 eProcuremen(. Purchasing P1 02 01 14 00 Pt-02-01-14.00 02 - F �p4 Elemerijp lemenis Need by Date or al andEndEnd of service date SF eProwrement`Pu chasing P11 02 01 15 00 P1-02-01-15.00 02 -Hess as er Priorjjy Code Jemergegcy or normal handling) SF SF eProcurement Purchasing P7 02 01 16 00 P1-02-01-1"0 02-Header Elements Jus ication/Comments eProcurement. P1 02 01 17 00 P1-02-01-17-00 02 - Header Elements Comment fields (multiple) with indicator designating internal or external SF eProcurement, Purchasing comments (i.e., internal - only seen by department personnel; external - carried forward and printed on PO to be seen by Vendor) Pt 02 01 18 00 P7-02-01-18-00 02 - Header Elements - Total r puis1lion cost SF eProcurement Purchasing P1 02 01 19 00 P1-02-01-19-00 02 - Header Elements Depar an SF eProcurementt Purchasing 1 Pt 02 01 20 00 P1-02-01-20-00 02 - Header Elements Fiscal Year SF eProcurement, Purchasing I P 02 Ot 21 0.Pt-02-01-2100 02 -Header Elements Default Account Distribution ( ional SF eProcuremer Purchasin P1 03 01 00' 001 P1-03-01-00-00 03 - Commodity Lines System provides the ability for commodity line dams to contain (including but not limited to) the following data elements: Pt 03 01 01 00 P1-03-01-01-00 03- Commo ' Lines ruential Line item number SF eProcurement. Purchasing I Pt 03 01 02 00 P1-03-01-02-00 02 - Header Elements 8uver ( it net) SF eProcurement. Purchasing I Pt 03 01 03 00 Pt-03-01-0300 02-Header Elements Buyer K?rc ne number (optional) MI eProcurement\ Purchasing LOW I P1 03 01 04 00 Pt-03-01-04-00 03-Commod' Lines Ouarl(I�y SF eProcurement. Purchasing I P1 03 01 05 00 Pt-03-01-0500 03-Commo Lines Unit of measure SF I eProwrement Purchasing I Pt 03 01 06 00 P1-03-01-06-00 03 - Comm Lines CommodiNinumber SF I eProcurement, Purchasing Pt 03 01 07 00 Pt-03-01-07-00 03 - C�m Lines $hart dpsc,(tp��on SF eProwrement, Purchasing Pi 03 01 OB O6 Pt-03-01-08-00 03- mine I Lines [o es p n SF eProwrement. Purchasing P1 03 07 09 M P7-03-01-09-00 03 - m t Lines Gus om description - used to provide additional information beyond SF eProcurement, Purchasing what is available in the commodity code table P1 03 01 10 00 P11-03-01-1000 03- Commoclj{y Lines $peB IInstructions SF eProcurement\ Purchasing P1 03 01 12 00 Pt-0301-12-00 n is 03-Commod/ Lines Ehs6 agfW unit coost'pllow z�rp qpd j�e live dollar values) SIF SF eProcurement Purchasing eProcurement`Purchasin P1 03 01 13 00 P1-03-01-1300 03 -Commo Lines Estimated total line i ern cost (etrlenrle SF eProcurement/ Purchasjipq P1 03 01 14 00 Pt-03-01-14-00 03 - Commo Lines Coding Block Elements for the Financia Data Classification Structure SF eProwrement, Purchasing L(nul user P1 03 01 15 00 P1-03-01-15-00 03 - Commodi Lines End ({+3er needg good or service) SF eProcurement, Purchasing P1 03 01 16 00 Pf-03-01-16-00 03 - Commodi Lines End user phone number SF eProcurement`` Purchasing Pt 03 01 17 00 P7-03-01-17-00 03-Comm ) Lines Deliveerr� address SF eProcurement.Purchasinq Pt 03 01 18 00 P1-03-01-18-00 03 - Commodi Lines ReQpeslad delivery date SF eProcurement, Purchasing P1 03 01 19 00 P7-03-01-19-00 03-Commo t Linea Freig9ht SF Procurement. Purchasing Pt 03 01 20 00 P7-03-01.20-00 03-Comm Lines Dellvery contact name SF eProcurement Purchasing P1 03 01 2f 00 P1-03-01-21-00 03 - Com L)nes Comments SF eProwrement`Nrchasinq P1 03 01 14 00 P1-03-01-22-00 03 - Commodi��y Lines Recycled goods indicator MI eProcurement, Purchasing LOW There is a recyclable datafield on the item setup, but this does not show within the requisition. Pt 03 01 21 66 P1-03.Ot-23-00 03 - cammoQ��((vv Lines Recycled go y j?e(C�ntage MI eProwrement Purchasnq LOW P1 i 03 01 24 00 P1-03-01-24-00 03-Corn icy Lines Emergency uussi)$cettons SF eProcurement.urchasmg Comments and justifications can be entered on the requisition. Pf 03 01 25 60 P1-0301-25-00 03 - Commodity Lines Sole source / proprietary justification SF eProcurement, Purchasing Comments and justifications can be entered on the requisition. P1 03 01 26 00 Pi-03-01-26-00 03-Commodity Limes Inventory Indicator SF eProcurement, Purchasing, Inventory City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 344 of 418 I ,r P1 00 27 00 00 P1-00.27-00-00 00 - General Requirements System provides ability to accommodate centralized and decentralized purchasing functions within a department and track procurements ac-ordingly. P1 00 28 00 00 P1-00-28-00.00 00 - General Requirements System provides the ability to automatically assign a sequential number, with or without a user -defined prefix and/or suffix, to each type of procurement transaction. P1 00 29 00 00 Pt-00-29-00.00 00 - General Requirements System provides the ability to maintain and report a detailed history of all ou'Wasir�q fivitv In_c_ludino, but not limit ed to: I P1 00 29 01 00 Pt-00-29-01-00 00- General Reauirements RRepyrsl'on Pt 00 29 02 00 Pt-00-29-02-00 00 - General Requirements so CM P11 00 291 03 00 P1-00-29-03-00 00 - General Requirements Response I P1I 00 291 04I 00 P1-00-29.04-00 00 - Ganeraa Recuirements Purchase Order I P7 00 29 05 00 Pt-00-29-05-00 - Generel ReauiremehisPo Chance Notice I P11 00 291 06 80 00 P1-00-2"6-00 a - General Reouirements Notes Screens I I P11 00 291 07 00 Pl-00-29-07-00 00 - General Requirements Contracts P11 00 291 081 001 1-00-29-08-00 00 - General Requirements I Receiver Information P11 001 291 091 001 P1.00-29-09-001 00 - General Requirements I Vendor P1 00 29 101 00 PI.00-29-10-00 00 - General Requirements Commodity P1 00 29 111 00 Pt-00-29-11-00 00 - Generel Requirements Procurement Method (RFQ. RFP. etc.) Pt 001 29 121 001 P1.00-29-12-00 00 - General Requirements I Procurement Status P11 001 291 131 001 P1 -00-29-13-00100 - General Requirements I Department P1 I 00 291 141 001 Pt-00-29-14-001 00 - General Reouirements I Anv Element of the Financial Data Classification Structure P1I 00 30 001 00I Pt-OOJO-00-00 00 - General Requirements System provides the ability to default vendor data from the vendor master file based on vendor number when a vendor is selected for any purchasing documents in a transaction. Pt l 001 31 001 00I Pt-00-31-00-00 00 - General Requirements System permits certain vendor defaulted fields to be overwritten based on P1I 001 321 00 `administrator -defined settinas. 001 P1-00.32-00-001 00 - General Requirements System supports self-service vendor registration and data maintenance P1 001 331 00I functi naIVJyy. 001 P1-00-33-00-0OI 00 - General Requirements affows selection of Pcard as a Method of Payment and will (System coordinate this payment method with the subsequent interface from the Peard vendor. tlklfili�i P1 01 01 00 - 00 P1-01-01-00.00 01 - Reouistiions / Requests Sys rxov Qes tpe �bi,l for d�ait is 10 define "yestors. P1I fill 021 00 OOI P1-01-02-00-0OI 01 - Requiskions /Requests System provides the ahihty to inlf(ate a purchase requisition for goods and as ice onl`npp A a Web browser. �ha P11 01 l 031 001 DOI P1-01-03-00-001 01 - Requisitions / Requests System pmvidea ability to query on the status of requisitions for goods or §99Jvlces arils off-line via a Web browser. Pt I 01 l 041 001 001 P"l-04-00-00 Ot - Requisitions ! Requests l ystem provides or the assignment of a unique purchase requisition 1 ppum��9ar 0xgyph system��enerated means. Pt 01 05 00 00 P1-01 -05-00-00 Ot - Requisitions / Requests System provdes the abffity ro support selection of a commodity through a I variety of means, including key words on commodity title, item descriptions or C. dino coTm iry numbers. P11 01 06 00 00 P1-01-06.0O-001 01 - Reouisitions / Requests Svsfem reoulres ,�a,_evpjv Ir'eculsj{'�pn line contain a wm�nodiN cods. P1I 01 07 00 00 P1-01-07-00-0OI 01 - Requisitions / Requests System provides (he abffity to Creole a requisition by copying an exfsting (including canceled) requisition, editing and saving with a new regulation number. The existing requisition can be from a dMerent department. IPt l 01 08 00 00 P1-01-08-00-00 fill - Requisitions / Requests System provides the ability to establish requisition templates for frequently 1 requested items. P1I Ot 09 00 00 Pt-01-09-00-00 01 - Requisitions / Requests ystem provides the ability to automatically generate a requisition to renew a contract based on a user -specified number of days before the contract I expires. P1 01I 10 00 00 P1-01-10-00-00 01 - Requisitions / Requests provides the ability for electronic notifications to be sent to the I (System respective purchasing agent Informing himther that line requisition has been (qleneraled and is endin his/her action. Pt 011 11 001 00 P1-01-11-00-00 01 - Requisitions / Requests System provides ttltl abffity for a requestor to cancel a requisition or individual re(�uisition line items orior to final aroroval. Pt l Ot l 12 00 001 PI-01-12-00.001 01 - Requisitions / Requests ISysta. provides the ability to cancel requisitions subsequent to final l aoofovat. P1 01 13 00 00�1.01-13.00.00 01 - Requisitions I Requests System provides the ability for viewing online or generating a `hard -copy' of the purchase requisition at any time to a local printer or a networked printer. Pt 01 14 00 00 1-01-14-00-00 01 - Requisitions / Requests System provides the ability for the automatic assignment of requisitions to buyers based on user -defined criteria (e.g., commodity, department etc.) and captures routina date and time. Pi I fill 151 001 00 P1-01-15-00-0OI 01 - Requisitions / Requests System provides the ability to manually assign/reassign requisitions to buvr..m. Pt l 01 16 00 00 P1-01.16-00.00 01 - Requisitions / Requests System provides the ability to assign more than one purchasing agent to a ursition fat line item level). Pt 01 17 00 00 P1-01-17-00.00 01 - Requisitions / Requests Yam provides the ability to maintain a schedule that can cause an electronic notification to be sent to a purchasing agents supervisor if the purchasing activity is not within the processing time assigned to the requisition. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 343 of 418 SF eProcurement, Purchasing MI eProcurement, Purchasing LOW Adding prefixes and suffixes requires logic to be added to the application. SF eProcurement. Purchasing SF Purchasing, Strategic Sourcing SF Purchasing, Strategic Sourcing SF Purchasina SF Purchasing SF Purchasina SF Purchasina SF I Purchasinq SF I - Purchasing, Pavables SF Purchasina SF Purchasina SF Purchasina SF Purchasinq SF I Purchasina I SF Purchasing SF 1 Purchasing SF I Purchasing, Strategic Sourcing l SF Purchasing SF eProcurement, Purchasina SF eProcurement, Purchasing i SF 1 eProcurement, Purchasing 1 SF 1 eProcurement, Purchasing l SF eProcurement, Purchasing SF eProcurement, Purchasinq SF eProcurement, Purchasing SF eProcurement, Purchasing MI eProcurement, Purchasing MEDIUM MI eProcurement, Purchasing MEDIUM SF SF SF SF SF SF RQ eProcurement, Purchasing eProcurement, Purchasing eProcurement, Purchasing eProcurement, Purchasing eProcurement, Purchasing eProcurement, Purchasing eProcurement, Purchasing System sends notification but requisitions are not automatically created. System sends notification but requisitions are not automatically created. I MEDIUM (This came be accomplished using custom workflow or with a custom report or query. I P1 00 05 04 00 P1-00-05-04-00 00- General Requirements Department SF eProcurement I P1 00 05 05 00 P1-00-05-05-00 00 - General Requirements Combination of dollar t�({1� commodity etc. SF eProcurement P1 00 09 06 00 Pt-00-05-06-00 00 - General Requirements Fund or other element of the Financial data Gassifirztion Structure SF eProcurement, Purchasing P1 00 06 00 00 Pt-00-06-00-00 00 - General Requirements System provides the ability to approve or reject all types of purchasing SF eProcurement activities in full or partially, and to return refection line items to the end user with ability to/uire a tree form reason for resection. P1 00 07 00 00 Pt-00-07-00-00 00 - General Requirements System provides the ability for a user to set an automatic renewal flag for MI Purchasing LOW [[ecu%%TT��nq pun ass o/dpt$ an releases for contracts P1 00 08 00 00 P1-00-08-00.00 00 - General Requirements $ystsm produces a (isf of con recta or releases that are eligible for renewal MI Purchasing LOW Pt 00 09 00 00 P11-00-09-00-00 00 - General Requirements System allows users to select contracts or releases for renewal and creates MI Purchasing MEDIUM the subsequent document P1 00 10 00 00 P7-o0.10-00.00 00 - General Requirements System provides the ability to prompt for automatic renewal requisitions for MI Purchasing MEDIUM blanket orders based on percent or dollar values consumed. P7 00 11 06 00 Pt-00-11-00-00 00 - General Requirements System provides the ability to copy one or multiple fines of field values to MA eProcurement, Purchasing HIGH This functionality is not the next1subsequent line(s) and change one or more field value elements currently available and will when using input screens for all purchasing documents need to be created using PeopleTools. P1 00 12 00 00 Pt-00-12-00-00 00 - General Requirements System provides the ability to create a new purchasing document (e.g.,. SF eProcurement, Purchasing requisition, PO, ate.) from a previously created purchasing document P1 00 13 00 00 Pl-00-13-00-00 00 - General Requirements System provides the ability to establish repetitive transactions and SF eProcurement, Purchasing, transaction templates (e.g., requisitions, solicitations, purchase orders, etc.) Strategic Sourcing P1 00 14 00 00 P1-00-14-00-00 00 - General Requirements System provides the ability to save and flag (or hold) incomplete and/or SF eProcurement. Purchasing complete purchasing documents so that It can prevent the flagged document from being Inadvertently released for approval at any stage (e.g.. solicitation, award, tabulation, contract, order, receipt, invoice, etc). P1 00 19 00 00 P1-00-15-00-00 00 - General Requirements System provides the ability to support punch out to a vendor catalog with a SF eProcurement round inback to the Purchasing document. P1 00 16 00 00 P1-00-16-00-00 00 - General Requirements System provides the ability to capture and report user defined performance RQ eProcurement. Purchasing MEDIUM data on measures and indicators of Buver activities Pt 00 17 00 00 P1-00-17-00-00 00 - General Requirements System provides the ability for the Buyer to view a worklist, including the MI Purchasing MEDIUM The system does provide a details of a procurement and the estimated required processing time, or worklist of activities to be any similar pro -defined performance metric performed, but there are no required processing time built into the notifications. P1 00 18 00 00 Pt-00-18-00-00 00 - General Requirements System provides the ability to show contract and spend data for the buyer's RQ Purchasing MEDIUM cis Yye:on;Z. P1 00 19 00 00 P1-00-19-00.00 00 - General Requirements its therability to link to 3rd party data sources for Industry SF Strategic Sourcing Strategic Sourcing has the market analysis capabilities to access 3ro party services such as DB.B or Credit Services to obtain external data for vendors. Pt 00 20 00 00 Pt-00-20-00-00 00 - General Requirements System provides the ability for logic to create multiple purchase orders by SF eProcurement, Purchasing vendor when multiple 0o argz:TcIPJ&d with a requisition - PI 00 21 00 00 Pi-00-21-00-00 00 - General Requirements b l' System provides the a r'Ity or au orized users to set up the business rules SF eProcurement for each procurement method using user defined parameters, such as restricting approvals by dollar value of purchase or limlting buyers to a particular commodity ty e. Pt 00 22 00 00 Pt-00-22-00-00 00 - General Requirements System provides the ability to utilize the Citys existing commodity code SF Purchasing structure (NIGP). P1 00 23 00 00 P1-00-23-00-00 00 - General Requirements System supports periodic updates of commodity codes based on externally MI Purchasing MEDIUM There is not a delivered provided files. integration for this however it can be developed using the delivered toolset. P1 00 24 00 06 Pt-00-24-00-00 00 - General Requirements System provides the ability to attach and retrieve multiple files, regardless of file type, to ell purchasing documents and carry forward files to supngpouenI Purchasinq documents: I P1 06 24 01 00 P1-00-24-01-00 00 - Gene al Requirements Scanned mapes SF eProcurement, Purchasing I Pt 00 24 02 00 P14)0.24-02-00 00 - General Raqulmmenis PDF files SF eProcurement Purchasinq I P1 00 24 03 00 P1-00-24-03-00 00 - General eauirements Word orocessina documents SF eProcurement, Purchasinq I P1 00 24 04 00 Pt-00-244)4-00 00 - General Regiirements $Qfeadsheets SF eProcurement, Purchasi�tg P1 00 24 09 00 Pt-00-24-05-00 00 - General Requirements CAD SF eProcurement Purchasing P1 00 25 00 00 P1-00.25-00.00 00 - General Requirements System provides the ability to prevent redundant data entry by providing fui( SF eProcurement,�urchasing, The suite of purchasing -related integration between all application components. Transaction creation, Strategic Sourcing products are all replacement, update or deletion of any common date element occurs only complementary and fully once, and Is r>3Med forward and reflected through all related tables (e.g., integrated. data entered on requisition is carried forward to the solicitation, PO, etc). P1 00 26 00 00 P1-00-26-00-00 00 - General Requirements System provides the ability to treat each City department as a separate SF eProcurement, Purchasing, entity (e.g., restrict departments from posting to other departments and Strategic Sourcing viewing data, eta without authorization) but also provides City-wide, consolidated querying/reporting from a data mposltory. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 342 of 418 1 1 S I INotes: Sort Sort Sort Sort Reqt Num Category Requirement Text Degree of Fit Response Module 1 2 3 4 Pt 00 01 00 00 P7-00-01-00.00 00 - General Requirements System provides the ability to support the following methods of procurement: P1 00 01 01 00 P1-0-01-01-00 00 - General Requirements Official sealed bids (Invitation to Bid (ITB) for commodities and SF Strategic Sourcing services) P1 0 0102 00 P1-0-01-02-0 00 - General Requirements Department -delegated procurements SF eProwrement. Purchasing, Strdteaic Sourcing P11 00 01I 03 00 P1-0-01-03.00 00 - General Requirements Emergency procurements SF I eProcurement, Purchasing, Strateai" r4lna P11 00 +I 01 04 00 P1-00-01-04-00 00 - General Requirements Proprietary or sole source procurements SF I eProcurement, urchasing, strat gc Sourcina Pt 001 011 05 00 P1-0-01-05-00 00 -General Reouirements Informal yq�geGWe bids SF I Strq Is Sourcina P1 001 Ot I OB 00 Pt•0-01-06.00 0 - General Requirements Recuesfs for Pmoosals (RFP SIF I jjr lealFc,Sourcina Pi 01 O11 07 00 P1-0-01-07-00 00 - General Requirements Reauests for Information (RFI SF I lra ealc Sourcina Pt l 00 01I 081 001 Pt-0-01-08-00 00 - General Requirements Request for Qualifications (K b) SF Purchasing, Strategic Sourcing P1 00 01 09 00 Pt-00-01.09-00 00 - General Requirements I Inter -governmental procurements SF eProcurement, Purchasing, Strategc Sourcina I Pt l OO 01 I 1 m 001 P1-00-01-10-00 00 - General Reauireents I MultIKe award procurements SF Strategic Sourcina I I P1 I 0 011 11011 001 P7-0 Ot-11-00� 00 •General Requirements 1 Special purchases (Handicapped, Co rectons, etc.) 1 SF I eProcurement, Purchasing, 1 Stratec`ic Sourcina 1 P11 00 01 121 OOI P1-0-Ot-12-001 00 - General Requirements I Multi -step (e.g., evaluate technical offers and select those qualified to SF Strategic Sourcing I t bid) I I P11 I P11 0 00 01 01 13 141 001b1-00-01-13.001 00 - General Requirements I P1-0-Ot-14.001 I State coprra jj feJ��nts 1v I SF Purchasing 1 I I 00 001 00 -General R�epquirements 00 - General utrements ISysBem Coo Israpirva o6terp(Offe contract orocuremems I ues SF SF Purchasing Purchasing I P11 0 02 001 001 P1-00-02-00-001 0 - General Requirements . aaabI t to create and maintain information relating to: I I i I Pt 00 021 011 00 Pt-00-02-01-001 00 -General Requirements R p}�Isitiona I SF I eProcurement Purchasing I P,1 00 021 021 001 1.00-02-02-001 0 - General uirements I Solicitations I SF I Stratec c Sourcina I P1 0 021 02I 01 i P1-0-02-02-01 00 - General eauirements I Sotiajj�% p(fparat�Pn I SF 1 Strdregc Sourcina P1 0 02I 02I 02I P7-00-02-02-02I 00 - General equirements Vendor bid Ilst creaibn and maintenance (Including subset of SF Strakegrc Sourcing qualified Small and Minority-owned/Other Targeted businesses I subcontractoml oil0 021 021 03 P7.0-02-02-03 00 -General Requirements �Et eecclIro p (patine ��d distribution (electronically by system) I SF Strata c Sourcina I I P1 00 021 021 1 jr-04 00 - General Reauirementa Electronic bid reca�ot SF Strate(Vc Sourcina I P11 0 021 021 O51 7 �� 2-0S 0 - General Requirements I Response tabulation (fad by elegy lonl`receiot or manually) I SF I Strategic Sourcina I I P1 001 021 021 061 P1-00-02-02-061 00 - General Requirements I Award ratification (So Coov or }lard DO I SF I Strategic Sourcina 1 01 02I 03I P7-0-02-03-0OI 00 • General Requirements PO / Conequiact IPt Pi 00 02 03 01 P1-0-02-03-01 I 00 -General Requirements 011 I Requisition to solicitation to PO/Contract I SF eProcurement, Purchasing, I Strategic Sourcina P71 00 021 03 021 Pt-0-02-03-021 00 - General Requirements I Revvpplsition a contract or PO SF eProwrement, Purchasing P11 00 021 03 031 Pi-0-02-03-031 00 - General Requirements Sof(citation to contract or PO (no requisition -optional; subject to SF Strategic Sourcing, Purchasing P11 �rooger authorizations) Pt 01 001 021 021 03 031 041 P1-0-02-03-041 051 P1-0-02-03-05 00 - General Requirements 00 -General Requirements PO to contract (r ,��p89sq aoair�` contraO PO or Contract witflout rC utsrtion or solicitation) SF SF I Purchasing I Purchasing P1 001 02 03 O61 P1-00-02-03-06 00 - �9nera Reauireme��is Auto aene2t PO from S�eSourced Contracts SF Purchasing P1 001 02I 04I 001 P7-00-02-04-00 00 -General Requaementa Goods receipt, shipment notification, returns, quarantines, and SF Purchasing 1 f)iiDlnent calrly/Ilations general j�S, )Ice rece SF Pavables P11 01 031 00 00 P7-00-03-00-00 00-neraequlremenfs System pro ides tithe ability to support different methods of payment approval which can be set up by purchase, by purchase type or by department. It should be possible to restrict administration of purchase type choi a to authorfj�p�ersonnel. Methods Include: I P1 I P1 I 0 001 03 03 01 02 031 00 Pt-00-03-01-001 00 - General Reauirements 0ON-00 -02-001 00 - General Requrements I Pt-0 Two wav mallchinq of Durcp.se ord/3r art invoice. Two wav matehino of gProt se orrlar and re „ vma report I SF SF Purchasing, Payables I I Purchasina, Pavables I IPi l 001 03� 001 -03-001 O0 • General Requirements 1 Three way matching of purchase order, receiving report and invoice. I SF Purchasing, Payables 1 1 P11 001 03 041 001 P1-0-03 04-00 00 - General Requirements I Four way matching of purchase order, receiving report, quality report SF Purchasing, Payables I I11 and Invoice. 1 P1I OI 041 001 00 P1-0-04-00-00 00 -General Requirements provides the ability for approvals for all types of purchasing 1 1I1 ISystem activities: I P1 i1 00 041 01l 00 P1-0-04-01-00 00- General Requirements Rgpuisitions I _ SF I eProcurement, Purchasing P1l 001 041 02 001 1-00-04-02-001 00 - General Reauirements I Solicitations I _ SF- I Strateaic Sourcina P11 01 04 03 0. 1-0-04-03-001 00 - General Requirements 1 Purchase Orders SF eProcurement. Purchasina P11 001 04 04 0-0-04-04-001 00- General Requirements Contracts SF eProcurement. Purchasina P11 001 04I 05 001 P1-00-04.05-001 00 - General Requirements I Receipts SF eProcurement, Purohasinq Pt I 001 041 061 001 P1-0-04.06-00I 00 - General Requirements I Invoices SF Pavables I P11 01 051 001 001 P1-0-05-00-001 00 - General Reaulrements ISvstemprovides the ability for approvals to be determined bv: I 1 P1 00 051 01 001 Pt-00-05-01-001 00 - General R��,qauiremehis Dolllar Threshold SF eProcurement, Purchasina P1 I 001 051 021 001 P1-0-05-02-001 00 - General Reauirements I Commoditv SF eProcurement I I P11 001 051 031 001 P7-00-05.03.01 00 - General Requirements I Procurement TVDe I SF I eProcurement I City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 341 of 418 I i F ]omplexityof Comments Modification F8 09 01 05 00 F8-09.01-05-00 09 - Credits I Note a tong text F8 09 01 06 00 FS-09-0140(5-00 09 - Credits 111 Payment Terms F8 09 01 07 00 F8-09417-07-00 09 - Credit$ Payment Methods F8 09 01 08 00 FS-08.01-08-00 09 - Credits I Payment Date F8 09 01 09 00 F8.0 14)9-00 09 - Credits Bank Account into (for ACH Payments) FB 09 02 00 00 FB-09-02-0O00 09 - Credits System provides the ability to capture the following on each c r tamer credit or adl�ustment: I F8 09 021 Ot (� FB{p-n2-01-00 09 • Credits Header IFB 09 02I 01� �{ Fg,IKjjl'1-01-01 09 Credits I Customer Number I F8 09 02 Ot 02 FB-O"2-0102 09 - Credit I Customer Address /selected from bin -to addresses on Customer record) I F8 09 02 01 03 F8-09.02-01-03 09 - Credits I Internal IJLvoice Ra%ranks I FB 09 02 01 04 FS-09.02-0t-04 09 - Credits I Pavrtreni Terms I F8I 09� 02 01 05 F8-09-02-01-05 09 - Credit I P eT.t Method (for refunds) IFB 09 021 011 06 FO-09-02-01-06 09 Credits l RRamiii To Address I FS 09 021 of l 07 F8.0"2-01-07 09 - Credits I Status (Feen. Paid. in Disoule. etc.) I F8 09 021 01l 08 F8-09.02-01-08 09 • Credits I External Co(.ument Reference (such as contract number) IF8 OB 021 Oil 09 F8-0&02-01-09 09 Credits Header Tex( F8 O8� 02I 01) 10 F8.O9-02.01-10 09 - credits Amount Receivable control account (defaults from customer record, can be weriden with alternate from customer record) I F8 091 02 02 00 F8.09-02-02-00 09 - Credits Line Items I F8 09I 02 02 Ot FB-09-02-02.O1 09 - Credits Una Number I F8 09 -1 021 02 F8-09-02-02-02 09 •Credit$ Invoice Line Item Reference I Fe 09 021 02 03 FS-09-02-02-03 09 - Credits {�,y�nj�1y I F8 09 021 02I 04 F8.09-02-02-04 09 - Credits I UrtO of Measure - I F8 09 021 021 05 F8-09-02-02-05 09 - Credits "am Number F8 09I 021 02 06 FB-09.02-02A6 09 -Credits Item De�riotion F8 091 021 02 07 FB-09-02-0Z-07 09 - Cratf Unit F8I 091 021 02 OB-Q�q-02-02-OB 09 -Creel is I Line Artaunt (QuanBty' Price) F81 09 22 02 09 FB-d9.22-02_. 09 - Credits I Comment Text F81 09 02 021 10 FB-09.02-02.10 09 - CedBs I Pike Discounts I F61 09 02 02 11 F8-0"2-02.11 09 - Credit I MultiQlp amountino distributions F11 09 03 00 00 F8-09.03-00.00 OB -Credits System defaults relevant header information from invoice when entering a customer credit memo F8 09 04 00 00 F84144.00-00 09 - Cedts System defaults relevant item information from invoice when entering a customer credit mama. yyy FB 10 01 1 00 00 FB•10-014)"O 10 - Manage NSF . ,.., System provides the ability to record dishonored revenue payments (i.e., NSF) by Checks name, account number, v isit number, date and amount pi FS 10 02 00 00 F8-10-02-00-0010 -Manage NSF System provides the abil record the initial receipt of an NSF Check in a manner Checks that reduces cash in bank and established a receivable (wing a different mnbol q�vnt the{wrtjy?I cl`,rClo receivabirysl. F8I 10 03 00 00 FB-CO-03-0. 10 -Manage NSF System prow s (he at"to Query customer receipts to identify the original receipt Checks transaction. I F8I 10 04 00 00 F8-10-04-00-00 to_Manage NSF (System provides a standard oommunica0oNleher to notify the cuss mer of the NSF Checks status. F8I 10 05 00 00 FB-10-05.00-00 10 - Manage NSF Checks System provides users the ability to restrict incoming payments from a customer to a re-(fa11 ryf(Wer or (yogic due to NSF check status te.a.. no checks). F8I 10 O6 00 00 FB-10-08.00-00 10 - Ma rage NSF System provides a n Hon to users that a customer has an NSF check outstanding Check. when oroae.aing receipts. FBI 10 07 00 00 F8.10-07-00-00 10 - Manage NSF Check Svstem resrict a cus(omen to a soechc oq r'avment F8I 10 08 00 00 F8-10-OB-00-00 10 • Menage NSF System allows users io perform one of f owing actions when settling w NSF Checks check: FB 10 OB 01 00 F8-10-08.01.00 10 -Manage NSF F8 10 08 02 00 F8-1U-0802-00 Checks 10 - Menage NSF (record r11 bl`ra�r7.1,1 f�! thr NSF Check 11 rdino rry�a7li a rev�plte for penaPoes) Reverse original appkcauon of paymenk an� reestablish the ongmai customer Checks receivabip I FB 10 08 03 00 F8-10A8-03-00 10 - Manage NSF Reverse the original application M payment and reverse the original customer Checks receivable FS 10 08 04 00 F8-10.08-04-00 10 - Menage NSF Checks Write off the amount to bad debt exoense. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 340 of 418 NA I Billing and Receivables does not currently support one-time Customers az defined by the City. NA Billing and Receivables does not currently sup port one-time -at-- as defined by the City. NA Billing and Receivables does not curenny support one -Doe customer as defined by the City. NA Biting and Receivables does not —fly support one-time wstarnere az "feed by the City. NA I Billing and Receivables does not wnently support one -erne customerses defined by the City. SF I Betina. Receivables SF Bill'' Receivables SF I B'I col' n Receivables SF I Brllino .-tvables SF Billin4,Receivables SF I BillinaReceivables SF 1 Bilfg�yRece'vades SF Billina�Receivables SF I Billin. Receivables SF I B'llyho Recerv.I SF I Bi8{ng,, emivables SF B'llino`Receivables SF Billino.Receivables SF I Billirgg, Receivables SF I Bik,e�,., Receivables SF B'll'ne Receivables SF I 81ll`�9 'em'vables SF Bilfy�e. Receivables SF I BillinY�Receivables SF I Billin��Receivables SF Biuyrc.Receivables SF B'll: Receivables SF BillipA Receivables SF Billing, Receivables SF ."'rig. Receivables MI Receivables LOW Receivables SF Receivables SF Receivables RQ MEDIUM Receivables I This funckonalmy is mot Currently a iiiibie 0M MI need to be created usxg MA MEDIUM P... IeToas. Receivables MI MEDIUM Receivables That functionality is not c 41Y araBaWe .,id rrin read 10 be created using MA MEDIUM Pe wTods. Receivables SF Receivables SF Receivables SF i Receivables SF I I � ► � � E r r � c � 1 r � � 1 � � 1 F8 08 05 03 00 F8-08-05-03-00 08 - Manage Customer Record receipt of cash and any collection fees associated with the collection, at any SF Receivables Accounts time against the original receivable and maintain proper accounting entries to reverse the bad debt a to raf�rd thN co lcci fee. �✓; 08 OS 04 00 FS-0e-05-04-00 08 - Manage Customer Obtain proper approva�on a fransacton tO wri(eog account balance if not SF Receivables Accounts ..., based on user -defined criteria such as receivable type and dollar amount. I F8 08 OA 05 00 FB-O""5-00 08 - Manage Customer System has the ability to support 4 levels of dunning notices. MI I Receivables MEDIUM Accounts IF8 08 05 OB 00 FS-08-0546-00 08 - Manage Customer System supports different dunning timing schedules, by department. MI I Receivables MEDIUM Accounts F8 08 04 00 6d Fa-08-06-D0g0 08. Manage Customer System provides the ablity to generate either a positive or negative adjustment which SF Receivables Accounts can eigrer be applied or not applied to a specific customer invoice, with proper controls end audit trail. Fe 08 07 00 00 F6-08-07-00-00 08 - Manage Customer system Provides the ability for customer accounts to be maintained either on an 'open SF Receivables Receivables operates in an Accounts item or'bi lance forward' basis m determined by a department. open item basis; however, I customer statements can IIII be produced in both bases. F8 08 08 00 00 F8-08.08400-00 08 - Manage Customer System provides ability to record a protested or unidentified payment as an unapplied SF Receivables Accounts receivable item (Lis. maintains clearing accounts) that can later be applied to receivable belances. F8 09 09 00 00 F8-08-09-DO-00 08 - Manage Customer System provides the ability to Beg accounts with a user -defined follow-up date for SF Receivables Accounts collection related activ'pY. F8 08 10 66 00 F8-08-10.00.00 08 - Manage Customer System provides the ability to include or exclude disputed bllingslcustomers from. Accortnts IF8 OB 10 Ot 00 FO-08-10-01-00 08 Manage Customer aging SF Receivables Accounts Fe OB 10 02 00 F8-0&10-02-00 08, Manage Customer finance charges SF I Receivables Accounts Fe 08 10 03 00 F8408.10-0340 O8-Manage Customer invoice generatioNpnnting SF I Receivables Accounts 08 10 04 00 FS-08.1044-00 O8-Manage Customer atakaeca SF I Receivables IFill Accounts F8 08 10 os 00 FB-OB-10-05-00 IM - Manage Cust mar dunning SF Receivables Aunts F8 08 11 00 00 FB-08-11-0000 08 - Manage Customer System provides the ability to calculate various types of interest/payment schedules, I Accounts including but not limited to: — F8 08 11 01 00 F8-08-11-01-00 08 - Manage Customer Interest -free periods MA Receivables MEDIUM This fur.-alq is not Accotaits I curr<ritly nd avaaw. awill need W be croatad veep i Pep�(eTods. FB 08 11 02 00 Ft1-08.11-02-00 OB - Manage Customer Installment payments MA Receivables MEDIUM Th;slunclionaley is not Accounts I I —,fly avaliaCle and wul need b W ueafod -inji PeoN Touts. FB 08 11 03 00 FS-Wit-03-00 08-Manage Customer Interest deferrals or suspensions of interest payments MA Receivables MEDIUM Tn-lunuionality is col Accents —ritly—il.bla and will need to be ce7 usvg ileTnels F8 OB 12 00 Manage y pro ny op y generate an automatic refund transaction on a 00 FB-08.12-0000 08 - Man a Cuataner System provides the ability to optionally MA Receivables MEDIUM 1'hw Iundio ..", is net Aunts s refund date to issue a a nt to the aatomer. peafied p Y� cerenay avadabe end w4I i need io M created vang PeooleTools F8 08 13 00 00 FII-M13.00.00 08 - Manage Customer System provides the ability to optionally generate a refund of revenue to a mil -Invoiced MI Receivables MEDIUM Accounts cuaarner(e.g.. grant overoavmen�8,1 with ptppgf ppfovala. I I I F8 08 14 00 00 F8-08-14-00-00 OB - Manage Customer System allows cues or commun(calbns Ia be Bed b: Accounts F8 08 14 Os 00 FB-08-14-01.00 1)8 - Manage Custontar Specific transactions (invoices or credit memos) SF Receivables Accounts F8 08 14 02 00 FO.OBe -14-02-00 08- Manage CuCutor General customer records SF Receivables Accountss III Fe 08 15 00 00 FB-08-15.00-00 08 - Manage Customer System provides the ability to attach files to customer communication records SF Receive bes Arcants �Ilrhllli6 JJlYII C� dhliil dlllll IIIII�II„licit !i IIIIIIIIbIIIiIIIiIIIIIi�VI�ir�li��181iiliIIIIII1111iiP�llilllllilll�lllilIli'llita�illli F8 09 01 00 00 FS-09.01-00-00 00 - Credits shall capture the Ibffowitlg Information for brre-tirrei otntomem when entering a credit: D9 01 01 00 F8-09-01-01.00 09-Credits Name NA I Billing and Receivables does not currently support IF8 one-time customers as defined by the City. F8 09 01 02 00 FB-0941-02-00 09 - credits Address information NA and Receivables does not currently support I IBilling 0 one -me customers as defined by the City. FB 09 Ot 03 00 FB-09-01-03-00 09 - Credits Tax -ID NA and Receivables does not currently support I (Billing One-time customers as defined by the City. F8 09 01 04 00 FB-09-014)4-00 O9 - Credits Phone number NA and Receivables does not currently support I I IBillirig one-time customers as defined by the City. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 339 of 418 4 I w F8 06 07 07 00 FS-06-07-07-00 06 - Cash Receipts - Drivers License (encrypted) NA Billing and Receivables Unbdled does not currently euppon one-time customers as defined by the City. F8 06 07 08 00 FB-06-07-08-00 OB - Cash Radii - payment Amount NA Billing and Receivables UMiped does not currently support one-time customers as defined by the City. F8 06 07 09 00 FS-06-07-09-00 06 - Cash Receipts - Place of cdlection NA Billing and Receivables Unbltled does not currently support one-time customers as defined by the City. F8 06 07 10 04 F8-06-07-10-00 06 - Cash Receipts - Payment Type/MethodlCredit card type NA Billing and Recevables Unbilied does not currently support one-time customers as defined by the City. F8 06 07 11 00 FS-06-07-11-00 06 - Cash Receipts - Accounting posting dale NA Billing and Receivables Unbitled does not currently support one-time customers as defined by the City. F8 OC 07 12 00 F8-06-07-12-00 06 - Cash Receipts - Externally assigned control number (check receipt) NA Billing and Receivables Unbilled does not cumently support one-time -.I-- as defined by the City. F8 06 07 13 00 FB-06-07-13-00 06 - Cash Receipts - User -Defined Field 1 NA Billing and Receivables UnbiBetl does not currently support one-time customers as defined by the City. F8 06 07 14 00 F8-06-07-14-00 OB - Cash Receipts - Usai,Dafined Field 2 NA Billing and Receivables Unbilled does not currently support pne-time -.I-- as defined by the City. F8 07 03 00 00 F8-07-03-00-00 07 - Deposit System provides the ability for daily cash drawer close-out, including, but not limited to, the followmo functional'' : F8I 07 03 01 00 F8-07-03_01-00 07 - DePoait Produce a done-ou( report to be balanced with the cash, checks, money orders, etc. SF Receivables in the operators drawer at the end of a cashiers scheduled work day or at any pant 1he work day. F8 07 03 02 00 F8-07-03-02-00 07 - Deposit 1rg users to enter counted monies by tender and the system automatically SF Receivables calculates any overage or shortage amount by tender. The calculation includes any cash drawer bank amount. Fe 07 03 03 00 F8-07-03.03 GO 07 - Deposit Create a recelpl within the system, crediting the appropriate accounting codes for SF Receivables the revenue or expense abatement. The receipt reflects any overage or shortage calculated. F8 d 03 04 00 FS-0743-04-00 07 - Deposit Print is deposit summary for each days sakes, which includes total receipts for all SF Receivables sh d q�(iypad v location. I FBl 07 03 04 00 Fit-07-03-05-00 07 - Oaao%tnersld frem rggpds by un rylty�,ng acgpuq,Iing tlislribu6ona.. RC Receivables F8I 07 04 00 00 F8-07-04-00A0 07 - Depoai1 Record apre-punted deposit alp number to support subsequent automated bank MI Receivables reconciliations for de sit aclivitl Iir 4VVVV VV I�VIV IIPIIIVV I! s' lOP 03 - Manage Customer System provides the ability to monitor llection dates and generate workflow SF Receivables FF1.1 08 ions thresholds.Wol� on uusse�e�6me 00 DO FB-0e-02-00-00 - MaA"counage Customer lh�tion tbas stem attachments(e.g..scanned ( g., SF Receivables F8 08 03 00 nts 00 F8.08-03-00.00 08 -Manage Customer documents) with u rp System provides I�ie ability fo nscoin customers open receivables as in dispute with a SF Receivables I Accounts held dedicated to the reason and details of the dispute. F8 09 04 00 00 F8-08-04-00-00 08-Manage Customer ,1ppu0on System provides the ability to merge two different customer records and maintain their MA Receivables A—ta associated history (e.g., able to review activity for both old cuslo"m under the current customer account. IFS 08 09 00 00 FS-08-06-00.00 08 - Manage Customer System provides the ability to process uncollectide accounts as follows: A —to Fit 08 66 01 00 FB-08-0"1-00 08 - Manage Customer Generate dunning letter to customer, which is customizable by the department SF Receivables Accounts 1�={704i 9 Isublevel. F8 08 OS 02 00 FS-0B-OS-02-00 OB - Manage Customer F.xporl data b legal representatives or third -parry collection departments and record SF Receivables A —to as bad debt, with option to retain memo entries of the receivable balance in 0te accounts receivable system. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 338 of 418 MEDIUM LOW Receivables does not System provides the punctuation support this ability; ability to merge two however, the City can relate different customer astomem together in a sudrecords and maintain customer relationship, their associated history (e.g., ails to review eckviry for bath old customers under the current customer account. k I I i i a # 1 F8 05 20 00 00 FB-0S20-00-00 05 - Cash Receipts - System provides a bath process to automatically match receipts to payments. SF I Receivables Billed F8 OS 21 00 00 F8.0S-21-00-00 05 - Cash Receipts - System Is able to recognize revenue and reduce the pre -payment when goods or SF Receivables Billed 9�^(Ices vaned. F8 05 22 00 00 F8-0S22-00-00 05 - Cash Recepts - System (a able fO match customer opan invoices to prepayments in an on-line SF Receivables Billed transaction. F8 05 23 00 OQ F8-05-234I0-00 05 - Cash Receipts - System Is able to match customer open invoices to pre -payments In a batch process. SF I Receivables Bored I F8 05 24 00 00 FB-0S24.00-00 05 - Cash Receipts - System allows users to reverse the application of a payment to an item and re- SF I Receivables Billed a rattan of the oan(rnent to a different hem. F8 OS 71 00 00 178.0S-25-00-00 05 • Cash Receipts - I Sys em allows users to reverse the application of a payment to an item and reverse the I SF Receivables Billed vment. F8 05 26 00 00 F8-05-28-00-00 OS -Cah Recepts - System provides the ability to associate attachments (e.g., Word, Excel, or scanned I MI Receivables HIGH Billed documents with customer , ,,.., .. F8 OB 01 00 00 FS-0e-011-00-00 06 - Cash Receipts - Systam provides the ability to record cash receipts for unb4led revenue. SF Receivables UnbiNed I F8 08 02 OOI DO F8-06A2-00-00 I 06 - Cash Receipts - ISystem provides the ability to code a receipt as a refund of expenditure, trust account SF Receivables UnbiNed d sit. revenue transaction, etc. F8 06 03 00 00 F8-0e-0300.00 06 - Cash Recepts - ISydem provides the ability to maintain default Chan of Account distributions for speck SF Receivables Unblled jjjvvv of oav nt$/� ry '.¢jr�Is. F8 D6 04 00� 00 FB-06-04-00-M O6 - Cash Receipts • rS ern provdes the abi1%(o automatically print a receipt for hems unbilled and allow SF Receivables through the cash Unbil for cashier to reprint the receipt manually, if necessary. IAvailable drawer capabilities in Receivables. F8+ 06 05 OOI 00 FB-OS-OS-00-00 I 06 •Csh Receipts - System captures the following information for unbilled cash receipts. UMraetl F8 OB 061 011 00 FB-06-05-01-00 D6 - Cash Reoepis • Customer Account SF I Receivables Unbllled F8I D6 051 021 00 FB4)6-05-02-00 OB • Csh Receipts - I Date received SF I Receivables UnbiNed I FB O6 OS 031 00 FB-06-05-0300 OB • Cash Receipts - Name/User 10 of person collecting monies SF I Receivables Unbified F8 OB 05 04 00 F8-06-OSO4-00 06 -Cash Rsrbpls • Unique, sequential receipt document number SF Receivables Unbilled F8 06 05I 05 00 FB•06-0505-00 06 - Cash Receipts • I hwoi- Rate-- fields SF Receivables Unbilied I F8I OB 051 06 00 F8-06-O5.08-00 08 - Cmh Receipts - I Customer Payment Identificationk Number (e.g., the number) SF Receivables UnbiNed 1A. F8 06 06 07 00 FB-08-05-07-00 OB - Cash Receipts - Drivels License (encrypted) MI Receivable. HIGH delivered, drivers Unbiltad license number is not F8 DB 051 08 00 F8-06-05-08-00 1 06 - Cash R—ii - I Payment Amount SF Receivables Unbmee FBI 06 05 09I 00 FB-0e-OS-0B-0O I OB -Cash ReceIP - I Place of cdiection SF I Receivables UnbiNed FBI OBI 051 101 00 FB-0SOS10-00 I OB - Cash Receipts - I Payment TypelMelhod/Creda card type SF Receivables Uroeled I I F8 06 061 11I 00 F8.06-0S71-OOI Cash Receipts- Accounting posting date SF I Receivables uroinad F8 O6 05 1 12 00 F8-06-OS12.00 06 - Csh Receipts • Externally assigned control number (check recept) I SF I Receivables (Deposit Number, Receipt I UnbiNed Number F8 06 051 13 00 F8-O6.OS13.00 OB-Csh Receipts- Uaar-Defined Field MI Receivables LOW Unbiiled I I I FS 061 051 14 00 F8-06.0114-00 O6-Cash Recaipta- Usar-Defined Field2 MI Receivables LOW Unb Ned FB 061 06 00 00 FB-06-06-00.00 06 - Cash Receipts - System ai an unbilbtl cash receipt to be reversed. SF Receivables I UnbiNed F8 061 07 00 00 FB-06-07-00-00 06 - Cash Receipts - System shell capture the foRov g Information for'ona-lime' customers when entering a Unbilled p"Zn`: F8 OB 07 01 00 F8-06-07-01-00 06 -Cash Recepta - uelomer Account NA ing and Receivables Unbiled does not currently support �Ilili one-time customers as defined by the City. F8 0] 0] 02 00 FB-06-07-02-00 08-Cash Receipts e ipts- Data received NA Billing nd ailled does rtently.ulppon I one-time -a'" rs as refined by the City. F8 06I 0] 03 00 FB-06-07-03-00 08 - Cash Receipts - Name/User ID of person collecting monies NA �Illing and Receivables UnbiNed does not currently support I One -rime -at-- as darned by the City. F8 0] 0] 04 00 FS-06-07-04.00 06 - Cash Receipts- Unique, sequential receipt document number NA and Receivables Unbilled does not currently support I IIlllllnl one -fine customers as IIII defined M the City. F8 06 0] 05 00 FB-06-07-05-00 06 • Cash Receipts - Invoice Reference fields NA end Receivables Unbtlled does not currently support I IIIIIPng one-time watomers as defined by the City. F6 06 07 O6 00 F1•01-07.OS00 06 - Cash Receipts - Customer Payment Iden0cation Number (e.g., check number) NA Silting and Receivables Unbilied does not currently support ( I one-time oustorners as defined by the City. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 337 of 418 I I l Fe 05 03 00 00 F8-05-03-00-00 05 - Cash Receipts - System provides the ability to capture cash receipts and apply them to outstanding SF Billed �usj0men u)vryce s). FS 05 04 00 00 FB-OS-04-00-00 OS - Gsn Receipts - uyslem provides ability to proceea multiple and/or partial invoice payments on the SF Billed aeons racegt. 05 OS 00 00 F8-05A5-00-00 OS - Cash Receipts - SyWan provltles the ability tocouture the following information when processing e ire Billed receipt for biped Items: FS 05 05 01 00 F8-05 05.07-00 05 • Cash Receipts - Customer Account SF Billed F8 05 05 02 00 FB-05-0SA2-00 05 - Cash Receipts - Date received SF Broad I F8 09 05 03 00 F8-05-05-03-00 05 - Cash Receipts - Name/User ID of person collecting monies SF Billed F8 05 05 04 00 FS-05-05-04-00 05 -Gah Receipts - Unique, sequen8al receipt document number 5F Biped Fe 05 05 05 00 FB-05-0S05-00 05 - Cash Receipts - Invoice Reference Tplds SF Fe 05 05 06 00 F8-05-06-000 & 81ped 05 - CashReceipts - Customer Payment Identification Number (e.g.. check number) SF Biped FB 05 05 07 00 F"li-05.07-00 05 - Cash Receipts - Drivers License (encrypted) MI Boned F8 05 05 08 00 F111-05-05.OB-00 05 - Cash Receipts - Payment Amount SF Bit ed FS 04 05 09 00 FS-05-05.09-00 g5 - Cash Receipts • Place of collection SF I Biped FS OS 05 10 00 FS-05-0&10-00 05 - Gsh Receipts - Payment Type/MeModlCredp card type SF I Billed F8 05 09 11 00 F8-05-0S11-00 05 - Cash Receipts - Accounting posting date SF Billed F8 69 05 11 00 FS-05-05-12-00 05 - Cash Receipts - Externally assigned control number (check recap() SF Biped F8 05 d,S 13 00 F84)5-0&13-00 05 - Cash Receipts - User•Defined Field 1 MI Billed F8 05 05 14 00 178-05-05.14-00 05 - Cash Receipts - User -Defined Field 2 MI BiXF8 05 06 00 00 F8.05-06-00-00 05. CashReceipts - System provides the ability to supply an outbound Interface for receipts k1 order to MI Billed update multiple specialized third -party tiling systems whose furw11oriality, cam" be 05 07 00 00 F8-05-07-00-00 05 - Cash Recepts - imp)pn�nted in an ERP billji irr am. Syyasliam provides the ability to support bar code or scan line printing on envelopes and RO IF8 Billed LerrQWrq+rgrJvKp to aid ir(remittl�nc�)rrpcessipd. F8 05 08 00 00 FS-06-O&00-00 05 •Gsh Receipts - $yslem shg)j albw peymen4 received to be matchad to an Invoice for a ono -time NA Billed customer. 178 05 04 00 00 F84e5-09400-00 05 - Cash Receipts - System provides the ability to uukze a predefined Interface for bar code or scan line TP Billed infomletlon which can cephrre carry forward invoice information to the payment receipt. `Fie 05 10 00 00 FB-05-10OD-00 05 - Cash Receipts - System provides the ability to record pre -payments for goods or services (such as SF Billrrd for ppgrk facilities) FS 05 11 00 00 F8-05-11-0000 05 -Gsh Receipts - yy provides the ability for on4ine review receipts before they are posted to the SF Biped qqean tat ladsip� andror matched to W tourer �1Q9� liert I Fe 05 12 00 00 F8-05-12.00-00 05 - Cash Receipts - Sys Pre 4dee the ability to cea rece pi ak any kkne before i1 is posted *in SF aillad Ar4pa rauth��yip. 05 13 00 00 FB-0543-00-00 05 - Cash Receipts • System govides me ability to enter, back separately, and process simultaneously the IFS Biped fo lq= I' a no situations /but not limped to): F8 OS 13 01 00 F8-05-13-01-00 g5 • Cash Race ipts - Lesfr, rig capture of Bank Code SF Biped F8 66 13 02 00 FS-05-13-02.00 05 - Cash Receipts - Check, including capture of ABA number MI I Billed F8 OS 13 03 00 FB-05-13.03-00 05 -Cash Receipts - Check, including capture of Account number MI Biped F� 65 13 04 00 F"5-13-04-00 05 - Cash Receipts - Check, including capture of Check number SF Billed F8 05 13 05 00 F8-05-13-05.00 05 • Cash Receipts - Cmdit/Debl Card via authorization code SF Billed F8 05 13 06 00 FS-W13.06-00 05 - Cash Receipts - Money Orders, including capture of Bank Code MI I Billed I IF8 05 13 07 00 F8-05-13-07-00 05-Cash Receipts- EFTIACH SF Billed I F8 05 14 00 00 FS-05-14-0000 05 - Cash Receipts - System provides Me ability to record receipts into a clearing account and subsequently SF F8 05 1S 00 DO F8-05-15-0000 Billed 05 - Cash Recapia - &V that rrrly)iot gpeirU1 an invoice- System provides Ore a 8y to apply payments on receivables by referencing the invoice SF Billed qurrtber. which In" a�`lJJvo�re irI(ormaar to ritWjpt. F8 OS 16 00 00 F8-OS•18-0000 OS -Gah Receipts - �e S'ys(em pmyidp a iiity fo capture and alp rece r(s via standard open interface F8 05 16 01 00 FB-05-16-01-00 Billed 06 - Cash Receipts - to No "ac: is Nnds tmnsfem (EFT) or ACM Inbound Payments provided elactonicalty SF Billed ty(dfa tonic FS 05 16 61 00 F8-WI6-02-00 05 . Cash Receipts - led Lodr Box SF Billed F8 09 16 03 00 FS-05-16-03-00 05-Cash Receipts - Credit Card Payments SF Billed F8 05 17 00 00 F8415-17-0000 05 - Cash Recepts - System provides the ability for a central Revenue division to pmomin receipts on behalf SF Billed of herM Fe 0S 18 00 00 FS-05-18.00-00 05 - Cash Receipts - System provides the ability to inquire into all of a customers outstanding invoiceslfess SF Billed y�tmhgqn receivrrgp�y z? hlf and tvoq of invdcaRee. F8 05 19 00 00 FB-05-19-00-00 05 - Cash Receipts - Systam provldes I"e abilk/ {o automaiidaily pant a receipt for payments on account and SF Billed Blow for cashier to reprint the receipt manually, 4 necessary. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 336 of 418 Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables HIGH As delivered, drivers license number is not encrypted I I Deposit Number. Receipt Number LOW LOW HIGH May require additional Integration eftwt. Billing and Receivables does not support one -lima customers. I I I HIGH HIGH HIGH I Available through the rash drawer capabilities in Receivables. 1 4 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 F8 04 18 05 00 F8-04-18-05.00 04- Enter Customer Note or long text NA Billing and Receivables Invoice does not support one-time customers. F8 D4 18 06 00 F8-00-18-06-00 04 - Enter Customer Account number NA Billing and Receivables Invoice does not support one-time Fill 04 18 07 06 F8-04-18.07-00 04-Enter Customer Occupancy 10(sell-address) NA customers. Billing and Receivables nvo Iice does not auppon one-ume customers. F8 04 18 08 00 F8-04-18-08-00 04-Enter Customer Imdce number NA Billing and Receivables Invoke does not support one-time customers. F8I 041 19 001 00 FS-04 1900-00 O4 Enter Customer Invoice System provides Me ability to capture the following on each customer Imvoice: F8 O4 191 01 00 F8-D4.19-01-00 Oil -Enter Customer Invoke Header SF Billing IF8I 041 191 01I 01 FS-04-19-01-01 I 04 - Ente I Customer Number I SF I Billing oCuustomer FBI 14Inim 191 01) 02 F8.04-19-01-02 04-Enter Customer I Customer Address(selected hero hlli•lo addresses on Customer record) I SF I Billing I F8I 04 19 Ot 03 F8-04-19.01-03 Invoice 04 - EnterCustumer I Payment Terms I SF Billing Invoice I FBI 04 19I 01 04 FB-04-19-01-04I O4-En ter Customer Dunning Terms ( SF Billing nvo ce I FBI 04 19I 01 05 FB-04-1"1-05 I 04 - Enter Cuauener Invoice Status (Open. Paid, In Dispute, etc.) I SF Billing FBI 041 191 Oil 061 F8-04-19 01-06I 04 - Enter Customer External Document Reference (such as contract number) I SF Billing I Invoke FB 041 19 01 07 F8.04-19-01-07 O4-Enter Customer I Header Text SF Billing Invoke FB 041 19 01 08 f8-W-19-01-08 04 - Enter Customer I Account Receivable control amount (defaults from customer record, can be MI Billing MEDIUM Invoke overriden vAth altemate from customer record) F8I 041 191 Oil 09I F8.04-19-01-09I 04-Enter Customer I Service address (not filling address) I SF Billing I Invoice F8 04I 191 021 00 FB-04.19-02-00 m I 04 -Enter Custoer I Llne Items SF I Billing nvdCe 8 041 191 02 01 FB-04-19-02-01I 04-Enter Customer I Line Number SF I Billing Invoice IF8 041 19I 02 02I F8-04-19-02-02I O4-EnUr Customer Quantity I SF I Billing Imcce I FS D4I 19 02 03 F8-04.1"2-03 04 - Enter Customer Unit of Messure I SF I Billing IFB 041 191 021 041 F8.04.19-02-04 Invoice I 04 - Enter Customer Item Number SF I Billing I Invoice I FB al 19I 02 06�8-04-19-02-05 I 04 -Eller Costumer I-- I It.. Description SF Billing I FS 04 19 02 06I 8-04-1902.06 I 04 - Enter Customer I Unit Prim SF Biking Invoice F8I 041 191 021 071 FB-04-19-02-07 I 04 - Enter Customer Invoice I Extended Line Amount (Qusnfity • Pdce) I SF I Billing FB 0641 19I 02I 08I F8-04-19-02-08 04 - Enter Customer Comment Text I SF I Blllmg F8 04 19 02 09 FS-014 9-02-09 I Invoice 04-EnUr Customer Price Discounts SF Billing Invoke I F8I 041 191 02 101 FB-04-19-02-10 16, - Enter Customer Multiple eccou,In, distributions I SF Billing B 04 20I 00 OOI FB-0 O-00-00 Invoice 04 - Enter Customer System e9ows financial data claealfiragon amounts to be determined based on a uaar- IF I Invoke defined allocation (e.g.. 10% to the General Fund and 90% to the Grams Fund). I F8 041 201 001 01I F8-04.20-00-01 I 04 - Enter tourer I Individually I SF I Billing oCu Invice I FBI 141 20I 00 021 1`8-14.20.00-02 I 04 - Enter Customer By customer or range of customers I MI Billing MEDIUM Invoice I F8I 041 201 00 03I FB-0420-00-03I 04 - Enter Customer By invoice or document number a range of numbers I MI Billing MEDIUM Invoice I F8I 04 20 OOI 04 FBfi4.20-00-04 O4-Enter Customer By any element of the financial date classfication structure MI Billing MEDIUM Invoice I I I I FBI 04 21 00 1 00 FB-04.21-00-00 04 - Enter Customer System provides a standard printed invoke that is cuatomizabla to include: Invoke FBI 04 21 Oil 00 FO-04-21-01-00 04-EnUr Customer Invoice I department specific contact information I SF I Billing FBI 041 27I 021 00 FB-04.21-02.00 O4 - Enter Customer Invoice Mader inform rtkn (Customer Information, Invoice Number, Invoice Date) SF Blllirg invoice F8 04 21 03 00 F8-04-21-03-00 04-Enter Customer standard Ut a -features, such as a bilmap or oilier image I SF Billing I Invoice I FBI 041 211 041 00 FS-04-21-04-00 04 - Enter Customer I mug6page logic (e.g., first page on letterhead, second includes graphic, but no SF I Billing Invoice addrola` FBI 04I 21 OS OOI F8-04-21-05-00 04 - Enter Customer I Ire item Information (Quanf try, Item, Prim, UoM, Extended Amount) SF I Billing I I nvolce FBI 04I 22 00 XI F8-04-22-00.00 04 - Enter Customer ISystam provides the ability to automatically calculate Interest and late fees on a I SF I Billing, Rece- es I Imawe mustomer account and big the customer for the interest and grinci al. F8I 04 23 00 00 F8.04-23-00.00 04 -Enter Customer System provitlss the ability to generate customer statements by department or I RQ Receivables Invoice o ni-tlonal sutl4evel e.. fund, subfurd, ..... ,:,. ... .... .. .. r ,_._.. FBI F8 05 07 00 00 F8-05.Ot-0D-00 OS - Cash Recepts - System provides the ability W import cretlitldedt card transaction files from a third parry. MI Receivables HIGH May req re additlonal Biped intermat m effort. F8I 051 021 OOI OOI F8-05.02-00-00 I 05 -Cash Receipts - ISyslem provides the ability to either apply an overpayment to a different invoice a to I SF I Receivables, Payables I I Billed create a refund transaction. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 335 of 418 1 1 1 Fe 03 12 13 00 F8-03-12-13-00 03 - Define Cuatomera Ds/au8 Payment Terms SF Billing, Receivables and Items F8 03 12 14 DO FB-03-12-14-00 03 - Define Customers Corresponding Vendor Number (for entities that are both vendors and customers of SF Biding, Receivables and Items the of F8 03 12 15 00 F8.)3-12-15-00 03 • Dan- Custmlars User tined Field 1 SF Billing, Receivables and Items FB 03 12 16 00 FB-03-12-16-00 03 - Deane Customers User Defined Field 2 SF Billing. Receivables and Items FB 03 12 17 00 F-0-12-17-00 03- Define Customers User Defined Field 3 SF Billing, Re w,11es and Items F8 03 13 00 00 F"3-13-00.00 03.Define Customers System provides a central .ecord of items add, including, but not limited to the and ttema folloann FB 03 13 Ot 00 F8-03.13-01.00 03 - Defi_ Crntomara Item Number SF eulml, Receivables and Items Fit 03 13 02 00 F8-03.13-02-00 03 - Define Customers Item Deauiptfon SF Billing. Receivables and items F8 03 13 03 00 F8-03-13-03-00 03. Define Customers Base Unit of Measure SF Billing, Receivables and hem' F8 03 13 04 00 F11-03-1344-00 03 - Define Customers Unit Price SF Billing, Receivables and Isms F8 03 13 OS 00 F843-13-0500 03 - Define Customers Default accounting information (i.e, revenue account) SF Billing, Receivables and uems ........ .... ... FB 04 0f 00 00 F8-04-01-00-00 04 - Enter Customer System provides the folkwing delivery options for customer imoips: Invoice F8 04 01 01 00 F84)4-01-01-00 04 - Enter Customer Print SF Billing Fe 04 of 02 00 FB-04-01-02-00 Invoice me 04 - Enter Customer Ema4 SF Billing Invoice F8 04 01 03 00 F8-04-0i-03-00 04 - Enter Customer Fax SF Billing Invoke F8 04 01 04 00 FB-04-01-04-00 04 - Enter Customer XML or EDI SF Billing Fit 04 02 00 00 FB-04-02-00-00 Invoice 04 - Enter Customer System provides the ability to upload customer invoices from Excel or other file formals. SF Billing FB 04 03 DO 00 Fe-04-03-00-00 Invoice 04 - Enter Customer System provides the ability to support revering billings to selected customers. These SF WIN Invoke recurring invokes can be set up to generate on a user defined schedule (quarterly on I the first aev. verv,7 v(eeW ev�rry rtr�nll`Pn llsth tc. F8 O4 04 00 00 FB-04-g4-0000 04 - Enter Cuabmer iy'tem provr'dea ebllify for a s1ngle 'mvorce neon {o be d bib�d across mWuae SF I Billing Invoice - nu a n / 7 F8 04 OS 00 00 FB-04AS00-00 04 - Enter Customer SysEam s ability for one department to b01 on behalf of other oily SF Billing Invoice department. on a conedidaled bill (e.g., both Fife and TPW coat reimbursements can I be included on a single invoice for Hazardous Matedal cleanup aai ties after a wreck). I F8 04 06 00 00 FB-04-06-004)0 04 - Enter Customer System provides the ability to add standard text comments to either an Individual SF I Billing Invoice jmr)i" o/ a rypu0 of invokes. F8 04 07 00 00 PS-04-07-00-00 04 - Enter Customer y eon provides the ability for users to define billing cycles and frequencies. SF I Billing I Invoice F8 04 08 00 00 FS-04-08-0000 04 - Enter Customer System provides the ability to ousbmize the prised irwdcsladjusbnsnb form to include RD Billing Invoke Y ek en d' my Shoe fs tern {�I a gseer nr 1 Fe 04 08 00 00 FB-04-09-00-00 04 - Enter Customer Sys pmv{des the ebi r users pre�ew, and re prr cualdnized SF Billing Invoice imdcesradjustmenh (including coor, font. type, size variations), including but not limited to: individually. V customer. ro7ge o(ylvoj� ;ualment numbers. F8 04 10 00 00 F&04-10-00-00 04 - Enter Customer System provides the abil'ay to copy and modify exs ng imdcea to create new invoices. SF Billing 1158 04 11 00 00 F8-04-1 1 -00-00 Invoice oa - Enter Customer 5Yetem provides the aollty, to creels Invoice templates. SF Billing [-of- F8 04 12 00 00 F6-04-12-0D-00 04 - Enter Customer System provides the ability to change account coding on invokes through a mess MA Billing MEDIUM Tart lunclionarny s -1 Invoice charge functionality, with audit ass and proper seounry. I currently availably and w01 need U DB create4 usaµl PeouleTods. F8 04 13 00 00 FS-04-1300-00 04 - Enter Customer System provides ere ability to generate an invoice document number based upon a SF Billing F8 04 14 0u 00 FB•04-14-00.00 Invoke 04-En rCustomer l gfa(gl 1rf) �urgpua srsjrergteQ y,InuenBal number. S vJ the eb (0 fag ! 1 pedal handgrg' (e_g., hand -delivery) MI Billing LOW Billing support entry of Invoice with the ability to solar comments (such as a time to deliver). comments, but the ability to flag for special handling will require a new field. F8 D4 15 00 00 F8.04-15-00-00 04 - Enter Customer System the stAilfi�ty, to associate attachments (e.g., Word, Excel, or scanned SF Billing Invoice egprovides won ns dkc'lr FB W 18 00 00 FB-04-1&0000 04. Ent., Customer To Ito gmc d I' aLwtl Sy eon au mvace s Ivory m from customer record to indiwdual invoices SF Billing I FB 0( 17 00 00 FB-O/-17-00-00 Invoice 04 - EMar Customer System allows ovemde o delivery method dunng and after invoke entry. SF Billing II Fe 04 18 00 RQ F8.04-18-MM Invoke 04 - Enter Customer System -all kapbre the tollm - information for'one-time' cuatomen when entering Invoke an invoice: F8 04 18 01 00 F8-01-18-01.OD 04-Enter Customer Name NA Billing and Receivables Invdse does not support one-time customers. Fe 04 18 02 00 F8-04-18-02-00 04 - Enter Customer Address inbrmateon NA Belling and Receivables Invoke does not support one-time customers. F8 D4 18 03 00 F8-O6.18-03-00 04 - Enter Customer Tair•10 NA �illing and Receivables Invoke does rat support one-time customers. F8 04 is 04 00 F8-04-18-04400 04 - Enter Customer Phone number NA Boiling and InvokeReceivables Invoe I does not support one-time customers. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 334 of 418 I I I s It 11 1 1 1 1 ( 1 1 11 1 # .401W # i 1 __ # F8 00 02 00 I 00 F8-00-02-00-00 00 - Rr ancigall 3yslem provdes Me4talll,5 w maintain an audit trail of all billing, accounts receivable, SF Billing, Receivables I FB 00 03 00 Control. and R. Dta DO FB-00-03-00-00 00 - Finanpai f�q 1. Cy= provide Re !%i ty for customer invoices, statements, and other customer RO Billing, Receivables `I I and Reporting communications to be charged to comply with ADA requirements (allowing for manges I'll 00 04 00 to font. la stc). 00 F8•00-04-00-00 00 - Financial Controls System pro ties the ability to simultaneously work in multiple fiscal years in the accouts SF Billing, Receivables and Reporting receivable module (i.e., have periods open in two or more final years at one time). l ,F8 00 05 00 00 FS-00-05-00-00 00 - Financial Controls System provides an automated process to convert credit AIR belances to a user- SF Billing, Receivables. General The City can use the and account e Reporting defined liability on a periodic basis (a.g., year,and close). I Ledger I delivered allocations functionality to meet this rq yiremem FBI 02 01 00 70 00 FB-02-01J)d00 02 - Integration with System the ability for full integration of Accounts Receivable and Receipts SF Billing, Receivables, General pprovides ther Modulas sub 1 Fit 02 02 00 00 FB-02-02-00-00 02o Integration with Tha s�ydem gsnerstas receive le ansachons in the General Ledger for at original I Ientrtes. SF I Billing, R—rrvda es, General other Modules atl�i41��l1�rneents f�9altles and Interest. I FBI 02 03 00 00 FB-02-03-00 00 02 - Inlag a fort w M System rs infeg sled v ilh Gren s Management to menage grantbiting SF Billing, Receivabes, I other Module Contracts Grants. 1.-1 F8I 02 04 00 00 FB-02-0400-00 02- Integretion with System ci integrated with Pmjed Management to manage billing for reimbursable SF Bill ing,)2ecelva6les, other Modules o�Y,9cb Contracts, Pr0ied Costinq Fit 02 OS 00 00 FB-02-05-00-00 02 - Integration with System Is integrated with other modules to support reimbursement for other work SF Billing, Receivables, I I Work Order managed other Modules efforts, such as ha tardous material clean-up efforts. Cordrads t Coss 1 i'�i�� Fe 03 01 00 00 FB-03-01-00-00 03-Define Customers S yefor, provides for •central file for storing all custvner-rebletl Information (e.g., SF B1IIii; B Iling, eceivables and )tams name. add—., contec). etc.). F8I 03I 02I OOI OOI FB-03-02-00-00 103 - Define Chis more �System provides the aNlity to create user -defined customer types. I SF Billing, Receivables I Ffl 03I 03I 001 00 Fit-03-03.OP00 and Items - Define Cuatomers System Imovidea the adlBy to toll, track and collect tor'one-tine' uletomers whose NA Bilfing and Receivables 103 and Items wsloner Informeton Is provided at the time that either bills or payments are reraiveq does not support one-time and not maintained in the central recor0 of custanera. customers. I FB 03I OsI OOI 00 Fit-03#00-00 103 - Define Customers System prov des the abut y to deaci vats and reactivate customers with apprap to SF &Ming, Receivables and Items Lle�sity a control. I F8I 03I 05I 00 001 F8.03-05-00-00 103 - Dafire Customers Bysiem ca nu a reason for deactivating a Customer MI Billing, Receivables I LOW I 1 and Items I I I FBI 03 OBI 00 00 FB-03-08 OP00 103 Dand efinalCustomers System provides the ability to prevent duplicate customer records. MI Billing, Receivables I HIGH Fe 03I 07I 00 001 F8-03-07-00-00 03--Deans Cusomere System provide the ability to record a customer as brooked from future services. f SF Billing, Receivables Customers can be end Items inactivated by function 1 (such as Bill To). 1 I FB 03 OBI 10 001 Fit-03-08-00-00 03 - Define Cwtomere System --- Ne ability to maintain an on-line Buda trail of changes made to the MI Bill rig, ReCeivaD es LOW and'. cuss er master. Fit 03 09I 00 OOI FB-0309-00-00 103 - Define Customers System maintains a history of changes to the customer record (old value, rev, value, MI Billing, Receivables LOW andItems user. date). F8I 03I 10 00 00 F8-03-10-00-00 03 - Define Customers ISystem provides the ability to copy a similar customer record when creating a new SF Billing, Receivables end Item. record. Fe 03 11 00 00 F8-03.11-00-00 03 - Define Customers System provides the ability for a unique customer number that is, at a minimum, 10 SF Billing, Receivables and Items characters in lenxim, FBI 03I 12 00 00 F8-03.12-00-00 03- Define Customers System provides a central record of customer information. including but not limited to I and Items the foltow)nn: Fill 03 121 0ij OOI FB-03.12-01-00 03-Define Customers I Customer Type SF Billing Race, bee I and Its.. FBI 03 12 02 00 F8-03-12-02-00 03 - Define Customere I Customer Name SF Billing, Remrvades I and Items I F8I 03 121 03I OOI F8-03-12-03-00 03 - Define Customers I Customer Address (multiple) I SF I Billing, Receivables I I and Items — IFB 03 121 04I OOI F8-03.12-04-00 103 - Deft l timers Customer Address Type (Bill{o, Ship -To, Soid-To, etc.) SF I Billing, Receivables I 1 A) IFit 03 121 05I OOI FB-03.12-05-00 i 03 - Defi Multiple contact names and numbers per customer (phone and fax). SF I Billing, Receivables I I and Ifomeomers Fit 03 12 OB 00 FB-0312-O". 03 - Deane Customers Cuato.ar ante" addres SF Billing, Receivables opd rams _ IF8I 03 12 07 DOI F8-03-12-07-00 03. Define Gustonnera TAD exount number MI I Billing, Receivables MEDIUM and Itema IFBI 03I 12 08 OOI FB-03-12-08-00 103 - Define Customers Tax -ID Number I SF I Billing. Receivables I and lams FB 03 12 09 00 FB-03-12-09-00 03 - Define Customers Default Account Receivable Control Account MI I Billing, Receivables MEDIUM and Items _ F8 03I 12 101 00 F8-03-12-10-00 03 - Define Customers Alui ats open -Bent managed balance sheet accounts (such ae Escrow) MA Billing, Receivables HIGH This funcb.—ly o rat and Rennie I I curwndy avaiiabie and wilt need im tie rated using PeouleT. ors. -_ FBI 03I 12I ill 001 FB-03-12-11-00I 03 - Define Customere Default Dunning Tema SF Billing, Receivabes and Items i i Fe 03 qJ 1 12 00 F8-03-12-12-00 03 - Define Customers Default Payment Methods SF Biting, Receivables and Items _ City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 333 of 418 F7 16 06 04 00 F7-16-06-04-00 16 - Grant Close- Open Procurement Encumbrances MI Grants, Project MEDIUM Out Costing F7 16 06 05 00 F7-16.06-0.5-00 16 - Grant Close- Revenues In excess of expenditures for MI Grants, Project _ MEDIUM Out a -rant Costm F7 16 06 06 00 F7-16-06 16 16 - Grant Close- Grant funded posit ons tied to the grant MI _ Grants, Pmject MEDIUM Out Costin F7 17 01 00 00 F7-17-01-00-00 17-Interfaces System provides the ability to support MI Grants, Project MEDIUM interfaces to Federal or State grant Costing systems so that required grant program and financial reports can be automatically —chanced. _ F7 17 01 01 00 F7-17-01-01-00 17-Interfaces IDIS MI Grants, Project MEDIUM Costin F7 17 01 02 00 F7-17-01-02-00 17-Interfaces DRGR MI Grants, Project MEDIUM Cost, F7 17 01 03 00 F7-17-01-03-00 17 - Interfaces Nortddge Loan Management System MI Grants, Project MEDIUM Costin F7 17 02 00 00 F7-17-02-00-00 17-Interfaces System provides the ability to Interface MI Grants,Project MEDIUM CFDA Information for Grantors from the Costing federally provided natalpn F7 17 03 00 00 F7-17-03-00-00 17 - Interfaces System interfaces grant awards to M&C MI I Grants, Project MEDIUM trackma system fEcounc0l Costin City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 332 of 418 1 1 i F7 13 03 00 00 F7-13-03-00-00 13 - Record System Provides the ability to calculate SF Grants, Project Grant In -Kind on a user -defined basis matching fund Costing and Match requirements associated with any grant and to provide system generated entries for the match. I F7 13 04 06 00 F7-13-04-00-00 13 - Record System provides the ability to define SF Grants. Project Grant In -Kind posting requirements for grant match and Costing and Match in -kind transactions that are unique to each Grant award. F7 13 OS 00 o6 F7-13-05-00-00 13 - Record System allows for in -kind revenue to be SF Grants, Project Grant Ind0nd defined as the off -set for In -kind Costing and MatcA a uses. FT 14 Ot 00 00 F7-14-01-00-00 14 - Processing System provides the ability to record Indirect Costs indirect costs assoclated with a grant / activity as either morn or actual entries, as: F7 14 Ot 01 00 F7-14-01-01-00 14 - Processing Fixed Dollar Amounts SF Grants, Project Indirect Costs Costing, General Le d(�er F7 14 01 02 00 F7-14-01-02-00 14 - Processing Standard Rates extended to actual SF Grants, Project Indirect Costs expenditures for pre -defined Costing, General categories of expense (e.g., 5 percent Ledger II Of salaries F7 14 01 03 00 F7-14-01-03-00 14 - Processing Standard ales extended to statistical SF Grants, Project Indirect Costs balances (e.g., 5 percent of head Costing, General count) Legr i F7 14 02 00 001k7-14-02.00-00 14 - Processing System automatically generates the SF Grants, Project Indirect Costs indirect costs entries for grants. Costing, General Ledger F7 14 03 00 00 F7-14-03-00-00 14 - Processing System allows for indirect revenue to be SF Grants, Project Indirect Costs defined as the off -set for indirect Costing, General expenses. Ledger F7 14 04 00 00 F7-14-04-00-00 14 - Processing System provides the ability to store SF Grants, Project Indirect Costs different indirect cost rates for different Costing, General departments along with the effective time Ledger sod for each ant! ac6vi JAt,�uur"6F715 0r0T- 00 F7-15-01-00-00 16 - Prepare system provides the ability to group city RO Grants, Project LOW Grantor Reports accounting structures into grantor Costing, General �R(�rise catefip.r199ii Levier F7 15 02I 00 00 F7.15-02.00-00 15 - Prepare System provxfes the ability to group city RO I Grants, Project LOW Grantor Reports program or organizational classifications Costing, General in to yyrantppJJ gglouPin�gs. LeclQPr _ F7 15 03L 0 00 F7-15-03-00-00 15 - Prepare ISysfam alfot4s grantor report groups to I SF I Grants, Project Grantor Reports be defined Independently of the city's Costing, General fiscal year. Le er p,�� - � N4 FT 16 01 00 00 F7-16-01-00-00 16 - Grant Close- System provides the ability to process SF Grants, Project Out expenditures and billing to a grant for a Costing. user -defined period beyond the grant end Contracts, data. Billing, Receivables F7 16 02 00 00 F7-16-02-00-00 16 - Grant Close- System provides allows users to change SF Grants, Project Out grant/activity status to alto. or prevent Costing specified types of transactions from posting (e.g., allow billing for a design phase, but prevent any further expppridkur��� or Comm it(�ants). F7 16 03 00 00 F7-16-03.00-00 16 - Grant Close- System nofff users with an error SF Grants, Project I Out (message 4 a transaction contains an Costing, General) inactive grant / activity number. Ledger F7 16 04 00 OOI F7-16-04-00-00 16 -Grant Close -I System provides the ability to close SF Grants, Project Out grants / activities independently of the Costing l or F7 18 05I 00 00 F7-16-05-00-00 16 -Grant Close- Sys em provides the ate for a ghe ability to support any SF Grants, Project F7I 16I 06I OOI OOI F7-16-06-00-00 �16 - Grant Close - out iSyst mdprovldes standard notifications I i Cortina F7 16 06 oil I OOIP 7-16-06-01-00 i6 -Grant Close- wOutstan id ng Reis nags r MI Grants, Project MEDIUM out I I I Costing F7 16 06I 02I 00 F7-16-06-02-00I16 - Grant Close-( Unbilled Expenditures � MI Grants, Project MEDIUM Out Costing F7I 161 O6I 03I OOI F7-16-06-03-00I16 - Grant Close-1 Outstanding relquests for MI Grants, i Project MEDIUM Out City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 331 of 41 S F7 12 09 00 00 F7-12.09-00-00 12 -Bill Grantors System allows uncollected receivables to SF Receivables be cabled forward at vfrand. F7 12 10 00 00 F7-12-10-00-00 12 -Bill Grantors System provides the ability to prompt or MI Grants, Project LOW alert users to initiate grant billing on a Costing user -specified schedule (monthly, etc.). F7 12 11 00 rparterly. 00 F7-12-11-00.00 12 - Bill Grantors System generates revenue accruals for SF Grants, Project grant expenditures that are incurred but Costing, General not billed. Let)per F7 12 12 00 00 F7-12-12-00.00 12 - Bill Grantors System provides the ability to apply SF Receivables reryryc�pjeived to more then one gpayments e F7 12 13 00 00 F7-12-13-00-00 12 - Bill Grantors System provides thle ability to bill grant SF Grants, Project phases in total or individually. Costing, Contracts, Billing, Receivables F7 11 14 00 00 F7-12-14-00-00 12 - Bill Grantors System provides the ability to bin multiple SF Grants, Project sponsors of a grant (grantor and local Costing, match). Contracts. Billing, Receivables F7 12 15 00 00 F7-12-15-00-00 12 - Bill Grantors System provides the ability for an edit to SF Grants, Project ensure that grant billings do not exceed Costing, the grant's reimbursable budget (does not Contracts, apply to fee -for -service contracts). Billing, Receivables F7 12 16 06 06 F7-12-16-00-00 12 - Bill Grantors System notifies users of outstanding RO Receivables LOW receivables according to a user -specified ��oainnyp schedule. F7 12 17 00 00 F7-12-17-00-00 12 - Bill Grantors System provides the ability to integrate SF Grants, Project with Accounts Receivable to provide all Costing, billing, aging, and tracking capabilities. Contracts, Billing, Receivables F7 12 18 00 DO F7-12-18-00-00 12 - Bill Grantors System provides the ability to calculate SF Grants, Pmject amount to be billed taking into Costing, consideration amounts previously billed, Contracts, accumulated costs incurred prior to Billing, federal authorization, and/or limits of Receivables matching funds, based on user -defined rules. F7 12 19 00 00 F7-12-19-00-00 12 - Bill Grantors System provides the ability to track orocram ire by source as either: F7 12 19 01 00 F7-12-19-01-00 12 - Bill Grantors recycled Tends - program income is MA Grants, Project MEDIUM This functionality is not currently to be returned to the acency Costing, General available and will need to be Ledger created using PeopleTools. F7 11 19 02 00 F7-12-19-02-00 12 - Bill Grantors reduction of future federal draws - MA Grants, Project MEDIUM This functionality is not currently increase estimated revenue for Costing, General available and will need to be program Income and decrease the Ledger created using PeopleTools. estimated revenue for the federal ppo�rtion F7 12 19 03 00 177-12-19-03-00 12 - Bill Grantors Rurlherance of the program goals - SF Grants, Project increase estimated revenue for Costing, General program income and increase the Ledger total appropriations so the program income could be Spent F7 12 20 00 00 F7-12-20-00-00 12 - BIII Grantors System provides the ability to back MI Grants, Project MEDIUM receipts and expenditures of program Costing. General Income by grant and user -defined time Ledger (enod. F7 12 21 00 00 F7-12-21-00-00 12 - Bill Grantors System provides the ability to generate SF Purchasing, imoiceslpayments based on defined Payables milestones. F7 12 22 00 00 F7-12-22-00-00 12 - Bill Grantors System provides the ability to produce an SF Billing invoice that can differ for each funding ounce. F7 13 01 OT "F7-13-01-00-00 13 - Record System provides the ability to record city SF Grants, Project Grant In -Kind match and/or 3rd party match amounts by Costing and Match grant / activity using any elements of the financial data dessification structure. F7 13 02 00 00 F7-13-02-00-00 13 - Record System provides the ability to track city SF Grants, Project Grant In -Kind match and/or 3rd party match amounts by Costing and Match fiscal oeriod. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 330 of 418 11 1 1 1 1 1 i If I i I a A 1 4 ► 0 1 1 1 I I i 1 1 I i f 1 1 1 1 F7 10 04 00 00 F7-10-04-00-00 10 - Expend System provides the ability to track SF Purchasing Grant Funds retainage withheld on contracts by grant. F7 10 05 00 00 F7-10-05-00-00 10 - Expand System allows users to manually SF General Ledger Grant Funds encumber grant funds outside of the procurement process (e.g., Police Office of Violence against Women grant requires that we reaene (not spend) 5 percent of, rent award . ti,..•k, ,,�r.. 1p �.,,' � ;` u1'A '° , yr' r, ,nex F7 11 01 OC W F7-11-01-00-00 11 - Pass System provides the ability to uniquely Through Grant identify each sub -recipient for grants and Funds all grant financial activity related to sub - recipients, including but not limited to the follovivivJJ: F]' 11 Ot Ot 00 F7-11-01-01-00 11-Pass AN ty to record planned payments to SF Purchasing, Through Grant sub-reciplents Payables Funds F7 11 01 02 00 F7-11-01-02-00 11 - Pass Ability to record funds received from SF Grants, Project Through Grant federal government (or other sources) Costing Funds for pass -through purposes as either revenue or as liabilities. F7 11 01 03 l>oI F7-11-01-03-00 peas Ability to cord funds l from SF Payables Through Grant thereductions city asexpenditures or ash I Funds F7 11 01 04 00IF7-11-01-04-00 sut�recipjent dudget SF Ledger rnrroxg-pass Grant and actualoup by ries as (General l Fundefined grant F7 11 Oil 05 00 F7-71.01-05-00 11 -Pass Ability to enter as memo or statistical SF Payabies Through Grant entries sub+eclpient actual Funds expenditures by categories while procGessing invoices to pay sub- reci F7 11 011 O6 00 F7-11-01-06-00 11 - Pass Ability to capture the effective SF Grants, Through Grant beginning and end date of the sub Purchasing Funds reci0anYs Dartlepts 'vq on anent. F7 11 Oil 07I 00 F7-11-01-07-00 l l - Pass Ability to warn user If draw -down or MI Grants LOW Through Grant reimbursement request exceeds a Funds threshold for the grant award to a sub- ...,. IfliLilh' IIa�1YV111141till lit � l l s„ F7 12 01 0G 00 F7-12-01-00-00 12 - Bill Grantors u8 a SF ill Billing, System providesuoautomatedmatching Receivables cash receipts to nq F7I 12 02I 00 001 F7-12-02-00-00 12 - Bill Grantors System notifies specified users o1 SF Billing, exceptions that occur during automated I Receivables matching of grant payments togrant receivables. F7 12 03I 00 OOI F7-12-03-00-00 12 -Bill Grantors allows for manual matching of SF Receivables ISystem payments received through bank I interfaces to outslandl( Invoices. F7 12 04 00 00 F7-12.04-00-00 12 - BIII Grantors provides the ability to accumulate SF Grants, Project total costs t regard to , Costing, ISystern ch funding source source and then bill contr �rd to the user -defined ser-def ed percentage s Receivables F7 12 05 00 00 F7-12-05-00-00 12 -Bill Grantors System allows for IndMdual transactions SF Grants, Project to be excluded from the automated split I Costing of expenditures to different funding F7 12 O6 00 00 sources. F7-12-06-00-00 12 -Bill Grantors System provides the ability to identify and SF Grants, Project bill grants on a reimbursement basis to Coating, predefined combinations of the financial Contracts, data Uessiftcadon structure (e.g., tund. Billing, grant, activity, account, program). Receivables F7 12 07 00 00I F7-12-07-00-00 12 - Bill Grantors System provides the ability to generate SF Grants, Project grant billing transactions from grants Coating, expenditure balances. Contracts, Billing, Receivables F7 12 08I 00 00 F7-12-08-00-00 12- BIII Grantors provides the ability to recognize SF Grants, Project revenue only after expenditures have Costing, (System .an incurred for grants that we on a Contract, reimbursement basis. Billing, Receivables City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 329 of418 F7 07 09 00 00 F7-07-09-00-00 07 - Define Grant System provides the ability for user- SF Grants, Project Award defined fields that document the required Coaling submissions for grant reimbursement. F7 07 10 00 00 F7-07-10.00.00 07 - Define Gran(System allows changing the CFDA MI Grants, MEDIUM Award number associated with a grant for a Contracts specified date range (e.g., by city fiscal Year). F7 08 01 00 00 F7-08-01-00-00 08 - Approve System provides the ability to create a SF Grants, Project Grant Budget budget for a grant and its activities. Costing, General Ledger F7 08 02 00 00 F7-08-02-00-00 08 - Approve System captures the following grant Grant Budget matching information within the budget: F7 08 02 01 00 F7-08-02-01-00 08 - Approve Amounts of city matching funds SF Grants, Project Grant Budget (multiple) Costing, General Led(ter F7 08 02 02 00 F7-08-02-02-00 08 - Approve Amounts of city non -matching funds SF Grants, Project Grant Budget (muf8ple) Costing, General F7 08 02 03 00 F7-08-02-03-00 08 Approve Amounts local in SF Ledger Grants, Project - Grant Budget of -kind match (multiple) Costing, General Led F7 08 02 04 00 F7-08-02-fit -00 08 - Approve Amounts of 3rd Parry matching funds SF rr Grants, Project Grants, Grant Budget (multiple) Costing, General F7 08 02 OS 00 F7-08-02-05-00 08-Approve Amounts of Maintenance of Effort MI Ledger Grants, Project MEDIUM Grant Budget (MOE) (multiple) Costing, General's Ledger F7 08 02 06 00 F7-08-02-06-00 08 - Approve Amounts of Other Resources non- SF Grants, Project Grant Budget match Costing, General Ledger F7 08 02 07 00 F7-08-02-07-00 OB - Approve Description for each of the matching MI Grants, Project LOW Grant Budget and non -matching funds and Costing, General Maintenance of Efforts Led(�er F7 08 03 oQ 00 F7-08-03-ooA 08 - Approve System provides the ability to establish SF Grants, Projscl Grant Budget grant budgets at varying user -defined Costing, General levels and combinations of the financial Ledger data classification structure for both anticipated receipts and expenditures. F7 08 04 00 00 F7-08-04-00-00 08 - Approve System allows the grant budget to be SF Grants, Project Grant Budget separate and independent of all other Costing, General budgets (i.e.. appropriation, organization, Ledger proq�ct, and contract). F7 08 05 00 00 F7-08.05-00-00 08 - Approve System provides the ability to establish SF Grants, Project Grant Budget budgets at varying levels of the grant Costing, General hiearchv. Led�ler F7 08 06 00 00 F7-08.06-00-00 08 - Approve System provides the ability to do phased SF Grants, Project Grant Budget budgeting for multi -year awards when Costing, General funding is received in installments. Ledger F7 08 07 00 00 F7-08-07-00-00 08 - Approve System provides the ability for positions SF Human Grant Budget to be funded from multiple grants. Resources F7 OB 06 00 00 F7-08-08-00-00 08 - Approve System provides the ability to record a SF Grants, Project Grant Budget billable budget (revenue budget) for Costing, General nts. L9 r F7 09 01 00 00 F7-09-01 -00-00 09 - Record System provides the ability to account for SF Grants, Project Grant Advances advance payments as unsamed revenue CosWp, and recognize revenue periodically based Contracts, on expended amounts. Billing, Receivables F7 10 01 00 V F7-10-01-00-00 10- Expend System provides the ability to apply SF Grants, Project Grant Funds multiole or s(�lit funding sources. Costing F7 10 02 00 DO F7-1 D-02-00-00 10 - Expand System provides the ability to check SF Grants, Project Assumes budgets are configured Grant Funds actual expenditures and encumbrances Costing, General to include the object against a list of eligible expenditure types Ledger codes/classes appropriate for the for the grant. grant. F7 10 03 00 00 177-10-03-00-00 10- Expend System provides the ability to route grant MI Grants, Project MEDIUM Grant Funds expenditures according to different Costing, workflow rules then those that affect an Purchasing, operating budget (as defined by either the General Ledger fund or grant codes). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 328 of 418 F7 07 02 36 00 F7-07-02-36-00 07 - Define Grant FICR Rate SF Grants, Award Contracts F7 07 02 37 00 F7-07-02-37-00 07 - Define Grant FICR Type (provision, pre- SF Grants, Award determined fixed final) Contracts F7 07 02 38 00 F7-07-02-38.00 07- Define Grant Grant Type e.g., �ederal, state, etc.) MI Grants, LOW Award Contracts F7 07 04 39 00 F7-07-02-39-00 07 - Define Grant CFDA number SF Grants, Award Contracts F7 07 02 40 00 F7-07-02-40-00 07 - Define Grant CFDA title SF Grants, Award Contracts F7 07 02 41 00 F7-07-0241-00 07-Define Grant Pass -Through Agency MI Grants, LOW Award Contracts F7 07 02 42 DO F7-07-02-42-00 07 - Define Grant Pass -Through Agency Contact MI Grants, LOW Award Information (name, phone, address) Contracts F7 07 02 43 DO F7-07-02.43-00 07 - Define Grant Funding Source - user defined MI Grants, LOW Award (Federal grant, Foundation grant, city, Contracts Other, etc F7 07 02 44 00 F7-07-02-44-00 07 - Define Grant Comment Id (free form 50 char) SF Grants, Award Contracts F7 07 02 45 00 F7-07-02.45-00 07- Define Grant Procurement Goals (MWBE, etc.) MI Grants, MEDIUM Award Contracts F7 07 02 46 00 F7-07-02.46.00 07 - Define Grant Original sub -recipient approval MI Grants, I MEDIUM Award ' amount Contracts F7 07 02 47 00 F7-07-02-47.00 07 - Define Grant Current sub -recipient budget MI Grants, MEDIUM Award I Co ots F7 07 02 48 DO F7-07-02-48-00 07-Define Grant Sub -recipient amendments MI Grants, MEDIUM Award Contracts F7 07 02 49 DO F7-07-02-49-00 07-Define Grant Sub -recipient carryovers MI Grants, MEDIUM Award Contracts F7 07 02 50 DO F7-07-02-50-00 07 - Define Grant Sub -re iplent fiscal period MI Grants, MEDIUM j Award I Contracts F7 07 02 51 DO F7-07-02-51-00 07 - Define Grant grant manager contact and phone MI Grants, MEDIUM Award ' number multipe) Contracts F7 07 02 52 00 F7-07-02.52-00 07 - Define Grant Original rant ward Number SF Grants, Award Contracts F7 07 02 53 00 F7-07-02-53-00 07 - Define Grant Grant Activities (hierarchical SF Grants, Award organization of grant phases/tasks) I Contracts F7 07 03 00 00 F7-07-03-00-00 07 - Define Grant System provides an edit that ensures the MA Grants, MEDIUM This functionality is not currently Award CFDA number Is valid for the grantor Contracts available and will need to be assigned to the grant. created using PeopleTools, F7 07 04 00 00 F7-07-04-00-00 07 - Define Grant System provides the ability to duplicate SF Grants, Award pre-existing grant data to establish Contracts templates for rrevt gran, l�j F7 07 05 00 00 F7-07-05-00-00 07 - Define Grant System pro es a ality, to add, SF Grants, Award modify, inactivate or delete grant award Contracts information online with audit trail of all chanoes. F7 07 06 00 00 F7.07-06-0010 07 - Define Grant System provides the ability to distinguish Award between grants, bans and contracts. F7 07 06 01 00 F7.07-06-01-00 07 - Define Grant Grants: montes / financial assistance SF Grants, Award which are not a loan, and do not need Contracts to be paid back. F7 07 06 02 00 F7-07-06-02-00 07 - Define Grant Loans: are monies / financial MA Grants, MEDIUM This functionality is not currently Award assistance that do need to be paid Contracts available and will need to be back, either with or without interest. created using PeopleTools. F7 07 06 03 00 F7-07-06.03-00 07 - Define Grant Contracts: are agreements to provide SF Grants, Award a tangible service or product for the Contracts government's exclusive use in return for compensation. F7 07 D7 00 00 F7-07-07-00-DO 07 - Define Grant System provides the ability to differentiate SF Grants, Project Award between federal, state, private and other Costing agency grants for audit purposes. F7 07 08 00 DO F7-07-08-00-00 07 - Define Grant System provides the ability for SF Grants, Project Award establishing grant activity hierarchies at Costing lower levels of detail than grant number and track financial activity associated with each lower level. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 327 of418 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 F7 07 02 00 00 F7-07-02-00-00 07 -Define Grant System provides the ability to track grant Award information, with the ability for the department to require or make optional the following fields: 02 01 00 F7-07-02-01-00 07 - Define Grant Grant Award number (internally SF Award a�siGnad) 02 02 00 F7-07-02-02-00 07 - Define Grant Grant Award name SF Award 02 03 00 F7-07-02-03-00 07- Define Grant Grant Application Number SF Award 02 04 00 F7-07-02-04-00 07-Define Grant Grant description SF Award 02 05 00 F7-07-02-05-00 07 - Define Grant Grantor SF Award 02 06 00 F7-07-02-06-00 07 - Define Grant Grantor Program Classifications (e.g., MI Award IDIS Activ' Number) 02 07 00 F7-07-02-07-00 07 - Define Grant Total gran{ approval amount SF Award 02 08 00 F7-07-02-08-00 07 - Define Grant Grant Original budget SF Award 02 09 00 177-07-02-09-00 07 - Define Grant Grant amendments SF Award 02 10 00 F7-07-02-10-00 07 - Define Grant Grant canywers SF Award 02 11 00 F7-07-02-11-00 07 - Define Grant Grantor fiscal year SF Award 02 12 00 F7-07-02-12-00 07 - Define Grant Grant beginning date SF Award 02 13 00 F7-07-02-13-00 07 - Define Grant Grant expiration date SF Award 02 14 00 F7-07-02-14-00 07 - Define Grant Letter of Intent to Award Date MI Award 02 15 00 F7-07-02-15-00 07 - Define Grant Approved Contract Date MI Award 02 16 00 F7-07-02-16-00 07 - Define Grant Grant Extension Date SF Award 02 17 00 F7-07-02-17-00 07 - Define Grant Grant Budget Begin Date (TO SF Award CONTROL ABILITY TO SPEND) 02 18 00 F7-07-02-18-00 07 - Define Grant Grant Budget End Date (TO SF Award CONTROL ABILITY TO SPEND 02 19 00 F7-07-02-19-00 07 - Define Grant Release of funds Date (to prevent MI Award expenditures before this date) 02 20 00 F7-07-02-20-00 07 - Define Grant Close-out End Date SF Award 02 21 00 F7-07-02-21-00 07-Define Grant Responsible department or division SF Award multip e) 02 22 00 F7-07-02-22-00 07 - Define Grant epa ent or division contact and MI Award phone number (multiple) validated from the EmDlovee table 02 23 00 F7-07-02-23-00 07 - Define Grant Reimbursement schedule SF Award 02 24 00 F7-07-02-24-00 07 - Define Grant City Secretary Contract Award Mi Award Number 02 25 00 F7-07-02-25-00 07 - Define Grant Grantor's Contract/Project Number SF Award 02 26 00 F7-07-02-26-00 07 - Define Grant Original Request Amount SF Award 02 27 00 F7-07-02-27-00 07. Define Grant Amounts of city matching funds SF Award muitl e) 02 28 00 F7-07-02-28-00 07 - Define Grant own of Federal matching funds SF Award (multiple) 04 24 00 F7-07-02-29-00 07 - Define Grant ounts of In -kind matching funds MI Award Co),ip e 02 30 00 F7-07-02-30-00 07 - Define Grant oun of 3rd Party matching funds SF Award mu ltiple) 02 31 00 F7-07-02-31-00 07 - Define Grant ,writs of Maintenance of Effort MI Award (MOE) (multiple) 02 32 00 F7-07-02-32-00 07 - Define Grant Description for each of the matching MI Award funds and Maintenance of Effort amounts 02 33 00 F7.07-02.33-00 07. Define Grant Contact infomreti,n for each of the SF Award �p �1, ntl``ies 02 34 00 F7-07-02-34-00 07 - Define Grant mlc tng cods rates (multiple by Sr Award phase 02 316 00 F7-07-02-35-00 07 - Define Grant Federa Indirect Cost Reimbursement SF Award (FICR) Allowable indicator (yes/no) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 326 of 418 Grants, Contracts Grants, Contracts Grants. Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants. Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts Grants, Contracts These fields that are available are specified. However, additional logic is necessary to specify which fields should be required or optional. LOW LOW LOW LOW LOW Contact validated but phone number does not appear. LOW MEDIUM MEDIUM LOW I # I I 1 a 1 r F7 04 01 04 00 F7-04-01-04-00 04 -Define Phone number (office, fax) Grantor F7 04 01 05 00 F7-04-01-05-00 04 - Define User defined grantor identification Grantor Coda F7 04 0i 06 00 F7-04-01-06-00 04 - Define User defined grantor Identification Grantor escripllQn F7 04 01 07 00 F7-04-01-07-00 04 - Define ange of valid CFDA Numbers Grantor (multiple) F7 04 01 08 00 F7-04-01-08-00 04-Define Grant Accountant Responsible Grantor l�ftlVIII1111IUU&Si14;€aluiVill.ni Ii111111il,w111111111I .1illilII„ flifill 11YWIII4,Ihulill, milli ill IIdilllidli�uY�l F7 05 01 00 00 F7-OS-01-00-00 05 -Define Sub- System provides the ability to track sub- RecI lent recipient information In addition to other vendor related fields, with the ability to require or make optional the following fields: F7 05 Oi Ot 00 F7-0"1-01-00 05 - Define Sub- Sub -Recipient number (multiple Recipient numbers to capture divisions within the vendor, such as the police de{ rtment for a Cltv F7 05 01 02 00 F7-05-01-02-00 05 - Define Sub- Sub -Recipient name(different than l Recipient vendor name' F7 05 01 03 00 F7-05-01-03-00 05 - Define Sub- Organization type (user -defined) Reclplent F7 05 01 04 DO F7-05-01-04-00 05 - Define Sub- FED, # RecJplent F7 05 01 05 OOI F7-05-01-05-00 05 - Define Sub- DUNS number Recipient F7 05 01 06 OOI F7-05-01-06-00 05 - Define Sub- Vendor ID (linked to vendor file) Recipient F7 05 01 07 00 +I F7-O&-W-07-00 05 - Define Sub- Sub -recipient description Recipient F7 05 01 08 OOI F7-05-01-08-00 05 - Define Sub- Sub -Recipient Contact Name(s) Recij�ient F7 OS 01 09 OOI F7-O5-01-09-00 05 - Define Sub- Sub-Reclpient Contact Role Redylent F7 05 01 10 OOI F7-05.01-10-00 05 - Define Sub- Sub -Recipient's mailing address and Reelplent email F7 05 01 11 OOI F7-05-01-11-00 05 - Define Sub- Sub -Recipient Phone number (office, Reci i rit fax F7 06 01 00 00 F7.06-01-1)O-00 06 -Apply for System provides the ability to upload Grant grant applications and proposals to funders. F7 O6 02 DOI DO F7-06-02-00-00 O6 -.Applyforystem IlDtential provides the ability to track grant Grant application's status. F7I O6 03 OOI 00 F7-06-03-00-00 06 —Applyfor stern theattach files a ISyto grant transo F7I 06 04 OOI DOI F7-06-04.OD-00 06 -G ply for p�hvestatu�t of grant ISyysstern F7I O6 051 OOI OOI F7-06-05-00-00 OB - .Apply for information requirements for Grant IAdpj siglications F7I 06 OS 011 001 F7-06-05-01 -00 06-.Apply for M&C number Grant I F7 06 OS 02I 00 F7-06-05-02-00 06 - .Apply for Solicitiatlon Name IjI Grant I F7I O6 05 03I OOI F7-06-05-03-00 O6-.Apply for Solicitation Number Grant I F7 06 OS 04 00 F7-06-05-04-00 06-.Apply for Application Number Grant I F7 06 05 05 00 F7.O6-05-05-00 06-.Apply for Geographical Referenca(s) Grant (Congressional District, Council District) I F7 06 05 0611 00 F7-0t1-05-06-00 06 - .Apply for Status Gant I F7 06 05 07 00 F7.O6-05.07-00 06 - .Apply for I Grant approved/denied date Grant F7 06 05 OB 00 F7-06-OS -08-00 06 - Apply for Dale application submitted Grant 1��,n � � 1 , . 1111lI��'11� uirRW'�IdI11Vl.I I I diVlilitllWl,Itlil>tl!It�9lI4.uEVl��I�IP�dIVI� II ���'�,�,VII'� F7 07 01 00 00 F7-l-00-00 07 - Define Grant System provides the ability to uniquely Award identify each grant through the assignment of an deparVrrent-defined grant number and maintain grant -related descriptive information in a grant table. City of Fort Worth / CIBEF, Inc. Professional Services Agreement Page 325 of 418 SF Grants SF Grants SF Grants SF Grants MI Grants LOW SF Purchasing, Vendor information captures Payables multiple locations which are used to capture divisions within the vendor. SF Purchasing, Payable. SF Purchasing, User-Definetl Field PaYabler SF I Purdhasing, PaYab`es SF I Purchasing, Pa abler SF I P., asing, Pa bias SF Purchasing, I (User -Defined Field Payable. SF Purchasing, Pa Y(abl es SF Purchasing, Pa abler SF Purchasing, PaYabler SF PPurchasleng, I MI Grants MEDIUM Grants supports this functionality for certain programs. SF SF Grants SF Grants MI Grants LOW MI Grants LOW SF Grants SF Grants SF Grants SF Grants SF Grants SF Grants SF Grants I I Contracts F7 03 01 00 00 F7-03-01-00-00 03 - Integration System provides the ability for integration SF Grants, Project with Other with other relevant Financial System Costing Modules modules. F7 03 01 01 00 F7-03-01-01-00 03 - Integration Grant Expenditures originate In SF Grants. Project with Other Procurement and/or Payables and/or Costing, Modules General Ledger Purchasing, Payables, General Ledger F7 03 01 02 00 F7-03-01-02-00 03 - Integration Appropriations orginate in the SF Grants, Project with Other Budgetary Control module Costing, General Modules Ledyar F7 01 01 03 00 F7-03-01-03-00 03 - Integration Grant Billing updates Accounts SF Grants, Project with Other Receivable Costing, Modules Contracts, Billing, Receivables F7 03 of 04 00 F7-03-01-04-00 03 - Integration Sub -Recipients are set up as Vendors SF Grants, Project with Other Costing, Modules Purchasing, Pavables F7 03 01 05 00 F7-03-01-05-00 03 - Integration Grantors are set up as Customers SF Grants, Project with Other Costing, Modules Contracts, Billing, Receivables F7 03 01 09 00 F7-03-01-06-00 03 - Integration Payroll expenses originate with SF Grants, Project Integration into Project Costing with Other Payroll Costing, Time & and Grants is from Time & Labor. Modules Labor F7 03 01 07 00 F7-03-01-07-00 03 - Integration Position funding is tied to the grant SF Human with Other Resources Modules F7 03 01 00 00 F7-03-02-00-00 03 - Integration System updates all financial ledgers SF Grants, Project with Other automatically when posting Individual Costing, General Modules Integration er F7 03 03 00 00 F7-03-03.00-00 03 Syslemt'prov�i�es the ability to link grants SF Grants, Project with Other to multiple projects. Costing Modules F7 03 04 00 00 F7-03-04-00-00 03 - Integration System provides the ability to link multiple SF Grants, Project with Other grants to a single project. Costing Modules F7 03 05 00 00 F7-03-05-00-00 03 - Integration System provides the ability to access SF Grants, Project with Other financial information from other modules Costing Modules (e.g., Procurement, Accounts Payable, etc.) at a detail and summery level for each orant / activlj�yy %a F7 03 06 00 00 F7-03-06-00-00 03 - Integration System provides ability to access RQ Grants, Project MEDIUM with Other detail transaction information from line Costing Modules item detail reports (e.g.. drill down to the individual expenditure and revenue invoices from a list of transactions for a QyranI). F7 03 07 00 00 F7-03-07-00-00 03-Integration System provides the ability to MA Grants, Project MEDIUM This functionality is not currently with Other accommodate differing capital outlay Costing, Asset available and will need to be Modules thresholds for grant funded assets and Management created using PeopleTools. assets acquired from other funding sources. f7 03 08 00 00 F7-03-08-00.00 03 - Integration System provides the ability to ioport SF Grants, Project with Other parallel depredation for grant funded Costing, Asset Modules assets using differing depreciation Management methods and useful lifes for grantor requirements than assets procured from other funding sources. F7 03 66 00 00 F7-03-09-00-00 03 - Integration System provides the ability to report on SF Purchasing Assumes Grant is a chart of with Other open purchase orders by grant and account element or project is Modules activity. acceptable. F7 03 10 00 00 F7-03-10-00-00 03 - Integration SF Receivables with Other System records payments that are Modules received from bank Interfaces. F7 04 01 00 00 F7-04-01 -00-00 04 - Define System captures the following grantor Grantor Information In addition to other customer Information F7 04 01 01 00 F7-04-01-01-00 04 - Define Grantor Contact Name(s) _ SF Grants Grantor F7 04 01 02 00 F7-04-01-02-00 04 - Define Grantor Contact Role SF Grants Grantor F7 04 01 03 00 F7-04-01-03-00 04 - Define Grantees mailing address and email SF Grants Grantor City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 324 of 418 1 1 1 1 1 1 1 1 1 1 1 1 F7 00 13 00 00 F7-00-13-00-00 00 - Financial System provides the ability to report sub- RQ Grants, Project MEDIUM Controls and recipient activity by grant. Costing, General Rgpprtir Ledyar F7 00 14 00 00 F7-00-14-00-00 00 -Financial System provides the ability to summarize RQ Grants, Project MEDIUM Controls and grant activities by grantor for user -defined Costing, General Reoortil lime Deniods. Ledger F7 00 15 00 06 F7-00-15-00-00 00 -Financial System provides the ability to modify RQ Grants, Project MEDIUM Controls and grant reports for federal and dry reporting Costing, General Reporting purposes without programming Ledger knowledoe. F7 00 16 00 00 F7-00-16-00-00 00 - Financial System provides the ability to convert SF Grants, Project Controls and inception to date balances for grant Costing, General F7 00 17 00 00 F7-00.17-00-00 Reoorlinq I -Financial (�a ma Dun)��JR Sys am provides the ability to report SF Ledyar Grants, Project Controls and direct and indirect costs by grant for all Costing, General Reporting levels of the financial data classification Ledger structure. F7 00 16 00 00 F7-00-16.00-00 00 - Financial RQ Grants, Project LOW Controls and System calculates outstanding grant Costing, General Re King award balance. Ledger F7 001 19 00 00 F7-00-19-00-00 00 -Financial System provides the ability to perform MA Grants, Project MEDIUM This functionality is not currently Controls and mass updates to grant reference date. Costing, General available and will need to be Reporting Ledger created using PeopdeTods. F7 00 20 00 00 F7-00-20-00-00 00 - Financial system provides the ability to allocate SF Grants, Project Controls and interest income to a grant Costing, Genera( Re(�1rtin9 tad@er F7 00 21 00 DO F7.00.21.00-00 00 - Financial System provides the ability to track how RQ Grants, Project MEDIUM Controls and Interest allocations are spent. Costing, General Re I Led er F7 01 01 00 00 F7-Oi-01-00-00 Ot - Automated JSystenn will facilitate notification of grant ! MI Grants MEDIUM Workflow grant phase applications, approvals and awards via workflow. F7 01 02 00 110 F7-01-02-00-00 01 - Automated System provides the abilityto utilize MI Grants MEDIUM Workflow workflow to notify user -defined grant administrators and other users (at use, defined time periods) of grant milestones (expiration dates etc.L F7 Ot 03 00 00 F7-01-03-00-00 01 -Automated System provides the ability for workflow SF Grants, Workflow to notify user -defined grant administrators Purchasing, - when a review and/or approval of Payables expenditure or, encumbering transactions. F7 01 04 00 DO F7.01.04-00-00 Ot -Automated System notifies users when expenditures SF General Ledger Workflow are within a user specified threshold of the grant budppt. F7 Ot 151 00 00 F7-01.05-00-00 Ot - Automated System contains an escalation procedure SF Grants, Workflow for items in workflow Purchasing, Payables, General Le r how I;g r �II d00 .:..... .. F7 02 01 00 F7-02-01-00-00 02-Budgetary etary Systemprovidesthe abilityfor buda as follows F7 02 01 Oil W F7-02.01-01-0OI 02-Bud eta Absolute Con of p SF Grants, Project Control transaction from processing, may not Coetlng, General I be overridden: Le per F7I 02 01 021 00 F7-02-01-02-OOI 02-Budgetary Override Control - prevents SF Grants, roject Control transaction from procesaing with the Costing. General I ability o cyanide ertor with Ledger I Pfjorocate sec�+Jity: F7 02 01 031 00 F7-02-01-03-00 02-Budgetary aming - prove os warning message SF Grants, Project Control but allows transaction to process. I Costing, General 4 9gar F7 02 01 04 00 F7.02-01-04-00 02-Budgetary No control - allows transaction to SF Gran, Project Control process wltltout warning. Costing, General Ledger F7 02 02 00 OD F7-02-02-00-00 02-Budgetary System supports the inception-to-0ate SF Grants, Project Control budgetary control for grant budgets, Costing, General rather than annuSystemcont al b etary ((,''Ipntrol. La er F7I 02I 03I 00 °°I F7-02-03-00-0OI 02 gran ndiiure SF Grants. control (budgets or the total award Costing General dip F7I 021 041 00 DOI F7.02.04-00-001 02- Budgetary controls grant expenditure SF Grants, Project Control (System budgets at lower levels of the coding I Costing, General block Ledger City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 323 of 418 Notes: Category I Requirement Degree of Fit Response Degree of Fit Module Complexity of Comments I Prior Text Change Sortt I Sort I TINd I all ones Modification J F7 00 01 00 00 F7.00.01.00-00 00 - Financial System provides the ability to track grant SF Controls and activity over multiple years while Reporting maintaining inception to date balances. F7 00 02 00 00 F7-00-02-00-00 00 - Financial System provides the ability to track and Controls and report grant operations over several Reporting differentperiods. including: F7 00 02 01 00 F7-00-02-01-00 00 • Financial city fiscal year SF Contmis and Reg�lrtirxl F7 00 02 02 00 F7-00-02-02-00 00 - Financial federal fiscal year SF Contmis and Re ortinq �nancial F7 00 02 03 00 F7-00-02-03-00 00 - program fiscal year SF Contmis and Re�yodinq F7 00 02 04 00 F7-00-02-04-00 00 - Financial multi -year grant period SF Controls and R.Fp ding F7 00 02 05 00 F7-00-02-05-00 00 - mancial any specified period within a grant SF Contmis and period Re prting F7 00 03 00 00 F7-00-03-00-00 00 - �Inancial System provides the ability to perform roll, RQ Controls and ups and drill -downs at various levels Reporting within the coding block hierarchy, including the grant hierarchy. F7 00 04 00 00 F7-00-04-00-00 00 - Financial System provides coding reduction of the MA Controls and grant accounting distribution for other Reporting elements of the coding block (e.g.. entering the grant number infers the fund). F7 00 0$ 00 00 F7-00-05-00-00 00 - Financial System provides the ability to make SF Controls and journal entry adjustments to grants for F7 00 06 Reppltinq 00 00 F7-00-06-00-00 00 -Financial anv open acCfyylut'no q$p((jj System prowdes the abilr to track grant SF Controls and expenditures to multiple finding sources. Re �O.nii F7 00 07 00 00 F7-00-07-00-00 00 -Financial System provides the ability to allow SF Controls and recording of memo and statistical s. F7 00 08 00 00 F7-00-08-00-00 00-aFinancal System prov�des the ability to produce the RQ Controls and Schedule of Expenditures of Federal Reporting Awards and State Financial Assistance (for the Single Audit Report). F7 00 09 00 00 F7-00-09-00-00 00 - Financial System provides the ability to close grant SF Controls and fund revenue and expenditrue balances Reporting to fund balance while maintaining inception to date balances for grant reriortino Dur�Dsas. F7 00 10 00 00 F7-00-10-00-00 00 - Financial System provides the ability to provide SF Contmis and budget to actual variance for year-to-date Reporting and inception -to -date or user -defined time period by grant for any element of the financial data classification structure F7 00 11 00 00 F7-00-11-00-00 00 - Financial System provides the ability to generate RQ Controls and reports by grant attributes, such as the Reporting Catalog of Federal Domestic Assistance (CFDAI number. F7 00 12 00 00 F7-00-12.00-00 00 - Financial yslem provides the ability to report grant SF Contmis and revenues/expenditures at all budgetary Repontino levels of the oranL City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 322 of 418 Grants, Pro Costing Grants, Project Costing Grants, Project Costing Grants, Project Costing Grants, Project Costing Grants, Pmject Costing Grants, Project MEDIUM Costing Grants, Project HIGH The City can use System provides the ability to Costing SpeedCharts/Types to default infer components of the grant accounting distribution into accounting distribution from transactions by selecting the other elements of the coding appropriate SpeedChart. block (e.g., entering the grant clarification However, the application, as number infers the fund). delivered does not support inference of chart of account elements based on others. Grants, Project Costing, General Led er Grants, �roject Costing, General Led{ er Grants, Project Costing, General Ledger Grants, Project MEDIUM Costing, General Ledger Grants, Project Costing, General Ledger Grants, Project Costing, General Ledger Grants, Project MEDIUM Costing, General Ledger Grants, Project Costing, General Ledoer F6 11 05 00 00 F6-11-05.00-00 11 - Reporting System provides reports for monitoring project spending across one or multiple F6 11 06 dmonnnents. 00 00 F6-11-06-00-00 11 - Reporting System provides reports for project expenditures at detail or summary levels of the Memel data��,''la$air4�{ion swclura. F6 11 07 00 00 F6-11-07-00.00 11 - Reporting Sysfem provides reports that summarize by user -defined time periods for reporting purposes. F6 11 08 00 00 F6-11-08-DD-00 11 -Reporting System provides queries and inquiries that can be stored for future use. F6 11 09 00 00 F6-11-09-00-00 11 - Reporting System provides the ablllty to download reports to Microsoft Office Desktop awlications. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 321 of 418 4 SF Project Costing, General Ledger SF Project Costing, General Ledger RO Project Costing, MEDIUM General Ledger SF Project Costing, General Ledger SF Project Costing, General Ledger I t I I I I i I I Reqt Category Num Requirement Text F1-01- 01 - Budgetary Budgetary control is fully integrated with all 06-00-00 Control modules to ensure that all transactions using or affecting budget (appropriation, grant, project, department budget) authority are validated online, real-time against up-to-date budget totals based on established budgetary controls. F1-01- 01 - Budgetary System provides the ability to override 07-00-00 Control appropriation, department, grant, and project budgetary control errors with the appropriate security authority for each type of budget, without opening the budget to other users. F1-01- 01 - Budgetary System allows available budget to be 09-00-00 Control calculated based on multiple user -definable formulas, including but not limited to the following: F1-01- 01 -Budgetary Original Budget 09-01-00 Control + Carryforward in - Carryforward out + Transfers in - Transfers out + Supplements - Recisions F1-01- 01 - Budgetary System allows Funds Available to be 10-00-00 Control calculated based on multiple user -definable formulas, including but not limited to the following: F1-01- 01 - Budgetary Available Budget (Encumbered Basis) 10-01-00 Control - Encumbrances - Expended Amounts City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 377 of 418 Degree of BAFO Phase 2A Fit CIBER Development Module Degree of Response response Hours Fit Impacted SF SF General Y Ledger SF SF General Y Ledger VIA RQ RQ 40 General Y Ledger INA SF SF General Y Ledger Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted F1-01- 01 - Budgetary Available Budget (Pre -Encumbered Basis) SF SF General Y 10-03-00 Control - Pre -Encumbrances Ledger - Encumbrances - Expended Amounts F1-01- 01 - Budgetary System performs an appropriated budget SF SF General Y 12-00-00 Control available edit and commits the transaction if it Ledger passes the edit or produces an error message if the transaction fails the edit. F1-01- 01 - Budgetary System provides the ability to control Y 13-00-00 Control appropriation budgets by user -defined combinations of the financial data classification structures elements and/or element hierarchies shown below: F1-01- 01 - Budgetary Fund SF SF General Y 13-01-00 Control Ledger F1-01- 01 - Budgetary Sub -Fund SF SF General Y 13-02-00 Control Ledger F1-01- 01 - Budgetary Department SF SF General Y 13-03-00 Control Ledger F1-01- 01 - Budgetary Hierarchical Organization (Department, SF SF General Y 13-04-00 Control Division, Section) Ledger F1-01- 01 - Budgetary Contract SF SF General Y 13-05-00 Control Ledger F1-01- 01 - Budgetary Program SF SF General Y 13-06-00 Control Ledger F1-01- 01 - Budgetary Location (e.g., Council District) SF SF General Y 13-07-00 Control Ledger F1-01- 01 - Budgetary Project Number SF SF General Y 13-08-00 Control Ledger F1-01- 01 - Budgetary Work Phase or Work Breakdown Structure SF SF General Y 13-09-00 Control (5 levels below work phase) Ledger F1-01- 01 - Budgetary Job SF SF General Y City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 378 of 418 0 1 0 I 1 11 1 1 P I I I f I 1 1 1 1 1 1 1 a 1 1 JI A I 1 I ! I 1 Degree of BAFO Phase 2A Reqt Num Category Requirement Text Fit CIBER Development Module Degree of Fit Response response Hours Impacted 13-10-00 Control Ledger F1-01- 01 - Budgetary General Ledger Account (Expenditure SF SF General Y 13-11-00 Control Object, Revenue Source or Balance Sheet Ledger Account) F1-01- 01 - Budgetary Grant SF SF General Y 13-12-00 Control Ledger F1-01- 01 - Budgetary Grant Phase or Activity (5 levels below Grant SF SF General Y 13-13-00 Control Phase) Ledger F1-01- 01 - Budgetary Function SF SF General Y 13-14-00 Control Ledger F1-01- 01 - Budgetary Fiscal Year SF SF General Y 13-15-00 Control Ledger F1-01- 01 - Budgetary User -Defined Field 1 SF SF General Y 13-16-00 Control Ledger F1-01- 01 - Budgetary User -Defined Field 2 SF SF General Y 13-17-00 Control Ledger 171-01- 01 - Budgetary User -Defined Field 3 SF SF General Y 13-18-00 Control Ledger F1-01- 01 - Budgetary System provides department budgetary Y 14-00-00 Control controls for each department by user -defined combinations of the financial data classification structures elements and/or element hierarchies shown below: F1-01- 01 - Budgetary Fund SF SF General Y 14-01-00 Control Ledger F1-01- 01 - Budgetary Sub -Fund SF SF General Y 14-02-00 Control Ledger F1-01- 01 - Budgetary Department SF SF General Y 14-03-00 Control Ledger F1-01- 01 - Budgetary Hierarchical Organization (Department, SF SF General Y 14-04-00 Control Division, Section) Ledger F1-01- 01 - Budgetary Contract SF SF General Y 14-05-00 Control Ledger City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 379 of 418 Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Fit Num Response response Hours Impacted F1-01- 01 - Budgetary Program SF SF General Y 14-06-00 Control Ledger F1-01- 01 - Budgetary Location (e.g., Council District) SF SF General Y 14-07-00 Control Ledger F1-01- 01 - Budgetary Project Number SF SF General Y 14-08-00 Control Ledger F1-01- 01 - Budgetary Work Phase or Work Breakdown Structure SF SF General Y 14-09-00 Control (5 levels below work phase) Ledger F1-01- 01 - Budgetary Job SF SF General Y 14-10-00 Control Ledger F1-01- 01 - Budgetary General Ledger Account (Expenditure SF SF General Y 14-11-00 Control Object, Revenue Source or Balance Sheet Ledger Account) F1-01- 01 - Budgetary Grant SF SF General Y 14-12-00 Control Ledger F1-01- 01 - Budgetary Grant Phase or Activity (5 levels below Grant SF SF General Y 14-13-00 Control Phase) Ledger F1-01- 01 - Budgetary Function SF SF General Y 14-14-00 Control Ledger F1-01- 01 - Budgetary Fiscal Year SF SF General Y 14-15-00 Control Ledger F1-01- 01 - Budgetary User -Defined Field 1 SF SF General Y 14-16-00 Control Ledger F1-01- 01 - Budgetary User -Defined Field 2 SF SF General Y 14-17-00 Control Ledger F1-01- 01 - Budgetary User -Defined Field 3 SF SF General Y 14-18-00 Control Ledger F1-01- 01 - Budgetary System provides appropriation budgetary SF SF General Y 15-00-00 Control control at varying levels and combinations of Ledger the financial data classification structures to be specified by authorized users (e.g., 3rd level of fund; 1st level of department). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 380 of 418 ► � I• i I j I I I I I , � I � I M I ! t Reqt Degree of BAFO CIBER Phase 2A Degree of Num Category Requirement Text Fit Development Module Fit Response response Hours Impacted F1-01- 01 - Budgetary System provides department budgetary control SF SF General Y 16-00-00 Control at varying levels and combinations of the Ledger financial data classification structures to be specified by authorized users (e.g., 4th level of fund; 4th level of organization, 2nd level of object of expenditure). F1-01- 01 - Budgetary System edits all transactions to ensure that SF SF General Y 18-00-00 Control appropriation budget is available before Ledger posting the transaction. F1-01- 01 - Budgetary System prevents transactions not meeting SF SF General Y 19-00-00 Control available appropriation edits from being Ledger transmitted to the next approval stage. F1-01- 01 - Budgetary System prevents transactions not meeting SF SF General Y 20-00-00 Control available department budgets that are Ledger absolutely controlled from being transmitted to the next approval stage. F1-01- 01 - Budgetary System provide the ability to drill down from the SF SF General Y 21-00-00 Control budget error message to the budget inquiry Ledger screen and automatically retrieve budget data. F1-01- 01 - Budgetary System provides the ability to by-pass MI MI General Y 24-00-00 Control budgetary controls for specified interfaces Ledger F1-01- 01 - Budgetary System provides an exception report of SF SF General Y 25-00-00 Control transactions that failed budgetary controls for Ledger interfaces. F1-02- 02 - Automated System provides for configuration of approval Y 01-00-00 Workflow paths via workflow for the following financial transactions: F1-02- 02 - Automated Departmental vendor invoice routed to SF SF Payables Y 01-03-00 Workflow central Finance Department for approval City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 381 of418 Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted F1-02- 02 - Automated System allows for escalation of items in SF SF General Y 02-00-00 Workflow workflow for a user speciified period to a Ledger, supervisor or proxy. Payables, General Ledger F1-02- 02 - Automated System provides for configuration of Y 03-00-00 Workflow notifications of specified users (not requiring approvals) for the following financial transactions: F1-02- 02 - Automated Vendor Creation MI MI 20 Purchasing Y 03-01-00 Workflow F1-02- 02 - Automated Vendor Updates MI MI 20 Purchasing Y 03-02-00 Workflow F1-03- 03 - Integration Budget control is integrated with other relevant SF SF General Y 01-00-00 with other modules, including but not limited to Ledger, Modules purchasing, asset management, accounts Purchasing, payable, cost allocation, revenue, grants, Payables, projects and general ledger modules. Receivables, Billing, Project Costing F1-03- 03 - Integration Transactions processed in the following sub- Y 02-00-00 with other ledgers automatically update the general Modules ledger in real-time F1-03- 03 - Integration Purchasing SF SF General Y 02-04-00 with other Ledger, Modules Purchasing, eProcurement F1-03- 03 - Integration Inventory SF SF General Y 02-06-00 with other Ledger, Modules Inventory City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 382 of 418 i I 'I ! I i I• I � I a 1 � k 11 i< i 4 I Reqt Num Category Requirement Text F1-04- 04 - Year End When encumbrances and pre -encumbrances 06-00-00 Close are selected to be carried forward, system is able to track them as prior year with the following functionality: F1-04- 04 - Year End Encumbrances are reported by fund balance 06-01-00 Close reserves and rolled forward to the current year. F1-04- 04 - Year End Keeping prior year funding and tracking fund 06-02-00 Close balance reserve by original budget year separately from the new current year fund balance reserve. F1-04- 04 - Year End Liquidate prior year encumbrances and pre- 06-03-00 Close encumbrances from prior year budget carried forward when encumbrances are either cancelled or paid in current year. F1-04- 04 - Year End Report and display prior year encumbrance 06-04-00 Close separately from current year encumbrances. F1-04- 04 - Year End When the encumbrance is closed with a 06-05-00 Close residual unspent amount, the residual amount is tracked and controlled separately and not added back to current year available funds. F1-04- 04 - Year End System provides the ability to close 07-00-00 Close encumbrances by type of encumbrance. F1-04- 04 - Year End System allows any activity after the year end 11-00-00 Close close balance carry forward to be reflected as equity in the following year. F1-04- 04 - Year End System allows for maintaining multiple open 12-00-00 Close fiscal years and periods concurrently, which allows users to post transactions for a new fiscal year prior to closing the previous year. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 384 of 418 Degree of BAFO Phase 2A Fit CIBER Development Module Degree of Response response Hours Fit Impacted Y MA MA 200 General Y Ledger, Purchasing MA MA 80 General Y Ledger, Purchasing MA MA 40 General Y Ledger, Purchasing MA MA 20 General Y Ledger, Purchasing MA MA 20 General Y Ledger, Purchasing MI MI 120 General Y Ledger, Purchasing SF SF General Y Ledger SF SF General Y Ledger 4 Reqt Num Category Requirement Text F1-04- 04 - Year End System provides standard and user -defined 03-00-00 Close year-end close encumbrance rules and functionality, including but not limited to: F1-04- 04 - Year End Carry -forward user -selected encumbrances 03-01-00 Close F1-04- 04 - Year End Carry -forward user -selected pre- 03-02-00 Close encumbrances F1-04- 04 - Year End Carry -forward pre -encumbrances and 03-03-00 Close encumbrances based on user -defined criteria using any element of the financial data classification structure or fields associated with the Appropriation (e.g., appropriation type, fund source) or Fund. F1-04- 04 - Year End Non -selected pre -encumbrances and 03-04-00 Close encumbrances are not carried forward F1-04- 04 - Year End Carry all pre -encumbrances and 03-05-00 Close encumbrances forward F1-04- 04 - Year End System creates year end accruals for goods 04-00-00 Close received but not yet invoiced F1-04- 04 - Year End Ability to maintain the same encumbrance 05-00-00 Close document number on encumbrances and pre - encumbrances that have been partially liquidated in one fiscal year and carried forward into the next fiscal year. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 383 of 418 Degree of BAFO Phase 2A Fit CIBER Development Module Degree of Response response Hours Fit Impacted Y SF SF General Y Ledger, Purchasing MA MA 200 General Y Ledger, Purchasing MA MA 100 General Y Ledger, Purchasing MA MA 50 General Y Ledger, Purchasing MA MA 50 General Y Ledger, Purchasing SF SF General Y Ledger, Purchasing MA MA 120 General Y Ledger, Purchasing Reqt Category Num Requirement Text F1-04- 04 - Year End System should support pre -close (i.e., trial 16-00-00 Close closes) and generates pro forma financial statements. F1-04- 04 - Year End System provides the ability to carryover open 19-00-00 Close purchase orders to the following fiscal year to post against new year budget. F1-05- 05 - Encumbrance System provides the ability for requisitions to 01-00-00 Accounting be entered without posting a pre -encumbrance based on document/transaction type. F1-05- 05 - Encumbrance System provides the ability to adjust or cancel 02-00-00 Accounting a requisition and generate appropriate pre - encumbrance accounting entries. F1-05- 05 - Encumbrance System provides the ability to automatically 03-00-00 Accounting liquidate all unused pre -encumbered money once the requisition's related solicitation and purchase order/contract have been final awarded and encumbered. F1-05- 05 - Encumbrance System provides the ability to change financial 04-00-00 Accounting data classification elements after initial set up with automated update of pre -commitments F1-05- 05 - Encumbrance System provides the ability to increase, 05-00-00 Accounting decrease, liquidate or add new financial data classifications to requisitions after the initial funds have been pre -encumbered. F1-05- 05 - Encumbrance System provides the ability to create an 06-00-00 Accounting encumbrance for estimated costs for inter- department/inter-fund work to be provided. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 385 of418 Degree of BAFO Phase 2A Fit CIBER Development Module Degree of Response response Hours Fit Impacted SF SF General Y Ledger SF SF General Y Ledger MA MA 120 General Y Ledger, Purchasing, eProcurement SF SF General Y Ledger, Purchasing, eProcurement SF SF General Y Ledger, Purchasing, eProcurement SF SF General Y Ledger, Purchasing, eProcurement SF SF General Y Ledger, Purchasing, eProcurement SF SF General Y Ledger, Purchasing, eProcurement Reqt Num Category Requirement Text F1-05- 05 - Encumbrance System provides the ability to establish 07-00-00 Accounting planned expendituress based on "legal obligation" without the need to process through the procurement system. F1-05- 05 - Encumbrance System provides the ability to adjust, change, 08-00-00 Accounting supplement, or reduce existing encumbrances and pre -encumbrances, maintaining an audit trail of all adjustments. F1-05- 05 - Encumbrance Planned Expenditures process should capture 09-00-00 Accounting the following data: F1-05- 05 - Encumbrance Type of encumbrance 09-01-00 Accounting F1-05- 05 - Encumbrance Date established 09-02-00 Accounting F1-05- 05 - Encumbrance Expiration Date 09-03-00 Accounting F1-05- 05 - Encumbrance Status (Open/Closed) 09-04-00 Accounting F1-05- 05 - Encumbrance financial data classification structure codes 09-05-00 Accounting (multiple sets) F1-05- 05 - Encumbrance Originating Center & contact info 09-06-00 Accounting F1-05- 05 - Encumbrance Encumbrance number (auto -generated by 09-07-00 Accounting type of encumbrance) F1-05- 05 - Encumbrance Fiscal year(s) 09-08-00 Accounting City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 386 of 418 1 t I f Degree of CIBER BAFO Fit Development Response response Hours SF SF SF MI SF MI MI SF SF SF SF SF MI SF MI MI SF SF SF SF 20 20 Phase 2A Module Degree of Fit Impacted General Y Ledger, Purchasing, eProcurement General Y Ledger, Purchasing, eProcurement 11 General Y Ledger General Y Ledger General Y Ledger General Y Ledger General Y Ledger General Y Ledger General Y Ledger General Y Ledger Reqt Num Category Requirement Text F1-05- 05 - Encumbrance Description 09-09-00 Accounting F1-05- 05 - Encumbrance Original Amount 09-10-00 Accounting F1-05- 05 - Encumbrance Amended Amount 09-11-00 Accounting F1-05- 05 - Encumbrance Current Balance 09-12-00 Accounting F1-05- 05 - Encumbrance Approval fields 09-13-00 Accounting F1-05- 05 - Encumbrance Text fields 09-14-00 Accounting F1-05- 05 - Encumbrance Multiple vendor numbers 09-15-00 Accounting F1-05- 05 - Encumbrance System provides the ability, at the time of 10-00-00 Accounting purchase order, to: F1-05- 05 - Encumbrance Automatically create the appropriate 10-01-00 Accounting encumbrance F1-05- 05 - Encumbrance Allow authorized users to edit the purchase 10-02-00 Accounting order and automatically adjust the encumbrance created by the system. F1-05- 05 - Encumbrance Automatically liquidate any pre -encumbrance 10-03-00 Accounting City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 387 of 418 Degree of BAFO Phase 2A Fit CIBER Development Module Degree of Response response Hours Fit Impacted SF SF General Y Ledger SF SF General Y Ledger MA MA 20 General Y Ledger MA MA 20 General Y Ledger SF SF General Y Ledger SF SF General Y Ledger MA MA 20 General Y Ledger 17 SF SF General Y Ledger, Purchasing SF SF General Y Ledger, Purchasing SF SF General Y Ledger, Purchasing, eProcurement Degree of BAFO Phase 2A Reqt Num Category Requirement Text Fit CIBER response Development Module Degree of Fit Response Hours Impacted F1-05- 05 - Encumbrance System provides the ability to release any SF SF General Y 11-00-00 Accounting remaining funds on a requisition related to a Ledger, partially awarded solicitation Purchasing, eProcurement F1-05- 05 - Encumbrance System provides the ability to set a system- SF SF General Y 12-00-00 Accounting wide variance between pre -encumbered and Ledger, encumbered amounts when converting a Purchasing, requisition to a purchase order. eProcurement F1-05- 05 - Encumbrance System allows creation of a purchase order for SF SF General Y 13-00-00 Accounting an amount or percentage over the amount pre- Ledger, encumbered, if within department and city-wide Purchasing, variance levels, without having to increase the eProcurement pre -encumbrance. F1-05- 05 - Encumbrance System provides the ability for departments to MA MA 120 General Y 14-00-00 Accounting set a variance level that is more restrictive, but Ledger, not less restrictive, than city-wide variance Purchasing, levels. eProcurement F1-05- 05 - Encumbrance System provides the drill down from obligation SF SF General Y 15-00-00 Accounting balances to detailed transactions. Ledger F1-05- 05 - Encumbrance System provides the ability to define SF SF General Y 16-00-00 Accounting encumbered amounts on a fiscal year basis for Ledger, purchase orders and releases against Purchasing contracts that cross fiscal years. F1-05- 05 - Encumbrance System provides the ability to encumber a SF SF General Y 17-00-00 Accounting single procurement document across multiple Ledger, fiscal years. Purchasing F1-05- 05 - Encumbrance System provides sync points for encumbered SF SF General Y 18-00-00 Accounting releases against contracts to ensure that Ledger, encumbered amounts are in balance with the Purchasing overall contract amount and fiscal year payment estimates (for operating fund appropriations). City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 388 of 418 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1 1 1 f Degree of CIBER Numt Category Requirement Text Fit response p Response F1-05- 05 - Encumbrance System provides the ability to accommodate SF SF 20-00-00 Accounting separate tolerance thresholds for budgetary control when processing encumbrances and pre -encumbrances. F1-05- 05 - Encumbrance System provides the ability to encumber to SF SF 21-00-00 Accounting multiple accounting distributions per line item F1-05- 05 - Encumbrance System provides the ability to establish SF SF 22-00-00 Accounting encumbrances for multiple fiscal years on a per PO line basis F1-05- 05 - Encumbrance System provides the ability to automatically SF SF 23-00-00 Accounting generate the appropriate updates to encumbered amounts and accounting distributions based on changes to the purchase order. F1-05- 05 - Encumbrance System provides the ability for an option to SF SF 24-00-00 Accounting liquidate remaining/outstanding encumbrance on a purchase order is closed. BAFO Development Hours Phase 2A Module Degree of Fit Impacted General Y Ledger, Purchasing, eProcurement General Ledger, Purchasing_ General Ledger, Purchasing General Ledger, Purchasing General Ledger, Purchasing, Payables Y Y Y la F1-05- 05 - Encumbrance System provides the ability to allow a PO to be SF SF General Y 25-00-00 Accounting charged to an accounting distribution other Ledger, than that of the associated requisition. Purchasing F1-05- 05 - Encumbrance System provides the ability to adjust or cancel SF SF General Y 26-00-00 Accounting a purchase order and generate appropriate Ledger, adjustments to encumbered balances. Purchasing F1-05- 05 - Encumbrance System provides the ability to allow the SF SF General Y 27-00-00 Accounting initiation of requisitions and purchase order Ledger, documents prior to year-end which cannot be Purchasing, pre -encumbered until the new budget is eProcurement loaded. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 389 of418 Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted F3-00- 00 - Financial System provides control by updating the SF SF General Y 01-00-00 Controls general ledger and all subsidiary ledgers from Ledger the same transaction source. F3-00- 00 - Financial System enforces user -based security rules Y 02-00-00 Controls based on financial data classification structures (either individually or in combinations), including but not limited to the following: F3-00- 00 - Financial Fund MA MA 40 General Y 02-01-00 Controls Ledger F3-00- 00 - Financial Sub -Fund MA MA 40 General Y 02-02-00 Controls Ledger F3-00- 00 - Financial Department MA MA 40 General Y 02-03-00 Controls Ledger F3-00- 00 - Financial Hierarchical Organization (Department, MA MA 25 General Y 02-04-00 Controls Division, Section) Ledger F3-00- 00 - Financial Contract MA MA 25 General Y 02-05-00 Controls Ledger F3-00- 00 - Financial Program MA MA 25 General Y 02-06-00 Controls Ledger F3-00- 00 - Financial Location (e.g., Council District) MA MA 25 General Y 02-07-00 Controls Ledger F3-00- 00 - Financial Project Number SF SF Project Y 02-08-00 Controls Costing F3-00- 00 - Financial Work Phase or Work Breakdown Structure SF SF Project Y 02-09-00 Controls (5 levels below work phase) Costing F3-00- 00 - Financial Job SF SF Project Y 02-10-00 Controls Costing F3-00- 00 - Financial General Ledger Account (Expenditure MA MA 25 General Y 02-11-00 Controls Object, Revenue Source or Balance Sheet Ledger Account) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 390 of 418 t I I I E I I i 1 1 $ J I I I I I 1 Reqt Degree of CIBER BAFO Phase 2A Degree of Num Category Requirement Text Fit Development Module Fit Response response Hours Impacted F3-00- 00 - Financial Grant SF SF Project Y 02-12-00 Controls Costing F3-00- 00 - Financial Grant Phase or Activity (5 levels below Grant SF SF Project Y 02-13-00 Controls Phase) Costing F3-00- 00 - Financial Function MA MA 25 General Y 02-14-00 Controls I Ledger F3-00- 00 - Financial Fiscal Month MA MA 25 General Y 02-15-00 Controls Ledger F3-00- 00 - Financial Fiscal Year MA MA 25 General Y 02-16-00 Controls Ledger F3-00- 00 - Financial User -Defined Field 1 MA MA 25 General Y 02-17-00 Controls I Ledger F3-00- 00 - Financial User -Defined Field 2 MA MA 25 General Y 02-18-00 Controls Ledger F3-00- 00 - Financial User -Defined Field 3 MA MA 25 General Y 02-19-00 Controls Ledger F3-00- 00 - Financial System edits transactions to ensure that each SF SF General Y 03-00-00 Controls entry to a fund is balanced and complete, and Ledger each fund is maintained as a self -balancing entity during all processing. F3-00- 00 - Financial System must balance at a lower level than SF SF General Y 04-00-00 Controls fund, by additional data classification Ledger structures, if configured accordingly. F3-00- 00 - Financial System simultaneously supports multiple Y 06-00-00 Controls bases of accounting for the appropriate fund types, including but not limited to: F3-00- 00 - Financial Full Accrual basis MA MA 200 General Y 06-02-00 Controls Ledger City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 391 of 418 Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted F3-00- 00 - Financial System provides transaction edits that permit, SF SF General Y 09-00-00 Controls warn, or reject transactions based on user- Ledger defined allowable data classification structure combinations. F3-00- 00 - Financial System has the ability to record and maintain Y 10-00-00 Controls the following financial balances across all elements of the financial data classification structure: F3-00- 00 - Financial Total Expenditures SF SF General Y 10-04-00 Controls Ledger F3-00- 00 - Financial Pre -Encumbrances SF SF General Y 10-06-00 Controls Ledger F3-00- 00 - Financial Encumbrances SF SF General Y 10-07-00 Controls Ledger F3-00- 00 - Financial Interfund Transactions SF SF General Y 10-08-00 Controls Ledger F3-00- 00 - Financial Fund Balance SF SF General Y 10-09-00 Controls Ledger F3-00- 00 - Financial Breakdown of fund balance into restricted, RQ RQ 40 General Y 10-10-00 Controls committed, assigned, and unassigned. Ledger F3-00- 00 - Financial System provides users the ability to select SF SF General Y 11-00-00 Controls summary or detailed posting of transactions to Ledger the general ledger from subsidiary ledgers/modules within the system. F3-00- 00 - Financial System provides for at least 16 user -definable SF SF General Y 13-00-00 Controls accounting periods per year that can either be Ledger used for transacting against financial balances, adjusting periods against financial balances, or adjusting periods that are for memo entries only and do not update financial balances, but will be reflected in annual reports. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 392 of 418 1 1 i I I I I I I i 1 1 4 1 1 1 1 1 1 Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted F3-00- 00 - Financial System provides subsidiary ledgers for balance RQ RQ 40 General Y 14-00-00 Controls sheet accounts as needed. These subsidiaries Ledger must generate reports of open transactions that accumulate to the balance sheet account totals. F3-00- 00 - Financial System provides ability to trace summarized SF SF General Y 15-00-00 Controls transactions online in the General Ledger back Ledger to detail source documents in other system modules or subsystems within the enterprise system. If the information must be retrieved from these modules or subsystems, it should be transparent to the user. F3-01- 01- Journal System provides ability to default offsetting SF SF General Y 14-00-00 Entries entries from sub -ledger transactions (e.g., Ledger Accounts Payable for vouchers, reserve for encumbrances for purchase orders etc.). F3-01- 01- Journal System provides the ability for an entry to MA MA 200 General Y 30-00-00 Entries reference a previously established Ledger encumbrance. After the transaction is posted, the referenced encumbrance document should automatically liquidate. F3-02- 02 - Month End System captures tasks required for month end SF SF Enterprise Y 11-00-00 Close close Portal F3-02- 02 - Month End System tracks status of completion for month SF SF Enterprise Y 12-00-00 Close end close tasks. Portal F3-02- 02 - Month End System prevents transactions from posting to a SF SF General Y 18-00-00 Close closed period in either the general ledger or the Ledger sub -ledger. F3-02- 02 - Month End System allows users to define closing periods SF SF General Y 19-00-00 Close and the period closing dates. Ledger City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 393 of 418 Reqt Num Category Requirement Text F3-02- 02 - Month End System provides support for multiple open 20-00-00 Close periods. F3-02- 02 - Month End System allows reopening a closed period for 21-00-00 Close transaction processing, with appropriate security. F3-02- 02 - Month End System allows posting of expenditure and 23-00-00 Close revenue accruals required for closing. F3-03- 03 - System provides the ability to create an 02-00-00 Interdepartmental inter/intra-Department encumbrance for Billing agreements that create an obligation. F3-03- 03 - System provides the ability to transmit 04-00-00 Interdepartmental inter/intra-Department billings with line -item Billing detailed charges for review prior to posting. F3-03- 03 - System allows for automatic posting of 05-00-00 Interdepartmental inter/intra-Department billings after a user Billing specified period of time has elapsed with no response. Degree of CIBER BAFO Fit Development Response response Hours SF SF SF SF SF SF SF SF MI MI MI F3-03- 03 - System provides the ability for the Department MI 06-00-00 Interdepartmental receiving charges to establish parameters that Billing determine where items are charged (what fund and cost center is used) while preventing them from changing the account or amount used on the transaction. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 394 of 418 MI MI 40 40 40 Module General Ledger General Ledger General Ledger Purchasing General Ledger, Billling, Project Costing, Contracts, Payables General Ledger, Billling, Project Costing, Contracts, Payables General Ledger, Billling, Project Costing, Contracts, Payables Phase 2A Degree of Fit Impacted Y Y M u u Y Y Reqt Category Requirement Text Num F3-03- 03 - System provides the ability to send a user- 07-00-00 Interdepartmental specified notification (e.g., email) back to the Billing originator, if the interdepartment/interfund entries are rejected or a specified period of time lapses, including communication of the correct account distributions to use. F3-03- 03 - System provides the ability to restrict inter- 08-00-00 Interdepartmental department postings based upon security to Billing authorized users within departments (e.g., fiscal coordinators). F3-03- 03 - System provides the ability to flag an inter- 09-00-00 Interdepartmental department entry "in dispute" and allow user - Billing defined workflow rules to resolve dispute. F3-03- 03 - System provides the ability to settle 10-00-00 Interdepartmental interdepartment invoices to cash. Billing F3-03- 03 - System provides the ability to establish 11-00-00 Interdepartmental accounting strings associated with Billing interdepartmental transactions to minimize keying of the seller account information on each payment. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 395 of 418 Degree of CIBER Fit Response response MI MI BAFO Development Hours 40 MI MI 40 MI MI 40 SF SF SF SF Module General Ledger, Billling, Project Costing, Contracts, Payables General Ledger, Billling, Project Costing, Contracts, Payables General Ledger, Billling, Project Costing, Contracts, Payables General Ledger, Billling, Project Costing, Contracts, Payables General Ledger, Billling, Project Costing, Contracts, Phase 2A Degree of Fit Impacted Y u Y v u Reqt Num Category Requirement Text Degree of BAFO Phase 2A Fit CIBER Development Module Degree of Response response Hours Fit Impacted Payables F3-07- 07 - Financial System provides ability to trace summarized RQ RQ 20 General Y 01-00-00 Reports transactions in General Ledger reports back to Ledger detail source documents in other system modules. F3-07- 07 - Financial System maintains a history of all General SF SF General Y 05-00-00 Reports Ledger transactions and produces detailed Ledger transaction reports to provide an appropriate audit trail. F3-07- 07 - Financial System provides the ability to drill down from SF SF General Y 35-00-00 Reports online inquiry screens to underlying detailed Ledger transactions (e.g., journal entries). F3-07- 07 - Financial System supports projecting cash requirements SF SF Cash Y 39-00-00 Reports for a user specified period of time using Management, relevant information about outlays and inflows Payables, from both Accounts Payable and Accounts Receivables Receivable. F3-08- 08 - Interfaces System provides the ability to interface MI MI 80 General Y 03-00-00 to/from other pertinent financial data classification structure Ledger Systems data to other systems. R F5-00- 00 - General System provides the ability to maintain Y 02-00-00 Requirements pertinent data on both capitalized and non - capitalized assets, which can be either portable or non -portable as follows: F5-00- 00 - General Capitalize assets based upon a user- MI MI 20 Asset Y 02-01-00 Requirements specified criteria, including amount threshold Management by asset type. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 396 of 418 I I I I I 1 II Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted F5-00- 00 - General Track assets (non -capitalized equipment) SF SF Asset Y 02-02-00 Requirements that are not to be capitalized per City policy but Management have been deemed to be secured by City or department policy (e.g., mobile phones). F5-00- 00 - General System provides the following Asset Y 04-00-00 Requirements Management functionality: F5-00- 00 - General Betterments SF SF Asset Y 04-07-00 Requirements Management F5-01- 01 -Asset add System is fully integrated with General Ledger, SF SF Asset Y 01-00-00 and Maint Procurement, and Accounts Payable to carry Management, forward relevant purchasing, descriptive, General invoice and accounting information as a Ledger, starting point for recording the asset. Purchasing, Payables F5-01- 01 -Asset add System tracks the following categories of Y 02-00-00 and Maint assets: F5-01- 01 -Asset add Land SF SF Asset Y 02-01-00 and Maint Management F5-01- 01 -Asset add Buildings SF SF Asset Y 02-02-00 and Maint Management F5-01- 01 -Asset add Leasehold improvements SF SF Asset Y 02-03-00 and Maint Management F5-01- 01 -Asset add Equipment SF SF Asset Y 02-04-00 and Maint Management F5-01- 01 -Asset add Furniture and fixtures SF SF Asset Y 02-05-00 and Maint Management F5-01- 01 -Asset add Vehicles SF SF Asset Y 02-06-00 and Maint Management F5-01- 01 -Asset add Trailers SF SF Asset Y 02-07-00 and Maint Management F5-01- 01 -Asset add Equipment acquired through capital leases SF SF Asset Y 02-08-00 and Maint Management F5-01- 01 -Asset add Construction in progress SF SF Asset Y City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 397 of 418 Reqt Num Category Requirement Text 02-09-00 and Maint F5-01- 01 -Asset add Infrastructure 02-10-00 and Maint F5-01- 01 -Asset add Other user -defined categories (please 02-11-00 and Maint document number and nature) F5-01- 01 -Asset add System provides the ability to automatically 06-00-00 and Maint create and assign an alpha -numeric asset number that is defined by department to a single item or multiple items purchased. F5-01- 01 - Asset add System provides the ability to maintain detailed 12-00-00 and Maint property information required to identify, properly account for, and safeguard all assets, including but not limited to the following: Degree of BAFO Fit CIBER Development Response response Hours SF SF SF I ` SF SF SF F5-01- 01 -Asset add Requisition Number SF SF 12-08-00 and Maint F5-01- 01 - Asset add Purchasing Document Numbers SF SF 12-09-00 and Maint F5-01- 01 -Asset add Asset Acquisition Date SF SF 12-10-00 and Maint F5-01- 01 -Asset add Delivery Date SF SF 12-15-00 and Maint F5-01- 01 -Asset add Unit Cost/Value SF SF 12-18-00 and Maint F5-01- 01 - Asset add Vendor Number, Name SF SF 12-23-00 and Maint F5-01- 01 -Asset add Asset Descriptive Information SF SF 12-24-00 and Maint F5-01- 01 -Asset add Manufacturer Number, Name SF SF 12-25-00 and Maint City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 398 of 418 1 1 1 1 1 Module Management Asset Management Asset Management Asset Management Asset Management, Purchasing Asset Management, Purchasing Asset Management, Purchasing Asset Management, Purchasing Asset Management Asset Management Asset Management Asset Management Phase 2A Degree of Fit Impacted Y Y Y Iv Y Y Y lit Y Y Y Y I I I I I I I II I I t I I t Reqt Degree of CIBER BAFO Num Category Requirement Text Fit Development Response response p Hours F5-01- 01 -Asset add Model Year SF SF 12-26-00 and Maint F5-01- 01 - Asset add Model Number SF SF 12-27-00 and Maint F5-01- 01 -Asset add Betterments SF SF 12-33-00 and Maint F5-01- 01 -Asset add Budget Year (from which asset was SF SF 12-41-00 and Maint purchased) F5-01- 01 - Asset add System captures an audit trail of changes to SF SF 16-00-00 and Maint the asset record, including user, date and time, old and new value) F5-01- 01 - Asset add System allows for drill -down to original SF SF 17-00-00 and Maint procurement documents from the asset record. F5-01- 01 - Asset add System provides the ability to copy an asset SF SF 19-00-00 and Maint record to create a similar asset record. F5-01- 01 -Asset add Authorized users are able to correct SF SF 20-00-00 and Maint discrepancies in asset records by overriding initially loaded information (received from General Ledger, Accounts Payable, and Purchasing modules) with proper authorization. F5-01- 01 -Asset add In addition to asset information listed MI MI 20 21-00-00 and Maint previously, system maintains detailed property information required to identify, properly account for, and safeguard City lands, including, but not limited to the following: F5-01- 01 -Asset add Acquisition information (purchased from SF SF 21-03-00 and Maint whom, etc.) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 399 of 418 Module Asset Management Asset Management Asset Management Asset Management Asset Management, Purchasing Asset Management Asset Management, Purchasing, General Ledger, Payables Asset Management Phase 2A Degree of Fit Impacted Y Y Y Y Y Y Y Y Asset Y Management Asset Y Management Degree of BAFO Phase 2A Reqt Num Category Requirement Text Fit CIBER Development Module Degree of Response response Hours Fit Impacted F5-01- 01 -Asset add System tracks assets purchased with various SF SF Asset Y 26-00-00 and Maint funding sources (i.e., grants) using a Management searchable reportable field. F5-01- 01 -Asset add System provides the ability for commodity line MI MI 20 Asset Y 28-00-00 and Maint items to contain the following data items, Management including but not limited to, the following data elements: Fixed asset Indicator (new, replacement, or enhancement; if replacement or enhancement, need existing tag number). F5-01- 01 -Asset add System provides the ability to capture a fixed MI MI 40 Asset Y 29-00-00 and Maint asset indicator (determine whether commodity Management is an asset based on dollar amount and expenditure object code). F5-01- 01 -Asset add System provides the ability to drop the "asset" SF SF Asset Y 30-00-00 and Maint indicator that was established at the time a Management, requisition was created, if the associated PO Payables amount is less than the user -specified dollar threshold, based on the City's business rules. F5-01- 01 -Asset add SF SF Asset Y 31-00-00 and Maint System provides the ability to assign multiple Management, expenditure line items to a single fixed assset Purchasing, record Inventory F5-01- 01 - Asset add System provides the ability to capture items SF SF Asset Y 32-00-00 and Maint such as lot number, serial number, asset tag Management, number, and expiration date at time of receipt. Purchasing F5-01- 01 - Asset add System provides the ability to flag purchases SF SF Asset Y 33-00-00 and Maint Management, as placed in service�� as fixed assets upon Purchasing receipt of good. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 400 of 418 1 1 1 1 1 1 1 i i I 1 4 1 1 1 1 1 1 1 Reqt Num Category Requirement Text F5-01- 01 -Asset add System evaluates purchase order line items 35-00-00 and Maint and applies the following edit: If the unit price is greater than the capitalization threshhold and the expenditure account is not capital outlay and the commodity code indicates that it may be a fixed asset, then the transaction should produce a warning if the fixed asset indicator is not selected 175-03- 03 -Surplus System should provide ability to support 05-00-00 Property electronic advertisement of items for sale (e.g., on the web) to designated customers. F5-03- 03 -Surplus System supports receipt of sealed bid 06-00-00 Property responses through electronic means. F5-03- 03 -Surplus If bid opening date and time has expired, the 07-00-00 Property System must prohibit the acceptance of a bid through electronic means. F5-03- 03 -Surplus System should support the publishing of 08-00-00 Property surplus properties to be sold on a web site. F5-03- 03 -Surplus System maintains a file of customers that 09-00-00 Property commonly bid on surplus properties. F5-03- 03 -Surplus System should allow for sale of items via 10-00-00 Property sealed bid and perform bid tabulations to show highest bidder. F5-03- 03 -Surplus System should allow for grouping of items into 11-00-00 Property lots for sale while retaining specific item owner information. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 401 of 418 Degree of BAFO CIBER Fit Development Response response Hours MA MA 40 SF SF SF SF SF SF SF SF SF SF SF SF SF SF Module Asset Management Asset Management, Strategic Sourcing Strategic Sourcing Strategic Sourcing Asset Management, Strategic Sourcing Asset Management, Strategic Sourcing Strategic Sourcing Strategic Sourcing Phase 2A Degree of Fit Impacted Y Itl Y Y Y In Y Y Degree of BAFO Phase 2A Reqt Num Category Requirement Text Fit CIBER Development Module Degree of Fit Response response Hours Impacted F5-03- 03 -Surplus System should allow for recording of proceeds SF SF Strategic Y 12-00-00 Property from sales of assets (net of auction costs) Sourcing when item is sold. F5-03- 03 -Surplus System produces a bill of sale for property SF SF Asset Y 13-00-00 Property sales. Management, Strategic Sourcing, Billing F5-05- 05 - Physical System provides fully integrated bar-code TP TP 40 Y 01-00-00 Inventory technology for physical inventory tagging upon acquisition/purchase and annual inventory certification(s). F5-05- 05 - Physical System provides ability to create a scanned TP TP 40 Y 02-00-00 Inventory record file from bar-coding for comparison to fixed asset and portable equipment records. F5-06- 06 - Capital System is able to identify/record all SF SF Project Y 01-00-00 Projects capitalizable costs associated with the Costing, Asset construction or purchase/acquisition of an Management asset. F5-06- 06 - Capital System captures and maintains construction SF SF Project Y 05-00-00 Projects work in progress information and provides the Costing, Asset ability to recognize fixed/capital assets when Management they are placed in service, regardless of whether the project has been completed. F5-07- 07 - Leases System tracks assets in accordance with the Y 01-00-00 requirements of FASB Statement No. 13: Accounting for Leases, as amended, including but not limited to: F5-07- 07 - Leases Tracking lease payments SF SF Asset Y 01-02-00 Management F5-07- 07 - Leases Periodic cost recognition SF SF Asset Y 01-03-00 Management City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 402 of 418 1 1 i i 1 11 1 1 1 1 1 1 1 1 1 1 1 1 1 Reqt Category Num F5-07- 07 - Leases 01-07-00 Requirement Text Tracking purchase options Degree of CIBER Fit Response response SF SF BAFO Phase 2A Development Module Degree of Hours Fit Impacted Asset Y Management F5-07- 07 - Leases System is able to differentiate between leased SF SF Asset Y 02-00-00 assets and purchased assets. Management F5-07- 07 - Leases System provides the ability to perform RQ RQ 20 Asset Y 04-00-00 lease/purchase comparative analyses. Management F5-08- 08 - Asset System should support hyperlinks to the MI MI 20 Asset Y 03-00-00 Warranties vendor's web site to reference asset Management maintenance and warranty information. F5-09- 09 - Querying and System produces a transaction register audit SF SF Asset Y 04-00-00 Reporting trail of all acquisitions, transfers, changes and Management retirements during a user -defined time period by asset type, department, transaction date or purchase amount. . ., .. •e.•m . . . N£, 5.•U is F6-02- 02 - Capture System provides the ability to allocate direct SF SF Project Y 01-00-00 Project Costs costs to projects through expenditure Costing, transactions. Purchasing, Payables, Expenses, General Ledger F6-07- 07 - Budget System provides the ability for project Y 01-00-00 Control budgetary control options by project budget line as follows: F6-07- 07 - Budget Absolute control - prevents transaction SF SF Project Y 01-01-00 Control from processing, may not be overridden Costing, General Ledger F6-07- 07 - Budget Override Control - prevents transaction SF SF Project Y 01-02-00 Control from processing with the ability to override Costing, error with appropriate security General Ledger City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 403 of 418 Degree of BAFO Phase 2A Reqt Num Category Requirement Text Fit CIBER Development response Module Degree of Fit Response Hours Impacted F6-07- 07 - Budget Warning — provides warning message but SF SF Project Y 01-03-00 Control allows transaction to process Costing, General Ledger F6-07- 07 - Budget No control — allows transaction to process SF SF Project Y 01-04-00 Control without warning Costing, General Ledger F6-07- 07 - Budget System provides the option to alert user with a Y 02-00-00 Control flag or warning when appropriated project budget is overcharged either by overall project, sub -project, phase, or job and allows the overcharge only with proper security. F6-07- 07 - Budget Overall project SF SF Project Y 02-01-00 Control Costing, General Ledger F6-07- 07 - Budget Sub -project SF SF Project Y 02-02-00 Control Costing, General Ledger F6-07- 07 - Budget Phase SF SF Project Y 02-03-00 Control Costing, General Ledger F6-07- 07 - Budget Job SF SF Project Y 02-04-00 Control Costing, General Ledger F6-09- 09 - Financial System provides the ability to establish project SF SF Project Y 01-00-00 Controls accounts to record project budgets, pre- Costing, encumbrances/encumbrances, expenditures, General anticipated revenues, receivables, and Ledger receipts. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 404 of 418 1 1 1 1 1 1 1 1 4 1 1 1 1 1 1 1 1 1 1 11 1 Reqt Num Category Requirement Text F6-09- 09 - Financial System provides the ability to record and 03-00-00 Controls maintain data at the lowest level of the chart of accounts structure and summarize data through roll -ups to higher levels of the projects hierarchy. F6-09- 09 - Financial System provides the ability to prevent 04-00-00 Controls contractors from receiving payment prior to certain user -defined criteria being met (e.g., prior to the official start date of the project or until other requirements are met). F6-10- 10 - Integration System provides the ability for the Project 01-00-00 Accounting module to integrate with other relevant modules, including but not limited to: F6-10- 10 - Integration Procurement for capturing projects: 01-02-00 F6-10- 10 - Integration on procurement contracts 01-02-01 F6-10- 10 - Integration on encumbrances 01-02-02 F6-10- 10 - Integration 01-02-03 F6-10- 10 - Integration 01-05-00 F6-10- 10 - Integration 01-05-01 City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 405 of 418 on retainage balances for vendors Accounts Payable for capturing: vendor invoices related to projects Degree of CIBER BAFO Fit Development Response response Hours SF SF SF SF SF SF SF SF RQ RQ 20 SF SF Phase 2A Module Degree of Fit Impacted Project Y Costing, General Ledger Project Y Costing, General Ledger Y Project Y Costing, Purchasing Project Y Costing, Purchasing, General Ledger Project Y Costing, Purchasing, Payables Y Project Y Costing, Payables Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted F6-10- 10 - Integration retainage balances for vendors RQ RQ 20 Project Y 01-05-02 Costing, Purchasing, Pa ables BONITOS ,. F7-00- 00 - Financial System provides the ability to perform roll -ups RQ RQ 20 Grants, Y 03-00-00 Controls and and drill -downs at various levels within the Project Reporting coding block hierarchy, including the grant Costing hierarchy. F7-00- 00 - Financial System provides coding reduction of the grant MA MA 40 Grants, Y 04-00-00 Controls and accounting distribution for other elements of Project Reporting the coding block (e.g., entering the grant Costing number infers the fund). F7-01- 01 -Automated System provides the ability for workflow to SF SF Grants, Y 03-00-00 Workflow notify user -defined grant administrators when a Purchasing, review and/or approval of expenditure or Payables encumbering transactions. F7-01- 01 - Automated System notifies users when expenditures are SF SF General Y 04-00-00 Workflow within a user specified threshold of the grant Ledger budget. F7-01- 01 - Automated System contains an escalation procedure for SF SF Grants, Y 05-00-00 Workflow items in workflow Purchasing, Payables, General Ledger F7-02- 02 - Budgetary System provides the ability for grant budgetary 01-00-00 Control control options as follows: F7-02- 02 - Budgetary Absolute Control - prevents transaction 01-01-00 Control from processing, may not be overridden; City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 406 of 418 SF SF Grants, Project Costing, General Ledger Itl go Reqt Num Category Requirement Text F7-02- 02 - Budgetary Override Control - prevents transaction 01-02-00 Control from processing with the ability to override error with appropriate security; F7-02- 02 - Budgetary Warning - provides warning message but 01-03-00 Control allows transaction to process. F7-02- 02 - Budgetary No control - allows transaction to process 01-04-00 Control without warning. F7-02- 02 - Budgetary System supports the inception -to -date 02-00-00 Control budgetary control for grant budgets, rather than annual budgetary control. F7-02- 02 - Budgetary System controls grant expenditure budgets for 03-00-00 Control the total award F7-02- 02 - Budgetary System controls grant expenditure budgets at 04-00-00 Control lower levels of the coding block F7-03- 03 - Integration System provides the ability for integration with 01-00-00 with Other other relevant Financial System modules. Modules City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 407 of 418 Degree of BAFO CIBER Phase 2A Degree of Fit Development response Module Fit Response Hours Impacted SF SF Grants, Y Project Costing, General Ledger SF SF Grants, Y Project Costing, General Ledger SF SF Grants, Y Project Costing, General Ledger SF SF Grants, Y Project Costing, General Ledger SF SF Grants, Y Project Costing, General Ledger SF SF Grants, Y Project Costing, General Ledger SF SF Grants, Y Project Costing Reqt Category Requirement Text Num F7-03- 03 - Integration Grant Expenditures originate in 01-01-00 with Other Procurement and/or Payables and/or General Modules Ledger F7-03- 03 - Integration Sub -Recipients are set up as Vendors 01-04-00 with Other Modules F7-03- 03 - Integration System provides the ability to report on open 09-00-00 with Other purchase orders by grant and activity. Modules F7-05- 05 - Define Sub- System provides the ability to track sub- 01-00-00 Recipient recipient information in addition to other vendor related fields, with the ability to require or make optional the following fields: F7-05- 05 - Define Sub- Sub -Recipient number (multiple numbers 01-01-00 Recipient to capture divisions within the vendor, such as the police department for a City) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 408 of 418 1 1 1 1 1 1 Degree of CIBER BAFO Fit Development Module Response response Hours SF SF Grants, Project Costing, Purchasing, Payables, General Ledger SF SF Grants, Project Costing, Purchasing, Payables SF SF Purchasing SF SF Purchasing, Payables Phase 2A Degree of Fit Impacted Y Y Y Y Y Reqt Degree of CIBER BAFO Num Category Requirement Text Fit Development Module response Response p Hours F7-10- 10 - Expend Grant System provides the ability to route grant MI MI 20 Grants, 03-00-00 Funds expenditures according to different workflow Project rules than those that affect an operating budget Costing, (as defined by either the fund or grant codes). Purchasing, General Ledger 4 e Phase 2A Degree of Fit Impacted Y F7-10- 10 - Expend Grant System provides the ability to track retainage SF SF Purchasing Y 04-00-00 Funds withheld on contracts by grant. F7-11- 11 -Pass Through System provides the ability to uniquely identify Y 01-00-00 Grant Funds each sub -recipient for grants and all grant financial activity related to sub -recipients, including but not limited to the following: F7-11- 11 - Pass Through Ability to record planned payments to sub- SF SF Purchasing, Y 01-01-00 Grant Funds recipients Payables F7-11- 11 - Pass Through Ability to capture the effective beginning SF SF i Grants, Y 01-06-00 Grant Funds and end date of the sub recipient's participation Purchasing on a grant. j F7-12- 12 - Bill Grantors System provides the ability to generate SF SF Purchasing, Y 21-00-00 invoices/payments based on defined Payables milestones. u F8-03- 03 - Define System provides a central record of Y 12-00- Customers and customer information, including but not 00 Items limited to the following: F8-03- 03 - Define Corresponding Vendor Number (for SF SF Billing, Y 12-14- Customers and entities that are both vendors and Receivables 00 Items customers of the city) F8-05- 05 - Cash System provides the ability to either apply SF SF Receivables, Y 02-00- Receipts - Billed an overpayment to a different invoice or to Payables 00 create a refund transaction. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 409 of 418 Reqt Degree of BAFO CIBER Phase 2A Degree of Num Category Requirement Text Fit Development Module response Fit Response Hours Impacted 1__ T P-irchasing I-_Regisl;tion � Sohbitati!ons Ih At �t P1-00- 00 - General System provides the ability to maintain and 29-00-00 Requirements report a detailed history of all purchasing activity including, but not limited to: PI-00- 00 - General Any Element of the Financial Data Purchasing 29-14-00 Requirements Classification Structure SF SF Y P i-01- - Requlsitions 1 System provides the ability fox cross- eProcurement 101 19-00-00 Requests referencing of purchase requisitions to the Purchasing, corresponding invitation for bid, purchase Strategic order, contract, receiving report, order number, Sourcing, invoice and payment. SF SF Payables Y P1-03- 03 - Commodity Sys#ern provides the ability fnr commodity line 01-00-00 Lines items to contain (including but not limited to) the following data elements: P1-03- 03 - Commodity Fixed asset Indicator knew, replacement, eProcurement 01-27-00 Lines or enhancement; if replacement or Purchasing, enhancement, need existing tag number) Asset SF SF Managerlient ; Y P1-04- 04 - Requisition System provides tree ability for purchase eProcurement 03-00-00 Accounting requisition to allow the entry of multiple Purchasing account codes for allocation of expenditure. SF SF Y P1-04- 04 - Requisition System provide the ability to optionally eProcurement 09-00-00 Accounting liquidate remaining/outstanding pre- Purchasing encumbrances when creating a purchase order from a requisition for less than the full amount requested, SF SF Y P1-04 04 - Requisition System provides the ability to adjust or cancel eProcurement 13-00-00 Accounting a requisition and generate appropriate Purchasing, accounting entries. General SF SF Y Purchasigg 11- Create Iaurchase Iiree'r i — I Contract _ City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 410of418 I I I I � i f M � I i ► r Reqt Num Category Requirement Text P2-00- 00 - General System provides the ability to capture a fixed 09-00-00 Requirements asset indicator (determine whether commodity is an asset based on dollar amount and expenditure object code). P2-08- 08 - Purchase System provides the ability to reopen a 04-00-00 Order Actg purchase order if the purchase order was closed in error (with appropriate security procedures). P2-08- 08 - Purchase System provides the ability to carryover open 09-00-00 Order Actg purchase orders to the following fiscal year for operating funds that use annual budgetary control. P2-09- 09 - Goods and System provides the ability to flag items 09-00-00 Services Rcpt received as "placed in service" as a fixed asset upon receipt of good. P2-10- 10 - Vendor System provides the ability to back out invoices 13-00-00 Invoice entered in error, with appropriate accounting entries. P3-02- 02 - Vendor System provides the ability for the vendor file 01-00-00 Master Data to include the following information, including but not limited to (access to information is based on security): P3-02- 02 - Vendor Vendor number 01-01-00 Master Data P3-02- 02 - Vendor Prior vendor name(s) and number (s) 01-02-00 Master Data P3-02- 02 - Vendor Vendor name 01-03-00 Master Data P3-02- 02 - Vendor Vendor status (active, inactive, on hold, 01-04-00 Master Data ineligible, etc.) City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 411 of 418 Degree of CIBER BAFO Fit Development response Response Hours MI MI 40 SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF Module Purchasing, Asset Management Purchasing Purchasing, General Ledger Purchasing, Asset Management Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Phase 2A Degree of Fit Impacted Y In kQ la V Y Y Y Y Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted P3-02- 02 - Vendor DBA Name SF SF Purchasing, Y 01-05-00 Master Data Payables P3-02- 02 - Vendor Prior DBA Name SF SF Purchasing, Y 01-06-00 Master Data Payables P3-02- 02 - Vendor Registration valid date on MI MI 20 Purchasing, Y 01-07-00 Master Data Payables P3-02- 02 - Vendor Registration valid date off MI MI 20 Purchasing, Y 01-08-00 Master Data Payables P3-02- 02 - Vendor Registration reinstatement date MI MI 20 Purchasing, Y 01-09-00 Master Data Payables P3-02- 02 - Vendor Federal tax ID number/Social Security SF SF Purchasing, Y 01-10-00 Master Data Number/ITIN Payables P3-02- 02 - Vendor Type of Number (EIN, SS#, ITIN) SF SF Purchasing, Y 01-11-00 Master Data Payables P3-02- 02 - Vendor Multiple Vendor contact information SF SF Purchasing, Y 01-12-00 Master Data Payables P3-02- 02 - Vendor Contact name SF SF Purchasing, Y 01-12-01 Master Data Payables P3-02- 02 - Vendor Contact title SF SF Purchasing, Y 01-12-02 Master Data Payables P3-02- 02 - Vendor Contact designation (accounting, SF SF Purchasing, Y 01-12-03 Master Data sales, etc) Payables P3-02- 02 - Vendor Contact email address SF SF Purchasing, Y 01-12-04 Master Data Payables P3-02- 02 - Vendor Multiple phone numbers (voice, fax, SF SF Purchasing, Y 01-12-05 Master Data mobile, etc.) Payables P3-02- 02 - Vendor Comment SF SF Purchasing, Y 01-12-07 Master Data Payables P3-02- 02 - Vendor Address type (s) (ordering, remittance, SF SF Purchasing, Y 01-13-00 Master Data 1099 etc.) Payables City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 412 of 418 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 r i Reqt Num Category Requirement Text P3-02- 02 - Vendor Multiple physical addresses 01-14-00 Master Data P3-02- 02 - Vendor Multiple mailing addresses (handles PO 01-15-00 Master Data and foreign addresses) P3-02- 02 - Vendor Address specific fields: 01-16-00 Master Data P3-02- 02 - Vendor Address 1 01-16-01 Master Data P3-02- 02 - Vendor Address 2 01-16-02 Master Data P3-02- 02 - Vendor Address 3 01-16-03 Master Data P3-02- 02 - Vendor Address 4 01-16-04 Master Data P3-02- 02 - Vendor City 01-16-05 Master Data P3-02- 02 - Vendor State 01-16-06 Master Data P3-02- 02 - Vendor Country 01-16-07 Master Data P3-02- 02 - Vendor Postal Code 01-16-08 Master Data P3-02- 02 - Vendor State where vendor headquarters located 01-17-00 Master Data P3-02- 02 - Vendor Website address 01-18-00 Master Data P3-02- 02 - Vendor Bank Transit Code (ABA/Routing number) 01-19-00 Master Data P3-02- 02 - Vendor Bank Account Number 01-20-00 Master Data City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 413 of 418 Degree of CIBER Fit Response response SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF BAFO Development Hours Module Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Phase 2A Degree of Fit Impacted Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted P3-02- 02 - Vendor Bank Name SF SF Purchasing, Y 01-21-00 Master Data Payables P3-02- 02 - Vendor Default (preferred) payment terms SF SF Purchasing, Y 01-22-00 Master Data (restricted to a city approved list) Payables P3-02- 02 - Vendor Multiple Methods of Payment (check, MI MI 20 Purchasing, Y 01-23-00 Master Data ACH, P-Card, etc.) Payables P3-02- 02 - Vendor Default (preferred) method of payment SF SF Purchasing, Y 01-24-00 Master Data Payables P3-02- 02 - Vendor Hold Reason and Hold Source MI MI 20 Purchasing, Y 01-25-00 Master Data (department level) Payables P3-02- 02 - Vendor Business Description SF SF Purchasing, Y 01-26-00 Master Data Payables P3-02- 02 - Vendor Ownership Type/Business SF SF Purchasing, Y 01-27-00 Master Data Structure/Governmental Organization (e.g., S- Payables corp, C-corp, federal department) P3-02- 02 - Vendor Small/Minority/Other Status and SF SF Purchasing, Y 01-28-00 Master Data Certification Types (MBE, WBE, DBE, Veteran, Payables etc.) P3-02- 02 - Vendor Small and Minority-owned/Other Targeted SF SF Purchasing, Y 01-29-00 Master Data Businesses Certification Number (assigned Payables subsequent to registration) P3-02- 02 - Vendor 1099 Reporting Flag SF SF Purchasing, Y 01-30-00 Master Data Payables P3-02- 02 - Vendor 1099 Reporting Vendor Name SF SF Purchasing, Y 01-31-00 Master Data Payables P3-02- 02 - Vendor Vendor backup tax withholding status SF SF Purchasing, Y 01-32-00 Master Data Payables P3-02- 02 - Vendor Foreign Corporation Information and SF SF Purchasing, Y 01-33-00 Master Data numbers Payables P3-02- 02 - Vendor Geographic Designation (City, State SF SF Purchasing, Y 01-34-00 Master Data Highway District, other) Payables City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 414 of 418 1 1 1 1 T s Reqt Num Category Requirement Text P3-02- 02 - Vendor User -defined vendor type fields (at least 2) 01-35-00 Master Data - for future reporting needs P3-02- 02 - Vendor W9 received (yes/no) 01-36-00 Master Data P3-02- 02 - Vendor Date W9 received 01-37-00 Master Data P3-02- 02 - Vendor One -Time Vendor Flag (used to expire a 01-38-00 Master Data vendor record after a user defined number of days) P3-02- 02 - Vendor Dummy Vendor Flag (used to require 01-39-00 Master Data payment information at the time a payment is requested). P3-03- 03 - Vendor System provides the ability to detect duplicate 01-00-00 Maintenance vendor information based on multiple criteria (e.g., FEIN, SSN, DUNS, address, etc.), with appropriate security. P3-03- 03 - Vendor Systems provides the ability for one Vendor file 02-00-00 Maintenance with different views of the data, with posting and inquiry capabilities controlled by security: P3-03- 03 - Vendor Purchasing view 02-01-00 Maintenance P3-03- 03 - Vendor Accounts Payable view 02-02-00 Maintenance P3-03- 03 - Vendor End User 02-03-00 Maintenance P3-03- 03 - Vendor Vendor Self -Service View 02-04-00 Maintenance P3-03- 03 - Vendor System Administrator View 02-05-00 Maintenance City of Fort Worth / CIBER, Inc. Professional Services Agreement Page415 of418 Degree of CIBER BAFO Phase 2A Degree of Fit response Development Module Fit Response Hours Impacted SF SF Purchasing, Y Payables MI MI 20 Purchasing, Y Payables MI MI 20 Purchasing, Y Payables SF SF Purchasing, Y Payables SF SF Purchasing, Y Payables SF SF Purchasing, Y Payables Y SF SF Purchasing, Y Payables SF SF Purchasing, Y Payables SF SF Purchasing, Y Payables SF SF Purchasing, Y Payables, eSupplier Connection SF SF Purchasing, Y Payables Reqt Num Category Requirement Text P3-03- 03 - Vendor MWBE View 02-06-00 Maintenance P3-03- 03 - Vendor System provides the ability to permit multiple 03-00-00 Maintenance addresses to be assigned to a specific address type for a specific vendor (e.g., multiple ordering addresses, invoice addresses, etc.). P3-03- 03 - Vendor System provides the ability to search for a 04-00-00 Maintenance vendor using multiple search criteria such as commodity code, commodity code number or description, Small/Minority/Other Targeted Business status, vendor name, vendor number, and DBA name, etc. P3-03- 03 - Vendor System provides the ability to track vendor 05-00-00 Maintenance history, to include date added or inactivated and reason. P3-03- 03 - Vendor System provides the ability to deactivate 06-00-00 Maintenance vendor from vendor listing by date with reason. Historical data should be retained. P3-03- 03 - Vendor System provides the ability for vendor numbers 07-00-00 Maintenance (numeric and alphanumeric) to be system generated or assigned manually based on system administrator -defined parameters. P3-03- 03 - Vendor System provides the ability for users with 08-00-00 Maintenance authorized security to have the ability to add, change or deactivate vendor master file records. P3-03- 03 - Vendor System provides the ability to maintain an on- 09-00-00 Maintenance line audit trail of changes to the vendor master file including date, time, and user, old and new values. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 416 of 418 I I i Degree of CIBER BAFO Fit Development Response response Hours MI MI 20 MA MA 40 SF SF MI MI MI MI SF SF SF SF MI MI 20 20 Module Purchasing, Payables Purchasing, Payables Phase 2A Degree of Fit Impacted Y Y Purchasing, Y Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables 20 Purchasing, Payables Y Y 94 Y IQ r - a Reqt Category Requirement Text Num P3-03- 03 - Vendor System provides the ability to maintain vendor 10-00-00 Maintenance open procurements when vendor name is changed - (updates PO, but maintains vendor history) P3-03- 03 - Vendor System provides automated notification to 11-00-00 Maintenance specified users (e.g, originator, buyers and vendors) of vendor name changes. P3-03- 03 - Vendor System provides the ability to maintain an 12-00-00 Maintenance online history of vendor transactions by month, quarter, fiscal and calendar year, inception to date, contract, bid number, department, etc. P3-03- 03 - Vendor System supports the use of "one-time" vendors 13-00-00 Maintenance that automatically expire after a user specified length of time. P3-03- 03 - Vendor System can be configured to support capture 14-00-00 Maintenance of the following fields when using a dummy vendor to generate P3-03- 03 - Vendor Dummy vendor number 14-01-00 Maintenance P3-03- 03 - Vendor Name 14-02-00 Maintenance P3-03- 03 - Vendor Address 1 14-03-00 Maintenance P3-03- 03 - Vendor Address 2 14-04-00 Maintenance P3-03- 03 - Vendor Address 3 14-05-00 Maintenance P3-03- 03 - Vendor Address 4 14-06-00 Maintenance P3-03- 03 - Vendor City 14-07-00 Maintenance City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 417 of 418 Degree of CIBER BAFO Fit Development Response response Hours SF SF MI MI SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF SF Phase 2A Module Degree of Fit Impacted Purchasing, Y Payables 20 Purchasing, Y Payables Purchasing, Y Payables Purchasing, Y Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables Purchasing, Payables in Y Y Y Y Y Y Y Degree of BAFO Phase 2A Reqt Category Requirement Text Fit CIBER Development Module Degree of Num Response response Hours Fit Impacted P3-03- 03 - Vendor State SF SF Purchasing, Y 14-08-00 Maintenance Payables P3-03- 03 - Vendor Postal Code SF SF Purchasing, Y 14-09-00 Maintenance Payables P3-07- 13 - P-Card System provides the ability to generate SF SF Purchasing, Y 13-00-00 accounting documents, including the electronic Payables funds transfer to pay the bank and the distribution to charge the account assignment. P3-07- 13 - P-Card SF SF Purchasing, Y 16-00-00 System provides the ability to capture P-card Payables, transactions in the system to record General expenditures against budget. Ledker IM-01-01- 01 - Inventory System provides the ability to support General SF SF Inventory Y 00-00 Accounting Ledger accounting for inventory by "purchase" method (expensed when purchased and operating budget reduced when paid) as assigned by individual inventory location. IM-01-02- 01 - Inventory System provides the ability to support General SF SF Inventory Y 00-00 Accounting Ledger accounting for inventory by "consumption" method (unit cost expensed and operating budget reduced at the time of issue ) as assigned by individual inventory location. City of Fort Worth / CIBER, Inc. Professional Services Agreement Page 418 of 418 in City of Fort Worth, Texas Mayor and Council Communication .Y IW. II, iIINIUdi, 1441. YI III.WII :. I:.,:i a.YY al W: .:. :II .:II:.. —I :.. .1.:14WI IeW ie.I:IIWIliielY.I.6YIlllsl,.tlel,.elol:l, Ix.YWbW COUNCIL ACTION. Approved on 611212012 DATE: Tuesday, June 12, 2012 REFERENCE NO.: C-25669 LOG NAME: 13CIBER ERP PHASE II IMPLEMENTATION SERVICES SUBJECT: Authorize Execution of a Contract with CIBER, Inc., to Provide Implementation Services, Change Management and End -User Training for Enterprise Resource Planning Phase II in an Amount Up to $16,677,689.00 with an Option for the City to Obtain Services for Implementation of Procurement in an Amount Up to $3,348,818.00 for a Total Project Cost in an Amount Up to $20,026,507.00 (ALL COUNCIL DISTRICTS) RECOMMENDATION: It is recommended that the City Council authorize execution of a contract with CIBER, Inc., to provide implementation services, change management and end -user training for Enterprise Resource Planning Phase II in an amount up to $16,677,689.00 with an option for the City to obtain services for implementation of the Procurement function in an amount up to $3,348,818.00, for a total project cost in an amount up to $20,026,507.00. DISCUSSION: The City is currently preparing for Phase II of the Enterprise Resource Planning (ERP) Project to replace the City's financial and budget systems. Phase II has been split into three sub -phases: I will focus on replacing core financials; IIB efforts include implementation services for the budget planning software; and, IIC, which is an optional phase, would replace the Capital Project Management System and procurement functions. The recommended vendor will team up with the ERP Staff and provide implementation consulting, technical support, end -user training and change management. On February 9, 2010, (M&C C-24088) the City Council authorized the purchase of Oracle PeopleSoft Software and Oracle Hyperion Budget Planning Software for Phase II. After an extensive effort by ERP Staff and the subject matter experts, who helped identify and rate thousands of requirements, a Request for. Proposals (RFP) for implementation services was issued in April 2010. In June 2010, the City received four responses to the RFP. The responding firms were: . CIBER, Inc. . CherryRoad Technologies, Inc. . Maximus Consulting Services, Inc. . Zanett Commercial Solutions An evaluation committee comprised of employees from the Financial Management Services, Water, IT Solutions, Transportation and Public Works departments and City Manager's Office evaluated each responder's proposal on a pre -determined matrix combination of qualitative and quantitative measures. The evaluation criteria were experience and capabilities, methodological approach to implementation, methodological approach to change management and training, qualifications, cost and financial stability. The three highest ranked firms were invited to make a presentation and be interviewed, after which Logname: 13CIBER ERP PHASE II IMPLEMENTATION SERVICES Page 1 of 3 additional points were awarded. Based on the total point distribution of the pre -determined measures and presentation, CIBER, Inc., received the highest score. Requested services include: • Implementation services, including all the services necessary to install, configure, test and deploy the PeopleSoft and Hyperion products; • Organizational change management services necessary to assist the City in successfully transitioning from its current systems and business processes to a PeopleSoft system with improved business processes; • Training services of the new finance, purchasing/e-procurement, and budget business processes for the City's end -users; and • Enhancement of existing internal controls. The actual contract amount for implementation is $13,898,074.00 plus an option for purchasing implementation for $2,790,682.00, for a total contract amount of $16,688,756.00. Additionally, $3,337,751.00 has been reserved in contingency for a total authorization of $20,026,507.00. It is anticipated that after an initial planning period in the fall, the Phase IIA (core financials) implementation efforts will begin in October 2012, with an anticipated go -live date in October 2014. Phase 116 (budget system) will begin in April 2014 with an anticipated go -live in March 2015. Phase IIC (capital projects and procurement), which is optional, would begin in October 2014 with an anticipated go -live date in December 2015. Phase IIC will only be considered as a viable option after an in-depth analysis considering all aspects of the potential replacements and overall change impact on the organization. BID ADVERTISEMENT — This Request for Proposal (RFP) was advertised in the Fort Worth Star- Telearam on April 28, 2010, May 5, 2010, May 12, 2010, and May 19, 2010. The Purchasing Division solicited 126 vendors from the purchasing system database who self -identified as providing technology services. M/WBE — CIBER, Inc., is in compliance with the City's M/WBE Ordinance by committing to 26 percent M/WBE participation level. The City's goal for this contract is 15 percent. FISCAL INFORMATION / CERTIFICATION: The Financial Management Services Director certifies that funds are available in the current capital budgets, as appropriated, of the ERP Capital Project Fund and Specially Funded Capital Projects Fund. FUND CENTERS: TO Fund/Account/Centers CERTIFICATIONS: Submitted for Citv Manager's Office bv: Oriainatinq Department Head: Additional Information Contact: ATTACHMENTS 1. 13ERP2TRANSFERS.pdf (CFW Intemal) 2. 20120524 CIBER MWBE.pdf (CFW Internal) FROM Fund/Account/Centers C291 539120 1310301361XX C296 539120 1310301361XX Susan Alanis (8180) Lena Ellis (8517) Greg Jordan (8843) $2.732.486.00 $17.294.021.00 Logname: 13CIBER ERP PHASE II IMPLEMENTATION SERVICES Page 2 of 3 r .r 3. C296 01361 available funds.odf (CFW Internal) a* ow aft w. w *R we mw w so rw w m Logname: 13CIBER ERP PHASE II IMPLEMENTATION SERVICES Page 3 of 3