Presentation on theme: "SDR Transformation Initiative DoD WebSDR"— Presentation transcript:
1 SDR Transformation Initiative DoD WebSDR Information Exchange under the DLMS
2 IssueAs a relatively new system, not all Component interfaces have been implemented and WebSDR is experiencing many changes that must be worked with limited programming resources.
3 Background What is an SDR? What is DoD WebSDR? WebSDR Concept Goals of Web SDRSF 364DLMS Supplement to Fed IC
4 What is an SDR?A Supply Discrepancy Report (SDR) is a tool used to report shipping or packaging discrepancies attributable to the responsibility of the shipper, (including Government sources, contractors/ manufacturers or vendors) and to provide appropriate responses and resolution.The purpose of this exchange is to determine the cause of such discrepancies, effect corrective action, and prevent recurrence.
5 What is DoD WebSDR? SDR Transformation Initiative Transitions current mixed-environment to interoperable DoD StandardDeveloped as a DLMS-compliant process, set in motion under OSD Business Initiatives Council in 2004WebSDR architecture is based upon a DAAS hub for communication and centralized data managementEliminates the need for numerous point-to-point communications linksTransaction driven process eliminates the need to re-key SDRs within separate Component systemsAutomatic reply to customer triggered by reply transaction eliminates action activity manual steps to print/mail/faxMove SDRs into an integrated transactional environment, thereby providing an effective means to report, resolve, and measure discrepancies related to pipeline performanceapproved by the OSD BIC and now under the oversight of the OSD (Logistics and Materiel Readiness) Supply Chain Integration Office
6 WebSDR Concept Phased development Benefits include: Continuous process improvement beginning at initial operating capability (Feb 2005)Working toward full DLMS compliant information exchangeBenefits include:Near real time SDR reporting for immediate identification and more speedy resolution of reported discrepanciesFacilitates interoperability internal and external to DoDSupports unique item identification and other DoD initiativesMaximizes the economy, efficiency, effectivenessFuture capture of perfect order fulfillment computationsMove SDRs into an integrated transactional environment, thereby providing an effective means to report, resolve, and measure discrepancies related to pipeline performanceapproved by the OSD BIC and now under the oversight of the OSD (Logistics and Materiel Readiness) Supply Chain Integration Office
7 Goals of Web SDR Quicker Response/Less Effort Reduces delays resulting from misrouted SDRs or mailed documentsElectronic interface eliminates data entry at action activityFacilitated web-based entry availableAuto-fill feature uses DAAS requisition history to populate SDRData content targeted to specific discrepant conditionMay be used by Military Services/Agencies (individual Service rules may differ)Contractors may use for discrepancies related to Government Furnished MaterialTransaction exchange through logistics hubILCOs (using AFSAC pilot) will interface with the DAAS/WebSDR on behalf of FMS customersDoD Component processing systems will interface with DAAS on a staggered implementation schedule
8 Business Object: DLMS 842A Derived from SF 364 Modernized systems will use business objects to transmit SDRsDLMS 842A available in X12 and XML formatIncludes data fields from the original SF 364 plus moreDLMS codes to support transactional exchangeComponent-unique data requirementsPlace holders for future enhancements, e.g., UID
9 Business Object: DLMS 842A DLMS Supplement to Fed IC DoD 4000.25-M Primary business object documentation is the DLMS Supplement (DS):The DS establishes the DoD standard format for an electronic equivalent of the SF 364/SDR.The DS provides specific business rules, conditions, and authorized codes necessary for appropriate use of this IC within the DLMS.Used to replace Component unique formats and paper form.
10 SDR Submittal ProcessLevel 2 drop window identifies conditions within selected category and completes the discrepancy codeYou must enter the requisition document number to access DAAS historical requisition information.Notice that a unique “WebSDR Control Number” is auto-assigned. If your local procedures include use of a control number configured differently, you may also include it as your “Customer Control Number.” Both numbers will be retained for the life of the SDR.You may now select the discrepancy code(s) applicable to the report. At least one discrepancy code must be entered, and a maximum of three may be entered.Due to the long list of available discrepancy codes, the codes are grouped according to categories. Sub-groupings within in each category are used to more clearly define the discrepant condition.Drop DownWindow
11 Email Distribution Confirmation copy for Web input Business rule drivenTransaction drivenCustomer responseA successful submission will provide an action copy to DoD Components which are not yet capable of receiving SDR transactions.In addition, WebSDR-input reports will trigger return of a distribution copy to the POC address (from previously entered POC information) as a confirmation file copy of the submission. You may use these to maintain a file of soft copy SDR submissions.WebSDR will also provide copies to any distribution addresses identified.
12 Discussion Resource Constraints System Interfaces Timeline Progress to dateDLMS Changes
13 Resource ConstraintsWebSDR is currently funded out of the DAASC budgetOne lead programmer with minimal other support77 Tasks PendingMonth Backlog, causing delays and frustration among user communityNew Requirements added on an on-going basisInitiative Forwarded to BTA to request additional funding
14 Systems Implementation Phased implementation beginning with initial operating capability (IOC):Ability to receive and pass SDR information using transactional exchange orAbility to create SDRs via DoD WebSDR (submission, follow-up, change, cancel, reply, request reconsideration)DoD SDR data baseLimited query capabilityUSAF, USMC,USCG, FAAPhased Implementation of System Interfaces Implemented: __________________ Development/testing:
15 Timeline BIC Project Submission September 2003 BIC Funding Received April 2004SDR IPT Charter SignedMarch 2004DLA Integration (DSS, SAMMS, BSM)January-February 2005AFSAC ImplementationNovember 2005Army Quick FixOctober 2006GSA Report InterfaceTBD –basic programming completedPDREP InterfaceTBD – initial programming completedNAVSUP InterfaceDecember 2006Army Full InterfaceTBDEMALL/Warfighter InterfaceUnavailable due to IA interfaceUSAFAwaiting ERP Development
16 Progress to Date Operational interfaces via transaction: DSS (842) BSM (842)AFSAC (842)CDCS (legacy)Limited query capabilityWeb Inputrouting/distribution copies
17 Related DLMS ChangesADC 158: Clarifies pre-positioned material receipt (PMR) requirements. Receiving DD required to submit SDR to ICP when new procurement material is received without prior PMRADC 174: Enhances Item Unique Identification (IUID) capabilityADC 184: Establishes new type R SDRs (properly routes discrepant Redistribution Order shipments identified at receipt to the DD that shipped the material)ADC 187: Enhances system capability to forward SDRs sent to wrong action activity back through WebSDR to correct action activity
18 Related DLMS ChangesADC 188: Establishes new Quality related discrepancy codes for DD to notify ICP regarding specific quality related issues (receipt & storage)Q11 = Returned or stock screen item, PQDR exhibit deficiencyQ22 = New procurement receipt, customer return, redistribution order or stock screen item quality deficiency, contractual noncomplianceQ33 = Returned, redistribution order, or stock screened item suspected material deficiency (DLA CRII items only)Q44 = New procurement receipt, customer return, redistribution order or stock screen item contracting deficiency, for specification and/or technical data deficientQ77 = New receipt, customer return, redistribution order or stock screen item identified as a Critical Safety Item (CSI)Q55 = Item under investigationQ66 = Customer return or stock screen item failed under useQ99 = New receipt item received for “First Article Test”
19 Related DLMS ChangesADC 196: Establishes new rules and WebSDR capability to route SDRs resulting from DLA-directed lateral redistribution of NAMI-owned (AJ2) material to NAMI for initial processingPhased implementation; programming in progressProgrammatic recognition of LRO under TAV with routing to NAMIADC 206: Establishes new discrepancy code for discrepant wood packaging material (WPM)Implemented September 1, 2006ADC 207: Establishes new discrepancy codes to identify discrepant hazardous material at receipt or in storageEffective 1 October
20 Related DLMS ChangesADC 210: Enhances web-entry for specific user groups:Defense Reutilization and Marketing Service (DRMS): Gives DRMS capability to distinguish different types of SDRs, e.g., sales, donations, demilNational Inventory Management Strategy (NIMS): Allows NIMS sites to properly identify their submissions for DD/ICP processingNon-DSS DD: Allows storage sites to submit type 8, 9, R (depot receipt type) SDRs directly into WebSDR to be routed electronically to the owner/manger/shipper as applicable
21 Related DLMS ChangesPDC 230: Establishes new discrepancy codes for discrepancies related to passive RFID tagsPDC under development for DAAS edit to systemically reject SDRs with invalid document numbers back to submitter or submitting system (establishes duplicate criteria)PDC under development for new query to identify/measure DLA Customer Interaction Center input on behalf of customer (hard copy or other reporting method)
22 Next Steps for WebSDR Electronic interfaces with Service systems: AFSAC-A operational; improvements ongoing – expand to other Service ILCOsTwo-way communication with AEPS (Army)Testing DLMS X12 XML interface with NSDRS (Navy)Testing DLMS X12 interface with PDREP for DoD-wide distribution of SA quality reportsComplete interface with GSADevelop management reports and ad hoc queries (better & more functionality)Associate financial view (debit/credit) with discrepancy report queryComplete implementation of DLMS Changes and ongoing enhancementsSupport BTA submission for fundingPrioritize programming requirements