Hello dear learners, welcome to today's program. I am Dr. Pallavi Gugoy of Padmanat Kuhaybara School of Humanities, Peshna Kander Handik's Theatre Pen University. Today I shall take up Unit 15, titled Story Writing, where we shall discuss samples of stories. This is from the Foundation course in English, semester 1, block 2. So let us quickly begin. First I shall start with table of contents. Starting with the learning objectives, followed by sample stories. I have selected two stories for this particular video, followed by questions to check your progress and preferences. Now come to your learning objectives. After going through this unit, the learner will be able to gain a better idea on the techniques of story writing through the given samples and also appreciate some of the basic important techniques of story writing. First let us take up a sample story. Let us take this extract from our story written by Guidey Mopasam. I am sure you must have heard his name. Quote, Along all the roads around Godaville, the peasants and their wives were coming towards the town because it was market day. The men were proceeding with slow steps. The whole body bent forward at each movement of their long twisted legs, deformed by their hard work, by the weight on their plow, which at the same time raised the left shoulder and swerved the figure, by the reaping of the wheat, which made the knees spread in order to hold the wheat firmly, by the slow and painful labours of the country. Their blue blouses ornamented with a little design in white at the neck and wrists puffed about their bony bodies, seemed like balloons ready to carry them off. From each of them a head, two arms and two legs protruded and they walked with a quicker and livelier step than their husbands. Their spare straight figures were wrapped in a scanty little shawl, pinned over their flat bosons and the heads were enveloped in a white cloth glued to the hair and surmounted by a cap. The short story from which this extract is taken is a piece of string by Gayati Mopasam. While writing a story if you wish to describe a character from an output perspective, you could give details of the character's dress, build, facial expression, movement and so on. However if you wish to describe what the character is essentially, in that case you could refer to qualities of the characters personality such as intelligence, courage, arrogance, honesty, nervousness and the alike. You could use outward details such as mesmerisms, action, relationships and speech as evidence of the character's internal traits or qualities while writing a story. Also you could want to concentrate on the dominant feature or describe several complementary features of the character in the story. Let's take another sample. Now let us look at a description of a scene as observed by a lady from a hotel window in Italy in this particular story by Ernest Hemingway. There were only two Americans stopping at the hotel. They did not know any of the people they passed on the stairs on their way to and from their room. Their room was on the second floor facing the sea. It also faced the public garden and the war monument. There were big palms and green benches in the public garden. In the good weather there was always an artist with his easel. Artists liked the way the palms grew and the bright colors of the hotels facing the gardens and the sea. Italians came from a long way off to look up at the war monument. It was made of bronze and clenched in the rain. It was raining. The rain dripped from the palm trees. Water stood in pools on the gravel paths. The sea broke in a long line in the rain and slipped back down the beach to come up and break again in the long line in the rain. The motor cars were gone from the square by the war monument. Across the square in the doorway of the cafe our waiter stood looking out at the empty square. The American wife stood at the window looking out. Outside right under their window a cat was crouching under one of the tripping green fables. The cat was trying to make herself so compact that she would not be tripped on. Now the tech source of this particular extract is from the story Cat in the Rain by Ernest Hemingway. In the extract many concrete details are used to describe the young man. These details help you to form your views about the person's character. You are to go through this particular sample once again to get a better idea of the same. Now let's quickly come to questions to check your progress. Question number one, what are some of the aspects that you would highlight as a story writer if you are to provide only the basic highlights of a character? Question number two, what are some of the aspects that you would provide in details if you are to provide an essence of a character in a story? Question number three, develop each of the following outlines into a form of complete stories. If you notice here are the incompleted outlines. You have to complete the same. Starting with number one, a grandmother celebrates the birthday of her four-year-old grandson who is far away in America with his parents. Hosts of guests and relatives arrive. Meribund. Grandson brings up his father. Grandmother greets happy birthday. Guests depart. Grandmother breaks down in loneliness. Now here's the second one, three schoolboys run off to the nearby river for a swim. The strong current carries away one of the boys. The other two shot for help. A fisherman leaps into the water. The boy's saved. Fisherman refuses reward from the father of the rescued boy. So you have to complete these outlines of the stories using your own imagination and creativity. Here's a reference I hope you'd go through the BA English Graduate Self-Learning Material SLM, a foundation course in English, block 2 unit 15 semester 1. Thank you dear learners.


My name is Jamie, I work for Cardinal Healthcare as a child support worker. I've worked for other care provider companies that provide care for people with autism, adults with autism and other additional needs.


Here's a quick tip on the Blackstar LT metal pedal. This tip is about dialing in a crunchy tone that's suitable for chugging along or playing metal tunes. The gain is set to above 12 o'clock so we can get a good amount of it. The level is set to above 12 o'clock so that we can hit the front end of the amp to help it misbehave, while the ISF is set to the left. When the ISF is set to the left, it's a little bit more snarly, brighter, and somewhat more how an American EQ would react. Lastly, the tone control is set up above 12 o'clock for even more high end definition. In this case, the pedal is going to hit the front end of a clean amp. Here's the tone of just the clean amp. Now let's engage the LT metal pedal.


