SRCSGT | D | Systems and Software Applications Support for DLIS and DLA Disposition Services

FBO DAILY ISSUE OF FEBRUARY 18, 2012 FBO #3738
SOURCES SOUGHT

D -- Systems and Software Applications Support for DLIS and DLA Disposition Services

Notice Date: 2/16/2012
Notice Type: Sources Sought
NAICS: 541519 — Other Computer Related Services
Contracting Office: Defense Logistics Agency, DLA Acquisition Locations, DLA Contracting Services Office - Philadelphia, 700 Robbins Avenue, Philadelphia, Pennsylvania, 19111-5096, United States
ZIP Code: 19111-5096
Solicitation Number: RFI-12-0034
Archive Date: 3/15/2012
Point of Contact: Donald Hinkson, Phone: 2157374337, William McClenahan, Phone: 2157377786
E-Mail Address: donald.hinkson@dla.mil, William.McClenahan@dla.mil
(donald.hinkson@dla.mil, William.McClenahan@dla.mil)
Small Business Set-Aside: N/A
Description: The DLA Contracting Services Office (DLA CSO) is conducting market research to determine the interest and capability of industry vendors to provide Systems Software and Applications Support (SSAS) of DLA Logictics Information Services (DLIS) and DLA Distribution services (DDS). T he pu r pose o f t h i s a c q u i s i t i on i s t o p r o v i de sup p o r t t o ass i st i n t he i m p l e m en t a t i on o f p r ocesse s, p r ocedu r e s, s t and a r ds, a pp li ca t i ons, t e chno l o g i es and t oo l s t hat w i l l i nc r ease t he p r odu c t i v i t y of D LA Lo g i s t i cs I n f o r m a t i on S e rv i ce ( D L I S ) and DLA Di s pos i t i on Se r v i ces ( DDS ) pe r sonne l. D L I S p r o v i des suppo r t t o t he m ili t a r y s e r v i ces, o t h er Depa r t m ent o f D e f en s e ( Do D ) a g enc i es, Fede r al Ci v i l a g enc i e s, i ndus t r y, N o r t h A t l an t i c T r ea t y O r g an i z a t i on ( N A T O ) and o t her f o r e i g n g o v e r n m e n t s f or t h e m an a g e m e n t o f ass i g n e d l o g i s t i cs i n f o rm a t i on. D L I S i s r espons i b l e f o r t he ope r a t i on, s y s t em d i sc i p li ne, and d i sse m i na t i on o f l o g i s t i cs d a t a f or t he Fede r al C a t a l o g S y s t em ( F C S ), t he Fede r al L o g i s t i cs I n f o rm a t i on S y s t em ( F L IS ), t he M ili t a r y E n g i nee r i ng D a t a A s set Loca t o r S y s t em ( M EDA L S ), D e f e n se R eu t il i z a t i on and M a r k e t i ng A u t o m a t ed I n f o r m a t i o n S y s t em ( DA I SY ), R e u t il i z a t i on M ode r n i z a t i on P r og r am ( R M P ) and o t her ass i g n e d l o g i s t i cs i n f o rm a t i on s y s t e m s. T he Di r ec t o r a t e o f L o g i s t i cs S y s t e m s p r o v i des a f u t u r e f ocus f o r t he o r g a n i z a t i on by d i r ec t i ng and i m p l e m en t i n g po li c i es a n d ob j e c t i v es r e l a t i n g t o n ew l o g i s t i cs i n i t i a t i v es and p r og r a m / p r o j e c t m an a g e m ent o f m a j o r i n i t i a t i v es. D L I S p r i m a r y f un c t i ons r e q u i r e t h a t e m p l o y ees i n t e r a c t w i t h v a r i ous l e g a c y s i t es and i n f o r m a t i on w a r ehouses i n l oca t i ons t h r o u g ho u t t he C o n t i g u o us U n i t ed S t a t es ( C O NUS ). I n add i t i on, D L I S su p po rt s t he i n f o rm a t i on t echno l o g y i n f r a s t r uc t u r e f or DD S app li ca t i on s y s t e m s. S e r v e r s t h a t r un t he DD S b us i ness app li ca t i ons a r e l oc a t ed i n bo t h C O NU S and O C O NU S ( O u t s i de C on t i g u ous U n i t ed S t a t e s ). C o n nec t i v i t y t o t hese s i t es i s c r i t i cal t o D L I S op e r a t i on s, as i s D L I S and D D S cus t o m e r s' connec t i v i t y t o D L I S m a i n t a i ned i n f o rm a t i on. The following Performance Work Statement details the required support: Section 2: PERFORMANCE WORK STATEMENT (PWS) 2.1 OBJECTIVE The objective of this Performance Work Statement (PWS) and the resulting task order is to provide a vehicle by which the vendor shall furnish the necessary services of qualified personnel to provide technical expertise to support the maintenance, enhancement and support of the technical support for System and Software Applications as defined in the following tasks. While executing these required activities, the vendor shall also sustain and maintain full operations for technical support for System and Software Applications ensuring users have access to the system and receive timely system and support staff responses, which may require support/coordination during non-duty hours. The accomplishment of these objectives requires skill and knowledge across the full spectrum of project management of standard systems sustainment, development and testing. These include, but are not limited to, requirements and business process analysis, configuration and requirements management, database design, information systems application design, software systems engineering, documentation development and maintenance, testing, and implementation. In addition to the technical skills, knowledge, experience and qualifications stated, these tasks will also require the services of qualified personnel in the areas of DoD logistics, and the Technical Support for System and Software Applications program and its current configuration. 2.2 TASKS All task deliverables will be provided in accordance with Section 2.3. All schedule and/or scope deviations from deliverables as defined under each Task shall be coordinated with the technical support for System and Software Applications Program Manager (PM) and approved by the Contracting Officer (CO) through the Contracting Officer's Representative (COR). 2.2.1 Task 1 - Program Management These activities shall be an on-going effort, performed over the life of the contract, to ensure that all the requirements defined in this PWS are met. The Vendor shall perform Program Management to include, but not limited to, cost management, technical planning, performance functions, briefings and attendance at functional and technical meetings with Technical Support for System and Software Applications providers and consumers. The Vendor shall coordinate with the Technical Support for System and Software Applications PMO to identify how software updates will be accomplished and what documentation should accompany those updates. The Vendor shall develop, document, and execute plans and procedures for conducting activities and tasks for maintaining Technical Support for System and Software Applications with regard to Problem Report and enhancement execution. Activities also include ensuring that deliverables are complete and delivered on time and within budget. 2.2.1.1 Monthly Status Reports The Vendor shall provide monthly status reports to include identified issues, issue recommendation strategies, major accomplishments, variance analysis and upcoming activities. Below is a further breakdown of the written progress reports: • Description of prior month's progress, in summary, task, completion date and revised completion date (if applicable) • Planned activities for the next month/future • Identification of risks and mitigation plan • Review of problems encountered and significant issues that may affect the completion of planned projects, schedule or funding • Identify future travel requirements 2.2.1.2 Prepare a Program Management Plan (PMP) The vendor shall document all support requirements in the PMP. The PMP shall describe the proposed management approach and detail Standard Operating Procedures (SOPs) for all tasks. The PMP shall include milestones, tasks, and subtasks required in this task order. The PMP shall provide an overall work breakdown structure (WBS) and associated responsibilities and partnerships between Government organizations. The PMP shall include the vendor's Quality Control Plan (QCP). The vendor shall provide the Government with a draft PMP, on which the Government will make comments. The final PMP shall incorporate Government comments. The PMP is an evolutionary document. It shall be updated yearly. The vendor shall work from a Government approved PMP. The vendor shall work from a new version of the PMP once approved by the Government. 2.2.1.3 Integrated Product/Program Schedule (IPS) The IPS shall consist of: Plan of Action and Milestones (POAMs). Outside of the WBS, the Vendor shall prepare a POAM for planned software releases and migration tasks. Schedule Management. Labor resources used will be appropriate for the performance measurement techniques and the type of effort involved. There shall be a logical sequence of effort that supports the contract schedule. The following shall be identified by task in the schedule: • Key milestones • Labor category • Resource names • Hours 2.2.1.4 In-Process Reviews (IPR) IPRs will be held weekly to address identified program risks and action items. The Integrated Product/Program Schedule (IPS) shall be the basis for these sessions and therefore shall be updated weekly and delivered to the Government one business day in advance of the weekly IPR, to reflect current progress. These reviews will be held to resolve open issues regarding one or more of the following, as identified by the PM and/or the Vendor: • Agenda/Task Review and schedule/Action Items Past and Future • Issues • Delays in schedule • Risks • Action Items • Other topics as required IPRs shall be conducted either in person, on site at DLA Logistics Information Service, or via teleconference, as specified by the Technical Support for System and Software Applications PMO. 2.2.1.5 Resource and Government Furnished Information (GFI) Spreadsheet The Vendor shall complete and submit a Resource and GFI spreadsheet within five days of task order award. The Vendor shall update and submit an electronic copy of changes in status to the COR and Technical Support for System and Software Applications PM within 2 business days of the change with the exception of the training status. The Vendor will be notified by the COR of all DLA mandatory training requirements (i.e.: e-mail and LAN access on the first day; specific certifications are up to 90 days after award). Upon receipt of the notice, the vendor shall submit weekly status updates until all designated resources have completed the training. 2.2.1.6 Briefings and Technical Meetings The Vendor shall prepare briefing materials and represent the Technical Support for System and Software Applications at briefings and meetings with organizations of interest, stakeholders, and provider and consumer systems. This representation shall be at a level that functionally and technically represents the mission and implementation capabilities of the Technical Support for System and Software Applications: • Brief charts and briefer (approximately 1 per month) • Meetings/Conference calls with various organizations, stakeholders, providers and consumers (approximately 2 per month) 2.2.1.7 Award Kick-Off The Vendor shall prepare and present an executive overview with 5 days of contract award in Battle Creek, MI. The executive overview will demonstrate the vendor's plans to manage scope, schedule and resources for the task order. Vendor shall introduce to DLIS management the proposed key personnel and plans for sustaining; and if required, replacing these key personnel. The vendor shall also meet with Technical Support for System and Software Applications PMO during this time to discuss PMO expectations and details of program execution. Deliverables: Weekly Meeting Report Monthly Reports Integrated Product /Program Schedule (IPS) In Process Reviews Resource and GFE/GFI Spreadsheet Transition Plan Quality Control Plan Briefings and representation at meetings/conference calls Award kick off Program Management Plan 2.2.1.8 Configuration Management and Software and Documentation Delivery Configuration Management and efficient delivery of the software and supporting documentation is vital to maintaining uninterrupted operation of the Technical Support for System and Software Applications. These activities will be performed over the life of the task order with deliverables as specified below. Technical Support for System and Software Application environments include development, development/test, functional, quality assurance and production. 2.2.1.8.1 Configuration Management The Vendor shall, as directed by the Technical Support for System and Software Applications PMO and/or in accordance with the current DLA Logistics Information Service Configuration Management guidance, establish procedures for tracking software problem reports and software changes made throughout the Technical Support for System and Software Applications life cycle. The current DLA Logistics Information Service Configuration Management guidance is available from the Technical Support for System and Software Applications PMO upon request. The Configuration Management process will achieve the following objectives: • Identify, define and control all relevant configuration items of the product • Control modifications of all configuration items • Record and report the status of configuration item and modification requests • Ensure the completeness of the configuration items • Control storage, handling, release, and delivery of the configuration items The Technical Support for System and Software Applications PMO will assign the priority to all PRs, CRs and enhancements to Technical Support for System and Software Applications. The Vendor shall coordinate with the PMO, either via the weekly IPR or through correspondence, to determine which PRs, CRs and enhancements to include in each update to Technical Support for System and Software Applications. 2.2.1.8.2 Software and Documentation Delivery For each update to Technical Support for System and Software Applications, the Vendor shall provide the following to the PMO: Deliverables: • Integrated Technical Support for System and Software Applications Software Product - the updated software • Software Version Description (SVD) - defining all the changes included in the software update • Software Installation Plan (SIP) - defining how the software is to be installed at the Government site • Unit Test Plan and Results - results of Vendor testing conducted prior to delivery (template to be provided at time of contract award). For each update to Technical Support for System and Software Applications, the Vendor shall provide associated updates to all affected documentation. Documentation shall be sustained in Documentation Library but also delivered to the Technical Support for System and Software Applications PMO in electronic format (see section 1.12). Documentation that may be affected includes, but is not limited to: Deliverables: Life Cycle documentation to include the following: The vendor shall provide and update the following documents or their IEEE 12207 equivalents: • Interface Control Documents (ICDs) • System/Subsystem Specification (SSS); Logical and Physical Data Models, RDE Database Specifications • Software Test Plan (STP) (can be identified and included in the Acceptance Test Plan) • Software Test Report (STR) • Software User Manual (SUM); SYSTEM User Guide • Software Center Operator Manual (SCOM); Developers & Administration Guides; Database Management Procedures; Deployment System Administration Support Report • Source Code • Configuration Management Plan (CM Plan) • Department of Defense Architecture Framework artifacts (DoDAF) • Requirements Traceability Matrix (RTM) 2.2.1.9 System Problem Reports (PRs) PR's are problems found (not working as designed) in the testing or operation of the Technical Support for System and Software Applications software by the users, the Technical Support for System and Software Applications PMO or by the Vendor. The PMO expects to initiate up to 1,000 PRs each year of this contract. The Vendor shall maintain a list of Technical Support for System and Software Applications PRs in Task Order Web Site (TOWS) and provide copies of all new PRs to the Technical Support for System and Software Applications PMO as new problems are identified. Technical Support for System and Software Applications PRs can be generated by the Vendor, PMO, testers and other users of the Technical Support for System and Software Applications. When the Vendor discovers a problem with the Technical Support for System and Software Application, they shall provide the PMO information so that the PMO can document the problem as a PR and assess the impact to Technical Support for System and Software Applications users. The Vendor shall always analyze any PRs required in the Technical Support for System and Software Applications and determine if there is any expected or perceived impact to the performance of the Technical Support for System and Software Applications and report that to the PMO prior to developing the change. The Vendor shall analyze all PRs and determine which documentation, software units and/or configuration items and version thereof need to be modified. The Vendor shall support the resolution of problems in a timely, prompt manor. The Vendor shall respond to assigned reported problems in accordance with the Government policy, including, but not limited to: • Priority 1 (Emergency)-System down or work stoppage. The Vendor shall initiate problem resolution procedures within 2 hours of initial problem report with program fix scheduled within 24 hours. • Priority 2 (Critical)-System Performance Degraded/Wrong Data. The Vendor shall initiate problem resolution procedures within one 2 business days with program fix scheduled within no more than 5 business days. • Priority 3 (Routine)-All other trouble calls. The Vendor shall initiate problem resolution procedures within 5 business days with program fix scheduled within no more than 15 business days. The Vendor shall conduct Unit Testing on all developed software to ensure the software meets the requirements of the PR. Unit Test Results will include the change that was tested, the scenarios used for testing and expected and actual results of the test. • Test scenarios/description • Test data inputs • Expected and actual results • Test procedures/steps required The Vendor shall coordinate with the Technical Support for System and Software Applications PMO to determine when the change will be delivered to the Government. The Vendor shall deliver the change in accordance with the CM and Software Delivery requirements specified in Task 2. The Vendor shall provide support in requirements determination and testing for PRs. Deliverables: Unit Test Plan and Results Software Installation Plan Software Version Description Updates to any other impacted life cycle documentation (as listed in Task 2) 2.2.1.10 Transition Plan The Vendor shall provide a written plan to include transition/prepare Government identified personnel to perform all actions required for comprehensive maintenance support, data engineering activities and application management of Technical Support for System and Software Applications. The Transition Plan shall describe all training requirements/personnel that will be provided by the Vendor to execute the transfer of knowledge. The Vendor shall submit an initial plan within six months of contract award. The Contactor shall submit quarterly updates to the transition plan, including a summary of the changes, if any. The Transition Plan and subsequent updates will be accepted by the PMO in accordance with paragraph 1.12 of this PWS. Deliverables: Transition Plan Transition Plan Quarterly Updates 2.2.1.11 Transition Plan Implementation The Vendor shall execute the approved Transition Plan developed for transitioning Technical Support for System and Software Applications at the end of this contractual agreement. During the transition phase, the Vendor shall provide weekly transition progress reports. The Vendor shall submit all written plans, updates and progress reports electronically to the COR and the PMO. The Transition Plan and subsequent updates will be accepted by the PMO in accordance with paragraph 1.12 of this PWS. Deliverables: Transition Documentation Transition Support (training) Weekly transition progress reports during the actual transition 2.2.1.12 Quality Assurance Plan The Vendor shall prepare a written Quality Assurance Plan (QAP) to the Government for approval. This QAP will outline how Technical Support for System and Software Applications the program can improve the quality of data within its system/program as well as a process to notify/communicate and monitor data quality problems with the authoritative source systems. The Vendor shall submit an initial Quality Assurance Plan within 30 days of contract award. The Vendor shall provide quarterly updates to the Quality Assurance Plan, including status of implementing and a summary of the changes, if any. The Vendor shall submit the Quality Assurance Plan electronically to the COR and the PMO. The Quality Assurance Plan and subsequent updates will be accepted by the PMO in accordance with paragraph 1.12 of this PWS. Deliverable: Quality Assurance Plan Quality Assurance Plan Quarterly Updates 2.2.1.13 Section 508 Compliance Requirements Unless the Government invokes an exemption, all Electronic and Information Technology (EIT) products and services proposed shall fully comply with Section 508 of the Rehabilitation Act of 1973, per the 1998 Amendments, and the Architectural and Transportation Barriers Compliance Board's Electronic and Information Technology Accessibility Standards at 36 CFR 1194. The vendor shall identify all EIT products and services proposed, identify the technical standards applicable to all products and services proposed and state the degree of compliance with the applicable standards. Additionally, the vendor must clearly indicate where the information pertaining to Section 508 compliance can be found (e.g., Vendor's or other exact web page location). The vendor must ensure that the list is easily accessible by typical users beginning at time of award. The vendor must ensure that all EIT products and services proposed that are less than fully compliant, are offered pursuant to extensive market research, which ensures that they are the most compliant products available to satisfy the solicitation's requirements. If any such EIT product or service proposed is not fully compliant with all of the standards, the vendor shall specify each specific standard that is not met; provide a detailed description as to how the EIT product or service does not comply with the identified standard(s); and shall also indicate the degree of compliance. Deliverables: Link to 508 web location Updates to compliancy when applicable 2.2.2 Task 2 - Data Base Administration (DBA) Support The Vendor shall provide data management and database administration services and support functions listed below. The vendor shall provide DBMS support for all computing environments currently supported by DLIS and any future DBMSs implemented. This includes mainframe, mid-tier and PC computing environments. DLIS currently supports Oracle, IBM's Universal Database (UDB), SQL Server DBMS and Microsoft Access. Each DoD vendor position responsible for Information assurance (IA) functional requirements(s) must be correlated with a category or specialty and level based on the functions found in the DoD 8570.1. Vendors performing functions in multiple categories or specialties must hold certifications appropriate to the functions performed in each category or specialty. (DoD 8570.1) Vendor personnel holding a certification must release their certification information to the Department of Defense through the Defense Workforce Certification Application (DWCA): https://www.dmdc.osd.mil/appj/dwc/index.jsp. (DoD 8570.1) Vendor IA certification holders must ensure that their certificates stay active (DoD 8570.1) 2.2.2.1 DBA Support The vendor shall: • Provide application and system, physical and logical, database management administration service and support functions as applicable to DLIS with respect to database software installations/upgrades and patch management; • Research, analyze, and determine Database Management System (DBMS) software/patch/upgrade availability, applicability; • Research and determine software/hardware requirements; • Analyze/determine impacts to DLIS applications, server O/S, COTS and GOTS software in addition to identifying any information assurance impacts; • The vendor will provide project management services and support for DBMS and DBA related projects and efforts, preparing requested documentation such as lists, word documents, spreadsheets, POAMs, Work Break Down Schedules (WBS) tracking status and progress and reporting both formal and informal progress to government personnel and management. • Determine required installation/upgrade/patch configuration parameters and space requirements: o Customize installations for application sustainment; o Develop an implementation plan and schedule; o Obtain Government POC approval for the installation schedule; o Coordinate schedule through configuration management; o Install/Configure DBMS software/upgrades/patches. • Provide database CERT/CTO/IA directives/mandates/regulations management: o Research, analyze, determine applicability, impacts of DBMS CERTS, CTOs, IA directives/mandates/regulations; o Develop implementation plan and schedule; o Obtain customer approval for installation schedule; o Coordinate schedule through configuration management and obtain approval; o Install and implement CERTS, CTOs, other IA directives, mandates and regulations to include but not limited Security Technical Implementation Guides (STIGs) and Security Readiness Reviews (SRRs); o Prepare Plans of Action and Milestones (POAMs) as required and implement mitigation measures/strategies as required. • Provide database backups and recoveries: o Determine, setup, coordinate backup schedule for DBMS and other related files; o Monitor backups to ensure completeness and minimal downtime in the event of a failure; o Ensure recovery of DBMS and other files is obtainable through established backups and processes; o Perform recovery of DBMS, databases and other database related files using established processes and procedures to minimize recovery time and unavailability of database. • Provide database Continuity of Operations (COOP): o Participation in all phases of COOP planning as needed; o Participation in COOP exercises and related activities as required; o Preparation of documentation for COOP exercise and related activities. • Assist stakeholders in resolving issues/concerns/problems as they relate to database access and availability: o Manage database space and storage requirements; o Determine, monitor and forecast space and storage management requirements for DBMS software, database files and related database files such as logs, etc.; o Assist in problem determination and resolution concerning the DBMS/database/database related files; • Create and maintain database user accounts, granting appropriate privileges and roles to the databases; • Assist in database modeling as requested, offering design options/solutions; • Administer application databases; • Assist HP and DLIS system administrators as required; • Provide data management: o Run queries and develop reports from databases; o Perform data cleansing of production database data; o Develop database related processes/procedures that enforce/compliment other data integrity processes and procedures implemented by DLIS; o Assist DLIS customers as requested with data management concerns/issues/problems. • Provide support to DLIS in the assessment and implementation of the concepts and technologies regarding data mining, data warehousing, data standardization, data management and data administration; • Develop policies, processes and procedures for effective data management and administration. Deliverables: COOP Documentation for exercises and related activities Forecast and management requirements Related database files and logs Source codes for any database modeling or technology implementations 2.2.2.2 Data Propagation The vendor shall assist in analysis, technical support, troubleshooting and monitoring of Information Integrator and Data Propagation software and servers. These tasks shall include: • Installation and application of fixpacks to database(s) and software products; • Troubleshooting system issues including loss of connectivity to data sources/targets, response time issues and potential problems with subscriptions; • Working with IBM Technical Support to resolve issues to replication and software operations; • Set up and monitoring of IBM DB2 backups and restores; • Registration of tables for replication; • Definition of subscription sets; • Windows scheduling and services; • Mass changes to replication subscription database for targets ; • Creation of database tables subscriptions; • Scheduling of software upgrades and services for Information Integration and Data Propagator; • Creation of wrappers and programming support for wrappers for specific operations (such as data conversion) for federated systems; • Installation of control tables for replication and scheduling of replication data; • Development of Consistent Change Data tables; • Defining connectivity between source/target and replication server(s); • Working with database personnel to identify and diagnose system problems then tuning database for optimum efficiency; • Responding to monitor alerts and identification of potential problem actions/resolutions. The vendor shall also provide support to DLIS in the assessment and implementation of the concepts and technologies of data mining, data warehousing, data standardization, data management and data administration. The vendor shall assist DLIS in developing policies, processes and procedures for effective data management and administration. Vendor DBMS support shall be provided for all computing environments currently supported by DLIS and any future DBMSs implemented system. This is to include mainframe, mid-tier and PC computing environments. Supported systems currently consist of Oracle, IBM's Universal Database (UDB),SQL Server DBMSs and Microsoft Access. 2.2.3 Task 3 - DLA Logistics Information Service eWorkplace The vendor is responsible to support sustainment of the Microsoft Office SharePoint Enterprise Business to Employee (B2E) portal used for knowledge management and information sharing. The vendor shall perform administrative and development activities related to overall system maintenance to insure system availability and peak performance. The vendor shall perform and remain current in the capability to perform the following duties: • Perform portal administration to include network and server administration and configuration to insure optimum performance; compliance with DOD/DLA regulations and policies; and coordinate and implement DLA Computer Emergency Response Team (CERT) tasks and patches to insure system security; • Design, develop, test and implement software enhancements to incorporate new functionality or to improve current functionality. 2.2.3.1 Portal Administration The vendor shall perform portal administration duties for supporting the existing Sharepoint application. This effort shall include the identification, implementation and documentation of actions required to maintain portal availability and performance. Vendor responsibilities include but are not limited to: • Support Level II helpdesk activities to include trouble-shooting and identifying cause and implementing remedy for problems identified by user trouble tickets; • Perform network administration tasks to insure server connectivity and user availability. Coordinate with DISA at the DLA Ogden Enclave (DOE) for scheduled and un-scheduled maintenance downtime; • Implement all directives and tasks associated with DLA Computer Emergency Response Team (CERT) patches to insure system security; • Monitor system performance and identify and recommend corrective action to potential and/or current system problems; • Provide immediate notification to government personnel of unexpected system outages, or performance degradations; • Provide detailed input to government staff for the DLA Enterprise system outage reporting process (INFOSPOT); • Document all configuration and server settings and changes and provide written documentation to the government. The Government will approve all proposed changes prior to implementation; • Demonstrate a high level of proficiency in the following knowledge/skill areas: Portal Administration User/Account Administration Portal Admin Quest Recovery Manager Quest Site Administrator 2.2.3.2 Sharepoint Applications Enhancements The vendor shall be responsible for developing software enhancements to correct problems that are identified within the Sharepoint functionality or to provide new functionality based on customer need. Software development responsibilities include: • Complete analysis of the requirement and recommended solution. This also includes analysis of current program code, provided during initial development for potential modification; • Preparation of milestones, cost estimates, and adequate resources; • Perform software programming upon Government approval of a change request or problem report; • Perform unit level testing on programmed changes; • Provide documentation for Configuration Management Process to include System Change Requests, Problem Reports, and Special Projects; • Delivery of program source and object code, unit test results, In-Process Reviews, Test Plans, and other applicable documentation; • Deliver metrics and reports to include project progress against milestones and completion dates; • Resume' will list experience in skill areas below and require approval before hiring: Sharepoint Portal Search Engines (Portal/Web) Business Process Workflow Programming Fundamentals and Best Practices MS SharePoint Designer Deliverables: System Report on outages and degradation issues Maintenance Log on all configuration and server setting changes Configuration Management Process for CR's, PR's, and Special Projects Source and Project Codes Metrics Report of Milestone completion 2.2.4 Task 4 - DLA Logistics Information Service - Map Catalog The DLA Map Catalog is an information system providing National Geospatial-Intelligence Agency (NGA) Product Catalog data to the United States Federal government, the armed forces of the United States government, and any other support personnel carrying out their mission related functions. The DLA Map Catalog uses commercial off the shelf (COTS) applications to create, maintain, and manage a geodatabase of NGA Product coverage and output data to industry accepted formats for use in catalog applications. The DLA Map Catalog provides access to databases and other information resources of the Mapping Enterprise Business System (MEBS), located at the DLA Aviation in Mapping Customer Operations (MCO) in Richmond, VA. The DLA Map Catalog embodies an open architecture designed to accommodate the rapid introduction into the system of advanced information processing resources. The vendor shall provide the following DLA MAP support: • Provide Technical Support for the DLA Map Catalog; • Provide ArcGIS Spatial Data Engine administration and support for all DLA Map Catalogs, both online and CD, both NIPRNet and SIPRNet; • Provide ArcGIS Server administration and support for all Online DLA Map Catalog (NIPRNet & SIPRNet); • Provide ArcGIS Internet Map Server administration and support the Online DLA Map Catalog, on both the NIPRNet and SIPRNet; • Provide Web Server Administration and Support for the Online DLA Map Catalog (NIPRNet & SIPRNet); • Provide 24x7 Sun Solaris administration support for the DLA Online Map Catalog (NIPRNet & SIPRNet); • Provide Technical Documentation support for the DLA Map Catalog; • Provide Data Quality and Statistical reports for the DLA Map Catalog; • Provide support for CD Catalogs, including Navy/Marine Corps Intranet and Classified; • Provide technical support for the Online DLA Map Catalog, on both the NIPRNet and SIPRNet; • Provide support for COOP on both the NIPRNet and SIPRNet; • Provide support for Geographic Information Systems (GIS) Processing Models; • Provide support for Notice to Mariner (NTM) updates; • Provide support for MEBS table loading; • Provide development and enhancement of the Online DLA Map Catalog with one annual release; • Provide development and enhancement of the CD DLA Map Catalog with one annual release; • Provide Feature Class Data Validation. Deliverables: CD DLA Map Catalog On-Line Release DLA Map Catalog Data Validation Report 2.2.5 Task 5 - DLA Customer Interaction Center (CIC) The vendor shall provide technical support for the DLA CIC component systems and applications. Support includes: • Development and maintenance of DLA CIC reports using Microsoft Access and Excel, Winbatch and Visual Basic language. The reports include primarily data from the SAP CRM (Customer Relationship Management within Enterprise Business Systems (EBS) application and the AVAYA Call (phone) Management System (CMS); • Development of reports accessible from the SAP Business Intelligence (BI)/BEX used as a source of CRM data; • Provide technical details of current and potential issues that affect the CIC and its components. i.e. evolving technology mandates, proposed changes to IT structure, security changes/patches, sustainment of remote work locations, etc.; • Work with and provide technical details to third party personnel tasked to support SAP in Battle Creek and CIC operations; • Determine efficiency of CIC system and operations; identify user/system errors and sources of resolution. Recommend, develop and implement solutions using current technology/programs to streamline agent workload and processes; Develop and maintain "Toolbox" mechanisms for CIC staff to streamline access to various tools/programs; • Provide technical support to CIC management including participation in CIC Program Management (PM meetings, webinars and teleconference; • Provide analytical information about CIC operations; • Monitor and maintain the Faxination server and Historical Backup server. Ensure the Faxination server is continually operational in accepting fax workload from CIC customers and distributing said workload correctly through the email system to the SAP CRM Service application. Coordinate with Local Area Network (LAN) support personnel on applying security patches and upgrades to Faxination; • Configure and monitor functionality of the Workforce Management Server (also known as Blue Pumpkin) to support agent scheduling and workload projections within the CIC environment. Ensures the server is continually operational with access to Avaya data. Troubleshoot and work with telephony group to rectify problems; • Monitor functionality of Quality Monitor (QM) application, which supports management oversight of CIC operations. Troubleshoot and work with telephony group to rectify problems related video/audio captures provided by QM; • Provide Data Quality support; • Analyze, review and provide solutions, reports, data quality and documentation; • Provide support for the Enterprise Customer Master (ECM); • Provide analysis and corrective actions related to connection problems with MIAP (Multi-host Internet Access Portal)/DSS (Distribution Standard System); • Develop and Maintain Report "Dashboards" to streamline CIC management reporting function. Dashboards are to house most current reports for distribution, with capability to directly email/distribute to relevant audience; • Troubleshoot outage and system/connectivity/response time degradation instances and facilitate required support to the Lansing CIC site as needed to maintain readiness and efficiency of operations; • Assist with COOP stress tests as requested; • Setup the training/COOP environment in Lansing and return to normal configuration at training conclusion, including coordinating with Lansing facilities IT staff; • Provide first line rapid response troubleshooting to CIC agents to ensure minimal agent downtimes. Coordinate with appropriate helpdesks to resolve issues, and facilitate/liaison with telephony to fix problems. Provide workaround processes/procedures & documentation to agents to accommodate quick setup after physical moves to different workstations/areas; • Continually monitor IT issues reported by agents to determine patterns of problems for reporting and assist in developing solutions. Deliverables: Customer Relationship Management Report EBS Customer Relationship Management Report AVAYA Dashboard Reports on system functionality, response time and readiness 2.2.6 Task 6 - DLA Logistics Information Service Distributed Learning Using blended IT solutions and Instructional Systems Design (ISD)/ Systematic Approach to Training (SAT) learning development models, the vendor's Distributed Learning Team designs, develops, and delivers effective and interactive business training to any DLIS/Disp Svcs/DLA user, worldwide. The Distributed Learning Team also provides design, administration and implementation support for streaming multimedia services. The vendor shall provide a Distributed Learning Team to design, develop, and deliver, effective and engaging business training programs for DLIS/Disp Svcs/DLA. Team applies knowledge of web technologies and design to create powerful applications and tools that support the learning processes to execute the following tasks: • deploy the ISD or SAT model or equivalent methodology to analyze, design, develop, implement and evaluate training materials; • develop and implement innovative distribution technologies to provide training materials to any DLIS/Disp Svcs/DLA user, anywhere in the world, as directed by the customer; • research, recommend and implement, as requested and as feasible, content delivery via emerging learning technologies such as mobile devices and online university training structures; • design, develop, maintain, and refine process templates to increase efficiencies during production and provide consistency for customer(s); • design and develop DLIS marketing materials, eCards, etc. to assist in the promotion of DLIS products and services and to educate customer(s); • design and develop other multimedia products, as directed by the customer(s); • maintain all materials, practices, and products as required by the customer(s). 2.2.6.1 Conduct Needs Analysis Perform front-end job or task analysis to determine: • the skills required to effectively perform the students' job; • current performance versus desired performance; • dominant learning styles and preferences; • students' current hardware capabilities/limitations. Analyze needs of the client to determine best possible solutions. Recommend optimum delivery method, which can include one or a combination of the following: • self-paced, interactive training distributed over the worldwide web (WWW); • self-paced, interactive training distributed via compact disc (CD); • instructor-led training captured on camera and distributed via blended learning DVD; • instructor-led training shared with students via web conferencing (webinars), online university, and video teleconferencing (VTC); • training videos combining video, graphics, and recorded audio and assembled with movie editing software; • future delivery methods that are influenced by emerging technologies. Manage the project (identify computer and human resources and timelines) from request through completion. 2.2.6.2 Provide Instructional Design and Develop Content In support of instructional design and content the vendor shall: • Gather information, drawing on several computer, library, and human resources, to locate, collect, and organize information about subject-matter; • Develop relationship with SME to develop comprehensive package; • Study and learn subject-matter well enough to develop models and analogies and thereby explain subject-matter to students; • Draw from existing knowledge of DLA/DLIS applications to deepen understanding of new subject- matter; • Capture and size application screens/web pages for media delivery; • Design instruction to include exercises, scenarios, interactions, knowledge checks, and expected outcomes; • Determine multimedia required to facilitate training for all learning styles, when appropriate, incorporate appropriate media elements, such as text, graphics, audio, animation, video, user interactions into design; • Design Section 508 compliance into every interaction, which includes providing key press equivalents for every mouse click, open or closed captioning for audio segments, and screen reader text files for on-screen text; • Identify content and utility buttons for program interface; • Manage the project: develop timeline and responsibilities for programmers and artists, functional testers, and clients; track progress, report to customer. 2.2.6.3 Develop Program The vendor shall: • Explore design techniques and layouts to develop a custom interface that enhances the content and fulfills the client's requests; • Create graphics to support content and facilitate learning; • Provide voice talent to record audio segments; • Capture and edit audio segments; • Capture and edit movies and video segments; • Create overall program and assemble multimedia components; • Provide a high level of support with these software products: • Adobe Acrobat Pro 9 • Adobe Robohelp 8 • Adobe AfterEffects CS4 • Adobe AfterEffects CS5 • Adobe SoundBooth CS5 • Altova XMLSpry 2009 • Adobe Bridge CS4 • Apple Quicktime 7 • Adobe Connect 7 • DameWare Remote System Management Software 7 • Adobe DreamWeaver CS4 • HiSoftware HiCaption Studio 9.0 • Adobe Flash CS4 using AS2 and AS3 Action Script • Macromedia Authorware 7.0 • Adobe Flash CS5 • Microsoft Office 2007 • Adobe Illustrator CS2 • Microsoft Project 2007 • Adobe Media Encoder CS4 • Microsoft Visio 2007 • Adobe Photoshop CS4 • Sony Vegas 7 • Adobe Photoshop Extended CS5 • Sony Sound Forge 9 • Adobe Premiere CS4 • TechSmith Snagit 9.1 • Adobe Premiere CS5 • Wacom Graphic Tablet • Windows Media Encoder and Utilities 9 • TechSmith Camtasia Studio 2 • UltraEdit 15 • Program Section 508 compliance into every interaction; • Test for functionality and Section 508 compliance. 2.2.6.4 Implement/Deliver Training The vendor shall: • Package for distribution and deliver master CD or DVD to client; • Prepare files for distribution over the internet; • Deliver instructor-led training via camera for delivery via blended learning DVD, streaming media, or satellite; • Coach DLIS instructors to deliver via camera for delivery via blended learning DVD, streaming media, or satellite; • Maintain the streaming server to continue to deliver to more than 1500 simultaneous users within the DLIS campus; • Grow the streaming server to deliver products from DLIS to DLA global users; • Provide Distributed Learning support for webinar training; • Assist instructors with webinar course design and development. 2.2.6.5 Conduct Training Program Evaluation The vendor shall: • Determine post training effectiveness via client and student feedback; • Track usage, completion rates, via custom web-based program; • Provide effectiveness feedback to customer(s) as requested; • Incorporate enhancements into product maintenance cycles; • Create maintenance plan (including content and development tools), with customer approval, and implement product(s). Deliverables: Promotional items: marketing materials, eCards Multi-media products (tailored to customer needs) Interactive training (via Web, CD, DVD, Webinars, VTC, On-line University) 2.2.7 Task 7 - DLA Logistics Information Services Applications 2.2.7.1 Technical Support The vendor shall develop in coordination with the PMO plans for new business/transformation and system initiatives. The vendor shall develop and maintain detailed Project Management Plans and Work Breakdown Structures identifying tasks and task resources. The vendor shall develop Requirements Traceability Matrix (RTM) documenting all functional requirements. The vendor shall meet with the applicable DLA Logistics personnel to discuss potential functional or technical revisions to the RTM. The vendor shall coordinate the project plans for review through the appropriate functional and technical groups and incorporate applicable comments. The vendor shall update the plans and work break down structures periodically. In addition, the vendor shall provide documentation of project management functions such as meeting minutes, status collection, project presentation materials, project planning activities, risk management activities and technical reports as needed. The vendor shall conduct the project meetings at the request of the DLIS COR. 2.2.7.2 Technical Guidance The vendor shall perform an analysis of project requirements and recommend technical solutions to DLIS/DDS. The vendor shall evaluate commercially available software and hardware solutions against baseline requirements. The vendor shall provide on-site technical management and guidance on the development and implementation of solutions involving data warehousing and data mining, distributed databases, database administration effort, Web technologies, Services Oriented Architectures (SOA), EC/EDI conventions and transaction sets, electronic document management, configuration management, process and data modeling, problem tracking, application run time improvements, disaster recovery backup solutions, remote user solutions and desktop enhancements. 2.2.7.3 Requirements Determination The vendor shall document system requirements with DLIS and DLA functional and technical groups, upon receipt of appropriate functional requirements identified by the DLIS TPOC, to ensure that projects are understood and the technical infrastructure that is in place shall support system change requests. The vendor shall provide functional and technical guidance to develop necessary technical requirements documentation. 2.2.7.4 Development The vendor shall provide applications support and development which includes systems review, and enhancements to current applications, feasibility studies, requirements analysis, software integration, design and implementation, system software support and applications software support for DLIS in its current and transitioning environments. DLIS may use additional programming languages and require vendor programming expertise for these additional languages. All code generated or otherwise developed by the vendor shall be the property of the Government. Documentation and program code shall be developed using approved formats and techniques, including Gold Standard Documentation. Further examples of development tools and languages requiring support includes: • COBOL; • MS.NET; • Java; • JavaScript; • Unix/Linux Shell Scripting; • Oracle DDL; • DB2 DDL; • MS ACCESS; • MS SQLServer; • Perl; • SQL; • HTML; • XML; • Message Querying; • CANAM Crystal Reports; • SCM Software configuration management for midtier; • CA Software Change Manager IUID Registry • C #; • webMethods. The vendor shall provide application software and system support required to meet DLIS current and future requirements. Software development may include new development, modification, reengineering, maintenance or any other activities that result in software products. The vendor shall support DLIS in the migration of applications from current applications to new environments. DLIS is researching different technologies to execute enterprise initiatives, to include initiatives of Customer Resource Management, Knowledge Enterprise Portal, Integrated Data Environment, Asset Visibility, Federal Logistics Information System Modernization and wireless development. The vendor shall provide assistance in the research and application of such software, technology operations. The vendor shall develop GUI screens, applications code, databases and other software utilities, which meet the business needs identified in baseline requirements. This development shall be done in an environment entirely compatible with the DLIS environment. Development shall be completed using only software available in the DLIS environment at version levels equal to those implemented there, or higher. The vendor shall use conventional techniques as well as Rapid Application Development (RAD) and Joint Application Development (JAD) techniques. The vendor shall provide on-site technical management resources to perform system/project walk-through presentations where applicable for systems/applications and/or interfaces. Code developed by the vendor shall be in accordance with government approved specifications and shall become property of the Government at the conclusion of each development effort. The vendor shall validate system requirements with the appropriate DLIS and DLA functional and technical groups to ensure that the project scope is understood and that the technical infrastructure that is in place shall support the project. The vendor shall provide functional and technical guidance and assist DLIS in developing all necessary technical requirements documentation. The vendor shall review DLIS task assignments, and provide estimated resource hours (and staffing), system hardware/software requirements, using applicable cost and schedule practices, and work breakdown structure (WBS). The vendor shall provide system and subsystem design support; provide software user manuals; provide program management user manuals; provide database assurance and regression testing; provide content management and publishing; and provide data migration, coding, design, and analysis. 2.2.7.5 Design The vendor shall design processes, procedures, applications, databases and/or other data structures, which meet the business needs identified in baseline requirements. The vendor shall document these designs in the appropriate design documents, using DLIS documentation policies/procedures, which are available at DLIS upon request. The vendor shall provide on-site technical management resources to perform system/project walk-through presentations where applicable for systems/applications and/or interfaces. The vendor shall attend and offer advice at various configuration management boards for Logistics. The vendor shall provide input to the DLA Information Technology Solutions Document or other Information Technology boards as requested by the Logistics Program Manager. 2.2.7.6 Systems Architect Support The vendor shall perform an analysis of project requirements and recommend technical solutions to DLIS. The vendor shall evaluate commercially available software and hardware solutions against baseline requirements. The vendor shall provide on-site technical management and guidance on the development and implementation of solutions involving: • MS Active Directory; • Windows 2003/2007; • MS SQL Server 2003, 2005 and 2008; • Host Based Security System (HBSS); • User Administration; • System Monitoring; • Message Querying; • Trouble shooting; • Network Support; • webMethods. The vendor shall support database administration, Web technologies, electronic document management, configuration management, process and data modeling, problem tracking, application run time improvements, disaster recovery backup solutions, remote user solutions and desktop enhancements. The vendor shall work with the technical staff at the Enterprise Data Center (EDC) or DISA to coordinate any required changes. Changes shall be executed in accordance with government approved policies and procedures, which are available at DLIS upon request 2.2.7.6 Testing The vendor shall develop software utilizing the DLIS Quality Assurance General Policies and Practices which are available at DLIS. During the design and development, the vendor shall support DLIS/DDS identified technical and functional subject matter experts (SMEs) in preparing test plans consisting of test cases and data. Test Condition Requirements shall be prepared and delivered. Unit system and integrated testing shall be performed to ensure accurate execution of each individual software component. System and integration testing shall be performed according to a System Test Plan. Test results and defects shall be documented and tracked to ensure resolution of all deficiencies and completion of a comprehensive test. Before each phase of the project is completed, the vendor shall provide the necessary training and test data for Logistics personnel to complete acceptance testing. Issues raised during acceptance testing shall be documented and reported to the DLIS TPOC. The DLIS TPOC will determine to proceed to the next phase of the project when all of the identified problems have been resolved to the DLIS's satisfaction. 2.2.7.7 Software The vendor shall use only licensed commercial off-the-shelf (COTS) software; vendor-developed software or Government furnished software in performance of this contractual effort. Any other software must be approved prior to purchasing through the Government Acquisition process (MARD System). 2.2.7.8 Software Quality Assurance The vendor shall perform Software Unit Testing with review and oversight by the Government. When the vendor has certified testing and the Government approves the code, it shall be turned over to the Government for system quality assurance testing. Software Quality Assurance inspections and audits will be performed by the Government. When making developmental decisions for this project (e.g., platform, development tools, language, and communications), the vendor shall follow the DLA Information Technology Guidelines. The vendor shall adhere to established DLIS development standards, which are available at DLIS upon request, and shall provide input to DLIS SQA to establish standards where none exist. 2.2.7.9 Quality Assurance Testing The Government will conduct Quality Assurance Testing. Any discrepancies will be returned to the vendor for correction and re-testing. The Assurance Test must be completed and documented prior to the transition of the system into the DLIS/DDS production environments. 2.2.7.10 Functional Acceptance The vendor shall complete all development test plans and test results for review by the DLIS TPOC prior to entering into Functional Acceptance. The vendor shall develop an Acceptance Test Plan and perform acceptance testing of the system. Acceptance testing shall exercise the complete functionality of the system based on the documented requirements. Any discrepancies in the functionality of the system and the documented requirements shall be documented, analyzed, and corrected prior to acceptance of the system by the DLIS TPOC. The vendor shall provide the DLIS TPOC access to the development environment for the execution of this acceptance test. Upon Government acceptance of the system, the vendor shall document the acceptance test results and any subsequent analysis in the DLIS Acceptance Software Test Results (STR) document. The functional acceptance test must be completed and documented prior to the transition and installation of the system/software into production environments. 2.2.7.11 Military Engineering Data Asset Locator System (MEDALS) Graphic User Interface (GUI) The vendor shall provide support for: • MEDALS Web development, programming, and programming sustainment • MEDALS Batch processes development, programming, and programming sustainment • Post Master, MEDALS AUTOMATOR, and MEDALS FTP server development, programming, and programming sustainment; • MEDALS documentation development and support; Deliverables: Business/transformation strategic plans Requirements Traceability Matrix Development Test Condition Requirements Application and source codes GUI Screens Work Breakdown Structure Test Plans and Test Condition Requirements 2.2.8 Task 8 - FLIS Portfolio Development/Maintenance The vendor shall attend monthly technical meetings. The vendor shall provide conceptual requirements building and manage systems under the FLIS Portfolio listed below. Consideration shall be provided to server inaccessibility, down time, latency issues, and any other issues affecting the performance of a FLIS- related system. Current systems that are managed under the FLIS Portfolio: • Federal Item Identification Guide (FIIG); • Taxonomy Cross Reference to NSN; • QDB - Quality Database; • QTS - Quality Tracking System; • DD Form 180/ DD Form 1685; • GIRDER/iGIRDER - Government and Industry Data Edit and Review; • LOLA CLASSIC- Logistics Online Access; • WEBFLIS; • DEMIL - Demilitarization; • Pass-through; • U.S./Canada Joint Certification Program (JCP); • Federal Logistics Information System (FLIS); • H-SERIES • Catalog Workload Tracking (CWT • Information Documentation System (IDS) • FLIS Portfolio Workbench; • Edit Guide Simplification (EGS); • Electronic Cataloging (eCAT); • Commercial and Government Entity (CAGE) code; • Universal Data Repository (UDR); • CAMS/BINCS (CAGE Re-Host). Vendors shall perform the following tasks: • Complete design, maintenance, and related activities for Federal Logistics Information System (FLIS) Portfolio; • Analysis, programming, testing, metrics, move packages, and documentation for Change Requests (CRs), and Problem Reports (PRs) related to FLIS Portfolio; • Deliver program source and object code, unit test results, In-Process Review (IPR) and move package reports and other applicable documentation; • Provide support for Initial Design Reviews (DR) and Final Design Reviews (FDR). Deliverables: Requirements Traceability Matrix Work Breakdown Structure Test Plans and Test Condition Requirements 2.2.8.1 WebFLIS The vendor shall perform the following until the sunset of Web FLIS: • Complete analysis for system/application changes/transformation; • Prepare milestones, cost estimates, and adequate resources; • Assist TPOC in defining specifications for complex software programming/Structured Query Language (SQL) or modifying and maintaining complex existing applications/systems; • Provide application/system design, coding testing, debugging, performance resolution and documentation; • Have technical knowledge of all software systems programming applications/systems; • Perform quality assurance review and evaluation of new and existing software products; • Provide metrics; • Deliver program source and object code, unit test results, In-Process Reviews (IPR's), and move package reports (Vendor shall provide software and version(s) description(s) with source code(s); • Support WebFLIS design, development, programming, programming sustainment, and problem reports; • Support web services design, development, programming, and programming sustainment; 2.2.8.2 Universal Data Repository (UDR) The vendor shall provide programming support for the UDR Medical Program. Programming support shall be provided for the UDR DB2 Database, the UDR Medical Program on CD-ROM/DVD, the UDR Web application and the UDR/DMLSS (Defense Medical Logistics Standard Support) Extract. In addition the vendor shall provide: • Maintenance and enhancements to the UDR DB2 database to support changes required by data sources (i.e., DLA Troop Support), the Military Services or the Joint Medical Logistics Functional Development Center (JMLFDC); • Monthly production of UDR products - the 2-disc CD-ROM/DVD, the Web application, the UDR/DMLSS Extract (both CD-ROM/DVD and XML update transactions via web service, and daily price updates); • Application design and development utilizing JAVA, COBOL, Visual Studio.NET, UNIX shell scripts and XML; • DB2 Database Administrator resource to support the UDR Medical Program; • Technical analysis/recommendations on system change requests and/or problem reports; • Development of logical/physical data models; • Database assurance/regression testing; • Resolution of customer inquiries (i.e., installation problems) and perform other duties as required. Deliverables: Source and object codes Unit test results Regression testing results Recommended performance resolution findings 2.2.9 TASK 9 - Item Unique Identification (IUID) Registry The IUID Registry is hosted in the Defense Information Systems Agency (DISA), Defense Enterprise Computing Centers (DECC). The IUID Registry makes it possible to uniquely identify a discrete tangible item or asset and distinguish it from other like items across multiple automated information systems (AIS) throughout the Department of Defense. This capability is facilitated regardless of the method of identification leveraged within an external Service Agency AIS by using the Unique Item Identifier (UII) as a data key in all DoD systems. This allows internal and external data sharing between acquisition, logistics and financial systems with a certainty that the item of interest has been correctly identified and resulting systems information is not being confused with similar item(s) identified using different sets of data as primary keys for information retrieval. The Unique Item Identifier marking of items provides additional benefits for life cycle management of assets. The IUID Registry is the DoD system of record for the reporting of all DoD Government Furnished Property provided to contractors in performance of their contract. The IUID Registry system/application is hosted in the DISA DECC. The IUID Registry is the primary application and has five support applications, a web based GUI, access control (3 applications) and a Data Dictionary. 2.2.9.1 Operational Support. The Contractor shall provide the resources necessary to sustain and maintain the IUID Registry system that supports the functionality and interfaces defined in the IUID Registry. The contractor shall maintain the existing government provided IUID Registry applications in a manner that is at least equal to or better than their current functionality. The contractor shall provide applications support consisting of monitoring, operations, maintenance, configuration management and enhancements, maximizing performance and reliability, support applications, extracts and (Extended Markup Language) XML data streams. Contractor resources shall be available to ensure the IUID Registry is operational and available. Resources shall be available during the work week between 0700-1630 as well as be available for calls and required monitoring the remaining hours. The contractor shall ensure that system to system interfaces are operating and that the scheduled interfaces run at scheduled times. The contractor shall ensure that the IUID Registry is appropriately sized and tuned for the most efficient operations/performance possible. When the Contractor uncovers problems (including nonconformance) in the software, they shall contact the help desk and open a trouble ticket, prepare a PR or CR, whichever is applicable or report a DISA DECC Hosting failure. If a problem has resulted from an error in the DISA DECC hosting, the Contractor shall advise the IUID Registry SM/SOM on the impact of the problem to the IUID Registry functionality and any corrective actions that the Contractor anticipates they will be required to take when normal DISA DECC Hosting functionality is resumed. The Contractor shall ensure all detected problems are promptly reported to the IUID Registry SM/SOM. Operational Support includes: 2.2.9.2 Application Support. The Contractor shall institute procedures to manage the IUID Registry capabilities. 2.2.9.3 Item Unique Identification Registry (IUID Registry). The IUID Registry is an Oracle based database consisting of tables / architecture to process and store data from Automated Information Systems (AIS) and direct customer input via a Web based GUI. 2.2.9.4 IUID Web Site. The IUID Web Site includes, but not limited to: • IUID Registry Support Applications • Business Partner Access and Security Information Center (BASIC) • Business Account Manager (BAM) • Business Registration System (BRS) • Data Dictionary (DD) 2.2.9.5 Database Support. The Contractor shall institute procedures to create and manage database tables necessary to store IUID data for operations. Support limited to the creation, enhancement and manipulation of data within the tables of the database of the IUID Registry. (Overall maintenance of the Oracle database will be performed by personnel of the DISA DECC). Deliverables: Special Job Request Operational Support for Application Operational Support for Database Operational Support ETL 2.2.9.6 System Change Requests (CRs) and Special Job Requests. CR: Up to four (4) version releases per year and up to four (4) software patches per year. SJR: Up to two (2) per week. Change Requests (CRs) are changes or additions to the functionality of the IUID Registry software requested by the users and/or the IUID Registry SM/SOM. CRs will be implemented based on SM/SOM approval. The IUID Registry typically releases two (2) major software versions per year followed by minor software patches to address low priority bugs or minor cosmetic changes. (Two software patches per release typical). The Contractor shall maintain a list of IUID Registry CRs in CA Software Change Manager and provide copies of all new CRs as new changes are identified. IUID Registry CRs can be generated by the Contractor, IUID Registry SM/SOM, testers and other users of the IUID Registry. The Contractor shall analyze all CRs and determine which IUID REGISTRY documentation, software units and/or configuration items and version thereof need to be modified. The Contractor shall always analyze any planned CR to IUID Registry and determine if there is any expected or perceived impact to the performance of the IUID Registry. The Contractor shall support the preparation of plans and implement changes in a timely, prompt manor. The Contractor shall respond to assigned change work in accordance with the Government policy, including, but not limited to: Change categories: • Small - no data changes, primarily modification of displays/reports, 40 hours or less of contractor work. For proposal preparation use 50 SCRs at 40 hours. • Moderate - minor data changes, requires 40-250 hours of contractor work. For proposal preparation use 35 SCRs at 100 hours. • Major - adds new data sources, data marts, and major functionality change and requires over 250 hours of contractor work. For proposal preparation use 5 CRs. These changes can be tasked separately under this contract. The Contractor shall assist the IUID Registry SM/SOM with documenting enhancement requirements. The Contractor shall conduct analysis and determine which documentation, software units and/or configuration items and version thereof need to be modified. The Contractor will complete the design based on requirements and deliver Design Documentation for review and acceptance. The contractor shall analyze total time for completion of each CR and assist the SM/SOM with identifying tradeoffs of design elements for maximum efficiency of final design. Design Documentation shall include: • Affected configuration items • Database changes • User interface changes and/or additions • Description of function or process changes • Estimate of labor hours necessary for completion of the CR (Concurrent and total) Upon approval of the design by the IUID Registry SM/SOM, the Contractor shall develop the changes to IUID Registry based on the Design Documentation. The Contractor shall conduct Unit Testing on all developed software to ensure the software meets the requirements of the CR. Unit Test Results will include the enhancement that was tested, the scenarios used for testing and expected and actual results of the test. When the changes from a CR result in one or more new functional processes and/or new user interfaces, the IUID Registry SM/SOM may request the Contractor deliver an Integration Test Document. The IUID Registry SM/SOM will notify the Contractor via email when the Integration Test Plan Document is required. The IUID Registry SM/SOM may use this document to perform acceptance testing of the software changes. The Integration Test Document will include: • Test scenarios/description • Test data inputs • Expected results • Set-up conditions • Test procedures/steps required • Integrated Test Plan and Results 2.2.9.7 Special Job Requests (SJR). Special Job Requests are onetime non-recurring requests for information, documentation, White Papers, recommendations, etc. Special Job Requests are typically required two (2) times per week. SJR forms are created and sent to the Contractor for action by the IUID SM/SOM. The most common SJR are for Custom Data Queries, Corrections, or Deletions. Custom data queries: Customer data queries result in data sets derived from the IUID Registry database tables. The resulting data shall be placed in a report, spreadsheet or other file format for delivery to customers. Corrections: SJR for Corrections are made to the Contractor to correct customer submissions that have incorrect data which the customer is not authorized to change or the volume of affected records are greater than would be efficient for the customer to correct manually. All requests for corrections shall be reviewed and approved by the authorizing process prior to action. Deletions: SJR for Deletions are used to delete records from the IUID Registry database which the customer is not authorized to delete or the volume of affected records are greater than would be efficient for the customer to delete manually. All requests for deletions shall be reviewed and approved by the IUID Registry SM/SOM prior to action. Deliverables: Design Documentation Unit Test Plan and Results Software Installation Plan Software Version Description Integration Test Plan and Results (as requested) Updates to any other impacted life cycle documentation 2.2.10 Task 10 - Reutilization Business Integration (RBI)/Applications The vendor shall provide technical support to Disp Svcs software to a modernized Disp Svcs Applications environment. Vendor support shall consist of software engineering. The vendor shall provide technical advice at monthly meetings. The vendor shall provide conceptual requirements building. The vendor shall, in accordance with DLA policy deliver "Gold" documentation on or before the date new or modified functionality is released into the applicable production environment. Disp Svcs Applicatons includes the family of systems that support the Disp Svcs mission. This includes Disp Svcs Applications, the related WEB applications, other small applications, databases, interfaces, tools and data associated with the operation of Disp Svcs Applicatons. Provide additional programming support for sustainment. The vendor shall perform the following: • Provide documentation and evaluation of the technical landscape of the existing DAISY family of programs, including bar code application; • Provide reports, studies or technical analysis in support of the development or acquisition of Disp Svcs Applications IT resources; • Prepare compliant software conversion studies, analyze software conversion feasibility, evaluate alternate platform conversion and convert software; • Analyze System Change Request (SCRs) to integrate Disp Svcs requirements across other impacted DLA systems; • Analysis support; • Design support; • Programming support; • Testing support; • Metrics; • Delivery of program source and object code, unit test results, In-Process Reviews (IPRs), move package reports, and other applicable documentation in accordance with approved configuration management plan; • Preparation of milestones, cost estimates (including EDC-Related cost), and adequate resources; • Support for Disp Svcs Applications Web development, programming, and programming sustainment for DSS Applications; • Provide complete analysis, programming, testing, metrics, move packages, and documentation for System Change Request (SCRs), Special Projects (SPs), and Problem Reports (PRs) related to Disp Svcs Applications; • ORACLE Database Administrator (DBA) Support; • Risk Management Analysis/Plan; • Interface Requirements Specifications and development of Interfaces, as required; (specs must be in Gold Documentation Format); • Software Requirements Specifications; (specs must be in Gold Documentation Format); • Software Test Description; (specs must be in Gold Documentation Format); • Software Test Plan; (specs must be in Gold Documentation Format) • System/Subsystem Specifications; (specs must be in Gold Documentation Format); • Database Design Document (in Gold Documentation Format); • Interface Design Document (in Gold Documentation Format); • Software Design Description (in Gold Documentation Format); • Perform unit/system level testing; • Work Breakdown Structure; • Project Proposals; • Data Quality Support; • Support with hardware in accordance with DLA specifications. 2.2.10.1 Disposition Services Sustainment The vendor shall provide technical support to Reutilization business Integration as follows: a. Sustainment includes the family of systems that support the Disposition Services mission. This includes batch processes, related WEB applications, other small applications, databases, interfaces, tools and data associated with the operation of sustainment workload. Provide programming support for sustainment of RBI Applications both a break/fix (Problem Report) and new functionality (Change Request) basis. a. Analysis support b. Design support c. Programming support d. Testing support Additionally, the vendor shall provide available documentation and evaluation of the technical landscape of the existing family of programs b. Web Administrative Support (HP-UX, Apache). The vendor shall provide system administration to the web servers for web applications. The vendor shall provide technical expertise, consultation and administration. The vendor shall administer the web applications, as well as provide for CERT support. c. Web Programming Support shall consist of software engineering for web application: Programming support for Compliance and RTD; i. Testing support ii. Documentation for system change requests iii. Problem reports and special projects iv. Delivery of program source code and object code v. Unit test plans and results vi. Interface requirements documentation vii. Software Life Cycle documents d. RBI Bridging/Conversion Support. Vendor support shall consist of: i. Software engineering. ii. Prepare compliant software conversion studies, analyze software conversion feasibility, evaluate alternate platform conversion and convert software iii. Technical advice at meetings. iv. Conceptual requirements building. v. Data tables vi. Bridging scripts vii. Software Life Cycle documents e. Bar Code Support i. Documentation for System Change Requests, Problem Reports, and Special Projects; ii. Delivery of program source and object code, unit test results, In-Process Reviews (IPRs), move package reports, and other applicable documentation; iii. Other The vendor shall perform the following: • Provide reports, studies or technical analysis in support of the development or acquisition of RBI IT resources • Provide documentation, sample, explanations, demonstrations and technical support for Business Process re-Engineering efforts Deliverables: System Change Request Documentation Problem Report documentation Source and object codes Management Analysis/Plan Interface Requirements Analysis Software Requirements Specifications Software Test and Design Documentation Software Test Plan Database Design Documentation Interface Design Documentation Work Breakdown Structure Risk Management Analysis/Plan 2.2.10.2 Disposition Law Enforcement Equipment Database System (LEEDS) The vendor shall provide technical support to the LEEDS Legacy System. Support includes: • Provide business area analysis support and expertise for DLA legacy systems; • Provide legacy business system problem resolution; • Provide implementation recommendations for new requirements that need to be worked into existing legacy systems; • Provide system expertise and business knowledge for existing legacy systems; • Provide maintenance for the LEEDS Web Site; • Provide support for routine system maintenance, data pulls, and system releases. • Interfaces to other systems as required;
Web Link: FBO.gov Permalink
(https://www.fbo.gov/spg/DLA/J3/DSCP-PB/RFI-12-0034/listing.html)
Place of Performance: Address: The primary place of performance will be at the Hart-Dole-Inouye Federal Center, 74 Washington Avenue, Battle Creek, MI. Other places of performance are various CONUS and OCONUS sites including Defense Information Systems Agency (DISA) at Ogden, UT where mainframe support is provided., Battle Creek, Michigan, 49037, United States; Zip Code: 49037
Record: SN02677224-W 20120218/120216234902-c736ec1a1022b5b8428e4fe83fc50a91 (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

D -- Systems and Software Applications Support for DLIS and DLA Disposition Services