DRAFT_PWS_for_RMT.pdf

PERFORMANCE WORK STATEMENT (PWS)

The Army Resource Management Tool (RMT)

Part 1 General Information

1. GENERAL: This is a non-personal services contract to provide technical, functional and managerial support services to support and maintain the Army Resource Management Tool (RMT) operations. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform functional assistance, technical assistance and programming support as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: RMT assists the Assistant Secretary of the Army for Financial Management & Comptroller (ASA (FM&C)) Army Resource Management operations to efficiently operate within the Army Planning, Programming, Budgeting, and Execution (PPBE) systems in order to execute funds control and budget execution processes in a real-time environment. Contractor Business Analysts (BA) and support efforts are required to maintain the RMT application at all operating sites throughout the Army, provide training and guidance as necessary to RMT users, and identify problems in the RMT program. Contractor programmers maintain the integrity of the SQL databases and fix anomalies in the web based code.

RMT is in a brownout phase; however, RMT operations are required until the liquidation of accounting transactions can occur for existing and future transactions associated with the nine Army commands that will not be deployed on GFEBS until the 2021/2022 timeframe. Per the Army policy there will not be a data migration for open transactions to the GFEBS accounting system, due to audit concerns.

Liquidation will occur as aggressively as possible, but is not expected prior to the last option year of the contract. The base functionality of RMT to include architecture support, surge programming requirements for malfunctions & interface re-design as well as minimal help desk support for a global operating environment are reflected in the PWS.

1.3 Objectives: The Resource Management Tool will continue in brownout posture as the Army fully transitions to GFEBS.

1.4 Scope: The RMT Program Management Office (PMO) requires contractor advisory and assistance support services to support RMT field operations, conduct data collection and analysis, prepare technical documentation of workflow processes, documentation of existing tools and interfaces between tools, assist and advise the Project Management Office and RMT commands, and suggest improvements for RMT tools that support effective business operations. This assistance includes maintenance of SQL databases and application code currently processed at the Army Analysis Group in Fairfield, California (AAG). The contractor shall keep RMT operational until such time as RMT is fully retired. This includes daily balancing for commands, assisting with user questions, maintaining the data integrity, and response to changes in security and Army compliance requirements.

DRAFT

1.5 Period of Performance: The period of performance shall be for one (1) Base Year of 12 months and One (1) Option year of 12 months. The Period of Performance reads as follows:

Base Year:

Option Year One:

1.6 General Information

1.6.1 Quality Control: The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control plan (QCP) is the means by which he assures himself that his work complies with the requirement of the contract. The Government shall incorporate the QCP in the contract that will result from this solicitation. The QCP will no longer be considered proprietary and will be considered releasable under the Freedom of Information Act (FOIA). The QCP is to be delivered within 30 days after contract award or with the contractors proposal if it is an evaluation factor, three copies of a comprehensive written QCP shall be submitted to the KO and COR within 5 working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to his QC system.

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3 Recognized Holidays: The following are the government holidays for which contractor will not be responsible for supporting RMT

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.4 Hours of Operation: The contractor is responsible for conducting business 24-hours-per-day, 5-days-per- week, Monday thru Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5 Place of Performance: The work to be performed under this contract will be performed primarily at contractor facilities, the Pentagon and Crystal City Government offices, and trips to RMT user sites, both CONUS and OCONUS. OCONUS support may require contractor personnel to travel to hazardous locations and remain on site for extended periods of time.

1.6.6 Type of Contract: N/A

1.6.7 Security Requirements: Contractor personnel performing work under this contract must have a SECRET clearance at time of proposal submission. The contractor is responsible for safeguarding information of a confidential or sensitive nature. Failure to safeguard any classified/privileged information which may involve the contractor or the contractor’s personnel or to which they may have access may subject the contractor and/or the contractor’s employees to criminal liability under Title 18, section 793 and 7908 of the United States Code. Provisions of the Privacy Act apply to all records and reports maintained by the contractor. All programs and materials developed at government expense during the course of this contract are the property of the government. Contractor personnel shall be required to obtain and maintain security badges and adhere to the installation security requirements.

The performance of this requirement will require the contractor access to classified information. FAR clause 52-204-2, Security Requirements, as required by either FAR Subpart 4.404 (a) and is accompanied by a Contract Security Specification, DD Form 254, in accordance with DoD Directive 5220.22-M, Department of Defense Industrial Security Manual for Safeguarding Classified Information, and any revisions, thereto, as well as Industrial Security Regulation DoD 5220.22-R. Failure to safeguard and classified/privileged information which may involve the contractor or/or the contractor's personnel or to which they may have access may subject the contractor and/or contractor's personnel to criminal liability under Title 18, section 793 and 7908 of the United States Code. Provisions of the Privacy Act apply to all records and reports maintained by the contractor. The contractor employees will require Secret Clearances at the time of award.

