Award Notice

Added: March 20, 2008 Modified: March 27, 2008Track Changes NAICS Code: 541512 This is just additional Technical Evaluation Information. There have been no revisions made to the RFP Technical Evaluation Criteria. The Techncial Evaluation Criteria will be evaluated against the following scale in accordance with the RFP. Rating Adjectival 1 Exceptional Description Exceeds all the minimum requirements of the criteria; has an above average probability of success; contains no significant or minor weaknesses. Few minor deficiencies that can be readily corrected. 2 Good Description Meets all the minimum requirements of the criteria; has an average probability of success; no significant weaknesses or deficiencies; and minor deficiencies/weaknesses can be readily corrected. 3 Marginal Description Fails to meet one or more of the minimum requirements of the criteria; low probability of success; major weaknesses and/or significant number of deficiencies exist. 4 Unacceptable Description Fails to meet any of the minimum requirements of the criteria; proposal needs major revisions; very low probability of success.

Added: March 20, 2008 Modified: March 27, 2008Track Changes NAICS Code: 541512 2nd Set of Questions and Responses: 1) How much of the business logic for OASIS is in Oracle stored procedures? A very minimal amount 2) What is the expected user base growth over time for the system? What is the usage frequency of the 500 users cited in the RFQ? Expected growth is expected as minimal, the usage is daily. 3) What kind of external systems does OASIS integrate with? Internal systems to EPA, typically Oracle and text uploads. 4) Does OASIS operate solely within the EPA, or does it have cross-agency functionality? Internal to EPA only. 5) How well documented is the existing Cold Fusion solution (e.g. are there documented unit and system functional tests)? Yes, there is system documentation in place. 6) The RFQ states "The contractor shall describe its technical approach in assisting EPA in a fully reengineered OASIS portal and applications in accordance with the seven tasks described in the Statement of Work (SOW). Specifically, the contractor shall articulate its plans for seamlessly implementing EPA's newly designed OASIS portal in a detailed report for the period ending the 15th and the end of each month." Does the Government wish for the response to the RFQ to discuss how it will get to the point of providing the report ending the 15th, or does the Government wish for the respondent to articulate its plans for seamlessly implementing EPA's newly designed OASIS portal in the response? Furthermore, to what does the 15th refer? The 15th of the month? The 15th day ARO? Something else? Government wish for the respondent to articulate its plans for seamlessly implementing EPA's newly designed OASIS portal in the response,The 15th of the month. 7) Can the Government provide existing documentation and/or screenshots of OASIS system? Yes, upon award. 8) Where can we find a list of approved EPA software products and a list of EPA established agency standards as referenced in Subtask 3? Pertinent software to this project is , Oracle 10g database, Coldfusion MX7/8 frontend software, as well as Flash, Flex and dream weaver. 9) Does the 15 page limit include cover sheet and table of contents? No 10) Is funding available for this effort? The Federal Government cannot pursue the procurement of items not earmarked within its approved budget.

Added: March 20, 2008 Modified: March 26, 2008Track Changes NAICS Code: 541512 Questions and Responses: 1) You will accept our sub-contractor past performance over the past three years to meet the past performance requirement? No. 2) Is there any incumbent contractor involved in the OASIS development effort. If so, could you identify them and give the contract details. There is no incumbent. 3) By EPA estimates the level of effort for this requirement is 6,240 labor hours for two 6-month periods. Do you mean 6,240 labor hours for each 6-month periods (a total of 12,480 labor hours) or 6,240 labor hours over the two six month periods (a total of 6,240 labor hours)? 6,240 labor hours for each 6-month period (a potential total of 12,480 labor hours). 4) Can you provide details of how you arrived at the 6,240 labor hours estimate including the labor categories you anticipate and the number of labor hours in each category? As stated the 6,240 is an estimate, no further information is available.

