Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF SEPTEMBER 12, 2007 FBO #2116
SOLICITATION NOTICE

70 -- Suspense Tracking Software

Notice Date
9/10/2007
 
Notice Type
Solicitation Notice
 
NAICS
541511 — Custom Computer Programming Services
 
Contracting Office
Department of the Air Force, Air Force Materiel Command, 377 CONS - Kirtland (Operational Contracting Squadron), 377 CONS/LGC Operational Contracting Squadron 2000 Wyoming Blvd SE, Kirtland AFB, NM, 87117-5606, UNITED STATES
 
ZIP Code
00000
 
Solicitation Number
F2K0AB7233A001
 
Response Due
9/13/2007
 
Archive Date
9/28/2007
 
Small Business Set-Aside
Total Small Business
 
Description
This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR 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. This requirement is set-aside for small business only. The NAICS Code for this synopsis/solicitation is 541511, Size Standard $23M. Solicitation/Purchase Request number F2K0AB7233A001 is issued as a Request for Quote (RFQ). This document incorporates provisions and clauses that are in effect through Federal Acquisition Circular 2005-19 effective 17 August 2007. The Government intends to award one contract line item number (CLIN 0001) for Suspense Tracking Software (See attached Statement of Work for Requirements). QUANTITY: 1 UNIT OF MEASURE: EA DESIRED DELIVERY DATE: Within 15 days ARO FOB: DESTINATION . Inspection and acceptance: DESTINATION . The following provisions and clauses apply to this procurement: FAR 52.204-7, Central Contractor Registration; FAR 52.212-1, Instructions to Offerors-Commercial Items; Addenda to FAR 52.212-1, 52.211-6 Brand Name or Equal. In accordance with the FAR 13.106-1(a)(2) offerors are notified that award will be made on the basis of price. Offeror will be evaluated in accordance with FAR 13.106-2. FAR 52-212-3 Offeror Representations and Certification-Commercial Items (all offerors shall include a completed copy of this provision with their proposal); FAR 52.212-4 Contract Terms and Conditions-Commercial Items; FAR 52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders-Commercial Items. [in paragraphs (b) and (c) the following clauses apply 52.219-1; 52.219-6; 52.219-28 ; 52.222-3; 52.222-19; 52.222-21; 52.222-26; 52-222-36; 52.225-13; 52.232-33; Addendum to FAR 52.212-5: FAR 52.252-1, FAR 52.252-2, Clauses and provisions may be accessed in full text at http://farsite.hill.af.mil/; Offeror Representations and Certifications--Commercial Items.; DFAR 252.204-7004 Alt A, Central Contractor Registration; DFAR 252.212-7001 Contract Terms and Conditions Required to Implement Statutes or Executive Orders Applicable to Defense Acquisitions of Commercial Items. [in paragraph(s) (a) and (b) the following clause(s) apply 252.225-7001; Addendum to DFAR 252.212-7001 252.225-7002. All payments are to be paid via the Internet through the Wide Area Work Flow (WAWF) system. WAWF may be accessed at https://wawf.eb.mil. WAWF training may be accessed online at http://www.wawftraining.com. Payment information may be accessed using the DFAS website at https:www.dfas.mil. Your purchase order/contract number or invoice will be required to inquire status of your payment. All offers are due no later than 5:00PM (Eastern Standard Time) 13 September 2007. Offers may be mailed to 377 CONS/LGCB, ATTN: Debora Scott, 2000 Wyoming Blvd., SE, Bldg 20604, Rm. B-22, Kirtland AFB, NM 87117, emailed to debora.scott@Kirtland.af.mil (Preferred Method), or faxed to (505) 846-4083 ATTN: Debora Scott ADDITIONAL INFORMATION: Be advised that all interested parties must be registered in the Central Contractor Registration (CCR) Database in order to receive an award. If you are not registered you may request an application at (888) 227-2423 or through the CCR website at http://www.ccr.gov. STATEMENT OF WORK HIGH LEVEL REQUIREMENTS Table of Contents 1. Scope 2 2. Overview and Objective 2 3. Business Justification 2 4. Business Requirements 3 4.1 Basic Work/Business Process 3 4.2 Processes to be automated 3 5. Technical Requirements 4 5.1 Hardware Requirements 4 5.2 Software Requirements 4 6. Functional Requirements 4 6.1 Data Acquisition Requirements 4 6.2 Data Analysis Requirements 5 6.3 Data Output Requirements 5 7. Security Authorization Requirements 5 7.1 Physical Security 5 7.2 Logical Security 5 8. Operate, Support, and Use Requirements 5 8.1 System Operation and Support Requirements 5 8.2 Service/Maintenance Requirements 5 9. Data Requirements 6 10. Test Requirements 6 1. Scope The purpose of this document is to define the business and technical requirements needed by the 58th SOW for the procurement of a Suspense Tracking Software Application. The Contractors quote will be fully burdened to include all costs associated with the application and training of end users on the software. 2. Overview and Objective The 58th SOW is in need of an automated process to track suspenses and routing of documents. The selected implementation is a suspense tracker application by a vender in addition to the creation of a Microsoft SharePoint site that will collaborate with the application. 3. Business Justification Currently all groups and squadrons in the 58th SOW use a mix of applications to track suspenses and routing. Some organizations have implemented elaborate Access databases while others use simple spreadsheets. There is little to no collaboration of data up the hierarchy of the organizational structure within the wing and often suspenses are not met and documents get lost or forgotten on someone?s desk. 4. Business Requirements The 58th SOW requires the use of a system capable of tracking any and all suspenses both upward and downward directed. The system will be capable of serial and parallel notification via email of all personnel involved with a particular suspense. Additionally the system will be able to synchronize with the tracker portion of Microsoft Outlook 2007 and 2003. Users should be able to see all suspenses created in the tracker application on their Outlook calendars. They will also be able to see all taskers created in Outlook, associated with them in the tracker program. 4.1 Basic Work/Business Process 4.1.1 Taskers are originated by AETC and 19th AF. A function will be available that will allow the secretary to pull those taskers directly into the Suspense Tracker. 4.1.2 Reports are generated by the Wing secretary, the two executive officers and other administrative staff to show: a. All suspenses not closed b. All closed suspenses c. Suspenses due within 10 days d. Suspenses due within 3 days e. Suspense due within 1 day f. Suspenses late g. Turnaround time by task h. Time to complete a task by organizations i. List of organizations that did not complete a task j. List of organizations that did not complete a task on time 4.1.3 Each user within 58 SOW will be able to generate workflows and tasks as needed to fulfill their mission requirements. 4.1.4 Users, administrative personnel and supervisors with receive automated notification when: a. An EPR is 4 months from closeout b. An OPR is 4 months from closeout c. A feedback is 60 days from due date d. A D?cor 6 is 30 days from due date Note: The technical details are provided below of how this will be accomplished. 4.2 Processes to be automated 4.2.1 Currently 58 SOW organizations use several different spreadsheets to track when OPR/EPR/Feedbacks are due. These spreadsheets will be consolidated by the 58th SOW SC and placed into SharePoint. The application will query the shared spreadsheet at 1200 every night and automatically generate a new suspense for any EPR, OPR, feedbacks or D?COR 6s that are due within the timeframe identified below. a. An EPR is 4 months from closeout b. An OPR is 4 months from closeout c. A feedback is 60 days from due date d. A D?COR 6 is 30 days from due date An option is to add ?Rater?, ?Date Last EPR/OPR?, and ?Separation/PCS/PCA Date? fields in the personnel table and then this can lose dependence on a spreadsheet. In this case as part of the tracker application installation this data will be bulk-loaded before standing up. 4.2.2 Requirement 5. Technical Requirements 5.1 Hardware Requirements 5.1.1 No network hardware will be required beyond the SharePoint Server that the 377th will allow the 58th SOW to use for this application. 5.1.2 CAC Card readers will be required on all user PCs to provide authorization and authentication to the application. 5.2 Software Requirements 5.2.1 Currently 58 SOW has a SharePoint sight provided by the 377th MSG. The Suspense Tracker will reside on the same server that hosts the base SharePoint system. The suspense application will have access to portions of the 58th SOW SharePoint space that holds documents related to the workflows and taskers. Security permissions will be synchronized between SharePoint and the Suspense Tracker. 5.2.2 The Suspense Tracker will use the same SQL Server that services the SharePoint system. 6. Functional Requirements The suspense tracker will be able to generate tasks/suspenses, notify users in serial or parallel, generate reports and archive past data for the 58th SOW. 6.1 Data Acquisition Requirements 6.1.1 The Suspense Tracker will query a shared spreadsheet residing on the 58th SOW SharePoint space 1200 every night to automatically generate a new suspense for any EPR, OPR, feedbacks or D?cor 6s due within a specified window. 6.1.2 The suspense tracker will have an option on the main page to perform a change of reporting official (CRO). This function will generate required packages/forms including EPR or OPR if needed. Additionally the Tracker will route packages to appropriate personnel. 6.1.3 The tracker will be able to bulk-load employees from the Global Address List and allow a user to enter rater, separation/PCS/PCA date and date of last report into each persons account file. 6.2 Data Analysis Requirements 6.2.1 The system will analyze report and separation/PCS/PCA information to generate suspenses for EPRs, OPRs, performance feedbacks, and D?cor 6s. 6.3 Data Output Requirements 6.3.1 Reports are generated by the Wing secretary, the two executive officers and other administrative staff to show: a. All suspenses not closed b. All closed suspenses c. Suspenses due within 10 days d. Suspenses due within 3 days e. Suspense due within 1 day f. Suspenses that are late g. Turnaround time by task h. Time to complete a task by organizations I. List of organizations that did not complete a task J. List of organizations that did not complete a task on time 6.3.2 The tracker application will be able to archive data within a provided data range upon request via a dialog box or form page. 7. Security Authorization Requirements 7.1 Physical Security 7.1.1 The system will reside in a protected facility provided by the 377th MSG. 7.2 Logical Security The system will use CAC/PKI to allow system access. Permissions for documents will be controlled either by SharePoint or the suspense tracker. Users will only be able to see information that pertains to them or people they are responsible for This is a hard requirement by the 58th SOW. Administrative and command staff will have visibility to all information that resides within their organization. 8. Operate, Support, and Use Requirements 8.1 System Operation and Support Requirements 8.2 Service/Maintenance Requirements Geographic Distribution System Use Statistics 8.2.1 Number of Users will be between 2000 and 2600 8.2.2 Number of Transactions will be over 500 per day 8.2.3 Volumes of Data will under 100 Meg per day and no more than 100 gig on the hard drive. If more space is needed, new hard drives will be provided by 58 SOW/SC 8.2.4 Disaster Recovery/Business Continuity will be maintained by nightly backups performed by the 377th MXG LAN Shop 9. Data Requirements Both SharePoint and the suspense tracker require a SQL Server to store documents, packages, metadata, etc. SQL Server will be provided by the 377th MSG. 9.1 User groups are as follows: Group 58 SOW Staff 58 MXG 58 OG ? 10. Test Requirements A period of one month will be provided with overlapping business processes to ensure robustness of system. All programmatic errors (at least 99%) will be resolved by the end of the 3rd month of operation.
 
Place of Performance
Address: 2000 Wyoming Blvd. SE, Bldg. 20604 Rm. B-22, Kirtland AFB, NM
Zip Code: 87117-5606
Country: UNITED STATES
 
Record
SN01400887-W 20070912/070910220751 (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.