Common Access Card. SecArmy memorandum dated 28 January 2006 on Contractor Verification System (CVS) Implementation provides guidance and instructions for the implementation of the CVS Army-wide. IAW that guidance, the authorizing official (Contracting Officer Representative (COR)), Contracting Officer Technical Representative (COTR), Contracting Officer, or other approving officials), the contractor's sponsor, approves issuance of the CAC though the automated CVS system. The Functional Representative identified in this task order is the designated Trusted Agent (TA). Further delegation of that authority is determined at the installation level. The contractor's CVS applications under this task order should clearly cite the contract and task order numbers identified on the DD Form 1155 for this task order.

Antiterrorism (AT) Level I Training. This provision/contract text is for contractor employees with an area of performance within an Army controlled installation, facility or area. All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 21 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 10 calendar days calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://atlevel1.dtic.mil/at.

AT Awareness Training for Contractor Personnel Traveling Overseas. This standard language text required US based contractor employees and associated sub-contractor employees to make available and to receive government provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13. Specific AOR training content is directed by the combatant commander with the unit ATO being the local point of contact.

Access and General Protection/Security Policy and Procedures. This standard language text is for contractor employees with an area of performance within an Army controlled installation, facility or area.

Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

iWATCH Training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area. The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 30 calendar days after contract award.

Contractor Employees Who Require Access to Government Information Systems (IS). All contractor employees with access to a government info system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter.

For Contracts that Require OPSEC Training. Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty. All contractor employees must complete annual OPSEC awareness training.

1.6.7.1 Physical Security: The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.6.7.2 Key Control: The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

1.6.8 Special Qualifications: Business Analysts/Subject Matter Experts must have at least 15 years of Army finance experience in funds control and budget execution, to include systems such as PBAS, ODS, STANFINS and dbCAS; and programmers must be proficient in Microsoft ASP, ASP.Net, and SQL server 2008. See Technical Exhibit 3 for identification of key persons.

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance:

maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.11 Program Manager: The Contractor shall provide a program manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Contractor when the manager is absent shall be designated in writing to the Contracting Officer. The program manager or alternate shall have full authority to act for the Contractor on all technical matters relating to daily operation of this contract.

1.6.12 Key Personnel: The following personnel are considered key personnel by the Government.

Program Manager Education: B.S. Business or Economics Qualifications: Must have at least 5 years’ experience in managing a complex multidisciplinary team.

Experience should involve all facets of technical effort. At least 3 years of direct supervision of technical personnel involved in life cycle management support of complex systems. Must be capable of leading projects that involve the successful management of teams composed of financial analysts and computer programming professionals who have been involved in analyzing, training, testing, documenting, and maintaining a complex system. Performs overall management of contractor support operations with groups of personnel at multiple locations. Organizes, directs, and coordinates planning and production of all contract support activities. Demonstrates written and oral communication skills.

Technical Support Manager Education: B.S. Business or Economics Qualifications: At least 15 years’ experience in technical work in the major area of complex integrated database and web based systems. Duties include supporting day to day management of the functional and technical operation of a complex data processing system. Must be able to translate user functional requirements into technical terms for direction to programming staff. Must be able to translate technical test plans into tasks that can be performed by functional Subject Matter Expert (SME) personnel. Must have an in-depth knowledge of Army financial systems and be able to analyze customer issues and assign corrective actions to either operational, functional or technical staff for action. Must have 4 or more years of experience programming in the current languages used by the programming team. Must be able to determine if proposed technical solutions are appropriate for the task at hand and within the capabilities of the technology employed.

Business Analyst/Budget SME Education: B.S or B.A. degree Business or Economics Qualifications: Must have at least 15 years of Army finance experience and an in-depth knowledge of Army financial systems such as Program Budget Accounting System (PBAS), Other Direct Costs (ODS), Standard Army Finance System (STANFINS) and Database Commitment and Accounting System

(dbCAS). Must understand the interrelationships of these systems and the constraints they place on the overall system. The SME must know how Army funds flow from Congress to the end users and the rules that govern the distribution and execution of these funds so that the proper controls can be placed on the system to ensure that funds are managed properly. Must be able to quickly analyze user issues and determine if the problem can be solved within the existing capabilities of the current system or if the problem must be referred to the technical or operational staff for corrective action. Must be able to perform ODS queries and other means to independently verify information.