to where we get, you know, how far we, so let's get started. All right. All right, welcome everyone to the TSC call. I see only a familiar name, so I assume you all know this is public call. Everybody is willing, is welcome to join and contribute. And this is not a figure of speech, by the way. I mean it. And so you all know the antitrust policy notice by which we must leave it. And the code of conduct, of course. So let's get to the agenda. And Gary has joined, so we have a full house, pretty much. Not quite, but enough anyway. All right, so there is some announcement that was inserted in the agenda and I will let Dave talk about the TSC election nomination. Thank you, Arno. So we are nearing the end of the nomination period for the 2020 TSC election. It closes at the end of the day, well I'll say midnight on the 19th. So this is our last chance to go and recruit people for nominating themselves or to nominate people to run for the TSC election. Once again, the way to do that is to email election at list.hyperligio.org and say, hi, my name is Such and Such, this is my email address and I would like to run for the TSC. We are currently sitting at 14. I haven't looked at my email yet this morning, but we have 14 nominations for 15 seats. So we still have one totally wide open seat. And yeah, this is our chance to encourage the people we'd like to see in the technical leadership of Hyperledger. So please spread the word. Okay, Arno. Thank you. So the next piece here is mine. This meeting will change soon. All meetings will change soon. Zoom has changed the way meetings are done. All meetings shortly will have to have passwords. So you will be getting new invites to pretty much every meeting that you have. So I'm gonna after this meeting, I'm gonna cancel the TSC meeting and I'm gonna replace it with another invite that has the new information. So that's just heads up. Can we wait a few weeks for the new TSC to be in place to do that at the same time since you're gonna have to update the... I think it's the 25th is when Zoom starts enforcing this. So I don't have control of when Zoom flips the switch. So no, not really. Arno, I just wanted to announce I just got one more self-nomination for the TSC. So we have 15 candidates for 15 chairs. So unless we get more nominations, it's pretty much a shoe-in for everybody. Yeah, we haven't really planned for that, but I guess if that's really, if that were the case, we don't have to have an election per se, right? We can just declare it or even... We still need to have an election per the charter. So we'll actually, what, the TSC gets to select the... Yeah. What should we do? Let's do this once we find out whether or not we have one more person. Yeah, we'll wait if we face that situation. Sorry, Brian. No, that's it. Just saying, we'll deal with it then. Yeah, I'm sure the charter outlines what to do, so. All right, thank you. Anything else on the announcement piece? All right, if not, moving on to the quarterly reports, I assume you guys saw, we just received a report from the borough project, Simon sent out an email to the TSC list. It's kind of big in the way he described the situation. He said he might join next week. I don't think we should get too much into this now, but we want to make sure people are seeing it. And I have to say, I appreciate this, you know, how candid he is in his report. And so please have a look. We are missing Avalon, but, you know, it was due today, no big deal. Hopefully we'll have it by next week. So that brings us to the issue at hand. We have one real issue we wanted to have this call for today, which has to do with the request from the Bezu team, hereby represented by Daniel, to be allowed to use Cal there instead of SEM there. There was a bit of, so thank you, Daniel, for putting the proposal on the wiki. There was a few comments. So I know that quite a few people have actually looked at it and commented on the wiki page by far not everyone, but, and then I do want to point out that Daniel also posted, he actually submitted a PR against the taxonomy, the release taxonomy document on GitHub. It's a draft PR. It constitutes a slightly different, I'm sorry, it's a draft PR against my own fork. So it's not formally yet. Oh, yes. Okay. Yeah, yeah, it's not been submitted. You're right. Thanks. But it's slightly different because it goes further. The proposal as described on the wiki is to allow Cal there in addition to SEM there. The draft PR that Daniel put together goes beyond that in saying, okay, SEM there is the default. Otherwise, use something else, but make sure you define it and there's a set of criteria. But I just want to highlight and I put that on the TSC channel that it's a bit different. It's broadening the proposal. So who wants to say anything about this?  I think the reaction I've seen is some people feel like it's not clear the change would solve the problem they have. And I will let Daniel speak to that. The other part was Dan came up with some suggestions to use some hybrid model. And then there was a suggestions which I guess the draft PR is defined with by Gary to just give up on dictating the release taxonomy. So that's, we have a whole range of possibilities, you know, facing us. So Daniel, why don't you explain a bit more? Yeah, sorry. You were going in the exact direction. I was going to ask that Daniel take the floor and give the next question. Okay. So Daniel, I think it'd be good to explain why you think this would solve your problem, especially the caliber at least. Right. So caliber is a numbering convention for releases. It's getting a lot of traction in various places. If you've ever used Ubuntu, you've been using a piece of software that's been calendar version. And other projects have rather than semantic version rather arbitrary numbering systems. The Linux kernel is famous that every so many releases, they just bump the Mac primary never because that's what they do. So my initial proposal was very focused on just say, let us use caliber and let us give some reasonable definition of it. And I wrote down what the issues were. But as I was reading and I think it was Nathan George's comment or Gary's, I realized that rather than specifying it, perhaps we just need to specify what a release policy the concerns or release policy needs to address. So that's what my point of my revision is. As I say, your default is Denver if you do nothing. If you want something else, you need to write up a policy and document it. And it needs to have a clear reason for clear philosophy of what your numbering is. It must also address forward and backward compatibility. And there's a couple of shoulds that you should use the tags because those are easily understood and you shouldn't just name it off characters in Toy Story because that confuses everyone. But those are two or two or shoulds that the two musts or that must be documented and sensible that it must address forward backwards compatibility. So, if we were to go with that in basic, we would probably go with a year or year dot quarter quarter release. And those two numbers together would represent where backwards compatibility is not guaranteed. And the second number is where we would introduce new features. And if we ever did, I mean the third number is where we'd introduce features and if we ever did a patch that did introduce features that was like fixing a critical bug, we might do the fourth number. So that would be the Bayesuit numbering. One of the reasons why this is quite interesting to us has to do with Ethereum 2.0. There is a bit of concern that if we do a Bayesuit 2.0 and it's an Ethereum client, people will say, well, does it support Ethereum 2.0? And it doesn't because it's wildly different. Ethereum 2.0 is just a proof of stake system currently that's being released possibly by the end of the year. So by going to a Calvary system, we can rather than having everything be one dot, a billion, we just use a numbering system that reflects the current year and the release within the year. And it goes up at a sensible pace and it's got a reasonable philosophy as to when we increase the major number, which would ideally be the year. So that's the essence of the proposal. That's what Bayesuit tends to do is to go to a Calvary type version, but as far as the general hyperledger policy, maybe the easiest thing to pass would be to say that you must define it, but you need to define it and it needs to handle backwards of forward compatibility or you should use Semper if you're happy with Semper. All right, thank you. Any reactions or questions? I think Chris has his hand up. So again, I'm not at all clear how this solves your problem, but that said, an argument for why we chose a strategy as opposed to really your own strategy is for some consistency across the hyperledger landscape or greenhouse and so that people could not be confused, introducing additional approaches letting each project essentially choose its own only further confuses people looking at hyperledger and looking at the SWAT feedback from the member summit strongly suggests to me that the confusion around things is one of the biggest impediments that we have. And so I'm not at all clear, given that I don't believe at all that this solves your problem that we should stay with what we chose, I don't know, four years ago, whatever, five years ago. I don't see a compelling reason to move off of it. I don't think we're doing a good job following it because no projects define their public APIs and there's no strict enforcement of my feature as, of course they do. Maybe they don't define their public APIs. Fabric has its documented. Is that the only one? I don't know, but you said that none of them do.  I mean, but again, I mean, part of my point was but we have a lot of reasons why we have to do that. And this is going to be similar to, Dan Oye, you know, you have similar situations too, right?  We do denounce like breaking changes in one case where we had a security violation and things like that in the release notes, but we're pretty strict on that, right? That we don't break stuff across the two-digit you know, boundaries, right? We're not as strict on back porting releases and dot releases sometimes, but we are on the compatibility one, but I guess anyway, I'll, so that part I think is fine, but. So the backwards compatibility is an interesting point. We generally don't do multiple release streams as well. So if we were to stick with one five and one six and one seven and one 2000, that might imply that, you know, you can have some expectation we might support older versions, which very much fabric does, but Bezu, it's because of the nature of main net Ethereum, there's one main net that we need to be compatible with and we can't support multiple streams with backwards compatibility because there's one current chain definition we must be compatible with. I think if you had enterprise users for Bezu who ask that you issue a patch release on an earlier branch, even though you've main net has moved on, you'd probably take that option, right? You'd create a, even if main net and everybody there was on 20.4, if somebody was on 22 and there was a assert notice published, you know, there'd be presumably networks who it might lag by a few quarters just because upgrading everyone is tough. And, you know, then the Bezu developers can make the choice of issuing a patch release on an older stream, right? Right, we can, we haven't done that yet and I think we would give them a bit of pressure of it should be backwards compatible with your genesis flags to go back and do the same. But you would issue a 20.2.1 or 22.2. And even though it was the fourth quarter of 2020. So what we would define as it would be the year-to-year and then the quarterly or whatever breaking level release we would do. So it would be incremented by one for each breaking release we do, probably three or four year. That's a process for all the users too. You wouldn't force users to go past a breaking release just to get a security fix. And if it's a security fix, we probably would. Yeah, so that's a good point. I think that's the main concern from an enterprise point of view is, you know, that enterprises do value that stability and there's substantial cost for the upgrade. Of course, it swings too far in the other direction. Sometimes we still have, I think too many users out there on old versions of some of our releases. So nudging them forward is great, but from a security and pushing out responses to certain notices and that sort of thing, kind of point of view, just knowing that that's an option there, that Calvary doesn't discourage that is good to know. You're right, it doesn't prohibit it. And in security, I didn't think about that level. We would put whatever passes out in production. It's non-security that we would drag our feet, probably ultimately do it if they're persistent enough but strongly encourage them to come up to mainline. But to a degree, right? I think it also depends on, but this is where, you know, I guess, yeah, I think that's where, you know, having the options didn't make sense. But look, and I know I'm like sometimes a broken record on this, right? But open source is not the same thing as commercially supported projects. And that's where I always like, you know, come down to the thing. I mean, yeah, so people can choose that and you know, the relationship of, you know, consensus and teams to Vesu, right? And they can choose how or whatever it becomes, Quorum or I wouldn't figure out what your product name would be, right? But it's up to them, right? I mean, we choose like, you know, mainly to keep things from a simplicity perspective, right, across the fabric community and working with like, you know, Oracle and others who do that, right? We try to, you know, we try to maintain the same thing that we're committed to doing from an IBM perspective because it's stupid to, for us to maintain forks and branches and whatever internal and IBM and all this aggressive stuff. And I'm fundamentally lazy, right? So we choose to do it that way, right? But you have other places, right? That are more confusing, right? So like Red Hat, right? You know, like, I mean, Red Hat has a similar thing, right? Which is very confusing for people, right?  And 3.9 was like whatever, but then it was never upgraded. Now they have a strategy where they have 424344 and those map to different Kubernetes versions, right? Like 1.13, 15, 16, 19. So I guess I always get on this thing that everybody assumes that everything that comes out of here is like, has to be managed and maintained and supported like it's an enterprise stuff. And that when an enterprise customer chooses to use open source that they're gonna go get this same level of thing as if they got enterprise support. I just disagree with that as an assumption that we should be propagating to people who consume our technology. All right, Dave has had these hands raised for quite a while. So let's get to it. Thanks Arnaud. All I really wanted to say was that I like Dana's idea of having a defined release policy. And I just asked that that release policy include some language around promoted releases as per the rules for promoted releases. Those are special and it causes the hyperledger community to spend real money on security audits and marketing and all of that. So if we do have policies, we need to define that so that we know when to ask for promotion and stuff and everybody knows what to expect. That's an interesting point because I don't think the current policy says anything about that, does it? Yeah, I thought that was maybe the truth. Promoting is defined as a December requirement. Yeah, correct. There was a, you know, hey, in general hand wavy, you know, major numbers were promoted releases, but we've seen promoted releases for fabric to 1.4, for instance, and there's one for 2.2. So yeah, I just wanna, I just wanted if they're gonna do like Calver or something else, just I guess maybe they don't need to explain how it ties to their versioning, but just what they expect to do, yeah, nevermind, you're right, there is no December requirement. I retract my statement. We can just go with, hey, we want this to be a promoted release and petition the TSE for that. Okay, so I have to say, I mean, I haven't expressed myself on the proposal. I, you know, I'm kind of in two minds, so I'm not going to make much of a difference, I suppose. You know, on the one hand, I agree with, you know, sensitive to the point that Chris talked to, which is, you know, we don't share that much stuff between the project. One thing that we've been trying to do is have more homogeneity or harmonization between the different projects. And this is kind of what, you know, going in the opposite direction. At the same time, I also feel, you know, there's no, I mean, there's no harm in and of itself if a project wants to use Calvair. I'm not sure that, you know, I would jump the gun and open it all up all of a sudden just because, well, then, you know, because we have two now, let's, you know, allow for anything. I mean, we, I'm not sure, you know, we need to be that blunt if we decide to open up a bit and say, okay, you can use either same there or Calvair. At least we have two well-defined entities. If we say something along the lines of what the draft PR that Daniel put together, you can use whatever you want as long as it's documented, basically. I'm afraid that's like, it actually puts a burden on us to then check that the projects do live by this. While if it's just a flag, you use Calvair or same there, it's still pretty simple. So, and you know, I'm happy for to stick to Calvair and same there for now. And if somebody came up with something else, they really want to use and they have a good reason. They can always reopen and we might add that to the list down the line, but I'm not sure there's a need to open it all up, but it matters. So I'm kind of like, I'm not sure we should do Calvair for the reasons I said, but I'm open to it, but I'm not so open to, you know, leaving it completely open. Totally agree. So there are quite a few people we haven't heard from. If I might, again, I'm in the uncomfortable position of being unable to raise my hand here.  I understand that this is becoming surprisingly contentious, but I would just ask the TSC to consider whether they really want to be involved in every little decision like this. Anyway, I'm done. Well, presumably it's not a little decision. So there's a lot we don't get into, right? Sure. Okay, but we haven't heard from people like Tracy, for instance, who commented on the Weki page, but, and I see Sweta has joined us. Welcome. Yeah, Arno, I'm kind of in agreement with you, right? Like I feel like the PR is too open.  It's going against the consistent nature. Like it means having to learn another numbering scheme for Hyperledger project. And I also, I think Nathan's comment on the chat, right, about what we're really concerned about is the stability, dependability, knowing like what it means when something dot, something dot, something happens, right? Is it just a minor fix? Is it a major fix? Is it a breaking fix? Those are the things that people are concerned about. And I guess with something like Calfer, I haven't yet been able to wrap my mind around exactly what each of those things means. You know, how do you number in Calver? Cause when a minor fix happens versus a major fix versus a break fix, right? Like a new year doesn't tell me that's a break fix. You know, a new quarter doesn't tell me that's a major fix. You know, it just, there's nothing there that maps in my brain to what we currently have within Hyperledger. And so I think, you know, that's a, that's an education, an additional education that we have to do to users of Hyperledger projects. All right, thank you, Tracy. Anyone else? Nathan has his hand up. Yeah, Nathan. I think it's easy to read too much into version numbers. Users of software usually have to test open source packages to know whether they're gonna get what they expect or not. Because if your use case is different than the main core project maintainers, what they consider a minor change might be very significant to you. So in projects that I've participated in that have used Calver in the past, it hasn't really disrupted or changed much in terms of the dynamic of the project. My interest here is that we still are promoting and preserving that culture of stability and dependability. And using a version numbering system that's somehow rational that, you know, the maintainers can have a civil discussion about whether a version should be revisioned or not and doesn't turn into a food fight. So I don't have any problem with Calver. I do also like what Dan's saying of, we probably don't wanna just open it up to any possible versioning number scheme because we want something that is familiar or comfortable for the general open source community to consume. And both Calver and Sember are broadly enough adopted and supported that when people see those version numbers, they'll be able to figure it out. So, you know, if they want something else, I'm happy having someone say, here's how we wanna do it because maybe someone will invent a new something for that we haven't thought of yet. But that's what I'm hoping we can move forward with, but I don't know where everyone else is. So. All right, thank you. Anyone else? Yeah, I know this is not just my hand. Yeah, go ahead. That's fine. Yeah, personally, I'm not a big expert with these two things, but I was feeling from another prospect. So, from a blockchain point of view, what it means for an adopter, an adopter when there is a versioning change or there is a bug fix, even a bug fix can produce a fork in the network if the rest, if you don't tell me how to upgrade my network to the new version, even a simple bug fix can create a fork in the network. So, what I personally will be concerned is, which are the rules? Do we make sure that when you really, when this project are releasing a new version, are they telling the people how to upgrade the networks? How to make sure that if I have an Ethereum network with the nodes of different versions, no matter what's the versioning or the meaning of the version, but they will not fork. I guess that's the most important thing to me for a blockchain system. Repeat, even a simple bug fix can produce a fork if the network is not upgraded properly. All right, thank you. We also have the hot on the queue. Hey, sure, thanks. Yeah, I was going to sort of, I guess, agree with Dan Middleton here.  And I think if we have people that are sort of looking at stuff and they see like a Calver, you know, numbering scheme, you know, I don't think that's something that people are going to struggle with. I would probably push back against, you know, sort of, you know, a more general proposal. We've had fun in the chat defining arbitrarily adversarial numbering systems.  All right, thank you. So I'm hearing pretty loud and clear, you know, agreement towards not allowing, not opening it all up completely. There's some reluctance to moving towards Calver, but there seems to be a majority in favor of it though. And so I just wanted to ask, so I think we can discard the draft PR that I'll put together and go back to the actual proposal that's on the Wiki that Ray is displaying right now. And my only question is, so do we need to say more about how Calver is used and the potential impact like Angela was talking about? Or do we leave that to the projects? I think you have to leave that to the projects, right? Because like for Ursa, well, I guess it would depend. But for like Ursa, for example, right, why would it care? Somebody who consumes Ursa will care if Ursa introduces a change or whatever and has to put it in their release notes or whatever, but Ursa doesn't really, you know, I mean, not everything's a blockchain, right? No, but I guess I know, but I was thinking maybe along with the, you know, allowing Calver, we could have wording. I don't know if it's in there. Daniel, something about, you know, being clear in the communication of what breaks backward compatibility since it's no longer part of the versioning. Oh, get it back. Can I say something? Get it back here. I'm not sure if I got to what you said because if Ursa changes the signature scheme and signatures that before were considered valid are not valid anymore, this can cause a problem if you upgrade your fabric network to the new, this new version of this signature algorithm. And then you might start saying, oh, what's happening here? Now certain nodes might reject, certain nodes might accept. So that's- What was it applicable to fabric but not to Ursa? Ursa can do whatever it wants. If Ursa screws around, bust something, changes something, does something bad, and it screws with fabric, then fabric either says, Ursa, go change it if we were using it, for example, we're not even using it, or we go find something else. The same thing- No, no, no, no. The same thing- No, no, no, no. Go TLS in 1.15, right? Yeah, yeah, yeah, yeah. I mean, there is an info. For Ursa itself, I agree. We don't care. So who is using Ursa? Should be care very much about what's happening, because as more change can produce a fork. I just think we're putting way more into release numbers than actually matters from a degree. I think everything should have a policy, and anybody who doesn't read release notes on enterprise, commercial, and especially open source software, if they have release notes, doesn't know what they're doing. I agree with this. The problem is another. It's the compatibility. That's not the version. I agree with that. Yeah, but okay. But so I think this is, I agree with Gary in the sense that there's a certain amount of that that's going to be project dependent, and we don't have to get into this as far as the policy is concerned. So I would advise people to look at a rise screen. The formal proposal, I'm leaning towards putting it for Molly and for vote. And the question to me is going to be like, along the lines of using Calvary, it sets a set of criteria that needs to be met for projects that would opt in to use Calvary. And are those the right criteria? Dan, I'm sorry, I saw you raised your hand. Did I take care of? No, you said what I wanted to say. We were starting to get into the minutia that Rai was warning us against. And I think we're ready to take a look at the actual text, which is I think the first four bullets of the proposal there. Yeah, okay, cool, thanks. So if people have a problem with one of those bullets, or if some additional bullets are needed, I think it would be good to say so. But now we're down to like refining the proposal before we put it to vote. I think Dan had concerns about the first bullet, if it's really necessary. Do we care if it's a library standalone program or does it just matter that the project opts into it? Yeah, I'm inclined towards less is more that we can be unnecessarily prescriptive and then have to come back and edit this, so. Yeah, that's a good point. I would agree with that. Dan, do you want to do the edit or do you want me to do the edit? Yeah, there are suggestions for changes. Yeah, it's better. I might as well do it right. Thank you. That way we can all see what you're doing. Okay, there we go. Freeing me if you was corrupt. I'm so used to that. If we're going to formalize that, should we? The parts before the bullets pull us, projects that opt in should meet these criteria. Since I was kind of vague about it, if we're going to make these criteria, we should probably make the header just reflect that. That I should or I must. Right, have we ever? Must, yeah, good point. So which word needs to change here? Projects that would opt in would need to meet these criteria, Colin, and some to these. Some to these. These need to meet these criteria. Thank you. And you just said we should change would need to by must meet. Must, yeah. I think that applies to the shoulds below as well. I'm looking for the other should, I'm sorry. There's three bullets down below and two of them have shoulds. There you go, right there. Yeah, maybe the last bullet, there must be some period of backward compatibility. So that should be a should. I've got a drop. Well, okay. I was hoping to get the vote in. Yeah. I think a should is reasonable for that one. But you can put should exist at the end instead of again. There should exist some period of backwards compatibility. Yeah. Should exist. There we go. I mean, I imagine like if there was a security problem that breaks by question, but if you don't like want to break the day, then you have a good reason to break it anyway. Okay. Me. Any chance that we could get a vote in before we lose one? I moved to vote. That's what I'm hoping for, right? So we, I heard, was that Dan? Yep. All right. Anybody wants to second that? I can second it. Okay. All right, thank you. I'll do a roll call vote. Angelo. I second. Arno. Yes. Chris, we lost. Dan. Affirmative. Gary. Yes. Hart. Yes. Mark is not here. Nathan. Yes. Swada. Yes. Tracy. Yes. And Troy has his regrets. The matter passes. We still have quorum, right? We lost, Chris. That was still eight. Yep. That's still eight. Okay. Cool. All right. That's it then. It's passed. So then we'll have to, I mean, Dan, can you update your PR to reflect this? And yeah, I'll update the PR and I will push it to the repo for form consideration. Yeah. Very good. Thank you. All right. So it's hereby approved and we have a plan, action plan to update the documentation accordingly. And I think we can close this call on that. Thank you. Good discussion. Thank you very much. And I think we made progress. Yeah. Talk again next week, I suppose. All right. Goodbye, guys.