Added: March 20, 2008 NAICS Code: 541512 STATEMENT OF WORK - BUSINESS PROCESS AND APPLICATION REENGINEERING The Office of Administration has developed a WEB-based portal, Office of Administration Information System (OASIS), for all Specialized Amoderate@ applications with vital information which requires that data be carefully stored, but accessible. Moderate applications must be given Special Handling to minimize opportunity for of harm resulting from loss, misuse, unauthorized access or information modification. The intent is to reengineer business processes and implement these changes into the system for better flow of application use. DESCRIPTION: The Contractor shall provide business process reengineering and system development life cycle support for the Office of Administration Services Information System (OASIS). OASIS is a secure portal that provides EPA employees access to eighteen OARM/OA custom applications. The work required under this Task includes: analysis of the existing OASIS custom application and to document the As-Is state; status and workflows. Then make determination for the To-Be state; with GAP Analysis to identify alternatives for achieving the To-Be state; with design of the new applications. The Contractor shall develop new workflow processes for each OASIS application. The new workflow processes must provide process improvements and eliminate redundant steps. The period of performance shall be for six months from date of award. This requirement also has a 6-month option period. OASIS TECHNICAL OVERVIEW: OASIS is a custom in house written application, developed in ColdFusion MX8 as the front end and Oracle 10g database. The application is accessed by over 500 users on a daily basis. All code in this effort will be written by the EPA in house IT staff. OASIS currently has three environments, production, development and test. The servers in each environment are Dell Power Edge servers. Below is a list of subtasks and the work that is required for each. Subtask 1 - Analyze and Evaluate As-Is Business Processes for OASIS Applications The Contractor shall conduct an independent review and or audit of the business processes and applications that comprise OASIS. The goal of this review is to assess current business processes, workflow, and to document the As-Is state. The Contractor will interview OASIS users to assess and document current business processes and workflows. The goal of this review is to assemble all information necessary to document the As-Is state. Deliverable: Current State Assessment Report Subtask 2 - Document To-Be Environment and Alternatives The Contractor shall conduct interviews with existing users of the OASIS applications and OARM/OA management to identify expected (desired) business and operational goals. For new OASIS applications, the users will be interviewed and all requirements are gathered to ensure a detailed workflow process is mapped before software design shall start. The Contractor shall describe how the business processes can be improved and simplified, and how the users' roles can be managed to deliver the functionality required in a more streamlined manner. The Contractor shall identify how to better address the users' needs and how to simplify their processing activities. The Contractor shall recommend a data infrastructure that supports integrated, online information and services center, which serves as a single point of access to all of the OARM/OA activities within a Portal environment. The structure of this environment shall be expandable, and `capable of supporting the addition of future applications. The environment shall be consistent with the OARM/OA web, security and privacy policies. The Contractor shall provide a To-Be process model describing the above environment, and the reengineering and redesign requirements necessary to achieve it. For each application, the Contractor will develop a requirements specification that addresses functional, operational and system performance considerations. For the OASIS portal and each application, the Contractor will identify the operational rules that define system security requirements including access and roles, and how the business processes can be improved and simplified. In combination, the To-Be requirements for each application and the OASIS portal will comprise the To-Be state. Deliverable: Future State Summary Report Deliverable: Future State design with new requirements for workflows Subtask 3 - System Reengineering and Design Implementation Following approval from OARM/OA management, the Contractor shall perform system engineering and design activities to implement the To-Be environment. This will include definitions, integrated system design, database design and other design activities. This effort will also address system conversion activities. All system design must be done using EPA approved software products and all implementations must comply with established agency standards. The portal and supporting applications will be designed to achieve a common, standard "look and feel," with a central system of role based security that supports the users and the OARM/OA IT Team. The portal will be engineered to permit the IT Team to add new applications, and include features such as help desk tools, email communications and user-oriented Help systems. Administrative functionality should be designed to simplify system maintenance processes and to leverage and optimize existing resources. This includes providing users with tools to manage and process their data more efficiently. Deliverable: Functional OASIS Portal and Applications (Readiness Plan) Subtask 4 - Testing Activities The Contractor shall coordinate OASIS testing activities to validate system performance. This will include the development of scripts to support detail end-to-end testing. System Integration Testing will be conducted by the Contractor & EPA team. User Acceptance Testing will be coordinated by the contractor and executed by EPA personnel. The Contractor shall remediate any changes or updates identified during testing. Change Requests (CRs) will be generated during testing to identify system problems and enhancements. The Contractor shall manage the CR process and ensure that all required corrections or changes are implemented and re-tested. A test plan and acceptance criteria will be developed and delivered to the Contract Officer Representative (COR). Deliverables: OASIS Portal and Application Test And Acceptance Plan including Test Scripts Test Analysis Report Subtask5 - Training The Contractor shall develop specific training materials to support the implementation of the new portal and applications. The Contractor shall evaluate training alternatives including: computer-based training (CBT), online or bubble help, classroom training sessions, "webinar" delivery and other alternatives. The Contracting Officer's Representative (COR) will review and approve the training delivery strategy prior to action by the Contractor. Deliverable: Training Plan and Products Subtask 6 - OASIS Implementation Following successful Testing and Training, the Contractor shall coordinate implementation of the new OASIS portal and applications with the OARM/OA IT group. Coordination with this group is essential to ensure the timely retirement of existing systems, conversion of existing application data, and, the implementation of the new portal and applications. Deliverable: To-Be State For OASIS Applications and Implementation Plan Subtask 7 - Other Deliverables In addition to the Deliverables associated with each subtask above, the Contractor shall be required to provide the COR with a Status Report for the period ending the 15th and the end of each month. The Status Report will be due within 3 business days following these dates and will address progress since the previous report. These Status Report shall be delivered to the COR in writing unless other arrangements are made between the Contractor and the COR. Cost Reporting - to include staff hours and funds expended during the prior month-end and inception-to-date; Accomplishments during the period; Project Risks and Contingencies; and, Upcoming schedule - initiatives or delivery items. User Guides Help Features ACCEPTANCE CRITERIA Delivery and product acceptance will be performed by the COR and will be based on meeting the criteria established for each deliverable. SECURITY CONTROLS The Contractor will be required to complete National Agency Check and Inquiry (NACI) paperwork within 10 working days of receiving the signed Task Order. OASIS Customer Application description Summary: 1. The Change Request application is design for requesting the following information electronically. 1. New employee PC setup 2. LAN IDs 3. Lotus Notes ID 4. Printer setup (Local and or Network) 5. PC moves, adds, changes and deletes 2. The COOP Action Tracking Systems (CATS) is design to track COOP actions. The OARM COOP staff has access to this application to make updates and view actions that are assigned. Actions are tracked by Org, Assign Date, Requestor and Priority. 3. The Print Job Tracker is design for EPA Print shop to track bulk printing and invoicing. 4. The Mail Center Application provides a mean to track two types of mail. 1. Critical Mail Tracking 2. Integrated Mail Management Critical Mail Management The tracking of critical mail is of great important to EPA and EPA tracks these critical items based on the following requirements. 1. Carrier 2. Mail Delivered Log 3. Mail received daily log 4. Mail received by carrier 5. Mail assigned to an EPA Massager 6. Mail not signed for 7. Mail delivery details 8. Mail delivered to an assignee Integrated Mail Management The Integrated Mail Management module has several sub-modules for tracking EPA internal mail deliveries. The first module Data Management which supports: Group Changes, Employees,Headquarters, Nationwide,All locations,Individual that have left EPA (Separated), 5. The Administration module provides a means to update address, locations, carrier and information. 6. The Warehouse Management Modules is an online inventory tracking system design to track items that are stored at the warehouse 7. This module is used to track all help desk request for support calls. Calls are tracked by individual names, location, and problem type. 8. The COOP Contact List is an online tool for making updates to the actual COOP list. This information is converted into an ICON and placed on each COOP Staff members Blackberry. 9. The credential Badging System was design to be an online system for all ten regions and headquarters. The credential badging systems will help each regional security rep submit, track and received approved credentials from headquarters. The following features are available in the credential badge system. 1.The ability to capture a digital photo and upload the photo for a credential badge 2.The ability to capture a digital signature and upload the photo for a credential badge 3.The ability for each region to submit a request for a new credential electronically. 4.The ability for headquarters to process any region's credential electronically. 10. The Parking and Transit Subsidy System was developed to track EPA employees parking and transit. The transit module tracks Smart benefits, Metro checks, enrollments and disbursements. 11. The Driver Tracking Module was developed to track EPA vehicle mileage, gas and driver assignments. Each vehicle is tracked and driver is tracked based on pickup assignment and or vehicle check-out and usage. 12. The Combinations, Locks, Incidents, and Keys & Safe (CLIKS) was developed to track all keys, locks and safes within EPA Headquarters. This part of the physical security to ensure each room and the keys are assigned and not duplicated. 13. The Fitness Center Management Module tracks EPA employee that use the fitness center and their pay history. Each time a person visit the fitness center they must sign into the fitness center module. By doing this we have a record of each visit. 14. The Action Tracking System was designed based on requirements for an online tracking system with the ability to re-assign actions down to the staff level. The Director and or their administrative assistance can assign an action to one or multiply division heads. The division head can take the action or re-assign it to one of their staff members. Staff members can not re-assign an action; they can only complete the action.

Added: March 20, 2008 NAICS Code: 541512 March 20, 2008 This is a combined synopsis/solicitation for commercial items prepared in accordance with the format set forth in Federal Acquisition Regulation Subpart 12.6,as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. The solicitation is being issued as a Request for Proposal (RFP). The U.S. Environmental Protection Agency (EPA), Office of Administration (OA), Office of Administation Services Information System (OASIS) intends to award a fixed-price requirement to the selected contractor to provide business reengineering and system development life cycle support. EPA estimates the level of effort for this requirement is 6,240 labor hours for two 6-month periods. The awarded requirement will have one base year period for 6-months, and one option year period for 6-months. Offerors shall submit a response utilizing the above level of effort and any anticipated other direct costs estimates to develop a proposed overall ceiling price. This requirement is a total set aside for Service-Disable, Veteran-Owned Small Businesses (SDVOSB). Any SDVOSB firm that believes it is capable of meeting EPA's requirement as stated herein may submit a proposal, which if received by the response date of this announcement will be considered for award. All responses received will be evaluated on a best value basis. Technical proposals shall address all aspects of the Statement of Work. Your cost estimate shall be separate from the technical proposal. The technical proposal should not exceed 15 pages total (including attachments). Past performance information shall include at least three (3) similar projects of a similar scope and nature. Further evaluation instructions are attached. The following provisions and clauses apply to this acquisition: 52.212-1, Instructions to Offerors - Commercial Items, 52.212-3, Offeror Representations and Certifications - Commercial Items, 52.212-4, Contract Terms and Conditions - Commercial Items, 52.212-5, Contract Terms and Conditions Required to Implement Statutes or Executive Orders - Commercial Items. Specifically, the following clauses cited are applicable to this solicitation: FAR 52.204-9, FAR 52.222-3, FAR 52.222-21, FAR 52.222-26, FAR 52.222-35, FAR 52.222-36, FAR 52.222-37 FAR 52.232-23, FAR 52.232-33, FAR 52.233-1, FAR 52.249-1 and FAR 52.249-8. The North American Industry Classification System (NAICS) code is 541512. All offerors shall include a completed Representations and Certifications based on FAR 52.212-3 within their proposal. As an alternate, vendors may complete this at the ORCA website, located at https://orca.bpn.gov/. Prospective offerors should submit any questions they may have concerning this requirement by email to Donna Blanding at blanding.donna@epa.gov by close of business on March 24, 2008. Responses to such questions will be provided to all prospective offerors. The Contractor shall provide a fixed price for each labor category proposed to satisfy the requirements of the Statement of Work (SOW) via e-mail and hard copy by 2:00 p.m. EST. on April 7, 2008. Mail Hard Copy to: US Environmental Protection Agency ATTN: D. Blanding Mail Code 3803R 1200 Pennsylvania Avenue, N.W. Washington, DC 20460 OR via Courier or Express service to: US Environmental Protection Agency ATTN: D. Blanding 1300 Pennsylvania Avenue, N.W. Washington, DC 20004 Enclosures: Technical Evaluation Criteria Statement of Work Technical Evaluation Criteria This section explains how the Government will evaluate proposals and indicates the consideration of factors used to evaluate each proposal. Award will be made to the contractor that offers the best value to the Government. For this requirement, all evaluation factors other than price, when combined, are significantly more important than price. However, as submissions become more equal in their technical merit, the evaluated cost or price becomes more important. The technical evaluation criteria, listed in descending order of importance, are as follows: Business Process and Application Reengineering Experience: The contractor shall describe its specific work experience with Business Process and Application development Reengineering related activities or projects within the last three (3) years. Relevant experience includes work on contracts, delivery orders, GSA schedules, or any other relevant agreement similar or greater in scope of analysis of the existing custom application and to document the As-is-state; status and workflows. Then make determination for the To-be-state; with GAP analysis to identify alternatives for achieving the To-Be-State; with design of the new applications. Other tasks to be completed within the RFP are but not limited to: Design implementation, testing, and training. Past Performance: Evidence that the contractor has consistently delivered high quality work in a positive and professional partnership with the client; conform to specifications and standards of good workmanship; ability to control costs and meet project schedules, and meet or exceed client expectations. The contractor will be evaluated on past performance over the past three years. The contractor shall include the following information for Past Performance evaluating purposes: 1. Contract/order number 2. Name, organization, telephone number, and e-mail address of a verified point of contact familiar with the contract/order 3. Dollar value of the contract/order 4. Period of Performance 5. A description of the nature of work performed by the Contractor. The description should only include work directly performed by the Contractor. 6. Names of subcontractor (s) used, if any, and a description of the extent of work performed by the subcontractor 7. The number, type and severity of any quality, delivery or cost problems experienced in performing the work, the corrective action taken, and the effectiveness of the corrective action Contractors are cautioned that it is exclusively their responsibility to ensure that information provided is accurate and complete for all points of contact listed. Further, contractors are responsible for ensuring references actively respond to the Government's attempts to verify information provided in your submission. The Government is not responsible for the inability to contact a contractor's references due to inaccurate or incomplete contact information or uncooperative references. Past performance information not validated may not be considered. Management Approach: The contractor shall describe its management approach in responding to the RFP, including its management philosophy and command, control and communications approach. The management approach shall clearly articulate the lines of authority and responsibility within the firm. It shall also specify how work will be managed on-site and off-site. The contractor shall also address how it plans to mitigate problems or conflicts of interest that surface throughout the life of the schedule. Where the contractor uses subcontractors, the contractor must demonstrate how they will manage the subcontractors to ensure work is well-integrated, consistent, and of high quality. Technical Approach: The contractor shall describe its technical approach in assisting EPA in a fully reengineered OASIS portal and applications in accordance with the seven tasks described in the Statement of Work (SOW). Specifically, the contractor shall articulate its plans for seamlessly implementing EPA's newly designed OASIS portal in a detailed report for the period ending the 15th and the end of each month. The technical approach shall also discuss the contractor's ability to assist and support EPA OARM IT personnel by complying with use of approved agency software and will be designed to achieve a common, standard "look and feel". Qualifications and Key Personnel Competencies: The Contractor shall submit a comprehensive staffing plan consistent with its price quotation that demonstrates how it will meet the performance requirements of the RFP/SOW. Within its staffing plan, the contractor shall identify each labor category. One Full Time Employee (FTE) is estimated as 2,080 hours per year. The contractor shall provide supporting information sufficient to demonstrate its rationale of utilizing the quoted labor categories and the number of FTEs for accomplishing all required tasks. The quotation should include any other relevant information the contractor deems appropriate to perform the requirements of the solicitation. The contractor shall also include an organization chart which demonstrates that the composition of the team is sufficient to efficiently complete the tasks in the SOW in a timely manner. Additionally, the contractor shall describe the availability of key personnel such as the percentage of time they are available to work on this contract. Finally, the contractor must include resumes for all key personnel not to exceed two pages each. The resumes shall include name, contact information, labor category, education, work experience, and references. Resumes are not to exceed two pages per person. STATEMENT OF WORK - BUSINESS PROCESS AND APPLICATION REENGINEERING BACKGROUND: The Office of Administration has developed a WEB-based portal, Office of Administration Information System (OASIS), for all Specialized Amoderate@ applications with vital information which requires that data be carefully stored, but accessible. Moderate applications must be given Special Handling to minimize opportunity for of harm resulting from loss, misuse, unauthorized access or information modification. The intent is to reengineer business processes and implement these changes into the system for better flow of application use. DESCRIPTION: The Contractor shall provide business process reengineering and system development life cycle support for the Office of Administration Services Information System (OASIS). OASIS is a secure portal that provides EPA employees access to eighteen OARM/OA custom applications. The work required under this Task includes: analysis of the existing OASIS custom application and to document the As-Is state; status and workflows. Then make determination for the To-Be state; with GAP Analysis to identify alternatives for achieving the To-Be state; with design of the new applications. The Contractor shall develop new workflow processes for each OASIS application. The new workflow processes must provide process improvements and eliminate redundant steps. The period of performance shall be for six months from date of award. This requirement also has a 6-month option period. OASIS TECHNICAL OVERVIEW: OASIS is a custom in house written application, developed in ColdFusion MX8 as the front end and Oracle 10g database. The application is accessed by over 500 users on a daily basis. All code in this effort will be written by the EPA in house IT staff. OASIS currently has three environments, production, development and test. The servers in each environment are Dell Power Edge servers. Below is a list of subtasks and the work that is required for each. Subtask 1 - Analyze and Evaluate As-Is Business Processes for OASIS Applications The Contractor shall conduct an independent review and or audit of the business processes and applications that comprise OASIS. The goal of this review is to assess current business processes, workflow, and to document the As-Is state. The Contractor will interview OASIS users to assess and document current business processes and workflows. The goal of this review is to assemble all information necessary to document the As-Is state. Deliverable: Current State Assessment Report Subtask 2 - Document To-Be Environment and Alternatives The Contractor shall conduct interviews with existing users of the OASIS applications and OARM/OA management to identify expected (desired) business and operational goals. For new OASIS applications, the users will be interviewed and all requirements are gathered to ensure a detailed workflow process is mapped before software design shall start. The Contractor shall describe how the business processes can be improved and simplified, and how the users' roles can be managed to deliver the functionality required in a more streamlined manner. The Contractor shall identify how to better address the users' needs and how to simplify their processing activities. The Contractor shall recommend a data infrastructure that supports integrated, online information and services center, which serves as a single point of access to all of the OARM/OA activities within a Portal environment. The structure of this environment shall be expandable, and `capable of supporting the addition of future applications. The environment shall be consistent with the OARM/OA web, security and privacy policies. The Contractor shall provide a To-Be process model describing the above environment, and the reengineering and redesign requirements necessary to achieve it. For each application, the Contractor will develop a requirements specification that addresses functional, operational and system performance considerations. For the OASIS portal and each application, the Contractor will identify the operational rules that define system security requirements including access and roles, and how the business processes can be improved and simplified. In combination, the To-Be requirements for each application and the OASIS portal will comprise the To-Be state. Deliverable: Future State Summary Report Deliverable: Future State design with new requirements for workflows Subtask 3 - System Reengineering and Design Implementation Following approval from OARM/OA management, the Contractor shall perform system engineering and design activities to implement the To-Be environment. This will include definitions, integrated system design, database design and other design activities. This effort will also address system conversion activities. All system design must be done using EPA approved software products and all implementations must comply with established agency standards. The portal and supporting applications will be designed to achieve a common, standard look and feel, with a central system of role based security that supports the users and the OARM/OA IT Team. The portal will be engineered to permit the IT Team to add new applications, and include features such as help desk tools, email communications and user-oriented Help systems. Administrative functionality should be designed to simplify system maintenance processes and to leverage and optimize existing resources. This includes providing users with tools to manage and process their data more efficiently. Deliverable: Functional OASIS Portal and Applications (Readiness Plan) Subtask 4 - Testing Activities The Contractor shall coordinate OASIS testing activities to validate system performance. This will include the development of scripts to support detail end-to-end testing. System Integration Testing will be conducted by the Contractor & EPA team. User Acceptance Testing will be coordinated by the contractor and executed by EPA personnel. The Contractor shall remediate any changes or updates identified during testing. Change Requests (CRs) will be generated during testing to identify system problems and enhancements. The Contractor shall manage the CR process and ensure that all required corrections or changes are implemented and re-tested. A test plan and acceptance criteria will be developed and delivered to the Contract Officer Representative (COR). Deliverables: OASIS Portal and Application Test And Acceptance Plan including Test Scripts Test Analysis Report Subtask5 - Training The Contractor shall develop specific training materials to support the implementation of the new portal and applications. The Contractor shall evaluate training alternatives including: computer-based training (CBT), online or bubble help, classroom training sessions, webinar delivery and other alternatives. The Contracting Officer's Representative (COR) will review and approve the training delivery strategy prior to action by the Contractor. Deliverable: Training Plan and Products Subtask 6 - OASIS Implementation Following successful Testing and Training, the Contractor shall coordinate implementation of the new OASIS portal and applications with the OARM/OA IT group. Coordination with this group is essential to ensure the timely retirement of existing systems, conversion of existing application data, and, the implementation of the new portal and applications. Deliverable: To-Be State For OASIS Applications and Implementation Plan Subtask 7 - Other Deliverables In addition to the Deliverables associated with each subtask above, the Contractor shall be required to provide the COR with a Status Report for the period ending the 15th and the end of each month. The Status Report will be due within 3 business days following these dates and will address progress since the previous report. These Status Report shall be delivered to the COR in writing unless other arrangements are made between the Contractor and the COR. Cost Reporting - to include staff hours and funds expended during the prior month-end and inception-to-date; Accomplishments during the period; Project Risks and Contingencies; andUpcoming schedule - initiatives or delivery items. User Guides, Help Features ACCEPTANCE CRITERIA Delivery and product acceptance will be performed by the COR and will be based on meeting the criteria established for each deliverable. SECURITY CONTROLS The Contractor will be required to complete National Agency Check and Inquiry (NACI) paperwork within 10 working days of receiving the signed Task Order. OASIS