Senior Programmer Education: B.S or B.A. degree Business or Economics Qualifications: At least 10 years’ experience in technical work in the major area of full life-cycle systems. Must have an in-depth knowledge of Army financial systems and how they relate. Must be able to use this knowledge to design systems that control the flow of data through the financial life-cycle.

Must be able to translate user requirements into technical instructions that the programmers can work from. Must be able to analyze user issues and determine where in the process the problem is most likely to exist. Using that knowledge, craft technical instructions to the programmers to shorten the resolution time. Provide overall guidance and prioritization of resources to meet workload.

Programmer Education: B.S or B.A. degree Business or Economics Qualifications: At least 4 years of programming experience with Microsoft (MS) products to include MS Visual Studio, MS SQL Server 2008, MS ASP.NET, HTML, JavaScript, and MS SQL Server Integration Services (SSIS). Must also be proficient in reading and writing MS SQL and be able to develop complex Stored Procedures, Views and SSIS packages. Should have a working knowledge of the Army budget process and understand how to process data and maintain data integrity. Must be able to independently read existing code and determine how it operates and analyze how the code and the issue at hand relate.

Must understand how to take flat file data and translate it into Structured Query Language (SQL) data for rendering on web pages.

1.6.12 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel will be required to obtain and wear badges in the performance of this service when required by their duty station.

1.6.13 Contractor Travel: The government anticipates that travel will be required to perform this mission;

however, that travel is not fully defined. For proposal purposes the estimated cost of travel is $3,000.

The contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR.

1.6.14 Other Direct Costs: There will be other direct costs for maintaining the helpdesk toll free number, printing costs for training materials to assist local commanders, and other minor direct costs, not to exceed (NTE) $2,000.

1.6.15 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.16 Surge Labor: Labor associated with programming requirements for catastrophic systemic failure or operational interface redesign requirements related to partner enhancements. This CLIN will be funded as required.

1.6.17 Phase In /Phase Out Period: NA

PART 2

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

2. GOVERNMENT FURNISHED ITEMS AND SERVICES:

2.1. Services: NA

2.2 Facilities: The Government will provided desks, chairs, office equipment and computers for contractors working at government sites.

2.3 Utilities: All utilities in the facilities will be available for the contractor’s use in performance of their duties. The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities.

2.4 Equipment: The Government will provide computers, scanners fax machines, and printer for contractor personnel working on government sites.

2.5 Materials: NA.

PART 3

CONTRACTOR FURNISHED ITEMS AND SERVICES

3. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

3.1 General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

3.2 Secret Facility Clearance: The contractor shall possess and maintain a SECRET facility clearance from the Defense Security Service. The Contractor’s employees, performing work in support of this contract shall have been granted a SECRET security clearance from the Defense Industrial Security Clearance Office. The DD 254 is provided as Attachment 1.

3.3 Materials: The Contractor shall furnish all necessary hardware and software as required to perform the tasks under this PWS.

3.4 Equipment: The Contractor shall furnish all necessary hardware and software as required to perform the tasks under this PWS.

PART 4

SPECIFIC TASKS

4. SPECIFIC TASKS:

4.1. Basic Services. The contractor shall provide services for SME and programming support for the

Resource Management Tool. RMT will setup a training site using simulated data. Since the OA and APC’s do not currently exist, RMT must use an existing RMT database that most resembles HRC data and modify it for use as a training site for the new users. HRC will have approximately 35 users and they will need to get access with AAG accounts and access to the training environment.

4.2. Help Desk Ticket Management – Review help desk tracker on the Army Analysis Group, Fairfield, CA website. Assist in problem definition, prioritization, and assignment of tickets. Assist in problem resolution.

4.2.1 Issue Analysis – Provide analysis of data inconsistencies to determine the likely cause and provide recommendations for fixing the immediate problem; assist in problem resolution. This requires extensive knowledge of Army financial systems to include PBAS, STANFINS, and ODS.

4.2.2 Reconciliation –Review daily status reports that detail the status of funding and execution at commands employing RMT, with attention to cause of discrepancies that indicate an out-of-balance condition annotated on reports. RMT must maintain a balance between the 2 controlling systems (PBAS and STANFINS), as well as, with RMT. The Business Analysts will be responsible for determining the correct balance amount and finding the cause of the out-of-balance condition and make a recommendation as to the correct course of action to bring the 3 systems into balance.