Other revenue aggregation rules, like right of return, repurchase agreement, bin and hold, age and relationship, consignments, warranties and non-refundable. In fact, you look so, number of businesses we are involved. So each business has its own way of recording the revenue. So for example, consignments, goods you sell it, send it to the consignee, consignee, goods send consignee to consignee. The consignee is not a sale yet, unless the consignee sell it for you and render accounts that he has sold this much and this is the money we share, only then it can be recorded. So in every case, bill and hold, they ask, get into an agreement and says, look, you bill us, but keep the goods unless we say where to deliver. So again, question arise, when to receive, when to record revenue. Similarly, return or sale, it happens that you're leaving the goods on the premises and says, well, you sell it and if you won't sell it, then return it. So that's again a problem. So this is how these are small, small things, but you have to go through the text for each and every item, how to record revenue when these are the things. Now let's see other. Types of transaction, description of revenue and timing of revenue recognized. Sale of product from inventory, revenue from sales, date of sales or date of delivery, very clearly. If you are selling the goods then it should be date of sales or date of delivery. Performing a service, revenue from fees or services, service performed and billable. Sometimes you perform the service, but the other party is not agreed, is not happy about it, so you can't bill it, so unless it is billable. Permitting use of an assets, revenue from interest and royalties at a time passes or assets are used. For example, you deposit money in the bank. So bank will pay you interest on the basis of time. Whatever rate agree, but the time passes only then you will earn their interest. Sale of assets other than inventory, gain or loss on disposal, the date of sales or trade in. So these are the basics rules. Thank you very much.


Hello again, nice to see you back. In this module, you will learn the importance of managed storage of university records. Although some units will find secure storage space at their office, others will require off-site storage. In this module, you will learn the importance of, 1. Managed off-site storage of university records, 2. Sending records to off-site storage, 3. Recalling records from off-site storage. Let's get started. Look familiar? Remember our infamous messy closet from an earlier module? Some university records in basements or closets might be convenient, but those places often lack physical and environmental security. You might not know who has access to the storage area, or forget what information is in those boxes. If the content of the boxes contains personal information, by law you must protect that information. Additionally, folks could accidentally destroy valuable records because they were not aware of what is in the boxes. Storing records in a closet or basement is not wise.  But even with proper security in place, the person responsible for the records might leave their position or simply forget about the records. When records are unmanaged, it is easy to lose track of them. Sending university records to UBC's managed storage is recommended because, 1. The records are both physically and environmentally secure, 2. And the retention and disposition is managed for you. You might ask, what is UBC managed storage? UBC provides fee-for-service managed storage to ensure the security, access, and disposition of university records is done properly. Remember, the records management office at UBC manages and destroys off-site records according to a retention schedule. The RMO will provide you with notification prior to the records being destroyed. You don't have to worry. Okay, here are the steps in the process. Step 1. Set up an account. Step 2. Get two documents for storage. Step 3. Call for pickup. The first thing you'll need to do is set up an account by contacting your campus records management coordinator. On both campuses, you will receive a setup package. This package contains two documents. The first is an authorized records access application form, and the second is a record storage template. Complete the authorized records access application form and return it to the records management coordinator. This form asks you about access authorization and billing information. Once you have an account, you're ready to go. Next, you will need to gather the documents to be sent off-site and place them in boxes. Make sure you have standard-sized boxes and only reuse boxes if they are in good shape. No broken handles, please. The records management office's website contains details on where to get the proper boxes. Pack the boxes with the folders upright as if they were in your filing cabinet. Fill your boxes to capacity. But do not overstuff them. Never lay folders flat in the box. Don't include hanging folders or binders or any non-record material. Be sure to store records with the same retention period together. For example, don't mix financial records with a seven-year retention with a group of committee meeting minutes. They have different retention periods. When completing the records storage sheet, provide a numbered file list with the following information. 1. A brief summary of what's in the box. 2. Records date range. From date. To date. 3. 4. Box number. Mark the box numbers at the bottom right-hand corner of the short side of the box. When the records management office picks up your boxes, an official UBC record storage barcode will be affixed to the box. Contact your records management coordinator if you need help. When the boxes are ready, send your records management coordinator an email to request pick-up. Attach the completed records storage sheet to the request email. The records management coordinator will reply with a pick-up date and time. Once the boxes are picked up, we label them with barcodes. You will then receive a copy of the records storage list, which includes the barcodes and location codes of those boxes. You should refer to these barcode numbers when requesting retrieval of boxes. Contact your records management coordinator if you need to retrieve boxes. The records management office at the university archives is available to help you with your unit's off-site storage needs. Check the resource section of this course for contact information. Let's recap this module. 1. University records require management. 2. Using a closet or basement to store university records is often poor security. 3. Records should be destroyed according to a retention schedule. Let's now do a quick quiz to see what you have learned.