4.2.3 Database Management – Provide data scripts to correct inconsistencies within the various command databases in order to maintain data integrity and make sure that RMT is consistent with the data in PBAS and STANFINS. RMT will stand-up a new command, HRC, which requires the establishment of a website running a new version of RMT and the creation and loading of a Microsoft SQL database to house the data. This setup involves taking a base schema and then populating the tables with standard data, as well as, data that is specific to the new command, HRC. RMT will create and populate relevant tables with HRC specific APC’s and ASN’s before the start of FY18. HRC will be copying its current OA22 APC’s and changing the OA to OA92. These APC’s will require a file to drop the OA22 APC’s followed by a file that adds them back with the new OA and other changed elements. They will then be imported along with the APC’s from the other 29 commands in RMT.

4.2.4 Code Maintenance – Correct anomalies in the code that prevent RMT from operating properly.

Provide recommendations for solutions that would prevent the users from inducing data inconsistencies.

4.2.5 Microsoft Application Support – Provide application assistance for newly identified tools for use in data analysis, data management, audit ability, and data conversion.

4.2.6 Process Improvement – Automate the PDF FAD program. Currently, three times per day, PDF FADS are manually entered in Oracle. Create an automated process for the PDF program.

4.2.7 System Interface Agreements and System Access Forms – Maintain the RMT System Interface Agreements (SIA) with DFAS and maintain all DD Form 2875’s – System Authorization Access Requests (SAAR). Ensure all agreements and forms are retained and easily accessible for audit purposes.

4.2.8 Policy – Document and maintain the retention policy for data within RMT and IOL. Additionally, maintain the RMT System Security Plan – Tenant Application.

4.2.9 Fiscal Year-End Close Procedures – Support the fiscal year-end close-out of the MACOMs using RMT and IOL, which entails actively monitoring the applications to assure issues are resolved immediately, adding, changing, and removing cycles for the applications to match DFAS STANFIN cycles, and migrating the RMT application to the new FY at midnight of the current FY. Also, support the year-end APC Candidate process.

4.2.10 Monthly Status Reports – The COR and the Functional Representative. These reports are intended to identify “earned value” in the sense that they will document costs incurred, hours allotted/expended/remaining and task/schedule completion in a manner that promotes trend analysis and integrated management assessment of performance. These reports shall be consistent with the contractor’s approved and QA approach (with any/all lower level metrics) as identified in the approved QA deliverable (see section 5.2.6 below).

4.2.11 Quality Control Plan – The contractor shall develop a quality control plan to insure that the ongoing operation of RMT contractors serves the needs of the commands and identifies and resolves the issues in a timely manner. Plan will provide means for determining the contractors’ ability to respond to command issues and system issues. RMT will need to upload the HRC file daily. There will be additional work needed to setup the file processing tables that will import the numerous files from the external agencies that support the STANFINS process. See para. 1.6.1

4.3 CONTRACTOR MANPOWER REPORTING (CMR): The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report ALL Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor shall completely fill in all the information in the format using the following web address https://Contractormanpower.army.pentagon.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative (COTR) or also known as the Contracting Officer’s Representative (COR); (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data; (5) Estimated direct labor hours (including sub-Contractors); (6) Estimated direct labor dollars paid this reporting period (including sub-Contractors); (7) Total payments (including sub- Contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-Contractor if different); (9) Estimated data collection cost;

(10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information); (11) Locations where Contractor and sub-Contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of Contractor and sub-Contractor employees deployed in theater this reporting period (by country). As part of its submission, the Contractor shall provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period shall be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a Contractor’s system to the secure website without the need for separate data entries for each required data element at the website. The specific formats for the XML direct transfer may be downloaded from the website.

PART 5

APPLICABLE PUBLICATIONS

5. APPLICABLE PUBLICATIONS (CURRENT EDITIONS) NA

5.1. The Contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures. These include system processing procedures (STANFINS, PBAS, ODS, etc.), AR 25-1, DFAS Reg 37-1 and DFAS Reg 37-100-XX, as well as local command Standard Operating Procedures.

TECHNICAL EXHIBIT 1

Performance Requirements Summary The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective (The Service required) Standard

Performance Threshold (This is the maximum error rate. )

Method of Surveillance

PRS # 1.

Help Desk Ticket Management

PWS Para 4.2.

Tickets will be reviewed within 8 business hours of initiation.

90% on-time. Random sampling of the recorded responses in the helpdesk system.

PRS # 2

Issue Analysis

PWS Para 4.2.1.

Respond to user problems within 8 business hours.