ry short uh I'll just I'll summarize it right since we're done with the armor for series we're going to be finishing the Unreal Blueprint stuff and once we do the Unreal Blueprint stuff as soon as I figure out how to make as soon as I figure out how to make a small little project because when it comes to game design there's a lot of there's a lot of stuff that has nothing to do with the engine we have to figure out how to do so for example let's just say we made our game in Unreal right let's just pretend that we somehow we knew how to do all the animation stuff the Blueprint stuff, physics stuff the special effects and the animation um you know IK control stuff or whatever let's pretend we know how to do all that stuff we still need to figure out how to export the project into a game file we still need to figure out where we can post that file like because I know like making that posting a game on Steam is not easy you have to basically spend like a whole two days setting up a page for it and even if you want to post it on itch.io you kind of have to follow a few settings right like it's a lot more lenient on itch but we need to learn how to export it from Unreal we need to learn how to upload it to a website that people can actually play the game on and then you got to you know you got to spend time promoting the game and talking about it and sharing it right and then you spend the rest of your life literally like maintaining it and updating everything all the time but uh yeah so there's a lot of work to that has to go into even just making a small simple project and I'm gonna try so we're gonna start with something small and fun and I have an idea and I guess you know I will I'll let you guys know I have a I think a fun idea for this little project that I think would be interesting for you guys to watch and fun to play but um I want to make like a really fun it's like an RPG well it's not really an RPG it's kind of like a small it's like a turn based Rock, Paper, Scissors fighting game but with like random characters from like the community right uh you know I would make the first 8 characters just because you know just to start it off but I do like the idea of having eventually like a little project where you know depending on if people have finished the character plug it in as long as they follow the same under the skeleton and everything um but you know that's kind of like a project we'll be talking about that stuff like later on as we go but no there's a lot of cool stuff we just have to figure out how to use Unreal first that's the thing right now I'm still new to this to the software I'm new to the engine I don't know how to do some basic stuff that you would need to make the engine um but once we figure that stuff out then that's when we can really kind of go crazy and we can do you know fun stuff like we could just download some 3D models of some F-22 Raptor airplanes and then some 3D models of some Pegasus knights right and then we can just have Raptors fight Pegasus and and just see who wins right like we could download Tyrannosaurus Rex and have them fighting a tank and we could have a team of tanks fighting a team of I don't know like Pac-Man or something like that once we know how to do the engine stuff there's like so much we can do but we have to figure out how to use the engine first and you know I would like to be able to get to a point where every time we have a fun little project like a random idea you know I could open it up to you guys in the chat and we could just have all 30 of you just you know playing together in like a 15 on 15 scramble of 15 T-Rexes vs 15 Pegasus knights right like something like that you kind of see where I'm going here that's kind of the idea like once we've figured out the engine we'll be able to have a lot more fun and do a lot more interesting stuff with it but right now we're kind of stuck in the boring part of figuring stuff out we're still trying to figure out how to get an object onto the screen trying to figure out how to make a missile instantiate and explode we're kind of stuck at that point right now and so you know and we'll probably go once we learn how to do stuff in Unreal we'll probably go in and start to try and look at other and kind of reverse engineer them and see if we can recreate parts of different popular games and talk about them and review them and stuff like that you know the shield system in Halo you know we could look into that and see what would it take to recreate that in Unreal and we could have a fun little live stream series where we try and do that in two hours or something and then we could when the new Smash game comes up maybe we could try and see if we could make a little Smash engine and see what we could do once we get to that point so T-Rex in a tank and an F-22 no we could do that we could do that kind of crazy stuff once we figure out how to use the engine that's what I'm trying to say we're stuck in the boring part right now so I already know that the next 15 videos I've got uploaded for you guys are really boring 30 seconds long each and they're probably not going to get too many views because there's not a lot of people looking for this specific information but I'm uploading them because I think they're important for you guys right like as far as like channel statistics go it's not really, it doesn't help my channel too much at this point to like upload 30 second tutorials but I just feel like it's the right thing to do so I'm going to continue to do that but yeah if you guys just continue to be awesome and leave likes and leave comments and just share things and shout out on Twitter and stuff like that then I think we'll be alright because I mean that's so far it's been pretty good so I'll read a couple more chats and then we'll close this video I want to know how to make adventure cookies and cream oh man you know what we could do we could turn cookies and cream into like a sexy anime wifey like that could be a heart competition on our discord you know do you know how to do A2D elements and such that would be an interesting series actually bro that is literally what I'm going to show you in the next two weeks like literally so you just just just hang tight that is literally what we're going to come literally we are actually covering that next so yeah just just just just hang tight like tomorrow you will see videos on that 30 vids are now how I thought uh I know I know the thing is like the algorithm just doesn't post him because when I make a video a 30 second video that does this job and you get the information that you want you do what you're supposed to do when you go back to work because now you have the information and when you do that like like if you look at if you come to my channel you have a question and you're like oh wow that's how you do it then you leave youtube and you go back to blender and you start to do your thing youtube sees that you left youtube right after watching my 30 second video so youtube specifically knows hey don't recommend these videos because every time we do we lose a viewer so my 30 second video is really especially now in the algorithm my 30 second video you're only going to find them if you like so that's how it is right now just because the algorithm is really good at knowing like what to recommend and based on what youtube wants so bit late to stream okay I want to let you know interested in playing some older armor for game tv see how modern this is we will probably visit some of the older armor for game go stream later I think that's something I've always wanted to do I just haven't had time to do it you may not get promoted by algorithm your videos are often the ones that cause problems really? I didn't know that but that's good to know man that's my saving grace because really if they don't then nobody finds it does a good fighting game on your tutorial for like the longest time before though I'll have to check it out well we'll check it out when we cross that grid yeah I reckon it makes sense well anyway it's getting pretty late over here where I am so I just wanted to say thank you so much for all of you guys being in the stream it's been fun, it's been awesome and I really really appreciate it like seriously it's been really good and I look forward to continuing to keep up the work all the way to 500,000 subs I'm still going to be over here doing my thing trying to make the world a more accurate, simpler easy to learn place so definitely stick around, I'll see you in the next video again I've got a bunch of under this tutorial ready to go so if you're interested in Blueprints then you'll just literally wait till tomorrow and you'll see a couple and you'll probably see a couple like two or three a day for the next four days probably so yeah anyway thank you guys, I'm going to go ahead and turn off the stream but as always I hope you have a


So 3,500 is what you would need to spend for like a clinic to be able to get them to have everything because that's what I wanted all the frequencies so that we have for a clinic about $5,000 will get you all the frequencies plus this plus the kit five to $6,000. Yeah, yeah, that that would be, you know, we call it like the professional package. Whereas somebody that is on a budget, right, they can just get the Chico mini. There's just one coil with eight free frequencies. And you can subscribe for $10 a month and you get 10,000 right frequency. So that's basically what everybody needs. And that's 399 so and it's financeable. Very, very.