No more than 5% deviation from the standard.

Random sampling of the recorded responses in the helpdesk system.

PRS # 3

Reconciliation

PWS Para 4.2.2.

Determine if command is in balance each working day. Initiate a helpdesk ticket with problem definition within one business day.

standard.

Review Daily Balancing report.

PRS # 4

Database Management

PWS Para 4.2.3.

Respond to critical tickets (those corrections that must be made to prevent significant adverse processing issues) with initial analysis within one business day.

Respond to high tickets (those corrections that must be made to prevent processing issues that require “work arounds” if the issue is not corrected)with initial analysis within three business days.

standard.

Random sampling of the recorded responses in the helpdesk system.

PRS # 5

Code Maintenance

PWS Para 4.2.4.

Respond to critical tickets (those corrections that must be made to prevent adverse processing issues) with initial analysis within one business day.

Respond to high tickets (those corrections that must be made to prevent significant processing issues that require “work arounds” if the issue is not corrected) with initial analysis within three business days.

standard.

Random sampling of the recorded responses in the helpdesk system.

PRS # 6

Microsoft Application Support

PWS Para 4.2.5

Respond to requests for assistance with initial analysis within one business day.

Provide the solution in the time proposed.

No more than 5% deviation from the standard.

Random sampling of the recorded responses in the helpdesk system.

PRS # 7

Process Improvement

PWS Para 4.2.6

Automate the PDF FAD program during the base year.

No more than 1 day late. 100% Inspection.

PRS # 8

System Interface Agreements and System Access Forms

PWS Para 4.2.7

Maintain all SIA and SAAR forms on the Army ‘H’ drive.

No more than 5% deviation from the standard.

100% Inspection.

PRS # 9

Policy

PWS Para 5.2.8

Maintain the RMT and IOL data retention policy and the RMT System Security Plan – Tenant Application policy.

No more than 5% deviation from the standard.

100% Inspection.

PRS # 10

Fiscal Year-End Close Procedures

PWS Para 4.2.9

Provide MACOMS using RMT and IOL with support for the fiscal year-end close-out. Issues must be addressed immediately.

Migrate the RMT application to the new FY at midnight of the current FY.

Support the year-end APC Candidate process.

No more than 5% deviation from the standard.

100% Inspection.

PRS # 11

Provide Monthly Status Reports

PWS Para 42.10

Delivered within 5 business days after the end of the month to include funding/expense report.

No more than 2 months where reports were delivered in excess of 5 days.

100% Inspection.

PRS # 12

Quality Control Plan

PWS Para 1.6.1 and 4.2.11

Initial Report delivered within 30 days of award and updates delivered within 5 working days.

No more than 1 late report.

100% Inspection.

TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

Deliverable Frequency # of

Copies Medium/Format Submit To

Helpdesk Tickets

PWS 4.2 to 4.2.4

Daily NA Entered in AAG’s ECM web based system.

COR

System Interface Agreements and System Access Forms

PWS 4.2.7

Ad Hoc 1 Electronic file stored on the shared-drive.

COR

Policy

PWS 4.2.8

On-going 1 Electronic file stored on the shared-drive.

COR

Monthly reports

PWS 4.2.10

At the end of each month after the award of the contract, a progress report discussing the progress made during that month. This report is due 5 days after the completion of the month.

1 Electronic file by e-mail as an MS Word attachment.

COR

Deliverable Frequency # of

Copies Medium/Format Submit To

Quality Control Plan

PWS 4.2.11

Within 30 days of contract award.

1 Electronic file by e-mail as an MS Excel attachment.

COR

TECHNICAL EXHIBIT 3

HISTORICAL WORKLOAD DATA

Below are the descriptions and estimated annual labor hours for the requirements of this PWS based on historical data and projected future requirements. These hours do not project actual requirements for the new contract, nor does it reflect hours required of subcontractors. The contractor is responsible for proposing the appropriate hours and labor mix to perform the requirements of this PWS. This data is provided for informational purposes only.

ITEM NAME ESTIMATED QUANTITY

1 Program Manager (key Person) Hours 480

2 Technical Support Manager (Key Person) Hours 1,920

3 Business Analyst/Budget SME (Key Person) Hours 9,600

4 Senior Programmer (Key Person) Hours 1,920 5 Programmer (Key Person) Hours 1,920 6 Admin Support Hours 1,320

7 ODC (Help Desk Phone Lines/Training Materials) Dollars $2,000 8 Travel Dollars $3,000

9 Surge Labor ( as needed) Dollars $50,000