Good morning or good afternoon depending on when you're joining us from today and a very warm welcome to everyone Today we'll be covering effective load restraint and we have a special guest presenter from Blue Scope Steel Now this particular webinar is part of the National Road Safety Partnership Program webinar series and a little bit of information on that for those of you unaware The NRSPP has been established to provide a collaborative network for Australian businesses and organisations to help them create a positive road safety culture both internally and externally It aims to help organisations of all sizes across all sectors to share and build road safety initiatives specific to their own workplace and beyond It's delivered by ARB and funded primarily by Government Coalition and ARB For more information and more tools like this webinar please refer to the NRSPP website Now as I said we've got a very special webinar presenter joining us today and I'll introduce him in one moment My name is Angela Yuhas and I will be your friendly webinar moderator today If you do experience any issues along the way or you have any questions please feel free to get in touch with me at any time Now for today's session we've allowed approximately 60 minutes total About 40 minutes of that will be spent on the presentation and we'll be taking questions throughout So please don't be shy, get your questions through to us and we'll be happy to deal with those as we go We are also recording today's session ladies and gentlemen and so there's no need to take notes All of the presentation material as well as the recording will be sent to you once the webinar has concluded Now as I mentioned before we welcome questions and discussion and if you would just look over to your control panel You'll notice a questions box, we ask that you type those in here and I'll make sure that Graeme gets them throughout the presentation and gets back to you on those Now without any further ado I will introduce our man of the moment so his name is Graeme Agnew Now Graeme is a logistics engineer with BlueScope Steel and is recognised as a leading expert in the field of load restraint and transport safety in the Australian steel industry having worked or consulted for various companies including BlueScope, ARIEM and Stramet With over 20 years operational and technical experience across manufacturing and transport functions Graeme has developed a practical hands-on approach to load restraint He's a mechanical engineer and also holds a Masters of Business and Technology through the University of New South Wales His current role as a logistics engineer with BlueScope He's been responsible for developing cost-effective and efficient transport safety solutions including the load restraint of a wide variety of loads as well as coaching and mentoring of drivers, loaders, supervisors and managers in their application A very warm welcome to you Graeme on this rather cold winter's day here in Melbourne How are you going today? Good Angela, how are you? I'm very well thank you and thank you for your time in preparing today's presentation and delivering it for our audience I'm sure we're all very keen to learn more about the good work of BlueScope Steel and this particular initiative So I'll hand over to you Okay Angela, absolute pleasure Alright, so firstly I thought I'd just give you a bit of background into who BlueScope Steel are Just so you can understand where we come from around this issue of load restraint Basically we are a global manufacturer and supplier of steel products and solutions Basically across the world with 17 countries employing over 17,000 people We have more than 50 facilities across the Pacific region and nearly 100 distribution centres just here in Australia with almost 8,000 people As far as that we also operate the largest steelworks in Australia here at Port Kemble which is where I'm based And basically that has an annual production capacity of around about 2.6 million tons of goods I'm sure many people have probably seen some of our brands in the past Things like Colobon, you'll see those ads on television Products like Zikaloon, Lysart and in the last 18 months or so we've acquired a couple of other well-known businesses And it's grown still in the screen of the builders and in what kind of steel The important part to understand about that is what BlueScope Steel is BlueScope is actually not a transport operator Basically less than 1% of our transport costs would actually be done on company-owned vehicles So primarily we are a loader, hacker, consigner, port receiver One of the things though that has happened in that time is back in the mid-1990s BlueScope Who was BHP Steel back in those days Realised that securing heavy steel products on trucks was a major risk to its employees, contractors and the community And basically started looking at ways to minimise that risk Across the steel industry we have seen a number of serious incidents which have included fatalities And basically that has occurred to both drivers and also other RAID users As a result of having loads that were incorrectly explained BlueScope itself, BlueScope is recognised as a leader in safety within the steel industry worldwide And basically one of the things that we do is we manage our high-risk activity in what we call codes of practice These are codes which sit across all our businesses And basically they set out the minimum standards or sites And also our service providers to adhere to And those high-risk activity such as mobile equipment, overhead grains, product storage and labour strength All up there's about 12 of those codes of practice in our business And as we said, labour strength is one of our major risks and hints as one of those codes of practice attached to it Alright, so that's just a bit of a background as to where we come from and why we take this seriously And that's probably where the real story begins right now and here as to what is effective labour strength And look, I understand that the BlueScope approach to labour strength is probably not right for every organisation But if you adopt two of the key models that we're going to discuss, it's possible to demonstrate compliance And when I look at what that compliance looks like Now I regularly, you know, people like the regulators talk about China responsibility And they kind of talk about three things They talk about information and instruction, training and equipment And I'll go into those in a bit later Because it is a holistic system that you need in order to manage labour strength So if I look firstly at information and instruction You know, we need to make sure that our people, both our employees and contractors Know how the load is to be put on the vehicle What the vehicle and equipment is required to restrain the load And how that restrain equipment must be applied Secondly, we need to ensure that our personnel are trained and competent to complete the tasks that they need to do And finally the second part is the auditing section So do work practices comply with instructions? Are personnel appropriately skilled? And is the equipment being maintained? And generally speaking, when I hear the regulators actually talk about compliance with COR requirements such as labour strength That third element, that auditing phase, that supervision Making sure people are actually complying with those systems Generally the one they say is fairly well done But look, the focus of today's webinar is to show you how we manage labour strength Using two different models Basically and show how we stop loads from coming off trucks And causing damage to both people and product Alright, so as I said The thing with BlueScape is that we are not a transport company primarily We primarily are a consign And really as far as consigning We have an effective system We can contract management with the actual product element of that Transport providers who work for BlueScape Steel Basically expect to sign up to what we call the Australian Steel Industry Logistics Safety Code And that safety code was actually developed by BlueScape and once steel And it's actually aligned with the actual National Logistics Safety Code Basically what that code requires is the contractors and sites that are working for us Have evidence that they've met a number of key criteria So they make sure that we have their trained equipment That their load Australian equipment is up to standard Meets the relevant requirements And that they actually have guidelines around how those loads must be trained on their vehicles So what we're basically doing by going through that code And auditing our contractors against that Is actually pre-qualifying those contractors Before they actually even come onto site So when I talk about the two different models that we use These are the two real models that you have in your business The first one is what I would call the contractor-based system And basically this is where you would go to the contractor And basically get them to develop an engineer labor strength system So what we do is we say to the contractor, look you've got some expertise in this You come to us with a system that meets the right About the legislative requirements of labor strength We then would review that system And if it's acceptable we would approve it We then would monitor that system through our contracts management process And basically part of that would be our contractors showing us Their compliance around auditing And also their compliance around You know, if they've had an incident How they actually manage that and what corrective actions They've actually been permitted to prevent further breaches from occurring It is From a contractor point of view Sorry, from a consignor point of view it is the simplest solution Okay, because what we're doing is we're getting them to do the work In the background around developing the system and we are simply monitoring that However, in our experience most of our contractors Don't have the hearing resources to be able to develop an engineer labor strength system So what we've basically done is In most cases we've adopted what I call the consignor model Where basically we have a team of specialised and experienced house engineers And basically what we do is we develop guidelines for them Based on our knowledge of over-straint and also different products And basically allow the contractors to adopt those And as I said, the vast majority of cases That's what happens within our business Okay, so as far as information instruction I'll talk a little bit about this now So why is it so important to have an engineer labor strength system? So I would compare this to driving down the highway And I'm going to go over a bridge You know, I want to make sure that when I go over that bridge Somebody has put some diligence into that Okay, so they've made sure that when they're designing that bridge That they've taken account of the weight of the vehicles going over that bridge You know, that bridge can take the loading of wind kind of push it sideways You know, you don't want to go over that bridge thinking Oh, you know what? The laborer on this job was the guy who selected the size And the strength of the metal girders that we're going into When I drive next to a truck out on the road I want to know that somebody has also put that same level of diligence The reality of that though is in most cases The restraint of most loads out on our roads Are left up to the driver And the truth of that is that most drivers Basically don't have any training around labor strength Or have very limited training And most of them don't understand the principle of labor strength I'll give you an example of that A couple of years ago I was training a driver who was new to our business And he came up to me at the end of the session and he said He said, I think driving a truck for 20 years And he goes, no one before today had actually told me What illegal requirements were for labor strength Until he used to put it up at the top of this class To me that was fairly scary to think that someone could do a job for 20 years And not understand, not know there was a legal requirement For a job that they're actually doing So what are the legal requirements? So for people who don't know The legislation around labor strength in Australia Comes out of the book that you see on the right hand side It's called the National Transport Commission Labor Strength Guide Meaning that guide, it sets out performance standards The load must be restrained And that performance standards are shown there in that diagram But to comply with the legislative requirements For a rail transport here in Australia Basically you must restrain 80% of the load in the course direction So if I had a 10 ton load I'd have to have equivalent of 8 ton of restraint 50% sideways and rearwards 10 ton load I would need 5 ton of restraint Vertically 20% So 10 ton load I would need to have 2 ton of restraint Now that's not as easy as it sounds And to make you understand that a little bit better Another example I was about I looked at a load once a couple of years ago And I actually went up to the driver And I asked the driver how much restraint he had on that load And the driver basically said Oh it's simple He said up to 10 ton I need 2 ton I asked the driver how did he work that out And what he said to me was That basically he needed to restrain 80% of the load forward So that was 8 ton And basically then 2 ton chains 8 ton of restraint Unfortunately it's not that simple as you'll see shortly And it's the reason why we need to have an engineering system Other requirements that the law also requires Is to set out in those performance standards That the load should not come dislodged from the vehicle And the load cannot adversely affect the vehicle Stability or weight distribution when it sees one of those forces outlining Graeme sorry to cut you off there I've had a couple of our audience members Just note that your audio is a little bit fading in and out I just wanted to make sure that the microphone is all clear at your end Sorry about that, yeah As far as I'm aware, yes Okay beautiful, thank you That's enough? Yes Okay, so as I said the reality is it's not that simple The truth is that load restraint is actually the size Now generally speaking the load restraint relies on three mechanisms To prevent the load from moving Frictional force created by the weight of the load itself Frictional force created by the clamping force applied by the restraints And the strength of their equipment used to restrain the load Either by blocking, containing or attaching to it So, once a look at an engineered load restraint system The way that we would do it The way that it is done regardless of whether or not You're working on the contractor based model Or the consignor based model is starting with the TCC By restraint performance You can see that there over on the left hand side We then model that particular load And basically put it into a model A whole heap of calculations that basically look at all the potential Of AMO's for that load Things like sliding, toppling and rotating And then we take those equations And we put it into what we call the load restraint guideline For that product Which is then the documentation, the driver and the loader's receipt What makes this even more complex Is that many of the variables used in these calculations Are not straightforward either So, the experience has shown us that in a lot of cases The actual load actually works and behaves a lot differently To what we would expect So what we actually have to do is actually go off And test those assumptions to validate them What we're trying to do here is create a real-world situation So that we can verify those assumptions So the things that we would look at would be the friction between surfaces Impact of different load configurations The behavior of restraints The stretch in the restraints of the different tensions You know, all that restraint actually depends on that Another thing that we actually would look at would be the performance of the packaging Because the packaging, as we'll discuss shortly, plays an vital role in the actual load restraint So, what we then do is we basically have a number of different types of testing And I've got some photos there on the screen that you can see And I'll talk about these These are some of the trials that we actually did last year On something that you see quite often out on the road So you can actually see there where we've got some tilt testing You can also sometimes prefer to a static testing So if you look at the NCC guideline And what they will talk about in that guideline here The load up to a certain angle You can simulate the 0.8, the 80% forwards Or the 50% side waves So as I said, some bulk bags I'll show you a little video of some testing that we did So you can see there we did some testing And obviously that was a fail One of the things that we started to do when we were testing these bulk bags Was found that the coefficient of friction with those bulk bags onto the pallets Was actually much lower than what we actually were looking at So then we took those bags And we actually did some drag test, friction test You can see there where we have the photo Where we've actually put the bulk bag down on the ground We've got a forklift, we've knitted that up with a chain Forklift, we have a load cell to then measure the peak force And then we can determine what the actual friction value is After doing that we actually were able to get the required friction By actually placing some rubber on the deck And some more tilt testing And then we went to what we call dynamic testing Now dynamic testing is very similar to the crash test Dummy type test We've actually put the load on a truck Run it down a vacant, isolated stretcher road And basically on one of our sites And basically slammed on the brakes and actually hit the risk point We have a decelerometer that actually measures The actual deceleration of the actual load So yeah, that's the type In developing an in-community load restraint system That's the type of extending the indicator So as I said, that due diligence approach So look, it has been fairly technical up to this point The thing to understand though Is when you're doing this with the actual audience That you catering for So yeah, we've done this technical work But now I need to do something for the loader And the driver that they're going to understand So I need to use language that they understand And I want to try and cut down on the number of tests And also photos and actually use diagrams So one of the things is Drivers want to be able to look at their load And basically then look at a photo And that need to go Well, my load needs to look like that So if you look at those two photos You can actually see that actually The other thing that our guidelines Certainly focus on is what we call By fundamentals of load restraint So one of the things that we've actually done Is we've done a lot of analysis over the years Of our load restraint instruments And what we've found is that In the majority of cases, it can be loaded back To one of five fundamental principles These being packaging, friction, drainage No gaps and also the number of restraints So I'll talk a bit more about each of those So the first one is packaging And one of the things that you kind of look at As you go through and actually get those five fundamental principles Actually how many of these Actually are the responsibility of the designer More so than what they are the actual loader In a lot of cases, probably the first four are And certainly packaging will always be The responsibility of the designer Okay, so the packaging One of the things to understand about it Is it must be able to withstand the 80% And the 20% Because it needs to be able to hold that object With one solid pattern on the debris Now, it's near impossible for a driver To directly restrain the load And packaging is not right So what we have in our business Is a series of critical procedures For packaging And basically we can see there an example Of what comes out of our distribution business With small parts And basically the operators Are basically trained and audited Against those procedures As far as fundamental number two Friction And really this is the most important Of those fundamentals Okay, it is more important Than the number of restraints We want to make sure that if you've got Low friction surfaces, things like Steel on steel, plastic on plastic Plastic on steel, breaking those up With something like rubber The third fundamental that we talk about Is drainage So we also, the guidelines will spell out Things like the correct size and type The drainage and how it must be Orientated on the truck You can see there over in the cutout The example of the good and the bad Okay, we don't want things like Rectangular drainage on its drainage Because it's very easy for that to rot And that creates real problems Because of the plastic restraints One of the other things we talk about Is how to eliminate gaps Okay, so you can see there an example Again, the cross for the bad The tip to the good If I've got gaps in loads That's going to allow my restraints to And my restraints to come in So as I said, a lot of those first forward A lot of cases do come down to The actual consignment The people actually load in the load Not always, but in a lot of cases That is the case The drivers have Definitely have the actual Responsibility form It's actually making sure They have the number of restraints So what we try to do here Is take out all those complex calculations And do that up front for the driver And then that driver And the table Or the number of restraints To actually determine how many Are you restraining me So if you look at that table there It's fairly easy If you have a 12 tonne of that product I would need to have three chains On that load So one of the other key things About these guidelines Is basically their availability Basically those guidelines Are available to employees And contractors online Through a couple of different systems We also display Those guidelines clearly At the dispatch point There's some photos there of One of our sites And you can actually see those guidelines Clearly on display At the labourage area Here on this Drivers are also Required to carry a copy Of those guidelines That are relevant to their load With the new trucks And we actually put it that as part of the whole process Some cases though We will also take that Restraint system One step further And actually also not only The guideline Or the technical grade procedure But we'll also have to design Some type of equipment To go with it So why do we do that Well there's a couple of reasons Sometimes the restraint can be Complicated so one of the things We're trying to do whenever we do Is to try and stick to the method of restraint The number of steps to drive out And the loaders have to put on So we can reduce the potential Of human error And also increase the efficiency When you do that You want to think about things like Using systems that block and contain the load Because what that will allow you to do Is actually reduce the number Of restraints required There's an example there We can actually see what we've done That we had a lot Down in Victoria last year And basically what we had to do Was of course these tools were so narrow And the potential for them to topple To see how we developed the technical Document that actually needed This equipment that we actually developed To allow that to That product to occur And to be moved safely Okay So as I said earlier The guidelines, that information That instruction part Is just the first element The second element That I want to just go through Is our load restraint train Basically Regardless of whether or not You adopt either A consignor model Or a contractor model You need to make sure That our loaders and our drivers Are competent So contractually, Looscape Requires that drivers Are trained and competent So all contract drivers Are required to do that We also Train our employees as well And why do we do that Because we want them to recognise High risk situations And so they're empowered To basically group in Non-compliant loads from the other side Our training Basically Available both A large focus Of that training is actually Those five fundamentals that we've taken You can see there are a couple of slides there That actually show the type of things we do Fundamental two, by friction Fundamental three The dangers have done it One of the things we also do With our training is A large library of incidents That were collected over 20 odd years To provide impact And the reasons behind The requirements So here we have a case here around One of those fundamentals The roll and done edge The rectangular done edge on its thin edge Basically a driver in this case Had that rectangular done edge On its thin edge Basically that done edge rolled When he applied the brakes At a rail crossing And basically without the chance to come forward And basically the load stood Into the back of the cabin and crushed that Really give impact Or recently was training some drivers Who were going to start to carry this exact same product And when I was able to say to them Here's the fatality Of exactly the same product Like carrying You can start to see That would have on somebody In their lives One of the other things that we are now doing Is also starting to develop Training videos To try and show That someone actually doing it So I'm going to play one of those You can actually see where we're headed I'm sorry Would you mind turning the volume up a little bit So that there is just an example That's one of our shorter ones There are two different versions of that There's a long line which goes into a lot of the detail The driver would have As part of his initial training The version there is more just for A refresher So different types of training We have both awareness And training and competency based training And that depends On the person's role For example You know we We've got a sales person In one of our small regional branches We don't need Them to have the same level of detail As the driver or the provider But we also want them to have some understanding Of what those higher risk situations are So if they see something Down on site they can actually stop that load From going out incorrectly with strain They may also have a discussion with a customer Who's going to pick it up around what The requirements are So we want them to have some awareness Of what those requirements are With the But for people like drivers and loaders There are higher requirements Which are the competency based requirements Basically our drivers Are required to complete theoretical tests And basically That Around some of the stuff we've seen And basically that then Is also tested practically They are audited By the supervisor on their first load To actually confirm their practical Competency The record Of that competency Is then actually The driver's passport So that if anyone goes to order That driver out on site That's very easy to verify Whether or not that driver has the right training That training is then Refreshed So the driver is required to go through that process To get it retrieved Or if there's a major revision There's an actual guideline There also need to do as well The third element Of Instructing and supervising that That System and we do that through our auditing Process As I said earlier This is the one that when I hear the regulators Talk is not very well done But I'll run you through exactly how we do So Our contract reviews Whether or not it's a contractor based system Or a consignment model Basically Our contract review process We regularly meet with the contractors And one of the items On the contractor reviews is actually The local strength review Contractors In that process are required to report On any local strength failures They have What actions they're taking around those Players and also their Audits And we actually also have commercial Penalties in our contracts With our suppliers We also Monitor loads on an individual Basis and we do that through Our local strength audit program Basically, annually We review our products To determine the risk type So we put them into a matrix as you see down The bottom and basically we look at What the risk Of that product is based on Its history And also the number of local Failures and then we rank them Low risk, medium risk or low risk And basically we've ordered High risk products every 5% of loads Medium risk 3.5% and low risk Every Half of the I'll talk a bit more about that in one of the next couple of slides How we also adjust That in one result Basically then what we do Is decide In basically depending on The number of loads that they actually dispatch And also what the product risk rating is They actually get an order target For how many loads they need to complete Every month Those local strength audits Come in a standard format They can be accessed Either by hard copy Or electronically So the technologies they have these days To what they are, people that actually Are using a tablet Technology such as an iPad Straight directly into the local strength audit system What those audits actually do Is require checks of Those essential requirements So making sure the actual person's been trained There's no low friction Surfaces That the actual They're following things like correct drainage Practices of the type, correct type The number of strengths in that Their equipment is even Equal to them One of the other parts of this as well Is it's not just about compliance But it's also an opportunity to follow up On the driver's training So often no one talks to the driver About load restraint after he's trained Unless somebody doesn't want it So it's a good follow up process For us around that It's also an opportunity for drivers And loaders to get the results So there's opportunity to be on that form To write any comments the driver might have So that we can process that Back through this We can then look at That might be needed to the guideline Basically we have Across Australia about 160 different Dispatch points And we would complete somewhere In the facility of 3,000 The 3,500 load restraint orders Across those sites Every month All that information goes into The database and we actually use That database to identify Any changes that may be required For any training requirements A couple of years ago we had Some statistics In our distribution business That's there And basically we organized A major intervention in those sites Right across the country And basically training up their people And that type of thing So that we could improve Their performance and we actually saw A marked improvement and have Their performance around load restraint To resolve that and monitoring that screen Across our business We actually target An order compliance of 95% And if a site Does not meet that Compliance of 95% What we actually do Over a three month period if they don't meet that If those actual targets That 5% provider is Loads would actually Get increased to 7.5% Okay they'd need to Order 7.5% of high risk loads Of loads for the next three months And then we would continue To monitor that and they wouldn't Drop back to 5.5% The requirement, the normal requirement Until they've had three months Consected in the building Above a 95% compliance Alright so the final little section Of our presentation today Is just about the future I want to give you some ideas Of the stuff we're starting to look at As far as load restraint is concerned Some of the things that we're starting to do Is actually Develop And use smart technology So we're starting to do Because I put go-pros on trailers To actually monitor The weights and transits To give us some more guidance On how they actually behave And that type of thing We're also using it as a bit of a training tool You know, show drivers and loaders Different parts of the actual process And we're also Develop what we call A smart phone app Which we're calling Steel Drive And I'll show you that In a little bit of an example Over here This is still in development The actual developer Still developers are telling us That it would be available Towards the end of November But this is where we're going with it So this is a driver This is an app that's being developed for our drivers So it would come into a little screen Like this As you can see here The name and password And then basically when it comes through It would then Come into this section here And basically it can then Come into here with different locations And you can see here Like this is my little finger Pretend that's my little finger on the screen They're scrolling through And I click on it's all touch screen And you can come down here It gets the details of Loading sites, details on the loading sites That type of thing And also any So as I said some of the data in here is not here But you get the idea The PPE requirements Things around Exclusion zones That type of thing That type of community facilities And also You know, the closest Way stations and rest stops And petrol stations That If that location Is part of the driver's Favourites It also would receive notifications So for example If that site The fork was broken down and we couldn't load for three hours That's the type of information The driver would notice Not get notifications So it gives us some idea Or some help Also manage our fatigue management The other information Look it's primarily been set up Around labor strength though And you can actually see That I was to click on here The driver then gets Information on the different guidelines As I click through You know depending on the product it would tell him How many restraints that he needed Back over here If I was to go through Sorry You can actually go down here as well And if I was to click on this one You would get For that product The video similar to what I showed earlier Alternatively You would come onto here And you would get our hard copy The whole copy The information's not there The other part of this as well Basically Is what we call load capture So one of the things that we want to do Is start to record Data from the actual loads And basically two reasons for that A, we're going to get the driver to actually take a photo Of the actual restraint And the reason that we do that Is another process So it's another thing the driver actually has to look at So he can't have a lapse In concentration and actually Something in the process And also it gives us some record Of how the load was actually restraining As I was to go through this I would Get a different product that I'm doing You know who I've carried for And then I can click on one of these Take a photo of the load And then there's a limit of eight photos He can actually take Goes into this database The driver then would press submit Except And that then is uploaded to a system And that stays on that system For a period of 30 days Allow us to review that The driver can also see that On his smartphone And basically scroll through and get those details Of that particular So thank you very much guys For listening today I hope you've got something out of it And I'll hand back over to Angela Thank you so much Graham Brilliant app concept We have had a couple of questions And I think it was November, December You said that it was ready to be Released, is that right? The information That I had from the developers In November, last week Was that they were looking at Late November, early December For implementation As the first phase of that Brilliant Well I look forward to seeing the final product That was great and thank you so much For taking the time to deliver this session I'm sure that our audience did get A lot out of it Now we do have a few questions And unfortunately only 10 minutes Remaining in the webinar So I'll select a few to ask Graham So I do apologise if we don't Have time to address your question today But Graham's details as you can see Are on there on your screen And we do welcome you to get in touch Any time if you'd like to discuss Your queries further I'm sure Graham will be more than happy To take your call or email Okay We've had a question here from Mark Mark is asking What are your thoughts on restraining loads Using standard alloy gates And 2T web straps Over the tops of the gates It depends On the load In a lot of cases I'd probably say It's not It probably doesn't meet the requirements But I I know in some cases where it can Different loads are different I would personally prefer To see those Webbing over the actual load Rather than Through the gate and actually Lamping down the actual load Rather than relying on On Those webbing following the gates In place. It does work in some Cases of loads But I'd be certainly concerned About it trying to Restrain something like a pallet On a trailer Great, thank you for that question Mark A question here from John And John's asking Have you found statements In the load restraint guide That are not in agreement with the blue scope Load restraint guidelines What approach do you take in dealing With such conflicts So For us As I said one thing that we do Is we actually start with The actual Legislation That's the only part of That actual line Legislation The rest of that Okay so we All our loads actually With those performance That's our basis to work from The rest of the Adjusting Alrighty another question here from Mark Can I ask why blue scope has only Released the documents as guidelines And have not had them certified To meet the performance standard Tricky one It is something that We have Discussed over the years And it has certainly You know there's been a lot of discussion over that And something that we are still looking at It's not something That There's been a decision in the past May that Was potentially we can see The real benefit in doing it But there's been You know Certainly it's an ongoing discussion The process The process to actually Certify those guidelines Is one Step that You know there's been some discussions In the past that regulate About So it's still something we are certainly looking at Right Okay a couple of questions here from David now David's asking About getting access To the guidelines and using them In their own training Material and he's referred to The videos that you showed during the presentation As well so are they available For our audience to Access view And reuse in their own organization So what would you suggest So Start with Any of that stuff that we've Got is available To people Who have agreements With us so it's not just People that want to deal Strammets seems to those companies We have agreements with certainly have Access to those Guidelines as well as Our carriers That actually transport providers People are told K&S Who work very closely with us They also have access to that So we've developed that and seen We've got an agreement with you guys Or you guys are working for us We're going to give you that information And So that's how it There's some thoughts about Also Widening back to what they are Other people to access them But that still Discussions around that at this point in time But if people Wanting More information that are outside of that group And they wanted to contact them We could certainly have a look at those requests Alrighty No worries at all Now we have had a couple of questions Presentation material and recording So just to reiterate Everyone that's participating here today Will be sent a copy of the presentation material As well as the recording Of today's session So you'll be able to review that at your leisure Share those with colleagues perhaps As I said Any time that's convenient You can have another look at that So thank you to everyone who Sent through questions relating to that We do have a couple more Questions So we might get time for one or two more A question here from Ian, Ian's asking Are chains used Are chains used for this presentation Grade 8 And 8mm So All our guidelines that we actually use Are 8mm Chains that meet the strain standard AS 4340 All our guidelines are based on those The only time that we've had to go To chains which are higher than that Is when we've had We had to do a guideline For one still around excavators And because some of those Were like 65 ton Basically we had to Go to n and 13mm chains But certainly any of our guidelines The minimum requirement is 8mm chains to AS AS 4340 Great Well thank you for that question And I hope we've managed to clarify that for you If not get in touch with us For a bit more discussion Alright one final question To finish up our webinar this afternoon Or this morning Depending on where you're joining us from The question here from John is Have you had on-road enforcement people Question your guides Would you have dealt with that? So In answer to that yes we have We have And generally speaking There is a fairly good relationship Between this type And regulators and we have Some of our senior managers Are certainly part Of The safety council And that type of thing In fact one of our general managers In the safety committee For Australian logistics There's a fairly good working relationship there There has been questions About it and there was A case Recently But basically Was not That was raised by an inspector We Challenged that together with Others that were in that supply chain And basically that case Was actually dropped Before it went Based on the fact that we had all the engineering Proved that the actual system Was compliant There is one other little bit to that as well We are now actually Basically adding some Additional comments to our guidelines To basically say That they are designed To meet the Australian Locust Bank performance standards That's an additional thing That our guide wants as a result Of that Place Great, alright Well on that note I will bid our audience fair Well and take this opportunity To thank them once again for joining In today and we really hope that You gain something valuable From today's session As I said if there's any part Of today's session that you'd like to review You will be getting that presentation Material shortly So do keep an eye on your emails Graham a big thank you to you For putting together this presentation And sharing your story with us It's certainly been insightful for me So look forward to that Out becoming available As I'm sure many of our audience Is also Yep no problem pleasure Beautiful Alright thank you once again And we hope you can join us for future webinars There will be a short pop up Survey that will pop up on your screen Ladies and gentlemen as I close down the webinar It's just a few short questions And if you could kindly let us know how we went today Be very grateful Thank you all and hope you can join us next time Bye bye


Welcome to Scientific Reports! If you are looking for an open access peer-reviewed journal to showcase your primary research from the natural and clinical sciences, you've come to the right place. Our goal is to let the community at large determine the impact of your work. That means while all papers we accept must make an original contribution, our editorial decisions focus on the robustness and validity of your research and not on subjective measures of perceived interest. Want to learn more about our editorial process? Let's talk about what happens to your manuscript after you submit it. Your manuscript is first checked for compliance with our editorial and publishing policies. These policies are based on the standards set by Nature Research and are some of the most rigorous in the publishing industry. We'll ensure your manuscript contains everything that's needed for our editors and peer reviewers to perform a fair and thorough assessment of your work. This includes checks on authorship, competing interests, ethics approval, plagiarism and image integrity. The process is overseen by a dedicated team of manuscript assistants whose job is to help authors ensure that their papers comply with these policies. If your manuscript passes our initial quality check following our standard process, we will assign it to a member of our editorial board. This individual will be an active researcher in your field and they'll be the one deciding whether your manuscript is suitable for peer review. It's the responsibility of the editorial board member to choose appropriate reviewers. Their choice is based on many factors, including expertise, previous experience and any apparent conflicts of interest. The editorial board member will ultimately decide how many reviewers are needed to evaluate your work, usually it's two or three. The reviewers will be asked to assess your paper based on the technical soundness and scientific validity of your methods, analysis and interpretation. The methods must be appropriate and properly conducted and the conclusions must be fully supported by the data. The editorial board member will consider the reviewers reports when deciding whether to accept your work as is, request minor or major revisions or reject it. A decision to reject a manuscript would occur if the editorial board member feels your work would not be suitable for publication even after revision. Published manuscripts typically undergo one or two rounds of revision before being accepted for publication. One of our large team of publishing assistants will assist you throughout the review process. If your paper is accepted, it will be prepared for online publication and you will receive a proof. Once your paper is ready, we'll let you know the publication date before it's made freely available to millions of readers. Ready to submit? Click on the link below to get started.